I'm a little disappointed by the very short length of swift-evolution reviews, and I'd like to suggest we do something about it.
In the last day, 4 reviews have started simultaneously:
- SE-0291 (2nd review): Package Collections (until Dec. 7)
- SE-0295: Codable synthesis for enums with associated values (until Dec. 11)
- SE-0293: Extend Property Wrappers to Function and Closure Parameters (until Dec. 13)
- SE-0294: Declaring executable targets in Package Manifests (until Dec. 13)
Firstly: these reviews appear to have started within hours of each other, yet they all end on different days. Is there even a standard duration for evolution reviews?
Secondly: I don't like the pressure this puts me under. We're getting towards the end of the year, when people usually have deadlines or want to push to meet some kind of milestone. It's winter, which means people could easily be out for a week or more with a cold/flu (not to mention the pandemic, which is surging apparently everywhere). With the speed these proposals are moving at, even a week away from the forums could mean you miss some very important proposal (at least 2, possibly 3 of those proposals I would consider "high impact" and I definitely want to take a close look at - but I probably won't get time).
I don't think this kind of "blink and you'll miss it" approach to proposal reviews does this community any favours. Why do these reviews have to be so short?
This has been going on for a while, but so far it hasn't been too bad because the core team has been a little... relaxed about when they actually close a review (e.g. the review for SE-0290 was supposed to conclude on November 17th, but it's 2nd December and there is no announcement; presumably you can still leave feedback). Recently though, I've noticed some proposals really stick to their 7-day window, and it means I've missed the window because I couldn't find time for my actual life and job and to read, research and write a considered review on the proposal. When I did find time, I was literally finishing my response as the review closed before my eyes.
So what to do?
I'd like to propose a different structure: that we publish a monthly collection of proposals, and that those proposals run through the entire month. Any proposals which are ready for review within that time must wait until the next month's publication, along with any revised proposals.
This kind of structure would make it easier for all members of the community to schedule time to read, research and respond to evolution proposals, and give them each the time that they (and the Swift language) deserve. A month-long review might seem at first glance to be a massive expansion of the review period, but it is still a much shorter and simpler process than for other languages, and would not impact the speed with which these features are delivered in stable releases.