Add an Investigation Effort Proposal template (#130)

This completes the public documentation for Interop 2023 proposals.

Author: foolip

.github/ISSUE_TEMPLATE/proposal.yml renamed to .github/ISSUE_TEMPLATE/focus-area-proposal.yml

@@ -1,19 +1,29 @@
-name: Proposal
-description: Proposal for feature to include in Interop 2023
-labels: proposal
+name: Focus Area Proposal
+description: Proposal for an Interop 2023 Focus Area
+labels: focus-area-proposal
 body:
 - type: markdown
   attributes:
     value: |
-      **Interop 2023 has not yet launched and this documentation is still being finalized. Please do not submit proposals yet.**
- 
       Thanks for taking the time to make a proposal for Interop 2023!
 
       Please see the [Interop 2023 README](https://github.com/web-platform-tests/interop/blob/main/2023/README.md) for the timeline and what to expect from the process.
+
+      If this feature is widely implemented, but lacks a high quality specification or tests, an [Investigation Effort](https://github.com/web-platform-tests/interop/issues/new?template=investigation-effort-proposal.yml) may be more appropriate.
 - type: textarea
   attributes:
     label: Description
     description: Brief description of the feature. Try to be clear about what parts of the feature are included and not.
+- type: textarea
+  attributes:
+    label: Rationale
+    description: |
+      Reasons for including the feature. A few dimensions to consider are:
+
+      - Web developer sentiment from polls or surveys, for example, [MDN surveys](https://insights.developer.mozilla.org/) or [State of CSS](https://stateofcss.com/).
+      - Examples of sites or libraries working around a missing feature or browser bug.
+      - Browser bugs or browser bug statistics, for example, [Chromium](https://bugs.chromium.org/), [Gecko](https://bugzilla.mozilla.org/),  or [WebKit](https://bugs.webkit.org/).
+      - Current usage of the feature, for example, [Chrome use counters](https://www.chromestatus.com/metrics/feature/popularity) or [HTTP Archive](https://httparchive.org/).
 - type: textarea
   attributes:
     label: Specification
@@ -28,14 +38,7 @@ body:
 - type: textarea
   attributes:
     label: Tests
-    description: Tests for the feature in web-platform-tests on [wpt.fyi](https://wpt.fyi/), or in Test262 on [test262.report](https://test262.report/).
-- type: textarea
-  attributes:
-    label: Rationale
     description: |
-      Reasons for including the feature. A few dimensions to consider are:
+      Tests for the feature in web-platform-tests on [wpt.fyi](https://wpt.fyi/), or in Test262 on [test262.report](https://test262.report/).
 
-      - Web developer sentiment from polls or surveys, for example, [MDN surveys](https://insights.developer.mozilla.org/) or [State of CSS](https://stateofcss.com/).
-      - Examples of sites or libraries working around a missing feature or browser bug.
-      - Browser bugs or browser bug statistics, for example, [Chromium](https://bugs.chromium.org/), [Gecko](https://bugzilla.mozilla.org/),  or [WebKit](https://bugs.webkit.org/).
-      - Current usage of the feature, for example, [Chrome use counters](https://www.chromestatus.com/metrics/feature/popularity) or [HTTP Archive](https://httparchive.org/).
+      These are the tests that will be used to score progress in this Focus Area.

.github/ISSUE_TEMPLATE/investigation-effort-proposal.yml

@@ -0,0 +1,33 @@
+name: Investigation Effort Proposal
+description: Proposal for an Interop 2023 Investigation Effort
+labels: investigation-effort-proposal
+body:
+- type: markdown
+  attributes:
+    value: |
+      Thanks for taking the time to make a proposal for Interop 2023!
+
+      Please see the [Interop 2023 README](https://github.com/web-platform-tests/interop/blob/main/2023/README.md) for the timeline and what to expect from the process.
+
+      **Please make sure you're using the right proposal template!** If this feature has a high quality specification and tests, submit a [Focus Area](https://github.com/web-platform-tests/interop/issues/new?template=focus-area-proposal.yml) proposal instead.
+- type: textarea
+  attributes:
+    label: Description
+    description: Brief description of the feature. Try to be clear about what parts of the feature are included and not.
+- type: textarea
+  attributes:
+    label: Rationale
+    description: |
+      Reasons for including the feature. A few dimensions to consider are:
+
+      - Web developer sentiment from polls or surveys, for example, [MDN surveys](https://insights.developer.mozilla.org/) or [State of CSS](https://stateofcss.com/).
+      - Examples of sites or libraries working around a missing feature or browser bug.
+      - Browser bugs or browser bug statistics, for example, [Chromium](https://bugs.chromium.org/), [Gecko](https://bugzilla.mozilla.org/),  or [WebKit](https://bugs.webkit.org/).
+      - Current usage of the feature, for example, [Chrome use counters](https://www.chromestatus.com/metrics/feature/popularity) or [HTTP Archive](https://httparchive.org/).
+- type: textarea
+  attributes:
+    label: Investigation Roadmap
+    description: |
+      Please describe the steps necessary to get this feature to a state of high quality specification and tests. Link to existing spec and tests, and describe what needs to be done, ideally as a set of distinct tasks. If there are open-ended questions about the behavior that require investigation, try to still capture this as a set of tasks, such as "test existing behavior", "update specification", and "update tests".
+
+      Any standards work must be done in the appropriate standards group, and those doing the work need to join those groups. Interop 2023 is not a venue for specifying new features.

2023/README.md

@@ -1,7 +1,5 @@
 # Interop 2023
 
-**Interop 2023 has not yet launched and this documentation is still being finalized. Please do not submit proposals yet.**
-
 Interop 2023 aims to make the web more interoperable in key areas, prioritized by web developer and user needs. The team is formed of browser vendors and other contributors to the web platform, and is part of [the web-platform-tests project](https://github.com/web-platform-tests/wpt).
 
 Similar to [Interop 2022](https://wpt.fyi/interop-2022), this will be a public metric based on the progress of selected focus areas and investigation efforts. The overall timeline for the planning process is:
@@ -15,19 +13,20 @@ If you would like to make a proposal or contribute in other ways, read on.
 
 ## Making a proposal
 
-**Interop 2023 has not yet launched and this documentation is still being finalized. Please do not submit proposals yet.**
-
 If you've had problems using a feature on the web because of differences between browsers, or because it isn't implemented in all browsers, it may be a good proposal for Interop 2023!
 
 Before making a proposal, here's what to expect:
 
-- Only features which have high quality specifications and tests are in scope. Interop 2023 is not a venue for specifying new features; that work happens in working groups within organizations such as W3C and WHATWG.
+- There are two kinds of proposals:
+  - **Focus Area**: Most proposals should fall into the category, where the goal is for browsers to pass a set of tests for a feature. Only features which have high quality specifications and tests are in scope.
+  - **Investigation Effort**: If a feature is widely implemented, but lacks a high quality specification or tests, an investigation effort may be appropriate. An investigation efforts consists of a set of tasks that will bring the feature up to the bar required for a Focus Area in the future. If this involves any standards work, that work must be done in the appropriate standards group, and those doing the work need to join those groups.
+- Interop 2023 is not a venue for specifying new features; that work happens in working groups within organizations such as W3C and WHATWG.
 - Interop 2023 is not a process for making browser vendors work on things they're opposed to. Decisions are made by consensus, so highly contentious features are unlikely to be accepted.
 - Even great proposals may ultimately not be accepted, since we have to prioritize.
 
 The process for making and driving a proposal is:
 
-- **September 15 to October 15**: [File a proposal issue](https://github.com/web-platform-tests/interop/issues/new?labels=proposal&template=proposal.yml) and fill in as many details as you can.
+- **September 15 to October 15**: Submit your [Focus Area](https://github.com/web-platform-tests/interop/issues/new?template=focus-area-proposal.yml) or [Investigation Effort](https://github.com/web-platform-tests/interop/issues/new?template=investigation-effort-proposal.yml) proposal and fill in as many details as you can.
 - **October 16 to October 30**: The Interop team review and discuss proposals. During this time some refinements to the proposal can still be made. After this point no further action is required, but continued participation is certainly welcome, particularly to answer any questions.
 - **November 1 to November 30**: The Interop team decide, by consensus, which proposals to accept. Accepted proposals will require a pull request to document the accepted proposal in the repository. Help with this is appreciated, but not required.
 
@@ -40,7 +39,7 @@ The Interop team is responsible for driving everything after a proposal is accep
   - Finalize test selection.
   - Complete announcement plans. Prepare dashboard for launch.
 - **January 23 to January 27**: Public launch.
-- **Throughout 2023**: Track progress on the public dashboard. If issues with the test suite are found, anyone can make [test change proposals](https://github.com/web-platform-tests/interop/issues/new?assignees=&labels=test-change-proposal&template=test-change-proposal.md), for review by the Interop team. Significant changes to the scope are unlikely to be accepted.
+- **Throughout 2023**: Track progress on the public dashboard. If issues with the test suite are found, anyone can make [test change proposals](https://github.com/web-platform-tests/interop/issues/new?template=test-change-proposal.yml), for review by the Interop team. Significant changes to the scope are unlikely to be accepted.
 
 Ultimately, the outcome we hope for is that interoperability significantly improves, and that web developers and users benefit.