Audio recording_1731427372055.m4a/2024-11-12
Let me just get set up here and contact switch a bit. How's everybody doing? Everybody doing okay? Yeah, good. How about you? Oh, pretty okay. Just... ...in the push-to-clock and push-to-work tasks. So I think it's already completely covered. These are tested. Tested both things and it looks like it's finished. I have fixed the issue with Google News feed, since there was some database error once you wanted to add a feed that is already owned by some other user. So this is also fixed. Yeah, there was one reminding issue, but I think it's not actually an issue. So yeah, so it should be covered also. I didn't manage to push the assembly AI match request on Friday. I want to do this today. But everything about that is already finished. So we are using kind of different audio model right now. I just need to de-play it. And most of the issues related to the audio processing should also be solved by this match request. And I think that's all from this side. Okay, so let's see. So what's issue number four? Two, three, seven, seven. Okay. So in this case, feature all consistent. So what actually shows up in the side panel? Because we fixed this, right? So it shouldn't say Google News. It should just say the search or the keyword. Yeah, it does it. I marked this as completed, but actually GitHub actually failed. And it didn't push the changes. But now I run it once again, and it works correctly. So I just need to validate it once again. And regarding the fourth item. Yeah, since we are using search API, there is no URL. So what I did is I put the query in the URL. Yeah, probably we need to hide this on the front end side, because there is no URL from Google News feeds. Yeah. Okay. Yeah, I think that makes sense. So is this clickable now or not? Isa? Yes, that's clickable, but it doesn't open anything. Okay. Because the URL goes to the down corner. You can see the URL, it opens, but the feed is empty when it's clicked. Yeah. Oh, okay. Yes. Amit, what do you think about just hiding this? Yeah, it's doable. Okay, so let's do that. So that then... Can we do like, let me Google that for you. Oh, we can do that as well, where we just append the search word after a queue is a parameter. Mm-hmm. Yeah, okay. That's probably a slightly better experience, so let's do that. Okay, should I use, let me Google that for you, or just google.com slash s equals the keyword? I would just do google.com. Okay. Yeah. That is supposed to be consistent, right? It won't change too often, right? It won't change to what? Google's query won't change too often, right? No, I don't think so. It should be super consistent, so I think it should just be something like google.com slash queue is keyword, right? Okay. Something like this. Without the quotes, okay. Yeah, without the quotes. Okay. Yeah. Oh, but that actually just fills in the search box. There's probably another URL that actually triggers the search. Mm-hmm. Yeah. Yeah. Okay. And then push to Slack and push to Rock ASAP. So it seems like those are fully validated on def. Is that correct? Yes. Okay. Yes, these two are fully validated now. Okay. Okay, so that sounds good. So we should get all of this out ASAP. Sebastian, what do you think about... So this one is validated or probably needs to do some final validation. Sebastian, what do you think about doing a production release for backend today? Yeah, we can do that. Yeah. Would you wait for assembly AI or not? No, no, no. I think we need to wait at least one day before pushing it to production because probably there will be some issues with that as always. Yeah, okay. So let's get all of the other things out. So push to Slack, push to Rock plus search API because that fixes the issue that we currently have in production. And then let's try to get assembly AI on def today as well so we can test that out. Okay. Amit, how about you? Get the playground for mobile release and then a bunch of tasks. Let me just check those. Okay, so mobile playground and add search to template directory. That was done. And change site panel behavior. That is live. And the last checkpoint of it has just been pushed. And then change feed directory behavior has been validated, 1115. And then 1121, add search to topics and meetings home list. I've also added it to the sidebar as well. So you can search for topics and meetings both in the home view of the respective home views. And after you go to the actual main view where you get to see the actual topic and meeting, there also you can search for the meetings and topics. And then meetings home converted to pick a template should open with the meetings preselected. That is done. And add download mobile app to meetings home. Okay. That is also live and can be validated. And I am doing 1122 right now. I have to rewrite to text block toolbar. Okay. And I have left a comment on 1118. That's basically already done because file upload model currently images, PDFs, and all text files and audio. So I'm not sure if you meant to just update the copy to reflect that. Yeah. So I was actually thinking of that because I remember like working on that task. But then when you actually log in, no, when you actually try to upload, when we say audio files or files, like we still have different copy for each. Right. But like in both cases, so if I do audio upload, I can upload files or like Word doc and PDFs and stuff or not. No, it's all. It's different. It's all. Yeah. So we have the main entry point. That is the normal upload file, generic upload file dialogue. And that currently has a few open. Yeah. So I do. I think it's not your upload file. Yeah. Yeah. So this, this, this is the generic one. And this accepts images, audio and PDF text, whatever. Okay. And then. Okay. And if I then do this, I'm not here, but not here as well. I still need to get used to the new thing. So if I then do here. Here only the audio is accepted. Okay. Here only the audio is accepted. Audio. Yeah. Okay. So we just need to change the copy on the other, like a generic one. Yeah. The generic one copy needs to just be. So it accepts everything. Oh, okay. PDF. PDF. .doc and .txt are all separated. You can just give me a copy and I'll update that. Yep. Okay. And this also accepts images and audio files. Yeah. Yeah. Okay. Let me, I'll provide the copy for that. Okay. Yeah. What it does is the same thing. Like for the image, it just goes through the same file. The image is supported here within the model itself, but for audio, it opens the audio model. Okay. Yeah. Okay. Okay. So that sounds good. Okay. Let's see. And 1117, I wasn't exactly sure what that task was about. So if you put. 111. 1117. Yeah. Okay. This one is floating a bit. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Oh, okay. So in this case. Okay. So in this case, let me actually show you. So currently we have this flow, especially with the new updated site panel. Right. So when you do this, you show this add new source, which I think is fine. Right. Because then you can pick an existing source or you can add a new source. But then when you do new meeting. Right. So I go through this flow. I then do meeting minutes. And then now I can only pick existing sources. Right. So what you want to have is the same option to do like a new source. So at least you can basically do the two different flows, existing sources or new sources. Okay. I think it was available previously. I'm not sure. But yeah. Yeah. And it was removed. I'm not sure why, but I think given these new flows, I think this is right. Like you need to have something here where if you want to start recording, you should be able to start recording. Okay. Yeah. Yeah. So that that one should also be like pretty straightforward. Okay. Okay. Given the state of things here, I think these were most of the smaller tasks that we had discussed last week. Right. Was there anything else? Yeah. These were the priorities that you had given me. Yeah. Okay. So when do you think we can do a front end production release? I think there are still a couple of tasks that haven't been validated. Once they are done, we can do it. Okay. Let's see. Which ones still need to be validated here? So. Change 1116. Okay. Workflows don't work anymore. I saw that one. What's the issue with that? Because we removed that dropdown, which had the initial trigger of workflow. Oh, okay. So I have fixed it. So it can be checked now. And other. This one. 1120. You can check it. 1120. Right now, you can just validate it to fit this. Yeah. Okay. I don't know. Yeah. Okay. Looks good to me. But it probably makes sense for you to quickly check these. And then check 1116 as well. And the workflows. As soon as those are validated, let's do a web release as well. Yes. Okay. Isa. Basically validated all the tasks that I've already mentioned. I'm not sure if I should go for them again now. And besides that, also validated a bunch of mobile tasks. There are still some open issues on the text editor. And I think on the collapsible sources as well. So I'm waiting for those to be fixed by ANGAP. Okay. Okay. That sounds good. And let's see. For QA in the mobile app, you download the APK, right? It's not yet on test flight or. Yes. Okay. Yeah. Okay. Let me check on the APK then. Hopefully we can do a release there soon as well. Okay. Wandele. Hey, everyone. So last week I worked on. Just a second. I worked on Google calendar integration. And then this week I'm starting. Actually, I'm continuing on admitting steps for mobile. But right now I am trying to adjust some comments on the Google calendar integration page that we had with Kenzo yesterday. Yeah. Okay. Yeah, we should go through calendar because I think we're getting to the point where we should be close to implementation. Before we do that, let's see. Let's jump into this. So a couple of bugs. So Google alerts not working we discussed. Other Google search API bugs I think we also discussed. So duplicate custom template in database. I think, Amit, you flagged this because of the embedded custom templates that we now do on different pages, right? I couldn't find that bug. Do you know what the ID for it was? I think I created it. Let me just search for it. It is 1112. 1112. Okay. Yes. Okay, so, Sebastian, so I think Amit's description here is pretty, like, basically what happens. So I think we should fix this. I looked into the database and, like, we actually have, because of this bug, we actually have a bunch of custom templates being created that should probably not be created. Right? So let's see. Where is the, yeah, I'm not sure where my database app is. But if you look into the, what's the thing called? What's the table called? If you look into the draft underscore template table, you see a lot of, like, custom templates being created all for this custom Teamworks quote that we've embedded in one of our blog posts. And that's as a result of this bug. So I would take a look at it and then see if we can fix it because I think it's going to basically mess up that custom drafts or the draft template table. Does that make sense? Yeah. Yeah. And I'm not sure, probably most of the custom templates in there are, like, need to be, like, removed. But just check if you can fix that. We still, we get, like, a decent amount of traffic on that playground in that blog post. So as soon as assembly AI is up and running on dev, I would quickly check this one and see if we can fix it. Yeah? Okay. What else? I'm still seeing persistent logouts on the web. Issa, have you seen this lately? Yes. Yes. Not on the day when you reported the task, the day it worked just fine. But it happens to me also a lot. Yeah. I suspect it's when you are on two tabs and logout at some point from one of them and then log in into some other account. But I can't reproduce it in a consistent way. Yeah. Yeah, neither can I. It's not a back-end issue for sure, because if I just open up Bash in an incognito window, I log into the same account, that incognito window stays logged in forever pretty much. So I'm not sure what else it could be. Web automatically logs out only in one instance where an API call is made, and that returns 401 unauthorized. And then we do a refresh access token, just because the current access token has been expired. So we ask for a new, fresh one. And even when that fails, that means that the refresh access call has been made after too long a time. That is also failed. And then we automatically log out because there's nothing we can do anymore. So you have to actually log in. So that is how it automatically logs out. Yeah. It doesn't automatically log out someplace erratically, but yeah. Yeah. Yeah, that's interesting. One thing I have noticed is as soon as, so like currently, like it seems to be fine, right? Like this is just my production, like Bash logged into my main account. So currently this seems fine, but not sure why this is not loading. But what I have noticed is, let's see, when this starts happening, right? Like the third party login for site settings is automatically disabled, which is a bit weird, right? So it's somewhere here. Let's see this one here. It's like allowed by default. But as soon as I'm in that loop where I can't stay logged in, this automatically gets blocked. So I'm not sure if that's related to anything. But for whatever reason, Chrome automatically starts blocking that third party signage. Yeah. I'm not sure. I'll check that as well. But yeah. But one thing to note is whenever you find it happen to you again, just open the console and check the Networks tab and see if there are a bunch of 401s that have been happening. And that means that if he is trying to make an API call and that has failed and it retries by getting the refresh access to one and even that has failed, and that is when you actually log out. So you can see there are a bunch of 401 network calls on your console. Yeah. And that's the only way that FE would log you out? Pretty much, yeah. Yeah. Okay. Okay. I'll keep an eye on that. And Isa, if this happens on your account as well, check on that third party sign-in if that's blocked for you as well because that might help us solve this. Okay. Let's see. Okay. I think that's that for this list. UX for Calendar. So I think, Sebastian, hopefully we can finally get Assembly AI live today on dev, test it out, and then push that to production. But then next I would work on Google Calendar integration and try to get this ready for Amit as soon as possible. Wandelay, do you want to walk everybody through the latest here? Yeah. So initially we had this UX over here. So we updated the design. I've been experimenting here with how to present the agenda. We updated the design here to include the agenda. So this would be basically all your upcoming meetings and previous meetings. The list is scrollable. Before you connect, you can click on connect Google Calendar here, and you will be able to pick your Google account and give us any permissions here. And once that's connected, you will basically have, let me just hide this menu, you will have all your upcoming meetings for that connected account here. So previous meetings would be, I'm sticking to meetings from the same week, but this could also be just the last three previous meetings or meetings from yesterday only. So depending, I think this is open for discussion. But basically the goal here is you've had a meeting recently and now you want to sort of take notes after the fact. You want to create a meeting document or meeting topic reference document after the fact. So we would show your most recent meetings that have passed here. We can also just show all your previous meetings and have this list infinitely scrollable, but that would be something that's up for discussion. And today's meetings, any meeting that is current or that's taking place or about to take place. So starting in the next five minutes would be highlighted in this way, and you can click on join meeting here and we will show the meeting name and all the participants here. And then for each of these, when you hover over them, we basically show all the details here, including the conferencing details. I'm still going to add location here. So I'm going to add location here just in case you're having a physical meeting and that would show the details here. And then this is for an upcoming meeting. You can create an empty meeting topic here that will use the title of the meeting as its title and the participants will be added as plain text and any description that goes with that event inside the calendar, depending on if we can pull that in. So that would just add context. And then for this context menu here, this is basically your multiple calendars. This is where you would add additional calendars so you can select and deselect and that would change basically the meetings that we show in here. You can add an additional calendar from here and you would basically go through the same authentication flow. And on the right here, we have all meetings. I've tweaked it a little bit. One, I've added the search to be more in line with what's currently been implemented and I've made it such that I've just removed the backgrounds inside of the actual bounding boxes that we had before so that it fits better into that screen. And down here is I'm working on a view for smaller screens where the meetings will just be sort of a side panel that overlays everything and it can be minimized or hidden away. And that would be mostly it for this screen. The other thing to mention would be inside of profile account and settings, you can click on add an app, add calendars and add calendars from there. And this is basically where you would be able to disconnect calendars from. Yeah, that's mostly it so far for the new meetings home with calendar integration, Google Calendar integration. Let's see. I think beyond this one delay, there was also a flow, right? Like once you create that meeting topic, we actually create a new topic with the calendar information, calendar metadata as a source in a meeting topic, right? Not necessarily as a source, but it would be let's do one event here. So for product design review, that would be the title. And then the events description would go into the actual topic description. And we were adding the participants here as a plain text. Yes. Yes. So that was mostly it for this. And then we would also pop up the meeting template screen. So you can pick your meeting template and upload the audio source or start recording, right? So with that flow, as I was workshopping it, I realized that this could be you're creating a topic beforehand so that you can take notes inside of the topic like you can on mobile. And that would sort of break the flow a little bit. And then in terms of adding a source that you can add a source from within the topic. So a draft from within the topic. So, yeah, that didn't make a lot of sense because the topic isn't populated yet. It doesn't have anything inside. I mean, sorry, the templates will use the entire topic as a source. And the topic doesn't have anything inside yet. So what makes the most sense is we create the topic. We have sort of all of the metadata filled in. And then the user can be able to click on add source inside of the topic to add the different sources. Okay. Okay. We can decide on that later. But, yeah. Okay. So I think this would be the full flow. Ahmed, any thoughts? In the previous meetings, there's an arrow. What does that do? This arrow opens any topics that have been created for the previous meeting. If there wasn't a topic that was created, the arrow wouldn't be there. But we would have to associate a topic with a meeting then. How would we do that? Yes. So one of two things here. In my discussion yesterday, I had suggested that one of two things can happen. We can either associate this sort of entry here with an actual topic. Or once a topic is created from a meeting here, we can just remove it from the previous meetings. And it will be in the all meetings list. Because these are basically just all meetings. Except some of them are already processed and have topics. And others aren't yet. So, yeah. I think maybe if that's difficult, we can just remove the entry from the list if a topic has already been created for it. Yeah. Are these the topics then? If these are the topics, then everything is openable, right? If previous meetings is basically what is being displayed on the right column under all meetings, and we are just displaying the top three recent ones as called and labeling it as previous, then everything is openable, right? Because it is a topic after all. I'm not sure I understand. So just to reiterate, you are saying that once when the user creates a new topic inside of meetings, it would be displayed in previous meetings. I'm saying it sounds like previous meetings is just another way to say get me the three most recent meetings. Meetings here just means topics. And display them here. Yes and no. So because these would be also just from the calendar. So any previous meetings from the calendar. And then if we have a topic for that meeting or that event in the calendar, then clicking that would open the associated topic. But if that simplifies it, I also don't mind that. It still makes sense to me if we just add the three most recent meetings here. Yeah, I guess that's a bit simpler because otherwise we would have to actual calendar event, right? Each calendar event has to be associated with the topic. And then there could be multiple topics created out of the same event and stuff like that. Work needs to happen to associate a calendar event with the topic. And we want one or one association or one or many associations. So it complicates it a bit. So yeah. Yeah. Okay. Another simplification we can do is we can remove sort of the link and just here I just have previous calendar events. And that would be fine. I'm thinking because if we just have the three most recent meetings here, if this list is sorted by most recent, it'll be duplicative. So here we can just have previous calendar events, then they wouldn't be interactable in any way. Or the only way you can interact with them is on Hava will basically just show you all of the details and then you can create a meeting topic from there. Yeah. Mackenzie to confirm what we are going to go. Yeah. Yeah. Okay. Wait. So I agree on like not coupling different meetings with specific topics. I think that makes implementation a lot easier. Let's see. I think if you click on one of these, we should like from a flow perspective, we should drive people towards creating a meeting topic with the meeting info as metadata. Right. So I think that's the key thing. Right. Let's let's let's simplify it and focus on that flow. And I'm also thinking that this should probably be more a bit of a scroll, but not like an endless scroll. But it needs to be more than the last three meetings, because some people have like 10 meetings a day, 15 meetings a day. Right. So I think this needs to go up at least probably like 10 previous meetings and down 10 upcoming meetings or something like that. So we should take that into consideration. Other than that, I think by not coupling it, I think it should simplify this flow quite a bit. And in the meetings, the tag filter has been removed. Is that deliberate or simply left out in the design? I just left it out in the design. I'm just referencing the actual sort of implementation stuff right now. And then I found that it simplifies the design a bit more. So what I'm thinking is the search can just behave the same way that the universal search behaves, where you can search for tags here and also select them. No. If that's that's something that's doable. I mean, it's just one line, right? Current. Current. If you open the current tab, it's just one additional layer. If we want it, we can have it. Otherwise, we can remove it all. So why to complicate it with the search and then including another thing? This is not that such. Then we would have to have search results and then all the sort of stuff. Yeah. I would just keep it. OK. No, no problem. That's that's fine. Let me just drop this in. OK, so. Yeah. OK. That would be tags. Tags would just show up underneath the search bar. OK. Ahmed, anything else? I think that's it for now. Once the entire production design is there, I could, when I am beginning to start developing, I'll probably have a deeper look and come up with comments if I have any. Yeah. So one day this should be production ready, right? It's completely tokenized. Yeah, everything is tokenized. I just need to finalize everything, make sure that all the flows are covered and add any annotations that might be necessary. OK, so that sounds good. Sebastian, any thoughts? Not really. Not at this point. OK. Yeah, I think from a back end perspective, a couple of call outs, I think the idea is that you can add multiple calendars to your, you can link multiple calendars to your account. So that's one consideration. Then, let's see. We need to set up the Google scope to make sure that we get authorization for Google Calendar or we get Google Calendar permissions to pull in some of the meeting information. So that's the second thing. And then, I think in this case, so we would populate a meeting topic with the calendar, with the meeting name, any description that's in the meeting invite, and then the list of participants. But all of this metadata needs to be used when drafting something. So if we don't add it as a source, we should make sure that the title, the description, and any text blocks are actually added as the context for the LLM. Yeah? One more thing that I'm noticing currently is if you add participants as a text block, it is easily modifiable, right? It is not a source of truth. Yes. Anyone can just do something and do it. Yeah, that is true, but I don't know. I think that's probably okay, right? Like in the sense of meetings change, people, like other people get pulled into meetings, et cetera. Some people are not in the invite, et cetera. So I think that's probably fine, unless you're thinking that we should just add the meeting as a source with all the relevant metadata. Yeah, I guess it could be added as a text source. So it is a bit immutable and automatically, you know, the LLM will automatically use it as a context. Yeah. But yeah, it's okay. Whatever is decided, we can do it, yeah. Yeah. I think there's something nice about just making sure that it's included as an additional source. Sebastian, what do you think implementation-wise? I think it's doable, and yeah, I think we can do that. Yeah. So one day, why don't we do this in the design? I think we should still take some of the meeting metadata and use that to populate the topic name, the description, and add this as participants, but also add a meeting object, which is basically a summary of that meeting source. So it's even clearer that this is based on a calendar meeting. Okay. So one additional document block that is just a meeting event or calendar object. Yes, exactly. But it would probably just look as a text source, I would think. Yeah, I think it probably makes most sense to just have it as a text source. Maybe, I guess, the presentation can be slightly different, but I'm not sure how valuable presenting that differently would be. Yeah. Okay, let's mock it up as a text source, then we'll see if we want to differentiate that at a later point. Yeah. Okay. So other than that, I think this design is pretty much ready. Once Wanderlei addresses the open comments here. Yes. Sebastian, how much time do you think you need for this? Hard to say at this point, but probably like four days, three days. Okay. Yeah. So let's get started on this as soon as Assembly's AI is live, hopefully today. Amit, how about you? I'd probably be able to have a better estimate once BE is available. Okay. So you would wait for back end before you start the UI work? Yeah, but I could start the UI work before two, that's not an issue. Okay. Okay, so let's take a look at like open tasks and then we figure out if there's anything else before you start working on this. But let's see. Okay. Okay, I think that's it in terms of agenda items. Let's see. Yep, so Wanderlei? Sorry, one thing that we forgot to mention is the meeting notification. So when you're in other parts of the app and there's this meeting starting soon, the pop-up would, if it's a conference, if there's conferencing, the pop-up would join meeting. So something like this. Yep. Is this supposed to be within app notification? Yes. Okay, so it will only be visible if they are on the tab and this is active. Yeah, I think if it's doable to send Browser notifications, that would be fantastic. But this should be enough because they will still get other notifications from presumably their calendar app and all of that. Yep. So implementation-wise, would we implement this through backend or can we implement this through frontend only? We can do it in frontend, but it would probably be, it would be like, if we fetch all the calendar events and let's say within a day, whatever, if the current day has any meetings, then it would probably set an interval at that time and the browser would automatically show it to them. But yeah, if, but that, the caveat is that if the tab sleeps and stuff like that, of course it won't show up. But again, if you refresh it and open it, then it would show up again. So yeah. Yeah. Sebastian, what do you think? What do I think about what? Sorry, I got lost. Thinking, what do you think about these types of notifications, having it done primarily through frontend or do you think we should implement something through backend? But do you want to implement this like, like real time or only on the loading of the web page? Because that's, yeah, that's a huge difference. I think it's a completely different implementation. Yeah, I think for this use case, it's probably fine to have it like only on the web page. There are a bunch of other use cases that we haven't really touched for notifications that probably require like more like actual backend work. Right. So, especially on mobile, because we have a bunch of loading states, etc. When you upload stuff and those types of things, so I think it would be nice to have notifications across the entire platform at one point in time. Yeah, but maybe not for this specific feature. Okay, so if you want to have it just on the load time, I can just create some normal endpoint and return the meetings that are starting soon and it should be pretty straightforward. So, once the command line implementation is done, it should take less than a day to implement such endpoint. Yeah, but if you want to support the real time notification, we should probably use several events and it would be much more complicated. For now, I don't think there is anything required because when this is going to be developed, there will be an API endpoint which lists all the calendar events, right? And Fe will be calling it regardless because we need to show it. So, we will call it anyway and in Fe, I can just see whatever meeting the start time is less than 24 hours. I can just attach an interval and at that point, it would just show it up. So, I think it's pretty straightforward to do it as is. Okay. Yeah, exactly. Okay. So, let's keep this as straightforward as possible then and implement it in front end. Yeah, okay. And I assume Anga would be able to take the same approach because he would need to pull in all the meeting events anyway and then use similar logic as what you're planning to use. Right? If you're saying something, you're on mute. But I think that should be correct. Okay. Let's see. Okay. So, I think that's it then. So, let's do a web release as soon as the last… Oh, Ahmed? Is there a point with regards to iOS app link? The current link is this one and apparently, it's getting stuck on connected. Should we remove the query parameters and is it okay or do you need it for some… No, no, no. I think we can remove it. I think this is a known issue. Where as soon as you do UTM tags, iOS blocks that. So, let's just remove it because we're not seeing this show up anywhere anyway. Okay. Yeah. Okay. Okay. So, we'll do a web release as soon as the final tasks are validated. We'll do a back end release. Sebastian, do you think you can still do that back end release today? Yeah, sure. Okay. So, let's do that back end release today and then let's get both of those out. I think that would be nice. Then, assembly AI in depth as soon as possible so we can test it out for at least today. And then, switch and hopefully that solves and improves some of our audio issues and audio transcription quality. Then, Sebastian will take a quick look at that custom template bug that we have in the database. Then, we'll switch to calendar integration that should take three to four days. And then, Amit, you and I will take a look at the list of tasks that we still have open and we'll figure out prioritization based on that. Yeah. Okay. Is there anything else anyone needs to cover or wants to cover? No? Okay. Then, that's it for now and we'll stay in touch over Rock. Thanks, everybody. Thanks, everyone. Bye. Okay, bye. Thanks, everyone. Bye. Bye. Bye.
Meeting on Project Updates and Tasks
Attendees
Sebastian
Iza
Amit
Wandile
Kenzo
Agenda Items
Project Progress Updates
Critical Bugs and Issues
Google Calendar Integration
Upcoming Releases
Action Items and Next Steps
Summary
The team reviewed project tasks, resolving several critical issues, including Google News feed errors and workflow challenges. They discussed the Google Calendar integration project, reviewing current designs and planning for implementation. They aimed to finalize Assembly AI testing on the dev environment and plan upcoming production releases for the web and backend systems.
Outline
Project Progress Updates
Iza and Amit validated multiple tasks, including UI adjustments and template directory changes.
Sebastian fixed the Google News feed issue and aims to deploy assembly AI on dev today.
Critical Bugs and Issues
Google Calendar Integration
Upcoming Releases
Action Items and Next Steps
Action Items
Sebastian and Amit to release production updates by today.
Iza to validate remaining web tasks for a production release.
Sebastian to address custom template database issues.
Sebastian to release Assembly AI to dev
Sebastian to start work on Calendar integration (3-4 days)
Wandile to finalize web/FE calendar integration designs with team's input.
Amit & Kenzo to review task prioritization before starting UI work on calendar integration.