OSS projects suggesting newbies contribute docs and tests is common, usually only because the author doesn’t want to do it themselves Writing a good test suite or coherent docs is work that requires a huge amount of project context, often much harder than contributing features
-
In short, I think that documentation should evolve independently of code, because you learn so much more about code long after it's published. We should be detailing bugs and other learned details against the range of historical versions to which they apply.
-
-
i think so too! and i think that kind of tooling will make documentation writing into only the fun part (if it’s possible to automatically weave together a coherent narrative from a specified range of commits)
-
I think my original plan, if you remember it well enough, was a bit optimistic with what could be possible with tying docs to commit hashes. Commits get squashed and rebased too often, and I think it would be too easy to accidentally orphan docs...
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.