Rules of the Game
As any other assignment, Tiger comes with its rules to follow.
- Thou Shalt Not Copy Code Nor Possess Thy Neighbor’s Code
It is strictly forbidden to possess code that is not yours. You are encouraged to work with others, but don’t get a copy of their code and don’t show or stream your code. See How not to go about a programming assignment, for more hints on what will not be accepted.
- Tests are part of the project, do not copy tests or test frameworks
Test cases and test engines development are parts of the Tiger Project. As such the same rules apply as for code.
- If something is fishy, say it
If something illegal happened in the course of a stage, let us know, arrangements might be possible. If we find out, the rules will be strictly applied. It already happened that third year students have had to redo the Tiger Project because their code was found in another group: -42/20 and a convocation to the assistants’ lab is seldom benign.
- Do not hesitate working with other groups
Don’t bother everybody instead of trying first. Conversely, once you did your best, don’t hesitate working with others.