►
From YouTube: CI/CD UX Meeting 2022-03-23
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
Today
is
the
23rd
march
and
we
are
meeting
for
the
cicd
ux
meeting
today
is
just
katie
and
I
so
we'll
keep
it
quick
and
short
all
right,
I'll
start
with
the
general
announcements.
First.
First
of
all,
we
have
an
upcoming
friends
and
family
day
on
25th
march.
So
if
you
haven't
applied
for
a
pto
yet
now
is
a
good
time,
then
the
next
standing
announcement
is,
of
course,
our
okr
progress.
A
So
take
a
look
at
the
issue
and
see
how
things
are
progressing
and
updated
there
next
is
in
april
I
mean
april,
is
kind
of
going
to
be
a
front-end
contribution
month.
So
what
we
need
to
do
as
designers,
for
that
is,
we
need
to
identify
a
list
of
low-hanging
fruits,
front-end
issues
that
could
use
community
contributions
and
how
we
can
prepare
for
it
is.
We
can
think
of
set
three
or
several
issues
that
we've
always
wanted
to
see
addressed
and
our
team
couldn't
make
time
for
those.
A
So
you
have
to
just
make
sure
that
there's
a
ux
label,
then
there
are
seeking
community
contributions
label,
but
I
just
wanted
to
add
here
that,
from
my
own
experience
to
have
the
seeking
community
contribution
label
stay,
you
have
to
make
sure
that
the
workflow
is
ready
for
development.
That
means
it
has
to
go
past
the
planning
breakdown
and
it
has
to
be
weighted
by
the
team
so
make
sure
that's
done.
A
The
design
is
up
and
the
weight
is
added
to
the
issue
and
then
add
these
labels
yeah
and
next
is
beautifying
our
ui.
So
every
milestone
there
is
an
ask
for
one
pd
and
one
engineer
to
volunteer
to
partner
in
mrs
to
fix
usability
issues
in
a
self-directed
way
and
it's
an
opportunity
to
explore
other
areas
and
to
fix
things
that
have
been
bugging
everyone
for
a
long
time
and
yeah.
If
you
need
want
to
volunteer
for
this,
please
create
an
mr
add
yourself
to
the
table
in
the
handbook
link.
A
That's
provided
here
in
this
section
then
check
the
ux
weekly
agenda
and
recording
for
more
information,
and
I
will
very
quickly
touch
through
the
items
that
gina
has
populated
here
for
pipeline
insights
and
runner.
So
gina
is
focusing
on
review.
Apps
for
1410
and
through
researchers,
she's
found
that
there
are
many
usability
issues
which
are
associated
with
it
and
she
has
stacked
a
couple
of
issues
that
she
would
be
looking
at
and
another
thing
that
she's
working
on
is
visionary
markers
for
ci
job
cues
and
the
link
is
provided
here
for
the
issue.
B
Next
well,
the
past
two
weeks
I've
been
really
focusing
on
settings
and
a
bit
of
background
about
that
is
that
package
has
a
lot
of
upcoming
settings
that
are
going
to
be
added
and
it's
a
good
chance
to
look
at
the
structure
of
settings.
So
I've
linked
a
whole
bunch
of
issues
and
mrs
here
of
things
that
I'm
working
on,
because
settings
is
very
big
and
I'm
coming
at
it
from
many
different
angles
and
the
first
one
is.
B
How
do
we
signal
to
the
user
that
a
setting
is
going
to
cascade
downwards
and
I'm
looking
to
audit
places
where
we
currently
do
this
in
the
product?
We
do
have
some
guidance
in
pajamas
about
the
way
it
should
appear
to
the
user
when
you're
in
the
child,
when
the
setting
is
locked
and
but
yeah.
There's
lots
of
different
use.
B
Cases
here
and
I've
also
made
some
design
proposals,
not
really
to
say
we
should
change
the
design
but
more
like
to
get
the
conversation
started
and
to
generate
some
discussion
so
and
if
you
have
some
time,
please
have
a
look
at
that
issue
and
yeah.
Let
me
know
what
you
think
another
one
I'm
working
on
is
that
users
are
often
going
to
the
feature
page
to
look
for
the
feature
settings.
I
think
eventually,
we
could
consider
placing
the
settings
contextually
closer
to
the
feature
like
the
security
has
a
configuration.
B
And
mr
for
that,
going
into
pajamas
I
was
also
very
confused
at
which
level.
B
So,
which
point
were
we
on?
I
was
talking
about
which
level
do
settings
live
on.
A
Right
and
I
I
did
look
at-
I
just
wanted
to
make
a
point
that
I,
when
I
looked
at
the
issue
that
you
had
created
where
you're
seeking
suggestions
from
team
members
around
cascading
settings
yeah,
it
did
make
me
realize
and
actually
observe,
like
how
much
of
difference
in
experience
we
are
providing
with
that,
and
there
are
certain
instances
when
I
see
things
populated
at
project
level,
but
I
do
not
realize
like
where
is
it
coming
from?
Is
it
coming
from
the
admin
level?
A
Is
it
coming
from
a
group
so
where
this
has
actually
been
set,
and
instead
of
appearing
as
a
limit,
it
appears
as
a
choice
that
I'm
making
so
like
I
had
put
screenshot
for
the
was
that
maximum
artifact
size.
So
if
I'm
on
group
level,
if
I
have
put
a
limit
of
let's
say,
100,
then
for
project
100
should
become
a
limit
for
me.
It
shouldn't
come
pre-populated,
as
as
that
you
made
hundred
as
a
choice
as
if
I
filled
it
there.
I
did
not.
B
Yeah
it's
just
as
I
was
making
the
designs.
I
realized
like
there's
no
way
that
this
is
one
size
fits
all,
because
the
settings
are
very
inconsistent,
so
it's
kind
of
like
you
just
need
to
pick
a
starting
point
like
we
also
need
our
settings
to
be
a
bit
more
consistent
as
in
like
sometimes
we
use
toggles,
and
sometimes
we
use
checkboxes
and
stuff
like
that.
So
it's
really
hard
to
make
a
consistent
visual
pattern
to
signal
to
the
user,
but
I'm
just
starting
somewhere.
I'm
gonna
see
what
happens.
B
A
lot
of
really
talented
designers
have
worked
on
this
in
the
past
as
well,
so
I'm
drawing
from
their
work
and
just
hopefully
take
it
a
little
bit
further
yeah.
That's
great
and
yeah.
I've
linked
a
few
more
issues
here
of
yeah,
I'm
working.
I
want
to
document
a
lot
of
the
confusion
I
had
about
settings
like
to
document
a
lot
of
implicit
rules
about
how
settings
work
in
pajamas.
B
I've
made
an
epic
about
that
which
is
also
drawing
on
a
lot
of
the
work
that
hayana
and
michael
lee
did
in
the
past,
for
new
proposals
so
feel
free
to
have
a
look
but
yeah
the
the
two
things
that
I'd
really
love
feedback
on
is
the
the
cascading
downwards
and
any
ideas
you
have
for
writing
guidelines
about
where
to
place
a
setting
like
admin,
group
or
project.
A
Thanks,
I
will
vocalize
for
nadia
today,
so
this
milestone
nadia
is
working
on
user
flows
and
visionary
mockups
for
the
ci
catalog
that
she
has
also
spoken
about
a
couple
of
times
before
in
ci
cd
meeting
and
the
team
is
taking
the
pivot
from
their
initial
vision,
based
on
the
poc
spike.
So
currently,
they're
exploring
the
user
flow
for
publishing
a
ci
component
to
ci,
catalog
and
then
they're
planning
to
use
the
existing
kit.
Love
features
for
everything
as
much
as
possible,
but
looking
ways
into
the
experience
can
be
guided.
A
I
mean
how
the
experience
can
be
guided
and
customized
to
this
specific
user
flow
and
she
has
added
the
issue.
Yes,
this
is
an
issue
for
that
and
for
the
next
point
also,
she
has
mentioned
an
issue
and
that's
about
like
she
would
love
to
get
our
vote
on
the
favorite
ci
component
name:
ideas,
yeah.
This
looks
like
something
really
interesting
and
then
I'll
move
any
comments
kitty
on
any
of
these
topics.
B
A
Me
who
needs
to
like
go
and
vote-
I
haven't
looked
at
it
yet
I'll.
Definitely
do
that
after
the
meeting,
all
right
so
coming
to
pipeline
execution,
the
new
milestone
has
just
begun.
So
I
don't
have
a
really
interesting
work
in
progress
to
show,
but
I
would
quickly
touch
upon
a
couple,
a
few
things
that
are
either
upcoming
or
something
that
I've
observed
in
my
like
stage
group
that
could
be
of
interest
to
other
team
members
so
designing
for
scalability.
A
After
having
the
discussion
with
some
designers
and
also
jackie
who's,
the
group
product
manager
for
verify
it
seems
like
the
new
emerging
theme
within
verify
is
scalability,
because
now
we
are
looking
at
how
to
present
to
users
very
high
number
of
resources
without
breaking
anything
at
our
end
and
also
keeping
the
experience
like
intact
and
good
for
them
to
look
at
those
things
and
the
kind
of
resources
that
I'm
talking
about
right
now
are
definitely
runners,
environments,
releases
pipelines,
jobs.
A
So
when
we
are
talking
of
big
enterprises,
the
scale,
the
number
of
resources
that
they
have
to
deal
with
is
a
lot
it
could
be
in,
like
hundreds,
thousands.
A
So
how
we
are
presenting
that
to
them
in
a
way
that
they
are
discoverable
in
a
way
that
they
could
kind
of
make
a
sense
out
of
the
trends
over
time
and
even
get
like
in
good
insight
so
that
they
can
perform
an
action
to
optimize
their
workflows
or
make
any
necessary
changes
that
they
need
to
to
keep
a
control
on
the
resources
they're
using
on
the
infrastructure,
resources
they're
using
like
runner
minutes
or
ci
cd
minutes
or
what
else
could
be
there.
A
So
it
seems
like
package,
I'm
not
sure
how
bulky
the
package
list
can
go
in
a
project
and
how
much
like
it
can
go
high
in
scale.
But
it
seems
like
that
can
also
be
covered
under
this
larger
umbrella,
but
yeah.
So
there's
an
upcoming
thing,
big
that's
happening
for
verify
in
april,
and
this
is
going
to
be
the
topic
that
would
be
talked
about.
A
So
this
is
just
to
announce
for
that,
and
then
we
are
finally
on
our
way
to
implement,
share
runner
usage
for
usage
quota
for
for
user
namespace,
and
we
are
doing
that
this
time
on
the
usage
quora
page
unlike
analytics.
A
So
I
have
like
I
sought
feedback
on
the
design
in
the
previous
meeting
and
there
was
a
lot
of
like
useful
suggestions
and
advice
that
I
received
on
the
design
and
the
experience,
and
that
really
helped
me.
So
it
looks
like
we
are
on
a
in
a
really
good
place
to
finally
push
things
to,
and
in
fact
it
is
in
dev
it
it's
being
developed
as
we
speak
and
soon
it
is
going
to
be
on
production
and
available
for
everyone
to
try
out
then.
A
Lastly,
it's
a
work
that
I
was
very
recently
exposed
to.
I
mean
I
just
came
across
this
issue
and
tried
to
understand
the
problem,
and
that's
that
was
my
kind
of
gateway
to
looking
at
access
in
gitlab.
So
this
issue
says:
auditors
cannot
view
ci
cd
analytics
and
even
though
I
had
done
like
a
kind
of
small
project
for
documenting
the
permissions
in
gitlab
ci,
it
still
came
to
me
as
kind
of
a
surprise
that
the
permissions
that
we
talk
about
in
gitlab
is
not
just
a
function
of
the
roles.
B
And
my
first
question
is
auditor:
I
know
that's,
not
a
role
is
that
something
in
the
admin
area
like
is
that
an
official
term
auditor.
A
A
So
this
is
the
link
in
the
docs
how
it
is
documented.
A
So
when
you
have
someone
audit,
your
group
or
audit,
your,
I
would
say,
group
or
namespace,
and
so
what
you
do
is
you
provide
them
with
an
auditor
access
apart
from
auditor
access,
there
are
a
couple
of
other
access.
If
you
go
to
your
gdk
and
go
to
your
admin,
dashboard,
there's
a
way
to
check
like
what
are
the
access
that's
available
to
assign
to
users
it's
in
the
user
section.
A
So
you
do
that
at
the
very
top
level
and
then,
when
it
comes
to
groups
and
projects,
you
provide
additional
roles
to
those
users
like,
for
example,
katie
is
an
auditor
I've
given
her
an
access
for
as
an
auditor,
but
when
it
comes
to
git
lab
project,
I
give
you
the
role
of
a
maintainer
or
a
developer.
B
A
Yeah
exactly
my
thoughts,
so
I
also
want
to
bring
this
up
with
other
designers
who
are
working
on
roles
and
permissions.
So
there
was
recently
an
issue
for
collaboration.
If
you
remember,
because
they're
kind
of
trying
to
make
a
single
page
for
controlling
the
roles
and
access,
I'm
wondering
if
this
was
taken
into
account.
Well,
I'm
sure
they
would
have
thought
about
it
or
they
know
about
it.
But
still
this
is
a
little
surprising
for
me
and
also
at
this
point
a
little
scary,
because
I
don't
know
a
lot
about
it.
B
Yeah,
that
does
sound
scary,
but
because
I'm
kind
of
in
the
same
realm
in
terms
of
like
who
can
do
what
with
the
settings
and
I've
never
heard
of
this,
so
I'll
have
to
look
into
this
as
well.
B
B
Yeah,
that
makes
sense
we
have
this
problem
in
the
container
registry
and
and
one
of
the
things
that
we're
going
to
do
is
like
it's
currently
a
list
that
might
be
sorted
on
on
date
or
something
and
it's
this
list
that
can
have
so
many
objects
in
it.
But
we
are
going
to
use
some
intelligence
to
kind
of
bring
up
the
most
relevant
like
what
we
think
the
user
is
probably
looking
for
and
bring
that
to
the
top
of
the
ui
things
like
this.
A
Yeah,
that
sounds
very
similar,
and
that
is
going
to
be
pretty
challenging,
because
I
mean
no
matter
how
much.
A
How
you
decide
like,
what's
going
to
be
important
for
users,
there's
always
like
some
small
gaps
that
are,
I
wouldn't
say,
overlooked,
but
it's
just
that.
How
much
can
you
cover
yeah
I
mean
there
would
be
some
sort
of
trade-offs
and
eventually
we'll
be
at
a
place
that
would
be
comfortable
for
most
of
our
users.
B
Yeah
yeah,
that's
awesome,
yeah,
I'm
curious
to
see
how
that
progresses
and
I
can
show
what
we're
gonna
do
with
container
registry
might
be
interesting.
A
Okay,
so
I'll
move
to
the
last
thread
and
I'll
just
touch
upon
it,
which
is
for
ux
research,
so
will
has
provided
some
updates
about
the
sus
results
that
him
and
hyanna
had
shared
with
the
release
team
and
the
mural
board
the
issue.
Everything
is
provided
in
the
agenda
and
then
he
also
had
a
conversation
with
adam
around
benchmarking
study
for
op
syria
and
he's
currently
trying
to
shop
around
the
idea
and
determine
what
stage
group
should
be.
The
focus
of
the
study
and
erica
has
mentioned
about
something.
A
That's
related
to
your
work
around
settings
that
how
the
research
around
the
settings
is
going
to
progress
which
is
going
to
be
like
so
interesting
to
look
at,
and
the
issue
is
marked
here
and
the
best
way
to
iterate
on
this,
she
mentions
is
to
create
a
modular
approach,
which
I
think
is
right,
because
it's
pretty
best
and
that
different
stage
teams
can
use
to
look
into
settings
for
the
areas.
A
This
isn't
currently
a
priority
for
ashley,
okay
and
she's,
currently
also
running
survey,
development
interviews
for
sas
sheridan
survey
and
the
ops
product
direction
survey
at
the
same
time
so
that
she
can
quickly
I
trade
on
those
products,
and
that
is
all
from
the
agenda
cool
all
right,
so
we'll
meet
in
another
meeting,
bye
kitty
catch.