10 Apr
2013
10 Apr
'13
noon
On Apr 10, 2013, at 11:50 AM, Marius Dumitru Florea <mariusdumitru.florea(a)xwiki.com>
wrote:
On Wed, Apr 10, 2013 at 12:43 PM, Vincent Massol
<vincent(a)massol.net> wrote:
Yes, it would be nice. We could either integrate this in the DW or redirect him to the EM
UI. Integration in the DW is nicer for a seamless user experience but more work.
Thanks
-Vincent
On Apr 10, 2013, at 11:20 AM, Marius Dumitru Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
Cancel DW is different. I think we need to have a separate "No flavor"
option, even if not selected by default.
On Tue, Apr 9, 2013 at 9:33 PM, Denis Gervalle
<dgl(a)softec.lu> wrote:
I wouldn't put that as the default; it's the flavor that only 0.000001% of xwiki
users would pick… ;)
Or do you mean to use that if the user "cancels" the DW? Hi Vincent,
On Tue, Apr 9, 2013 at 12:38 PM, Vincent Massol <vincent(a)massol.net> wrote:
> 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.
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.
IMO custom Flavor is the same as "don't
install any flavor" since it means going to the EM UI to manually install extensions.
Yes, but I thought maybe the user will want to install some extension
from the start. It's not that important. Thanks,
Marius
>
> Thanks
> -Vincent
>
>> Thanks,
>> Marius
>>
>>>
>>>
>>>> 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