Keyword: Maintainer model
-
Software development is most of all a social process
- Voluntarism as fundamental pre-condition
- No alienated incentives
- Makes possible and requires personal decision
- Self-organization as fundamental pre-condition
- Without external command or alienated goals
Visible for instance in release dates
- Without external command or alienated goals
- Maintainer keeps the project on course
- Makes binding decisions
- Supervises adherence to internal project standards
- If necessary cares for further development
- Organizes consensus ("Nobody needs to object")
Not: Animosity - Can not command other participants
- Mutual dependence
Participants need the functions of the maintainer
Maintainer needs the participants- On failure: Fork
Maintainer model is a frequent way to organize
Here: Doubly Free Software projects
Balances conflicts in Free Projects in an optimal way