ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: eregontp@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:92671] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan
Date: Wed, 15 May 2019 21:46:02 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-78034.20190515214602.5151175cd2652801@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15782.20190422123643@ruby-lang.org

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


* [Feature #14844] Future of RubyVM::AST?
  * What can we do about this? The current situation is confusing for everyone, the API sounds "blessed" by being in core but it's actually experimental and unstable.
    Can we document it as clearly as possible when this API should be used?
    Could we improve the API so it's less fragile to parser changes and could be reasonably implemented on other Ruby implementations?

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-78034

* Author: k0kubun (Takashi Kokubun)
* 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/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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

----

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/

  parent reply	other threads:[~2019-05-15 21:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-15782.20190422123643@ruby-lang.org>
2019-04-22 12:36 ` [ruby-core:92365] [Ruby trunk Misc#15782] DevelopersMeeting201905XXJapan takashikkbn
2019-04-22 12:43 ` [ruby-core:92366] " takashikkbn
2019-04-23  4:42 ` [ruby-core:92373] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan tenderlove
2019-04-23 15:05 ` [ruby-core:92385] " grzegorz.jakubiak
2019-04-26  7:11 ` [ruby-core:92415] " koic.ito
2019-04-27  3:24 ` [ruby-core:92430] " merch-redmine
2019-04-27 13:26 ` [ruby-core:92437] " alanwucanada
2019-04-27 14:23 ` [ruby-core:92439] " manga.osyo
2019-04-30 14:54 ` [ruby-core:92496] " manga.osyo
2019-05-01 10:07 ` [ruby-core:92512] " lourens
2019-05-01 22:36 ` [ruby-core:92521] " samuel
2019-05-06  8:10 ` [ruby-core:92570] " grzegorz.jakubiak
2019-05-12  0:39 ` [ruby-core:92624] " nobu
2019-05-12  8:17 ` [ruby-core:92626] " takashikkbn
2019-05-15  9:13 ` [ruby-core:92655] " eregontp
2019-05-15 12:45 ` [ruby-core:92658] " hsbt
2019-05-15 21:46 ` eregontp [this message]
2019-05-19 21:54 ` [ruby-core:92724] " bogdanvlviv
2019-05-20  0:14 ` [ruby-core:92726] " shyouhei
2019-05-21  2:15 ` [ruby-core:92734] " manga.osyo
2019-05-21  2:21 ` [ruby-core:92735] " mame
2019-05-22  2:41 ` [ruby-core:92753] " muraken

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-78034.20190515214602.5151175cd2652801@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).