OSHW Dashboard - Revision history

Marcin: /* How Does it Work? */

2016-02-03T19:51:15Z

How Does it Work?

← Older revision		Revision as of 19:51, 3 February 2016
Line 14:		Line 14:
	If an individual who is not part of a larger project is developing open source hardware, then the Entity name should be replaced with a person's name.		If an individual who is not part of a larger project is developing open source hardware, then the Entity name should be replaced with a person's name.

	This standard is recommended for use as a hashtag, or an XML tag embedded in documentation or on websites, etc. It isThis standard currently has no formal platform for implementation, nor a verification schema.		This standard is recommended for use as a hashtag, or an XML tag embedded in documentation or on websites, etc. It isThis standard currently has no formal platform for implementation, nor a verification schema.

			=Why it Works=
			Since the ''OSHW-'' has a clear brand related to the [[Open Source Hardware Association]], any tags beginning with these letters are usually associated with open source hardware.

	=Full OSHW Dashboard=		=Full OSHW Dashboard=

Marcin: /* Content */

2016-02-03T19:47:19Z

Content

← Older revision		Revision as of 19:47, 3 February 2016
Line 16:		Line 16:
	This standard is recommended for use as a hashtag, or an XML tag embedded in documentation or on websites, etc. It isThis standard currently has no formal platform for implementation, nor a verification schema.		This standard is recommended for use as a hashtag, or an XML tag embedded in documentation or on websites, etc. It isThis standard currently has no formal platform for implementation, nor a verification schema.

	=~~Content~~=		=Full OSHW Dashboard=

	These are the essential metatags and metadescriptors to be incorporated into documentation of open hardware projects:		These are the essential metatags and metadescriptors to be incorporated into documentation of open hardware projects:
Line 32:		Line 32:
	#Predecessors – This project descended from…		#Predecessors – This project descended from…
	#Content Location – A URL to the main project repository		#Content Location – A URL to the main project repository


	=Example from Website=		=Example from Website=

Marcin at 19:41, 3 February 2016

2016-02-03T19:41:00Z

← Older revision		Revision as of 19:41, 3 February 2016
Line 3:		Line 3:
	This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified within the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013. Currently, OSE is committing to usig this format, and wider adoption is sought.		This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified within the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013. Currently, OSE is committing to usig this format, and wider adoption is sought.

	The concept is that [[OSHWA]]-compliant open hardware projects should be identified non-ambiguously as such, and other projects that do not comply with the OSHWA standard cannot use the open source label. Such license clarity helps to promote collaboration, while not diluting the Open Source brand with ''fake open source.'' Anything that does not provide the [[4 Freedoms]] of ~~free and open source software~~ is not open source. The point to consider here is that Open Source has a strict definition (see OSHWA), which has in turn been founded on the [[OSI Definition]]. There is legacy here, yet lack of this historical knowledge has led to an effective re-definition in popular media. The current popular definition of open source has been watered down to, essentially, ''something cool'', not a body of work that follows the principles set forth by the [[Open Source Hardware Association]].		The concept is that [[OSHWA]]-compliant open hardware projects should be identified non-ambiguously as such, and other projects that do not comply with the OSHWA standard cannot use the open source label. Such license clarity helps to promote collaboration, while not diluting the Open Source brand with ''fake open source.'' Anything that does not provide the [[4 Freedoms]] defined by [[Richard Stallman]] of the [[Free Software Foundation]] is not open source. The point to consider here is that Open Source has a strict definition (see OSHWA), which has in turn been founded on the [[OSI Definition]]. There is legacy here, yet lack of this historical knowledge has led to an effective re-definition in popular media. The current popular definition of open source has been watered down to, essentially, ''something cool'', not a body of work that follows the principles set forth by the [[Open Source Hardware Association]].

	=How Does it Work?=		=How Does it Work?=

Marcin at 19:39, 3 February 2016

2016-02-03T19:39:54Z

← Older revision		Revision as of 19:39, 3 February 2016
Line 3:		Line 3:
	This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified within the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013. Currently, OSE is committing to usig this format, and wider adoption is sought.		This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified within the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013. Currently, OSE is committing to usig this format, and wider adoption is sought.

	The concept is that [[OSHWA]]-compliant open hardware projects should be identified non-ambiguously as such, and other projects that do not comply with the OSHWA standard ~~do not~~ use the open source label ~~without merit~~. Such license clarity helps to promote collaboration, while not diluting the ~~Ope~~ Source brand with ''fake open source'' ~~which are~~ not ~~open to~~ the [[4 Freedoms]] of free and open source software. The point to consider here is that Open Source has a strict definition (see OSHWA), which has in turn been founded on the [[OSI Definition]]. There is legacy here, yet lack of this historical knowledge has led to an effective re-definition in popular media. The current popular definition of open source has been watered down to, essentially, ''something cool'', not a body of work that follows the principles set forth by the [[Open Source Hardware Association]].		The concept is that [[OSHWA]]-compliant open hardware projects should be identified non-ambiguously as such, and other projects that do not comply with the OSHWA standard cannot use the open source label. Such license clarity helps to promote collaboration, while not diluting the Open Source brand with ''fake open source.'' Anything that does not provide the [[4 Freedoms]] of free and open source software is not open source. The point to consider here is that Open Source has a strict definition (see OSHWA), which has in turn been founded on the [[OSI Definition]]. There is legacy here, yet lack of this historical knowledge has led to an effective re-definition in popular media. The current popular definition of open source has been watered down to, essentially, ''something cool'', not a body of work that follows the principles set forth by the [[Open Source Hardware Association]].

	=How Does it Work?=		=How Does it Work?=

Marcin: /* Introduction */

2016-02-03T19:37:30Z

Introduction

← Older revision		Revision as of 19:37, 3 February 2016
Line 3:		Line 3:
	This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified within the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013. Currently, OSE is committing to usig this format, and wider adoption is sought.		This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified within the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013. Currently, OSE is committing to usig this format, and wider adoption is sought.

	The concept is that [[OSHWA]]-compliant open hardware projects should be identified non-ambiguously as such, and other projects that do not comply with the OSHWA standard do not use the open source label without merit. Such license clarity helps to promote collaboration, while not diluting the Ope Source brand with ''fake open source'' which are not open to the [[4 Freedoms]] of free and open source software. The point to consider here is that Open Source has a strict definition (see OSHWA), which has in turn been founded on the [[OSI Definition]]. There is legacy here, yet lack of this historical knowledge has led to an effective re-definition in popular media. The current popular definition of open source has been watered down to, essentially, ''something cool'', not a body of work that follows the principles set forth by the [[Open Source Hardware Association]].		The concept is that [[OSHWA]]-compliant open hardware projects should be identified non-ambiguously as such, and other projects that do not comply with the OSHWA standard do not use the open source label without merit. Such license clarity helps to promote collaboration, while not diluting the Ope Source brand with ''fake open source'' which are not open to the [[4 Freedoms]] of free and open source software. The point to consider here is that Open Source has a strict definition (see OSHWA), which has in turn been founded on the [[OSI Definition]]. There is legacy here, yet lack of this historical knowledge has led to an effective re-definition in popular media. The current popular definition of open source has been watered down to, essentially, ''something cool'', not a body of work that follows the principles set forth by the [[Open Source Hardware Association]].

	=How Does it Work?=		=How Does it Work?=

Marcin at 19:33, 3 February 2016

2016-02-03T19:33:17Z

