This page is an area where Debian developers and users can leave comments so that ?BrandenRobinson, DonArmstrong and BenjaminMakoHill can better represent the desires and hopes of the Project when they attend the GPL v3 Launch conference at MIT in Boston, Massachusetts on 16 and 17 January 2006.
Branden suggests drafting comments to answer questions along the following lines:
- What are the current GPL's strengths?
- What are the current GPL's deficiencies?
- Are there significant threats to software freedom that the current GPL does not address?
- Should a new GPL attempt to explicitly broaden its applicability to works other than computer programs (e.g., image, sound, or music files; documentation; dictionaries; encyclopedias)?
- What parts of the GPL are difficult to understand?
- If you have copyright in a GPL-licensed work, what area(s) of the GPL do you find difficult to adjudicate?
- What part of the current GPL would you most like to see preserved as-is?
- What part of the current GPL would you most like to see changed?
- Is the time ripe for revising the GPL?
- On balance, has the GPL been a benefit or a detriment to the Debian Project?
Do not feel compelled to comment on areas that don't interest you.
Please do not edit other users' comments except as they request (e.g., for spelling corrections and improved grammar).
Branden recommends placing comments between two horizontal rules. Please sign your contributions; anonymous comments are not possible on this Wiki, as it is only editable by registered users. If you would like to comment but want your identity to be held in confidence, please send private mail to firstname.lastname@example.org with the subject GPLv3 launch comment. Feel free to GPG-sign and/or -encrypt such mails.
Branden is monolingual in English, so comments left in other languages will have to be translated for him to understand them.
This is an example comment.
At various points, people have wanted to base distributions on top of GPL-incompatible but still free (or arguably free) system components. GPLv2 makes this difficult, but it's not obvious that preventing this provides any benefits to the recipients of software. It would be advantageous to suggest that this situation be examined in GPLv3.