From: Robert Pluim <firstname.lastname@example.org> To: Ihor Radchenko <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [PATCH] describe how to override Author Date: Thu, 30 Jun 2022 17:17:03 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <87edz670gn.fsf@localhost> (Ihor Radchenko's message of "Thu, 30 Jun 2022 21:19:36 +0800") >>>>> On Thu, 30 Jun 2022 21:19:36 +0800, Ihor Radchenko <firstname.lastname@example.org> said: Ihor> Robert Pluim <email@example.com> writes: >> >> Occasional committers would probably not read org-maintenance.org, and >> >> those are the people this section is aimed at, I think. Plus itʼs the >> >> kind of thing you need to catch early: once the commit has been pushed >> >> itʼs too late. >> Ihor> Not really. org-contribute.org is the page directly linked from Ihor> orgmode.org. It is aiming for new contributors with no write access. >> >> This particular change is in "Your first commit as an Org >> maintainer". Perhaps that node should be moved to org-maintenance.org? Ihor> I do not think so. I am seeing this section as a "crash course" for the Ihor> new maintainers. We should only provide the critical information there. Ihor> Not too much, not too less. Something to not scare people with the Ihor> details. I guess we disagree about whether knowing about the distinction between 'Author:' and 'Commit:' is critical or not. For a free software project correct attribution of changes is very important, so committers should pay attention to it (and by extension the documentation should educate them about it at the earliest opportunity). But youʼre the maintainer :-) Ihor> The elaborate details should be in org-maintenance.org, which is Ihor> directly mentioned at the end of the "first commit" section. In "Where can I track bugs, patches and updates?" or somewhere else? BTW, Iʼm having trouble parsing this sentence from there: You don't much more: confirming bugs is a critical contribution. Thereʼs at least one word missing betweeen "donʼt" and "much" there. Robert --
next prev parent reply other threads:[~2022-06-30 15:18 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-28 14:38 ox-latex table tabbing support emacs--- via General discussions about Org-mode. 2022-04-04 10:33 ` Ihor Radchenko [not found] ` <87wng5nno3.fsf@localhost-Mzo7eKN----2> 2022-04-04 14:03 ` emacs--- via General discussions about Org-mode. 2022-06-21 4:43 ` Daniel Fleischer 2022-06-24 13:37 ` Robert Pluim 2022-06-24 14:20 ` Daniel Fleischer 2022-06-24 15:01 ` Robert Pluim 2022-06-24 15:50 ` Daniel Fleischer 2022-06-24 19:32 ` emacs--- via General discussions about Org-mode. 2022-06-25 3:32 ` Ihor Radchenko 2022-06-26 10:08 ` Robert Pluim 2022-06-26 13:47 ` [PATCH] describe how to override Author Robert Pluim 2022-06-26 14:04 ` Daniel Fleischer 2022-06-27 9:53 ` Ihor Radchenko 2022-06-28 12:07 ` Robert Pluim 2022-06-29 10:10 ` Ihor Radchenko 2022-06-30 8:18 ` Robert Pluim 2022-06-30 13:19 ` Ihor Radchenko 2022-06-30 15:17 ` Robert Pluim [this message] 2022-07-02 4:21 ` Ihor Radchenko 2022-06-26 1:54 ` ox-latex table tabbing support Ihor Radchenko 2022-06-26 3:49 ` Kyle Meyer 2022-06-26 14:46 ` [PATCH] " Daniel Fleischer 2022-06-26 18:18 ` Kyle Meyer 2022-06-26 18:48 ` Daniel Fleischer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] describe how to override Author' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).