►
From YouTube: configure team meeting - 2020-12-09
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).
B
C
C
C
D
D
Sure
so
I
have
been
designing
the
state
file
versions.
Diff.
Has
anyone
seen
the
review
I
had
with
matt
the
design
review?
Thank
you.
Justin.
B
I
I
chatted
with
matt
about
it,
so
I
guess
I
heard
it
directly
from
him,
but
okay,
not
watched
or
seen
anything.
D
Okay,
well,
I
posted
the
video
in
the
agenda
in
case
anybody
wants
to
view
it.
Since
then
we
had
one
more
sync
yesterday,
because
it
was
still
hard
for
me
to
decide
that
this
design.
So
let
me
share
my
screen
I'll
try
to
present
it
as
less
confusing
in
as
less
confusing
way
as
I
can,
but
basically
the
whole
page
has
there
were
three
levels
we
needed
to
decide
on
three
design
decisions.
D
D
Sorry
well
and
two
versions
of
filters
so
filters
where
you
can
filter
by
all
changes
created,
update
deleted,
and
then
you
can
see
the
resource
that
correspond
to
the
change.
The
second
one
was
dabs
and
the
third
one
was
a
very
complex
indentation,
where
you
would
have
one
component
one
container
and
then
all
the
resources
that
corresponded
to
this
type
of
change.
So
the
current
decision,
from
myself
and
victor,
is
to
go
with
the
filters,
and
it's
the
simplest
before
I
I
should
have
said
before.
D
I
started
that
the
requirement
from
user
testing
was
that
this
page
is
as
similar
as
possible
to
the
mr
page.
So
this
is
why
I
went
for
the
mr
page
design
so
going
back
to
the
problems.
The
second
problem
is:
how
do
we
display
the
diff?
D
The
actual
diff
matt
has
proposed
a
few
presentations
in
the
issue,
so
feel
free
to
go
there
and
check
out
the
original
discussion.
So
his
thinking
was,
if
we
just
do
a
div,
we
will
see
many
irrelevant
changes,
because
there
is
a
whole
lot
of
hierarchy.
D
D
But
his
formal
proposal
was
to
parse
the
name
of
the
resource
and
then
below
add
for
created
a
block
of
things
that
were
created
for
this
resource.
So
there's
no
comparison
in
this
case
for
updated
just
the
thing
that
was
updated
for
a
resource
and
not
the
other
lines
within
the
hierarchy
and
for
deleted
similar
to
created.
D
However,
discussing
well
designing
the
diff,
I
was
thinking
that
this
parsed
view
would
remove
the
line
numbers
because
we
are
taking.
We
are
basically
creating
our
own
div
and
then
I
started
wondering
whether
users
are
interested
in
the
the
fact
that
this
is
resource
122
instance
0
and
attribute
well
or
attribute
an
attribute
size,
or
do
they
just
care
about
this.
D
So,
while
I
was
preparing
a
final
recommendation
for
the
nbc,
I
realized
that
I
should
have
a
view
of
the
diff.
D
If
you
just
run
the
diff,
we
have
we
run
for
the
code,
so
I
was
going
to
propose
to
use
the
simplest
div
as
a
starting
point
and
then
try
to
parse
if
needed
and
then
maybe
enhance
the
function
I'll
give
this
page
by
providing
two
ways
to
view
it
like
with
a
json
diff
or
the
parsed
view
that
we
created
for
the
user.
D
However,
while
I
was
thinking
to
propose
the
simplest,
mvc
and
simplest,
if
I
was
like
what
is
this,
I
don't
know
what
how
it
would
look,
so
I
reached
to
matt
to
show
me
and
we
basically
didn't
get
into
the
showing
part
as
we
discovered
there
are
many
things
we
don't
know
if
they're
possible
and
how
much
effort
they
would
need.
D
Also,
there
is
a
component
of
the
page
that
I
haven't
showed
you
so
similar
to
vmr
page.
There
is
a
tree
view
here.
So
much
use
case
was,
if
you
have
thousands
of
changes,
this
view
does
not
really
allow
you
to
review
them.
So
you
need
a
more
concise
way
view.
So
the
proposal
is
to
group
either
modules
or
resource
types,
or
both
I'm
not
very
clear
on
that,
and
you
have
the
ability
to
also
search
for
resources.
D
So
then
ma
told
me
that
he
doesn't
know
what's
easiest
and
what's
possible
and
that
we
the
best
way
to
approach
it,
would
be
to
do
a
poc
so
which
diff
would
be
easier
for
us
to
implement
how
easy
or
hard
it
is
to
add
the
line
numbers.
D
If
we
go
with
the
design
that
we
show
the
json,
then
sorting
by
type
of
change,
so
users
said
they
want.
The
resources
sorted
by
created,
deleted,
updated
or
in
some
grouped
by
the
type
of
change
depends
on
the
way
we
diff
them.
D
Then
matt
was
wondering
the
performance
of
the
page,
which
type
of
diff
will
provide
the
best
performance
and
what
needs
to
happen
on
the
client
side
and
what
needs
to
happen
on
the
server
side
and
then
finally
investigate,
on
the
left
hand,
side
the
tree
hierarchy
if
we
can
actually
show
folders
for
modules
and
resource
types.
D
So
I
discussed
this
briefly
with
victor
and
I
said
that
parts
of
the
page
we
can
start
working
on.
But
then
the
actual
content
will
depend
on
the
poc.
So
the
issue
is
blocked
by
the
poc.
A
So
this
mvc
is
not
a
version
diff.
You
still
have
to
go
in
there
and
see
somewhere
find
out
the
way
to
to
get
the
the
change
values
you
you
just
have
here
the
change
resource
names,
so
I
would
rather
have
the
mvc
to
have
a
pure
diff
of
the
two
jsons
without
any
special
formatting
or
anything
like
something
I
could
get
on
various
online
services
as
well.
D
I
agree
that
satisfy
is
more
the
use
case
of
troubleshooting,
but
it
depends
to
what
level
the
users
want
to
see
changes
so.
D
Before
I,
I
think
I
should
mark
this
issue
blocked
and
create
an
issue
for
a
poc,
and
these
two
can
happen
well,
not
in
parallel,
but
we
cannot
make
any
decisions
for
the
actual
content
and
the
poc
could
involve
what
victor
just
said.
Just
the
simplest
diff.
B
That's
a
completely
different
poc,
though
right
because,
like
the
poc
that
we
were
discussing
before
would
be
actually
approaching
some
of
these
harder
questions
that
we
want
to
be
able
to
answer.
B
I
think,
like
differing
two
json
files
is
trivial,
so
we
I
mean
we
can
poc
that,
but
I
don't
know
what
what
does
that
tell
us.
A
B
I
mean
if
for
iteration
one
we
want
to,
I
I
feel
like
we've
done
a
lot
of
work
and
and
researching,
and
so
like
I
wanna,
I
wanna
honor
that,
but
I
I
feel
like
if
for
iteration
one
we
just
want
to
do
a
json
diff.
B
I
can
understand
why
we
would
do
that
while
we
follow
that
up
with
a
more
complex
and
usable.
A
D
That
leaves
me
with
a
question:
are
we
gonna
have
line
numbers?
If
we
just
do
a
diff?
I
I
haven't
seen
one
like
what
is
returned
so
yeah.
What
do
we.
B
I
spoke
with
matt
a
little
bit
about
this.
A
lot
of
this
yesterday.
It
sounds
possible
to
do
to
get
the
line
numbers.
It
does
add
complexity.
So
if
we're
talking
about
the
most
basic
easiest
thing
to
get
out
the
door,
I
would
say
we
would
not
have
line
numbers
originally.
D
Sorry,
this
is
a
grouping.
Also,
users
want
to
group
the
resources
by
module,
if
possible,
which
is
another
enhancement,
so
the
feedback
from
craig
was.
If
we
enable
expansion,
display
and
change
lines,
numbering
becomes
significant
if
we
forgo
expansion
and
display.
Only
this
line
numbers
are
relevant.
B
F
Sometimes
there
are
arrays,
though,
which
will
have
like
kind
of
indexes,
but
it
would
still
be
visually
represented.
I
think.
B
So,
for
my
conversation
with
matt
and
obviously
I'd
prefer
that
he
speak
about
it,
but
it
sounded
like
he
wasn't
sure
if
this,
mr
diff,
that
if
the
code
behind
it
would
even
be
usable
depending
on
now
that
may
have
been
in
reference
to
the
more
complex
presentation
that
we're
proposing.
B
I
don't
know
about
the
simple
presentation:
it's
just
the
json
diff,
but
it
sounded
like
it.
It
would
just
be
we'd,
be
rewriting
or
writing
our
own
diff
code.
D
D
Well,
I'm
happy
to
move
forward
with
the
diff
if
I
have
a
screenshots
of
the
state
like
a
pure
state,
if
jason,
if
or
if
you're,
okay
moving
forward
with
the
issue,
I
can
just
use
placeholders
as
well
in
here.
A
A
Okay,
now,
just
from
the
design
point
of
view,
said
because
you
are,
you
are
right
now
designing
these
and
I'm
more
than
if
it
from
design
point
of
view,
makes
sense
to
to
have
designs
in
the
mr
in
the
same
figma
file
and
whatever
then.
C
A
Sure,
okay,
in
this
case,
what
I
recommend
is
yeah,
let's
open
files
for
the
pocs,
but
at
the
same
time
for
the
mvc,
I
would
just
go
forward
with
the
simple,
the
simplest
possible
json
div
and
we
still
need
some
kind
of
different
use.
I
I
think
we
we
probably
can
provide
something
like
green
red
for
the
4d
lines.
A
C
It
kind
of
depends
like
if
we're
just
going
to
use
the
terraform
plan.
It
sounds
like
the
data.
C
D
A
A
It
might
happen
that
at
the
end
we
can
get
to
something
similar
based
on
the
designs
here
that
you
have
created,
etc,
but
at
the
beginning
I
would
expect
that
this
will
differ
a
lot
because
for
the
plan
we
can
from
the
very
beginning
make
structural,
because
that's
what
drawform
provides
us
as
well,
but
here
for
the
state
for
the
mvc.
I
really
would
just
go
with
the
simplest
json
5d,
and
then
it's
up
to
the
user
to
figure
out
what
those
things
actually.
A
D
A
I
don't
know
what's
easier
to
start
with,
but
you
were
correct.
I
would
say
that
we
need.
We
don't
need
these
elements
for
the
mvc
in
terms
of
the
commit
list
choice.
D
A
A
I've
made
the
deprecation
note
for
this
release
post
about
gitlab
managed
apps.
I
had
a
discussion
with
tong
this
morning
to
to
clean
up
some
of
the
details
that
I
had
questions
around
and
I've
created
a
video
as
well.
If
you
want,
I
can
post
it
in
in
the
in
our
channel
as
well.
I
post
it
in
the
what's
happening
at
gitlab,
so
people
can
provide
us
feedback
if
there's
something
that
they
are
worried
about
as
we
deprecate
these
things.
A
The
basic
idea
is
that
we're
going
to
duplicate
v1
and
for
v2.
We
see
what's
what's
going
on
there,
because
we
might
just
say
that.
Okay,
this
is,
if
you
don't
have
nginx
ingress
instead,
yet
then
this
is
an
option
for
you,
but
it's
not
something
that
we
want
to
to
push
forward,
because
the
discussion
with
tong,
what
my
takeaway
is,
that
really
want
to
allow
our
users
to
bring
their
own
installations
to
gitlab.
A
This
is
what
we
discussed
when
we
started
the
whole
agent
topic
and
seemingly
we
miss
basically
an
api
to
set
up
these
integrations,
and
even
the
ci
based
setup
could
use
this
api.
If
we
ever
moved
to
that
direction,
but
john
went
through
the
limitations
of
that
and
and
what
we
should
figure
out,
so
basically
we
would
just
deprecate
v1
apps.
A
We
would
create
the
api
where
people
can
register
the
apps
that
they
have
nginx
installed,
and
this
is
how
you
can
find
it
and
the
ci
ci-based
apps
would
leave
there
if
somebody
wants
to
use
it
to
get
started,
but
we
wouldn't
focus
on
that
much
we
might
attach
to
the
api.
But
that's
all
do
you
have
anything
any
questions
around
this
or
anything.
You
would
like
to
to
comment
on.
E
A
Yeah
this
is
this
is
so
this
this
might
not
be
related
to
v2
actually,
but
just
to
the
api,
as
you
mentioned
in
the
first
half,
I
don't
know
if
you
want
to
keep
that
ui.
What
we
have
today
or
use
the
integrations
ui
under
settings
integrations,
because
if
I
think
about
prometus
integration,
I
would
say
that
we
have
the
api
for
that.
It's
yeah.
A
Settings
integrations
so
I
don't
know
about,
I
don't
have
an
opinion
about
dui,
but
I
would
say
that
the
ui,
as
we
know
it
today,
would
go
away
and
they
might.
We
might
build
a
ui
that
shows
parts
of
the
integrations
page
or
something
like
that.
B
Yeah
I'll
just
segue
for
victor
there
he's
he's
going
to
meet
with
the
american
bank
of
the
west
about
the
kubernetes
agent.
So
sorry
he
had
to
jump
out
there
were
there
any
more
questions
or
concerns
about
deprecating,
gitlab
managed
apps.
Anything
that
we
hadn't
captured.
F
My
only
thought
was,
I
heard
a
lot
of,
I
think,
talking
about
being
like
some
sort
of
a
top
level
thing
we
need
to
know
about,
but
I'm
just
not
sure
we
even
need
that
I
don't
like
unless
we
have
some
new
features
built
by
release,
which
actually
might
be
the
case,
then
I
don't
know,
I
don't
think
we
have
any
strong
dependency
on
nginx
being
present
in
the
cluster
or
something
we
need
to
really
actually
think.
B
About
yeah,
I
I
I
do,
I
do
remember
there
being
a
set
of
managed
apps
that
we
were
going
to
retain
for
now.
This
was
based
on
the
conversation
we
had
with
sid.
I
think
nginx
was
it's
like
engine
x
prometheus.
B
Yes,
we
had
runner
prometheus
nginx.
I
think
that
was
one
more
I'm
blanking
on
it.
I
think
we're
going
to
continue
supporting
those
for
now.
So
that's
where
I
I
feel
like
we're
announcing
that
we're
going
to
deprecate
them
all,
but
I
don't
know
that's
actually
the
case.
I
think
we're
like
things
are
going
to
be
shifting,
so
there's
certain
ones
that
we
will
support.
B
I
believe
so
anything
else
there.
Thank
you
emily.
B
B
Yeah
yeah,
I
think
I
think
that
is
the
plan
we're
trying
to.
I
believe
the
idea
is
to
try
to
shift
towards
a
new
pattern
of
deploying
these
apps.
We
haven't
decided
what
that
is.
I
know
there's
been
a
number
of
previous
conversations
about
what
it
could
be,
but
until
that's
decided,
we
have
a
road
map,
we're
kind
of
creating
creating
the
direction
like
directionality
towards
that
new
new
version
of
this
by
getting
rid
of
the
ui.
B
Concerns
all
right
just
got
a
few
other
random
announcements,
just
a
friendly
reminder
to
take.
Take
a
look
at
the
engineering
week
in
review.
I
think
that
there's
been
some
questions
on
how
many
people
are
actually
reading
it.
This
is
specifically
for
the
engineers
maria,
if
you
want
to
take
a
look
at
it
by
all
means,
so,
for
example,
reminder
to
install
jamf
one
of
the
things
that's
in
there
so
and
as
well.
We
have
an
ongoing
security
issue
well
with
the
terraform
plan
artifacts.
B
This
is
a
very
old
thing
that
we've
known
about
that
security
actually
went
through
five
months
ago
and
gave
us
recommendations
and
we
implemented
those
recommendations.
But
now
it's
kind
of
come
up
again.
So
if
you
want
to
check
out
that
issue
by
all
means
we're
trying
to
figure
out
how
to
implement
a
stop
gap
and
then
matt
and
tiger
are
trying
to
implement
a
real
solution
to
the
problem.
B
B
Yeah
friday,
the
18th,
so
that
was
so
because
because
of
where
it
landed
and
how
our
releases
work
is
that
they're
kind
of
working
on
it
from
the
17th
through
the
22nd,
so
it's
like
some
people
wouldn't
be
able
to
take
the
day
off
so
they're,
giving
more
time
to
prepare
the
release.
I
don't
know
friends
and
family
day
in
january.
I'm
sorry
I'm
blanking
on
when
that
is,
but
if,
if
it
did
fall
within
that
time
period,
I
bet
that
they
would
do
the
same.
B
But
in
terms
of
budgeting
for
the
holidays,
I
think
for
the
next
milestone,
we'll
probably
just
try
to
do
less.
I
think
that'll
probably
be
the
the
reality.
B
D
Just
wanted
to
give
an
update
and
it
has
to
do
with
a
planning
of
13.8.
And
since
I'm
out
for
two
weeks,
I
will
plan
only
one
issue
or
a
big
issue
and
a
small
issue.
But
I
just
wanted
to
also
update
you
on
my
holiday.
B
Okay,
yeah,
I'm
I'm
planning
to
be
out
between
christmas
and
new
year's.
Also,
so
I'm
sure
you
know
if,
if
anyone
wants
to
take
that
time
off
or
or
any
time
up
just
by
all
means,
do
it
so
we'll
just
try
to
do
less
in
the
next
milestone.
Even
even
this
milestone,
you
know
will
probably
be
scoping
back
a
little
bit.
So
it's
just.
B
So
yeah
just
feel
free
to
update
what
is
a
pto
pto
by
roots
now,
and
it
will
kind
of
coordinate
there
and
then
in
terms
of
milestone,
planning
victor,
and
I
will
just
take
a
look
at
and
just
try
to
be
real
about
what
we
can
get
done.
So
anything
else.