#<Speaker1>[00:10.

160] We are recording this call for better note-taking, follow-

up, and training purposes.[00:14.520]
#<Speaker2>[04:31.107] Hello.[04:31.574]
#<Speaker3>[04:38.334] We can't hear you.[04:39.214]
#<Speaker4>[04:45.627] #<filler> I don't think it's on our side. Because they- they
can hear us.[04:48.538]
#<Speaker2>[04:49.458] Hello.[04:49.831]
#<Speaker5>[04:49.831] Hello, there.[04:50.527]
#<Speaker4>[04:50.598] #<unintelligible> Yeah, there it is.[04:52.417]
#<Speaker2>[04:52.468] Cool.[04:52.918]
#<Speaker5>[04:53.545] We're muted, apparently.[04:55.010]
#<Speaker4>[04:55.188] #<laughter>[04:56.074]
#<Speaker5>[04:56.487] Well, all right.[04:57.547]
#<Speaker4>[04:58.190] We have a new setup in here, so I- I thought that it was
probably on our side, but how are y'all doing?[05:04.560]
#<Speaker5>[05:05.585] Good. We're doing good. Want to introduce you to the newest
member of our team, I don't think you've met yet, this is Jerry, Jerry Mack.
[05:14.537]
#<Speaker6>[05:15.625] Nice to meet you.[05:16.476]
#<Speaker2>[05:16.857] Nice to meet you, I'm Casey. This is Rudra.[05:19.701]
#<Speaker3>[05:19.512] Hey, man. Yeah.[05:20.559]
#<Speaker2>[05:21.063] Hey, you've met Rudra? Have you met Steven?[05:22.903]
#<Speaker6>[05:23.474] No, I've only met yesterday.[05:25.823]
#<Speaker2>[05:26.525] #<unintelligible>[05:27.965]
#<Speaker2>[05:29.669] You're good.[05:30.282]
#<Speaker3>[05:30.234] You- you- #<filler> you could- you can barely see his beard
though.[05:32.802]
#<Speaker6>[05:35.452] Little bit.[05:36.052]
#<Speaker4>[05:34.616] #<laughter> Anyway.[05:39.163]
#<Speaker5>[05:39.571] Yeah, if you guys need to get now.[05:41.088]
#<Speaker6>[05:41.752] This is kind of like #<unintelligible>[05:43.897]
#<Speaker3>[05:42.607] Oh. yeah. Oh. Yeah, we will- we do- we do need to get one
here, for a conference room.[05:49.301]
#<Speaker5>[05:52.432] Well, tell Collin about your request.[05:54.101]
#<Speaker4>[05:54.981] Oh, God. #<laughter>[05:56.539]
#<Speaker5>[05:56.609] #<laughter>[05:58.878]
#<Speaker4>[06:01.369] Oh. all right, what's on your agenda Rudra?[06:04.058]
#<Speaker3>[06:05.147] #<filler> I need to get over the- what we need to get over
the- the rocker party over to Garrett. #<filler> Garrett, we have that, we're just
making sure #<filler> it runs fine with docker compose up and whatnot, so that you
guys can serve everything up locally #<filler> using just one terminal and not
having to pull up 10 different ones.[06:26.499]
#<Speaker7>[06:27.339] Mm-hmm.[06:27.965]
#<Speaker3>[06:28.210] The next thing, #<filler> some items I got from our meeting
yesterday, was we need to move all the documentation we have on frontend/backend in
the stack repositories over to conference. Then we need to provide documentation on
how to update environment variables for QA, staging, and production instances,
[06:49.042]
#<Speaker3>[06:49.042] and then I need to get you new URLs for the QA and pre-prod
instances to what KiwiTech was- was using before because the URLs KiwiTech we're
using before, for those instances pointed to their Jenkins, we need new ones that
points to ours. [07:06.891]
#<Speaker5>[07:07.444] Well, and supposedly Kiwi did that, 'cause- and- and so, I
just don't know in all of the information that they provided, if they told us what
those were.[07:22.712]
#<Speaker3>[07:23.183] #<filler> So, they did set up #<filler> the Jenkins server,
we were able to login, we changed the password and then we restricted access to
only yours and ours IP. #<filler> I- I didn't see in the- #<filler> in the
documentation[07:39.560]
#<Speaker3>[07:40.772] #<filler> that said like, "Hey, this is the old URL in this
instance. Now you guys are supposed to use this and not this one." I- I did not see
that.[07:49.338]
#<Speaker5>[07:49.858] Yeah.[07:50.218]
#<Speaker3>[07:49.892] That- that's what we're missing. #<filler> So, it's not-
it's not going to be a like a deep investigation in work investigation work for
those, we just have to go through those projects on Jenkins and figure out what U-
URL is that in- in season.[08:04.686]
#<Speaker5>[08:05.470] Okay, all right.[08:08.301]
#<Speaker3>[08:08.907] Yeah. #<filler> And I would like to- Sam, last night on
HubSpot #<filler> before I leave today, #<filler> I need to get him #<filler> the
URLs or- not URLs, but the file locations from where the HubSpot API's getting on.
[08:27.466]
#<Speaker3>[08:28.123] And by Hubspot API, I mean- I'm guessing not Hubspot forms,
it's just the API that is of the month.[08:35.281]
#<Speaker5>[08:36.545] I believe so. #<filler>[08:39.117]
#<Speaker3>[08:39.727] Okay. But #<filler> I will- I will send all those locations
to him.[08:42.383]
#<Speaker5>[08:42.687] Okay.[08:43.609]
#<Speaker5>[08:44.951] #<filler> Yeah. He is- yeah, doing some tweaking there, and
HubSpot has updated something that we now need to then update, so he's handling
that.[08:58.805]
#<Speaker5>[08:59.854] #<filler> But that's why he- yeah, needed to know we're in
our code, all that was, so he can #<filler> do what he needs to do. I haven't
talked to him about it in about two weeks, so #<filler>[09:15.306]
#<Speaker3>[09:15.986] Okay.[09:16.306]
#<Speaker3>[09:16.706] #<filler> I know one of the upcoming items next week is for
us to work on the FRD for Cherry Integration. #<filler> I know Garrett needs a
working local instance before he can finish up the PRD for that. #<filler> Once we-
#<filler> well, the- the meeting we had yesterday he was able to- well, not in the
call, but I'm pretty sure after that, he- he should be able to view the instances
locally,[09:44.609]
#<Speaker3>[09:45.067] and work with it. #<filler> The- the stuff that he's waiting
on from us would just make that process easier, but the work we did almost wrapped
up tomorrow or yesterday, #<filler> should have- should have allowed him to
continue on with in- or most investigative work for Cherry.[10:01.010]
#<Speaker5>[10:01.846] Okay. #<filler> So, yeah. #<filler> We are- yeah, so we're-
we're getting back on our two-week sprint cycle. #<filler> And so our- we've done
away with the Wednesday to Tuesday sprint going back to calendar weeks and back to
aligning it with our pay periods just to make things simpler on our side.
[10:31.461]
#<Speaker4>[10:31.824] Yeah, we got it. Yeah.[10:33.379]
#<Speaker5>[10:31.824] So, sprint- sprint 43 started on Sunday.[10:36.605]
#<Speaker4>[10:37.045] Okay.[10:37.524]
#<Speaker5>[10:38.045] We'll end a week from Saturday.[10:40.739]
#<Speaker4>[10:41.221] Okay.[10:41.596]
#<Speaker5>[10:43.826] #<filler> So, #<filler> So yeah, so I want us to just start
getting back onto that cycle, and being able to then do production deployments as
need- you know, a- as- as part of that cycle.[11:01.958]
#<Speaker4>[11:02.569] #<filler> So, whether it's the HubSpot API updates, the
Cherry Integration stuff, the- #<filler> the other thing is Stripe that we are
working on.[11:18.894]
#<Speaker5>[11:19.027] #<filler> So, our focus right now before we do any other
feature development, is making sure that our business systems are all talking to
each other properly. Starting with the customer at landsuite, being able to go
through our sales- #<laughter> our sales system, to payment system, and ultimately
to the accounting system, right?[11:46.450]
#<Speaker5>[11:47.050] And #<filler> the API #<filler> implementation of Stripe and
landsuite, was- we don't know how they did it, but they didn't do it well.
[12:03.300]
#<Speaker5>[12:04.091] And so, #<filler> I'll let Graham get into that 'cause he's
been wait- waiting into that. But that is- that has been the big impetus for us to
get local development, environment setup to be able to get into the code and sort
out things with the Stripe API. [12:25.978]
#<Speaker5>[12:26.498] #<filler> And then understand the process of then being able
to test and ultimately push to production. #<filler> And we're going to need some
support around probably I- figuring out what key we did, in terms of our Stripe
integration? And #<filler> how we-[12:47.912]
#<Speaker5>[12:54.323] if we have to, how do we burn it down, and start again?
#<laughter> To make it easier for us to be able to manage pricing, and subscription
tiers, and to have Stripe and landsuite talking back and forth, so that there's
subscription management.[13:10.313]
#<Speaker3>[13:11.360] Y-yeah. #<filler> #<filler> Hey, Graham. #<filler> As part
of your investigative work with #<filler> for Stripe, #<filler> have you created
any #<filler> like documentation for example, for us to quickly jump in and see how
products are structured?[13:28.651]
#<Speaker8>[13:29.482] We do have a PRD for Stripe at the moment. I'm having to
have that compares and relates to Maxio, but as is, if y'all wanted to look at
that, I could put that link in the chat, could be of any help.[13:43.974]
#<Speaker3>[13:45.534] Y-Yeah. Can you- #<filler> can you put that on Slack
instead? And then #<filler> what we'll do is we'll- we'll just use that #<filler>
and see how Stripe is structured. Because #<filler> I don't think we have access to
you- you guys at Stripe.[14:00.452]
#<Speaker3>[14:01.805] If not, #<filler> you can add us as developers #<filler> to
the Stripe account. #<filler> Add me #<filler> and Austin. Add me and Austin
#<filler> to Stripe.[14:15.863]
#<Speaker3>[14:17.454] #<filler>[14:18.085]
#<Speaker5>[14:18.885] Not right now.[14:19.574]
#<Speaker3>[14:19.814] The next step would be for us to look into the backend
repository, and see how the web hooks are implemented, or if they're implemented,
because that's how Stripe would know too. #<filler> Well, that's where Stripe would
send us the data if any.[14:34.821]
#<Speaker5>[14:44.930] All right. So,[14:46.017]
#<Speaker5>[15:02.462] All right.[15:02.902]
#<Speaker8>[15:07.465] You all want to look at that. That's sending Chromeware
Slack BPRD on me. I guess y'all should have access to see the Stripe itself too.
[15:17.739]
#<Speaker5>[15:19.183] #<filler> And then I know that Kiwi has #<filler> had done
Stripe-related documentation. Have you seen that?[15:32.890]
#<Speaker8>[15:33.968] Worked over it before.[15:35.474]
#<Speaker5>[15:35.559] Uh-huh.[15:35.959]
#<Speaker8>[15:37.185] Go the section confluence with you.
#<unintelligible>[15:41.391]
#<Speaker5>[15:41.572] Yeah. It was either in product development or project
management. I'm not sure which, but they done a bunch of Stripe-[15:50.052]
#<Speaker8>[15:49.400] Stripe implementation comprehensively. Cool.[15:52.497]
#<Speaker5>[15:52.225] Yes. When I had identified to them, "Hey, Stripe does not
seem to be comprehensible," you know. So, #<filler> not sure that you-[16:04.685]
#<Speaker5>[16:09.764] Really much of anything about Stripe integration. So.
[16:12.295]
#<Speaker8>[16:13.253] They wrote a little guide that was- would look like they
copy-paste it off the website, the features. Yeah, that's kind of what we'll do,
what they posted. [16:20.815]
#<Speaker5>[16:18.982] Yeah.[16:19.270]
#<Speaker5>[16:21.166] Okay.[16:21.583]
#<Speaker5>[16:22.918] Because- yeah, I actually had to pull up the Stripe website
and go through like, "Hey, we can't easily update subscriptions. Our subs- you
know, we can't- you know, do all of these things that Stripe says we can do.
#<laughter> So,[16:37.591]
#<Speaker8>[16:38.264] Yep.[16:38.463]
#<Speaker4>[16:39.733] #<filler>[16:40.523]
#<Speaker8>[16:40.523] I'm dropping it in the Slack.[16:42.176]
#<Speaker5>[16:43.011] What's that?[16:43.285]
#<Speaker8>[16:43.503] I'm dropping it in the Slack.[16:44.646]
#<Speaker4>[16:45.050] That's already in the Slack. #<unintelligible> They are
going through it. Unless you #<unintelligible>[16:50.408]
#<Speaker8>[16:48.827] #<unintelligible> Yeah, #<unintelligible>[16:51.259]
#<Speaker8>[16:51.783] I can go in and send it too, I- I don't think it would be so
#<unintelligible> anything can happen.[16:55.637]
#<Speaker5>[17:03.115] Okay. So, alright, so Rudra and Austin have been invited to
Stripe as developers as well. #<filler> So, that's-[17:17.483]
#<Speaker5>[17:19.559] that's what we're the- I mean that's, that's my biggest
thing is we're getting- yeah, we're getting back onto our two week sprint cycle,
we're going to be expected to have- you know, production pushes on a regular basis
to be able to tell other people what's happening.[17:37.898]
#<Speaker5>[17:38.074] And you have them timelines. So, #<filler> regardless of new
feature development, #<filler> I need to make sure that my team can- has the- has
what they need to be able to do that, and we need to do Stripe and then we need to
do Cherry.[17:55.643]
#<Speaker3>[17:57.197] Yeah. #<filler> What we'll also do in the meantime #<filler>
is do some test deployments on QA and pre-prod instances. We- we'll stay away from
production for now.[18:08.138]
#<Speaker3>[18:08.475] #<filler> But one thing, #<filler> I don't know if you saw
Steven's document on conference, just- #<filler> he was just explaining what he did
on- on AWS infrastructure regarding different services and security group- groups
and whatnot.[18:25.482]
#<Speaker5>[18:25.922] Yep.[18:26.208]
#<Speaker3>[18:25.922] One of the things that #<filler> we noted down and the audit
as well, but #<filler> he emphasized in the do-document that the production
database #<filler> that KiwiTech created was- or is hosted on a service called
LightSail, and it has a public mode turned on, right?[18:45.992]
#<Speaker3>[18:46.381] And- you know, in order to turn that off, well, we- we
cannot just turn it off, right?[18:52.412]
#<Speaker6>[18:52.418] No, #<filler> so- see that says #<filler> a LightSail
database. You either need to be on the same #<filler> PC Network #<filler> inside
of the LightSail service, or have that database public, so that a service outside
of LightSail can reach it.[19:17.577]
#<Speaker6>[19:18.514] #<filler>[19:19.094]
#<Speaker5>[19:19.557] And so that's why it's public right now?[19:21.405]
#<Speaker6>[19:21.405] Right. 'Cause if you turn off public, since your #<filler>
main infrastructure is in AWS, it would lose access to the LightSail database
instance.[19:34.027]
#<Speaker5>[19:34.498] Okay.[19:35.018]
#<Speaker8>[19:35.403] Similar issue with #<filler> Markus Enterprise.
#<unintelligible> same sort of thing.[19:41.557]
#<Speaker5>[19:39.361] Okay.[19:39.860]
#<Speaker5>[19:41.647] Okay.[19:42.047]
#<Speaker5>[19:43.290] So, what #<filler> so what do we need to do to fix that?
[19:50.547]
#<Speaker3>[19:51.354] We'll have to create a- well, a database under a service
called RTS. #<filler> We can- we can look up- I'm pretty sure there has to be a gu-
guide on how to migrate a LightSail database to Amazon RDS. If- if we can find that
guide, perform the migration,[20:10.733]
#<Speaker3>[20:11.811] #<filler> without affecting the parent database, obviously.
#<filler> Once the migration is completed, test the connection on master data-
well, the new database that we're going to create on RDS, see everything works
fine, and if it does, switch it out on the main production instance.[20:29.699]
#<Speaker5>[20:30.281] Mm-hmm.[20:30.898]
#<Speaker3>[20:31.258] And we allow it to be accessed from the resources, that is a
positive.[20:35.739]
#<Speaker5>[20:36.904] All right.[20:37.424]
#<Speaker3>[20:37.664] If not, the- the next viable solution is to create a
#<filler> this is an official term, it's called a dump, or SQL dump.[20:47.357]
#<Speaker5>[20:48.237] Okay.[20:48.563]
#<Speaker3>[20:48.220] #<unintelligible> data from the database, put it- put it on
new database and switch things up.[20:53.016]
#<Speaker5>[20:54.656] Okay.[20:54.959]
#<Speaker2>[20:56.088] So, this su-suggestion that y'all are going for is more of a
temporary thing to make it so that service works while being secure. And that a
more permanent solution of a place where to put the data needs to be created?
[21:12.521]
#<Speaker3>[21:13.407] Yeah, that's the- that's the RDS service. So what the
solution I'm talking about is permanent.[21:17.444]
#<Speaker4>[21:18.364] Okay.[21:18.776]
#<Speaker3>[21:18.933] It's- it's- it's going to replace the- the LightSail
database that we have.[21:22.772]
#<Speaker4>[21:23.612] Okay.[21:24.017]
#<Speaker5>[21:25.117] #<filler>[21:26.117]
#<Speaker3>[21:28.297] #<filler> Yeah, #<filler> unfortunately, that's not-
#<filler> that's not something we can do #<filler> without- well, without bringing
up- bringing it up because it affects production. #<filler> That's why we wanted to
talk it- talks about this first before we can actually do the work.[21:44.226]
#<Speaker5>[21:45.031] Yeah. Okay. #<filler>[21:48.317]
#<Speaker5>[21:53.239] All right. Well?[21:54.174]
#<Speaker5>[21:56.134] If that's #<filler> okay, so then how does- and I don't know
what that does, but I know Steven you had brought this up previously, about
teleport, and getting- perhaps getting that set up for access of things is that
part of #<filler>[22:15.803]
#<Speaker5>[22:19.643] Will- will that help this situation at all?[22:22.282]
#<Speaker2>[22:24.162] So, teleport would just be a way of you being able to access
the database and manage it #<filler> through #<filler> like- like- what's the term
Rudra? When you're requesting data from the database?[22:40.246]
#<Speaker2>[22:40.246] Querying and-[22:41.743]
#<Speaker3>[22:41.697] Yeah, yeah, querying.[22:42.839]
#<Speaker2>[22:43.310] Yeah, querying and- and getting into it via command line two
if you need to. #<filler> Teleport is basically a secure access proxy. It's- it's
#<filler> not necessarily built a bridge #<filler> connection from a database to a
server that's- that's #<filler> trying to pull that data for- for 24,000 production
usage, it's more a #<filler> s- more secure way of getting #<filler> remote access
to your- to your assets.[23:19.164]
#<Speaker5>[23:19.564] Okay.[23:19.964]
#<Speaker3>[23:21.892] Yeah, this- this situation is par- in particular is just a
#<filler> bad infrastructure setup.[23:27.656]
#<Speaker5>[23:29.096] Yeah.[23:29.324]
#<Speaker3>[23:29.962] #<filler> Unfortunately, #<filler> well, I don't think- Tel-
Teleport is needed, and we'll - we'll- we'll do it once #<filler> the overarching
issues gets fixed, and we'll just help it, hope you guys set it up on the
Intelligence Officers.[23:45.589]
#<Speaker2>[23:45.688] We- we do need- #<filler> we do need your okay to do it just
since it's a #<filler> open source software. Or else-[23:55.998]
#<Speaker5>[23:56.231] Tel- Teleport is?[23:57.012]
#<Speaker2>[23:57.159] Yeah. #<filler> So, if you'd have time to look at their
website, and you feel comfortable with it, then- you know, once you give me the go
ahead, I can- I can roll that out whenever.[24:07.045]
#<Speaker5>[24:07.723] Okay.[24:08.133]
#<Speaker2>[24:08.493] It won't affect- #<filler> it- it would not affect
production or anything, it would- it would just kind of sit in the background and
be rolled out.[24:17.908]
#<Speaker5>[24:18.508] Okay. All right. Well, #<filler>[24:23.240]
#<Speaker6>[24:23.240] Also, #<filler> I- I- I'm just going to state this just so
you're aware of it. #<filler> On- what- whenever talking about the #<filler> trying
to patch the connection between your existing database and your server, #<filler>
the reason why it really needs to be migrated, is[24:44.046]
#<Speaker2>[24:44.730] even if you were to kind of proxy and patch that connection
over, you're going to run into a ton of egress charges, which is going to run your
bill way up when- when it's way cheaper just to knock it out and migrate it.
#<filler> #<unintelligible> have egress and- and ingress traffic charges.
[25:04.614]
#<Speaker5>[25:05.173] Okay.[25:05.447]
#<Speaker4>[25:05.632] So, this new thing would be on AWS?[25:08.665]
#<Speaker3>[25:10.482] By new thing, you mean you mean new RDS?[25:11.944]
#<Speaker4>[25:12.771] #<filler> Yeah.[25:14.374]
#<Speaker3>[25:14.601] #<filler> So, #<filler> RDS is a serv- #<filler> RDS is a
service by Amazon. The new database is going to be under that service.[25:21.996]
#<Speaker4>[25:23.535] Okay.[25:23.751]
#<Speaker4>[25:24.654] I think it stands for Relational Database Systems. Yeah.
[25:28.329]
#<Speaker4>[25:29.831] Okay. Thank you.[25:31.111]
#<Speaker5>[25:32.070] All right. Well, yes, so let's- let's go ahead and do the
migration. And #<filler> 'cause- yeah, that definitely needs to get- get fixed.
[25:44.776]
#<Speaker5>[25:45.200] #<filler> After- after that, from a- from an architecture
fixing standpoint, #<filler> what- #<filler> what- what's the next thing we need to
tackle architecture-wise?[25:58.801]
#<Speaker3>[25:59.775] #<filler> One thing I see since the Sybase react phase,
#<filler> I- I really don't see a need of #<filler> standing up containers just for
the frontend. Either #<unintelligible>. There is a service called Amplify by AWS
again, that can literally take up your react project.[26:20.035]
#<Speaker3>[26:20.528] You put it in environment variables, and it's going to spun
up a new site like that. It literally takes like five minutes. And for our- one of
our clients, we have stood up like 10 production sites using that service program.
[26:34.919]
#<Speaker3>[26:35.519] Oh, okay.[26:35.959]
#<Speaker3>[26:36.559] Yeah. #<filler> It's pretty easy to create a #<filler> proof
of concept application. It's called- it's called Databse Assembly file. It's- it's
very- it's like- it's like Heroku within AWS.[26:49.931]
#<Speaker3>[26:52.235] So, if you have used Heroku or Netlify, or any of the
standalone #<filler> cloud provide- no, not cloud providers, what you call them?
Deployment systems? #<filler> It's exactly that. But in Amazon.[27:09.688]
#<Speaker5>[27:10.637] All right.[27:11.045]
#<Speaker5>[27:12.760] #<filler> Yeah, now we got a notification overnight that AWS
#<unintelligible> is migrating stuff?[27:22.147]
#<Speaker3>[27:22.482] Yeah. Yeah, it's- it's going to Virtual CPU. #<filler> It's
just- it's the way how- #<filler> how they calculate charges and #<filler> well,
the underlying infrastructure essentially. #<filler> In in your case, it won't be-
well, we have to- we have to do the migration at some point, but #<filler> it- it-
it won't be that bad.[27:45.618]
#<Speaker5>[27:46.807] Okay.[27:47.650]
#<Speaker5>[27:48.850] #<filler> Well, I mean it's saying this transition-
#<filler> we don't expect the transition to have any effect on your ability to
launch new test at pods, it's expected to complete by October 21.[28:02.067]
#<Speaker5>[28:06.472] Okay. #<filler> All right. Well, I just want to make sure
that as we're making architecture changes, that we're- #<filler> we've got a- we-
we update our architecture #<filler> diagrams, #<filler> so that we know.
[28:23.712]
#<Speaker5>[28:24.201] #<filler> We're going to be a little- well, I'm gonna be a
bit anal about documentation in that because we're going to be raising capital and
potentially having to go through technical due diligence. And so,[28:40.618]
#<Speaker3>[28:40.809] Sure.[28:41.165]
#<Speaker5>[28:42.412] having all that stuff up to date, and readily #<filler>
accessible #<filler> is going to be important. So,[28:50.136]
#<Speaker3>[28:50.365] It-it's important. As part of that, I'm pretty sure
#<filler> y- you already know #<filler> one of the things I have to do is make sure
our- our architecture is by #<unintelligible> compliant. #<filler> Doing- because
the- the- the- that's one of the thing I-I've seen with other clients that they do
as part of raising capital list.[29:10.468]
#<Speaker3>[29:11.156] The architecture they are using is- have to be- have to be
following one of these standards. So, we'll have to whatever architecture diagram
to attack has created. Who love you? Just make sure it's following those standards.
[29:16.616]
#<Speaker4>[29:17.169] Mm-hmm.[29:17.587]
#<Speaker3>[29:17.867] So, we'll have to- whatever architecture KiwiTech has
created, #<filler> we'll have to just make sure it's following those standards. And
if it's not, we'll have update and- update services and the diagram accordingly.
[29:29.885]
#<Speaker5>[29:30.841] Yep. #<filler> Yeah, we're- #<filler> we're going to be
starting the launch of our #<filler> hundred million dollar fund #<laughter> or LAN
Development Fund, #<filler> so, f- and part of the attraction of that, is that
there's an exclusive license to our technology that goes along with the fund.
[29:54.851]
#<Speaker5>[29:54.921] And so- presumably before someone's going to write us a 10
million or 50 million or a hundred million dollar check, they're going to want to
look under the hood. #<filler>[30:05.405]
#<Speaker3>[30:04.879] Yeah. #<laughter> Yeah.[30:06.066]
#<Speaker5>[30:06.608] One would hope at th- you know, that that is before they
stir up that kind of a check, that they want to do. So, #<filler> so yeah, I'm
trying to get- trying to get out in front of that. #<laughter>[30:20.809]
#<Speaker3>[30:22.283] That is- it's- it's a good thing to have as well regardless.
[30:24.898]
#<Speaker8>[30:25.579] Yeah.[30:25.756]
#<Speaker5>[30:27.316] #<filler> So, yeah, I don't want that to be- you know, a
bum-rush fire drill activity. You know, like, "Oh my God, we got to clean up all
the documentation." #<laughter> So, #<filler> 'cause that always sucks for
everybody involved.[30:43.201]
#<Speaker3>[30:43.745] Yeah.[30:43.985]
#<Speaker5>[30:45.745] #<filler>[30:46.369]
#<Speaker5>[30:52.289] Yep, no, appreciate that. #<filler> Yeah, Garrett's behind
me here, writing all over the whiteboard, so.[30:58.117]
#<Speaker2>[30:58.628] You're doing a great job, Garrett.[30:59.889]
#<Speaker4>[31:00.077] #<laughter>[31:05.877]
#<Speaker4>[31:01.896] Trained my whole life for this.[31:03.317]
#<Speaker5>[31:06.142] Oh, so that you guys know, we probably- I- #<unintelligible>
haven't told you, but #<filler> we're separating from Iron Logics, our- our managed
services provider.[31:17.418]
#<Speaker2>[31:17.847] Okay.[31:18.218]
#<Speaker5>[31:21.317] Irreconcilable differences, I believe is the politic term
for that.[31:26.100]
#<Speaker2>[31:26.407] Okay.[31:26.570]
#<Speaker5>[31:27.109] #<laughter> So, #<filler> so yeah, so we're taking control
of- of everything, so Steven, when it comes to Teleport, or anything else that
meant, #<filler> send it my way. 'Cause we'll have- we have internal control over
all that good stuff now.[31:47.917]
#<Speaker2>[31:48.033] That's nice. Cool.[31:50.288]
#<Speaker5>[31:53.346] I think we might have had enough technical brains kicking
around here that we don't need another MSP for a while.[32:00.616]
#<Speaker2>[32:02.596] That makes sense.[32:03.074]
#<Speaker4>[32:03.728] Yep.[32:03.914]
#<Speaker5>[32:07.482] All right. What do you need?[32:09.234]
#<Speaker7>[32:10.228] #<filler> I- #<filler> so, in our past conversations about
documentation, I felt like we've been speaking past each other with the expectation
of like, "All right, to what level do we need the documentation?" And there is this
disconnect of like because y'all are primarily taking up the position at least
temporarily, as cloud architects,[32:36.943]
#<Speaker7>[32:37.321] #<filler> that the- where that knowledge sits inside your
head, there's a bit more of a barrier than if somebody was here in the office. But
even if somebody was here in the office, leading that up, there would still be an
expectation for #<filler> written documentation.[32:55.182]
#<Speaker7>[32:56.022] #<filler> Now here, the level of documentation as required
of us, is so that one, if somebody who was not in the room when all of that was
created, could they, without your help, person, or any persons who made the
documentation, follow it to be on-boarded themselves?[33:16.004]
#<Speaker7>[33:16.703] #<filler> And that's- now that sounds extensive, but it's
also- well, it is, but it's also through that effort,
that- #<filler> that you're able to vet and put out there exactly what has
happened.[33:33.425]
#<Speaker7>[33:33.646] #<filler> And there is a mutual responsibility by all
parties involved, take ownership of the documentation, update things when they can,
#<filler> or notify people that- who know more than them, some of that is self-
admitting that you know, "Oh, I can't fix this," or "I don't know the specifics
about this," to then reach out to another person #<filler> to help update that. But
#<filler>[33:58.441]
#<Speaker2>[33:58.942] so one of the hurdles that we encountered yesterday was you
know, the stuff to do with the environment- environmental files #<filler> on top of
all the- the missing file in the repository. But when we're standing up the
#<filler>[34:18.629]
#<Speaker7>[34:19.739] thing on our local machines are on Zoom call with the
subcontractor standing something up on their machine, #<filler> so that they can do
something that they're expected to deliver on within a span of two weeks, most of
the time that meeting happening somewhere during the fern- front cap that first two
weeks, #<filler>[34:41.171]
#<Speaker7>[34:42.254] we need to be able to dictate are we able to use the
environmental file or environmental parameters that you need. Now obviously,
there's security around keeping those behind closed doors, so the documentation
that I would like to get from y'all is to equip somebody like me, who's a non-
expert to be able to dictate and draft up the correct environmental variables
#<filler> for a perso- bringing in a person, 'cause[35:10.845]
#<Speaker7>[35:11.346] I was explaining actually to Jerry today the development
site, this parallel development, as we're calling it. #<filler> Now, this would be
a helpful time if you could actually see the whiteboard, but #<filler> as we found
out with the whiteboard behind you all, that is not really possible.[35:28.802]
#<Speaker3>[35:28.861] Yeah.[35:29.381]
#<Speaker8>[35:28.861] Yeah.[35:29.381]
#<Speaker7>[35:29.501] I can't see anything on there. Y'all can't see anything up
here. #<filler> Sort of thing. But #<filler> if you break down the entire- both on
the SASS end and the data end and professional service end, you break down
everything that we do into #<filler> essentially a hierarchy down to features and
subfeatures,[35:52.486]
#<Speaker7>[35:53.004] and there's other terms for things smaller than that, but
let's leave it at that. #<filler> With this- #<filler> following the scrums
#<filler> development cycle, everything- everybody or every feature and subfeature
assigned its owner.[36:10.014]
#<Speaker7>[36:10.665] And within the two weeks, you may have something that during
the previous sprint planning, you were assigned to take a PRD that you've been
working on, and move it forward. But while in parallel to that, you're looking at
your other ownership assignments, and being generative and drafting out the next
iterations of those.[36:30.881]
#<Speaker7>[36:30.944] So that when it comes to decide what's going to be in the
next production release for that two weeks, what's going to be- well, you have been
walking what is now going to be sprinted to finish on call finish line[36:44.654]
#<Speaker2>[36:45.200] Yeah.[36:45.480]
#<Speaker7>[36:45.547] #<filler> So, I'm sorry I forgot where I was going with all
of that. #<filler> I apologize y'all.[36:55.138]
#<Speaker3>[36:55.430] Creating detailed documentation. #<filler> And you- and you-
you wanted, which one of the things I've said in the beginning of the meeting, that
we wanted #<filler> a documentation on how to add/replace environment variables
based on the envi- well, we base on the stage, whether that be QA #<filler>
staging, pre-prod, prod. [37:15.895]
#<Speaker7>[36:57.457] Yes.[36:57.855]
#<Speaker7>[37:16.585] Yeah.[37:16.978]
#<Speaker3>[37:17.277] Yeah, that's one of the- that's one of our items to
#<filler> get that to you as soon as possible.[37:21.847]
#<Speaker7>[37:22.582] Yeah. #<filler> Yeah, as well as- so you all have been
looking into this, the whole architecture of our platform that Kiwi has made, and
I've been noticing some things and communicating it to us. But one of the things
that's been missing is a document or a diagram, at least that I haven't
seen[37:42.979]
#<Speaker4>[37:43.619] of all of that, so that not only are you communicating to us
and we're understanding existent conversation, there's also something to look at.
Both in terms of pictures and parts.[37:54.326]
#<Speaker7>[37:55.065] #<filler> So- yesterday I realized my own shortcomings and
not communicating that to y'all adequately. So I wanted to take a moment during
this meeting to in hopes stop this whole speaking past each other and #<filler>
communicate that to y'all.[38:13.030]
#<Speaker3>[38:15.841] Yeah, I mean it-it makes total sense to- to us and we'll
just make sure going on forward, the- the documentation is in- in detail and in
depth to what you guys need.[38:26.868]
#<Speaker5>[38:28.032] All right.[38:28.338]
#<Speaker3>[38:28.599] Obviously, there's going to be a big back and forth on that
as well, because we- we write documentation mostly from #<filler> a different
perspective. And if you need something more detailed, you can say like, "Hey, can
you give more instructions on how to do this?" And we'll- we'll be more than happy
to #<filler> add it to that.[38:47.434]
#<Speaker7>[38:48.175] Mm-hmm.[38:48.537]
#<Speaker3>[38:49.021] Okay.[38:49.230]
#<Speaker4>[38:49.883] So, are you looking for- right now, an updated architecture
diagram? Is that what I'm hearing you say?[38:55.117]
#<Speaker7>[38:56.218] #<filler> That's one of the bits. So again, what I was
writing earlier before I was writing in pink, I was writing and blue, is like, "All
right, so what exactly is the documentation that at least from my perspective, I
think I need in order to talk to somebody who knows nothing about our platform?
Make them from zero to hero quite literally terms of understanding landsuite in an
hour."[39:18.880]
#<Speaker7>[39:19.801] #<filler> At which would normally be what we'd consider a
completely onboarding meeting for the subcontracted developer that for this
specific feature, for them to #<filler> develop to the next iteration.[39:36.243]
#<Speaker7>[39:37.105] #<filler> And that is- so there's four docking, I guess
large letters that I've created, and that's the onboarding, the architecture, test
is then pushed production. Underneath onboarding, I put the- also, the zero to
hero, #<filler and that's frontend, backend then grouped together staff and
connecting the databases.[40:04.567]
#<Speaker7>[40:05.260] #<filler> And then in- under architecture, was the
diagram/locations #<filler> you know, where are things in the cloud and in what
cloud #<filler> if they're not on AWS. Where is it.[40:20.264]
#<Speaker4>[40:20.893] #<filler> Address/access information. All right, well, now
that I know where it is, how do I get access to it? And who do I need to talk to,
or what files behind security firewalls do I need to go to?[40:33.756]
#<Speaker7>[40:34.514] #<filler> And then, the environmental stuff for #<filler>
determining how to configure the environmental file, so that when you stand
something up locally, things work. And you can actually go about testing it and
then the testing documents, and the push to production documents.[40:54.752]
#<Speaker7>[40:55.137] Please- in my mind, that's was- like what I needed.
#<filler> I was- you know, putting myself in the hypothetical- hypothetical
position of, "All right, I'm talking to somebody about bringing them onto this and
going through this process in two weeks. What do I need with my current knowledge
in order to best steward them through that?[41:16.385]
#<Speaker4>[41:18.830] Okay. Yeah, I'm following you. Do you mind #<filler> taking
a photo of what you have on the whiteboard and sending it to us? I just don't want
to lose all those details that you just went through.[41:28.044]
#<Speaker7>[41:28.835] Absolutely. I'm gonna go grab my phone. I don't have it on
me.[41:32.141]
#<Speaker4>[41:32.661] Okay. #<laughter>[41:33.483]
#<Speaker7>[41:37.110] It's all making sense to you guys too?[41:38.368]
#<Speaker2>[41:39.041] Yeah.[41:39.161]
#<Speaker6>[41:39.401] Yeah.[41:39.641]
#<Speaker7>[41:56.745] #<filler> Also, if y'all see holes in there, or feel like
I'm double dipping in areas with the way I've broken it up, this is an open
invitation to say, "Hey Garrett, #<filler> that's not how that works," or "That's
not how it should be,"[42:14.369]
#<Speaker7>[42:14.635] you know, 'cause we also #<unintelligible> we had the
conversation about," All right. Well, what should be- what is- #<unintelligible>
standard for amongst developers," so you- one of the things you pointed out to me
that I was not aware of, was the #<filler> documentation that was actually
underneath the repositories in GitHub.[42:35.970]
#<Speaker7>[42:36.483] And #<filler> have been going through that discussion of,
"All right, should stuff be there? And if it is supposed to be there, what is
supposed to be there?"[42:48.975]
#<Speaker3>[42:49.464] Just the- just the installation and setting up instructions.
[42:53.144]
#<Speaker7>[42:54.168] I'm sorry, say that again, I got distracted.[42:56.727]
#<Speaker3>[42:57.257] Just the installation instruction and basic instruction on
how- what you need in order to run this code. #<filler> Explanation of the code,
business logics, workflows, it can be on conference.[43:11.458]
#<Speaker4>[43:03.988] Okay.[43:04.751]
#<Speaker4>[43:11.900] All right.[43:12.332]
#<Speaker7>[43:36.378] Okay. And the blue marker did not come out very well on the
whiteboard, so let me know if I need to rewrite that in the image of- it's got a
lot of marker residue, so it's not adhering very well.[43:49.099]
#<Speaker5>[43:53.223] Well, there's also the handwriting to cite for an issue. If
so, in which case, yeah, you might need to just type that up.
#<laughter>[44:02.022]
#<Speaker7>[43:58.456] Why are you got-[43:58.978]
#<Speaker4>[44:02.137] I can decipher it.[44:03.274]
#<Speaker5>[44:03.730] Well, hey.[44:04.342]
#<Speaker7>[44:07.347] Why you got to come after me like that?[44:09.641]
#<Speaker5>[44:09.641] #<laughter> No, this is- this is fine. What you got here.
Thank you.[44:15.566]
#<Speaker7>[44:18.614] Okay.[44:19.054]
#<Speaker4>[44:23.325] Right. Well, #<filler> well, having concluded that topic, I
would like to be make one last note and thank you all for your patience and your
grace towards us #<filler> in all of this. And being so flexible and accommodating.
#<filler> I don't actually-[44:44.707]
#<Speaker4>[44:43.846] Yeah, actually we're happy to help.[44:45.355]
#<Speaker4>[44:45.989] express my gratitude enough in that fact.[44:49.176]
#<Speaker7>[44:49.536] #<laughter> Well, we appreciate y'all as well. Thank you so
much. We're glad that we're delivering some sort of value to you all of course. The
last thing we want to do is you know, the KiwiTech.[44:59.979]
#<Speaker5>[45:00.160] #<laughter> Yes, nobody wants to be there.[45:03.032]
#<Speaker7>[45:03.477] #<filler> At this point, I think you can consider yourse-elf
#<filler> you know, in the scrapbook as like you're- you know, we're talking about
vendors, you're either KiwiTech or Chromeware.[45:15.044]
#<Speaker5>[45:14.297] #<laughter>[45:15.841]
#<Speaker6>[45:14.961] #<laughter>[45:16.504]
#<Speaker4>[45:17.385] Oh, we love to hear that.[45:18.513]
#<Speaker4>[45:20.914] All right. Is there anything else that you all need at the
agenda right now?[45:23.449]
#<Speaker5>[45:24.928] So, Jerry, did you- did you run into issues that you wanted
to-[45:29.496]
#<Speaker6>[45:30.060] #<filler> So, some of the files or on the GitHub
repositories, are those done? Or are those going to be- I know you say you're
updating documentations, is that going to be further updated or is that considered
complete?[45:48.968]
#<Speaker8>[45:52.935] You're talking about Kiwi's #<unintelligible> was that? Look
like the files just through the website. I don't think they're going to be changing
those. Those are just little #<unintelligible> Kiwi.[46:03.192]
#<Speaker6>[46:04.581] Yeah. Because they- you all created #<filler> what,
landsuite stack?[46:08.425]
#<Speaker8>[46:08.850] #<filler> Well, that's what we were talking about yesterday.
Correct.[46:11.282]
#<Speaker3>[46:11.968] Yeah, it's- so landsuite stack is missing- well, not
landsuite stack, but landsuite frontend is missing a file called Dockerfile.
#<filler> We have that- well, ready now, #<filler> we're just making sure-
#<filler> well, we are just running that file ourselves locally. And just making
sure that's all you guys need and not anything else. So after this meeting, we'll
just send that over to you.[46:34.296]
#<Speaker7>[46:35.548] Okay. So, when I make my way through the complete setup,
I'll take notes and we'll see if everything is easy for onboarding.[46:46.897]
#<Speaker3>[46:47.429] Yeah.[46:47.861]
#<Speaker7>[46:52.006] And #<filler> Jerry Mack knows a little bit more of what
he's doing and I do, so, take comfort in that.[46:58.682]
#<Speaker6>[46:58.866] #<laughter>[46:59.937]
#<Speaker7>[47:01.884] Well, Jerry, you're going to be our guinea pig for now. This
onboarding process.[47:05.943]
#<Speaker6>[47:06.259] I- I've already heard that.[47:08.043]
#<Speaker5>[47:07.896] #<laughter>[47:08.962]
#<Speaker2>[47:11.072] So from our end, don't be afraid to- #<filler> to tell it
like it is.[47:16.402]
#<Speaker6>[47:16.669] Yeah, okay. Yeah, I'll be in the #<filler> Slack. I was- I
was added to the Slack, so I'll be in there.[47:23.700]
#<Speaker2>[47:24.296] Okay.[47:24.732]
#<Speaker4>[47:31.258] All right. Well, we don't have anything else on our agenda
from our end, #<filler> so I think we're all set. If y'all are.[47:39.120]
#<Speaker8>[47:41.460] Are we all set?[47:42.395]
#<Speaker5>[47:42.500] Are we?[47:43.024]
#<Speaker6>[47:43.463] That's all I had.[47:44.766]
#<Speaker5>[47:45.026] All right. Cool![47:48.261]
#<Speaker4>[47:48.533] Cool. All right.[47:49.669]
#<Speaker5>[47:49.909] We'll give you 15 minutes of your life back.[47:51.941]
#<Speaker7>[47:52.070] #<laughter> All right, thank you all for your time as
always, we really appreciate it.[47:57.001]
#<Speaker5>[47:57.225] Thank you. #<filler> Yep, ever forward.[48:00.095]
#<Speaker7>[48:00.301] All right. Great to meet you, Jerry.[48:02.139]
#<Speaker6>[48:02.576] Nice to meet you too.[48:03.498]
#<Speaker7>[48:03.851] Bye.[48:04.506]
#<Speaker3>[48:04.502] Bye.[48:04.861]
#<Speaker5>[48:04.916] Bye.[48:05.348]
#<Speaker6>[48:05.705] Bye. [48:06.064]
#<Speaker5>[48:07.625] You wanna hang up?[48:09.049]
#<Speaker3>[48:08.952] Oh, yes.[48:09.732]