On Wed, Apr 9, 2014 at 3:53 PM, Dan Garry <dgarry@wikimedia.org> wrote:
I have been raising these issues from time to time in our weekly meetings. I've thought about that, and decided that that meeting is long enough already without me trying to cram more into it. I think a large part of the lukewarm response I get trying to recruit people to do these things is due to the forum I'm raising these issues in. So I've got an alternative solution: product microtasks™ [1].

Product microtasks are problems that have been reported by a user that I have assessed, prioritised, and defined a clear-cut engineering solution for. If you're stuck on your current project and want something else to work on to cleanse your programming palate, you can do one of these. The intention for these is that they're little discrete chunks of work that are easy for you to pick up and not have to worry about defining the solution, just implementing it.

I think this is a good idea! I also think you should go ahead and continue raising these tasks in our weekly meeting. Perhaps we could make microtasks be one of our regular sections in the Google doc. I think your effort to articulate the scope and selection criteria for these tasks will make recruiting developer time easier.