►
From YouTube: 2023-04-23 GitLab Hackathon Kick-Off FY24Q1
Description
Hackathon kick-off.
For more information see https://about.gitlab.com/community/hackathon/
A
A
A
So
well
just
quickly
open
those
details
up.
So
the
merge
requests
need
to
be
raised
between
the
23rd
of
April
and
the
30th
of
April
and
they
need
to
be
merged
by
the
30th
of
May.
So
we've
got
about
a
month
to
get
those
merch
requests
merged.
Just
allows
us
time
to
put
them
through
review
and
apply
any
comments
from
the
reviewers.
A
So
we've
got
a
new
leaderboard.
We
can
see
that
there's
already
four
four
people
with
merge
requests
raised
and
each
of
these,
if
you
hover
over
it,
says
that
none
of
them
have
been
merged.
Unsurprisingly,
yet,
but
once
the
the
cutoff
date
is
passed,
May
the
30th.
These
scores
will
change
to
show
the
relevant
points
based
on
the
merge
requests
which
were
merged
as
a
reminder,
all
repositories
in
the
gitlab,
org
and
gitlab
com,
namespace,
are
included
and
all
contribution
areas
front
and
back
end
Docs
design,
everything's
included.
A
So
it's
only
the
gitlab.com
and
gitlab
org
namespace,
so
I
will
have
to
make
a
change
to
either
move
the
the
leaderboard
project
or
to
include
the
gitlab
community
namespace.
My
inclination
is
maybe
to
include
the
gitlab
community
namespace
going
forward.
So
anyone
that
maybe
fancy
is
improving
our
meta
project
or
when
we
get
our
terraform
scripts
built
to
to
manage
the
community
Forks
using
terraform.
A
All
of
those
things
could
be
included
as
well,
so
I
I
think
if
we
do
have
any
Mrs,
I'm
happy
to
add
those
and
in
fact
a
good
murder
request.
Two
good
merge
requests.
If
not
three
could
be
one
to
modify
the
leaderboard
to
include
merge
requests
in
the
gitlab
community
group
and
one
could
be
to
update
this
hackathon
documentation.
The
hackathon
website
to
include
so
somewhere
we
should
have
or
I
thought
we
would
something
that
says
which
projects
are
included
and
which
projects
qualify.
So
all
in
gitlab,
org
and
gitlab.com.
B
And
another
way
of
thinking
maybe
include
a
leaderboard
and
kind
of
gamification
into
gitlab
product
having
product
on
the
page,
and
we
already
have
kind
of
idea
to
likes
or
reactions
to
the
comments
to
issues
or
comments
to
measure
requests
to
be
counted
somehow,
and
the
people
who
obtain
a
lot
of
reaction
are
leaders
and
can
celebrate
their
achievements.
Absolutely.
A
No
I
100
agree
with
that.
This
I
put
this
together
quite
quickly,
and
you
know
that
because
it
was
you're,
an
Alexi
who
kind
of
gave
me
the
idea
and
suggested
we
put
something
together
so
in
interest
of
speed
and
getting
it
in
in
time.
I
threw
it
together
as
a
separate
project,
but
I
I
definitely
agree
that
we
should
build
it
into
the
product.
A
You
might
even
know
better
than
me
I'm
sure,
somewhere,
you
can
get
a
list
of
contributors,
but,
alas,
I
I
think
that
this
was
getting
up
quick.
What
we
need
to
find
out
is
who,
who
would
own
this?
Who
would
be
the
dri
and
would
need
to
get
the
designers
involved,
show
them
what
we've
got
so
far
and
and
go
from
there?
I
did
deliberately
build
this
in
such
a
way
that
it's
parametized.
A
So
that
we
can
repurpose
it,
the
only
thing
that
isn't
included
at
the
moment
is
the
group
parameter.
If
we
were
to
add
that,
then
you
know
you
or
or
any
other
individual
or
organization
could
actually
use
it
for
your
own
internal
purposes.
So
it
has
been
built
in
such
a
way
that
it's
not
too
hard-coded
to
to
to
the
gitlab
hackathon
itself,
but
we
wanted
to
get
it
in
quickly.
So
again,
what
would
be
amazing?
A
It
will
happen
if,
if
even
if
it,
if
you
don't
move
it
forwards,
but
if
someone
would
like
to
start
by
creating
one
or
more
issues
in
the
gitlab
project
itself
linking
and
referencing
this
leaderboard
that
we've
built,
but
to
kind
of
start
the
conversation
around
how
we
can
get
this
into
the
the
product
and
what
it
might
look
like,
I
guess,
there'll
be
a
few
differences.
Maybe
the
The
Styling
the
look
and
feel
maybe
isn't
entirely
in
keeping
with
the
gitlab
UI
look
and
feel
but
yeah.
That
would
be
great.