OLPC und Open Source

From OLPC
Revision as of 10:06, 20 April 2007 by 134.2.35.142 (talk)
Jump to: navigation, search
  This page is monitored by the OLPC team.

deutsch | english | español | português (stub) | 한국어 | العربية

Was für uns "Offenenheit" heißt: Freiheit in der Software und OLPC

Author: Benjamin Mako Hill

Der $100-Laptop wird den Kindern Technologie als Mittel zur Freiheit und zur Selbstbestimmtheit bringen. Ein Projekt-Erfolg wird angesichts der überwältigenden globalen Unterschiede nur möglich sein, indem man Offenheit einbezieht und indem man den Laptop-Benutzern und seinen Entwicklern ein grundlegendes Maß an Freiheit bereitstellt.

Wenn die Kinder wachsen und selbst neue Ideen entwickeln, soll die Software und die Werkzeuge auch in der Lage sein, mitzuwachsen und eine Verbindung zu anderen Technologien ermöglichen.


To achieve these and other practical goals and to live up to the principles upon which we believe the success of our platform will be built, we insist that the software platform for the One Laptop Per Child project:

  • Must include source code and allow modification so that our developers, the governments that are our customers and the children who use the laptop can look under the hood to change the software to fit an inconceivable and inconceivably diverse set of needs. Our software must also provide a self-hosting development platform.
  • Must allow distribution of modified copies of software under the same license so that the freedoms that our developers depend upon for success remain available to the users and developers who define the next generation of the software. Our users and customers must be able to localize software into their language, fix the software to remove bugs, and repurpose the software to fit their needs.
  • Must allow redistribution without permission -- either alone or as part of an aggregate distribution -- because we can not know and should not control how the tools we create will be re-purposed in the future. Our children outgrow our platform, our software should be able to grow with them.
  • Must not require royalty payments or any other fee for redistribution or modification for obvious reasons of economy and pragmatism in the context of our project.