Re: [xwiki-devs] [Proposal] New xwiki-extensions GitHub organization

What do you do when an extension is used in more than one flavor ? It would definitely be a good thing for the design and features of this extension, as it would have to evolve in a more "generic" way to satisfy the needs of distinct flavors. But if the original extension owner has a specific view on his roadmap, and it does not fit with the flavor roadmap, what happens ? I suppose there would be a fork at some point, and the original extension would have to move back to contrib ? That would be a pity though. Something seems difficult to me, is the difference between a contributor and a committer, it is not always in roadmap content, but more in deadlines. For ex-contributors, it could be difficult to stick to specific release dates - though they could want to keep being the RM of "their" extension. Well, of course here I'm taking the worst-case scenario... And maybe I didn't get the whole thing.

> > As for moving extensions out of xwiki-contrib to xwiki-extensions, > > it's not simple. First, it's not very clear which contrib extensions > > will be chosen. You said "some maintained apps" but the link you gave > > is more about the functionality they provide and whether they fit in > > our view of the collaborative app suite. Then in order to move an > > extension you need to ask the contributors, otherwise you'll have to > > fork the repo and create a new extension id. > > They’ll be chosen on a case by case basis with a VOTE for each. The person > proposing it will put forward a maintainer for the extensions (who will be > responsible of Roadmap/Releases Notes and performing releases). > > Note that IMO there are some conditions that we could define as base > conditions: > * Having had several releases already > * Obeying the app best practices as defined by > http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPra… > * Having some tests and for apps, having at least one functional test > (this means the functional test fwk is in place and ready to receive more > tests) > * Code style needs to obey > http://dev.xwiki.org/xwiki/bin/view/Community/CodeStyle and generally > speaking obey the practices defined on http://dev.xwiki.org > > > Then what happens if an > > extension from xwiki-extensions stops being maintained, do we move it > > back to xwiki-contrib? > > Yes, same as what happens currently in the xwiki organization. > > > I'm not fully convinced by your proposal. > > The real goal of this proposal is to start having nice applications that > can be a showcase of XWiki. Till now we have the engine and some extensions > but none of them are developed as strongly as platform and they fall short. > This is an effort to make a usable XWiki *product* vs just an XWiki > *platform*. > > Again, we should take in only extensions that we can maintain, i.e. for > which we have a volunteer to maintain them. > > TBH I don’t know if this will succeed or not but I feel it’s worth trying > :) > > Do you have some better idea? > > Thanks > -Vincent > > > Thanks, > > Marius > > > > On Mon, May 5, 2014 at 5:43 PM, vincent(a)massol.net wrote: > > > Hi devs, > > > > > > Right now we have 2 organizations related to the XWiki project on > Github: xwiki and xwiki-contribs. > > > > > > The separation is currently the following: > > > * XWiki Committers maintain the code in the “xwiki” organization > > > * non XWiki Committers (aka contributors) maintain the code in the > “xwiki-contrib” organization in the way they want (some extensions there > are not maintained, others are maintained) > > > > > > After brainstorming with Thomas Mortagne we’d like to propose the > following changes: > > > > > > Need > > > ===== > > > > > > * Be able to extract some maintained apps from xwiki-contrib to > separate them from less maintained extensions. For example the top apps > listed here: > http://design.xwiki.org/xwiki/bin/view/Proposal/CollaborativeApplications > > > * Be able to extract some extensions currently located in > xwiki-platform but not released with XE so that they can have a different > release cycle (examples: FAQ app, IRCBot extension, JIRA macro, etc). > Having different release cycle allow to release new versions quicker to our > users (bug fixes, new features). > > > > > > Proposal > > > ======= > > > > > > * Introduce a new xwiki-extensions organization in GitHub which would > be maintained by the XWiki Dev Team (aka XWiki Committers) > > > > > > * For now, move out of xwiki/xwiki-platform all modules that are not > bundled by default in XE. This rule will be reviewed and modified when we > introduce the flavors concept in the future. The idea is that > xwiki-platform will contain “core extensions” only and as we progress > towards extensions, the number of core extensions will get smaller and > smaller till possibly only the EM and what it requires. Everything else > would be located in the xwiki-extensions organization > > > > > > * Have one repository per extensions in the xwiki-extensions github > organization so that each extension can be released independently of each > other > > > > > > * In order to make it simple to release, the idea would be to have > Roadmaps and aggregated Release Notes per Flavor (this is what we’re doing > now with the “XE” flavor BTW). > > > > > > * We will be able to vote in committers for specific repos located in > the xwiki-extensions organization without having them voted for the xwiki > organization (although, over time, they would be able to become xwiki > committers for the xwiki orgnization should they wish and if they’re voted > in) > > > > > > * Extensions from xwiki-extensions published on e.x.o would have > “XWiki Development Team” as author, which means they will be officially > supported by the xwiki committers. > > > > > > > > > WDYT? > > > > > > Thanks > > > -Vincent & Thomas