Mer/Documentation/Vendor Social Contract - Revision history

amigadave: /* No tivoization */ fix link

amigadave — Wed, 22 Sep 2010 09:42:53 GMT

No tivoization: fix link

← Older revision		Revision as of 09:42, 22 September 2010
Line 5:		Line 5:
	==No tivoization==		==No tivoization==

-	{{quotation\|[:wikipedia:Tivoization\|Tivoization] is the creation of a system that incorporates software under the terms of a copyleft software license, but uses hardware to prevent users from running modified versions of the software on that hardware.}}	+	{{quotation\|[[:wikipedia:Tivoization\|Tivoization]] is the creation of a system that incorporates software under the terms of a copyleft software license, but uses hardware to prevent users from running modified versions of the software on that hardware.}}

	A user of your device, running Mer, should always be able to replace the OS image with one of their own making. This can be fulfilled by:		A user of your device, running Mer, should always be able to replace the OS image with one of their own making. This can be fulfilled by:

amigadave: {{Mer}}

amigadave — Wed, 22 Sep 2010 09:42:32 GMT

← Older revision		Revision as of 09:42, 22 September 2010
Line 1:		Line 1:
		+	{{Mer}}
		+
	The “Vendor Social Contract” is how we'd like to position the Mer/Vendor relationship. We politely ''request'':		The “Vendor Social Contract” is how we'd like to position the Mer/Vendor relationship. We politely ''request'':

	==No tivoization==		==No tivoization==

