#ubuntu-ops policy discussion

[John Vivirito]

On 02/01/10 09:16, Juha Siltala wrote:
> Greetings fellow IRCers,
> 
> In yesterday's IRC Council meeting[1], we discussed the item of
> #ubuntu-ops policies including 'no-idling' and +v. The no-idle policy
> generated a lengthly discussion and we decided to postpone the item
> until the next meeting and ask for community feedback.
> 
> According to the current policy, we allow no idling on the channel by
> non-operators. Users should only visit the channel when they have
> outstanding issues that require operator assistance. The purpose of this
> policy is to ensure that ops and users can work out any issues without
> spectators or intrusions by those not directly involved. It also allows
> ops to quickly recognize anyone in need of assistance by noticing that
> they are not voiced. Transparency is achieved by having channel logs[2]
> publicly available.
> 
> Some discussants were not happy with the current level of transparency,
> and offered suggestions as to how to handle an open channel:
> 
>     * allow open discussion on the channel, handle distractions on a
>       case-by-case basis
>     * allow anyone to join and idle, moderate the channel and figure out
>       a way to voice those needing voice
>     * allow interested parties or monitors to join under strict moderation
>     * two channels: issue management channel and a general discussion
>       channel
>     * two channels: the current -ops channel, and an open, moderated
>       mirror channel where all discussion on -ops is relayed
> 
> Naturally, one option is to keep the current policy, which continues to
> stand for the time being. The Council would like some feedback on
> potential benefits of opening up the channel more, and on how to achieve
> it in practice.
> 
> For a full picture, please review the meeting log. The issue is the
> first item of the meeting.
> 
> [1] http://irclogs.ubuntu.com/2010/01/31/%23ubuntu-meeting.html
> [2] http://irclogs.ubuntu.com/
> 
> Thanks for any feedback and advice,
> 
> 
So many good ideas :) ok lets try this.
1. Let the idling as a trial run. +1
2. If that fails, as it has in the past open up a channel for
lurkers example (ubuntu-ops-ot) or something along those lines.
3. To allow dealing with problems in /query can cause a lot of
problems, as they can accuse an op of something that didnt
happen when in #ubuntu-ops.
4. I think adding +m #ubuntu-ops prevents problems from being
discussed maybe as simple as it is. example (people would be
unable to join channel to discuss problems they have with ops,
they would have to pm an op)
5. As for Popey and others that are "good eggs" i dont mind
them in the channel however is it fair to have him/them in
channel and others not. I'm not real sure how to handle that
other than +v the "good eggs"?

Ok i think i hit every point but I'm sure i missed 1 or 2

I would like to add something that may be off topic from the
above.
Can we get one of the bots to log -ops only and the IRCC so we
dont have to save logs as they seem to get really really big,
just have a log site so we can easily find "problems" if the
user comes to revisit.

Sorry its so long but i was just pointing out some of the
ideas for the "idle" rule.

Thanks :)
-- 
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

"How can i get lost, if i have no where to go"
    -- Metallica from Unforgiven III

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-irc/attachments/20100201/deba21c7/attachment.pgp>