Editing Mer/Documentation/Vendor Social Contract

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
-
{{Mer}}
 
-
The “Vendor Social Contract” is how we'd like to position the Mer/Vendor relationship. We politely ''request'':
+
== Social contract for hardware vendors ==
-
==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.}}
+
<quote>
 +
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.
 +
</quote>
-
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 on your device with one of his own making with ease. This can be fullfilled through:
-
* Not using hardware to prevent users from running modified versions of the OS.
+
-
* Not requiring signed firmwares.
+
-
* Publishing bootloader specifications (firmware format and methods of firmware replacement).
+
-
(Note: Mer does use some GPLv3 software, so tivoization may contravene the license of some software.)
+
* Avoiding bootloaders and firmware replacement software requiring firmwares to be signed.
 +
* Publishing to the Mer community information on bootloader, firmware format and methods of firmware replacement.
-
== Open source kernel modules ==
+
Be aware that Mer uses GPLv3-licensed software, so tivoization may already be forbidden.
-
Please publish the source for any modules required to access hardware on the device.
+
=== Open source kernel modules ===
-
* Allows users to use modern kernels in their devices.
+
We ask that kernel modules used for your device is open source. In 5 years, it should still be possible to get a modern kernel running on your device, and closed source kernel modules are linked to specific kernel versions, hence hindering future development of Mer for your device.  
-
* Permit continued development of Mer for the device.
+
-
* 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.
+
The advantage for you is that community members with your device can continue development for your device, even when your company has moved on.
-
==Redistribution is allowed==
+
=== Redistribution of firmware and differentiation ==
-
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.
+
We ask that you seek to allow the Mer community to redistribute binary copies of any firmware that is needed to support your device. The Mer community can organize a procedure such that the firmware is only redistributable to users of your device, 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 bundled software, we ask that you allow same redistribution 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 he had when he had 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==
+
-
 
+
-
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:
+
-
* Support the spirit of the Vendor Social Contract.
+
-
* Respect the copyright/patent/license limitations that vendors may be faced with when distributing software.
+
-
* Support vendors in finding open solutions if desired.
+

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)

Templates used on this page:

Retrieved from "https://wiki.maemo.org/Mer/Documentation/Vendor_Social_Contract"