<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>From Devin Balkind: <a
href="https://wiki.p2pfoundation.net/Spokes_Council_Model">https://wiki.p2pfoundation.net/Spokes_Council_Model</a><br>
</p>
<p>"Occupy Sandy, which took place about a year after Occupy Wall
Street, worked a bit differently. We recognized the flaw in a
council of affinity groups and instead organized a spokes council
around projects. Project members, unlike group members, had to
agree to maintain a membership list, vouch for their members, and
articulate success metrics that the group had to meet to remain in
good standing with the council. Those elements made a world of
difference. The Occupy Sandy Project Council successfully managed
hundreds of thousands of dollars through a consensus-based process
that, while sometimes contentious and stressful, actually
succeeded in allocating funds to impactful projects in transparent
ways that won the respect of myriads of people — from city
officials to direct action organizers. I've been trying to
translate this "project spokescouncil" approach to other types of
organizations ever since, with some success.
</p>
<p>Here's how I've been applying these principles:
</p>
<p><b>Instead of creating an "organization," create a charter that
explains how to run a network.
</b></p>
<b>
</b>
<p><b>Instead of figuring out all the things you want your
organization to do, find people already doing these things and
invite them to join your network.
</b></p>
<b>
</b>
<p><b>Instead of creating a central administration to run the
network, encourage projects to commit to performing the various
functions needed to sustain the network, including
administrative ones.
</b></p>
<p>One of the great features of the project spokescouncil approach
is that participating projects don't have to agree on anything
more than a charter. For-profits, nonprofits, cooperatives,
coalitions, grassroots projects, and other groups can all coexist
without forcing their processes on each other"
</p>
<div class="moz-cite-prefix">On 8/19/2019 11:29 AM, Mark Carmel via
OSList wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFDvDFg9HGrYAvVgOn+yLr5NHGxGPFHmEmauJMkev4ZB1OKYbw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">1st of all thank you for everyone who gave me
feedback on my big idea for certification. It was sincerely
appreciated. However I can see it was something that did not
Resonate well.
<div dir="auto"><br>
</div>
<div dir="auto">Open space technology has clearly set the
standard for the facilitation of peace and human
understanding. It is such a powerful and simple tool but
highly complex. As Harrison says.. chaos plows the fields of
the mind so that new ideas can grow... I think there is ample
chaos for us to tackle right now.</div>
<div dir="auto"><br>
</div>
<div dir="auto">I think it is highly important for the
leadership of our open space world to make a decision now
while we still have Harrison among us as a living spirit.
Because we have already set the standards why not cement the
standards and turn it into an everlasting association that
could be organized to deliver training, etc. To advance the
mission of human peace and understanding in a more organized
way?</div>
<div dir="auto"><br>
</div>
<div dir="auto">If you want to be a beautician or a mechanic or
a rocket scientist or a city manager there are associations
for that .</div>
<div dir="auto"><br>
</div>
<div dir="auto">Why not an association for open space technology
practitioners to define the standards, the ethics, code of
conduct, the way that Harrison has already articulated them,
but to formalize them and help us get organized and stay
organized until we get the job done?</div>
<div dir="auto"><br>
</div>
<div dir="auto">Respectfully submitted,</div>
<div dir="auto">Mark Carmel</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OSList mailing list
To post send emails to <a class="moz-txt-link-abbreviated" href="mailto:OSList@lists.openspacetech.org">OSList@lists.openspacetech.org</a>
To unsubscribe send an email to <a class="moz-txt-link-abbreviated" href="mailto:OSList-leave@lists.openspacetech.org">OSList-leave@lists.openspacetech.org</a>
To subscribe or manage your subscription click below:
<a class="moz-txt-link-freetext" href="http://lists.openspacetech.org/listinfo.cgi/oslist-openspacetech.org">http://lists.openspacetech.org/listinfo.cgi/oslist-openspacetech.org</a>
Past archives can be viewed here: <a class="moz-txt-link-freetext" href="http://www.mail-archive.com/oslist@lists.openspacetech.org">http://www.mail-archive.com/oslist@lists.openspacetech.org</a></pre>
</blockquote>
</body>
</html>