Savannah WordPress Happy Hour on Friday

The WordPress core team will be working together from downtown Savannah tomorrow afternoon as part of the annual get-together, and we’d love to meet local WordPress users, developers, designers, consultants, etc. after we call it a day. Come meet us!

We’ll meet up at Jazz’d at 6pm and will be the group wearing an assortment of WP shirts. If for some reason Jazz’d turns out to be a poor choice, the backup plan will be to mosey over to The Jinx.

So please, come out and say hello! If no one comes we’ll be forced to come to the conclusion that no one in Savannah likes WordPress very much, and we’ll just give up and take up miniature golf instead. And I really suck at miniature golf, so please come  have a drink after work tomorrow.

See you there? See you there!

Posted in Community, WordPress | Tagged | Leave a comment

Timing

Doing the core team meetup on Tybee is great, because it means I don’t have to abandon the kid for a week. Doing the core team meetup on Tybee is rough, because even after staying up working late with the guys, I still have to get up at 6am for the morning routine.

Posted in Personal | Tagged | Leave a comment

I commented on WordPress Sidebars as Menus: Part 1 by Ipstenu

Posted on by

Will Work For Music*

Note: This was originally posted on an internal work blog. Then I remembered that my co-workers aren’t the only people with digital music libraries.

Tomorrow morning I will get into a 16′ rental truck with a broken radio and begin a drive that will be a minimum of 17 hours over 2 days (with my mother driving in her car behind me). Not having anticipated this, I have the wrong laptop with me — no music on it — and my iphone only has a playlist on it from my last drive with Morgan (in other words, mostly Glee soundtrack, ouch).

If anyone is bored today and wants to throw together some music and put it on dropbox or some such for me so I could download it tonight and make a tiny dent in the driving monotony tomorrow and Monday, that would be awesome, and I’d owe you one. I’ll love just about anything except contemporary country, Christian rock**, death metal, or obnoxious top 40 like Ke$ha.*** Bonus if anyone does a playlist that encourages singalongs (it’s a good way to stay alert on the road).

Once I get today’s packing/loading done I will be on an expedition to find a place within 60 miles to buy a decent portable speaker (oh, x-mini, why did I leave you in my car at home?) and an ipod I can use for the trip (so my phone won’t die out, will need it for internet and phone), so I will have gigs and gigs (well, probably 16) of room to fill.

Anyone?

If you want to send me music, you can email a link to your dropbox file to me at jane at wordpress.org. Or, if you have music to share but no dropbox space left, I could give you access to my folder.

Many thanks!

* In exchange for road trip tunes I will continue to do my part to keep WordPress pretty and useful.

** Though actual gospel music is okay — did you know that once upon a time I sang tenor in a gospel choir?

*** G6, my a$$.

Posted in Personal | Tagged , | Leave a comment

Testing 1, 2, 3: Usability and WordPress

I did some lo-fi testing of WordPress 3.3 pre-beta on Sunday/Monday with local users, but since in the next set I want to get more multisite users, finding good participants will be tougher. Savannah has an art school, a music scene, and a burgeoning tech culture, so I can’t spend an hour at The Sentient Bean without overhearing someone tell their co-caffeineators about some new WordPress site they’re working on — a flyer posted for half a day gets plenty of individual users.

Multisite superadmins, though, are a bit harder to come by without effort, so I’m going to test out using some fancy web technology called “the skype” + “quicktime recording” as an experiment.

A Bit of Testing History

Once upon a time, usability testing was done in a lab, and was very expensive. Costly software like Morae was used, whole research teams were needed to recruit participants, moderate test sessions, and analyze results, and sometimes things went really high-end and lasers were involved. We’ll call this “formal usability testing.” The testing done in Spring 2008 on WordPress 2.5 and the Crazyhorse prototype was formal, included laser eye-tracking, and led to/strongly influenced the 2.7 admin redesign. Read all about it.

If you couldn’t afford formal testing, lo-fi setups involving a camcorder and a tripod allowed capturing the screen and participant speech, but even with a decent camera, the screen images were never fantastic. Also, unless you set up two cameras, you would miss things like facial expressions (which are hugely informative during observational testing). Although you could set it up anwhere and didn’t have to rent a lab, it was a clunky solution.

It is hard to believe it’s been so long, but I have been doing usability testing –both formal and informal — for more than 12 years now.

In July 2008, Clearleft released their Silverback app, and popularized the concept of  ’guerrilla’ usability testing. Armed only with your Mac and their app, you could get screen capture and user video/audio thanks to your Mac’s built-in iSight. This was a game-changer. Though it didn’t have the hardcore analysis features of Morae, simply getting a high fidelity screen cap on your own was huge… and it was only about $50! Suddenly, you didn’t need to rent a big lab, you could use your regular office or even set up shop at the local caffeine vendor. Just stick people in front of your laptop and you were good to go. Suddenly testing costs could be a tenth of what they had been, and guerilla testers cropped up everywhere. By the time 2.7 was ready for testing in Autumn 2008, that’s how I was doing it, too.

I had grand plans to introduce a distributed testing model to create an avenue for usability testing professionals to have a way of contributing to WordPress that would be analogous to writing patches or helping in the forums. I put up a post about it, corresponded with potential volunteers, and tried to work out the logistics. Having each volunteer running Silverback and then uploading their videos to a central repository for analysis was the plan, but infrastructure was a problem in two ways:

  1. How would we match volunteer test moderators/usability professionals with volunteer participants? Well, there were some more grand plans around building a volunteer database tied to the .org profiles, but when the person who was working on it left, that basically sputtered, so finding participants remained a normal logistical nightmare.
  2. It would mean only Mac users could conduct testing, and non-Mac users would be using an unfamiliar OS during the test.
  3. We didn’t have a good way to collect the session videos.

So that plan never really got off the ground.

Skip to Today

Guerilla testing is still going strong, and if the number of people proposing sessions about it at SXSW is anything to go on, the fact that it’s been more than 3 years since Silverback was introduced hasn’t made it any less exciting a concept. That said, it’s still not a perfect solution. Let’s look at pros and cons…

  • Pro: Output video content and quality on par with tools like Morae
  • Con: Lacking in the post-test analytic tools of Morae.
  • Pro: Works on Macs! Morae is still PC only.
  • Con: Works on Macs! 3 years later, Silverback is still Mac only, excluding all our PC users from participating in tests in a familiar environment, and preventing non-Mac usability pros from getting involved this way.
  • Pro: Much cheaper than buying Morae.
  • Con: If the plan is to have many people doing testing all over, each moderator needs a copy of Silverback. While markedly less expensive than copies of pro software like Morae, adding up all the copies of Silverback would wind up being more than one person or team running Morae.
  • Pro: Can conduct testing in convenient locations such as an office, a coffee shop, etc. or travel to participant location. Great flexibility.
  • Con: Limited to in-person-only testing unless test participants download and install Silverback on their machines. We don’t want to require people to install software (even a free 30-day trial version) just to be a volunteer test participant, so anywhere we want to test with real users, we would need volunteer moderators with the software to be co-located.
  • Con: Non-realistic experience when using a moderator-provided laptop during in-person tests. Real-world things influence how a user interacts in the browser with any web app — saved passwords, form auto-fill, chat windows popping up, email notifications, torrent downloads of Doctor Who hogging your bandwidth, screaming kids in the background, a ringing phone, you name it. To get a more realistic picture of usage/behavior, the researcher always prefers the setup that is as close to normal as possible. Using someone else’s laptop just doesn’t cut it.* And just as Morae limited us to PCs, Silverback is limited to Macs, but we want to test with users of both platforms. (And Linux! Don’t forget Linux!**)

