On Wednesday, 2 December 2015 at 16:22:32 UTC, bachmeier wrote:
Setup and maintenance is one thing.
Another is having to learn Git if you don't already know it.
Another is that there is no guide for contributing to the
documentation. I didn't know lines are supposed to be no more
than 80 columns. I didn't know you can't have whitespace at the
end of a line. I'm sure there are others that I'm not thinking
about right now.
Another is that you have no way to know what is an acceptable
change and what is not. Fixing a typo is no big deal. Anything
more than that, it is apparently up to the person that reviews
the PR. It's a big project to create a PR to suggest a change
that might or might not satisfy unstated criteria.
I'm not sure what the answer might be, but contributing to the
documentation is not at all the trivial process that is often
claimed.
Good that we're talking about this now. Maybe the D leadership is
not aware of this. Too many little annoyances that keep people
from contributing.
