Jenkins project CLA
ccla.txt contain the CLA paper. In particular,
icla.txt and ccla.txt in the
are the official versions that people should be using.
See the governance document for the background.
How to file CLA
For each committer that works on the core, ICLA must be in place:
- Fork this repository, and check it out locally
- Create a directory under
collected/icla/YOURNAMEwhere YOURNAME is your Jenkins community ID
- Have ICLA printed, signed, scanned back to PDF. Encrypt it (see below) and put it as
- Add a property file at
collected/icla/YOURNAME/committer.propertiesand list your name, email address, and GitHub ID.
- If your company has a signed CCLA in place, create a symlink at
collected/icla/YOURNAME/cclato the corresponding
- File your fork as a pull request
There should be a plenty of examples of this in our PR section .
To encrypt your CLA, you need gpg. First, obtain the public key of the Jenkins board:
curl https://raw.githubusercontent.com/jenkinsci/infra-cla/approved/publicKey.asc | gpg --import
The command to sign it is:
gpg --encrypt --sign --armor -r "Jenkins Project CLA" < cla.pdf > cla.pdf.asc
If you work on Jenkins core on behalf of your employer, your company needs to have CCLA in place. Have CCLA printed, signed, scanned back to PDF, then send it to
email@example.com along with your account on Jenkins.
How to accept PR
A board member accepts a submitted PR via the following step.
- Check that the submission is in order
- Check that
cla.pdf.asccan be indeed decrypted, and make sure it has valid content
- Merge the PR
- Create a signed tag (
git tag -s) on the merge commit to create a proof
- Add the person to the core team