Discussed pivotal tracking pointing system for user stories.
Gave respective points to all of the defined user stories.
Setup the next meeting on 11-4 for finishing wiki page and discussing with Brandon.

2022-11-4 In Person Meeting (1 1/2 hours)

Attended by Lucas, Brandon, Austin. Jack and Evan were unable to attend due traveling.

Finished wiki page
Finished submitting user stories to pivotal tracker after finalizing all points between all members.
Discussed future meeting for sprint setup

2022-11-6 Zoom Meeting (1 1/2 hours)

Attended by Lucas, Brandon, Austin, Jack, Evan.

Discussed Sprint 1 setup and work distribution.
Setup consistent meetings times for scrum meetings.
Assigned Scrum Master to Austin.
Assigned Product Owner to Brandon.
Setup RSpec.
Added chores to Pivotal Tracker.
Made further project layout decisions.

2022-11-7 In Person Meeting (15 minutes)

Attended by Lucas, Brandon, Austin, Jack, and Evan.

Discussed current progress and impediments for sprint 1.

2022-11-9 In Person Meeting (15 minutes)

Attended by Lucas, Brandon, Austin, Jack, and Evan.

Discussed current progress and impediments for each of our user stories for sprint 1.
Discussed finishing the MVP for sprint 1.
Set up a meeting to finalize our sprint 1 at 6:30 on 11-9.

2022-11-9 Zoom Meeting (1 1/2 hours)

Attended by Lucas, Brandon, Austin, and Evan. Jack was unable to make it due to conflicting meetings.

Finalized our sprint 1 product.
Filled out the SPRINT1Summary page and relevant information.
Discussed issues we had this sprint and how to fix them.

2022-11-11 In Person Meeting (15 minutes)

Attended by Brandon, Austin, Evan, and Jack. Lucas could not attend due to transportation issues.

Designated new Scrum Master to Jack.
Designated new Product Owner to Evan.
Discussed and confirmed to keep the same meeting layout for sprint 2 as we did in sprint 1.

2022-11-13 Zoom Meeting (2 hours)

Attended by Brandon, Austin, Evan, Lucas, Jack.

Discussed CI/CD Pipeline for our github repo.
Discussed new points for preexisting stories that were over or underestimated.
Discussed new stories that needed to be added due to previous unknown circumstances.
Discussed our point breakdown for sprint 2.
Determined application flow for a better understanding of story implementation that is consistent with the whole group.
Decided on the stories and order that each member would take and complete.

2022-11-14 In Person Meeting (15 Minutes)

Attended by Brandon, Austin, Evan, Lucas, Jack.

Each person spoke about their current progress and impediments regarding sprint 2.
Discussed expectations by next meeting.

2022-11-16 In Person Meeting (15 Minutes)

Attended by Brandon, Austin, Evan, Lucas, Jack.

Discussed the lofi sketches and database diagrams.
Discussed current work progress on pipeline and user stories.
Discussed Navbar for our website.
Discussed which user stories have impediments of other user stories for this sprint.

2022-11-18 In Person Meeting (15 Minutes)

Attended by Brandon, Austin, Evan, Lucas, Jack.

Discussed current progress and impediments.
Discussed work plans over break.
Discussed requiring linting in our pipeline.

2022-11-21 Zoom Meeting (1 hour)

Attended by Brandon, Austin, Evan, Lucas, Jack.

Discussed setting up a development branch so that we can keep the working production on main only. The idea was contentious.
Decided on not doing a development branch but rather having separate heroku deployments for commits tagged with the Sprints and non-tagged commits.
Jack currently finishing faculty search.
Brandon working on applications.
Austin working on sending private messages and receiving them, currently impeded by having logged in accounts.
Lucas working on log in functionality and user authentication. Beginning to look into student document storage.
Evan working on viewing student applications as a student and faculty, currently impeded by having logged in accounts.

2022-11-27 Zoom Meeting (1 hour)

Attended by Brandon, Austin, Evan, Lucas, Jack.

Discussed and wrote Sprint2Summary
Created a checklist of everything that needed to be done for each person before the end of Sprint2 (deployment, git tag, etc.)
Each person opened up pull requests for their respective features which were merged and solved.
Discussed how we could change the problems that we encountered this split going forward, specifically merge conflicts and feature breaking changes
Decided to have a Sprint 3 whiteboard meeting where we could draw our path for sprint 3 out so everyone not only starts off on the same page, but with a better understanding.

