For the repository organization, I propose the
following :
xlet/ (
http://svn.xwiki.org/svnroot/xwiki/xlet/)
|__applications/
|__trunk/
|__xapp1/
|__xapp2/
[...]
|__xappN/
|__branches/
[...]
|__tags/
[...]
|__extensions/
[...]
|__macros/
[...]
|__modules/
[...]
|__plugins/
[...]
|__skins/
[...]
Each of the first level sub-directory (applications, extensions,
macros,
etc.) having the same meaning of is currently defined on
code.xwiki.org
WDYT ?
+1
Note: It's important to write somewhere clearly that Xlet projects are
not done by the xwiki dev team and not supported by the xwiki dev team
(and thus that the quality depends on the contributor(s)).
It could also be mentioned that at some point an Xlet project could be
elected to become a platform project if the interest is generic, if
it's voted and if the quality is good enough.
Thanks
-Vincent
Jerome.
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.
>
> 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).
>
> 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.)
>
> And my +1 for this second proposal
>
> Please, let me know what you think
> Jerome.