Changing project after application?
olafBud...@gmx.net
It seems we have two very promising applications for the same project
idea. We don't want to have two students working on it, as redundancy
seems rather pointless for this task. So we want to ask one of the
students to work on some other project. (For the same organisation, of
course.)
Now the question is: Is it allowable for a student to work on a differet
project than the one he originally applied for? Or should we better ask
the concerned students to hand in a second application for a different
project?
-antrik-
Ryan Pavlik
(out of band, so to speak) to apply again with a different project. The
personal portion and experience portion could easily remain the same,
and presumably the student would understand the new project well enough
to write a (concise) summary.
--
Ryan Pavlik
www.cleardefinition.com
#282 + (442) - [X]
A programmer started to cuss
Because getting to sleep was a fuss
As he lay there in bed
Looping 'round in his head
was: while(!asleep()) sheep++;
David Anderson
Yes :-).
It's fine to ask students to work on something else. If you believe
that they have what it takes to work on another project without a
proposal, that's fine. However, I think that a new application for the
task in question couldn't hurt - it'd get a few design and timeline
questions out of the way now, and having an application whose title
matches the actual task to perform will be less confusing during
ranking. Plus, if both students are selected, both their abstracts
will be made public, which would further confusion if the application
is still for the original task, rather than the one being worked on.
So, to sum up, it's fine to offer alternative tasks to students, but
it would be best in that case to have them write up a separate app for
it, so that the title and abstract are right at least.
- Dave
>
> -antrik-
>
> >
>