On Wed, Nov 3, 2010 at 4:14 AM, Chad innocentkiller@gmail.com wrote:
+1. I feel like we're trying to change a workflow when we should be trying to get rid of a backlog. Instead of trying to discuss ways to improve the workflow, we should Just Do It.
The problem is agreeing on what "it" is. Every time I ask for a list of what the requests are, the list generally contains lots of things that many people agree are low priority and/or things that many would agree are too hard to tackle right now. For example, there are plenty of db cleanup exercises in the "shell" keyword, only some of which have cleanup scripts that would be of any use in addressing. A pared-down list of the most obvious problems to tackle stands a much better chance of actually being completed.
That said, I've been looking through the list of shell requests, and it does look like there are plenty there that do just need a little TLC. I believe it's generally Mark's team that would deal with that list, but it might be something that folks on my team can help out with (I know, I'll volunteer *you* to do it) :-P Seriously though, part of the problem is that it might be falling through the cracks because Mark thinks it's my job, and I think it's his job, so I'll follow up on that.
Having a good workflow is important, because it helps us see whether or not we're making progress, as opposed to relying on anecdotal evidence that we are/aren't.
Rob