Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Choose a license for this repo #151

Closed
mcgege opened this issue Aug 21, 2018 · 6 comments
Closed

Choose a license for this repo #151

mcgege opened this issue Aug 21, 2018 · 6 comments

Comments

@mcgege
Copy link
Member

mcgege commented Aug 21, 2018

See https://help.github.com/articles/adding-a-license-to-a-repository/

@mcgege
Copy link
Member Author

mcgege commented Aug 21, 2018

@chris-rock @artem-sidorenko Can we set the license to Apache-2.0 as this is also used for most other repos of dev-sec?

@timstoop
Copy link
Contributor

According to the README.md in the root, it already is licensed under the Apache-2.0 license.

@timstoop
Copy link
Contributor

While on the subject, according to https://dev-sec.io/docs/coding/contributing/#contributing each commit is required to have the HardeningFramework-DCO-1.1-Signed-off-by: Joe Smith <joe.smith@email.com> (github: github_handle) line in the commit message. However, I notice the last few commits do not have this. Is it a soft requirement or are they merged in error?

@mcgege
Copy link
Member Author

mcgege commented Aug 23, 2018

@timstoop I must admit that I didn't know about this ... but as I don't see this regularly in the other dev-sec repos I suppose this is more of a soft requirement ;-)

@timstoop
Copy link
Contributor

And there I was, being the nicest kid in the class and adding it to all my commits :P

@mcgege
Copy link
Member Author

mcgege commented Aug 27, 2018

Thanks ;-)

@mcgege mcgege closed this as completed Aug 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants