[python-committers] Vote to promote Hugo van Kemenade

Hello, I have just opened the poll to grant core dev priviliges to Hugo van Kemenade. Please see details at: https://discuss.python.org/t/vote-to-promote-hugo-van-kemenade/20990 Thanks. ___ python-committers mailing list -- python-committers@python.org

[python-committers] Announcing the Python Language Summit 2022 blog posts

The blog posts about presentations and discussions from Python Language Summit 2022 are now up for your enjoyment. Main article: https://pyfound.blogspot.com/2022/05/the-2022-python-language-summit_01678898482.html - Python without the GIL

[python-committers] Re: Python Language Summit at PyCon 2022 in Salt Lake City

e: in person during PyCon US, Salt Palace Convention Center, room TBD Sign up to attend: https://forms.gle/CS8B6wJdcaN3rtWV8 (closes March 25 th, 2022 AoE) Sign up to discuss a topic: https://forms.gle/LAFE6TTYi15jL5RaA (closes March 25th, 2022 AoE) On Mon, Mar 21, 2022 at 9:14 AM Mariatta

[python-committers] Re: Python Language Summit at PyCon 2022 in Salt Lake City

resentation proposals yet. (less than 5) >From the signups, it seems like attendees are interested in discussing topics like: Cinder, Faster CPython, and various PEPs. So if you've been thinking about submitting a proposal, please do it soon! Thank you, Mariatta

[python-committers] Python Language Summit at PyCon 2022 in Salt Lake City

PSF's Blog. *Is this event recorded? Can I watch the livestream?* No, there will be no recording and no livestream available. If you'd like to participate in discussions, please sign up to attend. If you'd like to listen in, please wait for Alex's blog posts after the s

[python-committers] Hugo van Kemenade is now a member of the Python Triage Team

Happy new year everyone. Just letting you know that Hugo van Kemenade (@hugovk on bpo and GitHub) is the newest member of the Python Triage team. I've seen Hugo's activity in various places: CPython, DevGuide, PEPs and the core-workflow. He has 19 merged PRs and has been actively helping to revie

[python-committers] Re: Opting-in for Hacktoberfest

On Fri, Oct 8, 2021 at 1:08 AM Chris Withers wrote: > > Don't get me wrong though: I think Hacktoberfest is a terrible idea in > that focusses on short-term fly-by contributing rather than fostering > the long term commitments that all open source projects desperately need. > > I understand the f

[python-committers] Re: Opting-in for Hacktoberfest

On Thu., Oct. 7, 2021, 12:35 a.m. Chris Withers, wrote: > Oh, well, that would explain the sudden influx of low value/quality PRs > including people pinging me directly by email.. > > huge -1 from me, please can we opt out of this? > We are opted-out right now so none of the PRs are eligible for

[python-committers] Opting-in for Hacktoberfest

Hello, I would like to propose that we opt-in the CPython project for Hacktoberfest this year, by adding the hacktoberfest topic on the GitHub repository. https://hacktoberfest.digitalocean.com/ Hacktoberfest is an annual event organized by Digital Ocean, now in the 8th year, where aspiring cont

[python-committers] Re: Do I qualify for a x...@python.org email

Hi Joannah, Yes you can request the email address by writing to postmas...@python.org On Sat., Oct. 2, 2021, 10:02 a.m. Joannah Nanjekye, < nanjekyejoan...@gmail.com> wrote: > Am migrating slowly away from using my Gmail address which I use for > CPython correspondence and development. > > I p

[python-committers] Re: Roundup to GitHub Issues migration

FWIW, GitHub announced new powerful Issues today. > https://github.com/features/issues > I have asked GitHub to enable it for the Python org. > ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-c

[python-committers] Re: Please make sure you're following good security practices with your GitHub account

Thanks for sharing your experience, and I think it's important for us core developers to be careful and vigilant about this. I was wondering if we should add under the "core developers responsibility" section (https://devguide.python.org/coredev/#responsibilities), about securing their GitHub acco

