Date & Time: 10/28/2025 | 01:00 PM EST

Attendees: Rao Bhethanabotla, Priyanka Tiwari, Sudhisha Palle, Achyuth Kumar Miryala, Anuhya Mandava, Arjun Rai, Astha Sharma, Bhargav Mylavarapu, Divyaraj Singh Nirwan, Jemin Miyani, Kaki Bhavana Shree, Likhith Kumar Vuchooru, Pradumna Patki, Priyanka M, Rithika Mary, Shambhavi Satish Patil, Sriya Avirneni, Teja Vadapalli, Ushasree Perakalapudi, Vedant Brahmbhatt, Saket Thorat

Topics Discussed:

• Marketing Collaboration:

  • Need to identify top 5–6 collaborator organizations per help category and assign volunteers accordingly.
  • Marketing efforts to follow a structured CRM approach — tracking contact attempts, responses, and follow-ups in GitHub issues or internal trackers.
  • Example organizations shared: Calm, Healthy, Happy Org and Shankara Eye Foundation (Gift of Vision) to be added as collaborators.
  • Marketing volunteers to work jointly with product managers when reaching out externally.

• Official Email Access:

  • Team reminded to use @saayamforall.org emails for outreach.
  • Rao to share Nettigritty webmail access details with the exec team.
  • Volunteers can request official IDs through the executive group for verified communication.

• Finance & Cross-Team Collaboration:

  • Finance members to be invited to PM/BA meetings since every use case involves cost implications.
  • Non-technical volunteers (e.g., from finance, robotics) encouraged to create new help categories or extend existing ones aligned with their expertise.

• Product Documentation:

  • Healthcare and well-being use case reviewed as a model example; other categories to follow similar structure.
  • Product managers must ensure numbering consistency (main category → subcategory → additional fields).
  • Labels in UI and wiki to match exactly (e.g., “Medical Consultation” = 5.1).
  • English labels finalized first; front-end will translate dynamically per locale.
  • Drop-down options must follow uniform grammar — all nouns or all verbs.

• Architecture Clarification:

  • System relies on numeric constants (e.g., 5.1, 5.1A) for backend mapping; labels vary by language.
  • Additional fields (A, B, C) denote dynamic UI prompts triggered during form completion.
  • Changes to numbering must stop once values are committed to the database (“frozen” constants).

• Follow-Up Actions:

  • Product Management & BA Teams:
    • Review all six use cases for numbering and field consistency.
    • Remove unused “Step” columns and finalize additional fields (A, B, C format).
  • Priyanka & Likhith: Host follow-up meeting at 3:00 PM EST for cross-team correction session.
  • Marketing: Begin collaborator outreach with confirmed organizations; use official emails.
  • Rao: Provide webmail access link to executive group.

Date & Time: 10/22/2025 | 01:00 PM EST

Attendees: Rao Bhethanabotla, Aaryan Wagh, Vidhi Upadhyay, Harsh, Pallavi Chitrada, Anmol Bhatta, Mary Ritika, Sharanya Gowda, Priyanka Tiwari, Prathamesh , LikithKumar, Bhargav Mylavarapu

Topics Discussed:

• Business model & actors: Monetization via ads and commissions; Defined actors: Beneficiaries (requesters), Organizations (explicitly includes for-profit and non-profit — replace “voluntary organization” everywhere), Volunteers, Donors.
• Razorpay / Payments UI: Razorpay demo was simulated. Logo missing; alignment problems vs PayPal/Stripe; Recommendation: center-align single-row payment options and ensure consistent logos and text casing (e.g., “Make a Donation”).
• Error message / code framework: Standardize information/warning/error codes (goal: globally recognizable codes like “SAAYAM-200”); Codes must be constant across 12 supported languages; messages localized; Maintain a wiki table of codes so search engines and users can find them.
• Localization / Translators: Need native speakers to produce colloquial, user-friendly translations rather than literal Google Translate results; Create and surface a translators group (Saayam Translators) in product pages and resource bundles.
• Authentication & Security: Cognito used for auth; educate users about weak passwords and dark web risks; Emphasize security hygiene and monitoring.
• Architecture & Performance: Dashboard data rendered from API Gateway → microservices (request, volunteer, etc.); Use ElastiCache for enumerations/caching to avoid hitting DB for reads; Microservices must have separate DB credentials to monitor read/write capacity per service.
• Delegation & Task Management: Assign leads for categories (Food & Essentials, Clothing Assistance, etc.); Use GitHub for task tracking and assignees; Rao emphasized delegation as a leadership skill.
• Quality & Reliability: Maintain high UX standards and disaster-recovery readiness (Amazon outage example).
• Rao’s LinkedIn/analytics visibility: project will be watched by industry peers — quality matters.

