2011/11/10 martin brook <[email protected]>: > ---------- Forwarded message ---------- > From: Carl Symons <[email protected]> > Date: Thu, Nov 10, 2011 at 1:21 AM > Subject: Re: [mer-general] Governance draft > To: martin brook <[email protected]> > Cc: [email protected] > > > Good work on getting something into a document. > > This addresses the way technical governance will work. Except for > interest groups and maybe the Advisory Board, which could really be > anything, there is nothing outward facing. > > It would be helpful to designate folks who will "speak" for the > Project in the outside world.
In truth, aren't each maintainer and technical leader capable of speaking of their own areas within the project? And each interest group gathers input from their members and speaks on behalf of themselves. You can speak on behalf of your area within the project, always - after all, you're the expert in that area within the project. This governance model isn't so about top down management but instead that a open source product (in this particular case) is formed by the various forces and recognising this. When it's a collaborative project like this, a lot of it is based around process and discussion, with someone (maintainer/technical lead/architect) capable of setting the direction within their area. For outreach, the advisory board can establish a group of people to go out for conferences and present based on what moves in the project or advise on what is recognised direction in the project. The only prominent and directly representing role is the architect, but in truth everyone else has their own area to speak of and present as well. It all depends on what roles they perform. Typically when a person is needed to represent the project, it is often that this is due to that the party wanting a representative thinks that the person can influence the future of the project. This would ideally in Mer be done through the interest groups - and through actual contribution to the project. You're not engaging with a single person/"CEO", you're engaging with an entire project in practice. BR Carsten Munk
