►
From YouTube: Settings UX - Protected branches exploration
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
One
of
the
issues
brought
up
by
mike
nichols
is
that
we're
planning
to
add
more
information
to
this
protected
branch
area
and
because
so
there's
limited
space
down
here
and
things
are
beginning
to
get
truncated
and,
as
a
result,
information
would
be
missing,
because
here
maintainers
looks
like
maintainers
in
something
else,
and
it's
not
very
user
friendly.
A
A
So,
like
we
said
before,
this
is
what
we
have
currently
and
with
the
proposal
of
changing
this
layout
is
to
only
show
the
information
to
add
a
branch
when
you
really
need
to
add
a
branch.
So
in
this
example,
we
have
all
this
stuff
hidden
away
under
adder
branch,
if
you
click
on
add
a
branch
that
information
will
appear,
how
this
will
appear
has
not
been
solidified
yet
no,
we
don't
have
rules
around
whether
this
should
be
a
model
in
line
or
a
separate
page.
A
This
is
something
that
we're
going
to
explore
further
in
the
upcoming
months
across
the
different
teams
and
scenarios
to
find
the
right
pattern,
but
as
the
first
mvc,
we
can
hide
and
show
existing
blocks
on
the
page.
So
we
might
go
with
the
inline
reveal
like
this.
So
click
on
that
reviews,
this
block
that
we
had
before
nothing's
changed,
and
the
only
thing
here
is
instead
of
saying,
protect
the
ctas
are
add
or
cancel.
A
So
the
proposal
here
is
that
potentially
to
have
a
read-only
view
of
what
this
information
would
look
like
so
for
content
with
long
names,
you
could
wrap
inline.
This
is
something
you
can't
do
with
drop
downs
and
if
you
want
to
edit
and
you
click
edit
and
then
it
opens
up
a
block
like
this,
whether
you
need
to
edit
things
on
the
immediately
directly
from
the
list,
that's
going
to
be
something
that
your
stage
and
group
will
be
responsible
for
figuring
out.
A
What's
the
right
user
experience,
but
in
a
general
high
level,
the
assumption
is
that
people
don't
need
to
make
those
kind
of
changes
really
quickly
and
that
these
types
of
changes
would
happen
once
in
a
while,
not
an
everyday
thing.
So
we
don't
need
to
optimize
for
that
experience.
So
we
would
just
review
that
information
when
you
click
edit
and
all
the
information,
including
new
ones,
can
just
be
added
to
this,
and
you
can
change
it
up.
A
How
you
want
the
beauty
of
the
read-only
view
is
that
this
is
only
one
of
the
many
ways
that
you
can
present
the
information
by
breaking
it
off
from
the
table
view
whether
you
need
to
do
the
comparison.
That's
one
thing,
but
another
way
to
look
at
this
is
to
potentially
rearrange
the
information
in
a
card
layout
or
something
that
presents
the
key
information
and
that's
necessary
immediately
or
in
the
most
effective
way.