http://tc.eserver.org/dir/Articles/Documentation/Open-Source A listing of the most recently indexed works about Articles and Documentation and Open Source in the field of technical communication. en-us Copyright (c) 2005-10 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Articles/Documentation/Open-Source http://tc.eserver.org/35707.html http://tc.eserver.org/35707.html Listen up open source developers, if you want your project to succeed you’re going to have to do more than write great code; you’re going to have to document it, teach new users how it works and provide real-world examples of what you can do with it. That’s the message from Jacob Kaplan-Moss, one of the creators of Django, a very successful open source, Python-based web framework. At least some Django’s success can be attributed to its thorough documentation which is not just reference materials, but also includes tutorials, topical guides and even snippets of design philosophy. http://tc.eserver.org/35617.html http://tc.eserver.org/35617.html Collaboration happens when multiple people work simultaneously towards a common goal. Collaboration software are tools which try to make working together easier and more productive. There are hundreds of methodologies and approaches out there to collaboration. We want to bring the focus on one particular dimension: open vs. structured collaboration. http://tc.eserver.org/35288.html http://tc.eserver.org/35288.html What issues and legalities do we as Technical Communicators or Wiki Administrators need to be aware of as we move towards collaborative authoring projects and so forth, especially when documenting open source software? http://tc.eserver.org/33755.html http://tc.eserver.org/33755.html Documentation is one area in which free/libre/open source software (FLOSS) is weakest. A project called FLOSS Manuals is trying to remedy this situation. The idea behind project is to create quality, free documentation for free software. http://tc.eserver.org/33726.html http://tc.eserver.org/33726.html I commented that many tech writers aren't interested in doing more tech writing in their spare time, but might be interested if doing so can help them professionally. In particular, folks coming into the field, either out of school or as career changers, need writing samples for their portfolio to show to prospective employers. http://tc.eserver.org/31112.html http://tc.eserver.org/31112.html There's a lot of great free and Open Source (FOSS) software out there. But one area in which it's lacking is professional-level help authoring tools. In 2005, Linux.com published an article titled "FOSS help authoring tools falter". And not much seems to have changed in the intervening years. http://tc.eserver.org/28127.html http://tc.eserver.org/28127.html As open-source development options proliferate, CIOs are finding ways to make it work for their organizations. http://tc.eserver.org/28124.html http://tc.eserver.org/28124.html Collaborative technologies are supplanting traditional channels for product tech support. http://tc.eserver.org/20030.html http://tc.eserver.org/20030.html There are at least two important issues that are closely related to the open-source software support questions we raised in part 1 of this look at open-source practicalities: documenting the software and training people to use it. With a traditional, commercially licensed product, documentation is as simple as obtaining a hard copy, a CD or going online to get all the details needed from the software's developer. Or, if something is missing, using support from the vendor to get questions and issues resolved. http://tc.eserver.org/19057.html http://tc.eserver.org/19057.html Technical communicators have become increasingly interested in how to 'open up' the documentation process - to encourage workers to participate in developing documentation that closely fits their needs. This goal has led technical communicators to engage in usability testing, user-centered design approaches, and, more recently, open source documentation. Although these approaches have all had some success, there are other ways to encourage the participatory citizenship that is implied in these approaches. One way is through an open systems approach in which workers can consensually modify a given system and add their own contributions to the system.