Notice of Change to Code of Conduct
by Adam Kaplan
Dear Shipwright Community,
As part of our onboarding to the CNCF, our project Code of Conduct is being
updated from the general Contributor Covenant to the CNCF Code of Conduct
[1]. Though some of the specifics are changing with respect to scope and
reporting, the spirit remains the same: make Shipwright a welcoming place
to collaborate and contribute.
Please review the linked pull request to view the changes in full. If you
have any questions or concerns, please do not hesitate to contact the
maintainers via email or Slack.
Sincerely,
Adam (on behalf of the Shipwright maintainers)
[1] https://github.com/shipwright-io/.github/pull/5
--
Adam Kaplan
He/Him
Principal Software Engineer
Red Hat <https://www.redhat.com>
100 E. Davie Street
adam.kaplan(a)redhat.com
<https://www.redhat.com>
3 weeks, 6 days
Developer Certificate of Origin (DCO) now enabled in all Shipwright Repositories
by Enrique Encalada
Hi all,
As part of our ongoing onboarding to CNCF, we have enabled by default DCO https://github.com/apps/dco .
What is this?
The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. See more in https://developercertificate.org/
What does this means for your contributions?
Upon opening Pull Requests, you will see now a DCO check, next to the CI checks. If the commits are not signed off, the DCO check will be in a failing state.
This means that all your commit messages must contain the "Signed-off-by" line with an email address that matches the commit author. See more on https://github.com/apps/dco .
Please reach out if you have any further questions.
Regards,
Enrique Encalada
3 weeks, 6 days