[xwiki-devs] [VOTE] SVN reorganization proposal
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
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 Ludovic 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
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
Hi Ludo, On Jul 23, 2008, at 3:21 PM, Ludovic Dubost wrote:
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 ?
Some ideas: 1) We decide what projects we accept of course so it's not like we're going to have hundreds with semi dead projects. Also all projects start in the sandbox and are promoted only when they're ready. 2) "Xlet" is meant to be a project for storing sources of macros, applications, plugins submitted by users on code.xwiki.org. It's meant to be very open for anyone who want to work on them or add new ones. 3) I think the differentiation will be done on the forge wiki + by each project's wiki + by xwiki.org I see xwiki.org as the federator, listing the projects, highlighting some of them, etc. + a page listing all forge projects (we have that page actually but we can enrich it with status information). Obviously as the number of projects grow we'll need to refactor xwiki.org so that the home page scales + the Ecosystem panel will also need to evolve.
We might have a lot of different plugins places:
- in platform - in some applications - in sandbox - in xlet or plugins
Yes, each project can have its own plugins or any other type of code for that matter. What's important is that plugins that are important enough and generic enough go in the platform eventually (as we've been doing, nothing new here). You haven't voted, does it mean you agree? :) Thanks -Vincent
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.
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
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 for me too On Thu, Jul 24, 2008 at 9:14 AM, Jerome Velociter <[email protected]> wrote:
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.
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
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Jul 24, 2008, at 9:14 AM, Jerome Velociter wrote:
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
yes. Thanks -Vincent
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
On Wed, Jul 23, 2008 at 1:18 PM, Vincent Massol <[email protected]> wrote:
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)
+1. -- Jean-Vincent Drean
+1 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
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 Vincent Massol wrote:
... 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) ...
-- Artem Melentyev
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
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Starting now... Thanks -Vincent On Jul 25, 2008, at 10:20 AM, Vincent Massol wrote:
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
participants (7)
-
Anca Paula Luca -
Artem Melentyev -
Jean-Vincent Drean -
Jerome Velociter -
Ludovic Dubost -
Thomas Mortagne -
Vincent Massol