[Doc] Define the user roles

[Huy-Ngo]

Expectedly resolve #192

The rendered table looks ugly due to word breaking tho.

[Huy-Ngo]

Hmm I think I should add the inheritance model here too.

[Huy-Ngo]

Eh... that model is not implemented anyway... should we include that?

[McSinyx]

As Raymond Hettinger once said, inheritance is for code reuse, and we do reuse code handling students and supervisors (in other words, there are places where they're treated the same). What you wrote described that well enough so I'm not sure what you planned to add.

[Huy-Ngo]

What you wrote described that well enough so I'm not sure what you planned to add.

I planned to add the UML for it, i.e. this one

By the way, since judge and supervisor can be the same person (though for different projects), what are we gonna do about it?

[McSinyx]

since judge and supervisor can be the same person (though for different projects), what are we gonna do about it?

I'd suggest adding a field judges to project which is differently invited (i.e. separate invite member from invite judge).

[Huy-Ngo]

I think judge can be added by the faculty's assistant.

[Huy-Ngo]

Referenced in #197