Skip to content
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

RFC: Label RFCs With Spec #108

Merged
merged 5 commits into from
Sep 9, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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 )
ForestEckhardt marked this conversation as resolved.
Show resolved Hide resolved
- Start Date: (2020-08-15)
ForestEckhardt marked this conversation as resolved.
Show resolved Hide resolved
- Author(s): (ForestEckhardt)
ForestEckhardt marked this conversation as resolved.
Show resolved Hide resolved
- 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.