added it to the next meeting… https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda
On 21 Apr 2015, at 14:57, Stephen Connolly <[email protected]> wrote: > I don't know the answer to that. I suggest adding it to the next governance > meeting agenda. > > PERSONALLY: > > My understanding is that you should only be using the OSS infrastructure > (wiki, jira, maven repo, update center, etc) if your plugin is OSS. > > While could accept a wiki page entry as an advertisement for a closed source > plugin, I would prefer a simple clear policy of: only open source plugins can > use the community infrastructure. > > If we want to host a "closed source plugins" wiki page to maintain links to > non-OSS plugins then I think that would be a reasonable compromise. > > On 21 April 2015 at 13:39, domi <[email protected]> wrote: > how do we deal with closed source plugins which only have the documentation > on the jenkins wiki? > e.g.: https://wiki.jenkins-ci.org/display/JENKINS/CxSuite+Jenkins+Plugin > > Domi > > > > On 21 Apr 2015, at 12:10, Stephen Connolly <[email protected]> > wrote: > >> If you come across a plugin on the OSS update center that is in fact closed >> source, please alert the community so that either the plugin can be removed >> or the plugin author can be nagged to open source it. >> >> And FTR CloudBees while has (quite a lot of) closed source plugins, but we >> only host closed source ones on our own update center, in accordance with >> the wishes of the Jenkins community. >> >> Any plugin that CloudBees publishes on the community's update center is open >> source... (part of our internal sign-off process before releasing a plugin >> to the OSS update center is to ensure that all source code is open source. >> For example the now defunct cloudbees-deployer-plugin which was to deploy >> applications to our old RUN@cloud product. That plugin started off as open >> source, then some changes required that it depend on a library we had that >> was closed source, so we had to fork it in-house for 2 years or so, then >> finally we got the full chain of dependencies open source again and re-open >> sourced the plugin... of course 6 months after that the business decided to >> shut down RUN@cloud... so we subsequently refactored the plugin to spin out >> the (to our thinking - quite useful) deployment framework as separate from >> the RUN@cloud specific deployment engine) >> >> On 21 April 2015 at 10:49, Christopher Orr <[email protected]> wrote: >> No, closed source plugins shouldn't be available in the update centre. >> >> You can install your closed source plugins manually, or host your own update >> centre, e.g. see this previous discussion: >> https://groups.google.com/forum/#!topic/jenkinsci-users/NArW8EeRgMs/discussion >> >> Regards, >> Chris >> >> >> On 21/04/15 11:09, Sergey Kadaner wrote: >> Hi, >> is there an option to post closed source plugin on >> https://wiki.jenkins-ci.org/display/JENKINS/Plugins or at least make it >> available in automatic update notifications inside Jenkins? >> >> I cannot find any option to do so. >> >> Thanks in advance, >> Sergey >> >> -- >> 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/55361D2D.8050507%40orr.me.uk. >> >> 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/CA%2BnPnMzjyJYqKqujNu3rRPfSW9EJuJD1k4jzt0MZSEy-fFg8sw%40mail.gmail.com. >> 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/36308A4A-E206-4232-B478-C860FB6A99A5%40fortysix.ch. > > 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/CA%2BnPnMwMO0pi_kZPRSBV0dTZH7e2RnK%3Dtx0y8pSBf9eQumzH9Q%40mail.gmail.com. > 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/D4C9DBFB-70A8-4B2B-9B4C-44CD9AD15458%40fortysix.ch. For more options, visit https://groups.google.com/d/optout.
