►
From YouTube: CI/CD UX Meeting (EMEA/Americas) - 2022-06-01
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
So
this
is
the
oh,
my
goodness
june
1st,
the
icd-1
meeting
america's
europe
version
a
couple
of
heads-ups
fyi
for
me
as
usual,
not
as
many,
I
guess
as
the
last
few
weeks.
But
if
you
haven't
completed
your
required
training
security
training,
please
do
so
sap.
I
think
we
are
at
64
percent
completion.
First,
you
shared
a
message
earlier
this
week
or
today.
So
please
complete
that
if
you
haven't
done
so,
I'm
gonna
find
a
reminder
in
our
team
chat
as
well.
A
I
don't
think
there's
any
updates
for
okrs.
You
know
you're
gonna
meet
tomorrow,
but
if
there's
anything
you
like
to
to
share
here
before
or
next
when
I
went
about
okay,
ours.
B
A
Okay,
awesome:
I
thought
that
nadia
left
some
updates
about
her
own
chaos,
jobs,
read
and
etc.
So
I
think
everything
is
on
track.
Pajamas,
migration
day
we
have
a
date
right
next
friday,
the
10th.
I
would
like
everyone
in
our
team
to
contribute
to
that.
So
at
least
one
component
migration,
it's
I'm
not
gonna,
say
it's
easy
because
it
can
be
pretty
complex
if
you
have
to
set
up
jdk,
but
you
know
last
time
the
the
instructions,
at
least
to
me.
A
They
were
really
helpful
and
it's
also
a
good
way
for
us
to
play
around
with
the
product
and
then
migrate.
Those
components
like
especially
buttons
that
are
outdated
or
incorrect
in
the
ui
in
your
product
areas.
So
please
schedule
some
time
if
you
can
to
contribute-
and
if
you
get
at
least
three
merger
quests
created
and
merged,
you
can
expense
a
meal
up
to
25
dollars.
So
that's
awesome.
A
I
had
lunch
last
time
sponsored
by
pajamas
components
and
that's
really
fun,
and
also,
if
you're,
not
able
to
create
the
components,
also
recommend
you
know
joining
the
slack
channel
and
being
available
to
review
those
components
because
there's
a
quite
some
mars
coming
from
engineers
and
those
needs
to
be
reviewed
by
designers
right.
So
that's
that's
for
you,
gina
and
I'll.
A
Send
everybody
else,
a
reminder
that
you
also
need
reviewers
for
those,
mrs
and
there's
a
link
here
to
the
issue
with
my
questions
and
also
the
guidelines
for
how
to
contribute
that
tori
has
put
together
so
paul
nazi.
If
you
have
any
questions.
A
All
right,
awesome,
and
then
next
thing
is
about
the
mr
reviews,
so
make
sure
to
check
if
the
boat
is
assigning
like,
if
you're
the
person
being
assigned
by
the
boat,
because
sometimes
the
developers
will
ask
the
random
person,
that
is
not
the
random
person
suggested
for
that.
I've
seen
some
basis
for
that
in
our
team.
So
please
double
check
if
you're
actually
being
suggested
by
the
the
roulette
before
even
nmr,
and
if
that's
not,
you
assign
it
to
the
designer
right.
A
That
is,
that
is
being
randomly
suggested
by
the
roulette
and
then
last
one.
I
promise
in
case
you
missed
it.
The
ux
cloud
sandbox
is
available
right
for
every
for
all
of
us
to
play
around
with
the
the
product
and
also
set
up
this
test
scenarios.
I
know
that,
will
it's
going
going
we'll
go
through
that
pretty
soon
and
there
are
also
guidelines
in
the
handbook
about
how
to
get
access
and
how
to
set
up
those
test
projects.
So
with
that,
I'm
done
with
my
initial
announcements.
A
So
if
you
have
any
questions,
feel
free
to
voice
those
otherwise
over
to
eugene.
B
Okay,
I'm
excited
to
use
the
ux
cloud
sandbox
by
the
way,
for
I
just
wanted
to
update,
because
I've
been
talking
about
artifacts
for
pipeline
insights.
So
often
I've
had
five
sessions
out
of
the
eight
that
I'm
doing
and
it's
moderated
sessions
and
there's
been
a
lot
of
findings
that
overlap
with
pipeline
execution
and
pipeline
authoring,
which
I've
already
looped,
spithika
and
nadia
into.
B
B
I
figured
it
would
be
interesting
to
tell
you
about
them,
so
we
were
validating
if
this
artifacts
page
was
something
that
we
should
move
forward
with,
and
it
turns
out
that
it
would
be
really
helpful
for
developers
and
for
devops
engineers
like
software
developers
and
devops,
and
we
would
have
it
at
the
project
level
and
a
lot
of
them
actually
asked
if
it
was
going
to
also
be
at
the
group
level.
B
So
that's
something
for
us
to
look
into
after
as
well,
and
the
main
like
job
that
it
will
help
them
do
is
when
they're
debugging
failures
in
pipelines
and
jobs.
If
they
need
further,
like
clarification
of
why
something
failed.
Sometimes
it
does
have
to
link
back
to
artifacts
and
then
some
other
things
that
I
learned
is
the
file
name
of
the
artifact.
So
it's
usually
like
a
file
like
gitlab.png
or
whatever.
It
is
the
file
name
and
the
file
extension
are
the
things
that
they
use
to
identify
them.
B
That
is
something
that
I
was
not
using
in
the
design,
because
today,
like
in
our
drop
down,
we
don't
add
the
file
extensions
when
you
look
at
a
pipeline,
so
that's
something
that
I'll
be
adding
and
then
the
other
thing
is.
B
We
were
looking
at
expired
artifacts,
which
means
like,
if
you
have
a
gillab,
sets
this
automatic
expiration
date
for
pipelines
that
include
artifacts,
so
that
we
don't
have
a
massive
amount
of
storage,
and
so
when
those
expire,
sometimes
there's
pipelines
that
depend
on
those
artifacts
and
then
those
pipelines
will
fail
because
the
artifact
is
expired.
B
So
you
have
to
go
back
and
rerun
that
initial
pipeline,
but
they're
only
important
when
that
dependent
like
dependable,
like
track
happens,
otherwise
they
don't
care
about
them.
So
that
was
interesting
too,
because
I
was
listing
all
of
the
expired
artifacts
hayana.
Do
you
wanna
voice,
even
though
you're
still
typing
sorry.
A
Yeah,
no,
I
think
it
you
gotta
answer
to
my
question.
I
was
wondering
if
there
is
so
far
if
you
heard
any
insights
about
those
pipelines,
those
jobs
and
the
art
facts,
artifacts
being
related
to
a
release
right
or
that
deploy
a
job.
I
think
and
why
that
would
be
important
to
debug
at
the
group
level.
A
That's
related
to
the
link,
the
issue
I
added
here
for
organization
level,
environment,
page
and
one
of
the
jobs
and
also
the
tasks
right
that
you
will
cover
with
a
page
like
that
at
the
higher
level,
similar
to
what
you're
mentioning
so,
you
know
being
able
to
move
things
and
out
of
a
release.
For
example,
debug,
a
failed
deployment
pipeline
see
the
status
of
what
goes
into
production,
but
also,
where
is
that
in
the
flow
etc?
A
So,
just
wondering
if,
if
you
heard
anything
related
particularly
to
release
it
so
far,.
B
Yeah,
the
the
one
thing
I
did
here
is
the
like:
the
pen
pipelines
type
of
thing.
I
also
have
heard
sometimes
so-
the
art,
the
artifacts
that
we're
talking
about,
though,
are
usually
just
passed
between
pipelines,
they're
not
used
to
be
like
deployed
out
into
whatever
they're
usually
used
as
like
reports
or
like
logging
kind
of
so
I
haven't
found
anything
that
really
overlaps
with
things
that
are
going
to
be
deployed
and
released.
A
Yeah,
that
sounds
good.
If
you,
if
you
see
anything,
then
just
be
me
in
the
in
the
research
issue
and
I'll
have
a
look,
because
when
talking
to
people
about
environments
and
for
example,
when
I
asked
them,
where
would
you
go
to
see
the
status
of
your
latest
deployment
or
where
would
you
go
to
debug?
A
I
don't
know
a
deploy
pipeline
that
has
failed.
They
would
always
go
to
the
pipeline's
overview.
They
would
not
go
not
always,
but
I
would
say,
like
70
of
them.
We
just
navigate
back
to
pipelines
to
see
that
and
we
have
been
talking
the
release
teams
in
in
implementing
a
view
of
environments
at
the
group
level.
But
if
the
pipeline
view
already
solves
that
problem,
I
think
you'll
be
interested
going
to
be
able
to
connect
with
insights.
So
we
don't.
A
B
No,
I
understand
what
you're
saying
we
had.
I
had
this
similar
thought
of
like.
Should
this
really
be
a
separate
page,
or
should
this
be
integrated
into
the
pipelines
page
already,
and
it's
really
hard
with
performance
as
well,
because
I
think
my
page
is
like
so
there's
so
much
there,
but
yeah
I'll
I'll.
Let
you
know
I'll
keep
you
updated,
yeah.
A
Awesome
and
then
I'll
share
later
with
you,
the
polisher,
already
the
link
here,
but
I'm
working
on
some
some
of
the
prototypes
and
when
I
have
that
added
to
the
issue
I'll
share
with
you.
So
you
can
see
how
that
relates
to
or
how
that
might
relate
to
what
you're
investigating.
C
Yeah
high
on
your
comments
about
wanting
to
see
things
at
a
organizational
level
for
environments
is
something
I've
seen
in
other
research.
I've
done
too.
So
I
help
out
with
the
enablement
group
and
for
global
search.
We
found
a
lot
of
people
talking
about
when
I
search
for
something
in
gate
lab.
I
just
want
to
be
able
to
search
within
my
organization,
not
just
like
a
specific
project
or
a
specific
group,
but
just
like
everything
for
my
company
that
they,
you
know
they
have.
A
Yeah,
that's
a
good
call
out
will
and
like
my
first
thought
is
like
performance
exactly
what
gina
just
mentioned,
that
you
know
in
the
past,
why
we
kept
separating
things
at
a
good
level
or
project
level,
or
you
know,
environment
deployment.
It's
also
because
we
cannot
support
all
this.
A
This
data,
or
I
think
we
can
but
there's
a
there's,
a
a
lot
that
needs
to
be
fixed
in
the
in
the
back
end
for
that
to
happen,
and
then,
for
example,
if
you
go
to
the
environment
dashboard,
which
is
not
the
environment
page,
you
know
that
we
have
something
separate
here.
I'm
gonna
drop
a
link
here
in
our
agenda,
real
quick.
This
is
where,
ideally,
you
would
go.
A
You
know
to
to
track
environments
across
multiple
projects
or
different
groups,
but
then
you
can
only
show
three
environments
per
project
at
a
time,
so
yeah
that
that's
why
people,
as
I
mentioned
before,
they
just
go
to
the
pipelines
page
and
I,
if
you
can
brush
translator,
will
to
those.
In
fact,
it
will
be
helpful
because
chris
also
asked
me
to
start
looking
at
this
environment
at
the
group
level
and
that's
why
I'm
like?
A
Let's
validate
that,
let's
have
the
jobs
to
be
done
first,
because
my
gut
feeling
my
experience
with
gitlab
safe,
we
don't
need
that
right,
we
kind
of
if
we
are
able
to
highlight
some
information
or
give
people
the
ability
to
filter
or
search
whatever
in
places
where
they
already
go
today.
Maybe
that's
a
you
know:
a
low-hanging
fruit
rather
than
a
redesign
anyways.
That's
me
brave,
starving,
so
I'll
stop
here.
C
Okay,
yeah
thanks
for
thanks
for
sharing
and
gina
sorry
for
the
collaboration
traffic
that
I'm
contributing
to.
I
guess
no.
B
Right,
I'm
gonna
I'll
finish
up
with
the
last
thing:
I'm
working
on
validating
the
new
list,
view
for
the
runner
admin
view
and
hayana.
I'm
gonna
start
recruiting
next.
My
my
goal
is
next
week.
I
have
a
discussion
guide.
That's
work
in
progress
right
now,
but
I'm
going
to
mix
unmoderated
and
moderated
so
I'm
going
to
only
interview
some
of
our
internal
gitlab
team
members
so
that
I'm
not
like
waiting
on
it
like
recruiting
the
enterprise
customers
which
has
taken
a
while
with
the
artifact
stuff.
A
All
right,
thanks,
gina
I'll
share
the
the
the
list
of
participants
that
I
use
for
the
environment
that
I
researched
because
remember
that
some
of
them
mentioned
runners
as
well,
so
you
might
want
to
have
a
look
there
and
see
if
any
of
those
are
going
to
be
useful
to
you.
Let
me
find
that
now
yeah.
Actually
you
you
share
that
with
me.
Right
will.
C
A
Yeah
here
share
with
me
I'll
share
with
katie
as
well
here
link
and
let's
see
here,
gina.
Thank
you.
I
think
there
were
at
least
two
of
them
mentioned
runners.
I
think
that's!
That's
the
one
time
I
pinged
you
that
I
that
I
looked
you
in
the
comment
section.
Okay,
I
think
you
need
breakfast.
Let
me
ask
you:
I
do.
A
I
guess
I'm
next,
I'm
out
of
office
on
monday,
the
6th,
it's
a
public
holiday
here
in
the
netherlands
and
I'm
also
out
of
office
in
june
14th
until
the
23rd
you've
already
mentioned,
that
to
all
of
you
we're
going
to
wanna
ones,
but
there's
a
coverage
issue
at
a
link
here
again
and
it's
your
work
in
progress.
But
you
got
a
very
issue
you
can
see.
A
A
So
that's
that
I'm
finishing
reading
that
handbook
page
and
we'll
see
what's
gonna
happen.
There
we're
gonna,
be
the
first
ones
doing
that
that
workshop,
that's
cool
and
then
other
than
environment.
So
I
have
to
I
didn't
add
here,
but
I
have
to
wrap
up
the
insights
on
the
research
that
I
conducted
and
then
also
I've
been
helping
collaborating
with
chris
and
will
on
the
benchmarking
for
release.
A
So
I
also
wrapped
that
up
just
I
think,
like
half
an
hour
ago,
trying
to
determine
which
tasks
happen
in
the
ui
and
api,
so
that
we'll
know
how
to
set
up
the
test
environment
but
also
the
tasks
that
are
going
to
go
through
doing
that.
Yeah.
Maybe
we'll
maybe
we'll
talk
about
that
later,
but
anything
you'd
like
to
add
about
the
benchmarking
project.
C
No,
we
had
a.
We
had
a
very
in-depth
discussion
about
it
a
couple
hours
ago
between
you,
myself
and
chris.
A
There
are
a
couple
updates
here
from
package
and
pipeline
authoring,
so
katie
and
nadia
had
a
session
earlier
today.
So
please
have
a
look
and
leave
comments.
If
you
have
any
and
these
days
out
of
office
this
whole
week,
she'll
be
back.
I
think
she's
back
next
week,
yeah
next
week
on
monday,
so
we're
gonna
skip
pipeline
execution
this
week
and
then
over
to
will
for
the
research
efforts.
C
Nice,
so
I'm
out
of
office
this
friday
I'll
be
back
on
monday
to
catch
up
on
things
and
as
I
spoke
to
a
minute
ago,
you
know
I
met
with
pioneer
and
chris
to
talk
through
different
release
topics,
specifically
the
usability
benchmarking
study,
I've
linked
to
the
mural
that
has
been
updated
a
little
bit
since
we
last
spoke
so
there's
a
list
of,
I
think
31
different
tasks
that
we
could
potentially
do
and
we'll
need
to
narrow
that
down
in
probably
the
next
week
or
so.
C
So
I'll
be
helping
out
with
that
and
then
creating
a
ux
sandbox
project.
I've
been
speaking
with
one
of
the
other
researchers
who's
done
that
and
he
added
a
lot
of
content
that
went
into
that
handbook
page
that
I
could
actually
link
to
so
I'll.
Add
that
page
in
just
a
moment
but
yeah
that
that's
kind
of
it
for
me
at
the
moment
any
comments
or
questions.
A
I
comment-
I
think
I
already
mentioned
this
in
slack,
but
for
the
the
tasks
that
we
we
added
to
the
the
mural
board.
I
I
think
that
there
are
a
couple
of
things
here
that
we
cannot
do
with
the
product
today.
A
So
what
do
we
do
with
those
tests
that
will
do
we
remove
them?
Do
we
leave
them
there
but
kind
of
like
because
we're
not
going
to
assess
it
right?
The
usability
if
we
cannot
perform
that
particular
test.
C
Yeah,
that's
a
good
question.
I
think
we'll
just
have
to
move
on,
because
we
we
can't
really
assess
them.
If
we
can't
actually
create
an
environment
where
participants
could
actually
complete
the
task.
C
We
could
make
note
in
the
report
that,
like
you
know,
we
wanted
to
do
these
tasks
and
like
list
them
out,
but
then
you
know
say
that
this
would
be
something
to
to
get
at
it
the
future.
If,
if
you
know
we
have
time
and
because
you
know
the
usability
benchmark
is
not
just
like
a
one
and
done
thing,
you
can
do
it.
I
think
roughly,
like
once
a
year
is
what
the
handbook
talks
about
so
yeah.
I
think
that's
that
would
just
like
get
added
to
a
backlog
in
a
sense.
A
No,
that
makes
sense
and
I'm
referring
to
create
a
release-
audit
checklist
in
particular,
I
actually
added
that
one
picky
and
the
task-
and
I'm
like
how
do
they
do
that
today
and
I
think
that's
a
a
good
way
to
find
out
is
checking
the
the
delivery
team
because
they're
the
ones
that
produce
with
kickfab,
but
I
know
that
it's
a
manual
task,
maybe
done
outside
of
gitlab.
A
So
do
we
measure
that
do
we
track
that
particular
you
know
scenario,
but
I
can
investigate
about
this.
This
sticky
create
really
solid
checklist.
C
Do
you
want
me
to
speak
to
erica's
stuff,
so
she's
got
her
prioritization
issue.
Still
there
she's
included
a
link
to
the
field,
notes
that
she
took
and
a
summary
that
she
did
based
on
her
experience
at
kubecon
that
I
think
was
about
a
week
or
two
ago,
so
definitely
check
that
out.
If,
if
you
haven't
already
I've
seen
some
of
the
documentation
that
she's
already
shared-
and
it's
it's-
you
know
very
extensive,
so
I
recommend
it
ayanna.
Did
you
want
to
voice
your
comment.
A
Yeah
so
I
haven't
had
a
chance
to
get
her
feedback
yet
so
I'm
just
asynchronously
saying
well
and
now
watching
the
video.
A
Thank
you
erica
for
moving
back
my
reminder
like
by
one
day,
because
she
created
writer,
reminders
to
like
the
product
designer
and
myself
to
go
over
the
dock
and
then
provide
her
with
feedback
and
everything.
I
haven't
done
that
yet
so
it's
in
my
list
and
it's
awesome
that
she
shared
those
insights
with
us
not
have
a
chance
to
see
and
also
learn
more
from
her
experience
as
well
from
cucumber.
C
And
then
it
looks
like
she's
working
on
the
analysis
and
report
for
the
kubecon
product
directions
survey.
She
shared
that
with
the
research
team
late
yesterday
and
I
provided
some
feedback
just
kind
of
in
an
early
review
state.
But
that's
that's
at
a
point
where
I
think
it's
pretty
close
to
being
shared
out
more
broadly.
C
And
then
she's
also
waiting
for
tim
to
review
the
shared
resource,
library
and
ci
templates
report
and
then
creating
actual
insights
as
well.
B
Erica
had
helped
me
if,
if
you're
watching
this,
thank
you,
she
had
helped
me
with
a
promotional
game
for
a
job
to
be
done.
Survey
that
we're
doing
for
artifacts,
and
it
was
really
she
had
this
like
whole
document
of
how
to
easily
pull
in
this,
the
block
basically
to
qualtrics,
and
so
I
wanted
to
ask-
and
I
can
just
ping-
I
could
ask
her
an
issue
or
something
if
that
would
be
something
that
we
could
add
to
the
handbook,
because
I
think
a
lot
of
people
would
use
that
for
surveys.
C
I
think
I
know
a
little
bit
about
what
you're
describing.
Could
you
like
explain
a
little
bit
more
by
what
you
mean
that,
like
she
was
able
to
pull
in
the
whole
block
into
qualtrics.
B
Yeah
in
qualtrics
you
can
use.
I
think
it's
called
like
shared
questions,
maybe
that
your
your
organization
can
use-
and
there
was
one
specifically
that
was
created
by
it-
must
be
from
the
research
team
that
was
for
this
promotional
game,
so
that
participants
would
be
given
and
like
get
put
into
a
game
to
win.
60
dollar
amazon
gift
cards.
B
C
Oh
yes,
I
I've
seen
this
exact
thing
and
I
actually
made
the
same
exact
comment
to
her.
I
was
like
wow.
This
is
really
good.
You
should
put
this
in
the
handbook
and
yeah.
I
forget
what
she
told
me
at
the
time.
I
think
she
was
maybe
like.
I
want
to
pilot
this
or
like
test
it
out
a
little
bit
more
before
I
put
it
in
there
but
yeah
I
was.
I
had
the
same
thought
as
judas.
B
I
was
because
it
made
it
so
it
was
so
easy
to
just
put
in
there
so
I'll,
maybe
I'll,
just
catch
up
with
her
and
see
if
it
would
be
possible.
A
Nice
and
that's
it,
thank
you
for
joining
for
brainstorming
and
chatting.
I'm
gonna
see
you
next
time.
Thanks,
bye,
bye,.