Any progress on that?

More than two weeks were passed :D 

Am Mittwoch, 12. Juni 2019 11:46:57 UTC+2 schrieb Martin Reinhardt:
>
> looking forward to friday ;)
>
> Am Mittwoch, 12. Juni 2019 09:28:57 UTC+2 schrieb Jon Brohauge:
>>
>> Hi Martin
>>
>> Thank you for stepping up to be a maintainer of this plugin. Can't wait 
>> for the PR's to roll onto master ;-)
>>
>> regards
>> Jon
>>
>> On Sunday, June 2, 2019 at 7:33:45 PM UTC+2, Martin Reinhardt wrote:
>>>
>>> Hi Mike,
>>>
>>> thanks for assisting here.
>>>
>>> My GitHub username is hypery2k
>>>
>>> And me Jenkins Account ID is mreinhardt
>>>
>>> -- 
>>> Martin Reinhardt
>>> Sent with Airmail
>>>
>>> Am 2. Juni 2019 um 03:43:43, Mark Waite ([email protected]) schrieb:
>>>
>>> Thanks in advance for adopting the plugin!  I've copied the most recent 
>>> committers to the plugin on this e-mail to assure that they are OK with 
>>> your adopting the plugin. 
>>>
>>> If no response is received from them in 2 weeks, or if they respond that 
>>> they are willing to add you as a maintainer, then the adoption process 
>>> described on the wiki page can start.
>>>
>>> What's your GitHub user name?
>>> What's your Jenkins infrastructure account ID?
>>>
>>> Mark Waite
>>>
>>>
>>>
>>> On Sat, Jun 1, 2019 at 7:37 PM Mark Waite <[email protected]> wrote:
>>>
>>>> The Adopt a Plugin page 
>>>> <https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin> suggests: 
>>>>
>>>> Email the Jenkins Developers mailing list 
>>>> <http://jenkins-ci.org/content/mailing-lists> and request to be made a 
>>>> maintainer (which usually means commit access to the plugin repository and 
>>>> being made default assignee for newly reported issues in JIRA). 
>>>> To that purpose, it's expected to try and reach out to existing 
>>>> maintainer(s) using a best effort. So, the typical way to do that is to 
>>>> put 
>>>> her/his/their email addresses in CC (hint: Git commits should have this 
>>>> information).
>>>>
>>>> We typically wait for about 2 weeks in normal work periods before 
>>>> proceeding, so please be patient. Hence, if you can prove the existing 
>>>> maintainer already agrees and you explicitly asked about taking over (e.g. 
>>>> in a PR discussion), the process can be fast-looped.
>>>>
>>>> *IMPORTANT: To speed up and ease the process, please provide the two 
>>>> following things:*
>>>>
>>>>    - Your GitHub username/id (e.g. oleg-nenashev for 
>>>>    https://github.com/oleg-nenashev/) 
>>>>    - Your Jenkins infrastructure account id. Create your account if 
>>>>    you don't have one <https://jenkins-ci.org/account/>. 
>>>>
>>>> Once granted access, you can file a PR (with your Jenkins 
>>>> infrastructure account id) against 
>>>> https://github.com/jenkins-infra/repository-permissions-updater to be 
>>>> able to deploy snapshots and releases for your plugin. You're generally 
>>>> expected to start slowly, by filing PRs, and not commit directly. Even 
>>>> more 
>>>> for plugins with a big number of installations for obvious reasons.
>>>>
>>>> On Sat, Jun 1, 2019 at 4:26 AM Martin Reinhardt <[email protected]> 
>>>> wrote:
>>>>
>>>>> Hi there,
>>>>>
>>>>> i want to step in for the Log Parser Plugin: 
>>>>> https://github.com/jenkinsci/lo=
>>>>> g-parser-plugin <https://github.com/jenkinsci/lo=g-parser-plugin>
>>>>>
>>>>> A already maintain the RocketChat Plugin.
>>>>>
>>>>> Looking forward
>>>>>
>>>>> Regards
>>>>>
>>>>> Martin
>>>>>
>>>>> --
>>>>> 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/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks! 
>>>> Mark Waite
>>>>
>>>
>>>
>>> --
>>> Thanks! 
>>> Mark Waite
>>> --
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>

-- 
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/591fda29-ae7c-42ca-818e-dadd110afb4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to