Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Contributor License Agreement of the Jenkins project
branch: master

This branch is 32 commits behind jenkinsci:master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
collected
.gitignore
README.md
ccla.txt
icla.txt
publicKey.asc

README.md

Jenkins project CLA

icla.txt and ccla.txt contain the CLA paper. In particular, icla.txt and ccla.txt in the approved branch are the official versions that people should be using. See the governance document for the background.

How to file CLA

Have ICLA and/or CCLA printed, signed, scanned back to PDF, then send it to jenkinsci-cla@googlegroups.com along with your account on Jenkins.

How we store signed CLAs

For now, this section is more of a note to the board for how to store this. Eventually I'd like to have people submit this via pull requests.

For each signed individual CLA, there should be one directory named collected/icla/JENKINSACCOUNT where JENKINSACCOUNT is the account on Jenkins. This directory should house the CLA encyrpted by GPG in the ASCII armored form. The public key for this is in publicKey.asc. The command to sign it is:

gpg --encrypt --sign --armor -r "Jenkins Project CLA" < cla.pdf > cla.pdf.asc

This directory should also have committer.properties that capture the key information about this individual.

For each signed corporate CLA, there should be one directory named collected/ccla/COMPANYNAME. COMPANYNAME could be anything reasonable descriptive and unique. Where an individual is related to a company, have collected/icla/NAME/ccla be a symlink to ../../ccla/COMPANYNAME to establish a relationship.

Something went wrong with that request. Please try again.