[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Welcome to new maintainer Sami Kerola
From: |
Sami Kerola |
Subject: |
Re: Welcome to new maintainer Sami Kerola |
Date: |
Sat, 30 Nov 2013 19:58:03 +0000 |
On 23 November 2013 18:34, Jim Meyering <address@hidden> wrote:
> On Sat, Nov 23, 2013 at 4:17 AM, Sami Kerola <address@hidden> wrote:
> ...
>
> Not a maintainer, but I approve :-)
>
>> diff --git a/README b/README
>> index c2740ea..808413b 100644
>> --- a/README
>> +++ b/README
>> @@ -41,6 +41,22 @@ Bug reports:
>> - unusual options you gave to configure, if any (see config.status).
>> - anything else that you think would be helpful.
>>
>> +Patching process:
>> +- All changes must be sent to mailing list.
>> +- Changes are reviewed by maintainers.
>> +- Maintainer does not review own changes.
>> + * In case of single maintainer, or unresponsive co-maintainer, mailing
>> + list subscribers does the review.
>
> s/does/may perform/
>
>> +- Review means either a patch approval, comments to author, or a reject.
>> + * Approved patches are taken to upstream git.
>> + * Commented patches will require work before they can be approved.
>> + Comments can be untechnical, such as a change author must submit a
>> + copyright assignment to FSF.
>> + * Authors are encouraged to discontinue work with rejected changes, as
>> + the reject is permanent.
>> +- Maintainers keep track of rejected changes so that developers can avoid
>> + proposing the same in future.
> ...
Pushed with small change proposed by Jim.
--
Sami Kerola
http://www.iki.fi/kerolasa/