Logistics of proposal selection

[foolip]

We're now in the proposal selection period, which is Nov 1–30. In #229 we decided that Nov 17 is the last day for us to share positions. In #240 we discussed how we'll handle these individual positions and how we'll communicate with proposal owners. Different options were discussed and we need to revisit. This issue is to discuss options async to make progress between meetings.

[foolip]

Here's a template for what we could post on accepted:

The proposal review period has now ended, and there was consensus to include this proposal in Interop 2023. The next step will be creating a pull request on this repository to record the final proposal rationale and test list. Help with this is appreciated but of course 100% voluntary.

And for rejected proposals:

The proposal review period has now ended, and unfortunately we did not have consensus to include this proposal in Interop 2023. Reasons given were:

• Unable to prioritize due to lack of resources this year
• Not a top priority for web developers
• Already largely interoperable between browsers
• The web standard for this technology is not yet mature or stable enough
• The testing infrastructure is not capable of testing this technology in a consistent fashion for all three engines, or on needed devices

Participating organizations may share additional details on this issue. Feel free to engage in a discussion about how to make the proposal stronger, if we should revisit this for next year.

Additionally, if we didn't have consensus on the reasons given, we'll add:

Note that this reflects a lack of consensus to include the proposal, not a consensus on the reasons given above.

[foolip]

Interop 2023 has launched, so closing this.