Action Items:

• Replace the term “voluntary organization” with “organization” everywhere in the UI, documentation, and presentations.
• Rename AWS AppConfig to a more suitable name such as parameters form or equivalent configuration method.
• Create a central error code table in the web app wiki, including code, message type, English message, and example usage.
• Display error numbers/codes in the UI for all information, warning, and error messages.
• Maintain consistent sign-in/login terminology across all navigation links and page headers.
• Add Razorpay logo and ensure it is properly aligned and visually consistent with PayPal and Stripe options.
• Center-align the Razorpay button when it’s the only payment option on the page.
• Correct text casing on payment-related headings (e.g., “Make a Donation”).
• Conduct a UI visual audit to ensure proper alignment, spacing, capitalization, and consistency across all pages.
• Create a translators group and list translator names on product pages and resource bundles for all supported languages.
• Recruit native speakers for translations to ensure colloquial, user-friendly language.
• Add translator ownership and supported languages to the product wiki.
• Use ElastiCache for caching enumerations to reduce database read load.
• Ensure each microservice uses separate database credentials to monitor read/write capacity.
• Implement monitoring for database read and write usage across microservices.
• Ensure enumerations and status values are exposed correctly via the API Gateway and mapped to localized UI text.
• Standardize six request statuses (Created, Matching Volunteer, Managed, Resolved, Cancelled, Deleted) and localize them.
• Assign category leads (e.g., Food & Essentials, Clothing Assistance, etc.) and document ownership.
• Track all project tasks and deliverables through GitHub issues with assigned owners and due dates.
• Include translator details, error code reference, and supported language list in the project wiki.
• Document naming conventions for all code identifiers (e.g., SAAYAM-200 format).
• Add a note in the wiki clarifying that organizations can be both for-profit and non-profit.
• Ensure UX consistency for icons and message display (info, warning, error).
• Conduct a full product demo walkthrough before next review session.
• Maintain high-quality standards for UI and resilience, emphasizing production-readiness and recovery planning.
• Ensure analytics and external visibility are properly tracked (LinkedIn, corporate observers).

Date & Time: 10/21/2025 | 01:00 PM EST

Attendees: Rao Bhethanabotla, Saket Thorat, Bhargav Mylavarapu, Poulomi Dey, Mary Rithika Reddy Gade, Parth Deshmukh, Nikhil Rajavarthanan, Divyaraj Singh Nirwan, Akash Chatla, Vaishnavi Mallagundla, Ameena Khan, Astha Sharma, Priyanka Tiwari, Shubham Gajendra Raut, Harsh (Web Dev), Pranai, Patiolla Akhila, and Charles Revanth

Topics Discussed:

• Importance of maintaining weekly timesheets for documenting active work and compliance purposes.
• Razorpay integration update — progress on backend setup; API key access requires verified business account. Rashmi and Srija identified as prior contributors for reference.
• Volunteers advised to complete one task at a time before switching between projects or teams.
• Rao explained DevSecOps setup — AWS services (Parameter Store, Elastic Cache) and use of Pulumi for infrastructure automation.
• Discussion on GitHub Actions for CI/CD in place of Jenkins for open-source pipelines.
• Overview of Generative AI usage — system currently consumes LLM responses (e.g., Grok) for “More Info” requests; no in-house model hosting.

Action Items:

