Co-maintainers requested for job-dsl-plugin

[Jamie Tanna]

Hey folks!

Last October I adopted the Job DSL Plugin. However, that was as I was leaving my previous job, where I used Jenkins heavily, to now not using it at all, which means it's hard to get closer to the real-world usage I once had. I'm also much less frequently using JVM languages, and losing a bit of my familiarity with a few things.

It'd be nice to get some more folks involved to keep this progressing in the future, and keep on top of new feature requests and bug reports.

I'm not immediately dropping all support or work on the plugin, but I thought I'd reach out to see if anyone's interested in starting getting involved, under some mentorship, until they feel comfortable being a co-maintainer, and then as things go on, I can slowly fade into the background.

[Harold Dost]

Hello,

I'm not sure if there's a place that lists all the expectations, but as a user of the Jenkins Job DSL I'd like to see it continue. Also selfishly I've found some bugs and I'd like to help fix them :) How could we get this train moving.

[Adrien Lecharpentier]

Hi,

this is the correct place. 

I'd invite you for submit a pull request on https://github.com/jenkins-infra/repository-permissions-updater so that we can grant you the release permission and someone would invite you in the plugin repository to grant you maintainer access as well.

As the plugin is marked as up for adoption, you'll get the permissions right away.

Welcome!

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/8b8bbc35-d8e5-4041-bf57-19dacb2bbbcan%40googlegroups.com.

[Basil Crow]

Just as Adrien Lecharpentier said, with the caveat that we generally
like to see a few high-quality pull requests first when granting
permissions to a high-profile plugin.