Apparently, it hasn’t happened. Because nobody else beside R4L is helping it along.
Sorry, but ya’ll just have more work to do, is all. Do it, or don’t, I don’t care. I honestly don’t care one iota if Rust ever gets in the kernel, or not. What I do care about is that the Linux kernel remains a stable project.
Ok, so then just toss in the towel, and make your own kernel, with hookers, blow, and Rust. Sorry.
Because the only “power” maintainers have is over the Linux kernel tree. They have no power over your own tree you maintain, with your Rust team. They have no power over the Rust kernel projects already working.
Hell, they don’t even have the power to keep you from taking their driver work, to build on! In fact, it’s encouraged!
This may come as a shock to you, and other proponents of the R4L team: The world does NOT revolve around you, and your preferred development language.
Or I can ask Linus to do his job properly and lead on this issue, whether it’s for or against R4L.
You seem to be under the impression that I’m somehow involved with R4L or Rust, or that I even use Rust. None of these are true. I’m just seeing an example of bad project management, and people like you that keep lying to justify the maintainers decision.
Or I can ask Linus to do his job properly and lead on this issue, whether it’s for or against R4L.
Linus owes you, nor anybody not signing his paycheck, a goddamed thing. Did you bother to read the article linked here?
You seem to be under the impression that I’m somehow involved with R4L or Rust, or that I even use Rust.
Ok then.
I’m just seeing an example of bad project management, and people like you that keep lying to justify the maintainers decision.
Nobody committing code to the Linux project, nor anybody doing the administrivia work owes anyone not involved in the project a goddamned thing. If you think you can manage it better, then fork, and do it.
Otherwise, you’re expecting other people to do free labor for you, and to do it to your specs. The world doesn’t work that way, and nobody owes you their labor.
Labor does. Laying out demands on labor does nothing, unless you’re the one meeting their material needs.
Linus owes you, nor anybody not signing his paycheck, a goddamed thing.
No, he owes the community to fulfill his role in this community project. He’s not a king or a monarch or whatever you think he is. If he’s not ready to fulfill this role, he should step down as project lead.
No, he owes the community to fulfill his role in this community project
Not really. He owes nobody his labor. If people don’t like how he runs it, they can fork, and run it as they please.
He’s not a king or a monarch or whatever you think he is.
Of course he’s not. And, neither are you. Neither of you can place demands on others to perform free labor.
If he’s not ready to fulfill this role, he should step down as project lead.
Well, he thinks he is fulfilling his role. You don’t. So, its up to you to show everyone how to do it right.
I’ve found most people who claim others “aren’t doing it right” actually mean that “they aren’t doing it how I want it to be done, and therefore I demand they do the work per my spec, even though I’m not meeting any of their material needs.”
Apparently, it hasn’t happened. Because nobody else beside R4L is helping it along.
Sorry, but ya’ll just have more work to do, is all. Do it, or don’t, I don’t care. I honestly don’t care one iota if Rust ever gets in the kernel, or not. What I do care about is that the Linux kernel remains a stable project.
Take the advice, or don’t. Its on you.
There’s no advice to take for working with maintainers who’ll abuse their power to stop a project they don’t like.
Ok, so then just toss in the towel, and make your own kernel, with hookers, blow, and Rust. Sorry.
Because the only “power” maintainers have is over the Linux kernel tree. They have no power over your own tree you maintain, with your Rust team. They have no power over the Rust kernel projects already working.
Hell, they don’t even have the power to keep you from taking their driver work, to build on! In fact, it’s encouraged!
This may come as a shock to you, and other proponents of the R4L team: The world does NOT revolve around you, and your preferred development language.
Or I can ask Linus to do his job properly and lead on this issue, whether it’s for or against R4L.
You seem to be under the impression that I’m somehow involved with R4L or Rust, or that I even use Rust. None of these are true. I’m just seeing an example of bad project management, and people like you that keep lying to justify the maintainers decision.
Linus owes you, nor anybody not signing his paycheck, a goddamed thing. Did you bother to read the article linked here?
Ok then.
Nobody committing code to the Linux project, nor anybody doing the administrivia work owes anyone not involved in the project a goddamned thing. If you think you can manage it better, then fork, and do it.
Otherwise, you’re expecting other people to do free labor for you, and to do it to your specs. The world doesn’t work that way, and nobody owes you their labor.
Labor does. Laying out demands on labor does nothing, unless you’re the one meeting their material needs.
No, he owes the community to fulfill his role in this community project. He’s not a king or a monarch or whatever you think he is. If he’s not ready to fulfill this role, he should step down as project lead.
Not really. He owes nobody his labor. If people don’t like how he runs it, they can fork, and run it as they please.
Of course he’s not. And, neither are you. Neither of you can place demands on others to perform free labor.
Well, he thinks he is fulfilling his role. You don’t. So, its up to you to show everyone how to do it right.
I’ve found most people who claim others “aren’t doing it right” actually mean that “they aren’t doing it how I want it to be done, and therefore I demand they do the work per my spec, even though I’m not meeting any of their material needs.”