From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Why are so many great packages not trying to get included in GNU Emacs? Date: Mon, 11 May 2020 21:57:40 +0300 Message-ID: <83blmu9u57.fsf@gnu.org> References: <9mmFgzvrBwjt_n_VJyaJdXINraNi5HsGpwq-0MLeKiJA7kG2BQA4uywrzjyz7lpRS0OZDpjEi8lspOKYUA7P_QsODsDew_8nbH960G55fmY=@protonmail.com> <97DA7804-F647-4A1D-B8E0-AFFE7A324C64@gmail.com> <87d07xamrg.fsf@ericabrahamsen.net> <878silajdl.fsf@ericabrahamsen.net> <87tv18pyh4.fsf@russet.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="77750"; mail-complaints-to="usenet@ciao.gmane.io" Cc: casouri@gmail.com, rms@gnu.org, eric@ericabrahamsen.net, emacs-devel@gnu.org, monnier@iro.umontreal.ca, ndame@protonmail.com, phillip.lord@russet.org.uk To: =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 11 20:59:12 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jYDdw-000K6C-K1 for ged-emacs-devel@m.gmane-mx.org; Mon, 11 May 2020 20:59:12 +0200 Original-Received: from localhost ([::1]:34608 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYDdv-0007pO-KX for ged-emacs-devel@m.gmane-mx.org; Mon, 11 May 2020 14:59:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48464) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYDdE-0007CN-1N for emacs-devel@gnu.org; Mon, 11 May 2020 14:58:28 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:44200) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYDdC-000448-9k; Mon, 11 May 2020 14:58:26 -0400 Original-Received: from [176.228.60.248] (port=2776 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jYDcZ-00062m-JK; Mon, 11 May 2020 14:57:48 -0400 In-Reply-To: (message from =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel on Mon, 11 May 2020 14:51:26 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:249864 Archived-At: > From: Clément Pit-Claudel > Date: Mon, 11 May 2020 14:51:26 -0400 > Cc: eric@ericabrahamsen.net, casouri@gmail.com, emacs-devel@gnu.org, > monnier@iro.umontreal.ca, ndame@protonmail.com > > On 06/05/2020 22.43, Richard Stallman wrote: > > It is not terrible lot of work for people to deal with those issues, > > but I wouldn't assume a simple program can. > > These days assignments are signed with PGP keys. Commits can also be signed using PGP keys. Wouldn't that provide an reliable way to pair up contributors who have assigned copyright with their contributions? I think you are missing the main point. The problem is not security, it is correct attribution. The author of the committed changeset (not the person who does the commit, the author) must be the person who actually wrote the code, not someone else. If that someone else is a real benevolent person, it is still a problem, because we will make a false presentation that a different person made the change.