[python-committers] Re: core-dev chat

I'm hesitant to start yet another communication channel without considering all the maintenance work that it entails. It's not just about "let's spin up the server" but we should think about who will moderate and administer it. Since we have tried various platforms in the past, and some just didn't

[python-committers] Re: Commits are no longer noted in bro issues

Is the bpo message posted by the CPython emailer webhook service? If so, I might be able to see logs on Heroku. On Wed., May 12, 2021, 8:15 a.m. Zachary Ware, wrote: > On Wed, May 12, 2021 at 9:23 AM Guido van Rossum wrote: > > (Could it have to do with the master->main move?) > > I think this

[python-committers] Jelle Zijlstra is now a member of Python Triage team

Hello, Wanted to share that I've granted the Python Triage membership to Jelle Zijlstra on Monday https://github.com/python/core-workflow/issues/401 Jelle already has the bug triage permissions on bpo, and additionally is already maintainer of python/typing, python/mypy, psf/black, python/typeshe

[python-committers] Re: How can I ignore email notifications on commits mentioning my GitHub handle on CPython forks?

> P.S. If anyone with communications channels to Github is planning to lobby > for changes, I'd prefer a way to say, "Never notify me of @ messages in > commit messages" followed by a special CC: address for easy filtering, > followed by "Please don't notify me a second time when an identical commi

[python-committers] Re: Python Language Summit 2021 Signups Are Now Open

Last call for signing up for Python Language Summit. The forms will automatically be closed at 6 AM Vancouver time tomorrow. Currently we have 82 sign ups and 22 topic proposals. Details: https://us.pycon.org/2021/summits/language/ Sign up stats: https://mariatta.ca/language_summit_data/

[python-committers] Re: PyCon US passes for core devs

This is great! Thank you! On Wed., Mar. 17, 2021, 8:23 a.m. Ewa Jodlowska, wrote: > Hi! > > As some of you may have seen, PyCon US > launched registration. We have dedicated passes set aside for core devs as > part of our financial aid program. > > If you are interes

[python-committers] Re: Python Language Summit 2021 Signups Are Now Open

now is the time. Details: https://us.pycon.org/2021/summits/language/ Sign up stats: https://mariatta.ca/language_summit_data/ On Wed, Mar 3, 2021 at 12:31 PM Mariatta wrote: > Sign up to Python Language Summit is still open for about 3 more weeks. > > So far we received 32 sign ups

[python-committers] Re: Python Language Summit 2021 Signups Are Now Open

es TBD depending on attendee timezones. >- Where: Online via Zoom (link will be sent via email to attendees) >- Co-chairs: Mariatta Wijaya & Łukasz Langa >- Blogger: Joanna Jablonski >- Sign up to attend *and actively participate*: >https://forms.gle/cgmGnmQMDhD2mhHY8 (

[python-committers] Re: bedevere/issue-number and bedevere/news: waiting for status to be reported

I tried removing the labels and adding them back. I didn't see any error logged in heroku. The app is running, yet the webhooks appeared to be delivered successfully, returning 200 status. Perhaps there's a problem from GitHub side. I'm on my phone right now and not able to further investigate un

[python-committers] Re: Fwd: [Python-checkins] Adding "stale" GitHub Action (GH-21247)

response to contributors would > be great, but using mindless automated rules will not get us there. In > any case, auto-closing after 35 days strikes me as madness. > > As it turns out, Mariatta changed the original 5 days in the PR to -1, > meaning never, but forgot to change the

[python-committers] Re: PRs for 3.9

I've deployed a fix in miss-islington ( https://github.com/python/miss-islington/pull/421/files) so this should be working again now. I've retriggered backports to several PRs that were stuck. On Sat, Dec 12, 2020 at 12:21 PM Brandt Bucher wrote: > I saw a (seemingly) related issue with the bot

[python-committers] Re: dependabot gone bonkers?

s this file: > > https://github.com/gvanrossum/cpython/blob/master/.github/dependabot.yml > > I still think this is a bug (or missing feature) in dependabot. Please +1 > that issue! > > On Tue, Dec 1, 2020 at 7:52 AM Mariatta wrote: > >> Maybe a recent change in dependabot

[python-committers] Re: dependabot gone bonkers?

Maybe a recent change in dependabot. This open ticket seems related https://github.com/dependabot/dependabot-core/issues/2804 On Tue., Dec. 1, 2020, 7:36 a.m. Guido van Rossum, wrote: > I got this too on two forks of cpython. It smells like a dependabot > mistake. > > On Tue, Dec 1, 2020 at 04:5

[python-committers] Re: Voter Roll for 2020 Steering Council Election (2021 term)

I think the PEP page hasn't been built yet to reflect the latest change. Though you can see the raw text here: https://github.com/python/peps/blob/master/pep-8102.rst On Mon, Nov 30, 2020 at 10:56 AM Ethan Furman wrote: > On 11/30/20 10:38 AM, Ernest W. Durbin III wrote: > > > All core devs sho

[python-committers] Re: Welcome Batuhan Taskaya to the team!

Welcome and congrats, Batuhan! Happy to have you on board! On Mon, Nov 9, 2020, 2:02 PM Brett Cannon wrote: > > ___ > python-committers mailing list -- python-committers@python.org > To unsubscribe send an email to python-committers-le...@python.org >

[python-committers] New Python Triage members: Irit Katriel and Andre Delfino

This week, we granted bug triage permissions to two new members: Irit Katriel[1] and Andre Delfino[2]. Irit has been active commenting on issues on the bug tracker and has helped move the issues along. She is also actively participating in our sprint this week. Andre already has the Developer rol

[python-committers] Re: Thank you Larry Hastings!

Thank you, Larry! On Mon, Oct 5, 2020, 11:39 AM Barry Warsaw wrote: > They say being a Python Release Manager is a thankless job, so the Python > Secret Underground (PSU), which emphatically does not exist, hereby > officially doesn’t thank Larry for his years of diligent service as the > Python

[python-committers] Re: Welcome Brandt Bucher to the team!

Welcome to the team, Brandt! Will you be joining the core sprint next month? Signup form: https://forms.gle/84NkyYt5g616fs1r5 Details: https://python-core-sprint-2020.readthedocs.io/ ___ python-committers mailing list -- python-committers@python.org To u

[python-committers] Re: RSVP: 2020 Python Core Dev Sprint

As an update, I've created https://python-core-sprint-2020.readthedocs.io/ with some details about the schedule, participants, and sprint projects, to give you a better idea of what to expect during the sprint. If you're planning to participate, please fill in this form: https://forms.gle/84NkyYt

[python-committers] Re: Save the date: Virtual Core Dev Sprint Oct 19-23, 2020

As an update, I've created the python/core-sprint <https://github.com/python/core-sprint>repo to give you all visibility of what we're up to. You can open an issue there if you have any suggestions or questions about the sprint. On Thu, Aug 6, 2020 at 9:06 PM Mariatta wrote

[python-committers] Save the date: Virtual Core Dev Sprint Oct 19-23, 2020

that you would plan to participate from wherever you are! - Mariatta ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python

[python-committers] Re: Notification of a three-month ban from Python core development

> > What's the point of sending this to everyone? Why wasn't this sent as a > quote? I'm not in the coc workgroup or steering council, but I think a copy was sent for transparency. I personally think it is important that we know that there was an incident, the incident was reviewed, and action w

[python-committers] Re: GitHub pull requests

> > Is there a way to do this if you have automerge set? I don't see a way to > control the commit message in that case, but I could easily be missing > something. Yes, you need to edit the PR description. Automerge will take the PR description as the commit message. _

[python-committers] Re: GitHub pull requests

