IRCCouncil

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2009-11-17 17:54:33 →
Size: 1075
Editor: 63
Comment:
← Revision 2 as of 2009-11-23 06:18:52 → ⇥
Size: 2420
Editor: c-67-164-44-209
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
  * Review the Operator Guidelines to ensure that they are accurate (Benjamin).
   *
   * Ops should be able to govern all channels to the same level of expectation?
Line 22: Line 25:

 * '''OBJECTIVE''': Prune channel access lists
 * '''SUCCESS CRITERIA''': There is an access list that contains active and trusted operators
 * '''ACTIONS''':
  * Pull channel access lists from core channels and put into LP team with expiry dates
   * Determine the work required to do this in an automated way (Jussi)
   * Implement the feature (Terence and Ben)
  * File a bug against LP for expiry email custom content
 * '''BLUEPRINT''': https://blueprints.edge.launchpad.net/bantrackertwo/+spec/import-access-list-into-launchpad
 * '''DRIVER''': Benjamin Rubin.
 * Please clarify "expiry dates". Operator should be able to renew in the same way as Ubuntu Membership by clicking a button, no formal process. ~ PriceChild


 * '''OBJECTIVE''': Membership Approval
 * '''SUCCESS CRITERIA''': Well-documented process for Ubuntu IRC Membership
  * Short backlog of applicants
 * '''ACTIONS''': Document IRC-specific requirements for Ubuntu Membership
  * create ~ubuntu-irc-members team
  * document process at https://wiki.ubuntu.com/Membership
 * '''BLUEPRINT''': <link>
 * '''DRIVER''': Benjamin Rubin, Jussi Schultink (Daniel Holbach can help out)

Ubuntu IRC Council Roadmap

  • OBJECTIVE: Document the operator assessment process

  • SUCCESS CRITERIA: Document an agreed-upon process that outlines how the IRC Council evaluates an Operator.

  • ACTIONS:

    • Review the Operator Guidelines to ensure that they are accurate (Benjamin).
      • Ops should be able to govern all channels to the same level of expectation?
    • Work with Benjamin to assess the elements involved in the assessment (Jussi).
    • Document these elements on the Ubuntu wiki (Jussi).
    • File a bug for this document not existing and assign to the IRC Council (Benjamin).
    • Community Council offers input on this document (Daniel Holbach).

  • BLUEPRINT: <link>

  • DRIVER:

  • OBJECTIVE: Community Council assist the IRC Council in developing a application process for Operators.

  • SUCCESS CRITERIA: A completed and well-documented application process.

  • ACTIONS:

    • Gather requirements for good operator best practice from the IRCC (Jussi and Benjamin).
    • Develop a recommended set of requirements for operators (Jussi).
    • Have the CC offer input on the document (Full Community Council).

  • BLUEPRINT: <link>

  • DRIVER:

  • OBJECTIVE: Prune channel access lists

  • SUCCESS CRITERIA: There is an access list that contains active and trusted operators

  • ACTIONS:

    • Pull channel access lists from core channels and put into LP team with expiry dates
      • Determine the work required to do this in an automated way (Jussi)
      • Implement the feature (Terence and Ben)
    • File a bug against LP for expiry email custom content

  • BLUEPRINT: https://blueprints.edge.launchpad.net/bantrackertwo/+spec/import-access-list-into-launchpad

  • DRIVER: Benjamin Rubin.

  • Please clarify "expiry dates". Operator should be able to renew in the same way as Ubuntu Membership by clicking a button, no formal process. ~ PriceChild

  • OBJECTIVE: Membership Approval

  • SUCCESS CRITERIA: Well-documented process for Ubuntu IRC Membership

    • Short backlog of applicants

  • ACTIONS: Document IRC-specific requirements for Ubuntu Membership

  • BLUEPRINT: <link>

  • DRIVER: Benjamin Rubin, Jussi Schultink (Daniel Holbach can help out)

Roadmaps/Lucid/IRCCouncil (last edited 2009-11-24 00:08:25 by c-67-164-44-209)