►
Description
This video provides an overview of how to Contribute to GitLab for Students at TOBB University of Economics and Technology who have a class assignment to contribute to an open-source project.
This is the first iteration - much more to come as we continue to build out the Student Contributor experience.
A
A
As
we
found
out
this
week,
dr
gary's
software
engineering
class
has
an
assignment.
Our
students
are
encouraged
to
contribute
to
an
open
source
project
and
we're
very
excited
that
the
students
are
reached
out
and
are
contributing
to
gitlab.
So
we
put
together
this
workshop
to
help
guide
all
of
the
students
to
make
their
contributor
journey
very
successful.
To
make
sure
that
you
have
all
of
the
things
you
need
to
get
started
and
then
to
welcome
you
into
our
community.
So
let's
go
ahead
and
jump
in
first.
A
We
want
to
start
by
covering
our
get
lab
community
code
of
conduct.
We
start
with
this
pledge
because
we
want
to
make
sure
that
our
community,
our
contributors
and
our
maintainers
all
make
participating
in
our
project
and
community
a
harassment
free
experience
for
everyone.
We
can
go
ahead
and
take
a
look
closer.
Look
at
our
code
of
conduct.
A
Gracefully
accepting
constructive
criticism,
focusing
what's
best
on
the
community
and
showing
empathy
towards
other
community
members.
You
can
scroll
through
the
page.
I
know
you
have
the
the
doc
block
all
the
links
here,
so
you
can
check
out
our
responsibilities,
scope,
enforcement.
What
I
do
want
to
point
out
is
that,
while
you're
contributing
or
engaging
in
our
community,
if
you
have
any
concerns
or
things
that
you
want
to-
let
us
know
please
feel
free
to
reach
out
to
us
at
conduct
at
getlab
gitlab.com,
all
right.
Let's
get
back
to
contributing.
A
Let's
talk
a
little
bit
about
what
is
open
source
software,
so
open
source
software
is
where
anyone
is
freely
licensed
to
use
copy,
study
and
change
the
software
in
any
way.
The
word
license
is
important
there,
because
open
source
projects
do
actually
have
licenses
associated
with
them,
allowing
for
the
distribution,
maintenance
and
changing
of
the
software
itself.
So
we're
not
going
to
get
into
that
today,
but
it's
just
something
to
be
aware
of
with
open
source
software.
The
code
is
openly
shared
and
people
are
encouraged
to
voluntarily
improve
the
design
of
the
software.
A
Changes
made
to
the
software
are
generally
accepted
and
maintained
by
the
code
maintainers
of
the
project
and
sometimes
they're
they're
volunteers,
they're,
active
community
members,
and
sometimes
they
work
at
the
company
themselves
and
that's
the
case
of
gitlab.
If
the
project
is
associated
with
the
company,
the
code
is
generally
kept
in
central
repositories
and
discussions
take
place
between
contributors,
maintainers
owners
and
users
of
the
code
as
well.
A
A
It's
also
a
really
great
way
to
build
your
technical
portfolio
with
the
public
record
of
your
contributions,
especially
if
you
are
a
student
in
school
and
you
don't
yet
have
your
first
job
coding
or
or
you
don't
have
your
first
internship
and
you
want
to
start
building
up
that
portfolio.
We
really
encourage
students
to
consider
making
code
contributions
to
get
started.
A
A
A
A
Are
there
issues
that
are
identified
that
are
great
for
new
contributors?
Are
there
communication
channels
and
forums
to
communicate
with
other
community
members?
How
responsive?
How
active
are
people
watching
those
issues
in
the
repositories?
Is
there
feedback
or
you
know,
are
you
going
to
be
waiting
for
months?
So
those
are
some
things
to
consider,
and
that
also
is
their
community
code
of
conduct.
A
So
we
have
a
list
of
projects
that
are
open
source
projects
that
are
stored
on
git
lab
itself.
So,
just
to
be
clear:
git
lab
itself
is
an
open
core
product,
but
then
we
also
host
open
source
projects
as
well,
so
you
can
contribute
to
gitlab
or
you
can
contribute
to
the
many
different
projects
that
are
hosted
on
gitlab,
but
we
can
go
ahead
and
open
up
this
link
and
again
you
have
all
of
the
links.
We
encourage
you
to
take
a
look,
and
this
is
definitely
not
a
comprehensive
list.
A
These
are
just
ones
that
we
are
aware
of,
and
you
can
see
here
we
have
a
description
and
then
we
have
links
and
the
links
may
take
you
to
the
project
itself
or
to
the
website
to
find
more
information.
So
for
your
assignment,
I
encourage
you
to
take
a
look
through
this
list
and
you
may
find
something
that
interests
you
to
contribute
to.
A
As
I
mentioned,
they
have
a
really
active
community.
I
think
that
that's
one
of
the
most
exciting
things
about
contributing
to
gitlab
is
that
there
are
a
lot
of
individuals
who
contribute
as
part
of
our
community.
We
have
great
ways
of
recognizing
our
contributors
through
our
hackathon,
our
most
valuable,
our
mvp
for
different
releases,
and
then
we
also
have
our
gitlab
heroes
program
and
this
con.
A
This
graph
shows
you
how
we've
been
able
to
grow
the
community
over
the
last
couple
years
and
again,
we're
excited
to
always
welcome
students
into
our
contributor
community.
So
let's
go
ahead
and
jump
into
how
you
actually
contribute
to
get
lab.
So
we
have
a
contribution
guide
that
we've
built
for
our
hackathons,
but
it's
a
great
place
to
get
started
even
if
you're
contributing
inside
the
hackathon
or
just
as
part
of
your
class
assignment.
A
And
what
we
really
want
to
mention
here
again
is
our
values
and
our
code
of
conduct
are
at
the
top,
but
then
we
have
basically
six
different
tracks,
which
are
ways
to
contribute:
there's
development,
documentation,
translation,
ux
design
and
then
engagement
and
project
templates.
I
would
say
these
first
four
are
actually
you
know,
considered
code
contributions,
and
this
is
probably
really
what
you're
looking
for.
A
So
you
can
fix
anything
from
fixing
typos
all
the
way
to
organizing
our
documentation,
there's
a
lot
of
different
ways
to
contribute,
and
if
this
is
what
you're
interested
in,
you
can
go
ahead
and
click
on
more
on
contributing
to
documentation
and
you'll
be
taken
to
another
link
here
and
for
each
of
these
different
tracks.
There's
specific
directions.
A
So
that's
a
great
tip
is
to
follow
the
directions
that
are
associated
with
the
track
that
you're
interested
in
contributing
to.
So
the
first
thing
it
says
is
to
view
the
documentation
issues
that
are
curated
specifically
for
new
contributors,
so
this
is
really
exciting
in
a
way
that
we
at
get
lab
really
encourage
new
contributors
to
enter
the
community.
So
let's
go
ahead
and
take
a
look
at
that
link
as
well.
A
So
you
want
to
look
for
both
of
those
things
and
then,
in
this
case
we're
looking
for
documentation-
and
you
can
see
here
it's
sorted
by
created
date
and
we
can
just
go
ahead
and
take
a
look
at
one
of
these.
So
allow
registering
an
agent
without
a
config
file.
Let's
go
ahead
and
open
that
up,
and
this
is
going
to
show
you
what
the
definition
of
done
is
what
the
problem
is
to
solve
some
additional
ideas
and
some
tips.
A
And
then
you
can
see
here
that
some
people
have
kind
of
already
been
collaborating
on
here,
and
the
scope
is
being
more
well
defined
and
there's
been
some
some
movement
here.
So
this
is
a
great
one
to
take
a
look
at
and
again,
you
can
see
here
good
for
new
contributors,
accepting
merge
requests,
some
of
the
other
things
that
you'll
find
are,
for
example,
this
has
kubernetes
management
associated
with
it.
It's
ready
for
development,
backend
documentation.
A
A
A
So
the
labels
really
provide
you
a
lot
of
information
for
for
what?
For
what
issues
to
choose
and
then
notice,
once
you
pick
an
issue
that
you'd
like
to
work
on
in
documentation,
you
want
to
you
want
to
at
mention
gl
dash,
docs
stream
and
they're
going
to
assign
it
to
you.
I
mean,
if
you
happen
to
you,
know,
pick
an
issue
that
that
is
already
chosen.
A
All
right.
Let's
go
back
to
our
main
main
page
here,
oops!
Sorry
about
that,
all
right!
Let's
go
back
to
our
main
page
here.
Let's
take
another
look
at
a
different
one,
so
development
is
really
a
little
bit
more
into
the
code
base
in
terms
of
fixing
bugs
or
adding
a
new
feature
or
helping
with
the
review
and
gitlab
has
a
lot
of
different
options
for
developers
from
all
backgrounds.
A
Here
we
have
a
list
of
the
top
10
projects
to
contribute
to
on
gitlab.
You
can
find
the
project
and
then
you
can
find
the
language
and
the
technology
that's
required
to
to
contribute,
and
so
this
is
a
great
way
to
look
through
this
list
and
say:
okay.
Well,
I
know
a
little
bit
of
ruby
or
css,
and
so
this
would
be
a
great
one
for
me
to
check
out
and
then
you
can
also
go
ahead
and
look
at
this
list
of
issues
to
work
on.
A
A
And
here
we
have
assignment
equals,
none
and
again.
That
means
that
a
contributor
in
the
community
is
not
currently
working
on
that
one.
So
that's
a
great
thing
to
look
out
for
and
then
this
one
is
accepting
merge
requests
and
you
can
see
here
we
have
it
sorted
by
by
ascend
name.
So
here's
some
examples
ensure
intelligence
works
in
conjunction
with
highlight
js
and
again
there
may
be
some
other
links
here.
There
may
be
some
questions.
A
And
if
we
go
back
to
this
page
here,
you'll
see
if
you
scroll
down,
there
is
actually
a
development
guide,
and
this
walks
you
through
how
to
get
set
up
to
contribute
to
the
code
base.
So
you'll
create
a
public
fork
of
any
gitlab
project.
You
want
to
download
and
set
up
your
development
kit
and
your
gdk
readme,
and
then
you
want
to
choose
your
issue
to
work
on
and
it
explains
all
of
the
steps
here
and
then
you
can
go
all
the
way
through
to
this
guide.
A
So
this
is
really
meant
to
help
walk
you
through
the
the
process,
and
one
thing
that
I
want
to
point
out
as
well
is
we
already
visited
the
documentation
page,
but
here
it's
you
know
it's
different,
so
there's
there's
a
different
set
of
instructions
depending
on
what
track
that
you're
interested
in
contributing
to.
So
I
just
want
to
make
sure
everyone
is,
is
pointed
back
back
to
that
list
and
then
you
can
also
work
on
translation.
If
you
know
another
language,
that
process
is
different
as
well.
A
We
are
translating
gitlab
into
35
different
languages
and
we
have
more
than
1500
contributors
who
are
working
on
that.
So
this
is
a
really
great
way
as
well
to
work
on
contributing,
but
not
necessarily
to
the
main
code
and
then
there's
ux
design.
So
there's
a
bunch
of
issues
that
are
improving
the
user
experience
and
again
this
is
a
different
set
of
instructions.
So
I
think
this
points
back
to
why
contribute
to
open
source.
A
Is
that
there's
a
lot
of
different
places
for
you,
depending
on
what
your
skill
set
and
your
interests
are
and
the
level
at
which
you
want
to
contribute.
So
we
hope
that
this
guide
really
helps
you
find
that
place,
that's
appropriate
for
you
to
contribute-
and
again
I
just
put
this
in
here,
because
you'll
have
the
deck
and
it
kind
of
summarizes
all
of
these
different
ways
to
contribute.
A
A
So
I
also
put
this
screenshot
in
there
as
well,
since
I
know
that
you'll
have
the
slide
deck
remember
to
look
for
accepting
merge,
requests
and
good
for
new
contributors,
look
for
not
assigned,
and
then
also
the
category
or
the
track.
So
documentation
is
a
really
good
good
example,
and
then
remember
if
there's
something
that
you
see
that
you
want
to
fix,
you
can
always
submit
an
mr
without
having
a
specific
issue.
We
just
recommend
using
the
existing
issues
as
a
great
place
to
get
started
next.
A
Most
important
thing
is
where
to
get
help,
so
we
have
a
a
contributors,
get
our
channel
and
we'll
go
ahead
and
open
that
up
to
show
you
what
that
looks
like,
and
you
can
sign
in
to
get
her
to
start
talking
and
you
can
see.
We
have
839
people
on
our
dinner
contributor
on
channel
and
a
lot
of
these
are
viet
lab
heroes
or
community
members
or
new
contributors.
A
A
Coaches
are
volunteers
that
work
at
get
lab,
who
are
designated
as
merge,
request,
coaches
and
they
watch
the
community
contribution,
merge,
requests
and
they
are
there
to
help
you
can
find
them
by
going
to
the
get
lab
team
page
and
searching
for
merge,
request
coach
when
you're
working
on
an
issue
or
in
an
mr
you
can
at
mention
at
getlab.org
coaches
and
that
will
alert
any
of
the
coaches
that
are
in
the
mr
coaches
group
to
come
and
take
a
look
at
what
you're
working
on.
So
that's
another
great
way
to
get
assistance.
A
We
also
have
an
mr
coach
tutorial
and
then
reviewers
and
maintainers
of
those
specific
lab
projects
are
listed
here.
So
that's
another
great
place
to
go
and
find
people
who
are
able
to
help
and
then,
as
always,
you
can
email
us
at
contributors.
Gitlab.Com,
although
I
will
say
if
you
are
used
to
working
in
gitlab,
we
would
that's.
Definitely
the
best
way
to
reach
us
is
on
the
issues
in
the
merge
requests
themselves
or
in
our
contributors.
Getter
channel.
A
So
again,
just
a
couple
tips
since
you'll
have
access
to
this
deck.
Make
sure
that
you
sign
up
for
an
account?
You
can
do
that
with
an
existing.
If
you
want
to
link
an
existing
account
and
then,
if
you
are
working
on
a
project
that
requires
you
to
run
ci
cd
and
you're
on
our
free
tier,
you
may
be
asked
to
enter
a
credit
card
to
verify
your
identity
and
we
don't
charge
our
credit
card.
A
A
A
There's
no
registration
required
and
you
can
work
on
these
issues
during
the
hackathon
and
we
have
office
hours
and
we
have
sometimes
we'll
have
meetups
and
everyone
is
on
high
alert
to
watch
out
for
people
contributing
and
help
you
out,
and
so
we
have
prizes
awarded
to
everyone
for
having
a
merge
request
that
was
successfully
merged
and
there
are
other
awards
for
each
hackathon.
Some
great
get
lab
swag.
A
So
we
encourage
you
to
take
a
look
at
that
as
well,
and
it's
just
really,
depending
on
the
specific
project
that
you're
interested
in
contributing
to,
and
then
we
want
to
make
sure
that
everyone
feels
free
to
reach
out
to
us
christina
here.
There's
my
my
twitter
and
my
linkedin
profile,
and
then
we
also
have
pj
max,
who
is
an
education
evangelist
on
our
team
and
pj
would
love
to
connect
with
you
on
twitter
linkedin
and
he
also
hosts
a
twist
quick
show
where
he
interviews
different
people
around
gitlab.
A
A
We
offer
free
ultimate
licenses
on
the
benefit
of
that
there's,
a
lot
of
different
features
in
ultimate,
and
also
you
don't
have
to
worry
about
that
credit
card
validation
step.
If
you
join
the
education
program,
we
have
a
team
intro
video
here.
That
tells
you
a
little
bit
more
about
what
we
do:
lots
of
different
ways
to
get
involved.
We
have
a
gitlab
forum
where
a
lot
of
people
ask
questions
about
the
products
meet
each
other
network.
We
have
an
education
category
there,
so
we
encourage
you
to
join
that
again.
A
We
can
come
visit,
your
classroom.
You
can
host
a
meetup
at
your
university
for
people
who
are
get
lab
enthusiasts
and
will
help
facilitate
that
and
also
we
can
help
you
find
a
speaker
on
whatever
topic.
It
is
that
you
would
like.
So
we
encourage
you
to
check
that
out
as
well
and
then
we've
had
us
many
universities
who
have
become
very
successful
using
gitlab
and
we've
documented
a
lot
of
what
they're
doing
with
with
some
of
our
education
case
studies.
A
So
we
encourage
you
to
take
a
look
at
those
and
read
a
little
bit
more
about
how
other
universities
are
being
being
successful
with
gitlab
here's
some
of
our
chinooki
shows
and
then
just
some
other
links
and
resources.
So
we
thank
you
for
your
time
and
we
really
look
forward
to
to
welcoming
you
to
the
community
and
also
to
see
your
your
contributions
and
hopefully
to
see
you
in
the
platform.
So
please
feel
free
to
reach
out
and
we'll
see
you
soon.
Thanks
for
your
time
and
good
luck
with
your
assignment.