Community Project Board meeting minutes - March 3rd

Summary

Decisions & actions made

Governance doc

• Gaetano : rephrasing both points mentioned in the Governance document (clarification)

External com

• Nicolas : Publish last meeting's minutes + this meeting's
• Andrew : Announce choice for 2-ways com (blog) + rationale, on our blog : http://share.ez.no/blogs/community-project-board
• Robin : contact form on share.ez.no : sync with share.ez.no team
• Everyone : Send to the ML the list of events you will be participating to, in which presenting/mentioning the Community Project is possible

Internal com

• Gilles & Nicolas : Webex test.

Release policy

• Keep open until March 24th. Update once inbetween with concrete feedback.
• Everyone : nurture the discussion.
• Gilles, Ole Marius : find someone to design/integrate a new front page block (replacing "Forum addicts of the the month" block. ).

Participation Model

• Ole Marius : integrate the remarks about CLA & documentation in it
• Nicolas : Visual of the slide & dice (as will be implemeted on share.ez.no, useful for understanding the RFC)

Next meeting date & time

March 24th, 2011, 17:00 GMT+1

Governance Document

Remarks from Gaetano :

• The renewal conditions & process are not very clear (under "Recruitment" header). To be rephrased, and properly explained
• Under "Responsibilities" : rephrase the first bullet-point, make clear that this concerns future Board members.

Product Direction

Release policy

Examination of the feedback received on the RFC so far.
Decision :

• Keep the RFC open for 3 more weeks (deadline : March 24th )
• Make it prominent on the homepage (replacing "Forum addicts of the the month" block. ).
• Participate to the feedback discussion. This could also trigger internal discussions. Update the presented RFC after concrete feedback has been gathered, if applicable.

Participation

Participation Model

Last feedback from everyone (Gaetano had some, Ole Marius will provide feedback during the meeting)
Ole Marius :

• Slice 'n dice the document in to digestible bits. Separate into several docs ?
• Update about the CLA + guidelines for how this applies
• GIT Tutorial : must-have, as a compliment to this doc
• Contributions to the Documentation : Geir Arne (eZ Doc-man ) is really open to this. Could be mentioned in the doc. Need for a light infrastructure to channel doc contributions.

Gaetano :

• Too long. Try to have a short introduction, and split-it up

Tools for the Board

Public, 2-ways channel

Deliverable :
Announce to the community, with a rationale for that. If negative reaction to this, we reconsider the choice. Topic : "No public ML but regular communication on RFCs (and not final decisions) through the blog"

Rationale private communication

(to be reconsidered/rephrased)
In an open source project, the default is to conduct discussions in open,
public channels. The private channel will only be used for exception cases to
this.
The cases we foresee, which will require discussions outside of the public eye,
are cases that:

• Deal with personal matters, of persons within, or related to the project.
• Communication regarding security issues, yet to be published.
• Communication with external persons who have requested non-public

Private entry-point to the board

For the persons not willing to publicly get in touch with Board members on the 2-ways channel mentioned above.
Deliverable : contact form on share.ez.no, clearly stating that other means are preferred (forums, etc.)

Internal, private

Webex ?
Action : test between Gilles & Nicolas, about sound issues.

External Communication on Cty Project

• List of events (including the ones where eZ is participating)
• Required resources (ppt templates, slidedecks, data & figures)
• Profiles update : mention membership to the eZComProj Board