Proposal: Adjourning the Orcanuts Pod
Consent required from: Orca-source
Consent by: 2022-07-07T11:00:00Z
Although we all felt that maintaining the Orcanauts Pod was worthwhile, lived experience shows that it serves no purpose in the current life and functioning of the community. It has been obviated by the creation of the Orca-source Pod, which has many of the same members, and SL members as well.
Even the 1 / month meeting we agreed to have did not happen, and there is no clear aim or domains for the Orcanauts Pod at this time. And all this would be a non-issue, except all Pods are publicly available online, and visible in relationships through the Orca Podarchy feature.
Currently, based on how the community was organized all the -naut Pods are children of the Orcanauts Pod. Yet it doesn’t function and those Pods are funded by the Orca-source Pod. This presents a false representation of how the organization is actually functioning. I believe, and hope you agree, that it is in our best interest to present as clear and accurate a representation of our experiment in governance with Pods as accurately as possible. We are already in a bit of a spotlight, and that light will grow brighter as we move from private beta, to public beta to initial release.
The only reason to maintain the Pod is that it has funds in its treasury. However, mothballing it by ‘hiding’ it, in the same way we have org-naut, should still leave working with its safe and treasury availble to us.
- No change: We leave the orcanauts Pod as is, and make it the false parent of all th -naut Pods.
- Move its Pod members: We remove member -naut Pods from orcanauts.pod.xyz and add them as children of the orca-source.pod.xyz Pod, which reflects our actual usage.
- Wait for Eject: Official removal of Pods from podarchy is on SL Roadmap, and we could wait for it to be live, and then Eject the Pod from our Podarchy, after moving -naut Pods to orca-source.
- Number of transactions: Any on-chain transaction will cost some gas.
- Consequences: Possible effects of this approach.
|1. No change||None||Podarchy would not reflect current governmental practice|
|2. Move sub Pods to orca-source.pod.xyz||>=6||Governmental practice reflected, Pod left floating by itself.|
|3. Move sub Pods and move it to “drydock” pod||>=7||Semantically accurate UX which keeps Pod visible in an accurate manner. Drydock could look funny online, but allows us to easily reuse Pods.|
|4. Move sub Pods and Eject||>=5||The designed way to “mothball” Pods coming soon from SL. Presumably without it taking space in the podarchy, and still able to be recovered|
|5. Move sub Pods and delete entirely||4||Most complete on-chain cleanup, but we lose the option to reuse this pod|
After consulting with @John_Sterlacci on Discord and digesting his feedback, I recommend option 2. In the alternative option 4 allows us to demonstrate the utility of a new feature if we are willing to wait. Or, even both in time as the ability arises.
The process would look as follows:
- remove *-naut.pod.xyz as a member from orcanauts.pod.xyz
- add *-naut.pod.xyz as a member of orca-source.pod.xyz
- remove all current members from orcanauts.pod.xyz
- maintain orcanauts.pod.xyz as a member to org-naut.pod.xyz
- transfer the admin key from zkchun.eth to orca-source.pod.xyz
This keeps also the orcanauts pod reusable for the future. Importantly, it moves the pod out of the Orcanaut podarchy, which makes it less confusing for outsiders to interpret how our organization is structured…
*The time limit for this proposal (2022-07-07T23:59:00Z) is set to be on the shorter side as it has been a discussion on orcanauts current relevance has happened in both Pod Lead and Orca Source meetings, on Discord and follwing posts, and some explicit discussion here on the forum. At the last Orca-source meeting there was agreement among ON members, except for @Appt_Pupil’s absence, that the Pod should be mothballed for now.
A veto from Pupil as not GEFNSETT would be happily accepted by me if clear and explicit reasons as to why we should not do this were stated. To this point that has not happened.
I made an omission in this proposal with respect to the funds in the orcanauts.pod.xyz. For options 2 - 5, I suggest that the funds currently there be transferred to the orca-source.pod.xyz safe, and that the amount received be documented as X1 funds in an Orcanaut document in ClickUp, so that disbursements from them be earmarked for purposes related to X1 or pre-X1 only, unless explicitly documented as to why something else should be allowed.
This is one more tx for all options 2 - 5.