Rule(s)

  • 7.1 Appointments to working groups, task forces and other bodies related to ICANN may be filled by approval of the Committee; 
  • 7.2 Such appointments shall normally be done through an informal call for volunteers, posted by the Chair to the public ALAC list, allowing at least 7 (seven) days for people to volunteer, and trying to reach consensus on the appointment. However, in case that consensus cannot be reached, or in case that this is requested by at least 3 (three) ALAC members, the Chair will start a formal election procedure as set forth in rule 10.
  • 7.3 The election can take place by electronic mail, online balloting, written balloting, or any other means deemed convenient and accurate 
  • 7.4 All appointments will require reaffirmation or (reassignment if appropriate) at the Annual General Meeting Following their appointment. 
  • 7.5 Appointments shall be freely chosen by the ALAC, according to the following criteria: 
  • 7.6 They shall accept to serve on behalf of the At-Large Community by acting for the good of the entire Committee, working to bridge differences and build consensus, but also recognizing difference and enabling different opinions to be shared; 
  • 7.7 They shall accept, while acting in their capacity as an ALAC representative, to put the collective views of the Committee always in front of their own.

Proposed Changes

Rationale 

Next Steps

  • No labels

2 Comments

  1. 7.4 seems to be overkill given that the Rule applies to all sorts of appointments. If we keep it, iwe better start keeping better records.

    7.7 should have same caveats that I suggested for Liaisons.

  2. We must put in a rule to allow the ALAC to reject candidates, as in the case of one (1) candidate.  The ALAC must have the right to pass over a candidate if it deems that candidate unsatisfactory or incapable of doing the work assigned. 

    The ALAC should try it utmost to approve a candidate by consensus. Polling should be used as a last resort