Definition of a "core op"

[Terence Simpson]

Hello everyone,

A few months ago it was agreed, by the IRC Council, that there should be 
a group of operators known as "core" operators, and these operators 
would have op access to all core channels. The point being that if no 
channel-operator was available to deal with a channel issue, a 
core-operator could step in and take control. These ops would generally 
only use their +o when no channel-specific ops available. You can think 
of them as "senior" operators.

The IRC Council has mostly left this idea on the back-burner for several 
months, but due to a recent conversation in #ubuntu-ops we have been 
motivated to reignite this discussion. So we would very much appreciate 
your ideas and opinions on this.

What we need is a set of requirements that define who can be a core-op. 
We already have the process for deciding who can be an operator in a 
core channel, now we need something similar for defining who can be made 
core. Currently all we have is the requirement: "Must already be an 
operator in a core channel", but we need some other requirements.

To be clear, we aren't deciding if this is a good idea or not, just what 
requirements must be met to be considered for core ;)

So if you have any ideas you can add them to the wiki[1] and discuss 
them on the list.

[1] https://wiki.ubuntu.com/IRC/IrcTeam/DefiningCoreOps

--
Thanks on behalf of the IRC Council,
Terence Simpson (tsimpson)