[haiku-development] Re: [haiku-development] Re: [haiku-development] Re: [haiku-development] Commit access for Andreas Färber

2010/6/7 Stephan Assmus <superstippi@xxxxxx>:
> Haiku has always been also a ground for experimentation and learning. The
> quality of a random part of the codebase is always a function of the skill
> and experience of whoever worked on it. If someone wants to work on a
> particular part of the code, especially with no one else wanting to work on
> it, then why should we make it harder for him?

If I were a dev that had to be able to fulfill our high qualities
before getting commit access I'd wonder if I'd be able to do it and if
it is worth the effort. Luckily Haiku is a very nice project to work
on. I'm not saying it should be lowered much, you still need to be
able to be a pretty decent developer and know your way around the
codebase.

But maybe it's just the way of working with patches that limits
outside devs. Patches tend to get stale quickly, but if you could
manage your own tree and changesets better it would not be much of a
problem. Would Git or Mercury be better?

/Fredrik Holmqvist, TQH

Other related posts: