ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "sampersand2 (Sam Westerman) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "sampersand2 (Sam Westerman)" <noreply@ruby-lang.org>
Subject: [ruby-core:120560] [Ruby master Misc#20949] DevMeeting-2025-01-09
Date: Wed, 08 Jan 2025 18:50:43 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-111371.20250108185042.18@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20949.20241212113519.18@ruby-lang.org>

Issue #20949 has been updated by sampersand2 (Sam Westerman).


* [Feature #21015] Add in a `-g` flag, like `-s` but with a few more quality of life features (sampersand2)
  * There's a hole in ruby for very simple argument processing to very short scripts (<=10 lines.)
  * The `-s` flag somewhat fills this, but most egregiously doesn't let you chain shortform options (`-abc` != `-a -b -c`).
  * I've gotten positive sentiment from quite a few people on the Ruby discord about this, so I think it's worth discussing

----------------------------------------
Misc #20949: DevMeeting-2025-01-09
https://bugs.ruby-lang.org/issues/20949#change-111371

* Author: mame (Yusuke Endoh)
* Status: Open
----------------------------------------
# The next dev meeting

**Date: 2025/01/09 13:00-17:00** (JST)
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 record of the discussion in the 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 of the meeting 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.
```

- It is recommended to add a comment by 2025/01/06. We hold a preparatory meeting to create an agenda a few days before the dev-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. We appreciate it if you could write a short summary and update from a previous discussion.




-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/

      parent reply	other threads:[~2025-01-08 18:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 11:35 [ruby-core:120215] " mame (Yusuke Endoh) via ruby-core
2025-01-05 13:52 ` [ruby-core:120484] " byroot (Jean Boussier) via ruby-core
2025-01-06 14:41 ` [ruby-core:120505] " Eregon (Benoit Daloze) via ruby-core
2025-01-08 18:50 ` sampersand2 (Sam Westerman) via ruby-core [this message]

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-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-111371.20250108185042.18@ruby-lang.org \
    --to=ruby-core@ml.ruby-lang.org \
    --cc=noreply@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 NNTP newsgroup(s).