►
From YouTube: 2023-04-05 GitLab Hackathon AMA
Description
GitLab hackathon AMA hosted by Petro Koriakin
A
And
yeah
welcome
to
the
gitlab
hackathon
ask
me
anything
session.
We
have
a
brief
agenda
and
a
few
guests
who
are
either
want
to
participate
the
hackathon
or
want
to
explain
things
for
those
who
are
going
to
participate.
I
had
to
an
item
in
agenda
for
my
site
to
tell
a
bit
about
open
source
philosophy
and
I'm,
not
a
philosopher
I
want
just
to
mention
heshikor,
who
are
built
in
entire
infrastructure.
A
A
Please
check,
notes
so
and
explore
this
universe
if
you
want
and
a
gitlab
or
open
Core
Company,
who
are
doing
great
things
for
devsec
Ops,
so
entire
life
cycle
and
our
open
source
with
and
our
free
features
available
for
just
entirely
everyone,
and
so
these
pretty
great
business
model
where
everything
is
going
on
pretty
well
for
for
a
decade,
I'd
say:
that's
it
from
my
site.
Any
questions,
Maybe.
A
Then
I'm
giving
birth
to
you
Lee
just
to
talk
to
explain
and
to
introduce
a
hackathon.
B
I
will
I
will
do
my
best
I
added
a
link
to
the
document.
B
It's
the
first
time
that
I've
run
the
hackathon,
so
I'm,
certainly
new,
so
go
easy
on
me,
but
I've
participated
and,
and
that
was
very
much
how
I
got
into
kind
of
get
loud,
gitlab
as
a
product
and
eventually
the
company
itself
through
the
hackathon
I,
think
I
started
probably
about
three
or
four
years
ago,
intrigued
by
what
the
hackathon
was
and
yeah.
That's
that's
kind
of
got
me
learning
more
and
more
about
the
product.
B
I
joined
the
gitlab
core
team,
maybe
three
years
ago,
and
then
the
contributed
sex
success
team
just
over
six
months
ago
now.
So
our
team's
goal
is
to
to
make
contributors
lives
as
easy
as
possible
and
to
help
try
and
reach
the
the
goal
of
1
000,
unique
monthly
immunity
contributors.
B
So
we've
got
lots
of
exciting
stuff
that
we've
been
working
on
to
try
and
make
that
easier.
The
the
hack
fund
itself
it
does
evolve.
We've
tried
to
keep
this
one
nice
and
simple,
because
it's
my
first
one
I
don't
want
any
crazy.
B
You
know
bonus
points
for
front
end
or
back
end
or
want
to
exclude
anything
like
specifically
docs
or
this
or
that
we
just
want
to
keep
it
as
simple
as
possible,
and
it's
a
week-long
starting
on
Sunday,
the
23rd
of
April
and
finishing
on
I
guess
it
will
be
Sunday
the
30th
or
Saturday,
essentially
the
the
end
of
the
day.
So
it
allows
some
people
to
contribute
that
want
to
contribute
during
the
week.
B
Maybe
they
can
contribute
as
part
of
their
job
or
some
people
who
maybe
can't
or
don't
want
to
contribute
as
part
of
their
job
that
actually
wants
to
do
at
the
weekend
as
kind
of
yeah
some
some
personal
activity.
So
to
speak.
We
have
a
lot
of
documentation
around
contributing,
but
it
it
is.
It
can
be
dumped
in
so
we're
there
on
Discord
to
help
out.
B
There's
community
members
plenty
of
community
members
there
to
help
out
as
well
and
some
links
from
the
link
that
I
shared
to
some
good
issues,
maybe
to
kind
of
consider
getting
started
so,
depending
on
whether
you're
interested
in
front
end
or
back
end
front
end
mainly
being
JavaScript
VJs
back
end.
B
Maybe
mainly
being
Ruby
on
Rails,
and
then
we've
got
some
or
quite
a
few
satellite
projects
that
that
are
golang
based
so
depending
on
your
your
kind
of
skill
set
and
what
you
want
to
pick
up
so
yeah
I
hope
that
that's
a
reasonable
introduction.
A
Hey
thank
you.
So
then,
let's
move
forward
to
q
a
session
and
I'll
verbalize
questions
for
those
who
are
not
on
the
call,
and
then
we
can
add
anything
else.
A
A
Okay,
my
question:
what
is
gitlab
core
team
and
why
excellent.
B
Question,
as
is
always
the
case,
we
try
gitlab
to
make
sure
everything
is
documented.
So
there's
there's
a
link
there.
That
will
give
you
a
reasonable
explanation.
B
Essentially,
it's
I
don't
want
to
call
them
contributors
necessarily,
although
they
primarily
are,
but
the
kind
of
ambassadors
that
have
have
been
elaborating
with
gitlab
in
the
community
for
for
a
reasonable
period
of
time
and
kind
of
shown
that
they,
they
kind
of
live
the
gitlab
values
so
that
they're
invited
to
join
the
core
team
I'm
not
overly
familiar
with
the
concept
but
believe
it
is
an
industry
concept.
I
think
view.
Js
have
a
core
team.
B
I
imagine
Ruby
on
Rails
have
a
core
team,
so
it
might
be
that
you
can
tell
me
more
about
what
the
the
kind
of
traditional
poor
team
roles
and
responsibilities
are,
but
essentially
it's
to
to
kind
of
help.
Gitlab
be
accountable
for
their
kind
of
values
and
uphold
their
values,
but
but
they're
kind
of
that
that
nice
intermediary
between
the
community
and
GitHub
team
members.
So
you
know
it
can
be
quite
hard
working
for
a
company
to
to
kind
of
see
everything
from
the
perspective
of
an
outsider
of
a
Community
member.
B
B
So
it
kind
of
means
that
they
can
also
help
out
with
things
like
labeling
issues,
assigning
issues.
Labeling
merge,
requests
to
sign
in
reviewers
those
kind
of
things.
A
Yay,
thank
you
for
this
pretty
or
detailed
explanations
and
for
the
note
in
the
notes.
The
next
question
from
admin
is
about
gitlab
hackathon
benefits,
and
especially
if
this
work
from
community
store
or
listed
on
the
page
is.
B
So
I
I
checked,
then
the
the
company
that
provide
the
swag
don't
ship
to
the
Ukraine,
but
it
looks
like
you're
having
an
awesome
solution
for
that.
A
Mm-Hmm,
yes,
yes,
I
am
editing
is
this
is
to
do
to
my
to-do
list
in
my
to-do
list,
application
in
my
markdown
based
to-do
list,
applications,
library
and
the
I'll
share
the
details
in
the
notes
and
through
other
channels.
The
workarounds
are
always
possible
great.
C
B
Absolutely
and
we,
we
would
definitely
encourage
you
today,
so
you
know.
Ultimately,
we
would
encourage
anyone
and
everyone
to
talk
about
get
Labs
and
yeah.
I.
Think
that
it's
if
everyone
has
a
different
kind
of
view
and
reason
for
contributing,
but
when
I've
been
responsible
in
the
past
for
interviewing
candidates
for
jobs,
especially
graduates
that
maybe
haven't
got
what
it
takes
for
the
role
I
was
interviewing.
I've
always
recommended
that
they
they
consider
contributing
to
GitHub
as
a
way
to
actually
get
some
essentially
commercial.
B
Some
real
life
experience
and
I
I
kind
of
say
that
I'm
almost
100
sure
that
someone
that
contributes
to
gitlab
as
kind
of
a
student
or
whatever
you
want
to
call
it
will
will
then
be
able
to
land
a
job
based
on
what
they
learn
there.
B
So
I
I
actively
encourage
it
in
that
scenario,
but
for
anyone
else
like
ultimately,
it's
a
kind
of
volunteer
open
source
work
is,
is
something
that's
that's
really
great
to
do
so.
Yeah
I
recommend
it.
A
B
So
Discord
is
is
definitely
the
right
place.
I've
shared
a
link
there
we
used
to
use
getter,
but
it
never
hugely
took
off
the
the
Discord
server
was
started
by
a
Community
member.
B
You
know
nine
months
a
year
or
so
ago,
and
it's
very
naturally
organically
grown.
So
it
shows
that
there
must
be
whether
it's
an
industry
standard
or
it's
just
a
good
platform
that
people
enjoy
using.
B
B
There
was
a
separate
hackathon
Channel,
but
I
recently
kind
of
archived
that
I
could
possibly
bring
it
back
if
we
want
to,
but
the
way
I
see
it
is
that
contributors
will
be
in
the
contribute
channel.
So
a
hack
phone
contribution
is
really
no
different
to
a
normal
everyday
contribution
and
also
we've
got
the
right
people
there,
both
team
members
and
community
members
to
be
able
to
help
out.
B
I
I
will
ask
I'll
ask
the
question:
it's
definitely
something
we'll
consider,
especially
if,
if
you
and
others
are
kind
of
say
that
it
would
be
beneficial,
I
would
encourage
everyone
to
use
the
main
contribute
Channel.
It
should
be
welcoming.
B
You
know
our
code
of
conduct,
our
ethos
that
we
shouldn't
and
won't
you
know,
belittle
anyone
or
kind
of
you
know.
We
expect
people
have
all
kind
of
experienced
someone.
That's
never
used
yet
before
you
know
spinning
up
GDK
for
the
first
time
to
to
those
who
are
kind
of
experts
and
really
putting
us
on
our
toes
and
and
kind
of
yeah,
with
with
crazy,
complex
Ruby
and
view
JS
queries
that
I
have
no
idea
how
to
solve.
B
So
if
we
can
use
exist
in
Channel
great,
but
if,
if
there's
definitely
kind
of
demand
for
a
slightly
safer
space
for
for
newcomers,
then
we'll
take
it
on
board
and
I'm
sure
we
can
create
a
new
channel,
hey.
A
Since
we
have
pretty
small
round
and
today
a
question
to
Alexi
and
you
Margarita,
do
you
use
Discord,
do
you
enjoy
it.
D
Right,
I
I
used
it
a
few
times
and
not
for
software
development.
It
was
like
some
other
activities
and
so
like
I,
haven't.
D
A
Yeah,
as
for
my
experience,
I
didn't
use
it.
I
am
not
a
gamer
person
where
this
sport,
how
somehow
initiated
and
when
I
joined
some
projects
on
patreon
or
pay
for
obsidian
paid
subscription
communities,
are
offering
me
to
join
their
servers
and
I
used
to
have
this
things,
and
gitlab
naturally
fits
into
they
that
ecosystem.
For.
For
me,.
A
And
then
question
from
my
side
and
I'll
probably
answer
it
as
I
am
the
host
today,
just
to
mention
the
question
is
I
have
a
full-time
contract
and
it
stays
some
cumbersome
legal
things
regarding
intellectual
property,
would
my
employer
be
able
to
grab
my
contributions
from
the
gitlab
code
base?
Somehow,
and
my
answer
is
this
is
not
the
case.
Gitlab
has
a
10
years
of
history
and
it
was
not
problem.
A
As
per
my
current
experience
at
all
and
personally
I
had
this
kind
of
contracts,
pretty
many
times,
usually
companies
to
not
to
do
this,
and
if
you
are
really
worried,
please
ask
your
manager,
ask
your
team
lead
and
explain
the
situation
that
that
we
will
be
pretty
enough
and
yes,
people
are
contributing
to
open
source
and
even
as
part
of
their
work
from
time
to
time,
which
is
also
great,
no
and
so
for
the
hackathon.
A
B
So,
okay,
so
wanting
to
start
a
new
business
and
why
would
join
in
the
hackathon
be
beneficial
so
the
the
thing
that
I
love-
and
this
is
great-
because
I
actually
own
a
business
as
well
and
I've-
got
a
few
blogs
that
I'll
share
some
links
that
I
did
in
collaboration
with
gitlab
before
I
joined
the
company
and
it's
the
the
kind
of
the
model,
mainly
the
handbook
first
and
docs.
B
First
approaches
is
one
of
the
things
that
I
love,
but
there's
there's
lots
of
things
that
I've
picked
up
along
the
years,
so
the
the
company
that
I
own
software
company
and
they
used
to
have
20
different
systems.
You
know
a
new
get
repository
system,
a
maven,
Nexus
repository
system,
issue,
tracking
system,
a
sub
version.
You
know
hundreds
of
different
and
they
started
to
use
gitlab
for
one
thing
and
slowly
realized
it
was
capable
of
all
these
other
things
and
started.
B
You
know
decommissioning
one
system
after
another
and
migrating
everything
onto
gitlab,
and
it
was
also
it's
a
very
small
company,
so
the
documentation
was
poor
to
non-existent
and
after
kind
of
seeing
the
gitlab
approach
to
things
like
everything.
B
Maybe
I
made
a
contribution,
and
somebody
said:
oh,
we,
we
don't
tend
to
take
this
approach.
We
we
do
this
instead
and
they
would
link
to
the
documentation
where
it
states
their
kind
of
best
practice,
their
design
principles,
their
approach,
the
reasons
and-
and
this
is
something
that's
kind
of
really
kind
of
stuck
with
me
and
that
I've
I've
kind
of
adopted
a
lot
of
these
processes.
But
for
my
company,
it's
it's
just
a
great
way
of
working.
You
know
this
kind
of
transparent
and
open
and
docs
first
approach.
B
So
in
the
past,
I've
always
seen
the
opposite.
You
know
you,
you
build
something,
and
then
you
maybe
think
about
documenting
it
afterwards
or
maybe,
when
somebody
starts
asking
you
questions
a
year
after
you
built
it,
and
you
can't
remember
how
it
works
or
why
you
did
this
or
you
know
you
start
to
learn
the
hard
way
and
I
think
that
GitHub
have
done
all
this
kind
of
hard
work
and
they're
sharing
it
with
everyone
to
be
like
hey,
you
know,
if
you
want
to
use
our
our
kind
of
approach.
B
B
Again
the
same
exactly
the
same
thing:
website,
internet
knowledge
base
everything
used
to
the
company
that
I
own,
the
sdu,
SharePoint
and
they've
moved
out
to
Hugo
and
get
their
pages.
So
it's
now,
you
know
managed
in
gitlab,
Via,
merge,
requests,
yeah,
there's
so
many
things
as
as
a
kind
of
startup
that
you
could.
B
You
could
definitely
learn
from
GitHub,
so
yeah
I
think
that
joining
the
hackathon
and
making
some
connections
at
GitHub
and
sort
of
understanding
that
their
approach,
their
approach
to
code
review
again,
if
it's
a
it's
a
tech
company
and
there's
going
to
be
code
involved
or
some
of
the
infrastructures
code,
the
terraforming
type
projects
and
GitHub
charts,
and
that
kind
of
thing
all
of
it's
going
to
be
super
relevant
and
educational
I
should
say
I
guess
for
where
you
may
end
up
going
with
that
company.
A
Was
it
hard
to
educate
your
colleagues
about
the
kit
lab
documentation?
First
and
all
these
engineering
like
details.
B
I
I,
don't
think
it
was
too
challenging.
I
think
that
the
good
well,
the
bad
thing
that
was
also
a
good
thing,
was
that
the
issues
had
already
been
like
it
was
the
hard
way
of
learning.
You
know
how
did
that
thing
that
we
built
three
years
ago,
work
I,
don't
remember
Okay,
so
we've
got
to
kind
of
look
back
at
the
source
code
and
and
basically
reverse
engineer
it
to
figure
it
out.
B
So
I
I
think
we'd
already
seen
the
challenges
that
come
with
not
doing
it,
but
maybe
you
didn't
know
the
best
way
to
do
it.
So
if
we
had
done
documentation
in
the
past,
it
was
like
Word
documents
and,
as
you
know,
full
well,
you
know
Word
document
you
he
doesn't
really
fit
with
Version
Control
and
Source
control.
It's
it's
a
binary
file.
B
You
know
you
can't
you
can't
see
if
you
did
use
and
modify
the
word
file
in
a
commit,
you
wouldn't
be
able
to
see
a
diff
doing
a
code
review
or
or
a
sort
of
technical
writing
documentation.
Review
would
be
next
to
impossible,
so
yeah
I
I
think
that
they've
embraced
it
really.
Well.
B
There's
a
lot
of
interesting
conversation.
That's
come
up
because
I
think
technical,
writing
and
documentation
is
is
quite
well.
B
It's
it's
huge,
so
there's
there's
a
lot
to
to
kind
of
try
and
they're
nowhere
near
the
kind
of
level
that
gitlab
are
at
now,
where
they've
got
this
real,
strong
and
I
understand
about
using
active
voice
and
forget
what
you
call
it
now,
but
a
certain
tense,
like
I,
think
it's
present
tense,
that
they
use
and
the
kind
of
language
rules,
but
at
least
the
the
doc's
first
approach
is
there
so
any
kind
of
new
features
that
are
being
added
to
a
product?
B
The
the
kind
of
rules
are
in
place
to
ensure
that
okay
you're
making
a
code
change.
You
should
be
making
the
docs
change
at
the
same
time
as
part
of
the
same
Mr
and
yeah
I.
Think
everyone
understands
the
benefit
and
is
already
kind
of
been
able
to
to
see
those
benefits
so
yeah,
it's
great.
A
B
B
So
you
know,
there's
self-hosted
instance
that
you
could
you
know
if
if
something
suddenly
happened
and
changed
the
business
model
and
gitlab.com
I
I
suspect,
there's
certain
things
in
place
for
protection,
but
if
all
of
a
sudden,
oh
it
doesn't
exist
anymore,
then
you
know
you,
you
can
still
use
the
most
recent
release
in
a
self-hosted
instance
and
you're
all
good.
B
They
can't
really
pull
it
away
and
it
vanish,
and
you
know
never
to
be
seen
again.
The
the
source
code
is
out
there,
it's
replicated
everyone
has
it
or
everyone.
Has
it
a
lot
of
people?
Have
it
locally
as
well.
B
So
I
I
think
that
it
would
be
different
if
it
was
a
free,
closed
Source
product
that
putting
all
your
eggs
in
that
basket
might
be
more
of
a
concern
but
yeah,
and
on
top
of
that,
the
the
kind
of
ability,
if
it
doesn't
do
exactly
what
you
want
it
to
do
to
be
like
well,
I'll,
I'll,
start
an
issue.
I'll
start
a
conversation
and
I'll
I'm
willing
to
contribute
that
feature
and
make
it
do
this
extra
thing.
A
Wow,
thank
you
giving
birth
to
you,
margarita.
C
Okay,
thank
you
Ali,
maybe
I
need
something,
but
what
is
your
own
project
am
I
right
to
understand
that
you're,
like
a
project
coordinator
or
like
organizer
of
yeah,.
B
So
so
my
role
at
GitHub
is
as
a
full
stack
engineer,
but
as
part
of
the
contributor
success
team,
so
essentially
to
to
help
our
contributors
to
provide
the
tooling
to
make
the
journey
and
the
experience
as
good
as
possible
to
ensure
that
our
process
is
internally
are
as
good
as
they
can
be,
but
but
essentially
to
to
get
more
contributors
make
sure
they
want
to
keep
coming
back
and
yeah
as
part
of
that
role,
I
have
I'm
going
to
say,
inherited
or
taken
on
board
or
or
signed
up
to
to
run
these
hacker
funds
so
yeah
this.
B
This
is
the
first
one
I'm
running,
but
because
I've
been
past,
this
participating
myself
in
the
past
I'm
pretty
close
to
the
the
process
so
again
open
for
feedback
from
that
point
of
view,
as
well
for
things
that
we
might
do
do
better
or
different
in
the
future
of
these
hackathons
I
personally
I
ran
an
event
at
the
beginning
of
February,
a
sort
of
in-person
hack,
fun,
I'd,
almost
call
it,
and
that's
something
that
I'd
love
to
do
more
of
going
forwards.
B
C
Okay,
so
in
case
in
getting
some
technical
organization,
questions
can
be
dedicated
to
you
directly
yeah.
B
Yeah
I
mean
I
would
I
would
encourage
to
reach
out
generically
on
Discord
and
just
just
with
his
my
problem.
Can
anyone
help,
but
certainly
if
you
don't
get
a
response,
you
can
ping
me
kind
of
directly
on
on
that.
But
you
know
there
will.
There
will
be
quite
a
large
number
of
contributors
and
you
know
I'd
feel
bad
if
I
kind
of
missed
one
out
so
initially
just
reach
out
and
the
chances
are
I'll,
be
the
one
to
maybe
reply
anyway.
B
But
you
know,
we've
got.
We've
got
plenty
of
team
members
and
community
members
on
the
Discord
or
willing
to
help
out,
but
yeah
you're
welcome
to
message
me
directly
as
well.
C
And
maybe
one
more
question
from
my
site
about
algorithm
of
contribution.
For
example,
I
take
some
issue
in
which
I
would
like
to
have
some
work,
should
I
notify
somebody
in
a
channel
that
I
work
working
under
this
one.
B
Yeah
so
so
I
have
a
adding
a
note
to
the
issue
itself
or
in
Discord
either
of
those.
So
a
team,
member
or
member
of
the
core
team
can
can
hop
on
and
assign
that
issue
to
you.
B
It
just
gives
a
bit
of
visibility
to
prevent,
maybe
two
people
trying
to
pick
up
the
same
issue
at
the
same
time,
although
we
are
quite
Keen
to
what's
the
word,
encourage
more
collaboration,
moving
forwards,
so
I
kind
of
attribution
model
at
the
moment
isn't
perfect.
From
that
perspective,
it
only
really
attributes
the
merge
request
to
the
author,
but
going
forwards
we
want
to
ensure
that
kind
of
co-authors.
Anyone
put
the
pushes
a
commit
to
a
merge
request
will
also
be
attributed
and
also
people
that
review.
B
So
we
have
some
great
community
members
that
are
doing
a
real
good
job
kind
of
reviewing
contributions,
not
just
making
the
contributions
themselves
but
reviewing
them,
and
we
want
to
kind
of
ensure
that
we're
recognizing
all
of
that.
So
we
would
like
to
encourage
at
some
point
more
kind
of
collaboration.
Maybe
you
want
to
work
on
something
that
needs
front
end
and
back
end,
but
maybe
you're
a
back-end
developer.
B
So
you
know
you
get
a
colleague
or
a
friend
or
another
Community
member,
that
works
on
the
front
end
side
and
you
kind
of
collaborate
on
that,
but
yeah,
but
ping
ping
on
the
issue
itself
that
you're
looking
to
work
on
or
or
on
Discord,
and
someone
will
assign
it
to
you
and
obviously,
if
any
additional
helps
needed
in
terms
of
a
kind
of
implementation
plan.
B
C
Okay,
thank
you
and
in
our
like
General
project,
we
have,
for
example,
business
analytics
which
can
justify
whether
it
is
a
bug
or
like
a
feature.
So
in
case
of
such
a
question,
to
whom
I
can
ask
it.
B
B
A
Small
note
from
my
site,
gitlab
is
all
about
asynchronous
collaboration,
so
feel
free
to
log
and
be
sure
maybe
search
for
the
keywords
and
check.
If
such
item
already
exists,
the
search
functionality
is
pretty
great
and
the
main
rule
rule
of
thumb
starts
from
the
issue
so
document
your
findings,
post
it
to
the
git
lab,
maybe
even
use
some
template
so
available
for
gitlab
com
repository.
A
They
are
pretty
detailed
and
interesting
and
not
so
necessary
and
then
post
a
link
to
the
Discord
and
start
the
discussion
in
that
issue.
Asynchronous
sleeveless
comments,
so
team
members
can
join
maybe
three
triage
it
and
and
so
on.
A
Hey
these
are
all
the
questions
we
had
in
our
notes,
so
we
are
a
bit
overtime,
but
so,
let's
still
continue,
maybe
something
we
want
to
be
on
the
recording
for
our
audience
possible
audience.
D
B
Yeah,
absolutely
the
I'm
I'm
trying
to
get
team
members
to
curate
lists
as
well
as
possible,
so
to
find
issues
that
they
think
would
be
suitable
for
newcomers
as
well.
As
you
know,
existing
contributors,
the
more
we
can
make
sure
that
it
is
very
easy
to
to
to
look
at
an
issue
as
a
regular
contributor
or
a
team
member
and
think.
B
Oh,
that's,
a
quick
and
simple
fix,
but
if
you're
new
to
the
the
the
project
the
code
base
it
that
may
might
not
be
the
case
so
yeah
we,
we
do
ask
for
team
members
to
try
and
curate
a
nice
list,
but
at
the
same
time
that's
there's.
There's
no
exclusivity
on
that.
B
You're
welcome
to
create
your
own
issue
and
have
a
little
conversation
about
something
that
you
maybe
want
to
add
or
change
that
an
existing
issue
doesn't
exist
or
search
for
or
find
or
even
if
you've
got
old
issues
that
created
some
time
ago.
You
can
pick
anything
up,
yeah,
absolutely.