It would be nice to be able to differentiate major projects vs simple extensions and plugins. Maybe that's what 'xlet' is for ? Or do we need a "plugins" directory ?

We might have a lot of different plugins places: - in platform - in some applications - in sandbox - in xlet or plugins

Vincent Massol wrote: > Hi, > > We need to better organize our SVN repos. Some current needs/issues: > > * Curriki needs its own svn location outside of main xwiki devs > * Chrono is currently outside of the main svn repo. Same for Sandbox. > * We'd like to offer a forge for xwiki -related project (for example > for the xlet project) > > We had a discussion before and I think we agreed to have a single SVN > repo vs one for each project. > See http://tinyurl.com/69c4bx for more details. > > Hence I propose the following new structure: > > https://svn.xwiki.org/svnroot/xwiki > |_ platform/ > |_ curriki/ > |_ sandbox/ > |_ enterprise/ > |_ enterprise-manager/ > |_ watch/ > |_ workspaces/ > |_ xeclipse/ > |_ xlet/ (or whatever name we choose for it) > > The idea is: > * Top level directories are projects. > * As such they get their wikis on xwiki.org (<project>.xwiki.org), > they are identified by the Committers group in that wiki. > * They also get a mailing list (they can use an existing mailing list > though) > > Thus we remove the notion of extensions and products and we replace > it > with the notion of projects which can be anything. This is more > scalable and in line with a forge idea. > > If we're ok I'll work with Raff to set this up and to modify all web > pages which have the SVN URLs (like ohloh, freshmeat, etc). > Developers will need to perform a new co. > > Here' s my +1 > > Thanks > -Vincent

Hello, It sounds good, I'm +1 Just to be sure : the levels under this new top level stay unchanged ? For example platform would remain : platform |_applications |_core |_plugins |_pom |_skins |_tools |_web Regards, Jerome. _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Result: 6 +1, no 0, no -1 (one unknown answer from Ludovic but I assume he was +1 or 0) Now the question is when do we do it? Does anyone has any constraint? (remember you'll need to do another check out of your sources and move your changes). If nobody disagrees I'll start the migration this afternoon. Now is a good time I think since several are on holidays and it's a "slow" period. Thanks -Vincent On Jul 23, 2008, at 1:18 PM, Vincent Massol wrote: > Hi, > > We need to better organize our SVN repos. Some current needs/issues: > > * Curriki needs its own svn location outside of main xwiki devs > * Chrono is currently outside of the main svn repo. Same for Sandbox. > * We'd like to offer a forge for xwiki -related project (for example > for the xlet project) > > We had a discussion before and I think we agreed to have a single SVN > repo vs one for each project. > See http://tinyurl.com/69c4bx for more details. > > Hence I propose the following new structure: > > https://svn.xwiki.org/svnroot/xwiki > |_ platform/ > |_ curriki/ > |_ sandbox/ > |_ enterprise/ > |_ enterprise-manager/ > |_ watch/ > |_ workspaces/ > |_ xeclipse/ > |_ xlet/ (or whatever name we choose for it) > > The idea is: > * Top level directories are projects. > * As such they get their wikis on xwiki.org (<project>.xwiki.org), > they are identified by the Committers group in that wiki. > * They also get a mailing list (they can use an existing mailing list > though) > > Thus we remove the notion of extensions and products and we replace > it > with the notion of projects which can be anything. This is more > scalable and in line with a forge idea. > > If we're ok I'll work with Raff to set this up and to modify all web > pages which have the SVN URLs (like ohloh, freshmeat, etc). > Developers will need to perform a new co. > > Here' s my +1 > > Thanks > -Vincent