If you want the associated bpo ticket to be closed when the PR is merged, you have to add the commit message saying "closes " (Note that we should document this: https://github.com/python/devguide/issues/502) If you want the the associated GitHub Issue to be closed, it is similar, you have to add

[python-committers] Re: GitHub pull requests

> > is it closed automatically ? What is "it"? The PR itself? yes the PR becomes closed if it is merged. ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.p

[python-committers] Core Workflow change: new commit to previously approved PR now requires re-review

X-post to python-committers, python-dev, and core-workflow mailing list I have just deployed a change to bedevere-bot to address the security concern related to automerging.( https://github.com/python/core-workflow/issues/325) Previously, if core dev has approved the PR and applied the "automerge

[python-committers] Re: Python Language Summit 2020 blog posts

The rest of Python Language Summit articles are now out: Property-Based Testing for Python Builtins and the Standard Library, Zac Hatfield-Dodds: https://pyfound.blogspot.com/2020/05/property-based-testing-for-python.html Core Workflow Updates, Mariatta Wijaya: https://pyfound.blogspot.com/2020

[python-committers] Re: Python Language Summit 2020 blog posts

> > Few more lightning talks from Eric Holscher and Zac Hatfield-Dodds > > ... and Jim Baker ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/ma

[python-committers] Python Language Summit 2020 blog posts

brary, Zac Hatfield-Dodds Core Workflow Updates, Mariatta Wijaya CPython on Mobile Platforms, Russell Keith-Magee Few more lightning talks from Eric Holscher and Zac Hatfield-Dodds Enjoy! ___ python-committers mailing list -- python-committers@pyt

[python-committers] Re: Language Summit

On Thu, Apr 16, 2020 at 1:10 AM Stefan Behnel wrote: > Gregory P. Smith schrieb am 15.04.20 um 23:33: > > FWIW, I found it surprising to learn that there even was an online > language > > summit happening (yesterday). I hadn't heard about that being planned at > > all. > > > > Just because I sai

[python-committers] Re: Language Summit

Antonio Cuni has published his slides: https://speakerdeck.com/antocuni/hpy-a-future-proof-way-of-extending-python On Wed, Apr 15, 2020 at 5:46 PM joannah nanjekye wrote: > > I am reliant on summaries and anyone attending posting details. > Everyone please share your slides if you have any that

[python-committers] Re: bpo email problems - Is there someone in the infra boat?

I think this is same issue as https://github.com/python/bugs.python.org/issues/38 To get in touch with infrastructure team, you can write to infrastructure-staff at python dot org On Fri, Feb 28, 2020 at 10:44 AM Antoine Pitrou wrote: > > (note - apparently the psf.org domain doesn't belong to

[python-committers] Re: Python Language Summit at PyCon 2020

devs. Among them were maintainers and representatives from BeeWare, CircuitPython, PSF board member, PyCharm, etc. Full details at: https://us.pycon.org/2020/events/languagesummit/ On Tue, Jan 28, 2020 at 1:07 PM Mariatta wrote: > (cross posting to python-committers and python-dev) > >

[python-committers] Re: getting old branches/releases

Great! Perhaps we should have this info in devguide. https://github.com/python/devguide/issues/572 Welcoming PR. ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://

[python-committers] Re: getting old branches/releases

On Tue, Feb 11, 2020 at 3:49 PM Ethan Furman wrote: > > I'm trying to get the 3.3 and 3.4 branches so I can check my libraries > compatibility with older versions, but I do not see those branches as being > available: > > How can I get those? > > > 3.3 and 3.4 existed before the migration from G

[python-committers] Re: [Python-Dev] Python Language Summit at PyCon 2020

rg/2020/events/language-summit/";. > > Either the link could be changed to " > https://us.pycon.org/2020/events/languagesummit/"; or " > https://us.pycon.org/2020/events/language-summit/"; could be configured to > redirect towards the correct page. > >

[python-committers] Python Language Summit at PyCon 2020

> Some changes to note this year: 1) We plan to start 1 hour earlier (9AM) 2) The room will have U-shaped table layout Thanks! Mariatta & Łukasz ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an

[python-committers] Re: Possible bug in voting system ? (was: Re: Reminder to vote for the 2020 Steering Council)

