* [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17
@ 2022-01-29 8:36 mame (Yusuke Endoh)
2022-01-31 0:45 ` [ruby-core:107375] " shugo (Shugo Maeda)
` (15 more replies)
0 siblings, 16 replies; 18+ messages in thread
From: mame (Yusuke Endoh) @ 2022-01-29 8:36 UTC (permalink / raw
To: ruby-core
Issue #18557 has been reported by mame (Yusuke Endoh).
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107375] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
@ 2022-01-31 0:45 ` shugo (Shugo Maeda)
2022-02-01 20:47 ` [ruby-core:107421] " peterzhu2118 (Peter Zhu)
` (14 subsequent siblings)
15 siblings, 0 replies; 18+ messages in thread
From: shugo (Shugo Maeda) @ 2022-01-31 0:45 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by shugo (Shugo Maeda).
* [Feature #13110] Byte-based operations for String
* Are there any objections to introduce byteindex and byteoffset? (not bytesplice)
* How about byterindex?
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96277
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107421] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
2022-01-31 0:45 ` [ruby-core:107375] " shugo (Shugo Maeda)
@ 2022-02-01 20:47 ` peterzhu2118 (Peter Zhu)
2022-02-02 1:43 ` [ruby-core:107425] " hsbt (Hiroshi SHIBATA)
` (13 subsequent siblings)
15 siblings, 0 replies; 18+ messages in thread
From: peterzhu2118 (Peter Zhu) @ 2022-02-01 20:47 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by peterzhu2118 (Peter Zhu).
- [Feature #18249] The ABI version of dev builds of CRuby does not correspond to the ABI
- ABI checking for development Ruby.
- Calculates the MD5 hash of header files during compilation of Ruby, stores this MD5 in native extensions, and compares the values when loading the binary.
- Prevents incompatible binaries from being loaded, which can cause bugs, crashes, or other incorrect behavior.
- Summary of motivation here: https://bugs.ruby-lang.org/issues/18249#note-15
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96321
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107425] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
2022-01-31 0:45 ` [ruby-core:107375] " shugo (Shugo Maeda)
2022-02-01 20:47 ` [ruby-core:107421] " peterzhu2118 (Peter Zhu)
@ 2022-02-02 1:43 ` hsbt (Hiroshi SHIBATA)
2022-02-02 8:32 ` [ruby-core:107431] " byroot (Jean Boussier)
` (12 subsequent siblings)
15 siblings, 0 replies; 18+ messages in thread
From: hsbt (Hiroshi SHIBATA) @ 2022-02-02 1:43 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by hsbt (Hiroshi SHIBATA).
* [Feature #18513] Hide patchlevel from `ruby -v`
* There is no reason to display it now.
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96325
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107431] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (2 preceding siblings ...)
2022-02-02 1:43 ` [ruby-core:107425] " hsbt (Hiroshi SHIBATA)
@ 2022-02-02 8:32 ` byroot (Jean Boussier)
2022-02-03 16:24 ` [ruby-core:107472] " headius (Charles Nutter)
` (11 subsequent siblings)
15 siblings, 0 replies; 18+ messages in thread
From: byroot (Jean Boussier) @ 2022-02-02 8:32 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by byroot (Jean Boussier).
- [Feature 18498] Introduce a public `WeakKeysMap` that compares by equality (byroot)
- Ruby's current weak reference constructs are not very usable.
- The most useful weak collection that is offered by most platform is `WeakKeysMap`
- The keys would be weak references, but the values would be strong references
- It would use equality semantic, just like a regular Hash
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96329
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107472] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (3 preceding siblings ...)
2022-02-02 8:32 ` [ruby-core:107431] " byroot (Jean Boussier)
@ 2022-02-03 16:24 ` headius (Charles Nutter)
2022-02-04 11:46 ` [ruby-core:107482] " hsbt (Hiroshi SHIBATA)
` (10 subsequent siblings)
15 siblings, 0 replies; 18+ messages in thread
From: headius (Charles Nutter) @ 2022-02-03 16:24 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by headius (Charles Nutter).
* [Feature #18568] https://bugs.ruby-lang.org/issues/18568https://bugs.ruby-lang.org/issues/18568
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96375
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107482] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (4 preceding siblings ...)
2022-02-03 16:24 ` [ruby-core:107472] " headius (Charles Nutter)
@ 2022-02-04 11:46 ` hsbt (Hiroshi SHIBATA)
2022-02-07 8:45 ` [ruby-core:107496] " byroot (Jean Boussier)
` (9 subsequent siblings)
15 siblings, 0 replies; 18+ messages in thread
From: hsbt (Hiroshi SHIBATA) @ 2022-02-04 11:46 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by hsbt (Hiroshi SHIBATA).
* [Feature #18571] Removed the bundled sources from release package after Ruby 3.2
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96383
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107496] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (5 preceding siblings ...)
2022-02-04 11:46 ` [ruby-core:107482] " hsbt (Hiroshi SHIBATA)
@ 2022-02-07 8:45 ` byroot (Jean Boussier)
2022-02-07 18:16 ` [ruby-core:107503] " Eric Wong
2022-02-07 22:31 ` [ruby-core:107506] " jeremyevans0 (Jeremy Evans)
` (8 subsequent siblings)
15 siblings, 1 reply; 18+ messages in thread
From: byroot (Jean Boussier) @ 2022-02-07 8:45 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by byroot (Jean Boussier).
[Feature #18566] Merge `io-wait` gem into core `IO` class. (byroot)
- It's very small and any non-trivial IO code will require it.
- Merge io-wait into io.c for Ruby 3.2
- Remove io-wait as a dependency of all gems maintained by ruby-core (e.g. net-protocol).
- Publish a new io-wait version that is simply an empty gem.
- Add a `lib/io/wait.rb` stub, with eventually a deprecation warning.
- @normalperson suggest to do the same with `io-nonblock`.
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96403
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107503] Re: [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-02-07 8:45 ` [ruby-core:107496] " byroot (Jean Boussier)
@ 2022-02-07 18:16 ` Eric Wong
0 siblings, 0 replies; 18+ messages in thread
From: Eric Wong @ 2022-02-07 18:16 UTC (permalink / raw
To: ruby-core
"byroot (Jean Boussier)" <noreply@ruby-lang.org> wrote:
> Issue #18557 has been updated by byroot (Jean Boussier).
>
>
> [Feature #18566] Merge `io-wait` gem into core `IO` class. (byroot)
> - It's very small and any non-trivial IO code will require it.
> - Merge io-wait into io.c for Ruby 3.2
> - Remove io-wait as a dependency of all gems maintained by ruby-core (e.g. net-protocol).
> - Publish a new io-wait version that is simply an empty gem.
> - Add a `lib/io/wait.rb` stub, with eventually a deprecation warning.
Please just keep lib/io/wait.rb stub empty indefinitely. No
need for deprecation warning, just a no-op is fine and don't
cause pain for existing users. I don't want to hurt:
1) users who aren't coders
2) users who lack permissions to change code
3) codebases which need to support both old/ancient Rubies + new ones
I'm looking at system-wide implications from distro-installed Rubies;
not from a webapp+bundler perspective.
> - @normalperson suggest to do the same with `io-nonblock`.
Actually, Benoit suggested io-nonblock. I suggested going beyond that :)
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107506] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (6 preceding siblings ...)
2022-02-07 8:45 ` [ruby-core:107496] " byroot (Jean Boussier)
@ 2022-02-07 22:31 ` jeremyevans0 (Jeremy Evans)
2022-02-07 22:52 ` [ruby-core:107508] " greggzst (Grzegorz Jakubiak)
` (7 subsequent siblings)
15 siblings, 0 replies; 18+ messages in thread
From: jeremyevans0 (Jeremy Evans) @ 2022-02-07 22:31 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by jeremyevans0 (Jeremy Evans).
* [Bug #18487] Kernel#binding behaves differently depending on implementation language of items on the stack (jeremyevans0)
* Is it OK to limit Kernel#binding to only look at the preceding frame, instead of the closest Ruby-level frame?
* If so, is the patch acceptable?
* [Bug #16663] Add block or filtered forms of Kernel#caller to allow early bail-out (jeremyevans0)
* Since the last developer meeting, a prototype has been created.
* Is the behavior of the prototype acceptable?
* Incorrect usage with `to_enum` raises `StopIteration` instead of crashing. Is that acceptable?
* [Bug #14103] Regexp absense operator has no chance to `^C` (jeremyevans0)
* One possible way around this is checking for interrupts and potentially yield to another thread every N times during backtracking.
* I submitted a pull request to do that (N = 1000), and it fixes the example given.
* Is such an approach acceptable? If so, is the patch acceptable?
* One issue not addressed by the patch is the modification of the string being searched by another thread during regexp evaluation (potentially causing a crash), but I'm not sure whether that is possible.
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96411
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107508] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (7 preceding siblings ...)
2022-02-07 22:31 ` [ruby-core:107506] " jeremyevans0 (Jeremy Evans)
@ 2022-02-07 22:52 ` greggzst (Grzegorz Jakubiak)
2022-02-08 18:57 ` [ruby-core:107523] " byroot (Jean Boussier)
` (6 subsequent siblings)
15 siblings, 0 replies; 18+ messages in thread
From: greggzst (Grzegorz Jakubiak) @ 2022-02-07 22:52 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by greggzst (Grzegorz Jakubiak).
[Feature #16989] matz has already accepted adding Sets as default. However, there hasn’t been any updates on the progress
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96413
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107523] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (8 preceding siblings ...)
2022-02-07 22:52 ` [ruby-core:107508] " greggzst (Grzegorz Jakubiak)
@ 2022-02-08 18:57 ` byroot (Jean Boussier)
2022-02-09 21:54 ` [ruby-core:107535] " tenderlovemaking (Aaron Patterson)
` (5 subsequent siblings)
15 siblings, 0 replies; 18+ messages in thread
From: byroot (Jean Boussier) @ 2022-02-08 18:57 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by byroot (Jean Boussier).
[Feature #18339] GVL instrumentation API
- It would allow to instrument the GVL which is a key metric for threaded environments, and to tune concurrency in applications.
- I implemented a (posix only for now) draft: https://github.com/ruby/ruby/pull/5500.
- The overhead when no hook is registered is just a single unprotected boolean check, so close to zero.
- `rb_gvl_hook_t * rb_gvl_event_new(rb_gvl_callback callback, rb_event_flag_t event)` to register a hook.
- `bool rb_gvl_event_delete(rb_gvl_hook_t * hook)` to unregister it.
- Is the general idea acceptable?
- Any API change before I try to implement the Windows version?
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96428
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107535] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (9 preceding siblings ...)
2022-02-08 18:57 ` [ruby-core:107523] " byroot (Jean Boussier)
@ 2022-02-09 21:54 ` tenderlovemaking (Aaron Patterson)
2022-02-10 7:38 ` [ruby-core:107548] " zverok (Victor Shepelev)
` (4 subsequent siblings)
15 siblings, 0 replies; 18+ messages in thread
From: tenderlovemaking (Aaron Patterson) @ 2022-02-09 21:54 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by tenderlovemaking (Aaron Patterson).
[Feature #12962] Adding "friend" method visibility
* Allow libraries with Object Oriented internals to call "not public" methods
* Useful when "protected" is too restricted, but the method shouldn't be "public"
* Refinements can't help because they are lexically scoped
* It's easier to add method visibility than to move all code around
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96447
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107548] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (10 preceding siblings ...)
2022-02-09 21:54 ` [ruby-core:107535] " tenderlovemaking (Aaron Patterson)
@ 2022-02-10 7:38 ` zverok (Victor Shepelev)
2022-02-14 14:08 ` [ruby-core:107575] " ktsj (Kazuki Tsujimoto)
` (3 subsequent siblings)
15 siblings, 0 replies; 18+ messages in thread
From: zverok (Victor Shepelev) @ 2022-02-10 7:38 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by zverok (Victor Shepelev).
* [Bug #18580] `Range#include?` inconsistency for beginless String ranges (zverok)
* `(...'z').include?('ww')` works for strings, due to historical reasons
* there is no semantical justification for it, and it is confusing for users
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96460
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107575] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (11 preceding siblings ...)
2022-02-10 7:38 ` [ruby-core:107548] " zverok (Victor Shepelev)
@ 2022-02-14 14:08 ` ktsj (Kazuki Tsujimoto)
2022-02-14 14:15 ` [ruby-core:107576] " nobu (Nobuyoshi Nakada)
` (2 subsequent siblings)
15 siblings, 0 replies; 18+ messages in thread
From: ktsj (Kazuki Tsujimoto) @ 2022-02-14 14:08 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by ktsj (Kazuki Tsujimoto).
* [Feature #18585] Promote find pattern to official feature (ktsj)
* Is it OK to to promote find pattern to official feature?
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96486
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107576] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (12 preceding siblings ...)
2022-02-14 14:08 ` [ruby-core:107575] " ktsj (Kazuki Tsujimoto)
@ 2022-02-14 14:15 ` nobu (Nobuyoshi Nakada)
2022-02-14 15:24 ` [ruby-core:107580] " byroot (Jean Boussier)
2022-02-16 17:36 ` [ruby-core:107604] " kddeisz (Kevin Newton)
15 siblings, 0 replies; 18+ messages in thread
From: nobu (Nobuyoshi Nakada) @ 2022-02-14 14:15 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by nobu (Nobuyoshi Nakada).
* [Misc #18362] mswin builds & vs2022
* What can we do for the bug?
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96487
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107580] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (13 preceding siblings ...)
2022-02-14 14:15 ` [ruby-core:107576] " nobu (Nobuyoshi Nakada)
@ 2022-02-14 15:24 ` byroot (Jean Boussier)
2022-02-16 17:36 ` [ruby-core:107604] " kddeisz (Kevin Newton)
15 siblings, 0 replies; 18+ messages in thread
From: byroot (Jean Boussier) @ 2022-02-14 15:24 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by byroot (Jean Boussier).
[Feature #18576] Rename `ASCII-8BIT` encoding to `BINARY`
- The `ASCII-8BIT` name is very confusing for beginners.
- Even for people who know what it is, it can easily be misread as `US-ASCII`
- It has been aliased as `BINARY` for a very long time, and in the vast majority of the case it's a better description.
- I expect the backward compatibility problems to be very minimal (limited to `Encoding#name`).
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96491
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:107604] [Ruby master Misc#18557] DevMeeting-2022-02-17
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
` (14 preceding siblings ...)
2022-02-14 15:24 ` [ruby-core:107580] " byroot (Jean Boussier)
@ 2022-02-16 17:36 ` kddeisz (Kevin Newton)
15 siblings, 0 replies; 18+ messages in thread
From: kddeisz (Kevin Newton) @ 2022-02-16 17:36 UTC (permalink / raw
To: ruby-core
Issue #18557 has been updated by kddeisz (Kevin Newton).
* [Feature #18589] Finer-grained constant invalidation (Kevin Newton)
* We want to trade a very small memory increase for much better constant cache invalidation.
* This will allow relying on more stable constant caches for better code specialization in JITs.
* This can also help speed up initial boot times since caches are currently invalidated each time a class is created.
----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96515
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2022/02/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/02/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/
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2022-02-16 17:36 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-01-29 8:36 [ruby-core:107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 mame (Yusuke Endoh)
2022-01-31 0:45 ` [ruby-core:107375] " shugo (Shugo Maeda)
2022-02-01 20:47 ` [ruby-core:107421] " peterzhu2118 (Peter Zhu)
2022-02-02 1:43 ` [ruby-core:107425] " hsbt (Hiroshi SHIBATA)
2022-02-02 8:32 ` [ruby-core:107431] " byroot (Jean Boussier)
2022-02-03 16:24 ` [ruby-core:107472] " headius (Charles Nutter)
2022-02-04 11:46 ` [ruby-core:107482] " hsbt (Hiroshi SHIBATA)
2022-02-07 8:45 ` [ruby-core:107496] " byroot (Jean Boussier)
2022-02-07 18:16 ` [ruby-core:107503] " Eric Wong
2022-02-07 22:31 ` [ruby-core:107506] " jeremyevans0 (Jeremy Evans)
2022-02-07 22:52 ` [ruby-core:107508] " greggzst (Grzegorz Jakubiak)
2022-02-08 18:57 ` [ruby-core:107523] " byroot (Jean Boussier)
2022-02-09 21:54 ` [ruby-core:107535] " tenderlovemaking (Aaron Patterson)
2022-02-10 7:38 ` [ruby-core:107548] " zverok (Victor Shepelev)
2022-02-14 14:08 ` [ruby-core:107575] " ktsj (Kazuki Tsujimoto)
2022-02-14 14:15 ` [ruby-core:107576] " nobu (Nobuyoshi Nakada)
2022-02-14 15:24 ` [ruby-core:107580] " byroot (Jean Boussier)
2022-02-16 17:36 ` [ruby-core:107604] " kddeisz (Kevin Newton)
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).