[haiku-development] Re: [haiku-development] Re: [haiku-development] Re: [haiku-development] Re: [haiku-development] Re: [haiku-development] Re: [haiku-development] Re: [haiku-development] Re: [haiku-development] Re: [haiku-development] SVN access for Fredrik Modéen

  • From: "Jorge G. Mare (aka Koki)" <koki@xxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 23 Apr 2008 15:12:28 -0700

Ingo Weinhold wrote:
> On 2008-04-23 at 20:43:09 [+0200], Niels Reedijk <niels.reedijk@xxxxxxxxx> 
> wrote:
>> Well, I do not really agree with that we should be able to discuss
>> people like this. For one, I do not have a good overview of what
>> Fredrik has contributed so far. I find it hard to vote in favor for it
>> (though I will not vote against it for now).
> Nobody forces you to vote. If you can't judge, don't vote.
>> I would suggest we will construct a policy for dealing with this
>> stuff. Note that the numbers below here are completely random:
>> A contributor can request SVN access (and as such join the development
>> team) with three requirements:
>> - Patches. The contributor should have contributed 8 patches, of which
>> 5 in one subcomponent. (We want the developer to be responsible for a
>> particular component. There might be people that spread patches all
>> over the place, but those patches will need to be reviewed).
>> - Sponsor. The contributor should ask the maintainer (or regular
>> contributor) of his 'main' component to consider him as a potential
>> developer.
>> - Reviewer. A secondary developer should review the patches (mainly
>> for style and quality) and approve the application.
>> So the procedure is the following:
>> #1 The contributor has sent in 8 patches via Trac. The sponsor either
>> invites him/her, or the contributor contacts the sponsor privately. He
>> will send in the list of patches in Trac.
>> #2 The sponsor reviews the application and lets the contributor know
>> if he will sponsor the proposal.
>> #3 The contributor looks for a reviewer.
>> #4 The reviewer approves the application and contacts the sponsor.
>> #5 The sponsor contacts this main mailing list with the list of
>> patches and asks if anyone objects to the application. This procedure
>> takes 7 days.
>> #6 After 7 days the sponsor makes sure the contributor gets svn access
>> and developer permissions on Trac
>> If during #5 someone objects, he will privately contact the sponsor.
>> The sponsor will mediate, but if this does not work, the sponsor will
>> call a vote by private mail. Voting is not anonymous.
>> The sponsor can at whatever time withdraw or veto the application.
>> The aim of this procedure is to show everyone how things work, and to
>> make sure nothing uneasy has to be discussed on this mailing list.
>> Also - this is not to discredit Fredrik or any of the other recent new
>> developers - it will quantify some standards that I up to now found
>> lacking.
> I'm all for formalizing the process a bit, but this sounds awfully 
> complicated.


> It's not a job someone is applying for. It's volunteer work and 
> he/she already has already contributed or no one would propose to grant 
> him/her write access. Every developer can (and should) subscribe to the 
> commit list and read through the patches that have been submitted.
> I'd be fine, if we had a rough description of what requirements a candidate 
> should fulfill and how long the voting period is.

The "Getting Started" page under the Development area of the website...


...states the following:

"After you've sent a few patches and thus shown us that you're serious
about contributing we will add you to the Haiku Project
<http://developer.berlios.de/projects/haiku> and give you SVN repository
write access. You will need a BerliOS <http://developer.berlios.de/>

In order to make this information more prominent and a bit more
explanatory, I suggest that we change the text to something along the
lines of:

Obtaining SVN write access

SVN write access to the Haiku repository is granted to developers on the
basis of their contributions to the Haiku code base. Your shortest way
to obtaining SVN write access is by submitting patches using our <>Trac
bug reporting tool<>.

After a number of your patches have been successfully committed to the
Haiku repository, you can send a request for SVN write access to <>the
[haiku-development] mailing list<>. In order to facilitate the task of
reviewing your contributions and making a decision on your request,
please include in the message a list of your patches (title and link to
the Trac entry).

If your request is accepted, you will need a <>BerliOS<>
<http://developer.berlios.de/> account.





Other related posts: