Commarch - Printrun
WORK IN PROGRESS - for now see RedTwo’s here
IRC: reprap
github: https://github.com/kliment/Printrun
documentation: https://github.com/kliment/Printrun/blob/master/README.md
other communication channels: http://reprap.org/wiki/Printrun
project website: http://www.pronterface.com/
THE PROJECT
HISTORY Patches approved by:
Commit access:
Total people with patches:
Total commits: Highest unique knowledge: Calloway Coefficient of Fail: 15
+5 for not announcing releases on mailing list
+10 for no mailing list
Core team turnover: No. BDFL/Lead Dev: Front end vs back end: J. What have been some of the major bugs/problems/issues that have arisen during development? Who is responsible for quality control and bug repair? K. How is the project's participation trending and why? L. In your opinion, does the project pass "The Raptor Test?" (i.e. Would the project survive if the BDFL, or most active contributor were eaten by a Velociraptor?) Why or why not? M. In your opinion, would the project survive if the core team, or most active 20% of contributors, were hit by a bus? Why or why not? N. Does the project have an official "on-boarding" process in place? (new contributor guides, quickstarts, communication leads who focus specifically on newbies, etc...) O. Does the project have Documentation available? Is it extensive? Does it include code examples? P. If you were going to contribute to this project, but ran into trouble or hit blockers, who would you contact, and how? Q. Based on these answers, how would you describe the decision making structure/process of this group? Is it hierarchical, consensus building, ruled by a small group, barely contained chaos, or ruled by a single or pair of individuals? R. Is this the kind of structure you would enjoy working in? Why, or why not?