this post was submitted on 07 Dec 2023
1401 points (91.7% liked)

linuxmemes

21611 readers
1672 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 2 years ago
    MODERATORS
     

    An oldie, but a goodie

    (page 2) 50 comments
    sorted by: hot top controversial new old
    [–] [email protected] 37 points 1 year ago (1 children)

    As many seem to have overlooked itb this is from more than a decade ago.

    And to those setting "not being toxic" == "being vague":

    Suggestion if you're in a situation: separate the subject discussed from the person and, to the contrary to what is said in some other posts, be very specific!

    Improvised example:

    Hey all,

    patch xyzz and its aftermath communication is unacceptable.

    It's content is not to the standards we have set here (explain).

    Even worse, in the communication aftermath we blamed behavior of user space applications for bugs that are within our domain instead of owning up.

    The bugs within the kernel will be focused on with highest priority by a, b and myself.

    For the communication: (consequences). As explained the patterns shown here are unacceptable.

    I have decided to no longer have x as a kernel maintainer on our team/enforce pairing for all communication/set up stricter consequence catalogue. Any specific action,really...

    Not perfect as it's very early here, I haven't slept well and I'm not deep into the topic.

    Just remember to separate subject to be discussed from person(s) acting please.

    And always remember: bad communication is really easy and a lot of managers trained that their whole life! ♥

    [–] [email protected] 23 points 1 year ago (10 children)

    Reading this version I wouldn't know the writer is deeply disappointed, frustrated and angry. It's good you're trying to improve the letter but this is exactly what many people don't like about it: it changes the meaning. Perhaps you could include a paragraph which conveys this, such that the reader understands the gravity of the situation better.

    load more comments (10 replies)
    [–] [email protected] 37 points 1 year ago* (last edited 1 year ago) (24 children)

    I think whoever recieved this would be completely fine to report Linus to HR or something. The fact somebody thought to circulate it is suggestive that it crossed a line. I do appreciate he does seem to really care about the kernel. He could maybe tone down the hysterics a little.

    I think if there's a lesson here its "Never hit send while you're angry" always wait until your hormones to subside before sending an email because emails are records and people don't have good judgement while angry, so an email sent in anger is just a record of your poor judgement.

    [–] [email protected] 37 points 1 year ago

    This is far from the first (or last) time he wrote something like this. This was just a regular thing in the kernel world for a long time (until Linus matured a little).

    Whether or not it was a good thing is up for debate I think. Yeah, it's very rude and unprofessional (and discourages new contributors who don't want to risk getting chewed out), but considering the importance of the Linux kernel, it's good to know the lead maintainer is doing too much of the right thing than not enough (i.e. being lax with bad code in order to be respectful). I'm fine knowing that a few tech workers got their egos smashed if it gives me confidence that the code powering civilization is high quality.

    load more comments (23 replies)
    [–] [email protected] 35 points 1 year ago (2 children)

    To be read in the voice of J K Simmons

    load more comments (2 replies)
    [–] [email protected] 35 points 1 year ago

    Stuff like this is the reason Linus decided to take a sabbatical back in 2018 to work on controlling his temper.

    [–] [email protected] 32 points 1 year ago

    One does not simply break userspace. You'll receive more than just angry bug reports. There are restless maintainers who will not sleep. And the great corporations are ever watchful.

    [–] [email protected] 31 points 1 year ago (2 children)

    Yeah, but like...

    He's not wrong though.

    load more comments (2 replies)
    [–] [email protected] 31 points 1 year ago (1 children)
    [–] [email protected] 34 points 1 year ago* (last edited 1 year ago) (5 children)

    Randomly blaming pulseaudio and opensuse when talking about 100% CPU usage by KDE. It seems yes.

    load more comments (5 replies)
    [–] [email protected] 30 points 1 year ago (20 children)

    I'll be that guy: I miss the old Linus. If I fucked up that badly I'd want to know I had fucked up that badly.

    load more comments (20 replies)
    [–] [email protected] 29 points 1 year ago

    Poor Mauro: they weren't good at what they loved, they blamed others for their failings, and their community leader was nuts.

    Jokes aside, we've already got toxic right there. Linus isn't right, but someone like that would be fired with good cause. It's one thing to make a mistake, it's quite another to blame your co-workers for your own shoddy work.

    What's that Reddit phrase? ESH!

    [–] [email protected] 29 points 1 year ago (2 children)

    I miss when people had higher standards.

    load more comments (2 replies)
    [–] [email protected] 27 points 1 year ago (3 children)

    I would not work with or even for someone with such an attitude, not even for money. Ok, do it yourself, bye. Got better places to be.

    load more comments (3 replies)
    [–] [email protected] 24 points 1 year ago (6 children)

    How sad to be working on a Sunday and two days out before Christmas.

    Wouldn't lift a finger for less than triple time.

    load more comments (6 replies)
    [–] [email protected] 23 points 1 year ago

    In the following responses Mauro was very professional. l haven't heard much about recently but Linus had some high tier anger issues. Most of the cases I was following back then he was right, but desperately needed to cool off.

    load more comments
    view more: ‹ prev next ›