-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Restructure the evolution process documentation #2953
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
new world of multiple evolution workgroups with slightly different processes.
guidelines, and describe a new lightweight review process that combines the pitch and review stages.
b4e8d8c
to
7f452d9
Compare
to be a little clearer. Make it clear that lightweight review should only be used with approval from a steering group or the Core Team. Update a few other sections in response to the introduction of lightweight review.
I copied this from the existing document, which apparently never got updated.
through constructive criticism and, eventually, determine the | ||
direction of Swift. When writing your review, here are some questions | ||
you might want to answer in your review: | ||
Language and standard library proposals use full evolution review. They are pitched in the [Evolution > Pitches][forum-pitches] section of the Swift forums and reviewed in the [Evolution > Proposal Reviews][forums-reviews] section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: here and few other places below need to be fixed to use “forums-pitches”.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there's one small formatting issue outstanding (#2953 (comment)) but broadly speaking this is a great improvement to the process docs, thanks!
The focus of this change is on (1) generally fixing and improving the documentation and (2) making room for a "lightweight", less structured review process. I am specifically trying to avoid resolving questions like whether SPM proposals should be part of the SE namespace and whether all evolution reviews should share a common category on the forums. The goal there is to document the current evolution process; if an evolution workgroup changes its practice in the future, editing this file will be the way it officially documents its new process.
Summary of changes: