►
From YouTube: GitLab 13.1 Kickoff - Enablement:Distribution
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
I'm
Larissa
Lane
product
manager
for
distribution.
Welcome
to
the
thirteen
point
one
kickoff
video
in
the
previous
milestone
13.0.
We
met
some
major
milestones,
including
minimally,
requiring
Postgres,
11
and
defaulting
to
chemo
for
our
web
server
in
13.1,
we'll
be
doing
a
combination
of
shifting
our
focus
to
some
new
major
areas
of
work
and
also
taking
some
learnings
from
the
past
three
months
and
making
some
improvements.
A
A
A
A
A
A
A
Developer
guidelines
for
contributing
to
the
home
charts,
so
one
thing
that
we
see
a
lot
of
is
we
get
a
lot
of
really
great
merge
requests.
You
add
features
or
support
for
configuration
in
the
omnibus,
but
not
as
much
for
their
home
charts,
and
sometimes
there
is
a
lag
between
adding
support
for
something
you
know
me
bus
and
then
adding
that
support
into
the
home
charts.
We
want
to
make
that
as
easy
as
possible
for
the
community
and
for
other
teams
at
gate
lab.
A
And
next
we
have
been
doing
some
investigation
into
options
for
encrypting
passwords
that
are
stored
in
the
gate,
lab
configuration
files,
the
one
that
we've
heard
the
most
requests
for
is
the
old
app
username
and
password.
So
we
have
thanks
to
DJ.
We
have
three
proof
of
concepts
proposed
in
this
epic
now
and
in
thirteen
point
one,
we
will
be
starting
work
on
the
first
proof
of
concept,
so
I'd
love
to
get
feedback
on
this
one
as
well.
We
have
the
three
proof
of
concepts
linked
here
and
I.
A
A
Next
up,
we
would
like
to
improve
our
support
for
using
kms
encryption
for
s3
object
storage
using
the
charts,
so
this
issue
has
been
blocked
by
some
other
work
that
we
need
to
do.
We
still
need
to
investigate
whether
we're
completely
unblocked
on
this.
If
we
are,
we
was
working
on
it
in
the
13.1
milestone
if
we're
still
blocked
it,
it
may
end
up
being
more
like
the
13.2
milestone
and
finally,.
A
A
So
we've
classified
the
home
chart
install
as
viable.
We
have
an
epoch
that
defines
what
it
would
take
to
move
it
to
complete
and
we
have
a
good
set
of
recommendations
in
that
epoch.
We
also
have
this
epoch
of
what
it
would
take
to
to
reach
the
loveable
maturity
level,
and
this
is
something
we
haven't
defined
very
well.
Yet
we
are
seeking
input
from
the
community
on
what
what
you
think
it
would
take
for
the
cloud
native
install
to
be
considered
loveable
and
over
the
next
several
weeks
in
within
the
13.1
mile.