emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] describe how to override Author


From: Robert Pluim
Subject: Re: [PATCH] describe how to override Author
Date: Thu, 30 Jun 2022 17:17:03 +0200

>>>>> On Thu, 30 Jun 2022 21:19:36 +0800, Ihor Radchenko <yantar92@gmail.com> 
>>>>> said:

    Ihor> Robert Pluim <rpluim@gmail.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
-- 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]