6 Jun
2016
6 Jun
'16
2:58 p.m.
On 06 Jun 2016, at 14:50, Marius Dumitru Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
On Mon, Jun 6, 2016 at 3:09 PM, Alexandru Cotiuga <
alexandru.cotiuga(a)xwiki.com> wrote:
I’d personally not like this for the following reasons:
1) I like that the XWiki runtime is all released at once with all extensions making it
using the same versions and verified to work together.
2) Support. The XWiki runtime is supported by the XWiki Core Dev Team. Extensions in
contrib are not supported by the XWiki Core Dev Team. In addition xwiki-contrib is very
open and anyone can make modifications there and quality is thus harder to guarantee.
We defined the xwiki github organization as containing horizontal modules, ie modules that
can be required for any flavor and both CKEditor and the Tour Application fit the need. By
opposition to vertical modules which make sense only for some use cases (like the Meeting
Manager app) and not by default in XE. We have the option of having flavors in contrib for
those if we want though. For CKEditor it’s not a good thing since we’d like it by
default.
One alternative (which I’m not fond of at all) would be to have ckeditor as a separate git
repo in the xwiki github organization.
Thanks
-Vincent
Hello all,
As it was decided already, a Homepage Tour have to be implemented. However,
no option regarding the place where the Tour Application should be added as
dependency was discussed.
There are some possible options:
1) XWiki Enterprise
2) XWiki Platform Distribution
3) XWiki Platform Helper
4) Is there any option to have the Tour Application as a part of the Core ?
What would be the best way to include the Contrib applications in XWiki?
On this topic (sorry if I hijack your thread) I was wondering why don't we
have dependencies from platform/enterprise to contrib. We have lots of
third party dependencies, contrib could be considered as such. Moreover,
we're in the process of moving non-core (vertical) extensions out of
platform to contrib. It would be a pity to move something from contrib to
platform and then back to contrib. I have the same issue with the CKEditor
Integration extension. We want CKEditor as the default editor, bundled with
the default distribution, but do we need to move it to platform? Same for
the Welcome Tour. Thanks,
Marius
>
> Thanks,
> Alex