Meeting Date: Thu May 07 2026
Source: Google Doc Link
Summary
Team introductions and app vision preceded technical stack discussions and the onboarding of a new developer.
Team Introductions and Vision
Members introduced their technical backgrounds and roles. The project vision focuses on creating a Buddhist learning application aimed at reaching 1,000,000 daily active users.
Technical Architecture and Stack
The team utilizes Flutter with Riverpod, Fast API, and Firebase. Development centers on core engagement features including notifications and community-building mechanics.
Developer Onboarding and KPI
A new developer will begin on the 18th focusing on Flutter front-end tasks. The team decided to limit this role to 10 to 15 hours per week.
Suggested Next Steps
- [The group] Define Requirements: Catch up to determine work expectations and required output for Rinzin Choephels KPIs.
- [CommOps Manager] Set Contract: Finalize Rinzin Choephels KPIs and set the part-time employment contract. Onboard the new hire following KPI establishment.
- [Rinzin Choephel] Review Codebase: Look into the code base hosted on GitHub.
- [Tenz Kuns] Share Documentation: Share the backend Swagger documentation with Rinzin Choephel.
- [Rinzin Choephel] Review Swagger: Look into the shared backend Swagger documentation.
Details
- Meeting Commencement and Attendance Status: The meeting started with greetings, and there was a slight issue with CommOps Manager being late to the meeting, which they apologized for (00:00:00) (00:05:20). Rinzin Choephel also had trouble joining, noting they were out and had not received the meeting invite (00:04:02). Kunchok Tashi was noted to be joining from China (00:00:00).
- Team Introductions and Roles: The CommOps Manager introduced the team, including Kunchok Tashi and Tenzin Tamdin, who handle the Flutter work, and Tenz Kuns, the back-end engineer, along with Evan Yerburgh from UI/UX. Rinzin Choephel introduced themself as a developer with experience in native Android, Flutter, and the MERN stack, who has primarily worked with startups and is currently permanently employed but is committing two to three hours daily as a part-time Flutter developer (00:05:20) (00:09:32).
- Part-Time Flutter Developer's Context: Rinzin Choephel is joining the team as a part-time Flutter developer, committing two to three hours per day. The CommOps Manager noted that Kunchok Tashi is also contributing in a similar scenario (00:09:32).
- Evan Yerburgh's Role and Background: Evan Yerburgh introduced themself as the Product Strategy and Documentation Lead, with a background in technical writing and UX design. Their role involves conveying the founder's vision to the team and working closely with UX designers, covering various tasks common in a startup environment (00:10:41).
- Tenz Kuns and Tenzin Tamdin's Roles: Tenz Kuns, a full-stack developer, has been with the company for five years, working on many in-house toolkit applications, and is now focusing on the application's backend services. Tenzin Tamdin has worked with the company for almost three years, also starting as a full-stack developer before transitioning to Flutter and working on the app for over a year (00:12:09).
- Kunchok Tashi's Background and Contribution: Kunchok Tashi shared that they have worked in multiple startups, starting as a native Android developer before moving to Flutter and gaining some iOS experience. They are currently working for a Calgary-based startup part-time while collaborating with the team on building the Flutter application (00:13:57).
- Confirmation of Rinzin Choephel's Focus: Kunchok Tashi sought confirmation regarding Rinzin Choephel's role, asking if they would be joining as a full stack developer or focusing on a specific tech stack. It was confirmed that Rinzin Choephel will be focused on Flutter, particularly the front end, for the time being (00:16:37) (00:36:48).
- Vision and Purpose of the App: Evan Yerburgh explained that the “We Buddhist” app targets a segment that is neither overly casual, like typical mindfulness apps, nor overly scholarly (00:16:37). The app’s slogan is “we are Buddhists we learn practice and connect,” focusing on bite-sized Dharma learning, practice (like meditation), and a future social aspect. The app is modeled after the “hook model,” which taps into user triggers, provides variable rewards, and encourages investment, such as building a community within the app (00:17:30).
- App's Model and Current Features: The larger vision of the app is likened to “Bible for Buddhists,” enabling casual study and sharing within a community (00:18:56). Currently, the app is in the beginning phase, focusing on basic study plans, such as breaking down the Bodhicharyavatara into five-minute daily segments (00:20:15). Future plans include adding features like streaks, sharing progress, working with Buddhist influencers to create content, and expanding to countries with large Buddhist demographics (00:21:28) (00:23:55).
- Monetization and User Base Goal: The app is being developed as a free service to the community and is funded by foundations and donors, consistent with the company’s open-source culture (00:22:53). The current focus is on increasing the user base, with a North Star goal of achieving one million daily active users in five years (00:23:55).
- Technical Stack and Content Focus: The team is using Flutter for both Android and iOS platforms (00:26:50). The current focus is on content creation, including practice plans. Tenz Kuns explained that the application is moving beyond being a simple library of Buddhist texts to offering solutions for problems, relating text to overcoming emotions through a plan (00:28:03).
- Rinzin Choephel's Specific Flutter Experience: Rinzin Choephel detailed previous Flutter projects, including a fitness-centric app focused on community, challenges, and scoring, and a cloud appreciation app involving cloud identification and scoring (00:30:34). They also have experience with both Android and iOS export, dealing with device sensors, and native integrations, but noted it has been about two and a half years since they worked primarily with Flutter (00:31:37).
- Core Feature Focus: Notifications: Kunchok Tashi emphasized that notification is a core feature for the application, especially for event planning, daily routines, and using the “hook model” to engage users (00:32:45). Rinzin Choephel confirmed experience dealing with notifications for both Android and iOS, although they would need to refer back to their code for specifics (00:33:42).
- Flutter Architecture and Tools: Kunchok Tashi specified that the team uses Flutter Riverpod for state management, describing it as an enhanced version of providers, with which Rinzin Choephel is familiar. The application uses clean Flutter clean architecture, and common packages include Flutter Local Notifications and Firebase Analytics (00:34:35). Tenz Kuns mentioned the backend uses Fast API with a Postgress database (00:36:48).
- Codebase and Documentation Access: The codebase is on GitHub and is mostly open source, which allows anyone to view it. The team also uses Figma for designs, but Tenz Kuns noted that the Figma seats are paid, suggesting Rinzin Choephel should look at the code base first (00:37:54). Evan Yerburgh confirmed they would be shifting to do more documentation to improve the existing API and code comment documentation (00:38:48).
- AI Tools in Use: Evan Yerburgh inquired about the team's AI stack. Rinzin Choephel mentioned their current company standard is integrating Cloud with VS Code for reviews and design, prioritizing it over GPT due to data security concerns (00:39:55). Tenz Kuns confirmed that the team uses Cursor primarily, with some members using Cloud Code (00:42:13).
- Onboarding and Start Date: The CommOps Manager asked about the earliest start date for Rinzin Choephel, given the part-time arrangement. It was determined that since there is no immediate need for new features, Rinzin Choephel could use a week to understand the application code base and join the Discord developer server (00:43:41). The planned start date is Monday, the 18th, with follow-up meetings to set up knowledge transfer sessions (00:44:51).
- Defining KPIs and Work Expectations: The team agreed that Rinzin Choephel is a good fit for the part-time role, especially given their experience with community-building and notification-heavy applications, even though the previous work was fitness-related (00:47:59). The CommOps Manager emphasized the importance of clearly setting key performance indicators (KPIs) for the new part-time role, which differs from Kunchok Tashi's contributions, to prevent future issues (00:49:05). The team decided to focus Rinzin Choephel on Flutter (front-end) as a part-time commitment, which is estimated to be 10 to 15 hours per week (00:50:28).
How is the quality of these specific notes? Take a short survey to let us know your feedback, including how helpful the notes were for your needs.
Meeting Transcript
Click to expand full transcript
May 7, 2026
#Interview & Discussion || Rinzin Choephel || Senior Flutter Developer - Transcript
00:00:00
Tenz Kuns: Shak.
CommOps Manager: Break limit break.
Tenz Kuns: Oh.
CommOps Manager: They
Tenz Kuns: Yeah,
CommOps Manager: not
Tenz Kuns: the Take her. Okay. Hello everyone.
CommOps Manager: Hello.
Evan Yerburgh: That's
CommOps Manager: Just a second.
Tenz Kuns: locked
CommOps Manager: Let me send him a message.
Evan Yerburgh: saying
Tenz Kuns: in.
CommOps Manager: Oops. I'm doing this.
Tenz Kuns: the last. Let's think background.
Evan Yerburgh: Oh yeah, you guys are sitting next to each other.
Tenz Kuns: Yeah, it looks like that. Uh okay. Good. Uh greetings to Kashi. Good morning.
Evan Yerburgh: Nice to meet you.
Kunchok Tashi: Hi guys, morning.
Evan Yerburgh: Are you in China? Cool.
Kunchok Tashi: Yep.
CommOps Manager: Okay, there's a slight issue.
Tenz Kuns: Okay, it's not joining.
CommOps Manager: I have no is joining but uh I shared the meeting invite to comox I don't think he have received it. But he'll be joining. I've shared it on
Tenz Kuns: Okay.
CommOps Manager: WhatsApp.
Kunchok Tashi: I
CommOps Manager: But uh maybe he'll take it from mobile most probably because
00:04:02
Kunchok Tashi: I
CommOps Manager: he wasn't expecting it. I think uh although he was aware 8 p.m. but uh the meeting invite did not got uh come
Kunchok Tashi: don't know.
CommOps Manager: up. See I just got the access today. So I'm not sure what's is it?
Tenz Kuns: Coffee.
CommOps Manager: Yeah, I think it's let me add him. Okay, is also here. Uh, can you hear me? You're on mute if you're speaking.
Rinzin Choephel: if you can hear
CommOps Manager: Yes. Yes,
Rinzin Choephel: me.
CommOps Manager: I can hear you. Will you be able to turn your camera on? Uh I know uh there was issue with emitting.
Rinzin Choephel: I'm out. Sorry.
CommOps Manager: Yeah. Yeah.
Rinzin Choephel: I didn't see
CommOps Manager: There was some iss right right.
Rinzin Choephel: any.
CommOps Manager: Is there a way so that you can settle down somewhere? Uh we can since everyone is here we can get on the C
Rinzin Choephel: All right.
CommOps Manager: discussion. Sorry guys, my bad I
00:05:20
Rinzin Choephel: Yeah, sorry. I didn't see my
CommOps Manager: guess.
Rinzin Choephel: name.
CommOps Manager: Awesome.
Rinzin Choephel: Hi. Hello.
Evan Yerburgh: Hello.
CommOps Manager: First of all,
Rinzin Choephel: Sorry, my
CommOps Manager: ring uh really yeah no sorry my bad uh really uh sorry for the
Rinzin Choephel: bad.
CommOps Manager: last minute bumper but I hope uh for the next maybe half for 1 hour uh we can get the discussion like this.
Rinzin Choephel: All
CommOps Manager: Uh first of all uh before I proceed like let me introduce my uh team I have Katashi and Taming who are currently handling the flutter part of the work and Kungang here is our post engineer and Ian from UIUXT and uh maybe we can get a little bit of introduction from your end and then we can start the discussion.
Rinzin Choephel: right. Yeah. So, yeah, my name is Renzen. I'm based out of Bangalore. Uh I've been working from 2016. I started with mobile applications doing Android stuff all native all Android native. During that time it was just Java and then the cling came in. Uh after 3 years I started doing flutter.
00:06:49
Rinzin Choephel: Uh when I started flutter it was a new stuff. uh the initial batch of flutter uh did that for more three years and uh in my current company I'm in uh working for more than five plus years so I'm running towards six year and right now I'm I do all month tech like full MongoDB uh NodeJS React ID all the web apps so it's been almost two two and a half years that I'm not doing flutter which I'm already told about it. Uh that's more about me like I've been in this company for 10 years. Uh sorry in the industry for 10 years and and yeah I've been always working with startups. So I was never into MNC's or anything always with startups. So uh there have been bitters of starters you keep sometime it works sometime it doesn't work. So that's why you see like 6 month one year kind of stuff. But uh the starting one I worked for 3 years and now I work for five five plus years in between I switch a lot of startups.
00:08:02
Rinzin Choephel: So yeah reasoning it's sometime uh the funk and stuff like that and that's my resume and it shows uh my journey. Um I guess that's more about it. I started with all the building uh POS systems. Uh so we build POSOS machines for small uh kind of grocery stores and stuff like that. And then I have been need to film trying to work with clients uh every time we try to see their uh requirements and everything. uh and then have built lot of uh health apps uh and lot of machine kind of like native integration and stuff like that. Right now I'm building uh uh uh the last one was into the health domain I built uhation kind of web app where you can do your all the consultation and you can have your PC2s and stuff like that. Right now I'm building a CRM. Uh so our company is a uh K based trade company. We finance our people based on their invoices. And right now I'm building the onboarding process of it where we handle the credit risk, the risk status, um, and all the basic So I handled the UI side of it.
00:09:32
CommOps Manager: Sure.
Rinzin Choephel: Uh that's building and react and VS code. So let's
CommOps Manager: Awesome.
Rinzin Choephel: move.
CommOps Manager: So to set the context uh to Ian and company uh so Renzin is currently permanently employed at one of the uh his current employer right so uh he is coming in as a part-time uh maybe committing three to four hours per week sorry per day right uh as a flutter two okay two to
Rinzin Choephel: two to three hours per day.
CommOps Manager: three hours uh I think uh we also have kungashi who is also contributing
Rinzin Choephel: Yeah, I
CommOps Manager: in such scenario uh and uh we have Ting here who is
Rinzin Choephel: think
CommOps Manager: currently uh taking over as a uh senior FL uh developer in our web app right and uh yeah so turning over to you uh Ian if you want to take it maybe we can start with a little bit of intro brief intro from Ian and then we can start something
Evan Yerburgh: Yes, sure. Hi. Hi. So,
Rinzin Choephel: That's
00:10:41
CommOps Manager: There's
Evan Yerburgh: I'm Evan and I am in the past I've worked as like a technical writer and UX writer and a little bit of UX design. Um, and I joined um two months ago, I think. But but our our founder Entie and I have been friends for like 15 years and I've helped him in different areas um over the years like with some technical writing and sort of strategy. Um yeah so my well I think my title is at we we um is um product strategy and documentation lead. So I we're since we're in like in a startup mode I kind of do everything just helping uh our founder NT um yeah so on on the we Buddhist app team um I like um help bring Antie's like vision to the team and work a lot with the um UX designers. Um,
CommOps Manager: All
Evan Yerburgh: yeah. And let's see. I think, yeah, that's enough about me, I guess.
Rinzin Choephel: Get
Evan Yerburgh: But
Rinzin Choephel: some
CommOps Manager: right. Uh, what to you or something you want to
00:12:09
Tenz Kuns: Okay.
CommOps Manager: take?
Tenz Kuns: Uh my name is Senzu Kunang.
Rinzin Choephel: questions.
Tenz Kuns: I uh it's actually echoing my sound. I'm getting double sound. Okay. My name is Sen Kunang. uh I have been working here in uh Tama Duta Vib Buddhist uh for like 5 years as a fullstack developer and until now uh I have worked on many uh in-house toolkits uh applications for various cases uh mainly most of them are beta
Rinzin Choephel: Stop.
Tenz Kuns: tools so yeah um and right now I'm going to jump on our application backend services. So that's yeah, it's all about me.
Tenzin Tamdin: Okay.
Tenz Kuns: Anything
Tenzin Tamdin: Yep.
CommOps Manager: Okay.
Tenzin Tamdin: My name is Tending and did my college education from Bangalore and I think I've probably seen you region and same youth also.
Rinzin Choephel: Yeah.
Tenzin Tamdin: Yeah.
Rinzin Choephel: Yeah.
Tenzin Tamdin: Their face looks.
Rinzin Choephel: You look
Tenzin Tamdin: Yeah.
Rinzin Choephel: familiar.
Tenzin Tamdin: So I worked here for almost three years I think. Basically first it was like we working and then we switched to like then now we just obviously we changing the company's name a lot and uh same like Kang I studied as full tech developer and worked on inhouse uh pure tools and gradually start with yeah uh flatter yeah yeah building app because I have uh in time I had uh learned flutter And that's why we first started working on
00:13:57
Rinzin Choephel: almost 15
Tenzin Tamdin: the FL app. Yeah. Um and I think it's been more than one year we building building business. uh starting it was only me and yeah now we have me Dagger and Keshi and Keshi was very helpful in that case since yeah he was senior and I don't have much experience working their mobile app so yeah looking forward to you Yep.
Rinzin Choephel: Let's
CommOps Manager: All right, you want to give us a brief intro and we can start
Kunchok Tashi: startup definitely.
Rinzin Choephel: go.
Kunchok Tashi: Um so uh hi Ringi. Um Tashi here. Um like you I have also worked in the startup for I think multiple startup in the past uh starting from Bangalore and then um uh in Gorgon and I end up here in Toronto at the moment and still I'm working in a startup Galgiri based startup at the moment as a part-time and you know part-time I'm trying to spend um collaborating with the viboutis uh building of mostly the flutter application right and um like you again uh I have started as a native Android developer with the Java in the beginning you know and then eventually moved to the flutter and then um little bit of iOS experience as well and here and there you know in the startup I have worked in the uh the web application as well building the both back
00:15:29
Kunchok Tashi: end and front end but mostly um uh what you mobile application especially crossplatform like flutter ra native and things like that yeah I think that's pretty much from my end and I Yes, we can proceed.
CommOps Manager: Awesome. So, I'll take it uh over to you guys to kind of ask questions. I mean, uh Renzin, I uh urge you to kind of ask questions on the uh kind of project that we do because uh I think you'll be able to commit only two to three hours per day. I want you to understand kind of the workload that we have currently in the application and the challenges and Ewan can also give us an input on the kind of the vision that we have for the app from the UIUX perspective and what kind of challenges we currently have and we have something and who are currently involved in the development of the application and also Kang can pitch in on the uh other perspective from the first uh I'll give it all to you guys And yeah, this
Kunchok Tashi: Uh well I have a question before we proceed.
00:16:37
Kunchok Tashi: I mean you guys can start. Um just to confirm I mean you will be I mean joining here as a full stack or specific uh text. I just wanted to confirm before we proceed.
CommOps Manager: Let
Kunchok Tashi: plut.
Rinzin Choephel: I think
Kunchok Tashi: Okay. All right. All right. All right.
CommOps Manager: it
Kunchok Tashi: Got it.
Rinzin Choephel: it's
Kunchok Tashi: Um, okay. Fine. I mean, I can come to that. You guys can go ahead first. Uh,
Tenz Kuns: Uh,
Kunchok Tashi: even you don't
CommOps Manager: heat.
Tenz Kuns: Evan.
CommOps Manager: You're on mute.
Evan Yerburgh: Okay,
Kunchok Tashi: need
Tenz Kuns: Yeah.
Evan Yerburgh: I can talk about the app a little bit before um yeah, like the vision of the app. Um I'm not sure how much you know about it. um in but uh like we're making me Buddhist is uh kind of like the segment is like not too casual like
Rinzin Choephel: It's going to
Evan Yerburgh: uh headsp space or calm like these mindfulness apps that aren't really Buddhist but not like a
00:17:30
Rinzin Choephel: look
Evan Yerburgh: scholarly app either like so it's kind of like casual five minutes a day kind of Buddhist practice and study so um like We Buddhist the our slogan is like um we are Buddhists we learn practice and connect. So there's like we you'll be able to like learn like bite-size
Rinzin Choephel: It's
Evan Yerburgh: um Buddhist dharma and then also practice maybe like meditation
Rinzin Choephel: okay.
Evan Yerburgh: and mantra accumulation and then a big part of it is going to be later is the social aspect. So you could be like there might be like meditation challenge or like um learning challenge like groups like doing like money accumulations or something like if there's like his holiness of the Dalai Lama is giving like an empowerment like we can collect mantras together um this kind of thing and it's the app is based on like the hook model. I'm not sure if you're familiar, but it's like we try to tap into the trigger like why do people want to like um practice or like use a Buddhist app and then we can like make the app like that.
00:18:56
Evan Yerburgh: So I think the hook model has like the person has an intention and then they make an action. So they feel like oh I want to like be a good Buddhist or something. They open the app and then the app gives like a reward a variable reward. So we have some there might be like some celebration or something and then investment. So like when we design the app there's um some investment like if it's social when it becomes social like your your community is there maybe your teacher is there your friends are there you can later share share your like um what you your feelings about like the dharma or like make a video reaction and put it in the app or link it to like social media. Yeah, but it it's sort of like social learning. Um yeah, for the Bible, there's like some really big apps like the um bible.com that has like 1 billion downloads. And apps like this are like kind of our um model like the bi if it's like Uber for X or like like Facebook for whatever ours is like Bible for Buddhists.
00:20:15
Evan Yerburgh: So like you can come and like casually study and like you see your friends there and you can share. So this is kind of the bigger vision. Right now we're in the kind of beginning uh phase but in we'll add more and more features like video and like sharing and like social aspects as we
Rinzin Choephel: All right.
Evan Yerburgh: go.
Rinzin Choephel: So is it more of a community or is it more of like a questionaire that you do like videos challenges and you have your schools and stuff like that and then you share among your peers and stuff like that. So what is what is that
Evan Yerburgh: Yeah, we haven't built all that out yet.
Rinzin Choephel: that
Evan Yerburgh: Right now, we're kind of on the basics of like um some like study plans like one is like the bodhicara jinguk uh in a year where we break the whole book into like five minutes a day. But on top of that, we'll add like a social aspect like um like streaks and then sharing like sort of like the running apps or like you know like people show their their their progress.
00:21:28
Evan Yerburgh: You might share like um your progress on social media like what did
Rinzin Choephel: It sounds
Evan Yerburgh: it Stavia or something there's or like you show your running route.
Rinzin Choephel: scary.
Evan Yerburgh: Um you can share we'll we'll do things like yeah sharing um your progress or like your feeling about it and um things like that. So it starts out just like kind of learning but then um actually one of the main things we're doing is working with influencers. Um last year they had be I think in Boda um we hosted the Buddhist influencer of the year award first like a Buddhist marketing conference and we brought together like maybe 100 150 amer um influencers and then had an award and like gave out an award for the influencer of the
Tenz Kuns: Yes.
Evan Yerburgh: year. And so we're working with communities and um influencers to like make content on the app. So then people might see something on Instagram and or you might see like some ribb like content and then you could come back to we Buddhist support like and do like a course and so it kind of bridges like social aspects on the app but also social media and influencers.
00:22:53
Evan Yerburgh: But these are kind of all future um future features that we'll be working
Rinzin Choephel: Okay,
Evan Yerburgh: on over like the next couple years I think.
Rinzin Choephel: Yes. So, are we trying to build like a substitution model or is it more of a more like a
Evan Yerburgh: Yeah,
Rinzin Choephel: service to the community? What is
Evan Yerburgh: it's yeah it's a service to the community.
Rinzin Choephel: it?
Evan Yerburgh: I think we're born from like a open source culture like uh Kungam and Tan they've been working for years making all these like tools for Tibetan language and Tibetan AI and they're all like open source and free for um any like Tibetan like developers who are working with Tibetan language and I think that makes it so like we Buddhist is also like a free app and it's funded by like uh foundations and and donors like we have some donors that like give us money and
Rinzin Choephel: Hey,
Evan Yerburgh: then um so it's free. It'll be free for everyone. I don't think there's any plan to like monetize it.
00:23:55
Evan Yerburgh: Yeah, there might Yeah,
Rinzin Choephel: now I'm welcome to my questions.
Evan Yerburgh: maybe like donation in the app like you could make a small donation but I think most of the money will continue to be coming from like foundations and like uh rich donors.
Rinzin Choephel: Morning.
Evan Yerburgh: Yeah,
Tenz Kuns: Currently
Evan Yerburgh: as far as I know. Yeah.
Tenz Kuns: we think uh I think we are focusing on increasing our user base. Yeah,
Evan Yerburgh: Oh,
Tenz Kuns: that's what we are.
Evan Yerburgh: yeah. Yeah,
Tenz Kuns: Yeah.
Evan Yerburgh: that's
Tenz Kuns: So,
Evan Yerburgh: true.
Tenz Kuns: yeah. Instead of Yeah. getting money. I think that's okay.
Rinzin Choephel: Okay.
Evan Yerburgh: Yeah. Yeah. So we have
Rinzin Choephel: So what is the double network?
Tenz Kuns: Okay.
Evan Yerburgh: a
Rinzin Choephel: Is it more users in India
Evan Yerburgh: Yeah.
Rinzin Choephel: or
Evan Yerburgh: So we're targeting like the big like kind of the big demographics. So like in India it turns out it's actually like um deadcar Buddhists are the biggest group like more I think there's more car Buddhists than Tibetans but we're come out of like everyone it's like 95% of the people that we Buddhists are Tibetan so we have like a Tibetan focus but we're expanding to like um all the other big all the big Buddhist countries I think slowly slowly we have to
00:25:17
Rinzin Choephel: There you
Evan Yerburgh: we're making partners like so Indians Buddhists and then from there
Rinzin Choephel: go.
Evan Yerburgh: we um one of the programs that we're working with or events is in Bgay is um a terra group the international chupitaka chanting committee ceremony and they have people from like 20 countries and so I think we'll spread like that maybe like I'm in Thailand so Thailand like um Korea, Japan, all the Buddhist kind of countries because as Kang was saying um we have like Ron Chingley um Enti our founder he gave us a northstar goal like our goal is of like 1 million daily
Rinzin Choephel: I think you
Evan Yerburgh: active users in um five years which sounds like a lot but um when we use the Bible metric the Bible has one one
Rinzin Choephel: Um,
Evan Yerburgh: billion downloads amongst like all Christian people in the world and there's a not there's far fewer um Buddhists but we think we can hit like 1 million users so it's kind of a wide demographic but like kind of
Rinzin Choephel: cool.
Evan Yerburgh: casual we're Buddhists but not like old um or too scholarly it's like young kind of young generation um casual Buddhist but identify as Buddhist.
00:26:50
Evan Yerburgh: Yeah.
Tenz Kuns: Yeah.
Rinzin Choephel: Thank
Tenz Kuns: So we are partnering partnering with those uh organizations like the typical
Rinzin Choephel: you.
Tenz Kuns: chanding ones. So they they are actually having a major event I guess in the coming days. So yeah we are putting our plans and application. Yeah the plans in their website just to attract some user. Yeah. and increase our user count. That's a plan that we are having right now. And uh other than that any question?
Rinzin Choephel: No,
Tenz Kuns: I don't have
Rinzin Choephel: no. Are we doing Are we doing like iOS?
Tenz Kuns: any.
Rinzin Choephel: Are you more Android focused?
Tenz Kuns: Uh yeah,
Rinzin Choephel: You do
Tenz Kuns: right now uh yeah, you'll be the
Rinzin Choephel: both.
Tenzin Tamdin: Yeah using flutter right it's like yeah for both
Tenz Kuns: Yeah.
Tenzin Tamdin: platform Android and yeah currently you can download and see currently I think we are mainly focusing on building the content first currently we have uh like so
Rinzin Choephel: See
Tenzin Tamdin: it's been a lot of changes in that app uh since we started uh actually at first it wasn't like I was uh I was the only And uh yeah we don't have
00:28:03
Rinzin Choephel: music.
Tenzin Tamdin: much like we don't have UI UX design at first and then gradually we had one and other two UX designer and currently we are in the stage of like yeah it's in the beginner phase but mostly uh we are creating the content. Okay. Uh practice plan. Yeah, we are starting the practice plan uh to make more content so that the groups user able to see the content first will making community to share and other practice that's what I Think that's what
Tenz Kuns: Yeah,
Kunchok Tashi: Okay.
Tenz Kuns: actually in the beginning we have a voteist website when we were beginning with
Rinzin Choephel: What are you
Tenz Kuns: the project.
Rinzin Choephel: doing?
Tenz Kuns: So we didn't have a uh application that on that time. So basically the website was a kind of a library for pHA. Uh there were uh yeah it was kind of a library. So the mobile application started as a library also. It was like the mobile application version of the website.
Rinzin Choephel: What is
00:29:19
Tenz Kuns: So gradually we uh asked the users uh one
Rinzin Choephel: it?
Tenz Kuns: major uh suggestion were came during the bodgaya event. So yeah, most of them wanted a solution for a problem rather than just getting the text itself. So we introduced the introduce the plan thing in it. So right now we are not directly showing the text in the application. We are just relating the text to an emotion like how you uh overcome the fear. So you have a plan for that and in the plan you can just refer to the text to overcome uh to see the solution. That's the idea actually.
Kunchok Tashi: Okay.
Rinzin Choephel: Nice.
Kunchok Tashi: Um so uh I just wanted to know a few things uh from you um
Tenz Kuns: Yeah.
Kunchok Tashi: especially uh regarding I mean you have talked about the your experience you know working in a multi- startup in the past um but could you um share us a bit about the flutter specific um application or a niche that you have worked in the past so that we I I mean even we can give you a better context what you'll be working on and and I
00:30:34
Rinzin Choephel: Sorry.
Kunchok Tashi: I
Rinzin Choephel: Yeah.
Kunchok Tashi: Yeah.
Rinzin Choephel: So I uh we worked I worked under Kelka uh so which is more of a fitness uh centric
Kunchok Tashi: Mhm.
Rinzin Choephel: where there is a guy who is a fitness coach and who wants to have his own community right uh and that's how we we build challenges uh like how we do it here it's more of
Kunchok Tashi: Mhm.
Rinzin Choephel: a community and challenges and then scoring and stuff like that and then I work on a cloud appreciation app where people who see clouds and they appreciate clouds, right? And then and then you can take a picture of clouds and then you can identify what kind of cloud it is and then based on which you can also kind of score it. So it's more of like community and then also trying all this different stuff where they try to increase your score like that. Um there um I have to go back and check what all
Kunchok Tashi: Uh,
Rinzin Choephel: about and yeah it's kind of yeah it's kind of more
00:31:37
Kunchok Tashi: that's okay. I mean, I just I mean, we just wanted to get
Rinzin Choephel: of community uh challenges and stuff like that which I believe you're also doing the
Kunchok Tashi: a
Rinzin Choephel: same. I worked on uh I had both uh the Android and the iOS side of it, right? So I deal with export of everything and uh and then I work with sensors like in so we I in the beginning of my flutter career I built a GPS wayoint where uh it's more like a if you are in a area where there is no network then we try to work on the sensors and like if you walk and so there are a lot of different sensors in the your phone which you can uh get your data out of it and stuff like that. So in that regard I've done a lot of you know uh native integration and stuff like that. to to deal with the device sensors and stuff like that. So yeah, in bit pieces I've kind of done uh quite a lot in the flutter.
00:32:45
Rinzin Choephel: Uh but it's been like almost two and a half years. Uh I'm not doing uh the last project I was doing was into react native and then I moved to react. So it's been like two years of my though I didn't never wanted to go far away from flutter but then yeah I kind of stuck into the world of react and uh JavaScript so uh that's
Kunchok Tashi: Got it. So um in in in our case I believe we were dealing uh I mean notification is the
Rinzin Choephel: Yeah.
Kunchok Tashi: one of the most uh core feature that we'll be dealing because especially like everyone mentioned in the
Rinzin Choephel: Yeah.
Kunchok Tashi: beginning it's the you know uh the event sort of planning the routine adding a plan you know planning for it even things like you know notification for daily routines you know upcoming upcoming events and you know uh the the the to to bring the user to the application we have a hook model to you know bring through the notification we can do bunch of things right.
Rinzin Choephel: I
00:33:42
Kunchok Tashi: So this is one of the core feature we have and I think since you did uh I
Rinzin Choephel: think.
Kunchok Tashi: I mean you coming to the your the what do you call the app that you have built in the past gymnastic right things like that I was hoping like those thing require another
Rinzin Choephel: Yeah. Yeah. Yeah. You deal a lot of we did a lot of notification.
Kunchok Tashi: right
Rinzin Choephel: It's a kind of a headache to do notification, but then Yeah. If is Android and iOS it will be different uh with notification and you have to handle it separately. Uh yeah uh I've deal with quite a lot of uh even business and stuff like that. So notification is something I have done but there's nothing that I remember on top of my head but if I go back to code yeah I I would pretty much deal
Kunchok Tashi: Got it. Got it. Um Okay.
Rinzin Choephel: with notifications so that shouldn't be a problem.
Kunchok Tashi: Okay. Fine.
00:34:35
Kunchok Tashi: Um so uh I mean just to give you a context. So we I I think like tempting mentioned we are using Flutter for the um both mobile and uh sorry Android and iOS application. And uh we were using um what do you call um the flutter river port for state management just to give you an context I mean in case you want I I'm not sure if you have in the
Rinzin Choephel: I've only worked with providers.
Kunchok Tashi: past right so I I I think you should be familiar with the flutter river port it's the
Rinzin Choephel: Uh yeah.
Kunchok Tashi: what do you call enhanced version of providers as well
Rinzin Choephel: Yeah, I love to see
Kunchok Tashi: and oh great I think that's a plus point um then we are using uh clean flutter clean architecture for the application probably I think once you are onboarded
Rinzin Choephel: you.
Kunchok Tashi: we can go through the whole code structure but uh generally we are I mean we just revamped the whole architecture now and um there are a few other packages that are commonly used like for instance the flutter local notification firebased analytics and bunch of other things are there which
00:35:31
Rinzin Choephel: Sure.
Kunchok Tashi: we could again discuss it at some other time but I I'm just giving you a context you know what sort of uh tools we are using within the flatter all
Rinzin Choephel: Sure. Sure. I've worked with Firebase uh also on the back end side of Firebase and also dealing with
Kunchok Tashi: Okay.
Rinzin Choephel: notifications and stuff like that using Firebase and also work on get X and providers and other like you say basic and stuff like that. Yeah. So the yeah uh I think I'm kind of familiar but then something is something I need to get my hands
Kunchok Tashi: Got it. Got it. All right. Um, you guys have anything to
Rinzin Choephel: Sorry.
Kunchok Tashi: add?
Tenzin Tamdin: And our back end is
Evan Yerburgh: What's go ahead.
Tenzin Tamdin: Yeah. Yeah. For the back we I think it's we using fast API just to inform and I think okay for the Ps we will have the same back end right we won't shift T or
Tenz Kuns: Yeah, for plans we are going to use the VUDS back end.
00:36:48
Tenzin Tamdin: secure
Tenz Kuns: For back end, yeah, we are using fast API. We have a Postgress database uh uh for both user and yeah plan.
Rinzin Choephel: Well,
Tenz Kuns: Yeah,
Rinzin Choephel: I don't know about fast, but I guess I have local.
Tenz Kuns: I think if you are coming then you will not be dealing with the back end as for
Tenzin Tamdin: I can't.
Rinzin Choephel: Yeah.
Tenz Kuns: now. Yeah,
Tenzin Tamdin: Yeah.
Tenz Kuns: you'll be just handling the flutter one the front side.
Tenzin Tamdin: Yeah.
Rinzin Choephel: I believe there should be a documentation of the code and should be a sigma file that I can just go around and see. Uh if you have all this practice then we like
Tenzin Tamdin: Yeah, we will be able to share the G link and Pigma files which I think you I think.
Kunchok Tashi: right?
Rinzin Choephel: Let's
Kunchok Tashi: I think it's open source since uh you should able to access all
Tenzin Tamdin: Perfect.
Evan Yerburgh: Yeah,
Tenzin Tamdin: Yeah.
Evan Yerburgh: GitHub definitely.
Tenzin Tamdin: Yeah.
Evan Yerburgh: I'm not sure about I think Sigma uh they might say like you have to pay for seats
00:37:54
Tenzin Tamdin: Oh
Evan Yerburgh: but and but
Rinzin Choephel: see.
Evan Yerburgh: yeah
Tenzin Tamdin: yes.
Tenz Kuns: Uh, is Figma ready here yet?
Evan Yerburgh: um I mean it we use it and and some of the stuff is ready and already been
Tenz Kuns: Evan.
Evan Yerburgh: used. Uh it's a little bit of a mess right now.
Tenz Kuns: Okay.
Evan Yerburgh: Yeah.
Tenz Kuns: Uh okay. As for now,
Tenzin Tamdin: Mhm.
Tenz Kuns: I think Len, you should look into the code base actually first and when the Figma is ready, we can all look it into it together
Rinzin Choephel: Yeah. Yeah. I mean, I wasn't looking at that. I was like,
Tenz Kuns: maybe.
Rinzin Choephel: do you do all this practice on like so just to make sure they get standard result?
Tenz Kuns: Yeah, our code base is on GitHub. uh it's basically open source as yeah K said so yeah anyone can see it
Rinzin Choephel: Is
Tenz Kuns: mostly most of the code are public uh yeah we believe in open source that's why um and
00:38:48
Rinzin Choephel: it
Tenz Kuns: also about the Figma all the designs are on Figma also but it's like yeah as Evan said team members are paid actually seats so I
Rinzin Choephel: very
Evan Yerburgh: Yeah.
Tenz Kuns: yeah
Evan Yerburgh: And I I wanted to mention about documentation too is um we actually have a new designer came
Rinzin Choephel: minute?
Evan Yerburgh: on like this week and so I'll be shifting a little bit and doing more documentation.
Tenz Kuns: Hm.
Evan Yerburgh: So like working with the developers to document I mean you have all the like API documentation and in I mean code comments and all this but I'm going to help like add more documentation. I'm not not necessarily for the app, but at least for the the tools and maybe the the lead um API. I'm not sure. We still have to talk about it, but the we the documentation should be continually improving, but I think it's already already
Tenz Kuns: Yeah, also I think the new the new designer is also helping us for regarding the branding also,
Evan Yerburgh: got
Rinzin Choephel: I'm
Tenz Kuns: right?
00:39:55
Evan Yerburgh: Yep.
Tenz Kuns: So that's something new and if you uh when you join then we can also share you the backend swagger documentations so then you can look into it also. Yeah.
Rinzin Choephel: sorry.
Tenz Kuns: Yeah.
Evan Yerburgh: Yeah. So, it's like a growing team and a lot of it's it seems like it's been changing quickly and the team is growing and like creating new processes.
Tenz Kuns: Yeah. In the application team, we also have one more. Actually, Dagar is also there, right? Tin.
Tenzin Tamdin: Yes.
Tenz Kuns: Yeah. One more. Yeah. You will meet him later on.
Tenzin Tamdin: Yes.
Tenz Kuns: He's also full-time with Tamin.
Evan Yerburgh: I wanted to ask about like AI AI stack AI tools and processes like maybe both from our our side and then your sides. Um in
Rinzin Choephel: All right. Uh I do a lot of chat but these days we are using cloud. So we use we integrate cloud with our VS code and then try to get all the reviews and all the designing done.
00:40:59
Rinzin Choephel: So we believe that the UI is better done using cloud and uh I have worked a bit on the blockchains of NFTs where I build a employee MFT and deal with all the metadata and stuff like that. So I've touched upon blockchain NFTs and then using AI tools like that. I worked with uh what was it? I built the entire app using it.
Tenzin Tamdin: I think
Rinzin Choephel: Uh there's one more there's what was it called?
Tenzin Tamdin: Okay.
Rinzin Choephel: Sorry man. Uh so you can use that and it is integrated with GitHub and you can using that you can build like the entire just using your commands.
Evan Yerburgh: This is
Rinzin Choephel: um not really doing but it does just the basic works and not into like harden integrations and stuff
Evan Yerburgh: me.
Rinzin Choephel: like that. So yeah uh but right now I'm data cloud and uh that's what our company standard is we're trying to use data as you know uh data security and stuff like that. uh because GBT will no concern about the data uh because it's a third party and cloud will integrate well with the VS code.
00:42:13
Rinzin Choephel: So right now I'm using this and yeah uh that's my so
Evan Yerburgh: Thanks.
CommOps Manager: All right.
Tenz Kuns: Okay.
CommOps Manager: Anything else?
Tenz Kuns: Okay.
CommOps Manager: Yeah.
Tenz Kuns: I was going to say about our our AI strike. Okay.
CommOps Manager: Okay.
Tenz Kuns: I think Tamin is using cloud code. Uh right. Yeah. Cloud code. But most of the team in our yeah tech team are mostly using cursor at a time. Uh some people are using cloud code but most of them are using cursor right now. Uh yeah that's our part of AI.
Rinzin Choephel: Tomorrow we are having a debate to decide on caus.
Tenz Kuns: Yeah.
Rinzin Choephel: cloud. So um that's my internal but yeah we will decide uh so among developers we need to have a discussion tomorrow with the founder to decide which I use that we're going to pay for so good know that we're using
CommOps Manager: All right. Uh Renzin, uh if everything works out, uh my when can you start as a part time?
00:43:41
Rinzin Choephel: Um I don't know how soon you want by the way
CommOps Manager: Uh something uh are we in immediate
Tenzin Tamdin: right now.
CommOps Manager: need,
Tenzin Tamdin: I don't think so. You want do you have more
Rinzin Choephel: Let me do
Tenzin Tamdin: feature?
Evan Yerburgh: Um I mean we have many features coming down from but I'm not sure
Rinzin Choephel: it.
Tenzin Tamdin: Uhhuh.
Evan Yerburgh: like exactly right now. I think it also depend it depends on the back end like I
CommOps Manager: I guess.
Evan Yerburgh: think maybe like coordinating between like the front end and back end and design like if one is too I'm not sure what if if one is the blocker for the other right now or like if we have more back end or more front end or more design then like that's the atmosphere
Rinzin Choephel: It's constitute.
CommOps Manager: Okay. Uh I guess uh even if you mentioned uh we don't have a immediate meeting then you can take a week right. So I guess you can use that week to kind of understand our uh application code base and also uh I've shared you the materials uh especially our discord link right uh we uh use
00:44:51
Rinzin Choephel: Yes.
CommOps Manager: app server uh since we are all working remotely uh that's the developer
Rinzin Choephel: Very good.
CommOps Manager: server so you will find all of us here and maybe uh we can try to start by the end of next week or start of next to next week right in between Monday
Rinzin Choephel: Yeah. Yeah. We can start on a Monday and then
Evan Yerburgh: Easy.
CommOps Manager: uh which week
Rinzin Choephel: Monday the
CommOps Manager: 18.
Rinzin Choephel: 18th.
CommOps Manager: Okay, awesome. uh in between we will set up a few meeting if required right uh just with
Rinzin Choephel: Yeah. We need to do our
CommOps Manager: something yeah and also the uh KTS and stuff right
Rinzin Choephel: talk.
CommOps Manager: so let me know uh if you need any help from me right and uh yeah any questions you have for us
Rinzin Choephel: for I think I I you can sit and discuss money.
CommOps Manager: okay awesome All right.
Evan Yerburgh: It's This
CommOps Manager: Uh guess thank you so much for your time in and uh I'll get back to you.
00:46:04
Rinzin Choephel: Sure.
CommOps Manager: Yeah.
Rinzin Choephel: Sorry for the bad start,
CommOps Manager: Okay.
Rinzin Choephel: but yeah,
CommOps Manager: That's okay.
Rinzin Choephel: I wasn't I wasn't notified.
CommOps Manager: That's Yeah. Okay.
Rinzin Choephel: All right,
CommOps Manager: Awesome.
Rinzin Choephel: see you guys here. Have a good time.
CommOps Manager: All right. Thank
Tenzin Tamdin: It's
Rinzin Choephel: Yes.
Tenz Kuns: Okay.
Evan Yerburgh: Thanks.
CommOps Manager: you.
Evan Yerburgh: Nice to meet you, B.
Tenz Kuns: All right.
Tenzin Tamdin: actually
CommOps Manager: I
Tenz Kuns: Okay, I think we have to list on the new upcoming features
CommOps Manager: think
Evan Yerburgh: Yeah. Yeah.
Tenz Kuns: actually.
Evan Yerburgh: I
Tenzin Tamdin: 15. We are busy with that. No.
Evan Yerburgh: think
Tenzin Tamdin: Uh priority set for the what I plan is it
Evan Yerburgh: Yeah. I mean,
Tenzin Tamdin: 15
Evan Yerburgh: tomorrow should be sprint sprint planning for our next sprint,
CommOps Manager: Nothing.
Evan Yerburgh: but um I'm not sure like how we are doing for
Tenzin Tamdin: years.
Evan Yerburgh: the like collection and a couple of finishing up the other pieces or we can start moving on.
00:47:10
Tenz Kuns: I think yeah Evan you have not been informed actually but they like already uh worked on the
Evan Yerburgh: Um,
Tenz Kuns: series one so yeah the read only version the web
Evan Yerburgh: okay.
Tenz Kuns: version already is using the series yeah
Evan Yerburgh: Yeah. Oh, okay. So
Tenz Kuns: he he has already implemented the progress bar and all those things.
Evan Yerburgh: then,
CommOps Manager: What?
Tenz Kuns: So I think we can yeah discuss tomorrow actually about this one.
Evan Yerburgh: okay. Yeah,
Tenz Kuns: Yeah,
Evan Yerburgh: I think they're finishing up some designs. Um, okay. So,
Tenz Kuns: let's also look into the design together actually.
Evan Yerburgh: we could bring Yeah. Yeah. Yeah. That's what I I told Paul D and Lyndon that we would like meet you guys and
Tenz Kuns: Yeah.
Evan Yerburgh: if MD has time too, but at least you guys can look at the designs before and we can like fix them a little bit if they need to.
Tenz Kuns: If anti comes then there will be like hundred of new images on top
00:47:59
Evan Yerburgh: Yeah.
Tenzin Tamdin: Mhm.
Evan Yerburgh: Yeah. Maybe it's not going to be it might be too
Tenz Kuns: of that.
Evan Yerburgh: much.
CommOps Manager: That's what because I was we urgently need
Tenz Kuns: Yeah.
Evan Yerburgh: Yeah,
CommOps Manager: you.
Evan Yerburgh: I mean we do but um day I don't know. Come down.
CommOps Manager: I think uh you guys can catch up and let me know what is required from him so that I could set the KPIs right uh for him right uh maybe is contributing like uh two to three by the way uh he's good enough right for the job the overall feedback
Tenzin Tamdin: I think okay we haven't looked in this like know but I think it's okay not sure we haven't seen this what he build I think it's good enough I think
Tenz Kuns: As for the part time,
Tenzin Tamdin: what
Tenz Kuns: I think it's he's good. Good.
Evan Yerburgh: Yes.
Tenz Kuns: Yeah. But we haven't questioned him. Yeah.
CommOps Manager: Okay.
Tenz Kuns: Like an interview actually. This time it was just like a discussion.
00:49:05
Tenzin Tamdin: you see
CommOps Manager: Okay.
Tenz Kuns: So can't really check his
Evan Yerburgh: Yeah. I had to be
CommOps Manager: Do you guys think we need uh another tech
Evan Yerburgh: enormous.
Tenz Kuns: No, no, I don't think so.
CommOps Manager: discussion?
Tenz Kuns: I I think we can just start with him and yeah, if while progressing we can see his level. I think that is but I think when Kungashi and he was
CommOps Manager: Okay.
Tenz Kuns: talking he he was understanding everything and he already he he was saying like he already had a lot of experience on what Kungjuti was saying.
CommOps Manager: right?
Tenz Kuns: So I
CommOps Manager: Because he has kind of worked on the community building application types, right? Although it was fitness. So kind of like a similar because that also has a plan and that also has uh user personification and stuff
Evan Yerburgh: Yeah.
Tenz Kuns: think
CommOps Manager: like that. So I think much of that is similar also dealing with notifications and stuff right. So yeah, maybe we can work this out and let me know the requirement from him because I need to be clear on his KPIs right if he's working in as a part-time uh it's completely different from KJI I think Kjashi already has a repo with Ken and you folks right so that's why he's contributing a lot actually right so in his case he's completely different uh I mean it's coming in private right so I need to set the KPI
00:50:28
CommOps Manager: straight before onboarding and then so that in future we don't face any issue. Although he has uh said if uh everything works out then he would like to be on boarded as a fullterm but currently uh he's working as a full stack right react and net and stuff and he's also getting some exposure in the devops so he's spending a bit of time there but eventually he loves flutter more than that yeah I think that's his
Tenzin Tamdin: Wait,
CommOps Manager: perspective cool you guys can catch let me know
Tenzin Tamdin: I
Tenz Kuns: Mhm.
CommOps Manager: uh how soon we need him one And the other thing are what kind of work that we expect
Evan Yerburgh: It's okay.
CommOps Manager: from me in the KPIs right and I'll set the contracts and onboard it. Yeah. No problem.
Tenzin Tamdin: in
CommOps Manager: Yeah.
Tenzin Tamdin: mostly.
CommOps Manager: Because uh at 2 three hours although he can come in as a full stack but uh for 2 three hours I don't think he can uh do both the full web and the mobile both right.
00:51:25
CommOps Manager: So I want him to focus on one thing that is I think uh flutter is much better as a part
Tenzin Tamdin: Yeah.
CommOps Manager: time. That's my opinion.
Evan Yerburgh: Then what do you think I'm done?
Tenzin Tamdin: Okay.
Evan Yerburgh: Like like how much like can he how much can we expect him to do like in like three four hours today?
Tenzin Tamdin: He you he wants to join us,
Evan Yerburgh: Uh oh.
Tenzin Tamdin: isn't it? from that.
CommOps Manager: Yeah. 2 3
Tenzin Tamdin: So we can only expect Yeah.
Tenz Kuns: Get out.
Tenzin Tamdin: to Okay.
CommOps Manager: hours
Evan Yerburgh: Yeah.
Tenzin Tamdin: Yeah. And since it's more interesting, I think Yeah. So we
CommOps Manager: that is like 10 to 15 hours per week.
Tenzin Tamdin: need
CommOps Manager: You can catch up later and let me know. And uh yeah,
Evan Yerburgh: Okay.
CommOps Manager: it's pretty late here.
Evan Yerburgh: Yeah.
CommOps Manager: Okay, cool.
Tenz Kuns: Okay,
CommOps Manager: Uh,
Evan Yerburgh: Okay.
CommOps Manager: yeah.
Tenz Kuns: bye.
CommOps Manager: Thank you so much for joining.
Evan Yerburgh: Okay. Thanks. Yeah.
Tenz Kuns: See you tomorrow.
CommOps Manager: Yeah. Yeah.
Evan Yerburgh: Cheers.
CommOps Manager: Good. Yeah. Thank you. Bye.
Tenzin Tamdin: Yeah.
CommOps Manager: Bye.
Tenzin Tamdin: Okay.
Transcription ended after 00:52:46
This editable transcript was computer generated and might contain errors. People can also change the text after it was created.