Policy Development

When a new policy is proposed, we should [put its text on a new page]. It should be clearly labeled as a PROPOSAL. Discussion about the proposal should take place in the discussion link for that page. From time to time a rough consensus will be formed around various points in the proposal and at that time the main page should be altered. This allows us to separate the general conversion (ideas that we talk about but may not end up in the proposal) from the actual proposal we end up making.

We need to keep in mind that folks who don't use the wiki will have opinions. These people should be encouraged to use the wiki, but current wiki users should also seek out and summarize their input, recognizing that not everyone who ought to weigh in on an issue will be a wiki user.

When a policy is finalized (when consensus is reached through the wiki, email lists, face to face meetings, and so on) we should re-label the main page as POLICY (as opposed to PROPOSAL). Using the category function in the wiki will make compiled lists of proposals and policies automatic.

Proposal and Policy Repository

This is our policy repository. Ideally when a proposal is made, a policy agreed upon, or an old policy unearthed, it should go here. Several Free Geek policies are currently buried in old meeting minutes, or completely unrecorded. Feel free to scour old minutes by browsing the archives of the various email lists at http://lists.freegeek.org/listinfo/ and posting newly discovered policies below.

Policies (Agreed Upon)

• Hiring Policy April 16, 2003
• Asking for Vacation Policy April 16, 2004
• Determining Seniority Policy April 16, 2004
• Paid Internship Policy May 21, 2004
• Room Use Policy May, 2004
• Volunteer Discipline Policy May, 2004
• Volunteer Ebay Sales Policy July, 2004
• Staff Contracting Policy August, 2004

Proposals (Not Yet Agreed Upon)

• Wifi Use Statement -- A policy statement in development: explaining our decision process about using wifi at Free Geek.