20130531 irc meeting

Agenda:

Feature freeze? (dtl)
PHPCR, PhpcrOdm, PHPCRODM, or what? - how should we reference PHPCR-ODM in directory names (dtl)
Testing component - directory structure (dtl)
Best/common format for CHANGELOG.md files? (lj)
Best way to structure documents? (lj)

spend of his time this week on the testing component (see also https://github.com/symfony-cmf/RoutingAutoBundle/pull/23)
submitted a PR to SonataAdminBundle to support setting the translation domain on FieldDescriptions which should allow us to implemnt Admin extensions in CoreBundle using the translation files in CoreBundle
handled the symfony_cmf prefix merge

is in a training and not here
tagged releases of all cmf bundles and phpcr-odm
preparation work to move RoutingBundle Document to Model classes to simplify ORM support.
created a cmf_request_aware tag and compiler pass in CoreBundle https://github.com/symfony-cmf/CoreBundle/pull/37
current menu item voters got merged (forward compatbile with knp menu 2.0) https://github.com/symfony-cmf/MenuBundle/pull/49
http://cmf.davidbu.ch now can filter by milestone (next is fix elasticsearch issues then we can hide not matching projects and filter for things changed in the last 7 days)
i did not sync the PHPCR changes yet, but there definitely are some things to do. https://github.com/phpcr/phpcr/issues/65

helping new team member at Powwownow get up to speed with the CMF-related project
integrating the RoutingBundle into my application, which was previously using a bespoke router
getting close to having a working preview/publish workflow for routes which among other things requires making it possible to dynamically select the document manager (not only in routing but also block etc, see also https://github.com/symfony-cmf/RoutingBundle/pull/99)

timezone handling in Jackalope Doctrine DBAL PR ready, missing a new test in the phpcr api tests and a migration script (https://github.com/jackalope/jackalope-doctrine-dbal/pull/109)
splitting hard/weak reference storage in 2 tables PR and migration steps ready, but needs testing (https://github.com/jackalope/jackalope-doctrine-dbal/pull/75). will improve performance, code readability and future performance improvements using deferred FKs
handled some of the symfony_cmf prefix related merges
updated some release tags to include fixes that were necessary after recent BC breaks
worked on the SimplePager (https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/119)

working on the SonataAdmin group list thing again (https://github.com/symfony-cmf/BlockBundle/issues/50). all the dependency issues are solved i should be making progress.
read a lot about other components like block bundle and we are investigating if the code we have could be of use
needs some help on the SimplePager with translation handling (https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/119)

hoping to look at the JOIN issues (for SearchBundle https://github.com/jackalope/jackalope-doctrine-dbal/issues/119 as well as the failing test for jackrabbit)

feature freeze is denoted by moving the bundle/component to RC phase
feature freeze planned for June 21st (workshop day)
try to get as many bundles to RC phase before then to also enable people to handle multiple bundles
update https://github.com/symfony-cmf/symfony-cmf/wiki/Roadmap with responsibilities (still missing owners!)

agreed to follow https://github.com/symfony-cmf/symfony-cmf/wiki/Change-log-format
Symfony2 core format doesn't fit since we do not squash commits
fazy will update all changelogs accordingly, for jackalope/phpcr odm he will send PRs, for the rest he will just edit

issue is that Doctrine does not use studly caps in Bundle names
sonata follows this, with SonataDoctrinePhpcrAdminBundle being the only exception
we have several class names that use "PHPCR" (though its actually PHPCR ODM)
decision to leave the bundle names, but rename all other classes to studly caps (Phpcr) and including "Odm" where relevant
dantleech will take care of it

blocks as children cause issues with merge/clone due to Jackrabbit bugs (which might get fixed)
blocks as children however make sense, since it allows referencing the block with a relative path ({{ sonata_block_render({ 'name': 'additionalInfoBlock' }) }}) and also because then their "life cycle" on delete etc is linked to the page that uses the block
however for blocks that are supposed to be reused it makes more sense to use ReferenceBlock or absolute paths in the template anyway and store the block independently of the page