* [ruby-core:102064] [Ruby master Misc#17535] DevelopersMeeting20210216Japan
@ 2021-01-13 16:26 mame
2021-01-13 21:37 ` [ruby-core:102073] " muraken
` (7 more replies)
0 siblings, 8 replies; 9+ messages in thread
From: mame @ 2021-01-13 16:26 UTC (permalink / raw)
To: ruby-core
Issue #17535 has been reported by mame (Yusuke Endoh).
----------------------------------------
Misc #17535: DevelopersMeeting20210216Japan
https://bugs.ruby-lang.org/issues/17535
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2021/02/16 13:00-17:00**
Place/Sign-up/Agenda/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 log about the discussion to a 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 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 2021/02/13. 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] 9+ messages in thread
* [ruby-core:102073] [Ruby master Misc#17535] DevelopersMeeting20210216Japan
2021-01-13 16:26 [ruby-core:102064] [Ruby master Misc#17535] DevelopersMeeting20210216Japan mame
@ 2021-01-13 21:37 ` muraken
2021-01-15 9:04 ` [ruby-core:102104] " nobu
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: muraken @ 2021-01-13 21:37 UTC (permalink / raw)
To: ruby-core
Issue #17535 has been updated by mrkn (Kenta Murata).
* [Feature #17291] Optimize `__send__` call (mrkn)
* [rspec-mocks](https://github.com/rspec/rspec-mocks) depends on redefining `__send__` to detect the form of the method call in a mock object.
* The mock object raises NoMethodError when the method call form is `obj.method` and the called method is not public.
* This behavior occurs the following step:
1. [Keeping the method name at `__send__` and `send` in mock object](https://github.com/rspec/rspec-mocks/blob/c1a86de005c5aa7885dbc92487422b0c0f43d324/lib/rspec/mocks/verifying_double.rb#L45-L57)
1. [Check the method called via `__send__` at `method_missing`](https://github.com/rspec/rspec-mocks/blob/c1a86de005c5aa7885dbc92487422b0c0f43d324/lib/rspec/mocks/verifying_double.rb#L20-L35)
1. [Check the method visibility in `ensure_publicly_implemented`](https://github.com/rspec/rspec-mocks/blob/c1a86de005c5aa7885dbc92487422b0c0f43d324/lib/rspec/mocks/verifying_proxy.rb#L48-L54)
1. [Raise `NoMethodError` in `raise_non_public_error`](https://github.com/rspec/rspec-mocks/blob/c1a86de005c5aa7885dbc92487422b0c0f43d324/lib/rspec/mocks/error_generator.rb#L111-L115)
* The new feature to detect the method call form is necessary to keep this behavior when we introduce this optimization of `__send__`.
----------------------------------------
Misc #17535: DevelopersMeeting20210216Japan
https://bugs.ruby-lang.org/issues/17535#change-89933
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2021/02/16 13:00-17:00**
Place/Sign-up/Agenda/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 log about the discussion to a 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 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 2021/02/13. 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] 9+ messages in thread
* [ruby-core:102104] [Ruby master Misc#17535] DevelopersMeeting20210216Japan
2021-01-13 16:26 [ruby-core:102064] [Ruby master Misc#17535] DevelopersMeeting20210216Japan mame
2021-01-13 21:37 ` [ruby-core:102073] " muraken
@ 2021-01-15 9:04 ` nobu
2021-01-28 21:03 ` [ruby-core:102279] " eregontp
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: nobu @ 2021-01-15 9:04 UTC (permalink / raw)
To: ruby-core
Issue #17535 has been updated by nobu (Nobuyoshi Nakada).
* [Feature #17544] Support RFC 3339 UTC for unknown offset local time
* In RFC 3339, -00:00 is used for the time in UTC is known, but the offset to local time is unknown.
Support that representation by `-` flag for `z`.
----------------------------------------
Misc #17535: DevelopersMeeting20210216Japan
https://bugs.ruby-lang.org/issues/17535#change-89961
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2021/02/16 13:00-17:00**
Place/Sign-up/Agenda/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 log about the discussion to a 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 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 2021/02/13. 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] 9+ messages in thread
* [ruby-core:102279] [Ruby master Misc#17535] DevelopersMeeting20210216Japan
2021-01-13 16:26 [ruby-core:102064] [Ruby master Misc#17535] DevelopersMeeting20210216Japan mame
2021-01-13 21:37 ` [ruby-core:102073] " muraken
2021-01-15 9:04 ` [ruby-core:102104] " nobu
@ 2021-01-28 21:03 ` eregontp
2021-01-29 13:00 ` [ruby-core:102302] " eregontp
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: eregontp @ 2021-01-28 21:03 UTC (permalink / raw)
To: ruby-core
Issue #17535 has been updated by Eregon (Benoit Daloze).
* [Feature #15752] A dedicated module for experimental features (eregon)
* From the discussion about RubyVM in [Feature #17500], I think it became clear that RubyVM is not a good place to put experimental features.
* So, how about adding an `Experimental` or `ExperimentalFeatures` module, and add new experimental APIs there, *instead* of in RubyVM?
----------------------------------------
Misc #17535: DevelopersMeeting20210216Japan
https://bugs.ruby-lang.org/issues/17535#change-90132
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2021/02/16 13:00-17:00**
Place/Sign-up/Agenda/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 log about the discussion to a 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 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 2021/02/13. 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] 9+ messages in thread
* [ruby-core:102302] [Ruby master Misc#17535] DevelopersMeeting20210216Japan
2021-01-13 16:26 [ruby-core:102064] [Ruby master Misc#17535] DevelopersMeeting20210216Japan mame
` (2 preceding siblings ...)
2021-01-28 21:03 ` [ruby-core:102279] " eregontp
@ 2021-01-29 13:00 ` eregontp
2021-01-29 17:06 ` [ruby-core:102309] " marcandre-ruby-core
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: eregontp @ 2021-01-29 13:00 UTC (permalink / raw)
To: ruby-core
Issue #17535 has been updated by Eregon (Benoit Daloze).
* [Bug #17591] Test frameworks and REPLs do not show deprecation warnings by default (eregon)
* I think ruby-core needs to have a clear message on this, and create PRs or issues for the main test frameworks/REPLs to show examples.
----------------------------------------
Misc #17535: DevelopersMeeting20210216Japan
https://bugs.ruby-lang.org/issues/17535#change-90160
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2021/02/16 13:00-17:00**
Place/Sign-up/Agenda/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 log about the discussion to a 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 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 2021/02/13. 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] 9+ messages in thread
* [ruby-core:102309] [Ruby master Misc#17535] DevelopersMeeting20210216Japan
2021-01-13 16:26 [ruby-core:102064] [Ruby master Misc#17535] DevelopersMeeting20210216Japan mame
` (3 preceding siblings ...)
2021-01-29 13:00 ` [ruby-core:102302] " eregontp
@ 2021-01-29 17:06 ` marcandre-ruby-core
2021-01-30 17:01 ` [ruby-core:102326] " jean.boussier
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: marcandre-ruby-core @ 2021-01-29 17:06 UTC (permalink / raw)
To: ruby-core
Issue #17535 has been updated by marcandre (Marc-Andre Lafortune).
* [Bug #17592] Allow reading class instance varaibles from non-main Ractor (marcandre)
* We need way to have global config that is mutated very little. `TVar` may be a solution; reading class instance variables would be simpler, backwards compatible.
----------------------------------------
Misc #17535: DevelopersMeeting20210216Japan
https://bugs.ruby-lang.org/issues/17535#change-90166
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2021/02/16 13:00-17:00**
Place/Sign-up/Agenda/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 log about the discussion to a 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 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 2021/02/13. 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] 9+ messages in thread
* [ruby-core:102326] [Ruby master Misc#17535] DevelopersMeeting20210216Japan
2021-01-13 16:26 [ruby-core:102064] [Ruby master Misc#17535] DevelopersMeeting20210216Japan mame
` (4 preceding siblings ...)
2021-01-29 17:06 ` [ruby-core:102309] " marcandre-ruby-core
@ 2021-01-30 17:01 ` jean.boussier
2021-02-06 1:14 ` [ruby-core:102406] " sawadatsuyoshi
2021-02-11 14:48 ` [ruby-core:102460] " daniel
7 siblings, 0 replies; 9+ messages in thread
From: jean.boussier @ 2021-01-30 17:01 UTC (permalink / raw)
To: ruby-core
Issue #17535 has been updated by byroot (Jean Boussier).
- [Feature #15752] `load_iseq_eval` should override the ISeq path (byroot)
- When loading a ISeq returned by `load_iseq(fname)` `fname` should be used as top stack location.
- Right now the location of the source file (compiled with `compile_file`) is used.
- Because of it moving a source file invalidate its iseq cache.
- This makes ISeq caching impossible on some platforms like Heroku.
- `__FILE__` would need to be changed to be a method like `__dir__`
----------------------------------------
Misc #17535: DevelopersMeeting20210216Japan
https://bugs.ruby-lang.org/issues/17535#change-90184
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2021/02/16 13:00-17:00**
Place/Sign-up/Agenda/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 log about the discussion to a 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 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 2021/02/13. 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] 9+ messages in thread
* [ruby-core:102406] [Ruby master Misc#17535] DevelopersMeeting20210216Japan
2021-01-13 16:26 [ruby-core:102064] [Ruby master Misc#17535] DevelopersMeeting20210216Japan mame
` (5 preceding siblings ...)
2021-01-30 17:01 ` [ruby-core:102326] " jean.boussier
@ 2021-02-06 1:14 ` sawadatsuyoshi
2021-02-11 14:48 ` [ruby-core:102460] " daniel
7 siblings, 0 replies; 9+ messages in thread
From: sawadatsuyoshi @ 2021-02-06 1:14 UTC (permalink / raw)
To: ruby-core
Issue #17535 has been updated by sawa (Tsuyoshi Sawada).
* Feature #17608] Compact and sum in one step (sawa)
* Let `Array#sum` ignore `nil` values, or introduce a method that does that.
* The reason for adding this in the agenda is because it has been closed before being discussed.
----------------------------------------
Misc #17535: DevelopersMeeting20210216Japan
https://bugs.ruby-lang.org/issues/17535#change-90279
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2021/02/16 13:00-17:00**
Place/Sign-up/Agenda/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 log about the discussion to a 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 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 2021/02/13. 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] 9+ messages in thread
* [ruby-core:102460] [Ruby master Misc#17535] DevelopersMeeting20210216Japan
2021-01-13 16:26 [ruby-core:102064] [Ruby master Misc#17535] DevelopersMeeting20210216Japan mame
` (6 preceding siblings ...)
2021-02-06 1:14 ` [ruby-core:102406] " sawadatsuyoshi
@ 2021-02-11 14:48 ` daniel
7 siblings, 0 replies; 9+ messages in thread
From: daniel @ 2021-02-11 14:48 UTC (permalink / raw)
To: ruby-core
Issue #17535 has been updated by Dan0042 (Daniel DeLorme).
* [Bug #17594] Sort order of UTF-16LE is based on binary representation instead of codepoints (dan0042)
* 'a' < 'ā' is true for UTF-16BE and false for UTF-16LE; imho it would be better to have the same result.
* casecmp compares codepoints when ascii, bytes otherwise
----------------------------------------
Misc #17535: DevelopersMeeting20210216Japan
https://bugs.ruby-lang.org/issues/17535#change-90348
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2021/02/16 13:00-17:00**
Place/Sign-up/Agenda/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 log about the discussion to a 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 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 2021/02/13. 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] 9+ messages in thread
end of thread, other threads:[~2021-02-11 14:48 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-13 16:26 [ruby-core:102064] [Ruby master Misc#17535] DevelopersMeeting20210216Japan mame
2021-01-13 21:37 ` [ruby-core:102073] " muraken
2021-01-15 9:04 ` [ruby-core:102104] " nobu
2021-01-28 21:03 ` [ruby-core:102279] " eregontp
2021-01-29 13:00 ` [ruby-core:102302] " eregontp
2021-01-29 17:06 ` [ruby-core:102309] " marcandre-ruby-core
2021-01-30 17:01 ` [ruby-core:102326] " jean.boussier
2021-02-06 1:14 ` [ruby-core:102406] " sawadatsuyoshi
2021-02-11 14:48 ` [ruby-core:102460] " daniel
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).