Determine how to ask the questions we want to ask during the tech preview

[Eemeli Aro]

At least #602 and #603 (comment) discuss specific feedback we're interested in getting while MF2 is in tech preview.

We should figure out how to ask such questions in general, and what the timing might be about getting responses so that they can be taken into account should they suggest some changed be made to MF2 from its LDML45 release.

[Addison Phillips]

Agreed. I have some ideas for how to do this. I think this will be one topic for the virtual face-to-face or even post F2F (so late February/early March timeframe).

In particular:

• update our repo README.md to have explicit status and instructions for feedback
• specific text in the spec itself relating to the tech preview status (with instructions for feedback)

In general, I think we'd prefer issues, but we might also use Unicode's PRI mechanism for general feedback. We will also explicitly ask for some (you and I have discussed W3C TAG, for example)

[Martin Dürst]

On 2024-01-22 04:41, Addison Phillips wrote: Agreed. I have some ideas for how to do this. I think this will be one topic for the virtual face-to-face or even post F2F (so late February/early March timeframe). In particular: - update our repo README.md to have explicit status and instructions for feedback - specific text in the spec itself relating to the tech preview status (with instructions for feedback) In general, I think we'd prefer issues, but we might also use Unicode's PRI mechanism for general feedback.

I guess the ideal would be to put things out as PRIs so that we can get feedback from the community that looks at PRIs, but to direct feedback back to github issues. Regards, Martin.

…

We will also explicitly ask for some (you and I have discussed W3C TAG, for example)

[Addison Phillips]

Note that the label Seek-Feedback-in-Preview is being used to track items of particular interest during the tech preview.