Browse files

Add missing project management files.

- Add Code of Conduct.
- Add templates for issues and pull requests.
- Add contributing guide.
- Add missing linter in the Makefile.

Signed-off-by: David Calavera <>
  • Loading branch information...
calavera committed Mar 15, 2017
1 parent b17056b commit 2dd52e77087ddb06eefbfec3b8a2e362780b4c6f
Showing with 186 additions and 2 deletions.
  1. +30 −0 .github/
  2. +35 −0 .github/
  3. +74 −0
  4. +41 −0
  5. +6 −2 Makefile
@@ -0,0 +1,30 @@
If you are reporting a new issue, make sure that we do not have any duplicates
already open. You can ensure this by searching the issue list for this
repository. If there is a duplicate, please close your issue and add a comment
to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to
include the BUG REPORT INFORMATION shown below. If you fail to provide this
information within 7 days, we cannot debug your issue and will close it. We
will, however, reopen it if you later provide the information.
If you have an issue that can be shown visually, please provide a screenshot or
gif of the problem as well.
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
**- Do you want to request a *feature* or report a *bug*?**
**- What is the current behavior?**
**- If the current behavior is a bug, please provide the steps to reproduce.**
**- What is the expected behavior?**
**- Please mention your Go version, and operating system version.**
@@ -0,0 +1,35 @@
Thanks for submitting a pull request!
Please make sure you've read and understood our contributing guidelines;
If this is a bug fix, make sure your description includes "fixes #xxxx", or
"closes #xxxx", where #xxxx is the issue number.
Please provide enough information so that others can review your pull request.
The first three fields are mandatory:
**- Summary**
Explain the **motivation** for making this change.
What existing problem does the pull request solve?
**- Test plan**
Demonstrate the code is solid.
Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
**- Description for the changelog**
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
**- A picture of a cute animal (not mandatory but encouraged)**
@@ -0,0 +1,74 @@
# Contributor Covenant Code of Conduct
## Our Pledge
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, gender identity and expression, level of experience,
nationality, personal appearance, race, religion, or sexual identity and
## Our Standards
Examples of behavior that contributes to creating a positive environment
* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
* The use of sexualized language or imagery and unwelcome sexual attention or
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic
address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting
## Our Responsibilities
Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.
## Scope
This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
members of the project's leadership.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
available at [][version]
@@ -0,0 +1,41 @@
Contributions are always welcome, no matter how large or small. Before contributing,
please read the [code of conduct](
## Setup
> Install Go and Glide
$ git clone
$ cd gotrue
$ make deps
## Building
$ make build
## Testing
$ make test
## Pull Requests
We actively welcome your pull requests.
1. Fork the repo and create your branch from `master`.
2. If you've added code that should be tested, add tests.
3. If you've changed APIs, update the documentation.
4. Ensure the test suite passes.
5. Make sure your code lints.
## License
By contributing to Netlify CMS, you agree that your contributions will be licensed
under its [MIT license](LICENSE).
@@ -1,4 +1,4 @@
.PONY: all build deps image test
.PONY: all build deps image lint test
help: ## Show this help.
@awk 'BEGIN {FS = ":.*?## "} /^[a-zA-Z_-]+:.*?## / {sub("\\\\n",sprintf("\n%22c"," "), $$2);printf "\033[36m%-20s\033[0m %s\n", $$1, $$2}' $(MAKEFILE_LIST)
@@ -9,10 +9,14 @@ build: ## Build the binary.
go build -ldflags "-X`git rev-parse HEAD`"
deps: ## Install dependencies.
go get -u && glide install
@go get -u
@go get -u && glide install
image: ## Build the Docker image.
docker build .
lint: ## Lint the code
golint `go list ./... | grep -v /vendor/`
test: ## Run tests.
go test -v `go list ./... | grep -v /vendor/`

0 comments on commit 2dd52e7

Please sign in to comment.