I feel like this was prematurely moved from the pitch phase to the review phase when a critical piece of feedback was given and not addressed (still isn't in the current proposal):
What is your evaluation of the proposal?
In general I'm +1, but we should address the point above.
Is the problem being addressed significant enough to warrant a change to Swift?
This provides a foundation of interacting with more authoritative sources like a registry or central index to aid in the real problem of discoverability of packages.
Does this proposal fit well with the feel and direction of Swift?
SwiftPM has had a direct intention of being decentralized as much as possible and this continues in that philosophy.
If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
NPM in the JavaScript world and NuGet in C# have a concept of providing additional registries when searching and interacting with the tool aside from the central authority.
This is very similar, but without a default central authority.
How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
I read through the original pitch and participated in its discussion.