10 Apr
2013
10 Apr
'13
11:20 a.m.
On Tue, Apr 9, 2013 at 9:33 PM, Denis Gervalle <dgl(a)softec.lu> wrote:
Hi Vincent,
On Tue, Apr 9, 2013 at 12:38 PM, Vincent Massol <vincent(a)massol.net> wrote:
Indeed, we could have two more options in the list of flavors:
* "No flavor" (selected by default maybe) which would install only the
EM UI to let the user install later what extensions he wants and
* "Custom flavor", allowing the user to select a list of extension to install.
Thanks,
Marius
Hi devs,
Caty, Thomas, Marius and myself have had a brainstorming session today
about Flavors. Here's the proposal that came out of it:
* Remove notion of XE/XEM distributions. The distribution is just "XWiki"
* XWiki becomes an empty shell (as it is already when you download the
WAR), even when you download the standalone distribution
* Generate distributions in xwiki-platform, maybe in xwiki-distributions
with installers inside and some functional tests (but most func tests will
be with flavors)
* Remove xwiki-enterprise and xwiki-manager and introduce xwiki-flavors/
in xwiki-platform
* Introduce notion of Categories for extensions (similar to the category
concepts in wiki macros)
* Flavors will be extensions categorized as "flavors" (using the
Categories system)
* In the future we'll also need a new Maven <paclaging> type to represent
a grouping of extensions with no specific content
* Display Flavors in DW first steps and ask user to choose which one they
want to specialize their wiki
* First 2 flavors we need: Workspaces and Knowledge Base (closest to the
current XE but without Blog). We need to define precisely the first version
of these 2 flavors
All this sounds good to me and a real improvement compare to the current
situation.
Regarding initial flavors, I also think we should also have a somewhat
"minimal" "untainted" flavor, with mainly EM and the administration
application. This could be your default choice if you do not want to take
any decision. Not installing anything make the wiki almost unusable except
for experts, so I really think we need this. The Knowledge Base flavor is
no more an acceptable default IMO. We also agreed that the main work to be done
before we can really have
flavors is to implement Categories for extensions.
Have you already some plan for implementing that ? How could this integrate
well with normal maven package ?
We'll need to decide when we start working on
this in our roadmap but
probably not before 5.2 anyway since 1) it'll be Marius and Thomas who
would work on this and 2) Thomas has to work on performance import/export
and Marius needs to work on AWM, probably both in 5.1 (roadmap not defined
yet).
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs