Hey folks -

Here is an update from the Steering Council. It covers July through

The update has been added to the Steering Council repo as well:

# Steering Council Community Update
July 2019 through October 2019

## July recap:
- PSF and the Steering Council worked on a proposal to hire a project
manager to help with Python 2 EOL communication. The proposal was approved
by the PSF Board and Changeset Consulting was contracted to help with this
work. Progress is being tracked [here](
- Release cadence discussions happened.
- [PEP 1](https://www.python.org/dev/peps/pep-0001/)’s copyright/license
section was updated to include a dual license of public domain and

## August recap:
- [PEP 572](https://www.python.org/dev/peps/pep-0572/) was updated to
replace `TargetScopeError` to `SyntaxError`:
- Vision document review and update happened.
- Release cadence discussions happened.
- Steering Council helped answer inquiries about proposed Python 2 EOL page.
- Steering Council reviewed the newly approved PSF Code of Conduct.

## September recap:
- Slide deck “Vision Doc” was created based off of the original Vision
Document and was discussed by the Steering Council. The Steering Council
decided to continue in this direction.
- The Steering Council discussed the Core Dev promotion topic and it was
suggested by the Steering Council that the Core Devs create a Work Group to
work on that:
- A timeline was selected for the Steering Council election and informed
the Core Devs:
- Release cadence discussions happened
- [Core Dev Sprint in London recap](

## October recap:
- Steering Council discussed the new Code of Conduct and agreed that it
should be sent out to the python-committers@ and python-dev@ mailing lists:
- Steering Council plans on presenting the Vision Deck at PyCon pending any
changes made by future Steering Council.
- Steering Council discussed the proposal made by [Thomas Wouters](
for approval voting. The Steering Council guided Thomas in the direction of
a [PR](https://github.com/python/peps/pull/1197) and a formal vote. That
resulted in a change to [PEP 13](https://www.python.org/dev/peps/pep-0013/)
stating core team members can vote for zero or more of the candidates for
the Steering Council.
- Steering Council discussed communal ownership of Python repo. It was
decided that the Steering Council will send an email to python-committers
about the topic. Brett sent the email on Nov 6:
- Steering Council met with GitHub team about the b.p.o. migration, PEP
https://www.python.org/dev/peps/pep-0588/) plan and discussed next steps.
Next steps for Python include finding a point person to lead the work (will
be a project manager), the Steering Council to find out more information
about search features and how mapping will work.
- The SC reviewed and discussed PEP 602 (1 year release cycle proposal by
Łukasz Langa) and PEP 605 (Nick Coghlan and Steve Dower's 2 year proposal)
and selected [PEP 602](https://www.python.org/dev/peps/pep-0602/).
- [PEP 484](https://www.python.org/dev/peps/pep-0484/) policy for inclusion
of stubs in typeshed was discussed and the [PR](
https://github.com/python/peps/pull/1218/) around it. It was decided that a
sentence would be changed to make type stubs an opt-out situation and not
- [PEP 608](https://www.python.org/dev/peps/pep-0608/) and [discussion](
were reviewed by the Steering Council. It was decided that the PEP as is
would be rejected, but that the buildbot CI option will work. Nick has
responded to the [discussion on Discourse](
with the decision and suggestion.
- It was decided that Ewa will help put together the Community Updates so
they happen monthly.

Thank you,


*As a non-profit organization, the PSF depends on sponsorships and
donations to support the Python community. Check out our Annual Impact
Report for more details: https://www.python.org/psf/annual-report/2019/
*Please contribute to PSF; we can't continue our work without your
support! https://www.python.org/psf/donations/
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
Message archived at 
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to