-
Notifications
You must be signed in to change notification settings - Fork 71
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
80b13ec
commit 2f6744b
Showing
1 changed file
with
27 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Meta | ||
[meta]: #meta | ||
- Name: (Tag RFCs With Specification Label ) | ||
- Start Date: (2020-08-15) | ||
- Author(s): (ForestEckhardt) | ||
- RFC Pull Request: (leave blank) | ||
- CNB Pull Request: (leave blank) | ||
- CNB Issue: (leave blank) | ||
- Supersedes: (N/A) | ||
|
||
# Summary | ||
[summary]: #summary | ||
|
||
It would be nice to start tagging RFCs with a label that indicates which part | ||
of the specification (i.e Buildpack Interface, Distribution, Platform | ||
Interface) the RFC is making purposed changes to. | ||
|
||
# Motivation | ||
[motivation]: #motivation | ||
|
||
Indicating which part of the specification the RFC is trying to update or | ||
modify, the RFC will become more digestible because it will allow people to | ||
hone focus in on certain RFCs that effect them. This means that potentially | ||
effected parties have to spend less time wading through all of the RFCs in the | ||
repository to find the handful that will affect them. Overall, this change will | ||
make reviewing RFCs a much more manageable process for new members and people | ||
that are concerned with specific parts of the specification. |