Thanks Brett. Re: notifying and sending email to people who were marked as inactive by the script. We can send automated email via Zapier. Let me know how I can help with this part. On Wed, Dec 11, 2019 at 11:20 AM Brett Cannon wrote: > I want to make two quick points and then I'm bowing out

[python-committers] Re: PEP 581/588 RFC: Collecting feedback about GitHub Issues

Sorry, but please leave comments in the GitHub issue, one feature request per comment. This will allow people to give +1 reaction to your request https://github.com/python/core-workflow/issues/359 On Thu, Sep 12, 2019, 2:30 AM Steve Dower wrote: > On 11Sep2019 1117, Steven D'Aprano wrote: > >

[python-committers] PEP 581/588 RFC: Collecting feedback about GitHub Issues

(cross posting to python-committers, python-dev, core-workflow) PEP 581: Using GitHub Issues has been accepted by the steering council, but PEP 588: GitHub Issues Migration plan is still in progress. I'd like to hear from core developers as well as heavy b.p.o users, the following: 1. what fe

[python-committers] Announcing the new Python triage team on GitHub

We have a new Python triage team on GitHub to help improve our workflow. GitHub has a nice table that shows what a triager can or cannot do in general: https://help.github.com/en/articles/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level More specific ro

[python-committers] Re: Cleaning up the historical list of core developers

> > Let's say someone made all of their commits from 2015-07-04 to 2015-10-04 > (and when I say "commits" I mean committing or authoring in git terms). > That means they committed over a span of less than 3 months over the entire > history of the cpython repo and that the last commit was more than

[python-committers] Re: Fwd: Python-checkins post from webhook-mai...@python.org requires approval

This seems to be a mailman feature. Would the suggested workaround below work? https://support.tigertech.net/mailman-implicit-destination Looking at the webhook mailer repo, there doesn't seem to be any recent code change to it, other than allowing the 3.8 branch. On Sun, Jun 9, 2019, 8:56 AM T

Re: [python-committers] Azure build operations

Maybe worth implementing a `retest` command so our bots can retrigger the tests without closing PR. Jenkins has this command. ᐧ On Tue, May 21, 2019 at 8:40 PM Steve Dower wrote: > Close/reopen is still the easiest way, unfortunately. I've been bugging > the team to improve this, but other prior

Re: [python-committers] miss-islington backport pipeline is stalled?

I'm seeing more of this today, just heads up in case you see miss-islington not working. Seems like this is a known issue with celery + kombu 🙁 https://github.com/celery/kombu/issues/1019 ᐧ On Wed, May 8, 2019 at 10:02 AM Mariatta wrote: > There was an error from Redis. I think thi

Re: [python-committers] miss-islington backport pipeline is stalled?

r on unhandled exceptions? > > Alex > > On Wed, May 8, 2019 at 1:02 PM Mariatta wrote: > >> There was an error from Redis. I think this is the first time I've seen >> it, so I don't have any resolution on how to fix it right now. 😟 >> I will look into hand

Re: [python-committers] miss-islington backport pipeline is stalled?

There was an error from Redis. I think this is the first time I've seen it, so I don't have any resolution on how to fix it right now. 😟 I will look into handling the error and have miss-islington leave a comment in the PR when there is such error. log: at=info method=POST path="/" host=miss-isl

Re: [python-committers] Merge with spurious CI failures?

If you can't merge from GitHub UI then you won't be able to do it from GitHub command line (it respects the same branch protection policy) I don't think we should merge if tests are still failing. Perhaps the test should be adjusted to handle this spurious errors? Can it be marked as "allowed fail

[python-committers] Reminder: Python Language Summit 2019 Signup

Just another reminder that sign up is still open for Python Language Summit (until March 21st, 2019) TL;DR: When: Wednesday, May 1, 2019, 10am–4pm Where: Huntington Convention Center, Cleveland, Ohio Apply: Attendance sign up form (before March 21, 2019) S

Re: [python-committers] Date for the Language Summit?

Date is listed here. More info will be added here too. https://us.pycon.org/2019/events/language-summit/ Process will be slightly different this year. Sorry, I'm busy with PyCascades this week. Next time I'll have more time to devote to this. On Thu, Feb 21, 2019, 5:21 AM Mariatta wrot

Re: [python-committers] Cheryl Sabella promoted as core dev

Congrats, Cheryl. Thank you for all your contributions so far. Glad to have you on the team. ᐧ On Tue, Feb 19, 2019 at 9:19 AM Victor Stinner wrote: > Hi, > > I opened a vote during 1 week to promote Cheryl Sabella. She got the > excellent score of 21 “+1” vs 0 “-1” with very encouraging commen

Re: [python-committers] Duplicate ("triplicate"?) Github notifications on Roundup

Know issue: https://github.com/python/bugs.python.org/issues/12#issuecomment-450681871 On Sun, Feb 3, 2019, 6:47 AM Antoine Pitrou > Hello, > > For some time now, Github notifications on Roundup when a PR is open > arrive three times instead of one. Is this a known issue? > > Regards > > Antoine

Re: [python-committers] REMINDER: governance vote is closing by end of this week

You have about 15 hours 12 minutes left to vote, if you haven't already. On Wed, Dec 12, 2018, 1:44 AM Łukasz Langa You have time until December 16th AoE to rank proposals and cast your > ballot. More information in PEP 8001. > > Note: reading the candidate PEPs will take you a while. Don't wait

[python-committers] Blurb-it is now available

Blurb-it is now available. For details, please see my post on discourse https://discuss.python.org/t/blurb-it-is-now-available/528 ᐧ ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committer

Re: [python-committers] A plea to stop last-minute changes to governance PEPs

As a reminder, PEP 8001 states: "November 16th, 2018 to November 30th, 2018 is the official governance PEP review period. We discourage the PEP authors from making major substantive changes during this period, although it is expected that minor tweaks may occur, as the result of this discussion p

Re: [python-committers] Timeline to vote for a governance PEP

> > Shouldn't people who were not involved in the individual creation > processes at least get two weeks to review the final work > to make up their mind before entering a voting period ? > It seems like we're completely skipping the review phase of the > regular PEP process and going straight from

Re: [python-committers] IMPORTANT: Missing Email Addresses for Governance Election Voter Roll

Bump. Some emails still missing, and we need them if you intend to vote in the upcoming CPython general election: Nov 16, 2018. Please provide your email address ASAP and before Nov 16, 2018. See this issue for more details. https://github.com/python/voters/issues/1 ᐧ On Tue, Nov 6, 2018 at 5:

Re: [python-committers] 1 week to Oct 1

Really sorry folks, but I also would like to request an extension, by one week to Oct 8. It's not because I've been slacking; I've started a five-page document (only Barry has seen it), but I still need his help before it can be ready for the public. In addition, I'm facing personal health issue. I

Re: [python-committers] Council / board (Was: 1 week to Oct 1)

My proposal is taking into consideration The PSF's mission and diversity statement. I will not remove the diversity clause from PEP 8011. To save us all trouble of discussing this particular issue, for those of you who disagree completely, and have other ideas about how you'd like Python to be gov

Re: [python-committers] Council / board (Was: 1 week to Oct 1)

> * Mariatta proposed to require to have a least one woman in that > council. > Why stop at women? My actual wording was: "not all white men", which actually means quite different from "must include one woman". I don't appreciate you jumping straight to accu

[python-committers] 1 week to Oct 1

at to have this written up soon, before Oct 1. Thanks. Mariatta ᐧ ___ 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] I have blocked someone from the Python org

Thanks for handling it, Brett. That kind of behavior is not something we need to allow or tolerate in this community. I'm fine with banning. Mariatta ᐧ On Thu, Sep 13, 2018 at 9:18 AM Brett Cannon wrote: > Someone left > https://github.com/python/cpython/pull/9195#issuecommen

