documentation

Big news in Affinity Bridge offices today! The announcement went out on Drupal.org this morning that myself (arianek) and Jennifer Hodgdon (jhodgdon) from Seattle have been appointed by Dries Buytaert as the new Drupal Documentation Co-Leads! 

This has been a long time in the making. It's really exciting to have the work I've been doing recognized, and also have the ability to leverage that work to improve documentation and help build a stronger Docs Team. On top of that, my community spotlight was also posted today, which is incredibly heartwarming.

A few weeks ago, I embarked on my first overseas trip to go to Copenhagen for this year's European DrupalCon. It was my 4th DrupalCon to date, but I've been wanting to attend one of the European ones for a while, as they have a reputation for having a different vibe than the North American ones (and of course so I could finally see some of Europe!)

The Core Dev Summit (+ Code Sprint Day)

Like the last conference in San Francisco, it was prefaced with the Core Developer Summit, which is a full day of presentations, discussions, and code sprinting on the core Drupal platform. The Core Dev Summit is the single day (twice a year at this point), where a good number of the people who work on Drupal core come together to take a step back and discuss in-depth any ideas or concerns. This often leads into some dedicated sprinting on core related issues (as well as some of the most crucial contributed modules).

With Drupal 7 down to 30 critical bugs, and Drupalcon Copenhagen just around the corner, it's only a matter of time before Drupal 7.0 ships. We want to make sure our Drupal 7 documentation is in great shape for this fantastic new release, and the Documentation Team could really use YOUR help getting there!

Last week, Zoe, Dave, and I made our way down to San Francisco for DrupalCon. It was a fantastic week, and even though I knew how many people were attending, I was still stunned by the actual size of the crowd, especially when we were all gathered together for the keynote sessions.

This post was originally posted on my personal blog, but we thought it was worth sharing here.

This one’s all Drupal folks, cause that’s pretty much all I’ve done for the last two and a half weeks. This is what happened when I asked the question, “Is there some reason we don’t just fix it all?” I did not know then what I was getting myself into…

A small inconsistency

It all started in late summer, when I was testing some Drupal 7 core patches for moving fields and image handling into core, and at some point clicked my way into the Help pages. There was a blatant typo on the Node module help, and then a change in language that needed to be made, so on August 1st, 2009 I created an issue for it.

As of today, we are now only two weeks from the Drupal 7 code freeze. When we hit Sept. 1, from then on in, only bug fixes will be worked on (no new features), as everyone focuses on generally improving the code and how it functions. Because of the deadline coming up, there is a lot of focus on getting new patches committed to HEAD before Sept. 1, and to get the patches committed, they need to be reviewed by the community and given a stamp of approval. As of 11:41am PST today, the D7 queue contains: