Drupal core development workflow

So it seems Larry Garfield (Crell) and me nailed a serious issue in Jimmy Berry's (boombatower) post about Drupal core development, where even chx's idea of sub-system maintainers not being able/allowed to commit their own patches would not help, because the lack of communication and coordination remains. In fact, adding more people with commit access would vastly increase the problem, and now that I think about it, this is exactly what Dries mentioned to me in person when I discussed more core committers with him in Paris.

Any Drupal developers out there?

This one is going to be short.

If you want to make Drupal 7 any sense for developers, themers, and users, then you really want to spend a fair amount of time on issues tagged with "API clean-up":

http://drupal.org/project/issues/search/drupal?issue_tags=API%20clean-up

In case you think you don't have time, then please prepare for not complaining later. Thanks.

Challenges for Drupal

DrupalCon Paris is over. Countless of badly needed discussions and brainstormings happened, and we have a couple of weeks to finalize and clean up all of the new APIs and features we added to Drupal 7.

Drupal 7 is not ready yet

So here we are. The feature-set and API of Drupal 7 is about to freeze. It contains many - actually plenty - of awesome and noteworthy improvements and new features. But those will be covered elsewhere and I don't want to talk about that.

Hello world!

As you may have experienced on your own, when being involved in consulting and development business, it can be very hard to find the time to work on your own presentation, which - of course - totally must include your great ideas and showcase your own quality standards... ;)