From: mame@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:91209] [Ruby trunk Misc#15546] DevelopersMeeting20190207Japan
Date: Mon, 21 Jan 2019 09:30:08 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-76447.20190121093006.f267c87e8c082997@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15546.20190119002150@ruby-lang.org
Issue #15546 has been updated by mame (Yusuke Endoh).
* [Feature #5632] Attempt to open included class shades it instead. (mame)
* Matz, do you still want to "fix" this issue? And how?
----------------------------------------
Misc #15546: DevelopersMeeting20190207Japan
https://bugs.ruby-lang.org/issues/15546#change-76447
* Author: shyouhei (Shyouhei Urabe)
* Status: Open
* Priority: Normal
* Assignee:
----------------------------------------
Please comment 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 ticket comments)
*DO NOT* discuss then on this ticket, please.
----
Date: 2019/02/07 (Thu)
Time: 13:00-17:00 (JST)
Place: MoneyForward.com (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/117659/
log: https://docs.google.com/document/d/e/2PACX-1vRbZsyab3LFwhcti973QNpaifVgdJHdxu00V0qdXk6EPv76OzfPRbqQHyUqIVhlWF7-HBv0QiIivrQ2/pub
logedit: https://docs.google.com/document/d/1U498rgriOF4094D9UKBJyjt0PFzXFvGSvMqLjci2AN8/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 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 is scheduled according to when/where we can reserve Matz's time.
# Agenda
## Next dev-meeting
## About 2.7 timeframe
## Check security tickets
## Carry-over from previous meeting(s)
## From Attendees
## From non-attendees
* [Feature #6470] Make attr_accessor return the list of generated method (eregon)
* I think not all related issues were considered. There are use cases, both for private attr_* and other modifiers (e.g., volatile, atomic, tracing accesses, getter/setter decorators, etc).
----
Please comment 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 about 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 about this feature.
```
We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2019-01-21 9:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15546.20190119002150@ruby-lang.org>
2019-01-19 0:21 ` [ruby-core:91164] [Ruby trunk Misc#15546] DevelopersMeeting201900207Japan shyouhei
2019-01-19 5:24 ` [ruby-core:91169] " aycabta
2019-01-19 12:50 ` [ruby-core:91180] [Ruby trunk Misc#15546] DevelopersMeeting20190207Japan eregontp
2019-01-21 3:46 ` [ruby-core:91199] " hsbt
2019-01-21 7:47 ` [ruby-core:91202] " glass.saga
2019-01-21 9:30 ` mame [this message]
2019-01-24 14:08 ` [ruby-core:91251] " mame
2019-01-24 20:05 ` [ruby-core:91253] " kevin.deisz
2019-01-26 8:35 ` [ruby-core:91276] " samuel
2019-01-30 3:35 ` [ruby-core:91325] " muraken
2019-02-01 7:34 ` [ruby-core:91371] " hsbt
2019-02-03 22:28 ` [ruby-core:91387] " bartdewater
2019-02-04 18:37 ` [ruby-core:91395] " alanwucanada
2019-02-05 4:48 ` [ruby-core:91405] " manga.osyo
2019-02-05 4:58 ` [ruby-core:91406] " manga.osyo
2019-02-06 1:37 ` [ruby-core:91415] " glass.saga
2019-02-07 5:58 ` [ruby-core:91448] " matz
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-76447.20190121093006.f267c87e8c082997@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).