Add links to other pods:

• golden pandas
• protozoa
• opti.mii

Add link to our venture buddies

• Enspiral Venture page

Links to networks

• Enspiral

Define what it means to be a member and that everyone in the group is a member

Contractors

Inter-Pod Delegates

see here https://www.rootsystems.nz/agreements/diversity-agreement.html

It would be cool to have some language that denotes that our agreements are linked - ie any change to the source is reflected in our handbook.

not sure I like the Living link to Enspiral agreement

When the pod is at level 0 buffer level we implement fairy gold. We need to work out the details of this

All pod members should have access to my.enspiral and Xero, at the very least view only rights

https://drive.google.com/drive/folders/0B70Rh6bijFGiaGVHM2pRRTROc0k

this should encapsulate the brief of the financial model

reference the archive section with current model

This came up for me recently - we need a simple agreement about what a full consensus agreement is.

I think we can keep it pretty straight forward - its either full agreement (all thumbs up) or majority agreement with no blocks.

Thoughts?
@sarah-arrrgh @ahdinosaur @gregorykan @iainkirkpatrick

https://handbook.enspiral.com/brand_agreement.html

submitted the "I would like to use the Enspiral brand in my project" form, answers recorded below:

Your name:

Root Systems

Briefly sum up your project: *

We're a small high-trust livelihood pod doing tech consulting and software development within the Enspiral network. Our purpose is to imagine and cultivate an ecosystem of local, replicable, life-support systems for interdependent abundance. See more at https://www.rootsystems.nz/.

Who’s responsible? And who else is involved? *

We have 6 members: https://www.rootsystems.nz/members/readme.html. We coordinate with other parts of the Enspiral ecosystem: https://www.rootsystems.nz/context/ecosystem.html.

How do you want to use the Enspiral brand? *

To identify as being "part of Enspiral", potentially in some context as "Enspiral Root Systems".

Are you running... *

A venture

Is this a project run through a different existing Enspiral venture? *
(eg OS//OS through EXP; Open Enspiral Workshops through Enspiral Labs)?

No

Who’s the audience? What is the reach that you anticipate this will have (local, national, international)? *

All of the above.

What are the benefits for the network? *

Maybe we are a wonderful example for how to organize a tech company. If we do good business, it would shine on the Enspiral brand.

What risks do you see for this project? *

Maybe we are a terrible example for how to organize a tech company. If we do poor business, it would reflect on the Enspiral brand.

How might you mitigate any of the risks? *

Do our best. :3

Anything else?

<3

What's your bank account and billing details?

Create a quickstart pod guide:
#13

Along the lines of the MOU we were discussing

some agreements specifically depend on others - so should be noted at the top of the agreement

our current standup format is to post in #root-systems re:

1. how I'm feeling (meta), 2) what i did yesterday, 3) what I'm doing today, 4) any requests and/or blocks.

this hasn't really been working, as in:

• we usually only answer in detail the first question "how i'm feeling"
• it's not super useful as project coordination, which is noticeable when most projects choose to add another process for catching up each day on the project activity

we should probably split the standup into two parts:

• a text post into #root-systems that signals: 1) how you're feeling, 2) what projects you are working on today, 3) any team requests
• a face-to-face (in-person or video chat) standup for each project that signals a traditional standup: 1) what did you do yesterday, 2) what are you doing today, 3) any project requests or blocks

Add to gitbook why we need a 3 month buffer

realized @Julietbc is missing from the member page, even if provisional. we need a silly introduction.

what are our preferred tools? it might be good to document this so we have a clear idea for what to use when starting a new project, plus what someone should have an account / installed when doing business with us. also if we document our tools then we know what our requirements are when thinking about what tools we want to build.

• project management: trello? waffle?
• video chat: zoom
• documents: google docs
• files: google drive
• real-time chat: slack
• discussions: loomio
• code: github
• time tracking: toggl

???

at the moment the home page says "Enspiral Root Systems", but we haven't asked for permission to use the Enspiral brand since the brand agreement.

we should either

• get permission to use the Enspiral brand
• only refer to ourselves as Root Systems

or both, so the default is Root Systems but we have permission to invoke the Enspiral brand as makes sense.

for context, i'm the one who made the initial name Enspiral Root Systems, since i wanted to provide credit and show connection to our parent network. i still use this name when identifying outside of the Enspiral network.

When we need to put something somewhere and agree on it when we don't know what to do with it.

• Add Working with us doc
• Primary service
• Products
• What we delegate