From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Co-authoring and attribution in commit message Date: Sat, 05 Oct 2019 09:55:15 +0300 Message-ID: <838spz65rg.fsf@gnu.org> References: <8736h9rdc4.fsf@gnu.org> <87a7bbjdwe.fsf@gnu.org> <87a7ba8uvx.fsf@gnu.org> <87pnk2zvvy.fsf@gnu.org> <87sgows6wy.fsf@gnu.org> <87ef0dy18z.fsf@gnu.org> <87impk675h.fsf@gnu.org> <874l13h30l.fsf@gnu.org> <7386ef98-c151-e1ce-23fa-11470a16f0d3@yandex.ru> <87h84x1zoa.fsf@gnu.org> <4be972f9-45a3-f2aa-f532-d7b8fbe054fd@yandex.ru> <87v9t69syt.fsf@gnu.org> <6aeaedee-ad6c-ca35-98d0-c07685e6a72d@yandex.ru> <878sq16ors.fsf_-_@gmail.com> <878sq0chwq.fsf@red-bean.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="150239"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org, kevin.legouguec@gmail.com, dgutov@yandex.ru To: Karl Fogel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 05 08:56:16 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iGdzD-000cz7-5k for ged-emacs-devel@m.gmane.org; Sat, 05 Oct 2019 08:56:15 +0200 Original-Received: from localhost ([::1]:54504 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iGdzC-0007l6-2q for ged-emacs-devel@m.gmane.org; Sat, 05 Oct 2019 02:56:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51369) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iGdyW-0007km-EJ for emacs-devel@gnu.org; Sat, 05 Oct 2019 02:55:33 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34886) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iGdyV-0005iP-TQ; Sat, 05 Oct 2019 02:55:31 -0400 Original-Received: from [176.228.60.248] (port=1640 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iGdyR-00089s-0p; Sat, 05 Oct 2019 02:55:28 -0400 In-reply-to: <878sq0chwq.fsf@red-bean.com> (message from Karl Fogel on Fri, 04 Oct 2019 16:36:21 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:240595 Archived-At: > From: Karl Fogel > Date: Fri, 04 Oct 2019 16:36:21 -0500 > Cc: emacs-devel@gnu.org, > Kévin Le Gouguec > > One place to look (and possibly to contribute a suggestion to) is https://www.conventionalcommits.org/. Another, older standard is at http://subversion.apache.org/docs/community-guide/conventions.html#crediting, though I think it's only used in that one project. The latter one looks like it's more directly relevant to this use case than Conventional Commits is, as it currently supports these fields: > > Patch by: > Suggested by: > Found by: > Review by: > Tested by: Emacs ChangeLog-related modes recognize the attributions via the following regexp: "\\(^\\( +\\|\t\\)\\| \\)\\(Thanks to\\|Patch\\(es\\)? by\\|Report\\(ed by\\| from\\)\\|Suggest\\(ed by\\|ion from\\)\\) > "Co-authored-by:" is probably similar to "Patch by:". Now, I think it still makes sense for us to use "Co-authored-by:", given that some (admittedly non-free-software) tools already parse it [1], but I wanted to make sure that these parallel efforts are known, so that we can learn whatever is available to be learned from them as we're setting a convention. I think this should be part of the GNU Coding Standards (GCS), and thus I suggest to discuss it on the bug-standards mailing list, not here. IMO, it isn't right for a single project to adopt such standards, this should be in GNU-common conventions and guidelines.