6 Oct
2009
6 Oct
'09
2:52 p.m.
Hi Jerome,
On Oct 5, 2009, at 6:00 PM, Jerome Velociter wrote:
Hi all,
The subject has been discussed already, see for example
http://markmail.org/message/h5e2qinrhsf2slww
The idea is to create a new top level project for modules (modules in
the sense of everything applications, macros, components, plugins,
skin
extensions, etc.) that are not part of any products (or the platform)
and that are not necessarily contributed by the XWiki development
team.
What needs to be mentioned is that it'll be open to anyone who ask for
it.
The difference with the sandbox is that sandbox is a
place for modules
being incubated, and that are not in a finished state. Thus, I think
one
of the rule for introducing new modules in the xlet repository would
be
that a functional version of the module should be released and
available
for download (for example on code.xwiki.org).
I'm ok with this but it also means that we should allow anyone who ask
for it access to the sandbox so that there's a path from sandbox to
xlet. It wouldn't be mandatory but people who want to start coding int
he sandbox could access it.
The name "xlet" is the name we've use
historically to talk about this
repository, this is open for discussion. (personally I like the name -
we have to agree this is how we want to name a XWiki "pluggable
module"
in the large sense).
Here is my +1 for the above
I would also like to propose that we create a new category of JIRA
projects : "XWiki Contributed Xlets" (or equivalent name) for such
projects that desire to track issues for their released module, and
have
the tracker hosted by XWiki.org. I believe this will make easier to
have
real release cycles for such modules (for example, we can link to the
JIRA project from the code.xwiki.org "module" page so that users can
report issues instead of using the comments, we can use JIRAs
changelog
for release notes on the download page, etc.)
+1
Thanks
-Vincent
And my +1 for this second proposal
Please, let me know what you think
Jerome.