Brought this up at the first source pod call (12 May 2022). But since we have quite a few conversation topics on the backlog, I’d like to suggest that we come to an agreement on this asynchronously.
Supporting roles (facilitator, secretary and recorder) are not mentioned, because this proposal only concerns the on-chain creation of the source pod; supporting roles are not exclusive to pod members.
Some points are things we already agree on, like its members and aim and domains. But some are not, which I’m prepending with a :
- Pod name
- Who to require consent from to ratify this pod
- Pod admin
Would love to get feedback by 2022-05-17T23:59:00Z so we can have this posted in time for Thursday’s source pod call.
Proposal: Source Pod Ratification
<consent required from>
Consent by: 2022-05-24T23:59:00Z
We have decided on the off-chain structure of this pod, its members and supporting roles, yet still need to accurately reflect this on-chain.
The source pod exists to steward the flow of information and coordination across pods.
- Home finding - Supporting new initiatives in finding homes (in existing pods or spinning up new pods)
- Information Flow - Ensuring SL and ON have proper channels and support for information flow between and among pods
None; the source pod is equivalent to the general circle in sociocracy.
Orcanauts - Gov-naut
- Appt Pupil (lead)
- Cadena (delegate)
Orcanauts - Art-naut
- PostArchitekt (lead)
- Gaian (delegate)
Orcanauts - Nav-naut
- dendrons (lead)
- aia (delegate)
Sonar Labs - Communications
- Julz (lead)
- frogmonkee (delegate)
Sonar Labs - Protocol
- Dan Wu (lead)
- John (delegate)
None; without a pod admin, source pod membership can be managed through multi-sig transactions.
I propose a transaction threshold of 4 of 10.
I propose we set a short review period to coincide with the review of the governance charter: 20 June 2022. This seems the safest to me as we can simply agree to extend the duration if no major concerns emerge.
(Unsure about this one, so very open to thoughts here. Trying to lean on the side of safety here, but also down to just set an arbitrary date.)