[Meeting] API meeting 5

[EthanThatOneKid]

🙋 Participants

@johncmanuel, @EthanThatOneKid, @Haothai1

📍 Meeting location

Open Source Software team VC

🗓️ Meeting date and time

April 17th, 2024 9:00 PM

⏱️ Estimated meeting duration

60 minutes

📋 Meeting agenda

• Welcome new and returning participants.

🚀 Meeting updates

Recent thoughts

• Clubannounce events/announcement editing is different slightly. We are relying more on discord itself because they have the UI for their own resources already.
• api.acmcsuf.com HTTP server still needs to be similar to what we already planned, just relying on more microservices (discord bot) intended to sync our database with discord. why we are approaching with microservices and not monolith like original plan: all the aspects of this project is a bit messy to have all in one: http server, discord bot and database connection(s).
• Scope of api.acmcsuf.com: provide infrastructure for managing club data like wikipedia in a convenient for board members and optimized for ease of member access. For example, the same event data from our database/api is used in multiple places such as acmcsuf.com/events, clubannounce, and acmcsuf.com/wiki.
• User flow for creating a club event: We create an event on discord, it shows up on our frontend (but we don't edit discord event, just see it). However, we can assign extra metadata (such as which team is hosting it etc.) on top of discord's event which results in our stored event. Note: acm events "wrap" discord events in that the inner discord event data of an acm event is only updated by invocations made through discord, while other metadata properties are updated via clubannounce ui.
• John likes the sound of Clubannounce, Hao agrees it is easier to say. They think acmannounce sounds good if not clubannounce.
• For development it is recommended to use Supabase's free postgres database manager in development mode, so maybe soon let's provision a shared QA/Dev database that we can all share, but it is recommended for every individual developer to have their own database to do their own testing on. The database manager should provide the postgres URI.
• John suggests we LOCK INNN and CODEEE!!! Ethan agrees we got to make some progress. Ethan did not realize it has been 3 weeks since the last commit.
• If we don't finish during the semester, can we work on it during the summer until it is fleshed out: Yes, it is a little far out from perfection, but we can make a lot of progress until then at least. The last two weeks of the semester will be busy anyway with studying for finals and turning in projects. School before open source 😔.
• Hao and John bring up the idea of automated live transcription summarization of meeting minutes. Hackathon project?? 🙈

😸 Action items

No response

✨ Meeting wrap-up

• Next meeting: Thursday in-person meeting
• Adjournment time: 9:45 PM