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...

By

Community Project Board meeting minutes - January 6

Friday 10 January 2014 8:13:18 am

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

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

#42 Jan. 6th 20:00 CEST

Present: Nicolas, André, Gilles, Joe, Greg, Robin

 

Catch-up open tasks

4 vs. 5 spreadsheet

Jira issue: CPB-5 

 

Old Update:

Discussion with Andre + Jérôme + Gilles. All agreeing in principle on furthering this spreadsheet.

Idea: extend the discussion to other community members, via a face-to-face meetup OR virtual meetings / hang-outs.

 

Gilles: conclude with Andre about the opportunity or not the let the engineering spend more time to fill the spreadsheet. Option 2 : do it with jerome outside the job time. In all case, a meetup is expected @ Lyon to extend the topic with other community members, helps to focus on important features to explain

 

Current update:

AR: Synced with Roland, we can after review and update to make it public, sharing with board now to be able to discuss it:

 

Gilles: it is also important for partners to be able to tell which extensions are exactly supported

 

Options:

  1. Have the confluence page as the reference doc on comparison, and link (at the bottom of the page) towards:

The confluence page is maintained by eZ Systems (Engineering/PM/Doc)

The spreadsheet will be maintained by …, with comments for improvement by community driven via a forum on share.ez.no

  1. Have only the confluence page

 

Decision:

Option 1 is chosen, with following provisions:

  • Make clear in the link to the spreadsheet that it is provided "as is" and not contractual
  • Add large disclaimer in the spreadsheet: "Last update on XXXXX",

Action[Andre]: Quick pass on the spreadsheet (includes the disclaimer) and add the links.

Action[Andre]: Remind Board in one week, giving a few more days for review of the confluence page

Action[Andre/Nicolas] Plan a blog-post (via Content Factory) about this on share.ez.no (Community Xmas gift!)

 

API doc page

Action [Gilles, Andre, Gaetano]: check out the status of documentation and come back with a suggestion on which tools to keep or drop

 

Update:

Still pending

 

2014.01 build

Update:

Not started yet.

 

Frequency of CP build

Proposal to go for every second month instead of every month was voted with unanimity in favor a while ago.

 

Action [Nicolas/Andre]: prepare a short blog post to explain this.

2013.11 would be the start of this new pace. Final round of internal feedback (eZ) appreciated before going public.

 

Update:

Still pending.

 

Mentoring / Diff Squad (was: “Robin”)

Ref CPB-4 (Grow the eZ Diff Squad)

 

Update:

Sept. 30th: Robin analyzed the contribution and reviewing patterns.

Nov. 4th: e-mail sent to list on Oct 15th, waiting for an answer. Andre to get back to Robin on this point.

 

Action[Robin/Andre][done]: Robin taking the next steps in getting the Diff Squad back on board.

 

Update:

The contribution patterns on the new stack are changing, being very different from the ones on legacy. The Diff Squad's mission is thus also changing, and the board decides to involved them in crafting their new role.

 

Action[Robin/Andre]: Reach-out to the team to update them and involve them.

 

References Sites catalog (was: “Gilles”)

(Moved to next meeting, 12/2/13)

 

Discussion: see previous minutes

 

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.

 

Actions:

Action [Nicolas]: Add an issue in the tracker  

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

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

 

Update:

Nicolas still to respond to Greg + Joe create the issue (wireframes) in the tracker.

 

New topics in this meeting

Board renewal. Ref last year's announcements:

 

Jobeet Tutorial

Gilles mentioning that they consider crafting the Jobeet tutorial for eZ Publish 5. Collaboration with eZ and the eZ Community should happen. New documentation recruit at eZ could be the collaboration agent for this project.

@Kaliop could lead the development

Ref: http://symfony.com/legacy/doc/jobeet/1_4/en/01?orm=Propel

Next meeting

Jan 27th - 20:00 CET

Adding QA reports to code builds

gg: one way to boost community participation would be to give free access to a "build server" to each user in the ez community. Using the ezextensionbuilder extension it is possible to run QA checks and reports on any Legacy extension.

Step 1: enable the reports on the code of eZ repositories, as part of the daily-build task

Step 2: allow users of projects.ez.no to configure their github projects to be able to send a ping to the “ez build server” to get reports generated for them

note by Andre: eZ Engineering is moving towards similar solution, but based on pure usage of external services (travis, coveralls, scrutinizer-ci, ...). It might be enough to give users such templates

Gittip

Gilles: could we introduce something like https://www.gittip.com to the eZ community?

André: Also interested to look at the organization here, not for eZ devs, but for community devs. It would be possible to get eZ to put some money into this, and I guess many partners would be interested as well if they can have a say in what is developed/direction/feedback.

Gaetano: we just need to make sure the dynamics are better than what was attempted already by eZ Systems a few years ago

Proudly Developed with from