[ruby-core:101735] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[ruby-core:101735] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[mame]

Issue #17480 has been reported by mame (Yusuke Endoh).

----------------------------------------
Misc #17480: DevelopersMeeting20210113Japan
https://bugs.ruby-lang.org/issues/17480

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/01/13 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.
```

- Comment deadline: 2021/01/06 (one week before the 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.




-- 
https://bugs.ruby-lang.org/

[ruby-core:101740] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[mame]

Issue #17480 has been updated by mame (Yusuke Endoh).


* [Feature #17472] HashWithIndifferentAccess like Hash extension
  * It is a good idea for Ruby 3.1 to provide small but immediate improvements like this. The constant name should be discussed.
* [Feature #17473] Make Pathname to embedded class of Ruby
  * We want to make Rubygems independent with any gems. Rubygems heavily depends on Pathname. So how about making it built-in?
* [Feature #16989] Sets: need ♥️
  * SortedSet has been removed from set.rb, so there is no longer a dependency problem.
* [Feature #17479] Enable to get "--backtrace-limit" value by "$-B"
  * Some libraries need to know what --backtrace-limit is specified. How about providing a command-line option `-B` as an alias, and a special variable `$-B` too?

----------------------------------------
Misc #17480: DevelopersMeeting20210113Japan
https://bugs.ruby-lang.org/issues/17480#change-89562

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/01/13 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.
```

