Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evolving OpenGov #2324

Closed
wants to merge 5 commits into from
Closed

Evolving OpenGov #2324

wants to merge 5 commits into from

Conversation

monsieurbulb
Copy link

@monsieurbulb monsieurbulb commented May 31, 2024

Project Abstract

Whilst influential, large ‘public good’ treasuries are just one component in what can be understood as a phased innovation process that should be structured through the full life cycle of R&D, productisation and go to market, with motivations, oversight, rewards and ROI contingent on the phase and the entity involved.

To encourage an innovative culture, we need to understand just how to identify, support and scale that culture through a phased approach that approaches talent, focus and outcomes independently but as part of a cohesive whole, evolving technical, social and meritocratic structures as we go.

The aim of this initial paper is to set context for, and a hopeful path towards a more structured approach to innovation in the ecosystem - beginning at the lowest levels of creative endeavour.

Grant level

  • Level 1: Up to $10,000, 2 approvals
  • Level 2: Up to $30,000, 3 approvals
  • Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

  • The application template has been copied and aptly renamed (evolving_opengov.md).
  • I have read the application guidelines.
  • Payment details have been provided (Polkadot AssetHub (DOT, USDC & USDT) address in the application and bank details via email, if applicable).
  • I understand that 30% of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
  • I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
  • The software delivered for this grant will be released under an open-source license specified in the application.
  • The initial PR contains only one commit (squash and force-push if needed).
  • The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
  • I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: `` (change the homeserver if you use a different one).

Copy link
Contributor

github-actions bot commented May 31, 2024

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@github-actions github-actions bot added the admin-review This application requires a review from an admin. label May 31, 2024
@monsieurbulb
Copy link
Author

I have read and hereby sign the Contributor License Agreement.

Copy link
Member

@semuelle semuelle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @monsieurbulb, thanks for the application. This sounds generally interesting, but I have a few questions/requests:

  1. Have you considered requesting funding for this from OpenGov? If not, why?
  2. Are you planning to fund the subsequent research through grants as well?
  3. Why are you focusing on Kusama only? I'm sure much of it would apply to Polkadot as well.
  4. You say that the paper is going to be largely qualitative. I understand that a lot of the work will be hard to measure, but I'd still be interested in at least trying to substantiate the work with data. Perhaps this could be structured beforehand (see next point)?
  5. The deliverables are not well defined. The specs of the 0x deliverables should be adapted to your specific project (you have not mentioned any data or artifacts to be delivered). The remaining deliverables are rather vague. It might make sense to structure these differently, e.g. by separating them into a bibliography, data and analytical tools and resulting paper.

@semuelle semuelle self-assigned this Jun 11, 2024
@semuelle semuelle added the changes requested The team needs to clarify a few things first. label Jun 11, 2024
@monsieurbulb
Copy link
Author

monsieurbulb commented Jun 12, 2024

Hi @semuelle thanks for the comment.

Have you considered requesting funding for this from OpenGov? If not, why?

Short answer Yes.

However...

I decided to submit this due to @anaelleparity's RFP Action Research for OpenGov... in conversations with her after she submitted the RFP that W3F preferred to see these go via the treasury as (paraphrasing) this would give contributors chance to learn about the system on which they are reporting.

Ultimately I want to assess the viability of this particular RFP - and indeed learn from the responses from people such as yourself... not to get too meta, but in some ways this proposal is just another active part of the 'Evolving OpenGov' paper.

You get different signal from W3F dedicated grants people such as yourself, KSM / DOT holders would be different, DV different again. Not saying one is better than the other, since all have a different perspective.

"The parable of the Blind Men and an Elephant is a story of a group of blind men who have never come across an elephant before and who learn and conceptualize what the elephant is like by touching it. Each blind man feels a different part of the elephant's body, but only one part, such as the side or the tusk. They then describe the elephant based on their limited experience and their descriptions of the elephant are different from each other. In some versions, they come to suspect that the other person is dishonest and they come to blows…"

This is from the Decred paper Forks in the Road.

I've spent an unbroken 6 years deep in the weeds of on-chain governance / treasury funding at decred, edgeware, kabocha, kusama and polkadot with my main curiosity related to how we create more collaborative, productive and sustainable funding environments compared to current incentives/structures/processes and the second order effects they produce on culture, politics and output.

That necessitates seeing the elephant from as many perspectives as possible.

Are you planning to fund the subsequent research through grants as well?

Perhaps, i wouldn't commit to a single route.

We're launching a new community oriented stablecoin with Brale on Kusama AH and they are taking their integration fee in KAB, the native token of Kabocha (which W3F has a 7.5% stake). The yield from that project is designed to create an alternative funding model to W3F grants and KSM/DOT treasuries, though we do see ways to involve them in the economic opportunity. We are also working on onboarding alternative financing structures - see Introducing an alternative financing strategy, structure and partnership for maximising the potency of Kusama’s treasury.

