Proposed Ubuntu-au Council structure

1. Current Model: Meritocracy

• Loco Contact
• Web Master

Election Process: Appointed

PRO's

• Great for starting a LOCO
• Controls tightly LOCO assets

CON's

• Process not transparent
• Breadth of talent is limited
• Open to accusations of abuse

2. Normal Model: Democratic

• Chairperson
• President (Loco contact)
• Vice-President Treasurer
• Ordinary Members (4-6)

Election: General (Annual or Bi-annual) Election by all Ubuntu-au Members

ChairPerson

• Chairs Council meetings (Driving discussion and decisions)
• Calls Ubuntu-Au elections
• Ensures that rules and processes put in place are adhered to

President/Vice President

President

• Serves as the Role of Team Contact for Ubuntu-AU

Vice-President

• Assists President

• Maintains records of LoCo membership where necessary

PRO's

• Creates a process, with public responsibilities

CON's

• Elections & politicisation

3. Representative Model (Ideally 7 +- 2 people) :Democratic

Chair Person (Loco Contact)

• Chairs Council meetings (Driving discussion and decisions)
• Chairs General meetings (Driving discussion and decisions)
• Calls Ubuntu-Au elections
• Liaises with Ubuntu-CC
• Allocates people access to resources (In consultation with Ubuntu-Au council members)
  • eg. Website Admin, List moderators, IRC Ops.
• Ensures that rules and processes put in place are adhered to

Election: Is reviewed yearly and appointed by Ubuntu-CC (with recommendation from outgoing contact person)

Web Master

• Responsible for setting up and maintaining the website(s)
• Website contact
• Reports to Ubuntu-au council
• Seeks approval to change website(s) structure (conducts reviews)
• Seeks approval to grant members restricted access to website(s)

Elections: Elected (Annually) by Council Members, Nominations from Members.

Representative

• State/city/region contact person (see model 'A' or Model 'B')

• Liaises with LUGS & other organisations

• Drives goals of Ubuntu-au at a local level

• Provides advice & support, to individuals and regional ubuntu groups.

• Raises issues (sets agenda items) with the Ubuntu-au Council at Council meetings.
• Reports back to Ubuntu-au Council on progress of said goals/functions etc.
• Drives Important events/functions i.e. Release parties
• Helps with website 'News/Announcement' items
• Chairs General Ubuntu-au Meetings (when needed)
• Chairs State Ubuntu-au Meetings (when needed)
• Helps with Elections
• Has official status within ubuntu-au and as such represents Ubuntu-au LOCO

Elections: Each representative elected/appointed by Ubuntu members in each corresponding state/city/region. (Seats are to remain open if no-nominations have been received. Chair person to assume responsibility)

Other positions

• Marketing - Media - Publicity
• Junior contact (Under the age of 18)

Elections: Elected or appointed by 'Ubuntu-au Council'

PRO's

• Gives each State/Region/City a voice in the direction of the community
• Delegates responsibility
• A local contact person

• Open & Transparent process

CON's

• Election process & politicisation

• A structure

A. Local City/Region Representative Model

• Each City/Region elects/appoints a representative to the Ubuntu-Au council
• Its members would represent a city or Region.
  • e.g. Brisbane, Townsville, Cairns, Toowomba, Mt Isa, Western QLD etc.
    • Sydney, Newcastle, Northern Rivers, Dubbo etc.
• Role: As per description in Model 3.

Advantages

• City/Regions have a direct representation on the 'ubuntu-au council'
• Cuts out a 'State council' B. Model
• Each member in the City/Region has a say in appointing/electing representative.

Disadvantages

• Election/Appointment Process

B. State council Representative Model

• This model would be used in conjunction with model 3A. except Regions/Cities would elect/appoint representatives to the 'State council' rather than the 'Ubuntu-au council'
• A state representative, could then be appointed/elected to represent their respective state in the 'Ubuntu-au

council'.

• A 'State council' would be created when there are 5 or more city/Regional representatives on the 'Ubuntu-au council'
• Role: As per Description on Model 3.

Advantages

• Each state is responsible for appointment/Election of the ubuntu-au council representative for the ubuntu-au council
• Could be useful if Model 3A. is selected and the ubuntu-au council becomes too large.

Disadvantages

• Another structural layer

Meetings

• Ubuntu-au Council- At least every 3 months, more if urgent issues arise. Quorum: 50% of Council members + 1

• Ubuntu-au General- Once a Month, if agenda items are posted. Quorum: # of Council members + 1

• Ubuntu-au State- Once a Month, if agenda items are posted. (Only required if model B is selected)

Notices are to be posted to email lists, Wiki and ubuntu.com.au and Facebook.

Election Process

Ubuntu-au Council

• Notice to members, Email Lists, Wiki, ubuntu.org.au, Facebook.

• Nominations called & displayed on ubuntu.org.au, All positions.

• Each state conducts an online poll to elect rep (if more than one nomination). Only State members eligible to vote. Each state shall maintain its own 'official' membership list.
• Web Master appointed by council members, in consultation with Ubuntu-au Contact