►
From YouTube: CI/CD UX Meeting - 2021-03-24
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
All
right,
this
is
the
cicd
ux
call
for
march
24th.
We
have
a
lot
of
fyi's.
I
apologize
for
that
mostly
on
my
end,
but
I
just
want
to
vocalize
a
couple
of
them.
The
first
one
is
that,
starting
next
week
I'm
going
to
be
busy
with
the
hiring
for
the
testing
and
runner
design
position
and
the
expectation
well,
my
expectation
is
that
yeah,
my
time
is
going
to
be
even
more
limited.
A
So
I
would
like
to
ask
you
like,
if
you
have
any
general,
mrs
or
ux
feedback
that
you
need
in
general,
don't
block
and
don't
be
blocked
by
me
on
that,
so
feel
free
to
reach
out
to
other
folks
in
the
ux
department
to
get
feedback
on
that
and
all
the
other
urgent
things
and
that
need
approval.
You
know
the
workflow,
please
feel
free
to
address
those
to
me.
So
any
questions
on
that
I'll
just
pause
for
a
second,
oh
good,
awesome
and
yeah.
That's
it
ian!
A
I
think
you
know
you
have
an
fyi
item.
I
don't
think
you
if
you
want
to
vocalize
that
feel
free.
B
Yes,
I'm
sure
most
of
us
have
probably
heard
this
already
but
congrats
to
daniel
for
officially
starting
the
transition
to
owning
release.
Yay
I'm
really
excited-
and
I
know
the
team
is
too
so
congrats.
A
That's
awesome,
super
happy
and
then-
and
next
discussion
item
is
actually
mine,
so
we
all
know
laura
is
leaving
very
sad
heartbroken
her
last
day.
I
think
it's
the
last
day
of
this
month,
she's
going
to
take
some
some
time
off.
So
that
being
the
case,
please
feel
free
to
address
any
research
proposals
in
scripts
to
me.
A
So
the
expectation
that
I
like
this
yesterday
with
valerie
is
that
ux
managers
are
going
to
be
the
ones
looking
and
giving
feedback
to
general
usability,
research
and
problem
validation
and
that
the
current
expectations
that
high-level
strategies,
strategic
research
will
be
paused,
so
obviously
the
ship
they
have
to
decide
what
they
want
to
move
forward
with.
I
believe
that
some
items
for
verify,
I
believe,
will
move
forward
because
jackie
might
be
able
to
push
this
herself,
but
just
so
you
know.
I
think
this
will
be
officialized
at
some
point.
A
There's
no
expectation
that
strategy
research
for
ops
will
continue
until
we
backfill
for
that
role,
because
jeff
is
also
leaving
the
organization
and
ian.
I
saw
that
you
added
a
comment
here.
B
A
That's
what's
immune,
thank
you
for
yeah
raising
raising
your
hand
there.
I
think,
especially
in
this
moment,
with
all
these
transitions,
it's
going
to
be
important
for
us
to
get
as
much
help
as
we
can
not
only
for
me
and
but
from
folks
in
the
ux
department.
A
So
for
me
at
this
point,
it's
a
bit
difficult
to
see
everything
that's
happening,
so
if
you
have
a
way
to
later
on,
maybe
just
maybe
we
can
discuss
like
give
create
an
overview
of
what's
happening
for
ci
cd
in
research,
so
we
can
try
to
help
each
other
out
during
this
period
might
be
a.
A
I
think
it
will
be
a
good
opportunity
for
all
of
us
to
also
understand
and
see
what's
happening
across
the
across
the
board,
but
in
general.
Well,
this
goes
with
the
with
lori.
I
think
tomorrow
we
have
our
last
101
set
and
we
talk
about
what
needs,
support
and
I'll
I'll
update
you
asynchronously
next
week,
so
daniel.
If
you
want
to
voice
your
comments,
feel.
C
Writing
yes,
plus
one
would
would
also
love
to
volunteer
to
help
structure
research
while
we
don't
have
a
dedicated
researcher
backfield
with
that
said,
I
think
perhaps
we
can
have
a
dedicated
process,
not
necessarily
a
meeting,
but
something
so
we
can
all
get
together
and
see
what
is
highest
pr
priority
in
terms
of
research
either
is
low
level
for
one
specific
team
and
we
can
help
each
other
out
or
if
it's
something
more
high
level,
and
it's
really
important
to
get
the
ball
rolling
on
that
can
at
least
outline
what
is
the
next
step
that
should
be
done
and
maybe
start
doing
it
ourselves.
D
Yeah,
that's
a
good
point.
I
think
this
could
be
a
good
opportunity
to
maybe
also
organize
all
of
the
cicd
research
in
one.
A
D
So
we
can
all
access
it
and
on
the
pipeline
authoring
team,
we're
not
planning
yet
but
we're
starting
to
think
that
in
like
two
milestones,
we
will
have
to
do
this
problem
validation
and
I
think
it
will
span
many
different
stages
and
affect
lots
of
parts
of
ci
cd.
D
So
we're
now
having
discussions
about
kind
of
shifting,
gitlab
ci
cd
model,
at
least
like
the
user
experience
for
creating
your
pipeline
configuration
to
have
these
shareable
pipeline
components
and
a
marketplace
for
them,
and
those
components
would
be
kind
of
packaged
in
a
certain
way.
So
that
also
if
we
were
to
pursue
this
and
there's
just
lots
of
feedback
that
we're
getting
that
there's
such
need.
D
I'm
not
gonna
go
too
much
into
technical
details
as
to
why,
but
basically
there's
this
need
to
have
these
more
bite-sized
pieces
of
code
that
that
would
be
packaged
with
a
way
to
manage
their
dependencies
and
versions,
and
things
like
that.
So
we
want
to
run
a
problem
validation
around
that
and
that
would
affect
a
lot
of
things
in
ci
cd.
So
it
could
be
a
really
good
effort
for
us
to
collaborate
on.
So
I
will
definitely
keep
you
in
the
loop.
A
That's
awesome,
thank
you
for
sharing
that
nadia
I'll
check
in
with
laurie
to
see
if
she
has
some
sort
of
issue
or
if
she
keeps
track
of
anything,
that's
going
on
for
ci
cd.
I
know
that
she
has
a
worksheet
I
just
linked
here,
where
not
only
laurie
but
all
ux
researchers.
They
keep
track
of
what
they're
doing
specific
milestones
for
stage
group
with
the
pm
et
cetera.
So
you
can
look
into
that,
but
I
think
it's
valid
for
us
to
have
our
own.
A
I
don't
know
epic
or
a
board
or
something
so
I'll.
Look
into
that
I'll.
Put
that
on
my
on
my
to-do
list
and
you
can
add
your
your
item
there,
and
maybe
we
can
even
use
this
call,
for
example,
to
just
do
a
synchronous
checking.
So
we
can
you
can
shape
that
as
we
move
forward.
A
That's
good!
Thank
you!
Nadia
for
the
heads
up
on
the
upcoming
pipeline
authoring
research.
That's
awesome.
A
And
danielle,
are
you
up
next.
C
C
C
So
the
goal
is
to
add
some
sort
of
more
interactive
dialogue
here,
where
you
can
approve
or
reject,
and
also
provide
notes
for
why
you
approved
or
rejected
and
and
there's
some
follow-up
states
that,
where
the
this
step
goes
after
being
rejected,
so
my
first
step
for
this
is
actually
to
try
to
understand
all
of
the
states
we
have
for
the
pipeline
jobs
today.
C
I
call
this
cookie
just
because
it's
round
and
cute
and
I
try
to
map
out
every
single
one
I
could
find,
but
I
keep
finding
new
ones
and
and
there's
so
many
little
variations
that
I'm
not
entirely
sure
what
all
of
them
do.
So
this
is
still
a
work
in
progress,
but
later
today,
I'll
share
it
this
with
you
all
on
the
channel-
and
I
think
especially
nadia
should
should
know
better
about
this,
because
it's
your
your
specialty,
if
you
see
anything
missing
or
if
there's
any
interpretation,
that
is
wrong.
C
Maybe
just
leave
a
comment
on
the
figma
file
or
just
on
slack.
That
would
be
super
helpful
and
yeah.
That's
that's
pretty
much.
It.
D
Yeah,
this
is
awesome
thanks
for
sharing
it's
very
interesting
that
you're
working
on
this,
because
technically
the
pipeline
authoring
team
owns
pipeline
graph
and
we've
been
working
on
all
of
the
changes
that
relate
to
the
pipeline
graph,
which
is
kind
of
also
a
bit
weird
because,
like
python
graph
is
used
for
so
many
different
things.
So
honestly,
I'm
not!
I
don't
even
know
like
what
would
be
a
better
way
to
split
this,
but
either
way
we
have
to
collaborate
on
this,
because
there's
lots
of
changes
that
we're
planning
for
the
pipeline
graph.
D
That
also
involve
like
changing
the
job
pills
and
we're
also
thinking
about
adding
some
additional
actions
to
these
job
pills.
So,
just
to
give
you
like
a
very
brief
overview
of
my
current
thinking,
we
eventually,
as
we
add,
more
and
more
features,
we
will
have
more
and
more
job
related
tasks
that
you
can
do
from
the
ui
or
you
know
we
have
an
opportunity
to
add
those
to
the
ui,
but
currently
the
way
the
jobs
are
designed.
D
The
whole
job
is
the
bottom,
and
I
I
also
like
not
harmful
sure,
but
I
think
that
is
also
an
accessibility
concern,
because
currently
it's
not
really
possible
for
you
to
tab
through
the
pipeline
graph
and
use
the
keyboard
to
navigate
into
the
job
details
or
like
job
logs.
So
the
focus
automatically
goes
to
the
retry
button
or
whatever
button
that
is
there.
D
Pipeline
pill-
I
don't
know-
maybe
it
could
be
fixed
by
just
differently
kind
of
approaching
the
component,
the
way
it's
built,
but
either
way
we
will
need
to
start
thinking
how
we
can
add
more
actions
to
the
job.
So
probably
some
kind
of
drop
down
we're
already
thinking
of
having
I
will
yeah.
It
will
take
me
ages
to
find
that
issue
probably,
but
I
will
edit
after
the
call
we
have
an
issue
now.
D
Actually
it
might
be
getting
implemented
already
in
this
milestone
to
add
a
drop
down
version
of
that
run
button.
So
we
have
an
issue
to
allow
you
two
different
types
of
retries.
So,
instead
of
just
retrying
the
job,
you
can
also
choose
to
retry,
like
only
failed
jobs
in
the
child
pipeline,
for
example,
so
that
little
round
button
would
have
a
little
drop
down
and
then
it
brings
up
like
two
different
options.
So
that
is
also
an
opportunity
to
add
extra
options.
D
A
Let's
see
what
we
have
next,
we
have
a
retrospective
for
13,
10
or
13.
11.
wait
a
second!
Where
are
we
in
time?
So
what
I'll
leave
up
it's
up
to
you?
If
you
would
like
to
to
voice
some
of
the
wins
challenges
and
shout
outs
for
for
this
milestone?
What
do
you
see.
A
Silence
in
the
in
the
digital
room,
so
we
can
skip
that.
I
I
haven't
replied
to
the
retrospective
yet,
but
I
saw
some
comments.
I
actually
wanted
to
give
a
shout
out
and
actually
wanted
to
ask
you
nadya.
If
you
could
share
a
little
bit
about
sorry
for
putting
on
us
on
the
spot,
about
your
async
design
critique
and
how
you're
asking
for
feedback
in
in
the
slack
channels
in
the
ux
co-working
channels.
A
Do
you
think
you
have
some
insights
to
share
with
us
on
how
you're
doing
that
now
that
you're,
especially
in
thailand
and
your
your
time
zone,
changed
even
more.
D
Yeah
yeah
sure
happy
to
share.
I
mean
my
strategy
is
quite
simple.
Whenever
I
work
on
something
I
try
to
think
would
sharing
it
bring
any
additional
value
at
all.
Even
if,
like
one
person
who
might
be
interested
in
this
sees
it,
will
it
create
some
value
or
the
synergy
and
maybe
uncover
some
opportunities.
And
if
the
answer
is
yes,
I
try
to
share
it
and
then
I
think
what
form
it
should
take
to
be
the
most
effective
like.
D
Should
I
make
a
two-minute
bloom
video,
or
should
it
just
be
a
little
psych
message,
or
is
it
better
to
put
it
in
an
issue
yeah,
and
I
I
found
that
it's
a
really
easy
way
to
just
bring
more
visibility
and
also
just
kind
of
extend
the
impact
of
your
work.
D
So
that's
why
I'm
doing
it
because
it
really
doesn't
add
any
more
work
to
my
plate,
but
seems
to
you
know
you
never
know
who
will
see
your
work
that
will
that
they
can
apply,
maybe
in
their
design,
so
they're
not
reinventing
the
wheel
or
maybe
they
will
find
some
gaps
in
your
designs
and
save
you
from
like
a
big
disaster
which
is
always
welcome.
A
That's
awesome
and
I'm
gonna
share
here,
I'm
not
sure
if
everyone
is
in
the
ux
co-working,
where
is
it
the
slack
channel,
I'm
gonna
link
here
to
nadia's
latest
post,
if
you're
not
there,
yet
people
to
join.
I
think
it's
also
one
of
the
ways
that
we
have
today
to
like
what
nadia
was
saying,
stay
informed
of
what's
happening
also
in
the
other
areas
of
the
product,
other
stage
groups-
and
I
also
was
it
that
you
are
or
vitica
that
recently
posted
on
twitter
to
get
feedback
from
from
our
users.
D
Yeah
we
both
do
it.
I
don't
know,
I
just
did
it
today.
Actually,
so
I
can
share
it
yeah
I
like
tweeting,
I
guess-
and
sometimes
I
tweet
at
our
users-
and
I
get
quite
a
lot
of
engagement,
because
there's
lots
of
gitlab
ccd
users
that
are
on
twitter
and
they're,
quite
active
and
very
helpful,
and
also
our
developer.
Evangelists
are
super
active
on
twitter
and
they
retweet
product
designers
tweets
sometimes
like.
D
If
it's
something
interesting
and
you
can
get
lots
of
available
feedback
like
this
and
even
find
some
potential
participants
for
research,
because
I
actually
get
dms
saying
that
hey,
I
saw
a
prototype
that
you
shared
would
love
to
participate
in
like
beta
test
testing
when
you
launch
it.
So
I
collect
all
of
these
amazing
volunteers
into
a
spreadsheet
and,
like
I
don't
always
reach
out
to
them.
It
depends
like
if
we
have
some
relevant
research
coming
up
for
example,
then
I
do
that
yeah
thanks
diana.
D
I
also
have
a
link
was
going
to
edit
to
the
agenda
yeah.
So
it's
a
good
way
to
get
your
feedback
again
like
very
kind
of
low-fi
and
very
low
effort.
It's
always
nice
to
take
a
break
just
to
open
twitter
and
you
can
do
something
productive.
At
the
same
time,.
C
A
And
I
think
it's
what's
the
name
of
our
developer
evangelist,
I
think
it's
michael
right,
if
you're
not
following
michael
yet
follow
him,
he's
a
very
engaging
and
also
marcel,
he
does
a
great
job
at
reaching
out
to
our
users
and
yeah
just
evangelizing
as
well,
through
social
media.
C
A
I
added
here
to
the
more
fun
stuff,
the
video
of
my
recording
with
with
tori,
when
we
talk
about
her
career
development,
gitlab
her
role
as
a
staff
and
now
producer
manager
for
the
ux
foundations
team.
So
if
you
haven't
checked
that
yet
have
a
have
a
watch,
if
that's
even
possible,
to
say,
I'm
also
trying
to
write
a
blog
post
to
summarize
all
the
findings
so
that
we
don't
have
to
watch
all
these
long
videos
but
yeah.
A
If
you
you
have
the
time
check
those
those
recordings
are
super
valuable,
whether
talk
about
not
just
their
trajectories
at
gitlab,
but
also
what
is
leadership
right
other
than
just
the
title,
and
how
these
designers,
that
that
are
recognized
as
leaders
in
organization.
What
are
opportunities
for
learning,
growth
and
development
that
they
created
but
also
pursued
at
gitlab?
So
it's
a
very
interesting
conversation
with
tori.
A
Time
all
right
violence,
then
we
can
wrap
this
up.
Awesome
enjoy
a
day.