Green-Software-Foundation / opensource-wg

GSF Open Source WG
Other
43 stars 8 forks source link

[Action Item] Setup DCO or similar (CLA) to allow non-GSF member PRs to be easily accepted #52

Closed Sealjay closed 1 year ago

Sealjay commented 2 years ago

DCO

source: https://en.wikipedia.org/wiki/Developer_Certificate_of_Origin

CLA

A formal agreement that individual contributors and members need to sign.

The Contributor License Agreement is the older of the two mechanisms and is often used by projects with large institutional backing (either corporate or nonprofit). Unlike software licenses, CLAs are not standardized. CLAs can vary from project to project. In some cases, they simply assert that you're submitting work that you're authorized to submit, and you permit the project to use it. Other CLAs (for example the Apache Software Foundation's) may grant copyright and/or patent licenses.

source: https://opensource.com/article/18/3/cla-vs-dco-whats-difference cc by sa attributed

github-actions[bot] commented 2 years ago

This issue is stale and will be closed at the next working group, because it has been open for 30 days with no activity. Remove ready-for-close label or comment to keep this going.

seanmcilroy29 commented 2 years ago

WG to approve either DCO or CLA at the next meeting

dtoakley-tw commented 2 years ago

One question that came up internally: if we go with a DCO, who is going to draft it? And how will it be stored (where and by whom)?

Sealjay commented 2 years ago

@dtoakley-tw - usually the DCO adopts the standard LF template; https://developercertificate.org/ - I haven't seen any deviations from that personally.

If we use that, then we don't need to store it anywhere else

seanmcilroy29 commented 2 years ago

Motion: any objections to adopting the DCO No objections WG agree to adopt the DCO

dtoakley-tw commented 1 year ago

Closing one as the DCO has been implemented!