Skip to content

Minutes of the Weekly Team Specific Meetings

Jump to bottom
Siddardth Pathipaka edited this page May 27, 2026 · 52 revisions

Welcome to the Request Microservices Wiki!

Purpose:
This page is designed to document weekly check-in updates where team members share what they worked on, what they are working on, and any blocks they’re facing, keeping everyone aligned, improving collaboration, and removing roadblocks to ensure smooth progress and project transparency.

Table of Contents

  • Every Wednesday at 1 PM PST our request microservices meeting is scheduled.
Meeting - 05/27/2026

Time:

  • 1:00 PM – 1:30 PM PDT

Project Manager's:

  • Siddardth, GiriTej

Attendees:

  • Siddardth, Gaurav, Linda, Shubham, Prashant, Pradnya, Kush Ahir, Anirudh, Shashank.

Note: This was the weekly progress and issue tracking standup. Wednesday standups at 1 PM PDT are now mandatory for all active team members. All members must attend at least two meetings per week: Wednesday standup and Friday scrum with Rao. If unable to join Friday scrum, Wednesday attendance is required so Siddardth can relay updates to Rao. Two team members (Shubham, Anirudh) have flagged upcoming departures due to OPT timelines.

Progress:

  • Gaurav - BA #26, new: #10 — BA #26 edit and delete APIs complete; additional details section in progress; will test locally with Rashmi once the build is done; ETA for full completion: June 3 (traveling with flight on Monday). Newly assigned to issue #10 (sendex synchronous notifications, high priority, collaborating with Linda)
  • Linda - #17 (complete), new: #10 — Raised and completed PR for issue #17. Newly assigned to issue #10 (sendex synchronous notifications, collaborating with Gaurav); will contact Shashank for handoff context on prior #10 progress
  • Shubham - new: #14 — Resolved local database connection issues; environment ready; newly assigned to issue #14. Note: OPT ending soon with no STEM extension available; expects to leave the org within 1-2 weeks
  • Prashant - #40 — Main implementation complete; blocked on test branch refactoring per the new architecture; PR expected Friday evening (May 29) or Saturday (May 30); will coordinate with Pradnya on branch issues after PR is submitted
  • Pradnya - #17 (complete), new: test branch coordination — PR for issue #17 raised against main branch; currently undergoing checks, not yet merged. Shifted focus to test branch refactoring; will coordinate with Prashant and share DevSecOps documentation with the team for PR creation guidance
  • Kush Ahir - #11 — Functionality working locally on feature branch; fixed helper response issue and Maven test suites; all test cases passing. Blocked since yesterday: GitHub 403 access errors and AWS Lambda access denied. Newly assigned to issue #33 (pending access restoration); action required with DevSecOps
  • Anirudh - new: #34 — AWS access obtained and database connection established; ready for new work; assigned to issue #34. Note: OPT ends June 15, has secured a contract job for STEM extension application. Needs HR contact for employment background verification
  • Shashank - #29 — Issue #10 reassigned to Linda and Gaurav. Newly assigned to issue #29. Ongoing blocker: AWS SQS integration access denied; has been coordinating with Aishwarya on the access issue

Challenges/Blockers:

  • Test branch blocker (P0, multiple devs affected): The dev branch is ahead of the test branch due to a prior forced PR merge, preventing several developers from raising PRs. A similar issue was previously resolved by the volunteer microservices group with Kirti's help. Pradnya and Prashant are coordinating on the fix; may require escalation to DevSecOps and Kirti
  • GitHub and AWS access issues (Kush Ahir, Shashank): Kush Ahir has GitHub 403 errors and AWS Lambda access denied since yesterday; Shashank has AWS SQS access denied; Siddardth will personally escalate to DevSecOps team leadership
  • Departing members: Shubham departing within 1-2 weeks; Anirudh departing June 15. Both to give one week's notice before last day
  • Anirudh HR verification: Needs a contact in HR for employment background check required for STEM contract application

Action Items:

  • Gaurav: Complete BA #26 by June 3; begin issue #10 in parallel
  • Linda: Start issue #10; coordinate with Gaurav; contact Shashank for handoff details on prior #10 progress
  • Prashant: Submit PR for issue #40 by Friday May 29; then assist Pradnya with test branch refactoring
  • Pradnya: Lead test branch refactoring coordination with Prashant; share DevSecOps documentation link in group channel
  • Kush Ahir: Add comment on issue #11 with current progress and move to blocked status; contact DevSecOps immediately to restore GitHub and AWS access
  • Shashank: Write up detailed description of AWS SQS access issue and send to Siddardth for escalation
  • Anirudh: Post in group asking for HR contact for background verification
  • Shubham: Give at least one week's notice before last working day; confirm ETA on issue #14 progress
  • Siddardth: Schedule call with Kirti to help resolve the test branch blocker
  • Siddardth: Escalate GitHub and AWS access issues directly to DevSecOps team PM
Meeting - 05/20/2026

Time:

  • [1:00 PM – 2:00 PM PDT]

Project Manager's:

  • Siddardth, GiriTej

Attendees:

  • Siddardth, Gaurav, Linda, Yashwant, Pavan Kalyan, Prashant, Krishna.

