►
From YouTube: GitLab 15.6 Kickoff - Configure:Configure
A
A
They
are
all
amazing
people,
and
especially
I
would
like
to
mention
one
thing
which
Timo
is
actually
the
maintainer
of
data
from
GitHub
provider
and
for
his
work
within
gitlab
and
on
the
provider.
He
was
considered
to
be
the
most
valuable
Community
contributor
back
in
March
this
year,
as
a
result
that
we
hired
these
three
amazing
people.
Our
number
one
goal
is
to
support
their
successful
onboarding.
A
A
This
enables
our
two
biggest
design
topics,
because
we
are
working
together
with
the
realistes
theme
on
kubernetes
Integrations
within
the
environments
page
on
the
design
side,
we
have
a
topic
to
solidify
the
user
Journey
for
managing
for
providing
these
insights
of
kubernetes
within
the
environments
page
and
to
design
how
it
should
look
like
as
well.
So
these
are
the
following
Milestones
work,
but
we
are
already
working
on
it
and
preparing
that.
A
The
second
goal
is
to
provide
an
infrastructure
visibility
toggle.
It
seems
like
a
simple
thing,
but
actually
other
teams
are
working
on
this
for
several
months
and
we
are
the
last
one
here
who
have
to
implement
it.
This
will
allow
users
to
hide
the
infrastructure
menu
from
the
main
menu,
and
hopefully
it
will
improve
the
user
experience
for
users
who
don't
need
it
and
followingly.
A
Followingly
a
steamer
joint.
Finally,
in
gitlab
we
want
to
migrate
away
from
GitHub
to
gitlab
we
deter
from
provider.
This
will
be
led
by
Timo
it's
his
primary
project.
This
should
allow
us
to
have
better
owners
of
the
project.
Hopefully
we'll
be
able
to
contribute
more
we'll,
be
able
to
build
stronger
relationships
with
the
Community
First.
It
will
be
much
easier
for
us
to
track
progress
and
feedback
on
the
project
from
the
community
within
gitlab.
Then
it
was
in
GitHub.
A
The
next
two
items
are
stretch
items
for
us,
one
is
to
support
templating
tools
to
support
and
improve
our
support
of
Han.
A
month
ago,
we
released
an
alpha
version
of
ham
support
with
the
agent,
and
the
next
step
would
be
to
add
environment,
support
to
that.
That
means
that
today,
there's
a
limitation
that
users
have
to
copy
the
whole
hem
chart,
together
with
values,
file
from
one
environment
to
the
next,
and
this
means
a
huge
amount
of
code
duplication.
While
one
of
the
features
is
that
they
have
something
called
values
yaml.
A
A
A
This,
these
are
the
Focus
topics
for
us.
The
reason
why
the
cube
CTL
issue
is
not
mentioned
on
the
goals,
because
we
are
here
mostly
waiting
on
the
info
team,
who
is
who
are
doing
an
amazing
job
to
support
us,
but
it
should
land
a
month
in
a
month.
So
this
these
are
our
goals.
If
you
have
any
questions,
please
reach
out
to
us
in
this
configure,
Channel
or
in
any
of
the
issues
playing
on
the
planning
issue.
Thank
you.