Change licence to GPL + OpenSSL exception
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GTimeLog |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
The fine people at Collabora would like to enhance GTimeLog with web-based applications that use SSL.
Pierre-Luc Beaudoin wrote:
> Python uses OpenSSL for the encryption part. Unfortunately, OpenSSL's
> license is incompatible with GNU GPL.
> http://
>
> Fortunately there is a solution, which is used by some other GPL
> applications. Relicense GTimelog as "GNU GPL with the OpenSSL special
> exemption." wget and climm are notable user of that license. That
> exception means that we'd have to advertise that SSL functionality is
> provided by OpenSSL.
>
> Do you think GTimelog contributors would agree to such a change?
I myself am fine with this. The other code contributors at this time are:
* people who sent me patches by email (and I can find their emails in my mail archives, if Google fails)
Thom May
Dafydd Harries
Ignas Mikalajūnas (my ex-coworker, I can get hold of him easily)
Gaute Amundsen
Chris Beaven
* people who attached patches to Launchpad bugs (and you can probably find out how to contact them by searching for bugs with the 'patch' tag)
Harald Friessnegger
Rodrigo Daunoravicius
Somebody ought to get their permission for the licence change.
Changed in gtimelog: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Going through bzr log now and looking if I left any people out from that list:
* Gintautas Miliauskas sent me a patch to fix log view column alignment (revision 67)
-- another ex-coworker, I can get hold of him
* Olivier Crête sent me a fix for a bug that prevented monthly reports from being generated in November; I didn't like his patch so rewrote it (revision 86)
* Adomas Paltanavičius sent me a patch to fix text alignment in reports when multibyte UTF-8 characters are present (revision 70).
-- I have him in my IM contacts list
I'm quite certain I never applied people's patches without mentioning them in the commit message, so the bzr log is definitive.
The list of contributors in README.txt is, sadly, not so diligently updated.