← Older revision		Revision as of 19:33, 3 February 2016
Line 1:		Line 1:
	=Introduction=		=Introduction=

	This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified within the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013.		This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified within the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013. Currently, OSE is committing to usig this format, and wider adoption is sought.

	The concept is that [[OSHWA]]-compliant open hardware projects should be identified non-ambiguously as such, and other projects that do not comply with the OSHWA standard do not use the open source label without merit. Such license clarity helps to promote collaboration, while not diluting the Ope Source brand with ''fake open source'' which are not open to the [[4 Freedoms]] of free and open source software. The point to consider here is that Open Source has a strict definition (see OSHWA), which has in turn been founded on the [[OSI Definition]]. There is legacy here, yet lack of this historical knowledge has led to an effective re-definition in popular media. The current popular definition of open source has been watered down to, essentially, ''something cool'', not a body of work that follows the principles set forth by the [[Open Source Hardware Association]].		The concept is that [[OSHWA]]-compliant open hardware projects should be identified non-ambiguously as such, and other projects that do not comply with the OSHWA standard do not use the open source label without merit. Such license clarity helps to promote collaboration, while not diluting the Ope Source brand with ''fake open source'' which are not open to the [[4 Freedoms]] of free and open source software. The point to consider here is that Open Source has a strict definition (see OSHWA), which has in turn been founded on the [[OSI Definition]]. There is legacy here, yet lack of this historical knowledge has led to an effective re-definition in popular media. The current popular definition of open source has been watered down to, essentially, ''something cool'', not a body of work that follows the principles set forth by the [[Open Source Hardware Association]].

			=How Does it Work?=
			To identify a project as open source, the standard proposed at the [[Open Source Hardware Documentation Jam]] was a tag that begins with:

			OSHW-Entity-Project - or for example:

			OSHW-OSE-CEB_Press.

			If an individual who is not part of a larger project is developing open source hardware, then the Entity name should be replaced with a person's name.

			This standard is recommended for use as a hashtag, or an XML tag embedded in documentation or on websites, etc. It isThis standard currently has no formal platform for implementation, nor a verification schema.

	=Content=		=Content=

Marcin at 19:23, 3 February 2016

2016-02-03T19:23:56Z

← Older revision		Revision as of 19:23, 3 February 2016
Line 3:		Line 3:
	This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified within the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013.		This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified within the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013.

			The concept is that [[OSHWA]]-compliant open hardware projects should be identified non-ambiguously as such, and other projects that do not comply with the OSHWA standard do not use the open source label without merit. Such license clarity helps to promote collaboration, while not diluting the Ope Source brand with ''fake open source'' which are not open to the [[4 Freedoms]] of free and open source software. The point to consider here is that Open Source has a strict definition (see OSHWA), which has in turn been founded on the [[OSI Definition]]. There is legacy here, yet lack of this historical knowledge has led to an effective re-definition in popular media. The current popular definition of open source has been watered down to, essentially, ''something cool'', not a body of work that follows the principles set forth by the [[Open Source Hardware Association]].
	=Content=		=Content=

Marcin at 19:15, 3 February 2016

2016-02-03T19:15:48Z

← Older revision		Revision as of 19:15, 3 February 2016
Line 1:		Line 1:
	=Introduction=		=Introduction=

	This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified in the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013.		This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified within the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013.

	=Content=		=Content=

Marcin at 19:12, 3 February 2016

2016-02-03T19:12:58Z

← Older revision		Revision as of 19:12, 3 February 2016
Line 1:		Line 1:
			=Introduction=

			This is a standard for documenting Open Source Hardware Projects so that there is a uniform protocol for how OSHW projects are identified in the greater world of proprietary and open product development. This format was proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013.

			=Content=

	These are the essential metatags and metadescriptors to be incorporated into documentation of open hardware projects:		These are the essential metatags and metadescriptors to be incorporated into documentation of open hardware projects:

Line 14:		Line 20:
	#Content Location – A URL to the main project repository		#Content Location – A URL to the main project repository

	~~This is a standard proposed as a result of the [[Open Source Hardware Documentation Jam]] of 2013.~~

	=Example from Website=		=Example from Website=

Marcin: /* Example from Website */

2016-01-08T17:48:38Z

Example from Website

← Older revision		Revision as of 17:48, 8 January 2016
Line 19:		Line 19:

	<html><iframe src="https://docs.google.com/document/d/1SIvmrkY9z1e-NIHGK25xkkWn2WuFMmS3u-fV3YOlZnE/pub?embedded=true" height=600 width=500></iframe></html>		<html><iframe src="https://docs.google.com/document/d/1SIvmrkY9z1e-NIHGK25xkkWn2WuFMmS3u-fV3YOlZnE/pub?embedded=true" height=600 width=500></iframe></html>

			[https://docs.google.com/document/d/1SIvmrkY9z1e-NIHGK25xkkWn2WuFMmS3u-fV3YOlZnE/edit]

	=Procedure=		=Procedure=