Why are you focusing on Kusama only? I'm sure much of it would apply to Polkadot as well.

Since this is a W3F stablecoin grant, I tend to think more holistically about the behaviour + output, rather than a particular brand narrative - please see Is Polkadot a brand? for further context.

Were the grant funded by DOT or KSM directly, then it would ensure the narrative would feature either Polkadot or Kusama more strongly.

Though Kusama and Polkadot are technically similar, they are not technically identical - ie there are different parachains running on each network and the treasuries fund different things, the token holdings are different and ultimately the cultures are different in obvious and non-obvious ways.

You say that the paper is going to be largely qualitative. I understand that a lot of the work will be hard to measure, but I'd still be interested in at least trying to substantiate the work with data. Perhaps this could be structured beforehand (see next point)?

Well I imagine much of this may come together with existing research that is more quantative that frames current ecosystem orthodoxy. I did a lot of work outlining data around Kusama treasury spending and modelling Coretime income.

The deliverables are not well defined. The specs of the 0x deliverables should be adapted to your specific project (you have not mentioned any data or artifacts to be delivered). The remaining deliverables are rather vague. It might make sense to structure these differently, e.g. by separating them into a bibliography, data and analytical tools and resulting paper.

The output is a single paper working title Evolving OpenGov that brings together historical analysis to present a strategic rationale for structuring support and spending across the full innovation cycle.

This is is not theoretical analysis, but pragmatic and actionable work (that we are actioning). In many ways I see this paper as a way of better communicating the strategy we are currently executing on, allowing a larger group to contribute to what is in effect a grass-roots rethinking of current ecosystem orthodoxy.

Maybe I've misunderstood the deliverables aspect of the grant template - would you like to see this section with more info?

  1. Consolidate information Aggregate existing research
  2. Structure document Outline the structure of the paper
  3. Complete paper Bring together the research into the paper

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the application. But at the moment the deliverables contain not a lot of details. For example, what kind of existing papers would you aggregate? Also not sure that our grants program should support: “‘thinking in public”. And just to mention it here: an RFP doesn’t necessarily be funded via the grants program. You could also apply for treasury funding with this.

@monsieurbulb
Copy link
Author

monsieurbulb commented Jun 12, 2024 via email

@semuelle
Copy link
Member

The output is a single paper working title Evolving OpenGov that brings together historical analysis to present a strategic rationale for structuring support and spending across the full innovation cycle.

This is is not theoretical analysis, but pragmatic and actionable work (that we are actioning). In many ways I see this paper as a way of better communicating the strategy we are currently executing on, allowing a larger group to contribute to what is in effect a grass-roots rethinking of current ecosystem orthodoxy.

Maybe I've misunderstood the deliverables aspect of the grant template - would you like to see this section with more info?

Research grants provided by the Grants Program have always been focused on small, well-defined questions and topics that allow (or rather, require) a thorough description of questions, methods, metrics and expected results. I think the OpenGov RFP also points in this direction. Your current proposal sounds more like a critique, which would be extremely difficult to evaluate. As such, I think it would be better suited for the treasury in its current form.

@monsieurbulb
Copy link
Author

@semuelle

Research grants provided by the Grants Program have always been focused on small, well-defined questions and topics that allow (or rather, require) a thorough description of questions, methods, metrics and expected results. I think the OpenGov RFP also points in this direction.

I’ll add more detail related here.

Quoting RFP;

There is the need for more encompassing, neutral, practical, and actionable case studies of OpenGov’s implementations, which can help establish a feedback mechanism and prioritise future developments for OpenGov.

The challenge with the nature of this framing is that operating within OpenGov is a subjective experience that leads to strategic insights that are by definition opinionated rather than neutral.

In part, as someone who has lived / worked under the system for a few years, we have an interesting collision where the W3F assess the validity of this experience without being party to it.

The current proposal sounds more like a critique, which would be extremely difficult to evaluate.

This is where the discussion becomes much more interesting - “what metrics matter in OpenGov” is an open question and is a part of the intended output.

We also connect back into the point of the submission which is a review of the system related to how innovation works.

How are we to assess the output of the system?

As such, I think it would be better suited for the treasury in its current form.

Let me do one more round of changes based on your feedback, this is a useful feedback loop for all sorts of reasons.

@keeganquigley
Copy link
Contributor

Thanks @monsieurbulb feel free to ping us once we should take another look.

@monsieurbulb
Copy link
Author

monsieurbulb commented Jun 25, 2024 via email

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for the update here. I'm going to close the PR.

@Noc2 Noc2 closed this Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
admin-review This application requires a review from an admin. changes requested The team needs to clarify a few things first.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants