Hi Julien, I agree if there are significant version restrictions it should be released as a different connector than the one that is already there.
Can you create an svn branch and start setting this up in it? There should also be a ticket created that you can use to name your branch. It's important to make sure there are no name collisions with the existing connector, of course. Thanks! Karl On Thu, Mar 5, 2020 at 12:59 PM <julien.massi...@francelabs.com> wrote: > Hi Karl, > > > > I have developed a new Confluence connector based on the existing one in > order to address 3 main issues : > > - the current connector does not correctly implements the security > > - the current connector has performance problems when handling a huge > dataset > > - the current connector generates a version string for documents that is > not > sufficient to detect all changes > > > > I would like to contribute it to the MCF community. But I am not sure what > is the best way to do it, since the core code is very different from the > original one. Furthermore it is only compatible from confluence v6 and > above. So I was thinking that we may release it as a different connector, > but I'd prefer to have your opinion on that. > > > > What do you think? > > > > Best regards, > > Julien > >
