[Python-Dev] Re: October/November/December Steering Council update

[Brett Cannon]

On Tue, Mar 1, 2022 at 9:00 AM Joannah Nanjekye 
wrote:

> > Steering Council did a one hour Q recorded session with Visionary
> sponsor, Bloomberg.
>
> Is it possible to access this recording for transparency purposes or is
> it confidential?
>

We can ask, but I vaguely remember the folks at Bloomberg being told they
could ask us questions involving internal tech.


>
> I saw some people in another language community on a twitter thread where
> people were having
> rumours and speculations of similar discussions, thinking such companies
> influence community decisions.
>
>
If I remember correctly it was the same type of questions we have gotten
from the host of the core dev sprints: where do you see things going, do
you have plans for this, what's the next challenge for Python, etc. It's
actually just like the kind of Q that has occurred at PyCon US as well.
Usually the private nature stems more from people saying, "we have this
system at work that does this and what do you think of that," and not any
influence campaign.

The fact that I can't remember what was asked shows how influential the Q
was. 

And in case anyone happens to be ever concerned, the 2/5 rule for any
single company being on the SC is a direct way this is kind of concern is
stopped. After that is not voting for anyone you think won't put Python's
best interest ahead of corporate interests.


> Disclaimer: I personally trust the SC.
>

Thanks! 

-Brett


