[sticky entry] Sticky: Where to go for help!

May. 4th, 2009 01:51 am
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
If you're having a problem with Dreamwidth, please contact Support. I do regret that I can't reply to Dreamwidth-specific issues that are left as comments to this journal, in private message, or in email -- [staff profile] mark and I are tremendously swamped, and we need to redirect all issues, problems, and questions to the support board instead of trying to coordinate having reports in multiple places.

You can use the following categories:

Site Interface: If you're having a technical problem with Dreamwidth or you'd like to report a bug.
Importer: If you're having problems importing your content from another site.
Entries: If you're having problems with entries to your journal.
Styles: If you're having problems designing the look of your journal.

Account Payments: If you're having a problem with a payment for your account, or want to discuss bulk account creation. (Or, you can email accounts@dreamwidth.org.)
Terms of Service: If you believe another user has violated the Terms of Service, or would like clarification on any of the points of the Terms of Service. (Or, you can email abuse@dreamwidth.org.)
Feedback: If you'd like to provide an opinion on dreamwidth.org the service. (Or, you can email feedback@dreamwidth.org.)
Webmaster: If you need to contact site staff for any other reason. (Or, you can email webmaster@dreamwidth.org.)

You can make suggestions by using the site's Suggestions form, and read and review others' suggestions -- as well as talking over the best possible implementation -- in the [site community profile] dw_suggestions community!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
I've been talking a lot at conferences this year about impostor syndrome, and if you're interested, the Ada Initiative has transcribed and captioned the talk I gave at linux.conf.au this year:

Kicking Impostor Syndrome In The Head: Lessons from AdaCamp DC and SF

This is the shorter version of the talk -- I gave the longer one at Open Source Bridge last week, and the slides for that one can be found at Kicking Impostor Syndrome In The Head. (The longer talk also includes a section on how you can help people around you with their impostor syndrome, especially if you're in a position of social or technical authority or status in your group or project.) I'm pretty sure video of that talk will be available at some point, too!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
(I need to email in these photos so I can link them from the news post!)

Photo #1: us outside our server hosting company, complete with bonus @dive and @cheyinka and their adorable tiny human. Photo #2: sunset over the Capitol building, as seen from our hotel room balcony. Both photos by the lovely and talented @sarah.

ack, forgot the cut! )
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Happy fourth birthday, Dreamwidth.

Good Lord, it feels like it's either been absolutely honking forever, or that we just started yesterday. Occasionally at the same time.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
applications for adacamp san francisco (june 8-9) are now open!

adacamp is a two-day unconference for supporters of women in open technology and culture. if you are significantly female-identified (*) and into open stuff -- not just programming or technical matters, but any form of open data, open government, fan and remix culture, open education, open source, open technology, and so on -- you should really consider attending.

there's childcare available, too, if that would be a limiting factor! and there's (limited) travel funding you can apply for. the conference itself is "by invitation", but the invitation process is basically to make sure people have a basic level of awareness of feminism in order to get the most out of things and not be detrimental to the group as a whole; it's not there to exclude people who aren't "technical enough" (if you're reading this on the internet right now, you're technical enough). so if you're interested in hanging out for a weekend and talking with other women about open technology and culture, you should apply.

i went to adacamp dc and it was an awesome experience being around so many smart, interesting, engaging women. i'm not 100% sure yet whether or not i'm going to be able to go to this one, but if you can, you really should.

(*) based on feedback and requests, the main adacamp sf programming is restricted to women and people who are significantly female-identified. there's a parallel allies track for people of all other genders, being held on june 8. the ada initiative uses an inclusive definition of female-identified: if you identify primarily or significantly as a woman, you can register for the main track.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
it's been ages and ages since the last time i did a bug count post! (no, really, ages. the last one was over a year ago, eep!)

but i'm in the middle of working through a whole fuckton of bugzilla cleanup this week, and i thought i'd post a count at the midpoint. the "all open" numbers look scary, but they're down considerably from where we started at the beginning of the week, so i am ridiculously pleased!

All open: 897
All assigned: 181
All unassigned: 716
Bugs only: 572
Enhancements only: 325
All resolved: 4025
All resolved-fixed: 3462

