►
From YouTube: Release Stage Community Office Hours - September 2022
Description
Recording of office hours
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/371708
B
C
D
D
F
Also,
it's
like
most
of
the
times,
there's
not
a
specific,
like
we've
been
running
coffee
circles
different
days
different
times
and
there's
we
couldn't
find
a
Golden
Rule.
Let's
say
golden
time
that
we
could
have
a
lot
of
people
on
Tuesdays
most
of
the
times.
We
have
people
when
we
do
it,
and
but
Tuesday
is
like
in
two
hours
from
now.
F
F
F
B
B
Thank
you
for
joining.
This
is
the
release
stage
Community
office
hours
for
September,
we'll
start
with
some
introductions
on
the
gitlab
team
side
and
then
intros
for
the
community
members
in
the
call
and
we'll
dive
into
our
agenda.
Does
that
sound
good
to
everyone
all
right,
so
gilab
team?
So
I'll
start?
My
name
is
Chris
bolani
I'm,
the
product
manager
for
the
release
stage
and
I'm
the
host
for
today
and
then
I'll
call
on
someone.
So
we
keep
going
here.
Will
you
want
to
go
next.
A
H
E
K
L
F
C
N
B
B
Cool
okay:
we
got
some
experienced
contributors
already,
so
that's
great,
and
so
our
main
topic
today.
So
thank
you
for
coming
back
and
it's
great
great
to
see
great
to
see
you.
Our
main
topic
today
is
contributing
to
front-end
features
and
Emily
Bowman.
Our
product
designer
will
leave
that
test,
so
I'm
going
to
pass
it
over
to
Emily.
L
So
pretty
much
gitlab
you're
able
to
contribute
open
like
ux
features
and
there's
a
few
ways.
You
can
do
that
so
the
ux
department
at
gitlab
uses
figma.
So
if
you're
a
designer,
we
have
our
figma
project
that
is
open.
You
can
kind
of
use
and
see
our
designs.
We
have
a
design
repository
for
documentation
with
details
on
working
with
these
files,
so
I've
dropped
these
into
the
agenda,
but
I
will
also
share
my
screen
and
walk
through
some
of
this.
L
So
just
give
me
one
sec
I
think
it
is
there
we
go
cool,
so
gitlab
uses
the
pajamas
UI
kit,
which
I
will
open
here,
oops
we're
in
the
way
there
we
go
so
the
gitlab
component
Library.
If
you're
interested
in
contributing
any
ux
related
features
or
creating
ux
issues,
you
can
come
into
our
component
Library.
This
is
where
you'll
be
able
to
find
our
design
and
assets,
components
and
styles
for
the
gitlab
design
system.
L
So
yeah
you
can
use
figma
to
create
your
mock-ups
and
but
we'll
gladly
just
accept
if
you
want
to
sketch
them
on
paper,
get
just
very
basic
ideas
done
for
that.
Those
are
cool
too,
and
you
can
find
other
design,
research
resources
and
documentation
in
our
design
system
and
use
it
where
see
where
we
use
common
design
Solutions
and
all
of
that.
So
this
is,
if
you
want
to
contribute
a
completely
new
feature
completely
something
new.
You
have
a
ux
idea.
L
You
want
to
get
out
there
sketch
it
out
on
paper,
use
our
design
system.
Everything
is,
and
designers
from
gitlab
can
help
you
out
with
that
we're
also
open
to
contributing
to
our
design
system.
So
if
you
see
a
component
that
we
do
not
have
yet
or
component,
you
want
to
work
on
and
fix
up.
You
can
also
go
into
pajamas
design
system
and
the
UI
kit
and
just
follow
our
typical
contribution
guidelines
in
our
handbook.
L
L
L
E
L
Yeah,
so
this
is
actually.
This
is
actually
due
to
like
the
ux
movement
right
now.
Some
of
the
Young's
links
are
broken,
but
those
are
being
fixed
in
the
next
few
weeks.
So
that's
an
unfortunate
thing.
That's
just
this
week.
Some
of
our
ux
handbook
pages
and
links
are
a
little
broken,
but
we
are
in
the
process
of
fixing
that.
L
Yeah
I
think
this
is
we
there's
recently
been
a
movement
with
ux
and
things
are
currently
moving
around.
So
I
think
the
labels
are
changing,
so
hopefully
we
will
be
fixing
this
up
in
the
future.
There
should
be
things
under
here
but
I'm.
Seeing
now,
there's
there's
nothing,
but
when
there
are
available
ux
issues,
they'll
be
kind
of
in
this
section.
E
L
G
My
goodness
so
much
less
of
a
presentation
and
more
a
handful
of
tips
on
how
to
have
a
nice,
smooth,
front-end
review
process,
especially
as
a
contributor
familiarize
yourself
with
the
front-end
development
guides,
because
oh
screen
sharing
isn't
working.
So
you
get
to
look
at
my
face
instead.
Unfortunately,
the
front-end
development
guides
kind
of
are
the
core
of
our.
How
we
code
with
regards
to
things
like
Style
and
tips
on
a
lot
of
tips
on
testing
and
view
X
and
graphql.
G
The
community
contributions
review
guide
is
quite
helpful
to
know
as
well,
mostly
because
it
gives
you
kind
of
an
overview
of
what's
expected
of
us
when
we're
reviewing
your
code
and
I.
Don't
know
it's
just
good
to
know
when
it
comes
to
actual
when
it
comes
to
the
actual
implementation
side
of
things.
If
you
can
use
gitlab
UI
utility
classes
wherever
possible,
it'll
save
us
all
a
lot
of
pain.
G
The
the
whole
review
process
is
quite
smooth,
however,
if
that's
kind
of
time
consuming
or
or
then
we
can
always
add
it
to
the
utilities.scss
file.
Within
gitlab
I
don't
have
the
full
path
memorized,
but
it's
probably
like
App
application
assets,
Styles
something
utilities.scss
and
we
can
make
a
follow-up
to
add
it
to
gitlab
UI
later,
if
any
feedback
doesn't
make
sense
at
any
time,
feel
free
to
reach
out.
G
G
The
the
biggest
thing
I
think
I've,
noticed
from
reviewing
Community
contributions
is
that
the
git
commit
message.
Stuff
is
a
little
bit
is
kind
of
the
biggest
hurdle,
especially
when
it
comes
to
changelogs
as
Community
contributors.
You
can
put
a
change
log
on
pretty
much
anything.
We
have
stricter
guidelines
for
ourselves,
but
we
want
to
give
you
all
as
much
credit
as
we
can
for
contributing
to
the
project.
G
D
L
B
F
Sure
no-
and
it's
like
Emily
before
mentioned,
about
the
accepting
ux
contributions
and
generally
we're
not
we're
trying
we're
trying
to
use
the
seeking
Community
contribution
as
as
a
label
for
catered
issues.
So
I
was
thinking
whether
you
would
consider,
maybe
renaming
or
instead
of
like
accepting
new
exported
users
using
the
seeking
Community
contributions
and
the
ux
label.
F
L
L
B
F
Yeah,
so
sorry,
I'm,
just
taking
this
the
community
challenge
is
this
something
that
we
still
we
still
doing
or
the
everything
else
is
pretty
straight
for
a
lot
hanging
through
the
good
Community
contributors
seeking
Community
contributions.
Certain
requests,
the
community
Talent,
is
something
that
you're
actively
doing
or.
G
F
F
We
have
labels
like
saging,
communicate
divisions,
and
there
is
the
community
challenge,
which
is
like
a
really
old
effort
where
every
month,
in
a
way,
people
teams
were
like
using
this
talents
to
motivate
contributors,
and
so
my
question
is
like
whether
you're
doing
it
and
if
not,
we
can
start
deprecating.
It.
D
B
Don't
believe
we
are,
we
can
double
check
and
yeah.
It
looks
like
there's
no
release
ones.
I
do
I'll
pull
the
list
for
just
across
gitlab
and
there's
quite
a
bit
so
I'm
not
sure.
What's
populating
that
label
right
now,
but
we're
not
and
then
I
I
agree
in
general
of
yeah
simplifying
and
pairing
down
all.
F
D
B
C
C
B
G
G
B
D
B
D
O
B
B
Cool
okay:
let's
move
on
to
the
next
topic,
which
really
is
about
feedback
from
you
all,
so
this
is
our
second
release
stage
focused
office
hours
and
at
Christos
and
others
and
the
rest
and
the
other
team
members
hosts
other
office
hours.
But
for
us
we
wanted
to
maybe
get
some
feedback
from
also
from
our
last
session
about
how
how
some
of
you
kind
of
find
issues
and
understand.
B
D
O
O
Yeah
yeah
of
well,
it
depends
because,
for
example,
if
I
have
a
problem
or
an
issue,
I
try
to
look
if
there's
already
an
existing
issue
about
that,
so
also
to
don't
open
a
million
of
duplicate
issues,
so
yeah
using
labels
or
maybe
using
if
I
can't
find
anything
using
the
label.
I
try
to
look
using
the
description.
Try
to
use
some
words
that
I
think
that
could
be
there
on
the.
B
B
O
O
N
N
In
two
words,
so
yeah
I've
only
been
working
on
one
main
issue
for
the
most
part,
but
I
found
the
descriptions
incredibly
helpful
and
very
very
thorough.
So
it's
easy
to
get
started.
That
was
a
huge
blocker
for
me
is
not
knowing
how
to
start
and
and
what
area
of
the
code
to
look
at
and
things
so
having
examples
and
showing
patterns
in
the
code
of
saying
here's
something
that
we've
implemented.
Similarly,
that
will
give
you
a
hint
on
how
to
do
it.
N
B
O
Another
thing
that
if
you
would
like,
if
you
find
an
issue
that
you
would
like
to
work
on,
and
you
don't
have
the
I,
don't
want
to
say
the
knowledge,
but
you
don't
know
where
to
start.
You
can
always
ask
the
people
that
comment
commented
on
that
issue
to
get
some
help
and
maybe
have
some
advice
on
where
to
look
for
on
how
you
could
try
to
work
on
that.
B
B
How
about
we
kind
of
touched
upon
this
already
and
the
next
one
was
communicating
with
us
just
like
how?
How
has
that
been
for
everyone?
Has
that
been
easy?
Do
you
know
who
to
reach
out
to
I,
think
I
think
one
of
the
benefits
of
these
office
hours
is
that
you
all
know
now
kind
of
both
ways,
but
you
all
know
now
our
faces
and
names,
and
you
should
feel
free
to
to
Ping
us
on
issues
to
get
more
support,
but
just
curious
how
that
process
has
been
pretty
well.
N
I've
found
communication
very
easy
and
straightforward
every
time.
I
get
stuck
and
I'm
debating.
Do
I,
ask
a
question
or
do
I
just
keep
trying.
I
should
just
ask
the
question,
because
every
time
it's
incredibly
helpful
and
I
get
a
ton
of
information
back.
That
helps
me
move
forward,
but
the
only
question
I
would
have
is:
what
are
the
expectations
on
the
community
side
for
timeline
of
responding
to
things?
I
notice,
skit
lab
members
tend
to
respond
within
24
to
48
hours,
but
I
don't
want
to
ping
someone
with
an
a
stupid.
N
B
E
I
would
say
for
Community
contributors
if
you
post
something
within
a
week,
that
would
be
great.
Two
weeks
is
okay
and
basically
we
will
ping
you
once
we,
for
example,
want
to
take
and
finish
the
issue
ourselves
just
to
check
if
you're
still
working
on
it
but
other
than
that's
like
when
you
have
time
answer.
If
you
have
other
commitments,
don't
feel
pressure
to
do.
G
As
Vlad
kind
of
touched
on
like
as
long
as
we're
not
actively
trying
to
schedule
the
issue
response,
time
is
less
of
a
problem.
Because,
if
we're,
if
we're
interested
in
scheduling
it
for
like
next
month
or
something,
then
we
want
to
make
sure
that
you're
not
halfway
through
it
or
almost
done
it
or
anything,
and
we
should
we
can
schedule
something
else.
Then
right,
yeah.
B
Yeah,
the
other
related
thing
yeah,
thanks
for
the
question
received,
that's
a
that's
a
good
one,
I
think
the
other
related
one
that
I've
seen
is
I,
think
sort
of
what
Andrew
was
touching
upon
like
if
we're.
If,
if,
if
an
issue
or
a
feature,
has
been
working
on,
but
then
we
don't
hear
back
from
the
contributor
and
we
were
interested
in
working
on
it
like
that,
that's
a
little
challenging
because
we
want
to.
B
B
B
E
D
N
F
E
E
O
Yeah
because
I
I
didn't
know
where
to
start
because
I
before
opening
the
issues,
I
tried
to
have
a
look
at
the
code
and
understand
how
I
could
do
what
I
needed,
but
jumping
straight
into
the
gitlab
code
base
without
Ruby
knowledge,
view
knowledge
or
anything
like
that,
it's
impossible
so
yeah.
He
walked
through
me
on
that
and
then
I
started
contributing
all
around,
not
only
on
those
issues
that
I
needed
about
I
kept
contributing
because
I
liked
the.
O
E
N
So
I
was
interested
in
git
lab
I
first
heard
of
it
from
a
friend
who
worked
at
gitlab.
He
since
moved
to
a
different
company,
but
he
always
had
amazing
things
to
say
about
gitlab
and
the
community,
and
once
I
switched
into
software
engineering.
I
wanted
to
learn
more
about
Open,
Source
contribution
and
gitlab.
Does
that
so
well,
you're
an
emblem
of
an
icon
for
open
source
and
remote
work,
so
I
wanted
to
get
involved
somehow
and
see
how
it's
done
properly.
N
M
M
E
F
B
F
B
L
No
worries,
I
I
was
also
going
to
say.
I
know
we
do
a
brainstorm
session
in
release
too
and
I'd
be
curious
if,
like
just
that,
processor
opening
up
like
a
brainstorm
session
during
one
of
the
office
hours
could
be
interesting
for
people
as
well
to
bring
ideas
and
then
just
chat
through
kind
of
how
we
land
on
certain
ideas
we
land
on.
N
B
Yeah,
it's
a
great
question,
so
I've
been
here
for
a
year
just
over
a
year
and
since
I've
been
here,
it's
been
this
way,
but
I
know
and
others
Junior
Vlad
others
have
been
around
longer
actually
and
so.
They've
probably
seen
the
evolution
of
the
you
know
of
the
group
in
general,
we're
organized
by
like
devops
stage
or
like
we're
right
now
we're
the
one
group
that
yes,
Story
Time
sure.
Maybe
the
next
topic
next
next
meeting.
So
right
now
we're
the
one
engineering
team.
B
We
call
them
groups
that
build
features
for
the
release
stage.
Prior
to
this
organization.
The
release
stage
was
composed
of
two
different
groups
focused
on
the
different
categories
that
we
have
so
yeah
I
think
it's
evolved
over
time
right
now,
yeah!
This
is
sort
of
like
this
is
where
we're
at
today,
but
anything
like
any
company
teams.
Change
teams
grow
so
on
yeah.
D
I
I
E
B
Again,
we
want
to
continue
to
do
this
monthly
as
long
as
it's
useful
for
everyone
and
as
long
as
everyone's
interested
and
as
long
as
we
have
topics
so
please
feel
free
to
suggest
more
topics
in
the
issue
that
we
had
for
today's
office
hours,
if
you
think
of
anything
else
and
or
if
you
have
any
other
feedback
and
then,
as
always,
we'll
continue
to
post
on
Meetup,
and
we
have.
We
have
planning
issues
for
each
of
these,
so
look
out
for
those
for
future
sessions
and
with
that,
thank
you
for.