• Volunteers: Update and submit weekly timesheets.
• Bhargav: Continue Razorpay integration; coordinate with Rashmi for API setup.
• DevSecOps Team: Maintain CI/CD via GitHub Actions and Pulumi setup.
• Interested volunteers (Poulomi, Rithika): Align with Gen-AI or DevSecOps teams as per assigned tasks.

Date & Time: 10/14/2025 | 01:00 PM EST

Attendees: Rao Bhethanabotla, Aakash Bhanushali, Abhay Patil, Abhiroop Somisetty, Akshay Bhagwat, Bharghav Mylavarapu, Divyaraj Singh Nirwan, Foram Raiyani, Hari Bolla, Kulnal Gulati, Lalith Kumar Dabilpuram, Monika Dhukia, Nikhil Rajavarthanan, Priyanka Tiwari, Parth Deshmukh, Pavani, Pranai, Rithvik Mysore Narasimhamurthy, Shyami Govind, Snidhi Reddy Gudoor, Veda Sahaja Bandi, Virat Sharma, and Saket Thorat

Topics Discussed:

• Volunteer Introductions: New volunteers from data analytics, HR, and marketing shared brief intros; orientation on GitHub wiki structure and project expectations.
• Naming & Professional Identity: Discussion on owning full legal names professionally; Rao advised keeping proper Zoom/LinkedIn display names and avoiding abbreviations.
• Resume & ATS Awareness: Explained how Applicant Tracking Systems (ATS) scan resumes using conditional logic; importance of clear formatting, keyword optimization, and truthful visa information.
• Open Source Orientation: Walkthrough of GitHub repositories (docs, architecture, webapp, volunteer-service); all contributors must understand wiki navigation and documentation editing.
• Programmatic Roles:
  • Frontend – React & React Native.
  • Backend – Java (requests/volunteer) and Python (communications, data, ML).
  • Database – Aurora PostgreSQL.
  • Cloud Services – AWS Cognito, API Gateway, S3, and DevSecOps setup.
  • Goal: MVP 1.0 release by Dec 31, 2025.
• Non-Programmatic Roles: Overview of Product Managers, Business Analysts, Project Managers, and Marketing/Finance teams. Each BA/PM acts as an end-user representative responsible for usability and requirement clarity.
• UI/UX Alignment: Example shared on Sign In → Login mismatch; PMs/BAs to verify page headers and link names for user consistency.
• Language & Accessibility: Application now supports 12 languages, including Arabic and Urdu. Introduced accessibility standards — Material Design, WCAG compliance, and acronyms I18N, L10N, A11Y.
• Agile Frameworks: Explained Agile as “iterative development”; difference between Scrum (sprint-based) and Kanban (continuous flow). Saayam currently follows the Kanban approach.
• Marketing & Outreach: Volunteers encouraged to join marketing team for social media presence, donor outreach, and fundraising efforts.
• Career Advice: Rao emphasized practical learning, certifications (AWS/Azure/GCP), and resume improvements for employability.

Action Items:

• Product Managers/BAs: Verify UI labels, create/update page ownership table, and maintain consistency in link-to-page mapping.
• Dev/Backend: Finalize volunteer and request microservices; maintain AWS configurations.
• QA/UX: Ensure accessibility compliance (color contrast, ARIA labels, mandatory fields).
• Localization Leads: Add Arabic and Urdu entries, assign native language reviewers.
• All Volunteers: Register on the dev app, test features, and update respective wiki pages.

Date & Time: 09/30/2025 | 01:00 PM EST

Attendees: Rao Bhethanabotla, Pradumna Patki, Abhay Suresh Patil, Allen Mathews, Ashirwad Srivastava, Divyaraj Singh Nirwan, Gopal Raj Suresh Dummugudupu, Nikhil Rajavarthanan, Panth Patel, Prashanna Prasai, Pruthvish Reddy, Rishab Muzhangathu, Rithvik M N, Sparsha, Subhash, Sylvester Rodrigues, Saket Thorat

Topics Discussed:

