News for hackers. Stuff that matters.
Re:Resigning as Asahi Linux project lead by bigstrat2003 on Thursday February 13, 2025 @10:50AM (#43037113)
"spreading awareness about a position" isn't a very accurate way to describe what happened. This is the guy who said he wanted to use social media to create a "hall of shame" for kernel developers. Of course Linus told him to knock it off, that's ridiculously unprofessional behavior.
Re:Resigning as Asahi Linux project lead by ho_schi on Thursday February 13, 2025 @11:37AM (#43037827)
Background Story

https://lore.kernel.org/lkml/a869236a-1d59-4524-a86b-be08a15...

https://lore.kernel.org/lkml/a869236a-1d59-4524-a86b-be08a15...

https://lore.kernel.org/lkml/a869236a-1d59-4524-a86b-be08a15...

https://lore.kernel.org/lkml/a869236a-1d59-4524-a86b-be08a15...

    1. I think the the DMA maintainer is correct. Don't intertwine implementation languages, that is bad idea and a maintenance hell.  
    2. Social media "hall of shame" 
    3. Torvalds is forced to make a statement because of 2. Not 1.
Re:Resigning as Asahi Linux project lead by oskarkk on Thursday February 13, 2025 @05:12PM (#43042091)
And here are the Hector's posts on Mastodon, now deleted:

https://archive.is/uLiWX https://archive.is/rESxe

"Behold, a Linux maintainer openly admitting to attempting to sabotage the entire Rust for Linux project (...) Personally, I would consider this grounds for removal of Christoph from the Linux project on Code of Conduct violation grounds, but sadly I doubt much will happen other than draining a lot of people's energy and will to continue the project until Linus says "fuck you" or something. (...)"

"Thinking of literally starting a Linux maintainer hall of shame. Not for public consumption, but to help new kernel contributors know what to expect. Every experienced kernel submitter has this in their head, maybe it should be finally written down."

"Okay I literally just started this privately and the first 3 names involved are all people named variants on "Christ". Maybe there's a pattern here... religion secretly trying to sabotage the Linux kernel behind the scenes??? Edit: /s because apparently some people need it."

Re:Resigning as Asahi Linux project lead by LinXitoW on Thursday February 13, 2025 @11:57AM (#43038161)
The issue is that Linus put the Rust developers in an impossible position: On the one hand he approved Rust in the kernel, but then never ever ever has the balls to enforce that decision.

Then, the fanatical C developers openly sabotage and work against all the Rust developers efforts. So, the last option for the Rust developers is to take it to social media. Otherwise, the C developers get away with creating a self fulfilling prophecy: Sabotage all Rust efforts, then claim the Rust experiment failed.

Linus didn't seem to ever have the time to actually take a stance, except of course on the social media issue. Fully ignoring all context. It's the equivalent of a school principal suspending the bullied victim for finally snapping and punching their bully.

Re:Resigning as Asahi Linux project lead by surajrmal on Thursday February 13, 2025 @12:28PM (#43038610)
The thread didn't really have drama before marcan stirred the pot. There was a disagreement, but the individuals pushing for the merge were not attempting to escalate, only try to find a path forward in a way that might make both parties happy with the compromise. The drama and social media outrage arguably did nothing to help, and as far as I can tell, simply makes for good entertainment for onlookers who like to gossip. While it would be nice to have Linus help out here with a clear resolution after escalation, it's clear to me that the behavior marcan displayed is the higher priority problem to address.
Re:Resigning as Asahi Linux project lead by adgjlsfhk1 on Thursday February 13, 2025 @12:55PM (#43038996)
I think this isn't the right take. the "disagreement" was a kernel maintainer saying "Rust in the Linux kernel is a mistake and I will do everything in my power to sabotage Rust adoption" (as feedback on version 8 of a patch). The fact that open undermining of Rust for Linux receives no pushback from Linus or anyone else with power in the Kernel is shocking.
Re:Resigning as Asahi Linux project lead by stirlo on Thursday February 13, 2025 @01:59PM (#43039784)
100% this. Yes, Hector went nuclear, but he begged Linus to step in and provide leadership (either merge or reject) and instead Linus ignored the whole technical issue with regards to rust being totally blocked.

Even now with Hector out of the picture, there’s still no suitable path forward for rust in Linux. No wonder why people are giving up (exactly what the blockers want).

Re:Resigning as Asahi Linux project lead by dralley on Thursday February 13, 2025 @04:01PM (#43041295)
>Even now with Hector out of the picture, there’s still no suitable path forward for rust in Linux

The suitable path forward is to submit the patch series like normal to Linus, where it will be merged regardless of CH's NACK. CH isn't able to actually stop this process, he's just being a jerk.

However, I agree with you that it would have been nice to actually publicly clarify the situation rather than ignore it and deal with the whole thing behind closed doors. It shouldn't need to be explained that letting this sort of thing fester is a great way to kill motivation in a project and ensure it's less likely that new people will get involved.

Re:Resigning as Asahi Linux project lead by Den_VR on Friday February 14, 2025 @04:10PM (#43053100)
The reasoning Linus himself gives for greenlighting Rust is, among other things, to avoid stagnation. In practice, CH is doing everything he can to stonewall and sabotage efforts to subsequently bring Rust to solve problems. This explosion, now, was plainly a consequence of months and months of failure. And that anyone name-calls to blame that failure on “a drama-seeker” leaves me to wonder about the future of Linux 20 years from now.
Re:Resigning as Asahi Linux project lead by o11c on Thursday February 13, 2025 @03:34PM (#43040968)
Counterpoint: prior to going nuclear, is there any evidence that Marcan directly tried to get Linus's attention, given the huge quanity of mailing-list mail Linus is sure to get every day?

I only see Danilo doing that in that thread. And admittedly Linus didn't respond (and Greg KH only minimally responded). But even CC probably means a lot of mail for top maintainers, and at that point I don't see anything that would've gotten in the way of "send a PR despite the Nacked-by", which has been done in the past.

Re:Resigning as Asahi Linux project lead by nrabulinski on Friday February 14, 2025 @02:55AM (#43045974)
He literally says in the post he reached out to Linus directly and to this day haven’t gotten a response. He also himself was (trying to) upstream patches for years, usually ending up similarly getting stonewalled
Re:Resigning as Asahi Linux project lead by o11c on Friday February 14, 2025 @12:39PM (#43050844)
I don't see the word "reach" or any relevant mention of "Linus" in either the "shaming" post or in the resignation post.

Even if there was, I'm not sure I trust the word of such a drama-seeker directly, so it's reasonable to a evidence of on-mailing-list appeals adding CC (as Danilo did), and if that fails mention of contacting Linus off-list in that specific subthread.

Re:Resigning as Asahi Linux project lead by surajrmal on Thursday February 13, 2025 @10:25PM (#43044475)
The rust project is not stalled. There is pushback from maintainers, but as trust is established, things will hopefully change and it'll get easier. Escalating erodes trust and simply will make the process take longer. Anything that fuels us vs them narratives are simply damaging. Everyone needs to focus on the shared objectives of the overall Linux project. Ignoring the maintainers and pretending their opinions are wrong or don't matter won't help. I'm not sure a top down directive is necessarily the right way to establish a healthy space for rust in linux.
Re:Resigning as Asahi Linux project lead by reshlo on Thursday February 13, 2025 @12:28PM (#43038612)
I agree. Everyone here seems to be criticising Marcan for not being professional, but it’s very difficult to remain professional when the people you’re working with gloat in public that they intend to completely sabotage your work product despite it being given explicit support by the CEO. Why are you the only one criticising the coworkers? I feel like I’m taking crazy pills reading this thread.
Re:Resigning as Asahi Linux project lead by hitekker on Thursday February 13, 2025 @12:36PM (#43038752)
Difficulties notwithstanding, Marcan’s drama is excessive. He has a history of it.

His fellow R4L partners chewed him out for jumping in and spoiling their work. They even quietly but publicly disaffiliated R4L from him.

Re:Resigning as Asahi Linux project lead by bigstrat2003 on Thursday February 13, 2025 @08:39PM (#43043713)
Because this thread is about Marcan's behavior, not others'. I think it's perfectly fair to claim that everyone behaved badly in this situation, but the person I replied to was insinuating that Marcan didn't do anything wrong. That is not true, and why I highlighted his behavior.
Re:Resigning as Asahi Linux project lead by sundarurfriend on Thursday February 13, 2025 @01:06PM (#43039151)
> So, the last option for the Rust developers is to take it to social media.

Social media is an amplifier of interpersonal problems, not a place to seek for a resolution for them - unless your intended "resolution" is to beat down the other side, the people you have to work alongside by necessity, via potshots from random strangers who hardly ever bother to inform themselves fully of the situation. That is never going to be a true resolution, and I think Linus, for all his faults, recognizes that and that's why he draws the line there.

Re:Resigning as Asahi Linux project lead by ndiddy on Thursday February 13, 2025 @02:50PM (#43040445)
The C maintainer in question had no power to stop the code from being merged, it wasn't in his directory. He was tagged as a courtesy in case he wanted to do a drive-by review since the code was wrapping his subsystem. The Rust code being reviewed wasn't written by marcan, and the other Rust developers called him out for taking the argument to social media when the code was likely going to be merged anyway (see https://lore.kernel.org/rust-for-linux/Z6OzgBYZNJPr_ZD1@phen... and https://lore.kernel.org/rust-for-linux/CAPM=9tzPR9wd=3Wbjnp-... ).
Re:Resigning as Asahi Linux project lead by cogman10 on Thursday February 13, 2025 @11:00AM (#43037242)
Yup, I think it went too far.

The fact is, you need buy in from other devs and if a dev won't buy in you need to work out a way to avoid them or avoid conflict. It sucks, it slows things down, but frankly making it a "them vs us" is a sure fire way to make them oppose any change you want to make.

Public shaming even more disastrous as there's no better way to entrench someone in a position.

Re:Resigning as Asahi Linux project lead by __float on Thursday February 13, 2025 @11:02AM (#43037280)
I'm not entirely convinced they meant to truly make a public hall of shame.

It sounded to me like a list of "friends who want to get more involved, I'll let you know who to avoid". Then, I read the interactions that sparked that post, and I could totally understand the frustration from OP's part.

Linus being unwilling to take a real stand on maintainers blocking Rust just because doesn't really help.

Re:Resigning as Asahi Linux project lead by diggan on Thursday February 13, 2025 @11:12AM (#43037431)
Someone wrote (https://lore.kernel.org/rust-for-linux/208e1fc3-cfc3-4a26-98...):

> To back up Sima here, we don't need grandstanding, brigading, playing

> to the crowd, streamer drama creation or any of that in discussions

> around this.

Marcan replied (https://lore.kernel.org/rust-for-linux/208e1fc3-cfc3-4a26-98...):

> If shaming on social media does not work, then tell me what does, because I'm out of ideas.

Then Linus replied (https://lore.kernel.org/rust-for-linux/CAHk-=wi=ZmP2=TmHsFSU...):

> However, I will say that the social media brigading just makes me not want to have anything at all to do with your approach.

> Because if we have issues in the kernel development model, then social media sure as hell isn't the solution. The same way it sure as hell wasn't the solution to politics.

To me, it sure sounds like Marcan is making the case that they tried other venues, didn't feel like it worked, so they resolved to using their social media following to shame kernel developers if they didn't stop.

Re:Resigning as Asahi Linux project lead by LinXitoW on Thursday February 13, 2025 @12:01PM (#43038220)
But the point is that the Rust developers have tried literally everything else.

If the C developers make it a "Them vs Us" thing, there IS NO ALTERNATIVE for the Rust developers.

Linus' reaction is quite literally the equivalent of a parent only punishing the loudest child, not the child that's been silently bullying that kid for months.

Re:Resigning as Asahi Linux project lead by cogman10 on Thursday February 13, 2025 @12:28PM (#43038608)
Don't know what to tell you. The C developers have the keys of the kingdom. It's up to the rust devs to appease them. When you are a new-comer to an old project a big part of that is working with the current gatekeepers to get your changes through in a way they'll accept. That can sometimes mean doing things sub optimally in your view.

In particular, the DMA maintainer didn't want rust code in their DMA subsystem. That sucks, but it means you need to relocate your dma bridge code out of their subsystem. It does mean your driver will be a second-class citizen in the kernel tree (which was always going to be the case for rust).

Linus' reaction was to someone who started a public campaign against another kernel developer and tried to use that following to pressure the maintainers of the kernel to bend to the will of the newcommer. I'm sorry, but I'd also have a pretty negative reaction to that.

The workplace equivalent is you publishing a whistle blowing article against a team in your company because they'd not accept a pull request you worked very hard on. You don't do that. You handle things internally and privately and sometimes you tell the boss "sorry, I can't get this done because another team is blocking the change and they are unwilling to work with me".

And do not mistake my post. I'm not siding with the C dev just because I'm critiquing the rust dev. Guy sounds like he's too stuck in his way. The problem is you don't get a big well working and long running project like the kernel without having these sorts of long-term maintainers that make the calls and shots on what to reject.

Re:Resigning as Asahi Linux project lead by dralley on Thursday February 13, 2025 @04:11PM (#43041410)
>In particular, the DMA maintainer didn't want rust code in their DMA subsystem. That sucks, but it means you need to relocate your dma bridge code out of their subsystem

The code was never in the DMA subsystem. At no point was there ever any Rust code in the DMA subsystem.

CH didn't even look at the patch before throwing the wall up. When it was pointed out that the patch already was the way he claimed he wanted it, he came up with a 2nd excuse, and then when that avenue was shut down he said he would do anything to stop Rust being put in the kernel, period, he wouldn't work with any Rust developers and he wouldn't accept adding a second maintainer for his subsystem that would do that engagement either.

From that point it's pretty clear that all previous engagement was just in bad faith.

Re:Resigning as Asahi Linux project lead by reshlo on Thursday February 13, 2025 @12:31PM (#43038672)
> The workplace equivalent is you publishing a whistle blowing article against a team in your company because they'd not accept a pull request you worked very hard on.

The workplace equivalent is your CEO making a public statement that your work is to be supported, then not firing people who openly gloat about their intent to sabotage your work.

Re:Resigning as Asahi Linux project lead by mardifoufs on Thursday February 13, 2025 @12:43PM (#43038839)
I mean, I hope that you'd get fired for trying to publicly shame people who you see as trying to "sabotage" you in any normal corporation, regardless of how much your vision aligns with the CEO's lol.

Not that it even makes sense to call it sabotage considering that most people that were involved in the original debate (in the rust for Linux side) didn't see it like that, that the normal kernel development processes were on their way to actually make the change happen anyways, and that Marcan's actions probably did more to sabotage actual support from other maintainers and Linus himself than the original NACK that started all of this ever did.

(Not that Linus ever even gave a blank check for rust on Linux, so I don't think that disagreements and even NACKs are somehow going against what Linus decided)

Re:Resigning as Asahi Linux project lead by reshlo on Friday February 21, 2025 @06:32PM (#43134424)
NACKs of bad Rust code, or Rust code that you don’t want in the system that you maintain, would be fine. The specific NACK at issue here was a NACK of code that used a maintainer’s API from a language that he didn’t like, which Linus has confirmed is not allowed.

> Maintainers like Hellwig who do not want to integrate Rust do not have to. But they also cannot dictate the language or manner of code that touches their area of control but does not alter it. The pull request Hellwig objected to "DID NOT TOUCH THE DMA LAYER AT ALL," Torvalds writes (all-caps emphasis his), and was "literally just another user of it, in a completely separate subdirectory."

> "Honestly, what you have been doing is basically saying 'as a DMA maintainer I control what the DMA code is used for.' And that is not how any of this works," Torvalds writes.

> Torvalds writes Hellwig that "I respect you technically, and I like working with you," and that he likes when Hellwig "call[s] me out on my bullshit," as there "needs to be people who just stand up to me and tell me I'm full of shit." But, Torvalds writes, "Now I'm calling you out on YOURS."

> The leader goes on to state that maintainers who want to be involved in Rust can be, and can influence what Rust bindings look like. Those who "are taking the 'I don't want to deal with Rust' option," Torvalds writes, can do so—later describing it as a "wall of protection"—but also have no say on Rust code that builds on their C interfaces.

> "Put another way: the 'nobody is forced to deal with Rust' does not imply 'everybody is allowed to veto any Rust code.'" Maintainers might also find space in the middle, being aware of Rust bindings and working with Rust developers, but not actively involved, Torvalds writes.

https://arstechnica.com/gadgets/2025/02/linux-leaders-pave-a...

Re:Resigning as Asahi Linux project lead by busterarm on Thursday February 13, 2025 @02:16PM (#43040020)
Why should there be an alternative for Rust developers? Are they entitled to having their code merged?
Re:Resigning as Asahi Linux project lead by bigstrat2003 on Thursday February 13, 2025 @08:41PM (#43043731)
> If the C developers make it a "Them vs Us" thing, there IS NO ALTERNATIVE for the Rust developers.

There is always an alternative. Exit the project quietly and gracefully if Linus won't show proper leadership. Don't engage in poor behavior back at the C developers, that is just as wrong.

Re:Resigning as Asahi Linux project lead by gjsman-1000 on Thursday February 13, 2025 @11:04AM (#43037310)
It's deeply ironic that he's complaining about kernel maintainers supposedly forming secret cliques.

However... this is the same man who made a sock puppet V-Tuber account, and acts in every way like they are two people; even though they've accidentally on-stream shared the system username, shared they have exactly the same kernel version, same KDE configuration, same login, same time zone, even (if I recall correctly) accidentally making GitHub commits as the other person once in a while. He also did this on the Linux kernel mailing lists, where he still maintains the charade.

Point out that's weird, or that it's weird for a maintainer to have a fake persona as a walking female stereotype; and you're the one he shreds and mocks - while simultaneously not denying it. For me, I caught on immediately when I saw the supposed "hijacking" of his stream on April Fool's day, which was her first appearance; and stopped donating. I don't pay people to support stereotypes about women in STEM.

Re:Resigning as Asahi Linux project lead by danw1979 on Thursday February 13, 2025 @11:20AM (#43037563)
How does having an alter-ego make it deeply ironic that he complains about secret cliques? I don’t get it.

I’ve been supporting Hector since week 1 of the Asahi project and I think it’s a shame he’s thrown in the towel but I can understand why.

I don’t know enough about kernel development to have an opinion about about the Kernel policy of “no aliases” for contributions.

I certainly don’t care that some people think it’s weird for a man to have a female alter ego.

Maybe those things matter to you.

Re:Resigning as Asahi Linux project lead by asksomeoneelse on Thursday February 13, 2025 @12:17PM (#43038451)
Having an alter-ego is one thing, but I strongly suspect that he had at least one sock puppet here during the drama with HN [0]

* a brand new account suddenly appears, defending Marcan's behavior (the only comment/post ever of this account) with a very similar writing style

* Marcan immediately "notices" the new comment while doing "random search" (how ? he claims he doesn't browse HN, and even posted a screenshot of news.ycombinator.com being routed to 0.0.0.0 to block his own access to it the day before)

* Marcan highlights the comment in question on his media account [1], praising them "at least [this commenter] gets it"

Only circumstantial stuff, but sure smells very fishy to me.

[0] https://news.ycombinator.com/item?id=35400352

[1] https://archive.ph/zdVbA

Re:Resigning as Asahi Linux project lead by gjsman-1000 on Thursday February 13, 2025 @11:22AM (#43037598)
Ah, yes, the classic Smugjak "How does this affect you personally?" retort.

> I certainly don’t care that some people think it’s weird for a man to have a female alter ego.

You're assuming that this does not affect women in STEM. For me, if I wanted to join something technical, and the first thing you see is a man talking as a woman in a comically high-pitched voice and feminine attributes turned to 11, how is that not off putting for women? In some ways, it's worse than a boy's club activity, as it directly parodies feminine attributes and stereotypes.

It's like me complaining about racism as a white man; and being told by a racist why should it matter, it doesn't personally affect me.

Re:Resigning as Asahi Linux project lead by saagarjha on Thursday February 13, 2025 @11:53AM (#43038100)
Are you a woman? Have you asked women how they feel about this?
Re:Resigning as Asahi Linux project lead by popcalc on Thursday February 13, 2025 @03:12PM (#43040697)
Are you insinuating that the parent is not a woman?
Re:Resigning as Asahi Linux project lead by saagarjha on Saturday February 15, 2025 @02:58AM (#43056748)
> as a white man

I mean, they are welcome to clarify if they want

Re:Resigning as Asahi Linux project lead by thw8419 on Thursday February 13, 2025 @11:12AM (#43037429)
Even if he did that, which I'm not in a position to judge:

That is an entirely different situation from facing inner circles in an open source project while contributing to a major port.

Sock puppets aren't taken seriously while the word of the inner circle is taken as gospel.

Re:Resigning as Asahi Linux project lead by gjsman-1000 on Thursday February 13, 2025 @11:13AM (#43037446)
Reminder that he did this on the Linux kernel mailing lists. If I was a Linux maintainer who found out that two of the people I'm talking to, are actually with high likelihood the same person secretly maintaining a charade, I wouldn't be far from banning both.

I also certainly wouldn't take any of his complaints about cliques or brigading with any seriousness or self-reflection afterwards.

Re:Resigning as Asahi Linux project lead by strunz on Thursday February 13, 2025 @11:36AM (#43037813)
Wait, what? I haven't heard about any of this in all the articles I've read over this drama.
Re:Resigning as Asahi Linux project lead by gjsman-1000 on Thursday February 13, 2025 @11:37AM (#43037828)
Re:Resigning as Asahi Linux project lead by epcoa on Thursday February 13, 2025 @12:24PM (#43038546)
There's nothing really to prove. They effectively confirmed it themselves:

https://vt.social/@lina/112887550181123672

https://docs.google.com/document/d/1W2Vvwg0rwSVb5r4TQ_NmAF8S...

Re:Resigning as Asahi Linux project lead by Capricorn2481 on Thursday February 13, 2025 @11:08AM (#43037362)
Wow, what an uncharitable read. Are you aware of what that term means? He said it was not about literally shaming people, but showing what contributing to the kernel is like, and even clarified it wouldn't be for public consumption. It's a colloquialism for a resource where peers can learn from each other's mistakes. My high school Spanish class had a hall of shame.

It's a magnitude more professional than the extremely over the top and public emails that Linus shares, which HN jerks off over. I too would be burnt out if people were picking apart what I said so closely but clapping when Linus says "this code is retarded"

Re:Resigning as Asahi Linux project lead by diggan on Thursday February 13, 2025 @11:14AM (#43037450)
> He said it was not about literally shaming people

The original message I read (https://lore.kernel.org/rust-for-linux/208e1fc3-cfc3-4a26-98...) they quite explicitly said (verbatim): "If shaming on social media does not work, then tell me what does, because I'm out of ideas."

Re:Resigning as Asahi Linux project lead by Capricorn2481 on Thursday February 13, 2025 @11:22AM (#43037596)
Yes I'm aware of that quote, which doesn't make sense to link with the original quote because his intentions with the "Hall of shame" are different from this quote.

This message brings up a lot of valid complaints about talented developers being stonewalled and you're honing in on one word that is not being used the way you think. Again, there are dozens of emails from Linus that are vastly more unprofessional than this.

Re:Resigning as Asahi Linux project lead by diggan on Thursday February 13, 2025 @11:32AM (#43037752)
> because his intentions with the "Hall of shame" are different from this quote.

Aha, I thought it was referring to the same "event"/context but it clearly didn't. Thank you for the correction.

Re:Resigning as Asahi Linux project lead by felipec on Thursday February 13, 2025 @11:21AM (#43037570)
As if he didn't read the comment about not wanting the cross-language code to spread like cancer in the most uncharitable way possible.
Re:Resigning as Asahi Linux project lead by Capricorn2481 on Thursday February 13, 2025 @11:27AM (#43037675)
My complaint is not that this maintainer would be charitable in their reads or should stay on the project, but that they are unevenly being examined because they are not one of the greybeards.

If you don't want a maintainer, that's fine, but to claim it has anything to do with professionalism is dumb when this is seen as communication to admire.

https://www.reddit.com/r/linusrants/

Re:Resigning as Asahi Linux project lead by finnthehuman on Thursday February 13, 2025 @11:55AM (#43038136)
> He said it was not about literally shaming people, but showing what contributing to the kernel is like

Oh. Nevermind then. If he says so then it must be fine. It has zero ulterior motives, will cause no unintended effects and is no longer dripping in passive aggressive hostility. Nice of him to clear that up.

Re:Resigning as Asahi Linux project lead by bigstrat2003 on Thursday February 13, 2025 @08:45PM (#43043760)
"hall of shame" inherently means it's about literally shaming people. If that isn't what he meant, then he shouldn't have used those words.

> It's a magnitude more professional than the extremely over the top and public emails that Linus shares

Since when do two wrongs make a right? I think it's perfectly fair to say Linus hasn't shown the best leadership here. But that doesn't excuse Marcan's behavior.