►
A
We
call
this
cells
I've
also
linked
to
the
blueprint
in
the
document,
if
you're
interested
in
learning
more
about
that,
and
in
order
to
achieve
that,
we're
also
working
on
introducing
a
different
concept
that
we
call
organizations
to
the
product
I've
also
linked
to
that
document.
If
you
want
to
learn
more
and
some
other
things
we
oversee
in
our
team-
are
groups
and
projects
in
general,
how
everything
inherits
in
groups
and
projects
workflows
relating
to
becoming
a
member
of
a
group
or
project
group
sharing,
and
we
also
oversee
the
user
profile
page.
A
B
A
Yeah
I've
added
a
bit
of
a
section
there
with
links
to
our
backlog
and
to
the
specific
Community
contribution
issues,
because
the
area
that
our
team
oversees
is
really
large,
our
backlog,
is
also
really
large.
So
we
definitely
welcome
any
kind
of
community
contributions
from
people
that
want
to
start
with
or
if
you
wanna
try
something
more
complex
as
well.
A
There's
a
lot
of
bugs
that
I
like
ux
improvements.
That
could
be
done,
that
we
will
not
get
to
at
this
point
in
time.
We
know
that
they're
super
annoying,
but
in
the
bigger
picture
it's
just
something
we
don't
get
too
easily.
So
especially
those
areas
are
really
nice
for
first-time
contributors
to
pick
up.
So
we
have
a
couple
of
easier
issues
selected
there
if
there's
something
that
is
not
labeled
as
looking
for
or
seeking
Community
contribution,
but
you
would
like
to
give
it
a
shot.
A
You
can
also
just
tag
me
there
to
get
in
touch
with
the
team
and
we
can
help
with
adding
an
implementation
plan
to
it,
because
sometimes
it's
a
bit
difficult,
also
depending
on
the
complexity
of
the
code
base,
to
find
a
good
starting
point.
So
it's
good
if
you
get
advice
from
the
designers
or
the
engineers
to
help
you
with
the
implementation
suggestions,
at
least
so
take
a
look
there
and
let's
go
to
any
questions.
If
you
have
any
about
the
team
or
Community
contributions
in
general
yeah,
let
me
know.
C
No
questions
but
I
saw
that
it
was
a
small
group,
so
I
just
figured
out.
Thank
you.
First
of
all,
for
hosting
this
I
am
a
quality
assurance,
professional
and
I've,
always
loved
get
Labs
process.
So
I
thought
I'd
come
in
today
and
take
a
look
at
how
you
operate,
especially
when
it
comes
to
bug,
fixes
and
things
like
that
and
perhaps
find
a
way
to
contribute.
If
I
could
business.
D
I
wanted
to
say
thank
you
too,
and
I'm,
mostly
interested
in
the
live
pairing
to
see
what
you
have.
I
wasn't
familiar
with
the
tenant
skill
team
at
all,
I've
contributed
to
other
areas
of
git
lab,
but
I'm,
slowly
getting
to
know
each
of
the
other
teams
and
everything.
So
it
looks
like
you
have
a
lot
of
open
issues
actually,
which
is
great
and
I,
might
dive
into
those.
Now
that
I
know
of
the
existence.
B
Yeah
thanks
both
for
your
comments,
yeah,
we
can
yeah,
sir.
We
can
wait
for
a
few
more
questions
and
comments,
but
yeah
we'll
dive
into
a
live
pairing
after
this
and
can
also
kind
of
go
through
like
how
you
can
contribute
and
a
little
bit
of
how
we,
how
we
like
look
at
bug,
fixes
and
how
we
approach
them
and
that
type
of
thing.
So
hopefully
the
live.
Pairing
can
kind
of
go
over
some
of
those
those
comments
but
yeah.
B
B
B
So
if
you
open
the
issue
up,
you'll
see
that
in
the
right
hand
sidebar
as
the
label
that
says
seeking
Community
contributions
and
that's
a
good,
that's
a
good
way
to
know
that
it
could
be
a
good
one
to
take
a
look
at
also,
if
you
go
to
current
backlog.
The
Christina
link
to
this
might
take
a
second
to
load
because
there's
a
lot
and
then
you
could
add,
the
playable
is.
B
B
B
Sorry
filter
them.
Sometimes
we
have,
unfortunately,
multiple
duplicate
labels
that
are
need
to
be
cleaned
up,
sometimes
so
yeah.
That's
a
good
good
starting
point
is
to
filter
by
seeking
Community
contributions
and
then
front
end
or
back
end.
Today,
we're
going
to
focus
on
an
issue,
that's
a
front
end
issue
because
I'm
a
front-end
engineer
and
that's
what
I'm
more
familiar
with
and
what
I
work
on
generally
and
hopefully
it'll
just
kind
of
give
everyone
an
idea
of
how
you
can
contribute
but
yeah.
B
This
one
is
pretty
simple,
so
it
doesn't
have
too
much
information
in
the
in
the
description,
but
some
of
them
might
be
a
bit
more
complicated
with
steps
on
how
to
reproduce
or
designs,
and
that
type
of
thing
this
one
and
then
also
it's
a
good
idea
to
just
go
through
the
comments
and
see
if
anyone
else
has
worked
on
it
or
tried
to
fix.
It
has
run
into
issues
that
type
of
thing
but
yeah,
so
this
one
is
about
the
group
overview
page,
which
we
go
to
gitlab
org.
B
This
lists
out
subgroups
and
projects,
and
if
you
hover
over
this
icon,
it
says
public.
This
group
and
public
projects
can
be
viewed
without
any
authentication
which
is
correct.
But
if
you
were
to
find
a
project
in
here
and
hover
over
it,
it
would
say
this
group
and
public
when
it
should
say
this
project.
So
this
is
a
pretty
minor
ux
bug
that
we
can
take
a
look
at
fixing
and
then
the
other
thing
that
is
helpful
for
when
choosing
a
an
issue
to
work
on.
B
Is
we
try
to
add
this
Implement
implementation
guide,
or
sometimes
it
might
say,
like
engineering
guide
or
that
type
of
thing,
to
help
contributors
figure
out
where
to
start
or
if
it's
something
that
they
might
want
to
help
contribute
to?
And
so
this
one
like
I
said,
is
a
fairly
simple
one.
So
it
just
kind
of
has
us
a
few
links
to
some
code
as
a
starting
point
and
yeah.
B
We
can
use
that
to
get
started
and
yeah
if
anyone
has
questions
while
I'm
talking
just
feel
free
to
jump
in
or
leave,
leave
your
question
in
the
chat
or
yeah
either.
One
of
those
and
I
can
answer
those
or
try
to
answer
those
so
yeah.
The
first
thing
that
you
would
want
to
do
to
to
get
started
on
an
issue
would
be
to
figure
out
how
you
are
going
to
like
make
the
code
change
and
then
view
it
there's
a
few
different
options.
B
It
looks
once
you
have
it
set
up
it
by
default
if
it
is
available
at
localhost,
Port,
3000
and
it'll
have
this
little
green
gitlab
logo
instead
of
the
orange
one,
and
this
is
the
performance
bar
that
you
can
use
for
queries
and
then
yeah,
there's
a
bunch
of
like
fake
data.
That's
seated
that
kind
of
helps
you
work
on
different
parts
of
the
of
git
lab.
B
So
that's
that's
one
way
you
can
do
it.
You
can,
if
it's
a
simple
change
that
you
feel
like
you,
don't
necessarily
need
local
like,
for
example,
maybe
there's
a
typo
or
something
that
you're
fixing.
You
don't
feel
like.
You
need
localhost
setup.
You
can
just
work
in
the
web
IDE,
which
is
pretty
cool,
and
to
do
that,
you
would
like
five
go
to
a
file
we'll
just
go
to
the
readme
for
now,
just
as
an
example.
B
B
So
it's
not
too
hard
to
set
up
and
yeah.
If
you
go
to
the
to
the
project,
there
is
a
like
getting
started
page
and
there's
a
one-line
installation,
so
I
think
it,
depending
on
how
complicated
the
change
is.
You're,
making
I
think
it
is
worth
setting
up
so
yeah.
Let's
get
let's
get
started
on
making
some
code
changes
unless
anyone
has
any
questions
about
any
of
what
I
just
talked
about.
F
E
For
that
overview,
another
point
of
mention
for
our
wider
community
members
is:
we
do
have
the
gitlab
community
Forks,
which
allows
you
once
you've
joined
the
gitlab
community.
You
can
use
a
community
fork
and
then
that
way
helps
you
bypass
some
restrictions
on
like
Ci
minutes
or
if
you
need
a
verification
of
a
credit
card
and
a
really
cool
thing
is
that
allows
you
to
partner
up
and
with
other
community
members.
E
B
A
B
B
We
can
talk
about
labels
a
little
bit
later
when
we
add
when
we
actually
create
the
merge
request,
because
that
is
that
is
helpful
as
well
and
you'll
get
prompts
if
you're
missing
labels
and
the
labels
are
kind
of
how
we,
how
we
categorize
merge,
requests
and
prioritize
them.
That
type
of
thing
so
yeah
we'll
check
out
a
new
branch
and
yeah
like
I
said:
I
already
have
git
lab
development
kit
running,
so
we
will
go
to
a.
F
B
B
So
that
yeah
generally,
where
I
start,
is
just
the
implementation
guide
and
then
pull
up
the
code
and
try
and
get
try
and
get
comfortable
with
it
and
what's
going
on
and
I
am
quite
familiar
with
this
part
of
the
code
base
because
I
have
worked
in
it
quite
a
bit.
So
I
do
understand
it,
but
there
are
bugs
that
I
work
on
that
I
come
into
it
and
I'm
not
familiar
with
the
code
that
part
of
the
code
base,
so
I
have
to
kind
of
go
through
and
figure
out.
B
B
So
in
this
case
we
can
use
the
view
Dev
tools
and
click
on
here,
and
we
can
see
that
this
group
item
component
that
we
were
just
looking
at
in
the
code
editor
is
in
fact
being
rendered
on
this
page.
So
we
know
we're
in
the
right
place
and
then
we
can
go
up.
We
can
go
up
the
the
tree
here
and
see
what
parent
components
are
rendering
this
just
to
kind
of
better
understand
how
it's
working.
B
F
B
B
Our
design
guidelines
called
pajamas,
so
when
this
is
what
we
try
to
use
to
get
consistent,
UI
throughout
git
lab,
so
that
all
the
styling
is
the
same.
So
in
this
case
we
have
a
tabs
component
coming
from
gitlab
UI,
and
then
this
overview
tab
or
this
sorry
subgroups
and
projects
tab
is
rendering
this
tree.
B
B
And
we
can
see
that
there's
this
computed
property,
so
in
view
a
computed
property
is
it's
kind
of
like
a
cached
conditional
or
some
logic
that
gets
cached
by
View
and
can
be
used
to
kind
of
it
can
be
it.
It
can
be
a
convenience
and
make
the
code
more
readable,
but
it's
also
cached,
so
it
can
improve
performance.
B
B
That's
we
can
actually
use
the
view
Dev
tools
to
find
this
icon
component
and
there
it
is-
and
we
can
see
that
the
title
which
we
were
just
looking
at
in
the
code
is
set
to
this
group,
even
though
it's
a
project
so
I
think
we
found
the
problem,
and
so
we
need
to
conditionally
change
this.
This
tool
tip
based
on
if
this
component
is
rendering
a
group
or
rendering
a
project,
and
so
it
looks
like
the
way
it's
figuring
out.
B
B
So
so
what
I
just
did
was
I
in
vs
code.
You
can
command
click
to
go
to
to
follow
the
the
import.
So
in
this
case
this
this
constant
is
being
imported
from
another
file,
so
I
can
command
click
to
go
to
it,
and
we
can
see
that
it's
a
an
object
of
that
lists
out
the
descriptions
for
each
visibility
level.
B
So,
if
one
is,
if
it's
public,
then
it
shows
this
if
it's
internal,
it
shows
this.
If
it's
private,
it
shows
this,
but
we
can
also
see
below
this.
We
have
one
that's
defined
for
projects
and
it's
basically
it's
the
same.
It's
just
that
it
has
different
descriptions
which
is
basically
exactly
what
we
want.
B
Check
if
it's
a
group
or
a
project
and
then
use
the
correct
mapping
here
and
the
the
nice
thing-
and
this
is
this
was
mentioned
in
the
implementation
guide-
is
we
have?
We
already
have
this
check?
This
dot
is
group
and
yeah,
so
the
data
that
we
have
in
this
component
has
a
has
a
type.
So
there's
this
group
prop
I,
believe
yeah,
so
in
view
there's
a
concept
called
props,
which
is
they
have
it
in
react
as
well,
and
it's
just
data.
B
If
it's
passed
to
the
component,
you
have
access
to
inside
the
component.
In
this
case,
we
have
a
group
prop,
that's
an
object
and
on
that
object,
there's
a
type
attribute
and
yeah
and
like
I
said.
Admittedly,
this
part.
This
component
is
a
little
confusing
because
it's
talking
about
a
group,
but
it
also
renders
projects
and
that's
part
of
the
reason.
B
B
B
So
now
we're
saying
if
it's
a
group
return
the
group
tool
tip
if
it's
a
project
return
the
project
tooltip.
So
hopefully,
if
we
go
back
here,
it
should
have
the
correct
tool
tip
now
yeah.
So
now
it
says
this
project
can
be
accessed
without
auth,
any
authentication,
which
is
what
we
wanted
to
say:
okay,
so
yeah,
that's
so
I
think
we
fixed
the
bug.
D
B
So,
let's
maybe
it
might
help
to
see
like
the
data
that
this
component
has
so
sorry.
What
is
this
called
group
item?
So
this
component
is
called
group
item.
So
if
we
go
into
the
view
Dev
tools
and
find
the
group
item
component,
we
can
see
the
props
and
yeah
like
I
was
saying
earlier.
This
component
is
a
little
confusing
because
this
prop
is
called
group,
but
we're
actually
referring
to
a
project
in
this
case.
Sometimes
it
would
be
a
group.
B
So
we
can
think
of
this
as
more
of
like
the
item,
and
so
this
item
prop
is:
has
all
these
attributes
that
we
have
access
to
and
in
so
right
here
we're
saying
this
dot
group
and
in
the
view,
Dev
tools.
We
can
see
this
dot
group
right
here.
So
these
are
all
the
attributes
we
have
access
to
and
then
we're
saying
this
dot
group
dot
visibility.
So,
let's
find
the
visibility
attribute
that
we're
referring
to,
which
is
here
public.
B
So
it's
just
the
string
public
and
this
data
is
coming
from
which
I
forgot
to
mention
apologies,
but
we
make
an
API
call
when
we
reload
this
page.
That
gets
this
this
data
and
feeds
it
to
the
component.
So
that's
where
the
stat
is
coming
from,
so
the
back
end
adds
this
attribute.
That
is
the
visibility
and
in
this
case
it's
public.
So
we're
saying
in
this
object
look
up
the
public
key,
which
is
here
and
return.
This
string
does
that
make
sense.
B
Yeah,
apologies
for
the
confusion
of
this
component.
This
so
I
mean
this
does
come
up.
Gilab
is
a
big
code
base
and
yeah
like
any
big
code
base.
There
is
like
technical
debt,
so
this
type
of
stuff
does
come
up
quite
a
bit
where
there
is
kind
of
just
a
little
bit
confusing
naming
like
in
this
case.
At
one
point,
probably
this
view
only
rendered
groups
and
then
we
added
projects
it
we
had.
B
It
updated
it
to
also
render
projects,
but
the
names
of
the
components
never
got
updated
so
and
yeah
so
like
in
this
case
sometime
we
may-
or
there
may
already
be
an
issue
that
exists.
That
says,
like
let's
refactor
this
code
and
update
the
names
to
make
it
a
little
bit
less
confusing,
which
could
also
be
a
good
contr,
Community
contribution
or
yeah.
If
you
were
working
on
this
component
and
you're
we're
thinking.
Oh,
this
is
confusing.
B
You
could
also
open
up
or
you
can
search
search
through
the
issues
to
see
if
one
exists
and
if
not,
you
could
also
open
one
up
and
say:
oh
let
these
component
names
are
kind
of
confusing
here's.
A
proposal
to
update
them
that
type
of
thing
but
yeah.
So
in
this
case,
so
now
we
are
rendering
the
tooltip
correctly
and
so
for
most
for
most
View
changes.
B
B
We
have
the
community
the
base
functionality
which
is
shipped
in
the
community
Edition
and
then
any
licensed
feature
is
shipped
in
Enterprise
Edition,
and
that
has
a
second
file
which
is
in
the
ee
directory,
but
in
this
case
we're
just
working
on
the
the
base
functionality.
It's
not
any
licensed
feature,
so
we
would
just
want
the
the
group
items
and
so
yeah
we
have
to
figure
out
if
there's
already
a
spec,
that's
testing
this
generally.
B
B
Okay,
so
it
passed,
which
means
we
probably
didn't,
have
a
spec
for
the
tooltip
or
we
didn't
have
a
very
good
one,
so
we'll
probably
want
to
refactor
or
add
a
spec,
but
we
just
have
to
figure
out
like
where
it's
actually
being
tested
and
so
yeah.
One
way
we
can
start
is
just
search
for
like
tool
tip,
because
this
is
a
little
bit
of
a
long
spec
file.
So
we
could
read
through
the
whole
thing,
try
and
figure
out
where
it's
testing
this
this
tooltip.
But
you.
A
B
So
I
think
I
had
I
have
like
my
search
to
match
the
case,
which
is
what
our
tooltip
didn't
come
up,
but
so
we
do
have
a.
We
have
a
test
that
says
should
render
component
template
correctly,
so
we
would
just
want
to,
and
then
we
have
a
test,
that's
grabbing.
Let's
see:
visibility,
icon,
okay,
so
it's
getting
this
icon,
which
is
what
we
had
the
tool
tip
on
and
it's
checking
the
title
attribute,
which
is
what
is
used
for
the
actual
tool
tip.
B
It
looks
like
yeah
so
and
then
it's
saying
to
be
VM
dot.
So
then
saying
should
be
this
tooltip
text,
so
I
think
what
we
need
to
do
is
so
this
test.
Is
it's
not
the
best
test,
because
it's
essentially
saying
like
grab
the
title
and
then
check
if,
if
it's
set
to
this
computed
property,
but
this
computed
property,
it's
not
checking.
It's
not
actually
testing
any
of
this
logic,
because
just
checking,
if
it's
set
to
this,
so
we
probably
want
to
update
this
test.
B
B
And
then
we
could
say
so
yeah
the
tests
generally
are
the
hardest
part
usually,
and
they
are
all
they
all
are
generally
set
up
fairly
is
about
the
same,
but
there
are
some
some
nuances,
especially
in
some
of
our
older
specs,
so
it
can
be.
It
can
take
a
little
while
to
like
figure
out
how
the
specs
are
working
for
myself,
included
and
I
work
on
these
a
lot.
So
we
just
have
to
figure
out
what
what's
going
on
here.
B
B
F
B
F
B
B
B
B
B
B
B
So
let's
just
comment
this
out
for
a
sec
and
yeah,
and
just
you
can
do
it.
You
can
do
describe
dot
only
to
say
like.
Let's
only
run
this
test,
because
this
is
the
only
one
that
we're
really
we're
trying
to
get
to
pass
at
the
moment
and
yeah.
Let's
just
see
if
that
passes,
and
it
does
surprisingly
for
the
I
generally,
don't
get
them
to
pass.
B
But
since
we
only
have
10
minutes
left,
let's
just
Commit
This
and
open
up
a
merge
request.
Just
so
we
can
go
through
that
process
and
hopefully
that
kind
of
helps
everyone
understand
the
full
flow
of
contributing
so
yeah
you
can
use
you
can
commit.
However,
you
like
I,
prefer
to
just
do
it
in
vs
code,
because
I,
like
the
UI
of
it
but
yeah
in
this
Source
control,
tab
I,
just
generally
look
at
the
the
code
make
sure
it
looks
correct.
B
Add
the
the
changes
add
a
commit
message.
So
in
this
case
we're
fix
the
project
tool,
tip
project,
the
visibility
tool
tip
for
projects,
and
then
you
can
add
so
this
line
is
should
be
is
supposed
has
to
be
under
72
characters.
So
we
have
a
bunch
of
rules
for
our
commit
messages
has
to
be
under
72
characters,
and
then
this
is
kind
of
the
title.
Then
the
description
you
can
say
on
the
group
overview
on
the
group
overview
page
previously,
the
tool
visibility
tool
tip
for
projects.
B
B
B
B
B
And
then,
if
you
go
to
so
there's
two
ways
you
can
do
it
it'll
give
you
this
link
here.
You
can
go
to
that
or
if
you
go
here,
it
should
have
this
alert
like
to
the
main
dashboard.
So
we
can
create
the
merge
request
and
so
like,
if
you're,
creating
from
a
from
a
branch
or
from
a
fork
you'd
you
should.
It
would
take
you
to
this
and
it
would
you'd
be
targeting
from
your
branch
to
the
git
lab
master
but
yeah.
B
F
B
B
We
still
need
to
finish
up
this
spec
here
that
we
have
commented
out,
but
yeah
when
it
is
ready,
I
would
use
the
gitlab
ready
and
that'll
ping
emerge
request
coach
and
you
can
also
ping
the
merge
request.
Coach
I
believe
you
can
do
yeah
gitlab
bot
help
if
you,
if
you're
stuck
on
something
and
then
that
might
ping
me
or
another,
merge
request,
coach
and
I
can
come
in
and
help
you
out
like.
So
you
don't
know
how
to
finish
up
that
spec.
B
D
I
have
a
question
about
a
general
question
that
might,
you
might
not
know
the
answer
to
Peter,
but
maybe
someone
else
does
so
if
you
create
a
fork
or
if
you
sorry,
if
you
use
the
community
fork
and
you
create
a
branch
and
then
you
create
a
merge
request,
then
you
create
another
branch
and
another
merge
request
using
the
community
Fork.
But
you
want
the
Upstream
Branch
to
be
your
first
Branch
like
you're,
creating
you've
made
changes
based
on
your
first
Mr.
F
G
G
G
So
I
do
this
occasionally,
where
you're
kind
of
waiting
for
one
thing
to
be
reviewed,
but
you
want
to
continue
working
on
the
development,
so
you
kind
of
do
the
next
one
and
the
Upstream,
your
your
merge
request
is,
is
going
to
master
Upstream.
So
that's
where
it
kind
of
now
shows
you
all
the
changes
from
your
original
merge
request,
plus
plus
the
new
one.
So
then
the
idea
once
the
first
merge
request
goes
in,
is
that
you
would
need
to
rebase
the
second
one.
G
G
G
The
second
one,
and
also
just
just
just
when
you,
when
you
create
that
when
you
create
that
merge
request
when
you're
in
the
edit
merge
request
view
you
can
also
set
a
mode
request
dependency
there.
You
can
actually
pop
the
link
of
your
first
merge
request
into
that.
So
it's
also
a
way
of
just
signaling
to
everyone
that
this
merge
request
is
dependent
on
another
merge
request
so
yeah
there
we
go.
F
G
E
I
just
want
to
say
thanks
to
Peter
for
walking
through
that
issue
emerge
request
and
it's
a
great
example
of
an
issue
that
seems
so
simple
at
the
start,
but
then
has
some
other
things
come
along
the
way
or
then
adding
tests
into,
and
also
you
point
out
a
good
example
of
using
the
gitlab
bot
help
command
to
get
Mr
coach
in
maybe,
if
you're
looking
for
assistance
with
writing
tests
and
things
like
that,
it's
a
good
use
for
that
command.
So
thanks
Peter.
B
Yeah
no
problem
I'm
glad
it
was
helpful
and
yeah
people
are
welcome
to
so.
I
am
a
merge
request,
coach
as
well,
so
you're
welcome
to
just
ping
me
directly
if
it's
on
any
merge
requests,
but
especially
if
it's
group
tenant
scale
and
I
can
try
and
help
or
if
it's
above
my
domain
I
can
reach
out
to
like
a
back-end
engineer
and
have
them
help
out
so
yeah
I
can
put
my
I'll
put.
B
My
I
should
link
to
my
Glam
profile
somewhere,
but
we'll
just
I'll
just
put
that
in
the
docs
and
yeah.
Hopefully,
that's
all
all
helpful,
and
if
there
are
no
more
questions,
we
can
can
end
it
there
and
I.
Don't
know.
I
know
there
are
office
hours
for
other
teams
as
well.
So
if
you're
interested
in
that
take
a
look
at
the
I
believe
they're
all
on
Meetup
yeah.
G
B
It's
yeah
so
like
when
you
use
at
gitlab
bot
help
it
I,
believe
it
just
randomly
chooses
or
maybe
based
on
the
labels
emerge,
request
coach
to
Ping
and
yeah.
There's
front-end
engineered
back-end
Engineers
across
multiple
groups
that
help
out,
and
they
also
help
with
like
triaging
the
community
emerge,
requests
and
yeah.
It's
something
that
some
some
of
the
engineers
volunteer
for
and
yeah
the
responsibility
just
gets
kind
of
passed
around
between
that
group,
depending
on
everyone's
capacity.
E
One
quick
follow-up
to
that,
and
one
of
the
responsibilities
for
Mr
coaches,
too,
is
like
identifying
the
labels
for
issues
and
merge.
Requests
and
I
was
just
thinking
about
this
issue
that
we
walked
through
I'm
wondering
like
if
I
had
seen
this
I'd
seen
that
bug
I
don't
know
if
I
would
have
known
to
label
it
as
Ted
at
scale
that
wouldn't
have
immediately
come
to
mind
so
I'm
wondering
for
your
group.
Do
you
have
any
tips
on
identifying
something
as
part
of
tenant
scale
or
not?.
G
G
Notes
come
on
notes
play
nicely
so
typically
I
and
I
use
this
when
I'm,
when
I'm
triaging
treasuring
issues
myself
I
use
this.
This
document
pretty
religiously,
if
I'm,
trying
to
find
where
exactly
a
certain
feature
fits
in
within
the
grand
scheme
of
things.
This
this
the
Stock's
a
great
one
to
to
understand
which
which
team
within
gitlab
is
looking
after
that
that
particular
feature
set.
B
Another
trick
that
I
use
sometimes
is
if
you,
if
you
find
the
future
in
in
the
docs
I'll,
just
share
my
screen
quickly,
but
yeah
that
the
page
that
page
is
super
helpful.
But
if
you
find
the
feature
in
the
docs
say
like
groups
and
then
if
you
just
go
to
the
bottom
and
click
page
source,
so
all
our
docs
should
have
a.
B
A
stage
and
a
group
listed
at
the
top,
so
if
the,
if
the
issue
is
about
groups-
and
you
go
to
the
groups
section
in
the
docs
and
click
edit
it'll
say
Group
Tennis
scale
and
the
stage-
and
that
should
be
should
be
true
for
all
the
features
in
our
docs.
Hopefully,
so
they
should
be
categorized
by
groups.
G
Yeah
and
don't
forget,
we're
currently
mid
hackathon,
so
it's
hacked
on
this
hackathon
week
this
week,
Missy
I'm
sure
you've
got
something
in
the
in
the
works,
if
not,
if
not
more
than
one
as
well
as
Marco
zenzi.
If
you
have
not
yet
had
a
chance
to
contribute
to
gitlab
now's
a
fantastic
time,
we're
accepting
Mrs
we've
got
a
hackathon
open
at
the
moment.
I'll
drop
a
link
to
the
hackathon
in
the
in
in
the
in
the
chat
too
and
yeah.
If
you
also
haven't
joined
our
Community
Discord.