Skip to content

Developer's Certificate of Origin version #92

Closed

Description

@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

Activity

  1. mikeal commented on Apr 18, 2016

    @mikeal
    Contributor

    We should update across the board to 1.1

  2. mhdawson commented on Apr 21, 2016

    @mhdawson
    Member

    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 ?
  3. williamkapke commented on Apr 23, 2016

    @williamkapke
    ContributorAuthor

    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.

  4. added a commit that references this issue on Apr 23, 2016
  5. williamkapke commented on May 19, 2016

    @williamkapke
    ContributorAuthor

    @mhdawson Did you get answers to your questions above from any @nodejs/tsc reps?
    (Looking to help move nodejs/benchmarking#46 forward)

  6. added a commit that references this issue on May 20, 2016
  7. added a commit that references this issue on Jun 8, 2016
  8. williamkapke commented on Jun 21, 2016

    @williamkapke
    ContributorAuthor

    Ok, so there is only 1 of these left in the entire org: nodejs/dev-policy#78. @jasnell - you have 99% of the commits on that repo, are you the only person with access to the Merge button? Can I get you to merge it so I can close out this issue?

  9. Fishrock123 commented on Jun 30, 2016

    @Fishrock123
    Contributor
  10. williamkapke commented on Jun 30, 2016

    @williamkapke
    ContributorAuthor

    🎉 thanks @Fishrock123 !

  11. added a commit that references this issue on Mar 9, 2023
  12. added a commit that references this issue on Apr 8, 2024
  13. added a commit that references this issue on Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions