[python-committers] Idea: Create subteams?
Andrew Svetlov
andrew.svetlov at gmail.com
Tue May 15 08:43:05 EDT 2018
More information about the python-committers mailing list
Tue May 15 08:43:05 EDT 2018
- Previous message (by thread): [python-committers] 3.7.0rc1 Delayed [was] FINAL WEEK FOR 3.7.0 CHANGES!
- Next message (by thread): [python-committers] Mentoring Office Hours - the idea, and a question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Agree with Yuri. We have not big amount of non-committer contributions into asyncio, and every non-trivial change requires very careful review. On Thu, Apr 26, 2018, 17:32 Yury Selivanov <yselivanov.ml at gmail.com> wrote: > On Thu, Apr 26, 2018 at 10:12 AM Victor Stinner <vstinner at redhat.com> > wrote: > [..] > > I identified 3 obvious subteams: > > > * Documentation > > * IDLE > > * asyncio > > Sorry, asyncio isn't an obvious choice for me. There are not so many > low-hanging fruits left in asyncio except improvements to its > documentation. I'm a firm -1 to allow people to merge without Andrew's or > my review at this point, almost no PRs are fine when they are submitted > (including our own). There's a lot of complexity in asyncio which isn't > immediately evident to people who are not working with its internals on a > daily basis. > > Now, people who report and submit asyncio PRs seem to do that just fine > without subteams. Although it's rare to see people contributing more than > once, but that's not an asyncio-specific pattern, I see it in every big and > complex project I happen to contribute to. Even having a dedicated asyncio > mailing list doesn't help to get people to contribute to asyncio more > frequently. > > Don't get me wrong, Andrew and I would certainly welcome any help we can > get, but I'd be against running a public experiment with asyncio to see if > 2 of us can handle the management of the new sub-teams idea. Unfortunately > 2 of us just don't have capacity for that. > > Please pick another project for your idea. Maybe we should try it for > documentation first, where we have a lot of core devs who can help with PR > reviews and management of "subteams". > > Yury > _______________________________________________ > python-committers mailing list > python-committers at python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- Thanks, Andrew Svetlov -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20180515/cea0a280/attachment.html>
- Previous message (by thread): [python-committers] 3.7.0rc1 Delayed [was] FINAL WEEK FOR 3.7.0 CHANGES!
- Next message (by thread): [python-committers] Mentoring Office Hours - the idea, and a question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list