Producing Open Source Software: Difference between revisions

[[Trustroots Wiki]] is an independent wiki with information for people who are actively exchanging hospitality.
Jump to navigationJump to search
from cs wiki
 
No edit summary
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
[http://producingoss.com/ Producing Open Source Software] is a great book by Karl Fogel, on how free software projects function and how to keep them functioning. "How to Run a Successful Free Software Project." Some ideas are useful for [[CouchSurfing]] right now, and some could be of help to make CS even more free and open.
:''Context: [[User:Guaka|guaka]] ([[User talk:Guaka|talk]]) started this article in 2006.''
 
[http://producingoss.com/ Producing Open Source Software] is a great book by Karl Fogel, on how free software projects function and how to keep them functioning. "How to Run a Successful Free Software Project."  
 
<blockquote>"This book is meant for managers and software developers who are considering starting an open source project, or who have started one and are wondering what to do now. It should also be helpful for people who just want to participate in an open source project but have never done so before."</blockquote>
 
 
Some ideas are useful for [[CouchSurfing]] right now, and some could be of help to make CS even more free and open.


It's [http://producingoss.com/html-chunk/index.html available online].
It's [http://producingoss.com/html-chunk/index.html available online].


==[http://producingoss.com/html-chunk/technical-infrastructure.html#tools-needed What a project needs]==
== [http://producingoss.com/html-chunk/technical-infrastructure.html#tools-needed What a project needs] ==
* Website
* Website
** but not CouchSurfing.com, could be wiki or <strike>dev-wiki</strike>
** but not CouchSurfing.com, could be wiki or <strike>dev-wiki</strike>
Line 14: Line 21:
** IRC, freenode? #couchsurfing (welcome to check out #couchsurfing on IRCnet!) Or some more closed system
** IRC, freenode? #couchsurfing (welcome to check out #couchsurfing on IRCnet!) Or some more closed system


== Social and Political Infrastructure==
== Social and Political Infrastructure ==


== Communications ==
== Communications ==


== Packaging, Releasing, and Daily Development==
== Packaging, Releasing, and Daily Development ==


== Managing Volunteers ==
== Managing Volunteers ==
Line 30: Line 37:
* The Automation Ratio
* The Automation Ratio


**Automated testing
** Automated testing


'''Treat Every User as a Potential Volunteer'''
'''Treat Every User as a Potential Volunteer'''
Line 37: Line 44:
** Patch Manager
** Patch Manager
** Translation Manager
** Translation Manager
**Documentation Manager
** Documentation Manager
** Issue Manager
** Issue Manager
** FAQ Manager
** FAQ Manager
Line 51: Line 58:
* Credit
* Credit


[[Category: Free software]]
[[Category:Free software]]

Latest revision as of 21:03, 26 July 2020

Context: guaka (talk) started this article in 2006.

Producing Open Source Software is a great book by Karl Fogel, on how free software projects function and how to keep them functioning. "How to Run a Successful Free Software Project."

"This book is meant for managers and software developers who are considering starting an open source project, or who have started one and are wondering what to do now. It should also be helpful for people who just want to participate in an open source project but have never done so before."


Some ideas are useful for CouchSurfing right now, and some could be of help to make CS even more free and open.

It's available online.

  • Website
    • but not CouchSurfing.com, could be wiki or dev-wiki
  • Mailing lists
    • and not the CS groups please
  • Version control
  • Bug tracking
  • Real-time chat
    • NO Flash!
    • IRC, freenode? #couchsurfing (welcome to check out #couchsurfing on IRCnet!) Or some more closed system

Social and Political Infrastructure

[edit]

Communications

[edit]

Packaging, Releasing, and Daily Development

[edit]

Managing Volunteers

[edit]
  • Getting the Most Out of Volunteers
    • Delegation
      • 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
  • Transitions
  • Committers
    • Choosing Committers
    • Revoking Commit Access
    • Partial Commit Access
    • Dormant Committers
    • Avoid Mystery
  • Credit