From: "jeremyevans0 (Jeremy Evans)" <noreply@ruby-lang.org>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:105616] [Ruby master Misc#18248] Add Feature Triaging Guide
Date: Mon, 11 Oct 2021 16:14:20 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-18248.20211011161414.1604@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-18248.20211011161414.1604@ruby-lang.org
Issue #18248 has been reported by jeremyevans0 (Jeremy Evans).
----------------------------------------
Misc #18248: Add Feature Triaging Guide
https://bugs.ruby-lang.org/issues/18248
* 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/
next parent reply other threads:[~2021-10-11 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 16:14 jeremyevans0 (Jeremy Evans) [this message]
2021-10-12 1:56 ` [ruby-core:105621] [Ruby master Misc#18248] Add Feature Triaging Guide Dan0042 (Daniel DeLorme)
2021-10-12 2:04 ` [ruby-core:105622] " mame (Yusuke Endoh)
2021-10-12 2:52 ` [ruby-core:105623] " naruse (Yui NARUSE)
2021-10-12 15:21 ` [ruby-core:105624] " jeremyevans0 (Jeremy Evans)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-18248.20211011161414.1604@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).