Skip to content

Commit

Permalink
RFC to label RFCs
Browse files Browse the repository at this point in the history
Signed-off-by: Forest Eckhardt <feckhardt@pivotal.io>
  • Loading branch information
ForestEckhardt committed Aug 14, 2020
1 parent 80b13ec commit 161fadb
Showing 1 changed file with 27 additions and 0 deletions.
27 changes: 27 additions & 0 deletions text/0000-tag-rfcs.md
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.

0 comments on commit 161fadb

Please sign in to comment.