1 of 31

Governance Tools Working Group

First meeting

21st March 2024

1

2 of 31

Agenda

This meeting is to:

Know each other
Give context
Define next steps

Participants Intro

02

Governance tools Intro

03

What is the purpose of this working group / Decentralisation

04

Next Steps

05

Questions

01

Related Miro

2

3 of 31

Introduce yourself

01

What’s your name
Where are you based
Why did you join us today
Anything else about you

3

4 of 31

Governance tools Intro

02

4

5 of 31

Governance Tools Goal

Provide a foundation to allow participation and so support adoption of the governance process

5

6 of 31

Common processes,

Supported by common tools,

Maintained by distributed development

owned by Cardano Community

6

7 of 31

Governance Tools

Open Source

Core Governance System of Tools - GovTool

Proposal discussion

Proposal submission form

GA on-chain submitter

Delegation

dRep registration

dRep delegation

Voting

Vote submission

Voting Review

GA outcomes

Important GAs outcome Reporting (for now gitbook + INT website)

dRep explorer

Proposal comments

ByronNetwork

TO BE AWARDED

WeDeliver Team

8 of 31

Governance Tools

Supporting tools

Open Source

Core Governance System of Tools - GovTool

DRep Campaign Platform

LidoNation

Proposal discussion

Delegation

Voting

GA outcomes

Constitutional Committee Portal

Bloxico

9 of 31

Voltaire GovTool

Core foundation to be supported and expanded by community itself

Reference implementation to support the experience of key governance steps

9

10 of 31

What is the purpose of this working group / Decentralisation

03

10

11 of 31

Governance Tools Working Group

Initial scope:�Refine the decentralisation process and play an active role in managing the Core Governance tools

11

12 of 31

Why do we need to Decentralise?

To ensure adoption of governance

To ensure adoption of governance, by ensuring the adoption of tools, that will ensure the adoption of governance recommended processes which will ensure the adoption of governance itself

To allow community who uses them to also feel empowered to improve and maintain them

We want to reduce the reliance on funding to get people interested in the tools and on working on them. We want to replace that with a sense of ownership to drive action (still supporting process with a budget)

To reduce reliance on Intersect Product team

We need to reduce reliance on an Internal govtech team otherwise the scale of team and resources to manage these tools will make grow this team out of proportion and not provide the right value to the community itself.

12

13 of 31

What do we mean by decentralising?

Open collaborative development�
Community ownership > �distribute decision making

13

14 of 31

Current strategy key points

Decentralise emotional ownership
Decentralise practical work
Break down the process to be decentralised in chunks (to make it easier to distribute)
Define a draft budget to support this ≈ $1M
Use current development to create a rich backlog to cover the whole process

14

15 of 31

Governance Tools Working Group

Initial scope:�Refine the decentralisation process and play an active role in managing the Core Governance tools and help manage the roughly $1M budget

15

16 of 31

Questions

04

16

17 of 31

Suggested Next Steps

05

17

18 of 31

Next Steps

Agree on meeting cadence and comms channels
Divide in groups [Who is interested in covering which part (refine how to distribute decision making and work on that part]
Review this deck and Miro > Leave comments or questions
…

18

19 of 31

Strategy details

19

20 of 31

Which tools do we need to decentralise?

03

20

21 of 31

Constitutional Committee Portal

All GovTool Pillars

Delegation, Voting, Proposal Discussion and GA outcomes

All Analytics and connected tools

Ex. usersnaps

Which tools do we need

to decentralise?

01

03

02

21

22 of 31

Which aspects do we need to decentralise?

04

22

23 of 31

Tasks we need to decentralise

Development

Design architecture
Flow mapping + interface design
Small bug fix
Big bug fix
New feature dev
New area / pillar dev

Definition of what needs

to be done

Research
Discovery
Feedback collection

Backlog creation and prioritisation

Review outcome of research /discovery/ feedback / bugs to suggest actions
Size / estimate / prioritise tickets + assign bounties if relevant
Product oversee (to keep a joint / cohesive experience and structure)

23

24 of 31

Tasks we need to decentralise

Procurement

Defining contracts with new builders
Contract signing
Payments

Maintenance

Analytics
Managing repos
Licenses updates
Domain and hosting management
Review and merge PRs
Maintenance of standards for github (dev + PM) and figma

Managing projects in github
Design systems
Managing environments
Standardise and manage tech stack
Peer code review

24

25 of 31

Which bodies can handle the decentralised tasks?

05

25

26 of 31

Potential Bodies

Governance Tooling Working group

This working group can manage feedback collection, review of outcomes of research, estimation and prioritisation of backlog, product oversee, managing github and figma, define new contracts. It can also be split in smaller working groups to manage specific parts of the process if needed

OSC

The OSC can oversee the development overall and the github and repo management

Intersect Members

Intersect members can contribute autonomously to any step and also access contracts and bounties.

General Community Member

General community members can contribute autonomously to any step.

Intersect Team

The Intersect Team includes any function of the team that needs to support the process. In particular Intersect team can manage projects and repos, manage contracts and payments and facilitate the process.

Contracted Intersect Builder

Contracted Intersect builders are organisational intersect members that have been contracted to cover a specific part of the process using the allocated budget.

Governance Tools Facilitator / Coordinator

This role could oversee the whole project making sure alignment is kept throughout

26

27 of 31

Current high level strategy

06

27

28 of 31

High Level Strategy

Decentralise and Build emotional ownership #1

The first step to make sure community takes these tools as their own is to build up their sense of ownership for them. If they feel they are their tools and they have control over them, it’s very luckily they will have the drive to take care of them, also helping us define how to decentralise practical work. To achieve these will need to structure a continuous marketing campaign and provide opportunities to contribute.

Decentralise practical work

The whole product development process needs to be decentralised. To do this we will taking guidance from OSC, we are growing a rich product backlog with low-hanging tasks to pick up (also useful to start test the process), we are creating a dedicated working group and we have allocated a budget to bounties to complete tasks.

How do both points above support each other?�To decentralise emotional ownership we’ll need to show not only that governance tools are community tools, but we need to also give them proof they can access and contribute. Viceversa to decentralise practical work we need to start to test our processes and get some people in. So the process to achieve the points above will be continuous and organic.

28

29 of 31

High Level Strategy

Rich Product Backlog

We are creating a rich product backlog with tasks that cover the whole process to decentralise. This will allows us to kick start the process and test every step.

Bounties

We have allocated a budget from the grant pot to incentive with bounties single tasks in our backlog. This will start to attract people and it will allow us to test processes.

Working group�We a community of builders, many of which are already part of intersect and building with us, it will be crucial to create a working group that can start to feel ownership for these governance tools and can start to refine this initial strategy

Rareevo 2024 - Governance event�2024 Rareevo will be the culmination of our work, we’ll showcase participation, we’ll have demos from the key current builders and we’ll reinforce community ownership by awarding the build of the last pillar in the event.

29

30 of 31

High Level Strategy

2025 budget

We are refining the budget needed to support governance tools, and we are working to justify its incorporation in the continuity budget.

Decentralisation option 1

The governance tools, starting from Govtool, have been structured to be sliced in pillars (Proposal Discussion, Voting, Delegation, GA outcomes). So the easiest way to decentralise them is to give each pillar to a different Intersect builder and then have a working group or us to act as a facilitator.

Decentralisation option 2�All the governance tools will be open source, and as mentioned above they will be slides in such a way that multiple developers can work on them, also supported by documentation and adoption of best practises. A more complex, but better and more organic decentralisation option will be to have many community members contributing to maintain and improve these tools, booth for free and for small bounties, and then one or more working groups to orchestrate.

Decentralisation option 3�Prefer option: A balanced mix of the first 2

30

31 of 31

Thank you

31