>
>
>
> On Tue, Mar 1, 2022 at 7:39 PM Pablo Galindo Salgado 
> wrote:
>
>> We’ve just published the October, November and December steering council
>> update for 2021, also included below:
>>
>>
>> https://github.com/python/steering-council/blob/main/updates/2021-10-steering-council-update.md
>>
>> https://github.com/python/steering-council/blob/main/updates/2021-11-steering-council-update.md
>>
>> https://github.com/python/steering-council/blob/main/updates/2021-12-steering-council-update.md
>>
>> 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
>>
>>
>> *October 11*
>>
>>- SC met with the Developer-in-Residence and provided feedback on the
>>Developer-in-Residence activity blog.
>>- SC decided to keep 2020 dates for 2021 election.
>>- SC discussed the draft about the SC's position on the PEP 649 / PEP
>>563 situation (stringified annotations) and provided feedback.
>>- SC discussed whether or not they should extend their weekly
>>meetings and/or do more async communications. They also decided that the 
>> SC
>>should continue having meetings and working during the elections.
>>
>>
>> *October 18*
>>
>>- Steering Council met with the GitHub Issues PM for an update on the
>>migration. Priority right now is getting a testing repo out to the core 
>> dev
>>sprint and triagers by Wednesday.
>>- SC reviewed PEP 663 (Standardizing Enum str(), repr(), and format()
>>behaviors) and potential PEP Delegates.
>>- SC reviewed and discussed issues open on
>>https://github.com/python/steering-council/issues
>>
>>
>> *October 19*
>>
>>- SC met with the Search Firm the PSF is using for the Executive
>>Director search, to provide input on the search parameters, and suggest
>>potential candidates.
>>
>>
>> *October 25*
>>
>>- Steering Council did a one hour Q recorded session with Visionary
>>sponsor, Bloomberg.
>>- Steering Council discussed PEP 649 and PEP 563 (stringified
>>annotations). The group may want to delegate this to Łukasz but will
>>discuss this more next week.
>>- The candidate PEP Delegate for PEP 663 (Standardizing Enum str(),
>>repr(), and format() behaviors) declined. The Steering Council will think
>>of who else it can be delegated to, or take it on themselves.
>>
>> November 1
>>
>>- The SC discussed PEP 649 -- Deferred Evaluation Of Annotations
>>Using Descriptors  & PEP
>>563 -- Postponed Evaluation of Annotations
>>. The SC decided it would
>>tell the community that more information is needed. Barry will draft an
>>email explaining the current situation and calling for help from static 
>> and
>>dynamic typing users.
>>- The SC reviewed the open issues in the public Steering Council
>>repo: https://github.com/python/steering-council/issues.
>>- The SC discussed SC promotion during the call for nomination
>>period, which started on Nov 1.
>>- The SC discussed PEP 663 - Standardizing Enum str(), repr(), and
>>format() behaviors  and
>>that Barry would write the rejection draft.
>>- Brett informed the SC of an issue involving the return type of
>>iterators and the SC decided it would continue discussing it at the next
>>meeting (https://bugs.python.org/issue45250).
>>

[Python-Dev] Re: October/November/December Steering Council update

[Joannah Nanjekye]

> Steering Council did a one hour Q recorded session with Visionary
sponsor, Bloomberg.

Is it possible to access this recording for transparency purposes or is
it confidential?

I saw some people in another language community on a twitter thread where
people were having
rumours and speculations of similar discussions, thinking such companies
influence community decisions.

Disclaimer: I personally trust the SC.



On Tue, Mar 1, 2022 at 7:39 PM Pablo Galindo Salgado 
wrote:

> We’ve just published the October, November and December steering council
> update for 2021, also included below:
>
>
> https://github.com/python/steering-council/blob/main/updates/2021-10-steering-council-update.md
>
> https://github.com/python/steering-council/blob/main/updates/2021-11-steering-council-update.md
>
> https://github.com/python/steering-council/blob/main/updates/2021-12-steering-council-update.md
>
> 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
>
>
> *October 11*
>
>- SC met with the Developer-in-Residence and provided feedback on the
>Developer-in-Residence activity blog.
>- SC decided to keep 2020 dates for 2021 election.
>- SC discussed the draft about the SC's position on the PEP 649 / PEP
>563 situation (stringified annotations) and provided feedback.
>- SC discussed whether or not they should extend their weekly meetings
>and/or do more async communications. They also decided that the SC should
>continue having meetings and working during the elections.
>
>
> *October 18*
>
>- Steering Council met with the GitHub Issues PM for an update on the
>migration. Priority right now is getting a testing repo out to the core dev
>sprint and triagers by Wednesday.
>- SC reviewed PEP 663 (Standardizing Enum str(), repr(), and format()
>behaviors) and potential PEP Delegates.
>- SC reviewed and discussed issues open on
>https://github.com/python/steering-council/issues
>
>
> *October 19*
>
>- SC met with the Search Firm the PSF is using for the Executive
>Director search, to provide input on the search parameters, and suggest
>potential candidates.
>
>
> *October 25*
>
>- Steering Council did a one hour Q recorded session with Visionary
>sponsor, Bloomberg.
>- Steering Council discussed PEP 649 and PEP 563 (stringified
>annotations). The group may want to delegate this to Łukasz but will
>discuss this more next week.
>- The candidate PEP Delegate for PEP 663 (Standardizing Enum str(),
>repr(), and format() behaviors) declined. The Steering Council will think
>of who else it can be delegated to, or take it on themselves.
>
> November 1
>
>- The SC discussed PEP 649 -- Deferred Evaluation Of Annotations Using
>Descriptors  & PEP 563 --
>Postponed Evaluation of Annotations
>. The SC decided it would
>tell the community that more information is needed. Barry will draft an
>email explaining the current situation and calling for help from static and
>dynamic typing users.
>- The SC reviewed the open issues in the public Steering Council repo:
>https://github.com/python/steering-council/issues.
>- The SC discussed SC promotion during the call for nomination period,
>which started on Nov 1.
>- The SC discussed PEP 663 - Standardizing Enum str(), repr(), and
>format() behaviors  and
>that Barry would write the rejection draft.
>- Brett informed the SC of an issue involving the return type of
>iterators and the SC decided it would continue discussing it at the next
>meeting (https://bugs.python.org/issue45250).
>
>
> November
> 8
>
>- The SC had their bi-weekly meeting with the Developer-in-Residence.
>Received an update from Łukasz on what he is working on.
>- The SC discussed PEP 663 - Standardizing Enum str(), repr(), and
>format() behaviors  and
>after some initial discussion, it was decided that it needs more discussion
>on python-dev@.
>- The SC discussed PEP 467 -- Minor API improvements for binary
>sequences . bchr() was
>taken out like the SC had requested and then an ascii() method was
>added in without any mention. Pablo will draft a response.
>- PEP 554 -- Multiple Interpreters in the Stdlib
> was discussed. A proof of
>concept is needed and the SC is not yet ready to review the PEP without it.
>
>
> November
> 15
>
>