A year ago, we had people interested in project management, but not a whole lot of people actually doing it in Drupal. This morning, we had the Project Manager Birds of a Feather session in a room that ended up being standing room only. Sure, there were a few laptop dwellers (and sometimes I’m one of them), but with roughly 40-50 people there, it’s the biggest PM BoF I’ve seen in the year and some change of getting really involved in Drupal community. So thanks.

We also had a panel today on The Care and Feeding of Project Managers, which was a lot of fun. The hour went by fast, with conversations about backgrounds, where we come from, but how we’re all sortof on the same page about how we build our processes.

The four of us (myself moderating, Wendy Iguchi, Chris Strahl, Crystal Williams, on the panel realized that project managers in Drupal haven’t really committed much back to the project itself. Just because there isn’t really a space for that in drupal.org is, realistically, no excuse, and I’ll be the first to say that I haven’t done a good job of putting my own work anywhere useful to folks. To paraphrase Dries, ‘Talk is silver, documentation is gold’.

I’m not sure where things will go from here, because the firehose of crazy projects + conferences + life is totally here, but I’ll be spending some time in the coming months on giving back.

Hope to see some of you in the Managing Expectations talk tomorrow morning, too early!

1) Write on your badge. If you’re doing new cool things, put it on there! If you’re hiring, and I think a few people might be, put that on there too.
2) Perform the Ceremonial DeBadging as you’re leaving the venue. While it’s funny to be branded with this weird blue alien that stares at people, don’t let that out in public.
3) Look at the schedule, see what you want to go to.. and then spend the rest of the time in the Hallway track. That’s where you’ll learn the most, from meeting with people.
4) See if you can’t brush up on actual names instead of drupal.org usernames. I haven’t seen the badge designs yet, but usually, first names are on top and are most visible. (Crell is actually Larry, etc.)
5) Go with the flow. Drupal’s moving and changing, and this is one of the points in the year where we get to talk about where we’re going, where we’ve been, and what cool things we want to see happen.

• WordPress is a CMS that’s built for blogging. This is primarily a blog.
• I create content here. I’m not trying to integrate a legacy system with lots of data and lots of users, I’m not trying to put a lot of media that needs to be very stable, and I’m not trying to create a completely search-optimised web presence. Yet. I’m working too hard doing that for other people to really do it for myself.
• I really like how WordPress ‘gets out of the way’ of your experience for creating good stories in text.
• I appreciate the experience of logging into my own site, swearing at it because ‘I can’t find X’, where X is something I’m very familiar with in one system, and forget all the time in others. It keeps me honest, and remembering what the content creation experience is like for the vast majority of CMS users.

So whenever you find me, and you want to know the answers about ‘Wait! You’re really involved in Drupal! Why does your own site run on WordPress?’
That’s why.
It probably won’t always be on WordPress; I may at some point decide to plan out msamye 2.0, and then I’ll start writing about the process of change, evaluating solutions to fit your needs, and actually doing it.

Saturday was sessions all day, with highlights include: Josh Konig talking about Drupal in the Cloud, Sam Boyer talking about Panels, Damien Tournoud talking about Drupal 7, and Bill Fitzgerald talking about Views. An international rockstar DrupalCamp, clearly. (There were also great conversations over sushi, showing out of towners more of the beautiful city of Portland, and appreciating Portland’s great microbrews.)

Yeah, I gave a session on project management.

I’ve spent the last few days in San Francisco deeply buried in Drupal and the future of Ubercart, and am flying up to Vancouver this afternoon to work with the D7CX initiative. We’ll be posting more about that in conjunction with BadCamp and the Drupal 7 Contributed Module sprint this weekend.
In fact, in almost every region of the US and Canada, there’s a Drupal event going on. Drupal Events Calendar
No, I’m serious.

See you all in Vancouver!

In retrospect, this is one of the best choices I think I’ve made. It has also been one of the most frustrating and rewarding choices.

I was fortunate to come into Drupal with an open mind, enough web development experience to ask the right questions, enough project management experience to not really screw up. At first. I got better at screwing up later on. It’s a really valuable skill: recognize when you’re screwing up because you didn’t ask the right questions, because you’re in the wrong position or when you didn’t answer the right question. I’m still getting better at that.

It’s frustrating because as a non-developer, getting into the Drupal communities has an extra layer of complexity to it. It’s like learning a foreign language where the first three weeks that you’re listening in, you’re trying to distinguish what sounds are words.

It’s frustrating because as you’re learning, you’re not quite sure of the questions you’re asking. You’re learning the vocabulary with the technologies. You’re pretty sure that when something doesn’t work like it intended, there’s a good reason for it, but you’re ignorant of the starting place.

But once you get past that whole learning curve part, there’s a whole bunch of people who are genuinely amazing and want to see more people get involved. They want the CMS project to succeed, and they want it to be useful. They want to use it to build easier to use websites, websites that scale better, websites that are easier to design for and still have the immense vastness of possibility that Drupal has.
That’s the rewarding part, and it is why I keep doing this.

It’s why I go to the DrupalCons, and interact with as many people as possible. Developers, project managers, business-side: we’re all living in the same sort of washing machine. DrupalCons are about trying to add as many new points of light to your own Drupal resource universe, whether that’s people or modules or integration strategies or new companies to partner with. It’s about being able to meet up and discuss hard problems in person, where communications are easier and you put faces to familiar names. And then I come back to Portland and play with the open source communities and try to figure out what other places do better, and what Drupal has to learn. (Also, what Drupal has to teach to the open source communities.)

This is why I do project management for a living, and community organizing for fun. Somewhere in here the stories of being an independent project manager will come out, but in the meantime, this is a ‘happy to be here’ post. DrupalCamp Portland kicks off Friday night, but that deserves its own separate post.

This is the ‘about me’ part. This is the personal website of Amye Scavarda, a ridiculous web citizen. I’m currently based out of Portland, OR involved in the open source community. Things that are near and dear to my heart are: community outreach, project management, and how to make people’s dreams of websites come true.

My current projects include OpenSourceBridge and all things tech conference related, understanding Drupal, WordPress and other open source CMS technologies, and making them more useful to users. Expect to see more of the same, interspersed with hilarious stories about life in Portland.