summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorMatthew Holt <[email protected]>2015-05-06 16:39:58 -0600
committerMatthew Holt <[email protected]>2015-05-06 16:39:58 -0600
commita5f20829cb87c3474b68e7af4def46e71b8864e0 (patch)
tree70aac3aa05df845a47627c3cbadefed86f518fa9
parentabe3e5f5976e278521c6526ce3dd223c5898a0ad (diff)
downloadcaddy-a5f20829cb87c3474b68e7af4def46e71b8864e0.tar.gz
caddy-a5f20829cb87c3474b68e7af4def46e71b8864e0.zip
Added link to Slack channelv0.6.0
-rw-r--r--CONTRIBUTING.md2
-rw-r--r--README.md2
2 files changed, 4 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e9680be9c..469a3d128 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,5 +1,7 @@
## Contributing to Caddy
+**[Join us on Slack](https://gophers.slack.com/messages/caddy/)** to chat with other Caddy developers! ([Request an invite](http://bit.ly/go-slack-signup), then join the #caddy channel.)
+
This project gladly accepts contributions. Interested users are encouraged to get involved by [opening issues](https://github.com/mholt/caddy/issues) with their ideas, questions, and bug reports. Bug reports should contain clear instructions to reproduce the problem and state expected behavior.
For small tweaks and bug fixes, feel free to submit [pull requests](https://github.com/mholt/caddy/pulls) at any time. For new features or to change existing behavior, please open an issue first to discuss it and claim it. This prevents overlapping efforts and also keeps the project in-line with its goals.
diff --git a/README.md b/README.md
index 5b684b1a4..87340acfa 100644
--- a/README.md
+++ b/README.md
@@ -114,6 +114,8 @@ For more documentation, please view [the website](https://caddyserver.com/docs).
## Contributing
+**[Join us on Slack](https://gophers.slack.com/messages/caddy/)** to chat with other Caddy developers! ([Request an invite](http://bit.ly/go-slack-signup), then join the #caddy channel.)
+
This project gladly accepts contributions. Interested users are encouraged to get involved by opening issues with their ideas, questions, and bug reports. Bug reports should contain clear instructions to reproduce the problem and state expected behavior.
For small tweaks and bug fixes, feel free to submit pull requests at any time. For new features or to change existing behavior, please open an issue first to discuss it and claim it. This prevents overlapping efforts and also keeps the project in-line with its goals.