As per the discussion on fundraising, I see a need for a capital
projects group. Perhaps this description is already encompassed
within the charter of another group at this point, but from what I
have seen, it appears to be more an intersection of the Space Ops and
the Finance group. I see work of this group largely being about
hashing through permits, meeting with contractors/subject matter
experts and discussing the general long-term plan improvement plan and
tracking project dependencies/contingencies. Perhaps a bug tracking
tool would be helpful for this? This group could report-to or
work-with finance or space ops group, whatever is preferred. I would
be willing to bottom-line this group. I think a lot of the work of
this group can be done in asynchronous mode and reports backs can
often be in the form of a wiki/email update as i would like this to
focus more information gathering/fact-finding than on binding
decisions. Initially, an in-person meeting might be a good idea. The
information gathered can be can be brought to other groups so
hopefully there's less of a need to pile on another evening weekly
meeting for this group.
In many respects a lot of specific fact-finding work is already
happening, thankfully, but I think we could benefit from a little more
coordination, so that's why I'm suggesting a focused group so that we
can begin to look over how money fits into specific project
On Wed, Jul 23, 2014 at 2:50 PM, Jenny Ryan <tunabananas(a)gmail.com> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
At last night's Omni governance meeting , we talked at length about
the current status of our working groups and how to go about
encouraging work to get done principally in these working groups. We
identified some issues, such as the same people bottom-lining and
participating in all of the working groups. In short, we need fresh
Working groups should also be encouraged to work as they see fit -
which oftentimes is _not_ yet another weekly meeting, but perhaps a
bi-weekly work party, monthly hackathon, or mostly virtual collaboration.
Current working groups and bottom-liners as per the wiki:
1. Communication - Elaine and Jenny (requesting new bottom-liner) 
2. Challenging Dominant Culture - Kazoo & Margit (new bottom-liner[s]
3. Legal & Governance - Niki 
4. Finances - Danny (has this group met?)
'Space Ops' never really got started, and there was a proposal to
replace this instead with two new groups in need of bottom-liners:
5. Building Maintenance - biweekly Tuesday work parties 
6. Common Space Coordinating
What follows are guidelines for working group functionality, also
posted on the wiki :
_Working Group Protocols_
In order to make progress on many different aspects of this project,
please use the following protocols. The intention is to support
horizontal, consent-based, transparent, good-faith collaboration.
1. Start a Working Group
* Create Working Group wiki page and link to it here:
* Articulate "mission" or purpose, goals, and any tasks you already know.
* Schedule regular meetings and add them to the Calendar:
* Announce upcoming meetings on the omni-announce list at least 24
hours prior to meeting: omni-announce(a)lists.riseup.net
2. Hold Working Group Meetings
* Before the meeting begins, designate a facilitator and a scribe to
* Conclude the meeting with Outcomes or Action Items and schedule next
* Post meeting notes to the wiki on the Event page (making it
discoverable through the calendar)
* Prepare report-back for weekly Omni Collective meeting.
3. Join a Working Group
* Check the Calendar  and attend the next meeting of the working group.
* Directly contact the individual(s) bottom-lining the group.
* Show up to a meeting, or use the communication channel specified for
that group to stay in touch.
4. Make Progress in a Working Group
* Set goals that aspire to deliver on the working group's "mission" or
* If necessary, outline tasks in order to reach each goal.
* Make progress on and seek to accomplish any tasks that contribute to
the working group's goals.
* When a working group's goals require feedback, formal approval, or
simply consent from the Omni Collective, create a proposal:
** Present this proposal to the Omni Collective delegates meeting to
ensure each member-group can build consent in their respective
community as necessary.
* When a working group has several divergent options or ideas and
cannot come to resolution on them alone, then create proposals that
represent these options and present these in some way to the whole
** Present proposals at an Omni Collective meeting for feedback
** Ask for feedback on the omnilogistics(a)lists.riseup.net email list
** Ask for feedback from other working groups, member-groups, or
individuals that are not involved with your working group.
** Rinse, repeat until you have garnered improvements to your proposal
from the invaluable experiences and contributions of everyone involved
with the omni collective, ultimately building consensus among the
"Technology is the campfire around which we tell our stories."
- -Laurie Anderson
"Storytelling reveals meaning without committing the error of defining
"To define is to kill. To suggest is to create."
- -Stéphane Mallarmé
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
GPG Key: http://taffy.findpage.com/~cere/pubkey.asc
GPG fingerprint (ID# 73FCA9E6) : F5C7 627B ECBE C735 117B 2278 9A95
4C88 73FC A9E6