There is an element in your note of there being a single person (or pair) with practical veto power over a component. I thought the switch in terminology from owner to maintainer was in part to avoid that implication.
As I had read it, a maintainer was someone who was promising to put in energy to keep a component current. That does not make him the owner. If he is busy, or just personally clashes with another contributor (we are human), someone else ought to be able to review a commit. I appreciate the need to distribute work. No one can or should have to know everything. (Although some folks seem to be able to come close.) But equally, an fd.io project is not a collection of fiefdoms. So I would hope that we would be careful about how we describe the process to avoid encouraging that. Yours, Joel -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Damjan Marion Sent: Wednesday, December 21, 2016 10:37 AM To: Kinsella, Ray <[email protected]> Cc: vpp-dev <[email protected]> Subject: Re: [vpp-dev] Committer / Maintainer model. > On 21 Dec 2016, at 15:58, Kinsella, Ray <[email protected]> wrote: > > My 2c is that my experience of this model is that maintainers typically get > frustrated and disillusioned over time and become inactive, as they feel they > are minions, doing the tough and often invisble review work but with no real > authority over a feature. You end up with maintainer churn etc. My view here is completelly different, maintainer should have authority of his feature. I.e. if somebody owns vagrant stuff, he should be asked to +1 on any non-trivial change. If maintainer is busy with something else and not taking much care about it anymore, then we either need to find another one or we should remove it completelly from the repo. What we have today is broken, there is many unmaintained stuff in the repo which went out of sync with time and if somebody submits patch to the gerrit, I (and I guess other committers also) don't have a clue what to do with it, as i really never started vagrant in my life. Same story with vppctl, rpm packaging, different plugins... _______________________________________________ vpp-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/vpp-dev _______________________________________________ vpp-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/vpp-dev
