From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Filipe Silva Newsgroups: gmane.emacs.devel Subject: Re: Please explain the FSF copyright assignment thing Date: Thu, 13 Jul 2017 15:32:56 -0300 Message-ID: References: <87shi08bx5.fsf@wanadoo.es> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a113bd0545a0f030554372960" X-Trace: blaine.gmane.org 1499970821 15214 195.159.176.226 (13 Jul 2017 18:33:41 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 13 Jul 2017 18:33:41 +0000 (UTC) Cc: =?UTF-8?Q?=C3=93scar_Fuentes?= , Emacs developers To: John Yates Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 13 20:33:37 2017 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 1dVivg-0003hj-91 for ged-emacs-devel@m.gmane.org; Thu, 13 Jul 2017 20:33:36 +0200 Original-Received: from localhost ([::1]:33479 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dVivl-0007lH-Qg for ged-emacs-devel@m.gmane.org; Thu, 13 Jul 2017 14:33:41 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50281) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dViv5-0007l1-1p for emacs-devel@gnu.org; Thu, 13 Jul 2017 14:32:59 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dViv4-0001go-5b for emacs-devel@gnu.org; Thu, 13 Jul 2017 14:32:59 -0400 Original-Received: from mail-oi0-x22c.google.com ([2607:f8b0:4003:c06::22c]:33742) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dViv4-0001gQ-0t for emacs-devel@gnu.org; Thu, 13 Jul 2017 14:32:58 -0400 Original-Received: by mail-oi0-x22c.google.com with SMTP id p188so53392467oia.0 for ; Thu, 13 Jul 2017 11:32:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fLGjJTvasOuUxlpF4Gext8RBg6fn8s3OL58FkNP1+PU=; b=MGGxT5+DU1vS8yhGn0IwQwEaG7A4lAfD8zYAw7/k4KAq9ZKrnZcl7dGePTAToz9F6u g456E1kAiV8QdktHAWRSQgXYHC1sM7ZqLi+FeB4DMUwFsvzHe82PtdvIkNQxVrPG95/i 3X0myuFxiDcasoHt8UrJnWEAtKeC2OULT3M2Xa3Zl6H3/iKSG7VHzeV/AUistwlR6+tL ubog21A2/y16zHApuPF9GAXLdpjM0ohBgluW9AFl+H0hRhnJ8EgE/mMa36QREpz5Ma1e peHMZP2f/Jr1Re7uZ8RuQhmKfvKH3ZaTPY23SZUTyno38QQD+zStLUyA79nXl0Y9CFDD fC/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fLGjJTvasOuUxlpF4Gext8RBg6fn8s3OL58FkNP1+PU=; b=Scr24kOAOBJ4EQ8U7yjB/y5jX/6ExZQ6Bou3LrxdCvMboIM97SYY5PT5GrXwNDAsHK RIlf5uyaupIAJMO/QOGkfKEwY1mtJ6lXIQOF2zlbAjGeta24Phz0GE7QjvAsB9LPWxvq X+e4hdrarqRAYu3+FuciPbXthrFHiOcCqARrH0ScbxYO0Wzcg0lvEesqUy6hMCVMvdOB njY7gSf32z17uIDVuEz5nVdtDdaK3+Ghl2mor4IWcuuSla/G+jS4O8oCK/Sh3FvHyp2h LZXbbgy4y37Kvu09xeeQv0ZUzbY/NXvUqZnamMDqwOjeQSEXkYSwTTUZUuRGznyoM5uq 1flg== X-Gm-Message-State: AIVw113qRtCYM4M2Mmx6/zMHrc+x8tS2LJY3rWhhWyLREN4twR1UU8XT mPSPvGfi8yoTYGK4ILvCMmbvWWC8AQ== X-Received: by 10.202.66.4 with SMTP id p4mr3695430oia.114.1499970777253; Thu, 13 Jul 2017 11:32:57 -0700 (PDT) Original-Received: by 10.182.85.69 with HTTP; Thu, 13 Jul 2017 11:32:56 -0700 (PDT) Original-Received: by 10.182.85.69 with HTTP; Thu, 13 Jul 2017 11:32:56 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4003:c06::22c 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:216595 Archived-At: --001a113bd0545a0f030554372960 Content-Type: text/plain; charset="UTF-8" I can guess: Because git is very important and magit solves that beautifully for emacs? Now the other question still stands: what could a berserk past author do legally to exert prejudice against the FSF or emacs users, given that the software he wrote is licensed under GPLv3? Why can't FSF distribute his software under the same license? On Jul 13, 2017 15:26, "John Yates" wrote: > Perhaps you should ask why Richard decided that Magit, among all > of the many non-FSF copyright assigned packages that emacs users > recommend to one another, was so intolerable as to justify suggesting > mounting a - to my mind doomed - competing project. It was not as if > all of those recommendations are for some proprietary or non-GPL-V3+ > package. > > Happily the community has rallied to Jonas' cause and will now try to > bring Magit into the FSF fold. > > /john > > --001a113bd0545a0f030554372960 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=C2=A0I can guess: Because git is very important and magi= t solves that beautifully for emacs?

Now the other question still stands: what could a berserk past autho= r do legally to exert prejudice against the FSF or emacs users, given that = the software he wrote is licensed under GPLv3? Why can't FSF distribute= his software under the same license?



On Jul 13, 2017 15:26, "John Yates" <john@yates-sheets.org> wrote:
Perhaps you should ask why Richard decided that Magit, a= mong all
of the many non-FSF copyright as= signed packages that emacs users
recommen= d to one another, was so intolerable as to justify suggesting
mounting a - to my mind doomed - competing project.=C2= =A0 It was not as if
all of those recomme= ndations are for some proprietary or non-GPL-V3+
package.

Happily the community has rallied to Jonas' cause and wi= ll now try to
bring Magit into the FSF fo= ld.

/john

--001a113bd0545a0f030554372960--