►
From YouTube: CI/CD UX Design Review - 06/15/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
B
Sounds
good,
so
I'll
spend
the
first
little
bit
just
going
over
what
we're
solving
for
in
the
design
Sprint
just
so
everyone
has
some
background.
So
our
current
environments
feature
is
really
like
an
afterthought
of
cicd
and
we're
looking
to
kind
of
rethink
it
and
build
on
the
knowledge
we've
learned
from
all
the
past
research
and
have
it
as
like
the
deployment
platform.
B
So
where
you
go
to
kind
of
control,
your
deployments
just
kind
of
rethink
of
how
users
are
using
it,
because
we
know
currently
that
environments
isn't
working
super
well
for
a
lot
of
users
just
the
way
we
currently
have
it
set
up
and
everything.
So
we
decided
to
host
a
design
Sprint
on
this
to
kind
of
come
up
with
a
concept
very
quickly
in
like
a
week
and
a
half
so
I
will
kind
of
share
my
screen.
B
The
zoom
thing
came
up
on
the
screen.
I
was
gonna
share,
so
I
don't
know
which
one
it
is
okay.
There
we
go,
oh,
so,
just
to
give
like
a
very,
very
quick
overview
of
what
we
did.
I
think
I
already
talked
with
some
of
you
about
this,
so
I
won't
go
in
too
much
detail,
but
we
spent
day
one
kind
of
recording
our
thoughts
on
previous
research
competitors.
B
The
environments
feature
as
it
is
now
to
kind
of
bring
up
different
problems
that
it
currently
is
having
and
what
competitors
are
doing
differently.
So
we
kind
of
use
the.
How
might
we
mapping
so
through
that
those
recordings
came
up
with
different
opportunities
we
wanted
to
solve
for
and
the
top
voted?
How
might
we
use
there
are
how
we're
currently
the
relevant
information
we're
showing
on
the
environments
page
just
isn't
there
and
like
presenting
we're
not
presenting
the
actions
or
information
in
the
right
way
either
that
works
for
users
workflows.
B
So
through
that
we
went
through
some
like
ideation
sessions
of
like
how
we
could
rethink
environments
and
the
one
I
really
want
to
like
zoom
in
on.
B
Is
this
particular
one
where
currently,
we
see
environments
more
as
like
a
linear
so
like
you
go
through
Dev
GA
staging
prod,
whereas
we
really
should
think
of
environments
as
like
this
Matrix,
where
you
have
your
environments,
but
you
also
have
your
services
so
like
your
apis
from
going
through
these
environments,
and
how
do
we
kind
of
visualize
this,
because
this
current
this
is
done
really
badly
right
now?
B
Is
that
like
moving
services
through
environments,
there's
not
really
a
good
visual
of
how
users
do
that
so
rethinking
things
around
there
as
well
as
rethinking
like
we
have
very
bad,
like
notification
system
with
our
environments
and
deployments
right
now.
So
how
can
we
integrate
with
notifications
and
how
do
we
rethink
of
it
from
like
the
group
project
details
view
and
go
on
from
there?
So
lots
of
great
ideas?
I
was
really
really
happy.
B
Everyone
on
the
team
was
super
into
the
sketching
exercise,
which
was
a
really
great
so
from
there
we
kind
of
built
out
like
okay.
If
we're
gonna
go
forward
with
like
this
Matrix
version,
instead
of
a
linear
way
of
dealing
with
environments,
how
do
we
kind
of
work
that
into
a
storyboard,
so
we
thought
of
okay?
How
do
notifications
work
with
this?
How
could
this
work
on
like
our
home
page?
B
How
could
this
work
with
kind
of
like
the
group
or
project
level,
and
maybe
there's
like
Mr
integration,
with
this
too,
like
that
environments
widget?
How
would
that
like
evolve
and
then
a
service
page
for
like
each
service?
B
What
would
that
look
like,
so
we
kind
of
then
jumped
into
like
different
iterations
of
the
Prototype,
so
we
have
like
iteration
one
where
we
did.
One
version
quickly
had
the
team
leave
comments,
feedback
jumped
into
version
two
another
feedback
session,
and
then
we
kind
of
landed
on
like
these
two,
for
just
like
the
outcomes
of
the
design
Sprint,
which
we
will
just
a
heads
up.
B
That,
like
the
data
in
this,
is
not
super
accurate,
it
was
just
stuff
we
threw
in
really
quickly
to
get
the
idea
together
so
like
the
commits,
are
all
the
same.
Some
of
these
like
service
Health,
don't
really
like.
If
you
click
into
it,
there's
like
some
errors,
which
it
shouldn't
be,
but
basically
what
we're
looking
to
do
is
like
have
a
way
to
register
services
on
gitlab,
so
these
could
be
like
your
apis
and
how
they
move
through
environments
and
within
each
service.
B
You'd
have
kind
of
like
the
metrics
that
go
into.
If
it's
like
healthy.
Do
you
need
to
take
action?
Is
there
like
a
pending
approval
on
a
service,
and
then
you
would
like
click
in
and
you'd
get
more
details
on
this
service
like
what's
the
active
deployment
going
into
it
right
now?
Where
does
it
sit
in
like
the
Topography
of
your
kind
of
stream
of
things?
What's
the
history?
Is
there
anything
pending?
B
So
this
is
kind
of
like
the
concept
that
came
out
of
the
design
Sprint,
which
we're
really
excited
for
because
we
think
this
solves
a
lot
of
our
current
problems
with
the
environments
area.
Having
a
flow
like
this,
but
yeah
I
will
think
that's
a
good
overview,
but
now
I'll
open
it
up
to
like
a
discussion
or
conversation.
A
I'm-
just
thinking
looking
at
this
that-
and
this
is
a
very
fresh
perspective
of
looking
at
environments
and
how
they
work
like
you're
keeping
services
at
the
center
and
then
referencing
to
the
environment,
like
from
that
point
of
view,
keep
like
in
case
I'm
very
sure,
like
this
is
going
to
get
forward.
You
will
be
validating
and
doing
all
of
that,
but
this
will
also
be
having
a
decent
amount
of
impact
on
how
we
present
other
resources
in
gitlab.
B
A
And
I
would
say
for
good,
because
we
are
doing
a
validation,
a
solution,
validation
for
variables,
and
we
are
getting
to
hear
a
lot
about
how
it's
not
intuitive,
for
the
developers
on
the
team,
while
they're
creating
a
variable
to
like
reference,
the
right
environment
and
Define
the
purpose
and
what
they
end
up
doing.
Is
they
end
up
creating
Nuance
each
time
and
overriding
it
so
like
having
a
consistent
terminology
for
I?
A
Think
the
whole
of
verify
once
your
work
like
progresses
to
a
stage
where
you
are
satisfied
with
the
outcome,
would
be
a
good
thing
to
have
like
a
small
workshop
for
all
the
rest
of
us
to
see
like
how
this
will
have
an
impact
on
what
we
can
do
to
make
the
process
smoother.
B
I
think
that
makes
a
lot
of
sense
and
for
the
validation
we
just
wrapped
up,
so
the
team
was
doing
like
internal
testing
quickly
with
so
we
did
three
internal
tests,
so
each
partner
group
did
a
test
with
someone
in
gitlab
I'm,
going
to
summarize
kind
of
like
the
outcomes
of
that,
and
then
we're
gonna
plan
on
running,
like
a
proper
solution.
Validation
study
on
this,
as
well
as
probably
a
navigation
study,
because
we
also
have
to
figure
out
where
this
fits
in
the
navigation.
B
Yeah
yeah,
so
right
now,
environments
is
very
like
environments
and
deployments
are
really
closely
related.
So
now
we're
gonna
relate
to
more
of
like
the
deployment
to
the
service,
which
is
in
an
environment,
so
we're
thinking
of
the
environment
as
more
of
like
a
bucket
that,
like
services,
will
sit
in
now
versus,
like
the
environment
being
the
place
you
go
to
take
action
on
the
deployment.
It's
kind
of
having
like
that
middle
section,
so
yeah
gonna
have
to
rethink
a
lot
of
the
architecture.
B
I
think
we
need
to
draw
out
a
whole
like
architecture
map
of
how
this
would
affect
everything
we're
changing.
But
it's
our
initial
idea
and
we
had
a
customer
in
the
design,
Sprint
and
back-end
engineers
and
all
three
of
them
were
super
excited,
but
the
outcomes
of
this.
A
D
B
B
C
Yeah
and
even
and
then
artifacts
come
in
in
here
too
I
mean
build
artifacts,
Plus,
I,
don't
I,
don't
know
what
you
would
call
the
other
artifacts
that
are
actually
like
generated
from
the
environment,
yeah
there's
there
would
be
a
lot
of
inner
linking
here
and
then
also
I.
C
Just
wanted
to
note
that
I
really
like
how
you're
combining
metrics
here
in
in
using
those
cards
kind
of
to
show
Like,
A,
visual
representation
of
that
service
and
where
it
lives,
I
I,
think
we
should
be
doing
more
of
that
I
like
it
a
lot
thanks.
B
Yeah,
that's
something
a
lot
of
our
Engineers
are
saying
was
missing
right
now,
especially
with
like
the
promote
and
rollback
feature
we
have
is
the
current
feature
we
have
for
that
is
very,
very
simple
and
having
some
sort
of
visual
similar
to
how
jobs
like
the
jobs
and
like
the
pipelines
view,
has
it
that
was
very
missing
from
the
the
environments
view
right
now
is
where
things
sit
in
the
big
scheme
of
things.
B
And
Ellie
I
noticed
you
have
a
question.
D
Yeah,
if
I
guess,
the
questions
also
got
a
similar.
D
Argentina
Titan
or
like
bringing
everything
together
like
so
the
persona
who
is
going
to
be
mostly
benefit
from
this
feature.
I'd
assume
is
mostly
platform,
engineer
type
folks,
yeah.
B
We
have
four
Sports
owners
actually
for
this,
which
is
the
platform
engineer,
application,
Ops,
so
Allison
the
development
team
lead
and
the
release
manager.
All
kind
of
would
relate
into
this.
D
Experience
with
configure
like
some
of
the
platform
Engineers,
they
work
across
groups
and
projects
and
yeah
I
was
always
thinking
of
ways
for
them
to
kind
of
navigate
across
all
the
all.
The
resources
that
are
being
used
across
groups
and
projects
and
I
see
these
things
like
approvals
as
well.
D
Yeah,
probably,
but
you
know,
suggested
about
visualizing
everything.
Monthly.
D
D
000
people
using
a
gitlab
instance
and
yeah
it
gets
missed.
B
So
it's
something
we
have
to
look
into
I
think
we
need
more
data
about
how
people
deal
with
services
at
the
group
level
to
be
able
to
scale.
For
that
and
I.
Think
the
answer
to
your
question
is:
we
haven't
really
figured
it
out
yet
how
to
do
this
at
the
instance
group
project
like
what
is
the
best
way?
Do
we?
Let
them
choose
like
how
they
want
this
to
run
I
think
we
still
have
to
figure
it
out.
C
Emily,
do
you
have
either
like
a
link
to
the
job
to
be
done
for
your
group
if
they're
still
applicable
or
could
you
help
me
understand
why
personas
would
want
to
come
to
this
page
and
like
what
what
they
would
take
action
on?
First.
B
Yeah,
so
our
main,
our
main
Persona,
which
is
the
one
I'll
focus
on,
is
the
platform
engineer
Priyanka.
So
the
task
it
kind
of
we
wanted
to
keep
this
high
level
page
more
of
an
overview,
so
there'd
be
no
main
action.
You
take
on
this
page
other
than
kind
of
like
overviewing,
the
metrics
of
everything
to
do
with
their
services,
seeing
service
health,
and
then,
if
you
do,
need
to
take
an
action
on
this
page,
you
would
then
click
in
here
now.
This
page
has
quite
a
few
actions.
Users
would
want
to
take.
B
You
could
promote
roll
back
so
move
your
deployment
between
things
here,
which
is
an
action
we've
been
struggling
with,
making
work
really
well,
so
that
promotion
roll
back.
This
is
also
where
you
can
get
more
information
into
your
deployment
history.
B
If
there
is
like
themes
there
that
you
want
to
figure
out,
get
an
understanding
of
your
current
deployment
like
the
status,
so
just
that,
like
metric
status,
overview
of
the
current
deployment,
Health
we're
also
playing
around
with
adding
things
like
feature
Flags
like
in
an
events
log
here
as
well,
but
we
still
have
to
figure
out
the
exact
like
actions
you
would
take
with
those
but
yeah.
Basically,
it
would
be
kind
of
like
actions
you
take
on
a
deployment
such
as
like
promoting
rolling
back.
B
Giving
approval
overview
of
past
deployments
would
be
the
main
kind
of
like
the
main
tasks
here
and
for
the
jobs
to
be
done.
The
environments
group
jobs
to
be
done
are
kind
of
messy
right
now,
they're
not
really
shown
anywhere
because
they're
a
big
conglomerate
of
like
releasing
configure
jobs
to
be
done.
So
that
is
something
we
actually
do
need
to
sort
out
sometime
soon.
B
C
B
The
job
is,
what's
the
template
for
a
job
to
be
done,
it's
like
I
want
so
that
what
are
the
three,
because
I
could
probably
like,
based
on
our
design,
Sprint
say
one
on
the
spot,
but
I'm
forgetting
the
first
sentence.
Okay,.
B
Perfect,
so
this
is
kind
of
like
when
I'm
monitoring
my
services
I
want
to
make
sure
everything
is
running
as
expected,
kind
of
like
so
that
I'm
confident
in
what
we're
building
or
something
that's
a
very,
very
on
the
spot
job
to
be
done.
But
this
page
is
really
about
wanting
to
know
how
your
services
are
doing.
So
you
can
be
confident
that
you're
building
correctly
okay.
C
Yeah,
no,
that
helps
that
helps
and
the
select
environment
drop
down
is
that
would
that
filter
the
whole
page.
B
D
D
Are
the
environments
independent
solely
for
this
project
or
can
other
projects
use
this
the
same
underlying
infrastructure?
That's
inside
this.
B
But
that's
some.
That's
another
architectural
thing
we'll
have
to
play
around
with
so
probably
for
MVC.
It
would
work
very
similar
to
how
we
currently
have
environments,
but
in
the
long
run,
I
think
we'd
want
to
really
figure
out
how
to
make
this
work
for
everyone
and
I
think
that
is
kind
of
like
detaching
environments
from
project
and
group
level,
but
I'm
not
sure
how
we
do
that.
A
B
D
C
Yeah
my
my
last
comment
here
just
because
I've
learned
from
this
is
actually
very
similar
to
the
job
to
be
done
for
runners,
but
obviously
not
about
Services
about
runners,
and
we
learned
that
showing
the
analytics
on
the
page
is
very
difficult
with
performance,
although,
if
you're
building
a
new
like,
if
this
has
to
update
the
architecture
in
the
database
anyways,
maybe
it
will
be
give
you
a
chance
to
do
it
more
in
a
performant
way.
But
it's
something
to
be
aware
of,
because
we
ended
up
adding.
C
B
Yeah,
that's
something
we'll
definitely
I
actually
took
something
inspiration
from
you
about
having
it
like,
not
update
in
real
time
and
have
like
the
updated
two
minutes
ago.
Just
so
this
page
doesn't
have
to
run
like
in
real
time,
because
that
would
be
a
performance
nightmare.
Yes,.
C
Yes,
definitely
and
then
it
brings
more
a
little
bit
more
stress,
though,
because
the
platform
engineer
wants
to
know
what's
going
on
at
the
moment:
yeah
not
updated.
It's
like
if
there
was
a
problem
with
one
of
the
services.
Maybe
it's
already
fixed,
but
we
haven't
updated
the
status,
which
is
something
same
thing
with
Runners
like
if
one
of
them
is
failing.
Maybe
someone
already
fixed
it
and
it
still
says
it's
failing.
B
B
Then
yeah
you're
able
to
get
the
data
right
away,
but
we're
not
having
all
the
problems.
We
could
especially
like
this
page
to
everything
real
time
here.
Yeah
would
be
difficult,
so
having
like
a
manual
refresh,
might
be
a
good
first
way
to
do
it
unless
the
engineers
can
figure
out
some
way
to
do
it
real
time.
But
right.
A
B
Yeah
for
sure
it's
funny
in
the
design,
Sprint
too
another
thing
came
up
where
we're
like.
Oh
can
we
rethink
our
single
stat
metrics
to
work,
something
like
this,
which
everyone
thought
was
really
cool.
So
that's
another
one.
We're
like
oh,
is
that
something
we
can
do,
because
when
we
did
some
of
the
hallway
testing
people
were
like
yeah
I
like
these
metrics,
but
like
in
the
grand
scheme
of
things.
Is
this
good?
Is
this
bad
like?
How
is
that
relating
so
we're
like?
B
B
B
And
I
guess
the
last
thing
is
design.
Sprints
are
fun.
So
if
anyone
wants
to
run
one,
let
me
know
because
I
think
we
took
a
lot
of
like
the
learnings
Victor
had
from
previous
ones
or
pure
N1
fully
sync.
It
didn't
work
here
in
one
fully
async
it
didn't
work,
so
we
were
trying
to
like
find
a
balance
of
like
how
do
you
run
it
partially
sync
and
partially
Asic.
A
B
A
Do
things
remotely,
with
the
help
of
everybody
else,
is
going
to
be
on
the
boat,
so
I'll
start
creating
a
plan
for
that,
but
I
will
definitely
Loop.
You
in
cool
sounds.
B
Well,
well,
that's
kind
of
all
I
had
to
share
thanks
again
for
all
the
feedback.
I
know
it's
like
a
very,
very
early
concept
that
we
don't
have
a
lot
of
user
research
in,
but
this
gives
me
a
lot
to
think
about
and
I
appreciate
the
feedback.
A
B
Yeah
I
think
that's
what
I
was
running
into
when
I
was
trying
to
do.
The
group
level
environments
is
is
just
the
same
perspective.
We
are
always
looking
at
environments
and
and
Victor
was
very
much
like
no,
let's
just
like
pretend
environments
doesn't
exist
and
like
how
would
we
design
the
perfect,
like
environments
feature,
and
then
this
kind
of
landed
from
that
great.
C
D
B
Like
notifications,
the
navigation,
everything
but
I
believe
the
initial
testing
will
just
be
an
updated
version
of
these
two
concepts
from
our
called
hallway
testing
from
the
design.
Sprint
and
we'll
really
be
wanting
to
understand.
Like
first
off
is
this
concept,
something
people
would
actually
use
as
something
they're
excited
about.
Does
it
work
with
their
workflow,
but
also
are
the
actions
and
metrics
we're
showing
the
proper
ones
and
is
there's
something
we're
missing,
especially
actions
wise
that
people
would
like
to
take
on
both
pages.
B
B
C
Cool
because
maybe
to
make
the
recruitment
easier
for
research,
you
could
do
a
combination
of
internal
and
external,
and
if
we
dog
food
it.
A
Perfect,
so
we
are,
are
we
at
time
or
do
we
have
more
time
anyway?
Yeah
any
other
questions?
We
do
have
time.
A
Okay,
so
if
there's
nothing
more,
let's
yeah,
let's
end
it
here,
and
it
was.
It
was
a
great
session
thanks
Emily
and
thanks
everyone
for
taking
out
time,
yeah
we'll
see
each
other
in
another
meeting,
I'm
not
sure
when
that
is
sounds
good.
Thank.