- Comment deadline: 2021/01/06 (one week before the 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.




-- 
https://bugs.ruby-lang.org/

[ruby-core:101742] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[chris]

Issue #17480 has been updated by chrisseaton (Chris Seaton).


* [Feature #17327] The Queue constructor should take an initial set of items (chrisseaton)
  * This simple feature captures a common pattern. There's a PR with an implementation based on initial feedback and specs https://github.com/ruby/ruby/pull/3768.

----------------------------------------
Misc #17480: DevelopersMeeting20210113Japan
https://bugs.ruby-lang.org/issues/17480#change-89563

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/01/13 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.
```

- Comment deadline: 2021/01/06 (one week before the 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.




-- 
https://bugs.ruby-lang.org/

[ruby-core:101810] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[takashikkbn]

Issue #17480 has been updated by k0kubun (Takashi Kokubun).


* [Feature #16806] Struct#initialize accepts keyword arguments too by default (k0kubun)
  * Is there any update on kwargs since [the last discussion](https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20200514Japan.md#feature-16806-structinitialize-accepts-keyword-arguments-too-by-default-k0kubun)? Can we introduce a warning for it in 3.1?
* [Feature #17490] Rename RubyVM::MJIT to RubyVM::JIT (k0kubun)
  * Any objections, or suggestions to the release plan?

----------------------------------------
Misc #17480: DevelopersMeeting20210113Japan
https://bugs.ruby-lang.org/issues/17480#change-89637

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/01/13 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.
```

- Comment deadline: 2021/01/06 (one week before the 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.




-- 
https://bugs.ruby-lang.org/

[ruby-core:101850] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[zverok.offline]

Issue #17480 has been updated by zverok (Victor Shepelev).


* [Misc #17499] Documentation backporting (zverok)
  * Address systematic lack of docs at docs.ruby-lang.org
* [Bug #16497] StringIO#internal_encoding is broken (more severely in 2.7) (zverok)
  * Still is, as of 3.0.0 
* [Misc #17407] `Fiber.current` and `require 'fiber'` (zverok)
  * The requirement seem to not be rethought for a long time, can it be lifted?
* [Feature #17312] New methods in Enumerable and Enumerator::Lazy (zverok)
  * Matz approved #compact, PR is provided, can it be merged?..
* [Feature #17330] `Object#non` (zverok)
  * Experimental proposal about syntax like `calculation.non(&:zero?) || something`
* [Feature #16122] `Struct::Value`: simple immutable value object (zverok)
  * The discussion hanged a year ago with Matz saying "We need to discuss further". Maybe now after 3.0 it is the time?

----------------------------------------
Misc #17480: DevelopersMeeting20210113Japan
https://bugs.ruby-lang.org/issues/17480#change-89682

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/01/13 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.
```

- Comment deadline: 2021/01/06 (one week before the 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.




-- 
https://bugs.ruby-lang.org/

[ruby-core:101854] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[eregontp]

Issue #17480 has been updated by Eregon (Benoit Daloze).


* [Feature #17500] Move RubyVM::* to ExperimentalFeatures (eregon)
  * I think this is the best solution, for everyone. Could matz and ruby-core agree to this?

----------------------------------------
Misc #17480: DevelopersMeeting20210113Japan
https://bugs.ruby-lang.org/issues/17480#change-89691

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/01/13 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.
```

- Comment deadline: 2021/01/06 (one week before the 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.




-- 
https://bugs.ruby-lang.org/

[ruby-core:101873] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[jzakiya]

Issue #17480 has been updated by jzakiya (Jabari Zakiya).


* [Feature ``#17496``] ``Add constant Math::TAU`` (jzakiya)
     * Reconsider adding to Ruby core, as more languages have. Increased adoption|use since last consideration. It has become ``time proven``, https://bugs.ruby-lang.org/issues/4897#note-41




----------------------------------------
Misc #17480: DevelopersMeeting20210113Japan
https://bugs.ruby-lang.org/issues/17480#change-89710

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/01/13 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.
```

- Comment deadline: 2021/01/06 (one week before the 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.




-- 
https://bugs.ruby-lang.org/

[ruby-core:101875] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[marcandre-ruby-core]

Issue #17480 has been updated by marcandre (Marc-Andre Lafortune).


* [Misc #0] Comment Deadline (marcandre)
  * Please make comment deadline closer to meetings (1 or 2 days, not 7).


----------------------------------------
Misc #17480: DevelopersMeeting20210113Japan
https://bugs.ruby-lang.org/issues/17480#change-89715

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/01/13 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.
```

- Comment deadline: 2021/01/06 (one week before the 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.




-- 
https://bugs.ruby-lang.org/

[ruby-core:101887] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[nobu]

Issue #17480 has been updated by nobu (Nobuyoshi Nakada).


* [Feature #17099] Remove boolean argument and warning from `Module#attr` (S_H_)

----------------------------------------
Misc #17480: DevelopersMeeting20210113Japan
https://bugs.ruby-lang.org/issues/17480#change-89728

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/01/13 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.
```

- Comment deadline: 2021/01/06 (one week before the 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.




-- 
https://bugs.ruby-lang.org/

[ruby-core:101944] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[merch-redmine]

Issue #17480 has been updated by jeremyevans0 (Jeremy Evans).


* [Bug #17429] Prohibit include/prepend in refinement modules (jeremyevans0)
  * I've added a pull request for this, is it OK to merge?
  * Do we want to implement a feature to copy methods from a module into a refinement, such as the `:import` option?
* [Bug #17423] `Prepend` should prepend a module before the class (jeremyevans0)
  * Should `Module#prepend` add iclasses to the start of the ancestor chain if the receiver already includes the module?
  * Should `Module#prepend` add iclasses to the start of the ancestor chain if the receiver has already prepended the module?
  * Should `Module#prepend` add iclasses to the start of the ancestor chain if the ancestor chain already starts with the iclasses for the prepended module?
  * If the answer to any question is yes, can we decide on details for how prepend should work?

----------------------------------------
Misc #17480: DevelopersMeeting20210113Japan
https://bugs.ruby-lang.org/issues/17480#change-89791

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/01/13 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.
```

- Comment deadline: 2021/01/06 (one week before the 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.




-- 
https://bugs.ruby-lang.org/

[ruby-core:102007] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[zn]

Issue #17480 has been updated by znz (Kazuhiro NISHIYAMA).


* [Bug #17517] File.expand_path returns us-ascii when both arguments are ascii compat (znz)
  * require_relative use expand_path, and it returns us-ascii

----------------------------------------
Misc #17480: DevelopersMeeting20210113Japan
https://bugs.ruby-lang.org/issues/17480#change-89852

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/01/13 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.
```

- Comment deadline: 2021/01/06 (one week before the 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.




-- 
https://bugs.ruby-lang.org/

[ruby-core:102028] [Ruby master Misc#17480] DevelopersMeeting20210113Japan

[mame]

Issue #17480 has been updated by mame (Yusuke Endoh).


marcandre (Marc-Andre Lafortune) wrote in #note-8:
> * [Misc #0] Comment Deadline (marcandre)
>   * Please make comment deadline closer to meetings (1 or 2 days, not 7).

Okay. In the next ticket, I will change it to 3 days and rephase "deadline" to "recommendation".

The reason of the deadline is that a few voluntary committers (including I) hold a preparatory meeting to preread the tickets and create a agenda a few days before the dev-meeting. It is recommended to add a ticket before the pre-reading meeting.

So far, many of the pre-reading meetings were held two days before the dev-meeting (in JST). Considering a time difference, I'd like to set it to 3 days before. You can add comments after the deadline, but sorry if I miss them.

----------------------------------------
Misc #17480: DevelopersMeeting20210113Japan
https://bugs.ruby-lang.org/issues/17480#change-89880

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/01/13 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.
```

- Comment deadline: 2021/01/06 (one week before the 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.




-- 
https://bugs.ruby-lang.org/