[another missing step; I can't wait to put all of these proverbial "spinning plates]

On Tue, 31 Jan 2017 at 10:26 Brett Cannon brett@python.org wrote:

[for my own notes, I forgot something in the list]

On Mon, 30 Jan 2017 at 15:21 Brett Cannon brett@python.org wrote:

Assuming I'm right and there are no more blockers for the migration (see my other email to this list on that topic), here is my current thinking on the steps necessary to migrate (I am CC'ing people I'm hoping can help me out with this plan and *bolded* their names; anything without someone's name is on me to do).

1. Make the hg repo read-only (*Benjamin*, *Georg*, or *Antoine*?)
2. Rename python/cpython to python/cpython-mirror
3. Create a new python/cpython project and add relevant

webhooks/integrations 1. CLA bot 2. Travis 3. Codecov

4. bugs.python.org webhook

5. Migrate the hg repo and push it to GitHub (*Senthil*?)

6. Update docs.python.org to build from GitHub (push

https://github.com/python/psf-salt/pull/91; *Berker*?) 3. Get buildbots to build from GitHub (*Zach*?) 4. Updates posted to #python-dev (*R. David*?) 5. Commits sent to python-checkins 6. Gather commit IDs from hg repo 7. Push update to hg.python.org/lookup (*Benjamin*, *Georg*, or *Antoine*?)

8. Merge the github branch of the devguide into master

1. Don't forget to update cpython-devguide.rtfd.io to point to master and only have a single branch

1. Add configuration files for services from

https://github.com/brettcannon/cpython-ci-test 1. Travis 2. Codecov

If I'm missing anything please let me know (everything else I know isn't really time-critical for accepting commits). Once we agree that these are the steps required and people whose help I need/want are on board then I will schedule with python-committers and the requisite release managers to get a date and verify with the people helping me. Then we can do the migration! I know there seem like there are a lot of steps, but a lot of this is parallelizable (e.g. once step 1 is done, steps 2-4 can occur, and after step 4 then the rest of the steps can happen in any order).

On Tue, Jan 31, 2017 at 3:52 PM, Ezio Melotti ezio.melotti@gmail.com wrote:

you can submit a project idea for GSoC by the 7th of February.

Where can I find instructions on how to do it? I may have an idea to submit.

On 2017-01-31 1:24 PM, Ezio Melotti wrote:

On Tue, Jan 31, 2017 at 11:21 PM, Alexander Belopolsky alexander.belopolsky@gmail.com wrote:

...

On Tue, Jan 31, 2017 at 3:52 PM, Ezio Melotti ezio.melotti@gmail.com wrote:

...

you can submit a project idea for GSoC by the 7th of February.

Where can I find instructions on how to do it? I may have an idea to submit.

See http://python-gsoc.org/#mentors and/or ask on #python-gsoc on Freenode.

A good project idea is something well-described that a student can make a plan to complete within the 3 month coding period, with the help of mentors. We usually ask for two mentors per project, but it's usually not too hard to find a backup mentor if you ask on the mailing lists or ask me (I usually have a few spare volunteers.) Basically, write a paragraph or two, provide links to related bugs or discussions, some information about difficulty, and any other information student would need to know is what we're looking for. (For a more specific checklist, there's an ideas page template that might help: https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate)

We get up to PhD level students with various levels of real project experience, but there are a huge number of students browsing ideas who are *maybe* 1st year university students without work experience. So when you're explaining difficulty, remember it's relative to those students who are young, inexperienced, and need to know what ideas are suitable for them.

There's a currently very blank template for python core ideas here: https://wiki.python.org/moin/SummerOfCode/2017/python-core

(If that's not convenient for you to edit, we also keep stuff on github, or you can just email me with the data you want on there.)

Feel free to ask me more questions or drop by #python-gsoc (or our new zulip instance: https://zulip.python-gsoc.org/ ) to chat.

Terri

On Tue, 31 Jan 2017 at 14:01 Berker Peksağ berker.peksag@gmail.com wrote:

On Tue, Jan 31, 2017 at 2:21 AM, Brett Cannon brett@python.org wrote:

...

Update docs.python.org to build from GitHub (push https://github.com/python/psf-salt/pull/91; Berker?)

I can review and test this on my development environment, but we probably need someone from the infra team to do the merging :)

I've emailed them to see if there's anything I can do to make it easier for them.