2021-11-05 F6 Retro and DoU Next Steps

[evolayak]

Attendees: Dan, Danaja, Felix, Heather, Liese, Lucas

F6 results

• We were super close to getting funded in F6- budget was too high - in the future look at the budgets of the other proposals in same challenges/similar components.
• Felix explained how this works. Numbers and stuff.
• Ratio of votes relate to your viability to get funded; we did pretty well.

Prepare for F7

• Copy paste F6 proposals.
• Adjust to the new challenges.
• Budget will be more for this round (8 million) because it doubles every round of funding.
• Think about coordinating with others proposals, teaming up?
• What challenges in F7? Something for community events…
• Felix invited us to join a network of proposals to have things reviewed (in 2 weeks is the deadline)

[The following section I wasn’t very good at getting down on paper]

Proof of Souls

• Felix goes into this community treasury; Proof of Souls: projects that are value-adding to communities not just themselves.
• Network of pools that define the community treasury.
• Each project has its own stake pool.
• Nori Nagoshima sets up fully automated stake pool services (for those who don’t have the time or skills) and takes a percentage.
• But we’d like to go with a person. (Lauris)
• Set up with stake pool through Lauris.
• Each project sets up second stake pool in 3-6 months (50/50 pool)
• 2-5 ppl per stake pool; almost all goes to delegators - want to incentivise community to throw into stake pool.
• Once community delegates into your pool, they receive rewards but we also want to attract investors - “I really believe in project” not so much about making money.
• Minting governance tokens give access to participate in the treasury but you can delegate the token to a person who represents your interest.
• Goal is to empty treasury to distribute to the community.

Next steps:

• Felix sends info to generate keys, then contact Lauris (stake pools operators)

DoU Changing platforms:

• DoU will make the switch to Discord (and eventually GitHub; see Dan’s GitHub workshop for Climate4 Cardano - internal workshop if still more Qs).
• Heather set up Discord server a couple weeks ago with help from [other] Vicc.
• Heather will continue to manage and hopes to slowly have Liese and Lucas (Dana too?) helps with community management. Internal onboarding will help if we go this route to onboard spaces.
• Try to minimise the number of channels on the Discord server: threads within channels can organically develop channels
• Lucas questions whether we should we want to use Discord and GitHub with the spaces. (Heather comments we should try ourselves before assuming it’s ‘too difficult’ for spaces and other communities.
• Also, Lucas questions if should we be called a DisCO, because do we want to self-organise/govern that way?
• Heather loves DoU and some agreement in the group that if we’re proposing to introduce the DisCO concept/framework to spaces of urgency we should seriously consider self-organising/governing as one.
• But This could take a lot of work in terms of setting up mechanisms to track contributions, voting power, etc.
• Where to start? SecretDesks repositories on GitHub, of course! (Thanks, Dan!)
• Dan also explained a bit about how SD is using Discord; we’re really free to use it as we wish.
• [Conversation served and Heather forgot to quickly explain that she saw the DoU Discord server as something close to but a simplified version the the SD server: 1) place for internal communication- more organised than Telegram; 2) first stop for people interested and basically the online community platform. Because there are different privacy settings for different roles, we can set it so we have channels for all, channels for core team members, etc. - all of this can evolve though.]

Next steps:

• Naming and ‘branding’: Because there is substantial disagreement within DoU, we need to set up brainstorm: what we each associate with the project, what we want to communicate, Miro board.
• How we organise and govern: Dive into SD repositories on GitHub; get some clarity about who can do what, level of commitment.

NFT Ticket update:

• Pedro and Tea confirmed verbally.
• Dan drafting contracts based on outline, Heather to edit.

Next Steps:

• Tea has more questions re: the agreement; Dan and Heather to have a call with her on Wednesday.
• SoU to make email address so Dan can register with NFTMaker pro

FTR:

• Apprx. 15 people from Catalyst Community at FTR.
• Tuesday meeting: talking about roles at FTR (moderation, etc.), regular check-in. Liese asks Dan and Heather moderate the blockchain and swarm session at FTR.. Heather bit unsure but totally down if it will make the discussion more fruitful.

[FelixfromSwarm]

small typo @evolayak . Loris is Lauris :)

[evolayak]

Thanks!

Sent from ProtonMail for iOS

On Sat, Nov 6, 2021 at 16:42, Felix Weber @.***> wrote:

small typo. Loris is Lauris

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[LucoSOU]

Hi @evolayak

I dont think i was really all to clear or making enough sense on some of the points in our discussion yesterday. Particularly on these two:

• Also, Lucas questions if should we be called a DisCO, because do we want to self-organise/govern that way?

• Heather loves DoU and some agreement in the group that if we’re proposing to introduce the DisCO concept/framework to spaces of urgency we should seriously consider self-organising/governing as one."

The main point I wanted to get across from this part of the discussion was to reflect on the naming of the project. For me, calling this project DisCO of Urgency is a little random and doesn't connect to a mission/vision/ impact strategy/target beneficiaries of what the DisCO is trying to achieve or who it is to represent. With the name now, it for me atleast feels like we are placing the urgency on an organizational model. Its kind of like Cardano calling itself Blockchain, or Proof of Stake. Or am I missing something? ha ! Somehow the name of this - project - organization - distributed cooperative , should address and speak the mission and beneficiaries.

Im in favour of developing the project in the organizational format of a DisCO, I think I was just questioning how we have not developed the project as a DisCO, or examplified that within our own working structure, yet we are calling the project DIsCO of Urgency.

happy to talk further about it!

[evolayak]

Ok, clarification much appreciated, @LucoSOU ! My only concern is, then what do we call it or is it enough to have it as a working title and then co-create a new one with community members at a later date; how would we do that in terms of voting etc. We should also be thinking about the decision-making processes (for everything really)... For me, the name makes sense. It's a DisCO that's working to empower, etc. spaces of urgency. But perhaps I'm just not aware enough of all of SoU's work to come up with an alternative...

[DanM3rcurius]

Do we have any further action items from this? @evolayak @LucoSOU Maybe to some basic documentation (here as an issue if you like) where you meet when to do what.