Issue #18248 has been updated by mame (Yusuke Endoh).


Thank you always for your continuous and great contribution, I really appreciate it.

I read the guide draft. I understand that the two new things are as follows:

* We can close a three-month stale feature request after a committer responded "unlikely to be considered".
* We can close a one-year stale feature request even if a committer responded nothing.

They may be somewhat arguable, but personally, I think it's fine to try this if Jeremy will operate the triage with this policy. If there are any problems, we can think about adjusting the guide later.

----------------------------------------
Misc #18248: Add Feature Triaging Guide
https://bugs.ruby-lang.org/issues/18248#change-94110

* Author: jeremyevans0 (Jeremy Evans)
* Status: Open
* Priority: Normal
----------------------------------------
Ruby added a bug triaging guide in June 2019, and since then I've used it to reduce the number of open bugs in the tracker from over 1400 to about 300.  Ruby currently has over 1200 open feature requests on the issue tracker. From a cursory review, many of these have already been implemented, and many are unlikely to be desired.  I would like to add a feature triaging guide to Ruby and start triaging feature requests, with the goal of having open feature requests be features not yet implemented that the Ruby core team would like implemented or would consider patches for.  By doing so, we can make it easier for potential contributors to Ruby to easily see possible contributions they could make.

I've added a pull request with a draft of the proposed guide: https://github.com/ruby/ruby/pull/4953



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>