I've seen some Drupal module developers out there have a lot of trepidation about moving to Drupal 8, most often via hearsay from others or via occasionally dipping in to look around and being spooked by newfangeldy stuff like namespaces, object-oriented code, and weird directory structures.
As Gábor pointed out, now's the time to help make Drupal 8 more unified and user/developer friendly. A great way to do that is try porting your modules, now, while there's still time to fix the APIs before code freeze.
But wait, there's more! ;)
The Spark distribution is a Drupal 7 distribution which aims to prototype cutting-edge authoring experience improvements that we hope to propose for inclusion in Drupal 8 core, announced back in May. Please download the latest release and check it out, and give us lots of feedback! (And/or patches! ;))
Greetings, Drupal Planet!
Here are the slides from my DrupalCamp Vancouver "hook_future_alter()" talk. This outlines the major changes currently in development for Drupal 8, how Drupal 8 will impact end users, site builders, designers, and developers, and how to jump in and help!
Here are some notes from the Drupal 8 status update talk that Dries and I gave today to the Acquia team, since this seemed like useful info for the community to know as well. :) It covers both process changes for addressing previous issues that arose in Drupal 7, as well as a status update on Drupal 8 progress to-date. This could be useful to folks who have been wondering where all of the various Drupal 8 status updates fit into the "bigger" picture.
Please comment here if I left anything out, or messed up anything.
Last month, I started my new job in Acquia's Office of the CTO. I posted my to-do list last month of a given week's worth of work, to try and provide some insight as to what I'm working on. Since that probably reads as chicken-scratch to you (my handwriting tends to be one-way encryption ;)), here are some of the highlights: