unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: luangruo@yahoo.com, masm+github@masm11.me, emacs-devel@gnu.org
Subject: Re: gsettings.m4 copyright
Date: Tue, 04 Jan 2022 05:31:44 +0200	[thread overview]
Message-ID: <83pmp8b2hr.fsf@gnu.org> (raw)
In-Reply-To: <E1n4XBP-0008KO-O0@fencepost.gnu.org> (message from Richard Stallman on Mon, 03 Jan 2022 18:56:07 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: luangruo@yahoo.com, fejfighter@gmail.com, masm+github@masm11.me,
> 	emacs-devel@gnu.org
> Date: Mon, 03 Jan 2022 18:56:07 -0500
> 
>   > > That file is full of non-trivial code from the GLib project.
> 
>   > You are saying that we cannot include it in Emacs, because whoever
>   > wrote the code didn't contribute it to us?  That's not a copyright
>   > question, that's a completely different (and more serious) issue.
> 
> GNU Project policy is that it's ok to import code from other released
> free packages whose licenses are compatible with the license we are
> using (which is GPL3-or-later).  The license LGPL-2.1 is compatible,
> so we can import this code.
> 
> We should make sure it carries the copyright notices and license
> notices that it should have.  The fact it was missing those is a
> small problem, but we can fix that.
> 
> If the whole Glib package carries a copyright notices, copy that one.
> 
> If it isn't clear what to do, how about asking its developers what
> that should be?

I prefer to implement that differently, since what the file does is
not clean enough for my taste.  If that is possible, it would also
solve this issue.  If it turns out to be harder than I thought, we
will reconsider.



  reply	other threads:[~2022-01-04  3:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r19pgl3x.fsf.ref@yahoo.com>
2022-01-03 10:38 ` gsettings.m4 copyright Po Lu
2022-01-03 12:53   ` Eli Zaretskii
2022-01-03 12:56     ` Po Lu
2022-01-03 13:02       ` Eli Zaretskii
2022-01-03 13:28         ` Po Lu
2022-01-03 13:39         ` Yuuki Harano
2022-01-03 14:29           ` Eli Zaretskii
2022-01-03 15:11             ` Eli Zaretskii
2022-01-03 15:59               ` Yuuki Harano
2022-01-04  8:35                 ` Yuuki Harano
2022-01-04 13:29                   ` Eli Zaretskii
2022-01-03 16:03             ` Stefan Monnier
2022-01-03 17:26               ` Eli Zaretskii
2022-01-03 23:56         ` Richard Stallman
2022-01-04  3:31           ` Eli Zaretskii [this message]
2022-01-04  3:48           ` Stefan Kangas
2022-01-05  3:53             ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pmp8b2hr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=masm+github@masm11.me \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).