Maybe try creating the permission-updater PR, and tagging them incase they
have some sort of email filtering going on.
On Tue, Nov 12, 2019 at 10:41 AM Björn Kasteleiner
wrote:
> Hello,
>
> thanks to Gavin and Oleg for replying to my mails.
> It was a good idea to try another way to contact the
Hello,
thanks to Gavin and Oleg for replying to my mails.
It was a good idea to try another way to contact the current maintainer.
The situation is kind of weird and I'm not sure if I should continue the
adoption process.
Two hours after my email on the 7th the current maintainer merged the
op
Yes, we usually CC folks in the email to the dev list.
It is what Bjoern did in the original email, and the email in the profile
was used.
+1 for a PR to Repository Permission updater and the final CC, but I
believe that 2-week timeout is over. We can do the transfer this week
On Thursday, Nove
I reached out on twitter -
https://twitter.com/halkeye/status/1192334639844577280, just in case
https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin doesn't give
explicit steps
I think since this has the time elapsed, the best thing is to make an INFRA
ticket on jira to get write access to g
Hello,
I would like to adopt the gitlab-oauth plugin, since the current
maintainer isn't responding anymore.
What do I have to do to become maintainer of the plugin?
Thanks a lot.
Cheers
Bjoern
Am 21.10.19 um 06:47 schrieb Björn Kasteleiner:
Hello,
I would like to adopt the gitlab-oauth-p
Hello,
I would like to adopt the gitlab-oauth-pugin, to take care of the
current issues of the plugin.
Gitlab-User-Id: bjkastel
Jenkins-User-Id: bjkastel
I've already tried to contact the current maintainer at the beginning of
September, unfortunately he hasn't answered yet. I've added him a
