►
From YouTube: Plan roadmap deep dive
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
B
B
B
Page
so
salute
yeah
yeah.
So
this
thing
here,
which
already
does
exist,
so
that's
great,
so
yeah.
So
basically
all
the
mouse
engages
in
the
password
based
on
the
title,
and
we
remove
that
because
we
have
group
milestones
down,
so
we
can
get
rid
of
these
pages.
That's
what
that
is.
That's
a
rescheduled,
very
straightforward.
This
is
another
example.
So
there's
a
Ginn
lab
C
version
of
10
0
and
there
is
gay
lab
EE
version
of
10
0
and
we're
just
getting
rid
of.
A
B
Page
as
it
says,
well,
it's
not
straightforward.
This
one
is
something
that
we've
talked
at
length
about
so
creature
on
earth,
a
firm
that
make
quick
actions
create
issue
from
that
make
so
same
thing
as
this
one
for
each
other
issue
from
ethnic
HIV,
epic.
This
one
is
one
that
is
a
lot
of
people
are
annoyed
about.
B
C
B
It
in
the
UI
during
so
that's
that's
these
two.
This
one
is
also
very
straightforward.
This
is
related,
merge,
request
issue.
So
what
I
talked
about
last
time
we're
working
on
right
now,
this
one
I,
don't
think
we
need
to
do.
That's
that's
why
it's
in
the
backlog,
but
right
now,
it's
there
they're
like
this.
B
Threaded
conversations
and
ethnics
a
little
bit
of
cleanup
design
once
this
to
be
called
threads
officially,
as
opposed
to
a
discussion,
there's
a
couple
places
and
then
API
support
so
again,
pretty
small
things,
so
nothing
not
creating
anything
new,
for
example,
there's
resolve
ability
of
discussions,
but
some
people
want,
but
I
don't
feel
super
important
that
we
need
to
talk
about.
That's
why
I
purposely
broke
that
out
a
little
bit.
B
A
B
You
can
see,
keep
going
scope,
labels
we've
talked
about
at
length,
so
that
is
additional
styling.
Some
more
background
technician
things
some
searching
things
making.
These
are
all
about.
Styling
making
the
system
notes
look
better,
even
though
notifications,
so
basically
every
time
we
have
this
thing
here
with
scope
labels.
This
will
happen
I
just
today,
I
staging
looks
great.
This
is
what
will
happen.
It
will
show.
B
You
know
added
this
and
move
to
move
that,
but
then
all
these
issues
are
make
it
to
so
that
this
is
one
transaction
and
it
would
be
communicated
as
such.
So
it's
a
you
know
like
added
this
scoped
label
and
so
on
so
important,
so
that
I
don't
get
changed
to
wraps
those
things.
This
is
doing
the
tree
in
addition
to
the
road
map
view
which
we
are
already
getting
and
then
also
dragging
and
dropping,
which
is
cool,
so
I
think
I
know
already
how
to
mock
up
the
app
for
this.
B
B
C
B
Around
exactly
issues
yep,
that's
that's
a
good
change,
so
the
design
is
pretty
awesome.
I
fully
expect
that
there
will
be
more
issues
added.
You
can
see
one
design
here,
so
there
needs
to
be
some
I.
Think
it's
ready
to
start
development,
slash
designed
to
be
put
into
things
so
I
haven't
pushed
the
team
to
to
add
anymore.
You
know
concept
yet,
but
I
fully
expect
that
we
will
have
you
know
two
or
three
follow-up
issues
after
we
start
just
digging
to
the
first
one.
So
that's.
Why
there's
only
one
issue
here,
but
I?
B
B
No,
this
is
yes,
so
this
is
doing
the
roadmap
in
the
Romantics
itself.
Sorry
I
mean
through
the
child
issues.
Child
ethics
in
the
roadmap
do
itself.
We
started
out
the
reverse.
We
had
the
roadmap
in
the
child,
so
this
is
something
that
we
might
not
need
to
do
so.
I'm,
not
not.
Students
is
one
of
those
that
I
would
really
look
at
how
people
are
using
the
road
map
view,
especially
in
light
of
adding
it
to
the
pages,
so
hide
issue
board
labels.
This
is
it
will
be
a
welcome
change.
Yeah.
A
B
As
it
as
in
as
we
should
do
in
kill
em
as
we
do
in
plan,
we
just
break
them
up
as
far
as
possible,
so
the
first
one
is
just
aa
glowing
it
and
there's
every
time
you
go
to
the
same
or
you
have
to
redo
it,
retail
it.
And
then
this
subsequent
issue
is
saving
that
as
a
preference,
so
so
it's
stored.
And
then,
if
you
think
you
know
for
five
minutes,
you
can
do
a
bazillion
different
things.
B
For
example,
you
can
make
we
have
some
mock-ups
you
can
you
can
shrink
them,
for
example,
you
can
instead
of
hiding
them
totally
you
can
you
can.
You
can
take
out
the
word
so
that
there's
just
a
bar
select
relevant.
You
can
have
dot
dot
and
show
like
five.
So
there's
like
so
many
variations
and
I
like
this
approach
that
we've
chosen
design
wise
to
take
the
most
non
grip,
the
most
rough,
the
most
course
designed
first
and
then,
as
people
expressed
I,
need
more
granular
control.
B
B
Next-Gen
for
design
I
put
this
all
together
as
a
parent
epic,
with
some
Sun,
epics
I
believe
yep.
This
is
something,
and
this
is
something
I'd
give
up.
We
just
sometimes
are
so
delayed
in
our
work
and
it
is
frustrating
so
these
are
designs
that
Pedro
put
together.
I,
don't
know
a
year
ago,
maybe
maybe
not
maybe
nine
months
ago,
but
they're
they're,
pretty
awesome
and
I
really
like
them,
and
so
especially
with
if
we're
making
boards
is
strong
Category.
This
is
this
is
where
we're
12.2
buddy,
so
one
of
them
is.
B
B
B
It
was
just
like
this
I
think
it
was
just
milestone,
but
it
was
something
similar
to
this,
where
it
was
just
for
a
milestone,
and
it
would
be
like
this.
It
would
be
like
a
lock
symbol,
and
so
you
can
see
how
for
milestone.
It
makes
sense,
because
you
only
have
one
Mouse
or
even
four
label
to
make
sense,
and
so
it's
locked
meaning
it's
not
it's
not
a
it's.
B
It's
configuration,
so
it's
associated
with
the
board
for
us
this
it's
associated
with
the
user,
so
you
can
see
it's
sort
of
pretty
slick
UI,
but
you
can
see
how
it's
also
confusing,
because
it's
not
the
same
concept,
because
one
is
filtering
and
one
is
associated
at
the
board.
So
so
the
current
design
and
the
decision
back
then,
was
to
do
it
as
such,
which
is,
you
know,
have
a
separate
modal,
and
then
we
talked
a
lot
about.
B
Do
we
even
need
to
show
this
here
and
then
the
final
decision
was
back
then
was
that
we
don't
need
to
show
it
like?
You
know
in
retrospect,
I,
don't
think
that
was
a
good
decision.
I
think
now
that
it
does
make
sense
to
show
it
back,
then
we
were
really
thinking
about.
Our
boards
are
being
used
by
team
workloads
like
agile
workflows
and
we're
really
limited
to
die.
B
So
it
was
like
moving
from
an
issue
from
from
in
dev
to
that
type
of
thing,
and
so,
if
you
think
about
that,
that's,
like
it's
a
plan
team,
and
why
do
you
even
care
to
look
at
that?
That's
silly,
but
then
boards
have
evolved
to
have
a
lot
more
usage,
for
example
like
when
we
were
thinking
about
this.
B
We
didn't
think
about
milestone
boards
or
assignee
boards
and
just
more
boards
in
general
and
so
I
think
now
it
does
make
sense
to
show
it,
and
so
that's
exactly
what
what
this
does
is
to
show
that
at
least
part
of
it
right.
We
can
just
see
it
here.
You
can
see
the
scoping,
so
I
think
that
would
be
great
change.
B
B
B
The
milestones
are
associated
with
the
board
right
now,
as
they
should
be,
but
you
can,
when
you
look
at
a
board
right
now
here
you
can't
change
the
milestone
if
there's
a
milestone
associated
with
it
right.
So
you
can.
You
can
click
here
and
add
a
milestone
but
like
if
I
choose
this
one,
for
example,
if
this
is
working
correctly,
it
shouldn't.
Let
me
choose
milestone
right,
so
you
see
I
can't
choose
a
milestone
here
because
it's
been
pre-selected
here.
So
so
that's
a
good
design,
because
it's
it's
it's
very
generic.
B
This
is
a
more
opinionated
design
which
says
that
you
should
be
able
to
change
the
mouse
tone
sort
of
on
the
fly
because
boards
are
associated
with
mouse
ones.
It's
really
from
an
agile
workflow
perspective,
and
but
you
should
still
have
a
default
one.
So
that's
this
video
right.
So
there's
the
default
milestone,
but
you
can
change
it
with
a
drop
down
really
quickly.
So
it's
not
associated
with
the
board
config,
but
it's
also
not
associated
I
guess
it
is,
but
it's
not
associated
with
this
search.
So
you
can.
B
You
can
do
both
okay,
so
this
is
the
type
of
thing
that
Pedro
was
at
a
lot
of
convinced
about
a
year
ago
but
a
year
ago,
and
so
that's
how
our
boards
are
evolving
or
the
design
has
evolved
a
lot.
This
was
also
inspired
by
JIRA,
really
refreshing
their
boards
again
over
half
a
year
ago
and
having
some
really
snazzy
design
and
coming
out
with
a
lot
of
these
things,
whether
it's
swim
lanes
and
so
forth,
and
so
that
really
needs
to
this
particular
design.
B
Where
you
can
see,
you
have
list
column,
lists
and
roll
labels
on
this,
so
just
lists
and
rows
or
columns
and
labels,
and
you
can
mix
and
matching
to
see
columns.
You
can
have
a
Chinese
and
Rose.
You
can't
labels
are
these
things,
so
there's
a
lot
more
detail
to
be
had
in
these
issues,
but
you
can
see
that
those
more
to
do
with
boards.
That
can
be
pretty
interesting
x-ray.
So
that's
that's.
What
should.
C
Be
just
going
on
in
the
future.
How
should
I
think
about
project
level,
boards
or
attributes
of
a
board
versus
filter
attributes,
a
user
of
a
given
board,
or
maybe
like
a
personal
board.
I
think
this
is
potentially
going
to
be
very
confusing.
I
think
it
already
is
a
little
bit
confusing
for
users,
but
I
think
moving
forward
I
think
you're
getting
at
the
heart
of
trying
to
fix
these
issues
right,
but
but
like
also,
if
we're
not
careful,
we're
just
gonna
make
it
even
more
confusing
yeah.
B
Couple
resources
that
I
think
this
will
help,
because
this
first
of
all
there's
a
little
bit
too
much
UI
here,
so
this
looks
scary.
But
yes,
what
Pedro
has
put
here
is
actually
less
confusing
because
it's
more
needed
it's
actually
less
flexible.
So
one
thing
he
wants
to
do
is
actually
get
rid
of
mixed
lists.
For
example,
I've
been
issue
for
that
somewhere.
B
So
let
me
go
back
to
a
board,
so
you
how
you
know
how
you
can
add
any
of
these
three
lists
once
you
get
rid
of
that,
so
that
would
definitely
help
I
have
some
epics
later
to
talk
about
templates
or
boards
and
board
types
as
well.
So
that
will
address
some
of
the
confusion,
because
you
just
have
a
board
and
it's
pre-configured
for
you
right
and
then
the
milestone
thing
again
is.
It
will
address
that
because
it's
one
less
thing
to
configure.
B
You
just
start
with
a
default
milestones
and
you
go
from
there
for
the
whether
it's
for
a
team
or
personal
use
case
and
so
on
so
forth.
Again.
This
should
help
you,
because
you'll
Dobby
types
of
mores
like
whether
it's
a
dsm
board,
whether
it's
a
a
workflow
board
that
is
based
on
scope,
labels
or
something
or
stages
in
the
future,
and
that
that
will
all
come
together.
B
So
in
terms
of
complexity,
the
only
additional
dimension
I
see
that
we
might
add
and
will
continue
to
take,
this
fall
of
complexity
is
swimlanes
because
you're
adding
a
different
dimension,
and
so
that's
obviously
a
level
of
complexity.
Other
places
for
complexity
that
we
could
be
adding
that
will
continue
to
take.
This,
you
expo
is
more
things
in
here
like
this
list
that
you're
able
to
filter
by
more
things.
B
So
one
of
them
that
we
want
to
do
is
buy
a
filter
by
project,
because,
if
you're
at
a
group
level
you'll
know
filter
by
project,
so
that
will
have
more
complexity
but
other
than
that
which
is
a
longer
but
I,
don't
think
we're
gonna
make
it
worse.
I
convincing
you
but
I,
don't
think
we're
gonna
make
it
worse,
because,
at
least
if
we
still
stick
with
group
or
attempt
Roger
we're
not
going
to
make
it
worst
in
terms
of
complexity
or
like
functionality,
we're
not
adding
more
functionality.
C
B
Yeah
well,
yeah,
and
and
also
because,
for
example,
he's
trying
to
indicate
like
you
can
assign
issues
to
two
people
here
or
boards
to
two
issues,
and
so
he's
trying
to
do
a
lot
here.
So
but
like
this
issue,
is
the
scoping
trying
to
scope
down
just
for
milestones
in
particular,
so
so
we're
definitely
not
gonna
build
everything,
not
even
like
Eastland
links
that
are
indicated,
but
this
is
just
reflecting
this
but
yeah,
so
so
that
that's
where
we're
headed
for
the
Fords.
B
D
B
B
So
this
is
exactly
what
what
what
it
is
right
so
not
like
this
right,
but
you
can
do
it
anywhere
and
get
like
there's
so
many
places
to
do
filtering
and
searching
to
that,
including
boards
and
stuff
like
that.
So
this
is
something
that
I
think
one.
We
need
to
be
very
careful
to
do.
This
is
a
bit
complicated
really
quickly.
It
can
become
gerrae
query,
language,
jaql
and.
B
A
B
B
B
So
these
your
two
logic
right
so
any
is
a
superset
of
none,
so
you
can
have
a
third
one
that
is
non
null
right,
so
so
you
can
have
potentially
somebody
crazy
could
look
like
not
milestone.
None
and
like
do
we
want
to
allow
that.
What
does
that
mean
like?
So
that's
like
really
messy
well,
but
we
have
these
to
start
off
with
right
now,
and
so
this
first
thing
like
my
side
yeah,
is
wrong
right.
So
for
most
of
these
right,
assignee
yet
remember
many
labels
as
well,
and
then
wait
I
think
so
it.
A
B
Okay
inherent
child,
so
this
is
once
we
have
those
we
already
have
child
epics
right
now.
I'm
sorry
hear
this
from
milestone.
Logic
uses
immediate
children's
issues
only
but
no
be
really
school.
Really,
it's
just
inherits
going
downwards
yep
and
if
you
just
sort
of
think
about
it
for
five
minutes,
the
best
way
to
do
it
is
just
to
look
always
look
at
your
immediate
children
and
don't
try
to
be
fancy
and
do
recursive
yeah.
B
I
mean
there's
not
there's
clearly
not
a
lot
of
usage
with
these
things,
so
I
haven't
seen
what
an
argument
either
way
yeah,
but
it
by
default.
Right
now,
when
you
create
a
new
issue,
a
new
ethic,
it's
going
it's
doing
the
autumn
inherently.
So
maybe
that
is
true
from
what
you
said.
So
if
you
just
let
it
be,
it
will
just
do
that
here.
Insists
on
mattress,
so
there's
the
default
cases
that
one
so
I
think
that's
a
difficult.
B
Real-Time
board
lists,
so
real-time
has
always
been
a
thing
at
good
lab
like
it
seems
like
every
couple
months.
Somebody
says:
let's
make
everything
in
kill
that
real-time
admitting
a
meta
issue
or
an
epoch
to
do
that,
and
you
know,
obviously
it's
a
lot
harder
than
that.
So
there's
to
my
knowledge,
there
hasn't
been
any
concerted
effort
to
do
something
like
that
and
to
my
knowledge,
it's
fairly
difficult
right
now
that
I've
stopped
asking
engineering
so
to
say
like
every
time
you
create
a
new
feature
just
make
it
real.
C
B
B
Them,
and
so
so,
this
is
less
about
updating
the
contents
of
the
issue
even
inside
that
I
see
an
issue
card
because
that
will
probably
not
be
real
time
required
that
much,
but
the
fact
that
issues
are
moving
around
in
the
court.
That
will
actually
be
more
interesting.
That's
what
this
is.
So
that's
why
I
call
great
time
for
this
yeah.
C
B
Again,
it's
not
a
great
experience,
because
sometimes
when
you
do
a
quick
action
and
when
you
do
a
quick
action,
it
doesn't
update
it,
but
when
you
make
an
action
in
the
sidebar
directly,
obviously
updates
it,
because
it's
you're
interacting
with
the
front
end,
do
I.
So
there's
a
lot
of
inconsistencies.
B
There
I
pushed
for
the
UX
team
to
have
some
good
like
guidelines
in
play,
but
in
the
design
system,
I,
don't
think
it's
very
complete
or
I
might
be
wrong,
but
I
getting
very
picky
from
from
things
like
when
you
change
go
from
here
to
here.
You
see
that
spinner
there
and
they're
like
yeah.
This
is
do
a
sync:
does
it
do
it
after
and
so
on
and
so
forth,
things
of
blocking,
and
so
there's
just
a
lot
of
stuff
they're
more
powerful
issue
boards?
B
B
B
B
A
B
Able
to
drag
like
three
things
and
move
them
over
all
at
once,
so
pretty
cool
unlock.
These
came
from
like
every
now
and
then
there
will
be
a
big
announcement
saying
like
Lassie
about
Trello,
and
then
everybody
I
feel
that
has
used
Gerry
on
our
Trello
and
that
everybody
will
say
like
we
should
have
all
these
amazing
features
we'll
fill
out.
So
a
lot
of
these.
B
There
so
so
so
that
context
there.
This
is
what
I
talked
about
earlier
with
the
filter,
I
think
so
filtered
by
the
project
on
this
will
be
super
helpful,
because
I
was
looking
at
the
release
post
today
and
then
what
I
see
is
that
when
you
do
this
and
get
that
you
can
add
projects
right,
you
can
add
Enterprise
Edition,
which
I
think
I
think
is
pretty
awesome.
B
Yes,
I
think
this
is
like
customized
to
me
and
then
so
I'm
not
subject
to
a
group,
and
this
is
super
flexible
and
they
take
our
lists
like
across
the
new
feature.
These
will
have
been
a
nice
project,
I
like
so
so.
None
of
the
plan
features
out
any
of
this
right
now
and
so
we're
struggling
because
we
a
lot
of
customers
need
this.
Where
you
need
a
project
here,
I
mean
the
group
there,
but
they
don't
want
them
under
the
sink,
because
it's
really
messy
and
I
think
that's
a
that's.
A
reasonable
request.
B
I
understand
why
the
the
people,
the
Kings,
designed
this
feature,
didn't
shove
this
inside
of
group,
or
maybe
it's
already
a
new
group,
but
have
it
like
at
the
instance
level
I
mean
for
just
because
just
add
whatever
projects
you
care
about
so
before
we
get
to
that.
What
can
we
do
that
eases
the
pain
in
the
spirit
of
collab,
a
small
primitive
as
it
were,
and
to
do
that
is
again.
A
B
So
this
is
quality
management,
so
there's
not
much
here
to
say
other
than
that.
There's
a
community
member
that
is
sort
of
working
on
it
so
dropping
in
and
out
every
like
one
week
or
two
I'm
saying
that
they're
working
on
it,
they
did
last
ping
me
this
Monday,
I,
guess
and
I
responded.
So
so
there
is
a
little
bit
of
pickup
for
this
one,
but
I
think
we
agree.
B
C
B
D
B
B
Multiple
losses
per
issue
or
merger
class
I
thought
I've
spoken
to
you
about
this,
adjusting
the
issue
that
a
milestone
can
represent
a
sprint
and
the
point-in-time
release
so
on
and
so
forth.
Maybe
there's
some
integration
with
the
release
object
that
was
invented
or
releases
ago,
but
for
now
I
think
this
is
a
good
change
on
itself.
It
stops
the
bleeding
I.
Think
it's
creation.
B
This
one
is
about
blocking
issues
and
sub
issues
so
blocking
issues
of
my
parent
child
issues.
I,
don't
even
think
I
have
mock-ups
for
any
of
this
yeah
I
don't,
but
it's
exactly
what
it.
What
do
you
think
it
is
so
depending
dependency
issues
and
then
Parent
Child
issues
are
exactly
the
same
concept
as
as
child
abuse.
So
I
think
that
would
be
a
welcome
change,
especially
for
key
levers
who
care
about
front-end
I
can
yeah
things
are
different,
more
real-time.
D
B
B
B
B
So
you
technically
don't
need
both,
but
it's
great
to
have
both
this
one
puts
in
a
new
board.
We
actually
really
literally
happen
every
iterated
on
burn
down
charts
since
I'm
joined
your
lab
I
think
we
put
them
on.
No
no
I
was
here
when
we
invented
them,
that's
it
and
we
put
them
in
project
milestones
and
then
good
Mouse
ones,
and
that's
it.
We
haven't
gotten
better,
so
I
think
it's
a
much
neat.
Weird.
No
choice
is
one
of
those
things.
B
That
is
it's
it's
like,
along
with
those
statistics,
things
like
metric
things
right,
so
you
could
argue
that
if
we
have
a
better
vision
for
PSMA
in
charge,
the
psycho
analytics
it
really
should
be
grouped
into
there.
I
think
because
then,
like
burn
down,
charts
are
just
like
team,
workflows
and
agile
and
stuff
like
that,
but
like
the
future
is
really
easy,
like
burn
down,
charts
I've
been
here
since
the
beginning
of
humankind,
but
I'm
agile,
but
the
future
is
really
about
DSM
in
psychoanalytic.
So
how
does
that
fit
into
that?
B
Recommend
that
game
they
think
of
that
together.
Okay,
this
one
is
pretty
obvious.
It's
something
that
we
just
avoided
doing,
because
we
don't
want
to
add
too
much
crap
to
this
area
here,
but
there's
you
know,
people
will
ask
for
it.
Surprisingly,
not
a
lot.
So
that's
that's.
Why
I
wouldn't
super
action
on
and
sort
of
like
waiting
the
man
type
of
thing,
because
we've
had
related
issues
and
relating
with
us
forever
and
you
notice.
Nobody
really
asked
I
want
to
see
all
your
labels
here.
So
so
to
me,
that's
that's
an
indicator.
B
Oh
I'm,
sorry
label
order,
they're
ordered
we
talked
about
this
I
think
was
it
yesterday.
It
was
it
no,
no,
no,
it
might
have
been
a
while
ago,
but
to
me
she
just
got
annoyed
and
just
implemented
a
I.
Think,
that's
I
think
that's
what
he
just
did.
This
is
like
about
two
months
ago.
All
labels
are
ordered
everywhere
now,
I'm
pretty
sure
so
they're
in
capita,
like
whatever,
like
so
bag
of
those
fancy
words
right.
C
B
C
B
B
B
B
C
I
think
I
think
road
maps
is
something
I'd
like
to
revisit.
If
we
have
time
in
this
is
our
trick,
but
yeah
I
mean
it
just.
It
was
just
a
thought,
because
you,
you
could
theoretically
have
a
use
case
where
someone
someone
is
saying:
okay,
I
always
want
this
label
at
the
top,
and
actually
now
that
I'm
thinking
about
it.
The
another
logical
question
is:
what
is
the
so,
when
we
launch
scope
labels
next
in
the
next
release,
how
will
scope
labels
be
sorted?
B
Or
the
value,
so
there
will
be
interwoven
because,
because
scope
labels,
it's
there's
literally
no
logic
from
my
understanding
that,
like
marks
them
as
such,
and
so
when
from
the
distorting
algorithm
perspective,
it's
just
the
title
right.
So
it's
I
don't
know
how
colon
is
in
the
lexicographic
orbit,
but
it's
just
yeah,
like
you
see
here
right
so
like
C
comes
before
G.
So
therefore
it's
like
this
and
that's
it
yeah.
B
Exactly
that
the
logic
is
applied,
the
exclusivity
is
applied
when
you
apply
the
label,
that's
that's
when
the
logic
is
consider,
and
so
when
we
ship
this,
like
it's
not
shipped
yet
right.
So
potentially,
if
I
take
this
epoch
and
put
category
issue
force
category
for
project
management
when
it
has
ship
it,
nothing
will
happen
to
that
right
now,
like
both
labels
will
still
be
there
at
the
moment.
I
add
another
category
called
:
label
you'll
remove
the
first
two.
So
we
purposely
did
that
because,
like
my
greatest
vacation,
yeah.
B
That
I
mean
that's
one
of
the
reasons
we
pick
double
call
it
so
that
we
don't
mess
that
up.
I
I
created
these
labels.
So
that's
why
I
know
what
I'm
doing
and
so
I
actually
see
some
people
using
double
pulling
them
on
purpose.
But
we
purposely
picked
double
:
because
we
looked
at
the
database
and
there
was
not
allowed
collab
Comcast
was
using
a
single
:
and
none
of
us
were
using
double
and
we
were
using
single
:.
Sorry,
don't
it
was
some
people
using
single
:,
but
very
little
people
using
double
:
and.
C
A
B
That's
that's,
okay.
This
one
is
interesting,
so
that's
labels.
This
one
is
interesting.
It's
one
of
those
annoying
tech
that
I
really
hate
it.
It's
nobody's
complaining
about
it,
but
it'll
be
great
to
get
fixed
ones.
I
don't
want
to
spend
too
much
time
on
it
because
again
it's
I,
don't
think
it's
high
priority,
but
basically
it
beers
its
head.
B
What
else
do
I
want
to
say
about
this?
I?
Don't
yeah
I,
don't
want
to
get
too
deep
into
this,
but
basically
again
here
ability
to
invite
users
to
a
confidential
issue.
So
so
what
Demetria
and
Sean
wanted
to
do
was
like
create
a
brand
new
feature
to
do
that
and
I'm
like
no,
no,
no,
no
I,
don't
I
want
to
support
like
a
feature
just
to
do
this
again.
This
is
like
a
really
edge
case,
but
there
are
some
times
which
this
needs
to
happen.
B
Probably
security
scenarios
I
guess,
but
if
I
have
my
design
here,
which
you
know
Sean
and
Alicia
do
agree
with,
then
you
don't
have
to
worry
about
this.
It's
that
the
concept
is
that
you
can
assign
anybody
to
any
issue,
even
though
they're
there
Joe
Schmoe,
and
they
don't
belong
to
the
project,
but
the
moment
that
they're
assigned
they
can
see
everything
in
the
issue.
So
you
have
that.
C
C
B
C
Know,
but
you
know
what's
a
teaching
about
this.
One,
though,
is
like
this
concept
of
you
know,
least
privileged
access
and
in
our
permissions,
are
very
a
very
coarse-grained
right,
and
so
you
know,
theoretically,
like
you
should
be
given
the
least
amount
of
access
possible
and
and
now
we
are
very
open
and
transparent
company,
but
many
other
companies
going
through
digital
transformation,
not
like
us
right
and
so
I
could
see
this
as
like
an
incredibly
valid
use
case,
especially
for
very
tighten
down
organizations.
C
That
would
want
to
only
give
someone
access
to
a
particular
issue
that
they
don't
need
to
know
anything
else
about
the
project,
just
a
single
issue,
and
then
maybe
maybe
when
their
piece
is
done
like
given
that
issue
like
they're
they're,
essentially
kicked
out.
It
could
be
to
me
that's
a
like
the
most
logical
use
case
of
the
feature,
but
obviously
would
a
person,
some
user
validation
right.
B
So
if
I
can't
find
out
in
20
seconds,
I
will
give
up
and
do
it
offline
and
I
can't
find
it
so
later,
but
the
person
is
security
said
they
wanted
the
ability
just
to
do
exactly
what
she's
just
said
just
created
an
issue
and
by
default
nobody
can
see
it
at
all,
except
for
themselves
and
then
just
whitelist
people
who
can
see
that
issue
then
white
light
listing
an
issue
is
interesting.
Yeah.
C
B
B
To-Do
list,
no,
no
I,
don't
think
it
was
that
I
think
it
was
they
just
like
working
and
some
security
workflow.
That
inside
this
is
like
the
red
team
which
I
googled,
that
they
attacked
us
on
purpose
and
then
there's
a
yeah,
so
I
guess
they're
doing
some
really
fun
things
to
hack
the
lab
and
then
maybe
they
need
a
workflow
to
I.
Guess
it
makes
sense.
B
They
don't
want
to
share
that,
obviously
with
everybody
yeah,
so
so
that
that's
there
was
a
shoe
that
flew
by
my
way,
requesting
that
and
then
maybe
super
related
to
this.
If
we
do
it
correctly,
okay,
so
that's
interesting!
Thank
you!
Thank
you.
So
that's
this
one.
That's
pretty
exciting.
Just
from
a
technical
but
like
not
begin
that
subversion
bulkheaded
improvements
again
something
sort
of
long-tailed
kill
that
that
we
should
do
but
just
hasn't
been
done.
B
Bulkhead.
It
exists
or
issue
lists.
Its
semi
ok
experienced
in
my
opinion,
but
it
doesn't
exist
for
the
coolest.
So
this
is
the
group,
and
so
you
can
see
it.
Have
you
ever
even
used
this
feature?
I'm,
not
sure
I,
know
that's
a
problem,
but
you
can
do
this
right.
You
can
select
multiple
of
these
and
then
I
change
labels
all
at
once
to
prepare.
So
people
want
this
for
the
of
course.
B
B
A
C
B
B
B
So
yeah
so
calendar
showing
the
shoes
on
issue
due
dates.
So
just
like
this
cool
avenues
showing
issues
there,
so
I've
always
been
like.
Oh,
why
reinventing
Google
Calendar,
that's
really
silly!
So
they're
a
marketing
has
been
asking
for
something
similar
like
this,
and
then
I
told
you
that
we're
able
to
solve
some
of
their
problems
using
the
clone
issue
and
clone
ethnic
functionality
yeah,
because
your
call
I
said
like
marketing
events
and
lend
us
if
this
would
work
for
them.
Another
interesting
thing
is
professional
services
that
get
lab.
B
They
apparently
I
did
not
know
this,
so
they
apparently
need
to
use
time
tracking.
So
that's
great
I
didn't
even
know
like
anybody
uses.
I
can
I
use
this
time.
Yeah
I,
don't
think
they're
using
it.
I
think
on
might
be
making
the
music
now
I
think
that's
like
what
I've
saw
edition
description,
which
is
pretty
funny,
but
basically
what
they
do.
Is
they
build
customers,
apparently
by
the
hour
or
whatever
and
per
project,
and
so
they
can
I
created
some
issues
for
them.
B
C
D
C
Know
you
could
have
like
the
exact
view
of
okay?
What's
my
PS
team
focusing
on
this
month
in
this
quarter,
and
then
you
could
even
drill
into
like
a
specific
project
that
has
you
know
individual
due
dates,
so
I
think
there
is
a
lot
of
value
for
that
use
case.
There's
probably
not
a
ton
of
value,
for
you
know,
get
lab
releases
because
everything
is
due
on
the
same
day
every
month.
So
right.
B
C
A
B
Your
alright
yeah,
it's
again
like
when,
when
do
we
put
this
in
the
the
laundry
list
of
things
we
want
to
do
so,
yeah
there's
a
lot
as
you
can
see.
There's
a
lot
here
extended
book
manage.
Oh,
this
is
really
crazy
as
a
feature,
this
is
really
straightforward
and
this
was
created
like
ten
years
ago,
three
years
ago,
say:
yeah,
I'm,
right,
I,
know
other
issues
that
were
created
four
years
ago,
and
this
is
one
of
them.
B
B
Engineering
folks
have
said
this
is
really
difficult
to
do.
For
these
reasons,
and
we
said
we
still
want
it
and
then
the
engineer
Dempsey
says
okay.
This
is
how
we
need
to
do
it
correctly.
If
we
were
to
do
it.
Okay,
it's
like
you,
see
the
words
migraine.
It's
probably
not
a
good
thing
right,
like
you
need
to
do
like
a
lot
of
back-end
changes,
yeah,
so.
B
Exactly
exactly
to
support
ice
at
scale
that
yeah
I
think
it
was
something
about
like
when
you
can't
surface
all
that
information
like
on
a
view
because
you're
querying
all
the
issues
on
at
all,
that's
the
same
timer
school,
which
is
crazy,
yeah,
okay,
but
yeah,
it's
something
that
I
can
get
off
shift
not
too
long
ago.
So
it's
come
up.
It's
one
of
those
things
they
go.
B
D
B
Know,
James
I,
don't
know
if
these
were
falling,
be
sure
you
were
here
when
James
was
doing
that
he
did
a
lot
of
description
there,
just
a
lot
of
templating
stuff
in
groups
and
projects
and
all
that
stuff.
So
this
is
would
be
following
in
those
footsteps
and
bringing
the
description
template
things
in
line
with
all
the
design
that
that
James
had
I
think
James
used
for,
like
a
group
level
of
description
template.
He
specified
like
this
project
serves
as
the
group's
version,
and
so
this
would
serve
directly
the
same
thing,
which
is
beautiful.
B
B
Default
description
templates
think
is
an
easy-chair
I
forget
what
anyways.
As
you
know,
description
templates
are
source
controlled
right
there
in
the
dot,
collab
file,
right
or
because
I
believe
the
default
like
when
you
first
create
a
new
issue.
You
see
something
there
that
thing
there.
That's
actually
not
source
window,
that's
actually
stored
in
the
database,
which
is
crazy
right
and
then
this,
like
the
symmetry,
has
been
in
gillip
forever
like
this
is
like
it's
8
point,
something
or
instance:
it's
really
crazy
that
that's
efficient,
and
so
this
just
makes
it
carbonized.
A
B
To
do
if
you're,
like
into
migration
and
communicating
with
customers
like
funding
there,
I'm
not
being
cynical
like
it's
just
fun
when
I
was
just
working
through
this,
like
it's
just
a
shame
again
going
back
to
whatever,
but
it's
a
shame
that
I
couldn't
execute
on
this,
because
it's
just
so
fun
like
to
know
I
you
have
to
you
know,
get
ready.
You
have
to
talk
to
people
in
the
product,
then
you
have
to
migrate
things
over
and
then
you
have
to
disable
something
and
talk
to
them
and
then
I
finally
cleaned
it
up.
B
So
this
is
something
that
would
be
just
fun
to
do,
and
it's
really
I
don't
know
it's
just
it's
just
fun
to
clean
up,
sometimes
like
clean
up
like
you're,
really
a
dirty
house
or
scheming,
and
that
one
is
just
just
gives
me
those
good
good
feelings.
I,
don't
know
why
that
one
specific
issue,
page
functionality,
there's
always
more-
you
can
do
in
an
issue
page.
So
that's
why
these
are
getting
subtopics
this
one.
Everybody
wants
tract
issue
like
source,
controlling
it
or
version
control,
at
least
pending
a
comment
of
these
boats.
Confidential
comments.
C
C
A
C
I
think
you
could
implement
moderators,
like
with
the
existing
programs
that
we
already
have,
but
it's
not
necessarily
a
first-class
citizen
right
because,
like
the
moderator,
went
and
deleted,
a
comment
like
you'd
probably
want
a,
but
you
wouldn't
just
want
that
to
disappear
off
of
the
thread.
You.
B
D
D
A
B
That
thinking
like
when
think
Roger,
oh
I,
don't
know
in
for
notes
from
the
color,
is
on
our
security
team.
Doing
I,
don't
know
what
his
title
is,
but,
like
he's
just
make
sure
like
there's
no
spam
and
stuff
at
syllabus
and
with
him
awhile
back
made
happier
back
and
just
understanding
of
how
we
do
moderation,
a
good
lab
because,
like
he
was
the
first
person
that
really
was
thinking
about
this
Kathy
hired
and
is
really
like.
B
The
subreddit
analogy
is
just
is
just
reused
groups
and
so
the
all
those
issues
that
we
were
supposed
to
build
for
him
that
we
have.
It
is
just
making
moderation
tools
better,
but
putting
them
all
at
the
group
level
so
that
you
can
do
all
your
martyr
II,
like
the
group
admin
has
all
that
you
know,
and
so
I
think
what's
missing
is
exactly
that.
B
You
said
that
you
can
go
in
and
delete
a
comment,
but
it's
it's
not
granular
enough
right,
so
you
can't
give
them
three
strikes
type
of
thing
that
you
can't
say
that
information
easily.
You
can't
I
think
there
was
like
banning
a
user
but
was
right,
I,
limit
and
stuff
like,
but
yeah.
We
went
through
that
exercise
of
identifying
all
those
features.
Even
before
that
person
join
I
mean
there
was
a
veneer
that
was
really
passionate
about
those
things,
and
this
came
up
when
we
created
service
desk,
which
is
pretty
interesting,
because
when
we
created.
B
I,
don't
think
it's
been
realized.
Well,
maybe
because
we
don't
have
a
lot
of
usage
about
now.
Anybody
can
create
an
issue
because
you
can
abused
that
email
address
right
and
there
you're
opening
spam
to
everybody
in
the
world.
So
in
that
context
a
lot
of
moderation.
Things
came
up,
but
again
that's
a
laundry
list
at
issue
somewhere
hit.
B
B
B
B
So
you
know
what
let's
see
give
me
two
seconds.
Let
me
let
me
use
three
minutes
to
go
through
the
rest
and
come
back
to
unify
to
using
a
position.
Okay,
so
yeah,
because
the
rest
are
pretty
small
filter
by
created.
Yes,
that's
exactly
what
it
is
community
resolve
ability,
as
I
mentioned
earlier,
so
that
the
merger
does
have
them
in
issues
in
that
face
alone
and
somewhere
phone.
We
talked
about
that
BSN.
We
talked
about
that
and.
D
B
Was
here
this
one
is
just
having
more
charts
throughout
gitlab.
We
have
this
thing
and
get
laughs
that
we
should
one
version
of,
and
we
haven't
really
done
anything
which
is
terrible.
We
have
this
and
the
thinking
is
we
want
more,
but
this
wasn't.
The
division
here
is
not
very
good
because
it's
not
in
line
with
VSM,
and
then
we
have
now
collab
insights
from
Maxime
being
thrown
in
to
get
out
so
there's
a
lot
of
good
stuff
in
the
pipeline.
But
it's
not
positioned
well
together,
everybody
that
would
need
to
be
fixed.
B
B
B
B
Yeah,
no,
no
definitely
so
it's
just
Jesus
like
there's
some
tech
dot,
as
you
can
see
here,
there's
making
it
like
when
you
do
this,
this
is
sort
of
really
not
correctly
at
some
of
this
there's
no
tabs.
Well,
if
you
look
at
slack
we're
just
copying
slack
for
these
things,
and
just
before
we
make
custom,
emoji
is
essentially
just
making
sure
this
experiences.
Okay,
okay,
cool,
make
sense
so
onto
this
crazy
idea.
I
had
like
maybe
eight
months
ago.
Now,
it's
really
good
I,
really
like
it.
I've
went
through
a
couple
of
iterations
artist.
B
I
shared
this
with
Jeremy
he's
is
on
board,
but
the
concept,
maybe
not
the
exact
I'm.
It's
still
lacking
a
lot
of
implementation
details.
The
reason
I
went
to
Jeremy
is
because
he's
managed
and
he's
doing
activity
thread
stuff
and
then
there's
a
lot
of
overlap.
Who's
who
think
to
do
is
notifications
to
be
thread
matei,
whose
designer
unmanageably
had
a
lot
of
great
concepts.
Here,
too,
you
work
on
a
little
bit
and
I
just
love
this
concept,
I,
don't
I,
don't
love
the
concept.
B
B
Of
the
application,
I
think
that's
a
huge,
huge
thing
where
our
issue
management
adoption
is
not
as
high
as
us.
Obviously,
in
the
lava
request,
I
think
a
lot
of
them
are
people
are,
are
using
a
notification
sort
of
out
of
the
box,
and
it's
good
in
our
but
I
I'm,
pretty
certain
that
again,
we
don't
have
data
to
back
this
up.
Increasing
our
customers
are
just
not
using
to
dues.
B
D
B
B
Always
a
good
a
person
I
do
this
certain
way
and
I
want
this,
and
so
we
started
suspended
and
said,
like,
oh
we'll,
add
more
this
or
more
of
this,
so
the
the
way
I
think
about
to
dues
and
applications.
It's
it's
a
mess
because
there
is
I,
don't
think
anybody
would
dispute
what
my
claim
that
there
is
a
lot
of
overlapping
functionality
between
to
do
simplifications,
I,
think
where
the
argument
is
to
be
had
is
conceptually,
are
they
the
same?
Can
they
be
merged?
Should
we
purposely
keep
them
separate?
How
should
they
you.
A
B
B
So
there's
a
couple
of
ways
that
people
have
wanted
to
address
this.
One
of
them
is
they
want
to
just
ran
more
and
more
notifications,
and
if
you
go
to
here,
this
is
really
messy
and
if
you
were
not
to
overhaul
the
system
which
essentially
proposing
you
could
do
a
pretty
good
job
of
cleaning.
This
up
like
this
is
just
terrible
UI.
It's
really
confusing
it's
repetitive,
because
you
can
go
to
the
group
to
toggle
this
and
you
can
toggle
on
here,
and
this
is
not
like
this
is
just
not.
B
B
B
B
So
again,
there's
consistency
there
and
then
what
you
do
is
you
can
pin
these
or
mark
them,
as
done
so
similar
like
the
inbox
or
Gmail,
and
that
would
be
analogous
to
when
you
click
Add,
to
do
here,
you're
generating
a
to-do,
that's
similar
to
this
you're,
generating
a
to
do
on
a
particular
issue.
But
you
know
you
whether
all
notifications
are
to
do
so.
So
my
great
idea
is
just
essentially
just
merge.
B
Two
views
and
their
vacations
have
one
stream
of
these
objects,
and
then
you
manage
them
as
such
and
then
so
the
implementation
detail
would
be
whether
you
can
archive
them,
whether
you
delete
them,
whether
you
mark
them
as
done
or
undone
whatever
language
you
want
to
do.
But
my
great
innovation
is
that
there
should
just
be
one
stream
of
information
and
not
two
separate
streams
of
information.
A
lot
of
people
have
argued
one
way
or
another
people
have
said
like.
Is
this
like
a
mobile
app?
Is
this
like
twitter?
Facebook?
Notifications?
Not
really.
B
C
My
on-the-fly
feedback
is,
you
know,
for
for
you
and
I
like
strong
users,
and
proponents
of
like
the
inbox,
like
I,
think
I
would
personally
like
love
this
right.
Like
you
know,
you
and
I
are
our
archivers
as
soon
as
we
see
something
we
don't
ever
want
to.
We
always
want
to
get
to
inbox
zero,
where
you
archiving
something
immediately
or
an
inbox
speak
like
marking
it
done
or
snoozing
it
or
painting
it
exactly
so
should
that
make
sense,
I
think
the
biggest
reason
I
don't
use
to
douzo.
C
C
I
can't
share
my
screen.
It's
gray
is
because
like
when
it
says
some
hey
someone
mentioned
you
on
this
and
it
says:
hey
someone
mention
you
on
merge
requests
to
one
three,
five,
four,
seven
I'm
just
like
I,
don't
know
what
that
is.
I
would
much
rather
say
like
hey
someone
so-and-so
mention
you
on
merge
request.
C
You
know,
add
Eric
to
team
yeah,
yeah
and
then
I
have
the
context
for
like
what
that
to
do
is
and
then
I
can
quickly
like
peruse
the
list
and
say:
okay
I
need
to
focus
on
this
one
now
or
that
one
at
this
point
how
it's,
how
it
is
today,
like
I,
can't
even
do
like
a
cursory
prioritization
to
see
what
like,
what's
most
important,
so
I,
don't
know.
If
we
talked
about
that,
I
mean
it's
not
they
addressed.
You
on.
B
C
Never
would
might
be
a
change
right
there.
They
kind
of
give
me
to
potentially
use
it
but
yeah
as
of
right
now,
I,
don't
use
the
news
at
all,
so
I
think
any
any
change.
It's
like
drawing
a
musical
analogy
right
if
you're,
if
you're
playing
in
an
instrument-
and
you
know
you're
out
of
tune
like
the
worst
thing
you
can
do,
there's
like
not
touch
your
cheating
side
like,
if
you
don't
know,
you're,
sharp
or
flat.
That's
okay,
just
pull
it
or
push
it,
and
then,
if
it
gets
worse,
start
going
the
other
direction.
B
So
I'll
share
with
you
one
thing
and
I
think
we're
making
good
time
so
yeah
I'm
pretty
much
done
so
the
main
reason
to
reach
out
to
Gerry,
because
I
noticed
that
he
was
doing
a
lot
of
good
changes
to
here.
So
this
is
actually
pretty
than
you
like.
This
view
is,
or
this
style
is
pretty
new,
look
at
Chris
I
like
it
and
so
they've
been
doing
a
lot
of.
B
Their
doing
they've
been
doing
this
things,
and
it's
the
opportunity
I
saw
here
is
that
these
events
are
the
same
as
these
events
here
as
the
same
events
in
my
email
as
the
same
events
in
a
common
thread
inside
this
issue.
So
there's
four
places
where
information
is
duplicated,
so
that
that's
where
I
saw
like
a
big
opportunity
to
to
to
to
do
some
innovation
and
clean
up
I
think
your
lab
is
really
bad
at
that,
like
it's
really
not
in
our
DNA,
so
that
we
can
address
a
link
baked
like
that,
we
can.
B
We
can
make
some
big
plans
and
inch
towards
that,
but
I
don't
think
we
have
the
wherewithal
to
actually
do
something
big
like
that,
so
I
wouldn't
even
like.
If
I
were
to
do
this,
I
wouldn't
even
claim
to
do
that.
I
would
only
want
to
merge
two
of
those
four
things
I
mentioned,
which
is
like
to
dues
and
notifications,
which
is
which
would
make
sense
because
they're
both
quite
plain,
but
ideally
it
would
even
like
it
would
even
be
the
same
event
object.
B
C
Here's
an
interesting
thought
which
would
be
what
would
it
take
for
us
to
develop
a
system
whether
we
call
that
a
unified
notification
to
do
system
or
just
a
new
like
message
center
and
get
lab
to
prevent
anyone?
I
get
lab
any
employee
get
lab
from
ever
having
to
login
to
Gmail,
except
for
the
odd
case
where
you
have
that
random
email
thread
with
someone.
B
A
C
Right
this
is
this
is
super
helpful
yeah.
This
is
great,
so
I
wanted
to
kind
of
come
up
a
little
bit
from
the
from
the
weeds.
So
to
speak,
because
this
is
this
is
great.
Obviously,
we've
got
things
scheduled
in
the
2021,
which
is
which
is
awesome,
but
if
you
can
push
pause
Sheryl
on
anything
I'm,
sorry
on
everything
that
we're
doing.
If
you
push
pause
on
everything
that
we're
doing
for
plan-
and
you
don't
have
to
worry
about
technical
death
or
scheduling
bugs
or
security,
what
is
the
next
thing
that
that
you're
working
on.
D
D
B
Lab
spirit,
mr.
bored's
is
good
in
the
issues
before
management
is
not
giving
up,
but
like
that.
This
is
good
enough
for
project
management,
so
you
have
other
tools
that
have
epochs
of
user
stories
or
whatever.
So
that's
good
enough,
so
what's
missing
is
portfolio
management,
so
so
that's
a
new
area,
so
I
would
do
that
and
work
on.
B
That
would
be
one
area,
I
would
work
on
do
be.
A
couple
of
alyssum
would
be
performing
management,
but
it
would
be
like
our
ROI
analysis.
It
would
be
like
finances
and
stuff
like
that,
where
it's
not
worth
quick
down,
structure
which
all
the
like
other
stuff,
like
really
corporates.
You
know
people
business
suit
stuff.
That
aspect
is
for
collaboration
without
be
number
one.
Another
one
would
be
some
going
after
Zendesk
or
salesforce,
so
either
service
this
or
give
that.
D
B
B
B
B
It
like
in
good
lab
it
would
maybe
like
we
inventing
the
wiki
and
then
combining
it
with
a
workflow
or
maybe
making
Google
Docs
really
awesome,
so
that
collaboration
was
as
possible.
I
don't
know,
but
that
would
be
my
third
area
where
it's
really
really
that
that
would
be
the
riskiest
one
like
just
trying
to
reinvent
collaboration
and
I.
Think
that
is
a
pretty
pretty
interesting
space
where
it's
not
a
description
and
then
a
comment
thread
underneath
is
that
model
is
pretty
good,
I
mean
I'm.
Sure
a
lot
of
companies
have
had
amazing
exit.
C
B
B
But
my
contention
is
that
a
lot
of
people
are
experimenting
with
different
things.
So
why
is
that?
The
case
is
that
there
is,
if
there's,
companies
that
are
surviving
experimenting.
That
means
there
is
a
need
for
it,
and
so
again,
like
this
video
right.
Is
it
really
the
video
aspect
or
is
it
merging
the
two
or
is
it?
Is
a
mortgage
starting
from
chat
instead
of
a
more
evergreen
object,
such
as
an
issue?
So
that's
not
clear
to
me
what
that
is
or
I,
don't
think
anybody
is
cleared,
that's
why
people
are
experimenting.