►
From YouTube: Package: Community Office Hours
Description
We discuss adding Cargo, the package manager for Rust
A
So
one
of
the
reasons
I'm,
particularly
and
particularly
interested
in
this
issue
is
because
it
was
opened
only
about
two
months
ago
and
it
went
from
zero
votes
to
over
I
think
it's
over
ninety
now.
So
it's
a
really
good
sign
that
the
community
is
really
active
and
that
people
are
really
interested
in
having
the
feature
and
then
I
threw.
The
issue
talked
to
Renee
a
bit
about
maybe
contributing,
and
it
can
be
a
little
bit
intimidating
when
you're
just
looking
at
the
documentation
and
maybe
some
of
the
existing
em
ours.
A
B
B
That's
awesome
and
we'll
kind
of
like
coach
you
through
and
help
as
much
as
possible,
or
if
you
get
to
the
point
where
you're
like
you,
know
the
off
system,
that's
really
weird
and
it'd
be
nice.
If
you
know
you
guys
could
just
help
figure
this
out,
I'm
happy
to
jump
in
and
make
some
commits
to
the
merge
request
to
myself
and
how
up
in
any
way
possible
to
continue
just
make
sure
we
keep
it
moving
and
that
everyone's
know
helping
provide
it
like
it's
really
valuable
that
that's
can
create
some
excitement,
cool.
C
D
D
C
A
D
C
B
I
can
definitely
help
with
a
lot
of
that
and
really
and
I'll,
be
sure
to
kind
of
you
know
post
this
in
in
the
issue
or
in
if
you
have
a
merge,
request
open
some
of
the
specific
links
to
these
files.
But
the
API,
like
the
sort
of
the
starting
point,
is
in
the
sort
of
the
the
EE
directory
and
then
the
Lib
directory
and
API,
and
so
that's
sort
of
where
you're
probably
going
to
create.
B
You
know
a
file
called
cargo
packages,
dot
RB,
and
that
is
going
to
be
so
that,
like
that's
going
to
be
where
all
of
the
different
endpoints
are
defined,
that
that
that
gitlab
will
be
available
to
consume
from
the
cargo
client
and
I'm
not
familiar
with
with
cargo
actually
really
at
all.
So
I,
don't
know
if
it
works.
Where
you
know,
you
said
like
a
remote
for
the
registry
and
then
from
there.
The
the
cargo
client
makes
requests
to
that
remote.
B
But
this
is
where
all
of
those
types
of
endpoints
will
live
and
be
defined,
and
then
from
there
it
kind
of
just
depends
on
what
functionality
is
being
built
and
maybe,
as
you
start
to
work
on
one
a
given
end
point
I
can
kind
of
peek
in
and
suggest
you
know
putting
certain
things
in
certain
places
like
there's
a
services
folder.
That
will
make
sense
for
a
lot
of
items,
but
really
that
that
that
API
folder
is
the
starting
point
for
everything
from
the
most
part.
Okay,.
B
D
A
A
C
B
Yeah,
actually,
in
that
case,
I,
wasn't
thinking
about
that.
It
would
not
end
up
in
that
folder.
So
yeah
still
I'm
pretty
sure
it's
just
the
the
non
EE
equivalent,
so
I
think
there's
probably
just
a
lid
API,
I
fold
ER
and
up
to
look
at
that
a
little
bit
but
yeah
and
and
one
other
aspect
of
know
where
things
kind
of
kill.
If
you
start
sort
of
just
building
out
and
it
all
kind
of
just
expands
into
one
big
file,
that's
not
a
huge
deal
and
you.
B
D
Mean
just
one
point:
I
want
to
add:
I
mean
regarding
contributions
to
EE
I
mean
we
have
community
contributors
that
specifically
contribute
to
a
code
base,
because
there
are
like
users,
OBE
or
I
mean
you
actually
don't
even
need
a
license.
A
ie
license
to
contribute,
like
you,
just
can't
run
any
tests
like
locally,
for
example,
but
I
mean
this.
D
It's
I
mean
it's
really
up
to
Tim
like
he
saw
this
size,
which
goes
into
like
a
e
for
the
large
part,
but
I
mean,
as
a
community
manager
I'm
not
going
to
complain
that,
like
we're
gonna
make
as
many
things
available
on
core,
so
I
won't
stuff
him,
but
I
mean
if
you
have
any
issues
with
licensing
and
stuff
I
mean
let
us
know,
but
in
general
whether
it's
like
a
core
or
Iggy.
Like
I
mean
we
accept
contributions
everywhere.
D
D
D
But
if
you
want
to
just
reach
out
to
a
wider
audience,
we
have
a
group
of
people
called
merge,
quest
coaches.
If
you
have
like,
if
you
don't
descend
a
pipeline
failure
message,
for
example,
I
mean
any
one
of
those
individuals
would
be
more
than
happy
to
jump
on.
We
have
people
all
over
the
world,
so
I
mean
the
time
zone.
Should
shouldn't
be
an
issue?
Okay
and
and
just
out
of
curiosity
Renee.
Why
are
you
located
I'm.
D
C
B
So
for
testing
with
Ruby
and
rails
there's
a
test
framework
called
r-spec
that
is
pretty
widely
used,
and
it's
it's
the
main
test
framework
that
we
use
in
the
gate,
lab
code,
business
and
so
that'll
be
something
you'll
have
to
get
into
and
I'm
happy
to
help
out.
If,
once
we
have
some
idea
of
the
first
few
bits
of
code
that
would
like
to
write
tests
for
and
and
I
can
point
you
to
some
of
the
good
resource
is
for
for.
C
B
Know
kind
of
learning
that
and
seen
examples
of
that
and
preceding
we
actually
just
finished
I
think
it
might
be
now
merged
into
the
codebase,
adding
seating
for
some
of
the
other
package
managers
and
so
it'll
be
pretty
straightforward
to
hopefully
follow
that
same
pattern.
I
hope
there
is
a
I'll
find
the
file
of
where
the
existing
ones
who
live.
So
you
can
take
a
look
at
it
just
to
get
an
idea.
A
C
B
One
thing
no
I
might
suggest
is:
even
if
you
don't
have
any
code
written
or
anything,
you
know
go
ahead
and
open
a
merge
request
off
of
that.
That
issue-
and
you
know
just
as
a
place
where
you
know
you
can
ping
me
personally
or
or
the
package
team,
which
I
think
is
just
at
package
stage
and
then
it's
a
place
where
we
can.
You
know
start
chatting
and
talking
respond
to
any
questions.
You
might
have
a
synchronously
whenever
you
happen
to
be
working,
and
one
of
us
happens
to
be
looking
on.