►
Description
In this video Rajendra shares why he started contributing to GitLab and how he was able to further develop his software development skills through his contributions.
A
A
So
I
want
to
first
of
all
introduce
rajendra,
and
I
I
know
that
regender
is
not
gonna,
do
this,
because
he
doesn't
like
to
talk
about
himself
but
just
wanna
to
share
a
couple
of
stats.
Let
me
make
sure
I'm
sharing
my
screen.
I
don't
think
I
am
so
here
we
go.
I
wanted
to
share
a
couple
of
stats
with
you.
I
just
did
a
query.
This
is
vitergia
is
the
dashboard
we
use
for
community
contribution.
B
A
B
A
Got
married,
so
that's
that's
pretty
amazing!
So
definitely
appreciate
your
contribution.
I
think
you
started
contributing
about
a
year
ago,
so
I
thought
your
perspective
would
be
interesting,
like
as
in
terms
of
like
getting
started,
why
you
got
started
and
then
how
you
gain
like
a
further
experience
contributing
over
over
the
past
12
months
or
so
so.
B
B
First
of
all,
thanks
for
having
me
for
this
interview,
like,
as
you
are
also
really
excited
to
share
about
my
channel
so
yeah,
so
I'm
rajendra
based
out
of
mumbai,
india.
I
work
with
the
open
source
team
at
bronx.
Apart
from
open
source
contributions,
I
like
to
travel
as
everyone
like
anywhere
and
everywhere.
Then
I
like
reading
some
books
on
financial
markets
or
any
products
like
I
finance,
is
my
second
interest.
But
if
I
was
not
a
software
engineer,.
A
There's
a
lot
of
movie
watching
going
around
with
the
shelter
in
place,
I'm
doing
a
lot
of
that
myself
spending
a
lot
of
time
on
things
like
netflix
and
also
avid
traveler
myself,
but
unfortunately
that
hasn't
been
possible
over
the
past
few
months
and
hopefully
we'll
be
able
to
do
that
soon
enough,
but
yeah.
So
I
think
I
mentioned
earlier.
A
I
think
you
started
contributing
about
like
12
months
ago,
and
I
you
know
this
is
an
often
question
that
I
ask
when
I,
whenever
I
meet
like
the
new
or
recent
contributors
so
and
I
mean
what
drew
you
to
contributing
to
gitlab,
what
was
your
motivation
and
heavy
use
like
you
know,
I'm
guessing
you
use
gitlab
before
you
started
contributing
to
your
lab.
So
if
you
can
talk
a
little
bit
about
that,
I
think
that
would
be
great.
B
Yeah
so
after
joining
my
current
organization
in
20
right
after
college,
so
I
started
learning
about
you
know
lot
of
stuff
about
writing
good
code
thinking
about
educations
of
a
problem
and
ways
to
handle
it.
But
I
really
wanted
to
you
know
sort
of
be
good
at
architecture
being
good
at
post
structure.
You
know
how
things
flow
inside
a
code
when
a
request
comes
to
a
machine
or
something
like
that.
How
to
so.
B
That's
when
I
thought
I
had
to
learn
this
and
best
way
is
to
you
know,
contribute
to
a
fully
open
source
project
and,
prior
to
this,
as
you
said,
yes,
I
was
a
gitlab
user
for
my
personal
projects
and
I
knew
it
was
fully
open
source,
and
that
was
a
point
like
when
I
thought
in
order
to
learn
about
good
architecture.
What
it
looks
like,
or
you
know,
learn
better
ways
of
doing
something
like
if
I,
if
I
know
how
to
write
architects,
I
I'm
sure
there
is
better
way
to
write
them.
So
I.
B
Mr
in
master,
now
it's
like
more
like,
as
you
said,
during
the
hackathon,
so
it's
like,
I
contribute
almost
daily,
if
not
four
contributions.
I
at
least
check
the
comments
or
you
know,
ask
for
help,
and
I'm
stuck
so
all
in
all
like
I
have
no
intentions
of
what's
able
to
stop
being
contributing
to
gitlab
but
yeah,
so
main
motivation
to
start
contributing
was
to
learn
good
ways
of
doing
a
single
thing
and
learn
about
good
architecture
and
learn
about
good
food.
A
Cool
so
it
almost
sounds
like
it
was
like
a
year.
You
already
have
a
full-time
job,
but
you're
almost
like
you're
taking
another
like
a
course
like
after
work,
I
mean
obviously
it's
self-paced,
and
then
I
mean
you
know,
gitlab
being
open
source,
you're
sort
of
able
to
look
under
the
hood.
If
you
will,
I
mean
look
at
the
code
base
and
and
documentation
is,
is
it's
probably,
it
sounds
like
what
you
did
like
so
so
I
mean.
A
B
A
B
A
A
So
yeah
I
mean
that's
really
interesting
because
you,
you
sort
of
started
looking
at
what
kind
of
issues
are
are
open
and
that
sort
of
gave
you
a
window
into
areas.
Where
I
mean
you
can
you
can
contribute
or
look
into,
and
then
I
mean
like,
like
I'm
just
clicked
on
one
of
the
issues
that
was
at
the
top
of
the
page.
I
think,
like
you
noted,
a
lot
of
the
issues
are
pretty
detailed
and
and
pretty
descriptive,
and
I
mean
this.
A
B
B
A
A
Right,
okay!
Well,
this
is
interesting
because
I
mean
I
think,
a
lot
of
people
say
I
just
you
know,
looked
into
different
files
and
look
explore
different
directories
or
look
at
docs.gitlab.com,
but
I
think
yeah
I
mean
this
is
definitely
definitely
another
way
of
doing
it.
Just
look
through
the
list
of
issues
that
everyone's
working
on,
because
I
mean
issues
are
not
just
for
community
members,
it's
for
even
for
gitlab
team
members
will
be
maybe
picking
up
picking
these
up
as
well.
So
yeah
I
mean,
I
think,
that's
a
good
point.
A
It's
almost
like
looking
at
future
work
or
future
demand
for
for
work.
That
needs
to
be
done.
So
this
is
another
interesting
way
of
way
of
doing
it
and
I
think,
like
you
mentioned,
you
know,
getter
in
case
people
don't
know
I
mean
this
is
where
a
lot
of
community
members
and
gitlab
team
members
sort
of
hang
out-
and
I
have
an
example
here-
there's
a
lot
of
gdk
discussion
going
on
that
happen
overnight.
A
My
time-
and
I
know
I
know
you
are
rajendra
and
lee
ticket
another
like
that-
have
been
very
active.
So
this
is
where
a
lot
of
people
hang
out,
and
this
is
where
people
tend
to
ask
questions
like.
I
have
a
question
about
this
issue
and
then
I
think
this
is
a
good
good
resource
and
you
can
get
help
from
people
like
rajendra
and
others
so
so
sort
of
going
back
to
like
the
early
days.
A
I
mean
you
mentioned
you,
you
sort
of
you
explain
how
you
sort
of
search
through
issues
to
find
areas
to
work
on
in
general.
What
you're,
like
you
know
when
you
started
submitting,
merge
requests?
What
were
some
of
your
approaches
like?
What
were
I
mean
you?
You
talked
about
like
a
specific
labels
that
you
look
for
for
to
to
search
for
type
of
issues
that
you're
interested
in.
But
what
were
some
of
the
approaches
when
you
started?
B
Yeah,
so
as
as
any
contributor
would
do
you
know,
I
started
off
with
smaller,
smaller
mrs
making
smaller,
I
think
smaller
and
smaller,
like
fix
it
type
of
pixel
documentation,
screen
or
fix
some
note
on
the
front
and
front
page,
because
for
me
personally,
I
really
feel
happy
and
get
more
excited
when
mr
gets
merged
into
master
of
a
huge
project,
which
is,
you
know,
contributed
by
a
lot
of
developers.
The
end
product
is
used
by
a
lot
of
users
and
myself
being
a
user.
So
for
me
this
was
the
oh.
B
Yes,
I
got
my
mr
into
the
master
feeling
that
you
know
I
used
to
look
for.
So
that
is
the
main
reason
I
started
off
with
smaller
issues
and
making
smaller.
Mrs
because
I
knew
if
I
started
with
bigger
issues,
you
know
changing
api
code
or
changing
model.
That
would
take
a
bit
of
an
extra
time
because
for
that
one
we
need
a
context
on
what
changes
we
are
making.
B
Second,
we
need
to
know
the
best
way
to
do
it
and
the
practice
that
is
followed
by
gitlab,
so,
for
example,
for
adding
a
new
api,
we
use
the
grey
framework
now,
prior
to
this,
I
never
you
know,
used
great
framework
for
any
of
the
projects
or
anywhere
else
so
for
adding
an
api.
I
had
to
you,
know,
read
about
and
have
basic
understanding
about
what
breakthrough
case
and
so
yeah
that
needed
some
time
so
api
addition
was
like.
I
started
off
at
a
later
part
in
the
contribution
stage,
so
in
january.
A
A
B
A
That
takes
a
little
while
and
if
you
tackle
a
substantial
project,
I
mean
that
that
it's
obviously
not
very
easy
to
sort
of
figure
out.
The
mechanics
like,
I
think
documentation
is
a
great
example.
You
you
improve
the
paragraph
or
even
fix
a
simple
typo.
I
think
you
get
a
sense
as
to
how,
like
your
review,
process
works
and
what
the
mechanics
are.
A
A
That
was
that
was
very
impressive,
and
this
is
the
thing
that
I
once
also
want
to
stress
to
other
community
members
that
might
be
watching
the
recordings
of
I
mean
I'm
a
gitlab
employee,
but
before
that
I'm
gonna
get
like
community
member.
So
if
somebody
from
the
community
reaches
out,
I
owe
I
owe
it
to
them
to
respond
in
a
you,
know,
a
reasonable
time
frame
and-
and
I
need
to
make
a
best
effort,
I
need
to
put
a
good
effort
into
doing
that,
and
that
applies
for
everybody
within
the
gitlab
team.
A
You
mentioned
like
people
like
clemen,
like
engineering
manager,
other
engineers
and
even
product
managers.
I
mean
I'm
pretty
confident.
I
don't
know.
I
wasn't
participating
in
all
the
discussion,
but
I'm
pretty
confident
that
they
got
back
to
you
within
a
recent
amount
of
time
and
they
were
very
helpful
and
then
so
I
mean
that's
another
thing
I
want
to
stress
like
this.
This
sort
of,
like
you
know,
that's
one
of
the
things
I
love
about
the
gitlab
culture
like
it
doesn't
matter
whether
you
work
at
gitlab
or
you're.
A
You
know
where
you're
based,
whether
you're
from
what
a
community
member
like
we,
we
always
want
to
treat
each
other
with
respect
and
then
be
responsive.
So
I
want
to
encourage
people
to
to
sort
of
follow
what
regenda
did
is
like
what
rajendra
did
and
and
not
be
shy
about
asking
for
help
and
and
asking
questions.
So
I
so
yeah.
I
I
I
really
like
the
I
mean
what
you
just
said
it
about.
You
know,
earl
how
you
got
through
the
early
learnings.
It
wasn't
just
reading
through
documentations
or
issues.
B
B
A
B
A
B
B
A
So
that's
that's
awesome
to
see.
So
I
think
at
this
point
we'll
sort
of
wrap
up
the
part
one
of
the
discussion,
because
I
wanted
to
sort
of
break
this
up
in
two
like
to
talk
about
your
early
days,
contributing
to
get
lab
and,
in
the
second
part
of
the
recording,
we'll
talk
about
once
you
got
over
the
hump
of
becoming,
I
mean
getting
experience
as
an
early
contributor.