►
From YouTube: Package Weekly Sync 07-06-20
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
Hello
and
welcome
to
our
weekly
sync
on
July
6th.
We
have
an
agenda
we'll
be
working
off
of
there's.
A
few
people
out
today
actually
had
the
first
agenda
item,
so
less
interaction,
less
milestone,
I
put
together
some
thoughts
on
prioritization
and
one
thing:
that's
come
up
as
being
organizationally
important
is
some
of
the
work
around
accurately
counting
storage
and
applying
storage
limits.
We
have
an
epoch
and
some
plan
work
coming
up
in
13-3,
but
I
just
wanted
to
make
a
team
aware
that
that
is
sort
of
like
a
spike.
A
Okay,
so
next
agenda,
but
there's
no
questions
I
signed
up
and
was
accepted
into
the
CEO
shadow
program.
The
good
news
is
that
it's
two
weeks,
but
it's
split
by
a
week
where
Sid
goes
on
vacation,
so
I
have
a
one-week
in
the
shadow
when
we
out
when
we
back
in
I'm,
really
excited
I'm
gonna
work
on
this
week.
What
has
to
be
true
for
me
to
feel
comfortable
about
being
out
during
that
time?
So,
if
you
have
anything
any
concerns,
you
I'll
share
around
an
issue
and
we
could
work
on
that
together.
A
Okay,
I
could
read
the
third
item
for
Gigi
who's
on
a
pack
time
and
not
here.
Yes,
what
about
adding
quotas
for
reviewing
community
Mrs
in
our
package
group
page,
we
could
have
clear
guidelines
in
a
time
box
for
reviewing
these
em
ours
to
communicate
effectively
what
our
capacity
and
expectations
are
we're
currently
imagining
big
community
contributions,
which
take
a
lot
of
effort
and
time
to
review.
A
A
B
Yes,
so
I
will
say
it
maybe
20
30
minutes
a
day
seems
a
little
bit
too
long,
and
the
other
thing
that
we
need
to
consider
is
like
conflict
and
like
a
man
like
if
there
is
a
community,
might
attach
the
same
code
that
you
are
touching
for
your
deliverable.
Now,
what
we
are
going
to
prioritize
is
dynamic
choice.
It's
always
deliverable
choice.
B
A
C
Was
just
gonna
say
that
I
go
to
the
runner
I'm
I
I'm,
the
writer
for
the
runner,
team
and
I?
Don't
know
I,
don't
think
they
have
rules,
but
I
think
they
had
the
same
problem
because
they,
if
their
board,
has
a
ton
of
community
stuff
and
they're
always
kind
of
yeah
same
problem.
I,
don't
know
the
solution.
Okay,.
A
A
A
C
I
just
had
a
couple
really
quick
questions
that
I
just
logged
in
and
looked
it
looks
like
the
it
looks
like
Nico.
Did
you
merge
the
mr
to
rename
it
so
everything
is
kind
of
gone
kannan.
C
So
I'll
go
ahead
and
merge
the
docs,
then
or
I
have
to
get
them
to
another
tech
writer
who
could
merge,
but
I
just
wanted
to
make
sure
there's
I
mean
there's
a
tiny
API.
That's
still
called
expiration
policy
and
it
sounds
like
Nico
said
you
know,
it'll
be
a
breaking
change
if
you
fix
that
so
I'm,
just
throwing
it
out
there
for
like.
Should
we
create
an.
C
B
Yeah
so
I
think
the
API
changes
when
it's
a
breaking
change.
They
follow
a
huge,
not
a
huge
but
a
pretty
long
workflow,
where
you
add
a
new
one
with
a
new
name
and
then
they
forget
the
second
one,
wait
ex
milestone
and
then
remove
it
and
it's
kind
of
a
big
deal.
But
we
can
do
it
just
need
to
a
plan
for
it.
What's
not
much
I'm.
C
C
A
C
And
then
the
next
one
is
oh
yeah,
okay
and
people
already
reply.
It
basically
was
just
there's
an
issue
to
improve
the
cleanup
policy.
Docs
and
I.
Just
yeah
Ian
has
a
new
design,
so
any
same
yeah
I'm,
not
sure.
If
the
doc
showed
up,
we
should
update
the
Doc's
twice
and
I
was
thinking
the
same
thing.
C
D
Hoping
to
get
the
designs
done
by
the
end
of
13,
so
it'll
be
ready
to
move
forward,
but
I,
don't
know
that
would
be
a
Tim
question
about
when
the
actual
change
should
be
spotted.
I
think
we
have
a
big
conversation
about
front
end
priorities
happening
this
Friday,
so
I
wonder.
If
we'll
have
a
bed
a
good
answer,
then,
and
then
we
can
make
a
decision
on
whether
we
make
small
changes
to
the
dock
style.
We're
really
just
wait
until
everything
goes
at
the
same
time.
A
C
And
just
sorry,
one
last
thing:
I
know:
I
didn't
put
it
on
the
agenda
because
I
just
thought
of
it
was
the
move
from
the
features
to
core
I
just
want
to
throw
it
out
there
again
yeah.
If,
if
you
need
help
or
if
I
mean
it,
looks
like
it's,
not
that
much
work
to
change
the
Docs
to
update
them
to
core.
But
if
you
guys
want
me
to
do
any
work
on
that
I'm
happy
to
help
so
keep
you
posted
okay,
yeah.
C
B
D
C
That's
okay,
I
I,
you
know,
I
didn't
think
about
it.
I
did
there's
a
couple
places
where
we
can
put
a
second
book
universe
is
introduced
in.
We
could
put
a
second
bowl.
This
has
moved
in,
but
I
think
I
think
I
covered
the
bulk
of
the
changes
in
that
comment.
Yeah
there's
probably
a
probably
good
idea.
If
I
I
look
read,
look
over
everything
and
kind
of
make
sure
I
didn't
miss
anything.
C
As
far
as
my
main
concern
was
that
when
you
change
the
title
and
you
remove
that
little
ultimate
badge,
it
changes
the
egg
link,
but
because
it's
only
listed
at
the
top
level
I
think
we're
okay,
because
we
don't
usually
link
to
those,
because
another
thing
that
will
break
is
the
release.
Posts
like
the
nav
will
break
and
then
the
release
posts
in
the
other
WWE
gitlab
project
that
link
to
those
would
break
but
I
think
we
don't.
We
never
link
to
the
top
level
anchor
and
that's
the
one,
that's
gonna.
C
B
Niko
you're
the
last
item
yeah.
So
speaking
of
dogs,
we
need
to
regenerate
the
screenshot
after,
like
13
to
uij
around
the
container
industry
changed
significantly
so
now
the
last
UI
change
it's
in
review
right
now,
but
since
it's
like
it
may
have
someone
like
look
that
review
cycles
on
it.
Does
it
make
sense
to
start
the
docs
update,
screen,
chat,
update
with
like
a
non
merged
stuff,
and
we
all
dog
just
to
merge,
but
we
can
review
it
with
stuff,
like
that,
all
it's
better
to
wait
until
it's
fire.
C
So
there's
a
we
have
this
thing
and
they
it's
not,
maybe
not
in
the
handbook
or
in
the
Oh,
still
waking
up
anyway.
There's
the
thing
called
like
a
post
post,
merge
review.
So
if
you
want
to
get
a
feature
in
and
then
review
the
docs
right
after
we
can
do
that.
So,
if
screenshots
are
giving
you
grief,
we
can
do
them
after
the
fact,
and
we
can
also
do.
Are
you
talking
about
the
cleanup
policy
screenshot
specifically
or
a
different
area
of
the
you
I
know.
B
C
Oh,
so
that's
probably
a
lot
of
screenshots
or
is
it
it's
probably.
C
B
C
So
really
quick,
I'm
gonna,
give
you
a
tech
writers
feel
if
you
can
handle.
If
you
don't
mind,
there's
there's
like
three
main
types
of
content
right:
it's
either
a
concept
where
you're
trying
to
teach
the
one
overall
concept,
there's
a
task
where
you're
just
trying
to
give
them
a
procedure
and
then
there's
reference
content
which
is
more
like
these
fields.
Do
this
right?
It's
just
reference.
You
know
it's
just
like
a
table.
You
would
look
up
information.
C
So
when
I
look
at
the
existing
content,
my
brain
is
always
like:
okay,
what's
a
concept
or
I'm
trying
to
teach
of
something
versus
a
task
verses
and
the
those
topics
that
are
like
a
screenshot,
and
it
says
in
this
on
this
page,
you
can
view
and
do
these
things
it.
It's
really
like.
If
you
think
about
how
you
as
a
user,
would
look
at
content,
you
would
never
really
you
wouldn't
search
the
help
for
this
kind
of
information.
You
just
be
in
the
UI
you'd
be
doing
stuff
and
you'd
be
clicking
things.
C
Oh
I
could
sort
I
could
filter
I.
Can
you
know
you
wouldn't
ever
say
how
do
I?
You
might
say
how
do
I
filter,
but
then
you
would
want
to
find
a
task
that
says:
filter
go
to
this
page
click,
this
button
filter
so
anyway
long
story
short
I'd
like
to
remove
so
these
screenshots
and
make
these
things
more
task-based,
so
that
they're
easier
to
search
for
and
find
that
if
that
makes
sense.
C
C
B
It's
not
much
about
taking
and
preparing
the
screenshot
is
a
much
like
having
the
feature
merged
and
then
working
the
screenshot
at
the
same
time.
That's
what
worries
me,
but
I
will
gotcha.
They
shouldn't
change
based
on
technical
review,
the
UX
reduced
them,
so
I
will
prepare
the
EMR
and
then
we
just
keep
it
blocked
until
the
UI's
merged,
and
then
we
merge
afterwards.
Okay,
thank
you
very
much.
I.