[#106939] [Ruby master Bug#18455] `IO#close` has poor performance and difficult to understand semantics. — "ioquatix (Samuel Williams)" <noreply@...>

Issue #18455 has been reported by ioquatix (Samuel Williams).

10 messages 2022/01/01

[#106977] [Ruby master Feature#18461] closures are capturing unused variables — "bughit (bug hit)" <noreply@...>

Issue #18461 has been reported by bughit (bug hit).

12 messages 2022/01/05

[#106994] [Ruby master Feature#18462] Proposal to merge WASI based WebAssembly support — "katei (Yuta Saito)" <noreply@...>

Issue #18462 has been reported by katei (Yuta Saito).

8 messages 2022/01/07

[#106996] [Ruby master Feature#18463] Random number generation with xoshiro — "bbrklm (Benson Muite)" <noreply@...>

Issue #18463 has been reported by bbrklm (Benson Muite).

8 messages 2022/01/07

[#107005] [Ruby master Bug#18464] RUBY_INTERNAL_EVENT_NEWOBJ tracepoint causes an interpreter crash when combined with Ractors — "kjtsanaktsidis (KJ Tsanaktsidis)" <noreply@...>

Issue #18464 has been reported by kjtsanaktsidis (KJ Tsanaktsidis).

14 messages 2022/01/08

[#107008] [Ruby master Bug#18465] Make `IO#write` atomic. — "ioquatix (Samuel Williams)" <noreply@...>

Issue #18465 has been reported by ioquatix (Samuel Williams).

16 messages 2022/01/09

[#107073] [Ruby master Feature#18481] Porting YJIT to Rust (request for feedback) — "maximecb (Maxime Chevalier-Boisvert)" <noreply@...>

Issue #18481 has been reported by maximecb (Maxime Chevalier-Boisvert).

26 messages 2022/01/12

[#107106] [Ruby master Bug#18487] Kernel#binding behaves differently depending on implementation language of items on the stack — "alanwu (Alan Wu)" <noreply@...>

Issue #18487 has been reported by alanwu (Alan Wu).

11 messages 2022/01/13

[#107190] [Ruby master Feature#18498] Introduce a public WeakKeysMap that compares by equality — "byroot (Jean Boussier)" <noreply@...>

Issue #18498 has been reported by byroot (Jean Boussier).

17 messages 2022/01/19

[#107203] [Ruby master Bug#18501] [BUG] try to mark T_NONE object in RubyVM::InstructionSequence. load_from_binary — "byroot (Jean Boussier)" <noreply@...>

Issue #18501 has been reported by byroot (Jean Boussier).

8 messages 2022/01/20

[#107204] [Ruby master Bug#18502] Make ruby-2.7.5 on Solaris 10 ld.so.1: gcc: fatal: libintl.so.8: open failed: No such file or directory — "dklein (Dmitri Klein)" <noreply@...>

Issue #18502 has been reported by dklein (Dmitri Klein).

8 messages 2022/01/20

[#107275] [Ruby master Bug#18512] MacOS 12.1 Monterey Bug — "oucl5976@... (Paul Liu)" <noreply@...>

Issue #18512 has been reported by [email protected] (Paul Liu).

9 messages 2022/01/25

[#107291] [Ruby master Bug#18518] NoMemoryError + [FATAL] failed to allocate memory for twice 1 << large — "Eregon (Benoit Daloze)" <noreply@...>

Issue #18518 has been reported by Eregon (Benoit Daloze).

12 messages 2022/01/26

[#107310] [Ruby master Bug#18555] Running "bundle exec middleman server" on M1 Mac gives [BUG] Bus Error at 0x0000000104b04000 — "anthonyaykut (Anthony Aykut)" <noreply@...>

Issue #18555 has been reported by anthonyaykut (Anthony Aykut).

13 messages 2022/01/28

[#107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 — "mame (Yusuke Endoh)" <noreply@...>

Issue #18557 has been reported by mame (Yusuke Endoh).

18 messages 2022/01/29

[#107392] [Ruby master Bug#18560] "Compaction isn't available on this platform" error running PG test suite on ppc64le — "vo.x (Vit Ondruch)" <noreply@...>

Issue #18560 has been reported by vo.x (Vit Ondruch).

7 messages 2022/01/31

[ruby-core:107132] [Ruby master Misc#18493] Asking for commit bit

From: "Eregon (Benoit Daloze)" <noreply@...>
Date: 2022-01-14 19:53:15 UTC
List: ruby-core #107132
Issue #18493 has been updated by Eregon (Benoit Daloze).


+1 from me, @zverok has done so many documentation improvements and for that I think it makes sense for him to be committer.
And lots of other contributions to Ruby as listed above.

----------------------------------------
Misc #18493: Asking for commit bit
https://bugs.ruby-lang.org/issues/18493#change-95976

* Author: zverok (Victor Shepelev)
* Status: Open
* Priority: Normal
----------------------------------------
I feel uneasy asking for myself (as far as I can understand, it is normal that other core team member proposes new contributors), but well... I am Ukrainian, and am not exactly subtle.

So... Can I receive a commit rights?

## About me

I use Ruby professionally as my main language since 2004, and interested in language's evolution since around that time. 

I am author of many [blog articles on Ruby](https://zverok.github.io/blog/), several [Ruby gems](https://rubygems.org/profiles/zverok), a few [conference talks](https://zverok.github.io/talks.html).

I maintain [Ruby Changes](https://rubyreferences.github.io/rubychanges/) annotated changelog for each version since 2.4 (and plan to extend it back to historical versions); and [Ruby Reference](https://rubyreferences.github.io/rubyref/) attempt to compile readable "semi-official" reference. This work was recognized by Fukuoka Ruby award.

I contributed several [Ruby features](https://zverok.github.io/ruby.html#ruby-features) (mostly on idea level) and [documentation improvements](https://zverok.github.io/ruby.html#documenting-ruby) (including reviewing of docs status before each version release and catching up on under-documented features).

## Why do I want it

TBH, one of the reasons is some "sense of belonging". I would be happy to think about myself as just "Ruby commiter" not "that guy who did this and that but not a part of the team".

More seriously, I am dedicated to Ruby's documentation quality, and willing to take a responsibility to work on it on a more systematic way. It requires at least more rights on Issue Tracker (assigning tickets, closing tickets, etc) and GitHub (adding labels, reviewing PRs etc).

*(It seems to me that sometimes others got confused assuming I can merge my small docs PRs myself [until reminded otherwise](https://bugs.ruby-lang.org/issues/18404#note-32))*

## What do I want to do as a committer

* Create and maintain some perpetual list of documentation problems and possible improvements;
* Review new feature PRs and clarify what needs to be documented; provide follow-up documentation PRs;
* Regular reviews of how docs are rendered to avoid rendering problems due to unrelated changes ([example](https://github.com/ruby/ruby/pull/2810/files))
* Maybe move forward on the idea Matz once had (#16512) to merge my effort on more logical/modern official docs? 

*NB: I have some ideas for new language features but obviously wouldn't abuse commit rights to merge them.*

## Counter-points

I am not 100% sure I am qualified to be responsible for (some parts of) documentation being non-native speaker. My English became better during recent years, but it is still far from flawless. I am trying to use spell- and grammar-checking software, but not sure it fully compensates for my flaws.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread