Thomas Mortagne wrote: > On Tue, Oct 6, 2009 at 14:45, Jerome Velociter <[email protected]> wrote: >> 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 ? > > I'm not sure it's the right way, i think i would prefer to have the > projects directly under xlet/ and have each project decide its own > organization. It's a real pain currently to release plugin and > applications which for lot of them should be released together, we > should try to go the right way this time for a new repository.
Don't you think it's good to have that distinction by type of project ? Do you think we can manage this by project names ? (for example "plugin-myplugin", "application-myapplication") It would mean making sure contributors name their projects properly (it's easier to have them create their projects in the proper directory properly IMO). Jerome. > >> 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. >>> _______________________________________________ >>> devs mailing list >>> [email protected] >>> http://lists.xwiki.org/mailman/listinfo/devs >>> >> _______________________________________________ >> devs mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/devs >> > > > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
