Issue #21630 has been updated by Earlopain (Earlopain _). This is certainly a bit unexpected to me. I really appreciate your vote of confidence, thank you. I have spent most of my time for ruby on prism itself: * Mostly the C parser as of late (and rarely `prism_compile.c` if needed) * Before that, I made sure that the prism AST translation for the `parser` gem was in a usable state for RuboCop I do want to make it very clear that I actually have no idea what I'm doing. I never went deep into C as a language and also have no knowledge of parser internals and how they're supposed to work/be written. That seems to have went well enough given this ticket I suppose. Take that as first-hand proof that prism is rather easy to contribute to. With that disclaimer out of the way, I wouldn't mind it. Prism is a great achievement and I want to make sure that it is as good as it can be, as far as I am able. I like writing Ruby more than writing Ruby tooling in C, but for this I will make an exception (; ---------------------------------------- Misc #21630: Suggest @Earlopain for core contributor https://bugs.ruby-lang.org/issues/21630#change-114807 * Author: kddnewton (Kevin Newton) * Status: Open ---------------------------------------- @Earlopain has been prolifically contributing to Prism for over a year, in addition to other various changes around ruby/ruby, like [96fdaf2e](https://github.com/ruby/ruby/commit/96fdaf2e393933fdd128cd1a41fa9b2062792a15), [3826019f](https://github.com/ruby/ruby/commit/3826019f310991aedf0612408d7b821faf513ca4), [a82e7132](https://github.com/ruby/ruby/commit/a82e7132df71bd99b5d02c0c8a348bc7526a5fbb), and [many more](https://github.com/ruby/ruby/commits/master/?author=Earlopain). I would very much like @Earlopain to be able to merge their own contributions to Ruby, since they have been of such high quality for so long. -- https://bugs.ruby-lang.org/