-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Document Contributing Examples #26
Comments
The general breakup I use for documentation is:
So, my vote on where to put this goes to DEVELOPMENT.md. |
Sorry for going over you here Kevin, While I think your distinction makes sense, I dont see why it would be in the DEVELOPMENT.md in this case - this is explicitly a guide how to contribute examples. I think all legalities are covered by our contributor license agreement. IMO CONTRIBUTING.md should cover everything that is useful to people who want to contribute - long before they open the first pull request CONTRIBUTING shows the conduct and general process of contributions. Most importantly IMO it also outlines all the ways that you can contribute without ever writing a line of code or opening a PR. Closing since the initial issue is resolved, and subsequent improvements to the doc would best be discussed in ory/meta |
No worries, there are many correct answers here. That was just my take on it. You make an excellent point that CONTRIBUTING.md is a natural place where people look for how to contribute examples. Good choice! |
We should add documentation how to contribute new examples.
Draft PR: #25
We can add a short section to the README or add it to the general template CONTRIBUTING doc or write a seperate CONTRIBUTING for this repo, what do you think @kevgo ?
The text was updated successfully, but these errors were encountered: