Announcement

Collapse
No announcement yet.

Linux Code of Conduct Likely To See Changes Ahead Of 4.19 Kernel Release

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Originally posted by DanL View Post

    At least you'll never have to worry about reality. But hey, way to turn a thread about the Linux kernel CoC into an AMD vs. Intel flamewar through gibberish and smilies.
    Sorry about that, there is no harassment-free truth, as truth always hurts

    Comment


    • #32
      Originally posted by anarki2 View Post
      "socio-economic status"

      That doesn't even have any meaning lol.
      The entire effort to call out the "protected classes" under this CoC will very likely reveal some "corner case" class that was omitted. Then some public outcry will occur, possibly followed by one or more media events. In parallel a seemingly endless stream of emails on the subject will occur that will make the best "flame wars" fo 1990s USENET look like school spats.

      Comment


      • #33
        Originally posted by Brutalix View Post

        I am not quite sure if I understand you correctly, but it's a commonly used term within neuropsychology and we also use it in neuroradiological research as a covariate when doing statistical analysis.

        Wiki def:
        Socioeconomic status (SES) is an economic and sociological combined total measure of a person's work experience and of an individual's or family's economic and social position in relation to others, based on income, education, and occupation.

        Kind regards
        B.
        A Wikipedia definition is the best you can do?

        Comment


        • #34
          Originally posted by jacob View Post

          It's to protect SJWs from reality. Otherwise it may be blatantly obvious that their degrees in Critical Theory are of zero value, zero merit and that people get on just fine without ever needing the millenial snowflakes' "insight".
          ^^^ THIS ^^^

          With a CoC like this one I think we can expect no critical commentary on code without backlash attacks threating some aspect of CoC against the commenter.

          Comment


          • #35
            Originally posted by NotMine999 View Post
            A Wikipedia definition is the best you can do?
            And what part of that do you disagree with?

            Comment


            • #36
              Quick question, can I be a moron, submitting patches that are literal garbage, be called out on it, and then claim harassment? I am glad that they've moved in a better direction, but I still prefer the (good code) > (your feelings) approach.

              Comment


              • #37
                Originally posted by DanL View Post

                At least you'll never have to worry about reality. But hey, way to turn a thread about the Linux kernel CoC into an AMD vs. Intel flamewar through gibberish and smilies.
                Well IMHO it's at least better than turning a hypothetical Intel vs AMD flamewar into a CoC orgy of victimisation olympics, which the Linux community is at great danger of turning into

                Comment


                • #38
                  Originally posted by jacob View Post
                  Well IMHO it's at least better than turning a hypothetical Intel vs AMD flamewar into a CoC orgy of victimisation olympics, which the Linux community is at great danger of turning into
                  "The sky is falling! The sky is falling!" Seriously, statements like the one quoted make you look far worse than most people that you label SJW's. Linux will be okay. Take a deep breath.

                  Comment


                  • #39
                    There's a few people asking "why now". It was long overdue to add a proper code of conduct to Linux! I hope all changes that are accepted are in the spirit to setup the processes, boards, working groups that have so far been missing to make enforcement and ultimately broad acceptance of the code of conduct for all contributors.

                    There are way smaller and younger projects that are more mature and take better care of their contributors than Linux. The CoC isn't a barrier for good code, the lack of it and associated practices is what scared (scares?) good coders away.

                    Comment


                    • #40
                      Love the comments. Agree or not, there's a behavior problem. When you have people in leadership positions telling contributors to kill themselves to make the gene pool better, that's kind of a "code smell." Telling someone to commit a sex act on someone of the same sex in response to a perceived professional inadequecy in a code review (actual verbiage is banned by content policy, use your imagination) is sophomoric at best, and not something most people want to deal with on a routine basis.

                      There seems to be this tacit assumption that a "thick skin" makes for a strong engineer and helps "weed out" the weak. The reality is that talented engineers don't have to take abuse, we have options. Our contributions are welcome and taken elsewhere. This is the type of behavior has made countless open source projects, mailing lists etc a cesspool. I can only imagine how much better linux would be if the people in charge hadn't spent years running off countless contributors.

                      The policy itself isn't perfect, but it's needed. You're engineers, work on it until it works and stop whining about SJWs, libtards, socialists (irony much?) and how whatever Boogeyman you imagine is coming to steal whatever it is you imagine you have to lose.

                      Comment

                      Working...
                      X