Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: error (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAPRnXtn1LNWOe4f3AjWfHwk_midmNwuCoCiUinDSXO_+HTqFRQ@mail.gmail.com>
References: 
 <CAOqetn-22NuJ5nhVcYCz4SD7c5TsM-Gyh_o11OS9H9h4W-PCOw@mail.gmail.com>
 <CAKprHVbuGRgLrNnew_2VAYvbW+4-CLyEyjYESFJ0=KmbV0WUEw@mail.gmail.com>
 <CAOqetn_ZD91VJWmL=Gx2u8_UPdi63rVdMrx=hzPTKQjygQ31yQ@mail.gmail.com>
 <CAKprHVZ2DXCu9TYnt6uGTRHaYYsUX4icpV9Y-hc_U0jQGx1g7A@mail.gmail.com>
 <CAOqetn_KF9ebVA9iyUES4w8CF+AsvtXWrCHOsnr+_AaKqbUr7A@mail.gmail.com>
 <CAJwFCa04ZPvi=5FX3Ec_qBeZaW+XHLnNZ8b-vQEJvNSH5D+gPw@mail.gmail.com>
 <CAPRnXtn1LNWOe4f3AjWfHwk_midmNwuCoCiUinDSXO_+HTqFRQ@mail.gmail.com>
From: David Nalley <david@gnsa.us>
Date: Fri, 2 Jan 2015 11:40:03 -0500
Message-ID: 
 <CAKprHVbg-Xme1j1UJLmVYyxn6hDu8_OFMzt+5mie=P8yqk6WQg@mail.gmail.com>
Subject: Re: Git write access for podlings
To: general@incubator.apache.org
Content-Type: text/plain; charset=UTF-8

On Fri, Jan 2, 2015 at 5:36 AM, Stian Soiland-Reyes <stain@apache.org> wrote:
> Git allows you to commit as "whoever you want" - e.g. like in SMTP
> email, the headers are decided by the sender. SVN on the other hand
> will show the authenticated user in the commit log. So - speaking as a
> former sysadmin - it sounds a bit daring to let anyone new to Apache
> from a fresh Incubator proposal to also get instant write access to
> all Incubator projects, including those that are just about to
> graduate.


>From a git commit log perspective, this is true, but we also retain
push records that show us the user authenticated as, as well as the IP
Address they are pushing commits from. In example:
https://git-wip-us.apache.org/logs/asf/incubator-nifi.git


>
> That said - assuming there has not been any reported abuse of this
> global write access - then it is a very good sign of all the new
> committers being responsible people - or perhaps they just didn't know
> they had that write access to begin with :). It's a trust-thing - I
> remember when I started my first proper sysadmin job, and on day one
> received the root passwords for systems running web and email for
> 30.000 students. "Don't mess it up" was implicit.
>
> Apache Commons has already given write access to *all* ASF committers
> [1] - which would presumably include any incubator committers.  If
> it's good enough for for Commons, it should be good enough for
> Incubator. Part of moving to Apache is also to trust all your
> committers.
>
> [1] https://mail-archives.apache.org/mod_mbox/commons-dev/201412.mbox/%3CCAB917RJy57Z-4PnwThvR9tUq7Y3td8USG8jCmhVDThALwhoBHg@mail.gmail.com%3E
>
>
> Even with the danger of introducing a bigger temptation by explicitly
> documenting the incubator-wide write policy - I would still +1 to
> document this so you are aware and don't accidentally push back (as
> git workflow is to commit locally and it is a bit easy to accidentally
> do "git push") - with a clause that this does not mean you have
> formally become a committer on the other incubator projects.
>
>
> I would propose to also improve documentation at
>
> http://wiki.apache.org/general/GitAtApache
> http://www.apache.org/dev/git.html
> http://www.apache.org/dev/writable-git
>
> so it does not give impression you have to use SVN-with-git-mriroring
> or that writeable GIT is "experimental". I don't know enough about the
> particular setup at git.apache.org yet to do it myself.


<sigh> I thought we had removed all of the experimental labels.
Thanks for finding these.

--David

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org