Proposed Ubuntu-au Structure(s) Summary

1. Current Model: Meritocracy

• Loco Contact: Manages LoCo Assets & assigns roles

• Web Master: Looks after the website.

Election Process: Appointed

PRO's

• Great for starting a LOCO
• Controls tightly LOCO assets

CON's

• Process not transparent
• Breadth of talent is limited

2. Conventional Committee Model: Democratic

• Chairperson: Chairs meetings (driving discussion & Decisions)

• President: Serves as 'Loco Contact'
• Vice-President: Assists President
• Ordinary Members (4-6)

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

PRO's

• Creates a process, with public responsibilities

CON's

• Elections & politicisation

3. Australian Community Council (ACC) Model (Ideally 7 +- 2 people) :Democratic

• Chair Person: 'Loco Contact' allocates Asset access in consultation with ACC.

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

• Webmaster: Looks after the website.

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

• Representatives: State/City/Regional representatives, make national decisions. (see 3A & 3B) Role Details here

Elections: Each representative is 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

• Decision making process easier ie. 8 instead of 40 in an IRC meeting
• Group leadership Team
• Country wide co-ordination

CON's

• Election process & politicisation

• A structure

3A. Local City/Region Representative Model

• Each City/Region LoCo elects/appoints a representative to the ACC.

• Its members would represent a City or Region.
  • e.g. Brisbane, Sydney, Cairns, Northern Rivers, Mt Isa, Western QLD etc.
• Roles: As per description in Model 3.

Advantages

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

Disadvantages

• Election/Appointment Process

3B. State Council Representative Model

• A 'State council' would be created when there are 5 or more city/Regional representatives (in One state) on the ACC.
• Cities/Regions would then elect/appoint representatives to the 'State council' rather than the ACC.
• A state representative, would then be appointed/elected to represent their respective state in the ACC.
• Roles: 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
• Reduces the size of the ACC.

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 "State councils" are created)

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/City/Region appoints/elects a representative (if more than one nomination).
  • Can be done using an online poll or a local meeting. Only City/Regional/State members eligible to vote. Each City/Region will keep their own 'official' membership list.
• Web Master appointed by council members, in consultation with Ubuntu-au Team Contact.

(Note: A Detailed Roles for model 3 & 3A & 3B can be found here)