Hi Thomas, Thanks a lot for stepping up! Indeed it would be great to have a maintainer for the plugin, and I'm happy to support you in this role. I have very limited bandwidth but I will do my best to help with some code reviews and onboarding if needed.
I will add you to GitHUb. Before releasing the plugin, let's have a chat in the email. To get release permissions, yu will need to submit a pull request to https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-role-strategy.yml Best regards Oleg Nenashev On Monday, November 29, 2021 at 8:17:18 PM UTC+1 Thomas Nemer wrote: > Hello Mark, > > Thanks for this nice documentation. > I'll read it entirely soon (and have a look at the videos too), but at > first glance, it seems I'm already familiar with all the tools and practice > described. > > I already have made this > <https://github.com/jenkinsci/role-strategy-plugin/pull/154> pull > request, which motivated the idea of becoming a maintainer for the plugin. > > Thomas Nemer > On 29/11/2021 17:52, Mark Waite wrote: > > > > On Monday, November 29, 2021 at 9:42:35 AM UTC-7 Thomas Nemer wrote: > >> Hello Jenkins Developers, >> >> It seems the role-strategy-plugin could need some help for maintenance, >> and I'm willing to offer my help on that subject. >> Oleg Nenashev proposed to discuss that here. >> >> I am globally not familiar with this process, but as I understand, there >> is a permission manager tool that needs to be updated so that it is >> possible to push on the binary repository and permissions needed on the >> git repo, but that's about all I know ^^ >> >> As I said to Oleg, I'm far from being an experienced plugin developer, >> I've only created a couple of PRs on nested-view plugin and I have one >> PR waiting on role-strategy-plugin which will probably need some rework >> before being acceptable, but I'm using the plugin on a daily basis, and >> would be happy to help making it properly maintained. >> >> > Thanks very much for your willingness to contribute to the plugin and to > become a maintainer. > > If one of the maintainers of the plugin is willing to approve you as a > maintainer, you can be made a maintainer immediately. If they're not ready > to do that yet, you can start contributing to the plugin through a series > of pull requests. The "Contributing to Open Source" workshop > <https://docs.google.com/document/d/1PKYIpPlRVGsBqrz0Ob1Cv3cefOZ5j2xtGZdWs27kLuw/edit#heading=h.hvd0nm6pz5o4> > > from DevOps World 2021 suggests a series of small steps that help the > plugin and help a new contributor become familiar with the plugin. That > document includes links to a five part video series > <https://docs.google.com/document/d/1PKYIpPlRVGsBqrz0Ob1Cv3cefOZ5j2xtGZdWs27kLuw/edit#heading=h.oz0bxvhyvna5> > > that illustrates many of the steps. > > Mark Waite > > >> >> Thomas Nemer >> >> -- > 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/dfb11be7-e55e-4b25-9af2-e5c702ccfe40n%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/dfb11be7-e55e-4b25-9af2-e5c702ccfe40n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- 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/6a547253-2750-4642-a34f-fa3558d76fb2n%40googlegroups.com.
