From: "tenderlovemaking (Aaron Patterson) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "tenderlovemaking (Aaron Patterson)" <noreply@ruby-lang.org>
Subject: [ruby-core:122331] [Ruby Misc#21369] Propose Max Bernstein (@tekknolagi) as a core committer
Date: Wed, 28 May 2025 19:23:38 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-113478.20250528192338.10073@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-21369.20250523234245.10073@ruby-lang.org>
Issue #21369 has been updated by tenderlovemaking (Aaron Patterson).
+1
I'm working closely with Max and I can recommend him to join the team.
----------------------------------------
Misc #21369: Propose Max Bernstein (@tekknolagi) as a core committer
https://bugs.ruby-lang.org/issues/21369#change-113478
* Author: k0kubun (Takashi Kokubun)
* Status: Open
----------------------------------------
## Proposal
I'd like to propose Max Bernstein (@tekknolagi) as a committer. He has a strong background in compilers, having previously worked on CPython/Cinder at Meta, and has demonstrated leadership in designing and optimizing ZJIT.
Given that he is leading the development of the ZJIT IR and has been making a lot of contributions, I believe he should be empowered to merge such changes himself.
I'll include his message below for reference:
## Max Bernstein's Message
I have been working on Ruby since December 2024. My main contributions so far have been to ZJIT:
* The high-level IR (HIR) data structures
* The IR
* The type lattice https://github.com/Shopify/zjit/pull/19
* Transforming YARV bytecode into HIR
* Optimization on HIR, such as
* Type inference https://github.com/Shopify/zjit/pull/23
* Constant folding https://github.com/Shopify/zjit/pull/74
* Direct calls https://github.com/Shopify/zjit/pull/84
* Strength reduction
* Dead code elimination (DCE) https://github.com/Shopify/zjit/pull/89
After we moved the ZJIT repo into ruby/ruby, I have continued contributing (see [all PRs](https://github.com/ruby/ruby/pulls?q=author%3Atekknolagi)). I would like to continue contributing to ZJIT and eventually to other parts of Ruby too. Being a maintainer would make it easier to work on ZJIT, especially as we continue the project bringup phase.
--
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/
next prev parent reply other threads:[~2025-05-28 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 23:42 [ruby-core:122265] " k0kubun (Takashi Kokubun) via ruby-core
2025-05-28 19:23 ` tenderlovemaking (Aaron Patterson) via ruby-core [this message]
2025-05-30 0:02 ` [ruby-core:122339] " eileencodes (Eileen Uchitelle) via ruby-core
2025-05-30 4:11 ` [ruby-core:122340] " duerst via ruby-core
2025-06-03 23:00 ` [ruby-core:122402] " tekknolagi (Maxwell Bernstein) via ruby-core
2025-06-05 4:05 ` [ruby-core:122416] " matz (Yukihiro Matsumoto) via ruby-core
2025-06-06 4:53 ` [ruby-core:122477] " hsbt (Hiroshi SHIBATA) via ruby-core
2025-06-06 15:56 ` [ruby-core:122487] " tekknolagi (Maxwell Bernstein) via ruby-core
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-113478.20250528192338.10073@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).