From HacDC Wiki
|Information on this page needs to be revised; it may not reflect the current situation or policies at HacDC|
Our general communications policy is simple:
- Pick a system that works to facilitate communication
- Use it
- Don't change it unless it's failing.
E-mail is the most common method of communication within HacDC and between HacDC and the outside world.
Public E-mail Lists
Our public lists, which anyone can sign up for, are:
- firstname.lastname@example.org : A moderated, weekly update list designed to keep the general public informed about what's happening, what's been discussed and what's coming up at HacDC.
- email@example.com : Our completely unmoderated and public open discussion forum covering a wide range of topics and questions.
Public POC E-mail
All inquiries from the outside world, via e-mail, should go to firstname.lastname@example.org.
email@example.com may be used within the web page, wiki, on documents, flyers, etc. as a way for those outside HacDC to contact the organization.
Internal/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.
Internal E-mail Lists/Accounts
|E-mail address||Purpose||List Members||Archived by|
|firstname.lastname@example.org||A discussion forum for the HacDC Advisory Council, where HacDC solicits advice and council.||Advisory Council, Members||Mailman|
|email@example.com||Contact list for the Board of Directors||The Board of Directors||Mailman|
|firstname.lastname@example.org||E-mail account for all things relating to HacDC Finances||The Minister of Finance||Archived E-Mail (7 year retention cycle)|
|email@example.com||Open, unmoderated discussion for HacDC Voting and Non-Voting (i.e. Honorary) Members||The Members, Honorary Members||Mailman|
|firstname.lastname@example.org||Moderated, essential traffic for members. Primary distribution method for weekly members update, meeting minutes and agendas and emergencies.||The Members, Honorary Members||Mailman|
|email@example.com||Primary contact address for the administrators of HacDC, designed for use by members to address specific concerns and by ministers to keep each other updated on minor administrative action.||The Ministers, Shadow Ministers||Mailman|
|firstname.lastname@example.org||Primary contact list for the PR team of HacDC, designed to help members and associates get events publicised via HacDC's public e-mail lists, blog, twitter, email@example.com||Mailman|
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 bod@ 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?|
|multi-touch-int-display@||(None)||Discussion list for the HacDC Multi-touch device Project.||Mailman via hacdc.org||Yes|
|museum@||(None)||Discussion list for the HacDC Museum Project.||Mailman via hacdc.org||Yes|
|neighborhoodwireless@||(None)||Discussion list for the Columbia Heights Wireless Project.||Mailman via hacdc.org||Yes|
|smartclothing@||(None)||Discussion list for the Smart Clothing Project.||Mailman via hacdc.org||Yes|
|micromondays@||(None)||Discussion list for the Microcontroller Course||Mailman via hacdc.org||Yes|
|reddoor@||(None)||Discussion list for the Door Entry Project||Mailman via hacdc.org||Yes|
Our main website is run on Drupal and functions primarily as a blog.
Our wiki is run on MediaWiki. You're most likely reading it now.
Our twitter is hacdc.
Our Livejournal is hacdc.
Our meetup is hacdc.
Our Phone number is (202) 556-4225 (556-HACK).
Projects whose communities rely on IRC are encouraged to start their own IRC channels or actively participate in existing channels - we have control of the entire #hacdc-* namespace, if sub-channels are needed.