Collaborative Waste

From Open Source Ecology
Revision as of 19:23, 9 August 2019 by Marcin (talk | contribs) (Created page with "*By [https://opensource.com/users/dbhurley] - 12 issues of open source - https://opensource.com/life/14/6/12-challenges-open-source-projects =Solutions= #Establishing a sta...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Solutions

  1. Establishing a standard for code submissions
  2. requiring acceptance of a common license
  3. implementing peer review are three ways in which good open source projects help to mitigate the risk of problematic code.
    1. For HeroX - update videos for contributions. Rewarding your contributions. You MUST inform people of your work, and allow them to contribute

Scope Solutions

  1. Modular breakdown to as many small pieces as possible
  2. Doing critical contributions only, not derivative ones, and phasing progress. For ex, CAD is king as the deliverable; an exploded part diagram may be in a subsequent phase (User Manual Phase).
Retrieved from "https://wiki.opensourceecology.org/index.php?title=Collaborative_Waste&oldid=196149"