Repo Owner Permission

[[Gmail] Goran Developer]

Hi,

This project is no longer being maintained by the original owners. Could i please take over the project? I have some pending changes but there is no one maintaining it or accepting pull requests. I would like to commit and make future modifications to the project.

Repo: https://github.com/jenkinsci/zaproxy-plugin

ID: JordanGS

Thank you for your time and consideration.

Cheers, Goran.

[Oleg Nenashev]

Hi Goran,

Have you tried contacting the original maintainers?
Added them to CC.

BR, Oleg

четверг, 1 сентября 2016 г., 18:13:06 UTC+2 пользователь [Gmail] Goran Developer написал:

[develop...@gmail.com]

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.

[develop...@gmail.com]

Correction. IRC*

[Daniel Beck]

> On 13.11.2016, at 23:44, develop...@gmail.com 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.

[Johann Ollivier Lapeyre]

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

[Daniel Beck]

> On 14.11.2016, at 08:06, Johann Ollivier Lapeyre <johann.olli...@gmail.com> wrote:
>
> i'm really thinking we should have only one zaproxy-plugin and one community to take care of it.

Goran has implemented a major, incompatible refactoring (as in, all existing plugin data in users' Jenkins instances cannot be loaded anymore). I suggested that rather than create an incompatible version 2.0 which comes with configuration data loss, it should be a new plugin, allowing users to migrate incrementally, and optionally declare the existing plugin deprecated and stop distributing it (or perhaps add a message to it, telling users to install the other plugin and migrate their jobs).

[Oleg Nenashev]

If there is a complete incompatibility between plugins like Daniel says, +1 for starting a new plugin instead. We already have such examples (e.g. Perforce and P4 Plugins), and such approach seems to be the most convenient one.

2016-11-14 11:34 GMT+01:00 Daniel Beck <m...@beckweb.net>:

> On 14.11.2016, at 08:06, Johann Ollivier Lapeyre <johann.ollivierlapeyre@gmail.com> wrote:
>
> i'm really thinking we should have only one zaproxy-plugin and one community to take care of it.

Goran has implemented a major, incompatible refactoring (as in, all existing plugin data in users' Jenkins instances cannot be loaded anymore). I suggested that rather than create an incompatible version 2.0 which comes with configuration data loss, it should be a new plugin, allowing users to migrate incrementally, and optionally declare the existing plugin deprecated and stop distributing it (or perhaps add a message to it, telling users to install the other plugin and migrate their jobs).

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/OhxA-bhbAW0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3A3F97F0-0DDF-483C-9E7B-8283B5B84DEE%40beckweb.net.

For more options, visit https://groups.google.com/d/optout.

[develop...@gmail.com]

The new GitHub plugin repo was made (https://github.com/jenkinsci/zap-plugin) and i have lost admin access to it, i am no longer the owner either.

Similarily a randon name has appeared in the team for zap-plugin developers, can we remove them? (https://github.com/orgs/jenkinsci/teams/zap-plugin-developers) and can i get ownership permissions back again please and thank you. :)