I think we don't give people enough direct credit for their work on RailsBridge, and one easy place to rectify that is in the docs! So I've added credits where I could tell (or know) who to give credit to.
This commit adds a note to the last page of a few curriculums with the name(s) of the original author(s) and a link to the history of the curriculum on GitHub so that curious people can see who has contributed specifically to this curriculum.
(I'm using the directory history instead of the contribution graph because the contribution graph can't be
broken down by what part of the codebase the contribution was made to, as far as I can tell.)
The history of the Suggestotron curriculum happened enough outside of git histories that I think it makes sense to leave it with the generic link to the contributor graph. The Ruby curriculum could probably use credit, but I'm not totally sure who it goes to, Travis maybe?
tjgrathwell
commented
7 years ago
I think we don't give people enough direct credit for their work on RailsBridge, and one easy place to rectify that is in the docs! So I've added credits where I could tell (or know) who to give credit to.
This commit adds a note to the last page of a few curriculums with the name(s) of the original author(s) and a link to the history of the curriculum on GitHub so that curious people can see who has contributed specifically to this curriculum.
(I'm using the directory history instead of the contribution graph because the contribution graph can't be broken down by what part of the codebase the contribution was made to, as far as I can tell.)
The history of the Suggestotron curriculum happened enough outside of git histories that I think it makes sense to leave it with the generic link to the contributor graph. The Ruby curriculum could probably use credit, but I'm not totally sure who it goes to, Travis maybe?