►
From YouTube: Release Stage Community Office Hours - August 2022
Description
Recording of office hours
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/368440
Meetup: https://www.meetup.com/gitlab-virtual-meetups/events/287756492/
A
I
wanted
to
get
started
hello,
everyone.
This
is
the
august
version
of
the
release
stage
community
office
hours
call.
My
name
is
chris
bolani,
I'm
the
product
manager
for
the
release
stage
group
here
at
gillab
and
let's
start
with
intros.
Actually,
if
that's
all
right
with
everyone,
so
let's
start
with
the
get
lab
team
andrew.
Do
you
want
to
kick
us
off
and
then
maybe
you
could
call
on
the
next
person
to.
D
E
Hey
I'm
vlad,
I'm
back
an
engineer
here
on
the
release
team.
I'm
super
excited
about
this
office
hours.
I
had
a
really
great
experience
with
community
contributions
before
yeah
and
I'm
the
first
one
located
in
europe
in
amsterdam,
not
in
the
us
and
definitely
not
in
toronto.
Maybe
alan
you
can
go
next.
F
A
H
A
C
I
J
K
L
A
M
M
A
A
As
you
can
see,
a
lot
of
most
of
our
team
is
actually
on
this
call
right
now
and
it's
great
to
see
just
everyone
who
meet
all
of
you,
and
it's
also
really
cool
for
me
to
see
everyone
just
where
everyone's
calling
in
from
because
our
our
own
team
is
we're
all
over
the
place
and
it's
nice
to
see
everyone
also
dialing
in
and
wanting
to
contribute.
So
again,
so
this
is
contributor
office
hours
for
the
release
stage,
who
has
joined
an
office
hours
before
anyone
get
lab.
A
Okay,
see
a
few
hands
a
few
of
us,
okay,
great,
and
so
those
of
you
that
are
new
that
haven't
been
really
excited
to
have
you,
those
of
you
that
have
been
to
office
hours.
This
might
be
a
little
bit
different
because
we're
we're
the
release
team,
we're
focused
on
the
release
stage
and
the
release
group
and
features
related
to
that
and
I'll
go
into
a
little
bit
about
what
that
is
in
a
moment.
So
we'll
be
talking
mostly
about
that.
A
We
have
a
lot
of
labels
and
it's
related
to
community
contributions
and
how
to
how
to
how
to
best
contribute,
we'll
talk
about
what
those
mean,
and
then
we
have
a.
We
have
a
walk
through
of
some
of
our
or
of
one
of
our
epics.
That
we've
been
talking
about
really
recently
as
a
team
that
we
could
use
a
lot
of
your
help
on
and
then
a
few
other
things
just
related
about
community
contributions
and
developing
in
general.
So
any
questions
before
we
get
started.
A
Does
that
sound
good
to
everyone
all
right?
So
what
does
group
release
do
so
we're
the
release
stage
here
at
get
lab?
There
are
many
stages
at
gitlab,
we're
the
we're
the
group
and
team
that
focuses
on
helping
our
customers
deploy
software
to
production,
so
releasing
software
deploying
software
to
different
environments
and
then,
eventually,
with
the
goal
of
helping
helping
ship
code
to
productions
and
to
gain
value
for
your
own
users
and
applications
that
you're
developing
it
looks
like
we've
got
one
more
entering
our
direction.
A
Page
has
a
lot
of
has
that
mission
statement
there
and
also
a
lot
more
detail
about
what
that
means
and
where,
where
we're
going
in
terms
of
our
features
and
product
areas,
so
I
definitely
encourage
you
to
take
a
look
there,
but
just
to
give
you
a
sense
of
what
categories
and
what
types
of
features
we
build.
I've
listed
a
few
of
those
here
in
the
agenda.
You
can
see
that,
but
environment
management
is
one.
That's
one
we're
focusing
on
actually
pretty
heavily
at
the
moment.
A
We
have
a
future
flag
feature
and
then
continuous
delivery,
so
get
lab.
Has
a
world-class
ci
cd
offering
we
we
work
on
and
make
progress
on
the
cd
part
portion
of
that,
so
that's
quick,
high
level
about
release
stage
and
again
more
information
on
the
direction
page
and
also
in
future
office
hours.
If
you
have
any
more
questions
or
even
later
any
more
questions
about
what
that,
what
we
do,
what
that
is.
E
E
A
H
J
A
E
E
One
of
the
things
to
notice
here
is
that
I'm
not
looking
at
the
gitlab
project,
I'm
looking
at
the
group
level
gitlab.org,
because
we
have
multiple
projects.
For
example,
in
our
team
we
have
a
few
project
projects
dedicated
to
kubernetes
deployments.
We
have
released
cli
and
many
more.
So,
if
you
just
look
at
the
gitlab
project
itself,
you
will
miss
some
of
these
issues,
something
about
these
labels.
E
So
if
you
contribution
for
the
first
time-
and
you
are
not
interested
in
interested
in
fixing
some
particular
bug
which
annoys
you
specifically,
I
would
recommend,
starting
with
this
label
seeking
community
contributions,
because
every
issue
you
can
find
here
this
all
of
this
was
created
for
the
epic,
but
let's
take
some
old
one.
It
will
have
something
we
even
have
a
bot
which
suggests,
like
please
add
the
some
description
which
actually
tells
you
how
to
implement
this
feature.
E
E
Sometimes
you
don't
even
need
to
set
up
the
gdk
or
it
will
be
a
really
small
fix
like
robocop,
it's
basically
a
linter
for
the
ruby
robocop
fix,
which
usually
doesn't
require
you
to
understand
a
whole
lot
of
about
like
architecture,
how
we
build
the
data
structures
and
so
on.
So
they
will
be.
Also
kind
of
these
issues
are
also
good
for
new
contributors.
E
E
So
if
you
want
some,
you
can
look
at
this.
We
only
have
14
issues
on
the
whole
gitlab,
but
yeah
take
a
look
if
you're,
interested
and
then
low
hanging
fruit
is
also
kind
of
a.
I
don't
know.
The
idea
behind
this
label
is
that
it's
some
kind
of
a
product
win
which
doesn't
require
a
lot
of
effort,
so
you
can
take
a
look
at
this
as
well
and
then
accept
energy
quests.
The
release
group
actually
has
like
700,
I
guess
of
these
issues,
yeah
731,
so
they
are
less
ground.
E
E
We
have
some
of
these,
some
of
them
as
well
yeah.
Three
issues
here:
yeah
and
documentation,
documentation,
also
kind
of
easiest
part.
I
guess,
because
you
don't
need
to
set
up
a
development
environment,
you
can
just
go
and
edit
markdown
files.
We
have
a
really
good
linters
for
them.
So
if
you
kind
of
mess
something
up,
it
will
catch
like
broken
links
and
stuff
like
this
yeah
any
questions
on
labels
so
far.
A
H
N
Yeah,
so
I
just
recently
started
yeah.
I
just
recently
started
contributing
to
it
lab
and
it's
a
good
product
because
I
used
it
last
year
in
our
company,
so
I
just
started
contributing
to
the
documentation,
technical
documentation
and
the
beginners
page,
where
it
suggests
the
beginners
how
to
contribute.
N
So
I
added
two
three
lines
over
there
in
the
website
and
now
in
the
documentation
for
name
spaces.
We
didn't
have
separate
page,
so
there
was
epic
going
on
over
there,
so
they
wanted
to
separate
the
name
space
to
a
separate
page
once
the
page
got
separated.
So
I
wrote
the
whole
page,
the
content
of
the
whole
page
name
space.
So
the
next
target
is
to
contribute
something
to
go
like
instead
of
technical
writing.
So
I
was
looking
for
something
going,
but
most
of
the
stuff
are
in
gooby.
A
B
E
Yeah
so
yeah,
basically,
oh
yeah,
shooting
community
contributions.
Press
enter
so
you'll
find
some
issues
here,
or
you
can
also
just
see
the
project
names,
for
example,
container
registry.
You
can
go
to
the
project
itself
and
go
to
the
issues
here.
There
will
be
a
lot
more,
which
are
not
maybe
ready
for
the
community
contributors,
but
you
can
go
through
those
and
maybe
pick
something
you
are
interested
in
yeah,
okay,
yeah.
E
I
guess
I
will
kind
of
go
ahead
with
the
next
topic,
which
is
we
recently
we're
looking
how
we
can
actually
how
many
people
are
using
the
environments
functionality
of
the
gitlab,
and
we
realized
that
we
are
not
mentioning
it
in
many
many
places
where
we
should.
We
have
a
lot
of
examples
in
ci
documentation
in
ci
templates
in
project
templates,
where
there
is
some
kind
of
a
deploy
job,
but
we
don't
actually
use
the
gitlab
environments
in
the
deployment
functionality
only
just
using
cci
as
a
tool
to
execute
code.
E
E
I
we
even
thought,
maybe
about
creating
an
issue
for
every
single
fix,
but
I
in
the
end
decided
to
make
batch
kind
of
batched
all
the
changes
together,
and
I
will
use
those
issues
as
kind
of
an
example
how
you
can
quickly
quickly
work
on
the
some
yeah
on
some
issue
and
contribute
easily.
I
will
copy
this.
I
have
a
separate
window
where
I'm
logged
in
as
not
a
gitlab
team
member,
because
it's
how
you
will
experience
this,
you
can
just
go
into
the
just
open
this
link.
E
E
E
F
E
Yeah,
it's
just
to
add
the
environment
production
into
this
template
yep.
You
just
do
this
commit
changes.
Add
the
environment
to
hexa,
ci
template
always
add
the
change.
Log
or
maintainer
can
ask
you
to
do
that
when
they
will
be
reviewing
your
code,
but
edit
there
is
like.
If
it's
a
fix,
it
will
be
fixed
and
yeah.
You
can
google
some
other
changelog
labels
we
use
or
just
skip
it.
If
it's
just
your
first
contribution,
maintenance
will
suggest
you
how
to
fix
it
on
yeah.
E
I
also
was
trying
to
do
it
today.
If
you
see
the
similar
problem
with
it,
just
hanging
just
go
here,
I
don't
know
increased
from
here
should
work
yeah
honestly,
I
have
no
idea
why
this
takes
so
much
time.
Yeah
and
the
first
thing
you
will
see
on
the
emergency
quest
is
that
gitlab
both
will
go
into
it
and
suggest
you
how
you
can
actually
continue
working
on
it
if
yeah,
the
like
the
best
line
here,
is
gitlab
help.
E
E
Now
I
apparently
tagged
someone
and
they
will
need
to
respond
to
me
yeah.
So
this
is
how
it
works.
Also,
when
it's
ready
you
can
just
if
you
know
the
people,
you
can
just
enter
gitlab
bot
ready
with
a
username,
if
not
just
ready,
and
it
will
go
to
the
people
who
look
at
your
emergency
quest
and
assigned
to
the
relevant
team.
These
issues
have
a
few
templates
which
need
to
be
fixed.
E
E
Yeah,
I
guess
yeah
looks
again
so
yeah
and
you
can
do
just
the
same
thing
here
commit
it
and
then,
when
it's
ready,
just
press
yeah,
gitlab
bot
already
and
it
will
be
submitted
for
review.
This
is
how
the
whole
process
work.
Why
I'm
showing
this
particular
issue
and
suggesting
kind
of
starting
with
documentation
and
stuff
like
this
is
because
you
don't
even
need
to
set
up
the
gitlab
development
kit,
which
is
a
kind
of
development
environment
we
use
because
it
actually
takes
some
time.
E
I
was
installing
it
a
couple
days
ago
and
it
took
me,
I
guess,
a
few
hours
to
figure
everything
out,
even
though
it's
automated
quite
well
actually,
but
still
it's
not
the
easiest
thing
to
do,
and
here
you
do
everything
in
the
web.
So
it's
really
easy
to
start
contributing
this
way
and
then,
when
you
kind
of
figured
out
how
the
whole
process
works
and
get
something
merged,
you
can
look
for
more
complex
issues.
E
E
But
if
you
have
time
you
can
read
this,
there
are
a
lot
of
interesting
things
here,
for
example,
you
can
use
like
workflow
and
review
it
will
trigger
against
the
same
thing
as
bit:
labor
trading
yeah,
and
I
will
not
go
into
how
to
set
up
the
gdk
to
do
this
again.
Sorry,
because
it's
actually,
it
takes
some
time,
as
I
mentioned,
but
just
google
github
development
kit.
You
will
land
on
this
page
from
the
first
page
on
the
google
and
scroll
here.
E
It
will
actually
yeah.
You
find
these
support
methods.
You
can
go
into
online
installation,
yeah
and
just
run
this.
It
will
install
everything
on
your
machine.
We
work
on
macbooks,
so
it's
like
you
will
have
more
success.
If
you
run
this
on
the
macbook,
if
you
have
linux,
you
may
see
some
issues
you'll
need
to
fix,
but
again
it
should
be
pretty
straightforward
yeah.
E
E
E
E
H
A
A
N
Yeah
yeah,
so
so
I
saw
a
guy
who
used
to
take
part
in
the
gitlab
hackathons
and
that's
why
I
also
took
part
this
year
also
so
now
he
is
interning
at
gitlab,
so
I'm
also
curious
to
work
at
it
live.
So
what
could
be
the
process
like
either
intern
or
sre
or
devops
kind
of
roles,
I'm
more
interested
in
those
areas.
So
what
could
be
the
way
or
what
would
you
suggest
me
to
do.
A
A
But
I'd
say
those
are
the
the
two
best
options
and
you
know
once
this
is
a
little
outside
of
the
scope
of
today's
call.
But
what
we
can
do
is
connect
to
some
hiring
managers
as
well,
but
I'd
say,
check
the
postings
they're
posted
on
our
website
and
then
potentially
a
referral
would
be
a
good
way
to
thanks
for
the
question.
A
J
E
A
E
E
I
guess
even
sometimes
before
you
actually
have
an
mr.
You
can
just
create
a
small
diff,
just
post
it
on
the
issue
and
ask
if
that's
the
right
way
to
do
it
or
not
shiny
actually
does
a
lot
of
this
stuff
he
sees
in
sees
an
issue
creates
a
short
div
posts
it
on.
On
the
issue-
and
it's
already
a
start
of
the
discussion
so.
A
Yeah
thanks
a
lot
thanks
missy
for
the
question
I'll
say:
even
I
don't
write
code
as
a
product
manager,
but
even
for
me,
just
put
whatever
it
is
recreating
issues
or
getting
proposals
or
whatever
it
is
putting
it
out
early
and
getting
feedback
is,
is,
is
definitely
the
get
loud.
It
aligns
with
our
gitlab
value
of
iteration,
so
yeah,
really
the
better.
F
A
Okay,
if
not,
let's,
let's
move
on
so
I
also
wanted
to
ask
the
group
what
what
topics
are
interesting
for
all
of
you,
so
we
covered
today
we
covered
what
the
release
stages
is
all
about
those
of
you
that
are
joining
for
the
first
time.
This
is
also
we,
the
team
used
to
do
these
in
the
past,
and
so
and
we
took
a
brief
pause,
but
we
want
to
start
doing
these
again
more
regularly
and
potentially
each
month
and
what
we're
thinking
about
is
rotating
different
topics.
A
F
A
Yeah,
so
one
one
idea
is
focusing
on
a
lot
of
our
ux
and
front-end
work.
That's
another
thing
that
another
area
that
we're
investing
in
emily's
our
product
designer
on
and
she's,
on
the
call
she's
looking
and
focusing
a
lot
on
making
our
ui
even
better
and
streamlined
and
making
it
better
for
you
all
too
so
so
that's
an
example
of.
Maybe
we
could
go
deep
on
the
ux
side
of
of
the
products
front
ends
how
all
that
works.
What
what
it's
like
to
develop
on
that?
A
H
A
A
F
J
A
H
H
A
H
E
H
H
E
H
A
Okay,
yeah
see
some
nods
there.
Okay,
so
that's
that's
like
a
good
way
to
discover:
okay,
cool
linkedin,
great
yeah.
We
did
a
few
linkedin
promotion
or
not
promotion.
I'm
sharing
that's
great
cool.
Thank
you.
Okay
sounds
like
those.
Those
were
the
right
channels
to
find
you
all.
So
thank
you
for
joining
okay.
I
think
any
last
questions
before
we
wrap
up
here.
A
Okay,
so
let
me
share.
We
also
created
an
issue
just
like
we
do
everything
here
at
gitlab,
I'll
share
the
link
for
the
issue
for
today's
call,
if
you
have
any
thoughts
or
other
feedback
positive
negative
anything,
we
want
to
hear
it
I'll
also,
maybe
start
a
poll
or
a
thread
for
future
topics.
So
we
can
get
other
ideas.
A
Welcome
comments.
Welcome
and
we
want
to
do
this
again,
regularly
we're
aiming
to
do
it
every
month.
So
hopefully
we
can
see
you
all
next
month,
okay!
Well,
thank
you.
Everyone
for
joining
thanks
vlad
for
covering
all
the
topics.
Thanks
for
all
the
great
questions,
marco,
do
you
have
a
question?
Oh
no,
okay.
I
saw
your
your
screen
pop
up.
Okay,
yeah
thanks.
Everyone
see
you
next
month,
bye.