Re: [PATCH] MAINTAINERS: create DCO section; add myself to it

[Jason Merrill <jason@redhat.com>]

On 6/2/21 12:33 PM, Koning, Paul wrote:
> 
> 
>> On Jun 2, 2021, at 11:03 AM, Jason Merrill via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>>
>> On 6/1/21 3:22 PM, Richard Biener via Gcc wrote:
>>> On June 1, 2021 7:30:54 PM GMT+02:00, David Malcolm via Gcc <gcc@gcc.gnu.org> wrote:
>>>>> ...
>>>>
>>>> The MAINTAINERS file doesn't seem to have such a "DCO list"
>>>> yet; does the following patch look like what you had in mind?
>>>>
>>>> ChangeLog
>>>>
>>>> 	* MAINTAINERS: Create DCO section; add myself to it.
>>>> ---
>>>> MAINTAINERS | 12 ++++++++++++
>>>> 1 file changed, 12 insertions(+)
>>>>
>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>> index db25583b37b..1148e0915cf 100644
>>>> --- a/MAINTAINERS
>>>> +++ b/MAINTAINERS
>>>> @@ -685,3 +685,15 @@ Josef Zlomek					<josef.zlomek@email.cz>
>>>> James Dennett					<jdennett@acm.org>
>>>> Christian Ehrhardt				<ehrhardt@mathematik.uni-ulm.de>
>>>> Dara Hazeghi					<dhazeghi@yahoo.com>
>>>> +
>>>> +
>>>> +DCO
>>>> +===
>>>> +
>>>> +Developers with commit access may add their name to the following list
>>>> +to certify the DCO (https://developercertificate.org/) for all
>>> There should be a verbatim copy of the DCO in this file or the repository.
>>
>> It's on the website now, at gcc.gnu.org/dco.html , and I've added the section to MAINTAINERS.  It's not clear to me that it needs to be in the source tree as well, since it's project contribution policy rather than license.
> 
> I'm wondering about change control of this document.  The GPL has a version number and references to use the version number.  The DCO seems to have a version number, but the DCO section in the MAINTAINERS file does not give it.  I would think that a certification should call out which DCO it uses, whether in a one-off (in a patch) or in the MAINTAINERS DCO list.

I've added the version to the MAINTAINERS list, thanks.  It is not 
customary to mention the version in a Signed-off-by tag.

Jason