Consultation v2 — Product Scope Document

I’m going to be the squeaky wheel about terminology / naming :slight_smile:

I believe RFP is the wrong term to use in our situation. An RFP is something someone submits out to industry to solicit proposals to come back.

An architectural firm would submit an RFP out to their contractor pool.

The architectural firm is at the top and it submits an RFP to those outside of it or below it who then submit proposals back in response to the RFP.

What we are doing is having everything start at the bottom or outside the DAO and move up to it.

RFC (request for comments) → TC (temperature check) → GP (governance proposal) or RDIP (radixdlt dao improvement proposal) or IP (improvement proposal)

For me personally if we use GP (governance proposal) it could be viewed as a proposal to change how governance is done.

I think we need a more general term that can encompass all types of things (ie what to fund, how to upgrade the protocol, how to change the governance structure, how to vote out people).

I think XYZ Improvement Proposal is in the right direction (where XYZ is some term we agree on). I believe we all will only vote and pass something that improves radixdlt.

Ideas

  • RadixDLT Enhancement Proposal (REP)
  • RadixDLT Advancement Proposal (RAP)
  • RadixDLT Improvement Proposal (RIP)
  • RadixDLT Proposal (RP)
  • Improvement Proposal (IP)
  • Proposal (P)
1 Like