So while guerilla testing with Silverback is cheaper/and more flexible than hiring a lab, and provides you with deeper observational information than an online service like usertesting.com, you’re still limited to doing testing in a place where you can have both a moderator and participants, which makes the participant pool quite limited, and not representative of the WordPress user base as a whole.

With the advent of Skype screensharing and Quicktime screen recording, we may finally be getting to a point where we can bridge that gap and include participants who are not local to the moderators — where we can get good recordings and can let participants use their own machines without significant cost or requiring unfamiliar software downloads. The drawback to this is that if you’re using skype to screenshare, you can’t also continue the video chat talking head.*** Still, observing real-time usage in a far-away participant’s own environment while being able to ask questions is a big step forward. So, I’m trying it out. We’ll see how it goes… Skype screensharing can get jumpy or laggy if you’re not on a reliably blazing internet connection.

If you are someone who uses WordPress multisite as a superadmin and would like to be a guinea pig to help me work out the kinks of this method (and get a look at some new UI stuff we’re considering at the same time), leave a note in the comments and I’ll get in touch over the next couple of days. Thanks!

When we get into Beta, assuming the trial run of this goes okay, I’m hoping to try and revive the distributed testing idea, so if you are a professional usability tester and would like to get involved with that in a couple of weeks, a note in the comments will get you added to the email list for when that’s ready to try again.

All that said, why do we do testing? It’s time-consuming and expensive, even when the software is cheap or free. Most agencies do it to show their clients that the design decisions they made were good ones. Most companies do it to find out what problems customers/users have with their products. With WordPress, we don’t so much have a “client” and our users tell us straight up in the forums what things cause them problems. So why should we do testing at all?

  • Define benchmarks. One of the things we’re always trying to improve with WordPress is making it faster. How long it takes to complete various tasks in wp-admin is one benchmark of performance and usability that can be measured. Testing can provide a sample data pool with these stats.
  • Test assumptions. With so many people weighing in on every design decision for WordPress, sometimes we have to forge ahead in what we think is the best direction despite siren songs from contributors who would prefer a different UI approach to something. Design by committee, camel, etc. That said, when’s there’s more than one UI idea or suggestion that seems reasonable for a given task, we don’t want to cling dogmatically to the status quo, either. Testing a few different design approaches allows us to see which designs people seem to respond to better.

So, could we live without testing? Sure. But do we want to? No. Seeing our work being used by regular people — not code contributors, not designers, not WordPress insiders with a vested interest in the choices made in the UI — keeps us humble. I challenge you to watch someone who’s not especially web-savvy figure out how to embed a video the first time. Change the tagline. Create a custem menu. I think the perpetual praise of WordPress as the most user-friendly platform for blogging and content management is justified, and we’ve worked hard to earn that reputation, but everyone on the core team is painfully aware of how much further we still need to go. Good testing can help us get there faster.

P.S. I haven’t even touched on testing with people of different abilities, different languages, etc., but that all needs to get more attention as well.

*And also means the researcher will have to re-arrange all her keys to be QWERTY for the sake of testing, then swap back to Dvorak afterward. Hmph.

** We usually forget Linux.

*** If we wanted to do another Mac-only thing, people with iPhones could use FaceTime for the talking head part while Skype was in screen share mode.

Posted in Usability, WordPress | Tagged , , , , , , | 23 Comments

In Praise of the Forums

Forum thread moderator resolution menuI go to a lot of WordCamps and meet WordPress users in person, I get a lot of email, and I monitor several official WordPress twitter accounts in addition to my personal one. Through all these channels, the most common question is not, “How do I become a contributor,” or, “How do I get more traffic to my site,” it’s “Where do I go for help with WordPress?” Little do they know that the answer to the latter is the answer to all: the WordPress.org Support Forums.

When I tell people (in person, via email, over Twitter) to head to the support forums, they often reply with annoyance. They want immediate one-on one assistance, phone help, me to rebuild their site and get them more traffic….. oops, tangent. The point is, people who don’t come from an old school web background mistrust the forum format. Their concerns:

  • No one will answer my question
  • How do I know they know what they are talking about
  • I will look dumb asking my question in public
  • Someone is going to scam me

This morning there was an example that made me think about how much better public support is than private.

  1. Bill asked his question in the forums about a Publicize notice appearing in his self-hosted dashboard.
  2. esmi (volunteer forum moderator) saw the forum post and replied within an hour.
  3. Bill clarified something in a reply, also within an hour.
  4. Nighttime. Sleep.
  5. In morning, esmi sees the reply and says she will ask around to find an answer.
  6. esmi emails the wp-forums list at 7:12am to see if other moderators have seen the bug/have any idea what’s causing it.
  7. I reply to list at 7:21am suggesting it may be Jetpack-related, and comment on the forum thread asking Bill for his URL (because then we could View Source) and whether he uses Jetpack.
  8. I post to an internal blog (7:31am) at Automattic for the team that makes Jetpack, noting the behavior and asking if they know what’s up.
  9. Westi (lead WP dev) sees my internal blog post and pings me in IRC at 7:33am to ask for more info, agrees it’s likely a Jetpack bug.
  10. Westi and I both leave additional comments on the internal blog (7:36am and 7:38 am, respectively) for Greg, the lone Jetpack team member who’s not en route to Lisbon for a WordCamp/team meetup.
  11. Greg replies to us at 9:34am (he’s in a time zone an hour behind me) and gets to work on fixing the bug.
  12. At 10:36am Greg posts to the internal blog with a link to the changeset that has his bugfix.
  13. Greg then posts to Bill’s original thread apologizing for the bug and notifying him that it is fixed.

Granted, this doesn’t happen with every thread, or even most of them. Most of the time the volunteer moderators are able to answer things on their own. But when they can’t, the moderators know exactly how to get the attention of the right people, and those people give them that attention because the moderators have earned trust — their requests for help are not seen as noise, but as a valuable community resource.

