-
Notifications
You must be signed in to change notification settings - Fork 403
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
Add community profile documentation #49
Conversation
The format is based on [Keep a Changelog](http://keepachangelog.com/) | ||
and this project adheres to [Semantic Versioning](http://semver.org/). | ||
|
||
## [Unreleased] - yyyy-mm-dd |
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.
This is an example and we will remove them once we release 0.1.0
@@ -0,0 +1,128 @@ | |||
# Contributor Covenant Code of Conduct |
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.
This is from standard Github's recommendation.
source: https://github.com/EthicalSource/contributor_covenant
@@ -0,0 +1,31 @@ | |||
# Contributing |
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.
This is high level contributing guidance. Each sub project should includes a DEVELOPMENT.md
for detail development and testing guidance.
d063c85
to
a06c8ae
Compare
LGTM. |
Co-authored-by: Eric Liang <ekhliang@gmail.com>
We have two members review the change and I think we should be good to go. Feel free to cut new issues if anyone has further feedbacks. |
* Add CODE_OF_CONDUCT.md * Move LICENSE to root level * Add CHANGELOG.md * Add CONTRIBUTING.md * Update CONTRIBUTING.md Co-authored-by: Eric Liang <ekhliang@gmail.com> Co-authored-by: Eric Liang <ekhliang@gmail.com>
Why are these changes needed?
We need to follow recommended community standards.
Related issue number
#48
Checks
These are documentation changes so I didn't run test against the changes
/cc @chenk008 @akanso @chaomengyuan