31 Jan
2014
31 Jan
'14
8:35 p.m.
Hi,
This mails wants to cover two topics:
1. Improving/cleaning/standardizing a bit the current tags added for e.x.o
entries;
2. Proposal to use the tag system to mark the extension's compatibility
field.
------
1. Currently we have 545 tags for 660 extensions (with 705 pages in
Extension space). Also we have 367 pages with no tag found in the Extension
space.
The idea is that I will want to clean a bit the useless tags and keep just
the relevant ones. Having useful tags will improve the findability of
extensions. Also all extensions should have a tag (right now we have
extensions without tags). Tags should be written using small-caps.
The current tags are a bit more complex because right now e.x.o also
contains 'Snippets' and their scope can be much broader.
The current extensions 'Types' (JAR, XAR, Plugin) are very technical and
not intended for end-user.
I've investigated a bit the tags used on e.x.o and you can see some results
here:
By Count:
http://design.xwiki.org/xwiki/bin/download/Proposal/RepositoryApplicationIm…
By Type:
http://design.xwiki.org/xwiki/bin/download/Proposal/RepositoryApplicationIm…
By Keep:
http://design.xwiki.org/xwiki/bin/download/Proposal/RepositoryApplicationIm…
The tags investigation images contain a 'Keep' (Y/N) column. If a tag is
marked as 'No keep' we should remove that tag (in some cases I provide an
alternative found in 'Type/Category' column). This is the first
organization, we could further improve on the categories/tags.
Having some 'standard' categories but also having multiple extensions share
the same tag/category will let us have something like 'Related extensions'
in the future.
Also very important is to 'standardise' the
'deprecated'/'obsolete'/'archive' tag to mark old/unmaintained
extensions.
In the future we could display the deprecated extensions in a separate
place, maybe called 'Archive'.
------
2. Right now the 'Compatibility' field of extensions is a free form
textarea. This is bad when you want to filter working extensions for a
specific version. Example:
http://extensions.xwiki.org/xwiki/bin/view/Extension/ForumApplication
Adding something in the 'Compatibility' field means that the extension has
been tested with that version and not that it works only with that version.
Using tags for the 'Compatibility' functionality will improve filtering
(and maybe reporting). Also we could parse tags and display in top
Compatibility section just the numeric tag entries (that will correspond to
the tested versions).
The format would be the same as in JIRA: '5.2.4', '6.0-milestone-1',
'5.4-rc-1', '4.5.x', etc.
Let me know what you think,
Caty
