<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Open Source</title>	<link>http://tc.eserver.org/dir/Open-Source</link>
	<description>A listing of the most recently indexed works about Open Source in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Open Source</title>
		<link>http://tc.eserver.org/dir/Open-Source</link>
	</image>
	<item>
		<title>Doing Good with Technical Communication Skills</title>
		<link>http://tc.eserver.org/35831.html</link>
		<guid>http://tc.eserver.org/35831.html</guid>
		<description>Writers suggest people maintain or improve skills – or develop new skills – in some open-source type project where there is no pay, but plenty of opportunity to learn and, well, practice. This post is for sharing a few of those places of practice.</description>
	</item>
	<item>
		<title>Writing about Open Source to Kick Start (and Sustain) Your Career</title>
		<link>http://tc.eserver.org/35782.html</link>
		<guid>http://tc.eserver.org/35782.html</guid>
		<description>A report of a presentation by Dru Lavigne at FSOSS 2009 that discussed how to create and sustain a writing career by writing about Open Source.</description>
	</item>
	<item>
		<title>Great Documentation Is Key to Open Source Success</title>
		<link>http://tc.eserver.org/35707.html</link>
		<guid>http://tc.eserver.org/35707.html</guid>
		<description>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.&#xD;&#xD;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.</description>
	</item>
	<item>
		<title>Janet Swisher on FLOSS Manuals, Open Source, and Book Sprints</title>
		<link>http://tc.eserver.org/35625.html</link>
		<guid>http://tc.eserver.org/35625.html</guid>
		<description>Janet Swisher, who’s worked in technical communication since 1999, is an Information Developer for a medium-sized software company. Her specialist areas include online help, tutorials, API documentation and programmer guides.  My “techie” cred is that she “can read code well enough to avoid asking obvious questions, and write code well enough to be dangerous.”</description>
	</item>
	<item>
		<title>Documentation Collaboration Service</title>
		<link>http://tc.eserver.org/35617.html</link>
		<guid>http://tc.eserver.org/35617.html</guid>
		<description>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.&#xD;&#xD;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.</description>
	</item>
	<item>
		<title>XMLmind DITA Converter</title>
		<link>http://tc.eserver.org/35619.html</link>
		<guid>http://tc.eserver.org/35619.html</guid>
		<description>XMLmind DITA Converter (ditac for short) allows to convert the most complex DITA 1.1 documents to production-quality XHTML 1.0, XHTML 1.1, HTML 4.1, JavaTM Help, HTML Help, Eclipse Help, PDF, PostScript®, RTF (can be opened in Word 2000+), WordprocessingML (can be opened in Word 2003+), Office Open XML (.docx, can be opened in Word 2007+), OpenOffice (.odt, can be opened in OpenOffice.org 2+).</description>
	</item>
	<item>
		<title>No More Slidesters, Part 3: Draw in the Open</title>
		<link>http://tc.eserver.org/35565.html</link>
		<guid>http://tc.eserver.org/35565.html</guid>
		<description>As discussed recently, many people use PowerPoint to design posters, an act that borders on criminal. PowerPoint was designed for multiple projected images with minimal text, not one large image with complex text and graphics. People use PowerPoint because it’s the only thing remotely resembling a graphics software that people are familiar with. Microsoft Office simply doesn’t have a good, high end graphics component. Publisher comes close.&#xD;&#xD;OpenOffice does have a graphics component, simply called Draw. If you are not willing to shell out the big bucks generally required of a professional graphics software package, Draw has several features in its favour.</description>
	</item>
	<item>
		<title>Active Open Source Translation Tool Projects</title>
		<link>http://tc.eserver.org/35513.html</link>
		<guid>http://tc.eserver.org/35513.html</guid>
		<description>I don’t intend to give a complete project list. I just chose some projects that might be interesting enough to people from localization industry based on two criteria: 1. The features are useful for language service providers (LSP). 2. The development status is Stable or Mature. In other words, it is ready for real production use from the view of development cycle.</description>
	</item>
	<item>
		<title>Open-Source Tech Writing: The Time is Now</title>
		<link>http://tc.eserver.org/35470.html</link>
		<guid>http://tc.eserver.org/35470.html</guid>
		<description>We are all going to have to collaborate like never before. Everyone should select at least one area of interest and specialize as best they can. Then we will need to start meeting and sharing information. Immediately. There are several ways to do this, I believe.</description>
	</item>
	<item>
		<title>Choosing a License for Sharing Documentation Content</title>
		<link>http://tc.eserver.org/35288.html</link>
		<guid>http://tc.eserver.org/35288.html</guid>
		<description>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?</description>
	</item>
	<item>
		<title>Open-Source Software for Technical Writers</title>
		<link>http://tc.eserver.org/35220.html</link>
		<guid>http://tc.eserver.org/35220.html</guid>
		<description>For companies that are struggling in the current times because of the economic slowdown, an option that might not compromise on product quality is to switch to open-source software. In this article, I will talk about open-source publishing tools for the writing community.</description>
	</item>
	<item>
		<title>Open Source: It&apos;s Just a License</title>
		<link>http://tc.eserver.org/35035.html</link>
		<guid>http://tc.eserver.org/35035.html</guid>
		<description>There&apos;s only one thing you can generalize: open source is a specific kind of license. And discussions about which license is better are rather academic. What you&apos;d want to decide on is what your software should do, if and how you want to customize it, and how easy it is to get support when you need it. That means doing your homework, and finding out the real story: you&apos;ll certainly want to know what&apos;s behind the facade. And that&apos;s something that applies to software under any license.</description>
	</item>
	<item>
		<title>OSCOM: Open Source Content Management</title>
		<link>http://tc.eserver.org/34749.html</link>
		<guid>http://tc.eserver.org/34749.html</guid>
		<description>OSCOM is the international association connecting users and developers of Open Source Content Management solutions.&#xD;&#xD;OSCOM organizes events, promotes standards and undertakes projects to further the state of the art of Open Source Content Management. OSCOM promotes Open Source Content Management solutions as powerful, affordable and flexible replacements for proprietary products.</description>
	</item>
	<item>
		<title>Alfresco Is Not A Picnic: The Problem With Metaphors and Content Management Systems</title>
		<link>http://tc.eserver.org/34579.html</link>
		<guid>http://tc.eserver.org/34579.html</guid>
		<description>In the content management system I currently use, I’ve noticed no less than nine metaphors, which are meant serve as organizing principles, but they don’t. Granted, the particular tool I use isn’t really meant for gobs and gobs of editorial work, but nonetheless its organization and structure were likely created by a developer within arm’s reach of a bottle of tequila.</description>
	</item>
	<item>
		<title>Open Source Alternatives To Tech Pubs Tools</title>
		<link>http://tc.eserver.org/34337.html</link>
		<guid>http://tc.eserver.org/34337.html</guid>
		<description>Given how hard it is for students (and their programs) to afford the expensive tools in our profession, I thought it might help to pass along these alternatives to commercial products. I think anyone breaking into the field (or a new type of tool) would do very well to train up on these open source tools and create portfolio pieces with them.</description>
	</item>
	<item>
		<title>Comparing Open Source Content Management Systems: WordPress, Joomla, Drupal and Plone</title>
		<link>http://tc.eserver.org/34104.html</link>
		<guid>http://tc.eserver.org/34104.html</guid>
		<description>In this report, we take a look at four different open &#xD;source Content Management Systems—WordPress, &#xD;Joomla, Drupal and Plone—and rate them on a variety &#xD;of criteria, including system flexibility, features, ease &#xD;of use and the availability of support. We chose these &#xD;systems because they’re the most popular four in the &#xD;nonprofit sector today, according to our analysis (see &#xD;Appendix C for more details on our market analysis). &#xD;We also dig a little deeper into what open source is all &#xD;about, and how a CMS can help streamline processes. &#xD;We even take a look at some vendor-provided systems, &#xD;along with a few other open source ones, in case you &#xD;don’t find what you’re looking for among the four &#xD;original choices.</description>
	</item>
	<item>
		<title>Top 3 Open Source Software You Can Use to Write and Design Technical Documents</title>
		<link>http://tc.eserver.org/34024.html</link>
		<guid>http://tc.eserver.org/34024.html</guid>
		<description>Although I love using the proprietary software that I’ve mentioned in the first sentence, I enjoy using open source software as well since some of them are actually better than the paid software in some respects.</description>
	</item>
	<item>
		<title>On Collaboration</title>
		<link>http://tc.eserver.org/33883.html</link>
		<guid>http://tc.eserver.org/33883.html</guid>
		<description>Openness is a faster route to better work. There are lots of ways of doing it, but I do think that as much as they pretend pure openness, successful OS projects all have hierarchy.</description>
	</item>
	<item>
		<title>FLOSS Manuals Sprints to Build Quality Free Documentation</title>
		<link>http://tc.eserver.org/33755.html</link>
		<guid>http://tc.eserver.org/33755.html</guid>
		<description>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.</description>
	</item>
	<item>
		<title>Getting Tech Writers Involved in FLOSS</title>
		<link>http://tc.eserver.org/33726.html</link>
		<guid>http://tc.eserver.org/33726.html</guid>
		<description>I commented that many tech writers aren&apos;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.</description>
	</item>
	<item>
		<title>The Emergence of Intelligent Content: The Evolution of Open Content Technologies and Their Significance</title>
		<link>http://tc.eserver.org/33622.html</link>
		<guid>http://tc.eserver.org/33622.html</guid>
		<description>This paper traces the history of open content technologies in an effort to understand the nature and significance of intelligent content. What is illustrated is that a common thread runs through SGML, HTML, XML, &#xD;Web 2.0, the Semantic Web, DITA, and OOXML and that the evolution of open content technologies has enabled the emergence of intelligent content and with it a new form of organizational agility. This whitepaper has been prepared as a corollary to the presentation “Content Fusion: There’s a Piece of Data Lodged in my Document” at Intelligent Content 2009, Palm Springs CA, January 29-30, 2009.</description>
	</item>
	<item>
		<title>Eclipse: Don&apos;t Get Left in the Dark</title>
		<link>http://tc.eserver.org/33396.html</link>
		<guid>http://tc.eserver.org/33396.html</guid>
		<description>Offers a detailed look at Eclipse—an open-source integrated development environment—and also discusses why it is becoming increasingly important to technical communicators in the software industry. </description>
	</item>
	<item>
		<title>The Content Management Dilemna: Good Time to Revisit the Open Source CMS</title>
		<link>http://tc.eserver.org/33374.html</link>
		<guid>http://tc.eserver.org/33374.html</guid>
		<description>Open source delivers on the basics. The move to Plone delivered on the basic value proposition of open source: we got a very sturdy platform that worked well for our editors and didn&apos;t have to pay a dime in license fees. </description>
	</item>
	<item>
		<title>Making A Better CMS</title>
		<link>http://tc.eserver.org/33283.html</link>
		<guid>http://tc.eserver.org/33283.html</guid>
		<description>This whole category of software desperately needs to be redesigned with writers, editors, designers, and site owners in mind. Here are my recommendations to the folks writing open source content management systems.</description>
	</item>
	<item>
		<title>Comparing Open Source CMSes: Joomla, Drupal, and Plone</title>
		<link>http://tc.eserver.org/33217.html</link>
		<guid>http://tc.eserver.org/33217.html</guid>
		<description>Open source content management systems (CMS) are particularly attractive to the nonprofit community because of their cost-efficiency, but what do these systems actually do? And what are the differences between the most common CMSs? We’ll compare Joomla, Drupal, and Plone for typical nonprofit needs.</description>
	</item>
	<item>
		<title>Six Strategies for Low-Cost Content Management</title>
		<link>http://tc.eserver.org/33218.html</link>
		<guid>http://tc.eserver.org/33218.html</guid>
		<description>Although Gartner says software licensing for basic content services can cost less than US$100 per user for large volume deals, requirements for extra functions will increase the initial software costs if content management components are not included. How do you set aside enough money to solve the initial ECM pain points and create a strategy for the future? We asked the experts for some ideas.</description>
	</item>
	<item>
		<title>It&apos;s Possible to Ditch Microsoft Office</title>
		<link>http://tc.eserver.org/33219.html</link>
		<guid>http://tc.eserver.org/33219.html</guid>
		<description>Is today&apos;s OpenOffice good enough for the enterprise? For most jobs—word processing, presentations or spreadsheets—the answer is yes. Compatibility with Microsoft Office isn&apos;t a problem unless sophisticated macros are involved. Interoperability, the greatest hurdle to conquer on the way to adoption, is almost a nonissue. OpenOffice even offers features missing in Microsoft Office, like PDF or Flash data exports.</description>
	</item>
	<item>
		<title>Creating Quality Content with Open Source Tools</title>
		<link>http://tc.eserver.org/32783.html</link>
		<guid>http://tc.eserver.org/32783.html</guid>
		<description>The detailed notes for the presentation on creating quality content with Open Source tools that was given at DocTrain East 2008 (Oct. 31, 2008).</description>
	</item>
	<item>
		<title>Introduction to Django: Helping Perfectionists With Deadlines</title>
		<link>http://tc.eserver.org/32652.html</link>
		<guid>http://tc.eserver.org/32652.html</guid>
		<description>Django is an open-source Web framework, written in Python, that allows you to easily and rapidly develop interactive, data-centric web applications. It came into being when two Web developers—Adrian Holovaty and Simon Willison—in Kansas, after moving their newspaper’s website from PHP to Python, found themselves repeatedly solving similar problems. They decided to extract the common functionality and released the resulting framework in 2005.</description>
	</item>
	<item>
		<title>Microsoft Word: An Unnecessary Evil?</title>
		<link>http://tc.eserver.org/32631.html</link>
		<guid>http://tc.eserver.org/32631.html</guid>
		<description>First and foremost, Microsoft Word is a solid piece of software, and the 2007 version is untouchable at present. It pretty much sets the standard. It&apos;s also in no way evil in and of itself. That said, it&apos;s unfortunately not free, so here are some alternatives that are.</description>
	</item>
	<item>
		<title>Eight Arguments for Open Source</title>
		<link>http://tc.eserver.org/32600.html</link>
		<guid>http://tc.eserver.org/32600.html</guid>
		<description>Is Open Source better? It&apos;s not a black and white question; the answer will depend on your needs and circumstances. Still, there are some very good things to be said for supporting Open Source and Open Standards. Here&apos;s a list of the top reasons why we prefer Open Standards and Open Source development.</description>
	</item>
	<item>
		<title>Changing the Way We Work</title>
		<link>http://tc.eserver.org/32605.html</link>
		<guid>http://tc.eserver.org/32605.html</guid>
		<description>The CMS market really took wing with the liftoff of the LAMP stack and the growth of a supportive development community. Suddenly it seemed everyone was producing LAMP-based CMSes under Open Source licenses.</description>
	</item>
	<item>
		<title>Ready for the Enterprise?</title>
		<link>http://tc.eserver.org/32609.html</link>
		<guid>http://tc.eserver.org/32609.html</guid>
		<description>A quick look at ten Open Source Content Management Systems which are beginning to find their way inside Enterprise IT Departments.</description>
	</item>
	<item>
		<title>Open Source Practices and Technical Communication Programs</title>
		<link>http://tc.eserver.org/32536.html</link>
		<guid>http://tc.eserver.org/32536.html</guid>
		<description>Structural differences among different resource formats impede efforts to develop a learning community. With OSS, education issues/critique include media, medium, and message. OSS complicates framework issues.</description>
	</item>
	<item>
		<title>Looking for Open Source CMS and Portal Software Options</title>
		<link>http://tc.eserver.org/32440.html</link>
		<guid>http://tc.eserver.org/32440.html</guid>
		<description>I find choosing a CMS incredibly difficult, and evaluating them is very time consuming and often frustrating. There are hundreds of options, one worse than the other. To date I have never come across a CMS that doesn’t have serious flaws. Even if a CMS looks good at a glance, once you start digging deeper you will always encounter problems with usability, accessibility, and front-end code.</description>
	</item>
	<item>
		<title>Introduction to Web Content Management Systems: Part One</title>
		<link>http://tc.eserver.org/32373.html</link>
		<guid>http://tc.eserver.org/32373.html</guid>
		<description>Content Management System (CMS) software tools give even the smallest business the chance to have a first-rate, interactive web presence. Packed with powerful features, and easily extended with add-on modules, CMS tools reduce web site development time and costs while providing interactivity, distributed responsibility, security, convenience and significant cost savings.</description>
	</item>
	<item>
		<title>Electronic Scholarly Publishing and Open Access</title>
		<link>http://tc.eserver.org/32300.html</link>
		<guid>http://tc.eserver.org/32300.html</guid>
		<description>A review of recent developments in electronic publishing, with a focus on Open Access (OA) is provided. It describes the two main types of OA, i.e. the `gold&apos; OA journal route and the `green&apos; repository route, highlighting the advantages and disadvantages of the two, and the reactions of the publishing industry to these developments. Quality, cost and copyright issues are explored, as well as some of the business models of OA. It is noted that whilst so far there is no evidence that a shift to OA will lead to libraries cancelling subscriptions to toll-access journals, this may happen in the future, and that despite the apparently compelling reasons for authors to move to OA, so far few have shown themselves willing to do so. Conclusions about the future of scholarly publications are drawn.</description>
	</item>
	<item>
		<title>Open Access News</title>
		<link>http://tc.eserver.org/32245.html</link>
		<guid>http://tc.eserver.org/32245.html</guid>
		<description>Putting peer-reviewed scientific and scholarly literature on the internet. Making it available free of charge and free of most copyright and licensing restrictions. Removing the barriers to serious research.</description>
	</item>
	<item>
		<title>Crowdsourcing as a Model for Problem Solving: An Introduction and Cases</title>
		<link>http://tc.eserver.org/32027.html</link>
		<guid>http://tc.eserver.org/32027.html</guid>
		<description>Crowdsourcing is an online, distributed problem-solving and production model that has emerged in recent years. Notable examples of the model include Threadless, iStockphoto, InnoCentive, the Goldcorp Challenge, and user-generated advertising contests. This article provides an introduction to crowdsourcing, both its theoretical grounding and exemplar cases, taking care to distinguish crowdsourcing from open source production. This article also explores the possibilities for the model, its potential to exploit a crowd of innovators, and its potential for use beyond forprofit sectors. Finally, this article proposes an agenda for research into crowdsourcing.</description>
	</item>
	<item>
		<title>Fulfilling the Promise of Open Content</title>
		<link>http://tc.eserver.org/31242.html</link>
		<guid>http://tc.eserver.org/31242.html</guid>
		<description>Unfortunately, the movement to use open educational resources in higher education hasn’t yet realized the full impact that its founders anticipated. Open content is still in its infancy and faces some technical and cultural challenges that affect its widespread adoption.</description>
	</item>
	<item>
		<title>A Few Thoughts on FOSS Help Authoring Tools</title>
		<link>http://tc.eserver.org/31112.html</link>
		<guid>http://tc.eserver.org/31112.html</guid>
		<description>There&apos;s a lot of great free and Open Source (FOSS) software out there. But one area in which it&apos;s lacking is professional-level help authoring tools. In 2005, Linux.com published an article titled &quot;FOSS help authoring tools falter&quot;. And not much seems to have changed in the intervening years.</description>
	</item>
	<item>
		<title>The Role for Technical Communicators in Open-Source Software Development</title>
		<link>http://tc.eserver.org/31085.html</link>
		<guid>http://tc.eserver.org/31085.html</guid>
		<description>Although it claims to adhere to user-centered design principles of participatory design and democratized technology, open-source software often fails to effectively address the usability needs of typical software users. In many cases, it embodies a system-centered design approach facilitated by the efforts of developer-users. In addition to the existing participation in open-source projects in the classroom, technical communicators should actively critique open-source software and promote user-centered design principles in open-source software projects.</description>
	</item>
	<item>
		<title>Usability in Open Source Software</title>
		<link>http://tc.eserver.org/30871.html</link>
		<guid>http://tc.eserver.org/30871.html</guid>
		<description>Open source is a software licensing philosophy which believes the human readable code source of a software should be available for the public to freely install, modify, or redistribute. The term &apos;open source&apos; can also refer to the community and development practices of thousands of free/libre/open source software (FLOSS) projects who subscribe to this philosophy and license their software under one of the many available software licenses.</description>
	</item>
	<item>
		<title>Open Source For Technical Writing Teams</title>
		<link>http://tc.eserver.org/29523.html</link>
		<guid>http://tc.eserver.org/29523.html</guid>
		<description>A presentation introducting how to support technical documentation teams with open-source tools.</description>
	</item>
	<item>
		<title>Categories of Free and Non-Free Software</title>
		<link>http://tc.eserver.org/29459.html</link>
		<guid>http://tc.eserver.org/29459.html</guid>
		<description>A glossary of various categories of software that are often mentioned in discussions of free software.</description>
	</item>
	<item>
		<title>&quot;Open Source&quot; is not a Marketing Term</title>
		<link>http://tc.eserver.org/29405.html</link>
		<guid>http://tc.eserver.org/29405.html</guid>
		<description>Open source software development is not just about providing the source code for your application. It is much more about building a community around a shared project. That takes time. I think the biggest myth about open source software is that you say &apos;hey, I&apos;m open source now&apos; and suddenly thousands of qualified people give up nights and weekends to work on your code.</description>
	</item>
	<item>
		<title>Open Source FAQ</title>
		<link>http://tc.eserver.org/29190.html</link>
		<guid>http://tc.eserver.org/29190.html</guid>
		<description>Open source is a licensing model where the software and the source code are distributed without requiring licensing fees.</description>
	</item>
	<item>
		<title>Free or Open-Source Tools for Technical Communicators, Part 1: The Software</title>
		<link>http://tc.eserver.org/28368.html</link>
		<guid>http://tc.eserver.org/28368.html</guid>
		<description>This article takes a look at some of the most successful free and open-source products available for technical communicators and their clients.</description>
	</item>
	<item>
		<title>It&apos;s Raining Code! (Hallelujah?)</title>
		<link>http://tc.eserver.org/28127.html</link>
		<guid>http://tc.eserver.org/28127.html</guid>
		<description>As open-source development options proliferate, CIOs are finding ways to make it work for their organizations.</description>
	</item>
	<item>
		<title>Open Source Documentation</title>
		<link>http://tc.eserver.org/28124.html</link>
		<guid>http://tc.eserver.org/28124.html</guid>
		<description>Collaborative technologies are supplanting traditional channels for product tech support.</description>
	</item>
	<item>
		<title>Using Open Source Software to Design, Develop, and Deploy a Collaborative Web Site, Part 1: Introduction and Overview</title>
		<link>http://tc.eserver.org/28039.html</link>
		<guid>http://tc.eserver.org/28039.html</guid>
		<description>In this series, follow along as the IBM Internet Technology Group team designs, develops, and deploys a closed community Web site using a suite of software that is freely available. The open source community provides various tools that, when plugged together, begin to create a useful development and production environment for complex Web applications. Using these tools as a foundation, we provide a methodology and set of enhancements to help you simplify the production process. Although customization is still necessary, this series shows you the tools and techniques to get relatively complicated Web sites up and running quickly using open source tools, including Drupal, MySQL, PHP, Apache, and Eclipse technologies. In this first article, you&apos;ll compare our approach with other software tools available and explore the enhancements we made.</description>
	</item>
	<item>
		<title>Using Open Source Software to Design, Develop, and Deploy a Collaborative Web Site, Part 2: Design for an Effective User Experience</title>
		<link>http://tc.eserver.org/28038.html</link>
		<guid>http://tc.eserver.org/28038.html</guid>
		<description>In this series, you follow along as the IBM Internet Technology Group designs, develops, and deploys a closed community Web site using a suite of software that is freely available. Most of this series focuses on the actual implementation of the Web site, but this second article is a bit more generic. Read it to explore our design process, which can help you to create user experiences for applications, other interfaces, or Web sites. Part 1 discusses the team&apos;s requirements, compares several open source content management systems, and provides the rationale for choosing Drupal.</description>
	</item>
	<item>
		<title>Indexing with Open Source Tools</title>
		<link>http://tc.eserver.org/27884.html</link>
		<guid>http://tc.eserver.org/27884.html</guid>
		<description>The index can often be the most heavily used &apos;chapter&apos; in any publication and helping the user find an answer is the key to fulfilling the technical document&apos;s mission, justifying the effort and expense for its creation. Yet, indexing facilities in open source packages for document creation remains largely unexplored, offering a marvelous opportunity to do it right!&#xD;&#xD;This article provides a generic specification (with reasons) to open source developers for creating useful indexing facilities in packages such as OpenOffice and Scribus. It also informs writers about what to look for and what to ask for in any indexing tool. Finally, the article demonstrates the need for software developers to work closely with practitioners and users. </description>
	</item>
	<item>
		<title>Calculating the True Price of Software</title>
		<link>http://tc.eserver.org/27452.html</link>
		<guid>http://tc.eserver.org/27452.html</guid>
		<description>Therefore, the major difference in worldview between open source advocates and proprietary software license advocates is explainable as a differing opinion on the correct value of the volatility of maintenance and upgrade pricing. People who believe that the pricing on maintenance is stable and unlikely to change see greater intrinsic value in the software. People who fear that the pricing is subject to large fluctuations see no intrinsic value in the up-front license; stripped of the options, the license value approaches $0.</description>
	</item>
	<item>
		<title>Is Open Source is Killing the Lone Coder?</title>
		<link>http://tc.eserver.org/27155.html</link>
		<guid>http://tc.eserver.org/27155.html</guid>
		<description>It is probably more true that open source is helping the lone coder find a niche or their own market share. There are plenty of them and more are appearing everyday. With potential clients looking for specialists in content management software like Drupal, Joomla, Mambo, Typo3 and a gang of newcomers finding a niche is becoming increasingly easier.</description>
	</item>
	<item>
		<title>Understanding Open Source, Part 1</title>
		<link>http://tc.eserver.org/26740.html</link>
		<guid>http://tc.eserver.org/26740.html</guid>
		<description>Open source software is big news right now. We&apos;ve heard from big-name corporations who support it and oppose it. A number of high-profile intellectual property battles concern it. You probably know an open source zealot who&apos;s spent some time extolling its virtues. Open source software is a good thing, and has an important place in the tech sector. Closed source software also has its place, and the industry will benefit most from cooperation between the two.</description>
	</item>
	<item>
		<title>Considering Open Source Content Management Systems</title>
		<link>http://tc.eserver.org/26497.html</link>
		<guid>http://tc.eserver.org/26497.html</guid>
		<description>Open source software content management systems (CMS) offer affordability, flexibility, and in many cases outstanding performance.</description>
	</item>
	<item>
		<title>PostgreSQL vs. MySQL vs. Commercial Databases: It&apos;s All About What You Need</title>
		<link>http://tc.eserver.org/25906.html</link>
		<guid>http://tc.eserver.org/25906.html</guid>
		<description>Can you trust the leading open-source database engines, PostgreSQL and MySQL, to deliver the performance and features that the Oracles, SQL Servers, and DB2s of the world do? Not just yet, but they could offer enough to meet your needs. Find out how they stack up against each other, as well as against the commercial alternatives.</description>
	</item>
	<item>
		<title>Intrinsic vs. Extrinsic Incentives in Profit–Oriented Firms Supplying Open Source Products and Services</title>
		<link>http://tc.eserver.org/25858.html</link>
		<guid>http://tc.eserver.org/25858.html</guid>
		<description>This paper contributes to the literature on Open Source (OS) software by providing empirical evidence on the incentives of firms that engage in OS activities. Data collected by a survey conducted on 146 Italian companies supplying OS solutions (Open Source firms) show that (surprisingly) intrinsic, community–based incentives do play a role but are not, in general, put into practise. We investigate this discrepancy between attitudes and behaviours and single out groups of firms adopting more consistent behaviours. Our results are in line with the literature on business models of the firms that enter the Open Source field.</description>
	</item>
	<item>
		<title>Beyond Markets and Firms: The Emergence of Open Source Networks</title>
		<link>http://tc.eserver.org/25854.html</link>
		<guid>http://tc.eserver.org/25854.html</guid>
		<description>Although hierarchies and markets (i.e., autonomy) have been subject to extensive study, heterarchies represent different modalities of organizing that have been little researched. Drawing on complexity theory and the main features of complex evolving systems (CES), this paper sets out to remedy this imbalance by showing that heterarchies feature highly decentralized and relatively stable interactions which are coordinated through an emergent process of parametric adaptation. Implications in terms of learning are discussed casting a new light on the delicate issue of motivation in Open Source software development.</description>
	</item>
	<item>
		<title>Introduction to LAMP Technology</title>
		<link>http://tc.eserver.org/25790.html</link>
		<guid>http://tc.eserver.org/25790.html</guid>
		<description>This tutorial explores the Linux-Apache-MySQL-PHP, or LAMP, Web development framework and shows how that framework can help you build applications to solve common business problems. The tutorial begins with an exploration of the LAMP architecture, then introduces fundamental PHP concepts. After a solid grounding of PHP, the tutorial explains MySQL support, with coverage focusing on database concepts and how to access MySQL from PHP. All of these techniques are discussed within the context of a real-world customer management example.</description>
	</item>
	<item>
		<title>Trust and Zeal in Open Source Advocacy</title>
		<link>http://tc.eserver.org/25569.html</link>
		<guid>http://tc.eserver.org/25569.html</guid>
		<description>People who are unfamiliar with open source generally don&apos;t like evangelists--at all. This is particularly true for managers who may take the same disdain to evangelists that they take to salespeople and marketers.</description>
	</item>
	<item>
		<title>Wide Open: Open Source Methods and their Future Potential</title>
		<link>http://tc.eserver.org/25471.html</link>
		<guid>http://tc.eserver.org/25471.html</guid>
		<description>The principles of &apos;open source&apos; - collaborative forms of creating knowledge pioneered in software development - have huge untapped potential to transform business, government and everyday life.</description>
	</item>
	<item>
		<title>The DocBook Project</title>
		<link>http://tc.eserver.org/25442.html</link>
		<guid>http://tc.eserver.org/25442.html</guid>
		<description>DocBook is an XML vocabulary that is particularly well suited to books and papers about computer hardware and software.</description>
	</item>
	<item>
		<title>Why Free IT Management Tools are Gaining Traction</title>
		<link>http://tc.eserver.org/25255.html</link>
		<guid>http://tc.eserver.org/25255.html</guid>
		<description>Free software has penetrated close to three-quarters of all multi-billion dollar corporations and growth continues steadily. Industry research confirms that the primary reason IT organizations purchase free software solutions is the opportunity to reduce costs and improve technology performance. While leading products such as Linux, Apache and MySQL have generated the most attention, free software tools for IT management such as Nagios have matured and are poised for mainstream adoption.</description>
	</item>
	<item>
		<title>Checklist for Justifying Free Software</title>
		<link>http://tc.eserver.org/25041.html</link>
		<guid>http://tc.eserver.org/25041.html</guid>
		<description>In a few years viewing source code within the major components of software infrastructure will probably be a routine way of doing business. In the meantime it seems that the only reason managers want free software is because it is free (as in free of costs). That&apos;s not a good reason in itself: in the long run there are compelling reasons that robust, mission critical infrastructure software should be made free software. </description>
	</item>
	<item>
		<title>Open Source Licenses Are Not All the Same</title>
		<link>http://tc.eserver.org/24998.html</link>
		<guid>http://tc.eserver.org/24998.html</guid>
		<description>One of the most significant developments in the software and web development community in the past few years has been the increased use of open source software. It&apos;s vital for any programmer, web designer, or other computer professional to understand that open source licenses are not all the same. The differences between licenses can have a big impact on how you may use or distribute the software.</description>
	</item>
	<item>
		<title>The MySQL Roadmap – What&apos;s Planned?</title>
		<link>http://tc.eserver.org/23809.html</link>
		<guid>http://tc.eserver.org/23809.html</guid>
		<description>MySQL is old news ...or is it? In this fast-paced expose, Blane looks at where MySQL is now, and what&apos;s planned in Versions 4.1 and 5 - including the exciting developments of MySQL Cluster and Stored Procedures!</description>
	</item>
	<item>
		<title>Key Open Source &quot;Best Practices&quot; Supported in the Tigris Project</title>
		<link>http://tc.eserver.org/23765.html</link>
		<guid>http://tc.eserver.org/23765.html</guid>
		<description>Software developers spend a large part of their time communicating with each other.  Clear and effective technical communications are needed to keep the team in synch and to allow individuals with key knowledge to apply that knowledge where it is needed.&#xD;&#xD;One tenet of the open source community is that techincal communications should take place in public forums.   Mailing lists are the backbone of open source communications.  Beyond that, open source projects need support for precisely communicating technical details and for group decision-making.</description>
	</item>
	<item>
		<title>Open-Source Content Management Systems</title>
		<link>http://tc.eserver.org/22080.html</link>
		<guid>http://tc.eserver.org/22080.html</guid>
		<description>Open-source CMS has now matured to the point where it should be considered alongside commercial products, but is not without its weaknesses and issues.</description>
	</item>
	<item>
		<title>Ethics in Technical Communication: Copyleft and the Open Source Movement</title>
		<link>http://tc.eserver.org/20614.html</link>
		<guid>http://tc.eserver.org/20614.html</guid>
		<description>A collection of resources about open-source software, innovation in copyright, and their implications for technical communicators.</description>
	</item>
	<item>
		<title>Public Key Infrastructure Digital Signatures and Systematic Risk</title>
		<link>http://tc.eserver.org/20052.html</link>
		<guid>http://tc.eserver.org/20052.html</guid>
		<description>The last few years have seen very considerable developments in the networks and technologies of electronic commerce, matched by the promotional and regulatory initiatives of international and national government towards electronic commerce. Of particular note have been the technological and regulatory developments in relation to public key cryptography and digital signatures. These regulatory developments arguably represent a promotion of an emerging Public Key Infrastructure as an international open network infrastructure for digital signature authorisation in electronic commerce. However, over the same period concerns have been growing in other international open network infrastructures, such as banking and finance, that such strongly inter-connected and inter-dependent infrastructures may be subject to systematic risk. Indeed, it appears that vulnerability to systematic risk is a characteristic of any complex open network. Therefore, the question can be posed whether the emerging Public Key Infrastructure is also vulnerable to systematic risk. </description>
	</item>
	<item>
		<title>The Challenges of Open-Source Documentation and Training</title>
		<link>http://tc.eserver.org/20030.html</link>
		<guid>http://tc.eserver.org/20030.html</guid>
		<description>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.&#xD;&#xD;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&apos;s developer. Or, if something is missing, using support from the vendor to get questions and issues resolved.</description>
	</item>
	<item>
		<title>Open-Source Software: Gaining Ground</title>
		<link>http://tc.eserver.org/19997.html</link>
		<guid>http://tc.eserver.org/19997.html</guid>
		<description>Have you ever run across a bug in your word processor that interfered with your work? Or perhaps you&apos;ve wished that your graphics program had a certain feature that would make your life easier.&#xD;&#xD;With most commercial software, you&apos;re at the mercy of the company that created it. All you can do is call the technical support line, explain the situation, and hope that there&apos;s a work-around or that your issue will be addressed whenever the next version is released.&#xD;&#xD;With proprietary software, the company owns the software and doesn&apos;t allow anyone else to modify it or even see the source code -- the human-readable (well, programmer-readable) instructions used to create the executable file that the computer runs. Some people have likened such software to a car with the hood locked shut so that only the manufacturer can service it.&#xD;&#xD;But with open-source software, you have other options because you have the source code. If you have the knowledge, you can modify the program yourself. If not, you can hire a programmer to make the changes you want. </description>
	</item>
	<item>
		<title>The Usability of Open Source Software</title>
		<link>http://tc.eserver.org/19544.html</link>
		<guid>http://tc.eserver.org/19544.html</guid>
		<description>Open source communities have successfully developed a great deal of software although most computer users only use proprietary applications. The usability of open source software is often regarded as one reason for this limited distribution. In this paper we review the existing evidence of the usability of open source software and discuss how the characteristics of open source development influence usability. We describe how existing human-computer interaction techniques can be used to leverage distributed networked communities, of developers and users, to address issues of usability.</description>
	</item>
	<item>
		<title>Clustering and Dependencies in Free/Open Source Software Development: Methodology and Tools</title>
		<link>http://tc.eserver.org/19539.html</link>
		<guid>http://tc.eserver.org/19539.html</guid>
		<description>This paper addresses the problem of measurement of non-monetary economic activity, specifically in the area of free/open source software [1] communities. It describes the problems associated with research on these communities in the absence of measurable monetary transactions, and suggests possible alternatives. A class of techniques using software source code as factual documentation of economic activity is described and a methodology for the extraction, interpretation and analysis of empirical data from software source code is detailed, with the outline of algorithms for identifying collaborative authorship and determining the identity of coherent economic actors in developer communities. Finally, conclusions are drawn from the application of these techniques to a base of software.</description>
	</item>
	<item>
		<title>Educational Models and Open Source: Resisting the Proprietary University</title>
		<link>http://tc.eserver.org/19056.html</link>
		<guid>http://tc.eserver.org/19056.html</guid>
		<description> This paper presents an educational model derived from open source methods for computer programming. The article places this search for an alternative model within a framework of proprietary educational practices that are driven by a need for efficiency and rationalization. As an alternative model, the paper suggests that an open source derived educational process would emphasize collaborative problem based learning, working through drafts, risk taking, mentoring, user testing, releasing early and often. . . . </description>
	</item>
	<item>
		<title>Full Text Available Documentation, Participatory Citizenship, and the Web: the Potential of Open Systems</title>
		<link>http://tc.eserver.org/19057.html</link>
		<guid>http://tc.eserver.org/19057.html</guid>
		<description> Technical communicators have become increasingly interested in how to &apos;open up&apos; 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. </description>
	</item>
	<item>
		<title>Applying Copyleft To Non-Software Information</title>
		<link>http://tc.eserver.org/18892.html</link>
		<guid>http://tc.eserver.org/18892.html</guid>
		<description>Copyleft contains the normal copyright statement, asserting ownership and identification of the author. However, it then gives away some of the other rights implicit in the normal copyright: it says that not only are you free to redistribute this work, but you are also free to change the work. However, you cannot claim to have written the original work, nor can you claim that these changes were created by someone else. Finally, all derivative works must also be placed under these terms. </description>
	</item>
	<item>
		<title>The Great Giveaway</title>
		<link>http://tc.eserver.org/18893.html</link>
		<guid>http://tc.eserver.org/18893.html</guid>
		<description>Good ideas are worth money. So why are hard-headed operators giving them away for free?</description>
	</item>
	<item>
		<title>What Is Open Source Software And Is It Usable?</title>
		<link>http://tc.eserver.org/18293.html</link>
		<guid>http://tc.eserver.org/18293.html</guid>
		<description>Open Source Software (OSS) is a software project where all the source code is freely available, usually according to a licensing agreement baring commercial gain on the source. The contributors to the project are usually part-time computing enthusiasts with a wide variety of backgrounds and experiences. Usability specialists are not generally part of the development process.</description>
	</item>
	<item>
		<title>Collaborative Virtual Workspace</title>
		<link>http://tc.eserver.org/14306.html</link>
		<guid>http://tc.eserver.org/14306.html</guid>
		<description>CVW is a collaboration software environment that provides a &apos;virtual building&apos; where teams can communicate, collaborate, and share information, regardless of their geographic location. CVW takes virtual meetings one step further and enables virtual co-location through persistent virtual rooms, each incorporating people, information, and tools appropriate to a task, operation, or service.</description>
	</item>
	<item>
		<title>Painless Linux</title>
		<link>http://tc.eserver.org/13957.html</link>
		<guid>http://tc.eserver.org/13957.html</guid>
		<description>Is Linux in your technical writing future? The possibility is becoming too strong to ignore. Companies like Merrill Lynch and Credit Suisse First Boston are using Linux now, and countries ranging from Germany and France to Pakistan and Venezuela are adapting it and other open source software for government business. In high-tech, IBM reports that over one thousand of its business partners became Linux-certified in 2001, and the Linux applications listed in the IBM Global Solutions Directory rose from 2300 to 2800 in the six months between June 2001 and January 2002. In a little less than three years, Linux has captured over a third of the server market, and, while its share of the desktop market seems stalled at four percent, growing concerns about security, the cost of commercial software, and restrictive licensing practices are starting to change that.</description>
	</item>
	<item>
		<title>The Implications for Technical Writers of the Movement Toward Open Systems</title>
		<link>http://tc.eserver.org/13454.html</link>
		<guid>http://tc.eserver.org/13454.html</guid>
		<description>The movement toward open systems is gaining momentum. Those technical writers in the computer and software industries who have been accustomed to working in the world of proprietary systems will have to adjust to working in this new world of open systems. This paper briefly describes the open systems movement and then discusses in detail the implications of that movement for technical&#xD;writers. This includes the challenges they will face and the skills they will need to develop. A brief case study of the involvement of technical writers in the Open Software Foundation’s DCE project is included.</description>
	</item>
	<item>
		<title>Hitching with Clipboard and Pen Along the Open Road: A Tech Writer&apos;s Guide to the Open Source Movement</title>
		<link>http://tc.eserver.org/12963.html</link>
		<guid>http://tc.eserver.org/12963.html</guid>
		<description>The idea behind Open Source is simple: everyone should have the freedom to copy, distribute, and change source code. The implications, however, overturn the conventional high-tech business model. When software is no longer intellectual property, everything changes. Development is quicker because more people are involved. Bugs are caught more quickly. Instead of being passive consumers, customers can become partners in development. Instead of selling software, companies sell hardware, services, or added value. Internally, companies become more interactive and more loosely structured. If Open Source continues to gather speed, high-tech workers will discover that it is not just a development model, but also a new model for corporate life. For writers, the approach of Open Source could be especially important. How documentation is viewed and used, how writers interact with developers, and what tools are used--all of these and more could be affected by the Open Source movement.</description>
	</item>
	<item>
		<title>Open Source Writers Group</title>
		<link>http://tc.eserver.org/12975.html</link>
		<guid>http://tc.eserver.org/12975.html</guid>
		<description>The Open Source Writers Group is a non-commercial, non-profit organization whose primary goal is to improve the overall quality and quantity of free open-source and open-content documentation. All OSWG activities and projects are related to this primary goal.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Open-Source.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>