ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: ko1@atdot.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:92281] [Ruby trunk Misc#15459] Developers Meeting before/after RubyKaigi2019
Date: Sun, 14 Apr 2019 01:12:38 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-77616.20190414011237.7d007a600e7af843@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15459.20181225083954@ruby-lang.org

Issue #15459 has been updated by ko1 (Koichi Sasada).


Hi all,

I asked Matz and we fixed dev-meeting schedule:

* 12:00-13:20 door open. I (ko1) will be there with bento-lunch.
* 13:20-13:30 opening
* 13:30-14:00 (1) keyword arguments progress report (mame)
* 14:00-14:30 (2) static checking progress report (mame)
* 14:30-15:00 (3) pattern matching (k_tsj)
* 15:00-15:30 break
* 15:30-16:00 (4) concurrency (matz)
* 16:00-16:30 (5) new built-in class/method definition (ko1)
* 16:30-17:00 break
* 17:00-18:00 (6) RubyVM + numbered parameters (eregon)
* 18:00- other remaining topics

For speakers: please prepare your slide at dev meeting. maybe 15min talk is good to reserve discussion time.

As you can see, each time slot is 30 min, so it is hard to discuss enough. So this dev-meeting is sharing ideas with committers and discuss more in break time and RubyKaigi dates.
Time schedule will not be managed strictly, but it is easy to exceeds. I ask you cooperate us to finish meeting successfully.

Thanks,
Koichi

----------------------------------------
Misc #15459: Developers Meeting before/after RubyKaigi2019
https://bugs.ruby-lang.org/issues/15459#change-77616

* Author: ko1 (Koichi Sasada)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
RubyKaigi 2019 will be at Fukuoka, Apr 18th to 20th 2019. It should be good time to gather Ruby interpreter developers.
I keep the meeting space at Fukuoka city, near to the Hakata station (the central station in Fukuoka) before and after RubyKaigi.

* Date: 
  * 2019/04/17 (Wed), before RubyKaigi2019
  * 2019/04/21 (Sun), after RubyKaigi2019
* Location
  * Fukuoka Ruby Content Industry Promotion Center,
    Fukuoka Higashi Sougouchousha 5th floor,
    1 Chome-17-1 Hakataekihigashi, Hakata Ward, Fukuoka
  * 福岡県Ruby・コンテンツ産業振興センター (in Japanese)
    http://frac.jp/about/ (Japanese page)

There are two days but Matz can only attend Wednesday.

Maybe on Wednesday we can have a meeting with agenda, for example about Ruby 3.

I'm not sure we need Sunday meetup, but I keep a room for people who want to continue development.
If nobody attend Sunday meetup, I'll cancel room reservation.

I hope we can discuss topics on Wed and continue to discuss RubyKaigi days, and make a progress on Sunday.

## Travel support

Same as last RubyKaigi, Cookpad Inc. will support travel fee (except hotel room fee) so please consider to attend this dev-meeting.
Also please invite people who are not a MRI committer but who are important person to talk with us.
I'll announce about this travel support soon.

## Registration

* Sign-up on https://rubyassociation.doorkeeper.jp/events/85108

## Call for Topics

* Please comment discussion topics on Wed meeting.
* We have limited time to discuss, so that I'll ask Matz which topics we should talk with, and make time schedule in advance if there are many topics.
* Meeting room has a projector so you can bring your slides.
* Maybe attendee's topics will be prioritize.

## Conclusion

Anyway, please keep your schedule.
FYI: Fukuoka city does not have enough hotel rooms so I recommend you to keep your rooms as soon as possible.

Thanks,
Koichi




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

  parent reply	other threads:[~2019-04-14  1:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-15459.20181225083954@ruby-lang.org>
2018-12-25  8:39 ` [ruby-core:90699] [Ruby trunk Misc#15459] Developers Meeting before/after RubyKaigi2019 ko1
2019-02-11  0:44 ` [ruby-core:91506] " merch-redmine
2019-03-18  4:49 ` [ruby-core:91860] " ko1
2019-03-18  4:52 ` [ruby-core:91861] " ko1
2019-03-18  5:12 ` [ruby-core:91862] " ko1
2019-03-24  5:51 ` [ruby-core:91963] " glass.saga
2019-04-02 18:34 ` [ruby-core:92114] " rafaelmfranca
2019-04-03 12:21 ` [ruby-core:92134] " lisa.ugray
2019-04-03 12:24 ` [ruby-core:92136] " eregontp
2019-04-07 17:21 ` [ruby-core:92181] " eregontp
2019-04-12  1:13 ` [ruby-core:92252] " ko1
2019-04-13  9:46 ` [ruby-core:92274] " duerst
2019-04-13 14:10 ` [ruby-core:92278] " kazuki
2019-04-14  1:12 ` ko1 [this message]
2019-04-15  0:01 ` [ruby-core:92285] " ko1
2019-04-16  8:44 ` [ruby-core:92303] " ko1
2019-04-16 15:07 ` [ruby-core:92307] " manga.osyo
2019-04-16 17:24 ` [ruby-core:92308] " ko1
2019-04-17  1:03 ` [ruby-core:92311] " alanwucanada

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-77616.20190414011237.7d007a600e7af843@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).