From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Luke Shumaker Newsgroups: gmane.emacs.devel Subject: Re: Why are so many great packages not trying to get included in GNU Emacs? Date: Thu, 07 May 2020 14:17:07 -0400 Message-ID: <87tv0ra9uk.wl-lukeshu@lukeshu.com> Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="126502"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/26 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) Cc: emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu May 07 20:18:18 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 1jWl6A-000Wns-2P for ged-emacs-devel@m.gmane-mx.org; Thu, 07 May 2020 20:18:18 +0200 Original-Received: from localhost ([::1]:58278 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jWl69-00058g-32 for ged-emacs-devel@m.gmane-mx.org; Thu, 07 May 2020 14:18:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39042) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jWl5E-0004IW-1O for emacs-devel@gnu.org; Thu, 07 May 2020 14:17:21 -0400 Original-Received: from mav.lukeshu.com ([104.207.138.63]:40846) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jWl5A-0004vA-NF; Thu, 07 May 2020 14:17:19 -0400 Original-Received: from build64-par (209-6-200-219.s4569.c3-0.smr-cbr2.sbo-smr.ma.cable.rcncustomer.com [209.6.200.219]) by mav.lukeshu.com (Postfix) with ESMTPSA id 9A75280590; Thu, 7 May 2020 14:17:07 -0400 (EDT) In-Reply-To: E1jWWVT-0002MP-7U@fencepost.gnu.org Received-SPF: pass client-ip=104.207.138.63; envelope-from=lukeshu@lukeshu.com; helo=mav.lukeshu.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/07 14:17:07 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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:249193 Archived-At: Hi, sorry to jump in as an outsider. I just wanted to clarify a couple of things about Git. > How could that be possible? How would we know who wrote those > changes? We can't assume it is the person whose account checked them > in. Often that is so, but not always. Git tracks separate "committer" and "author" information (both of which are name/email/timestamp). Unfortunately, it only allows exactly one author; limiting the case where a change has 2 collaborators. > There may be other issues, such as, if the name on that account is > John Doe, does that mean the user of that account is the same John Doe > that signed an assignment? Git tracks both name and email. Surely assuming jdoe@foocorp.com is the same jdoe@foocorp.com that signed the assignment is a safer assumption? Of course, that can be intentionally spoofed. I'm not sure whether the concern is about accidentally mixing up two people, or about someone maliciously misrepresenting the authorship. If the concern is malicious misrepresentation, then this could be solved with GPG-signing of either the emails with the patches, or the Git commits (which is something that Git supports). ---- FWIW, several free software projects that I've contributed to (and require copyright assignment or other licensing paperwork) handle this by requiring that each commit message have a specially formatted line in it: Signed-off-by: Full Name for each person that contributed to that commit (this line can conveniently be added with `--signoff` flag to `git commit`); and they have an automated system that validates that each submitted commit has such a line, and that the person mentioned in the line has signed the agreement. I believe this is standard for projects under the auspices of the Linux Foundation. -- Happy hacking, ~ Luke Shumaker