Journalists don't understand Wikipedia sometimes

This morning I saw some pissed-off twitters that led me to articles about Wikipedia’s sexist bias. Always up for a little early morning smash-the-patriarchy outrage, and well aware of some of the clusterfucks that often play out in Wikipedia admin pages, I forged onwards and read the articles, flaring my nostrils in anticipation. In Wikpedia’s sexism towards female novelists Amanda Filippachi points out that many women tagged with Category: American women novelists aren’t tagged with Category: American novelists. She named several examples. Katie Mcdonough from Salon picked up on this, with Wikipedia moves women to American Women Novelists Category Leaves Men in American Novelists.

Even the most cursory googling shows that this is not a very accurate spin. For example look at Amy Tan, Donna Tartt, and Harper Lee, who are named by Filippachi as missing from American novelists. Here is the Donna Tartt article’s history page going back the last 500 edits to 2004. Tartt was never listed as being in Category: American novelist, not because “Wikipedia is sexist” but because no one thought to put that down amid the hundreds of small edits that incrementally improved the article. Until today when someone added “American novelists” to her page, in virtuous activist response to injustice (which I respect, actually). “Category: American women novelists” was never on Tartt’s page.

Okay, how about Amy Tan. The last 500 edits for Amy Tan’s page go back to 2008. Category:American women novelists was not ever on Tan’s page, but American novelists was added today.

Harper Lee’s history, on the other hand, shows an edit on Feb. 21 removing American novelists and adding American women novelists. If you look at the user who made that edit, they often edit categories, and occasionally makes disputed judgement calls, but they appear to be acting alone and from the pattern of their edits, they do many types of edits in several areas, rather than waltzing around sexist-ly removing women from the category of generic human beings, or even novelists.

Just from these three samples, it does not seem that there is any particular movement among a group of Wikipedia editors to remove women from the “novelists” category and put them in a special women category instead. I would say that the general leaning, rather, is to stop people who would like to label women writers as women writers *in addition* to labeling them as writers, claiming there is no need for Category: American women writers at all and that it is evidence of bias to identify them by gender.

When I add writers to Wikpedia because I love their work or find their lives interesting and significant I often am unsure what the trends in categorization currently are. I may add them as Women writers and also American novelists based on looking at a similar writer’s article. If some of the potential categories aren’t there I hope someone will add them.

mmme_hardy on Twitter pointed out to me immediately that the discussion on this topic amongst Wikipedia editors takes place here: Categories for discussion. There is a proposal here to merge “Category:American women novelists” into “Category: American novelists”. The consensus there is to merge the articles, with some people (including me) mentioning the option to merge and keep the category. Merging the category would remove “Category: American women novelists” from many writers’ pages. That also means the page that lists all the pages in Category: American women novelists would no longer exist.

Thus, a well-meaning attempt to include women in the main categorization for American novelists (where many of them were never listed in the first place) may result in women writers no longer being easily identifiable to those who might want to find them. For example if you are looking for Caribbean women writers and they have all been merged into Caribbean writers that might not be a desirable outcome! Filippache mentionsEdwige Danticat being ‘plucked from “Haitian Novelists” and dumped into “Haitian Women Novelists.”’ But I don’t see that plucking happening from the history! Where did that happen!?

Joanna Russ in How to Suppress Women’s Writing lists miscategorization as one of the ways that women’s work is disappeared over time. In this case I am a bit annoyed at the facile reporting that does not seem to take into account the complexity of how information gets added to Wikipedia. If someone can point me to a Category decision from the past where a bunch of editors agreed to remove women en masse from American novelists and put them in American women novelists, go for it, I would appreciate the help in understanding this.

It is much more often the reverse and it would not be too hard to come up with examples — where someone works rather hard on creating a category for Women activists or American anarchist women and then a bunch of other (often male!) editors step in and say that that is sexist and unnecessary and “ghettoizing”. What would be so hard… or so wrong… about listing writers or other people by gender, race, ethnicity or other factor that people who care about identities and identification may want to browse by? Librarians certainly catalogue writers and works that way, and it is extremely useful! I think that the backlash against identity politics is evident here. Yes Wikipedia editors and admins often have systemic bias. In this case the story has been told in an inaccurate way (that I don’t even have time to debunk thoroughly — I am neglecting my day job right now to write this!) and in a way that both discredits reports of actual systemic and individual bias and that harms the visibility of women writers while trying to help that visibility. The sexist thing we should be up in arms about isn’t labelling women as women! It’s the efforts to delete entire categories (like Haitian women writers, for example) because someone has decided that that meta-information is unnecessary “ghettoization”…. the false belief that we should or can be “gender-blind”, “color-blind”, and so on.

The particular moment of charm

I spent some time this week going through my book wishlist, requesting them from the library in a new surge of conviction that THIS TIME I won’t just eat the very same cost of the books in library fines as I would if I had bought them. But since that still leaves me with the need for e-books on my phone to fall asleep on, I bought a couple of new books. Lately my book recs have come from particular blogging friends (oursin, wiredferret, seelight) and my friend Bryony in England (though I am ignoring her obsession with Icelandic mystery and action novels).

