P2138 Rules of Design <=> Wording engagement

[wg21bot]

P2138R0 Rules of Design<=>Wording engagement (Ville Voutilainen)

[wg21bot]

P2138R1 Rules of Design<=>Wording engagement (Ville Voutilainen)

[brycelelbach]

Informative only?

[wg21bot]

P2138R2 Rules of Design<=>Wording engagement (Ville Voutilainen)

[wg21bot]

P2138R3 Rules of Design <=> Specification engagement (Ville Voutilainen)

[wg21bot]

P2138R4 Rules of Design<=>Specification engagement (Ville Voutilainen)

[brycelelbach]

2021-06-14 Joint Library Evolution and Language Evolution Telecon

P2138R4: Rules of Design <=> Specification Engagement

2021-06-14 Joint Library Evolution and Language Evolution Telecon Minutes

Chair: Bryce Adelstein Lelbach

Champion: Ville Voutilainen

Minute Taker: Inbal Levi

Start: 2021-06-14 08:04 Pacific

What does urgent mean?

How will authors find wordsmiths?

This would probably need to be codified in a standing document.

Attendance (self identified as Evolution telecon regulars): 11

Attendance (self identifies as Library Evolution telecon regulars): 12

POLL: Adopt P2138R4 as the official process of the C++ Evolution groups.

Strongly Favor	Weakly Favor	Neutral	Weakly Against	Strongly Against
5	6	6	1	0

Attendance: 24

# of Authors: 1

Author Position: SF

Outcome: Consensus in favor.

Should go to electronic polls next, then possibly plenary.

End: 09:15

Summary

We reviewed P2138R4 (Rules of Design <=> Specification engagement), a paper that proposes formalizing our design and specification process and adding some checks and balances that aim to improve the quality of the International Standard and avoid inefficient uses of committee time. The author of P2138R4 believes much of what this paper proposes is already our defacto process, or what we intend our defacto process to be.

We discussed when exceptions from the process would be needed, such as for urgent work, like NB comment responses or bug fixes. We also talked about whether adopting this proposal would increase the burden on proposal authors and increase the amount of time that it takes for proposals to land, and whether that was a bug or a feature.

P2138R4 asks proposal authors to find a wordsmith for both Evolution and Library Evolution proposals. We talked about the challenges associated with this. How will authors know who wordsmiths are? Will we have a sufficient quantity of wordsmiths volunteering to help authors? Will wordsmiths become a bottleneck?

We also discussed the need to document these changes to our process if they are adopted, in either a standing document or the existing documentation on isocpp.org.

Outcome

We had consensus on the telecon that we should adopt P2138R4 as the official process of the C++ Evolution groups. The paper will go to Library Evolution electronic polls as a next step.