Its interesting to note that this plugin is was partly copied with no attribution from my own plugin - down to the screenshots.
(Mind to mention that he previously asked Write Access to the Jenkins-CI fork of my repo. I don't know what option the admins took, I believe he didn't) The main reason, and I'm responsible for it, is that this user had Pull Requests Denied, and started to give me advice on how to run my project. I politely asked him in private to simply fork it and stop harassing me. Well, I'm just making the situation public. I admit I've had a couple of issues, and also didn't get along, but I don't like the idea of having a simply copy (not even a fork!) only to satisfy the needs of this user to get his changes published and bypassing the whole process. -- -- 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:12 PM, David Tanner <[email protected]> wrote: > I would like to publish a new plugin that publishes files to Amazons > elastic beanstalk. My githubID is DavidTanner, my jenkins-ci.org > username is davidtanner, the plugin is located at > https://github.com/DavidTanner/awseb-publisher > > -- > 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.
