►
From YouTube: GitLab Q1 2021 Hackathon Kickoff
Description
Q1 2021 GitLab Hackathon Kick-off call!
A
Good
morning
afternoon
evening
to
everyone,
I
hope,
we're
alive.
Let
me
check
yes,
we
are
welcome,
welcome
everyone
to
another
gitlab
hackathon.
I'm
really
excited
about
this
one
specifically
and
let's
get
things
started.
First
of
all,
hi.
My
name
is
christopher
harakis,
I'm
the
senior
contributor
program,
manager
and
I'll
be
your
host
for
this
two
days.
A
Let
me
quickly
brief
start
my
screen,
so
here
at
gitlab.
Our
motto
is:
everyone
can
contribute,
that's
why
we're
also
making
this
hackathon
and
trying
to
make
it
a
as
a
as
an
opportunity
for
everyone
to
contribute,
and
it
is
easier
as
it
can
get
again,
I'm
christos.
I
live
in
berlin,
originally
greek!
A
So
hello,
if
you
speak
any
greek
out
there,
this
is
the
day's
agenda.
I
would
like
to
spend
a
fair
amount
of
time
in
the
community
code
of
conduct.
It's
really
important.
We
want
here
to
gitlab
everyone
to
feel
safe,
included
and
be
able
to
communicate
and
in
in
a
safe
environment
here
at
gitlab.
A
So
it's
really
important
for
us
to
enforce
the
code
of
contact
in
case
that
you
see
any
disrespectful
behaviors,
any
disturbing
behaviors
any
offensive
behaviors
and
in
a
emergency
quest
or
an
issue
or
in
in
our
communication
channels.
Please
send
us
an
email
and
we
will
respond
as
soon
as
possible,
we're
generally
monitoring
all
of
our
channels,
so
yeah
we're
trying
to
be
there
all
the
time
for
for
everyone.
A
So
again,
at
the
glance
two
days,
it's
it's
an
online,
it's
an
online
event.
Hackathon
for
all
of
contributors.
We
have
some
really
exciting
prices
which
we're
gonna
dive
more
in
a
later
slides,
it's
gonna,
it
started
already,
and
it
starts
on
the
31st
of
march
of
at
your
local
time
zone
and
finishes
on
thursday
at
april
1st,
on
your
local
time
zone.
It's
really
important
to
keep
that
in
mind.
A
But
we
made
it
in
utc,
so
it's
like
nine
degrees
c
for
just
to
have
a
to
have
a
reference
all
right.
We
have
spent
before
jabbing
into
the
suggestions
you
used
to
work
on,
because
I
want
to
spend
a
lot
of
time
there
here
is
the
this
time.
Here
is
the
rundown
of
our
sessions
this
time
we're
gonna,
keep
it
as
simple
as
possible.
We
want
to
run
mainly
office
hours,
calls
to
be
able
to
support
you
all
so
we're
going
to
have
enough
two
office
hours
a
day.
A
One
is
the
owner
of
this
hour.
The
only
other
one
is
going
to
be
the
package
group
office
hour.
So
if
you
want
to
contribute
to
runner
or
the
package
group,
please
feel
free
to
join
these
sessions.
Our
maintainers
they're
going
to
spend
some
time
going
through
some
of
mrs
how
they
review
them
and
also
going
to
be
there
to
help
and
address
any
questions
you
might
have
at
any.
Given
time
you
can
reach
out
to
us
on
our
githur
instance,.
A
It's
getter.im
slash,
gitlab
contributors.
If
you
need
anything
you
can
ping
me
directly,
but
also,
if
you
need
help,
you
can
join
there.
All
of
our
community
and
gitlab
team
members
are
there
to
help
you
and
support
you
for
any
merge
requests.
Generally
we're
keeping
an
eye
on
merger
press.
Today.
Every
marriage
request
that
you
open
as
a
community.
It's
gonna
automatically
be
tagged
as
hackathon,
but
feel
free
to
ping
me
as
well.
In
order
to
make
sure
that
your
mr
is
gonna,
be
counted
towards
the
prices.
A
Everyone
with
everyone
with
merge,
merge
request
is
gonna,
receive
a
price
and
the
users,
the
contributors
with
a
high
amount
of
marks,
are
gonna
receive
a
grand
prize.
Last
hackathon
we
had
two
actually
people
claiming
the
grand
prize
and
we're
gonna
have
also
second
place
winners
with
some
prizes.
A
Our
prizes
are
here.
The
first
one
is
a
hackathon
special
swag
box.
It's
a
mystery,
but
that's
all
exciting.
The
third,
the
the
second
place
price
is
a
duffel
bag,
gitlab
socks,
a
charging,
multi-board,
cable
and
a
collapsible
straw,
and
for
every
merge
request
that
everyone
is
merged.
We
have
a
gitlab
socks
and
a
charging
multiport
cable.
A
So
let
me
quickly
go
through
some
of
the
ways
to
contribute
to
gitlab.
So
if
it's
your
first
time
contributing
to
gitlab,
please
check
the
contributing
to
guide
gitlab.
Here
there
are
some
areas
for
the
hackathon.
Specifically
only
development
and
documentations
are
counted
as
as
contributions
towards
the
hackathon.
So
in
the
development
specific
specific
category
there
are,
there
is
a
list
of
the
top
10
gizla
projects
to
contribute
their
top
10
top
10
based
on
the
people
contributing
to
them.
A
So
we
went
ahead
and
analyzed
all
of
our
projects
and
saw
that
these
10
projects
are
receiving
the
most
community
contributions.
So
for
each
project
you
can
see
the
language
technology
is
needed,
so
you
can
figure
out
a
project
to
contribute
to
based
on
your
skills.
So
if
you
have
some
html
skills,
there
is
gitlab
omnibus.
A
The
project
has
different
development
guide
than
the
general
gitlab
one,
so
detailed
distractions
for
how
to
set
up
your
development
environment
exist
there,
and
on
the
last
column,
you
can
find
a
link
to
issues
that
are,
you
know,
let's
say,
tailored
to
the
community
I'll
say,
for
example,
if
I
click
on
the
ui
police
and
accepting
marriage
request,
it's
going
to
take
me
to
gitlab
and
I'm
going
to
apply
the
filters
needed
for
issues
that
are
accepting.
Merge
requests
have
been
fleshed
out
for
the
community,
so
we
have
314
issues.
A
You
can
also
filter
them.
Based
on
weight.
Weight
is
how
important
they
are
right
now
for
git
lab,
but
yeah.
You
should
select
the
issue
to
work
on
based
on
what
based
on
based
on
your
skills
and
your
experience.
If
you
want
to
work
on
something,
it's
also
gonna
be
great
to
leave
a
comment
and
say:
hey,
you
know
I
would
like
to
work
on
that:
hey,
hey!
A
I
am
working
working
on
that
as
part
of
the
gitlab
hackathon,
so
you
let
everyone
know
that
you're
working
on
that
and
no
one
else
is
going
to
go
there
and
start
working
at
the
same
time.
So
you
both
deliver
a
merge
request
and
that's
it
and
then
you
just
work
on
that
and
when
you
submit
the
merge
request,
make
sure
that
you
also
link
the
issue
here.
A
Moving
on
for
setting
up
the
developer
environment,
there
is
a
new
tool
that
is
called
git
pod.
If
you
click
here,
you
can
find
the
guide.
It's.
It's
really
really
really
simple
and
straightforward.
It's
as
simple
as
clicking
one
button.
For
example,
if
I
go,
these
are
the
instructions
just
like
you
see
the
button
here.
A
If
you
go
to
when
you
enable
git
bot
and
when
you
go
to
the
gitlab
repository,
there's
going
to
be
a
button
here,
gitbot
and
it
automatically
builds
a
development
environment
on
the
cloud
on
your
browser
or
your
browser
tab,
and
you
don't
have
to
download
anything.
You
don't
have
to
set
up
anything.
It
just
works
out
of
the
box,
so
check
it
out,
it's
making
it
easier
for
everyone
to
contribute.
A
Now,
if
you
want
to
work
on
the
website
on
the
on
the
gitlab
website,
let's
go
to
the
hackathon
page,
for
example,.
A
So,
and
I
want
to
check
something,
for
example,
I
want
to
fix
that
the
event
is
in
progress
has
been
completed
that
has
been
completed.
Here
is
something
that
you
know
it's
it's
confusing
right.
So,
by
the
way
we
have
65,
mrs
already
submitted.
That's
great.
If
you
go
down
down
down
down
here
again,
you're
gonna
see
view
page
source
and
edit
with
web
id.
A
If
I
click
here,
it's
gonna
take
me
to
the
web
id
where
I
can
edit
the
website
and
change
stuff
around
and
submit
the
merge
request
without
downloading
anything
again
pretty
cool.
Okay.
As
far
as
I
remember
this
counter
this.
Oh
sorry,
this
message
is
somewhere
else
here
the
event
has
been
completed.
It's
you
know.
It
says
javascript
file,
it's
not
here.
A
So
I
guess
we
will
need
to
find
yeah
here
the
next
hackathon
countdown.
This
one
is
somewhere.
Let's
see.
A
A
And
I
can
click
commit
here
and
I
can
put
a
message:
update
wording
of
course,
creating
new
brands
all
right,
because
I
cannot
commit
straight
to
master
and
then
you
can
see
the
changes
here.
You
can
preview,
the
changes
what's
changed
and
I
click
commit
and
automatically
it's
gonna
forward
me
to
opening
a
merge
request
with
this
branch
and
that's
it.
It's
really
easy
to
contribute
to
to
the
website.
A
A
A
Again,
if
you
need
any
help,
you're
gonna
find
us
at
guiter
on
our
guitar
channel.
If
you
need
any
help
with
coaching
and
you
can
find
you
can
tag,
you
can
mention
the
gitlab
coaches
on
your
merge
request.
A
But
generally
I'm
gonna
spend
all
of
my
day
today
and
tomorrow,
going
through
all
of
your
mars
and
make
sure
that
the
right
people
were
assigned
so
they're
gonna
be
reviewed
as
soon
as
possible,
again
any
emerging
quests
that
happen
from
the
31st
of
march,
at
your
local
time
zone
until
the
first
end
of
day,
first
of
march,
at
your
local
time
zone
and
are
merged
until
end
of
april
they're
going
to
be
counted
towards
the
prices
all
right.
A
I
know
that
the
the
time
zone
thing
might
be
confusing,
but
because
everyone
we
have
contributors
from
around
the
world,
we
need
to
make
it
tailored
to
everyone's
time
zone
and
not
have
one
specific
time
during
the
day,
because
if
we
say,
for
example,
that
the
hackathon
takes
place
from
midnight,
utc
of
you
know
of
wednesday
until
midnight
btc
friday,
then
you
know
it's
might
be
better
for
people
in
in
the
east,
because
they
have
more
free
time
and
wherever
the
people
from
the
west,
they
don't
in
any
case,
don't
worry
about
it
again.