More nuts and bolts
More nuts and bolts [UPDATED 06-07-12 CHANGED EMAIL GROUP IDEA TO GOOGLE GROUP]
Basically I envision the system working with 5 basic documents. One is the contact list which should include at a minimum name, email, city and state. County, phone, and other data could be added but I'd say it doesn't really matter at the initial stage. Two is a organizational document explaining what the project is and how to participate. A basic instruction manual on what we're doing/trying to do and how to participate. Three is a "map". This would be THE go to document for supporters to find out all the information they'd want/need to know for what's happening, who's who and where to participate and discuss. Four is an archive document of all the emails that have been blasted out to supporters. Five is a log book of who is doing what and will be internal to the committees to basically record rep and will be used to replace people in the committees who are inactive.
The committees
The whole thing will hinge on the committee. It will be the basic unit of the organization and eventually each geographic area will have a committee. At first we just need one national committee of say 10 or so people. These people should be "web warriors" in that all they really do is maintain the above mentioned web documents, answer emails, and email supporters summaries of what's happening locally/currently. It would simply be a google group (mailing list). Whenever someone wants to join the list they email the committee. When someone wants to promote a project they email the committee. When an email needs to be propagated out to supporters someone in the committee uses the contact list and sends it out.
So you want to join the list, you email the committee. Someone on the group replys to all "i got this" that person updates the contact list and sends a "done" email to the group after responding to the original supporter and the item is deleted. Same for a project, someone from the committee updates the "map" and after its handled and supporter is notified item is deleted.
[ADDED 06/07/12] This scenario can easily be done using a google group. The committee sets up a google group and invites committee members to join. Only can join the group via invite. All the posts remain private but anyone can email the group (using the groups email address) and create the post/action item. Committee members take responsibility for an item with an "i got it" post after making sure they are the only one handling that item (see logbook description below). Having this group makes it to where the supporter can be assured that someone is handling their item and that it will be handled quickly.
In Gmail this could be structured as follows: Someone from the committee has an alias email address that supporters email, say [email protected]. That's the email supporters use. That address has a filter that forwards to all members of the group. Members of the group take responsibility for the item by a "I got it" reply all email and a follow up one after the task is complete. In this way there's redundancy and the supporter can be assured that someone will take action. When you just email one person they may be away for however long and the feedback loop might be too long.
The map
There needs to be one central document where all the important info can be recorded and linked to. This document could be a google doc that all members of the committee can update. Things could be broken down as header info and events/projects/people/information broken down by area. Header info would be links to the organizational document, and would have links to drill down to other map documents for specific areas maintained by respective local committees. The header would also have the email addresses for the committees so members know where to send information to. The body of the document would be project/event/people/information SUMMARIES, not all the information. The summaries should simply state date, status, description, and a link to a forum or other website/network where the details can be found. When too many projects exist and are outdated or inactive they can be archived (link to archives on map doc).
Email and email archive and contact list
The actual emails sent to supporters should include actionable items that are important and current. It's the committees job to view the map and pick out things that are actionable/notable, perhaps some brief descriptions of local news items (but limit this) and meta-info about how this project is going, how many members/committees etc. All these emails should be recorded in an archive document so supporters can play catch up and view info that might be outside their area. Again, SUMMARIES and LINKS, not giant emails describing everything, let the supporter decide what they want to drill down to. When supporters are actually to be emailed someone from the committee takes responsibility and imports (this is Gmail way) the list into a contact group and then sends it, simple to do. Doesn't have to be the same person every time it's not difficult importing emails into a group in gmail.
Organization document
Like I said this is just the advertising and instructional manual for this project. This task I'm going to spearhead. I'll be on the national committee and people with feedback or improvement ideas can email the committee and then the doc can be updated/expanded.
The logbook
Committees should all have a logbook where they can update how much time they've spent doing work in say a weeks time. This will be a good barometer to know who is doing what and inactive committee members can be replaced. Nothing personal but to be on the committee means to do work, if you don't have time for that someone who does needs to be in your place.
[Added 06/7/12] Another function of the logbook is to make sure tasks aren't being duplicated by committee members. Before a committee member begins a task they enter it into the logbook (date, senders email, subject). Since it's a shared doc the committee member will know/see if someone else is trying to do the same task, only when you're sure you're the only one handling it will you send out the "got it" email.
Projects and links
It's important to point out that the committees and their members are NOT project organizers. They are informational and communication agents. If you or someone else has a project they should notify the committee to get it part of the map. The map should link to say a forum post. That forum post should have contacts listed for that project organizer/coordinator. It's the committees job to propagate info about events and projects that are taking place NOT TO HANDLE RSVPS.
It's my feeling that all these projects and event info should link to discussion boards. Even if its an election campaign. Let the discussion board link to more drilled down info like the candidates website, who to RSVP, etc. This way from receiving an email about a project users are only 2 or 3 clicks away from participating and discussing and aren't blasted with a page worth of text via an email. For important events/projects it probably would be good to send the email to RSVP to with the summary as many people (who use their phone for email) might want to get involved but don't have direct access to the web.
Going forward
Like I said, initially just one national committee, I think 10 or so people could handle a significant amount of information and when it becomes too much we split it off into regions at first and then state by state. The map document is the hub though for linking and directing people to the right address to send the info and join the list.
This is the basic outline I see, it's achievable and simple enough for everyone to see how it works. We don't need a "leader" or a president or a corporation. We do however need people to do the work. I see a lot of potential for all us web warriors to make up these committees considering how much effort we expend online doing very little in the direction of liberty. I'm working on cleaning up the documentation and ironing out the details (still a work in progress) but I think this is the path we need to take so I'm trying to stay focused and committed long term.
I'm going to form this initial committee and when I get the documentation together and an initial list of volunteers who are willing to spend a few hours a week working on this and get the documents shared and put up, I'm going to go more hardcore into pushing it out and asking for stickies and blasting out to meetups/facebook and whatnot. Still not at that point yet. Again feedback is appreciated and let me know if you'd like to help and in what capacity, I've got a short list right now and I'm not playing email tag with everyone yet but I'm getting there.