On 3/1/2014 7:11 PM, Chris Angelico wrote: > Way back in 2012, Martin Löwis declared a standing offer on this list > to get issue patches reviewed: review five issues and he'll review one > of yours. As I remember, he set a pretty low bar for 'review', lowing that I think you are thinking. > I have a couple of patches outstanding, notably issue 20249 [2], which > is a small change, has a patch, and has no activity or nosying since > its creation. And the other? > More importantly, if there is such an offer, it'd be great to mention > it somewhere, so people can know what they can do to move an issue > forward. (And preferably with a link somewhere to what it means to The question has been asked on core-mentorship list. I have considered making an offer, but haven't yet. > review a patch - what it takes to make a useful and helpful review, > which I'm not entirely sure of at the moment.) If there's not, is it > something that could be considered? I'd love to see some downward > movement on the Open Issues figure, but am not really sure what I can > personally do to help. You are active on python-ideas, so build on that. There are 1551 open enhancement issues. Some have no response. Some should be rejected (for instance, if a couple of core devs have given negative responses, and none positive). Some should probably be closed, but possibly discussed on python-ideas. You could open either suggest that the OP post on python-ideas or open a discussion yourself. Many should have been discussed on python-ideas first, to garner support, but may have been posted before it existed, or at least before it was very well known. Some might be obsolete given what has otherwise been added, or by changes from py2 to py3. Any that are left open should be marked for 3.5. -- Terry Jan Reedy
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4