►
From YouTube: 2023-07-09 GitLab FY24Q2 Hackathon Kick-Off
Description
A
Welcome
everyone
to
the
gitlab,
hackathon
I'm,
just
gonna,
do
a
quick
answer
of
any
questions.
Everything
you
need
is
hopefully
on
the
lab.
Hackathon
website
and
I
just
want
to
show
off
the
hackathon
leaderboard,
that's
linked
from
the
hackathon
website,
and
we
introduced
this
I
think
for
the
first
time
for
the
the
q1
hackathon,
and
it
just
gives
you
a
real-time
viewer
on
everyone.
That's
taking
part
in
the
ACT,
fun
I!
A
Think
since
then,
we've
added
a
tiny
little
feature
as
well,
so
you
can
actually
zoom
and
sort
of
drill
down
on
these
to
see
the
individual
merge
requests
as
well.
If
you've
got
any
feedback
or
ideas
again,
this
project
is
on
gitlab
source
code
link.
There
feel
free
to
create
an
issue
ping
me
or
submit
a
merge
request.
A
So
that's
something
that
will
be
really
good
is
if
I
could
flesh
out
a
bit
more
in
future
in
or
on
the
hackathon
site,
but
to
try
and
summarize
the
story,
we
started
the
hackathons
for
quite
a
lot
shorter,
like
two
or
three
days
and
I
think
they
were
always
mid-week.
The
problem
we
found
was
some
people
can't
contribute
during
the
the
week.
A
You
know
due
to
their
day
jobs
or
whatever
it
might
be,
so
we
then
considered
moving
it
to
a
weekend,
but
then
we
had
the
the
opposite
scenario:
some
people,
you
know
at
home,
families,
kids.
They
could
only
contribute
during
the
week.
So
we
felt
the
simplest
solution
was
to
do
a
seven
day
a
full
week
and
that
should
hopefully
cater
for
for
everyone
and
anyone.
So
those
that
can
only
contribute
at
the
weekend
and
those
that
can
only
contribute
during
the
week
and
those
that
can
do
both.
A
So
let
me
just
expand
as
well.
You
said
about
the
fact
that
the
team
members
are
only
generally
available
Monday
to
Friday
as
well.
So
that's
a
good
point
might
be
a
bit
slower
to
get
responses
on
the
weekend,
but
a
couple
of
things
to
consider.
First
of
all,
what
time
is
it
now
so
like
in
Australia?
It's
probably
maybe
I'm
exaggerating
a
little
bit
but
sort
of
like
10
o'clock
in
the
evening?
A
It's
getting
quite
late
so
later
on
today,
Australia
and
you
know
that
side
of
the
world
will
be
online
to
support.
Also,
we've
got
until
the
16th
of
August
to
get
these
merge
requests
merged.
So
the
idea
is
to
get
it
submitted
this
week,
but
we
know
full
well
that
a
lot
of
merge
requests
have
to
go
through
a
few
cycles
of
review
and
feedback
and
iteration.
So
you've
got
a
month
from
the
hackathon
sort
of
closing
date,
if
that
makes
sense
to
actually
get
them
merged.
B
A
Correct
exactly
okay,
so
he's
down
to
the
diet
in
which
the
the
merge
request
was
actually
created
and,
as
I
say,
with
the
caveat,
it
does
need
to
be
merged
within
the
month
so
by
by
16th
of
August
and
those
dates.
So
we've
got
the
the
kind
of
hack,
Von
dates
here
and
somewhere
here
it
says
they
need
to
be
submitted
between
these
dates
and
merged
by
this
date.
Gotcha.
A
I'll
hold
my
hands
up
here,
and-
and
this
is
what
my
wife
is
on
the
hackathon
leaderboard
already,
because
I
I
I
I
missed
this
one.
Actually,
so,
if
I
show
you
the
so,
this
tracking
issue
references
all
of
the
merge
requests
that
are
submitted
for
the
AG
from
and
the
way
that
that
happens,
or
it's
supposed
to
happen,
don't
think
we've
had
any
new
ones
yet
or
have
we.
Let
me
just
check
one
of
these.
B
A
Yes,
here
you
go
so
this
our
trusty
bot
when
somebody
raises
a
new
merge
request
during
the
hackathon
window
this
week
or
our
bot
will
add
a
note
to
mention
that
it's
part
of
the
hackathon
with
a
link
to
this
issue,
which
is
the
the
tracking
issue.
Essentially,
it
just
has
a
list
of
all
the
merge
requests
that
were
submitted
during
the
hackathon,
and
it
also
applies
this
hackathon
label
here.
A
So
everyone
should
take
care
of
everything
for
us,
but
I
hadn't,
updated
so
again,
really
good
the
bot
links
to
the
project
and
the
individual
processor.
That
is
actually
responsible
for
doing
that.
So
you
can
see
here,
there's
a
start
and
end
date
for
the
hackathon
and
I
hadn't
updated
this
quickly
quickly.
Did
this
on
me
this
morning,
so
yeah
that
will
now
every
merge
request.
That's
raised
between
those
dates
by
community
members
should
get
tagged.
Labeled
automatically.
A
B
A
Live
run
in
total
of
how
many
merge
requests
the
way
that's
actually
populated
and
now
I've
said
it
is
that
yeah
that
links
to
it
as
well.
So
the
way
that
it's
populated
is
by
making
an
API
call
to
this
issue
and
getting
the
count
of
merge
requests
that
are
related
to
this
issue.
So
yeah,
the
the
easiest
way
is
probably
to
go
to
the
hackathon
website
and
click
on
this.
This
big
purple,
I
think
I
call
it
box.
A
So
believe
it
or
not,
this
is
the
Q2
hack
one.
So
the
gitlab-
let's
say
Financial
year-
starts
in
February.
So
if
I've
got
this
right,
so
February
March
April,
so
April
was
the
q1
hackathon
and
then
May
June
July.
So
July
is
the
Q2
hackathon,
maybe
in
the
future,
I
should
just
call
it
the
the
kind
of
July
2023
hackathon
rather
than
using
our
financial
periods.
That
might
make
it
a
little
bit
more
simple.
Let
me
make
a
note
of
that.