diff --git a/src/lescrampte/badass/index.html b/src/lescrampte/badass/index.html new file mode 100644 index 0000000..dd95c1e --- /dev/null +++ b/src/lescrampte/badass/index.html @@ -0,0 +1,553 @@ + +
+ + + + + + + + + + + + + +
+Please adhere to 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 student or group whose work is evaluated the possible
dysfunctions in their project. Take the time to discuss and debate the
problems that may have been 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. Pedagogy is effective only if peer evaluation is conducted seriously.
+
+- Only grade the work that was turned in the Git repository of the evaluated
student or group.
- Double-check that the Git repository belongs to the student(s) and ensure that
the project is the expected one. Also, check that 'git clone' is used in an
empty folder.
- Check carefully that no malicious aliases were used to deceive you into evaluating
something that is not the content of the official repository.
- To avoid any surprises and if applicable, review together any scripts used
to facilitate the grading (scripts for testing or automation).
- If you have not completed the assignment you are going to evaluate, you have
to read the entire subject prior to starting the evaluation process.
- Use the available flags to report 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 in cases of cheating, students are
strongly encouraged to review the submitted work together
to identify any mistakes that should not be repeated in the future.
+