►
From YouTube: July 8, 2021 - Ortelius Architecture Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay,
so
today
is
july,
8th
or
to
this
architecture
working
group.
We
have
just
a
few
people
today.
I
think
summertime
we're
running
into
people's
holidays,
so
on
the
general
meeting
on,
I
think
we're
gonna
have
one
on
tuesday
we'll
go
ahead
and
figure
out.
If
this
is
a
good
time,
like
you
said,
jack
is
the
he
had
a
rush
back
from
work
and
stuff.
A
We
have
a
couple
other
folks
that
are
running
into
the
same
thing,
so
we
may
push
this
back
to
a
half
hour
an
hour,
we'll
have
to
kind
of
vote
on
that
at
the
general
meeting.
So
that's
just
a
heads
up
on
that.
Some
things
that
we
have
going
on.
Let
me
drop
the
link
in
the
chat.
A
Everybody
has
it,
I
think,
tracy's
assigned
everybody
in
just
what
we
have
going
on
right
now
is
on
the
service
catalog
side
we're
working
on
the
the
ui
piece.
We
have
a
good
portion
of
the
microservices
for
the
back
end
have
been
completed
or
far
enough
along
that
we
can
tweak
them.
A
There
are
some
new
people
that
are
looking
for
coding,
work
and
I've
been
working
with
them
to
go
ahead
and
get
that
some
of
the
cleanup
done
to
get
everything
kind
of
pulled
together,
packaged
up
and
ready
to
go
for
the
service
catalog
release
and
where,
where
I
can
pull
it
in
for
the
front
end
and
hook,
everything
together,
so
some
of
the
pieces
on
the
service
catalog
that
are
kind
of
that
we're
working
on
that.
So
is
we're.
A
Looking
for
a
javascript
library
for
this
to
present
the
swagger
json
file-
and
I
believe
we
have
found
one
budakarsh
is-
is
that
that's
what
you're
working
on
right,
you're
doing
a
poc
on
that.
B
A
Perfect,
so
I
did
add
in
the
readme
to
that
we
did
make
a
decision
to
go
ahead
and
store
some
of
these
files,
like
the
readme
file,
the
the
swagger
file,
some
of
the
license
information
in
the
ortelius
database
to
make
just
rendering
and
persisting
things
a
lot
easier
than
running
into
cross
domain
urls
and
having
to
deal
with
you
know,
iframes,
just
to
make
it
a
a
better
implementation.
A
Also,
it
gives
us
a
snapshot
of
what
those
files
look
like
at
the
time
the
component
was
created,
so
that's
happening
also
on
the
back
end
side
on
our
python
library
to
go
ahead
and
hook
into
like
a
pipeline
like
jenkins,
that's
being
updated
as
well
to
push
those
that
data
up
into
the
database
through
the
the
new
microservice
apis.
A
So
that's
kind
of
what's
happening
on
the
service.
Catalog
is
coming
along
pretty
good,
so
many
other
things
that
we
are
pulling
in,
and
this
is
what
I'm
working
on
right
now
is
bring
in
all
the
licenses
and
the
cves
that
exist
in
a
container.
A
So
one
of
the
pieces
of
the
service
catalog
is
to
enable
people
to
see
what
are
the
the
cves
and
the
licenses
that
their
containers
actually
has
in
it.
So
part
of
that
is
hooking
in
like
a
cyclone
dx
to
go
ahead
and
scan
the
container
or
python
safety
to
do
some
scanning.
So
there's
a
couple
issues
out
there
around
running
these
scanning
tools
and
being
able
to
get
the
output
from
them
and
push
that
into
into
ortilius
as
part
of
the
the
database.
A
Now
on
that
front,
when
we
talk
about
like
the
cves
we're
just
going
to
provide
a
link
to
where
they
can
go
and
get
the
real
detail
about
the
cve,
you
know
the
you
know
all
the
the
gory
detail
about
how
it
how
it
occurs,
what
how
they
hack
it.
Those
type
of
things
so
right
now
we're
just
grabbing
the
the
cv
cve
number
and
we'll
provide
the
link
to
where
they
can
look
up
the
the
details.
A
On
that
same
with
the
licenses,
the
scanning
tools
will
kick
out
all
the
licenses
that
the
container
has
in
it
and
then
we'll
go
ahead
and
aggregate
those
up
and
provide
a
link
to
where
those
licenses
exist.
If
they
do
so,
that's
kind
of
what's
happening
in
that
front,
it'll
be
nice
to
have
all
this
information
together
in
one
place
it.
Let
me
see
if
I
have
it
running
yeah.
Let
me
share
my
screen
real.
A
So
here
is
a
new
component,
the
map
of
it
we've
broken
it.
A
The
detail
was
getting
awfully
long,
so
we
split
it
into
two
columns
and
then
like
here
is
the
the
readme
file
that
we
brought
in
it's
a
markdown,
so
we're
able
to
render
it
there
was
a
markdown
library
I
found
that
allows
us
to
go
ahead
and
render
it
format
it
in
the
little
box
here
and
then
the
swagger
piece
will
get
plopped
in
here
and
we'll
render
this
the
the
swagger
we'll
have
to
play
with
this
to
see
on
the
the
size
you
know
from
a
ui
perspective
and
then
we're
bringing
in
the
cves
and
the
license
consumption.
A
That's
going
to
be
at
this
point,
so
that's
kind
of
what's
what's
happening
there.
We
did
move
some
things
around.
Some
of
the
mapping
got
moved
down
to
the
bottom
here,
so
we'll
have
to
kind
of
play
around
with
where
we
need
things.
One
of
the
last
architecture
calls
we
had
was
talking
about
creating
some
ways
to
navigate.
A
So
if
you
wanted
to
have
a
get
to
the
cves,
you'd
have
a
tab,
a
button
here
or
something
that'll
jump
you
down
to
that.
Also,
there
was
talk
about
making
these
collapsible
rows,
so
you
could
collapse
this
row
to
get
it
out
of
your
way
as
part
of
that
process.
A
A
So
that's
kind
of
what's
happening
on
the
the
service
catalog
piece
it'll
be
nice
to
have
all
the
detail
that
we're
going
to
be
able
to
grab
for
a
container
and
the
main
focus
is
on
containers
and
not
worrying
about
like
jars
or
ears
or
war
files
for
all,
like
the
swagger
ui
it
you
could
upload
it.
It's
not
going
to
hurt
anything,
but
it
is
our
primary
focus.
A
I'm
sorry
for
the
cves
we're
going
to
be
focused
on
what's
in
the
container,
not
like.
What's
in
the
jar
file,
for
example,
the
so
the
swagger
will
actually
work
for
like
a
jar
file
or
file
as
well
as
a
container.
That's
just
a
an
extra
file.
A
That's
gonna
be
in
the
repo
some
of
the
things
that,
if
anybody
has
any
other
items
that
they
want
to
add
in
such
as
we
had
one
of
our
friends,
who's
working
for
uber
basically
said
that
they
look
at
slos
and
slas
that
type
of
data,
not
sure
how
we
would
be
able
to
bring
in
slo
into
this,
and
how
that
really
looks.
So,
if
you
see
data,
that's
missing
for
microservice
that
we
should
be
tracking
just
go
ahead
and
raise
an
issue
in
the
ortelius,
slash,
ortilius,
github,
repo,
the.
C
A
A
A
So
that's
kind
of
what
is
happening
on
that
front
for
the
service
catalog,
so
oops.
Let
me
get
back
to
the
document.
A
Oh
there,
it
is
so
tonight
at
4.
30
mountain
time
is
we'll
have
another
architecture
meeting
with
the
brad
mccoy
amit
and
a
couple
others
down
in
australia,
they're
working
on
the
get
ops.
A
Solution
for
ortulius
how
ortulius
and
gitops
are
going
to
play
together
also
sergio's
been
attending
those,
so
they're
they've
been
focusing
on
on
the
get
ops
aspect
of
this.
So
if
you're
interested
or
if
you're,
awake
and
interested
that's
going
to
be
at
4
30
mountain
time
today,
we
do
record
those
as
well,
and
I
try
to
put
the
meeting
minutes
in
as
well.
I
missed
last
week's
getting
the
notes
in
here.
A
I
got
that's
one
of
my
to-do
lists
today,
so
that's
kind
of
where
we're
at
for
the
architecture.
We
don't
really
have
any.
Oh
on
the
get
ops
piece
it
did
come
across
on
the
discord
channel.
Some
discussion
about
argo
workflow
so
and
syme
was
trying
to
figure
out
what
that
meant
because
I
sounded
like
it
was
a
big
overlap
with
tecton.
A
So
basically
it
sounded
like
you're
gonna
be
able
to
run
a
workflow
inside
of
kubernetes
and
which
is
exactly
what
tekton
is
doing,
so
it
it's
going
to
be
one
of
those.
I
don't
think
it's
going
to
affect
us.
A
A
So
some
of
the
the
other
for
lack
of
a
better
word
boxes
that
we
want
to
put
out
here
is
you
want
to
put
like
a
box,
probably
with
a
big
giant.
You
know
number
that
says
you
know
100
uptime
or
you
know
zero
errors,
or
something
like
that.
A
So
people
can
understand
the
details
around
the
health
of
the
service.
A
Now
the
tricky
part
is
on
that
and
some
of
the
other
data
that
we're
looking
to
collect
is
being
able
to
take
that
view
not
only
for
what's
running
in
production,
but
also
for
any
any
stage
of
the
life
cycle,
whether
it's
to
be
production,
qa,
uat
or
alpha
testing,
or
even
what's
happening
in
you
know
the
the
developers
world
being
able
to
have
a
view
to
tell
us
the
health
of
those
things,
because
one
of
the
things
when
we
start
gathering
that
information
and
people
see
it
early
on
that
we're
able
to
really
get
some
traction
and
show
some
visibility
not
only
for
what's
in
production,
but
help
sres
and
developer
to
determine
if
they
have
a
problem
like
in
qa.
A
What's
going
on,
you
know:
did
they
just
not
turn
up
the
the
correct
number
of
replicas
in
the
replica
set,
or
do
they
have
a
transaction?
That's
going.
You
know
to
the
other
side
of
the
world
and
coming
back
those
type
of
things
we
will
need
to
capture
like
I
said,
we're
going
to
be
adding
some
more
boxes
to
to
do
that,
processing
as
well.
So
just
a
heads
up
on
that
as
part
of
that
process.
C
Can
you
scroll
down,
you
were
sharing,
I
want
to
make
see
if
the
you
still
have
the
blast
radius
in
there
right.
It's.
C
C
A
Yeah
and
this
one's
a
really
simple,
this
has
just
two
just
two
and
when
we
get
into
mapping
out
when
we
look
at
our
component
set
implementation,
this
will
grow.
B
A
So
you
know,
if
you
look
at
like
on
netflix's
micro
servers
map,
it's
just
a
big
giant
death
star
and
it's
just
not
readable,
and
we
want
to
make
it
usable
for
people.
D
C
D
Steve
I'm
curious
about
something
with
that.
Can
you
make
that
hierarchical
or
or
is
it
more
of
a
like
a
mind,
map
type
feel
like
you:
have
it
now.
A
So
that's
this
point
of
view
that
we're
looking
at
now.
You
can
flip
it
the
other
way
where
you
have
an
application
in
the
middle,
and
then
you
can
show
all
the
consuming
services
that
it's
using.
So
we
can.
We
can
flip
it
any
direction,
and
then
you
can
get
into
an
environment
that
stuff
has
been
deployed
to
and
we
can
see
the
relationships
of
all
the
services
and
how
they're
interacting
in
an
environment.
A
So
whatever
lens
you
know
whatever
direction,
you
want
to
point
the
lens
we
have.
Those
slices
now
like
tracy,
was
saying
when
we,
the
amount
of
data
is,
gets
and
you'll
see
this
in
the
hipster
store
demo
data,
where
we
have
like
14
services,
and
it
gets
pretty
crowded,
really
quick.
So
I
think
that
in
the
upcoming
component,
implementation,
so
components
set
is
where
we
can
group
tightly
coupled
services
together,
and
that
will
be
that
that
will
be
the
representation.
A
And
then
you
can
drill
into
that
to
go
into
the
what
what
are
in
what
components
are
in
that
component
set.
So
it
is
going
to
be
hierarchical
down
the
road
and
also
with
the
domain
driven
design.
We
can
bring
in
like
the
security
domain
and
you
have
like
the
payment
domain
and
those
will
be
mapped
out
as
well.
So
you
can
kind
of
see
from
more
of
a
logical
view
of
how
things
are
kind
of
organized,
and
then
you
can
drill
into
that
that
level
as
well.
A
If
you
have
any
ideas
on
how
to
deal
with
a
huge
amount
of
of
hierarchical
data,
we've
looked
at
a
couple,
different
ideas,
there's
there's
a
couple.
The
one
main
ones
that
we
were
looking
at
was
the
d3s
javascript
library
and
the
other
one
is
viz.
Js
vis.js
are
the
two
primary
libraries
that
we've
looked
at
for
doing
the
rendering
yeah.
A
Okay,
so
it's
the
it's
a
hard
model
to
you
know
one
of
the
things
that
actually
it
sounds
crazy.
But
when
you
look
at
a
world
map-
and
you
have
like
you-
can
drill
down
into
africa
or
india-
and
you
can
do
you
know,
then
you
can
get
into
the
the
the
states
or
the
counties
that
hierarchical
from
a
world
map
perspective
may
work.
You
know
where
we
create
a
world
map
of
the
services
and
you
can
drill
down
that
way.
Just
the
relationships
we're
just
gonna,
we
have
we're.
D
The
tricky
part,
what
about
something
like
the
periodic
table
of
the
elements,
because
you
know
in
the
periodic
table
you've
got
you've,
got
the
metals.
You've
got
the
noble
gases,
you
know
and
they're
kind
of
related
and
they're
together,
and
so
you
can
see
those
relationships
and
then
you
could
drill
farther
down.
That's
just
something
that
popped
into
my
head.
A
Yeah,
that's
that
one's
called
and
I
think
it's
called
an
icicle
hierarchy.
A
It's
either
icicle
or
the
sunburst
hierarchy,
where
you
can
drill
down
any
group
that
level
and
that's
where
the
domain
would
come
in
as
well
to
give
you
that
high
level
grouping
like
gases
versus
metals
and
then
you
could
drill
into
that
from
that
level.
So
we
are
thinking
along
the
same
lines.
A
It's
just
going
to
be
how
we
can
figure
out
the
best
way
to
communicate
what
we're
trying
to
represent
to
people.
You
know.
Sometimes
you
can
make
something
look
really
cool,
but
people
don't
understand
what
the
hell
it
means
exactly.
Yeah.
Sometimes
fancy
is
not
good
yeah.
So
I
think
that's
about
all.
I
have
any
other
questions
for
anybody.
D
D
A
D
Great
so
first
the
software
as
a
service
link
in
the
readme
is
broken.
I
can't
install
okay.
If
somebody
could
get
that
link
fixed,
I
could
move
forward
and
get
a
little
bit
more
detail.
There.
D
A
Okay
and
the
the
so
just
to
give
you
kind
of
lay
the
land
of
of
on
the
back
end
side
or
where
we
manage
everything,
so
everything
is
managed
off
of
god.
If
I
can
find
zoom
there,
it
is
so
the
main
repo
which
is
the
artillery
slash
artelius
repository.
A
So
even
though
we
have
like
20
repositories
for
all
the
different
microservices,
if
we
find
a
problem
like
with
a
microservice,
we
report
it
against
the
the
main
repository
just
so
we
keep
all
the
issues
in
one
place.
It's
just
just
from
a
project
management.
It
makes
it
easier
and
github
will
allow
you
to
go
ahead
and
cross-reference
issues
and
prs
across
repositories.
A
So
that
way
we
can
have
links
in
there
as
per
that
process.
So
if
you
find
an
issue
with
the
documentation,
just
go
ahead
and
you
know
provide
as
much
detail
you
can.
You
know
which,
which
page
it
is
and
go
ahead,
put
the
the
issue
out
there
and
then
there's
a
few
folks
out
there.
That
will
fix
the
you
know,
correct
the
the
documentation
or
you
can
correct
it
yourself
the
whole.
A
D
Okay,
you
might
have
to
run
me
through
that
process
once
if
we
get
a
chance
to
talk
one
on
one.
So
I
can
get
a
better
feel
for
that.
D
The
second
question
I
had-
and
I
just
been,
like
you
know-
kind
of
ruminating
a
little
bit
about
things
from
my
perspective,
which
is
the
perspective
of
an
end
user
and
dealing
with
people
who
are
not
computer
people
and
I'm
wondering
if
there
is
a
place
for
a
demo
that
talks
about
why
you
would
want
ortelius
in
a
completely
non-computer
way
and
just
to
write
it
down
now.
D
A
A
No,
we
always
want
fresh
looks
at
this,
because
we've
been
heads
in
the
weeds
so
long
that
we
miss
things
simple
things
like
that
are
are
missed
all
the
time
because
we're
so
low
level
from
our
perspective.
A
So
yes,
a
now
siddharth
was
working
on
or
had
that
a
similar
idea
around
a
demo
and
being
able
to
structure
that
into
I
don't
know
if
he
tracy
do
you
remember
if
he
was
planning
to
do
youtube's
or
just
like
what
was
his
thoughts
on
the
training
stuff,
yeah.
D
Got
it
right?
Okay,
so
so
I
have
a
question
for
you.
So
tell
me
whether
you
think
this
makes
any
sense
or
not
because
it
makes
perfect
sense
to
me,
but
I'm
me
so
if
you
think
about
it,
the
universe
operates
with
microservices
and
basically
you
know
to
try
and
put
this
in
a
generic
way.
I'm
just
going
to
use
universe,
but
basically
there
are
a
certain
number
of
elements
and
everything's
created
out
of
that,
and
so
those
elements
are
related
and
they've
got.
D
You
know
just
a
little
bit
different
characteristic
that
meets
a
need,
but
the
universe
doesn't
create
a
new
service.
You
know
a
new
element
every
time
it
needs
to
do
something
and
it
uses
the
same
stuff
over
and
over
and
to
try
and
expand
on
that
to
get
people
to
understand
that
microservices
are
really
a
very
logical
way
to
deal
with
things
and
and
kind
of
start
there,
and
I
I
have
a
document
written
up
that
I
threw
together
just
to
kind
of
get
my
thoughts
down
about
that.
D
But
do
you
think
there's
a
place
for
something
that
is
that
far
off
of
you
know
the
computer-related
stuff
for
people
that
you
know,
because,
basically,
in
my
experience,
you've
got
an
awful
lot
of
non-computer
departments
who
will
go?
I
really
don't
care,
I
don't
need
to
understand.
Just
do
it,
you
know
blah
blah
blah
and
the
reality
is
they
do
need
to
care
to
some
extent
they
need
to
know.
What's
going
on
right,
most
of
the
time,
they're
funding
it.
D
You
know,
and
it's
a
way
to
lay
it
out
and
say
you
know
what
this
is
you
deal
with
this
every
day.
This
is
not
a
weird
concept
and
it's
not
way
out
there.
You
know
this
is
literally
how
you
live
your
life
and
put
it
in
those
type
of
terms,
so
that
people
go
oh
well,
that's
why
I
want
it
right,
and
so,
for
example,
just
briefly
with
that
scenario,
ortegas
then
becomes
the
periodic
table
of
the
elements,
because
that's
your
microservices.
D
It
becomes
the
laws
of
physics,
because
it
controls
how
you
can
deploy
those
services
and
how
they
relate
to
each
other.
You
know,
and
it
just
just
stuff
that
everybody
learned
in
middle
school
right
right,
so
you
got
any
thoughts
about
that.
I
mean
is
that
just
too
far
out.
A
Now,
that's
very
similar
to
another
way
that
we've
looked
at
it
the
way
I've
looked
at.
It
is
also
yeah
and
I
kind
of
throw
them
the
map.
If
you
try
to
the
one
thing
that
we
try
to
bring
is
the
mapping
of
the
services,
so
one
of
the
the
another
way
I've
used
to
explain
it
is
around
the
the
planet,
solar
system,
constellations.
A
A
Put
in
there
yeah
yeah,
so
if
you
look
at
if
you
look
at
just
our
solar
system,
so
our
solar
system
is
a
an
application
or
it
could
even
be
just
a
a
version
of
a
component
and
then
how
that
component
has
changed,
with
the
different
functions
being
added.
So
back.
You
know
in
you
know,
1200
that
they
didn't
know
that
pluto
existed
and
you
can
actually
see
the
versions
of
our
solar
system
over
time.
So
how
are
our
component
our
solar
system,
which
would
be
our
component
version?
A
We
have
different
versions
of
of
our
solar
system.
Then
our
solar
system
is
related
to
our
star
as
part
of
a
constellation
and
constellations
kind
of
build
up
into
the
galaxy
and
then
some
of
the
harder
parts.
In
that
metaphor
is
there's
not
a
lot
of
sharing
of
stars
in
you
know.
You
don't
have
two
constellations
that
overlap
and
share
the
same
set
of
stars.
So
that's
where
that
that
metaphor
kind
of
falls
apart,
but
we've
we've
talked
about
something
similar
to
that.
D
Not
that
far
off
yeah
dang.
That
actually
makes
me
kind
of
happy,
because
it
means
that
that
I'm,
in
with
my
peeps.
A
So
the
big
thing
is
when
you
think
about
this
is
everything
in
the
artillious
world
is
versioned?
So
you
have
a
version
of
a
component,
and
component
versions
are
packaged
into
application
versions.
A
We
are
going
to
be
adding
in
versions
of
an
environment
which
is
where
you're
going
to
put
the
application
version
into
so
everything's
versioned,
and
then
because
we
have
these
relationships,
you
get
these
maps
maps
of
relationships.
So
those
are
the
two
main
underlying
concepts
is
versioning
and
mapping.
D
Yeah,
you
know
I
bet
you
could
put
like
a
hubble
metaphor
in
there.
D
Know
basically,
when
you've
got
copernicus
looking
at
things
and
then
you,
oh
yeah,
you
version
it
out
to
this
is
more
detailed
and
more
detailed
and
more
detail
yeah
that
could
that
could
actually
work
for
some
folks.
D
A
Our
and
then
we
have
our
alien
mascot
and
the
reason
why
the
alien
mascot
came
about
because
trace
and
I
are
in
new
mexico
and
we're
famous
for
our
aliens
in
roswell,
but
also
we
have
the
very
large
array
which
you
know,
does
some
really
cool
stuff
down
it.
You
know
looking
at
the
the
cosmos,
so
that's
just
a
kind
of
a
sidebar.
D
Yeah
well
thanks
for
entertaining
me
here
for
a
sec.
You
know,
because
I
have
I
have
to
admit
when
you're
coming
in
brand
new
you
I
I
need.
You
know
personally
the
way
that
I
think
and
the
way
that
I
do
things
I
have
to
have
some
of
that
information
so
that
I
can
align
myself
and
not
feel
like
I'm
too
far
off
the
mark.
A
Yeah
and
then
before
I
forget
so
tracy
syme
is
working
on
some
catacota
trainings
for
linker
d,
so
he
is
learning
how
to
put
together
the
catacota
trainings
great.
So
one
of
the
things
jack
that
we're
gonna,
we're
looking
at
is
o'reilly,
provides
a
framework
for
doing
training
material.
A
So
you
could
do
like
a
little
module.
Then
you
have
a
quiz
to
see
how
you
did
that
type
of
thing,
and
one
of
our
contributors
from
islamabad
is
is
doing
it
for
another
project,
the
that
software.
So
hopefully,
when
we
get
ready,
you
know
when
we
get
into
past
all
the
holidays,
for
everybody
that
we'll
be
able
to
bring
that
in
as
well
the
training
training
in
general.
We
like
to
structure.
You
know
like
a
five
to
ten
minute,
little
section
to
focus
on
stuff.
A
D
Right,
yeah
I've
seen
the
discord
discussions
overnight.
That's
one
of
the
advantages
of
working
nights
is,
I
I
can
see
those
real
time
and
so
yeah.
I
was
kind
of
following
along
with
what
was
going
on.
I
have
to
admit
that
I
don't
know
very
much
about
the
details,
but
at
least
I
could
kind
of
figure
out
what
they
were
doing.
A
Yeah
yeah,
and
if
you
it's
a
great,
we
have
a
really
good
bunch
of
folks
on
this
project.
So
if
you
don't
understand
something
just
tell
them,
can
you
enlighten
me
and
I'll
be
happy
to.
D
Oh
yeah,
I'm
here!
No,
I
don't
have
any
other
specific
questions
right
this.
Second,
what
I
need
to
do
is
I
need
to
get
that
installation
done
so
that
I
can
start
looking
at
the
application
itself-
okay
and
and
move
forward
there.
The
only
other
comment
I
would
have
is
about
moving
the
time
and
you
know.
D
Obviously
you
have
to
work
with
what's
best
for
most
people,
but
I
have
to
admit
that
you
know
when
you're
working
12
and
a
half
hour
shifts
that
this
meeting
eats
into
the
little
bit
of
sleep
time
that
I
have
and
if
you
then
move
it
a
half
an
hour
or
an
hour,
then
that's
even
less
sleep
that
I
get,
and
so
personally
I
would
rather
be
a
couple
minutes
late
to
a
meeting
than
move
it
any
further
than
it
is
now
again.
A
Okay,
we'll
let
you
know
like
I
said,
we'll
we'll
throw
that
discussion
out
there
on
our
general
meeting
as
part
of
that
process.
Utica,
do
you
have
anything
from
your
side?
Are
you
good
to
go.
A
Okay,
excellent:
when
do
you
think
you'll
have
the
the
you
said,
you're
going
to
be
able
to
show
something?
Maybe
today
on
the
swagger.
B
Yeah,
so
do
you
want
to
show
here
yeah.
C
And
jack,
that
might
be
something
you
want
to
you
might
want
to
do
as
well.
That's
what
we're
calling
our
cohorts
for
alerting
really
to
the
ins
and
outs
of
ortillius,
so
that's
just
a
hands-on
kind
of
we
call
it
getting
started.
A
Yeah
so
that
we
can
fit
into,
we
have
some
like
pre-planned
slots,
but
if
you
want
to
just
do
some
hands-on
stuff
to
get
started,
just
grab
a
time
on
my
calendar
that
works
for
you
that
you're
not
sleeping
yeah.
C
D
Yeah
wednesday
is
my
my
first
day
of
the
week,
and
so
we
work
either
three
days
or
four
days
a
week.
You
know
alternating
and
so
the
tuesday
one
would
be
the
one
that
would
be
best
for
me.
Yes,.
B
Okay,
so
basically,
these
files
are
the
static
files,
so
we
don't
need
to
change
anything
so
to
render
any
swagger.
You
know
endpoints
or
any
swagger
files
that
we
have
when
I
say
files,
the
files
can
be
in
the
json
format
or
in
the
yaml
format.
We
just
need
to
change
this
url.
B
So,
first
of
all,
let
me
show
you
how
it
will
get
rendered
using
this.
You
know
sample
url.
B
B
B
A
Okay,
now
on
the
go
ahead
scroll
down
and
what
do
we
have
that.
A
B
Perfect,
so
this
this
is
coming
from
the
the
sample
url.
So
whatever
they
have,
you
know
done
there,
so
that
will
come
exactly.
A
B
Yeah,
so
I'm
not
altering
any
information
any
data
here
coming
from
there.
The
end
points
are
coming
from
there.
A
And
then
go
back
to
the
code,
how
is
it
being
placed
on
the
page
where,
where
is
ui,
how
are
you
placing
it
into
the
right
place
on
the.
B
Yeah,
basically,
these
files
have
been
generated
using
a
swagger
ui,
which
is
a
library,
javascript
library,
so
that
will
generate
you,
these
static
files,
so
once
that
is
generated,
you
just
need
to
take
care
of
this
url
and
arrest
will
be
taken
care
of.
A
Oh
okay,
I
see
right
there
on
line
43,
so
43
is
where
you're
referencing,
where
you
want
it
placed
on
the
page.
So
that's
going
into
that
div
on
34.,
okay,
perfect!
That's
exactly
what
I
needed.
B
D
Just
as
a
comment,
I'm
familiar
enough
with
html
that
if
you
had
grunt
work
that
you
wanted
done
that
you
know
it's
not
worth
a
developer's
time
like
wholesale
changes
to
something
or
you
know
in
certain
texts
and
stuff
like
that,
please
let
me
know
I'll
be
more
than
happy
to
take
care
of
it.
For
you.
B
A
Take
out
the
a
in
the
first
name:
that's
it
perfect!
When
you
get
a
chance.
Yeah
thanks
jack.
Well,
like
I
said
we'll
on
the
like
on
the
documentation.
So
all
of
our
documentation
is
in
markdown
and
it
lives
in
a
repository.
A
It
is
then
put
through
a
process
that
allows
us
to
basically
it's
hosted
through
a
hugo
server.
So
hugo
will
take
the
the
mark
down
and
translate
it
into
html
for
us
and
then
that's
what
allows
us
to
go
ahead
and
do
a
regular
file
based
process
for
changes.
There's
there's
no
like
wordpress
login
or
anything
like
that.
So
it
makes
it
really
easy
to
to
work
through.
Have
you
worked
with
github
and
doing
pull,
requests
and
stuff
like
that.
D
Sorry
I
did,
but
it
was
four
or
five
years
ago
now
and
that's
why
I
wanted
a
little
bit
of
your
time
just
to
refresh
my
my
memory
and
my
ability
to
go
through
there,
because
it
wasn't
difficult.
But
you
know
if
you
haven't
done
something
in
a
few
years:
it's
a
little
hard
to
just
pick
it
right
back
up.
A
Yeah,
so
I'm
going
to
give
you
a
link
here
in
the
chat.
A
Wherever
chat
went
there,
it
is
so
there
is,
so
we
split
our
our
into
two
worlds.
One
is
the
contributor
side
like
how
do
you
contribute
to
the
project?
The
other
one
is
how
to
use
the
product.
So
that
was
what
I
just
sent.
You
is
the
link
to
the
contributor
guide
and
then
there's
the
pr
cheat
sheet
that
will
kind
of
help.
You
walk
through
doing
a
pull
request
and
stuff
like
that.
It'll
jog,
your
memory
awesome,
and
if
you
run
into
anything
I
you
know
just
just
need
some
help.
A
You
don't
have
to
just
grab
me
just
throw
something
out
on
the
general
discord
channel
and
somebody
will
come
along
and
help
you
so
there's.
You
know
we
have
folks
all
over
the
world
like
you're,
watching
everybody
in
in
india
and
pakistan
and
in
australia
last
night
talking
so
and
they're
they're
everybody's
everybody's
really
willing
to
help.
So
we've
taught
people
that
have
never
done
a
pull
request
or
done
any
changes.
There's
a
person
in
poland.
He
does
a
lot
of
our
documentation
stuff.
A
So
got
him
doing
the
pull,
requests
and
he's
the
one
that
actually
wrote
that
pull
request
section
from
from
his
experience.
D
Awesome
thanks
for
entertaining
my
newbie
questions.
There.