On Fri, Feb 12, 2016 at 12:45 PM, Thomas Mortagne <[email protected]> wrote: > On Fri, Feb 12, 2016 at 12:32 PM, [email protected] <[email protected]> > wrote: >> >> >> >> >> >> On 11 Feb 2016 at 17:10:28, [email protected] >> ([email protected](mailto:[email protected])) wrote: >> >>> Hi devs, >>> >>> Now that we’ve voted on the "XWiki Core” concept and that we’ve agreed that >>> the xwiki organization on github should focused on offering core extensions >>> only (and the rest should be moved to contrib) we need to ensure that we >>> use the same terminology everywhere. >>> >>> I’d like to start updating xwiki.org(http://xwiki.org) accordingly but >>> first I want to be sure we agree on the terminology: >>> >>> * The "XWiki Runtime”: the XWiki WAR that you get from the various >>> distributions that you can find on xwiki.org(http://xwiki.org). It’s a >>> minimalistic runtime on top of which you can install Extensions. >>> Documentation for it will be available at http://platform.xwiki.org. >>> >>> * “XWiki Core”: Represents the set of XWiki APIs/sources making up the >>> "XWiki Platform”. The sources are available in github in the xwiki-commons, >>> xwiki-rendering and xwiki-platform repositories. More globally can be meant >>> to represent all the sources found in the xwiki github organization. >>> >>> * “XWiki Contrib”: Extensions to the "XWiki Runtime”. Located under the >>> xwiki-contrib organization in github. >>> >>> * The "XWiki Core Development Team” or “XWiki Core Team” (previously called >>> "XWiki Development Team"): the list of committers of the “xwiki" github >>> organization. >>> >>> * “XWiki Platform”: synonymous for “XWiki Core”. Since “XWiki Platform” >>> could also represent the xwiki-platform github repository, it’s better to >>> use “XWiki Core” when wanting to name the full content of the xwiki github >>> organization. For example: “The XWiki Core Development Team works on XWiki >>> Core”… >>> >>> * “Flavor”: a set of Extensions (usually with a purpose) that can be >>> installed all together in a XWiki Runtime or when creating a subwiki inside >>> the XWiki Runtime. >>> >>> * The “Default Flavor”: the unique flavor provided by the “XWiki Core >>> Development Team”. Contrib projects and more generally anyone else can >>> contribute other flavors on >>> extensions.xwiki.org(http://extensions.xwiki.org). These flavors will >>> appear in the XWiki Platform when you first run it or when you create a new >>> subwiki. The Default Flavor is going to replace “XWiki Enterprise” (and >>> enterprise.xwiki.org(http://enterprise.xwiki.org) will be removed and >>> folded into platform.xwiki.org(http://platform.xwiki.org) - the same will >>> happen for xwiki-enterprise which will be folded into xwiki-platform in >>> github) >>> >>> * “XWiki Committers” or “XWiki Team". Vague terms that represent the full >>> set of committers of both the xwiki and xwiki-contrib github organizations. >>> >>> * “XWiki N.P”. Shortcut for the “XWiki Runtime” version N.P (e.g. “XWiki >>> 7.4.1”). >>> >>> * The “XWiki Project”. Generic term that includes the work done by XWiki >>> Contrib Committers, XWiki Core Committers and by extensions the work done >>> by the full community of contributors to both xwiki and xwiki-contrib >>> github organizations. >>> >>> >>> Do you agree with this? Any other terms that we should define? >> >> I forgot a very important one: What’s the scope of "XWiki Core”? For that we >> can update the “XWiki Core” definition: >> >> * “XWiki Core”: Represents the set of XWiki APIs/sources that end up being >> in the “Default Flavor". The sources are available in github in the >> xwiki-commons, xwiki-rendering and xwiki-platform repositories. More >> globally can be meant to represent all the sources found in the xwiki github >> organization. Generally speaking any module that isn’t bundled in the >> “Default Flavor” should be moved to XWiki Contrib. > > Not sure about this. Out of the blue it's more or less what we want > but there is use cases where a module that is not absolutely needed to > have in the default flavor is still very tied to the platform version > and should be released with it. One example is Repository App for > which all the last changes were in sync with changes in the extension > API (so more tied to commons than platform here), would be a pain to > maintain this one as a contrib module.
I guess we could say that's the rule and in rare cases we have exceptions (like ignoring a checkstyle rule). > >> >> WDYT? >> >> Thanks >> -Vincent >> >> >>> >>> Once agreed I’ll kickstart the work by updating xwiki.org(http://xwiki.org) >>> pages by creating a Terminology page and update some existing pages. >>> However it’ll be up to everyone to follow the terminology. >>> >>> Thanks >>> -Vincent >>> >> >> _______________________________________________ >> devs mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/devs > > > > -- > Thomas Mortagne -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
