From 41cb4d2459d97348262441715c79c1b7cd4b6bc6 Mon Sep 17 00:00:00 2001
From: David Choi <dchoi27@gmail.com>
Date: Fri, 25 Jun 2021 16:19:53 -0700
Subject: [PATCH 1/2] Create nitro-m1-metrics

---
 proposals/nitro-m1-metrics | 44 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 44 insertions(+)
 create mode 100644 proposals/nitro-m1-metrics

diff --git a/proposals/nitro-m1-metrics b/proposals/nitro-m1-metrics
new file mode 100644
index 00000000..cfd24a13
--- /dev/null
+++ b/proposals/nitro-m1-metrics
@@ -0,0 +1,44 @@
+# [project name here] 
+
+Authors: <!-- List authors' GitHub or other handles -->
+
+<!--
+This minimal project pitch (MPP) template is for a proposal/brief/pitch for a significant project to be undertaken by a Web3 Dev project team.
+The goal of project proposals is to help us decide which work to take on, which things are more valuable than other things.
+-->
+<!--
+A minimal project pitch (MPP) should contain enough detail for others to understand what problem this project solves and why this is important for our
+team's goal of achieving product-market fit, a high-level description of what the idea/proposed solution is, and space to add more detailed technical 
+design and planning information as we develop this information.
+
+The MPP itself does not need to describe the work, technical design, scope, and project plan in much detail.
+
+Projects can include work for major programs (such as Bedrock and Nitro), but they can focus on other areas, e.g. refactors for future capability, 
+improving our testing infrastructure, testing and validation, and other engineering-oriented projects.
+-->
+<!--
+For ease of discussion in PRs, consider breaking lines after every sentence or long phrase.
+-->
+
+## What is the problem this project solves?
+_Describe the status quo, including any relevant context on the problem you're seeing that this project should solve. Who is the user you're solving for, and why do they care about this problem? Wherever possible, include pain points or problems that you've seen users experience to help motivate why solving this problem works towards top-line objectives._ 
+- Tracking success metrics of Nitro for M1 and more generally so we know how we're doing as a program
+
+## Impact
+_What goals/OKRs are being addressed (for w3dt, a specific program, etc.)? Why is this project important? What do we get with this project that we can't get without it?_
+- Can't know how we're doing without tracking the metrics
+
+## The idea
+_Describe the proposed project solution, at a very high level. Stay at the level of the high-level requirements. Diagrams and interface descriptions can be useful, if you have any that help clarify and explain the idea._
+- Identify, implement, and dashboard metrics that summarize how we're doing with Nitro - most relevantly in M1 (e.g., web3.storage adoption metrics)
+
+## Success/acceptance criteria (optional)
+_How do we know we're done with this project? How do we know we're successful? This field is OPTIONAL for the first draft of an MPP. Sometimes this field needs to be filled out once we have more detail on the shape of the actual solution._
+- Dashboard that reflects reality of how things are going, and gives us actionable insights
+
+## Detailed plans (optional)
+_Link to more detailed project plans, e.g. product requirements documents (PRDs) and technical design docs, once they have been created for this project._
+
+## Program (optional)
+_If this project is part of a program, please indicate the relevant program here._
+Nitro

From 3f690b619999bfcb0974340046750a0f6adc90ed Mon Sep 17 00:00:00 2001
From: David Choi <dchoi27@gmail.com>
Date: Mon, 9 Aug 2021 10:45:06 -0700
Subject: [PATCH 2/2] Update and rename nitro-m1-metrics to nitro-metrics

---
 proposals/{nitro-m1-metrics => nitro-metrics} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename proposals/{nitro-m1-metrics => nitro-metrics} (93%)

diff --git a/proposals/nitro-m1-metrics b/proposals/nitro-metrics
similarity index 93%
rename from proposals/nitro-m1-metrics
rename to proposals/nitro-metrics
index cfd24a13..3ea4a6fa 100644
--- a/proposals/nitro-m1-metrics
+++ b/proposals/nitro-metrics
@@ -22,7 +22,7 @@ For ease of discussion in PRs, consider breaking lines after every sentence or l
 
 ## What is the problem this project solves?
 _Describe the status quo, including any relevant context on the problem you're seeing that this project should solve. Who is the user you're solving for, and why do they care about this problem? Wherever possible, include pain points or problems that you've seen users experience to help motivate why solving this problem works towards top-line objectives._ 
-- Tracking success metrics of Nitro for M1 and more generally so we know how we're doing as a program
+- Tracking success metrics of Nitro so we know how we're doing as a program
 
 ## Impact
 _What goals/OKRs are being addressed (for w3dt, a specific program, etc.)? Why is this project important? What do we get with this project that we can't get without it?_
@@ -30,7 +30,7 @@ _What goals/OKRs are being addressed (for w3dt, a specific program, etc.)? Why i
 
 ## The idea
 _Describe the proposed project solution, at a very high level. Stay at the level of the high-level requirements. Diagrams and interface descriptions can be useful, if you have any that help clarify and explain the idea._
-- Identify, implement, and dashboard metrics that summarize how we're doing with Nitro - most relevantly in M1 (e.g., web3.storage adoption metrics)
+- Identify, implement, and dashboard metrics that summarize how we're doing with Nitro
 
 ## Success/acceptance criteria (optional)
 _How do we know we're done with this project? How do we know we're successful? This field is OPTIONAL for the first draft of an MPP. Sometimes this field needs to be filled out once we have more detail on the shape of the actual solution._