Little did Mr. Bill realize that when he asked his question he would get the attention of an experienced moderator, the UX lead, a lead developer, and one of the Jetpack developers all at once. And thanks to him asking that question in the public .org forums, the right people were pulled in, and the bug was fixed right away.

So, back to those concerns.

  • No one will answer my question. Well, first you should use the search box and see if they’ve already answered it for someone (or some hundred) before you. Then you don’t have to wait at all. If you do post a thread, it will most likely get an answer pretty quickly (or at least a request for more information to allow volunteers to troubleshoot).
  • How do I know they know what they are talking about? If someone is labeled as a moderator, keymaster, core team member, etc., they know what they are talking about. Other volunteers may also offer help. Usually additional people will weigh in to say if their advice is correct or not.
  • I will look dumb asking my question in public. No, you won’t. We all start somewhere, and the first question you ask in the forums should be a mark of pride: you’re learning how to do something new! And while I encourage this bravery, some people are just too shy to ask. With almost 60 million WordPress installs worldwide, I guarantee you are not the only one with your issue/bug. Asking in the public forums means other people can benefit from the answer as well.
  • Someone is going to scam me. No one who is official in the forums will ever ask for your admin password, for money, or for sketchy personal details. If someone does, please add the modlook tag to your thread so we can check them out and correct the behavior (if they just didn’t understand the rules) or ban them (if they are scammers/spammers).

Oh, and as for those other questions people tend to ask me that also can be answered with the forums…..

How do I become a contributor? You can start by helping people in the forums! This is a great way to give back even if you’re not an expert yet, because there’s almost always something you’ve learned already that someone else hasn’t. If you’re a developer, it will also help you find bugs to fix. Helping people in the forums with consistency and accuracy builds your reputation with the core team, and gives you an “in” with the powers that be. Having a close connection to WordPress users via volunteering in the forums gives you insight into the way people use the product and what bugs or workflow issues need the most help, which will help you focus on the most important things to improve in core.

How do I get more traffic to my site? Well, you can specify your site URL in your forums profile, and it will be linked from your name in your forum replies. If you give helpful answers in the forums, people will tend to click that link to learn more about your awesomeness.

And a bonus tip if you are a WP freelancer or run a WP-based business: Paying one or more of your employees to spend some time helping in the forums (and/or contributing to core with patches) is a smart idea for several reasons:

  1. Your company will suddenly know a lot more about the needs of the WordPress community and can address them better with your products/services.
  2. You’re investing in the platform that powers your business.
  3. You gain reputation — both bragging rights and core team appreciation and respect.
  4. Clients like to hire people/companies that have their hands in the actual project, because they feel more secure knowing that you will always be ahead of the curve and know the codebase better than your non-contributing competition.

So! Asking questions in the forums? Win-win. Answering questions in the forums? Win-win-win. All hail the forums, and the amazing efforts of volunteer moderators like esmi, Ipstenu, alchymythandrea_r, samboll, and zoonini,  and active volunteers like kmessinger, Rev Voodoocgrymala, crondeau, and danhgilmore.* The next time I write a post like this, I hope your name will be listed here!

*This list is based on activity I see on the wp-forums list, a tweet asking for recommendations, and a quick query on posting activity. We really need to start gathering stats on forum activity. What kind of activity levels do these guys have? Here are the top five posters and how many posts they’ve made to the forums in the past 3 months:

  • esmi: 8514
  • Ipstenu: 4432
  • alchymyth: 2018
  • andrea_r: 1385
  • kmessinger: 1074

Remember, you don’t need to put in this much time to make a difference. Having a goal of helping one person a day, or even per week would make a big impact if everyone did it. Happy helping!

Posted in Community, WordPress | Tagged , , | 11 Comments

DevPress, WPCandy, and Why I’m Now 80% Blonde: Part the First

Every morning I wake up at 5:42am so that I can make lunch for my niece (11th grade! I remember her emergency birth — weighing 2 lbs 13 oz — back when I was in Okinawa to take care of her as a newborn. They grow up so fast!) and send her off with a wish for a good day before she goes to school. After that, I start work. By the time most people are getting to their coffee I’ve already put in a few hours (per trend), so it wouldn’t be accurate to say that I woke up on September 9th to find out I’d been accused publicly of starting a war; I was already awake. That said, it was a sucky way to continue the morning, the day, the week. Especially because I was not accused directly, nor did the person who printed the accusation bother to contact me about it; I found out because I get the pingback notifications from WordCamp.org, and Ryan’s article linked to the fundraising page on the planning site.

I don’t even know where to start. Here’s the list of the things that I feel obligated to do now, in written form, in public:

  1. Set the record straight regarding my communication with Justin, which in no way resembles starting a war.
  2. Explain why giving away memberships is not the same as underwriting an event.
  3. Explain why the guideline exists in the first place, the long-term reasons why they’re important, and the plans for their evolution.
  4. Ask why someone (I’m looking at you, Ryan Imel) would publish something so inflammatory without even checking with the person being accused of something first to see if it’s a) true, b) something that could be worked out without animosity somewhere other than in the comments of WPCandy.
  5. Defend myself against the slur of needing an English degree.

Well! I guess I won’t be spending the morning working on the uploader UI. Because — let’s face it — there’s no way I, the wordiest of the wordy, can address all of these things in one succinct post, I’m going do a series of three. A trilogy, as some English majors might say. And the posts probably won’t be succinct, because this brouhaha has brought up a lot of issues, and though people are claiming their questions are simple, generally there is a simple answer, but then a long drawn-out answer is required if someone doesn’t feel the simple answer was adequate, so might as well just put it all out there.

In this post, Part the First, I’ll largely be providing an account of what went down from my point of view, reacting to the way this thing blew up, and talking about how it affected me personally. In Part the Second, I will address the sponsors vs. giveaways issue. In Part the Third, I will give an overview of why the guidelines exist, how they are decided and evolve, and possibly give some examples of things that have happened but not been publicized that have contributed to certain guidelines (if I can figure out how to do so without violating anyone’s privacy — when you start talking about stalking, financial malfeasance, or lawsuits, it gets very tricky). So if you don’t care that I feel unfairly attacked and you just want to know about guidelines, come back in a few days, because Part the First is apparently 4,325 words.

Guess I’ll just jump right in.

Here’s how it went down, from my point of view.

  • I saw Justin tweet re giving free memberships to WC Philly attendees.
  • I touched base with Andrea (who does all the WC approvals and works with organizers to keep things cool re guidelines). She was already contacting WC Philly organizers, but didn’t know Justin, so I offered to contact him since we’d exchanged a few emails in the past and it would be more casual.
  • Opened a new email, but due to new laptop and no autocomplete for Justin’s address (as it had been awhile since I’d been in touch about anything — the last time was when he declined to lead a .org theme developers’ handbook because he’d landed a gig with a publisher) and Thunderbird search sucking, figured I’d just ping him on Twitter.
  • 9/2 – DM to Justin. Normally I would never post DMs, but since a chunk of this controversy stems from me “starting a war” per Justin’s published statement, the actual exchange is relevant. I will note that a 140-character limit is terrible for this kind of exchange, and I wish I’d looked up his email instead.

