2023 05 02 TA Meeting Notes

Meeting Notes

The notes are based on the corresponding agenda.

Each team member reports on their progress since the last meeting, including any completed tasks and any obstacles encountered.
Guiding questions:
- What did you do since the last meeting / last week?
- What are you planning to do next, until the next meeting / next week?
- Are there any obstacles in your way?

Everyone worked on the Project Plan and Code of Conduct, no obstacles were encountered.

GitHub - GitLAb issues:
- We want to mirror GitLab into GitHub, because issues are not mirrored to GitLab
- We should modify the development process, which is hard to do on GitHub, so preferred is GitLab
- We can make a project on the GitHub repository, which would separate our changes from the repo and allow us to use another pipeline
Project Plan Won't haves:
- They define the border of our scope
- Put there whatever we feel needs to be there
Blue Checkstyle
- Leave it there, as long as we can justify our choices
No MoSCoW for Non-Functional Requirements
For contacting the coach, wait a few more days then send a friendly reminder
How can we tell when documentation is sufficient:
- Every merge requests adds documentation
- Mostly up to us, but it must be there
Project plan is part of our grading:
- If the requirements change, it's not a problem, we just have to explain it to our TA through a small document that specifies the changes
How to quantify the quality of each other's work:
- Perhaps using code metrics, like absence of code duplication
- Doesn't need to be quantified to a number, but rather a set of requirements must be followed
CoC:
- We can elaborate more for our quality of work targets, not necessarily just our grade