►
From YouTube: 2023-01-10 Code Review UX Sync
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
Yes,
Welcome
to
the
first
ux
Sink
of
the
new
year.
Most
of
these
are
just
sort
of
like
Curious
thoughts.
I
think
we're
about
to
hit
next
Milestone
and
coming
off
of
vacation.
So
I
was
just
trying
to
throw
some
some
discussion
things
out
there.
One
of
them
was
capacity,
I
know,
will
be
sort
of
reduced
on
the
ux
side,
and
so
I
wanted
to
know.
A
If
there
was
things
that
we
could
help
out
on
to
to
make
sure
they're
wrapped
up
before
out
of
offices
and
other
things
again,
and
then
you
know
the
other
one
is
like:
do
we
have
enough
sort
of
of
the
smaller?
What
I
call
like
filler
type
issues
ready
for
front
end
if
needed
over
the
next
period?
I
know
there's
like
such
issues
and
other
things
and
I
just
don't
know
what
like
states
of
those
like.
Should
we
revisit?
A
B
Yeah,
the
the
things
that
we're
trying
to
wrap
up
like
before
Pedro
is
more
focused
on
Create
and
then
I'll,
be
mostly
off
next
month.
Like
Pedro's
doing
the
restructure,
I
need
to
finalize
a
few
things
for
that
research.
We
finished
up
and
then
I'm
trying
to
go
back
to
the
review
rounds
and
find
out
what's
next,
how
I
can
break
it
down
into
smaller
versions,
but
I
don't
expect
that
to
be
touched
while
I'm
gone.
Basically,
there's
nothing
to
build
yet
and
we're
not
we're
not
ready
for
that.
B
It's
already
scheduled
for
this
Milestone,
but
then
there's
like
edit
pending
comment
looks
different
than
when
you're
actually
posting
a
pending
comment,
so
that
could
be
something
to
work
on
and
then
I've
added
a
bunch
of
ideas
to
the
beautifying
UI
for
15.11,
which
I
could
get
into
a
better
state,
but
I've
never
really
gotten
the
sense
that
front
end
is
looking
for
things
to
do.
They
seem
to
be
pretty
busy
most
of
the
time,
so
I
wasn't
sure
how
much
to
do.
A
That's
a
good
question
I.
We
did
like
the
prioritization
session
earlier
this
week
and
there
was
like
a
couple
issues
that
we
brought
that
a
few
people
brought
that
were
like
not
ux,
ready
like
one
of
them
was
the
file
browser
tree
button
thing
that
was
I,
think
you
know
what
I
mean
but
like
like
that,
one
where
we
don't
know
like
what
the
plan
is
on
that
one,
and
so
it's
a
question
of
like.
Should
we
solve
it
or
not?
A
I,
don't
think
they're
like
I,
don't
think
any
of
the
ones
that
we
saw.
There
were
huge
priorities
and
I.
A
Don't
know
that
we're
hurting
for
work,
but
also
you
know
we're
expecting
two
and
a
half-ish
Milestones
is
sort
of
like
not
necessarily
having
capacity
if
things
come
up
and
so
I
want
to
make
sure
that
there
is
like
a
few
things
of
some
so
like
the
ones
that
you
mentioned
like
about
like
in
beautifying
or
in
other
places
like
if
there
was
like
a
handful
of
issues
that
were
ux
ready
or
even
if
they
were
like
not
broken
down
like
I,
there's
follow-ups,
I
know
from
like
the
Mr
Design
chain,
like
the
merge,
widget
design,
changes
that
still
need
to
be
handled
like
there's
a
bunch
of
little
things
like
that.
A
I
think,
if
you
have
like
a
list
of
what
those
are
that
you
think
are
ux
ready
and
would
like
make
sense,
then
like
just
having
those
around
in
our
back
pocket
would
make
sense
versus
I.
Don't
know
if
investing
in
new
issues
or
like
getting
some
ux
ready
unless
you've
got
like
some
that
are
just
burning
to
do
then,
like
that
would
make
sense.
That's
sort
of
I
think
my
ask
here
is
like.
B
A
High
than
just
making
sure
we
have,
those
would
be
good.
B
Yeah
that
sounds
good
I
can
I
can
look
at
that
and
yeah
the
the
file
tree,
one
that
is.
B
Those
are
the
kinds
of
issues
where
it's
like
I.
We
don't
have
a
design
it
could.
It
could
go
many
ways,
but
if
front
end
wants
to
just
try
something
great
like
that
would
be
you
know
it
doesn't.
Anything
is
better
than
nothing
and
anything
would
be
a
shortcut
and
it's
been
written
a
few
times,
but
yeah
if
front
end
just
wants
to
just
start
going
with
no
ux.
That
would
be
kind
of
cool.
A
B
Yeah
yeah
and
we
also
have
like
a
pending,
merge
request.
It's
been
open
for
a
bit
for
the
issue
to
so
we
still
have
the
sidebar
changes
behind
a
feature
flag
because
we're
still
waiting
on
plan
to
implement
a
similar
rearranging
for
a
few
of
their
components,
but
it's
still
not
done,
and
that
would
be
fantastic
to
get
in
forget
it
actually
forget
it
because
it
would
get
in
now
and
then
I'll
be
out
and
I
need
to
open
another
feedback
issue.
So
just
forget
I
said
all
of
that.
A
B
A
Okay,
yeah
I
think
that's,
that's
really
just
those
are
those
feel
like
good
things
and
if
yeah,
if
you
can
figure
out
which
ones
are
mostly
ux
ready
and
just
make
sure
we
have
a
bucket,
then
that's
awesome,
I
appreciate
it.
Thank
you.
A
The
other
was
was
a
topic
from
like
the
vision
stuff,
but
I
saw
Ben
that
you
responded
in
so
I
was
just
gonna,
pick
your
brain
and
see
if
you're,
in
your
five
minutes
of
thinking
like
what
you're,
what
your
thoughts
were
about
the
CLI
research
and
I.
One
of
the
things
that
I've
been
trying
to
figure
out
is,
it
feels
like
forget,
lab
it's
not
easy,
but
like
we
can
go
out
to
like
various
places
and
get
feedback.
A
This
is
such
like
a
specialized
tool
that
I'm
sort
of
like
wondering
how
we
find
I
think
my
biggest
question
is
like:
how
do
we
find
users
like
what
are
what
are
some
of
the
strategies
we
could
like
start
thinking
about
now,
because
I
expect
it'll,
take
us
a
while
to
find
maybe
users
to
give
us
feedback,
and
so
that
way,
if
they've
got
longer
lead
times
to
do
that,
we
can
start
working
on
like
building
a
pipeline
of
people
before
we
even
know
necessarily
like
what
we
want
to.
C
Yeah
yeah
the
best
way
to
do
this
is
probably
we've
done,
similar
things
like
for
Wiki
and
for
Pages.
Finding
those
users,
just
through
a
survey
asking
them
if
they
use
it
and
asking
them
if
they're
willing
to
be
interviewed
or
be
contacted
for
further
research,
can
be
a
lengthy
process
to
get
any
enough
users.
C
But,
depending
on
what
questions
you
really
want
to
ask,
you
might
not
need
that
many
to
start
out
with
if
you're,
just
thinking
about
a
couple
of
interviews,
sort
of
depends
a
little
bit
on
what
questions
we
want
to
ask,
but
couldn't
hurt
to
just
get
the
ball
rolling
there.
A
A
A
That
I
will
yes,
we
know.
C
Doesn't
actually
matter
that
much
right
now,
but
it
will
make
things
more
challenging
unless
we
can
find
a
way
to
yeah.
C
A
I
had
I
had
the
same
question.
Maybe
I
was.
A
B
A
Dig
but
I
had
thought
about
that
too,
like
I
wonder
if
we
could
catch
them
on
an
upgrade
to
be
like
interested
in
providing
more
feedback
and
like
have
a
link
to
like
a
form
and
like
sort
of
Evergreen
have
a
list
of
people
who
would
like
always
want
to
do
something.
I
just
don't
know.
If
we
can
do
that.
C
Yeah
I
mean
that's
I've
done
these
kinds
of
that
kind
of
thing
before
we
call
the
customer
councils
previous
job,
but
that
sort
of
looks
different,
because
the
ask
is
different.
C
A
Yeah
that
makes
sense,
yeah
I,
don't
I,
guess
maybe
it
would
make
sense
to
start
with
sort
of
like
what
do
we
want
to
know
from
them?
I
think
one
of
the
things
I
want
to
know
is
which
I
talk
about
is
like
I'm,
really
curious
on
the
split
of
users
between
like
interactive
and
like
non-interactive
use
like
how
many
people
are
using
it
for
scripting
and
how
many
people
are
interacting
with
it,
because
I
think
that
changes
potentially
like
what
we
would
want
to
build
like.
A
If
there's
lots
of
interactive
users,
then
there's
a
proposal
for
like
someone
who
wants
like
a
terminal
user
interface,
which
I
don't
think
we
would
ever
do
it's
sort
of
wild
and
crazy.
But
like
would
we
want
to
explore
like
some
form
of
like
code
review
commenting
or
like?
A
Would
we
want
to
get
more
into
like
these,
like
detailed
workflows,
if
people
are
like
actually
interacting
with
it,
whereas
if
people
are
doing
like
all
non-interactive
commands
where
they're,
just
like
literally
scripting
things
in
CI
jobs
or
in
external
scripts
or
other
tools,
then
like
that
sort
of
changes?
How
you
like
what
you
would
build
right,
like
you,
don't
want,
prompts
we
would
change,
maybe
some
default
Behavior
around
prompting
we
would
change
like
other,
probably
wouldn't,
approach
like
big
features,
because
you
wouldn't
automate
things
that
would
then.
B
A
User
input
and
so
I
think
that's
sort
of
like
the
initial
one
that
I
want
to
know
like
where
that
split
is,
but
then
like
it'd
be
worth
following
up
with
all
those
people.
I
think
Amy's
talked
about
like
docs
would
be
nice
to
sort
of
build
up
like
what
are
people
doing
with
it.
It
could
be
cool
to
have
like
some.
A
Some
of
those
people
like
give
us
really
specific
things
to
like
build
some
docs
that
are
actually
useful
for
people,
so
I
want
to
start
there
I,
just
don't
like
I,
don't
think
like
a
one
survey
question
of
like
do
you
use
this
interactively
or
like
scripted,
is
like
helpful
in
any
way,
shape
or
form,
and
so
like
thinking
through
that
more
would
probably
help,
but
yeah
I
I
think,
like
figuring
out
the
audience
is
going
to
be
the
tough
part
too,
because
we
don't
want
to
buy
us
like
if
people
are
using
it
automated
all
the
time,
they
may
never
see
like
an
upgrade
message
that
says
like
sign
up
here,
to
get
this
feedback,
because
they're
never
actually
seeing
those
things
they're
just
pulling
a
Docker
container
or
something
like
that.
C
Yeah
one
other
thing
we
could
try
is
if
we
can
get
a
blog
post
up
there,
you
know
sort
of
like
Hey
we're
off.
You
know,
hoping
you
enjoyed
the
release
of
the
CLI
a
while
back.
We
want
to
know
how
it's
going
for
you,
if
you're
interested
on
providing
feedback
or
becoming
part
of
a
you
know
ongoing
whatever
we
want
to
call
it
get
in
touch.
A
Yeah
I
will
open
at
some
point
in
the
near
future
like
a
research
issue,
and
we
can
start
thinking
about
it.
I
don't
think,
there's
any
like
pressure
to
start
doing
anything,
there's
a
lot
of
still
cleanup
and
Automation
and
things
that
need
to
happen
in
the
CLI
before
we
begin
doing
new
things,
but
yeah
I
will
excuse
me
some
things
to
think
about.
C
A
A
B
Yeah
Amy,
if
I,
don't
think
I
can't
think
I'm
waiting
for
anything.
So
I
will
message
you
if
it's
urgent
but
I
I,
think
I
ping,
you
a
lot
and
I
I,
then
I
forget
about
it
right
away,
so
it
can't
be
that
important,
I'm,
usually
just
like
hey,
is
this
good?
Okay,.
A
A
A
Well,
it's
good
to
see
everyone
enjoy
the
rest
of
your
week
and
we'll
chat
again
soon.