PEP 458: Final Reviewer Edits

[vladimir-v-diaz]

@dstufft @r1chardj0n3s

I edited and made pull requests to add all of the text, images, and modifications I felt were still needed in the draft. All that remains is for pull requests #20 and #17 to be reviewed and merged, and for Donald to incorporate his edits; he can review the draft for technical issues and add any text he feels is missing.

Things to review:

• Finalize section "Appendix C: PEP 470 and Projects Hosted Externally". It lists options for how to handle externally hosted projects, but we need to clearly choose one method.
• Anticipate the problems that may crop up while implementing PEP 458. (Is the mirror protocol good enough? CDN Purging?)
• Ensure PEP 458 provides enough flexibility so that PEP 480 does not require major changes.
• PEP 458 has relied on referencing the TUF white paper and spec to get a grasp of what’s going on. Ensure this is no longer the case.
• PEP 458 reads more like suggestions about how we might go about implementing TUF rather than an actionable plan for implementing TUF.
• Clearly state the impact of PEP 458 without having to go through and understand the intricacies of TUF or how PEP 458 integrates TUF.

[vladimir-v-diaz]

Changed Remaining Issues: to Things to review: Hopefully there shouldn't be much left to include, mostly finalization of sections / text that read more like suggestions.

[dstufft]

I plan on digging into this in the near future fwiw.