[xwiki-devs] [VOTE] Directory/Git Reorganization re platform vs extensions
Hi, After brainstorming with Thomas, Sergiu and Fabio we came to the following idea: Proposal ======= * Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version) ^^^^^^^^ This is the important part! Pros ==== * Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors Directory org ========== platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/ Details: * Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?) Migration details ============= * Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org). Here's my +1 (meaning I'll help perform this move) Thanks -Vincent
+1 too On Mon, Apr 4, 2011 at 15:04, Vincent Massol <[email protected]> wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On 04/04/2011 09:04 AM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)]
+1 tell me what to do. Caleb
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Here is my +1, but ... I am really too busy too really help. Denis On Mon, Apr 4, 2011 at 15:35, Caleb James DeLisle <[email protected]>wrote:
On 04/04/2011 09:04 AM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)]
+1 tell me what to do.
Caleb
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll
know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory
representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc)
* Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
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
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
On Mon, Apr 4, 2011 at 3:04 PM, Vincent Massol <[email protected]> wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
+1 for me I just had a thought about the granularity... Having everything in a big repo will make people clone more than 200Mb of source code even to hack a little module (currently xwiki-trunks on github downloads 277Mb of code). But maybe this is not really an issue. -Fabio
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 04/04/2011 03:49 PM, Fabio Mancinelli wrote:
On Mon, Apr 4, 2011 at 3:04 PM, Vincent Massol<[email protected]> wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
+1 for me
I just had a thought about the granularity... Having everything in a big repo will make people clone more than 200Mb of source code even to hack a little module (currently xwiki-trunks on github downloads 277Mb of code). But maybe this is not really an issue.
Most of it (140M) comes from xwiki-core, which is not a real module yet. And most of it comes from the very early history when we had all the libs in the svn. So, we could decide to drop the history before the introduction of maven, or we could move the core in its own repository and push for a faster migration to components. Or we can just learn to live with it, we have a long history and we're proud of it.
-Fabio
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
-- Sergiu Dumitriu http://purl.org/net/sergiu/
On Mon, Apr 4, 2011 at 17:12, Sergiu Dumitriu <[email protected]> wrote:
On 04/04/2011 03:49 PM, Fabio Mancinelli wrote:
On Mon, Apr 4, 2011 at 3:04 PM, Vincent Massol<[email protected]> wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
+1 for me
I just had a thought about the granularity... Having everything in a big repo will make people clone more than 200Mb of source code even to hack a little module (currently xwiki-trunks on github downloads 277Mb of code). But maybe this is not really an issue.
Most of it (140M) comes from xwiki-core, which is not a real module yet.
I am not sure it really worse to consume that bandwidth for such information. But how could we keep it online for reference in case we need to check it ? Denis
And most of it comes from the very early history when we had all the libs in the svn.
So, we could decide to drop the history before the introduction of maven, or we could move the core in its own repository and push for a faster migration to components.
Or we can just learn to live with it, we have a long history and we're proud of it.
-Fabio
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
On Apr 4, 2011, at 6:16 PM, Denis Gervalle wrote:
On Mon, Apr 4, 2011 at 17:12, Sergiu Dumitriu <[email protected]> wrote:
On 04/04/2011 03:49 PM, Fabio Mancinelli wrote:
On Mon, Apr 4, 2011 at 3:04 PM, Vincent Massol<[email protected]> wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
+1 for me
I just had a thought about the granularity... Having everything in a big repo will make people clone more than 200Mb of source code even to hack a little module (currently xwiki-trunks on github downloads 277Mb of code). But maybe this is not really an issue.
Most of it (140M) comes from xwiki-core, which is not a real module yet.
I am not sure it really worse to consume that bandwidth for such information. But how could we keep it online for reference in case we need to check it ?
I don't agree about removing any history. It looks to me that using git means using a lot of disk space (since you get a local repo with full history), we need to live with that or not use git at all. Thanks -Vincent
Denis
And most of it comes from the very early history when we had all the libs in the svn.
So, we could decide to drop the history before the introduction of maven, or we could move the core in its own repository and push for a faster migration to components.
Or we can just learn to live with it, we have a long history and we're proud of it.
-Fabio
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Apr 4, 2011, at 6:21 PM, Vincent Massol wrote:
On Apr 4, 2011, at 6:16 PM, Denis Gervalle wrote:
On Mon, Apr 4, 2011 at 17:12, Sergiu Dumitriu <[email protected]> wrote:
On 04/04/2011 03:49 PM, Fabio Mancinelli wrote:
On Mon, Apr 4, 2011 at 3:04 PM, Vincent Massol<[email protected]> wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
+1 for me
I just had a thought about the granularity... Having everything in a big repo will make people clone more than 200Mb of source code even to hack a little module (currently xwiki-trunks on github downloads 277Mb of code). But maybe this is not really an issue.
Most of it (140M) comes from xwiki-core, which is not a real module yet.
I am not sure it really worse to consume that bandwidth for such information. But how could we keep it online for reference in case we need to check it ?
I don't agree about removing any history.
It looks to me that using git means using a lot of disk space (since you get a local repo with full history), we need to live with that or not use git at all.
Note that there's still the github/svn integration so someone who really doesn't want the history can still get the source without the history using the svn integration. Last, we also publish source code in our maven repo and thus it's possible for someone just to get the sources for the version he wants to patch/build if size is really an issue (like if he's building xwiki on his iphone for example). Thanks -Vincent
Thanks -Vincent
Denis
And most of it comes from the very early history when we had all the libs in the svn.
So, we could decide to drop the history before the introduction of maven, or we could move the core in its own repository and push for a faster migration to components.
Or we can just learn to live with it, we have a long history and we're proud of it.
-Fabio
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
On 04/04/2011 06:21 PM, Vincent Massol wrote:
On Apr 4, 2011, at 6:16 PM, Denis Gervalle wrote:
On Mon, Apr 4, 2011 at 17:12, Sergiu Dumitriu<[email protected]> wrote:
On 04/04/2011 03:49 PM, Fabio Mancinelli wrote:
On Mon, Apr 4, 2011 at 3:04 PM, Vincent Massol<[email protected]> wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
+1 for me
I just had a thought about the granularity... Having everything in a big repo will make people clone more than 200Mb of source code even to hack a little module (currently xwiki-trunks on github downloads 277Mb of code). But maybe this is not really an issue.
Most of it (140M) comes from xwiki-core, which is not a real module yet.
I am not sure it really worse to consume that bandwidth for such information. But how could we keep it online for reference in case we need to check it ?
I don't agree about removing any history.
It looks to me that using git means using a lot of disk space (since you get a local repo with full history), we need to live with that or not use git at all.
Personally I don't find that "a lot". An unarchived XWiki instance takes 170M. 270M for having the 6-year history of over 35000 commits at our fingertips is pretty neat. Another thing is that forking doesn't consume users' space. Only the changes brought on top of the fork will be counted in their quota. So, unless someone has a very strong opinion against the current size of the repo, I'd like to keep it as it is.
Thanks -Vincent
Denis
And most of it comes from the very early history when we had all the libs in the svn.
So, we could decide to drop the history before the introduction of maven, or we could move the core in its own repository and push for a faster migration to components.
Or we can just learn to live with it, we have a long history and we're proud of it.
-Fabio
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
-- Sergiu Dumitriu http://purl.org/net/sergiu/
On Mon, Apr 4, 2011 at 6:43 PM, Sergiu Dumitriu <[email protected]> wrote:
On 04/04/2011 06:21 PM, Vincent Massol wrote:
On Apr 4, 2011, at 6:16 PM, Denis Gervalle wrote:
On Mon, Apr 4, 2011 at 17:12, Sergiu Dumitriu<[email protected]> wrote:
On 04/04/2011 03:49 PM, Fabio Mancinelli wrote:
On Mon, Apr 4, 2011 at 3:04 PM, Vincent Massol<[email protected]> wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
+1 for me
I just had a thought about the granularity... Having everything in a big repo will make people clone more than 200Mb of source code even to hack a little module (currently xwiki-trunks on github downloads 277Mb of code). But maybe this is not really an issue.
Most of it (140M) comes from xwiki-core, which is not a real module yet.
I am not sure it really worse to consume that bandwidth for such information. But how could we keep it online for reference in case we need to check it ?
I don't agree about removing any history.
It looks to me that using git means using a lot of disk space (since you get a local repo with full history), we need to live with that or not use git at all.
Personally I don't find that "a lot". An unarchived XWiki instance takes 170M. 270M for having the 6-year history of over 35000 commits at our fingertips is pretty neat.
Another thing is that forking doesn't consume users' space. Only the changes brought on top of the fork will be counted in their quota.
So, unless someone has a very strong opinion against the current size of the repo, I'd like to keep it as it is.
I started the thread so I chime in just to say that my remark was just... a remark :) So no strong opinion on my side. -Fabio
Thanks -Vincent
Denis
And most of it comes from the very early history when we had all the libs in the svn.
So, we could decide to drop the history before the introduction of maven, or we could move the core in its own repository and push for a faster migration to components.
Or we can just learn to live with it, we have a long history and we're proud of it.
-Fabio
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Mon, Apr 4, 2011 at 18:21, Vincent Massol <[email protected]> wrote:
On Apr 4, 2011, at 6:16 PM, Denis Gervalle wrote:
On Mon, Apr 4, 2011 at 17:12, Sergiu Dumitriu <[email protected]> wrote:
On 04/04/2011 03:49 PM, Fabio Mancinelli wrote:
On Mon, Apr 4, 2011 at 3:04 PM, Vincent Massol<[email protected]> wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
+1 for me
I just had a thought about the granularity... Having everything in a big repo will make people clone more than 200Mb of source code even to hack a little module (currently xwiki-trunks on github downloads 277Mb of code). But maybe this is not really an issue.
Most of it (140M) comes from xwiki-core, which is not a real module yet.
I am not sure it really worse to consume that bandwidth for such information. But how could we keep it online for reference in case we need to check it ?
I don't agree about removing any history.
It looks to me that using git means using a lot of disk space (since you get a local repo with full history), we need to live with that or not use git at all.
Well, let say that I both agree and disagree. For me, the main advantage of using Git is to have more contributors that participate, since the project is easy to fork... and merge ! Moreover, reducing the number of repos, simplify also contribution, and it goes the same direction. So, I really think we should weight the consequence of having a so heavy history, that could afraid contributors. I would really prefer to left over some very old history, if this helps receiving more contributions. Denis
Thanks -Vincent
Denis
And most of it comes from the very early history when we had all the libs in the svn.
So, we could decide to drop the history before the introduction of maven, or we could move the core in its own repository and push for a faster migration to components.
Or we can just learn to live with it, we have a long history and we're proud of it.
-Fabio
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
On Apr 4, 2011, at 9:58 PM, Denis Gervalle wrote:
On Mon, Apr 4, 2011 at 18:21, Vincent Massol <[email protected]> wrote:
On Apr 4, 2011, at 6:16 PM, Denis Gervalle wrote:
On Mon, Apr 4, 2011 at 17:12, Sergiu Dumitriu <[email protected]> wrote:
On 04/04/2011 03:49 PM, Fabio Mancinelli wrote:
On Mon, Apr 4, 2011 at 3:04 PM, Vincent Massol<[email protected]> wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
+1 for me
I just had a thought about the granularity... Having everything in a big repo will make people clone more than 200Mb of source code even to hack a little module (currently xwiki-trunks on github downloads 277Mb of code). But maybe this is not really an issue.
Most of it (140M) comes from xwiki-core, which is not a real module yet.
I am not sure it really worse to consume that bandwidth for such information. But how could we keep it online for reference in case we need to check it ?
I don't agree about removing any history.
It looks to me that using git means using a lot of disk space (since you get a local repo with full history), we need to live with that or not use git at all.
Well, let say that I both agree and disagree. For me, the main advantage of using Git is to have more contributors that participate, since the project is easy to fork... and merge ! Moreover, reducing the number of repos, simplify also contribution, and it goes the same direction. So, I really think we should weight the consequence of having a so heavy history, that could afraid contributors. I would really prefer to left over some very old history, if this helps receiving more contributions.
well we're just making this up so far since AFAIK no contributor has expressed any concern over this yet :) So let's wait for someone to raise an issue maybe? IMO contributors would definitely express issues over using Git since 99% of them are probably using svn and not git so this far down in the list of issues contributors would have IMO ;) Thanks -Vincent
Denis
Thanks -Vincent
Denis
And most of it comes from the very early history when we had all the libs in the svn.
So, we could decide to drop the history before the introduction of maven, or we could move the core in its own repository and push for a faster migration to components.
Or we can just learn to live with it, we have a long history and we're proud of it.
-Fabio
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
On Mon, 2011-04-04 at 15:04 +0200, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ...
Platform here contains only features which are bound with the platform, right? (e.g. in the current extensions I noticed the photoalbum application, for example, which is not). So I agree with this only if under platform modules are only the things bundled in the platform. Otherwise it doesn't make sense releasing everything.
|_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution.
Why? It would be great if we could put webapp resources under platform/modules as well (such as js & css), each for its feature, and make them endup in the distribution webapp. For all the other aspects, with the little knowledge that I have about the git model, I guess I agree with Fabio that 277 megs for a guy that only needs to patch a module rebuild it and drop it in his classpath is a bit too much, so we might want independent repos (but I am not sure). Overall 0. Thanks, Anca
wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Apr 4, 2011, at 4:53 PM, Luca Anca wrote:
On Mon, 2011-04-04 at 15:04 +0200, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ...
Platform here contains only features which are bound with the platform, right? (e.g. in the current extensions I noticed the photoalbum application, for example, which is not).
Nope :)
So I agree with this only if under platform modules are only the things bundled in the platform. Otherwise it doesn't make sense releasing everything.
Platform means any module that can be used to build a runtime product (XE, XEM, watch, etc). A runtime product doesn't have to use all modules from the platform. Said differently platform contains all the bit and pieces that can be reused to build a full-fedged runtime application. Note that this is the current definition and this proposal keeps that definition.
|_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution.
Why?
It would be great if we could put webapp resources under platform/modules as well (such as js & css), each for its feature, and make them endup in the distribution webapp.
Yes definitely. I was talking about the distribution part (the creation of the WAR). I agree that the templates and web resources in general should be under platform/modules too.
For all the other aspects, with the little knowledge that I have about the git model, I guess I agree with Fabio that 277 megs for a guy that only needs to patch a module rebuild it and drop it in his classpath is a bit too much, so we might want independent repos (but I am not sure).
Well if git is "bad" then we shouldn't used it but I'd hate to choose to make our life really hard just because git has a model that is disk-space-hungry. If we don't want to waste disk space we shouldn't use git at all! Imagine: we're 15 committers and we'll have 15 times the whole history. That's disk space waste and is the downside of other nice features of git. Personally I think we're beyond disk space nowadays in 2011 and I don't see it as a problem (note that just using XWiki requires 164MB). Thanks -Vincent
Overall 0.
Thanks, Anca
wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
On Mon, 2011-04-04 at 18:34 +0200, Vincent Massol wrote:
On Apr 4, 2011, at 4:53 PM, Luca Anca wrote:
On Mon, 2011-04-04 at 15:04 +0200, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ...
Platform here contains only features which are bound with the platform, right? (e.g. in the current extensions I noticed the photoalbum application, for example, which is not).
Nope :)
So I agree with this only if under platform modules are only the things bundled in the platform. Otherwise it doesn't make sense releasing everything.
Platform means any module that can be used to build a runtime product (XE, XEM, watch, etc). A runtime product doesn't have to use all modules from the platform.
Said differently platform contains all the bit and pieces that can be reused to build a full-fedged runtime application.
Note that this is the current definition and this proposal keeps that definition.
So we release everything everytime? even things that haven't changed a bit and that noone uses? I'm not sure this is clearer than having independent versioning of things. Also, this creates a bit of work, because hopefully we'd want to be able to say that 3.6 of the photoalbum works on 3.6 of platform, for example. Otherwise it doesn't make sense to release it.
|_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution.
Why?
It would be great if we could put webapp resources under platform/modules as well (such as js & css), each for its feature, and make them endup in the distribution webapp.
Yes definitely. I was talking about the distribution part (the creation of the WAR). I agree that the templates and web resources in general should be under platform/modules too.
For all the other aspects, with the little knowledge that I have about the git model, I guess I agree with Fabio that 277 megs for a guy that only needs to patch a module rebuild it and drop it in his classpath is a bit too much, so we might want independent repos (but I am not sure).
Well if git is "bad" then we shouldn't used it but I'd hate to choose to make our life really hard just because git has a model that is disk-space-hungry. If we don't want to waste disk space we shouldn't use git at all! Imagine: we're 15 committers and we'll have 15 times the whole history. That's disk space waste and is the downside of other nice features of git.
Personally I think we're beyond disk space nowadays in 2011 and I don't see it as a problem (note that just using XWiki requires 164MB).
It's not disk space, it's bandwidth. And even if that is no longer such a big concern nowadays, it still takes some time. And time is money. Thanks, Anca
Thanks -Vincent
Overall 0.
Thanks, Anca
wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi Anca, On Apr 5, 2011, at 7:24 PM, Luca Anca wrote:
On Mon, 2011-04-04 at 18:34 +0200, Vincent Massol wrote:
On Apr 4, 2011, at 4:53 PM, Luca Anca wrote:
On Mon, 2011-04-04 at 15:04 +0200, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ...
Platform here contains only features which are bound with the platform, right? (e.g. in the current extensions I noticed the photoalbum application, for example, which is not).
Nope :)
So I agree with this only if under platform modules are only the things bundled in the platform. Otherwise it doesn't make sense releasing everything.
Platform means any module that can be used to build a runtime product (XE, XEM, watch, etc). A runtime product doesn't have to use all modules from the platform.
Said differently platform contains all the bit and pieces that can be reused to build a full-fedged runtime application.
Note that this is the current definition and this proposal keeps that definition.
So we release everything everytime? even things that haven't changed a bit and that noone uses?
Yes. We're already doing this a lot, we're just expanding the scope and at the same time certifying that everything released works together.
I'm not sure this is clearer than having independent versioning of things.
It's clearer because when you use XWiki Enterprise 3.0 you have no clue what version of the Administration app you're using and if you find an issue you have no clue what version to use in jira for the affects field. However the main reason for this proposal is to ease release management.
Also, this creates a bit of work, because hopefully we'd want to be able to say that 3.6 of the photoalbum works on 3.6 of platform, for example. Otherwise it doesn't make sense to release it.
Yes that's the point too: be better at certifying what works on what. We're reducing the # of combinations but improving the quality of the few versions we release. I'd suggest you propose yourself as release manager for 3.1 to understand what it means to release XE! :) Thanks -Vincent PS: I'm not sure we're going in the right direction. It's possible that in the future we change track and separate everything again. What I'm sure of though is that this new organization will greatly simplify release management and user issue reporting.
|_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution.
Why?
It would be great if we could put webapp resources under platform/modules as well (such as js & css), each for its feature, and make them endup in the distribution webapp.
Yes definitely. I was talking about the distribution part (the creation of the WAR). I agree that the templates and web resources in general should be under platform/modules too.
For all the other aspects, with the little knowledge that I have about the git model, I guess I agree with Fabio that 277 megs for a guy that only needs to patch a module rebuild it and drop it in his classpath is a bit too much, so we might want independent repos (but I am not sure).
Well if git is "bad" then we shouldn't used it but I'd hate to choose to make our life really hard just because git has a model that is disk-space-hungry. If we don't want to waste disk space we shouldn't use git at all! Imagine: we're 15 committers and we'll have 15 times the whole history. That's disk space waste and is the downside of other nice features of git.
Personally I think we're beyond disk space nowadays in 2011 and I don't see it as a problem (note that just using XWiki requires 164MB).
It's not disk space, it's bandwidth. And even if that is no longer such a big concern nowadays, it still takes some time. And time is money.
Thanks, Anca
Thanks -Vincent
Overall 0.
Thanks, Anca
wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
On 04/04/2011 04:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc)
* Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
If we consider the GWT API a feature then we could have: |_ xwiki-platform-gwt |_ xwiki-platform-gwt-api |_ xwiki-platform-gwt-dom |_ xwiki-platform-gwt-user |_ xwiki-platform-wysiwyg |_ xwiki-platform-wysiwyg-client |_ xwiki-platform-wysiwyg-plugin-api |_ xwiki-platform-wysiwyg-server |_ xwiki-platform-wysiwyg-war But since: * the current platform/web/gwt module is not used any more in the standard XE distribution, and, as a consequence, it isn't maintained * xwiki-gwt-dom and xwiki-gwt-user modules are used only by the WYSIWYG editor * GWT is not popular among web devs, i.e. I doubt we'll use GWT for something else other than the WYSIWYG editor keeping the gwt-dom and gwt-user modules inside the WYSIWYG editor (feature) module also makes sense.
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
+0 Thanks, Marius
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 04/04/2011 03:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
I agree that it would be much simpler for users/contributors, so +1. It seems to me that we were going in the opposite direction, moving towards more decentralized components.
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
OK, but why is it xwiki-platform-skin-colibri and not "xwiki-platform-colibri"? Also, why is every directory prefixed with its parent directory name? Why not: platform/ |- modules/ |- search | |- application | |- lucene |- colibri If this is just to have the same name as the projectId inside the poms, then it only makes sense from the developer point of view, users don't care about what's inside POMs.
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc)
+1.
* Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git
I can take care of that.
* Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
I'd rather keep it, at least for the moment.
Here's my +1 (meaning I'll help perform this move)
-- Sergiu Dumitriu http://purl.org/net/sergiu/
On Apr 4, 2011, at 7:29 PM, Sergiu Dumitriu wrote:
On 04/04/2011 03:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
I agree that it would be much simpler for users/contributors, so +1.
It seems to me that we were going in the opposite direction, moving towards more decentralized components.
Yes we were but I think we're starting to realize it's complex to do so we should only do when it's really necessary. We're lacking tooling to make it practical: * release tools * issue tools * ci tools (we'd need to have a test grid to validate all versions, see which one work together) That said, it's also possible that at some point in the future we'll want to move back to splitting platform into several parts...
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
OK, but why is it xwiki-platform-skin-colibri and not "xwiki-platform-colibri"?
Also, why is every directory prefixed with its parent directory name? Why not:
platform/ |- modules/ |- search | |- application | |- lucene |- colibri
If this is just to have the same name as the projectId inside the poms, then it only makes sense from the developer point of view, users don't care about what's inside POMs.
Yes the idea is to use the artifact id as the directory name. I thought we had discussed this already and agreed but I may be wrong. I've starte a new discussion thread for this.
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc)
+1.
* Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git
I can take care of that.
* Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
I'd rather keep it, at least for the moment.
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
Results so far: +1: Vincent, Thomas, Caleb, Denis, Fabio 0: Anca no -1 So let's start implementing it today since we need to move to a stable git organization ASAP to be able to continue coding. Let's sync over irc. Thanks -Vincent On Apr 4, 2011, at 3:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
On Apr 4, 2011, at 3:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
To be more specific (thanks to Anca's question), I'm proposing: platform/modules/ |_ xwiki-platform-templates/ |_ xwiki-platform-resources/ |_ xwiki-platform-distribution/ <-- generate the WAR The reason for having xwiki-platform-distribution inside modules is because it should be released together with all modules. If we don't do this we need an additional directory level, for example: platform/ |_ core |_ modules |_ distribution |_ tools which is not very nice at all. The other option is to move out tools but there's no better place than platform since it's related to plartform. WDYT? Thanks -Vincent
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
On Tue, Apr 5, 2011 at 12:51, Vincent Massol <[email protected]> wrote:
On Apr 4, 2011, at 3:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
To be more specific (thanks to Anca's question), I'm proposing:
platform/modules/ |_ xwiki-platform-templates/ |_ xwiki-platform-resources/ |_ xwiki-platform-distribution/ <-- generate the WAR
The reason for having xwiki-platform-distribution inside modules is because it should be released together with all modules. If we don't do this we need an additional directory level, for example:
I don't understand this argument actually, I tough the whole repository was released at once, tools included since in git branches and tags are at the whole repository level. If tools don't have the same version then they should have their own repository each.
platform/ |_ core |_ modules |_ distribution |_ tools
which is not very nice at all.
The other option is to move out tools but there's no better place than platform since it's related to plartform.
WDYT?
Thanks -Vincent
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Apr 5, 2011, at 1:52 PM, Thomas Mortagne wrote:
On Tue, Apr 5, 2011 at 12:51, Vincent Massol <[email protected]> wrote:
On Apr 4, 2011, at 3:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
To be more specific (thanks to Anca's question), I'm proposing:
platform/modules/ |_ xwiki-platform-templates/ |_ xwiki-platform-resources/ |_ xwiki-platform-distribution/ <-- generate the WAR
The reason for having xwiki-platform-distribution inside modules is because it should be released together with all modules. If we don't do this we need an additional directory level, for example:
I don't understand this argument actually, I tough the whole repository was released at once, tools included since in git branches and tags are at the whole repository level. If tools don't have the same version then they should have their own repository each.
Yes my bad you're right. Tools have their own git repo and so does xwiki-platform-modules. Now the question is whether we want a special repo for distribution or should we put inside xwiki-platform-modules and thus consider it as a module. WDYT? I'm open to both although having a repo for 1 file sounds maybe a bit too much... ;) Thanks -Vincent
platform/ |_ core |_ modules |_ distribution |_ tools
which is not very nice at all.
The other option is to move out tools but there's no better place than platform since it's related to plartform.
WDYT?
Thanks -Vincent
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
On Tue, Apr 5, 2011 at 14:02, Vincent Massol <[email protected]> wrote:
On Apr 5, 2011, at 1:52 PM, Thomas Mortagne wrote:
On Tue, Apr 5, 2011 at 12:51, Vincent Massol <[email protected]> wrote:
On Apr 4, 2011, at 3:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
To be more specific (thanks to Anca's question), I'm proposing:
platform/modules/ |_ xwiki-platform-templates/ |_ xwiki-platform-resources/ |_ xwiki-platform-distribution/ <-- generate the WAR
The reason for having xwiki-platform-distribution inside modules is because it should be released together with all modules. If we don't do this we need an additional directory level, for example:
I don't understand this argument actually, I tough the whole repository was released at once, tools included since in git branches and tags are at the whole repository level. If tools don't have the same version then they should have their own repository each.
Yes my bad you're right.
Tools have their own git repo and so does xwiki-platform-modules.
Now the question is whether we want a special repo for distribution or should we put inside xwiki-platform-modules and thus consider it as a module.
WDYT?
1 for same repo
I'm open to both although having a repo for 1 file sounds maybe a bit too much... ;)
Thanks -Vincent
platform/ |_ core |_ modules |_ distribution |_ tools
which is not very nice at all.
The other option is to move out tools but there's no better place than platform since it's related to plartform.
WDYT?
Thanks -Vincent
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Tue, Apr 5, 2011 at 14:07, Thomas Mortagne <[email protected]> wrote:
On Tue, Apr 5, 2011 at 14:02, Vincent Massol <[email protected]> wrote:
On Apr 5, 2011, at 1:52 PM, Thomas Mortagne wrote:
On Tue, Apr 5, 2011 at 12:51, Vincent Massol <[email protected]> wrote:
On Apr 4, 2011, at 3:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
To be more specific (thanks to Anca's question), I'm proposing:
platform/modules/ |_ xwiki-platform-templates/ |_ xwiki-platform-resources/ |_ xwiki-platform-distribution/ <-- generate the WAR
The reason for having xwiki-platform-distribution inside modules is because it should be released together with all modules. If we don't do this we need an additional directory level, for example:
I don't understand this argument actually, I tough the whole repository was released at once, tools included since in git branches and tags are at the whole repository level. If tools don't have the same version then they should have their own repository each.
Yes my bad you're right.
Tools have their own git repo and so does xwiki-platform-modules.
Now the question is whether we want a special repo for distribution or should we put inside xwiki-platform-modules and thus consider it as a module.
WDYT?
1 for same repo
s/1/+1/
I'm open to both although having a repo for 1 file sounds maybe a bit too much... ;)
Thanks -Vincent
platform/ |_ core |_ modules |_ distribution |_ tools
which is not very nice at all.
The other option is to move out tools but there's no better place than platform since it's related to plartform.
WDYT?
Thanks -Vincent
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne
I have also started a proposal for refactoring the JIRA components for the Platform JIRA project: http://dev.xwiki.org/xwiki/bin/view/Drafts/JIRA+Reorganization+for+Platform Comments? Thanks -Vincent On Apr 4, 2011, at 3:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
On 04/05/2011 02:09 PM, Vincent Massol wrote:
I have also started a proposal for refactoring the JIRA components for the Platform JIRA project: http://dev.xwiki.org/xwiki/bin/view/Drafts/JIRA+Reorganization+for+Platform
Comments?
The current "Office Importer" component targets also the Office Viewer and Office Macro modules so I think it should have a more generic name. "Office Integration" ? Also, in https://github.com/xwiki/xwiki-platform-core currently I see xwiki-platform-office/ xwiki-platform-officeimporter/ We either have an xwiki-platform-office module like we did in SVN, that holds the importer, the viewer and the macro, or we have these three as top level modules in xwiki-platform-core. But not both. Thanks, Marius
Thanks -Vincent
On Apr 4, 2011, at 3:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Wed, Apr 6, 2011 at 09:32, Marius Dumitru Florea <[email protected]> wrote:
On 04/05/2011 02:09 PM, Vincent Massol wrote:
I have also started a proposal for refactoring the JIRA components for the Platform JIRA project: http://dev.xwiki.org/xwiki/bin/view/Drafts/JIRA+Reorganization+for+Platform
Comments?
The current "Office Importer" component targets also the Office Viewer and Office Macro modules so I think it should have a more generic name. "Office Integration" ?
Also, in https://github.com/xwiki/xwiki-platform-core currently I see
xwiki-platform-office/ xwiki-platform-officeimporter/
We either have an xwiki-platform-office module like we did in SVN, that holds the importer, the viewer and the macro, or we have these three as top level modules in xwiki-platform-core. But not both.
Yes and that's the plan AFAIK but the reorg has not really been done yet, only the svn-> right gt repo has been done.
Thanks, Marius
Thanks -Vincent
On Apr 4, 2011, at 3:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
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
Since we have used "core" for commons we should also use "core" for platform. So instead of "modules" (which is a bit too catch all anyway), I'm proposing to use xwiki-platform-core. Thanks -Vincent On Apr 4, 2011, at 3:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
participants (8)
-
Caleb James DeLisle -
Denis Gervalle -
Fabio Mancinelli -
Luca Anca -
Marius Dumitru Florea -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol