Merge #641: Remove mention of contact@ and the slack

762cb76 Remove mention of `contact@` and the slack (Wladimir J. van der Laan)

Pull request description:

  The `contact@` address for "For general enquiries and press" is unattended. No one is handling these since @btcdrak became inactive, so imo it's better to remove it.

  As far as I know, no bitcoin core developers regularly attend the Slack, so remove it from contact information as well.

Tree-SHA512: 68a463eef83573ac8ab91a07a2f0855812c1f4dd1da3789d39bdab7266934b693a56fb1a0ae3378ee484a6c40a34af98ff540a1cdd86dbcc5209a6d6b3ceca8a

Author: harding

_includes/references.md

@@ -123,8 +123,6 @@
 [bitcoin-discuss]: http://lists.linuxfoundation.org/mailman/listinfo/bitcoin-discuss
 [bitcoin-dev]: http://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
 [bitcoin-core-dev]: http://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev
-[Slack]: https://bitcoincore.slack.com/
-[slack-invite]: https://slack.bitcoincore.org/
 [software life cycle]: /en/lifecycle
 
 [laanwj-key]: https://pgp.mit.edu/pks/lookup?op=get&search=0x71A3B16735405025D447E8F274810B012346C9A6

_posts/en/pages/2016-01-01-contribute.md

@@ -26,7 +26,7 @@ Feel free to report [issues][issues] and open [pull requests][pulls], but please
 
 **Discussion**
 
