unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: rms@gnu.org
Cc: luangruo@yahoo.com, emacs-tangents@gnu.org, eliz@gnu.org,
	akira@akirakyle.com, larsi@gnus.org
Subject: Re: On Contributing To Emacs
Date: Fri, 31 Dec 2021 00:18:50 -0500	[thread overview]
Message-ID: <CADwFkm=YsbKEMya2bDsgmx72hPmCz0cY_UNOxThnHqYGEUJU6g@mail.gmail.com> (raw)
In-Reply-To: <E1n39UD-00052T-7A@fencepost.gnu.org>

[Moving this to emacs-tangents.]

Richard Stallman <rms@gnu.org> writes:

> The Glibc and GCC developers made a bad decision last June.  The DCO
> they are using is full of gaps, and they don't get it from all the
> authors.  A copyright assignment is much better.

What is your view on the GNU software that does not have a copyright
assignment, and not even a DCO?

IMO, it would be more important for Glibc and GCC to maintain the
copyright assignment than it is for Emacs.  AFAIU, GPL violations with
GCC are very common, and they are also common with Glibc.  However, they
are exceedingly rare with Emacs.

I think this is no accident, but a result of the fact that it is more
attractive to try to steal code from systems libraries and a compiler
than from a text editor.

The risk in our case is therefore lower than it is for these projects.

> I ask lawyers how to keep the the copyleft strong, because that is
> a priority for the free software movement.  I don't ask them whether
> that should be our priority, because that's the starting point.

My starting point is the need to eradicate proprietary software.  To
achieve that goal, copyleft is one tool, and successful software is
another.  The reason that I think we should accept the risk here is that
it is a) very small, and b) it will bring other huge advantages.  The
benefits would by far outweigh the drawbacks.

In particular, it would allow us to include and re-use code from Lisp
libraries that have been developed without copyright assignment.  It
would also significantly lower the barrier for entry, and together with
other changes I think it has the potential to significantly help in
recruiting new contributors.

I do not find the blanket "our lawyers told us so" argument
satisfactory.  It would be better to discuss the pros and cons of the
various approaches.



       reply	other threads:[~2021-12-31  5:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Ms-vAhM--3-2@tutanota.de>
     [not found] ` <E1n2Qvx-00086Q-Vj@fencepost.gnu.org>
     [not found]   ` <87k0fn8od1.fsf@gnus.org>
     [not found]     ` <CAPWcbYExSATMox9pCN13iZGUcQg=UroSkx9RHvWsrDNQAeZMvg@mail.gmail.com>
     [not found]       ` <83y242ip0a.fsf@gnu.org>
     [not found]         ` <CADwFkmkqGvq1OV8gjy2sDMBaSt_761FZ0NFx5VS+36YbD=Ex-A@mail.gmail.com>
     [not found]           ` <87ilv6nzk5.fsf@yahoo.com>
     [not found]             ` <CADwFkm=6k9c6Rmt053aSFtL4MmM0MhH6i7OMSYo-uj4kGm1rwA@mail.gmail.com>
     [not found]               ` <E1n39UD-00052T-7A@fencepost.gnu.org>
2021-12-31  5:18                 ` Stefan Kangas [this message]
2022-01-02  6:59                   ` On Contributing To Emacs 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='CADwFkm=YsbKEMya2bDsgmx72hPmCz0cY_UNOxThnHqYGEUJU6g@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=akira@akirakyle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-tangents@gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.com \
    --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.
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).