►
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
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.
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
B
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.
A
B
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
A
A
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
A
B
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
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.
D
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.
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
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
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.
A
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
B
B
B
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.
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
C
B
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.
C
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
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.