And tonight in the bath I was reading the book I bought, Throne of the Crescent Moon, by Saladin Ahmed. For a while it felt a bit stumbly and awkward, but lovely anyway. It was easy to let go of whatever hangups bugged me about the writing style and see where the book and its charming characters were going. The lion-girl was a good sign! Sometimes I wait while reading for myself to open up to the experience or the ride and have to let go of… of something. (That’s an important feeling, hard to convey, which people may describe as taking a while to get into, but which I think is often a lack of context on the reader’s part. ) Without practicing that letting-go, omg, the things I would have missed in so many excellent books! And details obviously references someone would make sense of were slipping by, that I knew I was missing,. Rughali = ghali = egyptian? Where is the Soo Republic – Soo = Somalia? Missing it all over the place. Tantalizing! Someone else will get it right off and like it. Good. Anyway, as I was in mid-story in Throne of the Crescent Moon, there was a moment where the book completely charmed me and I trusted the story. That’s what I want to describe!

book cover of throne of the crescent moon

The point of view changes frequently, from Adoulla the ghul-hunter (who feels a bit like the main character so far), to Raseed, his assistant, then to the lion-girl. How the characters think of each other and their relationships is important shifting territory. Adoulla’s friend Litaz and her husband Dawoud, alkhemists from another land, are helping him in a crisis. Litaz is thinking about her (locked/twisted) hair and how her husband affectionately teases her about it at times and how his people do their hair in his country (which is in like West Africa somewhere. Unlike how they do it in her homeland (which is in East Africa). And I was keenly appreciating that they were outsiders in the city yet they weren’t just lumped together like “the alkhemists from Africa”. Then…

Upon waking a few hours later, Litaz made more tea and Adoulla thanked her for it as if she had saved his mother’s life. He was a bit less inconsolable after his rest, grim planning clearly giving him purpose.

“That jackal-thing that calls itself Mouw Awa, and its mysterious ‘blessed friend’—they must be stopped. Somewhere out there is a ghulmaker more powerful than any I’ve ever faced. I fear for our city,” Adoulla said. He took a long, messy slurp of tea and wiped the excess from his beard.

Your city, my friend, not ours, some resentful part of her protested. She’d lived in and loved Dhamsawaat for decades now, but the older she grew the more she pined to return to the Soo Republic. This city had given her meaningful work and more exciting experiences than she could count. But it was in this dirty city that her child had died. It was in this too-crowded city that her husband had grown older than his years. She did not want to die saving this place — not without having seen home again.

She spoke none of this, of course. And she sat complacently as Dawoud said, “Whatever help you need from us is yours, brother-of-mine. Whatever this is you are facing, you will not face it alone.” For a long while, the three of them sat sipping tea…

That was great! And so rare! Here we are in a fantasy novel and someone has thought subtly of her own feelings and motivations. The city Adoullah loves is, to Litaz, also the (exciting, cool, but…) dirty city where her child died. We are treated to a person who helps her friend loyally and is about to be heroic, though she has mixed feelings about it all, and doesn’t see the situation the way he does or the way her husband does.

The “of course”, thrown in offhand, on how she didn’t speak up to discuss this, was nicely done. She doesn’t behave in an out of place woman-fighting-patriarchy way (as so many annoying perky princesses unfortunately and pluckily and fakely do) and she is in control of her situation. And suddenly all the characters seemed to bloom as different from each other and as people, on their own tracks, rather than little representations of “people” who (as if their labor of existence were ultimately exploited by a capitalist machine) serve either the story or the Hero. I hope this conveys something of what charmed me. And I wish that charm wasn’t so rare.

Now to read on. I hope Litaz doesn’t die saving the city, and gets to go back to the Soo Republic and have a nice life being the best alkhemist ever.

It was a nice day but a tiring day; I had a very annoying bus driver and was filled with rage and sadness and confusion on the way to work (about which more later); I put it behind me, I worked hard, had a really nice lunch with co-workers, worked more, rode the bus home while working some more, thought fondly of my friends, made dinner for Oblomovka’s daughter (he is in Hong Kong for the circumvention conference), saw her and Taren off to the Exploratorium, listened to all the Perfume Genius songs twice indulging in a sort of luxurious solitary melancholy (instead of reading aloud and responsibly telling a small human to brush her teeth and put her pajamas on and get in bed twentyeleventy times), and read my friend Gina’s book draft (the Perfume Genius songs were in honor of her book, to go with it). I look forward extremely to reading more and the later versions.

File a bug: the missing manual, now with unicorns

At countless conference talks I have heard standard advice on “how to get involved in an open source project”. It goes something like this:

Step 1. File a bug!
Step 2. Submit a patch! (repeat steps 1 and 2 for a while)
Step 3. Now you are ready to write some new features and stuff! Fly and be free!

I always thought that was interesting because it is an attempt to reassure people that you don’t have to leap into immediate coding. Just file a bug, that is the first step. This results in people coming into projects and wondering vaguely how to find bugs.

Part of what I want to do as bugmaster for Mozilla is to put in another step — look at the bugs already reported, since there are a squizillion of them, and see what you can do to improve the meta information of those bugs.

Today on Planet Mozilla I noticed some really good advice from Jason Smith on how to find bugs: WebRTC testing: Try out conversat.io and file bugs. It is really sensible and practical. Jason’s blog has a few posts like this that advise focus in a particular area, like WebRTC or Desktop web apps, by incorporating use of those tools in your daily life. Our “get involved in open source” sequence now looks more like this,

Step 1. Find some feature that could use testing.
Step 2. Figure out how to use it regularly.
Step 3. Use it.
Step 4. Encounter behavior you think is a bug.
Step 5. FILE A BUG (BUT HOW?)

There is a lot of background knowledge necessary to actually file a bug in the complicated system that is bugzilla.mozilla.org (or BMO).

So let’s take the WebRTC example. Say you’ve followed Jason’s advice, used conversat.io for a while, and found A BUG. Jason helpfully provides a link directly into Bugzilla to the enter_bug form, with the Product and Component pre-filled out to be for a bug with WebRTC (the component) and Core (the product.) Bugs in BMO are categorized according to Product, like Firefox Desktop, Firefox for Android, FirefoxOS, Thunderbird, etc. “Core” is the product for the code that is shared between many other products. If you were looking to file a bug with WebRTC from scratch you would probably not know which product to file it under, though you have to choose one. So it’s great that Jason gives a link to the right product and component!

But wait. There is so much more background, or context, to understand. You don’t have to, but it is very good to understand it!

First of all you have to have a bugzilla account for the link to work properly. If you do that, you will be a new bugzilla user, and some of the bug entry forms will look different to you — you’ll be automatically directed to a “guided bug entry form” which is broken into several steps, rather than the form that shows you the whole “advanced view” with several dozen fields and dropdown menus.

Second, how about looking at the list of all the components in the Core product. This is a good part of the background knowledge – a little piece of the map or geography of Bugzilla. As you can see, there are a lot of components that are part of Core. Scrolling down to the WebRTC bit, you can see that there are several sub categories: WebRTC, WebRTC:Audio/Video, WebRTC:Networking, and WebRTC:Signaling. Click on the general WebRTC component to see a list of open WebRTC bugs. This is where your geography lesson gets useful.

Right now there are 113 open bugs for WebRTC. You might look over them simply to get an idea of what kinds of bugs others have found. More about this later!

The important thing at this moment is: Is your bug already reported? Depending on how many bugs there are in this list, and your levels of interest and patience, you might want to either quickly read through the summaries (the title of the bug) or do a search down the page for words that might be in the bug you’re about to file.

If you find something in that list that you think is your bug, take a closer look at it. Read it and the comments and try to understand what they’re talking about. If it is the same as your bug, you may want to leave a comment describing what you saw happen.

But let’s say you don’t find your bug on that list. Aha! Here we use the File a bug link from the original blog post, link to file a bug with WebRTC. If you are me, or a user of Bugzilla who has made more than 25 edits or comments to bugs, you will see the advanced bug entry form, which is huge (you can see it from space) and looks like this:

Enter bug webrtc advanced

If you are a relatively new user of Bugzilla, you’ll come first to a guided entry form, broken into several screens. (At any point, you can switch to the advanced entry form with a link at the bottom of the page, if clicking through multiple screens annoys you.) The first screen for guided bug entry would normally be for selecting the product and component. Since you have these already chosen in Jason’s convenient link, you start on Screen 2, where you can enter the summary for your bug. In this case I am reporting a sort of unicorn invasion:

Enterbug webrtc screen2

After you enter a summary you will see a list pop up underneath the summary field, of bugs that may be similar. It is worth reading through those to see if anyone else has reported unicorns invading their conversat.io screens in Firefox. In this case, definitely not.

Enterbug webrtc screen2 list

Since no one else has reported this bug, I click the “My issue is not listed” button, and advance to screen 3, which suggests how I can describe my actions or steps to reproduce the issue, exactly what happened that I think is a bug, and what I think should have happened instead.

Enter bug screen3 unicorn jpg

Great, we have filed a bug! Back to that list of “how to contribute to an open source project”:

Step 1. Find some feature that could use testing.
Step 2. Figure out how to use it regularly.
Step 3. Use it.
Step 4. Encounter behavior you think is a bug.
Step 4.5 Make a bugzilla.mozilla.org account.
Step 4.6 Confirm it with the email confirmation.
Step 4.7 Log in to bugzilla.mozilla.org.
Step 5. FILE A BUG (which we now know how to do!!!)

But wait, there’s more — or there can be if you want to get your bearings on that map of Bugzilla. Take a look back at the list of all the general open WebRTC bugs. What can we understand from this list?

As I look over the current list it is pretty mysterious. From the language in the summaries, I would guess some of the bugs are notes by the development team for their own to-do list, and some of them look like bugs discovered by general users of the software. My first impulse is to sort the page a few different ways to see what that reveals. Sorting by Status shows the UNCONFIRMED bugs at the top and the NEW bugs listed just underneath. There is one titled getUserMedia freeze all system that isn’t confirmed yet and may be a good example.

Here is an interesting one, No event when remote peer disappeared. My view of this bug is going to be different from yours, if you are new to Bugzilla, because I have more magic powers, ie, canconfirm and editbugs permissions, as well as some extra admin stuff. There is a lot of stuff on the page. It’s extremely “busy” with text! You have to learn to skim it and parse it mentally so that you can see and notice the stuff that is important to you at the moment. Here is what this bug looks like for a new Bugzilla user.

Example webrtc bug2

What I can see from reading this bug is that there is at least one person actively looking at newly filed bugs, triaging them, and working on the project. And in fact as I click around and read more of the bugs for WebRTC I can see Jason is actively engaged with most of them, which is not a big surprise since he is blogging about the subject.

Jason’s blog looks like a quite useful place to find out areas that welcome testers and bug-finders. You can also look at the QMO quality assurance and testing pages which explain how to run nightly builds and participate in QA’s bug test and triage days.

My bigger point here, though, is that to start contributing to an open source project, aside from reporting one-off bugs you accidentally discover, it is super helpful to learn the landscape of the project. Adopt the project and poke around to learn about it. If you are reporting a bug, look at the other bugs. Look at who is commenting and working on those bugs. Join their IRC channel and read their wiki pages and (usually more formal than the wiki pages…) developer documentation. Or simply google the project to learn more about what’s going on with it. In this case I found that conversat.io is quite new and was developed partly to show off what WebRTC is and what it can do.

It was really apparent, from my morning of poking around, how much transparency there is at Mozilla, and the amazing technical depths you can get to from half a day’s reading and bug surfing. As a society we really have yet to realize the implications for education and educational institutions. It is a major cultural shift I am happy to be part of.

Noisebridge! Best thing ever!

On April 2nd and 3rd I am going to spend several hours teaching at least 70 high school physics students how to solder and some alluring information about contributing to open source software!

They are doing a project to design and build a solar home. If you know anything about electronics or solar energy cells please join us a do some teaching!

rowan learning to solder

I spent $250 of my own money to buy a crapload of little LED kits so they can have a conveniently teachable soldering project – that is how much I love Noisebridge, and geeky things, and teaching, and non hierarchical anarchist/mutualist community spaces!

I am thinking of the Hackability group that meets at Noisebridge to fix and mod their wheelchairs and mobility scooters! We take over a classroom, gank all the workshop tools, and get on the floor where none of us think it is weird that we scoot and crawl and roll across the floor to pick up a screwdriver just out of reach, laughing at all this solidarity! We bravely dismantle our cyborg leg-wheels and bolt them on again covered with LED lights, jazzed up with arduinos to measure battery voltage, then roll on out into the town!

potentiometer and its lever

And the fierce, fun feminist hacker hive that is a chaotic unstructured network of strength and curiosity and information sharing, that stretches from Noisebridge to sudo room and LOLSpace, and beyond!

Claudia

We need more paying affiliate members — we need you! We need your cold, hard bitcoins or your cash!

I am thinking of all the people I’ve given tours to who come in from out of town and are all starry-eyed and inspired, who meet people and go to Python and Ruby and web dev and Linux classes and eat the strange productions from the Vegan Hackers, the laptops that people at Noisebridge fix and give away, the cameraderie I always find there and the fabulous energy of young people just moving to San Francisco to do a startup or find some kind of freedom or empowerment and hope to find at least part of it at this weird ever changing junkyard coffeehouse-feeling co-op workshop. We made this place that isn’t anything like any other place and it can also be YOURS. Meddle in it!f

surface mount soldering

SUBSCRIBE to support Noisebridge’s rent, its freely provided wifi, its bins of electronics parts that anyone can rummage through and pillage, its beautiful giant robot, its classrooms and electricity, its ADA-compliant bathroom custom built specially by Noisebridge folk, its elevator, its devotion to support accessibility for all, all its copies of keys that I and others have distributed as Keys to the City, the library of excellent technical books, well used and loved and read!

Hacker moms visiting Noisebridge

Our rent went up this year, and our people’s job security and income went down. It’s exactly at that point, when the economy is hard on us all, that we need collectives and co-ops and hackerspaces. We have to band together in the best ways we can come up with.

me and maria zaghi at noisebridge

People visit Noisebridge and like it so much that they move to the Bay Area. They come to Noisebridge for education, to find peers and mentors, to teach, and sometimes to find as close as they can get to home and family when they are hackers down on their luck.

Noisebridge - looking west

They come to speak in public for the first time at 5 minutes of fame. They sound a little odd and then they turn out to be geniuses. They drudge to clean the floors and toilets and scrub the kitchen and buy toilet paper, doing the unglamorous physical domestic labor of maintaining this place that’s used heavily 24 hours a day 7 days a week.

noisebridge

We do good work together as best we can. We give a lot to our community! We give access, tools, skills, time, belief, trust, fantastic spectacles, beauty and humor and art. With a sense of wonder and playfulness people walk in and look around – I see it on their faces – like they have just had a million new ideas churn around in their heads – So many possibilities and they know they can be part of it.

Noisebridge table

circuit hacking monday

And we need widespread, ongoing support.

Donate, sign up for a monthly subscription, be a fabulous affiliate of Noisebridge!

If you can spare any, we need your exclamation points as I have used most of them in this post!!

Noisebridge tea cart

Shorter posts with more worklogs and book reviews

While I love to go on at length and be thorough sometimes it’s been stopping me from recording interesting stuff lately. I’ll be at a conference and take great notes, which years ago I would have posted unedited. Now I tend to procrastinate posting about something “until I can do justice to it” which often results in “never”. Have I posted about Kiwicon? NO! Argh. Fuck that, I need to just post.

So I’m resolving to write more frequently about smaller topics. They may not turn into comprehensive book reviews but at least there will be something here.

mozilla roof

At work I am organizing a Bugzilla bug day and preparing to go to Toronto next week for a community building work week.

Not-at-work, lots of people are rumbling about wanting another feminist hackers meeting and a hackability wheelchair/access device hack day. I have Noisebridge stuff going on and AdaCamp is coming up in June. I forgot to actually sign up for WisCon panels but in theory am going to WisCon. There is a lot of “event to-do list” stuff here!

Notable books I read in the last few days: The Brontës Went to Woolworth’s by Rachel Ferguson, which was fantastic; The Diary of Elizabeth Pepys by Dale Spender, which I adored but which was very depressing as you can imagine if you have read Pepys; and Japanese Inn (my boring-book for bedtime) by Oliver Statler, which functioned perfectly as a boring-book and which was good but very colonialish and patronizing in the way you might expect from a book from 1960 and which if you are not trying to fall asleep at night would just make you wonder why you are bothering and realize it would be better to read some actual work of Japanese history or a primary source by one of the people referred to. Though I did enjoy reading Isabella Bird’s travels.

I am feeling more energy lately and less pain, which I attribute to my 2 months of Enbrel injections and perhaps also Tramadol, which is great as an occasional painkiller.

Here is a photo of the fabulous glistening Minecraft block cake I made for Milo’s 13th birthday party (which was at the musee mecanique again)

Minecraft cake

There really need to be square cupcake pans (well, cubical) Maybe there already are! Then it would be easy to make little Minecraft block cakes and frost them all different colors and build a hilarious structure which could be easily (if stickily) disassembled.

Feminist hacker lounge at PyCon

PyCon gave non-profit booth space to The Ada Initiative and Mozilla for our Feminist Hacker Lounge and it turned out just awesome. Though it was only a 10×10 booth space lined with beanbags we met and hung out with lots of fantastic people. Lukas, Val, Mary and I roamed the exhibit halls, went to talks, and handed out stickers. We were right next to the PyLadies booth, across from CodeChix, and diagonally across from Women Who Code. So that made for good synergy. We also sent emissaries across the exhibit hall to trade stickers with the Lady Coders.

ada init booth

In the afternoon on Friday we had some larger discussions but mostly people just wanted to talk with each other in small groups. One of the things people said most often was how welcoming various Python communities had been to them and how comfortable they felt. That was great to hear.

We talked about hackerspaces and projects like Planeteria and whatever we have going in github and our jobs. We talked about stuff we want to do at AdaCamp in June. And Lukas and I got into some weird installer problems in trying to deploy bz-tools with stackato on paas.allizom.org. We told some horror stories and a lot of jokes. I painted my nails “VT100” green with “Tux” black stripes. At one point I watched two math nerds realize they shared a “pure math” background and saw them both get ecstatic expressions on their faces, scream, and hug… And obviously we all spent a lot of time just staring at our laptops while lying there on the floor.

ada initiative

One thing I talked about to people…. brainstorming ideas for a project that I thought of when I read harthur’s post after some code of hers got harshly criticized. (She has a followup post: Open Source Rocks which is also very good.) As I was thinking about students looking for open source projects to contribute too, I wondered if we could offer github projects owned by women to women — in a similar way to how Code Triage works. You could add your repo to the tool and then other women might browse through by language or in some other way, find it, and pick it to contribute to (perhaps getting a periodic email invitation with a bug to fix.)

This would be easier and slicker than many “mentoring”, even peer mentoring, match-up tools I have seen over the years.

(The obvious problem, of course, is that adding your repo to this tool may just get you threats, rude propostions, and nasty hate mail. But so does everything else that identifies us as female — and that just can’t stop us.)

I also spent some time talking with a very nice guy about his teenage daughter’s ventures into hackerdom. She has been doing electronics and robotics projects since she was in preschool. He recommended this amazing looking camp for gifted math students to girls and young women looking for their peers. They are Epsilon Camp for age 8 – 11, Math Path for middle school students, and Math Camp for high school.

It was great to be at PyCon and meet so many amazing people! I really appreciated that the PyCon organizers gave us some free passes which we gave out to some Feminist HackerHive women who would not otherwise have been able to go. Yay PyCon! And much thanks to Mozilla for providing the beanbags and portable whiteboard.

feminist hacker lounge

Screen reader and accessibility bug day

Tomorrow Mozilla is hosting a screen reader and general accessibility bug day.

Len Burns and I have invited screen reader users of Firefox and other Mozilla products to join us in sorting through existing accessibility bugs. Some folks from the Mozilla Accessibility team will be on hand to talk with us.

I’m pretty sure we will also collect some new bugs along the way!

I hope that people will make new connections, and that we can attract a wider accessibility bugmaster team to do ongoing work with Mozilla’s existing developers and a11y experts.

The screen reader landscape for web access is fairly complicated. For example, here are the Firefox Gecko docs for Windows accessibility vendors which explain the relationship between the DOM tree and Microsoft’s accessibility API. Common screen reader software includes NVDA, Window-Eyes, JAWS, and Orca.

Orca2 sm

If you would like a quick overview of common web access issues, look through Aaron Leventhal’s presentation. I like it because he includes some political dimensions and context for accessibility.

So far, the “bugmaster” bug days have been combined with QA’s efforts. I’m hoping to also hold focused bug days like this one, in cooperation with various teams across Mozilla. As we gather more templates for bug managing and triage, I hope we’ll coalesce bugmaster teams with expertise in particular areas. And we can repeat topic-focused bug days periodically.

If you are interested in web accessibility or if you use a screen reader, please drop by on Tuesday and say hello in the #accessibility channel on irc.mozilla.org.

You can also add the name you go by, your irc handle, your contact infomation, or anything else you use to identify yourself, on the wiki page for the bug day under Participants: https://wiki.mozilla.org/Bugmasters/Bug_days/a11y#Participants .

The goals of the screen reader bug day are to improve everyone’s experience of Firefox and other Mozilla tools. We would like for everyone to be able to access the web smoothly. Through collecting more information on accessibility bugs, we hope to connect committed technical users with accessibility developers, and make our community better and more powerful. Our bugmaster work should help to make developers’ work easier. That way they can spend more time fixing stuff.

If you have any questions or feedback, please feel free to email me at lhenry@mozilla.org.

In setting up this event I tried to make sure that the tools we are using are as accessible as possible. Etherpad, which Mozilla teams often use for bug triage events, is not useable for screen readers. The wiki.mozilla.org pages seem readable though editing may be more of a challenge. IRC feels like our best bet for good communication. I also went through about 100 screen-reader-related bugs and emailed the bug reporters and commenters to send them invitations to participate.

Len is particularly interested in developing a plan for Thunderbird and screen reader vendors. If you share this interest I recommend joining the mailing list tb-planning.

Here is what Len has to say on Thunderbird accessibility:

It is complicated, because the issues are really between the two major screen reader vendors and Mozilla. Meaning, that the solution would need to be a cooperative one. Because the screen reader vendors perceive, right or wrong, that little more than security bugs are being updated in Thunderbird, they do not seem terribly motivated. I am not quite sure where to take it.

Unless I could convince the vendors that solving these issues are worthy of their time, I am a bit stuck.

I would definitely be willing to raise the specifics with both vendors if I could give them some reason to encourage a belief that there is a mutual interest in improving things. When I have raised several with GW Micro I hear things like: This has been filed for over a year with no response, and the like.

Those of us using screen readers are currently in quite a pickle regarding email. The choices are quite limited. A lot of us have been using Thunderbird for some time, but when things reach a point where you are spending too much time trying to send a simple email, something must give.

I can also tell you that what finally tipped me were problems between the composition screen, and other open apps on-screen. If I were going to compose an email in TBird right now, I would have to be sure that Skype was minimized, MirandaIM was minimized, etc. If I did not, I would be likely to encounter a range of strange behaviors in the edit window such as being unable to read back the text I am writing, inaability to use my backspace, format distortion, and more.

What has been slowing me down on these issues was a lack of knowing avenues of pursuit. The challenge will be convincing vendors that investing time is a benefit. My position is that I am not sure, but, we have a good chance of catalyzing and contributing to change and possible strengthened relationships.

Len has been a professional system administrator, coder and web accessibility consultant since the Internet was a kinder and gentler place. He makes his living these days free lancing as a web accessibility consultant for colleges and universities and coding the back-end glue of web sites for small to mid-sized businesses.

Len FB profile

Thanks to Len for his insights on web dev, email, and access in the last couple of weeks as well as his outreach efforts to talk with vendors, software users, and developers!

Bugzilla hijinks, Tuesday March 5

Tomorrow evening (Pacific time) the bugzilla.mozilla.org and IT folks will be moving BMO to a new infrastructure and upgrading to Bugzilla 4.2.

No bugzilla cartoon

I’ll be up on the 7th floor of the SF office with Shyam and probably others. I know a few comunity contributors will be showing up on IRC around 8pm PST to help test during deployment so if you’d like to participate, let me know!

Earlier on Tuesday, before the outage, there will be a QA-run Firefox unconfirmed bugs day. This is a good event for people new to bugzilla and bug triage! Create a bugzilla.mozilla.org account for yourself and come introduce yourself on irc.mozilla.org on the #qa or #bugmasters channels.

I plan on going through all the Mac bugs that I’m able to, to try to replicate them and add any useful information to the bugs. Right now there are 85 unconfirmed Firefox bugs that were first reported in the last week. That number might be different tomorrow obviously!

I find it very useful in Bugzilla when I get a link to a search like this one, to click “Edit Search” at the very bottom right of the page. From that, I can see what options created that result. And I can narrow the search down further or build something useful for myself, and then save it in my saved searches. Now I have a nice search for just the recent bugs reported for Firefox on MacOSX. I mention this mainly because it took me a while to notice the “Edit Search” link — until then, I was trying to deconstruct and add to the parameters in the URL by hand.

At 8:30pm the Bay Lights are going to come on: a dynamic light show decorating the whole north part of the San Francisco Bay Bridge. I’m hoping to get some awesome photos of the lit-up bridge from the Mozilla office roof. It looks basically like thousands of blinky christmas lights all over the bridge along with some sort of giant arduino mastermind program. It is nice that the bridge will be known for something other than “3rd most destroyed bridge in disaster movies throughout the ages”.

CodeTriage looks very cool!

André Klapper showed me a nifty tool called CodeTriage yesterday. I really like its simplicity, its friendliness, and what it conveys about open source bug management.

Once you sign into CodeTriage with your github account you can browse code repositories by programming language. I picked flask and codetriage repos to follow.

Codetriage homescreen

Codetriage then sends me a daily email with link to a random issue from each repo, asking me to triage the bug.

Codetriage email sample

This makes it beautifully clear that, with only a little time and thought, without any particular programming skill, anyone can contribute useful work to an open source project. Each email comes with a little pep talk about the goals of triage:

* Help share the weight of maintaining a project
* Minimize un-needed issues
* Prevent stale issues
* Encourage productive communication
* Teach good citizenship
* To become a better coder

Short, sweet, and to the point. The how-to-triage part of the email is not specific to any programming language or project, yet, or to the bug itself, but is an overview of the concepts of improving the quality of any bug.

It gave me a nice feeling that I had been helpful, when I tried it this morning.

André and I were talking excitedly all afternoon about shaping the idea of bugmastering (or triage) for our communities. Bug management is a great way for contributors to become familiar with a project and ease into development or become experts in QA. It’s a good evolution of a definite role in open source ecosystems.

So CodeTriage gets across exactly what I want to convey to aspiring Mozilla bugmasters. I feel super inspired to build something to hook into bugzilla.mozilla.org with a similarly lovely interface. Thanks to Richard Schneeman for creating CodeTriage!

Two especially nice days

What a gorgeous day! I could feel the vitamins shining into me! While it may be boring to read I would like to record how much I enjoyed the last two days back in SF and getting over my jet lag. I was in bed all weekend wondering if I had ruined myself forever and would never get to do anything nice again. Though it was so cosy to be home, to have Danny to talk everything over with, and to have Milo here and a cat to cuddle. Then . . . of course . . . by Tuesday and after a lot of sleep, everything was fine again. I feel lucky (and a little silly for panicking).

Yesterday Val came over and we worked from my house with several pots of tea and conversations in between our meetings and moments of fierce concentration. Yatima walked in around 4:30 to join us. It was like a fabulous dream come true to have my house full of feminist friends who can just drop in. At some point Val and I headed off to dinner at Balompie with Danny. Then to the Noisebridge meeting and elections. I shelved some books. Thus ends my dutiful stint on the Noisebridge board, where the main job is to practice not wielding authority.

Today, hazelbroom picked me up at 8:30 after dropping off her son at school. She hoisted my scooter for me and left us outside Haus on 24th street. I adore 24th street with its trees shading the sidewalks, the million Precita Eyes murals, the bakeries, excellent mercaditos, new bookstores, and lively community life. It makes me happy just to be there. Worked really well from Haus, which had peaceful music and rows of somberly dressed laptop people with big headphones and knit caps, facing each other across the room, with the light from the street streaming in. Outside a group of guys in orange vests were digging up the street and I wished that someone would courteously bring them coffee and pastries on a tv tray. Usually the window tables in Haus are taken first but today no one seemed to want to be on whichever side of the aquarium windows it may be with the guys up to their knees in red clay dirt glassed off from the cleanness of the insides. I enjoyed my chocolate croissant and cappucinino and felt all fired up as I triaged some Firefox bugs, wrote email, and planned a screen reader bug day.

Discolandia

Then I beetled over to Garfield pool. The entry guy recognized me which was nice but guilt-inducing since I have not done any pool/swimming physical therapy since October. There is a new push button door opener, which is very exciting and awesome for me in the scooter! And the women’s bathroom, which previously was like one’s nightmare of a state hospital circa 1955 where they hose you off or whatever, with no door to the “accessible” stall and many other horrors, and I had planned to bring a shower curtain to at least have privacy to pee — now it is all fixed up with a higher toilet seat, handrails, large stall you can get a powerchair into, and bench. They took out 2 sinks and just totally fixed the problems. So great! While I don’t know what else they did in the renovations, everything looked a little less skanky, and all the things I was emailing the SF parks and rec dept about last year are fixed.

I strapped on some arm floaties and rode the hydraulic lift into the pool. It was reasonably warm!!! My upper back and neck are kind of “stuck” right now, one of those things where I can’t look all the way up and to the right, a bit hunchy-over . . . so I was moving very cautiously. I also didn’t want to over do my activity on my first day back in the pool. So it was gentle thrashing about in the 5 foot deep area like slow water treading while leaning back and a bit of walking back and forth and doing leg lifts.

Got to chatting with a guy who asked me if I had back problems and told me about his. He has to have some vertebrae fused and is worried about it.

As we gently flailed I felt I was making a really nice friend and now look forward to hanging out with him in the pool some more. He is a garbage collector in my neighborhood (but not on my street) and lives over near the pool. We talked about places we have traveled (him: south africa, greece, italy, mexico, me: london, vienna, beijing, greece, mexico) and places we want to travel. He told me about his ranch in the country and his grown children and the young visiting Sicilians who came to stay temporarily and then became renters in his house, and what his village was like where he came from in Mexico (near Guadelajara, with lots of river and underground water for wells and springs, near ocean, very relaxing, good restaurants, nothing happening ever) And how his co-worker retired there by him buying his aunt’s place by the river which has a spring-fed swimming pool and now all the children and people love him because he helps everyone with his truck. We agreed about some of the things that are nice in life. We agreed on our love of pick up trucks (I had one for 13 years.)

I love a fellow extrovert . . . With the distraction of talking I stayed in the pool the full 50 minutes. It really helped to get a ride there, too.

Then went to hazelbroom’s house nearby where she gave me an amazing massage. The stuck bit of my back is still stuck. (I am icing it.) And she fed me the most amazing lunch. I love my friends. Trout (?) on rice with broccoli and then jars of kim chi and japanese seaweed seasoning and soy sauce and pickled things. delish. I got to hold her son’s new hamster. She invited me to ride out to the VA hospital with her where I could work while she went in to have a physical for her new job there.

Hammy2

I worked from her car on the way there (with 4G on my phone giving me internet) but paused to gawk at golden gate park and try to take pictures as we drove through. The pond was especially pretty. A guy was just bending over to sail his model sailboat. It was like some idyllic scene out of Stuart Little.

I felt so happy to be in the moving car in the warm sun, seeing trees and water and flowers and birds.

Va sunny liz

Got a hot chocolate from the VA canteen which had ramps to the outside picnic benches that overlook Land’s End with a great view of the golden gate (the opening of strait, not the bridge) and Marin headlands. There is a wheelchair accessible table right next to the Battle of the Bulge Memorial Trail. There was good wifi with 4G reception and it is a quiet, good place to work. I felt a little funny going through the VA on my scooter getting the “special smiles”. No – I was not blown up in combat. I did have a pretty great race with a guy in the parking lot who had a super huge scooter engine. He kicked my ass. It wasn’t as big of a scooter as the one I had in London though.

Showed the marine traffic site to hazelbroom when she was finished with her physical and came out to join me. She also loves cargo ships and we saw one come in in real life and on the screen.

Then she drove me past Sutro Baths. I wanted to believe that the lump we saw way down there was Sutro Sam the river otter who is eating all the goldfish in the pond. But now that I see the photo magnified on my screen sadly it is just a rock. I felt like it was the otter sleeping in the sun and was happy. Who needs reality. Anyway we knew he is there.

Sutrobaths sunset

As if this weren’t enough she then drove us down Irving and got us bubble tea. I had ginger milk tea with ENORMOUS tapioca bubbles. The ginger was so strong it made tears come to my eyes and cleared out my sinuses. I will sweat ginger for days. Cannot remember all the things we talked about on the way home but it was lovely.

If anyone in SF feels like giving me a ride to pretty much anywhere on a nice day, I am very portable, and as long as I have wifi, power, or decent phone data reception I can work from wherever. I spend so many days working from bed (because of pain or mobility issues) that a quiet outing on a good day cheers me up amazingly. I miss the times when I used to be able to drive all around town, going to random places off the map and settling myself in a good cafe or in a parking lot overlooking the beach.

Now am going to put in a little more work (collecting email addys of people who report screen reader issues in bugzilla, to invite them to a bug day). Danny will come home soon from the EFF office and tell me all about his day and my sister is going to drop by.

The only way this could be nicer is if the kids were here. Ada’s birthday party is this weekend so that’s going to be great, and then Milo’s party is in a couple of weeks. I plan on making him a cake that will be a block from Minecraft – three 9 by 9 pans should get me a block shape, chocolate cake, and then green frosting on top and chocolate frosting on the sides. I think that gummy worms in the layers will be a good touch. If I can find the frosting spray paint in varied colors maybe I can pixelate the cake surface.