The maintainer responded with a reasonable explanation and objected to your adoption request: https://github.com/jenkinsci/tap-plugin/pull/36#issuecomment-1893725271
Thanks for understanding. > On 16. Jan 2024, at 13:53, 'Alexander Brandes' via Jenkins Developers > <[email protected]> wrote: > > I have reached out to the maintainer will keep you posted with their decision. > >> On 16. Jan 2024, at 13:36, 'Alexander Brandes' via Jenkins Developers >> <[email protected]> wrote: >> >> As seen evidently in https://github.com/jenkinsci/tap-plugin/pull/35, the >> maintainer is not inactive. I have forwarded the mail to the maintainer >> allowing some time for them to decide :) >> >>> On 16. Jan 2024, at 13:17, Jiri Vanek <[email protected]> wrote: >>> >>> hello! >>> >>> It seems, that when there is unresponsive maintainer (about half year and >>> more of none, or weird replies to PRs or bugs), >>> then it should be possible to rise a PR and become comaintainer of the >>> plugin. >>> >>> eg: >>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3721/ >>> >>> However that is not enough - as it is allowing to push to artifactory, >>> however not to repo. So one can not do changes, nor approve PRs, nor to do >>> a release. >>> >>> Is that expected? If so, From above scope, what is the point of granting a >>> permissions the jenkins-infra/repository-permissions-updater in such case? >>> (as release can not be done anyway) >>> If not, what was expected? Or was something not working as expected? >>> Is there some mechanism how to fix unresponsive maintainer completely? >>> >>> I know that this may be fragile and sensitive topic, but I belive that >>> plugin belongs to wider community, and should not die jsut because single >>> maintainer pass away or say that will do, but never does. >>> >>> Thank you in advance, >>> J. >>> >>> >>> >>> -- >>> Jiri Vanek Mgr. >>> Principal QA Software Engineer >>> Red Hat Inc. >>> +420 775 39 01 09 >>> >>> -- >>> 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/6fed3265-79d7-4e4d-989c-bdc02a3a332d%40redhat.com. >> >> >> -- >> 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] >> <mailto:[email protected]>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/1F78030A-1613-405E-B439-BEDA543B20AF%40notmyfault.dev >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/1F78030A-1613-405E-B439-BEDA543B20AF%40notmyfault.dev?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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/785B4889-CA83-4DDB-AF9D-87C02176F3D0%40notmyfault.dev > > <https://groups.google.com/d/msgid/jenkinsci-dev/785B4889-CA83-4DDB-AF9D-87C02176F3D0%40notmyfault.dev?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/9D0DB105-260E-4D9F-9A28-863B4A0DB18D%40notmyfault.dev.