Re: [python-committers] Automerge bot deployed

Update to the automerge bot: It will not merge unless there is "CLA signed" label, and no "DO-NOT-MERGE" label. Again, please edit the PR title and description before adding the `🤖 automerge` label. The PR title and description will be used as the squashed commit message. Mariattaᐧ ᐧ ___

[python-committers] Automerge bot deployed

sions in https://github.com/python/core-workflow/issues/29 https://github.com/python/bedevere/issues/14 The previous way of merging PR still works. If you prefer merging the PR yourself, just don't apply the "🤖 automerge" label. Mariatta ᐧ _

[python-committers] 3 weeks to Oct 1

0 The BDFL Governance Model - https://www.python.org/dev/peps/pep-8011 The Council Governance Model - https://www.python.org/dev/peps/pep-8012 The Community Governance Model And don't forget about the lucky PEP number 13. https://www.python.org/dev/peps/pep-0013/

Re: [python-committers] Organizing an informational PEP on project governance options (was Re: Transfer of power)

ance models out there, I was thinking perhaps you can ask non core developers to help out with this effort. So that way you're not constrained by the limited number of core devs and their limited free time available. What do you think? Mariatta On Wed, Aug 1, 2018 at 8:17 PM Nathaniel Smith

Re: [python-committers] Push rights for new Jython contributors

Your question is regarding push access to hg.python.org/jython, right? Seems like according to Jython's devguide , you'll need to send the SSH key to hgaccou...@python.org. But it also seems to be the same email address we used when adding committers

Re: [python-committers] Reminder of BDFL succession timeline + CFP

of separate PEPs of each candidates. Who can nominate: Python core developers Who can be nominated: Python core developers *Dec 15 AoE Voting for new successor starts* (Depends on the governance model chosen on Dec 1) *Who can vote:* *Only core developers can vote.* *Vote

Re: [python-committers] List of all core developers

ack and maintain the list of the core devs of alternate Python implementations. Don't they have their own community / website? They have their own repo, bug tracker, governance model, and everything, right? Mariatta On Wed, Aug 1, 2018 at 2:54 PM Eric Snow wrote: > On Wed, Aug 1, 2018 at

Re: [python-committers] Reminder of BDFL succession timeline + CFP

ting to set up a deadlines and process as wanting to rush things. I'm open to extend the dates, and even wait another year if we need to. Or do folks want to come up with a completely different process than what I've proposed? In the end, I just want to know whether we will come to decisi

Re: [python-committers] Reminder of BDFL succession timeline + CFP

and it's acceptable if you want to propose that we go this route for X years and re-evaluate it again. It should be ok for us to choose one governance model this time, but decide on something else next. Mariatta ___ python-committers mailing list pyt

Re: [python-committers] List of all core developers

See also an open issue to revamp the Developer log: https://github.com/python/devguide/issues/390 Someone has also said that they're working on tracking down the dormant core devs, but now I can't find that email. Mariatta On Wed, Aug 1, 2018 at 2:15 PM M.-A. Lemburg wrote: >

Re: [python-committers] Reminder of BDFL succession timeline + CFP

Thanks! AoE timezone works for me. In that case, let's use AoE instead of UTC. Mariatta On Wed, Aug 1, 2018 at 1:36 PM Thomas Wouters wrote: > > > On Wed, Aug 1, 2018 at 12:42 PM Mariatta Wijaya > wrote: > >> 2. Are people ok UTC timezone? >> > >

[python-committers] Reminder of BDFL succession timeline + CFP

le ok UTC timezone? 3. Should this be a PEP? Mariatta ___ 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] Mentoring Office Hours - the idea, and a question

fixed weekly schedule works for me, but others might have more flexible schedule. Mariatta On Thu, Jun 14, 2018 at 4:58 PM Mariatta Wijaya wrote: > Thanks for starting this, Brian. > > As such, it needs a person/persons/list to contact should something arise >> in this cont