(some of the queries have been removed, since we've moved to github for submitting patches, so the queries are no longer meaningful!)

of particular note: we have passed 4000 resolved bugs, and are approaching 3500 resolved/fixed!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Thank you all for attending my talk! The slides are downloadable from Slideshare:

Web Accessibility for the 21st Century

This is the table of contents for the resource package, which contains:

  • 31 Quick Techniques to Make Your Site More Accessible: a text-only version of the 31 tips provided in the talk itself, so you don't have to mess around with transcribing them.

  • Further Reading: A list of resources, further reading, and Useful Sites.

  • Writing Useful Alt Text: An exercise for you to practice with! A handful of images, each presented with two different bits of text. Write the alt text for each image in each context.

  • Writing Alt Text: Answers (and not-answers): My own answers to that exercise, and my reasoning for why -- these aren't definitive, because there are many different ways of doing it, but you can compare my answers with your own.

  • Inaccessible (and annoying) Websites: A discussion in [site community profile] dw_accessibility where people name off examples of particularly inaccessible websites (and why they're inaccessible). I wound up not having time to fit that into this tutorial, but you can browse the comments and see the examples!

  • Assistive Tech (semi-) Poll: A while back, we wound up asking people to comment in [site community profile] dw_accessibility with information about what assistive technology they use. The answers are fascinating, and demonstrate the wide variety of assistive tech out there.

  • And [site community profile] dw_accessibility in general: this is the community for our accessibility project team, and you can read through both the general accessibility-related discussions and also see some examples of how we solicit accessibility-related feedback and design features to be as accessible as possible.


If you have any questions that I didn't answer in the talk, or want to share some resources (or success stories after you go implement some of the advice!) please do comment!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
These are the 31 points I covered in the talk, for ease of copy/pasting and not having to dig through and transcribe my slides! For those who haven't seen the talk, they'll probably be pretty understandable anyway, but you still need to see the talk to get the nuance. I am happy to come deliver this talk, or the longer version I cut this down from, to your local group ;)

31 Quick Techniques to Make Your Site More Accessible )
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Here's a list of a whole bunch of resources, tools, and information for you to do more reading about accessibility and accessible design. (This was done with the help of the [site community profile] dw_accessibility community, who are a bunch of very lovely people!)

They're roughly divided into categories, more or less.

If there's something I've missed, or another tool or resource you're fond of, leave a comment! (If you're commenting anonymously, or logged in with OpenID, you can leave links in the comments, but they'll be rewritten to display as bolded text followed by bare URLs: that's an antispam feature. I'll try to come through behind people and turn them into clickable links. Or you could create a Dreamwidth account!)

Further Reading )
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Here are my answers to the Writing Alt Text exercise, and my reasoning for why on each.

You may disagree with me on many or any of the image descriptions! That's okay (and expected). As I said in the talk, many of these questions don't have a single answer, or have multiple possible answers, and people will disagree as to which one is better or best. So if you're worried because your answer isn't close to mine, that's fine: think about your reasoning, consider the basic principles and the desired goal, and work from there.

And, of course, if anybody wants to share their answers because they like theirs better than mine, feel free!

My answers to the alt text exercise )
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Writing good alt text is an art, not a science. The same image can be described in different ways based on context, flow, and what aspects of the image you want to call to a listener's attention. The WHAT WG HTML Living Standard "4.8.1.1. Requirements for providing text to act as an alternative for images" has a collection of requirements for alt text, and WebAIM has a whole article on Appropriate Use of Alternative Text -- both of these are very useful resources! But it still takes practice to get really good at it.

So, let's practice, and see ways in which the same image in two different contexts might make you want to write the alt text differently.

Each of these sample images has two sets of text next to it: one formally-written piece (unless otherwise cited, it's from a relevant Wikipedia article), and a more casually-written sample that might be a blog post in which the image would appear.

Your task, should you choose to accept it, is to write relevant and useful alt text for the image in each context. Don't just look at the image and think in your head "oh, I'd do blah blah": actually write it out!

As you work, think about the differences in how you write the alt text in each context, and how different uses of the image make you want to call attention to different aspects of the image contents.

At the bottom of the page is a link to my version of the answers, with a brief explanation for each. I will reiterate that my answer is not necessarily everyone's answer! There are many, many ways to write alt text, and many people disagree as to which is the most useful.

Screenreader users: please note that I'm just using the alt text provided by Flickr's "get this HTML code" here, to avoid giving too many clues. Non-screenreader users: please don't just take Flickr's "get this HTML code" without altering it; it defaults to the title of the picture, which is usually fairly unhelpful for descriptive purposes!

I've turned comments off on this particular post, but they're open on the "answers" page, and if people would like to discuss their choices (or why they don't agree with my choices), feel free.

Take the alt-text practice exercise! )
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Using site search with certain keywords to find search-engine-ranking-boosting spammers, and getting distracted because the keywords also turn up interesting-looking fic.

HOORAY!

Aug. 30th, 2012 04:53 pm
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Both [staff profile] mark and I got notice this afternoon that our proposed tutorials have been accepted for LinuxConf Australia in Canberra in January!

I will be giving (with help from [personal profile] deborah on the development thereof, but alas, she had a conflict with the conference itself) a one and a half hour tutorial called "Beyond Alt Text: What Every Project Should Know About Accessibility":

working description of tutorial! )

