<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
<br>
</div></div>That implies closing 183 issues and 65 PRs from where we are now. And<br>
when you say "adding features" presumably that means somehow<br>
forbidding people (core devs? we can't forbid anyone else...) from<br>
creating new PRs until we're below the limit.<br>
<br>
In general, I don't think it's practical in a volunteer-based project,<br>
to "force" people to hit specific targets.<br></blockquote><div><br></div><div><br>you certainly can't be hard line about it, but I think it's a practical rule and achievable.<br>you just don't work on new non-critical things until you get the issue and PR counts down.<br>As much as I would like to see pypa have a "system" of issue and PR review, I think a simple rule like this is more achievable right now.<br></div><br></div><br></div></div>