eZ Community » Blogs » Community Project Board » Community Project Board meeting...

By

Community Project Board meeting minutes - Dec 5th

Friday 09 December 2011 8:36:58 pm

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

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

Ole Marius excused : sick.

Table round on prev. tasks

Robin

Gaetano & Robin fixed the windows installer. Now working smoothly on Vista & W7.
Action [Nicolas/Robin] : take the "ideal pull-request" task together : Robin was blocked.
 
Fixing a bug or implementing an enhancement :

  • Spot the issue in the issue tracker. If none existing, report one (learn to be proficient with the “search” button)
  • Have a good look at the coding standards: <link to CS>
  • Try to keep pull requests atomic, i.e. use separate pull requests for unrelated fixes such as e.g. improving comments comments and correcting functionality
  • Follow the tutorial <pointer to tutorial>
  • [Optional] Provide a unit test
  • [Optional] For database-related code, please test on all supported platforms (or at least do not introduce mysql specific code). Changes to database schema should be reflected in share/db_schema.dba and also in an upgrade sql script. The DB upgrade scripts need to be placed under update/database/<mysql|postgresql>/<current-ezp-version>/dbupdate-<previous-ezp-version>-to-<current-ezp-version>.sql. If already existing, please simply update it.
  • [Optional] If there are some backward-compatibility issue arising from the changes, mention it in the pull request so that the Engineering team can take care
  • Describe your pull-request in the PR message (can vary from the commit message if multiple commits provided)
  • [Optional] If a functionality was changed and requires modifications in the documentation : provide the changes in the pull-request thread/forum on github.com directly
  • Add a link in the issue tracker to the pull request page

 

Gilles

Gilles delivered a new version of the wireframes : agreed upon by everyone.
Action : Creation of the HTML for the new layout.
Action : test the build script for producing MS WPI starting from the CP 2011.11 build
 
Left :

  • Learning the build procedure.
  • Twitter block on every event, scanning the event's hashtag

 

Gaetano

Action : build the WPI for 2011.11 (if Gilles fails)
Action : automate steps in the existing build process.

Windows installer :
We still want this to be field-tested more before it is advertised to Microsoft.

Windows installer screencast : re-assignment ?

History and dependencies graph:

Ole Marius (through email)
Nicolas

- get a new logo available for docblox homepage
Action : Include eZ Tags in 2011.12

Evangelism

Action [All] do more

New slide sets available (from Nico):
http://www.slideshare.net/jeanvoye/nicolas-pastorino-rest-recommendation-consume-the-right-content-anywhere-ipc11
http://www.slideshare.net/jeanvoye/nicolas-pastorino-the-opensource-roar-in-the-ez-community

gg: it would be a good thing to have a dedicated page on share.ez.no to put links to all available slide sets
nfrp: ok - let’s write is down in the issue tracker
[done: #018833]

Build automation

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

 oms: Discussed, but further discussion needed to figure out how, where to host and how to do this.

Action [Ole Marius/Nicolas] : Need to test-drive the php script replacing the ruby script building the changelog : iso-functional or not ?

Extensions included in the builds

Blog post launched. Waiting for feedback from community.
http://share.ez.no/blogs/community-project-board/taking-the-community-project-one-step-further-bundling-community-extensions

Target: 2011.11. Deadline for the decisions: two weeks before the build. Starting with eztags, possibly up to 3

Action [ALL] :

  • sdk-public@lists.ez.no
  • Twitter (tags : #ezcommunity #ezpublish #opensource #oss #innovation) + aftershocks
  • Google+
  • Skype statuses
  • [done] Main story on the home page of share.ez.no
  • IRC #ezpublish : push it there
  • Link-back from other blogs (gilles, in french ?)

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

oms: (In addition to extensions) We have looked into new approach for bundling packages and extensions, and will investigate this further, e.g. bundled packages above downloaded packages for simplicity.

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 mid-november. Actions resuming on this then.
Help needed :

  • Peer-reviews
  • IDE plug-ins : Eclipse, Vim, Emacs, PHPEdit, PHPStorm, NetBeans, and 10 more... (php world). Holy grail: an online editor ;-)
  • rules for style checker tools

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. Tip : rather start from scratch, KISS.

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

oms: improving visual layout (typography) could also have a positive effect - eg. have more whitespace between the paragraphs

Action [Gilles]: 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 [Nicolas / Ole Marius] : 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.

Versions map between EE / CP

Action [Gaetano]: Create visual timeline mapping builds between Enterprise and Community editions. example : http://www.levenez.com/unix/unix_a4.pdf
Deadline : should be online by next meeting.

Action []: Add visual map on the main Downloads page.
Deadline : once previous task is completed.

Distribution of eZ CP

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

Action [Robin + Ole Marius] :

Action [Gaetano] :

  • 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 :

Action [Gaetano] : update on the feasibility/conditions of bundling eZP along with the Postgresql installer
Deadline : postponed sine die - low priority task

Misc infrastructure advances

  • Action [Nicolas] get a new logo available for docblox homepage
  • Action [Gaetano] : get them to change the logo on the homepage

Next build : 2011.12

Organizational considerations (to be developed next meeting)

Agile organization, issue tracker/PM to set-up (Redmine).

Next meeting

Mon Jan 9, 2012 at 20:00

Proudly Developed with from