• haverholm@kbin.earth
    link
    fedilink
    arrow-up
    88
    arrow-down
    20
    ·
    18 days ago

    My first impression was the lead developer calling a PR for gender neutral pronouns in the documentation “personal politics”. Pardon me if I’m still underwhelmed, no matter the state of the project.

    • TGhost [She/Her]@lemm.ee
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      3
      ·
      edit-2
      17 days ago

      Ohhh,
      The name of this browser, and this commit, that’s definitely a no go concerning me.

      There is enough as**oles like this,

      • N.E.P.T.R@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        27
        ·
        18 days ago

        Some made a pull request with all the changes made already. The issue that the PR addressed was the excessive use of he/him in the docs when referring to developers (aka the person reading the docs). Contributors expressed that they didnt think using male only pronouns in the docs made much sense when referring to any developer reading the docs. This wasn’t some entitled person trying to force the ladybird dev to rewrite the docs, all they needed to do was merge the changes.

        • agelord@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          17 days ago

          I think a bit more context could help here. What if those devs are male and prefer he/him? Should those pronouns be changed?

          • inspxtr@lemmy.world
            link
            fedilink
            English
            arrow-up
            12
            arrow-down
            1
            ·
            edit-2
            17 days ago

            In this scenario, I think the pronouns should be changed regardless of the gender of the devs. Here’s a screenshot of the suggested changes, which are quite minimal. The reason why I think this should be changed is because this is in the build instructions for a project that many devs are needed. Hence, they should at least be open to discussion rather than shutting it off completely. And honestly, this is a small change. Their reaction to this made it more political than the commit itself, and honestly the commit was not political in my mind. Their reaction also demonstrated how they respond to contributions, and an ambitious project like this will need a lot of contributors. If their leadership keeps this up, it is very off-putting for people to collaborate with them.

            • PlexSheep@infosec.pub
              link
              fedilink
              English
              arrow-up
              5
              arrow-down
              1
              ·
              17 days ago

              I’m usually in the camp that people should just speak as they like, but using they is just a really natural thing and non invasive in the English language. That’s a change that makes sense. They in this position might also refer to an organization, it Abstracts the entity using the thing away, which makes sense.