From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Daniel Pittman Newsgroups: gmane.emacs.devel Subject: Re: Licensing for source code contained in Emacs manuals Date: Mon, 12 Nov 2018 16:35:58 -0500 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000c21bc1057a7e7ef4" X-Trace: blaine.gmane.org 1542058545 1924 195.159.176.226 (12 Nov 2018 21:35:45 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 12 Nov 2018 21:35:45 +0000 (UTC) Cc: licensing@fsf.org, emacs-devel@gnu.org To: eggert@cs.ucla.edu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 12 22:35:40 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gMJrw-0000R2-BA for ged-emacs-devel@m.gmane.org; Mon, 12 Nov 2018 22:35:40 +0100 Original-Received: from localhost ([::1]:50754 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gMJu2-0001HI-Rn for ged-emacs-devel@m.gmane.org; Mon, 12 Nov 2018 16:37:50 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50834) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gMJt1-0001H1-Q9 for emacs-devel@gnu.org; Mon, 12 Nov 2018 16:36:48 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gMJt0-0007Wi-9b for emacs-devel@gnu.org; Mon, 12 Nov 2018 16:36:47 -0500 Original-Received: from mail-oi1-x233.google.com ([2607:f8b0:4864:20::233]:32967) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gMJsz-0007TX-Rr for emacs-devel@gnu.org; Mon, 12 Nov 2018 16:36:45 -0500 Original-Received: by mail-oi1-x233.google.com with SMTP id c206so2926274oib.0 for ; Mon, 12 Nov 2018 13:36:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xJPb7Nk+b31WDimGAJdCN5QeKCWERvy7RnBmOfX1C/E=; b=vvYVjh8HuVUMGKLHSRb1wysyb8DtwjQsZTpe5HMhdWcc8G4vtIdRSwhJuM755r8qAV UF0+2icjtI2Nw+VgFugfs9LCTU6OgN+l0/PBXLodZzzFQJQC5OVeBI298hs+ByNtdQDq wDDV6JJqiM4UE9edhNOnj+/jNRc7YFA9gFQvNFUd/DkhcLdP29opsIH55bmfnhv2CBOv sV+PqkxG8F7WVo0iFMbKDsd3VUZ9A3awf5RDF6EDnb2vwtRGlZ9M4nE7qbgFJ+6xd8Bq Czthh+rtGoWE2+tsd8hlQmxBFWT3E7FVIUncyv/65efmiMk/tpUqGb5wZQlz63vdfFNF taXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xJPb7Nk+b31WDimGAJdCN5QeKCWERvy7RnBmOfX1C/E=; b=W8YsN2+wywylTAlPJ7X1Cl4APsFEKhm+ybBroeaa67/rR1PfaR7KyT7t9iBByhGTVD qX71OZOphuZRTZUu+0WLHt0lcsyefeeLLUMP9fWAInLXuWnJd2vXeU3BaR5Etp4x7Pbl uL7AgnN+NvPREB4PiANiY9YqtsECAIHOjWe6ygQQX+GxnBLcBcj6KNW/G9CaKUVq3oU8 eYE78EnjYdg0Pf9+YtRxzwyu/++AByiTo5sxgS0K8KwIemQgCTO3zg2LXmU0NEgu9gJB 3i9D75TeaZuXE3E85pglgh8dsbv3l8DkLqkUfpEuHDeddhgCvgoWKxiBWInszAyaiade Q06A== X-Gm-Message-State: AGRZ1gIdQEgK46Bnm3k49gMjoZdRxufep4xvSzijZrv4GJMVpsn7xFgo q1J7WZjn0HHChawZUJRjiS1VtD41RmZDlSX2yR59zA== X-Google-Smtp-Source: AJdET5e0LFQa0+y2kVdADd7naXZg26frRh4Mxn884fYYOXwzJczT8aqh/5n9iswkIHaNvXhMwHspP+Jg6mAFPaKEH0s= X-Received: by 2002:aca:abc6:: with SMTP id u189-v6mr1440435oie.316.1542058594643; Mon, 12 Nov 2018 13:36:34 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::233 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:231105 Archived-At: --000000000000c21bc1057a7e7ef4 Content-Type: text/plain; charset="UTF-8" On Mon, Nov 12, 2018 at 3:01 PM Paul Eggert wrote: > Daniel Pittman wrote: > > Would it be appropriate to extend the documentation to explicitly permit > > reuse of the sample code in the Emacs flymake manual, or all Emacs > manuals, > > under the same license as Emacs itself? That is, sample code could be > used > > under the GFDL*or* the GPLv3 (at this time). > > I'm sure that could be fine. Alternatively, and without needing any > special > rules about this, the distribution could contain a separate copy of the > code in > question in standard source-code form, licensed under the GPL. The > documentation > could explain that the code itself is also available outside the > documentation > and that it is GPLed there. As a user, I'd prefer that to cutting and > pasting > out of the documentation. > My plan, then, is to give the FSF licensing folks a chance to speak up, and then submit a patch that will adjust the licensing text used for the various manuals appropriately. I think that, while additional files absolutely make sense, ensuring accurate documentation when future manual authors forget that extra step will be beneficial to all. :) --000000000000c21bc1057a7e7ef4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Nov 12= , 2018 at 3:01 PM Paul Eggert <egg= ert@cs.ucla.edu> wrote:
Dani= el Pittman wrote:
> Would it be appropriate to extend the documentation to explicitly perm= it
> reuse of the sample code in the Emacs flymake manual, or all Emacs man= uals,
> under the same license as Emacs itself?=C2=A0 That is, sample code cou= ld be used
> under the GFDL*or*=C2=A0 the GPLv3 (at this time).

I'm sure that could be fine. Alternatively, and without needing any spe= cial
rules about this, the distribution could contain a separate copy of the cod= e in
question in standard source-code form, licensed under the GPL. The document= ation
could explain that the code itself is also available outside the documentat= ion
and that it is GPLed there. As a user, I'd prefer that to cutting and p= asting
out of the documentation.

My plan, then= , is to give the FSF licensing folks a chance to speak up, and then submit = a patch that will adjust the licensing text used for the various manuals ap= propriately.=C2=A0=C2=A0=C2=A0I think that, while additional files absolute= ly make sense, ensuring accurate documentation when future manual authors f= orget that extra step will be beneficial to all. :)
--000000000000c21bc1057a7e7ef4--