Sept 2, 9:34 AM DM
Sept 2, 10:33 AM DM

Side note on how I work:
I usually work about 15-18 hours per day, mostly including weekends, though fewer hours if I have any obligations in my #fakemom role. I’m working on getting this number lower, but for now it means continually flipping through Skype (usually 6-12 ongoing, active chats plus an average of about 20 specific pings/chats per day, IRC (usually 6 channels), Thunderbird (too many emails), Chrome (usually 4-6 windows with about 20 tabs each), Preview (viewing attachments from said Skype pings, emails, etc), and TextEdit (usually about 8 active documents). Some days you can also add in Coda and Terminal, and/or Inkscape and Gimp. And if I really want to be inclusive, System Preferences a few times a day to deal with my wifi being capricious. When someone pings me in Skype or IRC, I bring that window into focus and they have my attention until more than a minute passes without them saying anything. Then I go back to my other stuff and wait for them to ping again.

With Twitter, I don’t have notifications on, because they were too disruptive. I use the Twitter website, not a desktop client, and use it as a casual dip-in-between-other-things form of interaction. One major drawback to the Twitter website design (hey, ex-boyfriend Doug!) is that there is no visual indicator when you have new @replies or DMs if you are on your main stream view, so I often miss these until I remember to check for them. If I send someone a DM, I wait around and leave the screen open for a few minutes, but then go back to the main screen or the @replies screen before leaving so I can see the number of new updates in the tab. It was an hour later when Justin replied, and I no longer had the DM view open, so I didn’t see his reply until the next time I clicked on Messages, which was a couple of days later because of the timing.

Back to the recounting of how events unfolded.

  • 9/3 – My brother’s wedding 3 hours away. I left the laptop behind and hung out with the family, getting back home around 4am on 9/4.
  • 9/4 – 9/6 – Labor Day weekend. Slept a day to make up for previous night, later made a bunch of plans with my mother for her big move.*
  • 9/7 morning to afternoon – Holiday weekend over. Giant email scrub and general catchup that takes forever (the reason I don’t normally take weekends off is that coming back means so much backlog).
  • 9/7 around 3:45 pm – Take doctor call telling me I need to come to office first thing next morning to discuss bad test results. Tell #fakekid I might not be there when she gets home from school next day because of appointment. She asks if she should be worried about appt. I say I’m not sure yet, but that I promise to stop working for the night at 7 for a change and take her dinner and we can talk about it then.
  • 9/7 4:20 pm – Return to DM with Justin.

Sept 7, 4:20 PM
Sept 7, 5:29 PM
Sept 7, 6:23 PM
Sept 7, 6:24 PM
Sept 7, 6:30 PM
Sept 7, 6:30 PM #2
Sept 7, 6:32 PM

  • 9/7 6:48 pm – Seeing that we’ve gotten to a point where we are needing to do multiple tweets per minute to finish a thought, I suggest moving to email or Skype for easier communication.

Sept 7, 6:48 pm

  • 9/7 7:00 pm – I close the laptop and take my #fakekid to dinner as promised.
  • 9/7 7:01 pm – Justin replies but does not take me up on the offer to switch to a non-140-character-limit mode of communication.
    Sept 7, 7:01 PM
    I don’t see this reply because I’ve closed the laptop. If you look at my profile, I was not on Twitter again until the following morning (though I will admit I forgot to check the DM view then, as referenced earlier re UI) when I was headed to the doctor’s office.
  • 9/8 – Spend morning at doctor’s office, being told I may have cervical cancer and getting a biopsy scheduled. Before I even get home, tweet to all women following me to please get a pap smear because I don’t want any of them dying from undiagnosed cervical cancer.
  • 9/8 – Once home, start throwing up from fear/stress thinking about what will happen to my niece and my mother — both of whom will be relying on me for support as of next month — if something happens to me, and go to bed with a big metal bowl at my side in the afternoon. Fall asleep and stay there until following morning.
  • 9/9 – Wake up, make the kid’s lunch, get her off to school, get back to work, start email scrub that will take hours as result of being offline after getting sick the day before. See email with ping notice from WPCandy on the plan.wordcamp.org site’s fundraising page, with a headline that sounds dramatic and confrontational: DevPress Deal Is Against WordCamp Guidelines. This seems to require immediate attention and I do not finish normal catch-up scrub, so do not get to Twitter or see Justin’s last DM yet.
  • Read article. See that Justin has vilified me and accused me of starting a war, among other things. Am astounded that Ryan Imel would print such an inflammatory email without even contacting me for a response or to warn me.
  • Ping Andrea. Turns out Ryan did exchange a couple of emails with her the afternoon before to make sure he understood the WC guidelines, but did not mention Justin’s email. Andrea had requested he hold off on publishing until she could check with me to make sure she hadn’t said anything incorrect. He did not.
  • WPCandy comments turning into another freakin’ dramarama. Some people get the point of the guidelines. Some people get the point but disagree with the policy. Some people don’t get the point.
  • Succumb to feelings about being attacked after being out of conversation for one day, open Twitter for first time that morning, and send a tweet I immediately regret because suddenly everyone I know is pinging to ask me about the state of my junk, which is a) uncomfortable, and b) not helping me get it off my mind.
    Sept 9, 5:59 am
    More nausea ensues.
  • Realize I am getting really tense. Go for a walk on the beach. Luckily, it is 3 blocks away. 15 minutes of wading in surf calms me down.
  • WPCandy comments turn to finger pointing against me, the Foundation, Automattic. Unsurprisingly, most of the nastiest ones are from the same people that make these kinds of accusatory comments every time there’s some kind of drama.
  • I get really upset. I think it is not cool that I was trying to be casual and friendly and get things ironed out privately so that everyone could be on the same page without creating a bunch of drama, and now suddenly I’m the villain in a very public crapfest that was completely unnecessary. If we had told WC Philly they needed to back out of the DevPress thing and had publicly blamed DevPress of not being aboveboard or something, I could see it, but that’s not what happened. We said fine, it’s done, let’s just make sure people know the score moving forward, which is how we’ve handled every guideline slip by an organizing team and/or a business that wants to get involved with a WordCamp. We assume the best: that people didn’t know, misunderstood, or forgot, and that we all want things to be cool. In this case, Justin and his very vocal backers assumed the worst of me, and decamped from direct communication in favor of publicly attacking me.
  • I get back to work on getting 3.3 ready for feature freeze. I’ve let this kind of stuff distract from the job of making WordPress too many times, and I decide to wait to write a response post until a) I’m less upset, and b) I get caught up on some 3.3 ticket review, as freeze is looming and I got really behind during WCSF organizing time.
  • Despite theoretical therapeutic value of immersing myself in work, I’m still upset. I decide that the only way to burn off my feelings and keep myself from writing comments or posts while in this mood is to make an appointment to bleach the crap out of my hair, which will take hours. I figure the burning scalp will distract me, and being limited to typing on my phone will restrain me. I call and they agree I can come in at noon. I write an intro paragraph and an outline so I’ll remember the things that stood out for me during the morning (because all this happened before the west coast even woke up), then head to Savannah to obtain the new ‘do.
  • 9/9 5:30 pm – Leave salon with a modern-day cruella de ville two-toned head.

