But all these efforts were not enough. Ever more authors and other volunteers needed guidance, and ever more documents had to be organized. The project hosted a lot of outdated documents by now, which became a bit shameful. Another problem was the random publication of documents. There was so much work and not enough people to do it, so anybody could publish almost anything. Scandal broke loose when a couple of opinionated documents were found, containing tainted and sometimes plainly wrong information that was possibly harmful to the readers.
Thus, 2003 became the year of revamping. A thorough search through the entire collection revealed more old or doubtful documents that were taken off-line for a revision. Documents too old to be useful were moved to the attic. Tabatha Marshall was appointed review coordinator and put together a team of reviewers. Together, they edit new submissions: they check for technical correctness, readability and grammar and spelling errors. Furthermore, they apply the TLDP style so as to give the collection consistency. The Weekly News was revived and offered over RSS feed. Input from the feedback mailing list was followed up once more. The Author Guide was revised to list the new procedures for publishing documents in accordance with the quality control guidelines. A HOWTO generator was created to facilitate submissions by new authors. Beyond these visible accomplishments, hundreds of people are working together now, everyone of them contributing a small part to this huge project.
People responsible for managing projects often ask us how we do it. This is how. There is no book that tells you how to do it. We are on a road with many bumps and ups and downs, and TLDP seemingly hangs together with hooks and eyes--but it's there and it doesn't go away.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
|Secure Server Deployments in Hostile Territory, Part II||Jul 29, 2015|
|Hacking a Safe with Bash||Jul 28, 2015|
|KDE Reveals Plasma Mobile||Jul 28, 2015|
|Huge Package Overhaul for Debian and Ubuntu||Jul 23, 2015|
|diff -u: What's New in Kernel Development||Jul 22, 2015|
|Shashlik - a Tasty New Android Simulator||Jul 21, 2015|
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- Home Automation with Raspberry Pi
- Huge Package Overhaul for Debian and Ubuntu
- The Controversy Behind Canonical's Intellectual Property Policy
- Shashlik - a Tasty New Android Simulator
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile
- diff -u: What's New in Kernel Development
- Purism Librem 13 Review