https://www.phoronix.com/news/Alex-Gaynor-Rust-Maintainer
Alex Gaynor recently announced he is formally stepping down as one of the maintainers of the Rust for Linux kernel code with the removal patch now queued for merging in Linux 6.19.
Alex Gaynor was one of the original developers to experiment with Rust code for Linux kernel modules. He's drifted away from Rust Linux kernel development for a while due to lack of time and is now formally stepping down as a listed co-maintainer of the Rust code. After Wedson Almeida Filho stepped down last year as a Rust co-maintainer, this now leaves Rust For Linux project leader Miguel Ojeda as the sole official maintainer of the code while there are several Rust code reviewers.
Alex Gaynor wrote on the patch removing himself as a maintainer of the Rust code:
"I've long since stopped having the time to contribute code or reviews, this acknowledges that.
Geoffrey Thomas and I created the "linux-kernel-module-rust" project at PyCon in 2018, as an experiment to see if we could make it possible to write kernel modules in Rust. The Rust for Linux effort has far exceeded anything we could have expected at the time.
I want to thank all the Rust for Linux contributors, past and present, who have helped make this a reality -- and in particularly Miguel, who really transformed this project from an interesting demo to something that could really land in mainline."
(Score: 3, Insightful) by Gaaark on Sunday November 30, @06:14PM (6 children)
Wondered what that meant.
So there is Officially one maintainer in a large bulk of software that was recently included in the kernel...
...don't know Rust, but doesn't that seem like a bit of a kick in the pants?
--- Please remind me if I haven't been civil to you: I'm channeling MDC. I have always been here. ---Gaaark 2.0 --
(Score: 2, Touché) by Anonymous Coward on Sunday November 30, @07:28PM (1 child)
Take a big hot dump into the top of trunk and make someone else maintain it.
(Score: 2, Insightful) by Anonymous Coward on Monday December 01, @12:05PM
Must have studied at the systemd school of development
(Score: 2) by sneftel on Monday December 01, @07:11AM (3 children)
No. What? No. How did you conclude “there is Officially one maintainer” from “formally stepping down as one of the maintainers”?
The patch removes him from the list of contributors.
(Score: 2) by Gaaark on Monday December 01, @11:19AM (2 children)
The patch itself shows there is only one Maintainer: 'M'
There are 3 Reviewers listed as well: 'R', but there is now only one 'Maintainer', Miguel Ojeda.
--- Please remind me if I haven't been civil to you: I'm channeling MDC. I have always been here. ---Gaaark 2.0 --
(Score: 3, Informative) by sneftel on Monday December 01, @04:23PM (1 child)
Ah, I see what you’re saying. It’s not unusual for even a major feature to have only one maintainer. There’s no formal order of succession, and Gaynor already having been de facto retired is, I assume, the only reason there’s two for that one. The patch only lists three reviewers because that’s how source code patches work: a few lines are listed before and after each changed line to help identify where the patch goes even if the file has been edited in the interim. If you look at the actual maintainers file you’ll see that there’s like eight reviewers for the feature, which is a bafflingly high number but suggests that there’s quite a deep bench of potential maintainers-to-be.
(Score: 2) by Gaaark on Monday December 01, @10:37PM
Thank you! :)
--- Please remind me if I haven't been civil to you: I'm channeling MDC. I have always been here. ---Gaaark 2.0 --
(Score: 4, Insightful) by VLM on Monday December 01, @03:34PM (1 child)
Rust is the only large scale language I know of where the community is too toxic to consider its use. How did they end up that way? It's wild.
Its not a memory-safe problem, for example golang isn't a raging dumpster fire. Just something about rust, the people who fund it or the people who they fund or ?
(Score: 4, Insightful) by Rich on Monday December 01, @08:35PM
Wayland, too, or actually the whole "Freedesktop" ilk with GTK4 and what not else. A platform should be there to service its clients. Yet they stubbornly refuse to
1.) accept the idea of a global coordinate plane and that an application could place its windows wherever it wants on there, quoting weird "it could be used for future VR goggles" and "someone could do screen hijacking" reasons.
2.) don't allow the application to reshuffle windows.
I might go in depth with a future journal post to vent my anger, but suffice to say that this precludes the entire domain of "appliance frontends", where the application is supposed to deliver guaranteed behaviour (like car dashboards or medical devices), while still providing the ability to develop that in a desktop environment. I hear the car people have a workaround lined up.
It's either people with some mental disorder in the autism spectrum power-tripping, or actual malevolence from the larger RedHat direction. I'm not sure, but it appears very similar to what can be seen around Rust.