Hi, I'm the OWASP ZAP Project Lead. We (the ZAP core team) really want to maintain and onwardly develop the official Jenkins ZAP plugin. jordangs (above) has been leading on this and we're very close to releasing it. What do we need to do in order to make this happen? We're open for taking over an existing plugin or starting a new one (eg zap-plugin).
Many thanks, Simon Bennetts On Tuesday, 15 November 2016 16:26:54 UTC, [email protected] wrote: > > My IRC chat is broken, it can send but not receive messages. I apologize > for the double post. > > I was given admin access of zaproxy-plugin however it was decided that a > new repo should be created since it is not a compatible update, called > *zap-plugin*. > > I currently have write access and would like admin/ownership of the > repository. > > Reason's as follows > > 1. manage the team (to allow other devs have write access) > 2. Manage the features (Wiki's,restrictions, issues) > 3. Types of merges > 4. Manage web hooks > > Is there any reason or policy to give me write access but not > admin/ownership? > -- 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/6b6b99a2-db56-4056-8da5-f244cfa2bf6f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
