In 2001 or so, I was working for Prudential Insurance & Financial, and the department I worked for had a "lunch and learn" type event to celebrate Pride month -- one of those "have a talk with real live gay people to talk about what it's like being gay" forms of diversity training. It was organized by one of the VPs of the department, a woman about 20 years older than I was who'd been living with her "roommate" for years, and one of the guys in the project management team, a guy about a decade older than me. Both of them were out in the not-really-out-but-not-really-trying-to-
I'd already been out at work, mostly because I am so very, very, very bad at staying in the closet and tended even then to out myself accidentally all the time. (Bruce Byfield contacted me yesterday for permission to name me in his article on LGBTQ presence in the open source world that stemmed from maddog's announcement, saying he knew some people were out to friends/family but not more publicly. I thanked him for his consideration but reassured him that people on Mars probably know I'm a dyke. *g*) Even so, and even though we were in a room full of other queer people and straight people whose presence at the (voluntary and self-selected) discussion group meant they were pretty far along the path towards ally-hood, I remember how ridiculously hard it was to actually open my mouth in front of a room full of my coworkers and peers and say, yeah, I'm a lesbian. I wouldn't have thought it would be, until I was halfway through a point I was making and realized I was shaking like a leaf.
Today, only a little more than a decade later, I don't have any problem at all calling sarah "my wife" in front of other people -- at work (and it's not just because my 'coworkers' now are people I'm also good friends with), at conferences, during doctor appointments, to people I'm talking with casually. Part of it is definitely because I live in a relatively liberal area of the US -- there are certainly parts of this country I'd be a little more careful and countries where I wouldn't mention it at all, and unfortunately that 'relatively' does still need to be in there because there are still many, many things that Maryland and Marylanders fail at -- and part of it is definitely because I've grown into a lot more confidence as I've gotten older. But a huge, huge part of it is changing societal attitudes and the increasing visibility of queerness.
Things aren't perfect. They aren't going to be perfect for a long time. But they are so, so much better, and every voice standing up to say "I'm so-and-so and I'm gay" helps to turn that tide.
Congratulations on being able to make your announcement, maddog. And thank you for doing it. :)
Long story short, the company Sqoot advertised a hackathon in extremely sexist terms, and a number of the hackathon's sponsors acted swiftly and decisively to express their displeasure. When the issue was not resolved to their satisfaction, they then pulled their sponsorship, with statements denouncing Sqoot's actions. Examples include:
* Cloudmine, a company providing backend for mobile apps, pulled their sponsorship and posted About Sexism in Tech (which I felt was an excellent post, and could probably be used as a textbook example of how to write an apology post);
* Heroku, a cloud application platform, investigated and pulled their sponsorship;
* Apigee, a data platform for mobile apps, pulled their sponsorship;
* MongoHQ, a hosted platform for using MongoDB, began with discussion and moved to pulling their sponsorship
Local area user groups also made strong statements against Sqoot's actions, which were also great to hear.
It seems like every time this happens -- and shit like this keeps fucking happening -- the discussion gets derailed into an endless series of explanations about why shit like this really is a problem and why exhortations for women to lighten up are never an appropriate response. Today, I am pleased to see so many voices challenging "brogrammer" culture and speaking up to say that casual sexism and the marketing of women as a "perk" of a hackathon is Not Okay.
I'm also really, really encouraged at how many of those comments are coming from men. It's easy, sometimes, for me to forget that there are so many male allies out there who are just as frustrated by this crap as I am. Thank you to all the awesome men out there who have my back, and thank you to the companies who refused to even passively support this kind of behavior.
Behind the cut: a table with comparison figures for three time periods, as close to one year apart as I have the data.
( Dreamwidth: Then and now! )
(Bug 8: Add ability to subscribe to a particular user's posts to a community; patched by sophie.)
We have 25 remaining double-digit bugs, some of which are metabugs/admin bugs that won't/can't be resolved and most of which are really involved epic projects I logged into Bugzilla off my initial "shit I'd love to do someday but probably we won't get to for a while" list I was keeping back during the initial brainstorming phase -- and I'm sure some of them could probably be closed now because they don't mesh with the direction the site developed, but I haven't been through Bugzilla on a "close bugs that are no longer relevant" run in a while -- but we now officially have knocked out all the single-digit bugs. I think this is very nifty. :)
Also of the nifty: we have 3369 bugs RESOLVED since we started using Bugzilla as a bugtracker in mid-January of 2009 (before then it was all just in our heads and in a few spreadsheets while we figured out how we wanted to set up bug tracking); we have 2975 bugs RESOLVED/FIXED. (The difference being: any time a bug is closed at all, it's counted as RESOLVED; RESOLVED/FIXED is for things where we explicitly made a change, while the others include such statuses as DUPLICATE, LATER, WONTFIX, and INVALID.) Some of those were massive sweeping changes; some of them were one-line fixes. I love every single one of them, because it means we're constantly trying to make things better. :)
I love working on Dreamwidth, because whenever I get discouraged or demoralized or just plain down -- which happens a lot; it's not easy working at home, in relative isolation, with nobody to re-energize yourself with face to face, and AIM and irc doesn't always work -- I can go and read all the awesome comments of encouragement and love, and it reminds me that there are people using this thing that we made and they are using it in awesome ways, and it reminds me that there are people out there who really get what we're trying to do with this whole thing and they appreciate all the time we take to get the little things right, and no matter how little a particular change is, it will always turn out to be that one thing that's been annoying the hell out of someone, and basically WE HAVE THE BEST USERS EVER. THE END. I LOVE YOU ALL. A LOT. THANK YOU FOR BEING FUCKING AWESOME.
(That all having been said, redpyre has now officially won dw_news commenting forever and ever with this comment.)
Not only is this an incredibly amazing rate of development, it's so awesome to open the Bugzilla queries for all resolved and all resolved/fixed (which are the ones that were specifically resolved via a patch, not resolved because they were duplicate/invalid/not something we wanted to do/fixed by proxy with another patch, etc, and which is at 2656 bugs) and see so many different names -- many of whom I know had never programmed in Perl before joining us, or who had never programmed at all.
I firmly believe we have the best darn development team of any project out there -- and we have a lot of fun while we're doing it. Y'all rock, people. Pat yourselves on the back!
This prompted a series of questions about fashions in which people code that are not suitable for public viewing. Therefore, I am making a poll:
At home, I regularly code:
Without pants on
In my underwear
While drinking (alcohol)
While drinking (highly caffeinated drinks)
With a cat draped over me
With a dog draped over me
In some other fashion not fit for public viewing
(kjwcode proposes the next step: pair programming in pajamas.)
( This is something I care about a lot. )
I am disappointed in Google for taking such a simplistic, reductionist approach to the problem of online abuse, harassment, and reputation. They can do better.
OUR LITTLE BABY IS GROWING UP.
On the one hand, I can't believe it's been two years already; it feels like just yesterday that mark and I were staring at each other and hyperventilating over it almost being the moment while janinedog and sarah looked on tolerantly and tried to calm us down. On the other hand, it feels like I've been doing this for years.
Building Dreamwidth has never been easy, but so far, it has been one of the, if not the, most rewarding, meaningful, and happiness-producing things I've done in my life. I get all emotional whenever I start thinking about it (or talking about it, or writing about it), because, just ... *hands* I LOVE YOU GUYS. ALL OF YOU. THAT IS ALL.
( a very small excerpt from our job logs )
1) LJ is still under wicked load due to the DDoS they're experiencing. This can mean the site timing out when we try to contact them for the data.
2) Every time LJ is inaccessable when the importer tries to hit it, the job goes on pause to retry again in a few seconds. It retries up to five times before giving up.
3) There are lots and lots and lots of people trying to import right now. (This means that imports from sites other than LJ will be slow too, because they enter the queue behind all the LJ import jobs.)
If I had to guess, I'd say the existing import queue as it stands right this very minute would take at least 24 hours to clear, because of a combination of the three above items. Please, please, please be patient!
The answer is at once both very simple and very complicated: we've spent the past six months or so concentrating on paying down our technical debt.
( So, what's technical debt, anyway? )