Community Project Board meeting minutes - Oct. 3rd

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

Event planner

To finish : 

• Nico : 2nd form edition part (half way)
• Gilles (+1 week) : Right side block (not the ezflow one, but the full view template one)
• Gilles (+1 week) : joined.in connection (half way... easy to finish)
• Nicolas : RSS feed for events + push to Twitter on dedicated twitter account.
• Gilles/Nicolas : screencast of how this was built, and how it works.

 
Thanks to Steven for delivering the YQL part.
 
Tasks for the second round of development (after launch) :
Gilles : New eZ Flow block for the home-page + right-column block for other pages
Gilles : Twitter block on the event full view
 

Evangelism

Action [Nicolas] : do more
http://share.ez.no/blogs/nicolas-pastorino/continuous-improvement-of-the-ez-community-through-cutting-edge-research-results-of-the-interviews-round

Build automation

Feedback from Github event in Oslo (Ole Marius) :

• They took into account our need for extended pull-requests,
• "Auto-CLA" checkbox : probably won't happen anytime soon.

 
The eZ Publish version numbers in ezsite_data are not updated today for Community Project, we need to make this into the build procedure.
 
Action [Ole Marius/Nicolas] : Discuss the feasibility of creating an CI/Build repository, dedicated to Community Project + tagging of builds on github.
 
Action [Ole Marius/Nicolas] : Need to test-drive the php script replacing the ruby script building the changelod : iso-functional or not ?

Extensions included in the builds

1st topic: we need to package, separately, the extensions made available in the build.

2nd topic: extensions that are not part of installation tarball but gotten via packages at setup wizard time: currently the version that is installed of these is still the one from Enterprise 4.5 version, so we’re not testing new code

3rd topic: inclusion of extensions from the community (see Ivo’s request to bundle eztags)

• long term, eZP should be able to allow one-click ext. install from eZ/community repos
• middle term, the setup wizard should allow more install choices
• short term: some community extensions could simply be bundled

Sample list of candidates: ezclasslist, eztags, fezmetadata, sitemap …etc (feed back by the community wanted for finalizing this).
If the board thinks an extension is not yet very mature, the board can give suggestions on how it can be improved. Example : the author of fezmetadata would be happy to enhance it.

Take care about security problems: if any are known, either someone should have write access to extension cvs, or we should be ready to drop it in next build.

Another long-term topic: deprecating bundled extensions when better ones appear / they are not updated / useful anymore

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

Action [Gaetano] : Blog post about “we want to include some extensions - top 3” - not yet integration in roadmap / voting systems. Target: 2011.11. Deadline for the decisions: two weeks before the build. Starting with eztags, possibly up to 3. Credit Ivo for triggering the discussion.

Coding standards

RFC in progress, a few more weeks before final publication. 15 comments so far on the RFC. (http://share.ez.no/blogs/bertrand-dunogier/the-ez-coding-standards-need-you)

Note : this won't be finalized until end of 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 : http://share.ez.no/learn/ez-publish/how-to-contribute-to-ez-publish-using-git/(page)/5
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 : https://github.com/oms/testingrepo/wiki/Contributing

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 : https://github.com/oms/testingrepo/wiki/Contributing
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.
Deadline : Nico to check with Andrew.

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).
Deadline : postponed next meeting.

Versions map between EE / CP

Action [Nicolas]: Create visual timeline mapping builds between Enterprise and Community editions. example : http://www.levenez.com/unix/unix_a4.pdf
Deadline : postponed next meeting.

Action [Nicolas]: Add visual map on the main Downloads page.
Deadline : postponed next meeting.

Distribution of eZ CP

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

Microsoft Web installer : version 2011.9 not packaged as WPI so far, since little feedback gotten to blog posts and twitter messages (see http://share.ez.no/blogs/community-project-board/a-call-for-testers-ez-publish-now-available-in-a-windows-platform-installer-package)

Robin actually tested it on a vista machine, found some quirks (minor?)

Action [Robin] :

• test on windows 7, report findings and details of platforms used

Action [Gaetano] :

• Make a screencast : "As a windows user knowing eZ Publish, how can i use Web Matrix ?"
• Update build checklist to include wpi instructions

Next steps : after more feedback from the eZ Community :

• Have that distributed on the Web Matrix platform (http://www.microsoft.com/web/webmatrix/),
• Have someone form the Board keep an eye on the forum there.

Misc infrastructure advances

• An account has been provided for the cpb members. One piwik installation holds access stats for both share.ez.no and pubsvn.ez.no
• eZ Publish is now listed on docblox homepage as user of that tool

Next build : 2011.10

20th of October, at a time that suits Gilles. Gilles leads, Nicolas or Gaetano help. Share

Next meeting

Mon. Oct. 24th 20:00 GMT+2 CET

Proposed list of topics:

• updates to pubsvn server
• tool for managing tasks of the cpb. Glles proposes Redmine
• management of topics for cpb meetings
• cpb workflows: discussing things via mail in between meetings (ie: during rest of the month) to keep meetings short and to the point
• cpb workflows: involving more community members in task execution to speed up execution (subcontracting)
• managing accounts on board tools/sites: a community one or per-person accounts?