►
From YouTube: Weekly Package Meeting 07-09-19
Description
Weekly team meeting in which we discuss process, welcome new team members and discuss open backlog issues.
C
C
B
A
C
C
B
E
A
A
They
had
a
link
to
that
time
zone
tool
and
it's
a
pretty
simple
and
cool
sorry
about
the
dog,
and
so
it
seemed
like
a
good
idea,
because
now
that
we're
getting
spread
out,
it's
good
to
know
when
everyone
else
is
yeah,
it
looks
like
Dan's
got
it
all
set
up
and
it's
all
working
and
I
think
pretty
much
everyone's
on
there,
one
of
either
Dan
or
Tim.
One
of
you
has
to
move
so
that
we
can
have
different.
You
know
not
more
than
one
person
in
each
time
zone.
B
B
We
awfully
spread
out,
I'm,
just
cool,
so
I've
added
that
link
into
the
document,
so
our
team
edge-
you
can
look
at
anyway
and
we
also
have
the
airdrop
team
is
a
toolbar
utility
that,
where
I'm
using
anyway
I
don't
know,
if
anyone
else
wants
to
use
it-
and
you
can
add
people
and
or
just
random
time
zones,
if
you
want
to
add
it.
So
that's
another
option,
I
think
the
other
question
I
have,
and
this
comes
a
little
bit
from
your
question
in
the
APAC
company
called
last
night.
B
Gigi
was
like
how
we
help
if
they
think
process
work
better
and
help
it
be
more
of
a
like
useful
experience
for
everyone
and
I.
Think
I
just
want
to
get
everyone
thinking
about.
I,
know
Gigi's
like
it's
day
or
something.
So
you
probably
have
some
limited
thoughts
about
it,
but
oh
yeah
yeah,
so
if
you
just
want
to
like
everyone,
should
be
thinking
about
how
we
can
help
this
work
better.
B
This
is
one
of
the
things
we're
doing,
which
is
having
a
teammate
of
meeting
later
in
the
day,
as
you
can
see,
Tim
added
new
sort
of
subjects
for
each
of
these
team
meetings
during
the
week,
so
that
we
can
do
a
bit
of
grooming
at
the
end.
What
I
wanted
to
go
fairly
quickly,
but
let's
sort
of
start
iterating
through
and
trying
to
find
a
good
way
to
handle
the
async
work
that
people
are
doing
and
I
will
be
moving
one
meeting
per
month
to
the
4
p.m.
B
time
from
this
meeting
and
one
meeting
per
every
other
I
think
it's
every
third
week
or
so
I'll
move
the
retro
as
well,
and
the
retro
next
week
is
going
to
be
at
4
p.m.
so
current
plan.
We
can
improve
if
we
need
to
so.
Thank
you
now.
I'll
read
next
Amelia
in
your
x-rays
and
concerns
around
new
container
registry,
empty
state
being
too
wide,
not
matching
up
with
guidelines.
This
is
my
bad
I,
missed
the
guidelines
around
this
and
increase
their
with
thinking.
It
would
suit
the
content.
B
Better
I've
created
a
new
issue
issue
where
this
can
be
discussed
once
the
solution
has
has
been
settled
on
I'll
apply,
the
fix,
I
wasn't
sure
about
milestones,
so
I've
added
12.2,
as
it
should
be
a
quick
fix.
If
this
is
wrong,
can
someone,
let
me
know
also,
please
add
any
comments.
If
you
have
any
as
well
Oh,
he
said
comments.
Anyone
if.
A
C
Tim,
okay,
so
well,
yeah
mine
was
welcome
and
he's
not
here
today,
as
we
could
see
in
the
time
zone
he's
it's
1
a.m.
for
him
presently,
but
he'll
be
in
the
next
set
of
meetings
that
we
have
really
excited
to
have
him.
It
kind
of
addresses
the
issue
that
Nick
mentioned
above
having
a
designer
fully
dedicated
to
our
team,
is
going
to
be
awesome
and
really
helpful
for
all
the
work
that
we're
doing
so.
I'm
really
excited
for
you
to
join.
B
Yeah,
it's
super
awesome
to
have
the
team
getting
built
out
and
then
on
that
note
as
well
to
continue
the
thought
of
being
stoked
to
have
peeps
here,
it's
great
to
have
you
on
the
team.
Gigi
first
thing,
moving
I
thought
I'd
bring
this
one
forward,
so
you
have
a
chance.
You
said
I
just
meet
a
couple
of
the
other
people
in
person
rather
than
having
a
look
at
and
look
at
me
the
whole
time
it's
great
to
have
your
teammate.
E
B
Glad
to
have
you
here,
like
Redis,
the
Redis
situation,
I
link
to
it
in
the
package
Channel,
and
this
is
a
rapid
action
around
radius
performance
that
was
actually
impacting
our
production
sites
overall
performance.
There,
a
lot
of
effort
going
in
just
sort
of
diagnosing
what
was
going
on
it
looked
like
they
might
have
been
some
issues
around
people
trying
to
hack
hack
or
DDoS
that
app
servers.
So,
if
I'll
add
the
link
here,
but
it's
definitely
in
the
package
channel
already
definitely
look
into.
B
The
next
thing
to
keep
in
mind
is
maintain
as
technical
interviewers,
going
hiring
and
also
actually
DB
maintain.
Is
we
want
to
keep
in
mind
that
it's
it's
sort
of
intended
for
senior
engineers
in
the
team
to
become
technical,
interviewers
and
maintain
is
relatively
quickly.
We're
pretty
short
on
maintain
is
right.
Now
we
only
have
one
database
maintainer
as
far
as
I
know,
so
that
puts
a
little
load
on
that
person.
It
means
that
our
requests
for
maintenance
and
sorry
reviews
and
approvals
will
be
delayed.
B
Boards
I've
created
three
boards
for
the
team
assignments
planning
in
bugs
they're
going
to
stay
at
the
top
of
the
the
agenda
document
as
Tim
already
added
them.
There
I
put
a
note
in
here
just
to
sort
of
call
them
out.
Everyone's
attention
assignments
are
going
to
show
just
anyone
on
the
team
of
what's
currently
assigned
to
them.
That
includes
myself
and
team
and
then
Steve
and
Gigi,
and
then
Ian
Nick
as
well.
So
we
all
have
a
column
there.
E
B
And
you
have
to
actively
sort
of
say
the
Mr
closes
or
or
or
whatever
I
think
it
closes
the
issue,
so
you
have
to
take
it
to
an
active
step
to
make
sure
the
issue
is
closed.
Once
the
EMAs
are
completed,
so
something
to
keep
in
mind.
Their
planning
is
open
issues
that
are
assigned
to
group
package
or
actually
no
that's
DevOps
package
and
other
other
workings.
We
actually
have
a
label
on
for
the
milestone.
Excuse
me
a
milestone
on
so
that's
all
like
all
of
the
ones
that
are
coming
up,
we'll
maintain
that
list.
B
This
will
be
the
basis
of
a
discussion
that
we
have
around
planning,
so
definitely
something
that
there's
more
sort
of
Tim's
realm,
but
definitely
something
that
we'll
be
chatting
about
in
in
these
meetings.
The
last
one
is
bugs.
This
is
a
good
place
to
go.
If
you
sort
of
like
hit
a
point
where
maybe
you're
waiting
for
a
couple
of
reviews
and
your
issues
and
you
you
know,
you've
got
a
little
bit
of
a
window
of
time-
might
be
worth
going
and
checking
out
those
bugs,
maybe
check
to
see.
B
In
your
case,
you
have
a
couple
of
assignments
already
and
that's
just
because
you're
onboarding
tasks
for
you
so
that
it's
clear
what
you
need
to
work
on
as
you're
starting
up
and
that
way
you
don't
have
to
be
like
what
do
I
do
next.
You've
got
something
there
to
work
on,
so
we
talked
about
that
yesterday,
but
I
just
wanted
to
save
here
cool.
Thank
you
Tim
over
to
you.
C
However
many
you
know
high-priority
items,
there
are
and
make
sure
that
we're
following
up
on
them
and
answering
any
questions
and
that
we
can
get
them
ready
for
whichever
milestone
they'll
be
put
in
so
as
part
of
that
I'm.
Looking
at
the
planning
board
and
the
column,
all
the
way
on
the
left
is
basically
our
full
backlog.
This
is
the
open
column
and
they're.
Not
all
sorted
you'll
see,
there's
hundreds
of
issues
there,
but
I'm
trying
to
keep
the
top
5
sorted,
and
so
the
first
item
on
here
is
this
registry.
C
B
B
C
It's
a
frustrating
experience
for
users
because
often
times
people
lose
all
their
work
or
lose
all
their
images
and
not
know
so
in
12,
oh,
we
launched
a
modal
here
that
would
warn
them
at
least
that
this
behavior
will
happen,
but
people
users
are
still
requesting
that
we
fix
the
core,
behavior
and
and
so
yeah.
This
is,
let's
see
if
37
fo,
so
it's
a
decent
amount
for
our
stage.
C
It's
not
the
biggest,
but
it's
definitely
on
the
higher
end
and
in
the
issue
there's
several
users
that
have
proposed
potential
fixes
and
even
contributed
a
merge
request,
which
I
think
we
decided
not
to
implement.
So
this
is
an
issue
that
I'm
working
on
grooming
now
I'm
just
ironing
out
the
the
problem
to
solve
and
putting
together
a
proposal,
but
I
just
wanted
to
bring
it
up
here,
as
this
is
something
that
I
would
like
to
see
us
to
work
work
on
and
if
there
were
any
questions
or
comments
or
anything
yeah.
C
B
C
B
So
this
is
this
is
a
sign
but
I'm,
given
that
it's
a
non-voting
table,
you
know
we
want
to
want
to
make
sure
GG
has
every
opportunity
to
so
they
get
a
sense
of
whether
it
is
but
yeah
I
agree
with
that
priority.
It's
a
it's
a
good
one.
Had
lots
of
value
it'll
be
really
a
fun
thing.
You
get
one
of
the
highest
up
votes,
GG
you'll,
be
sort
of
finishing
off
there
and
we'll
be
pretty
stoked.
B
E
C
E
B
E
C
Yeah
that
makes
a
lot
of
sense.
Okay,
so
back
to
the
sheets,
wherever
this
box
is
it's
in
one
place:
okay,
the
next
issue:
this
is
the:
how
to
transfer
project
with
the
container
registry
enabled.
This
is
another
really
popular
issue
for
us.
33
up
votes,
a
lot
of
negative
customer
sentiment
about
people
that
are
trying
to
transfer
a
project
and
then
are
blocked
from
doing
so
once
the
container
registry
is
enabled
they
just
receive
it.
C
C
B
A
B
A
I
think
that's
exactly
what
he's
finding
is
that
the
way
that
the
images
are
created
is
it.
You
know
the
hashing
and
digests
that
are
created
would
change,
and
that
certainly
would
break
things,
but
yeah
that
would
take
investigation
I'm
guessing
that
is
the
root
of
the
problem.
Is
that
it's
dealing
with
the
way
that
the
image
itself
is
constructed.
Yeah.
B
C
B
C
Sorry
again,
I'm
really
interested
in
and
for
us,
as
a
team
figuring
out
this
made.
This
makes
sense
and
really
what
we're
saying
is
what
is
a
registry,
and
how
does
it
move
between
projects?
Is
it
transferable?
What
are
the
qualities
of
that?
Some
I
think
the
reason
I
bring
up
this
issue
now
is
exactly
for
that,
so
we
could
talk
about
it
and
figure
out
what
what
should
the
desired
behavior
be,
and
how
can
we
plan
for
that?
C
A
Maybe
there
was
an
issue
for
doing
sort
of
the
investigation
that
was
part
of
that
milestone
which
led
to
doing
the
work
in
this
milestone.
So
I
don't
know
if
we
wanted
to
follow
that
pattern
at
all
and
kind
of
set
this
one
up
like
one
or
two
milestones
ahead
of
time,
to
assign
to
an
engineer
to
take
a
closer
look
at
that.
C
Makes
sense
to
me
I
just
actually,
but
it's
really
interesting.
You
bring
that
up,
because
today,
in
the
product
meeting,
they
were
talking
about
a
product
discovery
milestone
where
you
will
go
and
try
and
basically
do
exactly
what
you
just
said,
try
and
find
out
as
much
information
as
we
can
you
bill
towards
a
prototype
and
then
in
the
following
milestone
you
built
towards
something
that's
more
more
of
an
actual
feature,
not
just
a
prototype.
B
C
Maybe
if
we
collect
that
data
and
then
maybe
display
it
in
the
UI
I
thought
this
could
be
a
nice
win
for
our
users,
who
are
having
trouble
with
things.
But
you
know
identifying
which
images
are
there,
as
we
can
give
them
some
extra
metadata
if
I
wanted
to
get
open
it
up
to
feedback,
and
if
you
think
this
is
useful
or
any
questions.
B
Yeah
I
think,
from
my
perspective,
this
sort
of
falls
into
the
sort
of
value
adds
for
somewhat
simple
value
adds
that
we
could
do
simple.
I,
don't
need
simple,
as
in
terms
of
engineering
effort,
that
I
just
mean,
like
the
sort
of
basic
level
things
that
we
could
add
to
help.
People
feel
a
little
happier
with
this
particular
product
offering
and
I
think
there
are
a
couple
of
other
issues
we
have
floating
around
for
that
as
well.
So
yeah
this
seems
like
a
reasonable
one.
B
Dad
I
think
we
start
looking
at
getting
responses
from
API,
the
docker,
a
distribution
registry,
okay,
API
and
then
sort
of
storing
them
in
some
way
I'm.
In
order
to
be
able
to
do
this
or
just
returning
them,
and
that
would
end
up
being
similar
to
the
package
list.
We
have
right
now,
which
you
know
you
can't
sort
and
it's
pretty
limited
in
some
ways.
So
yeah
I
think
this
one
seems
fine
for
that.
Okay,
thanks
Neil.
C
That's
an
interesting
one:
I
actually
wanted
to
talk
to
Steve.
You
and
I
had
spoken
about
this.
Maybe
a
couple
of
weeks
ago
about
NPM.
We
don't
allow
users
to
publish
NPM
packages
to
or
or
maven
for
that
sense
to
the
group
level.
We
will
we
allow
for
pulling
from
the
group,
but
not
necessarily
pushing
to
the
group
I
wanted
to
get
a
sense
from
you,
Steve
and
maybe
Dan
like.
Do
you
think
that
we
should
allow
that?
Is
that
something
that
you
could
see
being
useful
and
and
if
so,
is
it
possible?
A
B
I
think
from
my
sense
of
it
is,
is
that
we
are
taking
this
protocol
and
mapping
mapping
it
on
to
our
workflow
and
that's
kind
of
why
we
say
you
want
to
like
publish
to
groups
or
whatever
so
I
think
from
a
customer
usage
standpoint
and
Graeme
from
wrong
team.
This
is
certainly
something
even
like
that
you
know
I,
think
for
my
customers.
It
standpoint
it
matches
up
to
how
a
customer
may
be
using
gitlab,
whereas
it
may
not
match
up
to
the
way.
B
Maven
was
intended
to
work
in
terms
of
how
things
are
published,
and
so
from
that
standpoint,
I
think
this
sort
of
falls
into
the
the
broader
sort
of
question
of
how
how
gitlab
wants
to
implement
these
protocols
as
it
overlays
on
top
of
what
our
tool
set
is
so
I
think
that's
kind
of
where
this
is
I.
Think
it's
more
of
a
like
hey.
You
know
how
we
currently
publishing.
B
Is
it
possible
just
to
add
an
endpoint,
and
it
will
be
fine,
and
that
will
just
take
it
some
investigation
around
what
metadata
is
stored
with
the
packages
we're
publishing
and
whether
we
can,
instead
of
identify
them
at
the
group
level,
in
a
way
that
isn't
sort
of
totally?
You
know,
contrary
to
the
way
we're
already
doing
it
for
for
a
project.
C
Okay,
that
makes
sense
right.
I
I
tend
to
agree
with
Steve
that
it
doesn't
necessarily
make
sense
to
push
maven
packages
to
the
group
level,
but
then,
when
I
think
about,
does
it
make
sense
to
put
images
and
tags
to
the
group
level
to
be
able
to
push
them
and
make
maybe
makes
a
little
more
sense,
because
you
may
share
common
images
across
projects,
whereas
a
package
feels
more
like
project
dependent
project,
encode
dependent,
yeah.
B
I
mean
I
can
see
an
organization
from
a
group
level
kind
of
having
one
team
that
publishes
packages
at
and
and
everyone
in
the
organ
in
that
sort
of
team
uses.
It
I
think
this
probably
could
do
with
some
investigation
instead
of
user
stories.
Yeah
I
think
I
think
if
we
struggle
to
come
up
with
user
stories
is
not
much
point,
invest
in
spending
a
bunch
of
time
investigating.
C
It
right
now
this
was
this-
is
how
apply
I
ever
since
Steve
and
I
talked
about
it
for
NPM
I've
been
thinking
about
it,
and
so
I
wanted
to
take
the
chance
to
bring
it
up
with.
This
may
be
an
issue
okay.
Well,
we
live
two
more
minutes.
I'd
only
I
have
one
more
issue
and
it's
be
I'm,
not
sure
if
we
could
do
it.
C
B
I
think
we'd
be
limited
in
terms
of
we
don't
have
the
notifications
API
set
up
right
now
so,
like
we're,
not
gonna
know
that
the
baseline
image
is
updated
right
so
like
we
would
need
some
way
to
be.
Have
that
information
push
to
action.
Yeah
we're
still
me
I,
can't
even
talk
anymore
pushed
to
us
in
order
to
then
say,
run
a
pipeline
again
to
rebuild
the
image
right
and
so
I.
A
C
A
B
Yeah
and
I
think
I'd
only
want
to
be
I,
don't
want
to
be
careful
about
if
we're
doing
some
sort
of
POC.
With
a
notifications
API
that
we
have
pretty
clear
on
what
the
investment
is
in
time
for
people,
because
we
do.
We
are
currently
planning
future
sort
of
steps
for
the
container
registry
as
a
whole
and
so
that,
if
it
might
be
just
sort
of
it,
may
be
really
helpful.
I'm
not
saying
it
won't
be,
but
it
might
not
be
useful
going
forward.
C
A
Yeah,
the
only
thing
was
just
mentioning
that
the
whole
subgroup
packages
issue
I'm,
not
so
sure
if
it
will
make
12:1
now
cuz,
it's
still
waiting
on
I
mean
the
maintainer
review.
I,
don't
think,
has
really
started
yet
so
I'm
not
like
I
know
that
you
know.
If
you
look
at
that
older
calendars,
where
the
code
cutoff
was
on
the
seventh
we've
passed
that
date,
but
I
don't
know
if
that's
still
a
thing,
but
I
guess
we'll
see.
A
A
A
That
I
wanted
to
say
Gigi.
If
you
have
any
questions,
you
know
I'm
yeah,
the
other
back-end
engineer
in
package,
so
feel
free
to
hit
me
up
on
slack
if
I'm
not
online.
At
the
same
time
as
you
and
you
know,
happy
to
help
with
anything,
I've
also
only
been
here
about
a
month
in
a
week,
so
going
through
just
went
through
the
same
things
you're
going
through
thanks.
B
Getting
getting
through
your
week
with
their
first
week,
onboarding
is
really
important.
I
would
encourage
you
not
to
get
into
working
on
code
yet
give
yourself
a
minute
to
get
through
that
stuff
and
then
sort
of,
as
you
start
picking
out
that
first
ticket
that
we
have
in
the
issue.
Excuse
me
that
we
have
in
the
list
I
think
you'll
get
some
help.
You'll
have
questions
and
a
lot
of
things
will
start
making
sense
quicker.
So
don't
stress
about
it
too
much.
There's.