Actions

Category

Policy: Difference between revisions

From HacDC Wiki

No edit summary
 
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
This is the Policy Manual for HacDC.  This is version 0.1. All policy pages are protected and can only be modified by vote of the membership at a membership meeting.  A hard copy of the policy in effect exists at HacDC in the [[Public Inspection Locker]]
{{Obsolete}}
This is the Policy Manual for HacDC.  This is version 0.1.
 
A hard copy of the policy in effect exists at HacDC in the [[Public Inspection Locker]].


(Note:  As of 4/10/08 these pages are still being edited and discussed.)
(Note:  As of 4/10/08 these pages are still being edited and discussed.)
Line 5: Line 8:
== The Core Policy Concept : C4K ==
== The Core Policy Concept : C4K ==


Our core policy concept is '''Command, Control, Communications, ''Collaboration'', and ''Khaos'''''.  While we are very serious about following our policies, the core concept is a [[wikipedia:Tongue_in_cheek | tongue-in-cheek]] reference to the military concept of [[wikipedia:C4ISTAR | C4I]], which stands for Command, Control, Communications, Computers and Intelligence.  In following the [[:Category:Khaos Policy | Khaos policy]], you might say that we have too many Computers and not enough Intelligence, so we just left those two out for good measure.  
Our core policy concept is '''Command, Control, Communications, ''Collaboration'', and ''Khaos'''''.  While we are very serious about following our policies, the core concept is a [[wikipedia:Tongue_in_cheek | tongue-in-cheek]] reference to the military concept of [[wikipedia:C4ISTAR | C4I]], which stands for Command, Control, Communications, Computers and Intelligence.  In following the [[:Category:Khaos Policy | Khaos policy]], Collaboration and Khaos are better than Computers and Intelligence, so we swapped those last two appropriately.  


* '''[[:Category:Command Policy | Command]]''': What members and project stakeholders agree upon, in addition to compliance with law and standards of good governance.  Our [[Articles of Incorporation]], [[Bylaws]], this [[Policy Manual]] as well as relevant [[Membership Decisions]] and [[Board Decisions]], [[Standing Rules We Must Follow Because They're More Or Less Out of Our Control Anyway]], and our [[Privacy Policy]] are the basic laws we set for ourselves.
* '''[[:Category:Command Policy | Command]]''': What members and project stakeholders agree upon, in addition to compliance with law and standards of good governance.  Our [[Articles of Incorporation]], [[Bylaws]], this [[Policy Manual]] as well as relevant [[Proclamations]], the [[Resource Use Policy]], and our [[Privacy Policy]] are the basic "command" for good corporate governance and compliance as a [[wikipedia:501%28c%29#501.28c.29.283.29 | 501(c)(3)]] exempt non-profit organization.  Our meetings are governed by our home-brewed [[MIBS Simplified Rules of Coordinated Consensus through Chaos]], an effective alternative to [[wikipedia:Roberts_Rules | Robert's Rules]].


* '''[[:Category:Control Policy | Control]]''': How things get done in the most productive, transparent and honest way possible.  How are privileges and access assigned and what are the associated responsibilities?  Who is responsible for certain mission critical functions?  [[The Ministers]] are responsible for day-to-day operations and they, along with the rest of the members, are bound by the [[Access Control Policy]] and [[Financial Operations Policy]] which includes [[Fundraising]], [[Procurement]], and [[Financial Reports | Financial Reporting]].  Our meetings are governed by our home-brewed [[MIBS Simplified Rules of Coordinated Consensus through Chaos]], an effective alternative to [[wikipedia:Roberts_Rules | Robert's Rules]].
* '''[[:Category:Control Policy | Control]]''': How things get done in the most productive, transparent and honest way possible.  How are privileges and access assigned and what are the associated responsibilities?  Who is responsible for certain mission critical functions?  The members in [[Central Services]] help the organization run efficiently.  They are primarily responsible for managing things like the [[Financial Operations Policy]] which includes [[Fundraising]], [[Procurement]], [[Inventory]] and [[Financial Reports | Financial Reporting]].  They also work on [[Public Relations]].


* '''[[:Category:Communications Policy | Communications]]''': We have an obligation to [[Effective Communication#Within The Group | communicate clearly and effectively]] within HacDC as well as a duty to [[Effective Communication#With the Outside World | communicate effectively with the general public.]] This policy outlines the technical structure of our communications systems as well as [[Effective Communication | guidelines for communicating effectively]] as a whole.
* '''[[:Category:Communications Policy | Communications]]''': We have an obligation to [[Effective Communication#Within The Group | communicate clearly and effectively]] within HacDC as well as a duty to [[Effective Communication#With the Outside World | communicate effectively with the general public.]] This policy outlines the technical structure of our communications systems as well as [[Effective Communication | guidelines for communicating effectively]] as a whole.

Latest revision as of 03:18, 3 April 2012

Information on this page is Obsolete; it is preserved for historical interest

This is the Policy Manual for HacDC. This is version 0.1.

A hard copy of the policy in effect exists at HacDC in the Public Inspection Locker.

(Note: As of 4/10/08 these pages are still being edited and discussed.)

The Core Policy Concept : C4K

Our core policy concept is Command, Control, Communications, Collaboration, and Khaos. While we are very serious about following our policies, the core concept is a tongue-in-cheek reference to the military concept of C4I, which stands for Command, Control, Communications, Computers and Intelligence. In following the Khaos policy, Collaboration and Khaos are better than Computers and Intelligence, so we swapped those last two appropriately.

  • Collaboration: We are here to collaborate. In one word, it is what we do. In serving charitable, educational and scientific purposes, our five point mission statement says that HacDC:
  1. Build and maintain spaces suitable for technical and social collaboration
  2. Collaborate on all forms of technology, culture and craft in new and interesting ways
  3. Apply the results of its work to specific cultural, charitable and scientific causes
  4. Freely share its research and discoveries, using what is learned to teach others (which is why we follow a very liberal Licensing Policy)
  5. Recruit and develop talented members dedicated to these purposes
  • Khaos: Let's not take ourselves too seriously. Respect the MIBS and the MIBS will respect and nourish you. Khaos is also the designated graffiti wall on our wiki.

This category currently contains no pages or media.