Re: [Steering-council] Re: Steering Council reply regarding conduct (was Re: Steering Council update for February)
by Carol Willing
Martin,
The decision regarding the action and email was unanimous (5-0). It was
discussed in our March 15 and March 22 Steering Council meeting.
This post and this other post (
https://mail.python.org/archives/list/python-dev@python.org/message/J5GR6YV…)
provides context on our discussion and actions.
Regards,
Carol
On Tue, Mar 23, 2021 at 1:58 PM Martin Dengler <martin(a)martindengler.com>
wrote:
> On Tue, Mar 23, 2021 at 12:02:38PM -0700, Python Steering Council wrote:
> >From Thomas Wouters, on behalf of and with full support of the Python
> Steering
> >Council:
> > [use of SC power; specifically, PEP-0013.Powers.2: 'Enforce ... code of
> conduct']
>
> From PEP 13[^1]
> >>> To use its powers, the council votes.
> [...]
> >>> Whenever possible, the council's deliberations and votes shall be held
> in public.
>
> Please share the deliberations and votes.
>
> Martin
>
> [^1]: https://github.com/python/peps/blob/master/pep-0013.rst
> _______________________________________________
> Steering-council mailing list -- steering-council(a)python.org
> To unsubscribe send an email to steering-council-leave(a)python.org
> https://mail.python.org/mailman3/lists/steering-council.python.org/
> Member address: willingc(a)gmail.com
>
3 years
May/June steering council updates.
by Thomas Wouters
The Steering Council is a bit behind on the community updates, but we just
published the May and June ones (also included below):
https://github.com/python/steering-council/blob/main/updates/2021-05-steeri…
https://github.com/python/steering-council/blob/main/updates/2021-06-steeri…
Just as a reminder, if you have any questions or concerns, feel free to
contact us or open an issue in the SC repo:
https://github.com/python/steering-council
May 3
- Steering Council used the weekly meeting to record their PyCon US
keynote <https://www.youtube.com/watch?v=xEkuOtCQ6vA>
<https://github.com/python/steering-council/blob/27a07634ab171fbe0f2a15f83d6…>May
10
- The Core Developers voted to promote Irit Katriel to Core Dev, and the
Steering Council has no objections.
- SC scheduled a PEP review in two weeks.
- SC discussed delegating typing PEPs, but did not reach a conclusion.
- SC discussed PEP 563 <https://www.python.org/dev/peps/pep-0563> (Postponed
Evaluation of Annotations), the unexpected effects of the change, the
last-minute postponement, and how to prevent similar occurrences in the
future.
<https://github.com/python/steering-council/blob/27a07634ab171fbe0f2a15f83d6…>May
17
- Group discussed documenting SC history and procedures. Carol is going
to start on it in the private repo and then it can pushed out to the public
one.
- Thomas is going to ask Nathaniel for a concrete counter proposal for PEP
654 <https://www.python.org/dev/peps/pep-0654/> (Exception Groups and
except*).
- Group discussed using Hypothesis in the standard library.
<https://github.com/python/steering-council/blob/27a07634ab171fbe0f2a15f83d6…>May
24
- The Steering Council did PEP review and assigned pings to PEP authors
and sponsors.
- The Steering Council discussed who applied for the
Developer-in-Residence position and Carol placed it on the agenda for June
7th.
- The Steering Council will not be meeting next week due to Memorial Day
in the US.
June 7
- The Steering Council reviewed the résumés received for the
Developer-in-Residence position. The candidates were selected for the
interview process. The Steering Council prepared for Developer in Residence
interviews by reviewing questions for the interviews.
<https://github.com/python/steering-council/blob/27a07634ab171fbe0f2a15f83d6…>June
14
- Steering Council and PSF staff interviewed candidates for the
Developer-in-Residence position, and discussed the interviews immediately
afterwards.
<https://github.com/python/steering-council/blob/27a07634ab171fbe0f2a15f83d6…>June
21
- The Steering Council extensively discussed the Developer-in-Residence
candidates, and made their final selection.
- The SC discussed improving workflows around full-time contributors.
The group will continue to think and discuss this.
<https://github.com/python/steering-council/blob/27a07634ab171fbe0f2a15f83d6…>June
28
- The Steering Council reviewed PEP 654
<https://www.python.org/dev/peps/pep-0654/> (Exception Groups and
except*). Thomas will schedule a call with Nathaniel and the SC, possibly
for next Monday (July 5), to hear Nathaniel's alternative proposal.
- The SC reviewed PEP 467 <https://www.python.org/dev/peps/pep-0467/> (Minor
API improvements for binary sequences) and there are concerns about the
value of the change and the future implementation. Thomas was going to
start a draft response, but didn't get around to it.
- The SC reviewed PEP 657
<https://www.python.org/dev/peps/pep-0657/> (Include
Fine Grained Error Locations in Tracebacks). The group approved it (Pablo
abstained because he's one of the PEP's authors) and Barry sent the
announcement
<https://mail.python.org/archives/list/python-committers@python.org/thread/3…>
to
python-dev@.
- Group discussed the request
<https://github.com/python/steering-council/issues/68> around modules
following a provisional policies. Group decided that Barry will reach out
to the module author about importlib.metadata's provisional status. The
group will continue their discussion on how to move forward with
provisional modules/packages.
- Group discussed enum.Enum repr and str changes in 3.10 & 3.11. It was
decided that Barry will email python-dev@ and strongly suggest that we
rollback to 3.9 behavior for 3.10 and write a new PEP for 3.11.
--
Thomas Wouters <thomas(a)python.org>
Hi! I'm an email virus! Think twice before sending your email to help me
spread!
2 years, 8 months
Steering Council update for February
by Pablo Galindo Salgado
Hi everyone,
The Steering Council just published the community update for February:
https://github.com/python/steering-council/blob/main/updates/2021-02-steeri…
As a reminder, we'll are trying to keep this up monthly. As you can see we
are mainly focusing on clearing the PEP backlog and to address ongoing
efforts and time-sensitive issues. Here you can find the text for the
update:
February 01
-
After more deliberation and consideration of all available information,
the Steering Council accepted the Pattern Matching PEPs. The Steering
Council agreed that high-quality documentation is crucial in this feature
and therefore its presence should be required before the release. A
response in the name of the Steering Council will be sent to python-dev
addressing the decision and the Steering Council view of the process.
-
The Steering Council discussed Debian's Python distro issues. The
Steering Council will collect and communicate where the concerns are to the
Debian maintainers. Thomas started a draft of the communication that the
Steering Council will review, complete and sign-off.
<https://github.com/python/steering-council/blob/main/updates/2021-02-steeri…>February
08
-
The Steering Council started the discussion of PEP 651. It was decided
that the group will leave this open for next week to better deliberate and
consider more information.
-
The Steering Council discussed the ongoing work on porting types in the
standard library to heap-types. It was decided that through Pablo, the
Steering Council will ask the core developers driving those changes to
create an informational PEP and not to make any more changes in this area
after beta 1, as per our general policy.
-
The Steering Council discussed adding a TOML module to the standard
library. It was decided that maintainers should write a PEP. On the topic
of the standard library, it was agreed that the Steering Council should
present at the PyCon US 2021 Language Summit on the future of the standard
library and Brett is going to gather data on what PRs are tied to which
module, which modules are imported and used the most, commit churn to help
start the planning so we can make data-driven discussions and decisions.
-
The acceptance notice for PEP 634 will be sent from the Steering Council
email, and Thomas will send rejection notices to other competing PEPs that
are therefore rejected.
<https://github.com/python/steering-council/blob/main/updates/2021-02-steeri…>February
15
[ The SC could not meet this week due to holidays in the US and Canada, and
the impossibility to find a common replacement date in the week ]
<https://github.com/python/steering-council/blob/main/updates/2021-02-steeri…>February
22
-
The Steering Council discussed PEP 651 request and has decided to reject
it. An email with the rationale will be sent to the author and python-dev.
-
Ezio joined the Steering Council meeting today to give an update on the
GitHub Migration. GitHub was dormant during the holiday months. Ezio and GH
had a productive meeting a couple of weeks ago. He is working on the tool
that will convert bpo issues into a format that the GH tool will accept. He
will also work on a community update once the test repo is ready. Another
sync up has been scheduled between Ezio and the SC on March 29th.
-
The Steering Council discussed renaming the master branch to main and
the consensus was that we should do that. The group is going to discuss the
timeline and how to approach this with other repositories under the Python
organization in some future meeting.
-
The Steering Council discussed the Debian situation. The group discussed
ways to approach the situation and how to coordinate with Debian
maintainers so it can benefit the Python community at large. It was decided
that the steering council will email the Debian maintainers to try to reach
some common ground and discuss how to proceed.
Regards from cloudy London,
Pablo Galindo Salgado
3 years, 1 month
Steering Council Update (November through December)
by Ewa Jodlowska
Hello!
Below is an update from the Steering Council. It covers November and
December.
The update has been added to the Steering Council repo:
https://github.com/python/steering-council/blob/master/updates/2020-01-06-s…
(added
to README as well).
------------------------------------------------------------------------
# Steering Council Community Update for November - December 2019
## November recap:
- Steering Council assigned one another tasks to check-in on and clean up
29 open PEPs in November (Nov 5 and Nov 12 meetings). See [PEP repo](
https://github.com/python/peps/) for details.
- Steering Council decided that going forward, only one person will need to
approve the minutes and the group will try to rotate that responsibility.
Additionally, to keep meetings efficient we will:
- 1. have a person responsible for the agenda to make sure the agenda
is accurate and timed appropriately
- 2. have a person run the actual meeting to make sure we stay on
topic and cut discussions when topics go over time.
- Steering Council discussed ideas on how to lower the count of PRs. It was
decided that Brett would start a discussion on Discourse with the idea to
close enhancement PRs. This has been done [here](
https://discuss.python.org/t/automatically-close-all-enhancement-prs-for-co…).
At a later time, it was decided the idea would be shut down since many
folks did not approve.
- Steering Council discussed how a hiring plan can coincide with the Vision
Deck and how it would work with sponsor/corporate collaborations. The
Vision Deck is an overview document the Steering Council is drafting, which
will help develop Python's roadmap for the next 5 years. Goal is to have
the Vision Deck complete by PyCon 2020.
- Steering Council had a brief discussion about encouraging more candidates
to run for the next steering council and that everyone would work on
raising awareness for this.
## December recap:
- The Steering Council reviewed [PEP 584](
https://www.python.org/dev/peps/pep-0584/) (“Add + and += operators to the
built-in dict class”) and decided that Guido would let the PEP authors know
| and |= was preferred and that the PEP needed some editing. [This was
done](
https://mail.python.org/archives/list/python-ideas@python.org/message/P46F7…).
At a later time it was decided that Guido will be BDFL-Delegate.
- The Steering Council decided it would meet after the 2020 Steering
Council vote ended. The Steering Council will meet December 10 and December
17th. The hand-off meeting will happen the first week of January. Ewa will
send out a Doodle for the first full week of January once the new Steering
Council members are known. It was decided that on January 8th, 2020 the
Steering Council will have a hand-off meeting between the 2019 team and
2020 team.
- Steering Council decided that we would send out ballots to Marc-Andre
Lemburg, Alex Martelli, and Kurt B. Kaiser. [Brett responded to thread](
https://mail.python.org/archives/list/python-committers@python.org/message/…)
noting this decision and future plans for [PEP 13](
https://www.python.org/dev/peps/pep-0013/).
- Steering Council discussed [PEP 611](
https://www.python.org/dev/peps/pep-0611/). Barry [emailed the python-dev@
list](
https://mail.python.org/archives/list/python-dev@python.org/message/KY46EXG…)
with the outcome of the discussion.
- Steering Council discussed PyPI’s typosquatting issues.
- Group discussed the status of the GitHub migration plan. Ewa drafted a
job description for the Project Manager role to help with the GitHub
migration for the Dec 17th SC meeting. The Steering Council reviewed it and
Ewa scheduled a call with the GitHub team for late January for next steps.
- Steering Council decided to keep Zulip since the Packaging-wg plans on
using it. We will re-evaluate usage next year. Guido informed the
[Discourse thread](
https://discuss.python.org/t/should-we-continue-using-zulip/2816/7). Brett
[posted an announcement](
https://python.zulipchat.com/#narrow/stream/116742-core.2Fhelp/topic/Engage…)
in Zulip.
Thank you,
Ewa
-----------------------
*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/
<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/
<https://www.python.org/psf/donations/>*
4 years, 3 months
Steering Council Update (July through October)
by Ewa Jodlowska
Hey folks -
Here is an update from the Steering Council. It covers July through
October.
The update has been added to the Steering Council repo as well:
https://github.com/python/steering-council/blob/master/updates/2019-11-09-s…
.
# 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](
https://github.com/orgs/python/projects/1#card-26091749)
- 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
CC0-1.0-Universal.
## August recap:
- [PEP 572](https://www.python.org/dev/peps/pep-0572/) was updated to
replace `TargetScopeError` to `SyntaxError`:
https://github.com/python/peps/commit/cd292d89972476fa485a8ac1b14c1ed85b8c4…
- 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:
https://discuss.python.org/t/concerns-about-how-we-vote-on-new-core-develop…
- A timeline was selected for the Steering Council election and informed
the Core Devs:
https://mail.python.org/archives/list/python-committers@python.org/thread/P…
- Release cadence discussions happened
- [Core Dev Sprint in London recap](
http://pyfound.blogspot.com/2019/10/cpython-core-developer-sprint-2019.html)
## 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:
https://mail.python.org/archives/list/python-committers@python.org/thread/6…
- 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](
https://mail.python.org/archives/list/python-committers@python.org/thread/U…)
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:
https://mail.python.org/archives/list/python-committers@python.org/message/…
.
- Steering Council met with GitHub team about the b.p.o. migration, PEP
[581](https://www.python.org/dev/peps/pep-0581/)/[588](
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
opt-in.
- [PEP 608](https://www.python.org/dev/peps/pep-0608/) and [discussion](
https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539)
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](
https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539/22)
with the decision and suggestion.
- It was decided that Ewa will help put together the Community Updates so
they happen monthly.
Thank you,
Ewa
-----------------------
*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/
<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/
<https://www.python.org/psf/donations/>*
4 years, 5 months
July Steering Council update.
by Thomas Wouters
FYI, I've just published the July steering council update, also included
below:
https://github.com/python/steering-council/blob/main/updates/2021-07-steeri…
Just as a reminder, if you have any questions or concerns, feel free to
contact us or open an issue in the SC repo:
https://github.com/python/steering-council
July 5
- No regular meeting because of the US holiday.
- Most of the Steering Council met with Nathaniel Smith to discuss his
alternative proposal for PEP 654
<https://www.python.org/dev/peps/pep-0654/> (Exception Groups and except
*).
- Nathaniel and Carol will work to flesh out his proposal.
<https://github.com/python/steering-council/blob/main/updates/2021-07-steeri…>July
12
- Steering Council discussed a clarification request from the PyPA folks
around PEPs. It was determined that PyPA folks can sponsor their own PEPs.
Brett informed them by responding to the comment.
- SC discussed the enum repr() and str() changes in 3.10 and 3.11.
- SC discussed PEP 582 <https://www.python.org/dev/peps/pep-0582/> (Python
local packages directory).
<https://github.com/python/steering-council/blob/main/updates/2021-07-steeri…>July
19
- Steering Council met with Łukasz, the Developer-in-Residence for the
first time. The group discussed prioritization, balancing, and how to
handle group requests. The Steering Council needs to handle prioritization
if folks send Łukasz their lists of jobs. The group also discussed how this
role is going to impact the strategic approach of merging issues from
bugs.python.org to GitHub. A group Slack channel was created for Łukasz
to have a way to ping the SC outside of email. The SC and Łukasz will meet
every two weeks for now.
- Group discussed PEP 649
<https://www.python.org/dev/peps/pep-0649/> (Deferred
Evaluation Of Annotations Using Descriptors) and typing in general. The
group determined that they need to discuss the status of typing as part of
the language, and write up a PEP to the community so the community knows
how to proceed with typing PEPs.
- Steering Council will continue to review PEP 648
<https://www.python.org/dev/peps/pep-0648/> (Extensible customizations
of the interpreter at startup) and will discuss it via email.
<https://github.com/python/steering-council/blob/main/updates/2021-07-steeri…>July
26
- The Steering Council discussed PEP 648
<https://www.python.org/dev/peps/pep-0648/> (Extensible customizations
of the interpreter at startup) and decided the PEP needed more use cases
and feedback from the community. The group is going to draft a response
(reject it and tell them use cases are needed) and Barry will send it. If
the PEP author provides use cases the SC can revisit the PEP later.
- The SC discussed PEP 467
<https://www.python.org/dev/peps/pep-0467/> (Minor
API improvements for binary sequences) and decided that they will recommend
removing the bchr builtin from the PEP and then the SC can review the
revised PEP if the author wants to revisit it.
- Thomas created the private Python committers Discord and Pablo
suggested we use it for the next virtual Sprint, which the group agrees
with.
--
Thomas Wouters <thomas(a)python.org>
Hi! I'm an email virus! Think twice before sending your email to help me
spread!
2 years, 6 months
March Steering Council update.
by Thomas Wouters
The SC has just published the community update for March:
https://github.com/python/steering-council/blob/main/updates/2021-03-steeri…
We're still trying to get these done every month, but between the rush of
PEPs and other issues before the 3.10b1 deadline, and PyCon US, we're
delayed a little. (The April update hopefully won't be too long.) In the
meantime, the SC keynote from PyCon US covers our longer-term plans and our
points of view on a few other subjects, and that will hopefully be up on
YouTube (
https://www.youtube.com/playlist?list=PL2Uw4_HvXqvYk1Y5P8kryoyd83L_0Uk5K)
soon. (Since it's mentioned in the notes below, I just want to point out
that we didn't record on April 19th; it was pushed back to May 3rd, the
same day 3.10b1 was cut.)
March 1
- Steering Council synced up on the rejection draft for PEP 651. Group
discussed the importance of conveying that all aspects of the proposal were
reviewed and the decision is a holistic one. Group will continue working on
the draft and will sync up via Slack during the week so it can be sent out.
- The Steering Council discussed PEP 648. Barry created a doc and the
group will consolidate feedback+questions into this document. Then the
Steering Council will post this on Discourse as well as to python-dev@.
- The Steering Council extensively discussed PEP 637. The group decided
that it would reject the PEP based on the PEPs costs not being worth the
benefits.
- The Steering Council also discussed typing in general and who should
own it.
- Next week the SC will vote on the Documentation Work Group's charter.
<https://github.com/python/steering-council/blob/main/updates/2021-03-steeri…>March
8
- The Steering Council discussed Mark's response to the rejection of PEP
651.
- The group also discussed the notification for PEP 637.
- The group approved PEP 624 & PEP 597.
- The Steering Council discussed PEP 644 and decided further
communication was needed with Christian.
- The Steering Council voted on and approved the Documentation Work
Group.
- The group discussed moving master to main and decided it needed to be
done. The SC discussed communication around this change.
<https://github.com/python/steering-council/blob/main/updates/2021-03-steeri…>March
15
- Thomas updated the notifications for PEP 597, PEP 624 and PEP 637, and
sent out the notifications March 15th.
- Group checked in on the draft for PEP 648. Thomas has more text to add
to it.
- The Steering Council discussed what kind of presentation they will
give at PyCon US. The group decided on a combination of presentation and
Q&A. Team is working on an outline. SC members were also reminded to
register for PyCon US, and encourage others to do so.
- Barry proposed to the SC that they create a Work Group with a subset
of the Python Security Response Team members and that group can help scope
the future of the PSRT group. Everyone is fine with this.
- Steering Council discussed code of conduct situations around changing
master to main. The group decided on a warning to S.D. that will be sent
as a warning to all. Thomas is working on the initial draft.
<https://github.com/python/steering-council/blob/main/updates/2021-03-steeri…>March
22
- Barry and Thomas checked-in on PEP 648's draft response, they will be
sending it out soon.
- The SC reviewed PEP 644 more. Pablo raised a concern around users that
can be in an env without OpenSSL 1.1.1 or newer and then not being able to
use wheels. Pablo will email Christian to get clarification and will keep
the SC informed.
- Steering Council discussed their keynote at PyCon US 2021. They would
like to gather questions from the community. Ewa will create a Slido, which
will be live from April 5 to 11th. SC will review questions on the 12th.
The current plan is to record on April 19th.
- Steering Council discussed the response to Debian. Carol's done with
her draft. Pablo is going to take a look at it to see if anything else
needs to be added.
- SC discussed the behavior on python-dev@ pertaining to switching git
from master to main.
<https://github.com/python/steering-council/blob/main/updates/2021-03-steeri…>March
29
- The Steering Council accepted PEP 644 (Require OpenSSL 1.1.1 or newer)
- SC accepted PEP 652 (Maintaining the Stable ABI)
- SC checked in on the draft response for PEP 648 (Extensible
customizations of the interpreter at startup), and the draft response to
the Debian discussion.
- SC met with Ezio, PM for the GitHub Issues migration, to talk about
status, progress and next steps, including keeping python-dev up to date.
--
Thomas Wouters <thomas(a)python.org>
Hi! I'm an email virus! Think twice before sending your email to help me
spread!
2 years, 11 months
Re: Steering Council Update (July through October)
by Wes Turner
Thanks for these minutes and for cc'ing the list with them! :+1: :clap:
(markdown emoji)
I know that I can:
- click 'Watch' on the GitHub repo [1] to get notifications when there are
changes
- get an 'Activity Summary' digest email from discuss.python.org
(Discourse) when I haven't logged in lately
- 'watch' or 'track' specific threads hosted by discuss.python.org
(Discourse) and get notifications
The README with links to the steering council updates is sufficient; but
would it be helpful to create a Jekyll theme (or put the logo on a minimal
theme) and setup GH pages for these? [2] There would then also be an RSS
feed and a reverse chronological blog view.
[1] https://github.com/python/steering-council
[2]
https://help.github.com/en/github/working-with-github-pages/setting-up-a-gi…
On Saturday, November 9, 2019, Ewa Jodlowska <ewa(a)python.org> wrote:
> Hey folks -
> Here is an update from the Steering Council. It covers July through
October.
> The update has been added to the Steering Council repo as well:
https://github.com/python/steering-council/blob/master/updates/2019-11-09-s…
.
> # 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](
https://github.com/orgs/python/projects/1#card-26091749)
> - 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
CC0-1.0-Universal.
>
>
> ## August recap:
> - [PEP 572](https://www.python.org/dev/peps/pep-0572/) was updated to
replace `TargetScopeError` to `SyntaxError`:
https://github.com/python/peps/commit/cd292d89972476fa485a8ac1b14c1ed85b8c4…
> - 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:
https://discuss.python.org/t/concerns-about-how-we-vote-on-new-core-develop…
> - A timeline was selected for the Steering Council election and informed
the Core Devs:
https://mail.python.org/archives/list/python-committers@python.org/thread/P…
> - Release cadence discussions happened
> - [Core Dev Sprint in London recap](
http://pyfound.blogspot.com/2019/10/cpython-core-developer-sprint-2019.html)
>
>
> ## 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:
https://mail.python.org/archives/list/python-committers@python.org/thread/6…
> - 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](
https://mail.python.org/archives/list/python-committers@python.org/thread/U…)
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:
https://mail.python.org/archives/list/python-committers@python.org/message/…
.
> - Steering Council met with GitHub team about the b.p.o. migration, PEP
[581](
https://www.python.org/dev/peps/pep-0581/)/[588](https://www.python.org/dev…)
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
opt-in.
> - [PEP 608](https://www.python.org/dev/peps/pep-0608/) and [discussion](
https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539)
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](
https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539/22)
with the decision and suggestion.
> - It was decided that Ewa will help put together the Community Updates so
they happen monthly.
>
>
>
> Thank you,
> Ewa
> -----------------------
> 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/
>
4 years, 5 months
Re: Steering Council Update (July through October)
by Petr Viktorin
[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 opt-in.
- [PEP 608](https://www.python.org/dev/peps/pep-0608/) and [discussion](https://discuss.python.org/t/rfc-pep-608-coordinated-python-rel…
On November 9, 2019 5:25:53 PM GMT+01:00, Ewa Jodlowska <ewa(a)python.org> wrote:
>Hey folks -
>
>Here is an update from the Steering Council. It covers July through
>October.
>
>The update has been added to the Steering Council repo as well:
>https://github.com/python/steering-council/blob/master/updates/2019-11-09-s…
>.
>
># 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](
>https://github.com/orgs/python/projects/1#card-26091749)
>- 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
>CC0-1.0-Universal.
>
>
>## August recap:
>- [PEP 572](https://www.python.org/dev/peps/pep-0572/) was updated to
>replace `TargetScopeError` to `SyntaxError`:
>https://github.com/python/peps/commit/cd292d89972476fa485a8ac1b14c1ed85b8c4…
>- 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:
>https://discuss.python.org/t/concerns-about-how-we-vote-on-new-core-develop…
>- A timeline was selected for the Steering Council election and
>informed
>the Core Devs:
>https://mail.python.org/archives/list/python-committers@python.org/thread/P…
>- Release cadence discussions happened
>- [Core Dev Sprint in London recap](
>http://pyfound.blogspot.com/2019/10/cpython-core-developer-sprint-2019.html)
>
>
>## 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:
>https://mail.python.org/archives/list/python-committers@python.org/thread/6…
>- 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](
>https://mail.python.org/archives/list/python-committers@python.org/thread/U…)
>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:
>https://mail.python.org/archives/list/python-committers@python.org/message/…
>.
>- Steering Council met with GitHub team about the b.p.o. migration, PEP
>[581](https://www.python.org/dev/peps/pep-0581/)/[588](
>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
>opt-in.
>- [PEP 608](https://www.python.org/dev/peps/pep-0608/) and
>[discussion](
>https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539)
>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](
>https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539/22)
>with the decision and suggestion.
>- It was decided that Ewa will help put together the Community Updates
>so
>they happen monthly.
>
>
>
>Thank you,
>
>Ewa
>
>-----------------------
>*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/
><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/
><https://www.python.org/psf/donations/>*
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
4 years, 5 months
Update from the Python Steering Council about CPython Development
by Carol Willing
The Python Steering Council is pleased to provide an update to the Python community about Steering Council activity and CPython development. We've created a GitHub repo for Steering Council updates and helpful documents: https://github.com/python/steering-council
Here's the latest update written after our meeting on February 26th:
https://github.com/python/steering-council/blob/master/updates/2019-02-26_s… (https://link.getmailspring.com/link/2AACF155-36B1-4D80-A2C1-A948561C45E4@ge…)
We'll be posting updates after each steering council meeting which will be roughly twice a month.
5 years, 1 month