On Thu, Jan 8, 2015 at 12:59 AM, Nick Coghlan <ncoghlan@gmail.com> wrote:
On 6 December 2014 at 06:04, Brett Cannon <bcannon@gmail.com> wrote:
> # Next steps
> I'm thinking first draft PEPs by February 1 to know who's all-in (8 weeks
> away), all details worked out in final PEPs and whatever is required to
> prove to me it will work by the PyCon language summit (4 months away). I
> make a decision by May 1, and
> then implementation aims to be done by the time 3.5.0 is cut so we can
> switch over shortly thereafter (9 months away). Sound like a reasonable
> timeline?

I've now updated PEP 474 to cover my current proposal for the support
repositories, as well as some of the preparatory work that is already
being undertaken: https://www.python.org/dev/peps/pep-0474/

By the end of the month, I'll also aim to have an updated version of
PEP 462 published that considers how the forge.python.org service
could potentially be extended to handle CPython itself, rather than
attempting to build those flows directly into the existing Roundup and
Rietveld based approach.

There could be JSON[-LD] schema to describe resources with attributes:

https://github.com/westurner/wiki/wiki/ideas#open-source-mailing-list-extractor

There could be configurable per-list link heuristics:
  • http[s]