-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem: The current shortnames are weird and hard to use/remember #32
Comments
I totally agree! We can even remove
We would need to update all the BEPs, it's feasible, we don't have many. |
Solution: Switch to shortnames like BEP-2, as suggested in issue bigchaindb#32
This issue is mostly resolved. The only thing left to do is update the pull request to create BEP-11: pull request #57. I'm not able to update that pull request. |
Problem Description
The current shortnames, such as
4/STANDARDIZE-DC
and6/SWP
are hard to use and remember. Do you remember what DC or SWP stands for? Will you remember in a year?Proposal
In practice, we've actually been using things like BEP4, BEP-4, BEP 4, or BEP#4, because that's much easier to say and to look up. The proposal is just to make that the official "short" way that we reference BEPs.
I think the Python community already does this when they refer to their PEPs, such as PEP-8.
Let's just change all the "shortname" labels to say BEP-N, where N is the BEP number.
Let's also do some searches for "1/C4" and "2/COSS" and replace those with BEP-1 and BEP-2. I think those are the only two shortnames we ever actually used.
master
branch. See PR Problem: Current shortnames weird/hard-to-remember #51The text was updated successfully, but these errors were encountered: