Advice for Proposal Authors during "Awaiting review"?

Hi! Does anyone have some advice for proposal authors to help move their proposal through to "Scheduled for review"? I'm following through the advice in Swift Evolution Process:

Once you have a working implementation and believe the proposal is sufficiently detailed and clear, mark the draft pull request in the swift-evolution repository as ready for review to indicate to the appropriate evolution workgroup that you would like the proposal to be reviewed.

It looks like the review process begins:

when a member of the appropriate evolution workgroup accepts a pull request of a new or updated proposal into the swift-evolution repository. That member becomes the review manager for the proposal. The proposal is assigned a proposal number (if it is a new proposal), and then enters the review queue.

My question then is what about that in-between phase? After a proposal diff is ready for review with basic implementations attached… is there anything left for the proposal authors to do before a review manager begins the process?

To put it another way: is it normally encouraged for proposal authors to "recruit" a review manager? Is it encouraged for proposal authors to message engineers from LSG directly if they think the proposal fits in with their area of focus?

Any more advice about that? Thanks!

No, you shouldn't try to recruit a review manager, that's not how that works. If you think your proposal is ready for review and it's been sitting idle for a few weeks, please feel free to ping someone from the appropriate evolution workgroup (e.g. the LSG for a language or stdlib proposal).

2 Likes