From 06f7266a6e23c9cbef51933a8ef95237f7867a59 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicol=C3=A1s=20Venturo?= Date: Tue, 12 Mar 2019 13:15:46 -0300 Subject: [PATCH] Replace mentions of Slack for forum links. (#1671) * Replace mentions of Slack for forum links. * make forum lowercase --- .github/ISSUE_TEMPLATE/bug_report.md | 2 +- README.md | 4 ++-- RELEASING.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index d932e7632..ce8896015 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -6,7 +6,7 @@ about: Report a bug in OpenZeppelin - + **💻 Environment** diff --git a/README.md b/README.md index 22a3df56f..4db9d1a78 100644 --- a/README.md +++ b/README.md @@ -30,7 +30,7 @@ contract MyNFT is ERC721Full, ERC721Mintable { > You need an ethereum development framework for the above import statements to work! Check out these guides for [Truffle] or [Embark]. -On our site you will find a few [guides] to learn about the different parts of OpenZeppelin, as well as [documentation for the API][API docs]. Keep in mind that the API docs are work in progress, and don’t hesitate to ask questions in [our Slack][Slack]. +On our site you will find a few [guides] to learn about the different parts of OpenZeppelin, as well as [documentation for the API][API docs]. Keep in mind that the API docs are work in progress, and don’t hesitate to ask questions in [our forum][forum]. ## Security @@ -53,7 +53,7 @@ OpenZeppelin is released under the [MIT License](LICENSE). [API docs]: https://openzeppelin.org/api/docs/token_ERC721_ERC721BasicToken.html [guides]: https://openzeppelin.org/api/docs/get-started.html -[Slack]: https://slack.openzeppelin.org +[forum]: https://forum.zeppelin.solutions [Zeppelin]: https://zeppelin.solutions [contribution guide]: CONTRIBUTING.md [Truffle]: https://truffleframework.com/docs/truffle/quickstart diff --git a/RELEASING.md b/RELEASING.md index 59c7ee971..e043bfe85 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -40,7 +40,7 @@ Once the CI run for the new tag is green, publish on npm under the `next` tag. Y npm publish --tag next ``` -Publish the release notes on GitHub and ask our community manager to announce the release candidate on at least Slack and Twitter. +Publish the release notes on GitHub and the forum, and ask our community manager to announce the release candidate on at least Twitter. ## Creating the final release