2022-11-28 In Person Meeting (1 hour 15 minutes)

Attended by Brandon, Austin, Evan, Lucas, Jack.

Discussed our current plans for Sprint 3. Sprint 3 Kickoff meeting.
Provided a layout of how we wanted our final product to navigate, see Sprint3Summary for details.
Decided to allocate some time to styling the way things are laid out so it is more intuitive for the user and makes sense -> given to Lucas
Discussed feature priority, deciding that getting full application functionality is very important and being able to search for universities is not important, so it was ice boxed.
Decided Lucas would be the new Scrum Master for Sprint 3 and Austin would be the Product Owner.
Allocated remaining user stories to people based on what they have been working on: i.e, Brandon takes application evaluation as he worked on the applications.
Discussed how we plan to create the 2-minute demo, as there is a lot of information to share -> demo should be split into student and faculty sections showcasing each side.

2022-11-30 Standup Meeting (in-person, 15 minutes)

Attended by Brandon, Austin, Evan, Lucas, and Jack

Discussed Rails's automatic handling of login session cookies and how it differs from manually-hashed session tokens. Ultimately, a clear understanding was unable to be reached.
Jack: Completed the approve faculty account feature without much issue. Described plans to make minor code tweaks based on input received on pull request. Continuing work on final decision for student application feature.
Evan: Was able to create user-specific home pages and requested our approval of the relevant pull request. Also made styling tweaks in a separate branch, which is currently pending approval.
Brandon: Highlighted his plans to work on the student evaluation feature later in the week.
Austin: Currently researching third-party authentication and the benefits/drawbacks of various gem libraries.
Lucas: Informed team of decision to enforce a length requirement for passwords. Described plans to fix session token tests. Stated he will begin work on the styling feature later in the week.

2022-12-02 Standup Meeting (in-person, 15 minutes)

Attended by Brandon, Austin, Evan, and Jack. Lucas was not in attendance due to a doctor's appointment.

Austin: Continuing to research OmniAuth and other third-party authentication implementation details. Expressed concerns of anticipated roadblocks with respect to proper testing and validation, given that much of the feature is out of our control.
Brandon: Discussed his plans to begin work on new features over the weekend. He believes that the time requirements of his stories may be an issue. After deliberation, it was determined that it is best to focus on the student evaluations story, as it is the most important of the features being worked on by Brandon.
Evan: Debated with the team about what exactly a "program" should encompass. We determined that these graduate programs would be largely correlated to areas of research selected by faculty members. He reports that he has started development on a feature that allows faculty members to add programs to the applications.
Jack: Informed the team of the successfully-completed final application decision feature and associated pull request. He plans to start working on chores, such as login validation for discussions and faculty account bug fixes, in the next several days.
Lucas: Spoke with team members individually to compensate for non-attendance. Points of discussion include the need to fix failing feature tests on his password-length/bug fixes pull request, as well as tentative plans to begin work on the styling story early next week.

2022-12-04 Sprint Review Meeting (Zoom, 1 hour)

Attended by all group members

Spent a significant amount of time deliberating on the merits and drawbacks of implementing third-party authentication. Austin reports that Twitter integration would require us to have a formally-written privacy policy. The group was hesitant to dabble in anything that could be treated as a legally-binding document. Additionally, third-party authentication would require significant changes to the Accounts model, due to the understanding that signing up through Twitter would mean that the user's email cannot be collected directly from the user during registration.
Discussed our highest priorities before the presentation. Current plans are to finish current user stories, ensure styling is at an acceptable point, and then hold off on taking on any additional heavy features. This will allow the most possible time to be spent on quality-of-life tweaks and bug fixes, as well as ensuring that the presentation will receive an appropriate amount of attention.
Went over high-level areas of focus for the presentation, including but not limited to: account creation, discussion posts, student application creation and document submission, faculty account approval, the pipeline, and our emphasis on process over aesthetics. The group has agreed to meet at some point during the middle of the week to begin work on the presentation together.
Discussed the possibility of last-minute additions to the Account model, namely adding the ability to update certain fields while logged in. The team felt that implementing session-less password resetting may be too significant of a security/spam vulnerability. It was agreed that any model changes would take the lowest possible priority over the next week, as it would be unwise to dedicate serious time to a feature which can only be implemented as a half-measure due to the aforementioned security concerns.