Note: This was a weekly progress and issue tracking standup. Pradnya was not on the call due to active blockers — Linda to follow up on her behalf and relay ETA to Sid. Shashank has ongoing access issues and is coordinating with Yashwant to resolve.

Progress:

  • Gaurav - BA #26: Took over from Janvi Ravi; had a call with Rashmi on Friday to understand frontend and backend requirements; APIs partially complete — edit functionality still needs to be implemented; local setup issues currently preventing testing; Gaurav is relocating to Seattle and will be unavailable for approximately 1 week in late May/early June; requested 1 day to confirm ETA for full issue completion
  • Linda - #issue 59 (Complete), #issue 17 (New): Completed issue #59 (API support — Get Help Requests); now assigned to issue #17 (CRUD functionality for comments on the request page); will collaborate with Pradnya on issue #17 — Pradnya has blockers and was not on the call; Linda to follow up and relay ETA to Sid
  • Yashwant - BA #64: Completed both dashboards (My Request Tab and Other Request Tab); implemented a sorting fix (descending order) per Rashmi's request; frontend integration pending Rashmi's sign-off on testing; will provide ETA for remaining work by end of day; Shashank has access issues and needs to connect with Yashwant to resolve
  • Pavan Kalyan - #issue 40 (New): Completed the getting started onboarding task — repository pulled, test branch connected, Postgres working; assigned to issue #40 alongside Prashant; to connect with Prashant via group message for guidance on the issue
  • Prashant - #issue 14 (Complete), #issue 10 (New): Implemented issue #14; code complete but needs verification due to VS Code setup issues; ETA for PR submission: Friday; reassigned from issue #40 to issue #10 (send asynchronous notifications); will coordinate with Shashank on issue #10 progress
  • Megha Narendhra - Getting Started: New volunteer onboarded following Siddardth's GitHub access restoration; assigned to getting started task; environment setup in progress
  • Himaja Dudhal - Getting Started: New volunteer onboarded following Siddardth's GitHub access restoration; assigned to getting started task; environment setup in progress

Challenges/Blockers:

  • Issue #58 branch blocker (P0): Janvi's completed work cannot be merged — the test branch is behind the dev branch due to a prior force-push directly to dev; Gaurav is the current point of contact but needs senior developer assistance; Krishna requested this be posted in the main Slack channel for broader visibility and help
  • No senior developer on the Backend Request team: Sharik and Fatima have left the org; Kirti has moved to the volunteer team; Rashmi is currently providing senior developer support for blockers on an as-needed basis
  • Gaurav unavailability: Will be unreachable for approximately 1 week during relocation (late May/early June), leaving BA #26 without a point of contact during that window
  • Pradnya blocked: Was not on the call; nature of blockers not detailed; Linda to follow up and get status on issue #17 coordination
  • Frontend integration pending for BA #64: Yashwant's dashboards are backend-complete; integration is waiting on Rashmi's testing confirmation

Action Items:

  • Gaurav: Provide ETA for BA #26 within 1 day
  • Linda: Contact Pradnya regarding issue #17 collaboration; get blocker details and ETA to share with Sid
  • Yashwant: Provide ETA for BA #64 completion by end of day; resolve Shashank's access issues
  • Pavan Kalyan: Connect with Prashant via group message for issue #40 guidance
  • Prashant: Complete issue #14 verification and submit PR by Friday; begin coordination with Shashank on issue #10
  • Siddardth: Post the issue #58 branch blocker in the main Slack channel to get senior developer support; assign an additional volunteer to issue #10
  • Krishna: Schedule a 1-hour session with Kirti next week; sync with Yashwant on codebase review

MVP Priority Status (as of 05/20/2026)

Noted during the meeting for team visibility:

  1. P0 tasks (2): Issue #58 (branch blocker — PR merge blocked) and Issue #59 (dashboard data display — backend complete, frontend integration in progress)
  2. P1 tasks (11): 6 assigned, 5 unassigned
  3. 3 new volunteers available for issue assignment — pending allocation
Meeting - 05/13/2026

Time:

  • [1:00 PM – 2:00 PM PDT]

Project Manager's:

  • Siddardth, Giritej

Attendees:

  • Siddardth, Yashwant, Linda, Gaurav, Pradnya, Prashant, Aniruddha, Shashank, SaiVarun.

Note: This was a weekly progress and issue tracking standup. Notes reconstructed from post-standup summary — confirm attendee list with Sid. Sid's GitHub access was unavailable during this meeting, blocking multiple new issue assignments.

Progress:

  • Yashwant - #issue 49 / BA #64: Deployed the getRequest API for the My Requests tab; initial testing confirmed working — Rashmi reported: "In initial testing it is working. I'll be testing it thoroughly tomorrow."; frontend integration with Rashmi ongoing
  • Linda - #issue 59: Recovered from sickness and back active; confirmed working on issue 59; needs a new issue assigned once Sid's GitHub access is restored
  • Gaurav - #issue 58, BA #26: Took over from Janvi following her departure from the org; met with Rashmi to collect frontend and backend requirements for BA #26; coding in progress; ETA pending
  • Pradnya - #issue 17: Actively working on CRUD functionality for the request comments page; ETA to be confirmed at next standup
  • Prashant - #issue 40: In progress; ETA to be confirmed at next standup; issue #47 remains blocked — Rishabh implemented the feature before leaving the org without providing final closure comments
  • Kush - #issue 11: Backend implementation complete per prior update; ETA was 5/7 — follow-up needed on PR status and AWS deployment
  • Aniruddha - #issue 37: Getting started task still in progress; progress has been slow over multiple weeks; direct follow-up required
  • SaiVarun - #issue 59: Assisting Linda; new issue assignment pending Sid's GitHub access

