[Rock-dev] Draft of Github-based development process [IMPORTANT]

[Sylvain Joyeux]

Hi

(Note: be careful, you reply only to me and not to the ML)

 - I don't want to give the power to a few people to do this selection. It
will lead to bikeshed bitter arguments (why am I not included ? Why is Y
included I don't think he should ? It can get very personal very quickly).
Rock is not big enough to already start having an overseeing team. Let the
coding decide.
 - people that have committed a lot are the ones that know the codebase, so
that is IMO the best people as a starting point
 - this is an INITIAL list. Obviously, it will be updated over time. Now, I
would NOT add anybody in there that did not already contribute a
significant amount of code, simply because they are probably not familiar
with the codebase (and therefore is not suited to decide what to push or
not push there).

Sylvain



On Thu, May 15, 2014 at 12:37 PM, Jakob Schwendner <jakob.schwendner at dfki.de
> wrote:

> >       Also, I don't agree with the last section. I would not want to
> rule who
> > has committed the most in the dicision on who gets the rights.
> >
> >
> > I don't understand your last sentence ... Can you explain ?
>
> In the text you suggest using the numbers on who commited the most to give
> out commit rights.
> Quantity is not quality, and I would argue its  better to select these
> people. These decisions should come from a management team.
>
> Jakob
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.dfki.de/pipermail/rock-dev/attachments/20140515/cac54be6/attachment.htm