Developer's Certificate of Origin version

[williamkapke]

Several Working Groups have a reference to Developer's Certificate of Origin 1.0 however nodejs/node#5170 makes me think maybe these should be updated to v 1.1.

Since WGs are autonomous I guess they're not forced to use v1.1, but I bet many just don't know of the newer version- or that the older one is used in their documentation. I can do PRs for all of these, but before I do- I'm wondering if this is one of those rare things that the lawyers insist WGs adopt. If so, should these just have a URL pointing to a "Master" Developer's Certificate of Origin that applies to all things under the Node.js Foundation?

Using DCO v1.1

https://github.com/nodejs/node/blob/master/CONTRIBUTING.md
https://github.com/nodejs/node-chakracore/blob/master/CONTRIBUTING.md
https://github.com/nodejs/docs/blob/master/CONTRIBUTING.md

Using DCO v1.0

https://github.com/nodejs/Intl/blob/master/CONTRIBUTING-draft.md
https://github.com/nodejs/TSC/blob/master/Applications/Express.md
https://github.com/nodejs/TSC/blob/master/BasePolicies/Governance.md
https://github.com/nodejs/TSC/blob/master/Project-Lifecycle.md
https://github.com/nodejs/TSC/blob/master/WORKING_GROUPS.md
https://github.com/nodejs/benchmarking/blob/master/CONTRIBUTING.md
https://github.com/nodejs/dev-policy/blob/master/README.md
https://github.com/nodejs/docker-iojs/blob/master/GOVERNANCE.md
https://github.com/nodejs/docker-node/blob/master/GOVERNANCE.md
https://github.com/nodejs/evangelism/blob/master/CONTRIBUTING.md
https://github.com/nodejs/hardware/blob/master/CONTRIBUTING.md
https://github.com/nodejs/iojs.org/blob/master/CONTRIBUTING.md
https://github.com/nodejs/nan/blob/master/README.md
https://github.com/nodejs/node-chakracore/blob/master/WORKING_GROUPS.md
https://github.com/nodejs/node/blob/master/WORKING_GROUPS.md
https://github.com/nodejs/nodejs-hu/blob/master/content/en/working-groups.md
https://github.com/nodejs/nodejs-uk/blob/master/CONTRIBUTING.md
https://github.com/nodejs/nodejs.org/blob/master/COLLABORATOR_GUIDE.md
https://github.com/nodejs/post-mortem/blob/master/CONTRIBUTING.md
https://github.com/nodejs/testing/blob/master/Governance.md

https://github.com/nodejs/inclusivity-slack-inviter/blob/master/CONTRIBUTING.md

https://github.com/nodejs/inclusivity/blob/master/CONTRIBUTING.md

legacy repos...

https://github.com/nodejs/iojs.org/blob/master/content/en/working-groups.md
https://github.com/nodejs/iojs.org/blob/master/content/tr/working-groups.md
https://github.com/nodejs/node-convergence-archive/blob/master/CONTRIBUTING.md
https://github.com/nodejs/node-convergence-archive/blob/master/WORKING_GROUPS.md

[mikeal]

We should update across the board to 1.1

[mhdawson]

In the case of the benchmarking and post-mortem WG it's simply a case of did not know. What's there was derived from what was in place when the WG formed. The only questions I have are :

• if we change do we need to actively alert WG members
• do we need to know what was contributed under one versus the other or is simply knowing the change over date/timestamps commits enough ?

[williamkapke]

it's simply a case of did not know. What's there was derived from what was in place when the WG formed.

@mhdawson I'm certain that is the case for all of them and I think you raise some good questions. Hopefully the TSC give some guidance.