Collaborative Waste - Revision history

Wesxdz: /* Introduction */

2021-11-19T21:02:52Z

Introduction

← Older revision		Revision as of 21:02, 19 November 2021
Line 9:		Line 9:
	#Upvoting platforms for distilling content so content transforms from cacophony to distilled wisdom		#Upvoting platforms for distilling content so content transforms from cacophony to distilled wisdom
	#Wikis - to manage large amounts of data collaboratively		#Wikis - to manage large amounts of data collaboratively
	#Live editable documents - such as Google Presentation - for large realtime design effort		#Live editable documents - such as Google Presentation/Colab - for large realtime design effort
	#Part libraries and open source CAD - with clear submission and file format guidelines, large part libraries can be managed effectively for large scale collaboration where many people work on different modules		#Part libraries and open source CAD - with clear submission and file format guidelines, large part libraries can be managed effectively for large scale collaboration where many people work on different modules
	#[[Realtime Documentation]] - ~~ivolving~~ remote teams in documentation and video production at the same time that a design/build occurs		#[[Realtime Documentation]] - involving remote teams in documentation and video production at the same time that a design/build occurs
	==Collaborative Waste of Documentation==		==Collaborative Waste of Documentation==
	Anyone who has worked on open source projects recognizes the vast effort required to document everything. For this reason, documentation is typically lacking. However, we emphasize that documentation is the only way that a project can scale. Writing has been developed 10,000 years ago, which allowed [[Time Binding]] to occur. In the 1990s, the wiki was developed. In the 2000s, live editable docs became a reality. Thus, in the digital age, we are not short of adequate tools for distributed documentation. The benefit of documentation outweighs the cost.		Anyone who has worked on open source projects recognizes the vast effort required to document everything. For this reason, documentation is typically lacking. However, we emphasize that documentation is the only way that a project can scale. Writing has been developed 10,000 years ago, which allowed [[Time Binding]] to occur. In the 1990s, the wiki was developed. In the 2000s, live editable docs became a reality. Thus, in the digital age, we are not short of adequate tools for distributed documentation. The benefit of documentation outweighs the cost.

Marcin: /* Introduction */

2020-07-17T12:36:23Z

Introduction

← Older revision		Revision as of 12:36, 17 July 2020
Line 2:		Line 2:
	=Introduction=		=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 (which is not a waste if this helps future generations), etc.		Collaborative waste is any ''waste'' that arises from large groups of people working together. There may be many sources of such waste: coordination losses, people not producing documentation, the sheer effort to produce documentation (which is not a waste if this helps future generations), etc.

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

Marcin: /* Introduction */

2020-01-08T00:16:46Z

Introduction

← Older revision		Revision as of 00:16, 8 January 2020
Line 2:		Line 2:
	=Introduction=		=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.		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 (which is not a waste if this helps future generations), etc.

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

Marcin: /* Collaborative Waste of Documentation */

2019-08-22T18:29:46Z

Collaborative Waste of Documentation

← Older revision		Revision as of 18:29, 22 August 2019
Line 13:		Line 13:
	#[[Realtime Documentation]] - ivolving remote teams in documentation and video production at the same time that a design/build occurs		#[[Realtime Documentation]] - ivolving remote teams in documentation and video production at the same time that a design/build occurs
	==Collaborative Waste of Documentation==		==Collaborative Waste of Documentation==
	Anyone who has worked on open source projects recognizes the vast effort required to document everything. For this reason, documentation is typically lacking. However, we emphasize that documentation is the only way that a project can scale. Writing has been developed 10,000 years ago, ~~so that~~ [[Time Binding]] ~~can~~ occur. In the 1990s, the wiki was developed. In the 2000s, live editable docs became a reality. Thus, in the digital age, we are not short of adequate tools for distributed documentation. The benefit of documentation outweighs the cost.		Anyone who has worked on open source projects recognizes the vast effort required to document everything. For this reason, documentation is typically lacking. However, we emphasize that documentation is the only way that a project can scale. Writing has been developed 10,000 years ago, which allowed [[Time Binding]] to occur. In the 1990s, the wiki was developed. In the 2000s, live editable docs became a reality. Thus, in the digital age, we are not short of adequate tools for distributed documentation. The benefit of documentation outweighs the cost.

	However, there must be clear standards for how to document: tools used, file formats accepted, best practices.		However, there must be clear standards for how to document: tools used, file formats accepted, best practices.

Marcin: /* Introduction */

2019-08-22T18:29:25Z

Introduction