That’s the end of my version of how this all unfolded. Taking a long weekend for a family wedding and holiday weekend and then taking a day off because of the doctor stuff did mean there were two times that I didn’t continue the DMs immediately. However, I was not under the impression that it was an issue of urgency. I hadn’t said it was, and if Justin thought it was, I’d think he would have pinged again. I’m the first to admit that I’m not always timely in following up on things — hell, it’s the entire reason Andrea got hired, so WordCamp organizers wouldn’t have me as a bottleneck — but in this case I don’t think I was guilty of inordinate delay.

Things that pissed me off (why sugarcoat it now):

  • People saying they were taking “the side of the community.” Dudes, if you are taking sides at all, you are not acting in the best interests of the community, regardless of which “side” you’re on. We shouldn’t be dividing ourselves into sides at all. Everyone should be working together to create common understanding and acknowledge the multiple goals and desires at play in this multi-stakeholder community. If you just want to complain about “the man” (or in this case, the woman) without making any effort to resolve the issues in a professional, collaborative manner, then I’m sorry, but you do NOT have the best interests of the community in mind. The phrase “haters gotta hate” comes to mind.
  • Justin accusing me of starting a war. If I wanted to start a “war,” I’d have posted publicly that they were not adhering to the guidelines and said nasty things about them. Oh, but I didn’t. Granted, at 140 characters, my Twitter DMs were to the point, but they weren’t rude, and I did ask if we could switch to email or Skype.
  • Justin accusing me of going to Ryan to blow up a story instead of talking directly with Justin. I was talking directly to Justin, and I would never choose a public scandal over a quiet conversation and resolution. If the quiet conversation had failed, I still would not have gone to WPCandy and asked them to post about it. When have I *ever* done that? If anything, I sometimes ask for things not to be posted right away so people can have more time to work things out privately. In this case, I didn’t ask for anything, because I was not contacted.
  • Justin saying that if I’d been willing to sit down and talk a week ago, things wouldn’t be out of hand now. They didn’t contact me beforehand, and the week-ago response to my DM did not ask for a conversation, just stated they thought they were within the guidelines. See timeline above to judge for yourself if I was refusing to sit down and talk to him a week earlier.
  • Justin’s snotty remark about my needing an English degree. The definition of guideline is a rule or policy by which one is guided, so saying over and over that we have guidelines-not-rules is not logical. The choice of the synonym for the plan site was very intentional: the word “rules” implies there will be a smackdown if you “break” them; the word “guidelines” implies that we’ll guide you back on track if a rule is broken. We don’t want to slam doors, we want to help guide people through the ones that are outlined on the planners’ site. Except in one or two notable extreme cases, anyone stepping on the wrong side of a guideline just gets pinged for a chat, and it’s resolved easily.
  • Ryan Imel posting that nasty email. It was, very simply, a personal attack and downright nasty. When even Carl Hancock, one of my most vocal detractors, agrees that it’s over the top, you know it’s crossed a line.
    Sept 10, 8:42 am
    His reply above did make me wonder how many people actually read the email that Ryan published.
  • Who prints that kind of stuff? Just the other day I told my 11th grade #fakekid to remove a snotty post (on which there were dozens of comments) from Facebook about a girl in her class who hadn’t done what Morgan wanted with their English project. Here’s what I told her: “Honey, you need to take that down. You don’t post mean things about people on the internet. It makes them feel bad and stirs up trouble that there’s no need for. It makes you a mean, nasty troll. If you have a problem with what she did, you tell her privately in person at school, in a Facebook chat or private message, or you call her. You’re almost 18, and you can’t solve problems anymore like you’re still in junior high. If you can’t work it out with her and you think your Facebook friends need to know, then fine, it’s your call, but even then keep your tone appropriate, watch your language, and focus on facts, not your emotions about her. Be fair.” Huh.
  • Ryan Imel saying in one breath, “It’s news! I have to report it!” (paraphrase) and then in another claiming that he’s just a fan/blogger and should not be held to journalistic standards like fact-checking and providing balanced coverage. Maybe WPCandy should change, “Keep up with WordPress news!” to, “Keep up with WordPress blog posts!” Without all this pot-stirring, maybe Justin and I could have talked and come to an understanding without creating a divisive community uproar. Maybe he’d have convinced us that the guidelines should be changed. We’ll never know now, will we?
  • Jeffr0 jumping in and stirring things even more. The “news site or fan blogging?” issue used to come up with Jeffr0 back before WPCandy totally eclipsed WPTavern. What’s funny is that when this WPCandy story came up, I totally starting thinking about how Jeff had really tried to take that balancing act seriously back in the day once it was pointed out to him that people were treating WPTavern like a news source. Then, the revived WP Weekly podcast of 9/9 did the same thing Ryan had done and stirred the pot without bothering to ask for a counterpoint to Justin’s version of events/the situation, and pretty much threw me under the bus. In that podcast, Jeff also got mixed up and referred to Andrea’s comment as Amanda’s. Since Andrea is from WordCamp Central and is the policy communicator/enforcer with WC organizers, and Amanda is a former WC organizer but not affiliated with WC Central, this was a notable error. When I talked to Jeff on Skype on 9/12 and pointed this out, he acknowledged not being clear on who was who, yet he’d sounded pretty confident when he was talking about [her] in the podcast. That’s just plain irreponsible.
  • People who have traditionally acted like my friends running with the accusations in this story and adding fuel to the fire. These people all have me on Skype, have my phone number, etc., and could have picked this bone with me directly, and possibly helped make the situation better instead of more dramatically in conflict. I am pretty sad to realize that these people are probably not really my friends, but have just acted that way because it was useful or expedient. In the past, when negative gossip about me reached my ears and was labeled as having originated with them, I had chalked it up to miscommunications, lack of context, and all the other things that go into assuming the best about people rather than the worst. In this case, that tendency has apparently led me to think that some people are nicer and/or more professional than they really are. That bums me out like crazy.

So thanks, Justin, Ryan, Jeff, and the rest of the people who publicly hung me out to dry without talking to me directly first. Your efforts in creating a kinder, gentler, more friendly WordPress community… er, not so much this time.

