[python-committers] Re: Call for resumes: Developer-in-Residence to support CPython
Hi folks - Just a reminder that we are still accepting resumes for the Developer-in-Residence role. The deadline to submit a resume is May 16th. If you would like to chat tomorrow, Saturday or Sunday, let me know. I am happy to share how the employee will work with the PSF and expectations. Ewa Jodlowska Executive Director Python Software Foundation [email protected] On Mon, Apr 5, 2021 at 4:00 PM Brett Cannon wrote: > > > On Mon, Apr 5, 2021 at 12:57 PM Ewa Jodlowska wrote: > >> >> >> >> On Mon, Apr 5, 2021 at 2:36 PM Victor Stinner >> wrote: >> >>> Hi Ewa, >>> >>> This is really awesome! It's great that the PSF can now hire someone for >>> that! >>> >>> The job offer is great, but I would like some clarification :-) (While >>> I was part of the previous Steering Council who helped to write the >>> job offer, sadly I was not avaialble last months when it was >>> discussed.) >>> >>> >>> Who is going to "manage" the candidate? >>> >> >> Great question! The technical direction will come from the SC and the >> people management will be Ee and myself. >> >>> >>> >>> On Mon, Apr 5, 2021 at 7:30 PM Ewa Jodlowska wrote: >>> > The Developer-in-Residence will work full-time for one year to assist >>> CPython maintainers and the Steering Council. Areas of responsibility will >>> include analytical research to understand the project's volunteer hours and >>> funding, investigation of project priorities and their tasks going forward, >>> and begin working on those priorities. We are looking to hire an existing >>> core developer because of the type of work involved and interaction with >>> volunteer core developers and contributors. Need and available funding will >>> determine any extension beyond the first year. >>> > >>> > Create metrics (...) Combine usage and surveyed metrics to determine >>> which standard library modules need help and what the maintainer cost is >>> for standard library modules >>> >>> What are the expected steps after the production of such report of the >>> stdlib usage and maintenance? Hire more people to maintain most used >>> stdlib modules, or deprecate least used modules? >>> >> >>> For example, asyncio and ctypes are popular but barely maintained. For >>> the CI, the most unstable test is test_asyncio (I asked for help >>> multiple times on python-dev). Do we need a more detailed reports on >>> the 302 (len(sys.stdlib_module_names)) stdlib modules? >>> >> >> One of the intentions is to document these cases to better prioritize >> funding we have and provide direction to potential future funders. >> >> I am sure someone from the Steering Council will want to chime in on >> additional, more technical intentions :) >> > > I think the results of the research is going to help inform what the next > steps are (hence the need for the research š). Guessing what needs work > and making a call without having at least *some* form of data seems > premature. I also have stdlib data already for a language summit discussion > (if it gets selected), and at worst I will just open source the Jupyter > notebook with the charts of what I found so this won't be starting from > scratch. > > Plus I suspect there will be some discussion here of what people want to > see be worked on. While the SC is the final decider on the priorities > simply because it would probably be a bit chaotic if the whole team tried > to direct a single person's work, that doesn't mean things won't be > discussed here to provide guidance and feedback to the SC. > > >> >> >>> >>> I understand that the first step is to put priorities in bug triage >>> and PR reviews for the candidate. >>> >>> >>> > Address Pull Request and Issue backlogs based on the developed metrics >>> and other metrics created by the Steering Council >>> >>> What about the candidate skills? I don't expect the candidate to be >>> able to fix any bug in any part of the Python. What if is the priority >>> is a module that the candidate doesn't know? They should do their >>> best, help debugging issues and propose a fix? I expect the existing >>> module maintainers to remain the local autority to review pull >>> requests written by the candidate, to avoid mistakes. >>> >> > What would *you* do in this situation? The expectation is the person > would act like any of us would: if they can fix something then fix it, > otherwise find the person who can and help them out. There is a reason we > hope a core dev is up for taking this job. š > > >> >>> In my experience, it usually helps a lot to do a first basic review, >>> but then ask for the maintainers of a module to do the final review >>> and merge the change. Finding the right people for a review on a >>> specific PR is a very valuable addition to a PR. The candidate could >>> be a great help for that! >>> >> >> Yes, great point to clarify. By "address" we mean either take care of it >> themselves if it is in their purview or work with the maintainers and >> support maintainers with setting up priorities/getti
[python-committers] core-dev chat
Hello Core Dev, I find a need for a core-dev chat service, wherein I could engage in some quick effervescent conversations. It is like a team chat, that is popular with remote work these days. We even seem to have used Zoom Chat yesterday! * I know #python-dev in IRC exists, but it is mostly a channel for bots to send notifications, and there are plenty. I am not certain if any core dev is active there. There was a time when this was active. * We tried python discord last year, and were bit overwhelmed with the number of channels and inability to customize * There seems to be Slack called pyslackers too[1]. I am yet to try it. To have a proper team-chat, we need a service (a) as well as (b) team using that. Does anyone else feel the need? Should we explore any? My thoughts and options are a) Resurrect #python-dev - changing notifications to different group. b) Request for core-dev in pyslackers Slack c) Request for core-dev in Discord. Any other ideas are welcome. If you think that chatting is not a good idea, and a mailing list, and discourse(discuss.python.org) are the best option, please share your thoughts as well. If we feel a chat service will be a good idea for core-dev to hangaround, then we can go to stage 2 of choosing the service by votes in discourse (discuss.python.org). Thank you, Senthil ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/BVPITIYRECSGCX2JUTMT7F7CCCYQSK4K/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: core-dev chat
Iāve found Gitter works well. Iād use that, assuming it was only open to core devs and invitees. On Thu, May 13, 2021 at 16:39 Senthil Kumaran wrote: > Hello Core Dev, > > I find a need for a core-dev chat service, wherein I could engage in > some quick effervescent conversations. > > It is like a team chat, that is popular with remote work these days. > We even seem to have used Zoom Chat yesterday! > > * I know #python-dev in IRC exists, but it is mostly a channel for > bots to send notifications, and there are plenty. I am not certain if > any core dev is active there. There was a time when this was active. > * We tried python discord last year, and were bit overwhelmed with the > number of channels and inability to customize > * There seems to be Slack called pyslackers too[1]. I am yet to try it. > > To have a proper team-chat, we need a service (a) as well as (b) team > using that. > > Does anyone else feel the need? Should we explore any? My thoughts and > options are > > a) Resurrect #python-dev - changing notifications to different group. > b) Request for core-dev in pyslackers Slack > c) Request for core-dev in Discord. > > Any other ideas are welcome. > > If you think that chatting is not a good idea, and a mailing list, and > discourse(discuss.python.org) are the best option, please share your > thoughts as well. > > If we feel a chat service will be a good idea for core-dev to > hangaround, then we can go to stage 2 of choosing the service by votes > in discourse (discuss.python.org). > > > Thank you, > Senthil > ___ > python-committers mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-committers.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/BVPITIYRECSGCX2JUTMT7F7CCCYQSK4K/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- --Guido (mobile) ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/EOYAWR2YDJYPGJCMSYHS7OZYM3MTFWJ5/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: core-dev chat
We already have https://python.zulipchat.com/ setup. https://mail.python.org/pipermail/python-dev/2018-April/152826.html I don't hang around there all the time, but I usually re-open a window there around pycons and core dev sprints. -gps On Thu, May 13, 2021 at 4:53 PM Guido van Rossum wrote: > Iāve found Gitter works well. Iād use that, assuming it was only open to > core devs and invitees. > > On Thu, May 13, 2021 at 16:39 Senthil Kumaran wrote: > >> Hello Core Dev, >> >> I find a need for a core-dev chat service, wherein I could engage in >> some quick effervescent conversations. >> >> It is like a team chat, that is popular with remote work these days. >> We even seem to have used Zoom Chat yesterday! >> >> * I know #python-dev in IRC exists, but it is mostly a channel for >> bots to send notifications, and there are plenty. I am not certain if >> any core dev is active there. There was a time when this was active. >> * We tried python discord last year, and were bit overwhelmed with the >> number of channels and inability to customize >> * There seems to be Slack called pyslackers too[1]. I am yet to try it. >> >> To have a proper team-chat, we need a service (a) as well as (b) team >> using that. >> >> Does anyone else feel the need? Should we explore any? My thoughts and >> options are >> >> a) Resurrect #python-dev - changing notifications to different group. >> b) Request for core-dev in pyslackers Slack >> c) Request for core-dev in Discord. >> >> Any other ideas are welcome. >> >> If you think that chatting is not a good idea, and a mailing list, and >> discourse(discuss.python.org) are the best option, please share your >> thoughts as well. >> >> If we feel a chat service will be a good idea for core-dev to >> hangaround, then we can go to stage 2 of choosing the service by votes >> in discourse (discuss.python.org). >> >> >> Thank you, >> Senthil >> ___ >> python-committers mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> https://mail.python.org/mailman3/lists/python-committers.python.org/ >> Message archived at >> https://mail.python.org/archives/list/[email protected]/message/BVPITIYRECSGCX2JUTMT7F7CCCYQSK4K/ >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >> > -- > --Guido (mobile) > ___ > python-committers mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-committers.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/EOYAWR2YDJYPGJCMSYHS7OZYM3MTFWJ5/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/JEUATFULRMNANC3AI4OF5GRTK4RVDYH5/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: core-dev chat
On Thu, May 13, 2021 at 04:53:08PM -0700, Guido van Rossum wrote: > Iāve found Gitter works well. Iād use that, assuming it was only open to core > devs and invitees. Thanks! I interpret this as a) Yes to a need for chat-service for core-dev. b) Add Gitter to the list of options to consider too. I have used Gitter and I could use it too. The important factor is the community and usage of chat. -- Senthil ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/RB4P6UENOQQKE46NKX5CAE3ILBMX7W2J/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: core-dev chat
On Thu, May 13, 2021 at 05:17:33PM -0700, Gregory P. Smith wrote: > We already haveĀ https://python.zulipchat.com/ setup.Ā Ā https://mail.python.org/ > pipermail/python-dev/2018-April/152826.html Is it fair to say that it didn't take off as well as we intended? Even discuss.python.org beat that take-off curve and seems like something that will stay around, at-least for capturing votes around decisions. > I don't hang around there all the time, but I usually re-open a window there > around pycons and core dev sprints. Not sure if there is any core-dev that hangs around zulip regularly. We couldn't use it as an effective medium. If there is interest again, we could add zulip in the list of votes. -- Senthil ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/2IBUKMV7J2JUGZUSYM7KGV6DZ3W3YZVA/ Code of Conduct: https://www.python.org/psf/codeofconduct/
