Sam Dean from OStatic sent me some questions via e-mail last week. Their website's mission statement reads:
Our goal is to increase the adoption of Open Source Software by helping users find viable projects and applications that fulfill specific needs, evaluate them against available alternatives and collaborate with their network of trusted peers.
I would love to see a series of blog posts from Drupal developers on patch review strategies they employ, so we can share some tips and tricks and ramp up our collective review IQs. I'll start it off with mine. I call it "The 6-Pass Patch Review" (wittier names welcome! ;))
Back at Drupalcon Szeged, I sat down with Michelle Pace from The Next Women to rave all about Drupal and the Drupal community for an hour or so. :) It was really interesting talking to her about her first impressions at Drupalcon and most of our discussions centered around what makes an open source community tick.
You can check out her write-up over at Sourcing Angie Byron.
Thanks, Michelle!
read more
As a standards zealot, one of the things I'd personally love to see happen in Drupal 7 is the eradication of table-based layouts. I'm giving stink-eye directly at you, Pushbutton, Chameleon, and Bluemarine. These themes are a strange abberation from the Drupal project's otherwise very meticulous attention to detail regarding web standards, and I'm quite positive that they directly contribute to the Drupal project's ongoing struggles to attract and retain visual designers.
Today was the first day of my vacation (linking to Wikipedia in case you, like me, were not sure what this word meant) so naturally a bunch of us spent the entire day in #drupal slashing through bugs and features in preparation of DRUPAL-7-0-UNSTABLE-2 which should be tagged tomorrow, with lots of nice goodies. :)
Tomorrow and Saturday, I'm headed off to Drupalcamp Montréal, our first such event in the fair city.
Like all such events, we won't really know what the schedule is until tomorrow morning, but here are the sessions I'm planning on giving, in relative order of geekiness:
As of this writing, there are over 5,600 active issues in the Drupal core queue. About half of those are listed in the 2,650 active issues for Drupal 7. And the "patch queue for Drupal 7 -- those issues that have at least *some* code to fix them in various stages of completion -- clocks in at 1,040 issues.
Here's another tip for those who are looking for more reviews of their patches and faster commits: describe what the heck your patch does! :)
A simple enough premise, and It sounds obvious, right? But you'd be surprised how few patches are accompanied by a good, solid list of changes.
I was recently named Geek of the Week by Maria "Ubergeeke" Webster of .51 - GeekSpace for Women.
I met Maria at OSCON this year, and she is hilarious, friendly, awesome, and possibly an even bigger geek than I am (I know, right? I didn't think it was possible either! ;)).
Patch authors are always looking for a strategies to help shorten the length of time it takes to go from creating a patch to seeing it reviewed to getting it committed. Here's a quick tip for any patches that involve a UI change: Submit a screen shot with your patch!
