[PATCH] Move the various map* functions to C; add #'map-into.
Stephen J. Turnbull
stephen at xemacs.org
Mon Feb 1 07:22:10 EST 2010
Ben Wing writes:
> On Mon, Feb 1, 2010 at 2:52 AM, Aidan Kehoe <kehoea at parhasard.net> wrote:
> > Ar an t-aonú lá is triochad de mí Eanair, scríobh Ben Wing:
> > > What exactly is the problem? Does it matter who the owner is provided
> > > we know what the license is?
No, it doesn't matter. Of course, if you don't know the author(s),
you have to wonder if you really know the license.
-------------- next part --------------
> > The files don?t have any licence information at all in them, and elsewhere
> > in XEmacs we?re in the process of deleting such files, or finding their
> > authors and asking them to confirm they?re okay with them being released as
> > GPLv3 or later.
That's a different case. The code in XEmacs we worry about was
contributed to XEmacs; we're where the buck stops if there is a
problem. In the case of code released publicly by a well-known
project, we can pass the buck to them.
I would bet on that, personally. But since you did the adaptation,
Aidan, your opinion rules.
> Surely we know they're LGPL? Doesn't it say somewhere that all files
> are LGPL? I don't think there's any requirement that says that the
> file header itself has to include its copyright info.
No, there's no requirement. But as usual with legal stuff, the courts
like it better if everything is nice and tidy. Every lawyer I've
heard mention the subject recommends having a brief permission notice
in every file, even if the license itself is a separate document.
Also, in the case of XEmacs, *most* of the files have the standard
permissions notice. That notice says "you may distribute XEmacs" etc
etc, so there's about 1100-fold redundancy there; every notice covers
all of XEmacs.
However, if somebody were to complain about one of the files without
the notice, a court might very well consider that evidence that we
were careless and go a little harder on us. I don't think it's a big
worry either way. But it's something we should do, and an opportunity
to clean up some cruft.
More information about the XEmacs-Patches