Question about uploading work for one of our tasks

[Adam Light]

Hi Leslie

One of our Drupal tasks (http://code.google.com/p/google-highly-open-participation-drupal/issues/detail?id=48) involved having the student take a very thorough usability review of the upcoming Drupal 6 release and create feature requests/bug reports in our issue tracking system on drupal.org for each problem identified in the usability review.  The student completed the task successfully, and in the process ended up creating about 30-50 issues in various places for the various bugs/requests.

As far as uploading the final work goes, what do you recommend?  I hate to have the student go back to those 30-50 issues and copy and paste the text from the issues into the Google tracker, as that would take a while and the original issues themselves might not make a lot of sense out of context like that.

Would it be OK if we don't require the student to upload the text of each issue he created?  Or, as an alternative, he did create 1 or 2 patches during the process.  We could have him upload those patches to the Google tracker so there is at least something there.

Thanks for your advice
Adam

[Leslie Hawthorn]

Hi Adam,

Please post the patches to the issue tracker and have the student
enter a comment hyperlinking to the issues in the Drupal tracker that
were the result of work on the task. That way students in the future
can get a good idea of the work required to complete a task of that
type.

After that, should be all set.

Cheers,
LH

--
Leslie Hawthorn
Program Manager - Open Source
Google Inc.

http://code.google.com/opensource/

[Adam Light]

Thanks Leslie

I'll let the student know.

Adam