A few months ago I ran for, and won, a seat on the Drupal Association (DA) Board as an At-Large Director. I'd like to share my journey with everyone, both to provide another look into the work that the board does, and to understand what it's like to be a new board member. I've now attended two board meetings (April and May) and taken part in my first board retreat, the weekend before DrupalCon LA. There's a lot going on, so I'll break this up into several posts.
Web and Tech
Wow. That was the first thing I said when I found out that I had been elected to the Drupal Association Board. The next thought was how much trust the Drupal community has put in me. I'm honored to be elected. Thank you. I also want to thank my fellow nominees, who all stepped forward with passion and great ideas. It was a joy to be on the "meet the candidate" discussions with them, and I would have been thrilled had one of them been elected in my place.
The Drupal Association (DA) At-large Board seat is now open for voting. The polls will remain open through March 20th. (Note: I couldn't find this written down, but I believe this means until 11:59pm UTC on the the 20th.) To be eligible to vote, you need to have a Drupal.org account already, and to have logged into it at least once in the last year.
A week ago I stepped up and nominated myself for the Drupal Association (DA) At-large Board position. This wasn't a decision I made lightly, and I'm very excited to see so many other people have nominated themselves as well. There are 24 people up for the vote, which bodes well for a strong community. I think a lot of people in the Drupal community don't actually understand the board and this election process.
So rocktreesky is finally running on Drupal 7. I upgraded the site a few weeks ago and thought I'd share my experience. This is a very simple blog site so my upgrade process was fairly simple and easier than it would be for almost any other site out there, although the overall approach is going to be the same with most sites. I got the site upgraded in a weekend, but even as stripped down as this site is, I had to drop features to complete the upgrade. On the flip side, Drupal 7 provided a bunch of little niceties that meant I could remove some custom code from my theme (and overall I really like theming with Drupal 7). Overall, the upgrade was pretty painless for me, but I wouldn't recommend firing up an upgrade for most sites right now, unless you have the time and resources to put some muscle into it. I'll walk through my process and some decisions I made to see why I come to this conclusion.
I've been playing around a lot with my site, doing an upgrade from Drupal 6 to 7. I also decided to set up a new server on Linode to give them a try (I've heard great things about them). I'm an Ubuntu gal so I had to choose between the LTS (Long Term Service) or the latest. Of course, I ended up picking the latest release, Natty Narwhal (It's a Narwhal!). Once I clicked a button or two to install the new and boot it up, I needed to do some work to make an actual useful web server. Here are my notes from getting things up and running. These aren't extensive notes with lots of explanation, but it is enough for me to get through the process without wasting several hours. Take them for what you want.
This Friday I am returning briefly to my favorite city, Copenhagen, only to shoot off again and go on vacation for the first time in years (that's a whole post in and of itself). On Saturday it turns out that there will be a event called Geek Girl Meetup Copenhagen (in Danish). There was such a huge response that the organizers had to close registration until they could find a larger venue. Hell yeah!
I signed up out of reflex even though it will be largely in Danish (um, jeg taler ikke Dansk?). I mean, I'm a geek. And I'm a girl. And all of the geek girls I know in Copenhagen are going too (and apparently a ton who I don't know). Even if I can't understand many of the sessions, I'll be spending my time chatting up with other girls who identify as geeks. Then today, one of those friends, Mary, went ahead and posted something thoughtful about it all, passing on Henriette Weber's blog baton. I do indeed have some thoughts on geekiness. (Jeez, Mary, making me blog and all.)
I recently wanted to do some quick vector image work, which I haven't really needed to do in quite a while. I am by no means a graphics person and certainly not a power-user. I just need to do some of the basics occasionally, preferably without getting totally overwhelmed. I limped along for a while when I first got a Mac using my beloved linux apps, Gimp and Inkscape, which I used for years previously, but I really can't stand using X11 on a Mac; really, it makes me a bit batty. A while ago I ended up buying Pixelmator to replace Gimp and I've been pretty happy with it. It satisfies most of my minimal graphics needs, but I never got around to finding a decent vector editor, and sometimes you just need vector. Today I ended up doing a quick search on The Google and asked for recommendations through Twitter. My criteria are pretty simple: under $100, native Mac app, and simple enough for me to get a basic project done without reading a whole damned manual. I ended up downloading four apps to try out:
In the past few weeks I have been building myself up to get back on track with my role as Doc Lead in the Drupal community. I've been off radar for quite a while now (since last fall) and I'm finally getting my feet under me to tackle the work of docs again. In the time that I was out of it though, it was too obvious that there needed to be some changes in how I (and the Drupal community) approach this whole documentation team thing. There were a few other people out there who had expressed the same concerns to me and so I sat down with them to kick around what we need to change. We came up with two fundamental shifts in how we do things as a team: communication and coordination. I think this will take a lot of pressure off of a number of people, myself included, as well as let the community take even more ownership of documentation and play a role in the steering of the ship, even if the captain sometimes goes AWOL.
It has been a while since I've been on radar, but with Drupal 7 fast approaching and Drupal living in the White House, we need to keep focus on one the keys to Drupal domination: documentation. Here is a little status update on where the Drupal docs world is these days and what's coming up next. (As an aside, I've been distracted from Drupal for a little while due to other things going on in my life, but hope to jump back into the fray by the end of the year.)