Tag Archives: opw

Open Help, part 1

Open Help is on this weekend in Cincinnati. We’re half way through the two conference days and have seen very interesting presentations from Jorge Castro about helping users help users, Janet Swisher on sprints and Rich Bowen about writing better help, which led to interesting discussions during the panel and open floor.

Happy Jimmimico

The trip over to the US was a bit long as Dave and I were delayed at almost every point of the way, but we finally arrived in Cincinnati after a 22 hour trip to a lovely reception at Via Vite on Fountain Square.

The conference itself has a very relaxed atmosphere. With around 40 attendees, it is possible to meet everyone and it is rather nice to have a fluid schedule. There are people here from a range of different projects, including Drupal, the Wikimedia Foundation and WordPress, including four people who previously participated in the OPW. Unfortunately, Sindhu and Aruna, the Documentation Team interns from round 5 and 6, could not make it because they have exams right now, but I am hoping to meet them at GUADEC.

Open Help Conference & Sprints

Updating Vinagre help

A couple of months after I finished rewriting the Vinagre help in Mallard, I have had to come back to it because the user interface changed quite significantly (and will continue to change), so some of the help pages needed rewriting/removing/reordering. Dave also noticed that the online version of the help was rather old and Damned Lies showed more translations of the help than actually existed.

One bug and a fix later, the online version should always be up-to-date now. Damned Lies has also been updated (the bug was fixed very quickly by Claude Paroz) which was followed by a surge of translations! More are always welcome 🙂

Vinagre help

Vinagre help

Help and help again

I based my application for the Outreach Program on a DocBook to Mallard port of the Vinagre help.. suffice to say, it wasn’t that great. So, I have now fixed it up, with some pointers from Shaun, to be more topic-oriented and less *ahem* technical.

I have since started working on Brasero. This time, I have an advantage of starting with some notes for what should be included in the help, which were written up at the Open Help Conference brainstorming sprint. While writing instructions on how to use the application is not particularly challenging, I am finding that writing in a way which is “not technical” and understandable by users who would look at the help quite difficult, because terms which I take for granted are often misunderstood or not known by the audience I should be aiming at.. which is probably not anyone reading this blog. But the biggest problem I have come across is that Brasero could do with some love and care. I won’t count the number of ways of making it crash that I have managed to find, but with 229 open bugs, it is in need of some maintenance.

I have not been able to find a good guide on the style of the writing needed for user help, so I have been using the Empathy help as an example, with Shaun giving me feedback as I go along.

I am… still me

..or at least I was, last time I looked in the mirror. Most people call me Kat. Those who don’t know me, attempt to use my full name. They often have fun trying to pronounce it right.

I have been a GNOME user for almost four and a half years. It wasn’t a voluntary decision, I came home one day to find that my laptop had this weird thing, that I had never seen before, installed on it. It took some time getting used to, and so did the ups and breakages downs. Feels like it’s now time for me to break fix GNOME a bit, which is why I am about to start (and if I am correct, I am the last to do so) one of GNOME’s Outreach Programs for Women: I will be working on documentation (with Shaun McCance keeping me in line).

Why last to start? Because I have just come back from an awesome holiday in the US.