►
From YouTube: GitLab Hackathon - Package Group Office Hour
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Good
morning
afternoon
or
evening,
everyone
whenever
you're,
watching
it
I'm
christos
and
with
me
I
have
tim
and
david
before
we
jump
into
the
introductions
and
also
the
details
about
the
call
just
a
friendly
reminder
about
some
of
the
logistics
of
this
hackathon.
Let
me
just
briefly
share
my
screen.
A
All
right
so
on
the
hackathon
page,
you
can
find
all
the
necessary
information
about
the
hackathon.
We
are
midway
of
our
sessions
today
there
are
there
is
there
are
two
more
in
total
coming
up
so
so
far
we
have
36
merge
requests
submitted,
which
is
really
exciting,
really
cool
thanks
everyone
for
your
contributions,
just
a
reminder
in
case
that
you're
beginner,
it's
the
first
time
trying
to
contribute
to
gitlab.
You
can
check
the
contribute
page
where
you
can
find
a
bunch
of
information
around
develop
contributing
code.
A
A
new
addition
here,
which
is
really
nice,
is
the
git
board.
So
a
lot
of
people.
You
know
they've
been
trying
to
set
up
the
development
environment
and
right
now
there
is
also
kidbot
which
helps
you
set
up,
jdk
really
easily
on
the
cloud
so
and
really
fast.
So
it's
really
easy
and
straightforward
for
everyone
and
they
can
contribute.
A
A
It's
going
to
calculate
it's
going
to
show
you
your
local
time
of
the
session,
and
each
session
has
a
zoom
link
and
some
of
them
they
have
representation
or
issues
relevant
issues
where
you
can
find
some
issue
relevant
to
the
product
or
issues
to
begin
with
or
where
to
work
with,
or
some
of
them
are
also
relevant
to
the
things
that
we're
going
to
discuss
during
the
calls.
A
And
with
oh
yeah,
another
reminder:
if
you
want
to
reach
out
or
get
help,
join
the
contributor's
kit
room,
you
can
find
everyone
there.
They
can
help
and
also
because
at
gitlab
we
we
want
all
of
our
events
and
generally
we
want
everyone
to
feel
included
and
safe.
We
are
enforcing
the
community.
A
We
oh
here.
We
are
the
community
code
of
contact
if
you
feel
insecure
or
if
you
feel
not
safe
or
you
under,
identify
an
inappropriate
behavior.
Please
reach
out
to
conduct
at
gitlab.com,
it's
really
important
for
us.
We
keep
an
eye
on
merger
quests
on
comments
and
also
on
the
guitar
in
case
we
spot
any
inappropriate
behaviors.
A
But
if
you
feel,
if
you
don't
feel
safe
from
someone's,
you
know
reaction
or
text
or
message
or
anything
just
feel
free
to
reach
out
to
us
and
with
no
further
ado,
I
will
pass
it
over
to
david,
ed
and
tim
thanks
for
joining
us.
B
B
I
think
maybe
a
brief
introduction
christos
will
be
valuable
to
the
package
stage
of
what
categories
we
cover.
So
the
package
stage
covers
multiple
categories.
It
covers
includes
a
package
registry
which
includes
a
variety
of
formats
that
you
can
publish,
install
and
share
your
dependencies.
B
We
have
support
for
composer
conan,
go
maven
and
pm
nougat
pi
pi
and
generic
packages
and
long
term.
We
have
intentions
to
add
all
these
other
formats
as
well.
The
most
the
highest
priority
ones
on
here
are
support
for
some
of
the
linux
packaging
systems
like
rpm
and
debian,
which
we
have
an
in-progress
merge,
request
for
and
then
as
well
as
ruby
gems,
which
will
be
really
important
for
git
lab,
because
that
we
could
actually
dog
food
that
feature
and
help
rapidly
transform
the
package
registry
based
on
the
sort
of
the
scale
of
gitlab.
B
B
We
offer
a
dependency
proxy
which
for
now
proxies
and
caches
images
from
docker
hub.
So
this
will
help
you,
if
you're
trying
to
avoid
the
new
docker
hub
rate
limits.
You
could
do
this,
so
you
won't
be
charged
for
an
image
pull
every
time.
You
pull
something
from
docker
hub,
also
in
2021
that
since
it's
the
new
year,
it's
worth
mentioning.
B
This
is
going
to
be
a
major
focus
for
us,
bringing
together
the
dependence,
dependency
proxy
and
the
package
registry,
so
that,
instead
of
just
proxying
and
caching
images
from
docker
hub,
you
could
do
the
same
with
node
packages
or
maven
packages
and
any
other
format.
But
those
are
the
most
important
too
for
us
a
little
further
down
the
road
for
us.
B
Is
this
dependency
firewall
and
you
could
think
of
this
as
going
well
with
the
rest
of
get
lab,
secure
products
which
will
tell
you
if
you
have
a
you
know
a
cve
when
you
download
a
dependency?
What
we'd
like
to
do
is
give
the
firewall,
as
give
you
give
administrators
the
option
to
say
never
download
a
package
that
has
this
license
or
never
download
a
package
from
npm
js
if
it.
B
If
the
author
name
has
changed
in
the
past
30
days
or
if
there's
any
suspicious
activity,
so
it
gives
you
a
little
bit
you're
preventing
things
from
ever
even
entering
into
your
system
as
a
so
that
that's
something
that'll
probably
be
more,
the
second
half
of
2021
and
then
a
recent
new
category
that
we
added
that
we
haven't
thought
too
much
about.
Yet
on
our
side.
Is
that
release
evidence?
B
So
when
you
create
a
release,
you
likely
want
to
have
links
or
packages
or
images
that
are
included
as
part
of
release
evidence,
and
it
makes
a
lot
of
sense
for
the
package
stage
to
own
this,
because
a
lot
of
the
dependencies
that
you're
working
with
as
part
of
the
package
registry
and
end
up
as
release
evidence
so
really
what's
our
goal.
Our
goal
is
to
build
a
product
that,
within
three
years,
is
your
single
source
of
truth
for
storing
and
distributing
images
and
packages.
We
would
like
to
be
this.
B
Your
soul
rely
solely
on
gitlab
for
those
we
have.
Ideally,
we
would
help
you
replace,
artifactory
or
sonotype.
For
example,
we
want
to
bring
together
the
container
registry
and
the
package
registry
through
the
dependency
proxy.
So
right
now
we
really
only
support
locally,
hosted
images
and
packages.
We
really
want
to
also
allow
you
to
support
remote
packages
as
well.
B
So,
for
instance,
if
you
wanted
to
proxy,
like
you,
could
proxy
now
images
from
dockerhub,
we
want
to
do
the
same
thing
with
node
packages
and
then
it's
very
important
to
us
that
everything
that
we
build
is
easy
for
people.
Folks
in
the
community
to
contribute
to
both
from
a
code
side
and
then
also
from
a
process
side,
do
you
know
how
to
engage
with
the
team?
Is
there
a
way
for
you
to
ask
questions?
B
Is
we
just
really
want
to
improve
the
performance
and
reliability
of
your
builds
by
reducing
reliance
on
external
dependencies
so
that
that'll
that
all
go
falls
in
line
with
everything
we
said,
but
that's
in
the
in
the
end,
a
big
goal
for
us
okay,
so
I
kind
of
gave
a
quick
run-through
of
the
categories
and
maybe
what
some
of
what
our
plans
are?
You
could
check
out
our
documentation,
just
look
for
packages
and
registries
and
you
could
dive
into
any
of
the
specific
formats
and
then
we
have
oops.
B
Let
me
minimize
that
we
have
a
hackathon
issue
for
today's
event
and
in
there
I
linked
a
bunch
of
issues
that
could
be
good
ideas
if
you're,
considering
contributing.
I
was
just
mentioning
to
christos
before
the
call
oops.
B
I
was
just
mentioning
that
we
last
hackathon,
I
made
a
mistake
and
I
included
a
bunch
of
more
complex
features
in
there
that
aren't
really
possible
to
contribute
to
in
one
day.
So
today,
if
you'll
notice,
these
are
the
weights.
B
Our
team
ads
adds
weights
to
each
issue
when
we're
about
to
work
on
them,
so
that
we
can,
you
know,
better
measure
our
work,
so
we
try
to
choose
all
small
issues
and
we
also
try
to
pick
initi
issues
that
range
from
updating
documentation
which
could
be
done
by
someone
who's,
not
necessarily
a
developer
like
a
product
manager
or
designer.
B
If
you
click
through
these,
I
would
say
you
know,
if
you're
interested
in
just
the
documentation,
if
you
click
on
any
of
the
they're,
usually
pretty
obvious,
like
update
documentation
for
anonymous
requests,
and
then
you
can
click
on
this
issue
and
you
could
read
through
what
we're
trying
to
do
and
in
this
case,
there's
even
an
existing
mr
for
updating
npm.
So
you
could
follow
what
we're
doing
there
and
do
the
same
thing
for
pi
pi
for
instance.
B
So
I
guess
that's
like
the
brief
summary
that
I
wanted
to
give
the
overview.
I
want
to
help
people
understand
what
is
what
would
do
what
we're
doing
what
issues
can
possibly
be
worked
on?
I
guess
I
should
say
how
should
people
get
in
touch
with
us
if
they
have
any
questions?
Well,
if
you're
starting
on
something,
you
could
ping
me
in
the
issue
directly,
that's
at
t
rizzi
or
you
could
email
me
t
rizzy
gitlab.
B
If
you
have
any
questions
or
look,
you
don't
see
anything
on
this
list
that
you
want
to
work
on,
or
you
found
something
else
that
you
want
to
work
on.
That's
totally
fine,
just
reach
out
we're
happy
to
help
and
and
dive
in
and
work
with
you
on
this,
because
we
really
enjoy
working
with
the
community
on
on
all
this
stuff.
A
Let
me
check
guitar.
We
have
two
viewers
online
on
youtube,
so
I
want
to
check
whether
there
are
any
questions
on
guitar.
C
B
C
No,
I
guess
you
gave
a
good
summary.
I
guess
my
advice
is
really.
If
someone
want
to
someone
wants
to
contribute
and
is
stuck
or
whatever
happens,
please
reach
out
the
team,
and
we
will
be
more
than
happy
to
help
it's
better
to
help
before
going
into
wide
ideas
and
then
well,
we
will
suggest
alternatives.
C
B
C
I
think
the
like
the
error
number
one
is
the
understanding,
the
iteration
value
we
have
at
github,
it's
quite
simple
as
a
concept,
but
it's
don't
work
on
everything
at
once
and
don't
try
to
put
everything
in
one
single,
mr,
you
can
split
the
work
create
as
many
mrs
you
want,
and
it's
easier
for
us
and
for
the
review
process
with
smaller.
Mrs,
I
saw
many
times
really
big,
mrs
and
those
are
quite
hard
to
work
with
and
well
each
time.
C
Each
time
we
suggest
an
improvement,
it's
it
end,
ups
in
huge
refactorings,
so
I
think
yeah
that
that's.
Why
I'm
I'm
saying
if
there
is
something
big
or
something
that
is
not
clear,
reach
out.
First,
because
we
can
discuss
about
the
approach
and
how
we
can
split
the
work
if
it
is
too
big.
C
C
It
has
nothing
to
do
with
with
what
I'm
doing
right
now,
but
I
can
improve
it
and
it's
a
small
thing,
so
I
will
add
it
to
the
current
changes.
But
that's
that's
not
a
good
habit,
because
you
will
end
up
with
an
mr
trying
to
do
too
many
things
at
once
and
well,
it's
you
have
to
cultivate
the
sense
of
okay.
This,
mr
will
focus
on
this
theme
of
these
exchanges
and
that's
it.
We
will
not
go
outside
of
it.
C
If
I
to
me
well
no
for
for
my
day-to-day
work
when
I
spot
something
that
I
need
to
do
outside
of
my
current,
mr,
we
just
create
a
new
issue,
and
actually
it's
it's
those
issues
I
saw
you
listed.
Those
some
of
them
are
mine
and
I
they're
awaited
one
and
their
origin
are
really.
I
was
working
on
something
and
I
spotted
something
that
was
wrong
and
well.
I
don't
have
time
to
deal
with
this
right
now,
so
I
would
just
take
the
problem
create
an
issue,
and
I
will
work
on
that.
B
C
Yeah
yeah,
it's
really
a
sense
of
knowing
that
you
have
many
benefits
on
working,
some,
some
on
something
smaller
than
bigger,
and
perhaps
those
benefits
are
not
straightforward
and
you
cannot
see
them
right
when
you
work
on
the
mr
and
it
takes
a
bit
of
experience
to
have
the
discipline
to
say.
Okay
now
stop.
This
is
too
big.
C
We
have
to
split
this
in
two,
mrs
and
well,
since
it
takes
experience,
that's
usually
what
happens
with
community
members,
they
don't
get
the
scale
of
the
code
base
or
the
or
the
the
scale
of
the
data
that
gitlab.com
handles,
and
we
we
end
up
in
really
big
amounts.
So
that's
why
please
reach
out.
If
you
need.
A
And
can
I
ask
a
question?
First
of
all,
I
can
reiterate
you
know
about
small
changes.
I
I
can
still
hear
my
manager.
I
just
recently
joined
recently.
I
joined
one
and
a
half
months
ago
and
my
first
one
of
my
first
onboarding
thing
issues
was
like
start
updating,
doing
changes
on
the
hackathon
page
on
the
page
of
the
of
your
program,
and
I
just
went
there
doing
some
changes
on
the
content
and
my
manager
was
like
no
that's
too
big
and
I'm
like
come
on.
I
just
changed
a
few
sentences.
A
A
When
you
make
a
merge
request,
you
want
to
have
only
one
commit
super
simple,
super,
simple
things,
but
some
cases
you
know
we
might
have
need
to
do
additional
changes
so.
C
Usually
I
try
to
have
a
single
comment
for
for
nmr.
Actually,
there
is
an
option
when
you
create
an
mr
that
you
can
take
it's
an
option
that
says
that
dmr,
when
it
will
get
merged,
gitlab
will
automatically
squash
all
the
comments,
so
you
don't
have
to
squash
it
manually,
squash
them,
but
in
development
is
really
hard
to
have
like
yeah.
You
have
this,
mr
in
three
comments,
and
there
are
three
logical
commits.
C
So
usually
what
happens
is
that
I
I
just
put
as
many
comments
as
I
need
and
during
the
reviews
we
you
will
get
feedback
and
I
will
apply
the
the
feedback
and
refactor
what
needs
to
be
refactored
and
then
at
the
end,
I
will
just
squash
everything
into
a
single
comment
or
have
this
option
in
the
image
request.
Enabled.
C
But
it
might
be
different
for
other
types
of
mrs
such
as
documentation.
Perhaps
it's
it's
it's
a
different
approach,
but
in
in
code
you
well
perhaps
it's
my
way
to
work,
but
I'm
really
doing
a
lot
of
things
at
the
same
time
and
modifying
a
lot
of
layers
of
the
code
at
the
same
time.
So
I
I
can't
organize
everything
in
logical
commits
and
well
it.
It
doesn't
make
sense,
because
you
work
in
logical
comments.
C
Okay
and
then
you
have
the
the
reviews
and
during
the
reviews
you
can
have
feedback
on
the
on
the
first
aspect
you
worked
on
so
then
you
have
a
comment
that
will
apply
the
feedback
on
this
first
aspect.
But
now
you
have
two
commits
that
are
changing
the
same
aspect,
but
they
are
separated
and
well
I
guess
I'm
I
don't
want
to
invest
a
lot
of
time
in
reorganizing
all
the
commits,
a
single
one
will
work
and
actually
there
is
a
benefit
for
the
production
team.
If
there
is
a
single
commit
for
for
nmr.
C
If
there
is
any
issue
and
we
can
source
the
issue
on
on
on
a
single,
mr,
the
production
team
will
be
able
to
just
revert
dmr
or
we
we
are,
or
even
the
engineering
team
will
be
able
to
open
an
mr
that
will
revert
the
default
t1
and
it's
easier.
If
it's
a
single
comment.
B
A
Let
me
check
again
get
there
nope
all
right.
B
I
was
just
gonna
say
one
of
the
things
that
I
love
about
get
lab
since
I
am
well
caffeinated
it's
the
morning
for
me.
Is
you
know
that
a
lot
of
people
use
this
platform
every
day
we
all
we
all
live
and
breathe.
B
I
mean
for
me,
I'm
living
and
breathing
in
gitlab
for
my
whole
work
day,
I'm
working
in
it
non-stop
and
the
idea
that
I
can
contribute
to
it
as
a
non-developer
or
the
idea
that
a
community
member
can
see
something
that
they
don't
like
and
contribute
to
it
or
add
examples
to
the
documentation
is
so
cool.
It's
you
know
it's.
It's
such
an
opportunity
to
say:
hey
you're.
In
this
platform
all
day,
you
should
have
the
right
to
change
what
you
don't
like.
B
You
should
have
the
right
to
improve
it,
and
I
really
love
that
aspect
of
gitlab
and
and
that's
really
to
me.
One
of
the
biggest
benefits
of
us
being
open
source
is
hey,
we're
all
on
this
platform
together
change.
What
you
don't
like
fix
it
improve
it,
make
a
suggestion,
make
a
change
and
we're
going
to
make
this
magical
devops
platform
that
we're
all
gonna
share
every
day.
C
I
said
already
earlier
that
when
I
found
something
that
we
need
to
work
on
or
fix,
I
will
just
create
an
issue
and
one
of
them
was
a
filled
in
in
an
object
that
was
not
validated
and
this
field
is
present
in
all
the
package
types
we
support.
So
I
created
an
issue
saying:
okay,
this
will
need
to
be
validated
and
we
have
all
these
types.
C
So
we
are,
we
will
need
to
validate
each
field
for
each
package
type
and
what
happened
is
that
I
implemented
for
one
package
type
and
all
the
others
were
implemented
by
the
community
itself.
So
I
I
reviewed
them,
but
it
was
super
impressive
that
okay,
this
was
a
side
work.
A
David
yesterday
I
come
from
a
strong,
open
source
environment.
I've
been
contributing
to
various
projects
for
the
past
10
years,
so
working
with
the
community.
It's
freaking
amazing
they're,
always
there
they
always
keep
you
accountable.
They
always
contribute
and
most
of
them
do
it
because
they
want
to
not
because
no
one
is
forcing
them
and
because
they
want
to
involve
projects
and
products,
which
is
quite
amazing.
A
Let's
hope
we're
going
to
get
more
also
memoirs
you're
in
this
hackathon.
A
Cool,
I
mean
in
case
that
there's
no
one
coming
up
live
right
now
with
questions,
and
there
is
nothing
from
the
other
side.
We
can
wrap
the
session
up
for.
B
A
I'll
keep
an
eye
on
guiter
in
case
there's
a
bridge
with
slack
as
well.
In
case
someone
has
a
specific
question:
how
I
will
tag
you
as
well,
thanks
again
for
making
the
time
and
thanks
again
for
your
tips
and
setting
experience
your
experience
and,
of
course,
for
for
the
content
as
well.
I
walk
through.
B
Oh
yeah
well,
thank
you
for
organizing
this
and
following
up
on
it
and
yeah
again.
If
anyone
has
any
questions,
just
reach
out
t
rizzy
at
gitlab
I'll,
I
could
help
follow
up
and
and
send
some
things
the
right
way
and
good
luck
hopefully
get
some
nice,
mrs
done,
and
I
think
there
are
some
prizes
right
for
contributions.
A
We
have
a
prizes
swag,
as
always
people
love
swag.
So
we
have
a
laptop
sleep,
whatever
emergency
quest
for
every
person,
but
something
someone
request.
We
have
a
duffel
bag
and
also
the
grand
prize
is
a
gift
card
for
for
the
gitlab
shop
to
get
whatever,
whatever
people
want
to
get.