Things that didn’t piss me off:

  • People thinking the guideline about giveaways was not a good one. We won’t all have the same ideas about what makes a good guideline. Most people are basing their opinions on their own WordCamp experiences and those of their friends. We (Matt, me, Andrea) base it on experience with all the WordCamps, interacting with all the organizers, and getting feedback from attendees all over the world. When we disagree with people, it’s usually because we have different starting points. If we have a conversation and you at least listen to where we’re coming from and you still disagree, fine. But if you’re just posting about what biased control-freak idiots we are without even asking why we made certain rules and what kind of situations engendered them, that’s just lame. As a former boss of mine would have said, “You’re a mixer.” (Because you like to stir things up.) If you want to be a community leader, act like one, and get all the facts before rallying people to a conflict/cause. It’s like we have our own WordPress Tea Party or something. The guidelines will continually evolve to make the WordCamp name ever more trustworthy, and making constructive suggestions on ways to improve them is very welcome. Making accusations about how we/I just want to ruin everyone else’s fun/business/life … not so much.
  • People using “Jane” and “the Foundation” interchangeably. Though the people who said it wasn’t accurate had a point, I can see why it made sense to others. I have been pretty much the only person doing stuff under the Foundation name, and whether the direction is coming from Matt or me is generally not stated. If anyone would bother to ask before making a federal case out of things, I’d be more than happy to explain the genesis of each decision and action. Now that Andrea is in the mix, and when we get a little further with some of the Foundation-based initiatives I have planned, there will be more people involved in things, but if all you have to go on is the (rarely-updated) WPF blog, yeah, why wouldn’t someone think it’s all me? I should update that blog more often, it just hasn’t been a priority compared to other stuff. At any time, any of the people who are now clamoring about lack of Foundation transparency could have pinged me to ask a question or suggest I post an update. As it happens I had 3 half-written WPF blog post drafts with news and updates I’d just never gotten around to finishing, and a prompt would have reminded me to get them up there.

So, yeah. This whole thing has made me feel personally attacked, has made me feel deceived by people I thought were friends (or least something akin to friendly colleagues), made me bleach half my head and now I look like a crazy person (though that one is on me), and caused serious distraction from what should have been my top priority, which is getting the new features and UI ready for 3.3 freeze.**

Next post will focus on why the guidelines for sponsorships are what they are and where they come from, and will reply to some of the comments, accusations, and suggestions raised in the WPCandy thread comments. It may be a couple of days, though, because I’m at WordCamp Portland and I’ve got the kid with me and Daryl and I have to finish 3 new features and then test them with WCPDX attendees and I have to stay on top of this weekend’s pre-freeze trac marathon and I need be helpful and friendly to all the people I meet at WCPDX and I still need to stay on top of email and WP help requests and everything else that doesn’t stop happening when a handful of people decide it’s been too long since they made a festival of declaring me the root of all evil. Have a nice weekend!

* I’ll be paying the mortgage on the townhouse she just bought so that she can afford to move closer to the family (esp. the grandkids) now that she’s retiring in early October.

** I notice that the people having such a good time proclaiming their concern for the community on WPCandy are not helping get WordPress 3.3 ready, despite the fact that surely the community’s greatest concern is the improvement of the software they all have in common?

Posted in Community, Personal | 15 Comments

Forking, Woo, Free Agency, Automattic, and Me: Or, a Simple Comment that Became a Really Long Post

I started writing this as a comment on Mika’s post on The Morality of Forking, but I think if you start to pass two paragraphs, it’s time to write a post instead. So here it is.

Open source (and specifically WordPress) developers have a lot of options. When Daniel Pink wrote Free Agent Nation back in 2002, the idea that people could just go from good opportunity to better opportunity for no reason other than wanting to (more money/flexibility/peanut butter cups/new challenges/location/people/whatever) was still pretty revolutionary. These days, in our community, it’s the norm. Netflix has a good presentation on how to keep the employees you value. If people feel valued, they don’t leave. We accept less money, shitty hours, and even snotty customers when we feel good about we’re doing. Just look at any startup or non-profit job.

I have not been following the Woo/Jigo thing at all (WCSF and 3.3 have kept me busy lately), but if the description in Mika’s article is accurate about the steps that were taken, I don’t think Woo pulled a dick move at all. I’m the first to hop into the forums (in ninja mode, as Mika says) and tell off someone who wants to redistribute a paid plugin for free without adding any value to it — I do the whole legal-but-a-dick-move spiel. In this case, though, it sounds like they tried to do the right thing.

E-commerce and WordPress seem like such a natural fit, and yet nothing out there is great. Period. I love all the guys who develop these plugins (and I’ve tried most of them) but without exception there are always issues. Spaghetti code, bad UI, weak features… e-commerce plugins have seemed to have some kind of inverse version of the project triangle forever.

Will forking Jigoshop and hiring the developers who got it to its current state catapult Woo to the exalted position of “the ones who got it right”? Maybe. And if that happens then Jigowatt will be super bummed. Maybe not, though. Maybe Jigowatt’s vision is better and they’ll wind up with new developers who share that vision and they’ll come out on top after all. And if Woo just wanted to fork something, they might have been better off forking Shopp — it has a more consistent UI, less complex code, and better reporting. Then again, Jigoshop creates fewer tables and uses custom post types. Hm, but WP e-Commerce also uses CPTs, has way better reporting, and creates fewer tables than Shopp. This is the problem — everyone is doing something better than the others, but no one is hitting all the targets yet.* Presumably Woo chose Jigoshop because they thought it was the best option for a starting point. Either way, whoever gets there first will win the hearts of the community and a ton of new business. (Side note: this is why I think a core commerce plugin that sets up how the WP core developers would recommend doing it and that independent devs could both contribute to and build on top of would be phenomenal and is actually the right answer.)

So why take the developers? Obviously they liked their work, if they were trying to buy it. At Automattic, when we’ve acquired a product/company, it’s always been about the team that made the product more than the product itself. Isn’t that kind of the underlying ethos behind most of the open source models that are successful (both as purveyor and as buyer): don’t pay for code, pay for people?

So I don’t think it was dick move. Good developers/employees are a hot commodity, and you need to give them something they don’t want to lose if you want them to stick around. If Woo looked better to them, it’s none of our business — that’s a decision for them and their families. The devs shouldn’t be judged for deciding to take a new opportunity, and Woo shouldn’t be judged for offering one. It’s not as if they hadn’t made their interest pretty plain, if there had already been acquisition discussions — it’s not the same as secretly trying to poach employees from friends/partners/fellow businesses while pretending to have no interest in them (which would be a total dick move). If Woo doesn’t deliver on whatever promise they’re banking on, the devs will find another opportunity. That’s how it works.

