<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 2, 2015, at 11:14 AM, Vladimir Diaz <<a href="mailto:vladimir.v.diaz@gmail.com" class="">vladimir.v.diaz@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class="">Thanks for the great feedback - Nick, Donald, Paul, and Richard (off-list).<br class=""><br class=""></div>I am totally fine with focusing on PEP 458 and applying the final coat of paint on this document.<br class=""><br class=""></div><div class="">There's a lot of background documentation and technical details excluded from the PEPs (to avoid turning the PEP into a 15+ page behemoth), but I do agree that we should explicitly cover some of these implementation details in PEP 458. Subsections on the exact format of metadata, explanation on how metadata is signed, and how the roles are "delegated" with the library, still remain. As Paul as indicated, terminology can also be improved so as to be more readable for "non-experts."<br class=""><br class=""></div><div class="">Let me know how we should collaborate on PEP 458 going forward. Guido van Rossum made minor corrections to PEP 458, and requested we reflect his changes back to the version on Github. We can either move <a href="https://hg.python.org/peps/file/a532493ba99c/pep-0458.txt" class="">hg.python.org/pep/pep-0458.txt</a> to <a href="http://github.com/pypa" class="">github.com/pypa</a> or <a href="http://github.com/theupdateframework/pep-on-pypi-with-tuf" class="">github.com/theupdateframework/pep-on-pypi-with-tuf</a>.<br class=""></div></div></div></blockquote></div><div class=""><br class=""></div><div class="">As far as I’m concerned I’m willing to collab however is best for y’all. It appears you’re doing it on Github in the <a href="https://github.com/theupdateframework/pep-on-pypi-with-tuf" class="">https://github.com/theupdateframework/pep-on-pypi-with-tuf</a> repository so I’m happy to make PRs there. I’m also happy to make PRs elsewhere as well though I prefer somewhere on Github. I’ll sit down with PEP 458 maybe this weekend and see if I can crank out some PRs to refine it.</div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">---</div><div class="">Donald Stufft</div><div class="">PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA</div></div></div>
</div>
<br class=""></body></html>