We might not be enforcing it today, but it's at least my intention that we want all the plugins in the community update center be hosted on our GitHub org. To me, it's an important part of creating an incentive for people to come to the community.
There's also the continuity problem --- if you write a plugin that works for you and you move on to other projects, and if somebody else takes over the plugin to carry it forward, we have no way of tracking whose plugins should be "official."
You say it is for obvious reasons you'd want them listed under different org, but I'd like to ask you why that is.
If it is the credit problem, we have companies like Praqma who develops plugins and posts them in the Jenkins org, and they'd still take credits by putting their logos on Wiki [1]. Other companies use their company names as package names.
[1] https://wiki.jenkins-ci.org/display/JENKINS/PRQA+Plugin On 03/24/2014 11:04 AM, Surya Gaddipati wrote:
My employer is interested in opensourcing a plugin that we developed in house. But we would like our plugin to be under github org not jenkins-ci ( for obvious reasons) . Is it possible to make plugin show up in the default jenkins update center? -- 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] <mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout.
-- Kohsuke Kawaguchi http://kohsuke.org/ -- 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.
