On Sat, Oct 17, 2020 at 7:31 AM Tal Einat <talei...@gmail.com> wrote: > > > 4. Encourage core devs to dedicate some of their time to working through > issues/PRs which are "ignored" or "stalled". This would require first > generating reliable lists of issues/PRs in such states. This could be in > various forms, such as predefined GitHub/b.p.o. queries, a dedicated > web-page, a periodic message similar to b.p.o.'s "weekly summary" email, or > dedicated tags/labels for issues/PRs. (Perhaps prioritize "stalled" over > "ignored".) >
I looked random pull requests during the core sprint and I have merged dozen pull requests. But it is difficult to find any pull requests I can do anything. See this list: open + awaiting merge: https://github.com/python/cpython/labels/awaiting%20merge open + awaiting core review: https://github.com/python/cpython/labels/awaiting%20merge * Some PR is "owned" by some core developer already. We just need to wait them. (Although assignee is not set in most case) * Some PR is under discussion in b.p.o. issue. * Some PR requires expertise at some areas. etc... Significant effort is required to find PRs I can help. My ideas: * Recommend to set "assignee" more aggressive. * "Assign me" when you will review/work on it later. * Check "assign to me" when you have time. * Feel free to un-assign. * Add "waiting who's help" in the issue title. * E.g. "needs compiler experts", "xml", "http", "mail", etc... It will help to find PRs I can help in my spare time. Regards, -- Inada Naoki <songofaca...@gmail.com> _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/U66XTG6YWPWRQZMFVRQJ3PPLPWWCEEKR/ Code of Conduct: http://python.org/psf/codeofconduct/
