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 » Community Project Board meeting...


Community Project Board meeting minutes - August 26th

Tuesday 27 August 2013 7:48:36 pm

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

Here are the minutes of the 38th Community Project Board meeting. Our previous minutes can be found here.


#38 Aug. 26th, 20:00 CEST

Present: Joe, Nico, Gilles, Greg, Robin

This meeting

Re-organization of team-work


Topic: management of tasks

  • users are not supposed to assign tasks to others, but only to volunteer to take responsibility for tasks
  • it is desirable to be able to involve community users (non-CPB), in case anyone shows-up / volunteers to participate in some tasks
  • focus is not given to task deadline; if current sprint-based interface turns out to be too cumbersome,

Catch-up open tasks

4 vs. 5 spreadsheet

Jira issue: CPB-5 

Update: issue blocked


Action[Andre]: André coordinating a short meeting (~30mins) between eZ Engineering, Gilles and other community members (including CPB members) to go through the spreadsheet.


Update: availabilities on both Engineering's and Gilles' sides were very busy --> not done yet.

Action[Nicolas]: speak with Andre to take-over the task. Idea: quick prep call, and then Gilles can move to Lyon for a physical meeting with the guys.


API doc page

New design by Joe available at, open to pull-requests.

Jira issue: CPB-8


Idea: make a php version out of that page which self-updates, to avoid maintenance


Idea: integrate the feature comparison spreadsheet right in to this page


Next possible steps: make it a template.


Gilles: linking back to downloads for both CP and Enterprise versions would make it easier for users (a notice for Enterprise versions that only partners can get it)


Nico: due to composer usage, we might have to change naming scheme for CP versions, eg: 2013.06 instead of 2013.6


Decision: publish current version of Joe’s page (votes: 5/5); refine further and integrate with the page maintained by eZ Engineering later (there could be at least some branding added to it)



[gg]: publish current  version

[gg]: give to Joe list of all directories with sources

[Joe]: make the page dynamic

[??]: generate API docs for CP 2013.5 and EE 5.1



  • docs for EE5.1, 2013.5 and 2013.6 in the process of being generated
  • simplified shell scripts developed to make generation of docs for specific releases a simple process
  • previous “preview” homepage by gg currently online, as short-lived replacement for Joe’s version
  • Source code added again in Doxygen (only for Trunk version). Example: 
  • available
  • other actions being worked on


Available options:

  1. Keep two separate home-pages
  2. Pick one, ditch the other,
  3. Mix the two into one (keep the hostname on top of => set up a new git repo for easy collab


Decision: option 3



  • [Andre] Create GIT repository under ezsystems organization
  • [Gaetano] Push existing code + directory specs to the repo
  • [Joe] Rework the page a bit.



Joe was not notified of access to the repo.


Action[Gaetano]: (CPB-13) to Joe and notify him.

2013.07 build

[done] A few roadblocks prevented Sylvain from finalizing the build last week. Tentative: this week.

Opening-up the JIRA tracker to the public

Decision: Board needs to use it a bit for a few weeks to be sure to stick to this choice, and then open it up.



Picking up on CPB-4, will ask on our mailing list for ideas/input for nurturing and growth of the Diff Squad.


Update: Robin picking this one in the near future.



Having a catalogue of sites built on Community version would be a boon


[gg] hand-curated catalogs take a lot of time

[gg] inviting partners to submit to this is easy, but sites managed by customers will most likely not submit by themselves as they see little value / have little time

[Joe] taking existing info from partner data and laying it out on a new page could be a good 1st step

Next step: make it a task :-)


Update: (discussions on this meeting):

  • Missing a "positioning statement" (telling what eZ Publish is - ex: Symfony description). The place where the positioning statement, we could lead to a very visual references page (ex: Varnish, Blend).
  • ( not found in


Decision: Principle decision to engage in:

  • Creating a place (tbd) where we present what eZ Publish is to the community, in a very synthetic way,
  • Creating a logo wall ( / portfolio / "who relies on" / ) showcase page where partners can submit sites built using eZ Publish. Edge-case: great brands known to use eZ Publish: contacted by eZ (Online Marketing team) to ask for authorization to publicize.
  • Optional: these new pages could be translated.



Action[Joe]: submit a first wireframe for inspiration to the board.

Action[Greg/Nicolas]: Come-up with a succinct way to describe eZ Publish


Next meeting

Monday Sept 30th 20:00 CEST

Proudly Developed with from