►
From YouTube: Plan stage weekly - 2022-10-06
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
Cool
all
right,
welcome
plan
stage,
weekly
October
6
2022.
This
is
our
Apec
hours.
One
I've
got
a
few
things
on
the
agenda
from
Lori.
You
want
to
go
ahead
and
start
your
demos
for.
B
B
A
A
It
cutting
out
for
everyone
yeah.
We
got
like
every
every
four
words
there,
Glory.
A
I
see
the
I
see
your
screen
perfectly
fine
I
think.
D
I
can
mobilize
the
future
in
case
of
flurry
once
because
I
I
can
see
that
her
frame
is
frozen
so
yeah.
So
this
feature
is
basically
replicating
what
we
had
with
the
issue
boards,
where,
if
an
issue
is
blocked
by
a
couple
of
issues,
then
we
show
an
icon
within
the
issue
card
and
when
you
hover
over
the
icon,
it
would
show
a
pop
over
and
show
list
of
all
the
blocking
issues.
D
So
we
are
basically
so
we
added
this
feature
for
epic
boards
a
couple
of
updates
ago,
and
now
we
are
bringing
that
feature
to
roadmap
as
well.
So
that's
basically
the
whole
thing.
B
And
we
also
have
the
Annie
and
none
this
is
like.
We
are
like
the
next
step
will
be
to
surface
the
exact
same
filter
token,
to
more
issue
boards
as
well
and
like
so
on,
like
everywhere,
we
need
it,
we'll
also
be
able
to
edit
the
health
status
from
the
issue.
Roadside
Bar
at
some
point,
that
kind
of
stuff,
so
we're
just
trying
to
surface
health
status
where
we
think
it
would
be
useful
for
us.
E
A
Awesome
and
then,
as
part
of
issue
boards,
are
we
planning
on
making
filterable
or
issue
lists
from
status
or
just
adding
it
to
the
filter
bar.
A
I
wonder
if
there's
a
plan
to
add
it
to
to
to
list
or
had
the
option
for
status
list.
C
B
Have
any
questions
posted
in
the
chat
or
the
agenda
and
I'll
just
answer
in
writing?
Cool.
F
A
Think
so,
right
now
it's
a
separate,
separate,
UI
I.
Think
there's
a
just
a
button
on
the
top
of
the
editor
that
gives.
F
Yeah,
there's
like
a
tab
right,
a
source
View
and
what
you
call
this
yeah.
A
I
think,
as
of
now,
we
are
and
I
just
saw
it
so
I
I
can
try
to
pull
in
the
branch
and
demo
it,
but
maybe
next
time
after
after
trying
it
a
little
bit
more
but
I
think
the
plan
is
to
at
least
as
of
now
to
keep
the
two
separate
editors,
one
for
more
of
the
markdown
editor
that
we
have
now
and
then
a
that.
That's
that
we're
calling
content,
editor
I
think
it's
already
been
on
the
wikis
for
a
bit
now,
I,
don't
know
if
it's
defaulted
on.
A
Yet
if
it's
defaulted
on
there
yet,
but
for
issues
like
it's
not
available
in
Mrs
yet,
but
for
issues
it'll
be
behind
a
feature
flagged
that
will
be
that'll,
that'll
be
off
for
a
while
until
we
fully
test
it,
because
I
think
Simon
was
saying
that
there
are
still
some
things
that
he
found
in
the
review.
That
need
to
be
that
need
to
be
cleaned
up.
D
Yeah,
it
was
shared
just
a
couple
of
minutes
ago
on
graphql
channels.
The
survey
is
about
what
you
think
of
building
rest
apis
along
with
graphql,
so
it
is
basically
same
as
the
conversation
we
had
in
a
couple
of
Team
meetings
ago.
So
just
in
case
you're
interested
in
filling
up.
The
survey.
A
Yeah,
it's
kind
of
also
related
to
the
the
other
conversation
in
I
think
it
was
plan
that
someone
had
asked
about,
but
actually
using
our
version,
three
rest
API,
which
I
really
think
they're
using
version
four.
They
just
are.
Maybe
just
there
was
some
confusion
there,
but
around
adding.
A
Think
the
API
around
epic
boards
that
we
have
available
in
graphql,
but
not
in
our
rest,
API
and
I'm,
not
sure
what
kind
of
our,
how
we're,
how
we're
handling
that
right
now
like
if
the
plan
is
to
go
in
there
and
add
those
things
to
the
rest,
API
or
if
we're
just
saying
that
since
we're
using
the
graphql
API
internally,
not
internally,
but
for
our
Decay
lab
project,
are
we
fine
with
just
keeping
it
in
the
the
graphql
API?
For
now?
A
E
E
But
it's
like
how
many
endpoints
do
we
have
I'm
like
I,
don't
know
like
do
we
have
this
as
a
stage
where
I
can,
just
like
put
it
in
it,
feels
like
I'd
love
to
fill
this
out,
but
like
I'd,
probably
put
in
oh
or
your
cat
is
wanting
to
be
another
meeting,
okay
yeah
anyway,
so
there's
I
think
I
would
probably
give
feedback
of
like
there's
certain
things
where
it's
like
this.
This
I
don't
know
how
to
answer
that
question
is
it?
Is
it
you
know,
required
that's
right.
E
Think
that's
good
feedback,
I
think
I'll
give
them
that
feedback,
because
I
thought
well
I,
don't
know
and
then
kind
of
just
like
I,
don't
know
my
eyes
glazed
over
a
bit
and
it's
not
because
it's
a
bad
story,
but
it's
just
like
maybe
this.
If
this
information
is
really
sort
of
on
a
group
level,
we
can
give
that
or
a
stage
level.
You
can
provide
that
and
then
people
can
just
put
it
in.
A
Is
there
a
question
later
on
in
the
after
the
first
page
around
like
what
group
you're
in
or
what
you're?
Yes,
okay,.
A
E
A
All
right,
Ezekiel.
C
Yeah,
so
this
is
just
a
FYI
in
case
you
missed
it.
The
latest
code
review
weekly
Workshop
is
on
security
independencies,
which
is
kind
of
nice
timing.
Considering
this
month
is
security
month,
yeah
I
just
found
it
really
interesting
to
watch
I
had
it
on
the
background,
while
I
was
doing
some
work
and
ended
up
just
paying
attention
and
listening
instead,
so
yeah
definitely
recommend
watching
it.
If
you
have,
some
time
goes
for
about
I,
think
45
minutes
so
yeah
very
interesting.
A
C
Was
it
part
of
maybe
LinkedIn
learning
or
one
of
those?
It's
like
security,
Awareness
Month,
let's
see
if
I
can
find
the
slide
message
and
pop
that
in
there
as
well.
E
It
is
cyber
security,
Awareness
Month,
so
that's.
F
A
Interesting,
that's
cool.
Should
we
be
focusing
on
actually
we're
pretty
good
on
the
security
issues?
I
think
we
have
too
many
in
the
backlog.
We've
been
able
to
stay
ahead
of
those
lately,
which
has
been
nice,
so
never
mind,
not
something.