Gpl3
Differences between revisions 2 and 3
|
Size: 2655
Comment:
|
Size: 830
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. == Release Note == This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.) It is mandatory. == Rationale == This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. == Use Cases == == Assumptions == == Design == You can have subsections that better describe specific parts of the issue. == Implementation == This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: === UI Changes === Should cover changes required to the UI, or specific UI that is required to implement this === Code Changes === Code changes should include an overview of what needs to change, and in some cases even the specific details. === Migration === Include: * data migration, if any * redirects from old URLs to new ones, if any * how users will be pointed to the new way of doing things, if necessary. == Test/Demo Plan == It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release. This need not be added or completed until the specification is nearing beta. == Outstanding Issues == This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved. |
Packages to look for which may create licencing problems when changing to GPL 3 |
| Line 61: | Line 14: |
| What will change to GPL 3 licencing? What will this affect? | Core packages such as glibc won't change to GPL 3 only. |
| Line 63: | Line 16: |
| KDE is GPL 2 only because of Qt. | Samba's libsmbclient will be GPL 3 from version 3.2. A second, 3.0 version will be needed for KDE. |
| Line 65: | Line 18: |
| Samba is a big issue for changing to GPL 3. | libgpgme used by kdepim seems to be remaining GPL 2. |
| Line 67: | Line 20: |
| libgpgme? | libgsl lots of rdepends, all need to be checked. |
| Line 69: | Line 22: |
| Are there Gnome apps which are GPL 2 only? Do they link to Samba or other (L)GPL 3 apps? | libgmp lots of rdepends, all need to be checked. libcdio6 various rdepends, all need to be checked |
Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.
Launchpad Entry: gpl-3
Packages affected:
Summary
Packages to look for which may create licencing problems when changing to GPL 3
BoF agenda and discussion
Core packages such as glibc won't change to GPL 3 only.
Samba's libsmbclient will be GPL 3 from version 3.2. A second, 3.0 version will be needed for KDE.
libgpgme used by kdepim seems to be remaining GPL 2.
libgsl lots of rdepends, all need to be checked.
libgmp lots of rdepends, all need to be checked.
libcdio6 various rdepends, all need to be checked
Gpl3 (last edited 2008-08-06 16:28:45 by localhost)