Challenges/Blockers:

  • Sid's GitHub access is down — blocking issue assignments for Linda, SaiVarun, Aniruddha, Pavan Kalyan, and two new GenAI team volunteers; 6 developers total waiting on assignments
  • Test branch is behind the dev branch — blocking the PR merge for issue #58 (Janvi's completed work is stuck); senior developer needed to resolve
  • Issue #47 cannot be formally closed — Rishabh left the org without providing final closure comments; Prashant needs to obtain his contact
  • Aniruddha has had minimal progress on issue #37 for multiple weeks; needs a direct push
  • Shubham has missed multiple consecutive standups with no response; escalation pending

Action Items:

  • Siddardth: Resolve GitHub access and assign new issues to Linda, SaiVarun, Aniruddha, Pavan Kalyan, and 2 new GenAI volunteers once access is restored
  • Siddardth: Escalate Shubham's repeated absences to Jeevan; determine whether to reassign issue #37
  • Siddardth: Identify a senior developer to resolve the test branch / dev branch gap blocking issue #58
  • Gaurav: Continue requirements gathering with Rashmi for BA #26; provide ETA at next standup
  • Pradnya: Provide ETA for issue #17 at next standup
  • Prashant: Provide ETA for issue #40 at next standup; contact Rishabh for issue #47 closure comments
  • Kush: Confirm PR status and AWS deployment for issue #11; provide update to Sid
  • Aniruddha: Complete issue #37 getting started task and move to a new priority issue; provide update to Sid by EOD
Meeting - 04/29/2026

Time:

  • 1:00 PM – 2:00 PM PDT

Project Manager's:

  • Siddardth,Giritej

Attendees:

  • Siddardth, Giritej, Prashant, Aniruddha, Kush, Janvi, Linda, Yashwant, Gaurav, SaiVarun, Keerthi, Shashank, Pradnya.

Note: This was a priority task and issue tracking meeting. Multiple team members joined throughout the call to provide updates on their assigned issues.

Progress:

  • Prashant - #issue 47: Discovered the issue was already fully implemented by Rishabh during the 2 weeks Prashant's system was under repair; Rishabh used new architecture with more precise functions; Rishabh has since left the organization after accepting a new job — Prashant to reach out to get his contact and obtain closure comments before closing the issue; yet to select a new priority issue
  • Aniruddha - #issue 37: Still in progress due to interview commitments; expects to complete within 1–2 days this week; blocker resolved — was unable to find "request microservice" option in Monday/Thursday work forms; Siddardth clarified to use "backend request" option instead
  • Kush - #issue 11: Backend implementation for request detail tabs complete; PR raised with CRUD operations — get and post endpoints; assigned to #issue 17 (CRUD functionality) and will begin work immediately; note — Pradnya also assigned to #issue 17 and Kush is redoing the PR the correct way
  • Pradnya - #issue 17: Assigned after the meeting; to coordinate with Kush who is also working on the same issue and redoing the PR correctly
  • Janvi - #issue 26 (BA issue): Active; needs to coordinate with BA team and database team for requirements; to use prod wiki table or BA group for contact; will mentor Gaurav (new team member) on issues 58 and 26
  • Linda - #issue 59 (dashboard APIs): Active; mentoring Saivarun (new team member) on the issue
  • Yashwant - #issue 49: Recently received AWS access and now actively working on the issue; coordinating with HR team.
  • Shashank - #issue 10: Working alongside Yashasvi; considering taking on additional issues
  • Gaurav - #issue 37/58: New team member completing setup; being paired with Janvi for mentoring on issues 58 and 26
  • Saivarun - #issue 59: New team member completing setup; being paired with Linda for mentoring

Challenges/Blockers:

  • Issue 47 cannot be formally closed — Rishabh (implementer) has left the organization; Prashant needs to obtain his contact to get final closure comments for GitHub
  • Aniruddha delayed on issue 37 due to interview commitments; form options confusion resolved during the meeting
  • Multiple team members still awaiting DevSecOps WhatsApp group access — requires HR lead (tejasree) to expedite approval
  • Test branch is critically behind the dev branch — root cause identified as a force-push directly to dev bypassing the workflow; proposed fix is to create a new test branch from current dev (similar to volunteer microservices approach); to be discussed with Rao in Friday scrum
  • Issue 17 has dual assignment (Kush + Pradnya) — Kush is redoing the PR the correct way; coordination required between both to avoid overlap
  • Prashant yet to select a new priority issue