• MVP Planning: PMs to document key pages and responsible owners for 1.0 and 1.2 releases.
• Page Ownership Table: Each page must list PM, BA, QA, UX, and Dev contacts; reference layout from DevSecOps Dashboard.
• UI/UX Consistency: Uniform error, warning, and info message formats required; add “All fields mandatory” note on signup.
• Mobile & QA: Majority of users on mobile; QA to test Android/iOS across major browsers.
• Localization: MVP supports 10 languages; identify native speakers per language for UI validation. Explore adding Arabic and Urdu later.
• GDPR Compliance: Ensure PII handling meets EU standards; data hosted in AWS Ireland (EU) and Virginia (US).
• AI Tools: Encouraged use of Gemini and Meta AI for drafting, communication, and documentation.

Action Items:

• PMs/BAs: Build MVP Page Ownership Table; finalize message formats per page.
• QA: Create mobile test matrix and multilingual checks.
• UX: Add mandatory field note and align message display.
• Localization Leads: Assign native speakers for each supported language.
• DevSecOps: Align wiki dashboard visuals with DevSecOps template.

Date & Time: 09/23/2025 | 01:00 PM EST

Attendees: Rao Bhethanabotla, Akshay Bhagwat, Divyaraj Singh Nirwan, Likhith Kumar Vuchooru, Nikhil Rajavarthanan, Raj (iPhone), S Nikita, Subhash, Sudhisha Palle, Saket Thorat

Topics Discussed:

• Social Media & Credentials: Need to maintain official account URLs in the wiki; credentials to be managed securely by designated leads. Usernames/passwords must not be posted in shared docs.
• Digital ID Cards: Reviewed Pranitha’s draft. Suggestions: include organization mottos, ensure company name is visible, and keep design one-sided for digital use. Cards to be distributed in PDF format, with future option to explore QR/NFC sharing at conferences. Meghana may need one for IIT conference.
• Volunteer Promotion Flow: Four-step wizard (terms acceptance, ID upload, skills, availability). Need for a volunteer table to track step-by-step progress and allow users to resume. Verification required before final promotion; HR team or third-party service to validate IDs.
• Database Design: Separate volunteer table preferred for efficiency. Option to use triggers for location updates and to track journey status. Volunteers promoted only after HR verification.
• Location Tracking: Volunteers’ locations to be updated every 5 minutes to match with in-person requests. User login locations may also be tracked for fraud detection (e.g., multiple logins from different countries/devices).
• Generative AI: Team applying LLMs to classify help requests and enrich dashboards. Example: predicting “food assistance” when user writes “vegetarian food.” Also integrating with Grok for request detail enrichment.
• UI/UX Consistency: Inconsistencies identified (e.g., signup collects phone + email, but login allows email only). Need consistent error/warning/information formats and icons across all pages.

Action Items:

• Marketing/Design: Finalize digital ID card template with mottos, company name, and QR option.
• Product Managers/BAs:
  • Review and document volunteer wizard requirements clearly.
  • Standardize field usage and error/warning message formats across pages.
• Dev/DB Team:
  • Implement volunteer table to track promotion journey.
  • Configure location tracking for volunteers (5-minute frequency).
• HR Team: Verify uploaded IDs before promoting volunteers.
• Generative AI Team: Refine categorization model and integrate external data enrichment.

Date & Time: 09/16/2025 | 1:30 PM PST

Attendees: Rao Bhethanabotla, Akshay Bhagwat, Niharthi Muddada, Likhith Kumar Vuchooru, Nikhil Rajavarthanan, Saket Thorat, Shreya (Business Analyst).

Topics Discussed:

• Importance of documenting in GitHub wiki pages over Google Docs for accessibility and security.
• Roles clarified between Product Managers and Business Analysts; product managers represent end-users, while BAs ensure feature completion internally.
• Detailed walkthrough of login page requirements: Product Managers to define requirements, UX team to design mockups, frontend to implement, backend with AWS Cognito for authentication.
• Identified missing features (cancel button, consistency in UI across pages, breadcrumb navigation, submit/cancel order uniformity).
• Discussion on user experience consistency: importance of uniform UI elements across the app.
• Review of Food & Essentials use case: hierarchical categories, need for clear subcategories (up to 5–6 levels).
• Emphasis on clear, unambiguous requirement writing to avoid confusion (example: food assistance should specify cooked/uncooked, in-person/remote).
• Importance of product managers stepping into the end-user’s shoes, ensuring clarity and usability in requirements.
• Collaboration strategy: Marketing and Data Engineering to jointly work on Food Assistance use case.
• Marketing concern on outreach: difficulty finding direct email contacts vs. phone calls; suggestion to use official Saayam email IDs for credibility.
• Action to leverage MetaEA tool for quick identification of potential collaborators (e.g., Second Harvest, Martha’s Kitchen).