-Most Bitcoin Core related discussion happens in the [#bitcoin-core-dev] IRC channel on irc.freenode.net or [bitcoin-core-dev][] mailing list. There is also a mailing list for Bitcoin protocol discussion [bitcoin-dev][] and a general Bitcoin discussion [bitcoin-discuss][]. We also have [Slack][slack] ([request an invitation][slack-invite]).
+Most Bitcoin Core related discussion happens in the [#bitcoin-core-dev] IRC channel on irc.freenode.net or [bitcoin-core-dev][] mailing list. There is also a mailing list for Bitcoin protocol discussion [bitcoin-dev][] and a general Bitcoin discussion [bitcoin-discuss][].
 
 **Contribute to this website**
 

_posts/en/pages/2016-03-12-contact.md

@@ -10,15 +10,13 @@ version: 2
 ---
 <i style="font-weight: bold">Please note Bitcoin Core does not provide general support. General community support can be found at <a style="color:blue" href="https://bitcoin.stackexchange.com/">bitcoin.stackexchange.com</a></i>.
 
-For general enquiries and press: <i class="fa fa-fw fa-envelope"></i> contact<span style="display:none"></span>@bitcoincore.org (<i style="color:red">not for support</i>).
-
 To report security issues: <i class="fa fa-fw fa-envelope"></i> security<span style="display:none"></span>@bitcoincore.org (<i style="color:red">not for support</i>).
 
 You can report bugs in our software using the <i class="fa fa-fw fa-github"></i> [issue tracker][issues].
 
 <i class="fa fa-fw fa-twitter"></i> Twitter: <a href="https://twitter.com/bitcoincoreorg/">@bitcoincoreorg</a>
 
-You can find Bitcoin Core developers on <i class="fa fa-fw fa-slack"></i> [Slack][slack-invite] and [IRC][#bitcoin-core-dev].
+You can find Bitcoin Core developers on [IRC][#bitcoin-core-dev].
 
 To report issue about this website please use the [website][website-issues] issue tracker.
 

_posts/en/posts/2016-01-28-clarification.md

@@ -12,7 +12,7 @@ excerpt: Where to find official information about Bitcoin Core and how you can i
 ---
 Initially, bitcoin.org was used to host the [original Bitcoin paper](https://bitcoin.org/bitcoin.pdf) and became the homepage for the [Bitcoin program](https://bitcoin.org/en/download). The site evolved into a general educational resource for Bitcoin, and is [not affiliated](https://bitcoin.org/en/bitcoin-core/about-site) with the modern Bitcoin Core project. The Bitcoin Core project's official website is bitcoincore.org and while other websites continue to host information about Bitcoin Core, their views do not represent Bitcoin Core. We know that the Bitcoin ecosystem can be confusing, and we are working hard to make these relationships more clear.
 
-For development work, Bitcoin Core mainly uses the `#bitcoin-core-dev` IRC channel on Freenode, [Github](https://github.com/bitcoin/bitcoin), and [the bitcoin-dev mailing list](http://lists.linuxfoundation.org/pipermail/bitcoin-dev/). We also recently created a community [Slack group](https://bitcoincore.slack.com) (request an invitation [here](https://slack.bitcoincore.org)) to enable the greater Bitcoin community to connect with Bitcoin Core developers and contributors more easily.
+For development work, Bitcoin Core mainly uses the `#bitcoin-core-dev` IRC channel on Freenode, [Github](https://github.com/bitcoin/bitcoin), and [the bitcoin-dev mailing list](http://lists.linuxfoundation.org/pipermail/bitcoin-dev/).
 
 While there are many forums in which the Bitcoin community and, indeed, Bitcoin Core contributors engage, Bitcoin Core is not responsible for those forums or their policies, nor does Bitcoin Core take official positions on the community's decisions to use them. Still, we believe it is critical that the Bitcoin community be able to freely discuss and critique every aspect of Bitcoin.
 

_posts/en/posts/2016-02-23-release-0-12-0.md

@@ -107,9 +107,7 @@ The Bitcoin Core Development Team
 IRC Community:
 Join the `#bitcoin-dev` and `#bitcoin-core-dev` channels on `irc.freenode.net`.
 
-[Slack Community](https://bitcoincore.slack.com), sign up at [slack.bitcoincore.org](https://slack.bitcoincore.org).
-
 Twitter:
 Follow Bitcoin Core updates at [@bitcoincoreorg](https://twitter.com/bitcoincoreorg)
 
-_This blog post was written by Ryan Shea based on the official [release notes](https://github.com/bitcoin/bitcoin/blob/v0.12.0/doc/release-notes.md)._
+_This blog post was written by Ryan Shea based on the official [release notes](https://github.com/bitcoin/bitcoin/blob/v0.12.0/doc/release-notes.md)._

_posts/en/posts/2016-03-15-announcelist.md

@@ -9,7 +9,7 @@ version: 2
 ---
 In an effort to increase communications, we are launching an opt-in, _announcement-only_ mailing-list for users of Bitcoin Core to receive notifications of security issues and new releases.
 
-While the Bitcoin Core project has a variety of communication channels, this website, Twitter [@bitcoincoreorg][], [Slack][] there have been a number of requests for an [announcement mailing list](/en/list/announcements/join). It is intended to be extremely low volume, focused on critical notifications as well as to announce new releases.
+While the Bitcoin Core project has a variety of communication channels, this website, Twitter [@bitcoincoreorg][], there have been a number of requests for an [announcement mailing list](/en/list/announcements/join). It is intended to be extremely low volume, focused on critical notifications as well as to announce new releases.
 
 To subscribe, enter your email address below:
 

_posts/en/posts/2016-08-23-release-0-13-0.md

@@ -193,7 +193,7 @@ For details on all the changes made in Bitcoin Core 0.13.0, please [read the rel
 
 With the release of Bitcoin Core 0.13.0, we begin the six-month release cycle for the next version of Bitcoin Core (expected to be 0.14.0).  With the participation of the community, we will also be choosing the BIP9 parameters for segregated witness and releasing a minor version (expected to be 0.13.1) with segwit fully enabled.
 
-If you are interested in contributing to Bitcoin Core, please see our [contributing page](/en/contribute) and the document [How to contribute code to Bitcoin Core](/en/faq/contributing-code/).  If you don't know where to get started or have any other questions, please stop by either our [IRC][] or [Slack][] chatrooms and we'll do our best to help you.
+If you are interested in contributing to Bitcoin Core, please see our [contributing page](/en/contribute) and the document [How to contribute code to Bitcoin Core](/en/faq/contributing-code/).  If you don't know where to get started or have any other questions, please stop by our [IRC][] chatroom and we'll do our best to help you.
 
 ## Hashes for verification
 
@@ -223,5 +223,4 @@ These are the SHA-256 hashes of the released files:
 [release notes feefilter]: /en/releases/0.13.0/#low-level-rpc-changes
 [release notes hd wallet]: /en/releases/0.13.0/#hierarchical-deterministic-key-generation
 [release notes segwit]: /en/releases/0.13.0/#segregated-witness
-[Slack]: https://slack.bitcoincore.org
 [transaction priority]: https://en.bitcoin.it/wiki/Transaction_fees#Priority_transactions

_posts/en/posts/2016-10-27-release-0.13.1.md

@@ -142,7 +142,7 @@ For details on all the changes made in Bitcoin Core 0.13.1, please read the [rel
 
 Bitcoin Core 0.13.1 is the only soft fork release planned for the 0.13 release series.  The next major planned release is Bitcoin Core 0.14.0, which has feature freeze [scheduled](https://github.com/bitcoin/bitcoin/issues/8719) for mid-January 2017 and release to follow after all testing is completed (this typically takes more than a month in order to give everyone sufficient time to test).
 
-If you are interested in contributing to Bitcoin Core, please see our [contributing page](/en/contribute) and the document [How to contribute code to Bitcoin Core](/en/faq/contributing-code/). If you don’t know where to get started or have any other questions, please stop by either our [IRC](https://en.bitcoin.it/wiki/IRC_channels) or [Slack](https://slack.bitcoincore.org/) chatrooms and we’ll do our best to help you.
+If you are interested in contributing to Bitcoin Core, please see our [contributing page](/en/contribute) and the document [How to contribute code to Bitcoin Core](/en/faq/contributing-code/). If you don’t know where to get started or have any other questions, please stop by our [IRC](https://en.bitcoin.it/wiki/IRC_channels) chatroom and we’ll do our best to help you.
 
 ## Hashes for verification
 

_posts/en/posts/2017-01-03-release-0.13.2.md

@@ -37,7 +37,7 @@ These are the [SHA-256 hashes](https://bitcoin.org/bin/bitcoin-core-0.13.2/SHA25
 
 ## Conclusion
 
-If you are interested in contributing to Bitcoin Core, please see our [contributing page](/en/contribute) and the document [How to contribute code to Bitcoin Core](/en/faq/contributing-code/). If you don’t know where to get started or have any other questions, please stop by either our [IRC](https://en.bitcoin.it/wiki/IRC_channels) or [Slack](https://slack.bitcoincore.org/) chatrooms and we’ll do our best to help you.
+If you are interested in contributing to Bitcoin Core, please see our [contributing page](/en/contribute) and the document [How to contribute code to Bitcoin Core](/en/faq/contributing-code/). If you don’t know where to get started or have any other questions, please stop by our [IRC](https://en.bitcoin.it/wiki/IRC_channels) chatroom and we’ll do our best to help you.
 
 [release notes]: /en/releases/0.13.2/
 [download page]: https://bitcoin.org/en/download

_posts/en/posts/2017-03-08-release-0.14.0.md

@@ -144,7 +144,7 @@ For details on all the changes made in Bitcoin Core 0.14.0, please read the [rel
 
 The next major planned release will be scheduled for approximately six months after the 0.14.0 release (but it will not be released until fully tested).
 
-If you are interested in contributing to Bitcoin Core, please see our [contributing page](/en/contribute) and the document [How to contribute code to Bitcoin Core](/en/faq/contributing-code/). If you don’t know where to get started or have any other questions, please stop by either our [IRC](https://en.bitcoin.it/wiki/IRC_channels) or [Slack](https://slack.bitcoincore.org/) chatrooms and we’ll do our best to help you.
+If you are interested in contributing to Bitcoin Core, please see our [contributing page](/en/contribute) and the document [How to contribute code to Bitcoin Core](/en/faq/contributing-code/). If you don’t know where to get started or have any other questions, please stop by our [IRC](https://en.bitcoin.it/wiki/IRC_channels) chatroom and we’ll do our best to help you.
 
 ## Hashes for verification