►
From YouTube: GitLab Virtual Meetup - Everyone can contribute
Description
This is a recording of the GitLab Virtual meetup from 2020/04/29 featuring Ray Paik.
Talk Title: "Everyone can contribute " by Ray Paik
Description: In this meet-up, Ray Paik, GitLab's Code Contributor Program Manager, will discuss how everyone can contribute to improving the GitLab product (e.g. code, documentation, translation, and UX design) and show how to submit an MR to get familiar with the contribution process. Ray will also go over resources that are available to help contributors.
---
We would love for you to contribute to our virtual meetups.
You can find upcoming virtual meetups and resources to plan your own here: https://about.gitlab.com/community/vi...
We want to hear your ideas for topics. Remote? Security? Contributing to OS? Email suggestions to evangelists@gitlab.com.
We also love when community members present at GitLab meetups. Send an email to evangelists@gitlab.com if you’re interested in being the featured speaker at a future remote meetup.
A
Thanks
everyone
for
joining
the
gitlab
meetup
today
my
name
is
John
Coghlan
I'm
on
the
community
relations
team,
at
gate,
lab
and
I
manage
a
couple
programs.
The
meet
ups
program
that
has
recently
moved
to
all
virtual
and
our
get
lab
heroes
program,
which
is
a
recognition
program
for
our
top
community
contributors
and
I,
see
at
least
one
of
our
heroes
has
joined
us
today.
So
thank
you,
nikka
for
being
here.
A
I'll
put
that
on
your
tally
there,
but
yeah
one
thing:
I
always
like
to
share
at
the
beginning
of
meetup,
so
I'm
gonna,
put
a
link
in
the
chat
is
a
get
lab
code
of
conduct.
You
know
we
want
to
make
sure
that
the
community
is
welcoming
and
inclusive
to
everyone,
and
so
you
know
a
task
that
you
all
take
a
second
to
review
that
if
you
have
not
already-
and
if
anyone
has
any
concerns,
they'd
like
to
report
in
the
Xoom
chat,
you
can
send
me
a
direct
message.
A
There's
a
kind
of
field
to
field
where
you
can
toggle
from
everyone
to
an
individual,
so
feel
free
to
send
me
a
DM.
If
you
have
any
concerns
or
you
can
send
an
email
to
evangelist
at
gate
live.com,
if
you'd
like
to
report
any
code
of
conduct
violations,
so
yeah
we've
been
doing
these
virtual
meetups
for
a
while
for
about
six
weeks
now,
and
the
results
have
been
great,
as
you
could
see
in
the
chat,
we
have
people
joining
from
all
over
the
world
which
is
really
cool
to
see
and
yeah.
A
It
just
makes
for
a
fun
event
when
we
have
this
kind
of
global
scale
and
global
reach,
I
think
it
makes
for
more
diverse
audiences,
which
is
great,
more
accessible
to
more
folks
and
you
get
to
meet.
You
know,
folks,
from
different
parts
of
the
world
and
kind
of
different
cultures
and
different
perspectives,
so
really
cool.
Another
thing,
I,
like
about
the
virtual
meetups,
is
that
they're
a
little
bit
more
collaborative.
A
So
you
know
a
lot
of
times.
People
are
joining
us,
you
know
from
in
front
of
their
laptop.
Maybe
they
have
their
keyboard
and
mouse
with
them.
So
it's
a
little
bit
more
hands-on
and
we'll
get
into
some
of
that
towards
the
end
of
this
meetup,
and
it's
also.
It's
also
a
little
bit
easier
to
break
the
ice
when
we
kind
of
force
everybody
into
breakout
rooms
and
no
one's
you
know,
needs
to
go
and
kind
of,
but
into
a
conversation
to
meet
other
folks
in
the
community.
A
So
it's
the
facilitation
of
the
networking
piece,
is
also
a
cool
advantage
of
these
virtual
events
and
so
I've
been
enjoying
them
and
happy
to
be
here
with
all
of
you
today
for
folks
that
are
just
joining
the
think.
Get
life
can
be
idea.
I
just
want
to
give
a
quick
overview
of
you
know.
What
get
lab
is
so
Gil
I
was
a
complete
DevOps
platform
delivered
as
a
single
application.
So
it's
one
interface,
one
permission
model.
You
know
one
kind
of
platform
where
the
conversation
and
the
work
is
happening.
We
have
thousands
of
features.
A
A
There's
lots
of
great
information
there
from
how
to
set
up
your
desk
to
how
to
communicate
with
your
team
to
conducting
remote
interviews,
lots
of
really
helpful
information
for
people
that
are
new
to
remote
work
and
you're.
Our
handbook,
you
know,
includes
a
lot
more
information
than
that
day.
Labs
values
include
transparency
and
I
would
say
we're
one
of
the
most
transparent
companies
in
the
world,
in
addition
to
being
the
biggest
or
remote
company
in
the
world.
A
So
you
can
see
you
know
our
company
roadmap,
our
strategy,
everything
we
do,
how
I
run
my
programs,
how
every
run
sales
programs
is
all
documented,
our
handbook
and
available
for
you
to
see
you.
So
if
you're
looking
for
some
inspiration,
feel
free
to
check
that
up
so
today,
Ray's
going
to
do
a
presentation
on
contributing
to
get
lab,
then
we're
going
to
go
into
breakout
groups.
A
I'll
talk
a
little
bit
more
about
the
breakout
groups
when
brace
them
with
his
talk,
but
everyone's
going
to
be
assigned
to
a
room,
they're
gonna
be
random,
we'll
go
in
there.
We'll
have
some
group
conversation
then
we'll
come
back
to
the
manner
at
the
end,
but
you
know
no
pressure
to
participate
in
the
breakout
groups.
If
that's
not
your
thing-
and
just
you
know,
would
ask
that
folks,
you
know
kind
of
trying
to
be
present
with
us
today.
A
So
if
you
could
turn
off
your
slack
notifications,
close
the
other
tabs
that
you
have
open,
you
know-
and
just
you
know
take
this
time
for
yourself
to
you-
know,
learn
about
gitlab
and
listen
erase,
presentation,
I,
don't
know
some
folks,
you
know
stay
muted,
so
we
don't
distract
our
presenter
and,
if
you're
comfortable
turn
on
your
camera,
so
that
we
can
see
you
if
you
have
questions
along
the
way,
use
the
chat
box.
We'd
love
to
hear
from
you
and
and
I'll.
A
B
Thanks
thanks
John
and
welcome
everybody
I
see
like
Northup
like
20
people,
on
the
call,
so
it's
great
to
great
to
have
you
I
mean
first
of
all
hope
you
are
all
safe
and
well
Cheryl
Tillett
in
place
like
like
a
lot
of
us
are
and
yeah
I
mean
thanks
for
the
opportunity
to
talk
to
you
about
contributing
to
get
lab.
Sorry,
let
me
advance
my
slide.
So
in
addition
to
John
and
myself,
I
mean
Scott,
unfortunately
couldn't
join
us
today.
B
He
had
some
last-minute
thing
come
come
up,
but
he
helped
me
what
the
the
presentation
and
he's
here
in
spirits
and
he's
one
of
the
lucky
active
front-end
engineers
that
helped
helped
a
lot
with
community
contributions
and
he
helped
us
sort
of
pilot
this
content
when
we
did
an
in-person
event
at
scale
about
six
weeks
ago.
So
this
is
who
we
are,
and
you
can
click
on
any
of
these
links.
B
You
can
click
on
the
photo
of
me,
for
example,
that
you
can
get
you'll
be
taken
to
our
team
page
and
you'll,
see
our
Twitter
handles
and
and
get
lab
handles.
So
if
you
want
to
reach
out
to
us,
let
me
feel
free
to
do
that
and
I
posted
this
link
to
the
slide
on
Twitter
and
reddit
and
for
him
yesterday,
and
so
this
is
completely
open,
so
feel
free
to
refer
to
this
after
the
after
the
talk.
B
So
this
is
so
the
quick
agenda
I
mean
I
won't
go
through
all
the
all
the
topics
here,
but
I
wanted
to
sort
of
focus.
This
talk
on
on
you
or
even
like
people,
who've
never
contributed
before.
So,
if
you've
been
a
regular
contributor,
I
mean
this
might
be
a
little
too
basic
and
may
not
be
that
exciting
or
interesting.
So,
if
you're
more
experienced,
if
you
can
help
out
with
questions
on
unzoom
like
like
John
and
mention
so
I
mean
basically
I
mean
two
things:
I
want
people
to
get
out
of
after
this.
B
Meetup
is
first
of
all
like
how
worried
to
find
issues
that
you
can
contribute
to
and
and
work
on,
and
to
it's
just
a
basic
mechanics
of
you
know:
how
do
how
do
you
submit
your
first,
mr
so
during
the
breakout,
hopefully,
will
will
give
you
a
chance
to
do
that.
I
have
a
list
up
like
a
simple
documentation,
errors
that
I
found
over
the
last
week
or
so
that
that
people
can
work
on.
If
things
all
go
well,
you
should
be
able
to
hit
the
submit
button
on
your,
mr,
in
about
10-15
minutes.
B
B
So
if
you,
if
you
have
not
contributed
to
get
lab
in
the
past,
like
john
said,
we're
an
open
core
company,
both
our
enterprise
and
community
edition
of
the
software,
the
source
code
is
available
and,
and
the
community
edition
is,
is
it's
based
on
an
open
source
MIT
license,
so
we
welcome
contributions.
I
mean
both
on
you
know,
pay
version
up,
get
lab
and
and
community
additions,
and
one
of
the
things
that
people
ask
me
about
in
terms
of
the
get
like
community
is,
you
know
the
size
of
the
community.
B
That's
a
very
fair
question,
because
you
know
you
obviously
want
to
participate
in
a
community,
that's
growing
and
and
a
lot
of
other
fellow
contributors,
a
second
that
you
can
bond
with
or
or
connect
with
so
I
got.
This
is
a
grab
this
chart
from
the
main
contribute
page
on
on
give
up
calm.
So
a
couple
of
numbers
I
wanted
to
share
so
on
the
right
inside
of
the
slide,
the
blue
chart,
B
blue,
like
a
numbers
or
bars,
or
dots,
basically
show
the
number
of
contributors
over
the
past
couple
of
years.
B
In
2019
we
had,
you
know
close
to
900
people
contributing
to
get
lab.
What
Mars
request,
which
is,
which
is
pretty
phenomenal,
and
also
that
represents
almost
like
a
hundred
percent
growth
year
over
year
from
2018
to
2019,
so
yeah
I
mean
it's.
This
has
been
very
heartwarming
to
see.
Community
members
continue
to
grow.
So
if
you,
you
know,
joined
the
get
lab
open-source
project
you'll
be
joining
a
lot
of
good
company
and
even
in
terms
of
like
merge
and
Mars
we've
seen
like
a
steady
growth
from
2017
to
2024.
B
So
you
know,
we've
been
pretty,
obviously
both
John
and
I,
and
the
rest
of
the
gate.
Lab
team
have
been
very
excited,
but
these
with
these
growth
and
I
mean
some
of
these
numbers
already
need
to
be
updated.
I
mean
we
just
hit
like
a
3,000
contributors.
It
says
2500,
plus
and
I.
Think
when
I
looked
at
the
data
for
the
past
12
months,
we've
been
closer
to
200
vs.
185,
like
average
contributors
for
per
month,
and
we
have
a
monthly
release
cycle.
B
So
it's
so
I
mean
again
just
wanted
to
point
out
that
if
you
becoming
community
members
and
and
contribute
mirja,
quests
you'll
be
joining
a
flying
company.
A
lot
of
contributors
out
there
so
just
want
to
share
that
really
quick
and
so
wanted
to
highlight
the
four
areas
that
people
can
contribute
to
and
I
mean
people
like
when,
when
you
hear
a
merge
request
or
or
commits
people,
most
typically
think
about
code,
and
obviously
we
love
code
contributions
that
come
from
the
community.
But
there
are
three
other
areas
that
I
wanted
to
point
out.
B
I
know
I
left
code
towards
the
end,
the
next
slide,
so
that
I
I
mean
I
wanted
to
emphasize.
There
are
other
areas
where
people
can
contribute
to
and
you
don't
necessarily
need
to
be
a
ruby
or
go
expert
to
contribute
to
get
lab,
even
even
through
merge
requests,
so
I
mean
the
first
area
that
I
want
to
highlight
is
is
UX
design
if,
if
user
interface
and
UX
design
improvement
is
what
you're
you're
passionate
about
the
project
that
you
can
go
take
a
look
at
is
the
gives
it
get
web
design
system.
B
We
have
a
catchy
name.
Let
me
just
click
on
a
link
here,
so
you
can
see,
call
the
pajama
design
system
so
sort
of
catchy
name
for
it.
So
I
mean
it
provides,
you
know,
design,
guidelines
and
various
components
that
goes
into
our
our
UX
at
gate
lab.
So
if
you're,
if
this
is
an
area
that
you're
passionate
about
versus,
like
writing,
Ruby
code-
and
we
definitely
welcome
community
contributions
and
a
lot
of
our
regular
contributors
have
been
active
participants
here
in
the
pajama
design
system.
B
So
I
have
a
link
for
UX
issues
that
that
open
for
community
contributions,
and
we
also
have,
if
you
want
to
get
more
detail,
we
have
tutorial
slides
and
videos
from
from
the
hackathon
a
couple
of
months
ago
that
you
can
take
a
look
at
it's
I
mean
it's
not
a
long
videos
about
20
minutes
and
one
of
our
community
contributors
George.
You
went
through
details
about
pajama
design
systems
and
where
community
members
can
help.
So
that's
one
area,
that's
not
directly
code
related
and
the
second
one
is
translations.
B
B
Document
lab
comm,
you
don't
even
need
to
create
a
separate
account.
You
can
just
use
your
get
web
login
to
help
participate
in
translating
get
lab
in
two
different
languages,
so
you'll
see
I
mean
last
count.
I
had
was
about
48
plus
languages,
where
you'll
see
various
levels
of
translations
Amharic.
This
is
the
one
that
got
started,
probably
around
February
timeframe,
and
but
there
are
other
languages,
I
simplified,
Chinese
Japanese
in
German.
B
They
have
like
a
very
high
levels
of
completion
in
terms
of
the
strings
that
are
translated,
so
I'm
going
to
click
on
chairman
here.
It's
just
as
an
example.
I
saw
a
couple
people
from
Germany,
including
eco,
so
whoops.
It's
asking
you
to
login,
and
this
use
my
Caleb
ID
to
go
in
there.
So
here
you'll
see
a
list
of
translations
that
are
waiting
for
waiting
to
be
translated.
So
you
see
those
like
a
ones
highlighted
in
red
and
and
they're.
B
Also
like
the
suggestions
from
Google
Translate
and
other
tools
that
you
can,
you
can
use
as
a
guide
or
you
can
just
enter
your
own
translations
here.
So
this
is
an
area.
That's
almost
like
I
mean
I,
don't
know
exactly
what
the
percentage
is,
but
if
you
look
at
the
participants,
people
that
are
translating
get
loud
I
mean
these
are
most
almost
exclusively
community
Durban.
B
So
just
want
to
highlight
translation
as
another
area
that
people
can
contribute
to
you
and
participate
in
and
again
there's
a
hackathon
tutorial
video
that
was
sorry
created
by
a
community
member
Hannes
a
couple
of
years
ago.
So
I
encourage
you
to
take
a
look
at
that
and
I
I
have
a
blog
post.
That
I
think
I
published
about
fifteen
months
ago.
If
you
want
to
learn
more
details
about
people
have
been
contributing
to
translations.
So
that's
another
area
where
we
can
help
you
can
help
us
out.
B
Moving
to
the
next
slide,
so
I
mean
I'll,
be
talking
about
documentation
in
a
bit
before
we
go
to
the
breakout
session,
I
mean
that
that
if
you
go
to
doc
socket
lab
comm,
we
you
know,
that's
our
you
know
quote
unquote
single
source
of
truth.
If
you
want
to
learn
about
our
product
or
even
contributing
to
get
lab,
things
are
documented
in,
in
doc
sake
lab
calm,
but
you
know
we
obviously
welcome
your
feedback
in
terms
of
you
know.
B
How
do
we
improve
documentation
so
from
simple
spelling
or
grammar
mistakes
to
I
mean
if
things
are
not
very
clear,
I
mean?
Obviously
you
know
we
have
a
great
technical
writing
team
that
worked
pretty
closely
with
the
product
team.
Members
to
you
know,
develop
documentation,
but
I
mean
we
get
great
feedback
from
users
about
why
certain
things
aren't
very
clear
as
its
as
its
laid
out
in
documentation
and
in
contributing
to
documentation
is
pretty
simple
and
let
me
go
to
a
Doc's
page
just
to
demonstrate
and
go
through
this
in
the
breakout
session
as
well.
B
So,
let's
say
like
you're
on
this
page
and
you
find
like
a
typo
or
simple
things
you
want
to
fix.
All
you
need
to
do
is
basically
scroll
all
the
way
down
to
the
page
and
you'll,
see
this
edit,
this
page
button
or
link
and
just
click
on
that,
and
then
you
know
basically
you'll
be
able
to
hit
the
edit
button
and
then
proceed
from
there.
B
So
I
mean
it's
pretty
straightforward
and
streamlined
I
mean
this
ghost
applies
not
just
to
documentation,
but
are
also
our
website
as
well
about
git
lab
comm.
If
you
find
an
area
that
you
want
to
contribute
to
just
hit
the
edit
this
page
button
at
the
bottom
and
you'll
be
off
on
you'll,
be
on
you're,
well
on
your
way
to
make
your
contributions
and
if
you
haven't
created
a
fork
previously
it'll
even
prop
you
to
create
a
fork.
You'll
see
a
button
up
on
the
right,
so
it's
a
pretty
streamlined
way
of
doing
it.
B
So
you
don't
have
to
figure
out
where
the
documentation
is
in
the
directory
structure
and
then
using
the
command
line.
So
that's
a
simple
way
that
you
can
start
contributing
to
get
lab,
but
with
your
first
request
and
the
last
but
not
least,
you
know
if
you're
experienced
developer
in
Ruby
or
other
languages
that
get
web
uses
like
JavaScript
for
a
lot
of
different
front-end
work.
You
will
mostly
like
have
to
install
a
git
web
development
kit
or
GDK
I
mean
GDK.
B
Basically
lets
you
create
a
self-contained
get
lab
environment
on
your
on
your
workstation
or
your
laptop
and
I
mean
it
does
take
time
and
effort
to
get
this
installed.
I
think
for
most
people,
I
mean
they
get
this
up
and
running
in
about
an
hour
or
two
and
I
mean
you'll
probably
need
a
decent
machine
with,
for
example,
with
four
gigs
of
memory.
But
you
can
get
these
more
details
on
this.
B
B
So
I
mean
Scott's
not
here,
but
if
you
have
further
questions
on
the
GDK
again,
this
is
a
little
bit
more
involved
and
requires
some
resources
in
terms
of
good
local
machine
and
and
obviously
technical
expertise
but
happy
to
answer
any
questions
you
have.
If
you
reach
out
to
me
either
directly
or
on
Gitter
that
I'll
talk
about
in
a
minute,
so
let
me
pause
here
really
for
a
second
I.
B
A
B
So
if
you
search
for
this
and
get
lab
in
Twitter,
you'll
probably
see
people
celebrating
their
the
mugs
they
received,
and
this
we
count
everything
in
terms
of
MRI,
so
it
doesn't
have
to
be
code.
We
count
documentation.
We
count
updates
through
our
handbook,
for
example
like
a
simple
typo,
so
anybody
with
the
first
contribution
will
roll
out
a
new
process,
so
you
can
order
a
mug
when
you,
when
you
have
your
first
time,
armor
all
right.
B
B
B
Basically,
you
know
signifies
that
the
product
and
engineering
team
has
looked
at
these
issues
and
they
know
this
is
something
that
I
mean
gillip
engineers
aren't
going
to
work
on
in
the
immediate
future.
So
that's
why
you
have
the
milestone
of
backlog
and
added
a
label
accepting
merger
quest.
So
this
basically
shows
you
over
like
1840
issues
that
people
can
pick
up
and
I
also
chose
a
weight
of
one.
So
we
have
like
a
weight
in
terms
of
difficulty,
one
being
easiest
and
ten
being
the
hardest.
B
So
if
you
want
to
pick
up
an
easy
issue
that
you
want
to
work
on,
this
is
a
reasonably
query.
To
start
with
so
I
mean
you
have
issues,
I
mean
here's,
a
music
UI
or
user
user
experience
related
one
from
enry
k
like
some
of
the
front
end
ones
that
I
see
here
so
here,
issues
that
you
can,
if
you're
interested
in
working
on
them.
You
can
just
mention
me
just
type
in
our
take
in
the
comments
as
I'm
interested
in
working
on
this
and
I'll
be
happy
to
assign
the
issue
to
you.
B
B
We
also
have
a
label
for
first-time
contributors
so
but
for
some
contributors
and
if
I
just
rerun
the
query
here,
this
issue
will
get
whittled
down
to
about
eight
18
issues.
So
I
mean
there
are
a
couple
of
different
ways
that
you
can
do.
You
can
search
like
a
certain
labels
like
good
for
good
for
first-time
contributors
and
then
the
other
label
that
you
can
look.
If
you
just
only
interested
in
documentation,
you
can
add
all
documentation
label
here
as
well.
B
So
if
you
want
to
continue
narrowing
it
down
to
find
an
issue
that
you
want
to
work
on
and
as
I
mentioned,
if
there
are,
there
are
certain
issues
that
you're
interested
in
working
on
like
feel
free
to
ping
me
or
anybody
else.
On
the
issue
from
gitlab
and
happy
these
assigning
to
you
once
you
have
the
are
going.
So
that's
a
one,
quick
way
of
sort
of
a
quick
way
of
finding
issues
that
you
can
work
on.
B
But
if
you
find
other
like
improving
areas,
for
example,
if
there's
a
documentation
change
that
you
want
to
make,
but
you
don't
you
know
you
can't
find
an
issue.
That's
associated
with
that.
Don't
worry
about
it!
Just
create
an
EM
are
having
an
issue,
is
not
a
requirement.
I
think
some
communities
what
they
have
rules
like
you
can't
work
on
anything
without
an
issue,
but
that's
not
the
case
that
get
lab.
B
If
you
want
to
create
an
issue
and
create
an
mr
subsequently
that
that's
that's
great,
but
I
mean
creating
an
issue
or
having
an
issue,
it's
not
an
absolute
requirement.
So
if
you
find
something
that
you
you
want
to
improve
or
fix,
you
know
we
welcome
your,
mrs,
and,
and
just
you
know,
ping
me
or
there's
a
get
lab,
so
we
can
triage
it
and
get
to
the
right
reviewers.
B
So
people
here
ask
questions
and
a
lot
of
times
I
jump
in
and
and
help
out
with
questions
as
you're
contributing,
but
we
have
like
active
community
members
like
rajendra
and
the
ticket
that
are
very
active
in
terms
of
answering
questions
or
helping
you
out.
So
this
is
a
great
resource
we
have
close
to
like
500
people
in
the
contributor
channel
and
there's
in
a
related
channel
for
heroes
as
well.
So
guitar
is
a
great
tool
to
use
and
again,
like
you,
can
just
log
in
with
your
get
lab,
ID
or
a
Gil,
a
blog.
B
You
know,
or
your
Twitter
account,
so
you
don't
have
to
create
a
separate
separate
account
to
get
involved
in
having
conversations
and
get
her.
So
this
is
a
great
place
to
reach
out
to
other
community
members
myself
and
get
help
as
you're
working
on
your
merge
request,
and
we
also
have
a
kit
lab
a
group
of
people
called
mergers,
request,
coaches,
there's
a
group
of
I
believe
we
have
10
people,
they
have
experience
in
both
like
back
in
in
front-end
and
other
areas.
B
You
can
find
them
on
our
team
page
that
I
referenced
earlier,
but
you
can
also
mention
them
directly
by
typing
this
text
here
in
your
whoops.
Sorry,
the
wrong
key
on
on
your
merger
quest
to
get
their
attention
for
some
reason.
If
your
MRI
hasn't
been
triage
in
in
a
timely
fashion
or
you
don't
feel
like
you're,
getting
people's
attention
feel
free
to
reach
out
to
the
coaches
and
the
other
thing
I
wanted
to
point
out.
I
mean
not
just
the
coaches,
but
it's
a
completely
fair
game
to
reach
out
to
anybody.
B
Get
lab
I
mean
we're
John
and
I
argue
lab
employees.
But
before
that
work
you
lot
of
community
members
and
we
we
owe
it
to
everybody
in
the
community
whether
you
work
for
get
leva
or
not
to
to
be
responsive.
So
if
you
feel
like
your
question,
is
not
getting
answered
or
things
are,
I
mean
people,
for
whatever
reason
are
not
being
responsive,
feel
free
to
reach
out
to
people
directly.
But
you
know,
if
you
know,
even
if
you
don't
work
at
your
lab,
it's
a
completely
fair
game.
B
It's
a
normal
practice
within
the
company
and
then,
if
you
want
to
read
a
long
list
of
like
a
developers
and
maintainer
I
also
have
a
link
to
the
page
here.
So
you
can
sort
of
identify
people
that
you
want
to
reach
out
to,
but,
like
I
said,
don't
be
shy
about
reaching
out
to
people
that
get
lab
or,
and
hopefully
you'll
get
the
help
you
need.
If
your
preference
is
to
you
know,
communicate
via
email,
it
send
an
email
to
contributors,
I
get
lab
comm.
B
This
email
comes
to
me
and
my
manager,
David
Piniella,
so
and
then
yeah.
So
email
is
another
channel
where
you
can,
where
you
can
reach
out
to
so
one
quick
thing.
So
in
couple
of
weeks,
we'll
have
our
quarterly
hackathon.
That's
that's
going
to
happen.
So
this
is
a
virtual
event
and
I
was
excited
to
come.
Do
this
virtual
meet
up
today,
because
this
is
a
great
segue
into
the
hackathon
in
a
couple
of
weeks.
So
this
is
a
virtual
event.
That's
held
over
two
days
and
it's
open
to
everybody.
B
So
it's
a
fun
event
to
participate
and
you'll
definitely
see
a
lot
more
communication
and
chatter
happening
on
the
git
er
channel.
So
it's
a
good
way
to
sort
of
bond
with
other
community
members
as
well,
so
I'll
be
updating
the
hackathon
landing
page
sometime
today,
with
the
will
announce
the
tutorial
session
and
the
prizes
so
I
mean
I,
encourage
everyone
to
participate
on
May,
13th
or
14th.
It's
happening
in
a
couple
of
weeks.
B
So
that's
a
quick
sort
of
advert
advertising
on
a
hackathon.
So
before
we
go
to
the
breakout,
just
a
couple
things
I
wanted
to
do.
I
mean
one
of
the
things
I
wanted
to
do.
If
you
have,
especially,
if
you
have
any
head
and
experience
submitting
an
MRI
like
we
want
you
to
go
through
the
process
or
become
more
familiar
with
that
and
I
created
an
issue,
simple
documentation,
fixes
or
typos
that
I
found
that
people
can
pick
up.
B
So
when
you
create
an
MRI,
just
mention
me
in
DMR,
I
also
had
a
simple
text
text
in
here
that
you
can
copy
and
paste
just
just
get
my.
This
is
a
good
way
to
get
my
intention-
and
just
tell
me
this
is
from
the
virtual
meet
up
today
and
if
you
submit
your
mrs,
by
end
of
the
day
tomorrow
in
your
local
timezone,
be
happy
to
send
out
a
pair
of
get
lab
socks,
that's
been
pretty
popular,
so
yeah.
B
So
hopefully
this
is
sort
of
a
fun
way
to
sort
of
get
your
feet
wet.
If
you
haven't
done
it
before
and
then
let
me
just
quickly
go
to
the
issue.
So
I
think
I
have
about
like
a
twenty
docs
improvement.
I
mean
these
are
usually
like
quick
fixes
like
like
the
first
one,
is
like
a
missing
the
word
too.
So
I
try
to
be
exploited
explicit
in
terms
of
where
the
errors
are
so
I.
B
John
I
assume
we'll
go
into
like
a
two
breakout
rooms
right
and
then
you
know
we
can
this
split
this
list
in
half
I'm
John
in
you're,
like
a
meetup
group,
you
can
take
the
first
major
first,
two
major
bullet
points
like
a
documentation,
guidelines
and
contributor
and
development.
Docs
I
think
there
are
about
ten
to
eleven
issues.
There
and
I
could
take
the
rest
and
then
encourage
people
to
submit
an
M
R,
and
then
then
we
can
go
from
there
or
you
know,
I
don't
want
to
force.
People
do
submitting
an
M
R.
B
If
you
want
to
just
ask
questions
or
if
you
want
to
chat
about
something
else,
is
completely
fair
game
as
well,
but
if
you
want
to
submit
an
MRI
even
after
the
call
by
in
the
day
tomorrow,
be
happy
to
review
them
and
and
then
help
them
get
it
get
in
triage
or
even
merge
them.
If
it's
a
if
it's
a
quick
fix
that
I
can
merge.
B
C
B
It
probably
won't
show
up
on
the
query,
because
I
I
didn't
add
like
accepting
contribution,
accepting
merge
request.
That's
my
bad,
but
yeah.
If
you,
if
you
crave
for
good
for
a
first
time,
contributors
you'll,
definitely
see
it
so.
Okay,
thank
you
just
do
that.
But
you
know
that's
a
very
good
question,
but.