Produktion af open source software

Hvordan man driver et fri software projekt med success

Karl Fogel


Mikkel Kirkgaard Nielsen

(dansk oversættelse) 


Denne bog er tilegnet mine to kære venner, uden dem havde det ikke været muligt: Karen Underhill og Jim Blandy.


Hvorfor skrive denne bog?
Hvem har interresse i at læse denne bog?
Bogens kilder
1. Introduktion
The Rise of Proprietary Software and Free Software
Conscious resistance
Accidental resistance
"Free" Versus "Open Source"
The Situation Today
2. Getting Started
Starting From What You Have
Choose a Good Name
Have a Clear Mission Statement
State That the Project is Free
Features and Requirements List
Development Status
Version Control and Bug Tracker Access
Communications Channels
Developer Guidelines
Availability of documentation
Developer documentation
Example Output and Screenshots
Canned Hosting
Choosing a License and Applying It
The "Do Anything" Licenses
How to Apply a License to Your Software
Setting the Tone
Avoid Private Discussions
Nip Rudeness in the Bud
Practice Conspicuous Code Review
When Opening a Formerly Closed Project, be Sensitive to the Magnitude of the Change
3. Technical Infrastructure
What a Project Needs
Mailing Lists
Spam Prevention
Filtering posts
Address hiding in archives
Identification and Header Management
The Great Reply-to Debate
Two fantasies
Version Control
Version Control Vocabulary
Choosing a Version Control System
Using the Version Control System
Version everything
Commit emails
Use branches to avoid bottlenecks
Singularity of information
Bug Tracker
Interaction with Mailing Lists
Pre-Filtering the Bug Tracker
IRC / Real-Time Chat Systems
Archiving IRC
Web Site
Canned Hosting
Choosing a canned hosting site
Anonymity and involvement
4. Social and Political Infrastructure
Benevolent Dictators
Who Can Be a Good Benevolent Dictator?
Consensus-based Democracy
Version Control Means You Can Relax
When Consensus Cannot Be Reached, Vote
When To Vote
Who Votes?
Polls Versus Votes
Writing It All Down
5. Money
Types of Involvement
Hire for the Long Term
Appear as Many, Not as One
Be Open About Your Motivations
Money Can't Buy You Love
Review and Acceptance of Changes
Case study: the CVS password-authentication protocol
Funding Non-Programming Activities
Quality Assurance (i.e., Professional Testing)
Legal Advice and Protection
Documentation and Usability
Providing Hosting/Bandwidth
Remember That You Are Being Watched
Don't Bash Competing Open Source Products
6. Communications
You Are What You Write
Structure and Formatting
Recognizing Rudeness
Avoiding Common Pitfalls
Don't Post Without a Purpose
Productive vs Unproductive Threads
The Softer the Topic, the Longer the Debate
Avoid Holy Wars
The "Noisy Minority" Effect
Difficult People
Handling Difficult People
Case study
Handling Growth
Conspicuous Use of Archives
Treat all resources like archives
Codifying Tradition
No Conversations in the Bug Tracker
Announcing Security Vulnerabilities
Receive the report
Develop the fix quietly
CAN/CVE numbers
Distribute the fix publicly
7. Packaging, Releasing, and Daily Development
Release Numbering
Release Number Components
The Simple Strategy
The Even/Odd Strategy
Release Branches
Mechanics of Release Branches
Stabilizing a Release
Dictatorship by Release Owner
Change Voting
Managing collaborative release stabilization
Release manager
Name and Layout
To capitalize or not to capitalize
Compilation and Installation
Binary Packages
Testing and Releasing
Candidate Releases
Announcing Releases
Maintaining Multiple Release Lines
Security Releases
Releases and Daily Development
Planning Releases
8. Managing Volunteers
Getting the Most Out of Volunteers
Distinguish clearly between inquiry and assignment
Follow up after you delegate
Notice what people are interested in
Praise and Criticism
Prevent Territoriality
The Automation Ratio
Automated testing
Treat Every User as a Potential Volunteer
Share Management Tasks as Well as Technical Tasks
Patch Manager
Translation Manager
Documentation Manager
Issue Manager
FAQ Manager
Choosing Committers
Revoking Commit Access
Partial Commit Access
Dormant Committers
Avoid Mystery
Handling a Fork
Initiating a Fork
9. Licenses, Copyrights, and Patents
Aspects of Licenses
The GPL and License Compatibility
Choosing a License
The MIT / X Window System License
The GNU General Public License
Is the GPL free or not free?
What About The BSD License?
Copyright Assignment and Ownership
Doing Nothing
Contributor License Agreements
Transfer of Copyright
Dual Licensing Schemes
Further Resources
A. Free Version Control Systems
B. Free Bug Trackers
C. Why Should I Care What Color the Bikeshed Is?
D. Example Instructions for Reporting Bugs
E. Copyright