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.

Sign up for GitHub

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

Jump to bottom

RFC: Label RFCs With Spec #108

Merged
merged 5 commits into from
Sep 9, 2020
Merged

RFC: Label RFCs With Spec #108

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
161fadb
RFC to label RFCs
ForestEckhardt Aug 14, 2020
35e58b1
Apply suggestions from code review
ForestEckhardt Aug 17, 2020
c5968a6
Adds target audience as tag as well as adding a process for tagging RFCs
ForestEckhardt Aug 24, 2020
83dbff5
RFCs will be labeled during weekly RFC review
ForestEckhardt Aug 27, 2020
c3f1e39
Update text/0000-label-rfcs.md
ForestEckhardt Sep 3, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
35 changes: 35 additions & 0 deletions text/0000-label-rfcs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# Meta
[meta]: #meta
- Name: Label RFCs With Specification And Target Audience
- 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 labeling RFCs with a label that indicates which part
of the specification (i.e. Buildpack Interface, Distribution, Platform
Interface) is being affected as well as a label to indicate the target audience
(i.e. Buildpack Authors, CNB Contributors, Platform Operators) of the change.

# Motivation
[motivation]: #motivation

Indicating which part of the specification the RFC is purposing to update or
modify will make the RFC more discoverable because it will allow people to
focus in on certain RFCs that effect them. This means that potentially effected
ForestEckhardt marked this conversation as resolved.
Show resolved Hide resolved
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.

# Implementation
[Implementation]: #implementation

During any Working Group meeting, when a new RFC is brought up it should at
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we try to do this during the weekly review of RFCs or would that bog that process down too much? Thoughts @sclevine?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the WG: we should be able to handle this as we go through the RFCs every week if you want to update @ForestEckhardt

Copy link
Contributor Author

@ForestEckhardt ForestEckhardt Aug 27, 2020 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hone Sounds good to me. I will update this when I get the chance.

that time be labeled with what part of the specification it affects as well the
target audience.
27 changes: 0 additions & 27 deletions text/0000-tag-rfcs.md
View file
Open in desktop

This file was deleted.