►
From YouTube: Q1 2021 GitLab Hackathon: Package group office hour
Description
A
All
right,
hello,
everyone
and
welcome
welcome
to
the
last
office
hour
call
of
the
day.
Just
let
me
quickly
share
my
screen
for
a
few
reminders
before
we
jump
into
the
content
of
the
call.
So,
first
of
all
here
at
gitlab
we
strive
for
before
fostering
and
building
a
safe
and
inclusive
environment
for
everyone,
so
enforcing
the
community
code
of
contact
is
really
important
for
us.
A
So
if,
at
any
point
you
feel
threatened
or
unsafe-
or
you
know,
harassed
through
a
comment
somewhere
or
through
our
communication
platform
feel
free
to
reach
out,
so
we
can
intervene
immediately,
other
than
that
you
can
always
seek
for
support
and
help
and
generally
guidance
or
ranging
related
to
the
hackathon
or
generally
gitlab
at
our
guitar
channel
github.im,
slash,
gitlab,
slash
contributors
feel
free
to
ping
me
directly
or
ask
your
question
there
straight
away
what
else
we
are
halfway
there
and
so
far
we
have
153,
mrs,
which
is
amazing.
A
B
B
Well,
thanks
thanks
christos,
and
it's
awesome
to
see
that
we
have
so
many,
mrs
already
in
progress,
maybe
we'll
hit
200
for
this
hackathon.
That
will
be
a
really
awesome
accomplishment.
B
We
have
an
issue
and
it's
linked
and
I'll
link
it
in
this
chat
as
well.
But
you
can
see
here
we
have
two
different
options
for
that
are
good
ideas
for
contributors
for
the
hackathon,
I
think
in
previous
hackathons
I
made
a
mistake
that
I
was
bringing
forward
issues
that
were
a
bit
larger,
a
bit
more
involved,
and
I
think
we've
learned
from
the
last
hackathon
that
it's
better
to
have
issues
that
are
easier
and
quicker
to
resolve,
especially
for
a
hackathon.
So
I
included
two
links.
B
One
here
lists
issues
that
are
labeled
good
for
new
contributors.
This
is
something
that
came
up
during
our
last
hackathon
that
we
said
we
should
label
identify
issues
like
that.
So
here's
a
list
of
12
options
that
are
good
for
new
contributors
that
are
are
limited
to
the
package
stage,
and
we
see
here
that
the
the
list
basically
runs
the
gamut
from
from
features
for
the
nuget
repository
composer.
B
So
really,
if
you're
interested
in
anything
to
do
with
packages
and
and
dependencies,
this
would
be
a
good
list
for
you
and
the
other
list
here
is
you
know
the
package
team
we
basically
and
we've
moved
myself
over
for
a
second.
We
use
the
weight
feature
for
when
we're
actually
going
to
work
on
issues.
So
it's
common
when
we're
planning
a
given
milestone
or
sprint.
B
The
engineers
will
go
in
and
add
weights
to
issues
using
a
scale
of
one
to
five,
so
I've
just
identified
a
list
of
package
related
issues
that
have
a
weight
of
one
and
then
there's
a
lot
of
issues
here
for
your
consideration
for
the
hackathon
and
you
could
sort
by
popularity,
so
you
could
see
what's
most
popular,
you
can
find
something
that
interests
you
using
label
search
so
yeah.
These
are
just
some
ideas
for
contribution.
B
A
For
reference,
I
have
linked
this
I've
added
the
information,
the
url
into
the
issue
that
you
have
into
our
hackathon,
wider
community
and
mars
issue
where
everyone
is
pointed
to
through
the
website
through
the
hackathon
website,
so
yeah,
if
you're
on
the
hackathon
website-
and
you
click
on
the
issue
where
we
track
and
you
can
find
issues
to
be
easy
issues.
To
begin
with,
you
can
find
the
package
group
issues
as
well.
B
B
So
the
first
piece
of
content.
Here
is
this
letter
from
the
editor.
You
know
as
someone
who's
been
I've
been
with
gitlab
for
nearly
two
years
now
next
week
and
I've
been
maintaining
this
page
for
for
that
entire
time.
So
I
thought
it
would
be
valuable
to
start
adding
a
personal
message
to
our
the
community
about
what
we're
working
on
and
why
and
what's
on
our
roadmap.
B
So
this
letter
talks
through
some
of
the
challenges
that
we're
facing
now
in
terms
of
building
out
our
existing
features
and
supporting
existing
customer
workflows
and
and
planning
some
additional
features
later
on.
That
will
help
us
to
build
a
more
competitive
feature
set
against
artifactory
and
the
big
key
component.
There
is
virtual
registries
so
we'll
be.
We
are
that's
part
of
the
dependency
proxy
and
we'll
be
working
on
that
later
this
year.
B
B
That's
what
we're
striving
towards
we've
validated
this
with
customers,
both
through
research
and
a
number
of
customer
interviews
and
prospect,
calls
and
things
like
that,
and
I
think
that
when
we
talk
about
customers,
it
could
be
valuable
to
distinguish
between
the
enterprise
and
non-enterprise
and
typically,
what
we
see
is,
if
you're
a
customer
or
an
organization
with
less
than
30
developers.
You
could
do
this
now.
B
You
could
use
git
lab
for
all
of
your
artifact
management
and
we
can
meet
your
needs
today
when
we
start
to
get
into
the
large
enterprises
teams
with
more
than
30
or
50
developers.
B
For
the
container
registry
right
now,
we've
gitlab
has
supported
a
native
container
registry
that
you
can
store
and
publish
container
images
to
your
project
right
now.
What
we're
working
on
is
a
change
that
will
add
support
for
online
garbage
collection
so
that
you
don't
have
to
set
the
registry
to
read
only
mode
when
to
clear
up
storage
so
for
our
self-managed
customers
that
have
many
terabytes
of
data
in
their
registry.
B
This
will
allow
them
to
remove
some
of
that
data
and
save
some
money
without
having
to
set
the
registry
to
read
only
mode
which,
for
a
big
global
company
can
be
difficult,
especially
because
the
development
never
stops.
B
What
else
the
package
registry
right
now
we're
really
focused
on
improving
our
existing
support
for
get
lab,
hosted.
Registries
last
milestone.
We
really
focused
on
composer
conan
and
generic
packages,
so
we're
at
continuing
to
round
up
that
functionality
and
yeah.
I
think
that's
probably
the
things
that
are
worth
highlighting
for
now.
It's
probably
five
minutes.
What
do
you
think
crystal?
Should
I
cover
anything
else.
A
No
that's
great.
Let
me
check
if
we
have
any
questions.
There
are
a
few
of
the
people
watching
on
on
youtube.
No
questions
there,
not
on
our
guitar,
so
yeah.
B
A
All
right,
thanks
for
joining
thanks
for
making
the
time
it's
really
nice
to
have
you.
I
know
that
in
some
some
cases
we
don't
have
people
participating
live,
but
I
go
check
out
the
videos
after
all-
and
there
are
quite
a
few
views,
especially
of
the
office
hour-
calls
that's
why
we
decided
to
have
all
your
office
our
calls
but
yeah.
A
The
point
of
the
office
hours
is
to
have
people
asking
questions
on
the
spot,
but
in
any
case,
we'll
reconsider
the
format
next
time
thanks
so
much
for
joining,
and
for
you
all
watching
at
any
time
again
thanks
so
much
for
your
contributions,
we're
slowly
reaching
200,
mrs,
which
is
quite
amazing
and
yeah,
looking
forward
to
see
more
and
at
any
given
time,
if
you
need
any
help,
support
or
have
a
question
head
over
to
our
guitar
channel
and
we'll
be
there
to
answer
any
of
your
questions
right.