Re: GPLv3 or later -- Lispref files refers to text in lispref.text

Andreas> I mean you can savely assume all code written for (X)Emacs Andreas> and sent in is meant to be distributed with it, is meant to Andreas> be with a license up to date. Anything else would bring the Andreas> work of the author simply out of use, which probably is not Andreas> the intent. In the worst case the author can't be contacted so the intent can't be checked. This implies we must assume the worst case which is that the intent was only to distribute the code as covered by the actual copyright. Andreas> Otherwise, should some author arg against publishing under GPLv3, Andreas> its time to remove that code still. Yes. And that is what we must do. We must identify the parts that is problematic and se what can be done about it. I'm trying to go down that path but unfortunately very slow. Hardly noticable I'm afraid. Andreas> Do you imagine an example, how someone might object GPLv3 Andreas> with the consequences seeing removed its code? Yes. Andreas> BTW what about to make an announcement at the XEmacs Andreas> html-site, telling authors about the license-change and Andreas> asking them to contradict if not agreed, assuming consent Andreas> otherwise? It will not stick. Real life can work that way but not in the world of copyrights. I think that some of the code hasn't even got any real author. It has just a copyright that doesn't allow us to relicens it as GPLv3 or later. We will not succeed in finding anyone that could grant us that right. So these files needs to go or be replaced. (I'm not a lawyer...) Yours -- %% Mats _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta