You can easily edit any documents on GitHub itself; It’ll automatically create a pull request for you. Github also has good features for having multiple maintainers, handing off ownership, and even forking in the worst case. You can even find active forks of any repo. (I have an extension that displays this information on the main repo page, called Lovely Forks.)
Github allows better organizatio of the information (e.g., in the textbook example, we could have had a separate directory for each subject, and a separate file in those for each contributor’s opinions), as well.
Now, I have no doubt that starting any such community effort is hard, and maybe using Lesswrong has a lower barrier to entry, but in the long run, a Github repo is more viable. The best case scenario is for the author to collate the comments on Lesswrong into the git repo, and provide links to tutorials on using Github’s web interface for new contributors.
You can easily edit any documents on GitHub itself; It’ll automatically create a pull request for you. Github also has good features for having multiple maintainers, handing off ownership, and even forking in the worst case. You can even find active forks of any repo. (I have an extension that displays this information on the main repo page, called Lovely Forks.)
https://github.com/JanVanRyswyck/awesome-talks/commits/master , for an example of one such repo I use and is in active “development.”
Github allows better organizatio of the information (e.g., in the textbook example, we could have had a separate directory for each subject, and a separate file in those for each contributor’s opinions), as well.
Now, I have no doubt that starting any such community effort is hard, and maybe using Lesswrong has a lower barrier to entry, but in the long run, a Github repo is more viable. The best case scenario is for the author to collate the comments on Lesswrong into the git repo, and provide links to tutorials on using Github’s web interface for new contributors.