5 May
2014
5 May
'14
10:39 p.m.
+1, looks very good :)
On Mon, May 5, 2014 at 5:56 PM, Guillaume "Louis-Marie" Delhumeau <
gdelhumeau(a)xwiki.com> wrote:
+1, looks good.
2014-05-05 17:03 GMT+02:00 Thomas Mortagne <thomas.mortagne(a)xwiki.com>om>:
http://design.xwiki.org/xwiki/bin/view/Proposal/CollaborativeApplications
> > * Be able to extract some
extensions currently located in
xwiki-platform
> but not released with XE so that they can have a different release cycle
> (examples: FAQ app, IRCBot extension, JIRA macro, etc). Having different
> release cycle allow to release new versions quicker to our users (bug
> fixes, new features).
> Note that it also allows
synchronizing extensions strongly tieds to
> external services (e.g. Google analytics) or some other project (e.g.
> ruby macro and JRuby) on those strong dependencies releases instead of
> XWiki core releases.
> > > Proposal
> > =======
> > > * Introduce a new
xwiki-extensions organization in GitHub which would
be
> maintained by the XWiki Dev Team (aka XWiki Committers)
> > > * For now, move out of
xwiki/xwiki-platform all modules that are not
> bundled by default in XE. This rule will be reviewed and modified when we
> introduce the flavors concept in the future. The idea is that
> xwiki-platform will contain “core extensions” only and as we progress
> towards extensions, the number of core extensions will get smaller and
> smaller till possibly only the EM and what it requires. Everything else
> would be located in the xwiki-extensions organization
> > > * Have one repository per
extensions in the xwiki-extensions github
> organization so that each extension can be released independently of each
> other
> > > * In order to make it
simple to release, the idea would be to have
> Roadmaps and aggregated Release Notes per Flavor (this is what we’re
doing
> now with the “XE” flavor BTW).
> > > * We will be able to vote
in committers for specific repos located in
> the xwiki-extensions organization without having them voted for the xwiki
> organization (although, over time, they would be able to become xwiki
> committers for the xwiki orgnization should they wish and if they’re
voted
> in)
> > > * Extensions from
xwiki-extensions published on e.x.o would have “XWiki
> Development Team” as author, which means they will be officially
supported
> by the xwiki committers.
> > > > WDYT?
> > > Thanks
> > -Vincent & Thomas
> > >
_______________________________________________
> > devs mailing list
> > devs(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
> --
> Thomas Mortagne
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO
On Mon, May 5, 2014 at 4:43 PM,
vincent(a)massol.net <vincent(a)massol.net>
wrote:
> Need
> =====
> * Be able to extract some maintained
apps from xwiki-contrib to
separate
Hi devs,
Right now we have 2 organizations related to the XWiki project on
Github: xwiki
and xwiki-contribs.
The separation is currently the following:
* XWiki Committers maintain the code in the “xwiki” organization
* non XWiki Committers (aka contributors) maintain the code in the
“xwiki-contrib” organization in the way they want (some extensions there
are not maintained, others are maintained)
After brainstorming with Thomas Mortagne we’d like to propose the
following
changes:
them from less maintained extensions. For example
the top apps listed
here: