#4196: Method for obtaining developer keys needed.
-----------------------+----------------------------------------------------
Reporter: cjb | Owner: cscott
Type: defect | Status: new
Priority: blocker | Milestone: First Deployment, V1.0
Component: security | Version:
Resolution: | Keywords:
Verified: 0 |
-----------------------+----------------------------------------------------
Changes (by gnu):
* cc: gnu (added)
Comment:
"(Anything we do w/o a developer key is GPL-compatible, as long as the
developer key-ed software is completely permissive.)"
That's certainly not true; for example, you can't ship binaries without
source or a written offer of source. You can't link GPL binaries to
proprietary binaries. Etc...
I think OLPC should strive to follow the GPL in all ways and at all times
-- not just after a developer key arrives. There may be small exceptions
where the FSF is willing to cut you some slack -- but they should be small
and they should be exceptional. Users of ordinary commercial GNU/Linux
laptops have expectations set by long experience with the GPL. OLPC
GNU/Linux laptops should come with essentially the same rights and
privileges. OLPC is trying to make a *better* laptop, *more free* than
the average laptop -- not less free.
--
Ticket URL: <https://dev.laptop.org/ticket/4196#comment:4>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system