15 messages in net.sourceforge.lists.courier-usersRe: [courier-users] DomainKeys on Cou...
FromSent OnAttachments
Vini EngelDec 12, 2006 3:17 pm 
Sam VarshavchikDec 12, 2006 4:53 pm 
Sergiy ZhukDec 12, 2006 5:18 pm 
JeffDec 19, 2006 9:30 am 
Sam VarshavchikDec 19, 2006 3:33 pm 
Alessandro VeselyDec 20, 2006 1:41 am 
Sam VarshavchikDec 20, 2006 3:58 am 
Bernd WurstDec 20, 2006 10:01 pm 
Malcolm WeirDec 20, 2006 10:32 pm 
Alessandro VeselyDec 21, 2006 1:36 am 
Harry DuncanJan 14, 2007 4:46 am 
Julian MehnleJan 14, 2007 6:10 am 
Sam VarshavchikJan 14, 2007 6:29 am 
Sergiy ZhukJan 14, 2007 4:55 pm 
Vini EngelJan 16, 2007 6:29 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] DomainKeys on Courier?Actions...
From:Malcolm Weir (ma@gelt.org)
Date:Dec 20, 2006 10:32:21 pm
List:net.sourceforge.lists.courier-users

-----Original Message----- From: Bernd Wurst Sent: Wednesday, December 20, 2006 10:02 PM

Am Mittwoch, 20. Dezember 2006 10:42 schrieb Alessandro Vesely:

However, I'm concerned about that "and no other version".

I'm concerned about the frequent use of "or any later version" in many free software projects. Some free software enthusiasts are still not very happy with the contents of GPLv3, so why should someone place his code under a license he does not know yet?

And while one's thinking about that, ponder the fact that a court in some jurisdiction somewhere in the world could decide to rule on some aspect of a license that developers thought they understood, and we'd end up with an _effective_ license that is different from the currently understood one (at least in that jurisdiction).

GPLv3 should come in a few months and Courier's Copyright holder may want to use it. Then, there will still be an incompatibility: would the DomainKeys Identified Mail (DKIM) addition have to be reverted in that case?

Don't spend too much brain about that version-stuff. After all changes that have been made, I still hope that GPLv3 will be somewhat compatible with GPLv2, so you can use GPLv2 code in GPLv3 projects. Everything else would break GPLv3's neck.

While we're at it, Sam is of course perfectly free to use any license he chooses, but changing a license mid-stream carries implications that are quite different in nature from changing the version of a library. Which is to say that if one is content with GPLv2, why on earth would one change?

Particularly since, in the short term, it may be wise to see if a new version like GPLv3 gets challenged or interpreted in some unanticipated fashion...

cu, Bernd

Malc.