This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit

eZ Community » Blogs » Community Project Board » eZ Community Board meeting, May 3, 2017


eZ Community Board meeting, May 3, 2017

Friday 05 May 2017 7:13:21 pm

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

Here are the minutes of the latest Community Board meeting,  May 3, 2017. Our previous minutes can be found here.

Present: Robin, André Rømcke, Sébastien, Ivo, Donat, Sylvain (Excused: Jani, Bertrand)


Open meeting


  • Donat all setup with access to mailing list, Google docs and Slack channel

Topics to be added to agenda?

  • no

Next meeting

  • Wednesday May 17, 17:00 CET (Amsterdam/Paris)

1 - eZ Platform - Legacy

Status:  Question if Legacy Bridge would be supported on eZ Platform V1, or also on V2. Invite André Römcke for the next meeting to discuss this topic.

Robin checked with Roland, Bertrand should be up to date on this as well. Roland indicates v2 should be supported also.

Minutes: technically it is possible according to André, but with V2 breaking changes will be introduced such as database changes. This could be solved with taking out the legacy storage engine and have this maintained by the community.

Ivo and Sebastien agree this could be a viable solution for legacy projects. Donat highlights the main question why we need LegacyBridge; have a back-end UI.

Ivo mentions the Admin UI (by Netgen), in regards to open sourcing and as option. Ivo also mentions the ezpublish-legacy repo. This repository would need tagging. Netgen currently forked this repo, to add these required tags.

Suggestion is that eZ Platform V1 would support LegacyBridge and legacy storage engine and would continue to do so for roughly 6 months after eZ Platform V2 is introduced (with major changes such as PHP7, Symfony 3 etc).

André also mentions that having the above mentioned solution would also be possible on eZ Platform V2, depending on the needs by the partners and community.

Next steps: 1, blog post to the community, what do they need in a legacy solution? 2, process feedback and 3, align with eZ Systems / Roland (Epic already open for support LegacyBridge).

2 - Status/improvement

Status: Donat; specific to Slack, which is closed. Educate community members where to put questions etc to preserve knowledge. Ivo; decide on using a forum and/or Q&A. Ownership of content on stack overflow? Bertrand notes you can query Stackoverflow: Also referred to by Bertrand in the chat: (this relates to a FAQ / Q&A).

Robin checked with Roland who prefers to run our own ‘forum’ instead of stack overflow due to lack of branding.

Minutes: Robin to discuss with Sylvain what is possible on We leave as legacy, and extend with a forum if possible.

3 - On-boarding new community members

Status: for next meeting

Proudly Developed with from