Constitution

Essentially, to become a real club, we need some sort of constitution, so this document is the discussion space for forming the constitution.

Below are the currently proposed groups and roles for the club: ¹⁾

• Purpose: to oversee the operations of the club and keep it running smoothly
• Composed of: Zealots, aka Officers

• Politics (constitution, elections, positions)
• Vision, Spirit
• oversees operation of club
• fills in the gaps

• Peon Training, Organizes Presentations
• sets up and manages utilities (bug tracker, etc.)
• makes everything run smoothly within the group

• Sponsors + Funding + Food + Resources
• handles club money, its approval, the banking information
• seeks out new sources of funding, writes application
• manages budget for food, hardware, software, online subscriptions, etc.

• Meetings + Announcements, via email + other forms
• Public Facing Website
• Wiki cleaning
• Marketing
• sends out email reminders
• sets up time/place for sessions
• manages club emails
• communicates with other clubs, re: support and setup of sites
• promoting documentation and acquiring resources + managing the doc section of wiki

• Purpose: to keep projects alive and on track
• Composed of: Heads (or Leads, Gurus), aka Project Leads / Lead Developers

• Purpose: come to sessions, contribute code, etc.
• Composed of: Peons (or Drones, Acolytes, Code Monkeys), aka Active Members/Developers

Any suggestions?

Ex.

• announce positions in April
• applications due late April, posted on wiki
• applicants must be an active member (see def below)
• short speeches and vote during a session in May
• every active member (see def below) has 1 vote, exec council members have 5 votes each, project leads have 3 votes each
• summer is transition period

“Active Member”

• a student that meets any of the following requirements:
  • has attended at least 4 dev sessions within the last 6 months
  • has made at least 4 commits to a web-dev project within the last 6 months
  • has made at least 4 contributions to the web-dev wiki within the last 6 months
• above requirements are at the discretion of the President
  • (ex. if someone makes 4 pointless edits to wiki, for the sake of having four edits, the President can disqualify the 'active member' status)

(see CESA Constitution (PDF) as a reference)

• The Club
  • Goals
  • What We Do
• General Membership
  • Eligibility
  • Privileges
• Active Members
  • Eligibility
  • Privileges
• Executive Committee
  • Eligibility
  • Privileges
  • Roles & Functions
  • Session
• Meetings / Dev Sessions
• Elections
• Finances
• Amendment

Should include following in Constitution:

• our dedication to contributing to skule
• cooperation w/ webmaster + sysadmin
• cooperation w/ startup web society

Other Notes

• limitations on roles
  • a single member cannot have more than one upper echelon position
  • a single member can be the lead for up to 3 (?) projects
    • an upper echelon position 'counts' as one of these 3 projects