Documentation for open source projects can sometimes be daunting, but is always rewarding. This lecture describes the method for tackling an open source writing project, and provides information and tools on getting the job done in the easiest and best way possible.

1. Technical Writing for hoopy open source froods who really know where their towels are

2. Me

3. What is this documentation stuff anyway?

4. Why Document?

5. Who Does?

6. Users

7. Contributors

8. Developers

9. So ... What's in it for me?

11. Information Plan Content Specification Writing Translation & Production Review Release 5 Phase Model by JoAnn Hackos

12. Planning 10%

13. Content Specification (Isn't there some rule about cats in presentations?) 20%

14. Writing 50%

15. Translation 19% i18n L10n g11n

16. Review 1%

17. Maintenance

18. What happens when things ... GO WRNOG?

20. You need tools!

21. Get organised

22. Choose your voice

23. Say what you mean

24. Use short sentences

25. Don't be A pretentious jerk

26. A word about passive voice (and cats)

27. Cut out the cruft

28. Where there’s a will ... There’s a way to rewrite it

29. Read what you write

31. +61 410 500 659 [email_address] @Loquacities Lana Brindley