Add contributor agreement workflow #1540
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What:
Add contributor agreement workflow
Why:
Legal requirement.
How:
As mentioned in the RELICENSE folder README:
openvas-scanner contribution agreement
We want to relicense our code to
GPL-3.0-or-later
orAGPL-3.0-or-later
in the future. Although most of the new code is licensed underGPL-2.0-or-later
we want to make sure that no problems accure when relicensing. Your contributions are licensed underMIT-0
and instantly relicensed to our currently used license. This means eitherGPL-2.0-or-later
orGPL-2.0
. Rust code is currently licensed withGPL-2.0-or-later
per default. C code depends on the location and changes.Please read and commit the /template/template.txt as [Name].md in this folder with your first PR. Having a valid
git.user.name
andgit.user.email
is sufficient.Example usage:
Happy hacking!
Checklist: