From 7bf5232aaf7ba1f6a615c5e4526c177aebfbeee2 Mon Sep 17 00:00:00 2001 From: Joaquin Date: Wed, 25 Sep 2024 18:59:25 -0700 Subject: [PATCH 1/7] update to feedback template based on FinOps staff discussion --- .github/ISSUE_TEMPLATE/feedback.yml | 65 +++++++++++++++++++++++++---- 1 file changed, 57 insertions(+), 8 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/feedback.yml b/.github/ISSUE_TEMPLATE/feedback.yml index 1ab51c5c0..5a9c9fd7d 100644 --- a/.github/ISSUE_TEMPLATE/feedback.yml +++ b/.github/ISSUE_TEMPLATE/feedback.yml @@ -1,12 +1,12 @@ -name: FinOps Use Case Feedback -description: Provide feedback on FinOps use cases that cannot be performed with the current FOCUS specification. +name: Feature Request and Use Case Feedback +description: Provide feedback on use cases or feature requests that cannot be performed with the current FOCUS specification. These may include FinOps-specific scenarios or other areas where the specification falls short. Your input will help prioritize improvements for upcoming releases. Please avoid sharing any information that may be considered Intellectual Property by any individual or organization. title: "[FEEDBACK]: " -labels: [""] -assignees: ["mike-finopsorg,udam-f2"] +labels: ["use case"] +assignees: ["salpaysenturus, udam-f2, jpradocueva,"] body: - type: markdown attributes: - value: "The FOCUS working group wants to understand what FinOps use cases cannot be performed today using the current specification so they can be prioritized for upcoming release. Please do not provide any information that may be considered Intellectual Property by any individual or organization." + value: "The FOCUS working group aims to identify gaps in the current specification, both for FinOps-related use cases and broader areas. We are interested in understanding which use cases or features cannot be supported by the current specification so they can be prioritized for future releases. Please do not include any information that may be regarded as Intellectual Property." - type: input attributes: @@ -18,8 +18,8 @@ body: - type: textarea attributes: - label: What FinOps use cases cannot be performed without the proposed change? - description: Describe in detail the current FinOps use cases your organization cannot perform without the proposed change + label: What use cases, FinOps or others, can't be performed with the current specification without this change? + description: Describe in detail the use cases, whether FinOps-related or otherwise, that your organization cannot perform with the current specification without the proposed change. validations: required: true @@ -51,6 +51,55 @@ body: validations: required: true + - type: textarea + attributes: + label: Business and Financial Objectives + description: Describe the business and financial objectives this use case aims to achieve. + placeholder: Describe the expected business and financial outcomes. + validations: + required: false + + - type: input + attributes: + label: Cost Drivers + description: Identify the primary cost drivers related to this use case (e.g., cloud spending, infrastructure costs). + placeholder: e.g., cloud spending, infrastructure costs, etc. + validations: + required: false + + - type: textarea + attributes: + label: Key Metrics and KPIs + description: List the metrics and KPIs that will measure the success of this use case (e.g., cost per service, spend reduction percentage). + placeholder: e.g., cost per service, spend reduction percentage, etc. + validations: + required: false + + - type: input + attributes: + label: Expected Financial Impact + description: Quantify the expected financial impact, if applicable (e.g., percentage cost savings, budget reductions). + placeholder: e.g., 10% cost savings, 5% budget reduction, etc. + validations: + required: false + + - type: textarea + attributes: + label: Testing Approach + description: Outline how the use case will be tested before full implementation. Specify the types of testing (e.g., pilot testing, A/B testing). + placeholder: Describe your testing approach. + validations: + required: false + + - type: textarea + attributes: + label: Validation Criteria + description: Define how success will be validated after implementation. Include metrics that will be reviewed post-implementation. + placeholder: e.g., metrics to validate success, financial impact, etc. + validations: + required: false + + - type: textarea attributes: label: Context / Supporting information @@ -65,5 +114,5 @@ body: description: Provide relevant sample data or data extracts that support your feedback. Ensure data is anonymized and does not include sensitive or proprietary information. placeholder: Attach sample data or data extracts here. Ensure compliance with data privacy guidelines. validations: - required: false + required: true From b546c5031a456f870303f3d6cbf8e5ca191b1a6c Mon Sep 17 00:00:00 2001 From: Joaquin Date: Wed, 25 Sep 2024 19:10:31 -0700 Subject: [PATCH 2/7] reduce descriptions below 200 characters --- .github/ISSUE_TEMPLATE/feedback.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/feedback.yml b/.github/ISSUE_TEMPLATE/feedback.yml index 5a9c9fd7d..dc90c611c 100644 --- a/.github/ISSUE_TEMPLATE/feedback.yml +++ b/.github/ISSUE_TEMPLATE/feedback.yml @@ -1,12 +1,12 @@ name: Feature Request and Use Case Feedback -description: Provide feedback on use cases or feature requests that cannot be performed with the current FOCUS specification. These may include FinOps-specific scenarios or other areas where the specification falls short. Your input will help prioritize improvements for upcoming releases. Please avoid sharing any information that may be considered Intellectual Property by any individual or organization. +description: Provide feedback on unsupported use cases or features in the FOCUS specification, including FinOps scenarios, to help prioritize updates. Avoid sharing proprietary information. title: "[FEEDBACK]: " labels: ["use case"] assignees: ["salpaysenturus, udam-f2, jpradocueva,"] body: - type: markdown attributes: - value: "The FOCUS working group aims to identify gaps in the current specification, both for FinOps-related use cases and broader areas. We are interested in understanding which use cases or features cannot be supported by the current specification so they can be prioritized for future releases. Please do not include any information that may be regarded as Intellectual Property." + value: "FOCUS working group seeks gaps in the current specification for FinOps and beyond. Share unsupported use cases or features to prioritize updates. Avoid sharing proprietary information." - type: input attributes: From 514858f13d0a4ab91e6e68569a0588c40c83d52a Mon Sep 17 00:00:00 2001 From: Joaquin Date: Mon, 30 Sep 2024 11:04:37 -0700 Subject: [PATCH 3/7] Update .github/ISSUE_TEMPLATE/feedback.yml --- .github/ISSUE_TEMPLATE/feedback.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/feedback.yml b/.github/ISSUE_TEMPLATE/feedback.yml index dc90c611c..c6a752839 100644 --- a/.github/ISSUE_TEMPLATE/feedback.yml +++ b/.github/ISSUE_TEMPLATE/feedback.yml @@ -2,7 +2,7 @@ name: Feature Request and Use Case Feedback description: Provide feedback on unsupported use cases or features in the FOCUS specification, including FinOps scenarios, to help prioritize updates. Avoid sharing proprietary information. title: "[FEEDBACK]: " labels: ["use case"] -assignees: ["salpaysenturus, udam-f2, jpradocueva,"] +assignees: ["shawnalpay, udam-f2, jpradocueva,"] body: - type: markdown attributes: From ee12620d1808ed70b02ec7fce163995427980851 Mon Sep 17 00:00:00 2001 From: Joaquin Date: Tue, 8 Oct 2024 17:00:05 -0700 Subject: [PATCH 4/7] remove udam --- .github/ISSUE_TEMPLATE/feedback.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/feedback.yml b/.github/ISSUE_TEMPLATE/feedback.yml index c6a752839..193884cf4 100644 --- a/.github/ISSUE_TEMPLATE/feedback.yml +++ b/.github/ISSUE_TEMPLATE/feedback.yml @@ -2,7 +2,7 @@ name: Feature Request and Use Case Feedback description: Provide feedback on unsupported use cases or features in the FOCUS specification, including FinOps scenarios, to help prioritize updates. Avoid sharing proprietary information. title: "[FEEDBACK]: " labels: ["use case"] -assignees: ["shawnalpay, udam-f2, jpradocueva,"] +assignees: ["shawnalpay, jpradocueva,"] body: - type: markdown attributes: From 93376e4fdb70c978c0691631a4ff62a5ea20c829 Mon Sep 17 00:00:00 2001 From: Joaquin Date: Tue, 8 Oct 2024 17:04:23 -0700 Subject: [PATCH 5/7] updates to feedback --- .github/ISSUE_TEMPLATE/feedback.yml | 42 ----------------------------- 1 file changed, 42 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/feedback.yml b/.github/ISSUE_TEMPLATE/feedback.yml index 193884cf4..d171f4f9d 100644 --- a/.github/ISSUE_TEMPLATE/feedback.yml +++ b/.github/ISSUE_TEMPLATE/feedback.yml @@ -51,22 +51,6 @@ body: validations: required: true - - type: textarea - attributes: - label: Business and Financial Objectives - description: Describe the business and financial objectives this use case aims to achieve. - placeholder: Describe the expected business and financial outcomes. - validations: - required: false - - - type: input - attributes: - label: Cost Drivers - description: Identify the primary cost drivers related to this use case (e.g., cloud spending, infrastructure costs). - placeholder: e.g., cloud spending, infrastructure costs, etc. - validations: - required: false - - type: textarea attributes: label: Key Metrics and KPIs @@ -75,31 +59,6 @@ body: validations: required: false - - type: input - attributes: - label: Expected Financial Impact - description: Quantify the expected financial impact, if applicable (e.g., percentage cost savings, budget reductions). - placeholder: e.g., 10% cost savings, 5% budget reduction, etc. - validations: - required: false - - - type: textarea - attributes: - label: Testing Approach - description: Outline how the use case will be tested before full implementation. Specify the types of testing (e.g., pilot testing, A/B testing). - placeholder: Describe your testing approach. - validations: - required: false - - - type: textarea - attributes: - label: Validation Criteria - description: Define how success will be validated after implementation. Include metrics that will be reviewed post-implementation. - placeholder: e.g., metrics to validate success, financial impact, etc. - validations: - required: false - - - type: textarea attributes: label: Context / Supporting information @@ -115,4 +74,3 @@ body: placeholder: Attach sample data or data extracts here. Ensure compliance with data privacy guidelines. validations: required: true - From e462d1f5232d4356503a929a12d4b1ab4c951617 Mon Sep 17 00:00:00 2001 From: Joaquin Date: Tue, 8 Oct 2024 17:08:55 -0700 Subject: [PATCH 6/7] updates to feedback --- .github/ISSUE_TEMPLATE/feedback.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/feedback.yml b/.github/ISSUE_TEMPLATE/feedback.yml index d171f4f9d..c2f314ade 100644 --- a/.github/ISSUE_TEMPLATE/feedback.yml +++ b/.github/ISSUE_TEMPLATE/feedback.yml @@ -8,7 +8,7 @@ body: attributes: value: "FOCUS working group seeks gaps in the current specification for FinOps and beyond. Share unsupported use cases or features to prioritize updates. Avoid sharing proprietary information." - - type: input + - type: textarea attributes: label: Proposed Change description: Short description of the change and why it is necessary. From 0f77f16ba1003cb9912a70815903d36250121ae2 Mon Sep 17 00:00:00 2001 From: Joaquin Date: Thu, 10 Oct 2024 12:10:59 -0700 Subject: [PATCH 7/7] Update .github/ISSUE_TEMPLATE/feedback.yml --- .github/ISSUE_TEMPLATE/feedback.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/feedback.yml b/.github/ISSUE_TEMPLATE/feedback.yml index c2f314ade..656903ca8 100644 --- a/.github/ISSUE_TEMPLATE/feedback.yml +++ b/.github/ISSUE_TEMPLATE/feedback.yml @@ -73,4 +73,4 @@ body: description: Provide relevant sample data or data extracts that support your feedback. Ensure data is anonymized and does not include sensitive or proprietary information. placeholder: Attach sample data or data extracts here. Ensure compliance with data privacy guidelines. validations: - required: true + required: false