Add CLA + CoC

[winfried-ripken]

Description

• Add code of conduct in documentation
• Add CLA and reference it with CLA bot
• Fix pre-commit: bump black version to 22.3.0

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring including code style reformatting
• Other (please describe):

Checklist:

• I have read the [contributing guideline doc] () (external only)
• I have signed the [CLA] () (external only)
• Lint and unit tests pass locally with my changes
• I have kept the PR small so that it can be easily reviewed
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• All dependency changes have been reflected in the pip requirement files.

[TiansuYu]

LGTM. One question: Where will be the signatures be saved? If this is saved in this repo, does that mean personal information will be collected and shared?

[TiansuYu]

Include yourself?
And is it possible to add a team inside?

[winfried-ripken]

Thanks for reviewing Tiansu! I excluded myself on purpose, because I wanted to test the functionality with my account.

From the documentation:
After the contributor signed a CLA, the contributor's signature with metadata will be stored in a JSON file inside the repository

I understand that the github username and a reference to the PR will be stored. This information would also be publicly available from the PR itself. In the case we want to avoid the signed CLAs being publicly available, we can store them in a separate repository (e.g. oss-infra). Only requirement would be that the cla-bot has access to this other repository.

[winfried-ripken]

Could not find any information about including teams, but will try that. Wildcards are supported for the allowlist

[TiansuYu]

I think for the moment, collecting github account names in this repo is fine, as they are already publicly available anyway in the git history. Thx for the explanation.

[winfried-ripken]

This is blocked until we figure out how the bot can get access to our repositories (probably by adding another minion account)

[TiansuYu]

Thanks, that looks great!