►
From YouTube: CI/CD UX Review - 2023-05-04
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
Okay,
it
looks
like
it
started
all
right,
so
I
will
get
started
introduction
in
case
anyone
watches
this
I'm
Gina
I'm,
a
student
product
designer
for
Runner
Fleet,
and
this
is
our
first
design
cicd
ux
review,
meeting
very
exciting,
so
I
wanted
to
share
an
issue
that
is
specific
to
to
disabling
or
enabling
shared
Runners,
and
the
problem
is
at
the
group
level
like
we
know,
there's
many.
A
If
you're
at
at
a
top
group,
there
can
be
many
nested
levels
of
groups
and
projects
within
there
and
what
we've
heard
is
that
it
is
really
difficult
to
enable
or
disable
shared
Runners
from
that
top
level
group,
because
right
now
we
only
allow
you
to
disable
and
and
once
you
do,
that
it
will
Cascade
down
the
entire
tree
of
whatever's
underneath.
A
But
then,
if
you
try
to
enable
again
from
that
top
level
group,
it
actually
only
enables
it
for
that
top
group.
It
doesn't
do
anything
for
the
groups
and
projects
below
and,
as
you
can
see
like
that,
could
be
really
difficult.
If
someone
mistakenly
disabled
Runners
and
wanted
to
re-enable
again,
they
wouldn't
be
able
to
do
that.
A
But
then
another
thing
I
wanted
to
share
another
use
case
where
this
impacts
people,
which
I've
added
a
screenshot
into
our
doc.
Is
we
heard
from
a
customer?
Oh,
we
accidentally
disabled,
shared
Runners.
Now
we
want
to
enable
them
again,
but
we
can't
do
it
for
all
the
groups
and
projects,
and
so
some
people
want
to
to
have
that
setting
Cascade
to
all
groups
and
projects,
but
some
others
due
to
security
restraints
or
you
know
like
whatever
it
happens
to
be
only
certain
groups
can
use
certain
Runners.
A
So
there
are
other
people
that
may
want
to
pick
and
choose
which
groups
and
projects
they
want
those
shared
Runners
to
be
available
to.
So
this
is
a
really
great
Tomas.
One
of
our
internal
git
lab
team
members
went
through
a
use
case
of
where
that
like
how
that
makes
sense
so
for
the
design
that
I'm
coming
up
with
our
quick,
our
our
iteration
I,
will
say
in
between
right
now,
since
we
don't
support
that
re-enabling
cascading
effect,
we
add
a
warning
dialogue.
A
Now,
when
you
do
disable
shared
Runners,
saying
like
you,
won't
be
able
to
easily
enable
them
again
you're
going
to
have
to
go
into
each
group
and
project
and
enable
them.
Are
you
sure
you
want
to
do
this?
So
that's
our
first
iteration,
but
what
I'd
like
to
do
is
make
this
more
of
an
ideal
experience
in
general,
supporting
both
of
those
main
use
cases
as
apply
this
to
everything
underneath
the
top
level
group
or
pick
and
choose
which
ones
I
want
to
apply
to,
and
the
person
who
would
be
doing.
A
This
is
a
platform
engineer.
This
would
specifically
be
group
owners
because
they're,
the
only
ones
who
can
access
the
settings
in
a
group,
an
admin
could
do
this
too,
but
it's
it's
likely
just
a
group
owner
and
I
talked
about
the
ideal
outcomes
and
then
I'll
talk
through
I'll
talk
through
these
two
points.
A
The
hardest
part
of
this
problem
to
solve
I
didn't
write
this,
but
it
I
think
it
will
be
being
able
to
display
a
ton
of
potentially
thousands
of
nested
groups
and
projects
under
that
top
level
group,
because
we
know
that
this
is
specifically
an
issue
for
self-managed
customers,
because
they'll
be
the
ones
who
are
creating
their
own
shared
runners.
A
So,
typically
those
are
huge
users
and
they
could
have
tons
of
groups
and
projects.
So
that's
a
struggle.
I
know
that
we'll
we
will
deal
with
and
then
a
known
constraint
just
about
how
this
works
today.
I
brought
this
up
in
the
beginning.
So
when
you
disable
the
shared
Runners
it
Cascades,
but
if
you
want
to
re-enable
it
does
not.
So
this
was
a
technical
constraint,
because
I
guess
cascading
cascading
in
the
other
direction
would
be
a
very
large
database
call
and
it
would
cause
a
huge
performance,
negative
impact
and
I
guess.
A
It
was
also
really
difficult
to
do
development
wise
this
was
years
ago.
So
we
haven't
really
worked
on
figuring
out
if
this
is
possible
again
and
the
workaround
is
for
users
to
go
to
each
individual
group
or
project
and
enable
the
shared
Runners
for
each
one,
which
you
could
see
as
being
very
tedious,
I'm
gonna
I'll
pause
there
are
there
additional
questions
or
anything
that
want
to
talk
about
before
I
go
into
figma.
B
A
I
guess
we
could
think
about
it
as
if
one
of
those
projects
that
wouldn't
be
a
huge
deal,
I
guess
the
risk
would
just
be
that
it
takes
longer
to
re-enable
Shared
runners,
which
may
help
you
get
like
a
production
fix
out.
But
I
was
rethinking
that
because,
like
if
only
one
project
needed
those
shared
Runners,
you
could
easily
go
into
settings
and
enable
it
for
them.
A
I,
guess
if
all
of
the
projects
and
groups
needed
them
like
that
would
be
the
biggest
risk
they
wouldn't
have.
Access
to
the
shared
Runners
and
they'd
have
to
create
their
own
runners.
D
A
D
A
B
B
Everything
is
scary
and
then
reverse
as
well
I'm
thinking,
if
there's
a
way
that
the
system
could
just
send
at
the
group
level,
those
yeah
okay,
like
I'm,
Sunshine,
Awards,
English
and
that,
but
you
know,
people
separately
individually
run
the
tests
in
the
background
for
each
of
the
projects
within
the
brook.
B
A
Yeah
I
think
that's
I,
I
think
from
a
database
perspective
that
would
be
feasible
and
easier
than
trying
to
do
everything
at
once
if
they
were
selecting
something
yeah
and
I.
Think
also,
as
for
the
use
case,
where
groups
are
dealing
with
security
issues
where
maybe
they
don't
want
to
re-enable
Shared
Runners
for
all
of
their
groups
and
projects,
this
would
make
it
easier
for
them
too,
because
they
can
select.
They
can
bulk
select
many
at
once,
rather
than
having
to
go
into
individual
ones.
A
A
It
looks
today
if
you
haven't
been
into
cicd
settings
into
and
up
for
a
group
you,
it's
just
a
switch
which
makes
it
seem
like
it
will
actually
work
when
you
switch
it
on
and
off.
So
it's
very
misleading
and
I
tried
to
give
you
like
an
idea
of
how
this
works,
which
I've
explained
but
visually
it's
a
little
bit
easier
to
see.
So
in
this
group,
like
the
use
case
here
would
be
that
we
need
to
restrict
this
group
from
using
shared
Runners
to
save
costs.
A
Let's
say
because
every
time
you
use
Runners
you're
pay
money,
so
you
want
to
disable
all
the
runners
for
all
the
groups
of
projects
in
this
group,
so
I
I
put
that
switch
off
and
then
I
come
back
and,
like
our
infrastructure
group
has
figured
out
how
to
reduce
costs
now,
I
want
to
bet,
come
back
and
enable
shared
Runners
for
all
those
groups
and
projects,
so
I
toggle
it
on.
But
oh
it
only
impacts
group
a
so
now.
A
So
what
I'm
proposing
now
is
to
be
able
to
allow
users
to
choose
groups
and
projects
that
they
want
to
disable
or
enable
shared
Runners
for
from
any
top
level
group.
So
as
long
as
it
has
some
type
of
nested
things
in
it,
you
would
be
able
to
pick
and
choose
and
when
I
started
like
brainstorming
this,
this
is
kind
of
like
what
I
was
thinking.
But
I
I
was
struggling
again
because
you
can
have
many
nested
groups
and
projects
like
how
do
I
display
those.
A
A
These
groups
and
projects
and
shared
Runners
are
disabled
for
these
ones
and
then,
when
you
edit,
it
there's
some
some
way
to
be
able
to
select
all
the
groups
and
projects
so
that
you
don't
have
to
like
go
through
and
click
them
all,
and
then
there's
also
some
way
to
search,
but
I
also
find
like.
We
don't
really
use
a
pattern
like
this,
where
you
have
these
two
forms
and
because
you're
really
just
pushing
something
back
and
forth
so
yeah.
B
Recently,
sorry,
someone
with
a
speaker
are
we
handling
information
like
this
anywhere
else
in
the
product.
Do
you
know
I'm
trying
to
think
like,
for
example,
when
we
are
one
example,
I
can
think
of
is
when
we
book
edit
issues
or
epics
right,
but
we
can
yeah
so
add
labels
or
remove
labels
to
the
issues.
B
That's
the
first
one
to
come
to
my
mind
and
my
grandfather's,
you
can
think
of
examples
of
how
we
handle
like
a
large
amount
of
data
in
the
product
today.
So
I
can
make
this
selection
and
change
of
status.
A
A
A
But
it
issues
and
even
like
this
is
different
because
in
settings
like
you're,
not
just
going
there
to
view
all
the
subgroups
and
projects
that
are
in
that
group,
so
I,
don't
we
don't
have
like
a
pre-existing
list
to
use
like
this.
Where
then
we
could
say
bulk,
update
or
whatever,
and
then
I
also
thought
of
token
access,
because
you
can,
you
can
customize
the
access
by
just
pasting,
a
project
path
which.
C
C
Go
ahead,
there's
a
fig
mod
file
that
I
worked
on
when
I
was
in
the
previous
group.
I
just
couldn't
find
the
issues.
I'll
just
add
the
figma
file
here.
Okay,
sorry,
that's
the
wrong
place,
and
this
issue
was
about
like
when
you
have
a
certain
quota
assigned
to
a
particular
group
or
a
particular
instance.
How
does
that
like
drizzle
down
to
all
the
groups
or
groups,
projects
inside
that
and
did
I,
not
add
the
link?
C
C
A
C
Do
remember,
like
the
team,
had
a
discussion
that,
instead
of
showing
how
these
were
inherited,
let's
just
put
the
path
there
and
that
would
just
solve
the
problem.
A
I'm
struggling
right
now,
answering
it.
Okay
hold
on.
A
A
Listing
the
the
data
out
but
yeah,
this
is.
E
Yeah
I'm
thinking
the
hardest
part
about
visualizing
like
how
these
all
connect
in
with
each
other
is
like.
You
were
saying:
if
you
select
the
like
top
level
group,
it
doesn't
select
everything
underneath
it
so
like
that
tree
format
doesn't
really
work
because
you
select
the
top
group.
It's
not
selecting
everything
under,
but
people
would
expect
it
to
so
I
get.
Why
that's
like
a
difficulty,
because
you
can't
really
show
it
in
like
the
tree
version,
because
it
would
just
be
assumed
it's
selecting
everything
under
it.
A
B
Is
there
any
common
criteria
that
people
will
look
at
when
thinking
of
making
that
selection
now
we're
thinking
of
the
name
right,
then
the
the
hierarchy
in
terms
of
yeah?
This
is
a
group
of
the
system
group,
but
when
they
they
have
that
huge
list
is
very
complex,
deep
hierarchy.
B
B
Is
there
anything
in
common
that
users
will
look
for
that?
We
can
Surface
in
order
to
yeah
yeah,
make
this
task
less
manual
right
and
more
intuitive.
D
B
D
My
comment
too
just
to
end:
it's
like
users
will
not
even
remember
the
names
of
the
projects
at
all,
and
so
it's
like
they
need
different
things
about
their
use
context
to
like
make
the
decision
so,
like
maybe
tags
labels,
the
environments
who
owns
it
and
the
type
of
access
they
have
would
be
candidates,
like
maybe
there's
like
AI
behind
the
scenes.
D
That's
like
making
a
recommendation
for
them
or
something
yeah,
but
this
is
like
gonna
blow
their
minds
like
it
blows
my
mind,
even
thinking
about
how
they
think
about
it,
and
it's
just
another
thing
to
keep
in
mind
that
I'm,
like
really
now
able
to
say
about
users,
is
that
they
have
the
facility
to
understand
all
of
this.
D
A
E
A
Like
security
rules
were
changed,
or
something
like
that,
that
would
be
important
to
show
okay
yeah
I
like
that
you're
right,
it's
not
just
the
name.
It's
definitely
not
and
then
I
also.
My
other
point
was
I'm
gonna
go
back
and
look
at
past
research
to
see
if
people
were
saying
exactly
what
they're
looking
for
like
what
context
they
need
to
be
able
to
make
the
decision.
A
C
A
C
Oh
no
platform,
Engineers,
like
jobs
should
be
done,
differs
from
what
the
admin
is
trying
to
do
on
the
app
that
console
versus
on
the
like.
When
somebody
is
in
the
settings
like
how
much
elaborate
information
would
they
require
to
make
a
decision.
D
This
is
reminds
me
of
a
design
pattern
that
you
have
in
qualtrics,
where
you're
able
to
like
create
variables
for
the
data,
and
you
can
like
bucket
them,
and
so
you
like,
so
it
gives
you
all
your
variables
and
then
you
can
like
aggregate
them.
So
an
example
would
be
you're
trying
to
take
suit
like
a
respondent
answers
business
size.
So
there's
like
me
and
then
there's
like
all
the
small
medium
business
sizes
like
below
500.
You
want
to
group
into
one.
D
Does
that
make
sense,
so
you
can
like
take
it
back
and
forth
and
then
so
I'm
thinking
like
something
like
that
might
be
helpful
where
they
can
like
bucket
them
yeah,
because
then
yeah
and
one
thing
to
then
add
on
to
that
would
be
like.
You
want
a
bucket
things.
D
So
then
you
need
a
label
for
like
outlining
what
happens
when
it
goes
in
that
bucket
yeah,
so,
like
I'm
gonna
make
this
variable
I'm
going
to
add
all
of
these
little
details
to
this
type
of
bucketed
variable
and
like
what
does
that
mean
for
my
analysis?
Steps
later
is
the
analogy
right
or
like
yeah
so
disabled
for,
like
what
is
it
so
let's
say
you
have
yeah,
so
is
it
just
binary
shared
Runners
are
enabled
or
disabled?
D
Yeah
so
you're,
just
when
you're
explaining
that
I
would
just
explain
the
implications
of
it
to
them.
Yeah
and
I
can't
give
you
a
screenshot
of
what
that
bucketing
behavior
looks
like
I,
don't
know
if
we
want
to
add
a
new
thing,
but
like
conceptually
to
me,
that's
what
it
is
as
opposed
to
like
toggling.
It
would
be
just
like,
drag
and
dropping
it.
Yeah.
D
But
I
think
the
other
comment.
There
is
just
have
some
text
underneath
it
explaining
the
implications
of
putting
it
in
that
bucket
like
yeah.
What
happens
there
if
I
put
it
in
the
disabled
bucket?
What
happens
yes
and
then
one
more
would
be
that
we
know
that
there's
going
to
be
some
some
projects
which
they
just
are
going
to
need,
control
over
and
so
they're
not
going
to
want
to
use
shared
runners
and
so
helping
them
to
find
those
will
be
helpful.
D
D
B
I
added
another
question
there:
do
you
know
this
is
the
smallest
thing
that
we
can
do
today
to
help
solve
this
problem
next
iteration,
obviously
so,
trying
to
think
small
before
you
wrap
up.
A
A
Oh,
it
kills
me
to
think
this
way,
because
sometimes
I'm
like
I,
know
that
this
isn't
going
to
be
the
ideal
solution,
but
I
would
say
the
smallest
step
would
be
providing
them
some
flexibility
in
either
in
selecting
which
groups
or
projects
they
want
to
enable
or
disable
Runners.
For
so
it's
not
just
a
enable
them
for
all
or
disabled
for
all
and
I.
Think
probably
the
easiest
way
to
do
that
is
I,
assume
the
path.
I,
don't
know.
I
guess
I
would
have
to
talk
technically
about
like
what's
easy,
I
guess,
ux
wise.
D
D
D
D
B
I
know
that
they
are
a
little
bit
over
time,
I'm,
finding
the
link
to
the
package,
cleaner
policies
here,
Gina
I'm,
adding
block
for
you
and
then
I
also
took
lots
of
some
action
items.
So
please
is
there
anything
else
anyone
wants
to
share
in
the
feedback.
C
A
discussion
we
can
like
extend
to
non-sync
channels.
Do
we
really
have
to
use
shared
word
or
runners
great
question.
B
A
B
And
also
I
want
to
ask:
do
you
feel
like
30
minutes
is
enough
to
have
the
discussion?
Should
we
next
time?
Let
me
try
45
what.
B
B
So
that
we
can
prepare
them
if
you
have
something
to
share
and
yeah
I'll
upload
this
as
well,
it's
live
so
I'm
not
going
to
upload
this,
but
yeah
I'll,
see
you
see
you
all
next
time
have
a
nice
rest
of
your
day.
Bye!
Everybody
thanks!
Bye,.