From: "shugo (Shugo Maeda)" <noreply@ruby-lang.org>
To: ruby-core@neon.ruby-lang.org
Subject: [ruby-core:110785] [Ruby master Misc#19074] DevMeeting-2022-11-17
Date: Wed, 16 Nov 2022 23:09:27 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-100132.20221116230926.18@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-19074.20221021112358.18@ruby-lang.org
Issue #19074 has been updated by shugo (Shugo Maeda).
* [Bug #19132] `**` with other keyword parameters causes "no anonymous keyword rest parameter" (shugo)
* RBS expects no name for keyword rest parameters while test_method.rb etc expects `:**`. Can we choose `:**` for consistency?
----------------------------------------
Misc #19074: DevMeeting-2022-11-17
https://bugs.ruby-lang.org/issues/19074#change-100132
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/11/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 2022/11/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/
next prev parent reply other threads:[~2022-11-16 23:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 11:23 [ruby-core:110461] [Ruby master Misc#19074] DevMeeting-2022-11-17 mame (Yusuke Endoh)
2022-10-24 10:08 ` [ruby-core:110497] " ioquatix (Samuel Williams)
2022-10-25 10:38 ` [ruby-core:110512] " byroot (Jean Boussier)
2022-10-31 13:49 ` [ruby-core:110561] " Eregon (Benoit Daloze)
2022-11-05 14:40 ` [ruby-core:110622] " tenderlovemaking (Aaron Patterson)
2022-11-05 15:10 ` [ruby-core:110623] " mame (Yusuke Endoh)
2022-11-07 18:16 ` [ruby-core:110643] " Eregon (Benoit Daloze)
2022-11-07 18:37 ` [ruby-core:110646] " jeremyevans0 (Jeremy Evans)
2022-11-07 22:02 ` [ruby-core:110648] " st0012 (Stan Lo)
2022-11-09 20:30 ` [ruby-core:110673] " jeremyevans0 (Jeremy Evans)
2022-11-10 12:04 ` [ruby-core:110682] " byroot (Jean Boussier)
2022-11-12 23:14 ` [ruby-core:110728] " bdewater (Bart de Water)
2022-11-16 23:09 ` shugo (Shugo Maeda) [this message]
2022-11-17 5:00 ` [ruby-core:110786] " mame (Yusuke Endoh)
2022-11-17 9:30 ` [ruby-core:110795] [Ruby master Misc#19074] DevMeeting-2022-12-01 (postponed from 11-17) shugo (Shugo Maeda)
2022-11-21 13:50 ` [ruby-core:110835] " Eregon (Benoit Daloze)
2022-11-25 16:26 ` [ruby-core:111011] " Eregon (Benoit Daloze)
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.journal-100132.20221116230926.18@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=ruby-core@neon.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).