Please respect the following rules:
- Remain polite, courteous, respectful and constructive
throughout the evaluation process. The well-being of the community
depends on it.
- Identify with
the person (or the group) whose work is evaluated the possible
dysfunctions in their project. Take the
time to discuss
and debate the problems you may have identified.
- You must consider that there
might be some differences in how your
peers might have understood the project's instructions and the
scope of its functionalities. Always keep an open mind and grade
them as honestly as possible. The
pedagogy is valid only and
only if peer-evaluation is conducted seriously.
- Only grade the work that is present in the Git repository of the
student or group.
-
Double-check that the Git repository belongs to the student
or the group. Ensure that the project is the
one expected
and also check that "git clone" is used in an empty folder.
- Check carefully that
no malicious aliases was used to fool you
and make you evaluate something that is not the content of
the
official repository.
- To avoid any surprises and if applicable, review together the
scripts used to facilitate the grading (scripts for testing or
automation).
- As an evaluator,
if you have not completed the assignment you are
going to grade, you then have to read the entire
subject prior to
starting the defence.
- Use the flags available on this scale to signal an
empty repository,
a non-functioning program, a norm error, cheating, and so forth.
In these cases,
the evaluation process ends and the final grade is 0,
or -42 in case of cheating. However, except for
cheating, student are
strongly encouraged to discuss the work that was turned in together,
in
order to identify any mistakes that shouldn't be repeated in the
future.