ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: nobu@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:93025] [Ruby trunk Misc#15874] DevelopersMeeting20190613Japan
Date: Sat, 08 Jun 2019 12:46:07 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-78400.20190608124607.b6b149c19384cbcd@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15874.20190524155851@ruby-lang.org

Issue #15874 has been updated by nobu (Nobuyoshi Nakada).


* [Bug #15908] Detecting BOM with non-UTF encoding

----------------------------------------
Misc #15874: DevelopersMeeting20190613Japan
https://bugs.ruby-lang.org/issues/15874#change-78400

* Author: mame (Yusuke Endoh)
* 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/06/13 (Wed)
Time: 14:00-17:30 (JST)
Place and Sign-up: https://ruby.connpass.com/event/132888/
log: https://docs.google.com/document/d/1XP_e-3utXlCaxZLJrov6c428ZNaMPmxa3eh9MASrzkI/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)

None.

## 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-06-08 12:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-15874.20190524155851@ruby-lang.org>
2019-05-24 15:58 ` [ruby-core:92828] [Ruby trunk Misc#15874] DevelopersMeeting20190613Japan mame
2019-05-24 20:39 ` [ruby-core:92830] " XrXr
2019-05-25  0:13 ` [ruby-core:92834] " nobu
2019-05-27  1:00 ` [ruby-core:92853] " s+ruby
2019-05-27  9:53 ` [ruby-core:92858] " tagomoris
2019-05-28  9:54 ` [ruby-core:92874] " jean.boussier
2019-05-30 22:31 ` [ruby-core:92898] " eregontp
2019-06-01  1:36 ` [ruby-core:92921] " nobu
2019-06-06  1:27 ` [ruby-core:92992] " nobu
2019-06-06  9:27 ` [ruby-core:93003] " eregontp
2019-06-08 12:46 ` nobu [this message]
2019-06-08 12:58 ` [ruby-core:93026] " email
2019-06-11 17:45 ` [ruby-core:93047] " merch-redmine
2019-06-12  6:22 ` [ruby-core:93059] " mame
2019-06-12 13:20 ` [ruby-core:93069] " takashikkbn

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-78400.20190608124607.b6b149c19384cbcd@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).