EDIT: I don’t like the term ‘soy boy’, just picked ‘soydev’ for a lack of a better word, intending to use it semi-ironically.

recently I saw a project move PR discussions to discord, like what’s the point of using a git forge at this point, you can as well just use git send-email

  • Saganaki@lemmy.one
    link
    fedilink
    arrow-up
    13
    ·
    11 months ago

    You are not alone in this.

    Prior to discord I’d get maybe a bug report/month. After, about 1/day.

    Simply put, the barrier to entry is huge.

    However, documentation on Discord (other than simple end-user instructions/links to git readmes) is sort of stupid.

    • Muehe@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      11 months ago

      Absolutely, what we have on the Discord in the way of documentation is a straight forward install guide with one screenshot and a download link (of the GitHub release) and a FAQ channel, which is basically just links to the GitHub for a good part of the answers. We also automatically mirror our changelog there. But that’s it, and it’s all on GitHub as well.

      What gets sadly lost on GitHub sometimes is “emerging events” like a new release of ours or the game we mod breaking something, where we will get yelled at on the Discord immediately and might have a hotfix release out before anybody even managed to create a proper GitHub issue.

      Edit: Oh and temporary workarounds. If we figured something out on the Discord it doesn’t get posted to Github necessarily even if there is already an issue. Hence why I’m looking into having a bot for that instead of literally having to copy and paste a message.