[haiku-development] Re: VOTE commit access for Augustin

  • From: Alexander von Gluck IV <kallisti5@xxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Fri, 25 Jul 2014 10:13:32 -0500

On , Oliver Tappe wrote:
On 2014-07-24 at 11:54:39 [+0200], Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
wrote:
> On July 24, 2014 at 1:21 AM Rene Gollent <anevilyak@xxxxxxxxx> wrote:
> On Jul 23, 2014 6:19 PM, "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> wrote:
> > I'd like to propose commit access for Augustin Cavalier. This is what
> > he's done so far:
> > http://cgit.haiku-os.org/haiku/log/?qt=author&q=waddlesplash
> I'm afraid I'm going to have to vote -1 at this point. While he may be
> enthusiastic, the patches are mostly trivial enough that they don't really
> convince me on a technical front, and what I've seen of his interactions
> on
> the mailing list and elsewhere leave me in serious doubt with regards to
> him being a good fit for the team in general.

Thanks for being so honest about it!

Since I don't have such doubts so far, could you elaborate a bit where you
see
the problems with him fitting into the team?

Additionally, while Augustin obviously is very determined to work on the next Haiku release, I'm not sure I feel very comfortable with the way how he has been going on about it, which involves repeatedly asking other people to do
things that he feels should be done now.

This is definitely an issue. The biggest law in open source is that if you want something done, ask those who know how nicely. Then do that thing yourself if
they don't have the time.

Once he follows that advice though, I'm confident that Augustin will manage to integrate and become a valuable member of our community, but right now I don't think it would be a good idea to give him commit access (and/or make
him our release coordinator/manager).

I wish the topic of him being not ready to be a release coordinator role came up more when he was proposing it on the ML. By staying quiet the community really hasn't directed him to back away from being the RC. I don't think he is ready either, but I couldn't say much after my release coordinator rage quit. I now have 0 free time and won't have any for quite some time. (which is why I was pushing to get R1A5 out as the RC a few months ago ;-)) I have no idea how we'll get the next release out at this point. R1A4 may be the last one for a while unless we have
someone with commit access step up.

-- Alex

Other related posts: