Attendance: Stampede, HHA | Ottersync, Chris, Eric d | Kwak
Welcome and Agenda Requests
State of Mind
Abra: feeling excited to keep pushing forward, thinking of how we can overcome some of these corporate vs. DAO governance conflicts, feeling grateful to everyone for showing up
Stampede: not taking things for granted, feeling grateful for the ability to contribute
HHA: recognized stampede’s feeling, and looking forward to driving forward together – emphasizes the need for focus on driving the product forward and getting behind that. Loves putting these ideas together and contributing together.
Chris: everything going well – working on project management initiative with the DAO
working on something similar to a gantt chart, but wants to keep it simple
https://www.notion.so/sifchain/6b2fe7325962405ebdea834670fc0803?v=2bfe197dac624d3cba04ff4896e69038
Chris has been working on a template / form that people could fill out that enables them to update their progress
Template contains data about the project, milestones, and specs to indicate what is actually being done.
Eric: the problem is the accountability toward completion. How can we handle this issue?
Chris: Part of the challenge is that people don’t have time, ie. DAO work is varied and permissionless. The place we run into problems is something that the community wants but people are committed to something but progress isn’t being made. With the template that I am working on, we can see: “are you actually committed to this, and if not let’s let someone else step in”
Frame: DAO contributors have their own commitments, let’s help those that stall when progress that is expected is not being made.
HHA: feels that the most important part is defining goals and that we have a sufficiently large team to define frameworks for setting DAO goals
DAO-perspective: the DAO contributors that are already active should define goals for the DAO
HHA: to clarify – we have a large enough team within the DAO (of DAO contributors) that we can start defining larger goals and also start delegating some work to them
Eric: Yes, we still need to define what our needs are.
HHA: yes, that’s a good point. We can continue to flesh that out during these meetings. For on-boarding, the key is to match what Sifcore is working on with the users / contributors that may be interested in what Sifcore is doing – ie, ensure that the message is getting across. Places communications as the number one goal of the on-boarding. Then as an ancillary role, the on-boarding council.
Eric: I agree, but we also need to do some more education.
Could we focus on a website.
SifDAO recruitment follow-up
SifDAO’s Hats
Eric: Let’s try to keep it simple instead of adding unnecessary complexity.
HHA:
Do we have a way to look at all the tools that we use?
We use coordinape (compensation), cosmos governance module (governance), discord (communications & roles), notion (collaboration), google suite (collaboration), commonwealth (long-form communication)
Is anything we use redundant?
HHA: We could maybe consider why we have both google suite and notion
On-boarding Processes
Closing
HHA: Can we pass on the podcast idea to Nomad?
Stampede: Hopes to organize the DAO in a fashion that ends up being both efficient and efficacious. We have people that are ready, but we’re not sure what we’re getting ready for.
Up for starting to take on a leadership role within the on-boarding group
Eric: feels like we’re too early for doing something like that
HHA: recommendation: each working asynchronously to write in the text channel to outline the goals of the group