David, 1. Add attribution as requested by Apache 2.0 License 2. Stop trying to be helpful under github.com/ingenieux/*
As long as you do this, you have my blessing to keep doing Copy and Paste. -- -- Aldrin Leal, <[email protected]> Master your EC2-fu! Get the latest ekaterminal public beta http://www.ingenieux.com.br/products/ekaterminal/ On Thu, Sep 11, 2014 at 2:12 PM, David Tanner <[email protected]> wrote: > I was attempting to get development of the plugin rolling since you hadn't > responded to anyone for at least six months, which if I understand from the > Jenkins documentation is the proper way to go about things. The issues you > have closed are still sitting in github and haven't been published either. > > > https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories > What to expect > > Please give us about a week to respond to your pull request. If the > repository in question is actively maintained, this is a sufficient time > span for a repository maintainer to acknowledge the pull request you sent. > > If an acknowledgement happens, please try to work with the plugin > maintainer so that he/she can integrate your changes. This is probably what > you are expecting — somebody to review the pull request and merge it. > > However, if your pull request doesn't seem to be getting any attention > after a week or so, then unfortunately we don't have existing developers > reviewing incoming pull requests. Perhaps the repository is not actively > maintained any more. In this case, we don't want your pull request to be in > limbo forever, and hence we'd like you to escalate as follows: > > - If you are comfortable with the change and you feel it should be > merged in the absence of a review, please drop us an e-mail on the dev > list <http://jenkins-ci.org/content/mailing-lists> and ask for commit > access (please provide your GitHub account name and the repository name you > would like to contribute to). See the later section for more information > about what you should be careful about. As explained in Governance > Document#Howtojointheproject > > <https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Howtojointheproject>, > we give out commit access to anyone who asks for it. Once the committership > is granted, please merge the change, and consider making a new release > <https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins>. > - If you feel that the code really needs to be reviewed by someone > more knowledgeable, then similarly drop us an e-mail on the dev list > <http://jenkins-ci.org/content/mailing-lists> and tell us why/what > should be reviewed. And hopefully one of us will be able to get to it. > > In either case, please also consider "joining" the project by getting the > committership, pushing changes directly, and reviewing other inbound pull > request submissions. > > On Thu, Sep 11, 2014 at 11:07 AM, Aldrin Leal <[email protected]> wrote: > >> Sorry David, I won't enter this discussion. I just wanted to make sure >> users were aware this is a copy driven by the pull requests which got stuck >> and got you fed up >> <https://github.com/ingenieux/awseb-deployment-plugin/pull/6> at the >> point of trying to bypass the process >> <https://groups.google.com/forum/#!topic/jenkinsci-dev/_HEkvSTupxk>completely. >> Plus, telling others when to close tickets >> <https://github.com/ingenieux/awseb-deployment-plugin/issues/3> isn't >> very polite. >> >> Great start as a maintainer, I'd say. >> >> Those actions are being disruptive and try to take away focus on >> consensus and treating your users right. >> >> Ethics are personal. Morals I'll leave to the others in this list. >> >> >> -- >> -- Aldrin Leal, <[email protected]> >> Master your EC2-fu! Get the latest ekaterminal public beta >> http://www.ingenieux.com.br/products/ekaterminal/ >> >> On Thu, Sep 11, 2014 at 1:50 PM, David Tanner < >> [email protected]> wrote: >> >>> I have no issues with attribution. I don't have any experience with >>> creating a duplicate plugin, and was unsure if you would even respond >>> helpfully to any of my emails after you told me off for doing anything with >>> your plugin. I didn't fork your plugin because I thought it needed a new >>> name for the plugin so there isn't any conflicts with the current one. >>> >>> These are the emails that Aldrin sent me. I never got the impression I >>> was harrassing him: >>> >>> >>> On Thu, Aug 21, 2014 at 1:31 PM, Aldrin Leal <[email protected]> wrote: >>> >>>> I just didn't like your attitude. Hard for me to translate into words. >>>> I understand I've been lagging, but at the same time, I believe your >>>> actions have been more about setting people apart than helping to build a >>>> community sense. >>>> >>>> As for that, I recommend you publish your own as a Post Build Step, as >>>> it makes sense. OTOH, I'll keep the AWS Deployment in maintenance mode. >>>> >>>> Thanks >>>> >>>> -- >>>> -- Aldrin Leal, <[email protected]> >>>> Master your EC2-fu! Get the latest ekaterminal public beta >>>> http://www.ingenieux.com.br/products/ekaterminal/ >>>> >>>> >>>> On Thu, Aug 21, 2014 at 4:29 PM, David Tanner < >>>> [email protected]> wrote: >>>> >>>>> Aldrin, >>>>> >>>>> I am not sure I understand what you mean? I asked for push access >>>>> because I had a pull request on the plugin for about a month. The policy >>>>> for plugins is if there is no response then we can ask for access. So I >>>>> did and started working on the open issues and pull requests. >>>>> >>>>> If you would like to maintain the plugin, I am more than happy just to >>>>> submit a pull request and let you handle it. >>>>> >>>>> Sincerely, >>>>> David Tanner >>>>> >>>>> >>>>> On Thu, Aug 21, 2014 at 1:12 PM, Aldrin Leal <[email protected]> >>>>> wrote: >>>>> >>>>>> David, >>>>>> >>>>>> Why don't you fork and create your own fork and publish it instead? >>>>>> >>>>>> Considering your attitude on the github repo, I'd advise you to do it. >>>>>> >>>>>> -- >>>>>> -- Aldrin Leal, <[email protected]> >>>>>> Master your EC2-fu! Get the latest ekaterminal public beta >>>>>> http://www.ingenieux.com.br/products/ekaterminal/ >>>>>> >>>>>> >>>>>> On Wed, Aug 20, 2014 at 8:11 PM, David Tanner < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> Can I be granted access to commit to this plugin? There are some >>>>>>> features I would like add, but it appears there has been no dev activity >>>>>>> here since February. >>>>>>> >>>>>>> githubid: DavidTanner >>>>>>> >>>>>>> Thanks, >>>>>>> David Tanner >>>>>>> >>>>>>> -- >>>>>>> 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]. >>>>>>> >>>>>>> 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]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> 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/Qpy7_lsZsWc/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> 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]. > 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]. For more options, visit https://groups.google.com/d/optout.
