►
From YouTube: Weekly Package Meeting 06-11-19
Description
- Upcoming milestone 12.1
- Discussion about the future of the container registry
- We started a support knowledge base for troubleshooting issues
A
B
You
Tim
so
I
would
like
to
officially
welcome
Nick
Kipling
is
our
first
front-end
engineer,
Nick
welcome.
We
introduced
you
last
week
Nick,
but
you
weren't
here.
So
this
is
kind
of
the
official
announcement
and
I
borrowed
the
little
snippet
from
the
front-end
department.
Call.
It's
asked
Nick
to
please
introduce
himself.
Tell
us
a
little
bit
about
your
front-end
engineering
background,
your
favorite
framework
and
your
favorite
IDE.
C
I've
run
yes,
so
I'm
Nick
I'm
joining
the
front-end
team
package,
so
I'm
really
excited
about
that.
Previously
I
worked
for
a
company
here
in
the
UK
just
up
the
road
in
Derby
called
common
time
where
I
worked
as
a
mobile
developer
and
we
used
Cordova
to
build
our
mobile
apps
and
we
had
a
product
that
sat
on
top
of
Cordova.
C
So
to
begin
with,
when
I
first
started,
it
was
very
much
using
the
product,
but
it
very
quickly
moved
away
from
that
and
we
moved
to
using
stock
Cordova
with
a
custom
framework
over
the
top
of
it,
which
is
built
into
JavaScript
and
based
off
of
web
components,
which
I
essentially
basically
built,
and
then
the
rest
of
the
developers
here
used
that.
So
we
would
build
mobile
apps
for
lots
of
different
customers,
and
there
was
quite
a
it
wasn't
just
front-end.
It
was
quite
as
a
full
stack
position.
C
A
bit
of
experience
with
that,
although
not
with
rails
specifically
and
yeah,
so
I
did
that
for
four
and
a
half
years
with
comm
time,
and
that
was
so.
That
was
fun
that
was
interesting.
I
felt
that,
towards
the
end,
I
wasn't
really
learning
too
much.
You're
progressing
and
I
wasn't
really
being
challenged
that
much.
So
that's
why
I've
decided
to
try
get
out
that
hopefully
become
a
better
developer
and
yes,
like
the
overwhelming
amount
of
information
that
I've
had
to
take.
C
You
know
the
last
week
and
a
half
yeah
that
there's
a
lot
to
learn
so
it'll
be
a
while
before
I'm
in
the
same
position.
Here,
that's
in
terms
of
like
favorite
framework
I
guess
it's
probably
reacts
just
because
that's
the
one
that
has
the
most
experience
with,
but
I
prefer
but
I
like
any
sort
of
decorative
front-end
room.
Very
much
so
view
will
be
absolutely
fine
as
well
and
I've
been
sort
of
picking
that
up
the
last
month
or
so
just
trying
to
get
to
grips
with
that
and
yeah.
It
feels
fine.
C
B
A
A
So
we're
looking
at
for
this
team,
the
publishing
npm
from
a
subgroup,
the
changing
the
container
industry
to
a
column
in
that
information
and
adding
a
timestamp
and
updating
the
500
error
page
for
the
container
container
registry
and
updating
an
API
response
code.
Everything
seems
straightforward.
No
questions
cool
like
I
like
that,
and
so
the
next
one
is
I,
opened
up
this
issue
and
it's
linked
there
in
the
doc
to
talk
about
the
maturity
path
for
the
container
registry.
It
feels
like
we're
at
a
little
bit
of
a
crossroads.
A
I
started
going
through
issues
and
thinking
about
how
can
we
add
in
sort
it
to
the
container
registry
page
and
I,
see
that
we're
blocked
because
we're
not
currently
storing
data
for
for
any
of
the
items
from
the
registry
and
then,
when
I
start
to
think
about
more
advanced
features
that
are
coming
like
expiration
and
retention
policies
and
it's
auditing
and
security
security
tests
scanning.
All
of
those
things
require
that
we
store
data
that
we
can
access
it
and
do
something
with
it
and
provide
some
user
experience
for
it.
So
I
opened
up
this
issue.
A
That
is
a
a
summary
of
the
discussions
that
have
been
had
before
most
of
our
time
here
at
get
lab
between
Camille
and
Gregor
and
Dimitri
and
aggregated
in
one
place
in
that
issue,
and
the
idea
is
to
answer
the
question:
is
our
current
implementation
of
the
container
registry?
Will
it
scale
to
the
future
features
that
we
want
for
it?
If
so,
what
do
we
have
to
do
to
achieve
that,
and
if
not,
what
does
that
mean?
Does
that
mean
that
we
build
our
own?
E
Don't
think
any
of
us
right
now
have
the
ability
to
make
that
call.
So
you
know
whenever
we
get
to
make
that
call
we're
probably
one
of
us
that
makes
the
decision
around
which
direction
we
want
to
go
there.
But
you
know
I,
don't
think
we
have
enough
information
right
now,
so
I'm
gonna
follow
up
today
with
with
those
three
people
and
try
and
organise
a
chat
with
them
this
week
about
about
the
container
registry
where
it's
at
and
and
they
thoughts
on
moving
forward.
A
From
that
makes
sense
to
me
and
from
the
product
perspective
I'm
about
I'm,
trying
to
make
a
push
for
user
interviews,
both
with
internal
customers
and
external
customers,
to
hear
about
how
they're,
using
the
container
registry
today
what's
not
working
what
they.
You
know
what
they
see,
that
mature
container
registry
product,
looking
like
so
I'm
going
to
throw
together
questions,
I'll
share
them
in
the
package.
Channel
and
I'd
love
to
get
feedback
from
all
of
you.
A
I
would
love
to
get
all
of
your
opinion
on
those
questions
and
add,
add,
as
developers
and
users
of
the
product.
What
do
you
think
would
be
valuable
to
know
from
users
as
we
consider
building
this
out
in
the
future
as
well,
so
that'll
be
something
from
a
product
perspective,
I'm
working
on
user
interviews
as
well
as
what
are
the
features
that
we
will
need
to
build
and
support
in
the
future?
And
what
do
those
features
look
like
and
make
ensuring
that
those
issues
are
groomed.
C
A
A
E
Sorry
to
interrupt
him,
I
just
wanted
to
call
out
that
Sara's
been
working
really
hard
on
getting
to
pipelines
working
for
our
Indian
package
history
and
that
work
is
awesome
and
very
much
appreciated.
Thank
you.
So
much
for
doing
it,
Sara
I
did
see
that
she
got
a
couple
of
like
responses
to
the
mud
requests
in
the
last
overnight.
I
think
so.
I
don't
know
if
you
need
some
help
Sara,
but
if
you
want
to
reach
out
to
my
cell
14,
we'll
do
the
best
we
can
to
to
help
work
through
those.
E
D
A
A
So
I
just
started
this
Google
Doc,
not
knowing
of
a
better
place
to
to
put
it
to
start
capturing
what
issues
how
we
resolved
it
if
there's
any
way
to
reproduce
it
and
then
detailing
any
resolutions
and
I've
I
found
this
helpful
I've
been
able
to
go
back
and
forth
with
some
engineers
on
our
some
users
saying
how
do
I
delete
items
from
my
registry
and
I
already
have
the
pre
canned
response?
I
have
some
user
generated
scripts
that
I
could
share
as
well
so
more
of
an
FYI?
A
Any
questions
or
concerns
about
that
John
or
Darby.
Have
you
seen
other
teams
do
implement
something
like
this
better
or
is
there
a
better
process
that
we
should
be
following
other
than
a
Google
Doc
I
have
not
seen
anything
else
like
this
I
think
this
is
great
I
I
think
what
we
do
on
release
right
now
is
is
probably
more
tribal
knowledge
ish
than
documented.
So
this
might
be
a
good
pattern
to
follow.
I
guess,
I
think.