Most days are pretty easy. Being that I maintain a large project (Open Dylan), there is almost always a simple bug to fix, documentation to improve, typos to correct, bugs to file, pull requests to merge from others.
It has been great for keeping things moving and making sure that every day, I make at least a little bit of progress. Every day, at least a tiny step forward.
I appreciate your contributions much more!
The contribution graph is in my opinion really a great motivational tool. Seems to work better for me than projects like Julython, however I'm guilty of a few single-commit days fixing a typo or updating some dependency packages. Looking forward to 365!
A few notes:
- it’s the time of the commit which is important, not the push. So you can contribute on your projects locally if you don’t have Internet access (e.g. on vacations), and then push at the end of the week. It’ll be the same as having pushed everyday during one week (this works with personal projects, be careful with projects where there are other contributors)
- Only contributions on 'master' are counted by GitHub, so if you use multiple branchs for new features / bug fixes, the contributions will count only when (and if) you’ll merge them into master
Actually, it is not the master branch. It is the default branch. I have a repo with a gh-pages branch, this works as well.
TFA isn't about a productivity metric, it's about establishing a habit. Everyone from Jerry Seinfeld to Anne Lamott to Pablo Picasso extoll the virtue of making a habit of doing some work--even sometimes crappy or merely symbolic work--every day. ("Inspiration exists, but it has to find us working")
But that said, it's not as if doing something every day is totally uncorrelated to productivity. Sure, it's a proxy metric at most, but doing something is eventually a prerequisite to productivity.
But then again, maybe I'm a "clueless manager" type because I'd also argue that test-coverage isn't totally unrelated to quality. It's also a proxy metric and one that's relatively easy to game, but come on, is there anything in software development you find measurable?
Blogging on github ( octopress, Jekyll, static files etc ) is one of the easiest ways to contribute.
Btw, anyone with similar habit for consecutive days visited on stackoverflow? http://stackoverflow.com/users/526535/manojlds
0 - http://blog.chewxy.com/2013/06/25/dry-spell/
I like the fact that sometimes you don't have time to start something complex, but find small improvements or documentation updates that can be made.
A song of GitHub for this user is quite interesting ;)
You're all being gamed by a flashy calendar.
Anyway, you MUST make commit an habit. If you're into gamification, force yourself to do that and you won't regret.
but i just recommitted a project that's been dormant for 10 months so maybe I can pick away at it and make it not suck by the end of the week.