dc10 - 0.5
DebConf10
Speakers | |
---|---|
Bradley M. Kuhn |
Schedule | |
---|---|
Day | DebConf Day 2 (2010-08-02) |
Room | Davis Auditorium |
Start time | 10:30 |
Duration | 01:00 |
Info | |
ID | 617 |
Event type | lecture |
Track | |
Language | en |
Feedback | |
---|---|
Did you attend this event? Give Feedback |
GPLv3: Better Copyleft for Developers and Users
Many developers have not yet investigated the new suite of GPLv3
licenses. This presentation helps developers already familiar with
GPLv2 and LGPLv2 to improve their understanding of GPLv3, LGPLv3, and
AGPLv3. This presentation covers changes in the patent provisions,
improved license compatibility, improved source code provision terms,
the internationalization of GPL and many other changes.
Many developers have not had the time to investigate the new suite of
licenses in depth, and understand the differences between the
GPLv3-based and the GPLv2-based licenses. This talk will help
developers who are generally familiar with the GPLv2 and LGPLv2 to
improve their understanding of GPLv3, LGPLv3, and AGPLv3.
Specifically, this talk will cover in detail the changes in the in
various parts of the license. The following is the list of changes
that will be explained in detail during the talk:
* Changes to improve the details regarding distribution between
GPLv2 and GPLv3. Traditionally, GPLv2 has been interpreted to
mean what GPLv3 says on this topic, but does not say so in the
letter of the license. v3 makes it clear how distribution can
happen under a copyleft license.
* GPLv2, while aware of the software patent issue, is extremely
naive in its provisions regarding patents. GPLv3 patent
provisions are much improve. This talk will explain how.
* GPLv2 is a USA-centric license. GPLv3 is internationalized.
* The termination provision in v2 extremely aggressive. GPLv3
has friendlier termination provisions more consistent with
community practices.
* License exceptions are nearly always necessary under GPL.
They existed under GPLv2, but the system for adding exceptions
was clunky and non-uniform. GPLv3 provides an exceptions
framework.
* GPLv2 does not handle embedded software situations well.
GPLv3 much improves this situation.
* GPLv2 has no web services clause. GPLv3 does not either, but
GPLv3's structure makes one possible through the Affero GPLv3.