Re: [python-committers] New team member intro
On 31 January 2017 at 19:13, Brett Cannon wrote: > I wonder, what city has the most number of core devs (depending on how you > define "metropolitan area" I'm fairly certain SF or Silicon Valley wins the > metro question)? Vancouver now has two. :) If folks have their location set in the GitHub profile, that data can be pulled to some level of granularity from the mirror repo (and the real one soon enough) I'm also hoping we may some day get reasonable country-granularity data from https://docs.python.org/devguide/motivations.html, but it looks like most folks still aren't too keen on filling that out at this point :) Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] New team member intro
On Wed, Feb 1, 2017 at 12:26 PM, Nick Coghlan wrote: > > I'm also hoping we may some day get reasonable country-granularity > data from https://docs.python.org/devguide/motivations.html, but it > looks like most folks still aren't too keen on filling that out at > this point :) Initially, I thought, the goal was to express the "intrinsic" motivations out on that page. I was negative for that purpose. IIRC, there was a debate on that too. It looks like we like can just mention our name, and generic details. Many core devs will be happy to just do it, like some of us have already done. -- Senthil ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] New team member intro
On 1 February 2017 at 22:43, Senthil Kumaran wrote: > On Wed, Feb 1, 2017 at 12:26 PM, Nick Coghlan wrote: >> >> I'm also hoping we may some day get reasonable country-granularity >> data from https://docs.python.org/devguide/motivations.html, but it >> looks like most folks still aren't too keen on filling that out at >> this point :) > > Initially, I thought, the goal was to express the "intrinsic" > motivations out on that page. It was, as *I* wanted a place to record that explicitly. > I was negative for that purpose. IIRC, there was a debate on that too. Yeah, after a few folks provided feedback I changed the comments in the source file to make it clear that "just the facts" entries were fine, and providing more details than that was entirely optional. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Any blackout dates to NOT migrate to GitHub?
All the blockers for migrating to GitHub are done! That means it's time to schedule the migration. Are there any days that people would really prefer we *don't* do the migration on? I'm hoping to do it next week and definitely this month. I have already asked Ned and Larry and they are fine with any date this month. So if there's some date people don't want the migration to happen on (e.g. running a sprint), please speak up. Otherwise I will schedule among those helping me with the migration and get this done! ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Any blackout dates to NOT migrate to GitHub?
On Thu, Feb 2, 2017 at 11:20 AM, Brett Cannon wrote: > All the blockers for migrating to GitHub are done! That means it's time to > schedule the migration. Are there any days that people would really prefer > we don't do the migration on? I'm hoping to do it next week and definitely > this month. I have already asked Ned and Larry and they are fine with any > date this month. So if there's some date people don't want the migration to > happen on (e.g. running a sprint), please speak up. Otherwise I will > schedule among those helping me with the migration and get this done! We are having a developer sprint on 18-19th of February in PyCon Pune. Maybe we can skip those two days :) Kushal -- Fedora Cloud Engineer CPython Core Developer http://kushaldas.in ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
