From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?UTF-8?Q?Cl=c3=a9ment_Pit-Claudel?= Newsgroups: gmane.emacs.devel Subject: Re: Why are so many great packages not trying to get included in GNU Emacs? Date: Wed, 13 May 2020 00:22:56 -0400 Message-ID: References: <9mmFgzvrBwjt_n_VJyaJdXINraNi5HsGpwq-0MLeKiJA7kG2BQA4uywrzjyz7lpRS0OZDpjEi8lspOKYUA7P_QsODsDew_8nbH960G55fmY=@protonmail.com> <87d07xamrg.fsf@ericabrahamsen.net> <878silajdl.fsf@ericabrahamsen.net> <87tv18pyh4.fsf@russet.org.uk> <83blmu9u57.fsf@gnu.org> <7c61a272-f4ba-fdfd-755b-1a720e8cc2df@gmail.com> <838shy9srs.fsf@gnu.org> <7f820b59-ebbc-18c7-9f08-104a7ba88dd2@gmail.com> <834kslao2y.fsf@gnu.org> <052569f9-0571-6471-7a27-f3d7b36497a0@gmail.com> <83sgg58ari.fsf@gnu.org> <837dxh847w.fsf@gnu.org> <834ksl833q.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="56814"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 Cc: casouri@gmail.com, eric@ericabrahamsen.net, emacs-devel@gnu.org, monnier@iro.umontreal.ca, eliz@gnu.org, phillip.lord@russet.org.uk, ndame@protonmail.com To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 13 06:23:49 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 1jYivs-000Ef7-Fw for ged-emacs-devel@m.gmane-mx.org; Wed, 13 May 2020 06:23:48 +0200 Original-Received: from localhost ([::1]:55488 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYivr-0002RQ-IW for ged-emacs-devel@m.gmane-mx.org; Wed, 13 May 2020 00:23:47 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35026) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYivB-00020J-Bp for emacs-devel@gnu.org; Wed, 13 May 2020 00:23:05 -0400 Original-Received: from mail-qk1-x733.google.com ([2607:f8b0:4864:20::733]:40996) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jYiv9-0005gX-OS; Wed, 13 May 2020 00:23:04 -0400 Original-Received: by mail-qk1-x733.google.com with SMTP id n14so16094236qke.8; Tue, 12 May 2020 21:22:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Xtd/4HbSKxPGdCy6W9QZlyx+1do1MfE80Zsp0oAPkM4=; b=lj/oFW/NgDJBHNjdnh5SzYtCj66JEGkjKTKQS4v84TyyGRApvNt//HWA9DbbAVWvDy BuWQHMaZNrlwg2wMA9GyXTbsoCzPPKnokG9UfTbOngrXR/OKwDzGI9U7UUT04hsnNkad B4hfiAi7CPhGsZFhkQiijuSrH5fdlNwWJIS9QG2v2Mkd+makd2sfOxKuc0MDXq/bepXO z86d6HWQNDlDxLmz+OKnaTkEWHQX6jeo7oRxnuC2Qso2HLfC7d9yCPiNhspnfoiLFAS6 ii9WnqVBCGBU187k8E18QGfL4R47LxFGyePC7Nwl9VgLiYw9C1LZbIMCLvVsc2cOhXCj 9fIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Xtd/4HbSKxPGdCy6W9QZlyx+1do1MfE80Zsp0oAPkM4=; b=KskcAKGNQoduSYbfEvO5LO2GJhFzdjamZHU0NEQp0549Sadx542uqvvxoIi50ovGbq g+4d2xAh4yFDCwFzHgQZOJRGE6vHHLyCoq9rYznfjXIvpZKqcES+yHAigRp3zEQeZDWq X6E5m6hnDsGyWG+zoIlWW5QqZJmBNLj0ONOj9NL3qtpZee7u0fSNtALZXoc4EsjfpAqo wike6Y4tm8VDhILMlK6QHdYzJ4+fC3l1W4MAoTgiw/MdxRyYtVmgDqXdmy1+g+PYgf7N hZqzgqMnjjBTh1fg3HuEXkEWAg/nPQ+9946TpY4XRmD0dJUdE2zK90mWffLqylyawkv7 xPDQ== X-Gm-Message-State: AGi0PuYvKsErCygyK4xF8/XYyG6VU5fPlEZW0YAuZ3TxYPLUFxvdhG+N nL2HEl6xtx6yGLYAO9K/DL4= X-Google-Smtp-Source: APiQypKPap6u+l5t+KuEyXp2NZFaRNKHCCcjg1c4UGo4zIM10s3U6+WjcLeF8U5FMSdGLJoB2RtIqQ== X-Received: by 2002:a37:b95:: with SMTP id 143mr23636736qkl.409.1589343778100; Tue, 12 May 2020 21:22:58 -0700 (PDT) Original-Received: from ?IPv6:2601:184:4180:66e7:4d17:b25e:8d9:2188? ([2601:184:4180:66e7:4d17:b25e:8d9:2188]) by smtp.googlemail.com with ESMTPSA id q17sm12979623qkq.111.2020.05.12.21.22.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 May 2020 21:22:57 -0700 (PDT) In-Reply-To: Content-Language: en-GB Received-SPF: pass client-ip=2607:f8b0:4864:20::733; envelope-from=cpitclaudel@gmail.com; helo=mail-qk1-x733.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001 autolearn=_AUTOLEARN X-Spam_action: no action 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:250094 Archived-At: On 13/05/2020 00.07, Richard Stallman wrote: > > Currently, the way you answer such a question is that you look at > > the commit, try to determine the author, and check a list of > > people who have assigned copyright to see if the author is in it. > > > This process is cumbersome, because few have access to the list. > > One way to make it smoother is to add an API that gives access to > > that list. > > I would like to make that easier. Thanks a lot. It would be great. > That may be complex. We don't > publish the list, for privacy reasons. We don't want to offer > the public a way to probe the list. Maybe we can publicize a part of the list which would not violate privacy? When I signed my copyright papers, I answered yes to a question that said "Would it be acceptable for us to publicize your contribution by microblogging that you are contributing, and listing your name in our monthly newsletter?". I think it is safe to assume that those who answered yes to this question do not object to appearing on a public list; correct? > > Indeed, currently, when you assign copyright to the FSF, you sign > > a document with a GPG key. The FSF could sign that key to > > indicate "we have received copyright papers for this author". > > > Then, to verify "do we have papers for the author of this commit", > > anyone could check "is this commit signed with a key signed by the > > FSF"? > > At first glance, this looks good to me. It would be necessary > for people to study it to make sure it doens't have problems. Note that with this scheme, it would be possible to reconstruct parts of the list, by looking for keys signed by the FSF. So, if knowing a list of address emails that have signed FSF copyright papers is an issue, then this scheme won't solve it.