►
From YouTube: Package: Post customer meeting thoughts
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
Hi
team
I'm
trying
something
new
today,
so
after
a
recent
call
this
morning
with
a
large
customer,
a
gitlab.com
customer,
I
thought
that
I
would
record
some
afterthoughts
from
the
conversation,
so
a
few
things
that
they
brought
up.
They
were
specifically
interested
in
some
of
the
maven
features
that
we're
working
on.
A
They
were
following
closely
the
issue
to
add
in
the
setting
to
allow
or
disallow
duplicate,
maven
uploads,
and
it
was
interesting
because
one
person
on
their
team
was
arguing
that
or
stating
that
they
would
really
like
to
prevent
duplicate,
uploads
but
sort
of
the
architect
at
the
customer
was
saying
that
this
is
actually
maven,
expects
that
you
upload
duplicates,
and
even
when
we
add
this
setting,
even
though
they
could
see
it
being
useful,
they
will
advise
their
teams
not
to
use
it.
Although
they
understand
that
several
of
them
may.
A
We
also
talked
through
a
maven
bug
that
we're
working
on
with
how
dependencies
are
resolved
by
version
number,
and
then
we
talked
through
just
a
few
more
road
map
items,
so
they
expressed
interest
in
a
helm
chart
registry,
and
this
was
interesting
because
I
brought
up
the
idea
that
you
could
use
the
container
registry
to
store
helm,
charts
with
helm,
v3
and
that's
kind
of
what
we're
pushing
everyone
towards.
A
We
actually
have
some
documentation
that
I
know
suzanne's
working
on
right
now
that
I'm
supposed
to
be
testing,
and
they
were
the
architect
at
this
customer
was
saying.
Well,
that's
maybe
helm
is
trying
to
move
away
from
that
and
that
that
hasn't
been
as
effective
and
part
of
the
reason
has
been.
Is
that
docker
didn't
accept
the
changes
upstream
to
expand
the
metadata
the
way
so
that
we
can
distinguish
between
home
charts
and
images,
which
is
that
one
of
the
problems
we're
having
now
and
why
that
future
development
is
blocked.
A
So
it
sounds
like
there's
some
validation
of
that
that's
needed.
If
that's
indeed
the
direction
helm
is
moving,
then
we
would
probably
need
to
change
the
direction
that
we're
going
as
well.
A
A
They
also
expressed
interest
in
the
go
proxy.
They
had
some.
You
know
they
were
saying
that
they're
very
interested
in
this
feature
and
that
it
would
be
very
useful
for
them
and
they
specifically
mentioned
the
their
desire
to
use
vanity
urls
versus
having
to
use
the
you
know
the
full
gitlab.com
api
slash
packages
url
overall,
it
was
a
good
call.
I
think
you
know
there.
It
was
really
interesting
to
see
how
the
different
developers
at
this
customer
interact
and
how
well
informed
the
architects
and
the
admin
administrators
of
gitlab
are
at
this.
A
Custom
are
of
what's
going
on
in
our
stage,
so
it
was
really
interesting
and
exciting
and
as
a
result,
we
shared
with
jr
some
of
the
links
to
some
of
the
push-pull
mirrors,
and
it
was
a
good
chance
to
like
re
step
in
and
talk
to
this
customer
and
give
them
some
updates.