Producing Open Source Software : How to Run a Successful Free Software Project


Karl. Fogel
Bok Engelsk 2009 · Electronic books.
Utgitt
Sebastopol : : O'Reilly Media, , 2009.
Omfang
1 online resource (304 p.)
Opplysninger
Description based upon print version of record.. - Producing Open Source Software; Preface; Who Should Read This Book?; How to Use This Book; Sources; Conventions; Comments and Questions; Safari Enabled; Acknowledgments; Disclaimer; 1. Introduction; 1.1.1.2. Accidental resistance; 1.1.2. Free Versus Open Source; 1.2. The Situation Today; 2. Getting Started; 2.2. Starting from What You Have; 2.2.2. Have a Clear Mission Statement; 2.2.3. State that the Project Is Free; 2.2.4. Features and Requirements List; 2.2.5. Development Status; 2.2.6. Downloads; 2.2.7. Version Control and Bug Tracker Access; 2.2.8. Communications Channels. - 2.2.9. Developer Guidelines2.2.10. Documentation; 2.2.10.2. Developer documentation; 2.2.11. Example Output and Screenshots; 2.2.12. Canned Hosting; 2.3. Choosing a License and Applying It; 2.3.2. The GPL; 2.3.3. How to Apply a License to Your Software; 2.4. Setting the Tone; 2.4.2. Nip Rudeness in the Bud; 2.4.3. Practice Conspicuous Code Review; 2.4.4. When Opening a Formerly Closed Project, Be Sensitive to the Magnitude of the Change; 2.5. Announcing; 3. Technical Infrastructure; 3.2. Mailing Lists; 3.2.1.2. Address hiding in archives; 3.2.2. Identification and Header Management. - 3.2.3. The Great Reply-to Debate3.2.4. Archiving; 3.2.5. Software; 3.3. Version Control; 3.3.2. Choosing a Version Control System; 3.3.3. Using the Version Control System; 3.3.3.2. Browseability; 3.3.3.3. Commit emails; 3.3.3.4. Use branches to avoid bottlenecks; 3.3.3.5. Singularity of information; 3.3.3.6. Authorization; 3.4. Bug Tracker; 3.4.2. Prefiltering the Bug Tracker; 3.5. IRC/Real-Time Chat Systems; 3.5.2. Archiving IRC; 3.6. Wikis; 3.7. Web Site; 3.7.1.2. Anonymity and involvement; 4. Social and Political Infrastructure; 4.2. Benevolent Dictators; 4.3. Consensus-Based Democracy. - 4.3.2. When Consensus Cannot Be Reached, Vote4.3.3. When to Vote; 4.3.4. Who Votes?; 4.3.5. Polls Versus Votes; 4.3.6. Vetoes; 4.4. Writing It All Down; 5. Money; 5.2. Hire for the Long Term; 5.3. Appear as Many, Not as One; 5.4. Be Open About Your Motivations; 5.5. Money Can&t Buy You Love; 5.6. Contracting; 5.7. Funding Non-Programming Activities; 5.7.2. Legal Advice and Protection; 5.7.3. Documentation and Usability; 5.7.4. Providing Hosting/Bandwidth; 5.8. Marketing; 5.8.2. Don&t Bash Competing Open Source Products; 6. Communications; 6.1.2. Content; 6.1.3. Tone. - 6.1.4. Recognizing Rudeness6.1.5. Face; 6.2. Avoiding Common Pitfalls; 6.2.2. Productive Versus Unproductive Threads; 6.2.3. The Softer the Topic, the Longer the Debate; 6.2.4. Avoid Holy Wars; 6.2.5. The ""Noisy Minority"" Effect; 6.3. Difficult People; 6.3.2. Case Study; 6.4. Handling Growth; 6.4.2. Codifying Tradition; 6.5. No Conversations in the Bug Tracker; 6.6. Publicity; 6.6.1.2. Develop the fix quietly; 6.6.1.3. CAN/CVE numbers; 6.6.1.4. Pre-notification; 6.6.1.5. Distribute the fix publicly; 7. Packaging, Releasing, and Daily Development; 7.1.2. The Simple Strategy. - 7.1.3. The Even/Odd Strategy. - The corporate market is now embracing free, ""open source"" software like never before, as evidenced by the recent success of the technologies underlying LAMP (Linux, Apache, MySQL, and PHP). Each is the result of a publicly collaborative process among numerous developers who volunteer their time and energy to create better software. The truth is, however, that the overwhelming majority of free software projects fail. To help you beat the odds, O'Reilly has put together Producing Open Source Software, a guide that recommends tried and true steps to help free software dev
Emner
Sjanger
Dewey
005.3 . - 005.1
ISBN
0596007590

Bibliotek som har denne