How to refer to IPs (Improvement Proposals) and RCs (Request for Comments)

[PaulRBerg]

Problem

SabVM will eventually become an open-source project and a public good, meant to be continuously improved by the global community of Sablier developers.

To that end, we need a pipeline of Improvement Proposals equivalent to EIPs (Ethereum Improvement Proposals) and PEPs (Python Enhancement Proposals), and another pipeline for RCs (Request for Comments).

Taken Names

As always, naming isn't easy. The obvious candidates are taken:

• SIPs is taken by Synthetix and Sui
• SRCs is taken by Fuel and Bitcoin Stamps

Suggestions

SBRC

SBRC = Sab Request for Comments

Couldn't think of any other better name. Maybe SABRC, but it would be fairly long.

SEPs

The only good name I could come up with is SEPs, which stands for Sab Enhancement Proposals.

Claude made several other recommendations, but I don't think any of those is better than SEPs.

SEPs appear to be unused in crypto. Some web2 tech and biology projects have used, but none appear to be active anymore.

Related

• SBRC-20: a token standard to ensure backward compatibility for ERC-20 #96

[IaroslavMazur]

Alternative names for "Requests For Comments":

• Feedback Requests
• Community Feedback Requests

Alternative names for "Improvement Proposals":

• Extension Proposals
• Change Requests
• Feature Requests
• Reform Proposals

Generally speaking, it'd be best to go for the standard "Requests For Comments" and "Improvement Proposals", to ease the burden of adopting a new terminology for SabVM that the potential contributors would have to carry.

---

SBRC / SEP

It'd be better if both prefixes are the same, for consistency and simplicity.
Having said this, wdyt about SFR ("Sablier Feedback Request"), instead of SBRC?

---

Now, given that the "M"-prefixed names ("Moniac"/"Mesh") have won the recent company poll, how about the following naming (with "Moniac" as an example):

• MRC (Moniac Request for Comments) and
• MIP (Moniac Improvement Proposal)?

[PaulRBerg]

Interesting naming ideas and agree that it would be helpful to use the same prefix. Let's go by elimination:

• Community Feedback Requests: verbose, we should stick with two words
• Extension Proposals: not all improvements are extensions. Some are just changes or removals.
• Feature Requests: again, not all improvements are features.

The others are interesting and I will think about them.

wdyt about SFR ("Sablier Feedback Request"), instead of SBRC?

Not bad!

have won the recent https://github.com/sablier-labs/company-discussions/discussions/52,

They haven't. We created another poll and "Project Sab" is winning traction: https://github.com/sablier-labs/company-discussions/discussions/54

"Sablier Mainnet" has won: https://github.com/sablier-labs/company-discussions/discussions/56

[PaulRBerg]

I went ahead with SRFs - Sablier Requests for Feedback. Good name @IaroslavMazur.

https://github.com/sablier-labs/SRFs