From: zverok.offline@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:94631] [Ruby master Misc#15996] DevelopersMeeting20190829Japan
Date: Wed, 28 Aug 2019 11:44:48 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-81228.20190828114448.3687633c52d28b81@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15996.20190711123559@ruby-lang.org
Issue #15996 has been updated by zverok (Victor Shepelev).
@mame OK, sorry. I was not sure how the process looks internally (e.g. should I save the space and attention of the reader in agenda by just listing things shortly, or provide the full context in-place). Here are updated descriptions, just in case:
* [Feature #14781] `Enumerator.generate`: Matz seems to have liked the idea and name proposed; implementation patch provided; the name should be decided upon: either `generate`, or, maybe, `produce` (looking like more-or-less oppose to `reduce`)
* [Feature #14784] `Comparable#clamp` with a range. The issue generally agreed on, except for behavior with upper bound with excluding-end range. `ArgumentError` is proposed for this case.
----------------------------------------
Misc #15996: DevelopersMeeting20190829Japan
https://bugs.ruby-lang.org/issues/15996#change-81228
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
* Assignee:
----------------------------------------
Please comment on your favorite ticket numbers you want to ask to discuss with your *SHORT* comment or summary.
(your summary/comment will help us because we don't need to read all of the ticket comments)
*DO NOT* discuss then on this ticket, please.
----
Date: 2019/08/29 (Thu)
Time: 13:00-17:00 (JST)
Place and Sign-up: https://connpass.com/event/139231/
log: https://docs.google.com/document/d/1XypDO1crRV9uNg1_ajxkljVdN8Vdyl5hnz462bDQw34/edit
# NOTES
- 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.
# Agenda
## Next dev-meeting
## About 2.7 timeframe
## Check security tickets
## Discussion
----
Please comment on your favorite ticket we need to discuss with *the following format*.
```
* [Ticket ref] Ticket title (your name)
* your comment why you want to put this ticket here if you want to add.
```
Your comment is very important if you are no attendee because we can not ask why you want to discuss it.
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.
```
We don't guarantee to put tickets in the agenda if the comment violates the format (because it is hard to copy&paste).
**A short summary of a ticket is strongly recommended. We cannot read all discussion of the ticket in a limited time.**
A proposal is often changed during the discussion, so it is very helpful to summarize the latest/current proposal, post it as a comment in the ticket, and write a link to the comment.
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2019-08-28 11:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15996.20190711123559@ruby-lang.org>
2019-07-11 12:36 ` [ruby-core:93683] [Ruby master Misc#15996] DevelopersMeeting20190820Japan mame
2019-07-11 12:37 ` [ruby-core:93684] " mame
2019-07-11 12:39 ` [ruby-core:93685] " mame
2019-07-23 13:24 ` [ruby-core:93883] " nobu
2019-07-23 18:10 ` [ruby-core:93890] " merch-redmine
2019-07-29 10:36 ` [ruby-core:93995] " glass.saga
2019-07-30 4:32 ` [ruby-core:94023] " s+ruby
2019-07-30 8:42 ` [ruby-core:94043] " ko1
2019-07-30 11:30 ` [ruby-core:94049] " nobu
2019-07-31 3:49 ` [ruby-core:94065] " nobu
2019-07-31 9:45 ` [ruby-core:94070] " eregontp
2019-08-02 0:08 ` [ruby-core:94104] " nobu
2019-08-07 3:04 ` [ruby-core:94170] " ko1
2019-08-07 13:10 ` [ruby-core:94181] [Ruby master Misc#15996] DevelopersMeeting20190829Japan nobu
2019-08-11 10:35 ` [ruby-core:94274] " zverok.offline
2019-08-13 9:29 ` [ruby-core:94319] " mtsmfm
2019-08-14 12:40 ` [ruby-core:94350] " nobu
2019-08-21 14:06 ` [ruby-core:94459] " takashikkbn
2019-08-22 0:09 ` [ruby-core:94469] " muraken
2019-08-22 0:47 ` [ruby-core:94470] " mame
2019-08-23 0:56 ` [ruby-core:94490] " mame
2019-08-23 2:44 ` [ruby-core:94494] " mame
2019-08-23 9:13 ` [ruby-core:94500] " manga.osyo
2019-08-23 17:43 ` [ruby-core:94509] " zverok.offline
2019-08-26 22:11 ` [ruby-core:94590] " daniel
2019-08-27 10:23 ` [ruby-core:94604] " duerst
2019-08-27 11:04 ` [ruby-core:94605] " shevegen
2019-08-27 14:56 ` [ruby-core:94611] " daniel
2019-08-28 3:07 ` [ruby-core:94626] " mame
2019-08-28 8:17 ` [ruby-core:94629] " mame
2019-08-28 11:44 ` zverok.offline [this message]
2019-08-28 13:27 ` [ruby-core:94632] " mame
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-81228.20190828114448.3687633c52d28b81@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).