From 22438ce16aa4d06f3a3764cf00e6f77a36c4ce6a Mon Sep 17 00:00:00 2001 From: Adomas Date: Thu, 2 May 2024 13:52:30 +0200 Subject: [PATCH] Delete docs directory --- docs/agendas/template.md | 62 ---------------------------------------- docs/agendas/week-01.md | 46 ----------------------------- docs/agendas/week-03.md | 61 --------------------------------------- docs/agendas/week-04.md | 51 --------------------------------- docs/agendas/week-06.md | 43 ---------------------------- docs/agendas/week-07.md | 43 ---------------------------- docs/agendas/week-08.md | 48 ------------------------------- docs/agendas/week-09.md | 45 ----------------------------- docs/feedback/.gitkeep | 0 docs/feedback/week-01.md | 13 --------- docs/feedback/week-02.md | 50 -------------------------------- docs/feedback/week-03.md | 50 -------------------------------- docs/feedback/week-04.md | 52 --------------------------------- docs/feedback/week-06.md | 51 --------------------------------- docs/feedback/week-07.md | 51 --------------------------------- docs/feedback/week-08.md | 53 ---------------------------------- 16 files changed, 719 deletions(-) delete mode 100644 docs/agendas/template.md delete mode 100644 docs/agendas/week-01.md delete mode 100644 docs/agendas/week-03.md delete mode 100644 docs/agendas/week-04.md delete mode 100644 docs/agendas/week-06.md delete mode 100644 docs/agendas/week-07.md delete mode 100644 docs/agendas/week-08.md delete mode 100644 docs/agendas/week-09.md delete mode 100644 docs/feedback/.gitkeep delete mode 100644 docs/feedback/week-01.md delete mode 100644 docs/feedback/week-02.md delete mode 100644 docs/feedback/week-03.md delete mode 100644 docs/feedback/week-04.md delete mode 100644 docs/feedback/week-06.md delete mode 100644 docs/feedback/week-07.md delete mode 100644 docs/feedback/week-08.md diff --git a/docs/agendas/template.md b/docs/agendas/template.md deleted file mode 100644 index bf2d9fc..0000000 --- a/docs/agendas/template.md +++ /dev/null @@ -1,62 +0,0 @@ -## Example agenda - -This is a template agenda. It gives an overview of what could be in your weekly agenda. -In the 'Points of action' part you will also find some topics to cover in/after your first meeting. - ---- - -Date: {Insert Here}\ -Main focus: {Insert Here}\ -Chair: {Insert Here}\ -Note taker: {Insert Here} - -In italics, you will find some additional explanations of the agenda points. You will find mostly the same points in the next agendas. - -# Opening -*Here you check that everybody is present.* - -# Approval of the agenda -*Make sure everything that needs to be discussed is in the agenda or add it if something is missing.* - -# Points of action -*The items below are things you should look into after the first meeting. During the meeting you can divide (some of) the work between the team members, so that everybody has something to do afterwards.* - - - Read Resources and Tools (on BrightSpace) - - Make sure you have a Mattermost channel (your TA will create one for you) - - It is your job that you and your team contribute (equally) - - If there is a problem it is your job to notify the TA - - Create a planning and put it on GitLab - - Implement all items on the todo list - - Discuss a cake rule: If you are late or not there at all, you have to bring cake (or something similar) - - Things to research: - - Scrum (see lecture 1) - - How are you going to use scrum in the team? - - Git (see lecture 2) - - How does it work? - - What is branching? - - Gradle (see lecture 4) - - What does it do? - - How do you add a library to the build file? - - Code structure (see lecture 4) - - How will you use packages? - - What will your code structure look like? (UML) - - GUI - - OpenFX - - IDE - - Eclipse - - IntelliJ - -# Action points for next week (Scrum board) -*Every week you fill the Scrum board with new action points for that week. See the to do list for the items you should implement.* - -# Any other business -*If anybody has something that should be discussed but came up with that after the agenda was finalized (in point 2), he/she should bring that up now so that it can be discussed after all.* - -# Questions for the TA -*Your TA will visit you in the second half of the lab session. Note down all questions that you have so that you can ask them then.* - -# Question round -*If there are any questions, now is the time to ask them.* - -# Closing -*Now you can start working on the project. Good luck!* diff --git a/docs/agendas/week-01.md b/docs/agendas/week-01.md deleted file mode 100644 index 9d3aec2..0000000 --- a/docs/agendas/week-01.md +++ /dev/null @@ -1,46 +0,0 @@ -| Key | Value | -| --- |------------------------------------------------------------------------------------------------------------------------------| -| Date: | 20.02.2024 | -| Time: | 13:45 | -| Location: | Cubicle 3 | -| Chair | Nikola Emilov | -| Minute Taker | Adomas Valiukevičius | -| Attendees: | Jordan van den Hoek, Adomas Valiukevičius, Leonid Margulis,
Kaan Altıntaş, Emiel Cijsouw, Nikola Emilov, Alexandra Neagu | - -**Prerequisites** -- Everyone is aware of the Code of Conduct assignment and the Project Backlog - -**Objectives** -- The main point of the meeting is to separate work for the Code of Conduct assignment - -**Agenda Items** -- Opening by chair (1 min) -- Check-in: How is everyone doing? (1 min) -- Announcements by the team (1 min) -- Approval of the agenda - Does anyone have any additions? (1 min) -- Approval of last minutes - Did everyone read the minutes from the previous meeting? (1 min) -- Talking Points: (decision-making/discuss) - 1. Discuss difficulties regarding Git. (5 min) - 2. How are we going to separate the work for the next assignment? (17 min) - 3. How are we going to combine our work? (3 min) - 4. Briefly discuss the project. (5 min) -- Summarize action points: Who , what , when? (3 min) -- Feedback round: What went well and what can be improved next time? (2 min) -- Planned meeting duration != actual duration? Where/why did you mis -estimate? (1 min) -- Question round: Does anyone have anything to add before the meeting closes? (2 min) -- Closure (1 min) - -**Estimated duration: 44 min** - -**Notes** -- no special announcements -- working week starts at the day of the weekly mandatory meeting (Tuesday) -- start working on the project from Week 2. -- 100+ lines of codes, 3 commits, have merge request, approve somebody else request starting Week 2. -- discussed code of conduct mini-deadlines, work distribution in the team, where to put the content (google docs) -> (formatting) -> uploading pdf. -- values discussed during meeting: -- - we make decisions together (collaboration), -- - profesionalism, -- - respect towards every of the team, -- - traspancency, -- next meeting on Thursday 5PM, which is going to be for discussing progress on code of conduct as well as the preferences towards the project (frontend, backend), and what tasks are going to be assigned to each person for Week 2. diff --git a/docs/agendas/week-03.md b/docs/agendas/week-03.md deleted file mode 100644 index 37f4608..0000000 --- a/docs/agendas/week-03.md +++ /dev/null @@ -1,61 +0,0 @@ -## Agenda week 3 - -Date: 27 Feb \ -Time: 13:45 \ -Location: Drebbelweg \ -Chair: Adomas \ -Minute Taker: Leo \ -Attendees: 6 + TA - -### Updates from last week / announcements (~16 minutes) -- Opening by chair (1 min) -- Code Of Conduct review (5 min) -- Weekly review of achievements related to assignment. Individual assesment of each others work (10 min) - -### Talking Points (~25min) -- Merge requests (5 min) -- - Merge Request Owners -- - Approving/Closing -- Considerations about what endpoints, services will we need on server-side (5 min) -- - Looking at template implementations (3min) -- Discussion on mock up examples and/or additional pages (5 min) -- Creating relevant issues in gitlab for discussed topics (5 min) -- Checkstyle configuration agreement (2 min) -### Finishing up (~5min) - - Goals for the upcoming week (3 min) - - Minute taker reads notes (2 min) - - Any questions, discussion with TA - -Total time: 45 minutes -**Notes** -- Code of conduct seems to be complete, we will meet on Thursday to discuss it and submit. -- All of the merge requests regarding the schema were sucessfuly closed. We are on track -- If somebody opens their merge request, exactly this person should merge it. избежать miscommunication -- After submitting Code of Conduct, this week we create issues for each of the basic requirements and implementing the server side of all the basic controllers -- All of us agree on the checkstyle -- We decide to write javadoc only when it's necessary -- Controller, Service, Repository -- We need to have at least one test for each endpoint -- We'll probably use Mockito for it -- We test all of the exceptions and then we test that it was added -- For a good grade we focus on doing 80% test coverage for functional classes(entities, controllers, jpa classes). In general it's better to test as much as possible. -- We must not do bad tests (such as overlapping tests or something similar) -- It's better to do boundary testings then just focusing on test coverage - -Tasks for this week: -- creating an event (Adomas) -- joining an event (Adomas) -- change title event (Leo) -- delete event (Leo) -- get event by id (Adomas) -- remove (participant) from event (Leo) -- expire the inviteCode (generate new) (Nikola) -- creating expense (requires title, payer, participants, amount) (Nikola) -- getting expense (Nikola) -- deleting expense (Kaan) -- changing expense details (title, amount, participants) (Kaan) -- get total participant debt (Emiel) -- get all debts in event (Emiel) -- create new transfer (requires from, to, amount, message) (Jordan) -- mark transfer as approved (only transfer receiver should be allow to mark it as approved) (Jordan) -- update bank account, name, email (Adomas) \ No newline at end of file diff --git a/docs/agendas/week-04.md b/docs/agendas/week-04.md deleted file mode 100644 index fcecdea..0000000 --- a/docs/agendas/week-04.md +++ /dev/null @@ -1,51 +0,0 @@ -## Agenda week 4 - -Date: 5 March \ -Time: 13:45 \ -Location: Drebbelweg \ -Chair: Jordan \ -Minute Taker: Kaan \ -Attendees: 6 + TA - -### Updates from last week / announcements (~15 minutes) -- Opening by chair (1 min) -- Controllers and Service Classes Check(12 min) -- Some tests are not finished yet(2 min) - -### Talking Points (~25min) -- The talk about reasons why test fails(2 min) -- The reason for why Debt not implented(1 min) -- We'll talk about how actualy client works on thursday meeting(2 min) -- Mentinoed resolved some conflicts(2 min) -- Importance of Team integration towards the project(3 min) -- Test Coverage is ok for now and future can be improved.(Aiming %80) (2 min) -- Some test are don't compile.(1 min) -- Buddy Check Assignment awarness.(Evaluation for team members)(3 min) -- Oral Exam.(Schedule can change if anyone of has a problem on that day)(2 min) -- Front End Devoplement Process(2 min) -- Assing one page each person.(2 min) -- Some functionalies can't implemented for now. (1 min) -- Decide database where to store.(1 min) -- Some design features on pages (1 min) - -### Finishing up (~5min) - - Goals for the upcoming week (3 min) - - Minute taker reads notes (2 min) - - Any questions, discussion with TA - -Total time: 45 minutes - - -### Chair - Minute Taker -- Leo -> Chair(Week-6) -- Niko -> Minute Taker(Week-6) -- Emiel -> Chair(Week-7) -- Jordan -> Minute Taker(Week-7) - -### Assign Pages -- Start Screen -> Adomas -- Leo Contact -> Details -- Kaan -> Invitation -- Niko -> Overview -- Emiel -> Open Debts -- Jordan -> Add Expense diff --git a/docs/agendas/week-06.md b/docs/agendas/week-06.md deleted file mode 100644 index 25c6bb3..0000000 --- a/docs/agendas/week-06.md +++ /dev/null @@ -1,43 +0,0 @@ -## Agenda week 6 - -Date: 19 March \ -Time: 13:45 \ -Location: Drebbelweg \ -Chair: Leonid \ -Minute Taker: Nikola\ -Attendees: 6 + TA - -### Updates from last week / announcements (~9 minutes) -- Opening by chair (1 min) -- We added mandatory approve to merge a branch (1 min) -- Discuss the code of conduct assignment. (We got 6/10) (2 min) -- Discuss why we failed in Tasks and Planning(5 min) - -### Talking Points (~31 min) -- Check what everyone did for the past 2 weeks. Discuss any issues and problems that might arise(5 min) -- Discuss our front-end style, so we do everything in the same style(4 min) -- Do we go for css? (1 min) -- Talk about how we store participant table? In the project backlog they had both IBAN and BIC, while we just have BankAccount. Do we really need User and where do we get it? (4 min) -- One more time about tests. What do we test? How much are we going to cover? How much coverage do we have right now? (2 min) -- What is left? We implemented Commons, part of Server and part of Client (5 min) -- How do we use server utils? (2 min) -- One more time about Oral Exam. Do we need a presentation for it? How do we divide our roles?(5 min) -- Are we going for some extra functionalities and what are they? Like transfering all of the debts only in n - 1 transfers, where n is the number of participants.(3 min) - -### Finishing up (~5min) - - Goals for the upcoming week (3 min) - - Minute taker reads notes (2 min) - - Any questions, discussion with TA - -Total time: 45 minutes - -## Notes -- decided to upgrade our planning -- we created a milestone for the week -- we have to use time-tracking and better labels for issues -- everyone should create their own issues, put the necessary features and assign it to themselves. -- we should start writing better descriptions -- we have created a template for the description of the issues -- decided to change the way the bank account is stored in the database -- we still haven't implemented the admin, providing choice of server and the language change. -- the tasks for the week are to finish the tasks from last week including the server \ No newline at end of file diff --git a/docs/agendas/week-07.md b/docs/agendas/week-07.md deleted file mode 100644 index 1f7f2a3..0000000 --- a/docs/agendas/week-07.md +++ /dev/null @@ -1,43 +0,0 @@ -## Agenda week 7 - -Date: 26 March -Time: 13:45 -Location: Drebbelweg -Chair: Emiel -Minute Taker: Jordan -Attendees: 6 + TA - -### Updates from last week / announcements (~6 minutes) -- Opening by chair (1 min) -- Short demo of the current application (5 min) - -### Talking Points (~27min) -- Check in on everyone about any issues about development last week. (3 min) -- Talk about whether a participants name should be unique since this issue came up last week (2 min) -- Talk about how to implement the language switch, researched by Jordan (2 min) -- Talk about the use of client side tests, researched by Kaan, and how we're going to reach the 80% test coverage (6 min). -- Talk about the implementation of the admin functionalities, researched by Leo (7 min). -- Talk about the use of long polling and web sockets, researched by Emiel (2 min). -- Talk about the implementation of user settings like language or a dark theme (2 min). -- Talk about how we're going to handle connecting to different servers and the user entities associated with them (2 min). -- Oral Exam reschedule to tuesday (2 min). -- Talk about the styling of the client application (1 min) - -### Finishing up (~5min) -- Goals for the upcoming week (3 min) -- Minute taker reads notes (2 min) -- Any questions, discussion with TA - -Total time: 38 minutes - -## Notes -- unique names checked by client, server allowes not unique names -- undo debt approving in debt scene -- fix edit expense being commented -- add back buttons to scenes -- double check once approving/deleting. Stuff thats hard to revert -- hci in general. Delete button with trash can etc. -- settings button; switch server, language, username, admin login (when starting server give password) -- Use websockets for debts and longpolling for participants -- seeing all total debts -- finish friday 12th april midnight \ No newline at end of file diff --git a/docs/agendas/week-08.md b/docs/agendas/week-08.md deleted file mode 100644 index 447b860..0000000 --- a/docs/agendas/week-08.md +++ /dev/null @@ -1,48 +0,0 @@ -## Agenda week 8 - -Date: 2 April -Time: 13:45 -Location: Drebbelweg -Chair: Kaan -Minute Taker: Emiel -Attendees: 6 + TA - -### Updates from last week / announcements (~7 minutes) -- Opening by chair (1 min) -- Project Pitch(1 min) -- Missing Requirements Implemented - (WebSocket, Long Polling, Admin, Settings, Language, Shortcuts)(5min) - - -### Talking Points (~24min) -- Check on everyone about any development problems last week.(4 min) -- Discuss about the merge request "Second part of Admin Functionality" by Leo(3 min) -- Testing still needs a work. Difficulties for testing each page and interactions between them.(5 min) -- Missing Requirements both Basic and Other(7 min) -- We should be able to edit the title of an event(1min) -- Tag functionality needs to be implemented.(1 min) -- Adding Statistic Page.(1 min) -- Styling the client side of app (Not getting into too deep but at least screen size can adapt to different devices)(2 min) - -### Finishing up (~5min) -- Goals for the upcoming week (3 min) -- Minute taker reads notes (2 min) -- Any questions, discussion with TA - -Total time: 36 minutes - -### Notes -- Confirmed that the late uploading of the presentation wasn't a problem. -- Confirmed that web socket communication doesn't need to be used for sending client data to the server. -- Discussed how participants should be added to an event by the owner of the event, decided that we should keep adding participants manually so that "ghost" participants can be created. -- Decided that we don't need to restrict editing participants to the owner of the event. -- Talked about the css styling and whether the application should be responsive, decided that we need to keep a uniform styling throughout the entire application and that we won't be doing full responsive design. -- Agreed on that everyone should test their own javafx controllers -- Talked about how we're going to implement indirect output tests. -- Talked about the HCI assignment, and how we're going to pass the multi-modality part of it. -- Discussed what should happen when a user wants to delete a participant that has debt entities related to them, decided that the server should not allow this. -- Discussd what features still need to be implemented before the end of next week. These include: - - Change the last activity field of an event when a user changes some data. - - Implementing the expense tags - - Implement the expense statistics - - Fix bugs including joining event with invite code not working, and debts not being created. \ No newline at end of file diff --git a/docs/agendas/week-09.md b/docs/agendas/week-09.md deleted file mode 100644 index 116cb73..0000000 --- a/docs/agendas/week-09.md +++ /dev/null @@ -1,45 +0,0 @@ -## Agenda week 9 - -Date: 9 April \ -Time: 13:45 \ -Location: Drebbelweg \ -Chair: Adomas \ -Minute Taker: Leo \ -Attendees: 6 + TA - -### Updates from last week / announcements (~7 minutes) -- Opening by chair (1 min) -- Did we manage to succeed on implementation last week - one by one (5min) -- Communication error - Adomas regarding language (1min) - - -### Talking Points (~32min) -- New feature implementation freeze (2 min) -- Known issues (10 min) -- Did we manage to fulfill all the missing criteria? (10min) -- What each of us is working till Thursday? (10min) - -### Finishing up (~4min) -- Feedback on Buddycheck (2min) -- Minute taker reads notes (2 min) -- Any questions, discussion with TA - -Total time: 43 minutes - - -### Notes -- Tag functionality is well implemented -- Statistics page is well implemented -- Handle exceptions on the Expense Overview page - Nikola -- Handle problems with duplicating debts when we reselect new participants on the Expense Overview Page - Emiel -- Not allow to delete Participant when this Participant is in some Debt - Leo -- Fix an issue with reconnecting to another server - Adomas -- Edit title of an Event - Nikola -- Deleting expense - Leo -- The deadline was rescheduled to Sunday evening instead of Friday evening -- On sunday we do not merge anything -- Next meeting on Thursday at 4.30 as usual -- Finish with java code until Thursday meeting -- Merge everything until Saturday evening -- Buddycheck DEADLINE Friday evening - diff --git a/docs/feedback/.gitkeep b/docs/feedback/.gitkeep deleted file mode 100644 index e69de29..0000000 diff --git a/docs/feedback/week-01.md b/docs/feedback/week-01.md deleted file mode 100644 index 234cbcb..0000000 --- a/docs/feedback/week-01.md +++ /dev/null @@ -1,13 +0,0 @@ -## Formative Assessment - Group 9 - -#### 1) Self-organization - -Excellent - Everybody participated in a nice introductory discussion. The tone was respectful, and they got to know each other and the project. - - -#### 2) Suggested Topics - -Excellent - All the suggested topics were covered. I also recommend taking a look at the teamwork lecture, to understand more what is expected of you. - - - diff --git a/docs/feedback/week-02.md b/docs/feedback/week-02.md deleted file mode 100644 index c1715cd..0000000 --- a/docs/feedback/week-02.md +++ /dev/null @@ -1,50 +0,0 @@ -# Group 9 - W2 Feedback - -#### Meeting Organization - -Mark: Pass - -Feedback: There were a char and a minute taker. - - -#### Agenda - -Mark: Excellent - -Feedback: The agenda was shared with the TA sufficiently ahead of the meeting. It followed the template provided by the course and the individual points of action/discussion were clear. - - -#### Performance of the *Previous* Minute Taker - -Mark: - - -Feedback: Not applicable, in W1 there was no minute taker. - - -#### Chair performance - -Mark: Excellent - -Feedback: The chair ensured that all the topics of the agenda were covered, with appropiate timing for each, and ensured that everyone was involved in the meeting discussions. - - -#### Attitude & Relation - -Mark: Excellent - -Feedback: The team took ownership of the meeting very well. Everyone was active in the meeting and engaged in productive discussions. The overall athmosphere was constructive. - - -#### Potentially Shippable Product - -Mark: - - -Feedback: Not applicable, development on the application has not started yet. - - -#### Work Contribution/Distribution in the Team - -Mark: Excellent - -Feedback: The students discussed the action list of last week, and also the plan of this week. - diff --git a/docs/feedback/week-03.md b/docs/feedback/week-03.md deleted file mode 100644 index 7331f7f..0000000 --- a/docs/feedback/week-03.md +++ /dev/null @@ -1,50 +0,0 @@ -# Meeting Feedback - Group 9 - -#### Meeting Organization - -Mark: Pass - -Feedback: There were a char and a minute taker. - - -#### Agenda - -Mark: Excellent - -Feedback: The agenda was shared with the TA sufficiently ahead of the meeting. It followed the template provided by the course and the individual points of action/discussion were clear. - - -#### Performance of the *Previous* Minute Taker - -Mark: Very good - -Feedback: The previous minute taker took a good amount of notes. They are clear and contain concrete agreements discussed during the meeting. The agreements are actionable and realistic, though in future consider also adding which people are assigned to which tasks in the notes. - - -#### Chair performance - -Mark: Excellent - -Feedback: The chair ensured that all the topics of the agenda were covered, with appropiate timing for each, and ensured that everyone was involved in the meeting discussions. - - -#### Attitude & Relation - -Mark: Excellent - -Feedback: The team took ownership of the meeting very well. Everyone was active in the meeting and engaged in productive discussions. The overall athmosphere was constructive. - - -#### Potentially Shippable Product - -Mark: Excellent - -Feedback: The team presented the current state of the their application, with good progress made from last week. Great job on it! You're on a good track toward creating a working application. - - -#### Work Contribution/Distribution in the Team - -Mark: Excellent - -Feedback: The students discussed the action list of last week, and also the plan of this week. The chairman held a standup where they made sure everybody was on track and finished their last week's work. - diff --git a/docs/feedback/week-04.md b/docs/feedback/week-04.md deleted file mode 100644 index 7551620..0000000 --- a/docs/feedback/week-04.md +++ /dev/null @@ -1,52 +0,0 @@ -# Meeting Feedback - Group 9 - -#### Meeting Organization - -Mark: Pass - -Feedback: There were a chair and a minute taker. - - -#### Agenda - -Mark: Excellent - -Feedback: The agenda was shared with the TA sufficiently ahead of the meeting. It followed the template provided by the course and the individual points of action/discussion were clear. - - -#### Performance of the *Previous* Minute Taker - -Mark: Very good - -Feedback: The previous minute taker took a good amount of notes. They are contain concrete agreements discussed during the meeting, but consider adding a bit more details to them to make them more undestanable afterwards. There was also a task distribution in the notes, with assigned people to the tasks. Good job on that! - - -#### Chair performance - -Mark: Excellent - -Feedback: The chair ensured that all the topics of the agenda were covered, with appropiate timing for each, and ensured that everyone was involved in the meeting discussions. He also accustomed for new topics requested to be discussed during the meeting, and made sure to bring the discussion back to the main points whenever it was straying unproductively, managing the time accordingly. - - -#### Attitude & Relation - -Mark: Excellent - -Feedback: The team took ownership of the meeting very well. Everyone was active in the meeting and engaged in productive discussions out of their own volition. The overall athmosphere was constructive. Keep it up! - - - -#### Potentially Shippable Product - -Mark: Excellent - -Feedback: The team presented the current state of the their application, with good progress made from last week, with the focus on backend. It's really good that you also already dived into integration testing and set up Mockito for it. For next week, when you're properly equipped after the JavaFX lecture, I suggest also working in the frontend such that you bring it to the same level of progress as the backend and you can connect them. - - -#### Work Contribution/Distribution in the Team - -Mark: Excellent - -Feedback: The students discussed the action list of last week, and also the plan of this week. The chairman held a standup where everybody presented what they worked on last week and made sure everybody was on track. - - diff --git a/docs/feedback/week-06.md b/docs/feedback/week-06.md deleted file mode 100644 index ed461d2..0000000 --- a/docs/feedback/week-06.md +++ /dev/null @@ -1,51 +0,0 @@ -# Meeting Feedback - Group 9 - -#### Meeting Organization - -Mark: Pass - -Feedback: There were a chair and a minute taker. - - -#### Agenda - -Mark: Excellent - -Feedback: The agenda was shared with the TA sufficiently ahead of the meeting. It followed the template provided by the course and the individual points of action/discussion were clear. - - -#### Performance of the *Previous* Minute Taker - -Mark: Very good - -Feedback: The previous minute taker took a good amount of notes. They are contain concrete agreements discussed during the meeting, but consider adding a bit more details to them to make them more understandable afterwards. There was also a task distribution in the notes, with assigned people to the tasks. Good job on that! Also, consider marking more clearly in the agenda where the agenda itself ends and where the notes start. - - -#### Chair performance - -Mark: Good - -Feedback: The chair tried to ensure that all the topics of the agenda were covered, with appropiate timing for each, and ensure that everyone was involved in the meeting discussions. He accustomed for new topics requested to be discussed during the meeting, and tried to make sure to bring the discussion back to the main points whenever it was straying unproductively, but sometimes the discussion would derail too much. On one side it was very nice to see everyone invested in the discussion and actively participating out of their own will, but on the other, keep in mind that you only have 45 mins a week with your TA, and some things you can discuss between yourselves whenever, whilst others, like TA announcements and updates, can only be discussed during this timeslot, so organize your future agendas and TA meetings accordingly. - - -#### Attitude & Relation - -Mark: Excellent - -Feedback: The team took ownership of the meeting very well. Everyone was active in the meeting and engaged in productive discussions out of their own volition. The overall athmosphere was constructive. Keep it up! - - -#### Potentially Shippable Product - -Mark: Good - -Feedback: The team presented the current state of their application, with progress primarly on the frontend. The progress comprised mostly of client scenes, and did not seem that substantial given the time available. You mentioned that you will work this week on connecting the client side to the server side, which I agree is the next logical step to do. Keep in mind to implement this with websockets, long-polling, and REST requests. You need to have these by the end of the project, and if you don't implement them early on, it will be harder to integrate them later and adjust your code to acommodate them. - - -#### Work Contribution/Distribution in the Team - -Mark: Excellent - -Feedback: The students discussed the action list of last week, and also the plan of this week. The chairman held a standup where everybody presented what they worked on last week and made sure everybody was on track. - - diff --git a/docs/feedback/week-07.md b/docs/feedback/week-07.md deleted file mode 100644 index be5587d..0000000 --- a/docs/feedback/week-07.md +++ /dev/null @@ -1,51 +0,0 @@ -# Meeting Feedback - Group 9 - -#### Meeting Organization - -Mark: Pass - -Feedback: There were a chair and a minute taker. - - -#### Agenda - -Mark: Insufficient - -Feedback: There was no agenda posted before the meeting. - - -#### Performance of the *Previous* Minute Taker - -Mark: Sufficient - -Feedback: The previous minute taker took a decent amount of notes, though they seem quite short for a meeting of 45 mins. Consider writing things more concretely. For example, you mention you aim to finish the tasks from last week, but you don't concretely include the distribution in the notes. Perhaps, in future notes, consider including the task distribution and summarizing a bit less and including more details, so after the meeting it's still clear what you meant in the notes. - - -#### Chair performance - -Mark: Sufficient - -Feedback: The chair ensured that everyone was involved in the meeting discussions. However, the meeting deviated from the agenda completely, and important parts such as the stand up from last week or announcements from the TA were skipped. New topics were accomodated into the meeting, but with poor time management, with one topic taking more than half the meeting time. To reiterate the point from last week, keep in mind that you only have 45 mins a week with your TA, and some things you can discuss between yourselves whenever, whilst others, like TA announcements and updates, can only be discussed during this timeslot, so organize your future agendas and TA meetings accordingly. - - -#### Attitude & Relation - -Mark: Excellent - -Feedback: The team took ownership of the meeting very well. Everyone was active in the meeting and engaged in productive discussions out of their own volition. The overall athmosphere was very nice and constructive. Keep it up! - - -#### Potentially Shippable Product - -Mark: Very Good - -Feedback: The team presented the current state of their application, with good progress made, particularly from Sunday when I ran and played around with your app. A lot more features were working since two days past, good job on that! Because of the button that was working but later commented out, and the demo running incosistenly between team members, I couldn't give an *Excellent*. - - -#### Work Contribution/Distribution in the Team - -Mark: Insufficient - -Feedback: This part of the meeting was overlooked and we didn't get to hold a stand up or discuss the action list of last week. - - diff --git a/docs/feedback/week-08.md b/docs/feedback/week-08.md deleted file mode 100644 index 672a9e1..0000000 --- a/docs/feedback/week-08.md +++ /dev/null @@ -1,53 +0,0 @@ -# Meeting feedback - Group 9 - - -#### Meeting Organization - -Mark: Pass - -Feedback: There were a chair and a minute taker. - - -#### Agenda - -Mark: Excellent - -Feedback: The agenda was shared with the TA sufficiently ahead of the meeting. It followed the template provided by the course and the individual points of action/discussion were clear. - - -#### Performance of the *Previous* Minute Taker - -Mark: Sufficient - -Feedback: The previous minute taker took a decent amount of notes, though they seem quite short for a meeting of 45 mins. Consider writing things more concretely. For example, you mention the tasks you aim to work on this week, but you don't concretely include the distribution in the notes. Perhaps, in future notes, consider including the task distribution and summarizing a bit less and including more details, so after the meeting it's still clear what you meant in the notes. - - -#### Chair performance - -Mark: Good - -Feedback: The chair ensured that everyone was involved in the meeting discussions. However, the meeting deviated sometimes from the agenda, and important parts such as the stand up from last week or announcements from the TA were skipped. New topics were accomodated into the meeting, but with poor time management, with certain topic taking more time than they should've. To reiterate the point from last week, keep in mind that you only have 45 mins a week with your TA, and some things you can discuss between yourselves whenever, whilst others, like TA announcements and updates, can only be discussed during this timeslot, so organize your future agendas and TA meetings accordingly. - - -#### Attitude & Relation - -Mark: Very Good - -Feedback: The team took ownership of the meeting very well. Almost everyone was active in the meeting and engaged in productive discussions out of their own volition. The overall athmosphere was very nice and constructive. Keep it up! - - -#### Potentially Shippable Product - -Mark: Good - -Feedback: The team presented the current state of their application, with good progress made, particularly from Friday when I ran and played around with your app for the Implemented Features rubric. A lot more features were working since then, such as the debt system. However, you didn't present me all the new functionalities implemented since last week. You started with presenting to each other the admin functionality, and then skipped over or brushed through newly implemented features. The focus of that functionality showing did not seem to be to present it to me, and so I couldn't get a clear grasp of what new additions you worked on. - - -#### Work Contribution/Distribution in the Team - -Mark: Insufficient - -Feedback: The team did not hold a stand-up and discuss what everyone did last week. - - -