►
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).
B
Mine
is
also
pretty
messy,
but
I'll
just
kind
of
walk
through
some
of
the
things
that
I've
been
exploring.
So
I
keep
going
back
to
the
three.
How
might
we's
that
mike
had
created
just
because
I
feel
like
there's
so
much
possibility
with
this
clabject
view
that
I
want
to
be
sure
that
I'm
staying
on
track
and
not
like
swiveling
off
too
far,
so
his
three
were
making
it
efficient
or
more
efficient
to
understand?
B
So
I've
been
just
kind
of
continuing
to
work
on
those
some
of
this.
We
had
looked
at
last
time,
but
I
added
on
to
it
just
a
bit
playing
with
some
ways
to
kind
of
notify
the
user
when
something
has
changed,
but
then
that
raised
the
question
of
what
kind
of
notifications
are
meaningful
to
users
in
terms
of
changes?
Does
it
matter
if
it's
a
description,
update
or
if
it's
it
went
from
confidential
to
not
confidential,
like
what
level
of
notification
needs
to
be
surfaced
and
for
which
notification?
B
B
I
also
explored
having
the
ability
to
maybe
even
sort
of
like
when
you
use
find
in
the
browser
having
the
ability
to
see
the
number
of
changes
and
then
potentially
click
on.
You
know
up
and
down
arrows
to
kind
of
navigate
through
it,
but
that
gets
complicated
if
we
had
a
sidebar
and
we
were
trying
to
address
it.
C
C
Seeing
the
historical
difference
so
like-
and
this
is
like
more-
I
think-
of
an
executive
or
like
somebody
who
just
wants
a
high
level,
because
the
descriptions
used
for
tracking
a
lot
of
different
things
like
everybody
contributes
to
it
sometimes
so
like
a
nuke,
was
a
good
example
where
he
uses
issues
he
goes
through
and
instead
of
reading
comments
and
all
that
stuff.
He
just
goes
and
looks
at
the
system
activity
to
look
at
each
of
the
different
diffs
so
like.
C
B
B
If
you
want
to
kind
of
within
the
same
context,
which
I
thought
was
really
interesting,
but
that
doesn't
seem
like
it
would
be
an
mvc
thing,
and
I
again
I
don't
know
if
that's
something
that's
going
to
provide
that
much
value
from
the
start.
So
I
want
to
be
mindful
of
that
kind
of
thing.
When
I'm
doing
my
designs,
but.
A
A
Of
like
a
notification,
though,
like
you
have
going
up
at
the
top,
I
don't
think
we
should
always
be
showing
the
diffs
or
things
like
that.
I
think
letting
you
know
that,
like
there
was
one
description
update
or
two
or
three
since
you
last
visited
and
having
a
click
or
two
deeper
to
go.
Look
at
the
diff.
If
you
want
to
yeah
versus
having
it
like
pile
up
in
the
ui.
I.
C
B
B
I
mean
what,
if
you
like,
I
and
a
lot
of
people,
I
think
here
at
git,
lab
have
tons
of
tabs
open
that
we
leave
open
all
the
time
and
maybe
having
better
collaboration
and
better
connection
between
these
things
would
reduce
that.
But
if
you
leave
it
open
all
the
time,
is
it
a
real-time
update
where
people
are
seeing?
You
know
that's
as
the
changes
happen,
or
is
it
again
a
reflection
of
a
forced
page
refresh?
B
B
C
C
So
so
like
it,
if
something
is
new
to
me,
it
means
that
I
haven't
looked.
I
haven't
put
my
eyes
on
it.
Yet
right,
okay,
and
so
usually,
when
you
put
your
eyes
on
it,
it
means
that
you
like
will
scroll
to
or
like
within
the
view
it
will
be
visible
to
me,
which
means
that,
like
I've
seen
it
so
it's
sort
of
like
what
slack
does
when
you
scroll.
D
B
A
B
Yeah
that
was
actually
kind
of
what
I
was
thinking
too,
with
these
arrows.
That
was
something
that
we
had
received.
Feedback
on
when
exploring
the
fixed
headers
in
the
past
was
that
people
really
love
that
navigational
aspect
of
mrs
that
they
can
go
back
and
forth
in
the
content,
and
they
wanted
something
like
that
and
issues
too.
B
But
inevitably,
the
goal
I
think
is
is
to
simplify
the
experience
of
consuming
that
information
and
making
it
easier
to
get
through
as
opposed
to
having
to
just
scroll
scroll
scroll
and
have
to
figure
out
where
you
were,
if
you're
coming
from
something.
But
that
was
also
what
I
was
kind
of
playing
with
here
was
that
maybe,
as
you
scroll,
it
highlights
something
new
in
some
way,
I'm
just
kind
of
demonstrating
it
with
a
soft
blue
background
right
now,
it
doesn't
necessarily
have
to
be
that,
but
then
the
gray
here
is
showing.
B
This
is
also
something
that
might
be
new,
but
it's
not
necessarily
in
your
either
in
your
direct
view
or
as
you
navigate
using
these
arrows.
If
that
was
something
we
wanted
to
pursue,
then
in
that
case
it
would
highlight,
as
you
got
to
two
of
two
but
then
one
of
two
would
kind
of
fade
to
a
different,
color
or
change,
but.
C
A
B
B
Sorry
about
that,
so
another
approach
that
I
was
exploring
again.
I
really
liked
gabe's
kind
of
minimalist
design
for
the
detail
view,
but
let
me
just
kind
of
show
how
this
could
potentially
work
so
going
back
to
again,
starting
with
to
do's.
We've
got
this
sort
of
minimized
view
of
the
call
object
and
when
you're,
in
this
view,
you
can
potentially
click
this
little
arrow
or
something
that
takes
you
to
sort
of
a
larger
detail
view.
This
is
when
you
have
intentionally
said.
B
I
want
to
leave
the
context
admin
and
go
to
a
full
view
of
this
thing,
as
opposed
to
the
previous
view,
of
course,
where
you're
kind
of
getting
both
you're
staying
in
your
current
context
and
getting
a
snapshot
of
what's
happening
in
the
collab
check,
but
not
necessarily
having
to
leave
your
contacts.
So
there's
value
I
think
in
offering
both.
B
I
love
that
thought,
particularly
if
it's
something
that
the
description
is
minimal
or
it's
not
that
important
to
me.
But
the
comments
are
very
important
to
me.
Maybe
I
want
to
expand
that
space
so
that
I
can
see
more
of
that
information
and
reduce
some
of
the
back
and
forth
that
I
have
to
do
between
those
pieces
again.
B
D
B
D
B
Is
so
something
else
I
had
explored
was
having
this
little?
I
don't
know
how
well
you
all
can
see
this,
but
this
little
activity
thing
here
as
opposed
to
the
notification
bar
at
the
top
having
something
that
kind
of
just
gives
you
a
little
notification
here
that
there's
something
new
happening
in
this
particular
issue:
oracle
object
and
when
you
click
it,
I
know
this.
Isn't
it's
not
necessarily
a
proposed
final
design,
but
just
kind
of
showing
that
maybe
it
can
provide
an
overlay
of
some
sort.
B
In
a
conversation,
that's
just
happened
or
potentially
be
able
to
revert
back
to
a
previous
decision
that
might
have
been
made
that
I
can
see
here
if
I
want
to,
but
that
could
be
mvc
or
not
in
vc.
That
could
be
later
on.
Another
approach
that
I
saw
to
this
that
I
thought
was
interesting,
was
putting
this
in
a
modal
or
also
even
separately,
going
to
a
tab
and
having
tabs
in
there.
B
C
I've
raised
my
hand
if
I
can
go
yes,
please
three
points.
I
like
the
overview.
I,
like
the
kind
of
dual
column
detail
view.
Is
there
an
opportunity
to
make
it
so
that
when
you
do
open
this
up,
you
don't
lose
your
content
context.
So
it's
almost
like
sliding
out
the
what
was
the
overview
into
this
more
like
broader
view,
so
like
I
could
see
the
preview.
I
could
see
this
full
view.
I
could
close
this
and
still
be
on
my
to-do's.
C
That's
point,
one
that
I
would
like
to
see
or
like
for
me
personally
as
a
user.
The
second
is
the
draggable
columns
width.
I
use
that
all
the
time
in
slack.
For
that
same
reason,
where
sometimes
I
want
to
look
in
the
the
thread
and
like
pay
more
attention
to
that,
I
will
drag
and
make
it
bigger
as
long
as
like
it
always
snaps
back
to
a
default.
C
You
know
if
I
close
the
sidebar
or
whatever
that
was
point
two
and
then
three
I
like
the
activity
in
the
drop
down
like
that,
because
you
could
also
make
it
scrollable
most
of
that's
like
noisy.
I
don't
think
people
always
care,
sometimes
they
might
want
to
know
so
long
as
we
then
figure
out
how
to
show
like
toggle
or
slide
through
the
history
of
the
description
change
like
near
the
description,
because
that's
the
one
system
note
that
you
interact
with
it's.
C
The
only
system
that
you
interact
with
it
would
make
more
sense
if
it
was
tied
close
like
that,
the
ability
to
switch
between
the
different
versions
or
see
them
was
tied
closer
to
the
description.
So
you
don't
have
to
like
you
know,
navigate
through
this,
the
notes
to
find
the
description
and
expand
to
see
the
diff.
You,
like
literally,
show
the
diff
right
in
where
the
description
is
now.
I.
C
The
other
thing
that
this
sort
of
ui
framework
approach
gives
us
is
that
when
we
want
to
layer
in
other
things,
like
maybe
a
relationship
hierarchy,
or
maybe
some
of
these
other
things,
we
can
always
have
the
discussion
present.
But
then
like
have
different
content
that
shows
up
in
the
left-hand
panel
right
depending
on
what
you're
clicking.
C
C
So
thinking
about
that
left
description
panel
is
a
panel
for
relevant
content,
depending
on
where
you're
at
in
the
conversation
or
what
you're
trying
to
do
so.
The
design
manager
would
be
a
good
example
right,
like
they're
like
if
you
want
to
reference
a
design
instead
of
spinning
up
and
overlaying
everything
you
could
display
the
design
that
you
reference
in
a
comment
in
that
left-hand
panel.
C
Instead
of
the
description
temporarily
or
another
issue
comment
somewhere
else
that
somebody
references
or
I
mean
you
could
use
it
for
all
sorts
of
different
things
or
showing
the
parent-child
relationship.
But
I
don't
know
I
was
just
thinking
about
like
remember
that
youtube
video
they
sent
you
about
the
scrolly
thing
where,
as
you
scroll
down,
it
changes
the
content.
Basically,
as
you
interact
with
the
main
content,
it
would
change
the
content
in
this
like
side
area
to
be
relevant.
That
sort
of
idea.
This.
D
And
make
one
quick
sure
I
don't
know
if
it's
too
soon
for
this,
because
it's
more
like
a
crit
type
of
level
of
feedback,
so
you
can
just
throw
it
away
if
you
want
to
with
the
the
law
of
proximity
your
like
thumbs
up
thumbs
down
the
little,
I
think
it's
activity
feed
the
emoji.
Those
are
all
according
to
a
lot
of
proximity,
they're
actually
related
to
the
things
above
them.
D
D
B
I
know
that's
a
very
good
point
honestly.
This
was
me
kind
of
pulling
that
information
over
when
it
was
in
this
sort
of
sidebar
piece
and
then
I
just
kind
of
left
it
there
as
I
started
exploring
other
things,
and
I
thought
I'll
come
back
to
this.
I
do
like
the
thought
of
it
being
here
just
for
simplicity,
but
I
see
what
you're
saying
absolutely
that
from
a
contextual
perspective,
people
may
not
realize
that
those
things
first
of
all
they
may
not
notice
them.
B
A
B
B
Yeah,
I
think
I
have
seen
some
of
the
discussions
surrounding
that,
but
I'll
check
with
them
as
well.
The
other
thing
that
I
was
looking
to
maybe
explore
next
was
kind
of
the
the
same
type
of
fun.
There's
absolutely
nothing
here,
obviously
right
now,
but
how
how
to
show
the
relationships
between
the
issues-
and
this
is
a
question
that
I
have
for
the
pms.
Actually,
what
kind
of
information
do
you
need
to
be
able
to
see
when
it
comes
to
relationships
between
things
like
we
know,
related
blocked
and
blocking,
but
what
else.
A
I
think
I
like
some
of
it
would
be
a
click
below
like
this,
but
it's
parenting,
lineage
like
it's
breadcrumb
or
something
I
think
that
needs
to
be
visible.
Okay
and
the
I
if
it's
related
or
blocked
needs
to
there
needs
to
be
some
indicator
that
that's
on
as
well.
So
I
don't
have
to
like
mystery
me:
click
on
linked
every
time
to
see
so
either
like
a
count
or
something
that
would
show
the
number
I
do
like
having
them
they're
available
so
that
it's
like
a
easy
tab
switch
without
losing
context.
C
Can
you
expand
it
yeah,
so
I
use
it
all
the
time
when
I'm
looking
at
issues
when
I
look
at
related,
merge
requests.
I
look
to
see
if
the
merge
quest
is
open,
closed
or
merged.
I
look
at
the
milestone
and
I
see
who's
assigned,
so
I
know
who's
working
on
it
when
it's
going
to
be
worked
on
or
when
it
is
planned
for
and
then,
if
it's
open
still
or
has
been
merged
right,
but
one
of
the
things
that
we
don't
do
well
now
is
like
we
don't.
C
I
don't
need
to
see
all
of
them.
I
just
want
to
see
the
most
like
relevant
ones,
because
sometimes,
if
there's
15
link
merge
requests,
I
don't
care
about
the
things
that
have
been
closed
like
six
months
ago.
I
care
about
the
thing
that
is
like
and
this
current
milestone,
or
that
the
team
is
working
on
now
right
and
the
status
of
that
thing
same
thing
with
parent,
with
the
issues
and
epics
and
stuff
like
that,.
A
A
C
B
I
do
because
I
think,
there's
a
lot
of
opportunity
there.
This
is
great
feedback,
though,
and
I
appreciate
it
because
I
do
want
to
be
thinking
about
it,
but
I
really
liked
what
that
obsidian
app
does
that.
I
think
I
showed
a
couple
of
you
that
mike
had
introduced
to
me
mike
nicholls
by
the
way
I
had
created
this
just
just
to
clarify.
I
had
created
this
oh
come
on.
It's
not
wanting
to
drag
over.
B
For
some
reason,
zoom
is
in
the
way
there
we
go,
so
I
had
created
just
some
test
things,
but
what
I
like
about
it
is
two
pieces
the,
and
this
is
more
for
kristen.
I
think
because
I
don't
think
I've
shown
her,
but
you
can
put
in
a
tag
for
something
and
then
it
will.
It
will
show
up
over
here
when
you
search
as
well
as
anything
else,
so
this
is
just
kind
of
a
way
to
connect
those
pieces,
but
then
I
can
also
do
this.
B
You
know
some
way
to
to
make
it
like.
Actually
I
need
to
do
this.
Sorry
not
mention
me.
I
need
to
actually
reference
the
title
of
one
of
those
testing
and
it
will
provide
like
links
to
other
things.
So
in
this
case
it
would
be
the
same
as
either
addressing
a
keyword
that
I
could
then
make
searchable
through
a
filtered
list
over
here.
That
shows
me
not
only
the
word
that
I've
searched
for,
but
a
bit
of
the
context
around
it,
which
is
really
helpful.
B
So
it's
not
just
showing
me
the
word
itself
in
this
case.
It
does
because
I've
only
got
one
thing
here,
but
if
I
add
an
additional
stuff,
it
shows
me
a
bit
of
the
context
associated
with
the
word,
which
is
helpful
if
you're
looking
for
something
that
is
like
a
yes
go
with
this
icon
or
no
don't
go
with
this
icon
and
it
turns
out
all
you're
searching
for
is
icon.
It
helps
you
to
quickly
be
able
to
filter
everything
and
see
the
context
related
to
that
particular
word,
which
is
nice
and
then
over.
B
A
This
I
haven't
seen
obsidian,
but
we
did
a
lot
of
deep
dives
into
rome,
research,
which
is
a
lot
like
this.
It's
a
competitive
wiki,
so
I
used
to
own
wikis.
So
I
think
that
that
this
type
of
markdown
could
be
really
useful
in
git
gitlab,
for
how
we
do
our
gitlab
flavored,
markdown
and
being
able
to
attach
specific,
especially
mentions
onto
markup.
A
But
I
do
think
the
current
wiki
team
is
evaluating
more
from
the
ui
experiences
with
code
blocks.
Dropping
in
more,
like
notion,
does
versus
like
editing
the
markdown
itself.
So
I
I
totally
on
board
that
I
think
that
this
could
work,
but
once
we
have
those
individual
blocks
or
areas
you
could
do
more
in
terms
of
like
maybe
we're
commenting
on
this
particular
paragraph,
or
this
particular
word.
D
C
C
A
B
Competitor
of
them,
but
something
that
I
thought
mike
had
said
that
was
really
interesting
was
we
were
talking
about
the
relationships
and
I
said
well,
there's
got
to
be
a
way
to
visualize
these
relationships,
and
I
said
I
want
to
be
able
to
incorporate
something
like
that
into
our
product
and
he
goes
no.
You
don't
want
to
do
that,
because
this
is
what
you
get
now.
This
is
simple.
Obviously
we
only
have
three
points
here,
but
if
you
have
40
points,
is
that
meaningful?
At
that
point?
It
just
feels
like
a
big
starburst
of
data.
C
C
B
Cool
yeah.
Well,
I
know
we're
at
time,
but
those
are
some
of
the
things
that
I
had
been
playing
around
with
and
exploring
and
kristin,
I'm
so
sorry,
I've.
You
had
asked
yesterday
about
a
link
and
I
just
realized.
I
didn't
share
that
with
you,
so
I'll
post
that
in
the
agenda
right
now
for
this
is
there
anything
else
like.
D
D
C
A
C
If
we
can't
technically,
then
I'm
fine
approaching
that,
but
the
way
that
they
told
me
yeah,
they're
gonna,
have
to
invest
the
time
to
rewrite
it
all
anyways
which,
if
we
don't
like,
have
design
input,
then
they're
gonna
have
to
do
it
again.
So
it's
like
double
the
work,
so
whatever
they
say
like,
I
follow
their
guidance,
but
that's
why
I
was
pushing
to
like
do
whatever
ui
change
we
wanted
now
so
because
it
it's
gonna,
be
the
same
amount
of
work,
whether
we
do
the
ui
changes
or
not.
If
that
makes
sense,
yeah.
B
I
put
a
question
just
for
everyone
to
kind
of
think
on
that.
It
would
be
helpful
for
me
to
see
if
there's
anything
that
we
have
identified
as
this
is
definitely
something
that
we
want
to
strive
for
for
mbc,
and
I
would
love
for
alexis
to
have
a
chance
to
kind
of
talk
for
hers
too,
because
I
want
to
make
sure
that
everything
is
being
reviewed.
But
is
there
anything
that
we
want
to
keep?
Is
there
anything
that
we
want
to
discard
of
what
we've
seen
so
far
like?
B
So
it
would
be
helpful
for
me
so
that
I
don't
just
keep
on
going
all
over
the
place
to
have
it
kind
of
honed
in
on
what
what
we
might
want
to
dig
deeper
into
versus
what
we're
done
with,
and
we
don't
want
to
explore
for
this,
and
you
don't
have
to
answer
it.
But
that
would
just
be
helpful
to
to
help
me
stay
on
track.