I reviewed Free Agent Nation for the now-defunct New Architect magazine (which had just changed its name from Web Techniques) in 2002 and noted that it resonated with me because I averaged a new job a year as I moved from opportunity to opportunity once the current one stopped being good enough to keep me around. When Matt hired me for Automattic, during the conversation about salary I said I didn’t give a crap about stock options because I’d never stayed at a job long enough for them to matter. We also agreed on an unofficial “easy out clause” that would protect our friendship for the inevitable day when I left after the challenge was gone, got sick of the people, or just plain felt like a change and decided to either go to grad school or run off and be a baker in a beachside cafe in Mexico (or he got sick of me), which was estimated to occur within or around the one-year mark.

Three years later, I’m still at Automattic and am not looking. I have never stayed at one job this long. EVER. It’s not money — though Automattic salaries are competitive, I made more at both of my last two jobs. I don’t run out of challenges, I respect both my co-workers and the company leadership, and Automattic works hard to make sure my work environment is awesome. They even make me take days off when I work too hard. I mean, come on.

Mika mentioned in her post that Nacin almost went to Woo before Matt “snatched him up.” She forgot to mention that John James Jacoby was consulting on WP e-Commerce for Instinct before Matt snapped him up, too. Dan has made a few comments of friendly resentment to me about this, but J-trip had already applied to Automattic when he started consulting for them and had informed Dan of this in advance — I can’t help it if sometimes our hiring process takes a long time (we like to be really sure the fit is perfect, which is part of why we have such low turnover). Even if J-trip hadn’t applied to us first, though, would it have been wrong to hire someone who wanted to be here? We should not be putting the success of companies before the happiness of the people who work for them (and make them successful in the first place). Corporations are not people, as much as the US Congress would like to believe it, and in our community, a company name is only as good as the people behind it. I want every WordPress developer/worker to be ultra happy, wherever that may be. I would believe this even if it meant Woo hiring away every single person from Automattic, and they are welcome to try (though Matt it would probably think it was rude to poach without giving us a heads up for the sake of the relationship, and he’d be right).** Who knows, a maybe a year from now Jigowatt will nab people from Woo. Or StudioPress will swipe iThemes guys. Or WebDev Studios will hire CubicTwo peeps. You get the picture. The thing is, if people are “swipable,” they’re not where they belong anyway, so no one should begrudge a change.

By the way? Automattic is totally hiring badass developers and designers and happiness engineers (wordpress.com support), so if you are one of these and need a new challenge, you should apply. The team I lead, the dot org team, is a group of people that are donated to the open source project: me, Ryan Boren, Andrew Ozz, Daryl Koopersmith, Chelsea Otakan, and Andrea Middleton. Wouldn’t you like to be the next name on that list? I need a developer or two. Must love the GPL, coding according to WP standards, decisions instead of options, Doctor Who/Dr. Horrible/The Guild/Firefly/Portlandia/Buffy/Torchwood (more the old one)/Misfits/Eureka/Warehouse 13, kittehs, standardization, accessibility, watermelon mimosas, turtles (sea variety), Words with Friends/Scrabble/Bendywords, steampunk/paranormal novels, and good food and booze. A couple of those are negotiable. Well, maybe. Think you’re good enough and cool enough? You might be right! Apply.

* Credit where credit is due: John James Jacoby recently did a review of the top shopping cart/ticketing plugins at my request. We’ll be releasing his findings soon.

** Fair warning if you’re going to try to poach from Automattic all sneaky-like instead of right out in the open: we love each other here, and we’re likely to immediately turn around and tell the rest of the company. Better to be up front and transparent and just say, “We really need someone like so-and-so and would love to have them on our team if they’re interested,” than to skulk around like a headhunter. When employees are unhappy, skulking works. Not so much with us. We will mock you on our internal blogs. :)

Posted in Automattic, Community, WordPress | Tagged , , | 12 Comments

WCSF Shirt

I am super-grateful that Randall Munroe replied to my IRC ping and gave his permission for us to use an xkcd strip as the basis for the WordCamp San Francisco shirts. You all know how much I love working on WC shirt designs (2 years in NYC, 1 in Savannah), so working on this one was an extra treat. #867 was one of my first choices, since it’s conference based. I changed herpetologists and ornithologists to developers and bloggers, and wrote some replacement text. Chelsea Otakan turned the PNG into a vector and used a fan-created font to approximate the look of real xkcd text. Mike Ritchey at High Voltage Productions (formerly Lo-fi Custom), who works with a lot of WordCamps on custom shirt printing, did some adjusting to make sure it would be legible. They’re being printed right now on sweatshop-free tees in a cheerful, summery blue color. And here is the WCSF2011 shirt art:

WCSF 2011 shirt design

Posted in WordCamp | Tagged , | 24 Comments

A Typical Day

I am always busy. I don’t work from home, I live in my office. Many people know this and are patient with me as I slog through each day’s list, and kindly pester me (specifically, they pester me kindly, not aggressively or with accusations) if I don’t get to them quickly enough for their own deadlines. Other people get snotty, demanding, insulting, and rude (which makes me feel great about helping them at the expense of others, including myself). Because of this, my days bear little resemblance to what they once were when I was a designer and got to concentrate on a task until it was finished, then leave the office and go back to a personal life. These days it’s ping-pong-ping-pong from the time I get up until I go to sleep (often this means falling asleep with laptop in bed).

I recognize that this is my fault. I’m not good at saying no, and added to the Yankee work ethic that was drilled into me growing up (I was working 10+ hours/day when I was a nanny at 13), I wind up with too many projects and not enough time. Because I by default don’t feel okay about putting myself before others, this also means I work far too many hours, don’t take care of myself, don’t get enough sleep, and miss out on having fun the way I used to.

Being a workaholic in some cases is considered to be on the OCD spectrum, as obsessive thoughts about obligation can get in the way of stepping away from work. The next time you hear or say, “If you want to get something done, give it to the busiest person you know,” think about this, and think again.

About a month ago I kept track of what I did for a little more than 24 hours. Here’s that typical day.

9:30 am

  • Check emails that came in since 4am when I went to bed
  • Review updates from internal blogs that came in since 4am
  • Respond to WordCamp ABC re their proposed space and money request (day total: x3 so far)
  • Team blog – post request for individual updates
  • Go to .com to check out forums, get distracted by Freshly Pressed post on 10 best indie movies, take quick detour to wikipedia to look something up
  • Turn on pandora.com, put cookies in oven (cheater cookies, just throw pan in oven)
  • Chat with Matt re announcement post for distraction-free writing and ui update

10:45 am

  • Check email
  • Start en.blog post for DFW and UI
  • Take cookies out
  • Email Ben re new tmce icons
  • Write en.blog post for DFW and UI
  • Write .com ux notes to follow up on sometime
  • Continue with en.blog post for DFW and UI
  • Post to .com team blog re faves menu
  • Accept UPS package (keyboard)
  • Continue with en.blog post for DFW and UI
  • Press this on tools page review