-	{{quotation\|[~~http~~:~~//en.~~wikipedia~~.org/wiki/~~Tivoization Tivoization] is the creation of a system that incorporates software under the terms of a copyleft software license, but uses hardware to prevent users from running modified versions of the software on that hardware.}}	+	{{quotation\|[:wikipedia:Tivoization\|Tivoization] is the creation of a system that incorporates software under the terms of a copyleft software license, but uses hardware to prevent users from running modified versions of the software on that hardware.}}

	A user of your device, running Mer, should always be able to replace the OS image with one of their own making. This can be fulfilled by:		A user of your device, running Mer, should always be able to replace the OS image with one of their own making. This can be fulfilled by:
Line 40:		Line 42:
	* Respect the copyright/patent/license limitations that vendors may be faced with when distributing software.		* Respect the copyright/patent/license limitations that vendors may be faced with when distributing software.
	* Support vendors in finding open solutions if desired.		* Support vendors in finding open solutions if desired.
-
-	~~[[Category:Mer]]~~

generalantilles: /* No tivoization */

generalantilles — Thu, 22 Oct 2009 21:06:16 GMT

No tivoization

← Older revision		Revision as of 21:06, 22 October 2009
Line 3:		Line 3:
	==No tivoization==		==No tivoization==

-	{{quotation\|[http://en.wikipedia.org/wiki/Tivoization Tivoization]] is the creation of a system that incorporates software under the terms of a copyleft software license, but uses hardware to prevent users from running modified versions of the software on that hardware.}}	+	{{quotation\|[http://en.wikipedia.org/wiki/Tivoization Tivoization] is the creation of a system that incorporates software under the terms of a copyleft software license, but uses hardware to prevent users from running modified versions of the software on that hardware.}}

	A user of your device, running Mer, should always be able to replace the OS image with one of their own making. This can be fulfilled by:		A user of your device, running Mer, should always be able to replace the OS image with one of their own making. This can be fulfilled by:

generalantilles at 21:05, 22 October 2009

generalantilles — Thu, 22 Oct 2009 21:05:55 GMT

← Older revision		Revision as of 21:05, 22 October 2009
Line 1:		Line 1:
-	~~= Vendor Social contract for hardware vendors =~~
-
	The “Vendor Social Contract” is how we'd like to position the Mer/Vendor relationship. We politely ''request'':		The “Vendor Social Contract” is how we'd like to position the Mer/Vendor relationship. We politely ''request'':

generalantilles: Copy-editing

generalantilles — Thu, 22 Oct 2009 21:05:37 GMT

Copy-editing

← Older revision		Revision as of 21:05, 22 October 2009
Line 1:		Line 1:
	= Vendor Social contract for hardware vendors =		= Vendor Social contract for hardware vendors =

-	The “Vendor Social Contract” is how we'd like to position the Mer/Vendor relationship.	+	The “Vendor Social Contract” is how we'd like to position the Mer/Vendor relationship. We politely ''request'':
-		+
-	We politely '''request''':	+

	==No tivoization==		==No tivoization==

-	{{quotation\|[http://en.wikipedia.org/wiki/Tivoization Tivoization] is the creation of a system that incorporates software under the terms of a copyleft software license, but uses hardware to prevent users from running modified versions of the software on that hardware.}}	+	{{quotation\|[http://en.wikipedia.org/wiki/Tivoization Tivoization]] is the creation of a system that incorporates software under the terms of a copyleft software license, but uses hardware to prevent users from running modified versions of the software on that hardware.}}

-	A user of your device, running Mer, should always be able to replace the OS image ~~on your device~~ with one of their own making ~~with ease~~. This can be fulfilled by:	+	A user of your device, running Mer, should always be able to replace the OS image with one of their own making. This can be fulfilled by:
-	* Not using hardware to prevent users from running modified versions of the OS	+	* Not using hardware to prevent users from running modified versions of the OS.
-	* ~~Bootloaders should not need firmwares to be~~ signed.	+	* Not requiring signed firmwares.
-	* ~~Ideally publishing~~ bootloader specifications (firmware format and methods of firmware replacement)	+	* Publishing bootloader specifications (firmware format and methods of firmware replacement).

-	(Note: Mer does use some GPLv3 software, so tivoization may ~~actually~~ contravene the license ~~for those applications~~)	+	(Note: Mer does use some GPLv3 software, so tivoization may contravene the license of some software.)

	== Open source kernel modules ==		== Open source kernel modules ==
Line 20:		Line 18:
	Please publish the source for any modules required to access hardware on the device.		Please publish the source for any modules required to access hardware on the device.

-	* Allows a modern ~~kernel~~ in ~~5 yr old device~~	+	* Allows users to use modern kernels in their devices.
-	* Permit ~~future~~ development of Mer for the device.	+	* Permit continued development of Mer for the device.
-	* ~~Advantage is community~~ ongoing support.	+	* Allows ongoing community support.

-	Open source software allows the development team to keep your drivers up to date, whenever Mer framework changes require driver modifications.	+	Open source software allows the development team to keep your drivers up to date whenever Mer framework changes require driver modifications.

-	==Redistribution ~~of firmware/hardware support software and any “differentiation” code~~ is allowed==	+	==Redistribution is allowed==

-	We ask that you allow the Mer community to distribute binary copies of any closed-source firmware ~~and/~~or hardware support software that is needed to support your device.	+	We ask that you allow the Mer community to distribute binary copies of any closed-source firmware or hardware-support software that is needed to support your device.

-	If absolutely required, the Mer community can organize a procedure ~~so the~~ firmware ~~and/~~or hardware support software is only ~~distributable~~ to users of your device, behind EULA, identified with their serial number, or MAC address, etc.	+	If absolutely required, the Mer community can organize a procedure to distribute firmware or hardware-support software only to users of your device, behind EULA and identified with their serial number or MAC address, etc.

-	If you choose to differentiate your device through closed-source bundled application software too (~~eg flash~~), we ask that you allow the same distribution rights for this.	+	If you choose to differentiate your device through closed-source bundled application software too (e.g., Flash), we ask that you allow the same distribution rights for this software.

-	~~The advantage is that a~~ user of your device can at any point in the future build a fresh Mer OS image without losing any functionality ~~in software or hardware that~~ they had ~~when~~ with the original firmware.	+	A user of your device can then, at any point in the future, build a fresh Mer OS image without losing any functionality they had with the original firmware

-	=Community Reciprocation=	+	==Community Reciprocation==

-	The community is committed to 100% OSS and ~~want~~ to support ~~organisations~~ moving ~~down that road although~~ we ~~recognise~~ and respect that they may not, at this time, ~~have~~ that ~~objective themselves~~.	+	The community is committed to 100% OSS and wants to support organizations moving towards open source. Although we recognize and respect that they may not, at this time, list that as one of their own objectives.

	The community will:		The community will:
-	* ~~support~~ the spirit of the ~~VSC~~	+	* Support the spirit of the Vendor Social Contract.
-	* ~~respect~~ the copyright/patent/license limitations that ~~the~~ vendors may be faced with when distributing software	+	* Respect the copyright/patent/license limitations that vendors may be faced with when distributing software.
-	* ~~support~~ vendors in finding open solutions if desired	+	* Support vendors in finding open solutions if desired.

	[[Category:Mer]]		[[Category:Mer]]

lma: /* Community Reciprocation */ typo

lma — Mon, 28 Sep 2009 01:28:28 GMT

Community Reciprocation: typo

← Older revision		Revision as of 01:28, 28 September 2009
Line 41:		Line 41:

	The community will:		The community will:
-	* support the spirit of the ~~VCS~~	+	* support the spirit of the VSC
	* respect the copyright/patent/license limitations that the vendors may be faced with when distributing software		* respect the copyright/patent/license limitations that the vendors may be faced with when distributing software
	* support vendors in finding open solutions if desired		* support vendors in finding open solutions if desired

	[[Category:Mer]]		[[Category:Mer]]

lbt: Community Reciprocation

lbt — Sun, 27 Sep 2009 13:33:12 GMT

Community Reciprocation

← Older revision		Revision as of 13:33, 27 September 2009
Line 36:		Line 36:
	The advantage is that a user of your device can at any point in the future build a fresh Mer OS image without losing any functionality in software or hardware that they had when with the original firmware.		The advantage is that a user of your device can at any point in the future build a fresh Mer OS image without losing any functionality in software or hardware that they had when with the original firmware.

		+	=Community Reciprocation=
		+
		+	The community is committed to 100% OSS and want to support organisations moving down that road although we recognise and respect that they may not, at this time, have that objective themselves.
		+
		+	The community will:
		+	* support the spirit of the VCS
		+	* respect the copyright/patent/license limitations that the vendors may be faced with when distributing software
		+	* support vendors in finding open solutions if desired

	[[Category:Mer]]		[[Category:Mer]]

83.6.163.30: /* Redistribution of firmware and any “differentiation” code is allowed */

83.6.163.30 — Sun, 13 Sep 2009 12:54:44 GMT

Redistribution of firmware and any “differentiation” code is allowed

← Older revision		Revision as of 12:54, 13 September 2009
Line 26:		Line 26:
	Open source software allows the development team to keep your drivers up to date, whenever Mer framework changes require driver modifications.		Open source software allows the development team to keep your drivers up to date, whenever Mer framework changes require driver modifications.

-	==Redistribution of firmware and any “differentiation” code is allowed==	+	==Redistribution of firmware/hardware support software and any “differentiation” code is allowed==

-	We ask that you allow the Mer community to distribute binary copies of any closed-source firmware that is needed to support your device.	+	We ask that you allow the Mer community to distribute binary copies of any closed-source firmware and/or hardware support software that is needed to support your device.

-	If absolutely required, the Mer community can organize a procedure so the firmware is only distributable to users of your device, behind EULA, identified with their serial number, or MAC address, etc.	+	If absolutely required, the Mer community can organize a procedure so the firmware and/or hardware support software is only distributable to users of your device, behind EULA, identified with their serial number, or MAC address, etc.

	If you choose to differentiate your device through closed-source bundled application software too (eg flash), we ask that you allow the same distribution rights for this.		If you choose to differentiate your device through closed-source bundled application software too (eg flash), we ask that you allow the same distribution rights for this.

lbt: punctuation

lbt — Thu, 10 Sep 2009 12:44:06 GMT

punctuation

← Older revision		Revision as of 12:44, 10 September 2009
Line 1:		Line 1:
-	= Social contract for hardware vendors =	+	= Vendor Social contract for hardware vendors =
		+
		+	The “Vendor Social Contract” is how we'd like to position the Mer/Vendor relationship.

-	~~The “social contract” is how we'd like to position the Mer/Vendor relationship~~
	We politely '''request''':		We politely '''request''':

lbt: /* No tivoization */

lbt — Thu, 10 Sep 2009 12:42:45 GMT

No tivoization

← Older revision		Revision as of 12:42, 10 September 2009
Line 13:		Line 13:
	* Ideally publishing bootloader specifications (firmware format and methods of firmware replacement)		* Ideally publishing bootloader specifications (firmware format and methods of firmware replacement)

-	(Nb Mer does use some GPLv3 software, so tivoization may actually contravene the license for those applications)	+	(Note: Mer does use some GPLv3 software, so tivoization may actually contravene the license for those applications)

	== Open source kernel modules ==		== Open source kernel modules ==