Maintainer for Log Parser Plugin

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Maintainer for Log Parser Plugin

Martin Reinhardt
Hi there,

i want to step in for the Log 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 [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

Re: Maintainer for Log Parser Plugin

Mark Waite-2
The Adopt a Plugin page suggests:

Email the Jenkins Developers mailing list 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:

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 <[hidden email]> wrote:
Hi there,

i want to step in for the Log 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 [hidden email].
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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHmOoWwqfZta-X%2BXNyhvaHm88YkG1zgogsbGz%3DR8MASnQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Maintainer for Log Parser Plugin

Mark Waite-2
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 <[hidden email]> wrote:
The Adopt a Plugin page suggests:

Email the Jenkins Developers mailing list 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:

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 <[hidden email]> wrote:
Hi there,

i want to step in for the Log 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 [hidden email].
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 the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Maintainer for Log Parser Plugin

Martin Reinhardt
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 ([hidden email]) 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 <[hidden email]> wrote:
The Adopt a Plugin page suggests:

Email the Jenkins Developers mailing list 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:

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 <[hidden email]> wrote:
Hi there,

i want to step in for the Log 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 [hidden email].
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com.
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMhJ%3D9MiFFR0zwFE1BsP_y5_yT10U7S_TsQQdZcRNnbMq_GrPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Maintainer for Log Parser Plugin

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 (<a href="javascript:" target="_blank" gdf-obfuscated-mailto="jEVIY9z9CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">mark.e...@...) 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 <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="jEVIY9z9CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">mark.e...@...> wrote:
The <a href="https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FAdopt%2Ba%2BPlugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEiDr0_VCGDBPNt8Wf6c8T30HlLXg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FAdopt%2Ba%2BPlugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEiDr0_VCGDBPNt8Wf6c8T30HlLXg&#39;;return true;">Adopt a Plugin page suggests:

Email the <a href="http://jenkins-ci.org/content/mailing-lists" rel="nofollow" style="color:rgb(75,117,139)" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins-ci.org%2Fcontent%2Fmailing-lists\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFeLeeU73EWn7-D-OoxXzZ_pZp4Gg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins-ci.org%2Fcontent%2Fmailing-lists\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFeLeeU73EWn7-D-OoxXzZ_pZp4Gg&#39;;return true;">Jenkins Developers mailing list 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 <a href="https://github.com/oleg-nenashev/" rel="nofollow" style="color:rgb(75,117,139)" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Foleg-nenashev%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEb5q_ghxLtwceG9I6_9GDd-X27jw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Foleg-nenashev%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEb5q_ghxLtwceG9I6_9GDd-X27jw&#39;;return true;">https://github.com/oleg-nenashev/)
  • Your Jenkins infrastructure account id. Create <a href="https://jenkins-ci.org/account/" rel="nofollow" style="color:rgb(75,117,139)" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins-ci.org%2Faccount%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEYfUxcOYA-WtsEuF6OmLwf-Ufrow&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins-ci.org%2Faccount%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEYfUxcOYA-WtsEuF6OmLwf-Ufrow&#39;;return true;">your account if you don't have one.

Once granted access, you can file a PR (with your Jenkins infrastructure account id) against <a rel="nofollow" href="https://github.com/jenkins-infra/repository-permissions-updater" style="color:rgb(75,117,139)" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;">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 <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="jEVIY9z9CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">reinhar...@...> wrote:
Hi there,

i want to step in for the Log Parser Plugin: <a href="https://github.com/jenkinsci/lo=g-parser-plugin" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Flo%3Dg-parser-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE4fRXoScUTDDlZFmd0OvPS-DEQxA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Flo%3Dg-parser-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE4fRXoScUTDDlZFmd0OvPS-DEQxA&#39;;return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="jEVIY9z9CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 <a href="https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe&#39;;return true;"> https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="jEVIY9z9CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;"> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a5a77d1f-db89-4ddb-85e3-1f31aa278c57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Maintainer for Log Parser Plugin

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 ([hidden email]) 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 <[hidden email]> wrote:
The <a href="https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FAdopt%2Ba%2BPlugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEiDr0_VCGDBPNt8Wf6c8T30HlLXg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FAdopt%2Ba%2BPlugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEiDr0_VCGDBPNt8Wf6c8T30HlLXg&#39;;return true;">Adopt a Plugin page suggests:

Email the <a href="http://jenkins-ci.org/content/mailing-lists" rel="nofollow" style="color:rgb(75,117,139)" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins-ci.org%2Fcontent%2Fmailing-lists\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFeLeeU73EWn7-D-OoxXzZ_pZp4Gg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins-ci.org%2Fcontent%2Fmailing-lists\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFeLeeU73EWn7-D-OoxXzZ_pZp4Gg&#39;;return true;">Jenkins Developers mailing list 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 <a href="https://github.com/oleg-nenashev/" rel="nofollow" style="color:rgb(75,117,139)" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Foleg-nenashev%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEb5q_ghxLtwceG9I6_9GDd-X27jw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Foleg-nenashev%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEb5q_ghxLtwceG9I6_9GDd-X27jw&#39;;return true;">https://github.com/oleg-nenashev/)
  • Your Jenkins infrastructure account id. Create <a href="https://jenkins-ci.org/account/" rel="nofollow" style="color:rgb(75,117,139)" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins-ci.org%2Faccount%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEYfUxcOYA-WtsEuF6OmLwf-Ufrow&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins-ci.org%2Faccount%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEYfUxcOYA-WtsEuF6OmLwf-Ufrow&#39;;return true;">your account if you don't have one.

Once granted access, you can file a PR (with your Jenkins infrastructure account id) against <a rel="nofollow" href="https://github.com/jenkins-infra/repository-permissions-updater" style="color:rgb(75,117,139)" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;">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 <[hidden email]> wrote:
Hi there,

i want to step in for the Log Parser Plugin: <a href="https://github.com/jenkinsci/lo=g-parser-plugin" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Flo%3Dg-parser-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE4fRXoScUTDDlZFmd0OvPS-DEQxA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Flo%3Dg-parser-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE4fRXoScUTDDlZFmd0OvPS-DEQxA&#39;;return true;">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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 <a href="https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe&#39;;return true;"> https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;"> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/01bc7036-c05a-480a-b7b9-814666ec39f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Maintainer for Log Parser Plugin

Martin Reinhardt
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 ([hidden email]) 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 <[hidden email]> wrote:
The <a href="https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FAdopt%2Ba%2BPlugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEiDr0_VCGDBPNt8Wf6c8T30HlLXg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FAdopt%2Ba%2BPlugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEiDr0_VCGDBPNt8Wf6c8T30HlLXg&#39;;return true;">Adopt a Plugin page suggests:

Email the <a href="http://jenkins-ci.org/content/mailing-lists" rel="nofollow" style="color:rgb(75,117,139)" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins-ci.org%2Fcontent%2Fmailing-lists\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFeLeeU73EWn7-D-OoxXzZ_pZp4Gg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins-ci.org%2Fcontent%2Fmailing-lists\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFeLeeU73EWn7-D-OoxXzZ_pZp4Gg&#39;;return true;">Jenkins Developers mailing list 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 <a href="https://github.com/oleg-nenashev/" rel="nofollow" style="color:rgb(75,117,139)" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Foleg-nenashev%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEb5q_ghxLtwceG9I6_9GDd-X27jw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Foleg-nenashev%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEb5q_ghxLtwceG9I6_9GDd-X27jw&#39;;return true;">https://github.com/oleg-nenashev/)
  • Your Jenkins infrastructure account id. Create <a href="https://jenkins-ci.org/account/" rel="nofollow" style="color:rgb(75,117,139)" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins-ci.org%2Faccount%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEYfUxcOYA-WtsEuF6OmLwf-Ufrow&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins-ci.org%2Faccount%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEYfUxcOYA-WtsEuF6OmLwf-Ufrow&#39;;return true;">your account if you don't have one.

Once granted access, you can file a PR (with your Jenkins infrastructure account id) against <a rel="nofollow" href="https://github.com/jenkins-infra/repository-permissions-updater" style="color:rgb(75,117,139)" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;">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 <[hidden email]> wrote:
Hi there,

i want to step in for the Log Parser Plugin: <a href="https://github.com/jenkinsci/lo=g-parser-plugin" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Flo%3Dg-parser-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE4fRXoScUTDDlZFmd0OvPS-DEQxA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Flo%3Dg-parser-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE4fRXoScUTDDlZFmd0OvPS-DEQxA&#39;;return true;">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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/61316fa1-7838-411a-ac3a-ce8e18d6dede%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 <a href="https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe&#39;;return true;"> https://groups.google.com/d/topic/jenkinsci-dev/e76TyU_MBVU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;"> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFb2avQOyN3_zoqsO2NukN3PBwqwU2vypyK3PLjyejpfQ%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
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.