>Jenkinsci project model is bazaar. I see no any reasons for enforcing somebody unrelated to reasons why plugin was created causing delays by asking why some company needs host some plugin. Somebody created plugin and share for mass usage, you may use it or not. Delays for development ends with cases when people start hosting plugins on their own servers.
I have a comment/proposal about this but don't want to hijack this thread as it seems offtopic. Perhaps a new topic. On Sunday, December 20, 2015 at 8:03:40 AM UTC-6, Kanstantsin Shautsou wrote: > > Situation: people doing reviews, blocking PRs for weeks,months,years while > some people do direct commits to core master without any reviews. > This ends to situations when master gets broken state that reflects on PR > builds verification, i.e. > https://github.com/jenkinsci/jenkins/commit/d86a88ab042cc55530d91e745af9e0886e8eeb79 > Unreviewed changes adds chaos. While people reviewing and close to get rid > of unconfigurable settings in > https://github.com/jenkinsci/jenkins/pull/1914 one person is doing direct > master changes > https://github.com/jenkinsci/jenkins/commit/653fbdb65024b1b528e21f682172885f7111bba9 > > Proposal: stop doing such unreviewed changes and forbid direct master > commits (either at all, either only for mentioned person). > > PS. AFAIR/AFAIK if you signed ICLA and do some questionable changes into > master (here i see 2 violations) person should get core access removal, > right? > > -- 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/0a9a4132-0e77-4588-83f3-a6d5e24f1754%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
