How To Run an Open Source Project: Difference between revisions
(→Links) |
No edit summary |
||
| Line 1: | Line 1: | ||
In an open source project, the trick is assessing capacity of contributors and doling out specific tasks. Modular breakdown into tiny chunks is essential. Collaborative literacy is key, starting with a [[Work Log]] for the [[Development Team]]. | In an open source project, the trick is assessing capacity of contributors and doling out specific tasks. Modular breakdown into tiny chunks is essential. Collaborative literacy is key, starting with a [[Work Log]] for the [[Development Team]]. | ||
Given that hackers are typically anarchistic in nature, it is important to set up an expectation of coordination. While anyone can contribute to the Wiki independently and on any topic related to creating the [[Open Source Economy]], coordinated development | Given that hackers are typically anarchistic in nature, it is important to set up an expectation of coordination. While anyone can contribute to the Wiki independently and on any topic related to creating the [[Open Source Economy]], coordinated development can deliver milestones on a predictable schedule. | ||
Projects are broken down into granular parts, such as [[3D Printer Modules]]. This allows a large team to tackle them in parallel. | Projects are broken down into granular parts, such as [[3D Printer Modules]]. This allows a large team to tackle them in parallel. | ||
Revision as of 15:14, 27 March 2019
In an open source project, the trick is assessing capacity of contributors and doling out specific tasks. Modular breakdown into tiny chunks is essential. Collaborative literacy is key, starting with a Work Log for the Development Team.
Given that hackers are typically anarchistic in nature, it is important to set up an expectation of coordination. While anyone can contribute to the Wiki independently and on any topic related to creating the Open Source Economy, coordinated development can deliver milestones on a predictable schedule.
Projects are broken down into granular parts, such as 3D Printer Modules. This allows a large team to tackle them in parallel.
A clear Getting Involved page should be granular to the point that microtasks can be allocated efficiently. A Contributing Tutorial Video should be prepared to emphasize the Work Log, Wiki, using FreeCAD, and using Google Docs.
Links
- Getting Involved - page listing all onboarding channels
- OSE Social Contract - OSE's promise to the world
- The Book - The project foundational text. In process, expected to be published a year from now.