[haiku-development] Re: Proposal of commit access for Puck Meerburg
- From: Urias McCullough <umccullough@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 16 Jan 2015 14:51:24 -0800
On Fri, Jan 16, 2015 at 2:45 PM, Augustin Cavalier
<waddlesplash@xxxxxxxxx> wrote:
> I too cleared it with them, because I have commit access to HaikuPorts and
> HaikuArchive (neither of which is "officially" affiliated with Haiku
> [Inc.]), and explicitly noted that I didn't have commit access to the
> "haiku" and "buildtools" repositories. As far as I could tell from their
> response, this last bit was the deciding factor. But since the contest ends
> in 3 days I guess there's not much point to debating or asking.
<sigh>
No I will ask again, and get the response in writing, because this
could matter next year as well.
What I was told, specifically, is that it would make no sense to
punish students who are already involved in the project and have
earned commit access - if anything, those students are more likely to
succeed and they deserve it.
People with commit access are in no way employees, contractors,
interns, officers, or directors of Haiku, Inc. - they are just people
with commit access. Haiku, Inc. essentially has no say over who has
commit access, or the direction of the project in general.
Furthermore, without a sponsoring organization, Google will not allow
a project to participate in GSoC or GCI, so it is not the project that
is the organization here, it is Haiku, Inc.
I'm sorry this thread was derailed on the basis of something that is
completely non-relevant to whether or not Puck should gain commit
access - but I feel like I've have this conversation 3 times with you
now...
- Urias
Other related posts:
