From 161fadb9fef3d188e19edebc7dc9b0393a5afb38 Mon Sep 17 00:00:00 2001 From: Forest Eckhardt Date: Fri, 14 Aug 2020 14:36:31 -0400 Subject: [PATCH 1/5] RFC to label RFCs Signed-off-by: Forest Eckhardt --- text/0000-tag-rfcs.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 text/0000-tag-rfcs.md diff --git a/text/0000-tag-rfcs.md b/text/0000-tag-rfcs.md new file mode 100644 index 000000000..2b89d2d99 --- /dev/null +++ b/text/0000-tag-rfcs.md @@ -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. From 35e58b11a67ff8c4091b0626550450d027ecb25b Mon Sep 17 00:00:00 2001 From: Forest Eckhardt Date: Mon, 17 Aug 2020 17:44:50 -0400 Subject: [PATCH 2/5] Apply suggestions from code review Cleans up meta Co-authored-by: Emily Casey Signed-off-by: Forest Eckhardt --- text/0000-tag-rfcs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/text/0000-tag-rfcs.md b/text/0000-tag-rfcs.md index 2b89d2d99..77951402a 100644 --- a/text/0000-tag-rfcs.md +++ b/text/0000-tag-rfcs.md @@ -1,8 +1,8 @@ # Meta [meta]: #meta -- Name: (Tag RFCs With Specification Label ) -- Start Date: (2020-08-15) -- Author(s): (ForestEckhardt) +- Name: Label RFCs With Specification +- Start Date: 2020-08-15 +- Author(s): ForestEckhardt - RFC Pull Request: (leave blank) - CNB Pull Request: (leave blank) - CNB Issue: (leave blank) From c5968a6ddb0edbbaa184cfbf518e3b843016843c Mon Sep 17 00:00:00 2001 From: Forest Eckhardt Date: Mon, 24 Aug 2020 11:10:03 -0400 Subject: [PATCH 3/5] Adds target audience as tag as well as adding a process for tagging RFCs - Change RFC file name to better reflect what it is actually purposing Signed-off-by: Forest Eckhardt --- text/0000-label-rfcs.md | 35 +++++++++++++++++++++++++++++++++++ text/0000-tag-rfcs.md | 27 --------------------------- 2 files changed, 35 insertions(+), 27 deletions(-) create mode 100644 text/0000-label-rfcs.md delete mode 100644 text/0000-tag-rfcs.md diff --git a/text/0000-label-rfcs.md b/text/0000-label-rfcs.md new file mode 100644 index 000000000..81c0cdbfc --- /dev/null +++ b/text/0000-label-rfcs.md @@ -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 +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 +that time be labeled with what part of the specification it affects as well the +target audience. diff --git a/text/0000-tag-rfcs.md b/text/0000-tag-rfcs.md deleted file mode 100644 index 77951402a..000000000 --- a/text/0000-tag-rfcs.md +++ /dev/null @@ -1,27 +0,0 @@ -# Meta -[meta]: #meta -- Name: Label RFCs With Specification -- 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. From 83dbff588a81ade7fdf19a94ff3cc9f2d93d3bd7 Mon Sep 17 00:00:00 2001 From: Forest Eckhardt Date: Thu, 27 Aug 2020 12:23:16 -0400 Subject: [PATCH 4/5] RFCs will be labeled during weekly RFC review Signed-off-by: Forest Eckhardt --- text/0000-label-rfcs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/text/0000-label-rfcs.md b/text/0000-label-rfcs.md index 81c0cdbfc..3242b8059 100644 --- a/text/0000-label-rfcs.md +++ b/text/0000-label-rfcs.md @@ -30,6 +30,6 @@ 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 -that time be labeled with what part of the specification it affects as well the -target audience. +RFCs should be labeled with what part of the specification it affects as well +the target audience during Working Group meetings while all RFCs are being +reviewed. From c3f1e396080ad1131c0ee96640e8c13ed5d410b2 Mon Sep 17 00:00:00 2001 From: Forest Eckhardt Date: Thu, 3 Sep 2020 09:48:52 -0400 Subject: [PATCH 5/5] Update text/0000-label-rfcs.md Co-authored-by: David Freilich Signed-off-by: Forest Eckhardt