Wouter de Jong

@ElectricMaxxx well, we can support both (decision is made using voters, isn't it?). This would result in the following decision flow for instance: 

Btw, I'm planning on restructuring the sandbox to put all feature demo's in under one `Feature` page. The extra benefit is that it would make the hierarchy a lot complexer...

I'm -1 on creating such a package. It'll contain a lot of completely unrelated interfaces, just because we want to extract the interfaces. There is nothing wrong with installing a...

> just to get one or two interfaces, they depend on a full bundle. They depend on a full bundle, because they use the features of the bundle. They do...

Actually, I think we can solve this problem quite easily by going back to our original idea: [Base and Standard Implementations](http://symfony.com/doc/current/cmf/contributing/bundles.html#base-and-standard-implementations): > Bundles should offer ready-to-use **and** fully integrated implementations...

You can also ask yourself why a bundle should depend on the FrameworkBundle. Nothing prevents you from using the code without that requirement.

I don’t think everything in Symfony CMF is sf related. Over soms time, we have a couple of completely coupled components. Symfony CMF is just a name for a group...

> Method names: $user = UserFactory::new()->create()->object() is unfortunate. The ->object() would be removed by removing the Proxy (above) but $user = UserFactory::new()->create() is still confusing... See #111 for a proposal...

@nikophil the library is written based on `doctrine/persistence` (with some specific features requiring `doctrine/orm`). So there is a theoretical chance that this bundle supports `doctrine/odm` already (but afaik, it has...

> @wouterj, what do you think about this? There is now no longer a way to access story state items without loading the story. Do you think this is a...