From: hsbt@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:100435] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
Date: Tue, 20 Oct 2020 00:04:23 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-88053.20201020000422.18@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17200.20200928232433.18@ruby-lang.org
Issue #17200 has been updated by hsbt (Hiroshi SHIBATA).
* [Feature #17267] Remove Win32API at Ruby 3.0
* Does anyone oppose it?
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-88053
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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: 2020/10/19 (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/
next prev parent reply other threads:[~2020-10-20 0:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
2020-10-01 13:34 ` [ruby-core:100256] " finch.parker
2020-10-01 19:13 ` [ruby-core:100258] " grzegorz.jakubiak
2020-10-01 19:41 ` [ruby-core:100260] " merch-redmine
2020-10-01 22:58 ` [ruby-core:100268] " merch-redmine
2020-10-03 7:32 ` [ruby-core:100287] " glass.saga
2020-10-06 9:39 ` [ruby-core:100307] " aycabta
2020-10-11 12:06 ` [ruby-core:100372] " kazuki
2020-10-14 9:31 ` [ruby-core:100399] " eregontp
2020-10-16 5:39 ` [ruby-core:100417] " marcandre-ruby-core
2020-10-18 0:36 ` [ruby-core:100421] " tenderlove
2020-10-19 0:16 ` [ruby-core:100423] " marcandre-ruby-core
2020-10-20 0:04 ` hsbt [this message]
2020-10-21 16:37 ` [ruby-core:100475] " grzegorz.jakubiak
2020-10-22 0:58 ` [ruby-core:100486] " ko1
2020-10-22 17:17 ` [ruby-core:100508] " eregontp
2020-10-23 5:42 ` [ruby-core:100513] " nobu
2020-10-24 3:38 ` [ruby-core:100520] " koic.ito
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-88053.20201020000422.18@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).