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 _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
