Conflict solving and maintainer

[Boudewijn Rempt]

On Monday 06 December 2010, Cyrille Berger Skott wrote:
> On Monday 06 December 2010, Boudewijn Rempt wrote:
> > On Monday 06 December 2010, Mark Kretschmann wrote:
> > > In Amarok, all of our core developers (or "citizens") are basically a
> > > team of maintainers. And we always try to resolve conflicts by
> > > consensus. Only if that fails (very rarely), then we might do a
> > > voting. That happens maybe once a year or so.
> > 
> > It depends a lot on the project and what you think the role of "maintainer"
> > is. If it's the cerberus who keeps ugly code out, then we can do without.
> > But in the current state, every koffice app needs someone who pulls,
> > pushes, blogs, writes, evangelizes, talks to the press, helps newcomers,
> > does janitorial stuff and keeps an overview of what's going on. That's the
> > role of a maintainer to me.  The amarok community might be large enough
> > that this sort of thing happens anyway, ours isn't yet.

> I am not sure if it is a question of numbers of developers, but more a 
> question of code size (and maybe ratio developers / LOC). KOffice is huge and 
> the maintainer become the contact point. Who will probably redirect questions 
> and inqueries.

That's indeed another role maintainers have in our community.


-- 
Boudewijn Rempt | http://www.valdyas.org, http://www.krita.org