11 May
2016
11 May
'16
9:47 a.m.
On 10 May 2016, at 23:12, 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?
Note that one consequence could be that we should deprecate the configured syntaxes, i.e.
the xwiki.rendering.syntaxes property in xwiki.cfg. Or at least don’t define it by
default.
This property is there since all syntaxes are bundled by default and admin may not want
their users to use all available syntaxes.
What would be nice is that, if we move some syntaxes out, when an admin installs them as
extension with the EM, they become active without having to stop and restart the wiki. I
guess we could implement this with http://jira.xwiki.org/browse/XWIKI-12474 and by default
when a new syntax extension is installed, it’s active i.e. do the same as we do for the
Applications Panel.
Thanks
-Vincent
Thanks
-Vincent