Decision Logs - Githubissues

mazfil / lab-allocator

COMP3500 - Resource maximisation planning system for labs

3 stars 1 forks source link

Decision Logs #93

Closed Edward-Nivison closed 3 weeks ago

Edward-Nivison commented 3 months ago

When you are making a decision, you can reference this issue over the semester in your commits, pull requests, comments. Wherever you see fit so that we can add the decision logs properly!

The structure for decision logs at the current moment is:

Decision	Outcome	Responsible Party	Decision Date	Status
Our client wants for distinctive colouring when viewing the timetable	We are working on filtering that will show what the user would like to see most prominently.	Frontend team	DD/MM/YYYY	In-Progress

This is an example, if you want to add your decision yourself to the decision log, it is located in laballocator/docs/Decision-log.md.

Thanks!

Edward-Nivison commented 3 months ago

We have made a decision to begin on the School of Computing Facilities team requirements that they have stated in previous communications (see issue #86 ). This is whilst we await for a reply from them regarding the implementation of a testing environment that we can use on campus and how we can access said environment. Date (12/08/2024)

Edward-Nivison commented 3 months ago

We have made the decision to also start testing on the development side, ahead of schedule to ensure that the product is working as intended and can produce what we are wanting it to produce. This is seen in issue #95

Edward-Nivison commented 3 months ago

We have made a decision to detail any important output that we should be showing to the audit in the Project Output. It isn't everything, as that would be impossible and ineffective use of our time, however it will show major points in our delivery to the client, team and project.