12:05 pm

  • Continue with en.blog post for DFW and UI
  • Credits page review
  • Report core bug and help with troubleshooting (mark will fix)
  • More press this graphic investigation
  • More icons follow up
  • Talked to Andrew to get dfw fixes in before merge
  • Continue with en.blog post for DFW and UI
  • Discussion with needyish community member
  • Finish en.blog post for DFW and UI, send to Matt to review

1:21 pm

  • Email slog
  • Realize I should eat, go make bagel
  • Review WordCamp ABC budget, cry
  • Read oatmeal cartoon to perk up
  • New hire hr check
  • Update hr on team meetup status
  • UI group mtg
  • Core trac scrub in -dev
  • Team meetup date determination with team members (people who have new date conflicts every time make my life harder)
  • Talk to WordCamp DEF organizer, agree to fill speaker cxl with 3.2 preview
  • More trac scrub
  • Revise credits list

2:50 pm

  • Art for WordCamp DEF order shirts
  • Edited swag store page
  • Contacted past designer re permission
  • Kid got home; ate a tuna sandwich while she described school day and ate cookies
  • MT not around, so make shirt art
  • Order shirts and send art to printer

4:05 pm

  • Replied to iphone app trademark infringement issue

4:15 pm

  • Looked into team meetup rentals
  • Called Palomar group sales re wcsf housing, will have proposal by end of week
  • Looked at other sf hotels, decided to call travel agent to have her do it instead
  • Talk logos with MT, how to rep multiple brands brainstorm
  • Words with friends, made joey for 47 points
  • Discussed shirt printing instructions with Mike from lo-fi

5:20 pm

  • Ask hr about using travel agent, new hire follow up
  • Core leads chat re [sensitive community issue]
  • Pinged organizer, discussed WordCamp GHI
  • Start laundry
  • Make answer key for practice math exam, set kid to problem solving

6:15 pm

  • Go to pick up dinner

7:00 pm

  • Check email, see more kerfuffle over [sensitive community issue] in inbox, shake head, look at how long i’ve already been working today, shake head again
  • Discuss .com/3.2 beta merge timing with Ryan Boren
  • Feed kid, eat dinner
  • Put laundry in dryer

7:30 pm

  • Check email
  • Look at potential team meetup rentals, send reservation inquiries

8:00 pm

  • Check on kid’s math progress, do some planning with her, discuss weekend plans

8:15 pm

  • Investigate cost/time of flying vs. driving to WC DEF
  • Talk logistics for merch table in Raleigh w/Lori
  • Begin reservation process for team meetup housing
  • Write to flipkey to ask about price guarantees on rentals (b/c the one I want has diff prices posted)
  • Post to team blog with instructions for team members to look up flight prices for specific dates

9:15 pm

  • Researched alternate meetup housing (wp users!)
  • Sent availability inquiry
  • Email check, p2 comments

9:45 pm

  • Flight research for team meetup
  • Review team member A’s flight options
  • Chat with team member B about time management, rescuetime, and capes

10:00 pm

  • Download Glee (suck it, haters!)
  • Check email, Skype, decide I need a break
  • Eat cookie, drink iced tea
  • Watch Glee while answering emails

11:30 pm

2nd wind!

  • Email

11:45 pm

  • 3.2 feature chat with Michael Pick for launch video

12:30 am

  • Internet dies

1:30 am

  • Go to sleep

…………………………….

6:15 am

  • Slept late, gah! get up, make lunch for morgan, get her off to school

6:45 am

  • Email WordCamp JKL organizer re WC sponsorship eligibility rules
  • Email scrub
  • Read daily digests for a few team p2s
  • Review dfw support page
  • Comment on HE p2 re dfw page, social p2 re ui refresh
  • Identify must-dos for today: launch dfw, get .org guidelines up, reply pending WCs, style update work with Daryl, review/edit prev organizer survey, WC sponsorships, pending emails, write to the not-100%-GPL-WC-sponsor, book meetup travel, post call for WCSF speakers, draft WCSF sponsorship levels, contact potential WCSF speakers, nail down weekend WC travel logistics, food shopping, talk to Caitlin’s mom, confirm Morgan can stay with her, bring ibuprofen to school nurse for Morgan, cat food, clean house
  • Forward all emails to WC PHX relevant to AG complaint
  • Ping Matt to review dfw post, make a couple of corrections on readthrough

7:30 am

  • Review plugin requests for wc.org from WordCamp MNO
  • Note issue with plugin forums re author links
  • Need to write up rules of the road for plugin repo, add to list

7:45 am

  • Read tv gossip blog article about new Torchwood
  • Try to get laptop sound to work again, no dice

8:00 am

  • More email
  • Team travel costs review (all have been posted now)
  • New icon sprite handoff
  • Chat with Peter re commit access, review commit screen, posted sys request for list

8:40 am

  • Make and eat bagel
  • De-dread hair with massive amounts of leave-in conditioner, decide to cut off hair and donate it by WCSF
  • Iced tea and a cookie
  • Review [would-be WordCamp sponsor that is not 100% GPL] backstory
  • Order cat food, sugaring kit, SDHD cards
  • Call hotel re shirt shipments
  • Chat with Ryan Imel re inaccuracy of ‘split GPL’ term (‘split license’ is accurate)
  • Talk dfw post w/Matt
  • Email
  • WordCamp stuff
  • Shower
  • Email
  • Review local vs shipped-in speakers for WC DEF, purse lips

11:00 am

  • Look for errant WC app
  • Check on WordCamp trademark status
  • Get dressed
  • Sign FedEx, square readers arrived
  • Email

11:20 am

  • Move outside
  • Chat matt
  • Confirm merge plan w/Ryan
  • Go back inside, too bright
  • Reboot laptop on freeze

11:45 am

  • Make and eat tuna sandwich

12:00 pm

  • More WordCamp drama emails
  • WCSF Kimpton follow up — too spendy this year, cheaper hotels online
  • Find designer to do icon swap
  • Reserve team meetup cottages, post details
  • Core – icons, links, errors
  • Register for WCDEF
  • Forums issue

1:33 pm

  • Hands/wrists give out
  • Head to high school for student-teacher conference

Not good, right? I never get all the must-do items done in a day. I now have a new team member who is taking over all the WordCamp coordination, so that’s good, but there’s still more work to be done than can fit in a day without feeling massively behind. I’m going to be trying to cut back on the hours, and actually do things like clean my house that have gone ignored, as well as go back to having a personal life that includes more than driving the kid places.

So if I seem less available than I used to, that will be why. I’m also going to practice saying No. If I say no to you, please don’t be annoyed, and recognize that I’m doing it for my health. If I tell you no for something, I’ll at least try to point you toward someone better able to say yes.

Wish me luck!

Posted in Personal | Tagged , , | 12 Comments