X-Git-Url: https://jfr.im/git/irc/freenode/web-7.0.git/blobdiff_plain/c5191f36cd34ba018b4bd133f1fe15a77f1fbccf..451d7720c831e134f2e860ddfe1138d1e92340ef:/content/news/2007-04-19-getting-voice-in-freenode-social.md

diff --git a/content/news/2007-04-19-getting-voice-in-freenode-social.md b/content/news/2007-04-19-getting-voice-in-freenode-social.md
index 0861b93a7..8bb01cb5b 100644
--- a/content/news/2007-04-19-getting-voice-in-freenode-social.md
+++ b/content/news/2007-04-19-getting-voice-in-freenode-social.md
@@ -1,9 +1,12 @@
-author: Xyrael
+---
+author: seanw
 date: 2007-04-19 13:07:23+00:00
 slug: getting-voice-in-freenode-social
-title: 'Getting voice in #freenode-social'
+title: Getting voice in #freenode-social
 category: community
 category: freenode
+imported: yes
+robots: noindex
 ---
 If you've been on the network for a little while you'll probably have noticed that #freenode presently forwards you to #freenode-social, a moderated channel. This is officially our "staff social channel", but it oftens confuses people how it can seem to take a long time to get a voice, when most of the channel are happily chattering away. I thought I'd have a go at clearing up this mysterious situation a little, in the hope that the channel will cause less angst in the future. At the moment, we get a lot of requests for voice, and I hope that by explaining the situation here it will be easier for people to understand what policies we are implementing.