Hi Ludovic/everyone, Good start. However we've already started designing the Extension Manager here: http://dev.xwiki.org/xwiki/bin/view/Design/ExtensionManager Thus this proposal should be modified to take that into account. IMO your proposal is slightly less advanced in term of our final goal than the Extension Manager one. That said there are common notions so it could be a problem to start implementing them in a not compatible manner. I also think that we could have a quick redesign of code.xwiki.org with better presentation and better XClasses/XObjects but without modifying a single line of code from XE. That would be easy to do and bring some improvements (not all obviously).

I'm worried that if someone start implementing your idea right now and quickly we're going to spend time on something that will be dumped when we start working on the Extension Manager. IMO it should be done and taken into account when we start working on the Extension Manager. However as I mentioned ago, I think it's perfectly fine to improve code.xwiki.org right now but with smaller goals. Just a L&F improvement, navigation improvement, etc but without touching XE's code.

What do others think? Thanks -Vincent On Oct 23, 2009, at 11:19 PM, Ludovic Dubost wrote: _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hello, On 10/23/09 11:19 PM, Ludovic Dubost wrote: I like "Extension" as prefix, and I'll vote for it. I've always thought the use of "extension" we are currently doing on code.xwiki.org is wrong (as in "An extension is an application or script that integrates or interacts with XWiki. In other word it's anything that doesn't fit in any other category ;)"). Extension captures well the polymorphism of what the repository will propose. And well, XWiki is all eXtensibility, isn't it? Here I like for "repository", as this is what ultimately we target for code.xwiki.org (similar to a "maven" repository for XWiki extensions, that can be used by the future extension manager http://dev.xwiki.org/xwiki/bin/view/Design/ExtensionManager). "Store" is maybe a more trendy name those days, but right now code.xwiki.org does not sell anything, so that would be wrong. So that would be Extension Repository for me. Concerning the data model and UI, I share most of what has been proposed. Some random remarks : - I like the experimental/beta/stable flag. - XRCode.DownloadClass should be XRCode.VersionClass IMO - "extension: page of the extension it is part of" for me this is not necessary, I would store both the XRCode.ExtensionClass object and all version objects in one document. - I don't think we need "minversion/maxversion" for the ExtensionClass, if we have this information in all Version objects we can draw the compatibility table. But that means trusting publishers will actually fill in that info for all versions and keep it up to date. - I don't like the livetable right at the top of the main page. My idea of the main page is something in the flavor of https://addons.mozilla.org, with a sexy intro that shows what are extensions, and then lists of "featured" and "popular" extensions for example. The full live table would come after that IMHO. Note that now that I look at addons.mozilla.org I think the idea of collections is interesting for us too, especially for the time we don't have an extension manager that can fix the dependencies issues. But that's another discussion :) Jerome. _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Any other opinion about the name: "Extension Repository" has 1 vote

? Jerome Velociter a écrit :

Any other opinion about the name: "Extension Repository" has 1 vote

? Jerome Velociter a écrit : -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs