In January, Lukas wrote a collection of things left to do. Later I wrote a tentative release schedule that turned out to be too optimistic. I just updated that document with new dates. Sorry about this.
There are two actually quite cool reasons for the delays. One is that we had two projects at Liip where we had to integrate the CMF into existing projects. It was fun, but we found quite a lot of issues and missing features in Doctrine PHPCR-ODM that we fixed resp. implemented. (The Symfony2 Form component is incredibly powerful, but requires the persistance layer to work very exactly and we did not want any more workarounds and hacks to a achieve functionality.) The other reason is that many other people started using the CMF too. Some found issues that need to be fixed, others even managed to contribute fixes themselves – but which took time to review and comment on. Also, a lot of new features have been built or are currently being built.
One feature I am particularly happy with is that PHPCR-ODM can now cascade persist referrers. This is quite useful for example to embed route and menu editing into the edit form for static content, as shown in the screenshot. (This is already in the ContentBundle and should come into the sandbox with the next update.)
As soon the above 2 client projects have stabilized, Lukas and I plan to focus on cleaning the base layers PHPCR and Jackalope to a point where we can tag release candidates, then bring Doctrine PHPCR-ODM to a state that can be called 1.0. We might have to postpone new features, but try to find all the interface changes and similar things to avoid BC breaks once 1.0 is stable.
Getting things out depends on contributions from the community too. While it is great to get new features, we now need to focus on cleaning up those we already have. On improving the documentation. On investigating bugs. The Release plan links the important missing pieces, if you want to dig into something.
There is the idea for a hackday in May or June. Please contact me or Lukas if you are interested. If we have enough interest, it is much more likely that we actually organize something.
I will present PHPCR at the Symfony Live conference in Paris beginning of April. I will also be at the hackday on Saturday if anybody is interested in meeting me there. Additionally, Thomas and me planned a (very focused) hackday on April 3rd to integrate SonataPagesBundle with PHPCR on the 3rd. If you are interested in helping with that integration, please contact me or Thomas.
This week, we also did a hackday at Liip, with focus on documentating some of those new features people built. I tried to collect what we achieved that day:
Thank you. I look forward to reading it.
Hey David great work with the documentation can we get the code as well for the slideshow block.
hi arthur, slideshow doc is almost there, you can read the current draft at https://github.com/symfony-cmf/symfony-cmf-docs/pull/104
Thanks a lot for the feedback and for caring enough about the CMF to get angry about the documentation ;-)
I think one of the big challenges we have is that those who write documentation already understand how the CMF works. So we really need feedback on where people get stuck.
It is on my agenda to go over the CMF documentation and i will try to streamline it more.
I will try to convert the “Getting started” section more into a “Code First” thing and will ping you when its ready for a review.
For the meantime, there is also the symfony-cmf-devs mailing list and the #symfony-cmf IRC channel where you can ask questions. I am optimistic that we can help you get unstuck.
First things first: I’m very impressed by your efforts on the CMF. I can see that it has MUCH potential.
Despite the fact that I can see the potential and want the effort to succeed, the documentation is just really bad. Not a little bad, but REALLY awful.
I’ve read every piece of Symfony CMF documentation. I’ve read the code for the SimpleCMF and all the CMF bundles. I know what all the pieces are supposed to do. But I still can’t get anything to work right together.
The simplest example of creating a document, attaching a route and a menu item, then displaying the data still eludes me. I’m doing something wrong and I have no idea what it is.
The Doctrine project does a great job of “Code First” documentation. My request to y’all is to put together a full “code first” that covers:
* Create a simple document class.
* Create a simple route class.
* Create a simple menu item class.
(Note: Not the three-in-one thing that SimpleCMF does.)
* Create data fixtures that populate data into the PHPCR using these three classes.
* Create a simple controller and view for the data.
I’m sure there are a few other things that y’all can think of that should go into such a document, but you get my point.
I would LOVE to help write documentation. I’ll test the code in the docs if you want. Whatever help you need, I’ll give you what I can.
But right now I’m pretty much dead in the water, and I know there are many others like me really struggling with this code base.
So please add this to your list of TODOs for a stable release.