4/24/23 – Coach Meeting #14
- Discussed final steps for client handoff
- Discussed suggestions on how to clean up team page and leave documentation for future teams and class records
4/21/23 – Client Meeting
- Demonstrated final version of app and all features and how to use all features
- Set up login credentials for the admin to use
- Provided client with links to documentation
- Updated client on future timeline and work that can potentially be distributed to a future COMP 523 team, or another separate development team
4/19/23 – Team Meeting #14
- Discussed possible security hole and plans to patch the security hole
- Planned out timeline for final presentation
- Discussed which features would be pushed for another team to work on and which features to polish before final handoff
4/17/23 – Coach Meeting #13
- Updated coach that we are done implementing the basic requirements
- Discussed timeline for final presentation and documentation process for handing off work to client
4/14/23 – Client Meeting
- Let the client know about the deployed prototype so client can use some features immediately
- Filled in client on some feature of app
- Got some requested features from client
- Let the client know about future features that are being worked on and the last features that are being planned
4/14/23 – Team Meeting #13
- Demonstrated current progress and provided updates
- Discussed plans for last few things to implement and timeline for testing and cleaning up codebase and database for handoff to client and future deveopers
4/10/23 – Coach Meeting #12
- Presented feature to edit and add data to tables, and new UI, as well as the deployed prototype
- Discussed future timeline and new features to be prioritized in implementation
- Discussed logistics and rough plan for final presentation
4/7/23 – Team Meeting #12
- Discussed plan for testing and creating the backend functionality for the create, update, and delete API requests
- Discussed how to implement features requested by client
- Discussed timeline to write up documentation plan
4/3/23 – Coach Meeting #11
- Presented changes to frontend components for editing, updating, and adding data
- Discussed outcomes of client meeting with coach
- Got advice on which tasks to prioritize among performance improvements, new features, and new technologies to implement into codebase
3/31/23 – Team Meeting #11
- Discussed progress on adding create, update, and delete functionality to data within the admin portal
- Worked on slides and content for tech talk
- Compiled plans and information for the testing plan
3/31/23 – Client Meeting
- Demonstrated changes to existing volunteer app and showed current features of new admin portal (being able to see all volunteer and shift data).
- Asked client to send list of requested features.
- Updated client on future timeline and next steps for the admin portal.
3/27/23 – Coach Meeting #10
- Demonstrated new features of the admin app – the login page, reroute page, and getting data for volunteers, shifts, and signups
- Discussed improvements to be made to current features, such as rerouting to same place regardless of whether or not the user attempting to sign in has a volunteer account or not
- Updated coach with next steps (which is being able to post, update, and create data directly from admin app instead of having to do it through the Supabase client)
- Ran current idea of tech talk through coach
3/22/23 – Team Meeting #10
- Created the shared repository for the new admin app and ensured everyone could run it locally.
- Created a new table in the database that stores which users are admins.
- Brainstormed some features for the admin app, such as filtering shifts based on time, sorting shifts based on dates, and searching for clients.
- Verified that the admin app could fetch all data from all tables (no work done on adding/deleting/updating data yet).
3/20/23 – Coach Meeting #9
- Demonstrated the last improvements (dark mode implementation and modified routing routes) to be made on the deployed volunteer app.
- Discussed implications of the change in routing structure. We will ask the client about how the app is being used to understand if the modified routing structure will be included in the last changes.
- Updated coach about new plan to create a separate app for the admin side and discussed future timeline for the creation of the admin app.
3/10/23 – Team Meeting #9
- Merged changes in darkmode implementation branch into the new routing branch. We will test the new routing more extensively before pushing these changes to main, but the dark mode implementation does not break functionality, so we can safely roll out both changes at the same time.
- Decided to build a separate app for the admin portion of the project to utilize the features of NextJS 13’s app directory more easily. Both the admin app and the volunteer app will use the same database, but the admin app will have more access to modify the data and will not have a signup component.
- Identified a few quality of life changes for the existing volunteer app, which includes automatically refreshing the page on signup of a shift, and making the popup box close after clicking “Yes” to confirm cancelling a shift.
- Created a custom admin role in Supabase with full permissions to give flexibility to choose between the default Supabase’s supabase_admin role or this new custom admin role.
- Emailed the client about new changes being made and progress with the admin app.
3/8/23 – Team Meeting #8
- Planned what to present to client and information to update client about
- Discussed new changes (dark mode implementation and frontend routing changes)
- Discussed which order to carry out the following steps:
- Merging the dark mode implementation to the main branch
- Working on putting user information into the bottom of the navbar and hiding the logout button in the user information at the bottom of navbar
- Creating the separate volunteer and admin role in Supabase (we will do this as a team to all have the same understanding of the backend)
- Manually creating an admin user
- Creating an admin page that is only visible to the admin once they are logged in (no content on the admin page yet)
3/6/23 – Coach Meeting #6
- Reviewed recent commits with coach and received guidelines for selecting which files to include in commit, as well as making sure commit changes are atomic
- Learned how to create push protections in Github to ensure code reviews before pushing
- Presented new proposed routing plan and received feedback about how to implement the routing, as well as details to be careful about
3/3/23 – Team Meeting #7
- Discussed timeline for wrapping up UI changes for the existing deployed project
- Started discussion on a plan to separate volunteer authentication vs. admin authentication via Supabase roles, and possible alternatives
- Divided up areas of research for Supabase authentication and Next.js routing, but no solid plan for routing/authentication until next coach meeting
2/27/23 – Coach Meeting #5
- Discussed next step and timeline
- Discussed plan for integration of SMTP2Go email platforms, along with some alternatives
- Updated coach about information from the client
- Briefly discussed the viability of containing volunteer-related components to a single volunteer home page, planning to go more into detail next meeting when a diagram is drawn
2/24/23 – Team Meeting #6
- Discussed progress on frontend changes
- Discussed tasks to do, such as creating a midterm presentation and architecture diagram
- Worked on creating slides and content for the midterm presentation
2/21/23 – Client meeting #2
- Updated client on deployed UI changes
- Presented UI mock-up for admin front-end and received feedback
- Clarified technological specifications and detailed features based on client needs
2/20/23 – Coach Meeting #4
- Demonstrated completed frontend project changes.
- Discussed strategies on how to move forward with deployment and getting client requirements.
- Received tips for how to set up pull request template, naming commits, and setting up a team code review process.
2/17/23 – Team Meeting #5
- Identified quick front-end quality of life changes to be implemented and divided up tasks for each person to implement.
- Updated the team’s Linear dashboard and discussed quality of progress made so far.
- Created deadlines for the upcoming UI changes for each person.
- Set up dates and times for next client meeting and next team meeting.
2/10/23 – Team Meeting #4
- Discussed and worked on Formal Requirements with User Stories
- Discussed other bugs in the UI that were relatively smaller fixes and would improve usability such as obscuring the password from view as an account is being created and automatic formatting on the phone number a volunteer has on file
- Identified our next deadlines such as the Ethics assignment and Tech Specs due and scheduled meetings the following week, one specifically for the Ethics assignment as it is discussion based and one for our formal technical check-in.
2/6/23 – Coach Meeting #3
- Discussed team meeting with the client including which requirements Wake Smiles would like prioritized and what the team should focus on first
- Discussed which bugs were small enough to get started on to get team members familiar with the codebase (Dark Mode)
- Identified concerns about client data in the backend database and using the data while the team will be developing and testing the project
2/3/23 – Team Meeting #3
- Set up each team member’s individual developer environments
- Mapped frontend infrastructure for the existing codebase
- Identified important but quick fixes to get started on immediately
- Change the font color of dark mode to something other than white
- Redesign the navbar to separate the logout component from the rest of the navbar components
- Discussed features to be implemented
- Create a UI interface for the admin to view and modify database information
- Set up automated emails to volunteers
- Host the application on a custom domain
- Identified action items to do after the meeting
- Contact the client for Supabase access
- Research 3rd party libraries to handle date picking as well as generating various new components
- Diagram the data model
1/31/23 – Client Meeting #1
- Introduced ourselves and talked about the vision and mission of the product
- Confirmed currently implemented features of the projects and detailed user stories extending on existing features
- Requested first-hand and volunteer user feedback on the deployed website to improve website usability
- Discussed prioritizing specific features based on the client’s needs
- admin login page/dashboard
- UI improvements for dark mode
- Login information recovery
- Mass email communication
- Extend the volunteer sign-up for a clinical audience
- Outlined general communication expectations for the semester (bi-weekly meeting with additional meetings if needed)
1/30/23 – Team meeting #2
- Brainstormed questions for clients
- What features should we prioritize? (UI/admin features/email automation/etc)
- What would the admin page look like? (dashboard/drop-down menu/etc) What tasks should be completed with admin access?
- Is there a specific style guide for UI? (logos/color/font/etc)
- what differentiates this product from other volunteer managing applications?
- Are there additional features you want to add to improve the product?
- Updated project site with current information
- Detailed team roles and responsibilities
1/30/23 – Coach meeting #2
- Discussed what changes we need to make to update the team site. (Project description, Journal, and Deliverables)
- Action items:
- Brainstorm user stories questions for the client
- Update project site
- Advice:
- Begin identifying tech specs
1/21/23 – Team meeting #1
- Determined when to hold weekly meetings.
- Solidified general team rules
- Sent an email to the client to introduce ourselves and schedule a meeting