2022-12-05 Standup Meeting (in-person, 10 minutes)

Attended by all group members

This meeting was mainly dedicated to getting pull requests reviewed and merged.
An issue occurred when Lucas's PR branch was merged in. The repository setting of "require branch to be up to date" did not prevent the merging of his remote branch, which did not have the latest changes from the main branch. As a result, a test began to fail on the main branch as indicated by the merge pipeline job. The group then used the "revert" feature on GitHub to create another pull request which would restore the main branch to its previous state.

2022-12-07 Standup Meeting (in-person, 15 minutes)

Attended by all group members

Jack: Made tweaks to the homepage as well as various bug fixes relating to his views. Also added a marker to differentiate faculty from students on discussion posts. Implemented login protection for discussions and student checklists.
Austin: Merged message replies feature to main branch without issue. He is mostly done with his features for this sprint and will be looking for minor tweaks and bug-fixes to be made before the final deployment.
Evan: Continuing work on graduate program features, but did not give specifics about what he believed could be finished before the release deployment.
Lucas: Expressed frustration to the group about a significant amount of merge conflicts that were being encountered after the reversion pull request (#37) from Monday. His only guess was that the reversion did not cut PR #34 out of the main branch as hoped, but instead created a new hash which replaced all changes made. This meant that any attempt to pull the latest changes from the remote would undo nearly all changes made to his feature branch. His only option was to perform an interactive rebase and re-implement changes one by one. Even after this, branch protection rules prevented the merging of this branch. In the end, the only way to resolve the issue was to work closely with Brandon to move the main branch back tothe hash before PR #34. So that the changes from #34 could be re-applied without issue.
Brandon: Helped resolve a complicated issue with the main branch that occurred during the previous standup. Told the group that he will begin work on student application evaluations tomorrow, due to an unforeseen circumstance relating to a group project for another course.

2022-12-09 Standup Meeting (in-person, 10 minutes)

Attended by all group members

Brandon: Signified to the group that he would be working tirelessly to implement as many of his stories as possible before the release deployment. In particular, he believes he can finish application evaluations and the needed integrations with login checking.
Austin: Reported that he has no features left to implement, so he plans to help oversee deployment.
Jack: In response to a bug/implementation conflict with respect to the research areas implementation Evan is working on, he informed the team of his decision to make the field optional. This will allow disagreements between his Faculty model and Evan's ResearchArea model to be resolved, and the relevant view tables to be loaded without causing RecordInvalid issues.
Evan: Opened two new pull requests for features relating to the adding and searching of research areas for faculty. Stated that he plans to address the code review concerns raised by Austin before the colloquium meeting this afternoon.
Lucas: Finished up his navigation/styling feature and fixed all of the tests that were failing. He also informed the team that he addressed a security vulnerability where updates to faculty account approvals did not verify that the user was logged in as a Department Chair. Lastly, he informed the team of a situation regarding Evan's pull requests, wherein the second PR was a superset of the changes made in the first. To address this, he researched the best practice for handling "stacked feature branches" and in the end, edited PR #42 to merge into the branch of PR #41. This allowed reviewers to see only the differences between the two when reviewing #42, rather than all changes together.
The group agreed to meet over zoom to make the final deployment sometime after the colloquium meeting.

2022-12-09 Sprint Deployment Meeting (Zoom, 3 hours)

Attended by Brandon, Lucas, Austin, and Jack

The group worked closely together to oversee the sprint 3 deployment and implement last-minute features/bug fixes.
Jack stayed on for part the meeting, during which he provided guidance with respect to fixing an issue with his Faculty approval implementation, where no code existed to create the required Faculty records upon Account creation. He was unable stay throughout the meeting due to other obligations, but agreed to be available for communication throughout the evening.
Austin and Lucas went through the code and addressed as many lingering issues as possible, while Brandon worked hard to wrap up his application evaluation features. This synergy allowed changes to be implemented incredibly quickly, and in the end Brandon was able to deploy a huge set of additional features before the deadline.