4 ms·

But many OS projects are desperate to get help from non-coders. For example: * documentation written by non-native speakers (and lazy/busy devs in general) ne

• dom0 10y ago
  > * documentation written by non-native speakers (and lazy/busy devs in general) needs a lot of editing and corrections. ftfy: > * documentation needs a lot of editing and corrections. Good docs can be as much work or more as the project itself.
  • nebabyte 10y ago
    Except that the former describes useful PRs that could be confidently contributed by someone who doesn't know the deep technicals of the item being documented, while the latter could just as easily need such knowledge. Bad docs can be just as much an impediment to useful work as bad PRs to the project itself. Someone not confident in submitting a code PR might similarly not wish to try and 'clarify' something they don't actually understand.
    • dom0 10y ago
      Can you elaborate? I only removed the qualifier ("written by non-native / lazy / busy devs"), since almost any text that has not been copy-edited can be improved by doing just that, which requires little or no domain knowledge. Also don't undervalue documentation feedback. Everyone makes first contact with a project only once, and the feedback of this "onboarding" can be invaluable and point to critical shortcomings of documentation.