Action Items:

• Akshay & Niharthi to update and align use case documentation format and template by Thursday’s Product Managers meeting.
• Product Managers to define additional fields (e.g., dietary restrictions) using lists/dropdowns in wiki pages.
• Marketing to continue outreach to collaborators using lists (received from Aryan & Manoj) and document in tracker.
• DevSecOps team to provide Saayam official email IDs for outreach.
• Marketing & Data Engineering teams to coordinate on Food Assistance collaborator outreach.
• Product Managers and Business Analysts to review and standardize requirement formats across all categories.

Date & Time: 09/03/2025 | 10:00 AM EST

Action Items

Discussion Points & Action Items

• When a user logs in, the system should highlight pending notifications that the user has not read yet.

• Implement end-to-end integration for profile picture handling including path check and storage.

• Before creating a help request, the system should validate if the user’s profile contains a complete address (Street, State, ZIP, etc.).

• If the address is missing/invalid, redirect the user to the Personal Information (Edit Mode) page with an indication that the address needs to be updated.

Date & Time: 08/27/2025 | 10:00 AM EST

Action Items

• Owner: Rashmi & Mobile App Team
• Action: Add AdMap on all pages of the mobile app. Include one ad at the bottom and one as a screen blocker, similar to the website.
• Next Step: Check with Google for the required process related to advertisements before the release of the smartphone application (AdMob integration).

• Owner: Rashmi
• Action: Update the About the Team page. Add new executives and clean up existing pictures for 1.0 MVP.

• Owner: Rashmi
• Action: Change the error code range to reassign more codes for both Mobile App and Web App. Ensure every message has a unique error code.

• Owner: Rashmi
• Action: Implement a resource bundle to show translated error messages to end users.

• Owner: Anmol & Rashmi
• Action: Pull scripts for repeatable tasks to ensure consistency across environments.

• Owner: Anmol & Rashmi
• Action: Research and validate security aspects during sign-in/sign-up, including checking location and timing correlations.

• Owner: Rashmi
• Action: Fix login delay issue. Remove the 3-second wait and immediately show the spinning wheel during login.

• Owner: Koushi (with UX Engineers)
• Action: Tweak columns in the requests page (post-login). Finalize look and feel with UX team before implementation by the Web App team.

• Owner: Rashmi
• Action 1: Add a distinct box when user selects “No” in For Self field. Action 2: Define what fields/data from Create Request should display on dashboard. Action 3: Finalize notification look and feel, with Volunteer Micro Services team.

• Owner: Rashmi
• Action: • Ensure user’s address is saved in profile before creating new request. • If address missing, navigate user to personal information page. • Read-only page → no asterisk. Editable page → asterisk shown. • Users can only move forward if required fields are completed; otherwise, remain on page with warning. • Remove asterisk from disabled Country field in profile page.

• Owner: Koushi
• Action: Enable new users to upload profile image. Store image in S3 and display it on login/usage of website.

• Owner: Dev Team, QA Team & Rashmi
• Action: • Do not log sensitive information (visible in browser inspect). • QA to confirm via logging levels. • Research dynamic debugging and debugger tools. • Follow OWASP Top 10 guidelines. - https://owasp.org/www-project-top-ten/

Date & Time: 08/26/2025 | 10:00 AM EST

Attendees: Rao Bhethanabotla, Niharthi Muddada, Akshay Bhagwat, Prachi Rajesh Khopkar, Shreenithi Sivakumar, Pratik Darade, Saket Thorat

Topics Discussed:

