The spirit of jenkins community has always been to lower the entry barrier
as much as possible (aka "*want to contribute ? you can commit now*") which
for most of us do immediately remind the "*great power gives great
responsibilities*" spiderman-syndrom, and make people act with care and/or
rely on PR for code they are not confident with.


2015-09-14 11:46 GMT+02:00 Kanstantsin Shautsou <[email protected]>:

> Branch may be more critical in plugin rather then master, so implicitly
> broke other branches is not a solution IMHO.
> Most maintainers has Admin access to their repos and can enable protection
> if they want, no need enforcing it.
>
> About [1]. This person was not maintainer of all (?) repos that he broke,
> so why he has access WRITE to all of them?
> IMHO happened because Kohsuke organised project in such way that everybody
> who don’t know about jenkins has write access everywhere and can f*** all
> plugins.
>
> On Sep 14, 2015, at 09:05, ogondza <[email protected]> wrote:
>
> My idea was preventing incidents like [1] to happen.
>
> I do not see a problem with force-pushing to feature branches (provided
> noone based ones work on that), not to mention we do not encourage people
> to create feature branches in core repo.
>
> [1]
> http://jenkins-ci.org/content/summary-report-git-repository-disruption-incident-nov-10th
>
> --
> oliver
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/0ciUju7raOA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/818ef4a1-8ced-4681-abeb-1468a550b2e1%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/818ef4a1-8ced-4681-abeb-1468a550b2e1%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 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/E6354652-2BD7-4354-836A-C6D99E5EBB88%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/E6354652-2BD7-4354-836A-C6D99E5EBB88%40gmail.com?utm_medium=email&utm_source=footer>
> .
>
> 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/CANMVJzne67DEWgFznAqvK768ejYZMfMr2NGiZwF9THZWmRHSpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to