Replies: 2 comments 2 replies
-
I very much share your ideas and thoughts and we've talked about them before as well. But we're not really good at properly tagging priorities, and the easy issues are not necessarily high priority, they're tagged as easy for another new contributor to pick up sometimes. So we don't mind them to stay open maybe. Related to this, also write my thoughts here: #27340 (comment) |
Beta Was this translation helpful? Give feedback.
-
Indeed we need better communicate what our priorities are. At a monthly developer meeting, it was proposed to maintain meta-issues labeled "high priority" or "maintainer focus" or "project focus". Maintainers would communicate on the issue that this is an issue an issue that they are focused on and ideally, this should not focus on more than 3 concurrent meta-issues at any given time, otherwise this becomes meaningless. That being said, monitoring more actively PRs that have already been approved once or explicitly labeled "Waiting for second reviewer" would also help not accumulate half ready PRs on the tracker. |
Beta Was this translation helpful? Give feedback.
-
Recently, I've been reviewing our issue tracker, and while the community of contributors and core developers is thriving (1.6K issues), I think tracking and resolving issues becomes challenging. Two primary reasons for that can be that some open-source contributors don't always complete their PRs - a common occurrence that I completely understand. Also, older issues often become buried beneath new ones, making it difficult to prioritize and address them.
I believe a temporary shift in focus from daily maintenance to the prioritization of specific issues could help reduce the number of open issues and pull requests.
I would recommend starting with these issues and PRs
https://github.com/scikit-learn/scikit-learn/pulls?q=is%3Apr+is%3Aopen+review%3Aapproved
https://github.com/scikit-learn/scikit-learn/pulls?q=is%3Apr+is%3Aopen+milestone%3A1.4
https://github.com/scikit-learn/scikit-learn/pulls?q=is%3Aopen+is%3Apr+label%3AEasy
https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aissue+is%3Aopen+label%3A%22High+Priority%22
https://github.com/scikit-learn/scikit-learn/pulls?q=is%3Apr+is%3Aopen+review%3Arequired+label%3A%22Needs+Decision+-+Close%22
https://github.com/scikit-learn/scikit-learn/pulls?q=is%3Apr+is%3Aopen+review%3Arequired+label%3A%22Needs+Decision%22
I would love to hear what you think about this direction, how it can be improved, and if we should try and work toward it
Beta Was this translation helpful? Give feedback.
All reactions