Re: [python-committers] Proposal: an explicit, time-limited moratorium on finalizing any governance decisions

already chosen by Dec 1. Mariatta ___ 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] Proposal: an explicit, time-limited moratorium on finalizing any governance decisions

On Thu, Jul 19, 2018 at 8:59 AM Brett Cannon wrote: > > I had Carol's same worry that while it's great to have a "no sooner than" > date, we also can't let this drag on and we have no "settle by" date, else > we risk losing the faith of the community in our ability to come together > and make dec

Re: [python-committers] Proposal: an explicit, time-limited moratorium on finalizing any governance decisions

+1 On Wed, Jul 18, 2018, 8:54 PM Ethan Furman wrote: > On 07/18/2018 08:45 PM, Łukasz Langa wrote:> > >> On Jul 18, 2018, at 9:36 PM, Nathaniel Smith wrote: > >> > >> I propose: no governance decisions finalized before October > >> 1, 2018. > > > > +1 but it's okay and expected that disc

Re: [python-committers] An alternative governance model

Next available is PEP lucky number 13 🙂 Mariatta On Wed, Jul 18, 2018 at 4:14 PM Barry Warsaw wrote: > On Jul 18, 2018, at 16:06, Fred Drake wrote: > > > PEP 2 is (currently) the "Procedure for Adding New Modules". Though > > superseded, recycling the PEP number

Re: [python-committers] An alternative governance model

Let's be clear that we're not yet at the stage where we can vote for anything, let alone how to vote. Barry made one proposal, that's all. Last week someone suggested doing research of other governance models. We should still do that before we even start voting on anything. Ma

Re: [python-committers] Language moratorium

> > There is a de facto moratorium for the time being until a new governance > model is chosen. Let's not formalize anything beyond that. I agree. Mariatta On Wed, Jul 18, 2018 at 9:24 AM Łukasz Langa wrote: > There is a de facto moratorium for the time being until a new g

Re: [python-committers] Transfer of power

roles (e.g. PEP decision making) 2. refactor large roles 3. mentor the new successor, shadow the previous leader 4. document all the things This might be selfish request, but I hope you can still assume power until we have new successor(s). Thanks. Mariatta On Thu, Jul 12, 2018 at 7:58 AM Gu

Re: [python-committers] A different way to focus discussions

extra "#" I've been waiting for the "excitement" surrounding PEP 572 to cool down before I want to merge PEP 581 (https://github.com/python/peps/pull/681/) I was hoping to bypass python-ideas since we've discussed at Python Language Summit :) but if really needed I

Re: [python-committers] A different way to focus discussions

lip, under a new #pep581 stream. Will that be ok? Mariatta On Thu, Jun 28, 2018 at 4:34 AM Antoine Pitrou wrote: > > Le 28/06/2018 à 13:04, Victor Stinner a écrit : > > It seems like the PEP 572 discussions restarted on python-dev mailing > > list with more than 100 emails

Re: [python-committers] Mentoring Office Hours - the idea, and a question

f-community/2018-April/000488.html Perhaps to start it could just be some of us who wants to volunteer and do it? I can set aside 1 hr each week Thursday as my office hours, between 7 PM - 8 PM Pacific. Mariatta On Wed, May 16, 2018 at 3:08 PM, Victor Stinner wrote: > 2018-05-16 11:

Re: [python-committers] Turning off AppVeyor as required

> > miss-islington currently ignores VSTS status No it does not yet ignore VSTS status. If VSTS status failed, it will not automerge. Mariatta ᐧ ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/li

Re: [python-committers] Comments on moving issues to GitHub

had someone who was responsible for that > Perhaps for a project the size of Python we should have a dedicated Project manager. Mariatta ᐧ ___ 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] Comments on moving issues to GitHub

't been reading the mailing list for sometime until today. For those who missed it, some resources: 1. My language summit slides ( https://speakerdeck.com/mariatta/mariattas-python-language-summit-2018-presentation ) There are 3 bonus slides at the end which I did not get to cover, because

  1   2   >