• jet@hackertalks.com
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    1 year ago

    Tldr: someone is upset a maintainer wrote their own patch following style guidelines

    • Platypus@sh.itjust.works
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      1 year ago

      The maintainer also comes off as a colossal asshole about the whole thing who didn’t even deign to offer a scrap of credit to the programmer who found and fixed a six-year-old bug. If the article is truthful, the maintainer is the sort of toxic, power-tripping, self-obsessed repo czar that actively makes the open source community worse.

      • jet@hackertalks.com
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        1 year ago

        Being a maintainer is often a thankless, unpaid, never ending job. I will always give maintainers the benefit of the doubt, especially when they are being active, and not leaving gaps.

        Regardless of how this contributer wants to be acknowledged for a drive by contribution, Im sure they will keep developing and build a name for themselves so that a single patch isn’t a huge issue

      • czech@lemmy.world
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        1 year ago

        The quote in the article is not what the maintainer actually wrote. What they wrote was:

        Thanks for your patch, but I wanted to fix it differently. Can you try the patch below and make sure it fixes the bug for you?

        Seems they should have attributed correctly but they weren’t as dismissive as the blog makes it seem.