I'm totally looking forward to it. We went to LCA a few years back (the year it was held in Wellington) and it was a fabulous conference full of fabulous people talking about smart and fabulous things. I'm looking forward to being able to return.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Awesomeness: load the Latest Things page and see so many posts that are like "I'm testing out email posting so I can try the first draft of file hosting!" We released this way because it was soooo much easier (seriously, "upload from file" is a pain in the goddamn ass to do right and really easily to do badly) but the side effect of spotlighting one of our lesser-known features is kind of great.

Less awesomeness: a full week of trying to shoehorn myself into a 24-hour sleep schedule means that despite having woken up at a reasonable-ish time today, I am sitting here WIDE AWAKE and the alarm will be going off in four and a half hours for breakfast, last bits of packing, and heading to the airport :(

Not awesome at all: having to go back home and leaving behind all the amazing energy, enthusiasm, and excitement that comes from having ten people all sitting in a room hacking on DW. We are totally doing this again sometime.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
...with having so many of our contributors here for OSCON is that we have to balance "going to talks and conference sessions to learn awesome things" with "hunkering down on the couches and tables in the hotel lobby and hacking on awesome things".

(Things that people are or have been hacking on this week: image hosting; HTML5/jQuery/responsive-design etc mobile page; "fuzzy" feed matching so there will be fewer duplicate feed accounts and allowing for a "did you mean?" suggestion when creating a feed; extra icon add-ons; the bookmarks/memories overhaul; HTML5, responsive-design site skin; "clean up ALLLLLL the tiny bugs!" (that would be me!); backend/site-reliability stuff; upgrading the code to run on Perl 5.14 ... I'm pretty sure I'm missing stuff, too. Heh.)
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
"We made it so you could switch [the $[ variable] back on, but you had to DECLARE your SINS."

...I love listening to Damien Conway's talks so much, hee.

Other good ones: talking about upgrading Perl and then trying to run scripts that weren't running under 'strict', since 5.12 and onward assumes 'use strict' by default (EDIT: when you declare the version with 'use', I forgot to specify that): "If you upgrade to [Perl 5.12], your program may do unexpected things. That's just a delayed form of justice."

"Why didn't Perl have a println? Pascal has a println!"

"Every time I write a say, I get this little ... BURST of happiness!"

"A lot of people want to tear [smartmatching] down and put up this little tiny effigy in place of it."

"Let's be honest here, Perl only DWIMs if you're Larry Wall."

"You can just use braces instead, but that's two extra characters of typing. With a shift key. Unacceptable."

"How is this different than 'use constant'? 'use constant' is an abomination before God, and this isn't."

"Unlike C++, Perl6 is not sent from hell itself."
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Kind of awesome: I'm at Peter Scott's "Perl: The First Three Days" tutorial at OSCON, and the room is like 85% Macs. *g*

I picked this tutorial because despite knowing a ton of useful intermediate and advanced Perl stuff, I am kind of laughably bad at some of the basics, and I have hit the point where the lack of the basics is totally messing with me. So I figure, I will keep taking intro stuff until I figure out data types and context properly :)

Also! We are having a BOF on diversity in open source, on Wednesday at 8PM. (I forget what room, but it's on the signup board.) If you are here at OSCON, come hang out with us and we'll talk about all kinds of stuff.

OSCON!

Jul. 13th, 2012 10:06 pm
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
So, is anybody else going to be at OSCON next week? We're bringing a whole DW contingent!
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
I wanted to specifically post congratulations to Jon "maddog" Hall (executive director of Linux International), who announced this week in his Linux Pro Magazine column, in honor of the 100th anniversary of Alan Turing's birth, that he is gay. It's humbling to realize that someone who is no more than twice my age was born in a time when such an announcement would have been unthinkable, where today the majority's reaction is usually more along the lines of "oh? Okay then!"

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-hide-it-too-hard kind of way, and that lunch was the first time either of them discussed being queer at work in any way other than to carefully-selected friends.

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 [personal profile] 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. :)
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Readers of the Geek Feminism blog will have already seen that this week was a disheartening week to be a woman in tech, with not one but at least three instances of being reminded that to a nonzero number of people in the tech world, I am valued more for my bra size than for my brain size. This is not, sadly, unusual, but this time on the Sexism Merry-Go-Round, I was pleased to see the script play out a little differently in one of those cases.

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.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Occasionally (when I remember to) I take a snapshot of the site's statistics for future reference and comparison (in the future we'll have historical stats as well as present-day stats -- the data's there, there's just no pretty frontend for the comparisons yet). I was doing that tonight, and I figured, for shits and giggles it might be neat to present a "then and now" comparison.

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! )
Page generated Apr. 25th, 2014 02:23 am
Powered by Dreamwidth Studios