On 7/1/2021 7:04 PM, Christopher Barker wrote:
PS: All that being said, we, as a community, could do better. For instance, someone like me could do high-level triage on bug reports -- I need to set aside some time to do that.
In addition/instead of triage, one thing we (as core maintainers) really need, which the more involved members of the wider community can provide, is *context*.
I presume that if you're on python-dev, you probably have (or have access to) a significant Python codebase. Many core developers do as well, but we know we don't have great view across all the different ways that Python gets used. Some of the "worst" regressions are due to scenarios that we simply didn't know existed until they were broken.
We don't need (or wouldn't benefit from) just seeing all of the code, because it's the understanding that's important. How would changes impact *your* projects, *your* users. Anywhere you can chip in with "we do XYZ and this change would [not] impact us this way" or "we'd have to mitigate it by doing ..." is very useful.
It's not just a vote, it's the added context that's helpful. Ultimately, "votes" don't count for much in merge/reject decisions, because we're trying to take into account all users, not just those who show up to click a button. Rational arguments based in real and personal impact statements are far more valuable, especially if you have context that we don't.
So feel free to drop into bugs or PRs when you have relevant context for the impact of a change. Try and be as detailed about the impact on you as you're allowed (or can be without distracting from the issue). Don't be offended if we still think that the impact is "worth it" or that your situation isn't actually as impacted as you think (that probably indicates that we need to do a better NEWS/Whats New entry for the change).
And yes, these can be *significant contributions* to the project, so if you find yourself in a position where you have to justify it to someone outside of the project (e.g. using work time for open source), hopefully any core developer you've interacted with a bit will gladly write a short endorsement for that.
Cheers, Steve _______________________________________________ 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/BB3YX3J5NZHBUKCV67O34TPVQLD2CLWA/ Code of Conduct: http://python.org/psf/codeofconduct/
