Angela Byron wrote:
Bruce Gordon wrote:
My earlier idea on having a Simpletest task accompany each module task is a way to double those tasks and improve quality. I know if you have almost no module tasks this does no good!
When things are bad it's often interesting to consider radical ideas. What about having the students submit tasks to a moderated queue that then gets approved/rejected.
Oops. Should read all the post first. I do realize that your particular task idea is dependent on module proposals, but I'm trying to stem off yet another "well what if we did something about $thingy?" thing which is ultimately unhelpful and frustrating. To the second point, students /are/ able to submit tasks to the same approval queue as everyone else (http://drupal.org/project/issues/ghop), but they can't claim tasks that they've proposed, due to the contest rules. So that eliminates a lot of the incentive there. However, creating tasks like "Research $foo area and come up with 5 GHOP tasks that could help improve it" _are_ legitimate tasks. But again, it takes people to actually step up and take the time to write them up and do the follow-up mentorship/guidance. *That* is what we need here. Not more ideas. -Angie