Re: [xwiki-devs] [VOTE] New Strategy for the XWiki Github Organization

On 23 Jun 2016, at 09:11, Vincent Massol <vincent(a)massol.net> wrote: Indeed going in circles a bit here but it’s an important decision… However we need to conclude quickly since we need to implement the solution for 8.2RC1 i.e. we need to close this thread at latest this week. Point 1: Scope of xwiki github org ========================== The strategy we’re voting here is about having XWiki Core Dev Team (aka XWiki Github Org) to be focusing about core stuff and reducing the scope of the core as we progress. And letting the community at large handle the non-core modules. What you mention above (and which was already proposed in the previous thread BTW) would lead to keep the same scope for the XWiki Core Dev Team. As you mention it also leads to making it more complex for others to contribute. Also don’t forget that we’ve already voted to move stuff ouf of xwiki github org and we’ve already started (markdown syntax, various platform modules already moved out), and have even already voted to move more stuff out. So the direction is to slim down the xwiki github repo, not just because we also want users to be able to install extensions in older versions of XWiki. Point 2: dependency hell =================== I would prefer that we keep releasing all XWiki Github Org together as much as possible to avoid dep hell (and increased testing efforts) as we had before. It’s fine to decide to include a few third party modules but that’s very different from deciding that the rule is now that all modules can have their own release cycle inside core. If the way to do this and be consistent is to say that the default flavor is released with the same versioning cycle than all the rest of the XWiki Github Org then I’d prefer that. Other thoughts ============ Now we could decide to move just CKEditor inside xwiki github org with the argument of controlling the quality. I think it would be more difficult to justify moving the Tour app. Also note that we should prevent ourselves from being able to bundle other third party extensions in the future in the default flavor if we think they should be in by default so I think we should still keep the strategy proposed in this thread.

I view the proposal in this mail as an add-on and not a replacement, i.e. to be clear: * Keep the same logic as proposed for xwiki github org * Still have a base and default flavor in xwiki github org * Still be allowed to bundle third party extensions in the default flavor * NEW: Allow ourselves to have special extensions in xwiki github org that have their own release cycles, and CK would be the first Right now I’m not fully convinced that we need to do this and I’d rather continue with the proposal as is and keep CK outside. The only reason to move it to the xwiki github org IMO is for quality reasons and I’d rather wait till we see a problem before considering it. Actually this thread mentioned about defining what a “basic wiki” is. I think we should consider moving CK in only if we consider that a WYSIWYG editor is part of a “basic wiki”. But I’m not convinced that a basic wiki requires 2 editors (the wiki one + a WYSIWYG one). WDYT? Thanks -Vincent > Thanks, > Eduard > > So, having that in mind, I would think of some questions: > - > >> >> Thanks >> -Vincent >> >>> Currently the users cannot upgrade the Blog because the new version of >>> the Blog depends on a new version of the XWiki WAR. With this new >> strategy >>> the users will be able to upgrade the Blog (considering that the Blog is >>> not part of the Base Flavor). >>> >>> On the same topic, we have the Extension Updater administration section >>> where users can check for extension updates. The problem is that the >>> extensions included in a flavor are considered dependencies of the flavor >>> and thus are installed as dependencies which means the Extension Updater >>> cannot separate them from other technical dependencies and thus won't >> check >>> for their updates. Ideally a flavor should be a pack of extensions that >> are >>> installed explicitly (not as dependencies). This way the Extension >> Updater >>> can propose updates and at the same time the users can uninstall >> extensions >>> from a flavor without removing the flavor. >>> >>> Thanks, >>> Marius >>> >>> >>>> * The consequence is that the XWiki Dev Team would need to be a bit more >>>> careful to monitor the quality of bundled third-party extensions in >> contrib >>>> (check commits, do some smoke testing, etc). Note that the goal of the >>>> Default flavor would not be to offer verticals (for this there should be >>>> some contrib flavors) and thus it wouldn’t bundle a lot of third-party >>>> extensions. Basically we’ll need to validate the version of those >>>> third-party extensions that include in the flavor. >>>> >>>> My POV is that globally this would offer more flexibility for our users >>>> (they’ll be able to install extensions such as CK and Tour in older >> XWiki >>>> versions and they’ll get more frequent releases) at the cost of some >>>> overhead to develop extensions that work in several versions. The dev >> team >>>> is pretty small and thus it means developing a bit less fast but it’s >>>> probably as important, if not more important, to make the code we >> develop >>>> available in older xwiki versions, as XWiki gains traction. >>>> >>>> Here’s my +1 >>>> >>>> Please cast your vote. >>>> >>>> Thanks >>>> -Vincent