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, November 7, 2019 at 8:01:39 AM UTC+1, Gavin Mogan wrote:
>
> 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 github
> and creating a PR for 
> https://github.com/jenkins-infra/repository-permissions-updater, pinging 
> yet again the original maintainer
>
> Gavin
>
>
> On Wednesday, November 6, 2019 at 10:51:44 PM UTC-8, Bjoern Kasteleiner 
> wrote:
>>
>> 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-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 as 
>> > CC to this mail. 
>> > 
>> > Thanks a lot 
>> > 
>> > Bjoern 
>> > 
>>
>>

-- 
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/027b6163-23e0-4f20-bf3f-39c53154b160%40googlegroups.com.

Reply via email to