[RFC] Manifesto for an open organization

Summary

This proposal is for standardizing the proposal/disclosure flow so that the Dev Protocol community is a more open DAO.

Component Summary

  • Anyone can make any proposals regarding Dev Protocol through the forum.
  • Anyone can disclose what you are trying to contribute to Dev Protocol through the forum.
  • Proposer/Discloser will post proposals/disclosures in the prescribed format.
  • Proposer should indicate that you are ready to accept feedback by including [RFC] in the topic title.
  • If the proposer needs a collaborator that you haven’t found yet, you can declare it on the section of Missing Rolls.
  • For proposals on protocol cores or proposals requiring DAO compensation, the proposal must ultimately be passed by protocol governance.

Motivation

An open improvement loop is very important for the Dev Protocol community (including Dev Null AG) to remain neutral.

A standardized framework is needed to get the improvement loop running quickly.

Details

Proposer/Discloser will post proposals/disclosures to the Feedback & proposals category, in principle through the following formats:

## Summary

A short description of the topic. What is this topic proposal/disclosure about? Suggest 30 words max.

## Component Summary

- A description of the purpose of each component in the topic. Suggest 30 words max per component.

## Motivation

A short description of the motivation behind the topic.

## Details

Describes the topic and the problem it is solving.

## Agreed Collaborators

- A list of collaborators who have already agreed.

## Missing Roles

- A list of missing collaborator roles.

### Compensation

How much compensation should be paid to the collaborators? If the compensation is pay from sources other than the Ecosystem Fund, what are the sources?

## References

- A list of supporting materials referenced by this topic.

For proposals, you must explicitly indicate that state by including [RFC] in the topic title.

When seeking compensation from DAOs, I strongly recommend that we carefully discuss the adequacy of the compensation amount, due date, and payment rules.

Proposal flow

If you don’t need protocol core upgrades and DAO funding

  1. Post an RFC in the forum.
  2. Get enough feedback from the comments.
  3. Comment a URL of a git remote repository or a URL of a pull-request (merge-request) in the post.
  4. Close the post.

Protocol core upgrades or DAO funding required

  1. Post an RFC in the forum.
  2. Get enough feedback from the comments.
  3. Comment a URL of a git remote repository or a URL of a pull-request (merge-request) in the post.
  4. Close the post.
  5. After the code to upgrade is developed, start on-chain governance to execute the Upgrader Contract. (Note that currently, only limited members can execute the Upgrader Contract)
2 Likes

It is really important having everything standardized like this. Currently I don’t see any issues with this flow.

Should ‘enough feedback’ be quantified? Shouldn’t voting be part of this?

I will think about this and comment later.

1 Like