►
From YouTube: Design Pair Session - 03-30-2023
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
Foreign,
this
is
the
design
pair
session
on
March
30th
and
today,
we're
going
to
work,
walk
through
the
glossary
to
discuss
deployments
so
I'll
hand
this
off
to
Victor
to
give
an
intro,
and
then
we
can
jump
into
it
after.
B
Yep,
all
right
so
yeah
I
mean
he
asked
me
to
give
an
answer
to
the.
What
is
this
address
deployments
logic
left
about
and
why
we
should
focus
on
it.
So.
A
B
When
we
speak
about
the
delivery
domain,
there
are
some
Core
Concepts,
like
environments
deployments,
releases
artifacts.
Perhaps
you
can
think
anything
around
secure
software
supply
chain.
That's
involved,
and
it's
not
obvious
what
remain
by
all
of
these
words,
especially
when
we
use
them
as
nouns
versus
men
use
them
as
verbs,
and
the
glossary
aims
to
to
have
a
common
vocabulary
for
us
to
discuss.
B
We
started
to
work
on
this
with
Mikhail
a
long
long
time
ago,
and
I
would
even
say
that
we
got
to
a
point
where
we
wanted
to
merge
it,
and
we
thought
that
it
is
good
enough
and
pretty
where
the
stripes
have
imagined
the
best
word
that
we
could
have
Within
gitlab,
but
it
was
just
so
far
away
from
what
gitlab
offers
that
we
never
got
to
the
point
to
merge
it
because
I
was
like
what
is.
B
It
is
probably
a
lot
of
confusion,
When
likely
like
where
would
we
put
it
and
so
on,
and
what
I
would
like
to
do
is
that
we
I
would
like
us
to
focus
first
on
the
glossary
of
how
we
imagine
the
best
possible
how
we
want
to
discuss
that
and
then
describe
as
well
what
git
LAB
Works
today
and
see
how
we
can
later
on
move
the
two
together.
So
that's
the
plan,
and
it
will
basically
help
us
afterwards
to
discuss
any
of
our
topics.
B
B
Don't
know
of
anything
in
this
way,
what
no
I
don't
know
if
anything
like
that
I've
heard
I've
heard
about
from
Philly
I've
heard
that
we
have
now
a
glossary
template
for
documentation,
but
I
don't
know
if
it's
used
and
but
pretty
sure
it
was
introduced
for
reasons
to
somebody
wanted
to
use
it.
But
I
don't
know
if
any
specific
usage
of
it.
A
And
one
other
question
the
ideal
like
intended:
this
is
going
to
be
in
the
docs
right
from
what
I
can
see
in
the
Mr
and
it'll
be
useful
for
both
us
and
our
customers,
so
it'll
be
kind
of
for
both
use
cases
for
us
describe
like
discussing
internal
features
as
we're
building
them
and
then
customers
to
review
if
they
have
confusion
over
our
wordings
for
things.
A
And
then
sorry,
one
other
question:
there
is
a
lot
of
work
done
on
this
and
I
know.
You
said
that
we
kind
of
went
in
a
direction
and
then
stopped
going
forward.
How
do
you
expect
us
to
kind
of
work
through
this?
Is
it
something
we
wanna
take
this
as
inspiration
and
work
from
scratch
or
work
from
this
Mr
to
fix
it
up?
What's
kind
of
I'm.
B
I'm
open
to
either
approach
whatever
you
think
is
the
best
to
to
do
personally.
I
think
it's
a
pretty
good
start.
What
we
have
like
you
guessed,
the
team
who
had
a
bunch
of
comments,
I,
think
back
in
January
so
and
he
could
easily
pick
up
and
and
add
a
piece
of
questions
and
and
topics
there.
B
Yeah,
it's
it's.
It
was
really
always
on
my
mind
to
to
merge
it
just
like
when
we
started
it.
I
very
quickly
realized
that
a
big
part
of
the
scope
is
outside
of
the
domain.
That
I
was
responsible
for
back
then,
and
actually,
when
I
was
the
acting
group,
product
manager
from
September
I
asked
Chris
and
I
think,
together
with
China
to
start
working
on
this
Lottery,
because
then
the
two
released
and
configure
groups
on
the
whole
domain
basically
can't
change
everything.
B
We
know
that
and
but
now
be
the
environment
on
the
domain
and
and
we
can
finally
it's
a
single
hand,
so
to
say-
and
we
can
finish,
the
work
I
think
awesome.
A
So
put
like
a
due
date
into
it,
and
then
I
probably
should
have
invite
invited
Philip
to
this
one
to
this
design
pairing
session
just
to
discuss
this
because
I
feel
like
he'll,
be
a
big
part
of
it.
But
yeah
does
anyone
else?
Have
any
questions
I
know
shinya.
You
worked
on
this
a
little
bit
before
as
well,
but.
C
This
module
gets
that
having
this
poke
apple
is
goes
at
least
in
our
documentation
will
be
good,
but
probably
we
want
to
put
in
a
user
doc
side
not
like
a
development
Dockside,
because
that's
not
surface
for
users
and
then,
like
I,
think
a
picture
pointed
out
that
had
a
good
point,
that
these
stocks
should
have
her
overview
of
police
and
configure
stages,
so
it
should
be
like
it
should
contain
more
like
overview
stuff,
for
example.
C
Okay,
this
is
a
documentation.
I
was
writing,
said
from
that.
C
Architecture,
so
when
this
documentation
the
intends
to
explain
like
how
deployment
workflow
works
with
these
blockable,
at
least
like
you
know,
there's
artifacts,
there's
releases,
there's
application
these
all
vocabul
user
defined
nicely,
but
we
it's
kind
of
hard
to
wrap
up
like
how
these
are
connected
like
how
this
is
going
to
be
projected
into
gilab
project
project
architectures
like
how
users
should
organize
their
Gila
projects.
Something
like
that.
So
I
was
wondering
that
we
can
expand
generalize
this
bit
more
from
overview
perspective.
C
Yeah.
These
points
are
basically
like
I
had
a
in
my
mind
where
I
see
this
manager
broadcast.
B
B
B
A
Guess
going
forward
with
this?
What
what
makes
that
kind
of
the
plan
to
be
I
guess
I
can
help
push
it
Forward.
A
B
I
would
like
ask
all
of
you
and
ask
Michael
specifically
to
to
dedicate
to
not
dedicate
that's
that's.
That
means
different
I
think
at
gitlab
than
at
other
places,
but
anyway,
to
dedicate
two
weeks
to
this
Mr,
which
means
that
all
of
us,
the
whole
team,
knows
that
for
those
two
weeks,
Vista
Mar
is
in
focus
and
we
want
to
close
it
by
the
end
of
the
second
week.
B
C
All
right,
just
if
we
want
to
merge
quickly,
I,
have
one
comment
that
can
we
drop
some
like
a
very
specific
specifications
like,
for
example,
artifact.
It
must
contain
cropped
crop
cryptographically
assigned.
This
is
something
like
then,
like
artifact
isn't
a
cryptography
signed.
It's
not
artifact
like
this
type
of
argument
is
gonna
happen,
so
like
I
wanna,
if
we
can
generalize
a
bit
more
so
that
we
can,
you
know,
move
on
like
more
details
later.
C
B
Not
against
that
yeah,
with
this
specific
example
that
you
gave
I
think
yes,
I,
don't
know
what
else
we
would
find
to
to
make
it
smaller
and
overall
I.
Think
merging
a
sloppy
terminology
is
worse
than
not
having
a
terminology,
I
agree,
so
that
that's
that's
that's
why
so
we
read
the
example
you
shared
I
would
agree
that
we
can
merge
it
even
without
that,
because
it
doesn't
affect
the
whole
flow.
B
On
the
other
hand,
if
you're
like
what
we
have
a
discussion
on
on,
what
does
a
release
mean
and
it
came
out,
it
might
not
be
even
needed
there.
I,
I,
I,
wouldn't
know
what
to
merge
at
this
point
and
I
think
it
would
just
cause
Constitution
that
we
merged
today,
one
wording
and
a
week
later.
We
want
to
change
it,
but
there
are
cases
very
likely.
We
can
simplified.
A
It's
almost
like
we
have
to
decide
which
like.
Why
do
you
want
to
voice
your
point
because
I
think
it's
similar
to
what
I
was
about
to
say.
D
Yeah,
can
we
try
to
iterate
on
it,
maybe
split
it
in
like,
for
example,
we
can
just
merge
empty
page,
which
says
this
is
a
glossary.
This
is
the
purpose
of
it
and
don't
merge
any
exact
terms
now
and
then
just
open
another
I,
don't
know
510
merge,
requests
with
specific
stuff
which
we
can
discuss,
which
will
be
much
smaller
and
can
be
merged
within
a
few
days,
because
right
now
it
looks
way
too
big
and
I.
Don't
know.
Two
weeks
timeline
also
appeals
to
me,
but
no,
we
can
do
it
even
like.
D
We
can
give
two
days
for
like
comments
and
addressing
them
and
then
just
merge
and
then
iterate.
Adjusts.
Okay,
like
dcmr,
is
way
too
big
to
be
merged
in
a
single
piece,
because
it
will
create
way
too
many
discussions.
A
Yeah,
it's
almost
like.
We
have
to
break
off
certain
terminologies
and
start
with
just
certain
ones:
perfect,
those
certain
ones
and
then
move
on
to
others.
Instead
of
trying
to
do
them
all
in
one
I'm,
not
sure
how
we
would
break
those
off,
but
to
Victor's
point
we
don't
want
to
merge
like
sloppy
terminology.
That
is
not
fully
agreed
on
by
the
team,
but
maybe
we
could
break
it
up
and
not
have
some
for
the
first
iteration
but
I
don't
know
if
that
would
be
helpful
or
not.
B
Oh
I,
like
the
idea
actually
I'm,
not
I,
don't
know
how
they
would
execute
but
I,
like
both
the
idea
of
starting
with
an
empty
page.
I
did
the
plus
one
there
and
as
well
that
nicely
we
can.
B
We
can
try
to
have
separate
Mrs
for
not
all
the
terms
but
like
some
terms
like,
for
example,
for
Target
infrastructure,
just
use
it
together
with
environments,
but
like
these
bigger
terms
and
and
that's
okay,
two
days
on
that
two
days
on
that,
and
we
can
even
move
back
when
we
figure
out
if
something
is
not
good.
Let's
move
forward
I
like
this.
D
Yeah
kind
of
changing
the
subject:
how
do
we
plan
to
address
the
difference
between
this
ideal
terminology
and
what
we
want
to
mean
and
what
we
actually
have
in
the
product
to
what
like
I,
also
read
about
the
release?
Also
being
cryptographically
signed,
yeah,
hard
work
to
say
and
like
we
have
none
of
this
right
now.
B
D
B
Yeah
I
think
we
should
be
very
clear
on
on
plan
features,
perhaps
having
similar
flag,
that
we
have
for
tiers
on
the
page,
headers
or
or
some
similar
symbol.
That
shows
that
this
is
a
plant
thing
and
doesn't
exist
yet
or
or
something
that
that
was
one
of
the
reasons
why
we
didn't
wanted
to
put
it
in
the
user
dot
actually,
but
when
I
we
need
is
somewhere
is
I,
don't
know
if,
if
in
your
culture,
you
have
something
similar,
but
in
in
Hungary
the
Oakland
stated.
B
I
guess
never
wanted
to
end
up
in
Moscow,
but
all
our
big
poem
poet
went
to
Paris.
Actually,
so
that's
why
the
glossary
is
is
shows
us
the
north
star
that
we
want
to
reach.
And
after
that
we
can
discuss
if
it's
feasible
at
all
again.
B
B
A
A
Just
capturing
notes:
well
that
makes
sense.
So
what
did
we
want?
The
timeline?
To
be
honest,
did
we
want
to
start
working
on
it
ASAP
this
Milestone
next
Milestone
kind
of?
When
should
we
make
plans
to
do
these
like
two
day
or
two
week,
not
Sprints
but
periods
of
time,
where
we
want
to
focus
on
this
effort.
B
I
think
it's
pretty
urgent
actually
because
they
are
working
in
this
domain
and
not
having
a
vocabulary
to
discuss
things.
That's
a
bit
awkward
to
start
with.
At
the
same
time,
it's
it
doesn't
it's
not
a
critical
issue
or
anything
like
that.
So.
B
Basically,
the
handbook,
especially
it's
super
unique.
We
don't
really
need
special
approvals
or
anything
like
that,
and
the
other
question
is
the
breakdown
that
Vlad
you
mentioned,
and
you
will
be
gone
by
next
Monday
and
I
think
it
would
be
really
helpful
if,
once
we
merge
the
empty
page,
if
you
Emily
or
me
could
work
together
with
one
of
you,
the
engineers
to
quickly
open
or
these
Mrs,
how
we
think
is
the
first,
the
first
place
of
of
the
big
Mr
so
to
say
we're
starting
at
the
same
time.
B
I
don't
want
it
to
take
a
huge
amount
of
I.
Don't
I
should
play
more
on
that,
but
if
anyone
has
Azure
ideas,
how
to
approach
it
or.
D
How
I
would
do
it
is
I
would
create
an
empty
page
inside
the
direction.
I
think
that
was
a
great
idea
from
Andrew
and
we
can
do
it
today
and
then
I
guess
you
make
sure
you
can
find
like
five
terms,
that
you
find
the
most
important
right
now
just
copy
existing
text,
which
you
already
have
and
open
NMR
with
them,
and
we
can
discuss
them
and
then
every
week,
every
couple
weeks
we
can
create
another
merge,
requests
moving
more
and
more
again
of
this
existing
content
and
discussing
it.
A
To
to
Victor's
point
of
having
a
plan
out
about
the
Mrs,
we
could
also
just
open
an
issue
that
has
the
list
of
what
we
think
we
want
to
open
and
just
have
it
collected
somewhere.
So
it's
not
like
busying
up
anywhere,
but
we
do
have
it
like
down
on
paper
that
we
want
to
get
all
of
these
open
in
the
next
month
or
so.
D
A
Well,
I
think
that
was
pretty
productive
in
getting
a
plan
down
to
get
this
work
done.
So
thanks
everyone
for
your
input
on
this.
Does
anyone
else
have
any
comments
or
questions
overall.
C
All
right
just
quick
question
when,
for
example,
when
do
we
use
this
stock
like
when
we're
talking
with
customer
or
were
we
talking
with
I
mean,
like
a
give
me
one
example.
B
We
would
use
it
so
we
planned
to
run
a
design
experience
for
environment
and,
for
example,
there.
This
would
be
very
likely
super
useful.
B
We
would
use
it
for
deployments
like
I,
think
yeah
either
on
that
issue.
That
tiger
created
the
example
project
on
how
to
organize
deployments.
We
could
use
it
there
as
well,
because
what
to
deploy
is
in
a
sense,
an
artifact
and
and
they
could
easily
describe
that.
That's
an
artifact,
but
it's
an
ocim
age
or
something
branch.
B
C
A
A
So,
just
to
summarize,
Victor
you'll
open
up
the
issue
with
the
planned
Mrs,
we'll
open
the
first
Mr
around
the
blank
page
today
and
that'll
kind
of
get
us
started
on
this.