►
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
I
think
I
started
it
last
week
and
then
I
went
in
and
updated
the
meeting
update
to
just
have
a
new
url,
but
I
set
everyone.
C
A
Hosts
in
the
event
that
I'm
out
or
whatever,
but
I
think
that's
an
interesting
observing
observation
daniel
it
could
be
that
you
were
the
first
one
in
and
therefore
you've
been
given
all
the
power
we'll
have
to
test
that.
C
C
Good
work
holly,
thank
you.
Maybe
we
can
make
that
just
a
small
task
at
the
end
of
each
of
our
meetings.
Just
someone
will
take.
C
D
A
I
have
two,
but
actually
I
seem
to
have
three
and
one
is
for
the
ux
calendar.
One
is
something
that
I
guess
it's
just
my
calendar
and
then
there's
a
third
and
I'm
not
sure
why
yeah.
B
A
You
and
I
are
meeting
in
a
bit
I'm
happy
to
if
you
want
just
a
second
pair
of
eyes.
I
don't
know
how
much
I
can
help,
but
I'm
happy
to
try
yeah.
D
D
C
So
the
question
I
had
on
agenda
was:
there
have
been
a
thread
a
while
back
in
the
ux
channel
about
using
decision,
trees
and
documentation.
I
think
initially
it
was
jeremy,
just
sharing
like
a
decision
tree
on
like
when
to
use.
C
So
I
just
took
whatever
information
was
in
that
decision
tree
and
put
into
a
mermaid
diagram,
and
I
was
considering
creating
an
mr
to
add
that
to
pajamas
and
then
iterate
on
like
how
it
would
make
sense
to
refine
it
further.
Like
my
biggest
thing,
I
don't
really
understand
is
there's
like
four
questions
and
I'm
like.
If
I
say
yes
to
any
of
these,
does
that
send
me
down
one
track
or
is
it
like
just?
C
Is
it
majority
yes
or
majority?
No,
I
don't
really
know
the
exact
situation,
but
yeah
I
was
trying
to
like
convert
it
to
make
sense
for
pajamas,
because
they
were
using
terms
that
didn't
necessarily
align
directly
to
pajamas.
Like
sheet
was
one
of
the
outcomes
I
was
like.
We
don't
have
a
sheet,
but
we
would
call
that
a
drawer.
C
B
I
think
it's
good
to
have.
I
don't
know
why
they
would
use
mermaid
versus
a
visual,
more
nice
representation,
I'm
assuming
it's
just
because
it's
part
of
the
system
that
automatically
reads
mermaid
code.
C
Fair
yeah,
I
don't
think
they're
pretty.
I
think
the
benefit
of
them
is
they
are
pure
markdown,
so
that
helps
us
a
little
bit
with,
I
guess,
blobs
and
not
having
to
deal
with
images.
A
C
C
A
I
love
your
thinking,
though,
of
of
offering
some
sort
of
decision
tree
approach
to
some
of
these
kinds
of
questions
was
that
was
it
kind
of
a
two-part
question,
then
of
should
we
use
the
mermaid
diagram
to
do
this,
or
should
we
do
this
and
then
separately?
Should
we
use
a
mermaid
diagram
to
do
this.
C
C
B
Well,
not
writing
a
new
thing
on
the
handbook
yet,
but
I'm
creating
a
new
error
message,
because
the
current
error
messages
aren't
scary
enough
for
this
particular
action.
So
I'm
having
to
use
a
modal
because
it's
like
pops
up,
saying
you're
going
to
do
this.
It's
going
to
be
bad
instead
of
just.
A
A
An
example
that
comes
to
mind
for
me
was
a
modal
recently,
in
which
case
we
were
asking
people
about
canceling
a
comment
and
then
there's
the
cancel
button
as
part
of
the
cancel.
This
comment,
which
was
causing
some
confusion,
but
the
long
story
short
was
that
there
was
a
title
in
the
modal
and
we
didn't
have
an
option
in
pajamas
to
have
a
modal
without
a
title,
and
so
then
there's
the
second.
B
I
would
probably
bring
it
up
with
the
foundations
open.
B
Of
as
we
design
the
component
or
as
we
first
on
the
design
from
the
foundation
side
and
second
implementation
for
everyone
else's
side,
is
that
something
that
needs
to
be
part
of
the
process
in
making
components.
D
Well,
and
could
we
also
look
at
like
what's
material
doing
what's
ibm,
what
are
all
these
huge,
huge
designs
to
see
how
I
was
thinking
the
same
thing
and
not
spin
our
wheels
so
much
as
you
know,
just
take
it
back
on
a
lot
of
the
research
that
they've
already
done
and
see
if
it
works,
but.
C
C
Well,
there's
not
like
a
perfect
answer,
so
I
guess
my
hope
would
be
this
decision
tree.
Would
land
us
on
a
consistent
experience
so
like
in
daniel's
example,
there's
a
question
that
says
like
is
your
content,
an
important
warning,
that's
preventing
or
correcting
a
critical
error.
Like
sounds
like
a
great
case
for
a
modal.
You
say:
yes,
that's
where
you
land.
D
D
C
Yeah,
I
I
think
that's
what
I
want
is
to
have
more
objectivity
into
it,
but,
like
I
brought
this
up
in
the
foundations
conversation
one
time,
because
there
were
several
pages
with
the
form
in
the
same
page
as
like
the
table,
specifically
protected
branches
or
creating
access
tokens.
Those
kinds
of
things
already
have
the
form
there
and
when
I
brought
up
the
idea
of
using
a
modal,
it
was
like.
C
C
I
think
that's
why
decision
tree
might
help
in
that
situation
is
to
like
take
out
some
of
the
subjectivity
of
saying.
Well,
I
like
being
able
to
see
everything
at
the
same
time,
and
I
said
it
moving
it
towards
like.
Do.
Users
need
to
see
the
content
of
the
table
below
in
order
to
complete
the
task
of
filling
out
that
form,
but
I
think
daniel's
on
the
right
track,
I'll
I'll,
open
a
smallmouth
and
then
like
put
it
in
the
foundations
agenda,
to
talk
about
and
see
if
it
gets
anywhere.
D
Yeah
all
right,
so
basically,
what
I
would
like
y'all's
opinion
on
is
how
to
best
socialize
this
major
change
in
our
tables
in
a
way
that
again
kind
of
admits
the
back
and
forth
like
well.
Should
we
do
this?
Should
we
do
this
or
I
feel
it
should
be
this
way?
I
feel
it
should
be
this
way
so,
and
I
I
linked
an
example
of
where
this,
this
back
and
forth
kind
of
an
example
of
what
how
this
could
happen.
You
know
like
for.
Let
me
share
my
screen.
D
In
a
nutshell,
we
kind
of
a
few
of
us
were
going
back
and
forth
like
well.
Should
it
what
is
the
intermittent
checkbox?
What
does
that
actually
mean?
It's
confusing
to
me?
Well,
this.
The
work
that
I've
done
specific
to
import
in
regards
to
enterprise
tables
stems
from
work
that
andy
had
done
a
while
back,
and
I
know
that
I'll
link.
All
of
these.
I
apologize.
These
aren't
linked
into
the
agenda,
but
andy
had
already
started
kind
of
doing
this
massive
exploration
on
how
we
can
use
enterprise
tables
to
get
left.
D
So
I
know
a
lot
of
his
work
stemmed
from
material.
D
I
don't
know
how
much
so
and
since
he's
on
paternity
leave,
I
am
where
I
am
stuck
is
how
do
I
socialize
this
with
the
ux
team
in
a
concise
way
that
we're
not
necessarily
arguing
whether
or
not
we
should
have
like
a
intermittent
checkbox
and
what
that
actually
means
and
how
the
user
interprets
that,
because
material
has
spent
a
lot
of
time
designing
their
tables
to
reflect
what
can
be
used
in
gmail,
which
gmail's
use
one
out
of
four
people
across
the
globe.
D
So
my
whole
thing
is:
let's
copy
exactly
what
material
has
done
yet
socialize
it
with
the
ux
group
to
say:
is
there
anything
missing
from
what
materials
already
done?
If
so,
how
do
we
implement
it,
or
do
we
even
need
it
to
be
in
the
table
like?
Does
that
make
sense?
Sorry,
I'm
a
little
flustered
when
talking
about
this,
but
I
hope
I'm
coming
across
as
clear.
B
I
don't
know
about
that.
I
think
that's
maybe
overthinking
it,
but
I
do
think
having
like
feature
parody
between
them
makes
sense
because,
as
you
stated
like
this
sort
of
thing
works
in
such
a
huge
use
case
and
across
so
many
use
cases,
I
think
it
makes
sense
to
have
it
just
as
a
basis
of
the
function
of
the
table.
B
D
I
just
want
to
make
sure
that
whatever
we
implement
can
be
used
for
us
through
across
the
entire
product.
I
also
this
is
a
huge
development
effort.
Potentially
so
I
don't
even
know
how
then
to
spread
this
out
across
multiple
developers,
or
I
mean
I'll
get
to
that
point.
I
guess,
but
really
I'm
looking
for
any
suggestions
on
how
to
socialize
what
material
is
already
done
with
the
ux
team
in
a
really
quick,
easy
way,
my
thought
was.
D
I
can
go
back
and
check
all
of
andy's
work
to
see
if
it
is
one-to-one
comparison
with
material
or
in
some
cases
I
might
just
screenshot.
I
was
thinking
just
taking
a
screenshot
of
what
material
has
on
their
website
posting
to
a
feedback
issue
and
saying:
hey:
is
there
anything
missing
from
this
table
functionality?
If
so,
what
and
why?
D
C
D
Everything
everything
that's
associated
with
taking
our
tables
to
kind
of
the
enterprise
level
which
we
don't
currently
have.
It's
like.
C
Okay,
that
checkbox
exists
in
our
pajamas
figma
library,
but
getting
your
developers
to
implement
it
can
be
a
pain
depending
on
what
table
they've
implemented
on
a
page.
If
it's
not
like
one
of
the
ones
that
has
that
as
an
easy
state
to
add
to
it
or
like
as
an
easy
control,
then
it's
going
to
be
a
really
good
pain.
So
to
me
it
seems,
like
you
just
need
to
slice
it
into
individual
pieces
and
then
try
and
work
your
way
to
that
like
holistic
picture.
C
So
maybe
this
is
an
epic
that
has
a
collection
of
issues,
one's
for
the
check
boxes,
one's
for
the
filtering
options,
one's
for
the
search
bar,
and
you
can
call
that
whole
component,
something
if
you'd
like.
B
Yeah,
that's
exactly
what
I
was
thinking
is
reduce
everything
to
one
one
quote:
unquote:
symbol
thing
so
like
check
box,
draggable
columns,
different
yeah,
zero,
zero
excuse
me
zebra,
coloring,
right
and
the
way
you
say
like
you,
wanna
socialize
it
to
make
sure
everyone
understands
or
sees
it.
B
I
think
that
might
be.
I
mean
you've
already
done
it.
You've
already
mentioned
it
in
the
comment
and
you've
had
feedback,
but
the
only
other
way
would
be
to
say
bring
it
up
in
the
ux
weekly
or
just
say:
hey,
here's,
a
new!
Mr
here's,
a
new
feature.
I
did
it
and
that's
what
it
is
and
then
let
people
provide
feedback
and
say:
oh
no,
it's
it's
on
fire.
We
don't
like
it
and
that's
where
the
conversation
comes
in
yeah.
B
Not
the
best
way,
but
that's
the
way,
gitlab
works
because
it's
you
know
so
iterative.
They
want
you
to
go
ahead
and
take
the
initiative
of
making
the
change
on
good
faith
that
it's
a
good
proposal
and
the
number
of
checks
to
go
through
a
final,
mr
approval
kind
of
would
catch
any
of
that.
So
I
would
just
say,
as
first
like
austin
said,
first
break
everything
down
to
specific
individual
things.
B
Make
this
one
big
epic,
because
I
know
there's
been
a
number
of
stuff-
that's
been
done
elsewhere,
like
I
was
thinking
about
draggable
columns.
Nick
was
talking
about
this.
You
know
years
ago,
when
we
first
got
hired
on
it's
just
an
ongoing
thing,
but
nobody's
ever
really
taken
initiative
to
really
just
do
it.
I
think
that's
kind
of
just
the
way
it
needs
to
just
be
done.
D
B
All
right,
let's
use
this
one,
actually
promote
this
to
an
epic.
I
mean
it's
closed
right
now,
but
I
don't
want
to
reopen
it
if
we
can
reopen
it,
promote
it
to
an
epic
and
then
just
break
every
one
of
those
off
individually.
This
one
here's
this
one.
C
D
B
B
Maybe
I
have
that
one
on
my
calendar
too.
I
don't
know
why
both.
C
Consistency
is
certainly
hard.
I
mean
something
that
I
know.
Holly
probably
knows
more
about
it's
like
even
the
search
bar
for
like
issues.
It
behaves
differently
if
you're
in
a
board,
if
you're
in
the
list
view.
So
you
know
when
components
like
look
this
similar,
like
they
end
up
behaving
differently
and
getting
that
to
be
consistent.
It's
it's
not
easy.
D
D
C
D
C
All
right
still
still
waking
up
here
a
little
bit
so.