Moving WATcher to general development stage

[damithc]

@gycgabriel has done the first version of WATcher available at https://github.com/CATcher-org/WATcher
@luminousleek @chunweii @kkangs0226 what else does it need before getting IWM students to join its development work?

[chunweii]

@gycgabriel @damithc I think some basic documentation should be written to orient new developers to get started with WATcher. Other than that, I think IWM students can start to join its development work soon.

I just have some concerns about the problems in CATcher that were brought over to WATcher. For instance, the outdated dependencies.

[damithc]

Thanks for the inputs @chunweii
@gycgabriel can quickly write some minimal dev docs. Refer to CATcher docs when possible (i.e., document only what's different from CATcher -- we want WATcher devs to be familiar with CATcher, as that's the purpose of having this project).

[kkangs0226]

Agreed with @chunweii that the most important would be to set up a basic developer guide first! Like what Prof. Damith has mentioned, I think @gycgabriel can document the differences, and maybe point them towards the section in the CATcher guide for the similarities e.g. setup of environment etc.

Perhaps to get the developers started on the actual development, tags can be added to the issues in the repository so the developers can start with the more critical/simpler tasks first. Priority, difficulty, and aspect tags will be useful, and maybe @gycgabriel can decide on the priority for the issues.