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 - Sept. 8th

Monday 12 September 2011 12:32:44 pm

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

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

Event planner

Meeting took place today (8/9/2011) on Skype (Nicolas, Gilles, Steven, Paul). YQL-part is next. Template operator and YQL is work in progress. UI, YQL and template operator to be joined in about a week from know. eZ Flow block and Twitter block needs to be added on the events page once code is on SVN.
Tasks first round:
Steven : Logged-in features : request a new event 
Steven : YQL connector (template operator) + edition interface.
Nicolas : have a proper guidance text.
Nicolas : RSS feed for events + push to Twitter on dedicated twitter account.
Done :
content classes, gmaps integration, templating is done

Tasks for the second round of development (after launch) :
Paul : addition of the back-end
Gilles : New eZ Flow block for the home-page + right-column block for other pages
Gilles : Twitter block on the event full view

Action [Gilles/Nicolas/Robin] : test-drive the consolidated solution (once Steven has dropped his code).


Action [Nicolas] : do more
Soon : Publication of the results of the survey + interviews done by Paul di Gangi, Robin Teigland and team.

Build automation

We should consider tagging the builds on github.

Ole Marius will attend an event in Oslo from Github, he will share ideas/best practice on pull requests.

The eZ Publish version numbers in ezsite_data are not updated today for Community Project, we need to make this into the build procedure.

We need to package, separately, the extensions made available in the build.

Briefly mentioned, new commit styles by github:

Interesting community suggestion:

Action [Ole Marius/Nicolas] : Discuss the feasibility of creating an CI/Build repository, dedicated to Community Project.

Action [Gaetano/Gilles][for 2011.9] :

  • Test these instructions for the next build (2011.9), and adjust them based on their external feedback. Gilles will jump in when available.
  • Build-in updated ezsite_data version values.

Action [Ole Marius/Nicolas] : knowledge transfer on how the extensions are built today using the current CI infrastructure

Coding standards

RFC in progress, a few more weeks before final publication. 15 comments so far on the RFC. (

Note : this won't be finalized until early october. Actions resuming on this then.

Ideal pull request

Pull-requests fixing more than 1 issue at a time can use the commit message format described here :
For larger pull-requests, join an explanation. Possible ways of documenting the feature :

  • in the pull-request description. The review team can take the liberty (with upfront request) to enhance the description in the pull-request.
  • have a dedicated feature-description file under doc/features/??/<feature-name>.txt

Ole Marius prepared a wiki page, based on the tutorial's contents. The idea is to strip it down to a series of command-lines examples. On top, the "ideal pull-request" description can be added there. Example :

Issue when writing the release notes : how can we present the new things on a catchy way ?
The "ideal pull request" should contain a description of any mid-size to large feature, helping write cool release notes.

Action [Nicolas/Robin] : Write the ideal pull-request document, publish it, and link it from the get-involved/develop page. Inspiration text :
Final location : wiki on eZ Publish's github repository.

Action [Robin {helped by Nicolas}] : Need to update the tutorial about git/github (or provide  a new one): explain how to install eZ Publish from a Github fork.

Mission statement

Action [Andrew]: Sketch out revised layout for Develop page to draw more attention to the development resources.

Open eZ Doc

Geir Arne is ok on the principle. Tagging the doc contents per version should be working (PHP example. Open-doc idea accepted too by Geir Arne. Need for a dev resource to make this happen.

Action [Ole Marius/Nicolas] : ask Geir Arne to produce his view on these (wireframes, functional description, concrete) two points : tagging + user generated content.
Deadline : loose, Geir Arne on holiday.

Action [Gilles] : Write short description of the main features of the solution currently built, in-house, for knowledge management. The content currently created can also be of interest (screencasts, etc).

Versions map between EE / CP

Action [Nicolas]: Create visual timeline mapping builds between Enterprise and Community editions.
example :

Action [Nicolas]: Add visual map on the main Downloads page.

Distribution of eZ CP

Gaetano investigated this. The Postgresql seem to have a channel to distribute "any" software. Action [Gaetano] : update on the feasibility/conditions
Deadline : next meeting.

Microsoft Web installer :
Updated in staller to the latest version of eZ Publish CP (upped rquirements to 5.3).
Blogged about it at No answer so far

Action [Robin] : test-drive this before the next meeting.

Action [Gaetano] : sustain the buzz within the eZ Community to gather more feedback on this. Make a screencast : "As a windows user knowing eZ Publish, how can i use Web Matrix ?"

Next steps : after more feedback from the eZ Community :

Next build : 2011.9

15th of September.

Next meeting

Oct. 3rd, 20:00 GMT+2 CEST

Proudly Developed with from