content/news/2007-05-15-all-roads-lead-to-defocus.markdown

   1 author: christel
   2 date: 2007-05-15 03:49:56+00:00
   3 slug: all-roads-lead-to-defocus
   4 title: 'All roads lead to #defocus'
   5 ---
   6
   7 Some time ago I used to work as a special projects mentor for a large international company, one of the things I were to try purvey to the people I trained was 'Change is good, change is great'. It took a long time for me to change my internal thought process and face my own fears of giving up security of what's familiar, and as such it took a long time for me to be able to stand there in a room full of people and utter those words while actually believing in and meaning what I said.
   8 This past week the phrase has played on my mind a lot, in regards to our changes to the official freenode help and social channels.
   9 We are certainly hoping that this change will turn out to be good -- and feedback so far has been primarily positive, though, that is not to say there hasn't been those unhappy with the change.
  10 I will try and speak of some of the reasoning behind closing down #freenode-social, and replacing it with respectively #freenode for help and #defocus for social chatter.  The below quotations may help you understand some of the reasoning behind changing the way we operate our social channel, these are just some and not all of the observations made.
  11
  12
  13 <blockquote>Over the last little while it has become apparent that running #freenode-social the way we currently do is not working for staff or users, and as such is not working for the network, the community or the visions and goals we possess.
  14 We (freenode staff) propose to close down #freenode-social and replace it with #freenode (focused on user/network support ala #tapthru) and #freenode-offtopic (for general natter), in this regard we would like to extend an invitation to the tapthru staff to come on board and co-manage #freenode with us.
  15 The list of items below should be considered a starting point for conversation rather than any definitive pronouncement of how the world should wag. It's not complete (no such list can ever be) but tries to hit most of the major issues we'll face as we embark on this project. Be blunt about your likes/dislikes of the various suggestions and about suggesting changes/additions/removals! Please note that there is no significance to the ordering of the items in the list below; that's just how they came out. They have numbers only to speed the referencing of them during discussion.
  16 1. What is wrong with #freenode-social? (This isn't the finger of blame! Just a way to get a handle on what we are trying to fix.)
  17 1. No defined topic (so no way to say: "that's offtopic")
  18 2. No defined rules
  19 3. Lack of regular chanops (we got scared and ran away)
  20 4. Chanop behaviour is sporadic and hard to predict
  21 5. Voicing/devoicing system has holes
  22 1. Voicing is random. This can cause various behaviors:
  23 1. People want to capture voice and hold it forever, against the time they might want to speak
  24 2. When someone has waited hours to be voiced, (s)he may already be quite frustrated
  25 3. By the time you're voiced, you forgot why you came
  26 2. We can't remember why a person was devoiced
  27 3. Access list too long to meaningfully evaluate
  28 4. No system for 'devoice for xx minutes', so devoices either get forgotten and remain forever, or someone is re-voiced sooner than the devoicing staffer wanted them to be.
  29 6. We used to say 'be a catalyst in #freenode-social and maybe we'll ask you to be staff someday' ... is that still true?
  30 2. Some scenarios for the new #freenode channel (things people will come to say). ?? Categorize as (O)OK, (N)Not OK, (P)Private ??
  31 1. Nick issues
  32 1. Help me register my nick
  33 2. Cloak me!
  34 3. Someone took my nick
  35 4. Lost my password
  36 5. Help me admin my nick options
  37 2. Client issues
  38 1. Help me with my client
  39 2. How does $somecommand work?
  40 3. Cannot connect to freenode
  41 3. Channel issues
  42 1. I need help with my channel registration, modes, etc
  43 2. They banned me in #foo!
  44 3. #foo is offtopic/offensive/criminal/other, whatcha gonna do about it?
  45 4. #foo has mean chanops
  46 5. We are having a disagreement in #foo, please come and mediate
  47 6. Explain primary/about channels for me again?
  48 7. Does #foochannel exist?
  49 8. Everybody come to #foo, it is the ubar-greatest!
  50 4. About individuals
  51 1. $somenick is PMing me and I don't like it
  52 2. $somenick is spamming/trolling/racist remarks/other on #foo
  53 3. $somenick is spamming/trolling/racist remarks/other on several channels
  54 4. $somenick is an asshole, kline him now
  55 5. $somenick's nick offends me
  56 6. My friend $somenick was klined, remove it already!
  57 5. Group issues
  58 1. GCF approvals
  59 2. Explain groups to me
  60 3. I'm a GC and I need something done
  61 4. Who is the GCF for $somegroup
  62 5. $somegroup has no right to exist, we are the rightful owners of that group name
  63 6. Freenode issues
  64 1. $somestaffer treated me unfairly
  65 2. I want to be a staffer
  66 3. Teach me to be a catalyst
  67 4. Announcements by staff
  68 5. Donation issues
  69 6. I want to host a freenode server
  70 7. This wierd thing just happened, is it a network issue, help!
  71 8. Help me understand the Freenode policy about $whatever.
  72 9. I disagree with Freenode policy
  73 10. Freenode should do this wonderful thing _______!
  74 11. Freenode should endorse my campaign to save the world
  75 12. I hate Freenode, rant-rant-rant.
  76 13. I love Freenode, love-love-love.
  77 7. Other
  78 1. I need help with something not in 1-6 above
  79 2. Let's talk about my life issues/problems/whatever.
  80 3. My political/religious/societal views
  81 4. spam
  82 5. random invective
  83 6. http://somelink is funny/offensive/interesting/whatever, let's all talk abut it
  84 7. well, all sorts of stuff not found in 1-6 above
  85 3. Escalating help. We all have different freenode-admin privs; some of us have none other than 'helpful person'.
  86 1. General SLA for the channel: "#Freenode tries but does not promise to solve your issue; if you are still unsolved here, talk to staffer via /stats p"
  87 2. Try to identify things that should happen privately (in PM) and move there as soon as possible.
  88 3. If you haven't the privs to resolve an issue, send them to /stats p or /who *freenode/staff* asap
  89 4. Suggestions?
  90 4. #freenode discipline
  91 1. What do we discipline for?
  92 1. Offtopic
  93 2. Tone/attitude
  94 1. Ontopic but rude
  95 2. Note- how to handle "I was not being rude, I was joking!"
  96 3. Personal attacks/characterizations/judgements. (Suggest: we simply avoid all observations of a personal matter)
  97 4. Giving out bad advice on the channel. Again, the issue of "I was joking" should be addressed.
  98 2. Possible discipline escalations:
  99 1. Catalyze in-channel, never ban or mute
 100 2. Catalyze in-channel, ban or mute after x lines or minutes if it doesn't work
 101 3. Mute immediately and catalyze in PM; unmute when they understand
 102 4. Ban/mute for x minutes on first offense, y minutes on second offense, z minutes on third offense
 103 5. Replace ban/mute with redirec to #freenode-offtopic; perform all catalyzation in there
 104 6. Some combination of the above
 105 3. How to handle leftover bans/mutes?
 106 1. leave forever since no one wants to override another chanop's actions
 107 2. periodically flush any ban/mute more than x days old
 108 5. #freenode-offtopic discipline
 109 1. none at all
 110 2. same as main channel
 111 3. relaxed rules
 112 4. different rules entirely</blockquote>
 113
 114
 115 Having spent some time discussing the situation and mulled over the above channel thoughts it was decided to move forward and start working out some clearer guidelines for the new channels. The name #freenode-offtopic was also replaced by #defocus, we considered keeping the #freenode-social name but decided that it was better to start afresh and sculpt something from the ground up and so we decided to re-name.
 116 The guidelines for the two new channels are far from set in stone, and we will continuously evaluate them and we ask for your help in ensuring that we choose a set of rules which are of the most benefit to the community at large. In this regard I highly encourage you to e-mail staff at freenode dot net with any concerns, comments, questions or ideas you have. We love hearing from you and your feedback is crucial to making freenode what it is.
 117 Like Rome, #defocus won't be built in a day and we expect some fumbling while we try work out which way suits our community best. We're trying something new and we are all learning on our feet.
 118 I hope the above helped clarify some of the motivation behind #defocus and I hope that you will come join us in the channel.