Re: [xwiki-dev] [Proposal] New SVN directory structure to accommodate the different applications we have

Hi Vincent, Sounds good to update the SVN structure for addressing the growing complexity :-) Here are below some questions and suggestions. Vincent Massol wrote: If they are used both by the platform and the applications, shouldn't we put the "tools" folder at the root level (/svnroot/xwiki/tools/)? Regarding the xarlets: why should they be considered as part of the platform? They build upon the platform, but they are rather extensions of the platform than part of it, aren't they? I have also this question: should we really distinguish in the structure between the concepts of plugins, xarlets and xwiki-applications? They have a different nature indeed, but won't splitting them into different folders make the life of developers more complex? If I write a BlogTrackBackPlugin that does some specific stuff with blogs, where will I put it in the repository? It should probably go to the "blog xarlet", which then contains xwiki-documents + Java classes. Isn't it likely that our xarlets, or at least some of them will evolve to full-fledged "applications" that will use all the XWiki concepts? Along the same lines, won't we have plugins that will have their xwiki-documents? If this happens, we can of course let the xarlet become an application and move it in the repository, but we may then consider putting plugins and xarlets in the xwiki-application folder, and distinguish between the following concepts not at the repository structure level but only at the deployment API and configuration levels: 1) application that contains only documents ("xarlet"): can be installed on any xwiki instance 2) application that contains plugins and possibly other Java classes, and possibly some xwiki documents (could be dubbed "xwiki application", "xwiki plugin" or "xwiki extension"?): can be installed on any xwiki instance, but it requires a restart of the application server 3) application that contains Java classes, xwiki documents and other contents: need specific deployment. -> "xwiki product"?. What do you think? Regarding the extensions you mention: I don't understand why we wouldn't consider xwiki-eclipse as part of the platform: how is it different from the /xwiki-platform/web/gwt? Here 's a modified tree to summarize my suggestions: xwiki-platform ============== /svnroot/xwiki/xwiki-platform/ |_ core for now |_ xwiki-model, xwiki-storage etc. in the future |_ webapp |_ gwt |_ standard |_ xwiki-platform-ui (the components below may be moved to the component level in the future, i.e. would be at the same level as xwiki-model etc.) |_ eclipse-ui |_ flex-ui |_ xul-ui |_ web-ui-standard |_ templates |_ skins |_ gwt |_ plugins: only the platform core plugins: image, packaging, fileupload, zipexplorer, but not: flickr, graphviz, ... xwiki-applications ================== /svnroot/xwiki/xwiki-applications/ |_ xwiki-blog |_ wiki |_ xwiki-calendar |_ plugins/ |_ com.xpn.xwiki.plugins.CalendarPlugin |_ wiki/ |_ xwiki-enterprise-manager |_ wiki |_ web |_ distribution |_ xwiki-watch |_ xwiki-concerto my .2 Xcents Stéphane -- Stéphane Laurière slauriere(a)xwiki.com XWiki Research http://www.xwiki.com http://concerto.xwiki.com http://nepomuk.semanticdesktop.org