Skip to content

Latest commit

 

History

History
22 lines (13 loc) · 1.83 KB

CONTRIBUTING.md

File metadata and controls

22 lines (13 loc) · 1.83 KB

Ensuring a clean code pedigree and lineage is critical to downstream adoption of open source code in industry.

Zowe requires the use of the Developer’s Certificate of Origin 1.1 (DCO), which is the same mechanism that the Linux® Kernel and many other communities use to manage code contributions. The DCO is considered one of the simplest tools for sign offs from contributors as the representations are meant to be easy to read and indicating signoff is done as a part of the commit message.

Here is an example Signed-off-by line, which indicates that the submitter accepts the DCO:

Signed-off-by: John Doe john.doe@hisdomain.com

You can include this automatically when you commit a change to your local git repository using git commit -s. You might also want to leverage this command line tool for automatically adding the signoff message on commits.

Signoff for commits where the DCO signoff was missed

When bringing in a code repository for the first time, or commits done before the DCO checks are enabled, there would be a series of commits that don't include the sign-off statement. You can retroactively signoff commits you've made by make a commit with your DCO signoff that contains a new text file ( suggested name is dco_signoffs/past_commits_name.txt ) with the following contents:

I, <author_name> hereby sign-off-by all of my past commits to this repo subject to the Developer Certificate of Origin (DCO), Version 1.1. In the past I have used emails: <emails>

<COMMIT HASH> <COMMIT MSG>
...

Each user who has made the past commits should have thier own Signed-off-by: line in the commit message.