*Checks Linux kernel email folder I haven't checked in ages.*
*Most recent message CCed to me is a submission that includes significant chunks my own code verbatim, including even comments, "authored" by a FDo CoC team member, with zero credit (not Co-developed-by, nothing).*
I guess I wasted my time being careful about authorship back when I was involved with the kernel people...
Not going to bother replying, last time I tried to argue about authorship I just got hostility and troll news cycles. They can have my code and do whatever they want with it.
With drm/asahi mysteriously being completely absent [lore.kernel.org] when the people in that crowd talk about Rust GPU drivers, I'm pretty sure they're deliberately trying to erase my name and work from as many places as they can get away with...
I should've never gotten involved with the Linux kernel and FDo. They only care about you when you're useful to them, once you no longer are you might as well not exist.
I guess they want to pretend I don't exist, so I might as well pretend they don't exist.
@lina for what it’s worth, I remember your work (as a layperson that doesn’t know anything about GPU drivers). And I won’t forget
@lina this is awful. really, really awful
@lina yeah I have noticed the same conspicuous absence—I look for mention of Asahi anytime Rust DRM drivers in general come up, but at this point I know not to expect it :/
everyone keeping this charade of neutrality going is an embarrassment to the free software community. including the ones that enable it by standing by and letting it happen
@lina I thought you stopped maintaining/developing GPU drivers. If so and you are the driving force there, let me say: OSS people are highly sensitive to software being unmaintained nowadays
@ppxl I stopped. The driver still exists and is being upstreamed by the rest of the Asahi Linux team.
That driver is the reason all the other drivers exist in the first place. It was the first one. I wrote all the abstractions that make all the other drivers possible. It's the only complete, functional, production driver that is actually being used by thousands. Choosing not to mention it is a deliberate action.
@YvanDaSilva @ppxl @lina even then, screw copyright but we Give Credit for basic civilized dignity
@lina A more elegant solution is to file a lawsuit for copyright infringement.
Technically, anti-piracy laws also apply to free software; the difference is that the limits are determined by a license.
@maotongzhi I don't have anywhere near the time, money, and spoons for that, nor is it clear it would go anywhere because parts of my credit (in other commits) are still there and the license is compatible anyway.
I don't actually care that much, all this does is make it increasingly clear that this entire crowd is toxic and I want to have nothing to do with them.
@lina As someone who has been following the Asahi Linux project from the beginning without really understanding the technical side, it's both interesting and quite sad to see how things have unfolded. Watching the project grow, the team dynamics shift, and now seeing the side effects, like Hector Martin stepping down and seeming burned out, you, feels unsettling.
@lina I do not know what happened between the people involved, but from the outside we only see the consequences. It makes me wonder what went wrong within the team and whether there is something to learn from it. I feel like I should gather the pieces of the puzzle to understand the bigger picture. I hope I can do that over time.
Until then, I offer you my deepest sympathy.
@thekhanj I summed up what happened here:
https://www.reddit.com/r/AsahiLinux/s/yCNyxLpzV5
The short version is, I've been let down by and am extremely disappointed in the Linux GPU/Freedesktop community. Essentially, I was targeted by an abuser and only saw community members (and especially people on positions of power) defend/support the abuser or "choose no side".
@lina Thanks, I'll read it today:)
@lina what's the date on that message?
Because the latest lore.kernel.org messages (2nd December) where you are CC'd have a "signed-off-by" line against your name. And it looks like the content was originally written by you in October?
@dijumx Patches 6 and 8 of that series are based on my code and lack attribution (patch 8 being *the* last and most recent email I was referring to).
I originally wrote all this like, years ago by now. I'm sure the submitter refactored it quite a bit but there's still major chunks of the original code left, including verbatim comments I wrote.
I know some previous patches in the series keep my name (not crediting me at all even though I literally authored that source file in the first place would be preposterous and make them look really bad) but it sure is conveniently careless to split off bits into separate commits and slap someone else's name on them...
Back when I was reworking Git history to submit parts of the legacy R4L tree, I was extremely careful to make sure everyone who touched the code was credited and all sign-offs were collected and carried over. It's really depressing to see that an X.Org BoD and FDo CoC member, who really should know better, just doesn't give a damn.
But then again, she signed off on onboarding an abuser and stalker into FDo and sending me a gaslighting email about it, so I know she doesn't give a damn.