Uploaded work and contacting students

[Adam Light]

Hi Leslie

We've run into two technical problems with the Drupal GHOP program and were hoping you could answer a few questions for us.

1.  For several of the tasks, a task was marked closed after the student submitted the work and it was reviewed and accepted, but before the student uploaded his/her work as an attachment to the task.  In many cases the task was a documentation style task and the student's work was to create pages on drupal.org.  I have added a comment to every issue in our GHOP queue where the student has not uploaded his/her final work to the task itself, however we have about 20 tasks for which there is still no final work attached.  I think part of the problem is that students apparently only get emails when their tasks have new comments if they've clicked the yellow star to subscribe.

So, the question:  Can we take on the burden to upload files to the tasks when students have not yet done so?  I would feel bad if a student doesn't get credit for a task they completed when it is partially our fault for not making sure they uploaded their work before we gave them credit for the task.

2.  We don't have a good way to reach all of our students to make sure that they know how to claim their prizes.  In retrospect, we should have required that all students subscribe to one of our mailing lists so that we have at least one way to contact them.  But we didn't think to do that earlier.  We can't see their email addresses on the Google code site, and as I mentioned above not all students have subscribed to their tasks so we can't even necessarily reach them that way.  We've sent out an email to our Drupal GHOP mailing list, and have a post about this on our site, but we know that not all students are subscribed to the mailing list.  Do you have any suggestions on how we can reach all of our students, or whether there's a way for us to track which students have turned in their claim forms so we at least know which students we need to try to contact?

Thanks
Adam Light

[Leslie Hawthorn]

Hi Adam,

On Feb 1, 2008 2:10 PM, Adam Light <acl...@gmail.com> wrote:

Hi Leslie

We've run into two technical problems with the Drupal GHOP program and were hoping you could answer a few questions for us.

1.  For several of the tasks, a task was marked closed after the student submitted the work and it was reviewed and accepted, but before the student uploaded his/her work as an attachment to the task.  In many cases the task was a documentation style task and the student's work was to create pages on drupal.org.  I have added a comment to every issue in our GHOP queue where the student has not uploaded his/her final work to the task itself, however we have about 20 tasks for which there is still no final work attached.  I think part of the problem is that students apparently only get emails when their tasks have new comments if they've clicked the yellow star to subscribe. 

So, the question:  Can we take on the burden to upload files to the tasks when students have not yet done so?  I would feel bad if a student doesn't get credit for a task they completed when it is partially our fault for not making sure they uploaded their work before we gave them credit for the task.

As long as the task was reviewed and marked complete, it is OK to back update the task with information on the work submitted.  This is definitely suboptimal, but it's a pilot, so mistakes happen.  Please fix it yourselves if you can't reach the student to do it and we're good.
 

2.  We don't have a good way to reach all of our students to make sure that they know how to claim their prizes.  In retrospect, we should have required that all students subscribe to one of our mailing lists so that we have at least one way to contact them.  But we didn't think to do that earlier.  We can't see their email addresses on the Google code site, and as I mentioned above not all students have subscribed to their tasks so we can't even necessarily reach them that way.  We've sent out an email to our Drupal GHOP mailing list, and have a post about this on our site, but we know that not all students are subscribed to the mailing list.  Do you have any suggestions on how we can reach all of our students, or whether there's a way for us to track which students have turned in their claim forms so we at least know which students we need to try to contact?

Honestly, the onus is on the students to submit their prize claims.  We asked folks to subscribe to the contest announcement list for information on how to claim their prizes.  If folks do contact you, please point them here (and more detail to follow):

http://groups.google.com/group/ghop-announce/browse_thread/thread/e5dd796f845e5c5d

If they can't figure out how to claim their prizes, I am sure they will contact you/us/send a mail to the discussion list. 

Cheers,
LH
--
Leslie Hawthorn
Program Manager - Open Source
Google Inc.

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

[Matthew Wilkes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Here's a fun one,

A couple of our tasks were re-arranging our issue trackers and merging
them all into one übertracker. That's quite hard to attach, what
shall we do?

Matt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFHopvXZnKd+ctxHMoRAj1IAKCdlPi/gUyQB+pjL5k7uvBUDSRrLQCfZbB+
p27waskIL0VhNyTdk69/miA=
=MbKa
-----END PGP SIGNATURE-----

[Leslie Hawthorn]

On Feb 1, 2008 3:11 PM, Matthew Wilkes <mat...@matthewwilkes.co.uk> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Here's a fun one,

A couple of our tasks were re-arranging our issue trackers and merging
them all into one übertracker.  That's quite hard to attach, what
shall we do?

Point to the work done as a comment in the issue tracker, then we should be OK.