►
From YouTube: CI/CD UX Meeting - 12-04-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
Yes,
I:
when,
honestly,
when
I
was
filling
out,
the
agenda
I
wasn't
sure
what
I
should
be
focusing
on
and
I
was
so
I
wanted
to
bring
it
up
with
the
group
and
just
ask
how
you've
been
feeling
with
the
structure
of
the
call.
The
specific
thing
I
was
confused
with
was
if
we
should
be
focused
on
a
design
review
or
if
we
are
normally
like
going
through.
All
of
our
group
updates.
D
D
A
A
Oh
I
I
think
it's
more
like
if
the
designer
view
takes
a
while
it
can
like
we
don't
stop
it
from
taking
a
while
and
then,
if
it
doesn't,
we
go
through
the
updates
that
should
work
pretty
well
all
right.
B
B
And
I
have
the
next
link,
okay,
so
the
design
this
shouldn't
really
shouldn't.
Take
that
long,
I've
been
I've
presented
in
the
past.
How
we're
updating
our
runner
creation
form,
which
is
really
a
nice
update,
because
we
get
to
do
a
lot
more
things
in
the
UI
and
explain
what
different
Runner
concepts
are
versus
before
it
was
just
in
the
CLI
and
the
problem
statement.
B
Concepts
are
unknown
to
these
novice
users
and
they're
they're,
not
sure
how
it
kind
of
fits
into
like
the
larger
scope
of
CI
CD
and
then
the
feature
that
I'm
trying
to
work
on
now
is
making
the
the
registration
form,
which
is
the
the
first
iteration
that
I
created
for
the
new
form
I'm
trying
to
make
it
a
little
bit
easier
to
digest,
which
it's
super
long
right
now.
So
it's
kind
of
hard
to
do
that
and
I
think
this
would
be
mostly
for
developers
whose
admin
like
restricted
their
shared
Runner
usage.
B
B
We
don't
show
those
in
the
UI,
though
it's
only
in
the
config
file,
so
now
I'm
gonna,
I'm
gonna,
open
up
my
figma
all
right.
So
to
give
you
just
so
we
have
a
before
state.
B
This
is
what
the
first
iteration
of
the
registration
looks
like
or
creation,
we're
calling
creation.
So
when
you
want
to
make
a
new
Runner,
you
have
to
select
the
operating
system
or
or
whatever
platform
you
want
to
make
it
on.
And
then
after
you
select
it,
you
get
this
like
form
of
different
fields
that
you
need
to
fill
out.
B
A
lot
of
them
are
optional,
but
the
only
thing
that's
not
optional
is
the
tags.
You
have
to
either
add
tags
or
you
have
to
select
run
untagged
jobs,
it's
one
of
the
one
or
the
other,
and
then
once
you
create
it,
you
get.
You
still
have
to
go
in
the
CLI,
but
you
get
like
this
one
thing
that
you
can
copy
paste
in
the
CLI,
and
then
you
have
a
runner.
B
I
was
looking
at
like
if
we
have
any
patterns
in
pajamas
yet
for
I
would
call
this
like
a
stepper,
but
I
guess
you
could
think
of
it
as
a
wizard
as
well,
and
I
saw
that
we
had
an
issue
that
was
already
open.
That
has
a
lot
of
work
done
so
I
kind
of
brought
that
into
this
View
and
I'm,
hoping
by
breaking
these
up
a
bit
more
I
can
help.
B
One
users
understand
the
concepts
a
little
bit
better,
because
kind
of
the
most
important
thing
is
the
tags
which
I
broke
out
into
its
own
step
and
then
I
can
also
get
at
the
fact
that
you
either
need
to
add
tags
or
you
have
to
mark
it
as
untagged.
B
So
the
design
is
really
just
like
breaking
these
up.
So
it's
not
as
long
so,
if
you
click
next
here
you'd
then
go
to
tags,
and
it's
the
only
one.
Also
that's
not
optional,
so
you
would
have
to
select
either
ad
tags
or
select
this
and
then
go
next
and
then
this
whole
step
is
optional
for
details
and
configuration.
So
you
could
just
go
next
immediately
and
then
you
get
to
that
same
screen
at
the
end
of
registration,
but
I
think
my
main
question
was
in
this
pattern.
F
For
me,
I
don't
have
any
other
like
adoption
for
this,
but
probably
in
the
future.
Yes,
and
so
I
was
like
looking
into
the
other
issue.
So
this
is
outside
of
verify,
but
I
have
seen
that
there
is
a
new
it's
behind
the
feature
flag
that
gitlab
Pages
team.
They
are
having
similar
Resort
things
on
the
UI
I'm,
not
so
sure
like
if
it
is
delivered
by
any
of
designers,
but
it
was
implemented
by
a
front-end
engineer.
F
F
Yes
and
then
making
those
two
different
sites
to
making
a
Geo
connection
so
that
they
can
start
mirroring
all
the
data
inside
one
GitHub
instance
to
the
other.
One.
A
Yeah
I
was
gonna,
say
the
same
thing,
not
so
much
on
my
current
team,
but
on
the
growth
team.
These
were
like
the
step
count
like
how
you
set
things
up.
I
know
we
were
playing
around
with
these
quite
a
lot
and
I.
Don't
think
we
ever
actually
came
up
with
a
component
for
it,
but
there
was
definitely
a
use
case
in
most
kind
of
setups,
like
setting
up
your
account
setting
up
and
getting
onboarded
into
certain
things.
A
So
I
do
think
it'll
be
useful
to
actually
finally
create
a
component,
because
this
is
something
we've
circled
on
for
months
on
that
team.
Okay,.
E
Yeah
also
in
in
my
area,
apparently
we're
working
on
the
onboarding
flow
and
it's
also
a
very
form.
Heavy
we've
tried
ways
to
kind
of
cut
it
down
and
include
some
navigation,
but
yeah.
We
certainly
didn't
think
of
going
the
stepper
Direction,
but
I
think
yeah
definitely
use
it
if
it's
available
I'll
copy
yours
in
fact,.
A
I
know
when
I
was
working
with
anti-abuse
temporarily.
We
also
did
like
something
like
this,
except
it
kind
of
went
down
the
page,
so
it
was
certain
like
collapsible
sections
that
reopened
yeah.
It
was
exactly
something
like
this:
okay.
B
Yeah
I
think
the
thought
was
that
and
Lee
Moore
was
doing
a
lot
of
work
on
this
before
so
he
had
created
a
bunch
of
different
options
like
vertical
a
lot
of.
Sometimes
you
can
jump
between
different
steps,
so
there's
that
option
as
well
and
then
there's
horizontal
and
then
this
linear
option
as
well.
B
I
think
the
only
other
thing
that
I
had
in
mind
was
something
that's
more
like
this,
where
you're
it's
more,
it's
like
looking
at
a
process,
so
in
this
case
it
was
updating
Runners.
We
don't
even
have
this
available
today,
but
in
the
future
we
might
and
I
was
thinking.
We
could
reuse
the
same
icons
that
we
use
for
the
Mr
widgets
and
then
just
like
give
status
of
each
step
that
you
go
through
because
there's
something
happening
in
the
like
I
could.
B
I'm
gonna
play
around
with
that
a
little
bit,
Erica
and
well
I
know
you
had
some
comments.
You
want
to
voice
them.
C
Yeah
mine
is
just
that
I
think
when
you're
ready
to
show
this
to
folks,
we
can
recruit
from
the
sus
respondents,
so
I'm
just
working
on
a
project
where
I
looked
at
this
that's
verbatim
for
the
last
two
quarters
and
just
as
a
side
note
Runners
and
Pipelines
popped
out
as
something
that's
particularly
confusing
on
the
bright
side.
That
means
that
we
can
find
people
who
think
letters
are
confusing
and
ask
them
to
participate
in
research
for
you.
D
Yeah,
so
as
a
part
of
the
like
sus
process
will
create
an
issue
either
myself
or
or
Nick,
depending
on
who's.
D
We'll
be
creating
an
issue
for
sus
follow-up
calls,
I
think
is
probably
been
traditionally
called
like
sus
responder,
and
this
will
be
a
male.
This
is
typically
made
available
to
PMS,
but
I
certainly
think
you
could
recruit
via
that.
She
like
just
find
any
like
relevant
quotes,
and
you
know
pull
them
into
to
your
study.
As
Erica
was
saying.
C
C
And
then
another
thing:
that's
coming
up
in
the
sus
verbatim
analysis
is
that
users
want
specifically
onboarding
content
related
to
like
learning
and
documentation,
so
we've
been
pulling
out
that
learning
and
documentation
is
important,
but
it's
targetedly,
onboarding
and
then
also
onboarding
related
to
pipelines
and
I.
Think
Runners
is
included
there.
So
this
is
helpful
like
what
you're
pointing
out
there
like
what
you're
kind
of
doing
is
an
onboarding
widget,
almost
yeah.
E
B
B
Just
that,
that's
like
how
the
tags
determine
which
types
of
jobs
that
the
runner
processes.
So
then
it
gets
like
a
little
bit
more
connected
into
the
CI
CD
process
and
then
I
linked
to
documentation
and
stuff
as
well.
But
I
think
that,
there's
more
that
we
could
add
yeah.
C
And
even
stepping
back
like
it's
like
how
did
they
get
to
this
point
in
the
workflow
right
like
how
do
they
know
if
they
should
be
doing
this
or
not
yeah,
like
shared
runners,
or
not,
this
I'm
thinking
so
like?
How
do
they
know
if
they
should
be
using
that
widget.
D
Yeah
and
I
think
on
the
topic
of
like
novice
users.
There
could
be
some
opportunities
for
like
tool,
tips
or
something
implemented
over
the
course
of
those.
You
know
different
pages
or
steps
to
kind
of
communicate
like
this.
Is
why
you're
making
this
or,
if
you're,
confused
like
here's,
some
information
that
can
help
you
make
a
more
informed
decision
when
you're
choosing
between
radio
options
or
what
should
I
enter
here
or
what
it
whatever
it
may
be.
D
F
B
This
is
the
current
one
that
we're
using,
and
you
have
so
I
I
think
this
was
just
more
of
a
mistake
that
we
made
you
have
to
either
select
that
the
runner
is
gonna
run
on
tag
jobs
or
you
have
to
add
tags.
So,
even
though
we
say
this
is
optional,
you
actually
have
to
do
one
or
the
other
here.
So
that's
why
I
was
trying
to
like
break
those
out
into
their
own
section,
because
that's
really
the
only
piece.
That's
not
optional,
yeah.
That.
B
You
have
it's
so
it
gets
so
confusing.
Okay,
so
you
can
have
you
can
add
tags
and
you
can
run
on
tag
jobs,
so
our
runner
can
run
jobs
with
tags
and
it
can
also
run
jobs
without
tags.
B
E
Well,
I
guess:
I
have
the
next
item,
so
I
am
continuing
work
on
the
onboarding
floor,
close
to
finalizing
it
now.
E
E
With
our
technical
writer
to
make
sure
that
yeah
we
communicate
clearly
with
settings,
you
can
change
and
yeah
once
I'm
done,
I'll
open
an
issue
for
review
and
I.
Think
I
can
also
do
a
presentation
here
as
well
and
then
yeah
looking
to
get
your
feedback
before
I.
Do
any
validation
with
internal
folks.
D
E
B
B
Thank
you,
I'm
running
solution,
validation
sessions
on
the
runner,
Fleet
dashboard,
which
I've
shared
in
the
past
and
I've
run
one
so
far,
and
the
early
insights
were
very,
very
positive,
which
were
excited
about
and
I
summarized
those
insights
in
the
issue
and
I'm
still
waiting
on
more
Enterprise
customers
to
meet
with.
A
I
guess
it's
me
so
in
environments,
we're
currently
working
to
put
together
a
glossary
which
I
think
is
much
needed
just
of
common
terms
within
like
the
deployment
area,
so
we're
getting
that
on
track.
But
looking
forward
for
this
to
help
with
like
async
communication,
the
design
Sprint
and
just
in
general,
talking.
C
A
So
just
wanted
to
bring
it
here,
so
all
of
you
could
see
kind
of
what
has
gone
into
it
so
far
and
then
just
want
to
know
if
I'm
also
working
with
Eric
and
will
to
test
out
the
common
screener
for
my
solution.
Validation,
study
for
group
level,
protected
environments,
so
kind
of
excited
for
this
to
test
it
with
self-serving
option
and
we'll
let
you
know
how
it
goes.
A
And
then
the
final
thing
I
have
is
just
more
of
a
question.
So
I
don't
know,
has
anyone
ever
been
assigned
a
community
contribution?
That's
not
in
their
group,
I
was
assigned
one
for
package
and
I
did
notice
in
the
ux
weekly
books
like
Pedro
is
the
one
that's
supposed
to
be
reviewing
these,
but
is
this
something
that
I
should
take
on?
Is
it
something
I
should
pass
off
to
Pedro
I'm,
not
sure.
If
anyone
has
experience
in
this
area.
F
Yeah
I
I
think
it's
not
similar,
but
I
haven't
experienced
like
selected
by
boat
automatically,
but
I
found
one
issue
that
is
dedicated
for
the
distribution
team
and
then
I
just
think
the
design
manager
that
I
can
review
this
so
because
I
already
have
the
setup
in
my
GDK.
So
I
had
this
discussion
with
hayana,
but
from
my
understanding,
the
community
contribution
without
any
designer
goes
to
Petro
and
I'm,
not
so
sure
like
how
we
can
make
those
change
in
our
boat
but
I
think
that's
the
process.
F
A
I
was
trying
to
reveal
it
myself.
It
looks
like
it's
one
that
I
need
to
have
like
packages
and
images
set
up
and
Mr
review
doesn't
have
instructions
on
that.
So
I
did
Ping
Pedro.
If
he
has
it
set
up
already,
it's
quite
an
easy
review.
If
not
it's
something,
I
can
look
into
I.
Think
I
just
need
more
instructions
on
how
to
do
it.
F
F
How
we
can
move
things
faster
and
there
are
a
lot
of
discussion
ongoing
and
then
so
in
the
end
too
long
discussion
to
read,
but
in
the
end
what
hayana
suggested
was
like:
okay,
let's
just
step
back
and
then
we
have
run
the
first
unmoderated
solution,
validation
using
the
usertesting.com
and
that
we
got
already
just
one
cycle
of
outcome.
So
let
them
decide
if
it
is
enough
for
them
to
make
decision
to
put
it
inside
the
left,
side,
navigation
or
not
and
corresponding
to
their
feedback.
We
just
choose
the
direction.
F
If
the
answer
is
no
from
the
foundation
team,
we
start
from
the
pipeline
editor
and
having
one
small
button
there
to
access
to
catalog
and
then
in
the
meantime,
we
we
still
gather
feedback
from
users
verbally
or
also.
We
need
some
more
metrics
to
use
snow
plow.
That
also
requires
some
front-end
implementation,
so
that
was
the
outcome
of
This
research.
F
F
So
this
is
something
that
I
try
to
onboard
myself
like
how
to
create
a
pipeline
as
I
want
and
then
how
to
choose
the
right
keyword
to
skipping
a
certain
job,
for
example,
and
then
myself
pointed
out
that,
like
hey,
this
is
also
a
very
crucial
part
of
our
ux,
like
we
should
focus
more
on
this
terminologies
and
also
the
experience
on
how
to
choose
the
right
keywords.
Is
it
easy
enough?
D
Yeah
I
just
got
a
couple
of
quick
updates:
I
graded,
my
parental
leave
issue
linked
to
it
within
the
doc.
There's
a
couple
sections
within
it
that
I'll
be
adding
to
over
the
next
couple
weeks.
So
I
get
closer
to
the
leave
where
I'll
be
assigning.
You
know
certain
tasks
or
things
that
I
won't
be
able
to
cover
to
different
people,
but
no
action
items
as
of
right
now,
just
making
you
all
aware,
I'm
also
going
to
look
over
Emily's
comments
on
her
solution.
D
Validation,
study
and
I'll
respond
to
that
comment
later
today,
Emily
and
then
I
watch
Ollie's,
video
I
think
it
was
with
Varin
and
Fabian
and
a
couple
others
I
thought
it
was
really
informative.
So
thanks
for
recording
that
and
sharing
that
ali
and
just
wanted
to,
let
me
know
if,
if
you
need
help
on
any
of
those
switchboard
related
issues,
I'm
kind
of
being
pulled
in
a
lot
of
different
directions.
So
just
make
sure
to
mention
me
on
anything.
D
C
Yes,
so
I
was
actually
gonna
take
some
time
off
next
week,
I'm
still
taking
some
time
off,
but
I
need
to
be
around
to
send
out
our
CI
components,
assignment
three,
which
I
also
a
lot
of
friends
and
family
day,
but
I'll
be
in
on
Monday
doing
that.
But
it's
exciting
because
we're
we're
finally
able
to
send
that
out.
So
people
in
our
Alpha
program
will
be
using
some
components
and
some
inputs
to
create
an
assignment.
C
So
we
are
kind
of
supporting
that
in
a
way
by
we're
giving
them
like
a
pre-selected
list
to
select
from
so
we'll
want
to
remember
that
if
we
see
really
good
success
rates
but
anyway,
but
it'll
be
good
to
get
feedback
on
that
and
then
hopefully,
I
think
Jackie
and
I
today
will
meet
to
finalize
the
next
steps,
at
least
for
Q
2,
for
The
Benchmark,
like
our
10
issues
to
Champion
for
Q2
and
then
I've
been
working
on
a
cross-functional
analysis
of
those
susp
verbatims.
C
It
was
originally
an
okr
for
I
was
thinking
of
the
okr
for
Q2,
but
I
I,
really
like
analyzing
data
and
so
I
finished
it.
So
now
we're
kind
of
socializing
that
around
to
look
at
the
next
steps,
for
that
so
we'll
see
how
that
goes,
and
then
I
think
we'll
wait
to
prioritize
the
research
for
Q2
for
Q2
until
we
think
it
comes
back
and
has
a
chance
to
like
chime
in
with
her
projects.
C
A
Okay,
awesome:
well
thanks
everyone
and
we'll
see
you
later
thanks
good.