►
From YouTube: CI/CD UX Meeting 2023-07-19
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
Added
alright
today
is
the
19th
July
and
we
are
meeting
for
cicd
ux
discussions.
A
There
are
some
starting
topics,
there's
just
one
impact
which
is
by
me.
So
in
pipeline
security
we
are
kind
of
experiencing
something
like
we
are
getting
Community
contributions
which
are
not
directly
related
to
any
issues
and
those
contributions.
They
are
like
not
very
small
in
nature.
So
what
ends
up
happening?
Is
it
kind
of
like
ends
up
being
in
conflict
with
something
that
we
already
have
plans
for
and
we
try
to
make
changes
so
that
we
can
accommodate
it
like?
A
A
So
probably
they
might
bring
in
a
couple
more
automations
to
the
process
or
some
additional
label
that
would
require
contributors
to
ensure
that
they
at
least
look
up
for
issues
which
are
relating
to
the
change
that
they're
proposing,
and
that
would
also
help
us
make
sure
that
we
are
not
discouraging
anyone
from
making
contributions,
because,
of
course,
if
we
just
continue
the
discussions
for
a
month
or
more
than
that
and
just
keep
on
changing
making
changes
to
the
decisions,
it's
not
I
would
say
for
someone
who's
taking
out
time
from
their
personal
time
to
do
this
work.
A
B
Yeah,
because
this
happened
to
me
as
well-
and
it
gets
a
little
frustrating,
especially
for
designers,
because
we
tend
to
have
to
go
back
and
like
retroactively
design
based
on
the
contribution
and
for
Runner
we
saw
it
was
the
same
contributor
every
time
who
was
doing
it.
So
we
ended
up
talking
with
the
contributor
success
team
and
then
met
with
them,
plus
the
contributor
and
kind
of
like
talked
about
our
road
map,
so
that
we
talked
about
our
roadmap
and
also
what
they
were
thinking
on
on
their
roadmap.
B
So
we
can
come
together
on
those
things
and
what
I
suggested
I
mean.
Obviously
we
have
to
like
be
open
to
them.
Contributing
so
I
suggested
that
if
they
have
like
a
new
feature
that
they
want
to
create,
they
create
an
issue
first
and
tag
me,
and
that
puts
a
lot
of
responsibility
on
us.
But
I
also
think
it
gets
us
involved
earlier.
B
A
A
Okay,
if
there
are
no
more
comments,
let's
move
to
product
design
so
for
the
first
section
which
is
switchboard
Hannah
has
some
updates
that
she's
working
on
the
backfield
requirement
for
Ali's
position
and
if
there's
anything
that
any
of
the
team
members
have
been
working
on
with
Ali,
they
can
just
let
her
know.
So
she
can
work
on
finding
alternatives.
A
Any
others
I
think
NFI
for
Emily
that
the
pairs
would
be
rotated
by
the
end
of
July
and
for
the
rest
of
us
as
well.
Of
course,
yeah
next
is
Gina.
B
Yeah
I'm
gonna
drop
a
little
bit
early
from
this
meeting,
but
also
the
things
that
I've
been
working
on
are
mental
model
research
for
runners
which
I
completed
and
thank
you
to
Erica's,
not
on
the
call,
but
if
she
watches
the
recording,
she
helped
me
a
ton
with
this
project,
so
yeah
thank
you,
Eric,
and
she
gave
me
a
skeleton
of
her
report
to
be
able
to
fill
out
with
all
the
analysis.
It's
still
a
work
in
progress,
but
you're
welcome
to
check
it
out.
I
also
added
a
summary
to
the
issue,
though.
B
So
what
came
out
of
it
was
defined
groups
of
the
runner
Concepts
that
users
think
about
when
they're
using
Runners,
and
then
we
also
had
them
like
come
up
with
their
own
terms
to
describe
certain
definitions
which
almost
all
were
not
aligned
with
what
we
use
at
gitlab.
But
conceptually
you
saw
some
connections
there.
B
They
just
weren't
the
exact
same
terms
and
then
the
final
exercise
was
to
have
them
match
the
terms
to
definitions,
like
the
terms
that
we
used
to
at
gitlab
to
the
definitions
and
most
of
those
they
did,
they
were
not
able
to
match
accurately
as
we
Define
them
at
gitlab.
So
there
was
a
lot
of
learnings,
but
what
I'm
seeing
now
is
the
next
thing
I
want
to
do
with
that.
B
But
what
I'm
seeing
now
is
that
the
team
is
very
it's
difficult
for
the
team
to
like
understand
that
these
Concepts
were
grouped
together
because
it
doesn't
align
with
how
Runner
actually
works
so
yeah.
It's
it's.
People
are
having
a
hard
time
looking
past,
like
the
technical
way
that
it
works
and
then
how
people
are
grouping
them
and
I
was
wondering
if
anyone
has
run
into
that
problem
and
kind
of
how
you're
approaching
it.
With
your
team.
C
Well,
I
I
did
want
to
give
you
space
to
see
if
anybody
has
like
thoughts
on
the
question
that
you
just
raised,
because
my
question's
a
little
bit
unrelated
okay,.
A
I
think
what
Emily
did
with
environments
was
something
similar
because
they
challenged
the
existing
ideas
of
Concepts
that
were
like
that
were
there
since
forever
in
gitlab.
So
I
don't
know.
Maybe
any
insights
like
how
did
the
team
take
take
it
when
they
learned,
but
this
was
rather
something
that
the
team
was
involved
in.
So
probably
that's
how
it
was
different
because
it
was
not
coming
from
outside,
but.
D
E
E
We
also
had
a
lot
of
research
to
back
that
our
current
feature
wasn't
working
so
I
think
that
made
it
easy
to
convince
the
team
because,
through
like
the
group
level,
environments,
research,
additional
research
before
we
were
aware,
like
this
feature,
wasn't
really
hitting
the
Mark,
so
collectively
I
think
it
was
much
easier
to
move
forward
versus
yeah
it
coming
from
someone
else.
So.
B
It
almost
feels
like
we
internally
because
we're
touching
it
all
the
time
we
have
a
much
deeper
understanding
of
it
than
our
users.
The
majority
of
our
users,
I,
would
say,
but
also
the
admins
or
platform
Engineers
who
are
managing
their
own
Runners
have
a
very
similar
understanding,
as
we
do
so
it's
hard
to
get
it's
hard
for
me
to
be
like
they're,
not
understanding
it
when
we
know
that
they
are
because
people
love
the
future.
A
The
one
thing
that
helped
us
like
I
know
we
are
at
a
very
I,
would
say
nice
and
stage
in
the
entire
native
Secrets
manager
concept.
But
one
thing
that
helped
us
was
the
competitor
evaluation,
because,
like
the
entire
team
got
to
like
take
a
peek
into
how
the
rest
of
the
industry
is
referring
to
different
concepts
and
that
also
helped
them
relate
with
the
research
data
that
Erica
had
like
created
reports
on
so
everything
together,
they
were
able
to
relate
one
thing
to
another
and
that
helped
in
like
gain
that
conviction.
A
B
C
Very
much
just
circling
back
to
my
question:
how
did
you
decide
to
get
survey
data
or
you
know,
Target
100
people.
B
Yeah
so
Erica
suggested
that
we
run
the
survey
for
I
think
a
month
and
a
half
I
think
it
was
or
we
or
when
we
get
to
100
people
like
whichever
one
comes
first
and
I.
She
was
saying
100
because,
like
that's,
the
average
number
that
they've
been
seeing
Trends
Lately
from
surveys.
But
if
you
have
other
suggestions,
I
am
very
open
to
it.
C
Yeah
I've
used,
like
survey
sample
size
calculators,
which
I
can
certainly
link
to
here.
So
if
you
know
like
how
many
people
are
using
a
particular
feature,
because
I
know
that
we
have
like
a
lot
of
internal
metrics
on
like
who's,
a
user
of
this
Stage
Group
or
that
stage
group,
you
could
use
that
as
a
little
bit
of
a
guide
into
like
okay.
If
our
population
is
X,
then
we
should
survey
this
many
people
to
get
somewhat
of
a
representative
sample
size,
but
yeah
I'll
include
one
below.
B
C
Yeah
so
I
added
a
link
there.
If
you
click
into
it,
you'll
notice
that
it
has
like
three
different
sections:
you
don't
really
have
to
mess
with
confidence,
interval
or
margin
of
error.
You
would
just
have
to
enter
the
population
size.
C
E
We're
good
excellent,
so
just
a
small
update
with
the
outcome
of
the
design
Sprint.
We
were
trying
to
figure
out
the
best
way
to
go
forward
with
the
research
here
and
we've
started
with
a
just
internal
customer
interviews
with
the
SRE
and
delivery
team
around
this
service
concept,
getting
a
better
idea
of
what
they
consider
Services,
how
we
would
populate
that
list
and
after
we're
done
those
internal
interviews
which
I
think
we
have
like
six
happening
this
week.
E
A
big
thank
you
to
Victor
for
scheduling
them,
we'll
be
able
to
move
forward
with,
like
external
user
testing,
just
an
update
on
that
front.
The
other
one
is
I'll,
be
working
on
this
design
issue
around
designing
for
external
jobs
and
I
believe
this
touches
kind
of
like
the
job
Details
page,
the
jobless
page
and
the
pipeline
Details
page
I'm,
not
sure
if
any
of
those
fall
into
the
verified
teams
that
have
designers.
But
if
they
do
just,
let
me
know
so.
I
can
involve
you
in
kind
of
feedback.
For
these
pages.
A
I
can
help
because
I
like
I,
took
part
in
a
lot
of
researches
for
those
pages,
so
I
can
help
with
any
feedback,
but
otherwise
there's
no
designer
for
pipeline
execution.
B
E
Yeah,
this
is
mostly
just
designing
it
around
this
new,
like
external
job
thing
and
what
visuals
will
show,
but
I
think
it'll
touch
like
all
of
these
pages,
so
figuring
that
out
as
I
go
forward.
E
Yeah
yeah,
so
this
is
one
that
I'm
just
starting
into
so
I
have
to
kind
of
look
for
it,
but
this
is,
as
far
as
I
know,
a
CI
job,
that's
being
executed
outside
of
git
lab.
A
E
E
No
worries
it's
so
what
this
is
is
I'm
reading
the
set
is
like
it's
adding
a
new
job
status,
which
will
represent
CI
jobs
that
are
currently
being
executed
by
a
service
external
to
gitlab,
so
adding
in
like
a
pending
kind
of
state
as
that
is
being
run
and
then
yeah.
So
I'll
actually
link
the
engineering
issue
here.
That
explains
it
a
bit
more
than
the
design
issue.
B
If
that
is
helpful,
I'm
also
reading
the
Epic-
and
it
says
external
jobs-
are
not
picked
up
by
a
runner,
so
it
might
not
even
connect
with
me
and
if
so,
you
don't
have
to.
Let
me
in.
A
E
Yeah,
this
is
new
for
16-3
I
just
started
looking
into
it
so
as
I
learn
more
I'll
reach
out,
but
it's
a
fairly
new
thing.
We're
looking
into
so
I.
Don't
have
all
the
details
right
now,
but
I'm
sure
over
the
next
week,
I'll
have
more.
D
D
A
It
with
me,
then
I
will
take
up
and
so
I'm,
mostly
focusing
on
just
one
thing.
A
Besides
a
couple
of
community
contributions
this
week
and
that's
the
like
finishing
the
POC
prototype,
so
I
created
the
user
map
inflow
on
big
jam,
it
looks
so
good
and
based
on
this
particular
story,
mapping
I
would
be
like
designing
the
different
pages
or
the
different
actions
for
this
flow,
and
that's
for
this
another
thing
that
I
wanted
to
share
was
I'm,
starting
to
add,
like
I've
added
a
slot
to
my
calendar
from
starting
next
week
for
every
Thursday
morning,
kind
of
a
time
that
suits
all
of
us,
like
all
the
members
in
the
CI
CD
team,
at
least-
and
this
is
for
like
to
have
a
sync
time
with
me-
to
discuss
just
anything
that
relates
to
public
presence.
A
We
can
just
like
use
this
thing
time
to
discuss
a
Blog
proposal
to
edit
a
Blog.
That's
already
there
to
like
write,
abstracts,
select
conferences,
designing
content
for
presentations,
I
mean
just
anything
that
comes
to
your
mind.
We
can
use
this
time
for
that
and
to
be
like
how
you
can
add
yourself,
you
can
just
like
go
to
the
link,
add
it
to
your
calendar
and
for
whichever
week
you
have
booked
it,
others
would
not
book
it
for
that
particular
week
yeah
and
that
is
it.
E
E
A
Yeah,
okay,
I'm
also
not
a
part
of
it.
That
is
amazing.
A
Yeah
or
we
can
just
like
synchronous
like
catch
up
over
slack
in
just
book
slots
manually
if
this
doesn't
work,
I'm,
not
so
good,
with
automating
things.
A
And
that's
it
yeah
sending
you
can
take
it
up.
D
No
I
just
wanted
to
say
plus
one
but
yeah,
it's
my
turn.
Okay,
so
I'll
type
it
later
so
thanks,
vitika
I
have
two
items
that
I
like
to
share
that
Dove
and
Mark,
and
myself
we're
planning
the
Q3
that
what
could
be
the
cicd
catalog
beta
and
then
what
could
be
included
technically
and
also
from
the
user
standpoint,
and
it's
almost
like
defined,
and
then
we
also
announced
it
to
the
team
and
then
now
team
is
on
board.
So
that's
exciting.
D
That
means
so,
just
to
tell
you
a
little
bit
of
more
details,
we
will
gather
more
metadata
from
now
on,
so
that
we
just
just
don't
need
to
hold
like
just
depend
on
the
readme.md
that
user
right
and
then
this
is
your
component
A
and
B
and
C
like
through
now
like
we
have
to
just
let
them
write
everything
and
then
just
slowly
depend
on
this
instruction,
but
you
like
to
kind
of
provide
a
better
assistance
and
suggestion
system.
D
So
this
is
exciting
for
me,
because
it'll
open
the
doors
for
the
further
ux
opportunities,
so
I'd
like
to
share
this,
and
the
other
point
is
probably
you
might
see
this
in
the
Mrs
pipeline
path.
There
is
a
now
failed.
Job
number
is
surfacing
in
those
tabs,
so
that
was
the
idea
for
this
hackathon
and
then
luckily
we
get
a
lot
of
positive
feedback.
D
D
Thanks
Erica
is
on
leave,
so
I'll
move
it
over
to
Bill.
C
Thanks
engine,
so
I
just
wanted
to
quickly
touch
on
an
additional
point
about
the.
B
C
Calculator
that
I
spoke
about
a
couple
of
minutes
ago
added
some
information
earlier
on,
but
I
would
just
recommend
you
know
working
with
your
researcher.
If
you
decide
to
use
one
of
those
types
of
tools
to
figure
out,
what's
the
appropriate
like
margin
of
error
and
confidence
interval,
because
if
you
leave
it,
as
is
that's
those
things
are
more
like
academic
standard,
so
it'll
tell
you
that
you
need
probably
more
than
you
really
do.
C
C
Second
half
of
August
I've
created
my
Q3
prioritization
issue
and
linked
to
that
here
a
lot
of
the
stuff
that's
represented.
There
is
just
carrying
over
from
this
quarter.
That's
still
active
and
then
I'm
going
to
be
picking
up
some
projects
that
are
paused
and
then,
since
Ali
has
departed.
C
Git
lab
I'm,
coordinating
with
the
PM
Lauren
and
then
hyana
to
determine
next
steps
for
the
solution,
validation
project
that
he
was
leading
so
we're
meeting
on
Thursday
to
discuss
this
more
in
a
sink
call,
but
we're
also
having
async
discussions
about
it,
like
kind
of
if
Hyatt
is
going
to
be
able
to
drive
it
while
I'm
out,
if
we're
going
to
just
kind
of
keep
it
pause
for
the
next
couple
weeks
until
I'm
back
those
sort
of
things.
So
that's
what's
going
on
with
me
right
now,.
C
Yeah,
my
wife
goes
back
to
work
next
week
for
the
first
time
in
like
12
weeks,
so
I'm
I'm
gonna
be
on
full
Dead
Duty
yeah,
24
7.,
so
give
it.
A
Okay,
so
with
that,
we
have,
at
the
end
of
the
agenda
anything
that
anyone
wants
to
bring
up.