On 04/04/2011 03:49 PM, Fabio Mancinelli wrote: wrote: following idea: extensions/modules in the top level platform repository (the platform version) 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. 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 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) 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?) (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. in there (maybe just user extensions and move platform features in platform.xwiki.org). -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

On Apr 4, 2011, at 6:16 PM, Denis Gervalle wrote: 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

On 04/04/2011 06:21 PM, Vincent Massol wrote: 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.

-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

On Mon, Apr 4, 2011 at 18:21, Vincent Massol <vincent(a)massol.net> wrote: On Apr 4, 2011, at 6:16 PM, Denis Gervalle wrote: 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

On Mon, 2011-04-04 at 15:04 +0200, Vincent Massol wrote: 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.

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

On Mon, 2011-04-04 at 18:34 +0200, Vincent Massol wrote: 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.

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 Apr 4, 2011, at 3:04 PM, Vincent Massol wrote: 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 _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

On Apr 5, 2011, at 1:52 PM, Thomas Mortagne wrote: 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 _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

On 04/05/2011 02:09 PM, Vincent Massol wrote: 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 _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs