►
From YouTube: Weekly Package Meeting 06-18-19
Description
Our weekly team meeting where we discuss upcoming milestones, process and anything else that needs discussion.
B
A
The
first
item
on
the
agenda
actually
is,
for
me:
I
shared
a
link
in
the
doc
to
our
group.
Presentation,
which
is
tomorrow
so
Dan
and
I
are
going
to
be
working
on
or
we'll
be
presenting
that
walking
through
the
different
slides
more
of
an
FYI.
Please
feel
free
to
take
a
look
through
and
if
you
have
any
questions
or
discussions
or
you
think
something's
wrong,
just
add
a
comment
there
and
I'll
address
it
before
Wednesday.
A
The
second
issue
is
me
as
well:
I'm
roped
in
it
now
officially
to
this
storage,
counter
and
limits,
storage,
counter
and
limits
discussion
that
the
delivery
team
is
working
on.
This
is
adding
in
first
counters,
for
all
of
our
storage
on
get
lab,
starting
with
the
package
features
and
then
the
idea
is
to
add
a
soft
and
hard
limit.
A
So
we
could
warn
users
when
they're
approaching
that
limit
and
eventually
then
say
well,
you
could
pay
for
more
storage
if
you
want
to
so
Marin
and
team
are
working
on
this
this
issue,
but
we'll
probably
start
to
get
roped
into
this
a
little
bit
because
they
want
to
hand
this
off
work
off.
So
at
some
point
they
want
to
have
a
successful
transition
so
again
more
of
an
FYI,
but
I
just
wanted
to
keep
everyone
up
to
date
that
this
work
is
happening.
So
if
you
get
pulled
into
conversations,
don't
be
too
shocked.
A
And
then
quickly,
I,
where
my
goals
for
the
end
of
the
week
to
have
12
to
fully
Grund
by
the
22nd
I,
put
a
link
to
the
the
milestone
there
and
just
a
quick
high-level
view
of
what's
going
on.
So
this
would
be
great
if
we
could
start
Trek
tracking.
Our
initial
set
of
metrics
in
12
and
I
have
a
Dan
looks
like
that
issues
still
aligned
to
you.
We
would
probably
have
to
change
that
and.
C
A
A
We
have
a
couple
of
front-end
changes
here,
so
one
is
changing.
The
overall
navigate
high
level
navigation
for
package
features
at
the
group
and
project
level,
and
for
this
one
we
do
have
design
I
believe
this
is
UX
ready,
so
amelia
created
some
SVG's
for
this
already,
the
other
one
Nick
has
been
working
on.
A
A
C
So
far,
it's
been
quite
positive,
so
I'll
be
doing
reference
checks
for
this
person
and
hopefully,
hopefully
that'll
all,
be
positive
and
we'll
be
able
to
send
out
an
offer,
and
at
that
point
where
we'll
have
a
technically
full
house,
although
people
haven't
started
yet
so
it
doesn't
feel
quite
like
a
full
house.
Yet
so
right
now
we're
scheduled
to
have
someone
joining
the
team
in
July
two
people
in
August
as
a
function
of
just
the
way
these
various
countries
work
and
with
contracts
and
whatnot.
C
So
like
we
were
pretty
excited
to
have
these
people
join
our
team,
but
this
was
as
soon
as
they
could
join.
Unfortunately,
so,
just
working
through
working
through
that
process
and
as
I
said
just
finalizing
the
reference
checks
today,
I
have
to
have
one
scheduled
another
one
that
I
have
pretty
much
just
have
to
book
a
meeting
for
and
then,
if
I
need
a
third
I
might
be
able
to
reach
out
and
that's
pretty
much
it
on
the
hiring
front,
as
Tim
rightly
mentioned.
C
Just
working
through
12,
the
big
thing
is
they
contain
the
registry
maturity
parts
that
I've
been
trying
to
get
a
handle
on
trying
to
add
some
sort
of
technical
information
pros
and
cons
and
whatnot
and
I
can
link
that
if
people
are
interested,
I'll
put
it
in
our
package
channel
and
slacks
and
people
can
check
it
out
and
basically
just
doing
bug
triage
as
well
and
trying
to
make
sure
I
understand
what's
going
on
there.
So
that's
it
for
me:
John
did
you
have
something
you
wanted
to
mention.
D
Google
Calendar
was
giving
me
a
404,
so
Tim.
This
is
for
you.
Nick's
doing
Nick
has
been
doing
an
awesome
job
working
through
his
first
two
issues
we
assigned
to
him.
So
we
wanted
to
reach
out
and
see
if
there's
any
other
additional
smaller
UI
issues
that
Nick
could
pick
up
and
work
under
package.
If
not
I
can
definitely
find
some
small
bugs
or
UI
polish
items
under
release
or
verify
as
well,
but
wanted
to
piggy.
First
there's.
B
A
1
6
3
9
and
6
2,
7,
7,
0,
ok,
both
seem
ready
to
work
on
and
our
UX
ready.
Ok
also,
we
could
start
there
and
and
and
there's
another
one
that
I
could
pull
forward
to
for
modifying
the
dependency
proxy
design.
That's
a
pretty
small
one,
so
we
could
add
that
one
and
two,
if
there
I,
could
pull
that
one
into
12
two.
If
there's
more
time,
ok.