[python-committers] formalising retirement as a Python committer

2016-01-02 Thread Andrew MacIntyre
Sadly I have come to the conclusion that there is no realistic prospect of my being able to actively contribute to Python development in the foreseeable future given my current pursuits and interests, though I rely heavily on Python both personally and professionally. As a practical matter I

Re: [python-committers] Github accounts (was: formalising retirement as a Python committer)

2016-01-02 Thread M.-A. Lemburg
On 02.01.2016 13:06, Andrew MacIntyre wrote: > While the announcement today of the planned move of the Python repository to > GitHub has no bearing > whatsoever on my decision, I would note that GitHub's requirement that a > person only have one > account - to be used for both personal activity

Re: [python-committers] Github accounts (was: formalising retirement as a Python committer)

2016-01-02 Thread Paul Moore
On 2 January 2016 at 13:46, M.-A. Lemburg wrote: > I guess the PSF could refund any Github charges incurred to > remedy the situation. Their smallest plan is USD 7 per month > and account, so that would mean costs of USD 84 per year and > committer - this certainly within range

Re: [python-committers] Github accounts (was: formalising retirement as a Python committer)

2016-01-02 Thread Senthil Kumaran
On Sat, Jan 2, 2016 at 5:46 AM, M.-A. Lemburg wrote: > So if you are using a free account for company purposes, you'd > have to get a paid account for personal use to e.g. contribute > to Python and clearly separate personal contributions from > ones you make as employee. > In

Re: [python-committers] Github accounts (was: formalising retirement as a Python committer)

2016-01-02 Thread Brett Cannon
On Sat, 2 Jan 2016 at 07:14 Nick Coghlan wrote: > On 3 January 2016 at 00:12, Paul Moore wrote: > > On 2 January 2016 at 13:46, M.-A. Lemburg wrote: > >> I guess the PSF could refund any Github charges incurred to > >> remedy the

Re: [python-committers] Github accounts (was: formalising retirement as a Python committer)

2016-01-02 Thread Brett Cannon
Another idea I had is could someone reach out to another project like Django or Go that switched to GitHub and see how they handled this situation for contributors? I don't feel I'm in a good position to ask about this since I personally don't have this issue so I don't think I could judge what

Re: [python-committers] We will be moving to GitHub (hopefully) in 2016

2016-01-02 Thread Guido van Rossum
Happy 2016 Brett! Thanks for all the care you've put into this decision. I should also mention that I am happy that as a community we're always willing to learn -- we've switched VCSes many times before and I expect we will again in the future. Each time things get better, and I'm looking forward

Re: [python-committers] We will be moving to GitHub (hopefully) in 2016

2016-01-02 Thread Nick Coghlan
On 2 January 2016 at 05:24, Brett Cannon wrote: > If you want to read the reasons I chose GitHub over GitLab, see > https://mail.python.org/pipermail/core-workflow/2016-January/000345.html . > If you want to discuss the decision or help with the transition, please > subscribe to

Re: [python-committers] Github accounts (was: formalising retirement as a Python committer)

2016-01-02 Thread Guido van Rossum
This hardly seems like a real problem, so let's not worry more about it until someone actually needs help solving this. -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org