Done. I added you as a committer Kaede. Please work as much as possible in
agreement with other maintainers. A good practice would seem to be to at
least go through a PR process and ping others, then if nobody complains,
say in a few days or something, merge it (so somehow using a form of lazy
consensus if need be).

Thanks for your work!

2016-03-15 15:20 GMT+01:00 Akai Kaede <[email protected]>:

> @eivndw, thanks confirmed PR processed.
>
> @Jenkinsci-dev, I like to maintain the plugin further and
> appreciate if someone can grants the appropriate control to my account
>
> Thanks,
>
> Kaede
>
> ------------------------------
> Date: Mon, 14 Mar 2016 20:06:46 +0100
> Subject: Re: Liking to follow-up the Pull Request for grinder plugin
> From: [email protected]
> To: [email protected]
> CC: [email protected]; [email protected]
>
> Hi,
>
> It's been years since I contributed the initial version of the plugin. I
> think it is positive if Kaede wants to maintain it further. I have merged
> the PR. Suggest push-access be granted to Kaede, as I don't seem to have
> the rights to grant this myself.
>
> -Eivind
>
> On Mon, Mar 14, 2016 at 7:00 PM, Akai Kaede <[email protected]> wrote:
>
> Adding eivndw...
>
> The last commit was made on Apr 6, 2012. Found no commit since then. The
> other PR by  frankbp
> <https://github.com/jenkinsci/grinder-plugin/issues?q=is:pr+is:open+author:frankbp>
> has been hold since Jan 26, 2014
>
> Thanks,
>
> Kaede
>
> ------------------------------
> Date: Mon, 14 Mar 2016 17:10:09 +0000
> Subject: RE: Liking to follow-up the Pull Request for grinder plugin
> From: [email protected]
> To: [email protected]
>
> Hi, the process is to try as much as possible to get an explicit nod from
> the deemed current maintainer. Please add her/him in copy.
>
> And cannot check that very repo now, but 2 weeks is still very short
> actually. Were there no commits recently? What is the most recent commit
> date?
> Thanks
> Le 14 mars 2016 4:48 PM, "Akai Kaede" <[email protected]> a écrit :
>
> Hi,
>
> It is seemed that no maintainer actively take care of the grinder plugin.
>
> How do I take an action in this case?
>
> Regards,
>
> Kaede
>
>
> ------------------------------
> From: [email protected]
> To: [email protected]
> Subject: Liking to follow-up the Pull Request for grinder plugin
> Date: Mon, 7 Mar 2016 17:15:36 -0500
>
> RE: [grinder-plugin] Update the result reader to parse final statistics
> only (#3)
> Akai Kaede
> 3/04/16
> <https://blu174.mail.live.com/ol/#>
> To: [email protected]
> <https://blu174.mail.live.com/ol/#>
>
> <https://blu174.mail.live.com/ol/#>
> Hi
>
> Please grant write access to the grinder plugin repository. My pull
> request has been not reviewed for 2 week and
> I like to contribute myself for the further development.
>
>
> my jenkins-ci.org for jira is plutoatom4
>
> Regards,
>
> Kaede
>
>
>
> ------------------------------
> Date: Mon, 22 Feb 2016 17:02:02 -0800
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> Subject: Re: [grinder-plugin] Update the result reader to parse final
> statistics only (#3)
>
> Thank you for this pull request! Please check this document
> <http://jenkins-ci.org/pull-request-greeting> for how the Jenkins project
> handles pull requests.
>
> -
> Reply to this email directly or view it on GitHub
> <https://github.com/jenkinsci/grinder-plugin/pull/3#issuecomment-187458660>
> .
>
> --
> 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/BLU174-W900DA3BC0B97089A4167195B10%40phx.gbl
> <https://groups.google.com/d/msgid/jenkinsci-dev/BLU174-W900DA3BC0B97089A4167195B10%40phx.gbl?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/BLU174-W352ADAD59EB6004D77B79595880%40phx.gbl
> <https://groups.google.com/d/msgid/jenkinsci-dev/BLU174-W352ADAD59EB6004D77B79595880%40phx.gbl?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/CANWgJS4Ta8gq9uV1%2BH6p3t%2BEPm4ZXd4g7Piq-NR9iionQSf%3D4A%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4Ta8gq9uV1%2BH6p3t%2BEPm4ZXd4g7Piq-NR9iionQSf%3D4A%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/BLU174-W443802ACF5528A248F9CC95890%40phx.gbl
> <https://groups.google.com/d/msgid/jenkinsci-dev/BLU174-W443802ACF5528A248F9CC95890%40phx.gbl?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/CANWgJS4ARhcz0ts4U-0OOpG-UQtkvjtMcCgKeiOWd987CGpfPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to