• MVP Progress: 0.5 and 0.8 releases completed (AdSense integration).
• 1.0 MVP to include help categories: food, clothing, housing, education, elderly support.
• Product Managers/Business Analysts to finalize use cases and define additional fields (e.g., tutoring subject, dietary needs).
• Marketing & Outreach: Marketing repo linked to MVP board. Collaborator organizations (nonprofit/for-profit) must be identified; written permission required to display logos. Partner logos to be featured on site, including ticker format.
• Social Media: Wiki page to track official accounts (YouTube, LinkedIn, TikTok, Instagram, etc.). Credentials to remain with exec members. Official name: Saayam For All.

Action Items:

• Product Managers: Review and finalize help category use cases.
• Marketing Team:
  • Set up project board in repo.
  • Coordinate outreach to organizations and obtain logo permissions.
  • Update wiki with social media accounts.
• All Volunteers: Test development site features and provide feedback.

Date & Time: 08/15/2025 | 10:00 AM PST

Attendees: Rao Bhethanabotla, Madhuri Katta, Manojna Angara, Saket Thorat, Anmol Bhatta, Likith Kumar Vuchooru, Sathya Gundla, Maharshi Prajapati.

Topics Discussed:

• AWS services for backend: EventBridge, Parameter Store, ElastiCache.
• Goal: Create a centralized ElastiCache instance (saayam_dev_cache) to be used by both Java and Python-based microservices.
• Initial setup to be done manually in AWS by creating a small, low-cost demo Elastic Cache for testing, then upgrading to a larger instance for production once validated.
• Need to recruit additional Java and Python contributors for this work.
• Requirement to create a wiki page documenting ElastiCache setup and usage.
• Demo to be presented in a future scrum call once Java and Python integrations are ready.

Action Items:

• Madhuri & Manojna: Set up initial ElastiCache instance in AWS.
• Recruit more Java & Python engineers to join the project.
• Draft a wiki page with setup instructions and use cases for ElastiCache.

• Owner: Arjun Pati

• Action: Configure the build action to trigger on any branch push.

• Steps to execute automatically: -Build -Test -Run

• Owner: DevSecOps Team

• Action: If contributors face issues while making GitHub changes, verify that they have been added to the appropriate Teams. Ensure Teams are linked to the correct repository.

• Owner: Meghana / UX Engineers
• Action: Test static pages for correct functionality when the browser language is changed.

• Owner: UX Team
• Action: Work on all 5 dashboards &Prepare mockups and present them for review.

• Owner: Product Manager / Business Analyst
• Action: Update roadmap slide based on release plans and updates.

-Action: Confirm with Exes if they wish to be part of 0.8 MVP.

• Action: Every message in WebApp and Mobile App must have a unique error code. Mandatory for both front-end and back-end teams.

• Owner: Samrudh Uchil & Rishitha

• Action 1: Explore opportunities to collaborate with Rotary.

• Action 2: Contact Expansion & Work on acquiring more contacts.

• Owner: UX Team / Rashmi / Sugandha

• Action: Prepare a static demo of the entire Saayam application. Use one category as an example.

• Purpose: Presentation in conferences and upload on YouTube channel.

• Access Hub – Service Access Request Guidelines: Service Access Request Guidelines

• Saayam Groups: Saayam Groups Wiki

• Teams – Team Leads – Contact Info: Teams & Contact Info

• Rao Bhethanabotla
• Manoj Mullapudi
• Yugesh Nakkala
• Shehban Patel
• Sair Ram
• Lokesh Vedullapalli
• Irhum Arif
• Juveriya F
• Uzair Pachhapure
• Sparsha
• Lalit Sharma
• Ishita Rastogi
• Keerthi Mandadapu
• Sugandha Agrawal
• Ramya Reddy
• Pranav Sasidharan
• Maharshi
• Advita Ingale
• Sreeja Tudhigeni
• Meghana Karri
• Vishnu Vardhan

• Uzair Pachhapure, Ishita Rastogi, Pranav Sasidharan are the new Product Managers
• Business Analysts & Product Managers are working on Writing the Use Cases

