Kift DAO created Pods to empower our members to create the change they wish to see within the Kift community. As Pods are a new organizational structure within Kift, it’s time for us to solidify how they operate to ensure community members have clarity on what to expect from Pods and how they can get involved.
In short, Pods are a way of managing the things being worked on within the DAO (via proposals and projects), with each Pod representing a different area of focus. The goal is for Pods to facilitate collaboration between DAO members with aligned skill sets, experience and interests.
As opposed to a system of a standing Pod with 1 leader and X members, we’re proposing a system where Pods are a more fluid mechanism for bringing up and discussing proposals. To do so, we propose that Pods switch to a proposal/project-based participation model.
Rather than artificially constrain the number of Pod members, Active Pod membership will be contingent upon someone either:
The process outlined in Proposal Process & Guidelines requires community members to collaborate in order to advance a proposal (KIP) to be voted upon and passed. This co-creative process of collaboration, refinement, and debate happens within the appropriate Pod for the proposal.
If a community member is interested in engaging in this proposal process, they are free to join Pod meetings, post in Pod channels, and contribute in any way necessary to help advance the proposal to a vote.
<aside> 💡 Example: the Gov & Law Pod is currently shepherding two proposals: A proposal for the Kift DAO proposal template, and this Proposal for Kift DAO Pod Formation. @Jeff Berezny and @Ola Kalejaye aren’t Pod leads but are passionate about Pod dynamics, so they collaborated, along with @Cam Lindsay to bring this proposal together and would thus be active Pod members under this model.
</aside>
If a proposal passes, it turns into a project. You can think of a proposal as a caterpillar 🐛 and the project as a butterfly 🦋
The proposal will outline who is responsible and the resources required for implementing the project. In most cases, this will likely be those who brought the proposal forward, but for larger projects it may include ongoing engagement from a wider group of people, from multiple pods. All primary contributors to the KIP/Project would be considered active pod members based on the expertise (or pod) that they are representing.
This team can evolve as interest from individual members ebbs and flows. Each project must have a leader(s) that is responsible for shepherding the project to completion. If the leader is unable to fulfill these duties, the leadership of the project must be transferred or the project canceled.