So I got a reply from Jetbrains and they would be willing to supply us with licenses expect for those that get paid to work on jenkins or sell a jenkins product (ie. Cloudbees). However they mentioned Kohsuke could still be the administrator but anyone could apply as long as they project lead or core committer.
Here is the emails between Jetbrains and me ------- Hello Joseph, Our apologies for a delay with a response from our side. Seems like your me= ssages were blocked by Spam filter. We used to support Jenkins project in our OS Program before the change in t= he rules. Our contact from your side has been Kohsuke Kawaguchi. To apply f= or the OS licenses on behalf of an OS project one should be the project lea= d or a core committer. Especially when a project is big as yours. [Here](ht= tps://groups.google.com/forum/#!msg/jenkinsci-dev/3XRhnf8ferI/VqUvT-xtAQAJ)= is mentioned Kohsuke Kawaguchi is no longer eligible to manage them. Why d= o you think so and who is the team lead now? We look forward to your response. Should you have any further questions - w= e are happy to help. Have a nice day! ------- Hi Thanks for getting back to me Kohsuke is still the project lead, though he works for Cloudbees, which sel= ls enterprise grade Jenkins. Which also exclude most of the core contributor, since they work for Cloudbees, from applying to the JetBrains OS license. https://www.cloudbees.com/products So according to a Jenkins meeting they saw the need to find a contributor that was not working directly for cloudbees, That did not fall under the "Projects that are sponsored by a commercial company or organization, or those with employees paid to work on the project are not eligible" http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-meeting.2016-03-30-18.00.html http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-meeting.2016-03-30-18.00.log.html http://meetings.jenkins-ci.org/jenkins/2015/jenkins.2015-02-18-19.01.html http://meetings.jenkins-ci.org/jenkins/2015/jenkins.2015-02-18-19.01.log.html And according to those meeting batmat one of Jenkins core contributor, that does not work for Cloudbees, were suppose to figure out the license owner for Jenkins. He has regrettably been too busy from my understanding, this is where I com= e in as a Plugin maintainer decided to take action. https://github.com/jenkinsci/accurev-plugin But if we could figure something out. I would happily put it on next meeting agenda for the Jenkins project March 1st or March 15th: https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda Looking forward to your response :) /Joseph ------- Hello Joseph, Thank you for a prompt and detailed response. Sorry for a short delay from my side. I've talked to the PMM for IntelliJ IDEA. We can support Jenkins with the free OS licenses. Kohsuke Kawaguchi can still remain the administrator for your project. This means he can send the request and distribute the licenses. He is not eligible for the free OS license - that's true. Do you wish to apply on behalf of Jenkins in general or on behalf of the plugins? How many licenses are needed? We look forward to your response. Should you have any further questions - we are happy to help. Have a nice day :-) Den mandag den 22. februar 2016 kl. 23.02.42 UTC+1 skrev Daniel Beck: > > Hi everyone, > > JetBrains recently changed the rules on open-source licenses, and KK is no > longer eligible to manage them. > > https://www.jetbrains.com/buy/opensource/?product=idea > > Ideally, someone else who qualifies would handle the IntelliJ IDEA > licenses for the software project. > > Any volunteers? > > Daniel > > -- 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/399d3e79-25ce-4df7-999f-d898431efc1e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
