Skip to content

Write DFMP-000, the proposal process paper #1

Description

@Hyadhuad

What is delivered

dfmpp/dfmp-000-dfmp-proposal-process.md written out: the path a proposal takes from an idea to a legitimated paper on master, in enough detail that someone who has never proposed anything here can follow it without asking.

Cover at least: what a proposal must contain before it is presented; how it is presented to the community through the issues; what "widely discussed and validated" means in practice; which DAOs or councils see it and how that is decided by purpose; how it enters the approval folder; how the pull request targets master and passes automated checks and public discussion; and how an update to an already-legitimated paper is handled.

Why it is needed

The file exists and contains only its own title. Every other repository in the ecosystem defers to "research organized through DFMP" — the process they defer to is currently undocumented.

Where to start

The README of this repository and dfmpp/README.md already describe the shape of the process in a few sentences. That is the skeleton; this function is the body.

Prior material

Drayker has earlier work on this subject in its own knowledge base — drafts, mostly in Portuguese, written before the public repositories took their current shape. It is not published yet. If you take this function, say so in the thread and the relevant material will be published alongside it, so you are consolidating and arguing with existing thinking rather than starting from a blank page.


This is an open function: small enough for one person to finish, defined enough that the result composes with the rest. Claim it in this thread before starting so two people do not carry the same function, and deliver through a pull request to master. It appears on the board at https://drayker.org/#org/fn

Metadata

Metadata

Assignees

No one assigned

    Labels

    effort:~8hRough estimatelevel:intermediateSome component or domain context is expected.open-functionConcrete contribution small enough for one person to deliver.skill:docsDocumentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions