Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
k-anderson authored Oct 27, 2017
1 parent 0048716 commit 04bcc29
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ No problem! We have many different places where folks can chip in time. These in
* Help find mistakes and write [user guides](https://forums.2600hz.com/forums/kazoo-platform-guides/index/)
* Contribute scripts to the [community repo](https://github.com/2600Hz/community-scripts)
* Help with building RPMs, DEBs, and other system packages
* Browse the open [Issues](https://2600Hz.atlassian.net/browse/KAZOO) and test bugs to see if they're valid
* Browse the open [issues](https://2600Hz.atlassian.net/browse/KAZOO) and test bugs to see if they're valid
* Make a sugestion!

### I know me some Erlang! How can I contribute?
Expand All @@ -124,7 +124,7 @@ No problem! We have many different places where folks can chip in time. These in
* If you're completely new to Git, read Github's [great introduction](https://help.github.com/articles/fork-a-repo/) to forking repos
* Squash a bug, build a feature, etc
* Browse the [ticket queue](https://2600Hz.atlassian.net/browse/KAZOO) and find one you'd like to tackle.
* Feel free to drop a line to the [dev mailing list](https://groups.google.com/forum/?fromgroups#!forum/2600Hz-dev) letting us know you're taking on a ticket, especially if you have questions.
* Feel free to drop a line in the [forums](http://forum.2600Hz.com/) letting us know you're taking on a ticket, especially if you have questions.
* Once you feel the code is ready for inclusion, issue a [pull request](https://help.github.com/articles/using-pull-requests/)!
* Please keep your pull requests focused and specific to the task at hand
* If, in the course of your work you add/modify/delete code unrelated to the core task, create a new ticket describing why you've made these additional changes, and issue a separate pull request.
Expand Down

0 comments on commit 04bcc29

Please sign in to comment.