►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
A
A
A
We've
settled
on
prong
owners,
parent-child
issue,
workflow,
where
a
parent
issues
of
feature
issues
that
we
scoped
at
a
at
a
milestone
level
and
and
you
plan
a
plan
to
deliver
in
a
milestone,
and
then
implementation
issues
are
created
by
the
engineers
as
we
break
down
those
features
and
choose
a
smaller
duration,
so
they
were
through
the
they
go
through
their
eat.
The
implementation
features
go
through
the
workflow
to
progress
so
I'm
quickly
to
share
my
screen
just
so
that
we
can
all
live
asleep
today
and
I
will
open
these
two
boards.
A
And
so
here
we
can
see
the
feature
issue
vote.
So
essentially
this
is
issues
that
are
better
had
that
after
deliverable
label
on
which
is
basically
what
we
used
to
Kate
what
it's
currently
planned
for
the
next
milestone,
so
we
can
see
there's
a
couple
that
have
already
like
in
review
in
development,
I.
Think
there's
a
few
min
that
officially
closed
as
well.
If
we
go
further
and
we
had
a
milestone
in
year,
the
only
one
we
can
scope
it
out
even
more.
C
A
A
So
you
know
that
this
is
kind
of
like
at
the
at
the
future
issue
level,
that
this
is
the
one
that
the
mostly
track
to
see
if
our
progress
against
the
milestone
plan
ease,
trap
and
so
far
from
what
I've
seen
on
see
that
we
have
too
many
issues
fund
arms,
the
next
one
that
we
have,
because
one
I
just
want.
Let
me
just
keep
on
you
know
any
other
way
here
we
go
so
this
is
basically
the
e
verse.
A
Might
be
a
bug
you
are
so
if
we
can
label
out
the
word
and
I'll
stand
because
solve
it.
That
should
give
us.
This
essentially,
is
the
scope
of
all
issue
implementation
issues
that
are
currently
in
progress.
So
this
should
reflect
more
accurately
the
themes
that
you're
actively
working
on
and
at
more
granular
level.
So
we
can
see,
for
instance,
with
city's
growth,
key
ball
verification
it
up
spending
on
growth,
killing
issues
there
that
excited
a
configuration
file
and
so
on.
A
So
this
is
not
to
conflict
work
reports
that
we
have
in
terms
of
what
I'll
be
watching,
mostly
from
from
my
point
of
view,
this
one
just
to
track
how
we
doing
on
earth
on
a
milestone,
planning
point
of
view,
and
it's
also
the
level
that
we'll
be
reporting
on.
You
know
group
calls
to
from
it.
Are
we
running
into
any
issues
that
we
need
to
show
you
discuss
with
it?
B
A
That
wouldn't
be
long
silent,
wait
moving
on
I
wanted
to
ask
everybody:
how
comfortable
are
we
with
using
the
acronym
is
as
EE
for
referring
to
that
exciting
written
there's
a
lot
of
places
where
we
use
you
sitting
kind
of
like
by
Queens
the
works
of
odd
names
and
stuff,
and
with
your
rights
that
excited
about
you
know
like
it,
takes
up
a
lot
of
space
and
things
and
first
of
all,
I
want
to
check.
Is
everybody
comfortable
internally
referring
to
it
as
he
as
a
static
site,
editor
and
then
also
honoring.
A
However,
I
feel
like
this
is
you
know
on
our
team
page,
it's
okay
to
refer
to
a
sec,
especially
if
we've
written
it
out
in
full
at
once,
at
least
and
when
internally,
referring
to
it
and
I,
now
slack
communications
believe
you're,
cheating,
fine,
you
know
workflow
boards,
which
is
mainly
used
by
our
team,
should
fine
as
well.
So
you
know,
can
I
get
a
quick
thumbs
up
thumbs
down
on
that,
but
maybe
before
that
Eric,
you
had
a
point.
You
wanted
to
call
out
him
I.
A
B
A
That's
a
very
interesting
point
you
made
you
know
like
they,
they
already
things
like
it,
sorry,
and
how
how
many
other
people
interpret
a
city?
How
are
they
going
to
try
and
think
that
this
is
a
site
stability
agent,
their
acronym,
or
are
they
actually
gonna,
even
kind
of
like
we,
you
know,
make
the
connection
of
static
site
editor.
C
Chad
I
think
it
would
be
okay
to
use
internally,
like
you
said,
but
we
should
ensure
that
we
define
it
on
all
of
the
main
public
facing
pages
for,
because
right
now,
I
just
searched
a
handbook
for
it,
and
nothing
came
up
so
just
to
make
sure
that
on
all
of
our
pages,
if,
if
we
define
it
and
people
search
for
it
and
they
have
booked
they'll
find
it
okay.
So.
A
A
B
A
They're
there,
after
you
can
recruit
it,
there's
a
CC,
so
that
I
think
would
be
acceptable
and
wherever
we
we're
writing
about
it.
In
a
formal
context,
like
a
blog
post
called
product
release,
post
will
always
write,
write
it
in
full,
so
I
think
that's
a
good
good
one
to
choose
any
internally
in
terms
of
our
our
slash
channels.
A
B
A
Because
just
just
freaking
of
the
context
that
Eric
mentioned
here,
you
know
there
are
so
many
acronyms
out
there
and
to
think
that
if
you
have
to
make
wonder
about
what
he
sees
he
is
like,
then
we
failed.
Our
communication,
so
I
think
publicly
is
mean
II
kind
of
like
it
issue
its
amar,
etc
and
formally
always
written
and
fully
so
those.