OK, that's a fair point.
I do recall writing a daemon that cleans up access control on
repositories (among other things like disabling issue tracker), but I'm
not too sure if we are running it regularly or not.
Maybe we can extend https://jenkins-ci.org/account so that people can
add/remove access to repositories by themselves? But then that means we
will get rid of the need to ask in the mailing list.
On 11/12/2013 02:05 AM, Christopher Orr wrote:
On 12/11/13 07:25, Kohsuke Kawaguchi wrote:
I still feel strongly that we maintain the open commit access policy.
This is how we've been operating for the longest time, and it's also
because otherwise adding/removing developers to repositories would be
prohibitively tedious.
I agree that the policy of allowing everyone to have a repo and to
commit relatively freely remains a good idea, but having the option to
give new developers push access to 1100 repositories due to how GitHub
teams and our IRC bot work is an issue that has been been raised before:
https://groups.google.com/d/msg/jenkinsci-dev/-Yk0UFfSPZc/GzOu5b1AP7QJ
Would it be reasonable to suggest that we remove the option to add
people to the "Everyone" team from IRC and, if GitHub still adds
newly-forked repos to every team by default, that we have some sort of
process to automatically clean up the teams, as mentioned in that thread?
Regards,
Chris
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins
--
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/groups/opt_out.
