From HacDC Wiki
This policy is meant to clarify how communications are handled at HacDC. We have an obligation to:
- Collaborate clearly and effectively within HacDC.
- Communicate effectively with the general public.
This policy outlines the various methods of communication necessary to facilitate the mission of HacDC.
E-mail is the front line of contact between HacDC and the outside world. It is also how most contact happens within the organization. The communications policy spells out how e-mail is to be used by HacDC for maximum effectiveness and mibs.
Member E-mail Addresses/Aliases
Each member is entitled to an @hacdc.org e-mail account. HacDC shall offer hosting for @hacdc.org e-mail accounts or offer the option of forwarding to the member's chosen e-mail address. Member e-mail shall not be archived, except as chosen by the member in a hosted e-mail account.
Ministerial E-Mail Addresses
These are rotating e-mail addresses forwarding to those currently holding the relevant title. They are subscribed by default to the appropriate internal organizational lists, allowing for easier changeover of positions.
|E-mail address||Aliases||Member||Currently Forwarding To|
|email@example.com||(None)||Coordinator in Chief||User:Q|
|firstname.lastname@example.org||(None)||Keeper of the MIBS||UNASSIGNED|
|email@example.com||(None)||Minister of Finance||User:nickfarr|
|firstname.lastname@example.org||(None)||Keeper of the MIBS||User:allirense|
|email@example.com||(None)||At Large Director 1||User:thomascrown|
|firstname.lastname@example.org||(None)||At Large Director 2||User:1057|
Internal E-mail Addresses
These addresses are the internal contact addresses within HacDC. They are not necessarily private, though we should encourage the public to contact us through one of the organizational e-mail addresses.
|E-mail address||Aliases||Group/Person Served||List Members||Archived by|
|email@example.com||theministers, officers, command, thanklessjob||The Ministersfirstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com||Mailman|
|firstname.lastname@example.org||theboard, ministersplustwo||The Board of Directorsemail@example.com, firstname.lastname@example.org, email@example.com||Mailman|
|firstname.lastname@example.org||(None)||The Members||The Members||Mailman|
|email@example.com||(None)||Advisory Council||Any person appointed by a Member||Mailman|
Organizational Contact E-mail Addresses
These are e-mail addresses that are public. They may be used within the web page, wiki, on documents, flyers, etc. as a way for people to contact members serving that particular function. Each generic list should also have an archival function associated with it, either an archive e-mail address or a web archive available only to members of the list.
Replies shall be handled by members from whatever e-mail address they choose to reply from. However, all replies must cc: the original contact list.
The following are the current OC e-mail addresses
|E-mail address||Aliases||General Purpose||Primary Contact||List Members||Archived by|
|firstname.lastname@example.org||press, help, abuse, *||General inquiries and contact, catch-all||Coordinator in Chief||The Ministers||Mailman|
|email@example.com||www, blog, wordpress||Web page design, inquiries, WordPress administrative requests||Minister of Information||Web Team||Mailman|
|firstname.lastname@example.org||mediawiki||Wiki inquiries, help, administrative requests||Minister of Information||Wiki Team||Mailman|
|email@example.com||irs, dcra, dmca, theman||Corporate paperwork, things we really cannot let slip by the wayside||Keeper of the Mibs||The Ministers||Mailman|
Static Organization E-mail Address
Static contact e-mail addresses should be used very sparingly for a particular justified purpose. These are actual e-mail accounts @hacdc.org. Only a relevant Minister should have access to each account.
Each key should only be considered valid if it is signed by the master HacDC GPG Key
|E-mail address||Aliases||General Purpose||Primary Contact||Key ID||Justification|
|firstname.lastname@example.org||paypal, donations, fundraising||Everything dealing directly with money||Minister of Finance||NO KEY YET||Financial transactions and details should not be sent to a list|
|email@example.com||gpg, pgp||Anyone who wishes to securely communicate with HacDC||Coordinator in Chief||NO KEY YET||Secure communications to be re-wrapped and sent by HacDC, Address associated with HacDC GPG key and other certificates|
Project Contact E-Mail Addresses
Each ongoing project must have an e-mail address associated with it. The e-mail address may be an alias for the project coordinator, a discussion list for the project as a whole or an alias to info@ so The Ministers may be able to send project inquiries to the correct relevant parties. In any case, the status of each project contact e-mail must be documented here:
|E-mail address||Aliases||General Purpose||Delivery Mechanism||Archived?|
|columbiaheightswifi@||(None)||Discussion list for the Columbia Heights Wireless Project.||Mailman via hacdc.org||Yes|
Web (Static Content)
Web (Dynamic Content)
IRC is another method of communication for HacDC. It is a great way to keep in touch or have meetings with groups of people separated by distances.
Members of HacDC (and a few Friends of HacDC) maintain the IRC channel #hacdc at freenode.org. This is the officially recognized channel where The Ministers and/or designates are expected to provide information on HacDC and discuss HacDC projects and activities.
Projects whose communities rely on IRC are encouraged to start their own IRC channels or actively participate in existing channels.
This category currently contains no pages or media.