16 Apr
2024
16 Apr
'24
5:47 p.m.
Issue #20336 has been updated by mame (Yusuke Endoh).
@matheusrich Are you organizing old tickets? If so, I thank you for your activity, and
would respectfully recommend that you aim to close/reject them in principle.
The fact that a proposal has remained undecided for a long time suggests that either not
many people wanted the same feature or that the design still needs some consideration.
If you happened to want the feature in your daily Ruby programming and found an old ticket
proposing the same feature, then no problem.
However, if you looked at an old ticket and just thought "this might be nice to
have," it might be a good idea to wait until you actually encounter several
situations where you would want the feature.
I feel that considering a proposal without someone who has actually experienced the need
for the feature will not lead to a positive outcome.
----------------------------------------
Misc #20336: DevMeeting-2024-04-17
https://bugs.ruby-lang.org/issues/20336#change-107927
* Author: mame (Yusuke Endoh)
* Status: Open
----------------------------------------
# The next dev meeting
**Date: 2024/04/17 13:00-17:00** (JST)
Log: *TBD*
- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug
tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend,
other attendees can ask instead of you (if attendees can understand your issue).
- We will write a record of the discussion in the file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place of the meeting are scheduled according to when/where we can
reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.
# Call for agenda items
If you have a ticket that you want matz and committers to discuss, please post it into
this ticket in the following format:
```
* [Ticket ref] Ticket title (your name)
* Comment (A summary of the ticket, why you put this ticket here, what point should be
discussed, etc.)
```
Example:
```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
* I feel this feature is very useful and some people say :+1: so let discuss this
feature.
```
- It is recommended to add a comment by 2024/04/14. We hold a preparatory meeting to
create an agenda a few days before the dev-meeting.
- The format is strict. We'll use [this script to automatically create an
markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). We
may ignore a comment that does not follow the format.
- Your comment is mandatory. We cannot read all discussion of the ticket in a limited
time. We appreciate it if you could write a short summary and update from a previous
discussion.
--
https://bugs.ruby-lang.org/