Re: [Python-Dev] Interested in serving on Steering Council

2019-01-14 Thread Nick Coghlan 
On Sat, 5 Jan 2019 at 06:28, David Mertz  wrote:
> It is interesting to me that whereas when I started volunteering for the PSF, 
> there was significant overlap between the PSF board and the core-committers, 
> I think there is little or no overlap today.  For better or worse, PSF is 
> much more community than technical today.

(tangent) For those that are curious, I went and looked this up [1],
and the current PSF board has 2 of 11 members being core devs, whereas
the early days of the board look like they had a ratio that was more
often on the order of 4-6 core devs out of 7 members.

I take that as a sign of healthy community growth :)

Cheers,
Nick.

[1]  https://www.python.org/psf/records/board/history/

-- 
Nick Coghlan   |   [email protected]   |   Brisbane, Australia
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] VxWorks and cpython?

2019-01-14 Thread Nick Coghlan 
On Fri, 11 Jan 2019 at 03:23, Victor Stinner  wrote:
> Le jeu. 10 janv. 2019 à 17:54, Kuhl, Brian  a écrit 
> :
> > Do we set them up, and just let them fail, till enough PRs are accepted to 
> > make it build?
>
> Multiple buildbot workers are failing since many years. *I* would
> prefer to see the full test suite passing (even if some tests are
> skipped on your platform) before adding a buildbot, but it seems like
> some people have a different opinion on that. For example, there is an
> AIX buildbot and some tests are still failing (it was always red,
> failing, no?).

Michael Felt has been working towards getting that AIX bot green, and
I merged several PRs over the end of year break to help make progress
towards that goal.

He hit a similar challenge to the one Brian will be facing: putting
all the changes in one PR can make it overwhelming to review (so the
PR stalls), but splitting them up into individual PRs can result in
changes that don't appear sufficiently well motivated on their own (so
those PRs also stall).

The AIX case is currently an example where some of the buildbot
"fixes" are actually test skips, as the goal is to get to a point
where "things that currently work on AIX keep working, while folks
interested in AIX can work towards getting the not-working things
indicated by skipped tests also working".

Cheers,
Nick.

-- 
Nick Coghlan   |   [email protected]   |   Brisbane, Australia
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com