Drupal workshop and coding

doh, i'm gonna miss out on all the fun, that's gonna be moving weekend for me!

Can't wait for this!! I'll be there with bells on! :)

...shortly after.

P

m

but likely I will be up to my eyeballs in packing and moving. If by some miracle I'm free and in town, I will SO be there!
Otherwise, I will be thinking of you all.

Djun

Unfortunately, cannot make it. : (

Whenever I've done sprints like this, there's usually a fairly broad audience who shows up: some hardcore developers who've been involved in Drupal for a long time cough chx cough ;), some front-end designers/developers, some technical authors, and some new to Drupal with no previous experience.

So here's a brain-dump on some possible "teams" we could have at the sprint and some things they could work on:

Team Critical Bug Smash!
Attack the list of remaining critical issues, particularly anything identified as as beta-blockers, via whatever means necessary. A lot of these do require a fair bit of Drupal experience, but I'm sure we can find one or two for less experienced folks to participate in, too.

Team Upgrade Path!
We want to test the living crap out of the upgrade path in preparation of the first beta release of Drupal 7. To help with this, we need both developers who can be on hand to fix bugs, but also end users and site builders who could practice the upgrade path on a variety of different types of sites and see what breaks. The issues we know about are under the D7 upgrade path tag.

Team Bartik!
For designers or themers in the room, a new default core theme, called Bartik, went into Drupal 7 only a couple weeks ago. There are still some clean-up tasks left to do, under the Bartik queue. In #drupal-contribute on IRC, there is usually at least one of the Bartik maintainers available who could help identify priority tasks and help new contributors work through any issues.

Team Documentation!
There are a number of API documentation fixes as well as user interface text bugs left to go. The former requires some development chops, but the latter is a great place for "newbies" to help with, since many of these are help strings directed at users new to Drupal!

Team Usability/Accessibility!
There are a number of usability and accessibility remaining. If you fancy yourself experienced in either of these areas, this is a great place to help out.

Team Testers!
Lots of issues are tagged as needs tests, so if you fancy yourself good with automated tests (or want to learn!), this is a great place to pitch in.

That should hopefully get us started. :) Obviously, if you have a "pet" issue don't let this list box you in, and I'm sure chx will have lots of thoughts of specific issues to task people with as well once he gets there.

That's 333 Seymour St, unit 1100, not 1100 Seymour St, unit 333. :D

</BC noob>

Just wanted to say a huge thanks to a few people for a wonderful day on Saturday.

1. Audrey - you did a fantastic job organizing this, thank you.
2. Chris Ng - You helped too ;) Great presentation
3. Yi - Really information presentation
4. Angie - It was wonderful to meet you. Your patience and knowledge is admirable.
5. Károly - Happy birthday again and thanks for your anecdotal tales on the Drupal 7 issues queue
6. FCV - Thanks for sharing your awesome office space
7. Everyone else who attended, it was great to meet you.

It's great to be surrounded by such smart people. I'm going to solve some issues this week if it kills me.

Col.

Hi all,

I put together a little blog post on what I learned at the sprint/workshop if anyone is interested.

http://blog.raisedeyebrow.com/2010/08/tackling-the-drupal-7-issue-queue/

Col.