Rename project to `RFCs`
Problem
Currently, the project is named RFC
, an acronym for Request for change. The common pattern used for RFCs across other projects like Vue, React is to use RFC as originally used by IETF, that is RFCs
which stand for Request for Comments.
See:
- https://github.com/vuejs/rfcs/
- https://github.com/reactjs/rfcs/
- https://www.ietf.org/standards/rfcs/
Proposal
- Let's change the project name to
RFCs
(Request for Comments) using plural since this could host several proposals. - All lowercase
rfcs
for project slug sounds good. - Remove all references of RFC as Request for change.
- Replace all references of RFC as Request for change with RFCs for changes to GitLab Frontend, RFCs for changes to Frontend, or something similar.
- (Optional) Add RFCs for changes to GitLab Frontend, or something similar, to the project description.
- (Optional) Remove the image from the README to make the process more interesting. Just kidding but that could work since RFCs in IETF are usually written in plaintext (
.txt
).🏀
Possible fix
diff --git a/README.md b/README.md
index a1e5ddf..f3868bf 100644
--- a/README.md
+++ b/README.md
@@ -1,11 +1,6 @@
-<h1 align="center">
- <img alt="Lumen" title="Lumen" src="https://assets.gitlab-static.net/uploads/-/system/project/avatar/13083/logo-extra-whitespace.png?width=140" width="140"> </br>
- Frontend RFC (Request for change)
-</h1>
+# RFCs for changes to GitLab Frontend
-<h4 align="center">
- Would you like to propose a new or a change to an existing frontend pattern in our codebase? Please create an issue here so that we can discuss it
-</h4>
+Would you like to propose a new or a change to an existing frontend pattern in our codebase? Please create an issue here so that we can discuss it using the RFC (Request for Comments) process.
## Why should we use this process?
Edited by Cameron McFarland (Admin)