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 10:48:26 -0400 Message-ID: <52d0b853-1627-0a54-6785-b5de7c53958b@gmail.com> 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> <83o8qr7wh0.fsf@gnu.org> 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="70487"; 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, rms@gnu.org, eric@ericabrahamsen.net, emacs-devel@gnu.org, monnier@iro.umontreal.ca, ndame@protonmail.com, phillip.lord@russet.org.uk To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 13 16:49:42 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 1jYsha-000IFR-7g for ged-emacs-devel@m.gmane-mx.org; Wed, 13 May 2020 16:49:42 +0200 Original-Received: from localhost ([::1]:35192 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYshZ-0007Ul-9s for ged-emacs-devel@m.gmane-mx.org; Wed, 13 May 2020 10:49:41 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58630) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYsgR-0006a6-Sc for emacs-devel@gnu.org; Wed, 13 May 2020 10:48:31 -0400 Original-Received: from mail-qt1-x835.google.com ([2607:f8b0:4864:20::835]:46437) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jYsgQ-00076y-7M; Wed, 13 May 2020 10:48:31 -0400 Original-Received: by mail-qt1-x835.google.com with SMTP id p12so14311107qtn.13; Wed, 13 May 2020 07:48:29 -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=27n8lyejkEoWYHu+Ni5PH65+sSiGSxzvFwDZ8IOpAdM=; b=m5pRuiUjHyK2+H+ZELgt3htt1BPXicNZC6Uc3h3ETA6TjBSMHwjcz+Qmn/Xhi+mBPf RCk4piY1ryCw7Faa3OfTwuF6ih04X7pR0YKn/2uwUhFpI8Fytg3zrqqaQaGrBwLuSwDA aOdj0DPYwUesFr9RJuPTygVK8T+m2OIyWd9Jsas8OHhIsvENzW8NB1wj4IWHv8GTh92Q mhAJ+P3Zj59H9WznA5HTzPy+wd5SOYHwo4vCr29x2G2oLoE/rzfZg9tT37KQA+xD/oLn x4YQUcmEkV4zFu9yeyPuWV4iHfY0gzA2Br/RY28Jbh6rEVtkvs9j5LbC3Bkqc+n1eXg1 ZJMw== 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=27n8lyejkEoWYHu+Ni5PH65+sSiGSxzvFwDZ8IOpAdM=; b=K7kEwNnB4Px2IaL0wjMXcL01wl4Y1WL4AIkXRKIkOGF23PgoloQ5JbIODw7IFKjVNu c9xiLrbZsMi3m5qPBE69YMpAogPAtquEFjBRfUIDWQwDBeZVJiPBJAlb0rc9nnLk35fB ejk4W7nuNKdIIxlg2zAGrOqpPAV7d0pqDLiWqBmCjjXkrxux3i5JRRJwK/Gfh/V1m7lK Eg2MFHx4G1ldot5/voeNJpKNYzsOR661jtDcji3LEt8/GJNrtqikFwpKIwJVCGHfyaIl I1f5dl4nu4yG1BkTK2+p47HYULCqU5u3fi3ISbO1NdGPwc3x3O0kv+NUSnZMy0k9+5Ai Qklw== X-Gm-Message-State: AGi0PuaODCtYVlYs/p564qUuYJ0YJUBilo/ceboOz6CvHr6D16PH1+4C GW+8dWmbqfBm02kPyJAZB/w= X-Google-Smtp-Source: APiQypJDZLL0QsRAXJx94pjqRxsspC/wvKB47HzTlT6eMNm0x5dPQA2jyTeQQRck4BJTABf+3nqCNQ== X-Received: by 2002:ac8:105:: with SMTP id e5mr15572742qtg.15.1589381308509; Wed, 13 May 2020 07:48:28 -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 x5sm16424338qtx.35.2020.05.13.07.48.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 13 May 2020 07:48:27 -0700 (PDT) In-Reply-To: <83o8qr7wh0.fsf@gnu.org> Content-Language: en-GB Received-SPF: pass client-ip=2607:f8b0:4864:20::835; envelope-from=cpitclaudel@gmail.com; helo=mail-qt1-x835.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, URIBL_BLOCKED=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:250129 Archived-At: On 13/05/2020 10.14, Eli Zaretskii wrote: >> Cc: rms@gnu.org, phillip.lord@russet.org.uk, eric@ericabrahamsen.net, >> casouri@gmail.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca, >> ndame@protonmail.com >> From: Clément Pit-Claudel >> Date: Tue, 12 May 2020 15:48:01 -0400 >> >> Another strategy, which doesn't solve the problem for past commits but could help for future commits, is to embed that information into commits. Something like adding a line in the commit saying "I-have-assigned-copyright: Yes". >> >> Of course, just adding that line doesn't prove anything: we want to make sure that we do have an assignment for that commit. >> So, instead of adding a line, the author could sign the commit with their PGP key, saying "all these changes are mine or from sources owned by FSF" (a bit like a developer certificate of origin). >> >> Now the problem is reduced to "does the author with this PGP key have an assignment on file"? But this question can be answered in a decentralized way (no need for an API): the FSF can just sign keys instead. > > This will only work for some cases: when the committer is also the > author, and when the committer has a PGP key. So some cases will > still need to be handled in some other way, and I suspect that those > cases are the majority. I have the opposite intuition, but not very much evidence. I think it depends a lot on how you end up using git, too (in particular, whether patches are typically rebased or marged). Alan raised the issue of PGP's complexity and availability, and I don't have much to say on that. But on the committer versus author debate, as long as the original patch sent by the contributor is signed, it might not matter whether the final commit is (as long as the committer also does have papers and record that they checked that commit).