Thanks! On Wed, Oct 21, 2015, 11:14 AM Oleg Nenashev <o.v.nenas...@gmail.com> wrote:
> Hi Lev, > > I'll ping Kohsuke regarding the ownership handover. > > Best regards, > Oleg > > среда, 21 октября 2015 г., 9:53:14 UTC+3 пользователь Lev Mishin написал: > >> sorry for the delay, I've just applied your comments >> >> On Saturday, October 17, 2015 at 7:05:07 PM UTC+3, Oleg Nenashev wrote: >>> >>> The response came in a separate thread. Added the plugin's maintainer to >>> Cc. >>> I'd bet that KK will allow it. >>> >>> I've also added some comments to your pull request >>> <https://github.com/jenkinsci/build-name-setter-plugin/pull/6>. IMO >>> needs an update before merging >>> >>> Hi, >>>> Great if you want to adopt a plugin. >>>> Please read and follow the small procedure here: >>>> https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Helpingandtakingoverdormantplugins >>>> >>>> Basically, the TL;DR is: you want to ping the current/last >>>> maintainer(s) to check they are OK to give ownership. >>>> If they give their agreement or don't answer within some days, then >>>> you'll be given permissions to become the official maintainer. >>>> >>>> Cheers >>>> >>> >>> среда, 14 октября 2015 г., 16:17:17 UTC+3 пользователь Lev Mishin >>> написал: >>>> >>>> The last repo update was commited two years ago so the repo looks >>>> abandoned, could you give me write rights for it please? >>>> >>>> On Friday, October 9, 2015 at 7:24:55 PM UTC+3, Lev Mishin wrote: >>>>> >>>>> >>>>> - Github link: >>>>> >>>>> https://github.com/Le0Michine/Jenkins-Build-name-updater-plugin/tree/master >>>>> >>>>> - Repo name: "Build-name-updater-plugin" >>>>> - User name the same as in the URL >>>>> - jenkins-ci.org username: Le0; >>>>> - Description: my plugin updates a build name during the build >>>>> process, it was necessary because custom build name could tell some >>>>> useful >>>>> information. Sometimes we just unable to set custom build name before >>>>> build >>>>> or in pre-build steps because we just don't know that so using my >>>>> plugin >>>>> you can set the build name in a separate build step, you can use a >>>>> file in >>>>> the build workspace or environment variable or both of them as the >>>>> build >>>>> name source. >>>>> >>>>> -- >>>>> >>>>> Kind regards, >>>>> Lev Mishin >>>>> >>>> -- > 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/i9bjjyF75bw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/a8210308-b935-472b-8e6c-f538b8244a1b%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/a8210308-b935-472b-8e6c-f538b8244a1b%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Kind regards, Lev Mishin -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAGAc5LUUrw4tmHTbmy_07uckJt%2BVV_%2B6pM1sMPgP%3DDyNERe5AQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
