Reposted from #disasterradio on Patchwork, originally published on Sep 28th:
\o/ back on patchwork, and very happy to be here!
I said I would share some of sudoroom / sudomesh's governance docs, so
here's a breakdown of the basic agreements / governance structure we could
adopt. Based on feedback to this post, I can turn these into some draft
documents up for consensus.
Here's a current draft of Sudo Mesh's bylaws, based on bylaws of the Omni
Sudo Mesh Bylaws
I'm thinking that formally, Disaster Radio would be a fiscally-sponsored
project of the Sudo Mesh 501c3 with a designated committee of all those who
participated in our first call. I can draft a fiscal sponsorship agreement
based on those we've written for Omni's fiscally-sponsored projects .
That committee would have full control of any funds designated as "Disaster
Radio, a Project of Sudo Mesh" in a subaccount of Sudo Mesh's bank account.
Initially transferring funds into a subaccount of Sudo Mesh's bank account
is necessary if we're using Sudo Mesh's 501c3 org status, because those
funds need to be allocated and tracked by the 501c3 and documented in the
annual 990 federal tax forms. Typically, a sponsoring nonprofit charges
5-15% of money raised by the project because of the administrative overhead
necessary (tracking expenses, writing receipts, annual accounting & taxes).
I would suggest the minimum 5%, which will in all likelihood end up going
to recurring server / bandwidth costs anyway , or perhaps that reserve
could go toward paying an accountant or lawyer.
New potential members of the project would be agreed upon by consensus of
the full committee, so long as a quorum of members (2/3?) are able to weigh
in. Decisions can be made electronically (see Sec. 16: Action by Unanimous
Written Consent Without Meeting) - perhaps we could implement a Loom.io
instance or some such for consensus proposals?
Financial decisions could be made by consensus of the whole committee -
however, it may be prudent to designate a sub-committee that focuses on
budgeting, accounting, and handling financial proposals / budget requests.
To that end, other subcommittees / working groups might include hardware
design, software development, community outreach, etc - with each working
group empowered to make certain kinds of decisions, rather than requiring
full committee consensus at each step, twist and turn :). Working Groups
would be required to be fully transparent and open to any committee members
to join 
The following is probably more proposals for Sudo Mesh the umbrella org,
which informs the overarching values and policies of its projects:
- For resolving conflicts, I'd like to propose we adopt sudo/omni's
Conflict Resolution Policy [4, 5] or some variant.
- In terms of values, I'd like to propose adopting a Statement of
Solidarity to articulate a commitment to prioritizing the needs of the
marginalized and oppressed , as well as a Safer Space Policy to
articulate commitment to a nurturing, harassment-free space (online and in
This is probably enough for one post... thoughts / feedback welcome!!
 Sudo Room's Fiscal Sponsorship Agreement w/ Omni Commons (set
$2000/month contribution toward rent/mortgage):
 Real Vegan Cheese's Fiscal Sponsorship Agreement w/ Omni Commons
(similar model Disaster Radio would have, 5% of income paid out to sponsor):
 Omni's Protocols re: Working Groups:
 Conflict Resolution Process for Omni, adopted from Sudo Room's:
 A visual schematic of decision-making processes:
 Omni's Statement of Solidarity:
 Omni's Safer Space Policy:
Help open a people-powered common space in Oakland, California!
"Technology is the campfire around which we tell our stories."
"Storytelling reveals meaning without committing the error of defining it."
"To define is to kill. To suggest is to create."