From 99785579cd98b92403d3c661129b65bc14ce0cf1 Mon Sep 17 00:00:00 2001 From: Alexander Hentschel Date: Fri, 1 Nov 2024 14:49:53 -0700 Subject: [PATCH 1/2] =?UTF-8?q?updated=20main=20readme:=20=E2=80=A2=20remo?= =?UTF-8?q?ve=20the=20mentioning=20of=20"All=20NEW=20FLIPs=20are=20numbere?= =?UTF-8?q?d=20by=20the=20PR=20number=20submitted."=20which=20is=20no=20lo?= =?UTF-8?q?nger=20correct=20=E2=80=A2=20explained=20the=20motivation=20beh?= =?UTF-8?q?ind=20creating=20an=20issue=20first?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2f8a1fc2..41d05a65 100644 --- a/README.md +++ b/README.md @@ -81,6 +81,8 @@ will solve it. Specifically, the FLIP will: * be formatted according to the FLIP template * be submitted as a pull request * be subject to thorough community discussion and review prior to acceptance or rejection +* for ease of tracking open flips that are currently in the process of discussion and refinement or implementation, we have a dedicated issue for each FLIP, + which is closed when the flip reaches either the `Rejected` or `Released` stage (no further updates to the FLIP) ## FLIP process @@ -102,9 +104,11 @@ Once the FLIP is ready for review: 2. Create an [issue](https://github.com/onflow/flips/issues/new/choose) by using one of the FLIP issue templates based on the type of the FLIP - `application`, `governance`, `cadence` or `protocol`. The title of the issue should be the title of your FLIP, e.g., "Dynamic Inclusion fees". - Submit the issue. + Then submit the issue and note the issue number that gets assigned. For example, for issue https://github.com/onflow/flips/issues/166, the issue number is `166`. - Note the issue number that gets assigned. For example, for issue https://github.com/onflow/flips/issues/76, the issue number is `76`. + Comment: + The reason we are creating an issue first is to track the progress of the various flips that are currently under discussion, refinement or being implemented. + Hence, from looking at the open https://github.com/onflow/flips/issues you get a concise overview of all FLIPs that you can contribute to, either to helping to refine proposal or contribute to its implementation. 3. Create your FLIP as a pull request to this repository ([`onflow/flips`](https://github.com/onflow/flips)). From 1634a5b654c1e6607a12723fea9aa0bbfc3415f9 Mon Sep 17 00:00:00 2001 From: Alexander Hentschel Date: Fri, 1 Nov 2024 15:18:53 -0700 Subject: [PATCH 2/2] status definition should be "draft" not drafted --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 41d05a65..6e629c1f 100644 --- a/README.md +++ b/README.md @@ -159,7 +159,7 @@ the [community forum](https://forum.onflow.org/), or file an issue in this repos ([`onflow/flow`](https://github.com/onflow/flow/issues)). ## Proposal states -* **Drafted:** The FLIP is in its early stage and is being ideated. +* **Draft:** The FLIP is in its early stage and is being ideated. * **Proposed:** The FLIP has been proposed and is awaiting review. * **Rejected:** The FLIP has been reviewed and rejected. * **Accepted:** The FLIP has been accepted and is either awaiting implementation or is actively being implemented.