While you're here, please consider supporting GamingOnLinux on:
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Former Nouveau driver lead joins NVIDIA and sent a massive patch set
- SteamOS 3.5.18 Preview released for Steam Deck
- Ghost of Tsushima PC specs revealed - should work on Steam Deck
- Free Stars: Children of Infinity, sequel to The Ur-Quan Masters now on Kickstarter
- Team Fortress 2 64bit support released, plus Vulkan for Linux via DXVK
- > See more over 30 days here
-
Win a Steam Deck OLED or a golden egg game bundle in Fa…
- dpanter -
Fedora Linux 40 is officially out now
- Woodlandor -
Open source Minecraft mod platform Modrinth goes indie,…
- hell0 -
Fedora Linux 40 is officially out now
- Linux_Rocks -
Slimbook reveal the upgraded Slimbook Fedora 2 with 14"…
- elgatil - > See more comments
Latest Forum Posts
- Weekend Players' Club 4/19/2024
- StoneColdSpider - Logitech G29 steering wheel - Snowrunner support
- silmeth - anyone know if humble bundle games still provide different option…
- Mezron - The Evercade Outpost!
- damarrin - SomeOrdinaryGamers posted a good beginner Linux video
- Lib-Inst - See more posts
View PC info
I do not find any sense on the argument about the hypothetical kernel development who is just starting. There is an established hierarchy and there are only a few people that Linus does care about. The rest will have to go through that road and that means no contact with Linus at all anyway. So all this makes no sense.
Also there are many cases (maybe most of the time) that you just do not want to accept the code. You do not want the developer to spend any time in any kind of fix because you are not going to accept no matter what. The sooner to clearly stop him the better.
I fail to see how this has anything to do with the matter at hand.
Also, are only a select few allowed to submit code to the kernel?
View PC info
Actually there is only one guy who is "really" submitting code to the kernel and that is Linus. Now that he left for a while he said who is in charge (I think Greg, I am not checking if I am wrong). So at any moment one guy and only one is accountable. That makes a clear hierarchy. Of course the code is GPL so anyone can patch and distribute but then it would be a fork. (many distros actually do that to the kernel but so far there has been no real fork in the sense that they keep getting the realises from Linus and do their little modifications. only google with android was close to really be a fork but to maintain a real fork would be too expensive.)
But we are not in the 90s. You do not send a patch directly to Linus. You contact with the people that are more closely related with what the patch does and the code reach Linus through a network of trust. There are only very few people Linus trust and will get code (probably without even checking that code most of the times).
View PC info
Yeah, surely this is the beginning of the end for Linus the Gorilla.... It's only a matter of time now, that a younger male from the troop will step up to take his place. Such is the way of the jungle.
View PC info
View PC info
It's not just about mailing list. Wherever you might post anything irrelevant to the project but using your e-mail or any other account, you'll be called out for that. And it's not a rare thing to happen even for your past messages from years ago. You'll need to watch your mouth (or fingers) each second if you don't want to be kicked out of the project and use that "inclusive genderless language" everywhere. Good luck with that.
And yeah, "when an individual is representing the project or its community" is intentionally very vague, it can be used basically anywhere if needed. And it will be.
View PC info
And as mirv already pointed out, you added the bit about "genderless" - it only asks to be welcoming and inclusive, which frankly is subjective enough that I don't see it being enforced for anything short of telling newcomers to fuck off, unless the people in charge are trigger-happy SJWs themselves. In which case I'd say, write it off and fork it.
Thank you, exactly.
There is a huge difference between "your code is crap" and "you (as a person) are crap". Saying the latter is not OK, no matter the circumstances.
View PC info
View PC info
There's nothing in there YET. The Code of Conduct will be ignored by the people that wanted it until they get a chance to use it against someone that they want to get rid of, then it will be applied to that person with a vengeance. Just remember that when it happens, not IF, but when, the Code of Conduct is working as designed when it chases off the productive members of the project. As others have stated, it already happened to FreeBSD. We already know how this goes because we can chart it in real-time over there.
This is classic Linus, the horrors of an idiot being told off(again):
https://lkml.org/lkml/2012/12/23/75
This is my the most relative part:
And Linus is completely pissed off that he continually refers to everything that was working as broken, because his patch made working programs stop working. He swears at him, tells him to shut the f^&K up, calls him a idiot, and in general belittles the hell out of him. And he earned every bit of it. He didn't just own up, he blamed everybody else for why his patch broke everything. And then he agrees with Linus a lot in the resulting back and forth.
Oh, no. He had to READ harsh words. What a horror. How awful. Linus didn't even really yell at him.
I don't know, maybe it's my Marine Corps background, but this is pretty normal to me. You get it done, you might get yelled at a whole bunch with lots of bad words, and there's nobody on the other end shinning up a participation trophy for you, but you got the job done. Or you get out of the way so that someone else can.