[OH-Dev] Login team, vs. commit access

[Asheesh Laroia]

Okay... so I guess we should set some reasonable rules for giving people
commit access, so that there is great clarity about this.

One possible rule set:

"At least one person in the Login Team vouches for you, and you have gotten
at least two patches merged into the project."


I'd love to hear any objections or discussion items people want to raise
with the above policy; in the absence of input, I'll implement that about
24 hours from now.


On Tue, Apr 15, 2014 at 5:17 PM, Asheesh Laroia <lists at asheesh.org> wrote:

> A question:
>
> What if I handed out commit access more liberally?
>
>
> http://openhatch.readthedocs.org/en/latest/community/login_team.html is
> the Login Team, but I could hand out commit access a little more liberally
> than Login Team access.
>
> I guess we could end up in a situation where code is pushed but not yet
> deployed.
>
> I guess we could do something smart with letting people run the
> deploy_myself.sh script, even if they can't
>
>
>
> In the absence of further input, I think what I'll do is:
>
> * Hand out commit access slightly more liberally, and
>
> * Keep deploy access more constrained.
>
> and accept the risk that the deployment may get out of sync.
>
> -- Asheesh.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/devel/attachments/20140416/ea28ba43/attachment.html>