On 11 May 2016, at 19:06, Marius Dumitru Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
On Wed, May 11, 2016 at 10:47 AM, Vincent Massol <vincent(a)massol.net> wrote:
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.
Another consequence is that it will be harder to see if a change in the
rendering API breaks one of the available syntaxes. But this is acceptable.