Merge pull request #581 from taldcroft/help-update-forums

Update the Help page in response to Astropy Community Engagement survey

Author: eteq

help.html

@@ -73,54 +73,32 @@
 	<h1 id="getting-help-with-astropy">Getting Help with Astropy<a class="paralink" href="#getting-help-with-astropy" title="Permalink to this headline">¶</a></h1>
 
 	<p>The best way to get help is usually by asking questions to the Astropy user
-	and development community. There are several very active forums and you are
+	and development community. There are a number of active forums and you are
 	welcome to use whichever one you are the most comfortable with.</p>
 
 	<ul>
 		<li><a href="https://community.openastronomy.org/c/astropy/8" title="">Open Astronomy Discourse</a> - This forum allows
 		questions to be tagged by topic, is searchable on Google, and displays
-	  code snippets better than some of our current alternatives. We plan to
-	  redirect user questions from Slack, Twitter, and mailing lists to this
-	  new site. Please head over and ask (and answer) questions.</li>
-
-		<li><a href="https://twitter.com/astropy">@astropy on Twitter</a> - Mention
-		@astropy in a tweet with your question. Your tweet may be re-tweeted in
-		order to reach the relevant community. Many tweets get responses within a
-		few hours.</li>
-
-		<li><a href="https://www.facebook.com/groups/astropython/">Python Users in
-		Astronomy Facebook group</a> - Post questions or start discussions on
-		anything related to Python programming applied to astronomy. This is a
-		closed group. If your request to join is not approved after a couple days,
-		please message one of the <a
-		href="https://www.facebook.com/groups/astropython/admins/">admins</a> with a
-		brief description of your involvement in astronomy. This is a very active
-		group and is the best place to get help. Most posts get responses within a few hours.
-		</li>
+	    code snippets well. Please head over and ask (and answer) questions.</li>
 
-		<li><a href="http://mail.python.org/mailman/listinfo/astropy">Users Email
-		List</a> - Post questions or start discussions about anything related to
-		Python programming applied to astronomy. This is an active email list and
-		most posts get a response within a few days.</li>
-
-		<li> <a href="https://astropy.slack.com">Astropy Slack team</a> (<a
-		href="http://joinslack.astropy.org">get an account</a>) - Some developers and
-		contributors use Slack for everyday discussions. Feel free to use this
-		forum if you have any questions about contributing to Astropy. The best place to ask questions about how to use Astropy is the
-		<a href="https://community.openastronomy.org/c/astropy/8" title="">Open Astronomy Discourse</a> server.
-		Please browse all the available channels before posting and try to choose the most
-		relevant one.
-		</li>
+		<li> <a href="https://astropy.slack.com">Astropy Slack workspace</a> (<a
+            href="http://joinslack.astropy.org">get an account</a>) - This forum is primarily
+        focused on developing and maintaining the Astropy project, but the
+        <code>#community-help</code> channel is a good place for users to seek help from the
+        Astropy community. </li>
 
-		<li> <a href="http://groups.google.com/group/astropy-dev">Developer Email
-		List [astropy-dev]</a> - Start discussion and ask questions about changing or adding
+		<li><a href="http://mail.python.org/mailman/listinfo/astropy">Astropy Users Email
+		List [[email protected]]</a> - Post questions or start discussions about anything related to
+		Python programming applied to astronomy.</li>
+
+		<li> <a href="http://groups.google.com/group/astropy-dev">Astropy Developers Email
+		List [[email protected]]</a> - Start discussions and ask questions about changing or adding
 			 functionality to the <code>astropy</code> package. This is also the place where significant
 		announcements for contributors/developers are usually made. If you would like to
 		participate in discussion about how the Project is run,
 		please join this list.
 		</li>
 
-
 	</ul>
 
     </section>