Project

General

Profile

Actions

Misc #20717

closed

DevMeeting-2024-10-03

Added by mame (Yusuke Endoh) about 1 year ago. Updated 12 months ago.

Status:
Closed
Assignee:
-
[ruby-core:119081]

Description

The next dev meetingΒΆ

Date: 2024/10/03 13:00-17:00 (JST)
Log: https://github.com/ruby/dev-meeting-log/blob/master/2024/DevMeeting-2024-10-03.md

  • 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 2024/09/30. 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. 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.

Related issues 1 (1 open β€” 0 closed)

Related to Ruby - Misc #14770: [META] DevelopersMeetingOpenActions
Actions #1

Updated by mame (Yusuke Endoh) about 1 year ago

  • Related to Misc #14770: [META] DevelopersMeeting added

Updated by byroot (Jean Boussier) 12 months ago

  • [Misc #20746] Request to migrate the json gem from flori/json repository to ruby/json (byroot)
    • Current maintainers don't have full administrative rights over the repo, which is problematic.
    • We've been trying to contact flori to try to resolve this situation with a transfer for over two years now, without success.

Updated by tenderlovemaking (Aaron Patterson) 12 months ago Β· Edited

  • [Misc #20728] Add eileencodes as a core committer
    • She's made many useful contributions
    • She's currently helping to maintain Prism / Prism Compiler and it would be helpful if she can merge her own commits

Updated by Eregon (Benoit Daloze) 12 months ago Β· Edited

  • [Feature #20750] Expose ruby_thread_has_gvl_p in ruby/thread.h (eregon)
    • I think rb_thread_call_with_gvl() should be allowed if the GVL is already acquired, it seems a much nicer way to solve the use cases the OP pointed out (for a C function which can be called either with or without GVL).
    • @ko1 (Koichi Sasada) What do you think, how do you want to solve that issue?

Updated by hsbt (Hiroshi SHIBATA) 12 months ago Β· Edited

Updated by Eregon (Benoit Daloze) 12 months ago Β· Edited

  • [Feature #6012] Proc#source_location also return the column (eregon)
    • How about {Proc,Method,UnboundMethod}.source_location #=> [path, start_line, start_column, start_offset, end_line, end_column, end_offset] ?
    • How about {Proc,Method,UnboundMethod}.code_location #=> object with path, start_line, start_column, start_offset, end_line, end_column, end_offset and code ?
    • It would avoid having to use RubyVM to find this information.
    • If some do not like these APIs, what do they suggest instead?
Actions #7

Updated by mame (Yusuke Endoh) 12 months ago

  • Description updated (diff)
Actions #8

Updated by byroot (Jean Boussier) 12 months ago

  • Status changed from Open to Closed
Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0Like0Like0Like0