From: merch-redmine@jeremyevans.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:95348] [Ruby master Misc#16232] DevelopersMeeting20191017Japan
Date: Tue, 15 Oct 2019 20:44:21 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-82057.20191015204420.c451cddac15b1b50@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16232.20191003063416@ruby-lang.org
Issue #16232 has been updated by jeremyevans0 (Jeremy Evans).
* [Feature #16131] Remove $SAFE, taint and trust (jeremyevans)
* Does anyone have time to review the patch (extensive changes, mostly code deletion)?
* How do we want to handle included libraries with separate upstreams that want to be compatible with older Ruby versions (bundler, rubygems, etc.)?
----------------------------------------
Misc #16232: DevelopersMeeting20191017Japan
https://bugs.ruby-lang.org/issues/16232#change-82057
* 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: 10/17 13:00-17:00
Place and Sign-up: (See the Log)
log: https://docs.google.com/document/d/1-IC98nOPY_FZnne2PXILYAaxt6PqHfhphAI908K3vD8
# 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-10-15 20:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16232.20191003063416@ruby-lang.org>
2019-10-03 6:34 ` [ruby-core:95195] [Ruby master Misc#16232] DevelopersMeeting20191017Japan mame
2019-10-03 10:02 ` [ruby-core:95197] " jean.boussier
2019-10-03 23:30 ` [ruby-core:95211] " merch-redmine
2019-10-09 10:52 ` [ruby-core:95290] " sam.saffron
2019-10-11 17:26 ` [ruby-core:95304] " rafael
2019-10-15 10:55 ` [ruby-core:95329] " kou
2019-10-15 11:26 ` [ruby-core:95330] " zverok.offline
2019-10-15 20:44 ` merch-redmine [this message]
2019-10-16 5:45 ` [ruby-core:95352] " ko1
2019-10-16 6:38 ` [ruby-core:95354] " mame
2019-10-16 6:55 ` [ruby-core:95355] " mame
2019-10-16 16:17 ` [ruby-core:95369] " daniel
2019-10-17 1:46 ` [ruby-core:95374] " zn
2019-10-17 2:12 ` [ruby-core:95375] " XrXr
2019-10-17 2:37 ` [ruby-core:95376] " manga.osyo
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-82057.20191015204420.c451cddac15b1b50@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).