• 3 Posts
  • 608 Comments
Joined 3 months ago
cake
Cake day: November 27th, 2024

help-circle

  • ubergeek@lemmy.todaytoLinux@lemmy.mlResigning as Asahi Linux project lead
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    3
    ·
    17 hours ago

    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.”


  • ubergeek@lemmy.todaytoLinux@lemmy.mlResigning as Asahi Linux project lead
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    edit-2
    18 hours ago

    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.


  • ubergeek@lemmy.todaytoLinux@lemmy.mlResigning as Asahi Linux project lead
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    3
    ·
    edit-2
    19 hours ago

    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.


  • ubergeek@lemmy.todaytoLinux@lemmy.mlResigning as Asahi Linux project lead
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    4
    ·
    19 hours ago

    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.



  • ubergeek@lemmy.todaytoLinux@lemmy.mlResigning as Asahi Linux project lead
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    7
    ·
    21 hours ago

    The maintainer literally says the issue is that there are two languages. There is no way to convince them, there’s nothing anyone can do.

    Sure there is! Maintain your own tree, like I said. Eventually, it’ll be proven to be workable. Or not.

    The maintainer didn’t say “I worry about the maintainability, please prove that it works outside the tree” (this concern was already discussed when the R4L experiment was officially OK’d). They are explicitly saying they’ll block Rust in the kernel, no matter what.

    No, they aren’t. They are blocking how it’s being done, with R4L folks wanting to toss the maintenance headaches over the wall, for someone else to deal with, because they don’t want to build their own C interfaces, that match the already existing ones.

    I don’t know how to better explain this to you.

    Try to understand the problem better, so maybe you’ll be able to understand why maintaining your own tree to prove the conceptual implementation works, and doesn’t hand maintenance overhead to another party.


  • ubergeek@lemmy.todaytoLinux@lemmy.mlResigning as Asahi Linux project lead
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    8
    ·
    22 hours ago

    I already did: maintain your own tree, and prove it out, that it’s better.

    If the maintenance load is so light, it’ll be easy work to do, to keep the tree in line with upstream.

    If it’s so obviously technically better, people will see it, and more people will push to mainline your tree.

    It’s work. And you need to convince others on technical merit. So, do the work.

    Just like what folks did with OpenBSD, the grsecurity tree.









  • The Air Force isn’t enforcing domestic policy.

    Yes, it is.

    Its the exact same reason we had a 2 day training on the Posse Comitatus Act, before engaging in JTF-6 border interdiction missions.

    We specifically were told we had to have names and unit insignia, because we were operating on US soil. And we were not allowed to touch anyone inside of the US border. We couldn’t even use mast mounted sights to locate people inside of US soil.

    Because it’s outright illegal to do so. Because the military are not law enforcement, and we only know how to handle EPWs, and not civilian prisoners outside of a war zone.




  • ubergeek@lemmy.todaytomemes@lemmy.worldForced to have "Gulf of America"
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    3 days ago

    Ok…

    So the main difference here is Denali is fully contained within the borders of the country choosing to name it.

    The Gulf of Mexico is International Waters, and the US doesn’t even have the majority of shoreline… Which is why we have an international standards body to name international waters, so people don’t get confused.

    For example, an airline flight from Tampa to Cancun reports its flying over the Gulf of America to a Mexican air traffic controller… The controller has no idea what the hell he is talking about, because THE ENTIRE GLOBE calls it “Gulf of Mexico”.