How to Report Software Bugs / Thunderbird Bug Party

From TCU Wiki

Workshop: How to Report Software Bugs / Thunderbird Bug Party


Do you ever wish you could make the apps that protect your security and privacy less frustrating to use? Do you see bugs or bad translations, but don't know how to tell the software developers there's a problem? Come learn the tricks to writing a bug report that software developers will actually act on!

In this CKS, we will explore the essential elements of a bug report, compare bug reports to "feature requests" and "user stories," and cover different writing styles used by different development teams.

We will use Thunderbird as an example, and work as a community on Bugzilla, their bug reporting system, doing some of the "bug triage" that can encourage developers to focus on your most pressing issues. These are not just ways to advocate for better software: they're skills you can put on your resumé if you are developing your career in technology, too! But you don't have to be a "tech person" to write a great bug report: in fact, good writing and people skills are just as important.

// We will be hosting a 20 minute post-workshop networking exercise to allow folks to meet others who share their interest, and strengthen collaborations across various lines. Make sure to schedule in 20 minutes extra on your calendar, if you are interested in joining //

Gus Andrews is an independent usability consultant working on Thunderbird on a grant from Internews. She is also Digital Protection Editor at Front Line Defenders, working on updating Security in a Box. Previously, she worked on secure tools usability on a Simply Secure fellowship and before that at the Open Internet Tools Project. She has helped organize the Hackers On Planet Earth conference and was the producer of The Media Show, a video series on digital and media literacy.

>> Check out notes from other sessions here


Notes will be posted here