Collaborative Waste

From Open Source Ecology
Revision as of 18:23, 22 August 2019 by Marcin (talk | contribs)
Jump to navigation Jump to search

Introduction

Collaborative waste is any waste that arises from large groups of people working together. There may be many sources of such waste: coordination losses, effort to produce documentation, etc.

However, in the digital age, there are tools to manage effective collaboration between large groups:

  1. Upvoting platforms


Article

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).

Direction Solutions

  1. Build it and show us the data puts a quick resulution of design debate

Judging

  • Judging and peer review can be combined. You get rewarded for working on winning versions. This forces you to contribute to something that you deem worthy - which is a form of peer review. If you work on a dead end, sorry but no cigar.