Hi all, As we now have passed 31th January, the drafted Mer governance and proposed bootstrapping method is now in effect and wiki pages/web page stating these will be put up.
>From Plasma Active, they have selected a representative - Danny Bennett, who is Principal Engineer at basysKom GmbH (http://www.linkedin.com/pub/danny-bennett/2/991/231) Nemo Mobile effort will be asked to send a representative as well to the first advisory board meeting. This is the composition of the advisory board as noted in the bootstrapping mail: * Architect: Carsten Munk * Nemo Mobile Representative: not chosen yet * Plasma Active Representative: Danny Bennett * Technical leads Representative 1: David Greaves * Technical leads Representative 2: not chosen yet * Maintainer Representative 1: Marko Saukko * Maintainer Representative 2: not chosen yet As interim project architect and hence chairman of the Mer advisory board, I'll work with the advisory board members to find a good date and time for first advisory board meeting (1 Feb is looking a bit unrealistic now) and propose an initial meeting agenda based on what is described in the governance bootstrap mail below. If you are a company utilizing Mer interested to register yourself as an interest group and hence participate in the governance model of the Mer project, please see http://wiki.merproject.org/wiki/Governance#Interest_Groups If you feel there's an agenda item that should be brought up at advisory board meetings, please mail me and this mailing list with the agenda item in question, latest 9 days before a advisory board meeting. The agenda will be available ideally a week before a advisory board meeting happens. After a 48 hour sanity check of the agenda item/result of public discussion, it'll be put on the meeting agenda and you'll have to show up to present the agenda item at the meeting or send a representative to do so. Please only submit topics that is relevant to the areas that the advisory board deals with, as according to the governance description. This can be for instance be nominations based on merit and other functions the advisory board serves. BR Carsten Munk 16. jan. 2012 20.44 skrev Carsten Munk <[email protected]>: > Hi all, > > As some of you know, we have a governance draft for Mer, which I think > it's about time we put it into action. It can be read at > http://wiki.merproject.org/wiki/Governance_draft - we've had a bit of > ad-hoc governance until now. > > However, we have a bit of a bootstrapping problem as we rely on the > composition and existence of technical leaders and maintainers and > interest groups to create the advisory board and without advisory > board we can't nominate technical leaders and maintainers. > > As per privilege of project founder (the only time I'll ever use > that), I'd like to propose the following based on what I can observe > in the community of activity surrounding Mer: > > * Begin with a initial advisory board of 5 participants, 2 interest > group representatives, 1 architect, 1 technical lead, 1 maintainer > > * To formally describe two interest groups for bootstrapping as > they've been the most active around Mer, each selecting a > representative for the advisory board: > - Nemo Mobile (http://wiki.merproject.org/wiki/Nemo) > - Plasma Active (http://community.kde.org/Plasma/Active) > > If anybody else want to register as an interest group in Mer, for > example if you're a company, a group of individuals, or group of > companies, or a open source project based on Mer, you're welcome to > contact this list to indicate your interest. > > * To have Carsten Munk/Stskeeps (me) make a meritocratic claim as > interim Project Architect, based on my project contributions and > architectural & project guidance up to now. > > * To have David Greaves/lbt make a meritocratic claim as interim > Systems & Vendor Relations Technical Lead, based on contribution to > Mer infrastructure and vendor interface/philosophy up to now. > > * To have Marko Saukko/Sage make a meritocratic claim as interim > Packages Maintainer (better title to be selected), due to extensive > contribution to the Mer Core (see http://review.merproject.org , > All->Merged) > > This would put the advisory board to the following structure: > > * Architect: Carsten Munk > * Nemo Mobile Representative > * Plasma Active Representative > * Technical leads Representative 1: David Greaves > * Technical leads Representative 2: not chosen yet > * Maintainer Representative 1: Marko Saukko > * Maintainer Representative 2: not chosen yet > > First items on the agenda for the new Advisory board would be to: > * Confirm project governance model as official project governance > * Discuss and probably re-confirm meritocratic claims and instate them > in that position officially > * Establish length of advisory board terms, initial proposal is two months > * Establish schedule of advisory board meeting, initial proposal is > once a month. > * Establish if there's any nominations needed for remaining Technical > Lead and Maintainer Representative positions > * Any other business, such as proposed items by project members, > project direction, requirements, needs, nominations, etc > > If anyone has any objections to this model or direction, please > discuss it on this mailing list, else the idea is that the proposal > goes into effect at 31 January 2012, with first Advisory Board meeting > on 1 February 2012. > > BR > Carsten Munk > Mer project founder
