Jullia

• Underestimated time and effort required for solving my issue. I initially estimated the task to be around 1 hour as I assumed it would only need a simple if statement for admins. However, it took longer than estimated as I had to search multiple files for where notifications where handled for new posts and also understand the logic of how they work in nodeBB.
• Partial progress on milestone 1. The task I completed was only one part of the acceptance criteria for the user story feature I was working on. As it took longer than expected and as the next issue deals with the front end, I was only able to make these successful changes at the end of Sprint 1. I am currently working on the making a successful settings button for this feature.

Alice

• First, added my refactored code in src/socket.io/admin/rooms.js . However, it was not passing the lint and run test on my local repository, but teammate Mia took a look and it passed on hers.

• Second, I tried first adding backend to the roles function/user story. However, this proved to be more difficult as I'm not familiar with backend. I instead switched to front end where, after a lot of time searching for the correct file, I was able to implement a dropdown menu.

Mia
I spent 8 hours on issue #10 to create the frontend UI anonymous toggle button on the post page. I then spent over 8 hours trying to implement the backend feature in which turning the anonymous toggle button on would allow the user to post with an "Anonymous" username and default profile picture. I was having many issues passing in post data that had an "anonymous" username.

I believe the process took much longer than I originally anticipated because I underestimated how large the codebase was. It was very difficult to figure out exactly where to implement my code in the first place, and that was a very time consuming process. The front end UI change process was also very confusing until instructor instructions were officially released right before the sprint one deadline.

Attempts for issue #11 :
I created a event handler for the action of the user turning the anonymous toggle button on. This function seems to be working based on a lot of console.log tests that I performed to make sure that the returning properties were correct (returns true is the toggle button is on).

The issue I am having is deciding where to call this function. I tried finding a location to call it in the async function post in the same file, however, non of the input data seems to be directly related to the uid, username, or displayname.

Another attempt at connecting the backend to the frontend was in the src/topcs/posts.js file. I set postObj.user.username and postObj.user.displayname to "anonymous", and that correctly displayed an anonymous username when I tried posting something on the forum. I struggled to find a way to connect these statements under and if statement that would only execute under the condition that the anonymous toggle was actually on.

Essentially, I think our team harshly overestimated our capabilities of implementation in the course of 2 weeks, and took on too many user stories (should have tried to focus on 1 - 2).

Jasmine

• The goal of this milestone was to automatically set 'Homework' and 'Assignment' tags for all users in NodeBB. However, the process encountered several challenges:

Underestimated time requirement: initial estimates (2h) didn’t include the depth of the integration needed between the client-side tagging operations and the backend processes, and understanding NodeBB’s tagging mechanics took more time than anticipated.
Difficulty in finding the right code location: too much time was spent on locating the correct place in the codebase to implement tag assignment, and the distribution of tagging logic across different files made it difficult to find the exact file needed for modifying tags directly.
Time spent understanding tag behavior: the behavior of the tagging system was more complex than expected, eventually leading to delays as code needed to be debugged and better structured to align with the expected behavior.

Cheyu

• Difficulty in locating the tpl files for frontend changes and relevant js files for backend. Using the inspect in the browser's developer mode doesn't help a lot. Need to find a more efficient way to locate files in the next sprint.
• Setting up the quickstart theme repo, resetting it, and setting up the shared frontend repo takes up much more time than expected.