We need a way to identify bitesized bugs in redmine.

More specifically, we need to:

1. "tag" an issue in some way so that it's clear it's bitesized
2. trivially query the system for all bitesized bugs

This gets progressively more important as we continue to get new contributors.

I'm going to make this an Immediate priority for 0.0.3 to at least look into more. If it's the case that we can't do this, then that's a very compelling reason to switch to another bug tracking system.

Problem

My images are overlapping each other, sometimes obscuring captions, therefore I find them less amusing.

Have you seen my giraffe? <holds hands out in front of chest, about shoulder-width apart> He's like, this big.

Hitman monkey <holding on to boy's head in rapidly flowing water. boy appears to be struggling> finds little pleasure in his job

I imagine this is a bitesize coding issue because I don't think it evokes any questions about design or implementation strategy.

tl;dr - I'm going to try and break up redmine tickets into three stages and record my findings here. I think it could help speed us along.

I find myself wanting to help a lot but (a) my abilities are limited at this point, and (b) it's hard to grab hold of these redmine tickets and run with them. I think we could quickly and easily break these tickets down into smaller bites, which would make our lives more wonderful in every way. I propose we use the following three ticket categories to clearly differentiate between the stages needed to complete an iteration:

• design
• implementation strategy
• coding

They each flow into the next, ie a design issue, once resolved, results in an implementation strategy issue, which when resolved would create a coding issue.

For example,

• design - the message queuing issue requires thought on multiple levels. At the top are design questions like, "how do we want the message queuing system to work, exactly? Which messages might we want to display? when? on which pages? where on those pages?"
• implementation strategy - below that are implementation strategy questions like, "is there an existing python package for this? would it be better to code a new one? What would the code look like, and where would it have to go?"
• coding - finally, there is (1)coding, (2)pushing, (3)review [goto 1] and (4)merging.

Breaking up issues into these smaller bites, ie separate tickets could speed things along. By confining the discussion to smaller areas, we free ourselves up by limiting the number of things we have to think about at the same time. Here's my suggestion - think about these categories as you are perusing redmine, and report back here with your findings. Or just follow along as I try it and give me feedback.

Or, if this problem is already solved in your mind, please point me to some reading material. Thanks!