How to give actionable feedback on a proposal

[littledan]

Online and in person at TC39 meetings, we're always giving feedback on proposals. There are some best practices here that would be nice to document (maybe people disagree with me on these points.:

• Whenever possible, give feedback ahead of a TC39 meeting in issues on the GitHub repository for the proposal. Search for existing issues which cover a topic before posting a new topic. It's helpful to give positive feedback, or feedback agreeing with a previous critique, as well as new points.
• Feedback which is given in channels outside of GitHub and meeting discussions is more likely to be lost.
• When in meetings, use the queue tool rather than interrupting the presentation to make a point.
• Follow the code of conduct in all proposal feedback
• Keep feedback respectful, constructive and actionable.
• When you see a problem, explain the problem as much as possible, and avoid jumping to a particular solution.
• When you don't understand the motivation for a part of a proposal, one good strategy is to ask a question about it.
• We're all coming from different perspectives and have partial knowledge of the universe. Give your feedback from wherever you're at. For example, there is no need to dress up feedback in formal language if your thought process doesn't correspond to that.

It would be good to explain how the champion group is responsible for carefully considering the sum of all feedback and making a recommendation to the committee taking this into account. Champions will not always be able to find absolute consensus among everyone who voices an opinion, but they will listen carefully.

Would anyone be interested in writing up this sort of documentation? We may end up having multiple documents, for committee delegates and online contributions.