On Fri, Apr 14, 2017 at 4:51 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com>
wrote:
Here is a new proposal on this subject.
This supersets the following threads:
*
http://markmail.org/message/mhhurc7lbyfanph7
*
http://markmail.org/message/nav5a77hzmhq4gq6
*
http://markmail.org/message/fd5ijxdquzdhtykw
We discussed with other committers (Vincent and Ludovic) and came to
the conclusion that it was not core dev team job to provide a specific
flavor like Knowledge Base and that we should focus only on a very
generic one (pretty much XE without the Blog).
Here are the details:
= One flavor
We develop only 1 flavor located in xwiki-platform repository. It's a
generic flavor not targeting any specific use case (the first version
with be XE without the Blog). We will discuss the name in another
thread later, let's call it "Wiki Flavor" for now.
Of course everyone is free and welcomed to build lots of contrib
flavors which will be proposed when you install XWiki ("Development
Flavor", "Demo Flavor", "Blog Flavor", etc.).
ok for now. Still I see this as in intermediate step until we get more
flavors. If it has no particular purpose / use case, I don't think people
will use / want it, especially when we will have the Demo or the targeted
flavors.
When we will have more flavors, I think the core dev team should take care
of the Base 'extension' and the Development Flavor.
= No "Base flavor"
But platform will provide an extension that can be used as dependency
by various flavors to get "core" UI extensions that we think make
sense in any kind of flavor.
We will need to make some special rules and treat this as API. We need
rules to add and remove dependencies and they should go through vote +
announcements since they could impact third-party flavors.
How many flavors should depend of an extension in order to consider it
going in the base? 3-5?
Can we add contrib extensions or just platform ones?
We kind of previously discussed some of the items several times in the
past, but we should document the rules.
= Demo package
We currently have a jetty/hsqldb based package in platform which let
you choose which flavor you want. We will show it in the download
page.
We will add another one with the Wiki Flavor already installed in it
(pretty much like the XE jetty/hsqldb package). Listed on the download
page too.
From a development / testing perspective I like this
packaging, since I
don't want to spend several minutes each day installing the
flavor. Still I
guess the time is kind of the same: spend on downloading or on installing.
The difference is that in DW you need to follow the steps.
We don't maintain exe/jar installers anymore in platform, they die
with XWiki Enterprise. They are a real pain to maintain and we are
actually failing since they don't really work properly everywhere they
are supposed to work. It does not worth the trouble for what is not a
production ready package and it's better anyway to make more clear
XWiki is a server thing.
ok.
Thanks,
Caty
WDYT ?
Thanks,
--
Thomas Mortagne