[haiku-development] Re: Dario
- From: Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 28 Oct 2018 20:43:57 +0100
On Sat, Oct 27, 2018 at 06:50:42PM +0100, Simon Taylor wrote:
Hi all,
This is a difficult subject to bring up one which I believe should be
discussed.
I think the project should consider revoking Dario’s commit access.
I would vote "not at this point".
First of all, I want to point out it seems very inappropriate for
someone not part of the project to bring up the topic. It is a bit like
someone writing to my employer, asking them to consider firing me.
Dario’s code and ideas may well be excellent. However there is more to being a
member of the Haiku project than simply writing excellent code. It is a team
project where discussion of changes should be welcomed and where engaging with
the peer review process is a fundamental part of being trusted with commit
access. The difference between Dario’s approach here and that of other
contributors is striking.
I agree on this, however we discussed this with Dario and I think he
understands the point. I think it's ok to give him a second chance, but
I consider the warning has been sent quite clearly. I hope it is still
possible to work with him, however I don't have much patience left now.
Without commit access Dario would be free to fork the repo as he liked and
make whatever changes he wanted without any requirement to describe or justify
them. I know from previous recent posts to the mailing lists that he has many
different ideas about the direction of the project as a whole. Therefore
despite having no doubt in the capability of Dario as a developer, I feel that
forking Haiku and working on it as a project with him as the undisputed owner
would be a better fit for his personality.
He already forked Haiku and is now working on V\OS, which reuses parts
of Haiku code running on top of a Linux Kernel. His current work is also
part of this effort, in an attempt to keep both project somewhat
synchronized.
Haiku may well lose some useful future contributions from him but it would
also reduce tension and friction in the remaining development team. Overall I
think it would be the right thing for both parties.
I still hope we don't have to get to a ban. I'll keep an eye on it,
however.
Also, we still don't have a code of conduct and neither do we have clear
written rules about how the project is organized and run (including how
adding or removing contributors is handled). It would be nice to write
this down so we can know exactly what to expect and how to handle such
things. I would prefer that we clarify this first.
--
Adrien.
Other related posts:
