Hello, I'm the original product owner of zaproxy-plugin, and this is true i've no time or opportunities with my current job to work on this, same for Ludovic. I'm hopping this could change in few months, but to avoid 2 plugins doing the same thing, which is always confusing for users, and to make easier the maintainance, i'm really thinking we should have only one zaproxy-plugin and one community to take care of it.
Is there still a thing i should do or allow for that? Johann Le 14 nov. 2016 1:14 AM, "Daniel Beck" <[email protected]> a écrit : > > > On 13.11.2016, at 23:44, [email protected] wrote: > > > > Hello, as per dicussions in RCI, i was unable to get in touch with the > original repo owners. The project was abandoned as far as i could tell and > rather than start a brand new project. I was given admin access to the > github repositrory, the wiki as we as the jira. Thank you. > > After some discussion on IRC, development will continue using a new > artifactId as this is a major, incompatible rewrite. Commits to > zaproxy-plugin will probably be reverted. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAP%3DWnj%3DkJSqAe3nBiU0MDNjUc8EXLs15hhV8apy0eBda%2BpoGWg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
