DDEP-0000:the-datdot-enhancement-proposal-process

[serapath]

@todo

• write up first draft
• commit as an "RFC" (request for comments) DDEP-0000:the-datdot-enhancement-proposal-process.md file to repo
  • datdot enhancement proposals. RFCs specifying the behaviors of datdot

---

Generally - the goal is to not have a DDEP as something where many people decide whether it is accepted, but rather a BDFL (benevolent dictator for life) or a small group, BUT it should link to other people or orgs or just places where different BDFL's or groups track their own STANDARD, which is either the same or differs in some aspects from a DDEP.

• that makes all related standards discoverable and it allows to discuss and may change or upgrade a DDEP to match one or more tracked other STANDARDs
• also via Pull Requests, a list of implementations that are DDEP compliant shall be kept :-)

process proposal - from the top of my head

1. join community chat and/or contact maintainers and talk to ppl to describe what a new DDEP or a change/update to an existing DDEP is all about and discuss it a bit
2. make an issue to summarize all thoughts and discuss it a bit there
3. make a pull request that adds the new DDEP or makes a change to an existing one and discuss and improve it
4. hope that maintainers will merge it
5. make your own copy of it - maybe give it a different name, but the same content
6. if many different proposals have the same content they should link to each other
7. maybe a viewer software can quickly check/notify if all standards linked in such a way are still in sync and notify people to update their links accordingly and talk to each other to:
   1. either bring them back in sync
   2. or state the reason clearly for why things are not in sync

It's kinda many many forks tracking each other and communicating to stay in sync if possible and clearly state reasons for a DIFF otherwise, like all decisions, reasons, pros & cons should always be captured :-)

---

proposal format inspiration

• https://www.bittorrent.org/beps/bep_0001.html
• https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1.md
• https://github.com/bitcoin/bips
• https://github.com/datprotocol/DEPs
• https://github.com/ChristopherBiscardi/toast/blob/master/rfcs/0000-template.md
• https://github.com/hypercore-protocol/hyp

e.g. Phases of new proposals or updates to Standards:

1. RFC (request for comments)
2. FCP (motion for final comment period) - which when period is passed without final comments becomes:
3. active (which means people can implement it and call themselves standard compliant
4. deprecated
5. archived