►
From YouTube: GitLab 13.11 Kickoff - Configure:Configure
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
Hello
to
the
1311
configure
group
release,
kickoff,
recording,
I'm
victor
knight,
the
product
manager
of
the
configure
group
and
here's
with
me,
maria
rafni,
the
product
designer
of
the
group,
and,
let's
see
what
we
plan
to
work
on.
As
you
can
see,
we
started
to
use
gitlab
for
our
roadmap
view
and
we
think
that
this
presents
very
well
our
plans
for
the
next
milestone
and
ongoing
milestones
as
well.
A
First
of
all,
we
are
slowly
finishing
the
connection
between
gitlab
and
the
agent
setup
and
all
the
the
necessary
works
that
are
required
to
provide
the
ci
tunnel
for
the
agent,
and
we
want
to
start
working
on
that.
But
before
a
country
we're
describing
the
roadmap,
there's
one
very
important
note.
I
have
to
make
that
this
list
is
not
priority
ordered.
Unfortunately,
that
is
not
possible
with
the
with
this
epic
view.
So
this
is
just
ordered
by
due
date
and
as
a
result,
we
are
going
to
speak
about
the
priorities
lubricator
so
anyway.
A
A
Another
topic
we
are
going
to
work
on
is
auto
devops.
We
want
to
run
a
design
sprint,
and
we
speak
about
that.
A
little
bit
later,
we
have
some
end-to-end
tests
outstanding
end-to-end
tests
for
qa
around
the
agent
that
we
want
to
finalize
in
the
coming
milestone,
and
then
we
have
an
issue:
that's
already
ongoing
in
development
in
the
secret
management
area,
with
the
group
level,
environment
variables
that
can
be
attached
to
specific
environments
and
a
strategic
goal
again
related
to
sequence.
A
A
The
following
epics
that
we
are
working
on
are
related
to
the
agent.
We
have
various
user
interfaces
that
we
would
like
to
ship
that
provide
a
simple
registration
flow
for
the
agent
or
provide
basic
insights
around
the
agent
status.
Whether
the
connection
was
successful
or
if
there's
an
error,
we
still
have
some
ongoing
work
around
the
gitlab.com
deployment.
A
Actually,
the
majority
of
these
issues
even
though
seem
to
be
finished
in
14.0.
That's
not
true.
We
just
don't
have
the
issues
that
we
move
on,
for
example
with
the
management
with
the
ci
tunnel.
We
know
that
it
will
require
some
infrastructure
changes
as
well
on
gitlab.com,
and
we
are
almost
sure
that
we
won't
be
able
to
ship
all
of
it
in
13.11..
A
A
A
We
want
to
ship
the
telephone
module
registry
thanks
to
the
amazing
work
of
the
package
team.
They
might
be
able
to
ship
relatively
valuable
portion
of
our
plans
in
1311,
but
there
will
be
still
ongoing
work
afterwards
and
we
have
planned
to
work
even
more
later
on
that
around
the
triform
registry.
But
that's
really
about
the
rule.
That's
not
for
the
next
milestone.
A
B
Thank
you.
So.
The
first
item
is
a
very
small
design
enhancement
to
enhance
the
agent
listing
under
the
operations
kubernetes
menu
with
information
that
will
be
useful
at
a
glance
for
the
user.
That
is
inspecting
the
list.
Information
like
whether
the
agent
is
connected,
so
the
connectivity
status
when
it
lasts,
communicated
with
git
lab.
B
The
next
item
is
working
on
the
autodesk
bob's
vision,
so
working
on
the
next
steps,
which
includes
mainly
devising
a
workshop
for
the
team,
so
an
asynchronous
workshop
or
design
sprint
for
coming
up
with
the
solution
of
our
devops.
B
This
will
include
jumping
to
the
fourth
item,
the
documentation
of
the
jobs
to
be
done
and
reviewing
of
the
interviews
around
well,
not
kubernetes,
necessarily
but
autodevops
as
well.
That
victor
has
run
so
that
we
can
inform
the
team
about
the
use
cases,
the
problems
our
customers
are
facing
and
then,
during
the
workshop
solutionize
towards
the
main
jobs
to
be
done.
B
Moving
on
the
next
one
is
the
jobs
to
be
done
for
the
for
our
code
category,
it's
along
with
you,
so
it's
time
to
add
them
to
our
configure
pages
so
victor
and
I
will
work
on
the
main
jobs
to
be
done,
especially
around
terraform,
well
around
our
infrastructure
as
code
usage
and
the
same
thing
we're
going
to
start
to
do
with
kubernetes
management.
B
So
these
two
are
laying
the
foundations
of
our
categories.
The
next
two
items
are:
oh
well,
the
the
first
one
is
a
foundations.
B
A
A
A
Some
agents
related
work,
which
is
to
define
some
conventional
labels
that
are
being
applied
to
the
cluster
when
the
agent
does
some
kind
of
some
any
deployments,
whether
it
be
full-based
or
push-based,
and
again
we
have
some
minor
work
around
providing
new
names
for
agent
tokens.
This
is
because
we
just
added
the
possibility
to
add
names
to
the
tokens
to
have
them
more
descriptive
and
we
have
to
default
to
new
names
there.
A
A
As
a
result,
the
engineers
could
not
take
it
as
deliverable,
but
actually
we
try
to
communicate
it,
countries
that
this
is
very
important
for
not
just
for
the
team
but
for
the
whole
company,
and
we
want
to
work
on
it
as
much
as
possible
and
one
we
want
the
engineers
to
have
time
dedicated
to
to
work
together
with
us
on
autodevops.
A
A
I
spoke
a
lot
already
about
the
content
of
each
of
the
epics,
and
actually
all
the
issues
here
that
are
considered
to
be
stretch
are
related
to
some
of
the
epics
already
presented
before.
So
I'm
not
going
to
go
into
details
there.
These
are
our
top
priorities.
I
hope
it
highlights
very
well,
and
I
hope
that
you
managed
to
relate
them
to
the
epics
as
they
were
presented
before.
A
So
this
was
the
release
kickoff
from
the
configure
team.
If
you
have
any
questions,
please
reach
out
to
us
on
the
s
configure
slack
channel.
Thank
you
very
much.