Re: [python-committers] Making the PSF CoC apply to core developers
On 2 March 2016 at 05:44, R. David Murray wrote: > On Tue, 01 Mar 2016 19:00:21 +, Brett Cannon wrote: >> Now obviously I could be totally wrong and this isn't an actual barrier for >> getting women or ethnic minorities to participate in Python's development. > > Yeah, there's no way to know, as far as I can see. But I think our > *being* welcoming is way, *way* more important than our *saying* we are > welcoming. Words that weren't backed up by behaviour would be false advertising, and hence far more problematic than silence or an explicit statement that an environment is deliberately adversarial. However, it also isn't reasonable for open source projects to expect potential contributors to invest weeks or months in assessing their likely treatment if they speak up on a mailing list or submit a new patch - it turns out that having the kind of spare time needed to speculatively invest in following a community for long enough to make that kind of judgement for ourselves is a rare luxury. That's where written behavioural commitments can help - as long as they accurately reflect the way that community members actually strive to conduct themselves, than it helps newcomers better assess "Am I likely to feel comfortable here?". Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Call For Participants For The 2016 Python Language Summit
On Tue, Mar 1, 2016 at 6:01 PM, Larry Hastings wrote:
> It's that time once again: time to start planning for the 2016 Python
> Language Summit! This year the summit will be at the Oregon Convention
> Center in Portland, Oregon, USA, on May 28th.
Thanks for chairing this again!
> Sadly, again this year Michael Foord won't be in attendance.
:(
> Second: we're using a Google Form to collect signups. This one form lets
> you request an invitation to the summit, and also optionally propose a talk.
In case folks are taking requests, I'd love to hear about:
* status report on core workflow improvements
* how typing has been received and what's next (e.g. more integration
into the compiler, multiple dispatch)
* Python in the embedded/-ish space (e.g. MicroPython, BBC MicroBit,
RaspberryPi, android, iOS, ARM)
* status of alternate implementations and tool chains:
- pyjion
- pyston
- pypy
- jython
- ironpython
- cython
- numba
- others?
FWIW, I've offered to present the following (as a last resort ):
* about C OrderedDict
* about my Multi-core Python project
* the successor to PEP 406 ("Improved Encapsulation of Import State")
-eric
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Call For Participants For The 2016 Python Language Summit
On Wed, 2 Mar 2016 at 08:27 Eric Snow wrote:
> On Tue, Mar 1, 2016 at 6:01 PM, Larry Hastings wrote:
> > It's that time once again: time to start planning for the 2016 Python
> > Language Summit! This year the summit will be at the Oregon Convention
> > Center in Portland, Oregon, USA, on May 28th.
>
> Thanks for chairing this again!
>
> > Sadly, again this year Michael Foord won't be in attendance.
>
> :(
>
> > Second: we're using a Google Form to collect signups. This one form lets
> > you request an invitation to the summit, and also optionally propose a
> talk.
>
> In case folks are taking requests, I'd love to hear about:
>
> * status report on core workflow improvements
> * how typing has been received and what's next (e.g. more integration
> into the compiler, multiple dispatch)
> * Python in the embedded/-ish space (e.g. MicroPython, BBC MicroBit,
> RaspberryPi, android, iOS, ARM)
> * status of alternate implementations and tool chains:
> - pyjion
> - pyston
> - pypy
> - jython
> - ironpython
> - cython
> - numba
> - others?
>
I've put in for a 20 minute slot request for Pyjion to give the team a mini
version of our actual Python talk to find out if we even have a chance of
getting the C API changes we want merged in. I have no issue talking about
the GitHub transition or about my push for the CoC applying everywhere, but
I'm not sure if (B|L)arry want to give me so many talk slots (I suspect the
CoC bit can be a lightning talk).
-Brett
>
> FWIW, I've offered to present the following (as a last resort ):
>
> * about C OrderedDict
> * about my Multi-core Python project
> * the successor to PEP 406 ("Improved Encapsulation of Import State")
>
> -eric
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Call For Participants For The 2016 Python Language Summit
On 2 March 2016 at 11:01, Larry Hastings wrote: > It's that time once again: time to start planning for the 2016 Python > Language Summit! Huzzah, thanks for organising this again! I've forwarded the email to a few folks to suggest they submit presentation proposals, but I also have a question for everyone else: would folks be interested in a summary of the SSL/TLS handling developments over the past couple of years and open issues (aka "things that are still hard that we would prefer were simpler") we could potentially help with in core dev? I don't think there's anything in particular pending that can't be handled just via the mailing lists and issue tracker, so this would be more a question of whether or not folks that haven't been following it closely would like to learn more about the *why* of it all. (Or, equivalently, "What do we know about network security management now that we didn't know back when the ssl module was added to Python 2.6?") Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