Action Items:

  • Siddardth: Follow up on pending AWS access requests with appropriate teams; share prod wiki table link with team for BA contact information
  • Prashant: Contact Rishabh for issue 47 closure comments and update GitHub; select new priority issue from list (#17, #33, #14, #40, #34, #29, #41) — pending as of meeting
  • Aniruddha: Complete issue 37 setup before Friday scrum call
  • Kush & Pradnya: Coordinate on issue 17; Kush to redo PR correctly; align on task split to avoid overlap
  • All team members awaiting access: Follow up with Keerthi ( Team lead) for DevSecOps WhatsApp group access
  • Janvi: Contact BA team via prod wiki table or BA group for issue 26 requirements; guide Gaurav on issues 58 and 26 over the next week
  • Linda: Work with Shashank on issue 59
  • Yashwant: Coordinate with HR on issue 49 and any new issue selection
  • Shashank: Confirm whether taking on additional issue 64; coordinate with Yashasvi
  • Janvi (ravi): Provide detailed analysis of branching errors to support the test branch resolution discussion with Rao
  • Team: Discuss test branch synchronization issue with Rao in Friday scrum call; proposed solution — create new test branch from current dev, retain old test as backup
  • All available members: Select from priority issues list (#17, #33, #14, #40, #34, #29, #41) and update Siddardth before Friday scrum

Deployment Workflow Clarification (Process Reference)

Clarified during the meeting for Kirthi's question on PR process:

  1. Deploy to AWS and test via API Gateway
  2. Share with frontend team for integration testing
  3. Push to test branch after frontend approval
  4. Write test cases with 90% code coverage
  5. Raise PR to dev branch for review
Meeting - 04/22/2026

Time:

  • 1:00 PM – 2:00 PM PDT

Project Manager's:

  • Siddardth, Giritej

Attendees:

  • Siddardth, Giritej, Janvi, Suraj, Yashwant, Shubham, Pradnya, Linda, Gaurav

Note: Some team members were absent — Siddardth to request updates from absent members via group chat.

Progress:

  • Janvi - #issue 58: Blocked on test/dev branch permissions; working with Suraj to resolve; available for additional work in the meantime — assigned to Task #26 (Rashmi's request)
  • Shubham - #issue 37: Completed environment setup; needs guidance on next steps — to be paired with Pradnya who completed the same issue 3 days ago
  • Pradnya - #issue 37: Completed; assigned to #issue 47 (create enumerations) to work alongside Yashwant; also serving as collaborator and guide for Shubham on issue 37
  • Linda - #issue 59 (API support - get help request): Resolved blockers after Friday's meeting with Rao; working with Ramya for additional support; ETA: Saturday
  • Suraj - #issue 53 (File attachment): Local testing complete; APIs sent to frontend team; waiting on frontend verification; ETA: Next week
  • Yashwant - #issue 50/49: Blocked on AWS DB read/write access; Suraj coordinating with AWS team; advised to complete local testing in the meantime
  • Gaurav - #issue 37: Recently onboarded; pending assignment to a senior developer for pairing

Challenges/Blockers:

  • Janvi blocked on test/dev branch permissions — waiting on Suraj (team lead for both volunteer & backend request teams) to resolve
  • Yashwant cannot proceed with full deployment until AWS DB access is granted; Suraj is coordinating with the AWS team
  • Issue 53 frontend verification pending — Suraj waiting on frontend team response
  • Issue 47 (create enumerations) — Pradnya and Yashwant assigned; progress tracking begins this week
  • Limited senior resources available; no senior dev identified yet to pair with Gaurav
  • Low meeting attendance; several volunteers absent without updates

Action Items:

  • Siddardth: Post meeting summary in group chat and request updates from absent members
  • Siddardth: Identify a senior developer to pair with Gaurav on an existing task
  • Siddardth: Confirm Pradnya–Shubham pairing for issue 37 guidance
  • Suraj: Continue coordinating with AWS team for Yashwant's DB read/write access; attend all internal team meetings going forward
  • Yashwant & Pradnya: Begin work on issue 47 (create enumerations); post ETA on GitHub issue
  • Yashwant: Complete local testing while waiting for AWS DB access
  • Janvi: Resolve test/dev branch permissions with Suraj; continue Task #26 in the meantime
  • Linda: Continue working with Ramya to complete issue 59 by Saturday
  • All: Use group chat for all technical questions to ensure visibility and faster response
  • All: Inactive members to respond with a status update or be removed from the team
Meeting - 04/15/2026

Time:

  • 1:00 PM – 2:00 PM PDT

Project Manager's:

  • Siddardth, GiriTej

Attendees:

  • Siddardth Pathipaka, GiriTej Naidu, Shubham Mendapara, Yashwanth Kumar Chundru, Aniruddha Rajnekar, Linda Sunil, Shashank Reddy

Note: Jahnavi Ravi was unable to attend due to an ongoing interview process; update submitted offline.

Progress:

  • Jahnavi Ravi - #issue 58: Front-end integration complete and deployed on AWS Lambda; only remaining step is raising a PR for code changes; test branch is currently behind the dev branch — needs to sit down with leads to resolve before PR can be raised
  • Shubham Mendapara - #issue 37: Had GitHub access issues due to accepting the org invite with a non-primary email; re-submitted access form with primary GitHub ID during the meeting; access resolved — assigned to issue 37 (Getting Started)
  • Yashwanth Kumar Chundru - #issue 49: Development complete and working in local environment; facing deployment issues on AWS; front-end integration with Rashmi pending deployment resolution; to reach out to Suraj for assistance and leave an ETA comment on the GitHub issue
  • Aniruddha Rajnekar - #issue 37: AWS access form reply had gone to spam; re-submitted form; received GitHub org access during the call (granted by Aishwarya Zadaw); to complete local environment setup — assigned to issue 37 (Getting Started)
  • Linda Sunil - #issue 59: Blocker — was coordinating with Hema for guidance, who has since left the organization; directed to reach out to senior developers (Suraj and others mentioned by Rao) for continued support
  • Shashank Reddy - #issue 10: Had submitted AWS access form twice (Apr 14 and Apr 15) without response; access resolved after meeting — to begin work on issue 10, coordinate with Yashasvi, and post ETA on GitHub

Challenges/Blockers:

  • Jahnavi's PR for issue 58 is blocked — test branch is behind the dev branch; requires a sync with leads to fix before PR can be raised
  • Shubham's GitHub invite was accepted under a non-primary email, making his username invisible in the org — resolved by re-submitting with the correct primary ID
  • Aniruddha's initial AWS access email went directly to spam; delayed onboarding by several weeks — resolved during the call
  • Shashank submitted the AWS access form twice with no response prior to the meeting — access expedited and resolved post-meeting
  • Yashwanth's code is working locally but failing on AWS deployment for issue 49; Suraj to assist with resolution
  • Linda's issue 59 point of contact (Hema) has left the organization; needs reassignment of support contact

Action Items:

  • Siddardth: Schedule a sync with Jahnavi and leads to resolve test branch being behind dev so she can raise her PR for issue 58
  • Siddardth: Coordinate with HR/Aishwarya to expedite remaining access requests; follow up with Shubham via WhatsApp once primary GitHub ID is confirmed
  • Jahnavi: Raise PR for issue 58 once test/dev branch discrepancy is resolved with leads
  • Shubham: Complete issue 37 (Getting Started) environment setup now that access is confirmed
  • Aniruddha: Complete local project setup for issue 37 and notify the group when done
  • Shashank: Begin work on issue 10 now that AWS access is confirmed; coordinate with Yashasvi and post ETA on the GitHub issue
  • Yashwanth: Reach out to Suraj for help resolving AWS deployment issues for issue 49; comment ETA on GitHub issue once resolved; coordinate with Rashmi for front-end integration
  • Linda: Reach out to Suraj or other senior developers (per Rao's guidance) for unblocking issue 59
Meeting - 04/08/2026

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Siddardth, GiriTej

Attendees:

  • Siddardth Pathipaka, GiriTej Naidu, Rishab Muzhangathu, Sudharshan Madhavan, Suraj Reddy, Saivarun Paruchuri (joined, could not be heard)

Progress:

  • Sudharshan - #issue 37: Completed getting started issue; set up project in local environment; now ready to move to feature work and assigned to assist Rishab with step functions
  • Rishab - Step Functions: Returned after a 2-week absence; working on identifying all Lambda functions required for the step function workflow (Start → Created → Matching Volunteers); clarified that SQS/SNS integration (issue #47) is a priority for relaying request state updates to the front end; assigned Sudharshan as collaborator; to sync with Usha on current priority issues for the 1.0 MVP release
  • Suraj - #issue 53: File attachment implementation ongoing; built on top of Janvi's completed work; no blockers; expects to complete by next week; will coordinate with Rashmi for front-end integration once done

Challenges/Blockers:

  • No meeting reminder was sent, resulting in low developer turnout
  • Saivarun joined the call but was not audible and could not provide an update
  • Rishab has been absent for 2 weeks and is not on Slack; needs to re-sync with Usha on updated priority issues and current state of the 1.0 MVP scope

Action Items:

  • Siddardth: Follow up with Usha on priority issues for 1.0 MVP release and communicate to the team
  • Rishab: Text Usha directly to get updated priority list and current issue ownership; re-join Slack
  • Sudharshan: Message Rishab on Slack to schedule a sync on step functions and Lambda function identification
  • Rishab & Sudharshan: Begin working together on step function workflow — identify all Lambda functions needed up to the matching volunteer stage, starting with SQS/SNS integration (issue #47)
  • Suraj: Complete file attachment feature (#issue 53) and coordinate with Rashmi for front-end integration
Meeting - 04/01/2026

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Siddardth, Usha, GiriTej

Attendees:

  • Siddardth Pathipaka, Ushasree Perakalapudi, GiriTej Naidu, Aniruddha, Saivarun Paruchuri, Janvi, Suraj, Yashwant, Sudharshan, Shubham, Gaurav, Shasank

Progress:

  • Gaurav - #issue 37: Recently joined; was traveling last week, getting started today
  • Janvi - #issue 58: Create help request API implemented and hosted on AWS Lambda for front-end integration; working with Rashmi on additional fields before raising PR to dev branch
  • Suraj - #issue 53: Started file attachment implementation building on Janvi's prior work; updates to be posted in group
  • Yashwant - #issue 49: Additional fields code complete and tested; pending front-end integration with Rashmi; to push code to dev branch with Janvi's assistance
  • Yashwant - #issue 64: BA task; required details received from BA team today, beginning to look into it
  • Sudharshan - #issue 37: New joiner; has both GitHub and AWS access; assigned to issue 37 to begin onboarding
  • Shubham - #issue 37: New joiner; GitHub invite received but needs to switch primary email before accepting; to be assigned to issue 37 once confirmed
  • Saivarun - #issue 37: GitHub access delayed; resubmitted access form (specifying "request" repo only, not "request backend") after coordination with Siddardth and Sharanya
  • Aniruddha - #issue 37: Submitted AWS access form; to be assigned to issue 37 after GitHub organization access is granted
  • Shasank - #issue 37: Pending AWS access; will be assigned to issue 37 upon confirmation

Challenges/Blockers:

  • Saivarun did not receive GitHub access despite Sharanya indicating it was granted; resolved by resubmitting the access form specifying "request" repository only — Siddardth to notify Sharanya once resubmission is confirmed
  • Multiple new joiners (Aniruddha, Saivarun, Shasank) still awaiting AWS access approval
  • Yashwant unsure how to push code to dev branch; Sharik unavailable — Janvi agreed to assist; Yashwant to schedule a sync with Janvi
  • Janvi holding PR to dev branch until front-end integration with Rashmi is finalized
  • Shubham needs to switch primary email before accepting GitHub organization invite
  • GitHub repositories are public for viewing, but organization membership is required for issue assignments

Action Items:

  • Siddardth: Coordinate with Sharanya to confirm Saivarun's GitHub access after form resubmission
  • Janvi: Assist Yashwant with dev branch deployment process for issue 49
  • Janvi: Continue front-end integration with Rashmi for issue 58 until demo-ready before raising PR to dev branch
  • Yashwant: Push code to dev branch for issue 49; coordinate with Rashmi on front-end integration; begin work on BA issue 64
  • Suraj: Complete file attachment feature (issue 53) and post updates in group
  • Gaurav, Sudharshan: Complete issue 37 environment setup
  • Aniruddha, Shubham, Shasank: Complete issue 37 after access confirmation
  • Siddardth: Post meeting minutes in project documentation
Meeting - 03/25/2026

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Usha, Giritej, Siddardth

Attendees:

  • Usha,Giritej Naidu, Siddardth Pathipaka, Saivarun Paruchuri, Yashwanth Kumar Chunduri, Jahnavi Ravi, Prashant Salunke, Shariq Ahmed, Kousalya, Linda Sunil, Chandrateja Kurapati, Harshawardhan TV, Sai Nikhil Reddy Kunduri

Progress:

  • Chandrateja Kurapati- finished writing the code for get help req API support needs to push code to dev branch
  • Prashant Salunke- #issue 47 Reimplementing the function in the control and service layer. Database part is resolved. Can finish the issue and close it by the end of the week.
  • Yashwanth Kumar Chunduri- #issue49 Implemented code. Waiting on create help req with additional help req to be implemented to test code. Assigned new issue BA issue #64
  • Linda Sunil- Has to still start working on code implementation of issue #59
  • Saivarun Paruchuri- Waiting on GitHub access will start working on getting started tasks #37
  • Kousalya -Waiting on GitHub access will start working on getting started tasks #37
  • Harshawardhan TV- New volunteer submitted GitHub access
  • Sai Nikhil Reddy Kunduri- New volunteer submitted GitHub access
  • Siddardth Pathipaka- Joined as new project manager

Challenges/Blockers:

  • Discussed in the meeting and solved by Shariq
Meeting - 03/11/2026

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Usha, Giritej

Attendees:

  • Saivarun paruchuri, Yashwanth Kumar Chunduri, Jahnavi Ravi, Prashant Salunke, Giritej Naidu

Progress:

  • Prashant Salunke- #issue 47 Implemented API's. Reach out to Pallavi for database support
  • Yashwanth Kumar Chunduri- #issue49 Implemented code. Waiting on some support/implementation from frontend team to clarify a new things. Will push the code to test branch once that is done
  • Jahnavi Ravi- Part of volunteer team, helping out the request team to provide API support for the Get Help request and additional fiealds issue #57, #58
  • Saivarun Paruchuri- New volunteer joined Saayam yesterday. Waiting on GitHub access
  • Giritej- Joined as a new project manager.

Challenges/Blockers:

  • Discussed in the meeeting
Meeting - 03/04/2026

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Usha

Attendees:

  • Usha, Linda Sunil, Yashwanth Kumar Chunduri, Hemalatha Shanmugham, Prashant Salunke

Progress:

  • Yashwanth- Working on issue #47 Running the code.
  • Hemalatha Shanmugham- Assigned BA #issue 26 , Providing API Support for Create help request and additional fields req issue 57, 58
  • Linda Sunil- Part of Volunteer team, doing initial setup and getting started #37
  • Prashant Salunke- working on issue 47

Challenges/Blockers:

  • Discussed in the meeeting
Meeting - 02/11/2026

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Usha

Attendees:

  • Usha, Suraj Alluri, Yashwanth Kumar Chunduri, Hemalatha Shanmugham, Prashant Salunke

Progress:

  • Yashwanth- Working on Getting started and initial task setup. Running the code.
  • Hemalatha Shanmugham- Assigned BA #issue 26
  • Suraj Alluri-Working on issue 53. blockers and challenges cleared by Rao and exec team
  • Prashant Salunke- issue 47 Verifying API's for req status and req type

Challenges/Blockers:

  • Discussed in the meeting by Suraj
Meeting - 02/04/2026

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Usha

Attendees:

  • Usha, Yashasvi Musku, Rishab Muzhangathu, Prashant Salunke, Anu, Gopi Kotadiya

Progress:

  • Prashant Salunke- #issue 47 Enable e-num based entities. Verified the code base, exposing the missing gate API's.
  • Gopi Kotadiya- New volunteer, Joined in Jan 1st week, Part of req team/ volunteer team issues with project set up- getting help from Yashasvi
  • Yashasvi Musku- #issue 10 implementing notification service. Done with SQS integration. Working on SNS topic. Neeraj is taking a break for a month from Saayam
  • Anu- Part of Gen AI joining req microservices to take up task. will work on initial task issue37 getting started
  • Rishab - Step function diagram, working on task assigned by Rao

Challenges/Blockers:

  • Discussed in the meeting
Meeting - 01/21/2026

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Usha

Attendees:

  • Usha, Hemalatha Shanmugam, Rishab Muzhangathu, Neeraj Ghate, Prashant Salunke

Progress:

  • Rishab – Working on issue 1;discussing blockers with exec team and in conversation with Rao about Step function diagram
  • Prashant – Working on the issue 47 Create Enumerations for Request Instance ; assigned the task today and will start working on it
  • Neeraj Ghate - Working on issue 10 Send Asynchronous Notifications to Users SQS created by Rishab on Dec 5th. Will work on creating a payload
  • Hemalatha Shanmugam- New volunteer just got github and AWS access. Is working on the initial setup and task. Will get help from Rishab to get started working on the first task

Challenges/Blockers:

  • Discussed in the meeting
Meeting - 01/14/2026

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Ushasree

Attendees:

  • Usha, No attendance from developers or leads

Progress:

  • N/A

Challenges/Blockers:

  • N/A
Meeting - 01/07/2026

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Ushasree

Attendees:

  • Ushasree, Rishab Muzhangathu, Suraj Alluri, Vanitha Sannaobappa

Topics Discussed:

Progress:

  • Rishab – Working on Issue 10 and issue 1; have some blockers with step function diagram implementation, waiting to discuss with exec team and Rao
  • Suraj Alluri – Working on the issue 53 Create Help Request page ; waiting on test team to test code in the volunteer req team to implement the same code
  • Vanitha - New volunteer onboarding is completing initial task

Challenges/Blockers:

  • Discussed in the team meeting
Meeting - 12/10/2025

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Ushasree

Attendees:

  • Rao, Ushasree,Suraj Reddy Alluri, Neeraj Ghate, Ayan Gora, Rishab Muzhangathu, Yashasvi Musku, Sri Charan Balankundhi, Prashant Salunke, Ranjitha*

Topics Discussed:

Progress:

  • Suraj Alluri – Working on the Create Help Request page; needs access to the application.properties file.
  • Rishab Muzhangathu – Working on Issue 10 (asynchronous notifications) and inclusion of Step Functions.
  • Neeraj Ghate – Working on Issue 10.
  • Yashasvi Musku – Working on Issue 10 and collaborating with Rishab and Neeraj.
  • Sri Charan Balakundhi
  • Ayan Ghate – Working on Issue 49 (Enable Edit Functionality for Help Request Details Page). Code completed; waiting on confirmation regarding additional help tabs. Code sent to testing.
  • Prashant Salunke – Not actively working on an issue yet; waiting to connect with another volunteer for support. If not possible, will self-assign a new task from the repo.
  • Ranjitha Narayana* - Table is created by database team will verify the code changes with the latest code

Challenges/Blockers:

  • Discussed in today’s meeting and resolved by Rao.
Meeting - 12/03/2025

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Bhavana, Ushasree

Attendees:

  • Rao, bhavana, ushasree, Rishab Muzhangathu, Ayan, Prashant Salunke, Ranjitha, Sahana, Yashasvi

Topics Discussed:

Progress:

  • Ayan- working on the request detail api and already created an api checking the functionality
  • Rishab & Yashasvi – Working on Issue 10; working with Neeraj, have some challenges with volunteer team checking with volunteer team
  • *Ranjitha - working on the issue 17, waiting on the db team to create request_comment table in database
  • Prashant - Assigned new task by Rao.

Challenges/Blockers:

  • Discussed in today’s meeting and resolved by Rao.
Meeting - 11/19/2025

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Ushasree

Attendees:

  • Rao, Fara Fatima, Rishab Muzhangathu, Vanitha Sannaobappa, Span Shah, Chandra tej, Prashant Salunke

Topics Discussed:

Progress:

  • Vanitha & Sapan- New volunteers waiting to be assigned tasks
  • Rishab – Working on Issue 10; working with Neeraj, waiting on AWS access likely to complete by the end of the week.
  • Issue 17- Waiting on database team to create database to create a new table
  • Prashant - Assigned new task by Rao.

Challenges/Blockers:

  • Discussed in today’s meeting and resolved by Rao.
Meeting - 11/12/2025

Time:

  • 1:00 PM – 2:00 PM PST

Project Manager's:

  • Bhavana, Sriya Avirneni, Usha Sree

Attendees:

  • Rao, Yashasvi Reddy, Neeraj Ghate, Rishab, Anurag Choubey, Kavana Manvi, Sriya Avirneni, Bhavana, Ushasree, Ranjitha Narayana, Ayan Gorai, Fara Fatima, Satish Mallikarjun, Madhuri Reddy, Manojna Angara, Siddhartha, Chandra Teja Kurapati

Topics Discussed:

Progress:

  • Rishab – Working on Issue 10 and collaborating with Yashasvi and Neeraj.
  • Neeraj – Working on Issue 10.
  • Yashasvi – Collaborating with Neeraj and Rishab (Send Notification Services).
  • Anurag Choubey – Trying to run a dev branch locally. Working on Issue 22. Adding unit tests and understanding the code.
  • Kavana Manvi – New volunteer; working in the healthcare category and adding subcategories.
  • Ranjitha Narayana – Working on the comments tab; reached out to the Database team to create a table for comments.
  • Ayan Gorai – Working on details; faced DB issues and resolved them. Created DB tables and needs to create pipelines.
  • Fara Fatima – Issue 41; creating help request.
  • Madhuri Reddy – Issue 46; figured out implementation logic and will finish it by next week.
  • Manojna Angara – Working on Issue 48 and also supporting other security-related issues.
  • Siddhartha – New volunteer; will pick an issue this week and assist Ayan.
  • Chandra Teja Kurapati - Working on issue 41. Completed "Create Request" story.

Challenges/Blockers:

  • Discussed in today’s meeting and resolved by Rao.
Meeting - 11/05/2025

Time:

  • 1:00 PM – 2:20 PM PST

Meeting Lead:

  • Usha, Sriya Avirneni

Attendees:

  • Rao, Yashasvi Reddy, Neeraj Ghate, Rishab

Topics Discussed:

  • Progress:

Rishab – Working on issue 10 and collaborating with Yashasvi and Neeraj.

Neeraj – Working on issue 10.

Yashasvi – Collaborating with Neeraj and Rishab (Send Notification Services).

  • Challenges/Blockers:

Discussed in today’s meeting and resolved by Rao.

Meeting - 10/22/2025

Time:

  • 1 PM - 1:30 PM (30 minutes)

Meeting Lead:

  • Bhavana Kuppadapu

Attendees:

  • Shariq, Fara, Chandra, Manojna, sneha, Ranjitha, Ayan

Topics Discussed:

  • Progress:

Chandra - working on issue 41.

Sneha - is new and have not been assigned a task yet.

Ranjitha - working on the crud operations issue 17.

Ayan - have been assigned to issue 17, but assigned newly to the edit request page details page issue 49.

Shariq and fara - worked on the issue 47,done with the request enum creation.

  • Challenges/Blockers: None
Meeting - 08/28/2025

Time:

  • 11 AM - 11:30 AM (30 minutes)

Meeting Lead:

  • Bhavana Kuppadapu, Yash Bhavsar

Attendees:

  • Ranjitha Narayana, Ayan

Topics Discussed:

  • Progress: Ranjitha completed her setup and will connect with Team lead and will post the updates regarding her ticket. Ayan completed a project under Database team and is looking for a new ticket to work on.
  • Challenges/Blockers: None
Meeting - 09/04/2025

Time:

  • 3:00 PM - 4:00 PM (60 minutes)

Meeting Lead:

  • Bhavana Kuppadapu, Yash Bhavsar, Rao

Attendees:

  • Shariq, Fatima, Pallavi Chitrada

Topics Discussed:

  • Progress: Shariq made changes in the new API and discussed it with Rao. Rao suggested documenting his classes in Java for future explanation about the classes. Pallavi joined from the database team since the Bkend team needed some assistance for integration. Fatima and Shariq are working on issue#42.
  • Challenges/Blockers: Unable to connect the database with the API.
Meeting - 10/01/2025

Time:

  • 1 PM - 1:30 PM (30 minutes)

Meeting Lead:

  • Sriya Avirneni, Yash Bhavsar

Attendees:

  • Neeraj, Shariq, Fara, Chandra, Satish, Rishab, Ranjitha, Poojan, Ayan, Shams.

Topics Discussed:

  • Progress: Neeraj – Currently working on Issue #10.

Shariq and Fara – Collaborating with the Database team; once the database work is complete, they will move on to the API and enums.

Chandra – Assigned to Issue #41, working with Pallavi. Will begin once Pallavi provides the necessary updates.

Satish – Working on Issue #40 with Madhuri. They encountered a database setup issue and are coordinating with a senior developer to resolve it.

Rishab – Newly onboarded and currently working on the onboarding issue ticket.

Ranjitha – Self-assigned Issue #17.

Ayan – Requested GitHub access to collaborate with Ranjitha on Issue #17.

  • Challenges/Blockers: None

Clone this wiki locally