►
From YouTube: Package Group Weekly Sync 20200309
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
Welcome
everybody
to
the
package
group
weekly
sync
for
March,
the
9
to
2020
I've,
upgraded
this
time
to
saying
the
correct
date
which
I
seem
to
have
got
wrong
open
times
in
sequence.
So
pretty
proud
of
myself.
They're
kicking
off.
We've
got
a
few
things
to
get
through
today,
so
I'll
try
to
move
relatively
quickly
through
my
stuff,
I
think
retro
I've
linked
there
for
a
12-9,
so
I've
tried
I'm
going
to
try
to
link
this
in
each
of
our
weekly
meetings,
so
that
I
can
remind
myself
to
look
at
it
as
well.
A
A
A
Yeah,
this
is
what
sort
of
means
that,
if
you
end
up
taking
longer
on
something
because
it
just
you
find
there's
some
issue
within
the
thing
we
weren't
aware
of,
but
whatever
it
is,
that's
not
sort
of
all
like
locked
out
all
the
other
work
we
have
scheduled.
But
you
want
to
verbalize
that
Nico
at
all.
A
Yeah
I
mean
it's
not
a
huge
deal.
It's
just
I
don't
want
to
get
in
that
habit
of
filling
our
milestone,
because
we
do
try
to
focus
our
milestones
on
on
things
we're
committing
to
working
on.
So
if
we
assume
a
bleep
reassign
them
it
just
sort
of.
It
means
that
it
can
be
kind
of
weird
for
people
who
are
like.
A
Ok,
what's
the
next
most
important
thing
with
someone
else
assigned
so
the
other
scenario
I
was
chatting
with
Ian
about
this
and
Ian
was
saying
his
work
flows
a
little
different,
so
Ian's,
mind
pre-assigned
things
and
that's
okay,
since
he's
the
only
one
that
would
end
up
working
on
them,
but
I
think
for
us
it
could
be
other
people
on
the
team
working
on
it.
So
that's
why
it's
like
hey
it's
not
because
if
you
need
to
take
some
time
off
or
whatever
right,
you
don't
want
that
stuff.
A
C
How
do
you
stay
yeah?
This
was
pretty
widely
distributed,
but
thought
I
was
worth
mentioning.
There
were
some
changes
to
this
security
developer
workflow,
mostly
having
to
do
with
you
know
where
you
link
different
Mrs
and
issues,
and
the
checklist
themselves
have
also
changed
in
the
issue
templates,
but
just
a
heads
up
if
anyone
as
a
security
issue,
they're
working
on
or
going
to
be
starting
back
today,.
A
Thanks
Steve
for
eliminate
crew,
I
can't
say
preliminary
apparently
preliminary
mo
for
measuring
our
progress
and
character
category
at
maturity,
goals,
I,
really
appreciate
people's
feedback.
I
know
some
people
had
got
into
this
already
and
gone
on
and
made
suggestions
which
I
really
appreciate.
D
I
thought
of
the
update
made
sense.
It's
in
line
with
everything
that
we're
doing
I
just
added
a
note
in
there
about
Ian's
role
in
this
as
a
product
designer
he
will
be
responsible
for
saying.
Okay,
we
have
these
maturity
targets.
We
have
the
features
there.
What's
our
grade
and
he'll
actually
evaluate
whether
or
not
we've
achieved
that
maturity
target
or
not,
based
on
user
research,
so
I
just
added
a
note
to
clarify
that,
but
other
than
that
it
looked
like
what
we
want
to
start
doing:
cool.
A
Thank
you
for
that.
It
ended
up.
Being
I
was
sort
of
thinking
in
my
head.
It
would
end
up
being
this
huge
page
of
like
information,
but
when
I
actually
wrote
it
then
I
was
like.
Oh.
This
is
like
a
like
a
couple
like
a
paragraph
maybe,
and
a
couple
of
bullet
points.
It
wasn't
that
big
a
deal
so
I
was
overthinking
it
in
my
head.
So
thank
you
very
much
for
that
feedback
Emma
to
merge
packaged
into
a
single
team
in
the
handbook,
so
we're
an
integrated
team
and
that
Emma's
been
merged.
A
Also,
if
you
look
at
our
team
page
now,
there's
no
more,
it
doesn't
have
Nick
and
Nico.
It's
stable
counterparts
with
me
as
a
stable
counterpart
to
myself,
because
we
don't
technically
have
a
front-end
engineering
manager,
I
think
I
could
disable
counterparts
myself
constantly
like.
Why
would
we
do
that
anyway?
So
that's
already
been
most
issue.
Discuss
code
review
survey
results
since
we
had
some
exhaling.
A
A
The
intent
is
to
have
action
items
that
come
out
of
that
that
are
public.
Once
we've
got
to
a
point
where
we're
pretty
happy
and
everyone's
had
their
opportunity
to
discuss
it
cool.
So
go
take
a
look
at
that.
Let
me
know
if
you
have
any
feedback,
you
haven't
already
12
10
review
and
discussion
issue.
Is
we
do
the
asynchronous
issue
to
say
what
we're
committing
to
in
the
next
milestone
and
12?
A
D
Yeah
I
think
first
Raman
halia
that
I
think
you're
you
both
are
still
working
through
the
online
garbage
collection
issue
and
defining
the
metadata
table.
I
was
wondering
if
there
are
issues
that
are
going
to
be
coming
from,
that.
That
will
open
and
if
we'll
have
those
done
like
earlier
this
week
or
if
it'll
be
something,
that's
done,
I'll
just
pick
it
up
once
we
start
as
a
milestone.
E
So
the
one
that
it's
going
on
is
the
database
schema
I
will
talk
to
have
that
done
for
twelve
nine,
so
I.
Don't
think
that
should
be
enough
time,
but
we'll
have
some
follow-up
issues
on
that,
one
that
will
fall
in
the
top
ten
milestone,
namely
implementing
the
database
in
the
registry.
So
we'll
open
an
issue,
at
least
for
that
one
and
I'll
ping.
You.
D
Okay,
yeah,
that
sounds
great
I'm.
Okay
with
that
and
the
other
question
can
I
ask
another
question
in
just
planning
a
nice
wee
GG,
now
the
urine
this
meeting,
it's
really
helpful.
We
added
the
metadata
to
the
package
registry
recently
where
we
could
show
pipeline
and
branch
and
commit
and
I
was
wondering.
Are
we
able
to
do
the
same
thing
for
the
container
registry,
because
that
would
be
a
nice
issue
to
pull
into
the
milestone
as
well,
but
I
didn't
know
if
the
API
covered
both
use
cases.
G
F
H
B
So,
as
usually
I'm
selling
the
proof
of
concept
at
every
corner,
so
we
have
now
await
for
the
backend
work
that
needs
to
start
next
needs
to
be
done
before
the
front
end
can
be
done.
So
do
we
want
to
move
on
with
this?
If
so,
I
could
start
working
on
the
front
end
and
in
parallel
the
end
features
like
as
usual.
If
not
I
can
stay
apart
for
a
bit
more,
you
know
any
question
any
disagreement
over
the
architecture
and
stuff
like
this.
This
is
kinda
different
from
the
usual.
B
F
A
Yeah
this
should
have.
We
should
add
the
package
triage
label
on
this
as
well,
because
it's
as
unless
it's
scheduled,
we
we
definitely
want
to
put
that
label,
and
so
people
know
that
you're
looking
for
assistance
and
out
of
the
team,
Gigi's
gonna
be
focused.
I,
don't
wanna
speak
the
AGG,
but
on
the
PPI
implementation,
our.
B
F
B
A
D
D
So
let
me
look
at
the
milestone
as
well
and
see
if
I
could
fit
in
an
issue,
and
maybe
I
have
to
swap
something
out,
but
I
think
this
could
be
valuable
to
get
into
this
milestone
so
I'm
a
and
then,
if,
if
we
can't
get
it
in,
then
it'll
be
the
thing
that
if
you
have
time
pick
it
up,
but
yeah
it'd
be
nice
to
fit
fit.
This
work
in.
E
We've
been
having
more
feature
requests
for
the
container
registry
and,
unfortunately,
a
good
portion
of
those
if
we
have
found
them
to
be
unfeasible
either
because
we
don't
have
required
data
to
implement
them
or
because
due
to
performance
constraints,
we
can't
do
it.
A
prime
example
of
this
was
the
distinction
between
docker
and
helm
images
and
with
every
feature
that
we
have
like
this.
E
D
E
We
should
note
that
this
is
only
for
those
beyond
12
times.
So,
what's
what
schedule
for
12:10
we
should.
We
should
do
it
because
it's
already
planned
and
it's
only
a
performance
improvement
on
the
github
site.
So
there
is
no
need
for
a
registry
changes
for
that,
so
that
won't
be
affected
and
I
think
we
should
consider
this
for
beyond
12
times
so
anything
beyond
that
should
be
freezed
unless
it
is
a
bug,
fix
or
something
critical,
but
if
it
is
a
new
feature,
I
think
we
should.
We
should
postpone
them.
D
I'm,
all
for
that
I
think.
One
thing
that
would
really
help
me
is
what
we
mentioned
earlier
in.
The
call
is
if
we
have
a
if
we
could
fill
out
that
epic,
with
a
set
of
issues
with
a
plan.
It
gives
me
something
easier
to
point
to
us
like
we're
working
on
this
and
anything
else
that
isn't
this
core
set
of
issues
is
a
distraction.
Yeah.
E
F
It's
not
even
that
worth
mentioning
and
just
being
silly
I,
just
noticed
slack
is
showing
the
other
person's
time
time
zone,
but
a
parent
doesn't
show
always
I
just
thought.
It
was
like
a
new
thing
or
something
but
I
guess
it's
not
just
shows
when
they're
all
the
persons,
don't
sleep
mold
or
something
like
that.
Just
thought
it
was
pretty
cool
when
I
saw
got
overly
excited.
A
Nice
I
think
I
think
saying
that
you're
now
a
little
bit
more
proximate
in
time
zone,
Gigi,
it's
more
than
happy
for
you
to
be
excited
about
such
things.
So
does
anyone
want
to
verbalize
their
comment?
Nico
and
Haley
yeah.
B
F
Don't
be
scared,
you
can
talk
to
me
anytime,
if
I'm,
not
if
I'm
away
from
a
computer
or
like
doing
and
available
just
won't
reply
or
like
replied
the
other
day.
So
don't
don't
worry
just
just
message
me
if
I'm,
you
know
I'm
pretty
comfortable
just
like
ignoring
when
you
know
when
I'm,
not
working
or
whatever
so
yeah
reach
out,
don't
don't
be
afraid.
A
Cool
all
right
with
that,
if
no
one
has
any
other
comments
on
cell
phone,
this
one
was
pretty
packed
with
things.
So
thanks.
Everyone
for
doing
that,
figs
are
one
thing
I
want
to
follow
up
on.
Is
the
Nicko's
proof
of
concept
back
in
work
couple
of
questions
there
about
separating
it
out
into
back-end
issue
and
separate
back-end
issue?
If
that's
going
to
be
helpful,
maybe
it
makes
sense
to
do
that.
We
go
otherwise
with
that
said,
I'm
going
to
finish
the
recording
and
people.
If
you
would
like
you
can
hang
out.