On 16.02.2015, at 16:43, Kanstantsin Shautsou <[email protected]> wrote:
> imho Assuming that now only CloudBees persons has power under jenkins, it's > main development and everything is locked on CB people, then we have no way. It shouldn't be a surprise that a company whose business is services on top of Jenkins wants to and can improve Jenkins. And anyone whose day job is work on Jenkins can often contribute more than someone doing this in their spare time. There's nothing "locked" about it. In fact, the entire Jenkins project is remarkably open and easy to get into (aside from a few areas that are more restricted for good reason, such as security and infra -- and all the available bees we pinged about INFRA-240 couldn't help us because they don't have access either!). -- 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/9BF4702F-EDA4-48EF-8BA0-1187E29FBE44%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
