Request to adopt plugin "bitbucket-branch-source-plugin"

[Nikolas Falco]

Hi all,

   I would adopt the Jenkins plugin "bitbucket-branch-source-plugin" as a co-maintainer. I use this plugin in all the companies I worked for and I have already contributed some PRs. Jetersen proposed me to become the maintainer of the plugin some time ago but I declined because I did not know it well (it has many server features, discontinued by atlassian, that I have no way to try).

Unfortunately the last version of this plugin that includes bug fixes was in May, after which subsequent versions only include security fixes or infrastructure changes. The number of bugs increases as well as PRs to approve. Some of those I need to update our production instance. I tried to mention some maintainers but with no luck. Maybe they are focused on other plugins with higher priority, so, I'm ask to participate to the maintenance to speed up the resolution of bugs and/or features that have been pending for a long time.

* Link to a plugin you want to adopt: https://github.com/jenkinsci/bitbucket-branch-source-plugin

* Link to pull requests you want to submit, if applicable: #851, #837

* Your GitHub username/ID: nfalco79

* Your Jenkins Infrastructure Account ID: nfalco

Best regards

Falco Nikolas

[Nikolas Falco]

Should I consider the request rejected/not approved?

[Tim Jacomb]

After 2 weeks and no response they are normally considered approved although you haven't done the second part of the adoption process:

https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/, 

heading "Submit a PR on the "Repository Permission Updater" repository"

This notifies via GitHub as well in case the maintainer isn't following the mailing list anymore.

Could you create the pull request please?

Cheers

Tim

--
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/89b614c8-0c2a-4753-a01b-b6540ebd8b60n%40googlegroups.com.

[Nikolas Falco]

Hi Tim,

  I did not prepare pull request at jenkins infra because I would as first step know if this request was acceptable or not, since the plugin was not marked as "open for adoption"

I had create the pull request now

https://github.com/jenkins-infra/repository-permissions-updater/pull/4152