+1
Most of the stuff you`ve mentioned is not even discoverable in the default
distribution without reading the docs so it`s pointless IMO to have it by
default and we should let the admin install it when needed.
Thanks,
Eduard
On Tue, May 10, 2016 at 11:12 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
Following our strategy of moving non-core extensions of platform in
xwiki-contrib I’d like to discuss moving non-core modules of
xwiki-rendering into xwiki-contrib.
My real need ATM is to know where I should commit the Markdown renderer
I’ve been working on as a proof of concept. It’s working but not everything
is supported yet and I don’t plan nor want to commit to make it work in the
near future. I also don’t want to put the burden of maintaining it on the
xwiki core dev team. And I also feel it should be located in the same
module where the Markdown parser is located. So one solution is to move the
Markdown syntax module into xwiki-contrib, as a whole.
Now, if we do this for the markdown module we might as well agree to do it
for other non-core modules, namely:
- some syntaxes: mediawiki, twiki, apt, confluence*, creole, docbook,
doxia, jspwiki, tex (+ markdown of course)
- some macro transformations: linkchecker, wikiword
- some macros like: the ctsreport one and the jira macro
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs