-
Notifications
You must be signed in to change notification settings - Fork 119
Add CONTRIBUTING.md & CODE_OF_CONDUCT.md #925
Conversation
#924 failed in jenkins because of https://github.com/gravitational/robotest/issues/154 (which I have an idea of how to fix), and this PR is inheriting the build status because the commit hash is identical. I retriggered, but it is hitting some sort of GH API throttling:
As seen here: https://jenkins.gravitational.io/job/Gravity-PR-5.2/job/PR-924/3/console Once that clears up, I'd expect the CI to be green. |
Once you know you have a issue, make sure to fill out all sections of the | ||
one of the templates at https://github.com/gravitational/gravity/issues/new/choose. | ||
|
||
Gravity contributors will triage the issue shortly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it safe to make this promise? I don't know what our issues/triage policy is currently.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple of typos.
While reviewing onboarding materials, @klizhentas noticed that the gravity repo was missing the code of conduct that was present in teleport. For consistency, adding it here. Addresses #923.
As I was looking at #923 (Gravity missing a code of conduct) I realised it didn't have any contributing info. Adding a CONTRIBUTING may help foster outsite engagement. Inspiration drawn from Teleport's CONTRIBUTING, mashed up with golang's.
This will help with discoverability, and tie the docs together more seamlessly.
Gravity uses the latter, as mentioned in: #925 (comment)
99a49dd
to
abaea0a
Compare
Resolves #923 by adding the code of conduct, and takes a stab at contribution guidelines. CONTRIBUTING felt appropriate to give discoverability to this info from the README.
Testing Done: