Blogs

Everyone is continuing to produce an incredible amount of content for the book, plus rework and update areas that were showing some age. The new set of chapters for developers and people who want to extend CiviCRM is really fantastic. Everyone who has been wanting to extend CiviCRM, but didn't know where to start should be able to dive in. Everyone is increasing their knowledge of CiviCRM, getting ideas for new features and improving existing features.

The following notes were gathered from the CiviCon session on what the community would like to see in CiviCRM 4.0:

* Goals * No new features * Framework switch * Not as major a rewrite as it looks * Don't want to change many of the private APIs * Want to switch away from pear * Test unit coverage * Better API hooks * What users would like to see * Continuous Integration * Hudson - as you submit code runs through suite of unit tests to see what's broken * Better decoupling * Drupal Forms API

It's 5 to midnight and we're just wrapping up. Mr Kurund says that I can't go to bed until I've written this post, so...

Participating in the second book sprint is just as fascinating as it was the first time around, but the dynamic is definitely different. Having a book in place already makes a big difference - there's no panicking that we'll end up with the sections half finished, and it is easier to cover components when a lot of the design decisions have already been made. Having already written sections on the components is especially helpful when covering new components.

Well, it's been done, we chose the translation platform: Transifex. We're fully aware that we did not actually choose a platform that fully supports the ideal situation, but such a platform does not exists. This is more the choice of a promising back-end which we hope we can eventually develop into the ideal situation.

The interesting part in the discussion was finding a balance between the technical and functional interests.