Erika H:
"Project update for Happening ATM.
.
Awesome seeing this project Happening At The Moment for city council meetings really take shape. Keep at it folks, thanks volunteers for continuing to carry this.
Github: https://github.com/codeforsanjose/project-happening-atm/pull/337
Discord: https://discord.gg/3bAd9DAWCp
Google interest form: https://forms.gle/pfLfKGidXK3HJGKf6
Website: https://opensourcesanjose.org/
Tag tax: #civictech #siliconvalley #bayarea #techworker #codeforgood #softwareengineering #opensourcesanjose #codeforsanjose "
[Thanks, Erika! - MichaelG]
![[The image text is as follows:]
Project Updates:
Happening ATM
Pull Req 349
What does it need?
+ Examine potential security risks with disabling client-side authentication
+ Get QA env running (It works locally, but it needs to work in the...)
+ UAT testing in this QA
# Github: https://github.com/codeforsanjose/project-happening-atm/pull/337
# Discord: https://discord.gg/43MaFEgDCr
# Website: https://opensourcesanjose.org](https://files.mastodon.social/cache/media_attachments/files/111/391/516/737/136/046/original/94214347a4cf1d87.png)
![[The text of the image is as follows:]
Project Updates:
Happening ATM
Pull Req 350
+ Users can now view the latest meeting and agenda item statuses without manual page refresh
++ Updated functionality applies to both admin and community users
+ PR includes detailed comparison of solutions considered:
1) Server Sent Events (SSE)
2) Interval Polling of DB, and
3) Implementing GraphQL subscriptions over Websockets
+ Chose interval polling as the implemented approach (#2) with reasoning provided in the PR.](https://files.mastodon.social/cache/media_attachments/files/111/391/516/971/110/131/original/476182e7a05c8275.png)
![[The image text is as follows:]
Project Updates:
Happening ATM
Pull Req 350
+ This PR adds logic for handling 1st time Microsoft oAuth logins such that when a user clicks "Sign in with Microsoft" for the first time, a new user is created in the DB (via existing graphQL mutation) with Microsoft oAuth-provided details (e.g. user's Microsoft outlook e-mail.)
+ Implemented logic for syncing Meeting and Agenda Item Status changes (item A0010 on tracking sheet).
+ Changes impact both the primary Meeting List overview page and the individual Meeting details page](https://files.mastodon.social/cache/media_attachments/files/111/391/517/220/793/244/original/b7488a4f1edf1339.png)