• IdiosyncraticIdiot@sh.itjust.works
    link
    fedilink
    arrow-up
    112
    arrow-down
    1
    ·
    11 months ago

    Imagine being in a corporate environment trying to implement an OSS into your platform and having to tell your 50 yo teammate: “Oh yeah, just pop in this Discord server real quick to see any relevant info”. Instant credibility loss

    • evatronic@lemm.ee
      link
      fedilink
      English
      arrow-up
      126
      ·
      11 months ago

      The loss of credibility is not because it’s discord,. specifically.

      It’s because the project thinks a chat platform is an appropriate way to document a project. I would feel the same way if someone told me to get on IRC for docs, or Slack.

          • wewbull@feddit.uk
            link
            fedilink
            English
            arrow-up
            21
            ·
            11 months ago

            Not even a forum.

            Documentation is not a snapshot of a discussion. It largely falls into two categories

            • collections of facts e.g. what command line switches there are, or all the options in the config files.
            • Guides on how to use the software.

            The first is vital. The second is really really useful.

          • pingveno@lemmy.ml
            link
            fedilink
            English
            arrow-up
            4
            arrow-down
            15
            ·
            11 months ago

            Wikis always seem to produce second rate documentation, except maybe the ones that are designed specifically around software projects. There are any number of tools out there that produce better documentation and it can be stored alongside the source code in a git repository to avoid drift between the code and the associated documentation.