anthonydpaul (@anthonydpaul) wrote at 8/20/2014 9:29 pm:We use GitHub for everything around a code project, including design critiques, tasking for requirements documentation, outstanding decisions, and more. It just makes sense.
| « PHP 5.6 is coming next week | Back On The Market! » |
At SunshinePHP in January, Elizabeth Naramore gave a talk on how GitHub uses GitHub internally for projects that may or may not involve code. For example, all requests for sponsorship are turned into issues, which are tracked, tagged and labeled.
After this talk, I decided to create repositories for the purpose of tracking bugs in my books. The idea was that I would have a place to track the issues, and that readers would be able to file their issues with the books in a place that most of us are familiar with using and interacting already. No writer is perfect, and no book is published without bugs, so it seemed like a win for everybody.
I created a repository for Mastering Object Oriented PHP and Practical Design Patterns in PHP. The latter has been updated to include the repo in the opening pages for people to file their issues. So far, it’s been really successful.
GitHub can also be really useful for storing documentation (it interprets Markdown files very well) and other items. Many people, including authors and non-technical individuals, use GitHub for a variety of purposes. Elizabeth’s talk was very enlightening, and opened my eyes to a bunch of ways we can use GitHub even when there’s no code involved!
Brandon Savage is the author of Mastering Object Oriented PHP and Practical Design Patterns in PHP
Posted on 8/20/2014 at 12:44 pm
We use GitHub for everything around a code project, including design critiques, tasking for requirements documentation, outstanding decisions, and more. It just makes sense.
| « PHP 5.6 is coming next week | Back On The Market! » |