Project Oriented Tasks
Published 2012-05-22 @ 12:00
Tagged productivity, omnifocus
Every project with a deliverable uses repeating tasks to manage itself.
Each nerd project corresponds to an open source product that I work on whether it is one of my own or a group project I contribute to. Each project has at least 2 repeating tasks to schedule task triage and release (assuming I have release responsibility for that project):
Triage is simply a matter of going over that project’s bug tracker to make sure that relevant tasks are assigned to me. Tasks are automatically created for every ticket assigned to me and added to that project in omnifocus. It also gives me the chance to look at existing tickets to see if they’ve been fixed already and need to be closed, or if I need more information from the user to make a decision.
Release is just that. If a project has had commits in the last cycle that are deemed “release-worthy”, then I’ll release. It doesn’t matter if it is a single bug fix or a major overhaul. Any commit that’s formatted for automatic changelog generation is considered “release-worthy” and will go out on the day that the release task is due. Hoe makes this so easy for ruby projects that there is no reason not to do it.