]> jfr.im git - irc/freenode/web-7.0.git/blame - content/news/2007-05-15-all-roads-lead-to-defocus.markdown
Clumsy sed fixed...
[irc/freenode/web-7.0.git] / content / news / 2007-05-15-all-roads-lead-to-defocus.markdown
CommitLineData
271fb63d
SB
1author: christel
2date: 2007-05-15 03:49:56+00:00
3slug: all-roads-lead-to-defocus
4title: 'All roads lead to #defocus'
d7dd9d5b 5---
271fb63d
SB
6
7Some 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
9This past week the phrase has played on my mind a lot, in regards to our changes to the official freenode help and social channels.
10
11We 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.
12
13I 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.
14
15
16<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.
17
18We (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.
19
20The 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.
21
221. 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.)
231. No defined topic (so no way to say: "that's offtopic")
242. No defined rules
253. Lack of regular chanops (we got scared and ran away)
264. Chanop behaviour is sporadic and hard to predict
275. Voicing/devoicing system has holes
281. Voicing is random. This can cause various behaviors:
291. People want to capture voice and hold it forever, against the time they might want to speak
302. When someone has waited hours to be voiced, (s)he may already be quite frustrated
313. By the time you're voiced, you forgot why you came
322. We can't remember why a person was devoiced
333. Access list too long to meaningfully evaluate
344. 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.
356. We used to say 'be a catalyst in #freenode-social and maybe we'll ask you to be staff someday' ... is that still true?
362. Some scenarios for the new #freenode channel (things people will come to say). ?? Categorize as (O)OK, (N)Not OK, (P)Private ??
371. Nick issues
381. Help me register my nick
392. Cloak me!
403. Someone took my nick
414. Lost my password
425. Help me admin my nick options
432. Client issues
441. Help me with my client
452. How does $somecommand work?
463. Cannot connect to freenode
473. Channel issues
481. I need help with my channel registration, modes, etc
492. They banned me in #foo!
503. #foo is offtopic/offensive/criminal/other, whatcha gonna do about it?
514. #foo has mean chanops
525. We are having a disagreement in #foo, please come and mediate
536. Explain primary/about channels for me again?
547. Does #foochannel exist?
558. Everybody come to #foo, it is the ubar-greatest!
564. About individuals
571. $somenick is PMing me and I don't like it
582. $somenick is spamming/trolling/racist remarks/other on #foo
593. $somenick is spamming/trolling/racist remarks/other on several channels
604. $somenick is an asshole, kline him now
615. $somenick's nick offends me
626. My friend $somenick was klined, remove it already!
635. Group issues
641. GCF approvals
652. Explain groups to me
663. I'm a GC and I need something done
674. Who is the GCF for $somegroup
685. $somegroup has no right to exist, we are the rightful owners of that group name
696. Freenode issues
701. $somestaffer treated me unfairly
712. I want to be a staffer
723. Teach me to be a catalyst
734. Announcements by staff
745. Donation issues
756. I want to host a freenode server
767. This wierd thing just happened, is it a network issue, help!
778. Help me understand the Freenode policy about $whatever.
789. I disagree with Freenode policy
7910. Freenode should do this wonderful thing _______!
8011. Freenode should endorse my campaign to save the world
8112. I hate Freenode, rant-rant-rant.
8213. I love Freenode, love-love-love.
837. Other
841. I need help with something not in 1-6 above
852. Let's talk about my life issues/problems/whatever.
863. My political/religious/societal views
874. spam
885. random invective
896. http://somelink is funny/offensive/interesting/whatever, let's all talk abut it
907. well, all sorts of stuff not found in 1-6 above
913. Escalating help. We all have different freenode-admin privs; some of us have none other than 'helpful person'.
921. 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"
932. Try to identify things that should happen privately (in PM) and move there as soon as possible.
943. If you haven't the privs to resolve an issue, send them to /stats p or /who *freenode/staff* asap
954. Suggestions?
964. #freenode discipline
971. What do we discipline for?
981. Offtopic
992. Tone/attitude
1001. Ontopic but rude
1012. Note- how to handle "I was not being rude, I was joking!"
1023. Personal attacks/characterizations/judgements. (Suggest: we simply avoid all observations of a personal matter)
1034. Giving out bad advice on the channel. Again, the issue of "I was joking" should be addressed.
1042. Possible discipline escalations:
1051. Catalyze in-channel, never ban or mute
1062. Catalyze in-channel, ban or mute after x lines or minutes if it doesn't work
1073. Mute immediately and catalyze in PM; unmute when they understand
1084. Ban/mute for x minutes on first offense, y minutes on second offense, z minutes on third offense
1095. Replace ban/mute with redirec to #freenode-offtopic; perform all catalyzation in there
1106. Some combination of the above
1113. How to handle leftover bans/mutes?
1121. leave forever since no one wants to override another chanop's actions
1132. periodically flush any ban/mute more than x days old
1145. #freenode-offtopic discipline
1151. none at all
1162. same as main channel
1173. relaxed rules
1184. different rules entirely</blockquote>
119
120
121Having 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.
122
123The 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.
124
125Like 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.
126
127I hope the above helped clarify some of the motivation behind #defocus and I hope that you will come join us in the channel.