This site has been archived. To learn more about our current products Ibexa Content, Ibexa Experience, Ibexa Commerce head over to the Ibexa Developer Portal

eZ Community » Blogs » Community Project Board » eZ Community Board meeting minutes -...


eZ Community Board meeting minutes - November 24, 2015

Saturday 28 November 2015 9:40:39 pm

  • Currently 3 out of 5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Here are the minutes of the latest Community Board meeting, November 24 2015. Our previous minutes can be found here.

Present: Robin, Roland, Bertrand, Greg, André


Open meeting


Minutes: Bertrand possibly going to start a weekly blog, similar to This week in eZ, with a focus on Engineering and technology.

Topics to be added to agenda?

Minutes: n/a

Next meeting

date/time: Wednesday December 16, 21:00 CET.

Governance document, renewal board

Intro: Robin has re-written the draft. Question is, can we publish this, and follow up with board renewal?

Minutes: Roland and André to have a final review, then publish as draft on share (action Robin).


Intro: two questions to discuss:

  • how we will do maintenance for eZ Publish Enterprise 5.x from now on (Roland, André)
  • how we would like to open the reviewer role on Github beyond eZ staff for eZ Platform and eZ Publish community project

Minutes: discussion on reviewers from the community, on GitHub. André: follow Symfony as example. Bertrand: useful to have extra reviewers. Authority on final review would remain with eZ Engineering as they are responsible for code stability and maintenance. (example: ). Remains as a work in progress after open discussion.

Maintenance eZ Enterprise 5.x: eZ support will focus on eZ Platform, communication following soon. André will send a draft to the board mailing list, for review.

Teams page

Intro: with regards to previous discussion on simplifying, what to do with the teams page? (, Roland)

Minutes: Suggestion: move the Teams page underneath the Get involved top menu item or as tab/page on the get involved page itself. Remove outdated information. Re-add teams at a later stage.

Roland: move to This would help an upgrade/migration, and would be more obvious (language).

Proudly Developed with from