Thomas Mortagne wrote: > On Tue, Oct 6, 2009 at 15:50, Jerome Velociter <[email protected]> wrote: >> Thomas Mortagne wrote: >>> On Tue, Oct 6, 2009 at 15:22, Jerome Velociter <[email protected]> wrote: >>>> Thomas Mortagne wrote: >>>>> On Tue, Oct 6, 2009 at 14:45, Jerome Velociter <[email protected]> wrote: >>>>>> For the repository organization, I propose the following : >>>>>> >>>>>> xlet/ (http://svn.xwiki.org/svnroot/xwiki/xlet/) >>>>>> |__applications/ >>>>>> |__trunk/ >>>>>> |__xapp1/ >>>>>> |__xapp2/ >>>>>> [...] >>>>>> |__xappN/ >>>>>> |__branches/ >>>>>> [...] >>>>>> |__tags/ >>>>>> [...] >>>>>> |__extensions/ >>>>>> [...] >>>>>> |__macros/ >>>>>> [...] >>>>>> |__modules/ >>>>>> [...] >>>>>> |__plugins/ >>>>>> [...] >>>>>> |__skins/ >>>>>> [...] >>>>>> >>>>>> Each of the first level sub-directory (applications, extensions, macros, >>>>>> etc.) having the same meaning of is currently defined on code.xwiki.org >>>>>> >>>>>> WDYT ? >>>>> I'm not sure it's the right way, i think i would prefer to have the >>>>> projects directly under xlet/ and have each project decide its own >>>>> organization. It's a real pain currently to release plugin and >>>>> applications which for lot of them should be released together, we >>>>> should try to go the right way this time for a new repository. >>>> Don't you think it's good to have that distinction by type of project ? >>>> >>>> Do you think we can manage this by project names ? (for example >>>> "plugin-myplugin", "application-myapplication") It would mean making >>>> sure contributors name their projects properly (it's easier to have them >>>> create their projects in the proper directory properly IMO). >>> Don't mix projects and maven artifacts, as i said most of our >>> applications have a corresponding plugin/component with the same >>> version you would like to release all in once. >>> >>> For me it should be based on what you want to build, we will never >>> want to build all the xlet/applications/trunk/ but >>> build/release/branch/etc.. xlet/myproject/trunk/ all in once will be >>> needed. If we separate all, it will just make contributor life a pain >>> for nothing, list project is already http://code.xwiki.org. It also >>> mean we can handling committers rights by project, if we see this as a >>> start of a XWiki forge we should definitely organize by project and >>> not by maven artifacts types. >>> >>> At worst why not have theses artifact type project base folder but we >>> also need a "project" folder or something like that where you can put >>> a more important contribution which have more than just one artifact. >>> >> OK, you fear that projects composed of several modules (like >> applications + plugin + macro) will be painful to handle from maven PoV >> if they are scattered over different folders. >> >> My only concern is that we might get project names that are not very >> descriptive (one would have to go and see its sources or pom.xml to know >> what it does). But we (XWiki Dev Team) can always interfere here as it >> concerns the repository organization, not projects themselves. > > You can have exactly the same issue with type based organization, if > you know xlet/extensions/trunk/toto42 is a extension you have no idea > what it really is.
but you know it's an extension (at least in theory) :) > And as you said we are creating the project on svn > so we can decide that a name does not fit with the provided > description when someone ask for a new project in XWiki contrib > repository. > > Also i really think we should think of security, even if we don't do > it from the starts, if we organize by project it will be a lot easier > to add rights management support the same we do this with project in > svn.xwiki.org based on some ProjectClass objects rights in > forge.xwiki.org for example instead of based on a group in some wiki. > Would be a good start for a real XWiki forge and we already have > everything we need to do it. Anyway, +1 from me for this organization, you've convinced me. Jerome. > >> Jerome. >> >> _______________________________________________ >> devs mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/devs >> > > > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