• Rao K Bhethanabotla
• Dmitrii
• Manoj Mullapudi
• Sai Srinivasa Murthy Ammanabrolu
• Praneetha dr ms
• Vennela
• Deeraj Thakkilapati
• Keerthi
• Shreeda Trivedi
• Ria Shah
• Ramya Reddy
• Swathi Ramesh
• Suprajareddy Anagandula
• Meghana Mendu
• Vighnesh Sridhar
• Suraj Sureshkumar
• Sugandha Agrawal
• Abhinav Nehra
• Uday Sujith
• Aryan Wagh
• Rashmi Bilaskar

• It was emphasized that the website needs to be tested on at least three different browsers: Chrome, Firefox, Safari, and Internet Explorer.

• in Executive Team Section Names should be displayed with first and last names, with the middle name as an initial (if available). Each name should be linked to the individual’s LinkedIn profile.

• In the main page the 'Join Us' Section, the current phrase “Looking to Join US?” is to be rephrased with more refined and engaging alternatives.

Suggested options include:

1. Join Our Journey to Create Impact
2. Ready to Make a Difference?
3. Become a Part of Our Mission

• In the About Us Section Enhancement, the existing real estate image is too large and should be replaced with a smaller image and can add some informative content in this section to enhance user understanding and engagement.

• The controls for the 5-minute introductory video on the homepage are currently hidden. Unhide the video controls to improve user interaction and usability.

• We can refer the Website of River Islands Homepageas a design reference for our own main page layout and aesthetics.

• Everyone from Saayam are requested to review the Saayam Onboarding Video (Google Drive Link) and provide feedback or suggestions for improvement.

• Rao Bhethanabotla
• Manoj Mullapudi
• Dmitrii Zagorodnikov
• Sreeja Tudhigeni
• Viswadha k
• Saketh Reddy Chappidi
• Aatish Kayyath
• Sohail
• Abhinav Nehra
• Sai Krishna
• Kiran K V
• Aryan Wagh
• Teja
• Praneetha Kamarajugadda
• Keerthi Mandadapu
• Ganesh
• Sugandha Agrawal
• Rashmi Bilaskar
• Uday Sujith
• Saketh
• Lal Reddy Indla
• Shashank Banala
• Viswadha

• It is mandatory to track user Last Login details, physical location, and IP address for security and fraud check purposes.

• All observed data should be stored under Virginia - Private bucket.
• Web application data specific to Virginia and Ireland can be stored in Public buckets.
• All other data must strictly be stored in Private buckets only.

• Team members should access AWS using only the North Virginia or Ireland regions/views.
• Any other AWS region instances must be identified and removed by the Dec-SecOps team.

• All Leads and Managers are requested to closely monitor and close issues in the Kanban Project Tracker.
• Ensure active tracking of volunteers as part of ongoing project management.

Note: "If something is free, there's usually no limitation on its usage. However, since the above activities incur costs, it is important to enforce limitations and best practices."

.5 MVP Static Pages - identify mistakes in pages & receive feedback sayaamforall.org (developing home page)

Architecture: Moving javascript bundle to s3

How are you developing application at sayaam for all ? GitHub devsecops 2 regions - North Virginia & Ireland

In webapp javascript stays in one place

2 Goals for test-salaam.netflify.app

• Impress users who visit the page (Inform users about the organization- what we are good at & what we do)
• Receive donations & join the organization

Tasks to do: 0.5 MVP Markups The YouTube video playing at the home page - https://www.youtube.com/watch?v=9CBLVoSSuwM&ab_channel=AlgoWorld

Marketing required at home page:

• A good logo
• Convert into a more interactive page

Toolbar is not clearly visible at the contact page:

• Need a page to show Metrix, not needed for 0.5 MVP, but needed for MVP
• Hide - join the community (login page) button for now
• When super admin or admin logged in page, they have to see the issues on priority
• For all 10 languages Including audio and video needs to be tested, and the entire UI should be tested in all languages
• Admins and Super Admins dashboards should see both internal and external numbers and others should see only external numbers
• Admins should have one more tab for preferences and preferences tab will have multiple options