← Older revision		Revision as of 18:29, 22 August 2019
Line 11:		Line 11:
	#Live editable documents - such as Google Presentation - for large realtime design effort		#Live editable documents - such as Google Presentation - for large realtime design effort
	#Part libraries and open source CAD - with clear submission and file format guidelines, large part libraries can be managed effectively for large scale collaboration where many people work on different modules		#Part libraries and open source CAD - with clear submission and file format guidelines, large part libraries can be managed effectively for large scale collaboration where many people work on different modules
	#[[Realtime Documentation]] - ~~nvolving~~ remote teams in documentation and video production		#[[Realtime Documentation]] - ivolving remote teams in documentation and video production at the same time that a design/build occurs
	==Collaborative Waste of Documentation==		==Collaborative Waste of Documentation==
	Anyone who has worked on open source projects recognizes the vast effort required to document everything. For this reason, document		Anyone who has worked on open source projects recognizes the vast effort required to document everything. For this reason, documentation is typically lacking. However, we emphasize that documentation is the only way that a project can scale. Writing has been developed 10,000 years ago, so that [[Time Binding]] can occur. In the 1990s, the wiki was developed. In the 2000s, live editable docs became a reality. Thus, in the digital age, we are not short of adequate tools for distributed documentation. The benefit of documentation outweighs the cost.

			However, there must be clear standards for how to document: tools used, file formats accepted, best practices.

	=Article=		=Article=

Marcin: /* Introduction */

2019-08-22T18:27:04Z

Introduction

← Older revision		Revision as of 18:27, 22 August 2019
Line 11:		Line 11:
	#Live editable documents - such as Google Presentation - for large realtime design effort		#Live editable documents - such as Google Presentation - for large realtime design effort
	#Part libraries and open source CAD - with clear submission and file format guidelines, large part libraries can be managed effectively for large scale collaboration where many people work on different modules		#Part libraries and open source CAD - with clear submission and file format guidelines, large part libraries can be managed effectively for large scale collaboration where many people work on different modules
			#[[Realtime Documentation]] - nvolving remote teams in documentation and video production
			==Collaborative Waste of Documentation==
			Anyone who has worked on open source projects recognizes the vast effort required to document everything. For this reason, document

	=Article=		=Article=

Marcin at 18:25, 22 August 2019

2019-08-22T18:25:54Z

← Older revision		Revision as of 18:25, 22 August 2019
Line 5:		Line 5:

	However, in the digital age, there are tools to manage effective collaboration between large groups:		However, in the digital age, there are tools to manage effective collaboration between large groups:
			#Modular breakdown - breakdown of complex problems into small parts is a critical tool for solving large problems with many people
			#Role definition - defining clear roles, tasks, and skill sets required to work on tasks
	#Upvoting platforms for distilling content so content transforms from cacophony to distilled wisdom		#Upvoting platforms for distilling content so content transforms from cacophony to distilled wisdom
	#Wikis - to manage large amounts of data collaboratively		#Wikis - to manage large amounts of data collaboratively
	#Live editable documents - such as Google Presentation - for large realtime design effort		#Live editable documents - such as Google Presentation - for large realtime design effort
	#		#Part libraries and open source CAD - with clear submission and file format guidelines, large part libraries can be managed effectively for large scale collaboration where many people work on different modules

Marcin at 18:23, 22 August 2019

2019-08-22T18:23:59Z

← Older revision		Revision as of 18:23, 22 August 2019
Line 5:		Line 5:

	However, in the digital age, there are tools to manage effective collaboration between large groups:		However, in the digital age, there are tools to manage effective collaboration between large groups:
	#Upvoting platforms		#Upvoting platforms for distilling content so content transforms from cacophony to distilled wisdom
			#Wikis - to manage large amounts of data collaboratively
			#Live editable documents - such as Google Presentation - for large realtime design effort
			#

Marcin at 18:23, 22 August 2019

2019-08-22T18:23:03Z

← Older revision		Revision as of 18:23, 22 August 2019
Line 1:		Line 1:

			=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:
			#Upvoting platforms


			=Article=
	*By [https://opensource.com/users/dbhurley] - 12 issues of open source - https://opensource.com/life/14/6/12-challenges-open-source-projects		*By [https://opensource.com/users/dbhurley] - 12 issues of open source - https://opensource.com/life/14/6/12-challenges-open-source-projects

	=Solutions=		==Solutions==

	#Establishing a standard for code submissions		#Establishing a standard for code submissions
Line 8:		Line 18:
	##For HeroX - update videos for contributions. Rewarding your contributions. You MUST inform people of your work, and allow them to contribute		##For HeroX - update videos for contributions. Rewarding your contributions. You MUST inform people of your work, and allow them to contribute

	==Scope Solutions==		===Scope Solutions===
	#Modular breakdown to as many small pieces as possible		#Modular breakdown to as many small pieces as possible
	#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).		#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==		===Direction Solutions===
	#''Build it and show us the data'' puts a quick resulution of design debate		#''Build it and show us the data'' puts a quick resulution of design debate

	=Judging=		==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.		*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.

	[[Category:Incentive Challenge]]		[[Category:Incentive Challenge]]

Marcin: /* Solutions */

2019-08-09T19:30:43Z

Solutions

← Older revision		Revision as of 19:30, 9 August 2019
Line 12:		Line 12:
	#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).		#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==
			#''Build it and show us the data'' puts a quick resulution of design debate

	=Judging=		=Judging=