►
From YouTube: Kubernetes Meet Our Contributors 20200108
Description
Join us, Jordan Liggit (@liggitt), Savitha Raghunathan (slack: @sraghunathan), Marko Mudrinic (@xmudrii), Paris Pittman (@parispittman) and a few other contributors for live upstream q&a, post kubecon story time, and your monthly dose of random!
When Slack seems like it’s going too fast, and you just need a quick answer from a human...
Meet Our Contributors gives you a monthly one-hour opportunity to ask questions about our upstream community, watch interviews with our contributors, and participate in peer code reviews.
Check out this page for more information: https://github.com/kubernetes/community/blob/master/mentoring/meet-our-contributors.md
A
A
Only
a
couple
days
of
the
year
and
I'm
already
making
drivers
say
so
welcome
everyone.
My
name
is
Paris
I
work
at
Google.
We
do
this
find
45
minutes
to
an
hour
of
enjoyment
ahead
of
us
for
mentoring,
on
demand
for
the
kubernetes
upstream
project.
We
have
over
thirty
five
thousand
contributors.
Obviously
it's
hard
for
us
to
give
our
individual
time
to
thirty
four
thirty,
five
thousand
people,
but
we
do
it
in
this
way
so
that
it's
reported
and
we
can
clip
out
really
cool
bits
of
information
that
these
folks
are
gonna.
A
Give
you
today,
like
all
other,
meet
our
contributors
days.
We
have
great
core
contributors
with
us.
We
also
Jorge
Castro
on
the
ones
and
twos.
That's
helping
us
with
YouTube
will
get
two
intros
in
a
second,
but
first
things.
First,
we
do
have
a
code
of
conduct.
Please
be
excellent
to
each
other.
That
includes
our
panelists
they're,
going
to
be
asking
each
other
questions
and
talking
to
each
other
too.
A
If
you
are
in
our
slack
Channel,
that's
hashtag
meet
our
contributors
when
they
kubernetes
slack
or
if
you're
on
twitter,
wherever
you
are,
please
be
awesome
to
each
other.
This
is
a
awesome,
helpful
community
and
we
would
like
to
keep
it
that
way
and,
as
I
mentioned
four
panelists,
please
feel
free
to
chat
with
each
other.
Many
of
you
don't
know
each
other
as
of
today.
So
that's
also
another
point
of
this
show
to
get
contributors
together.
A
That
might
not
know
each
other,
so
let's
go
ahead
and
go
into
intros
and
then
what
we're
gonna
do
is
I'm
gonna
pull
up
some
contributor
announcements
as
well,
some
things
that
we
want
the
broader
community
to
know
and
then
we'll
get
into
questions
cool,
alright,
so
first
person
in
my
zoo
window
box
here
is
Jordan
Jordan.
Who
are
you?
How
long
have
you
been
with
the
project?
And
what
are
you
currently
doing
now?
Okay,.
B
I'm
Jordan
Liggett
I
work
at
Google
I
work
mostly
on
open
source
kubernetes.
So
this
is
what
I
do
most
of
the
time
and
I've
been
with
the
project
for
a
while.
So
I
tend
to
look
across
lots
of
different
areas
and
try
to
make
connections
between
people
working
different
areas
say:
you're
gonna,
add
something,
and
someone
over
here
is
gonna,
make
some
change
I'd
like
to
help
connect
people
and
make
them
aware
of
each
other
and
things
they
need
to
keep
in
mind.
C
D
I
am
Savita,
I
worked,
the
Matt
works,
I
am
a
platform
engineer
and,
of
course,
I
use
kubernetes
to
create
in
destroying
architecture,
art
forms
I
can
use,
they
can
be
used
to
host
web
application
and
I
got
interested
and
inspired
by
the
when
I
started.
Using
communities.
I
got
inspired
and
I
wanted
to
be
a
part
of
the
community
and
I
wanted
to
contribute
back,
and
that's
how
I
stumbled
upon
this
amazing
group
of
people
who
help
each
other.
I
am
relatively
a
new
contributor
I've
been
contributing
for
the
past
seven
eight
months.
D
A
You
so
much
for
being
here:
I
met
Savita
at
another
awesome,
mentoring
event
at
cube
con
that
we
do.
We
do
a
little
pod,
mentoring
and
note
the
pun,
where
three
people
join
up
and
have
a
conversation
and
then
in
20
minutes
get
up
and
have
a
conversation
with
three
other
people,
so
kind
of,
like
musical
chairs,
meets
kubernetes
contributors,
which
is
very
cool
so
back
to
announcements,
really
quick.
Some
things
that
we
wanted
to
review
cube
con
use
coming
up
check.
A
A
A
A
Or
a
thumbs
up,
yep
looks
fine,
okay,
cool,
so
yep.
This
is
our
communication
file
in
the
community
repo.
You
can
find
that
at
kubernetes,
slash
community
under
communication
as
well
as
well
as
all
of
our
best
practices
in
here
for
how
you
run
things.
So,
if
you're
also
participating
right
now
from
another
community
and
want
to
know
how
we
run
some
things
like
that
this
is
it
it's
a
great
resource.
A
A
B
So
170
no
went
out
in
December
117
one
resolves
a
few
issues
that
were
found
in
it
and
that
is
closing
out
end
of
this
week
and
should
be
getting
released
next
week.
I
know
the
schedule
development
scheduled
for
118
just
got
announced
as
well,
so
the
dates
around
design,
freeze
and
code
freeze
and
all
that
got
announced.
So
that's
under
the
cig
release
repo.
If
you're
interested.
A
Awesome
and
way
to
go
release
TM,
as
always.
Thank
you
so
much
for
everyone
that
participated
and
that
release,
especially
getting
it
out
with
limited
time,
limited
deadlines,
people
out,
etc,
y'all
Rock,
Marco
or
George,
or
anyone
else
have
any
contributor
related
announcements
that
would
be
fruitful
to
get
out
to
this
group.
E
A
One
more
one,
more
actually
begging
for
your
time
for
ten
minutes,
doing
the
contributor
experience
survey
for
everybody,
that's
joining
us
at
the
current
contributor
or
even
folks
that
just
have
a
couple
of
contributions
under
your
belt.
Every
year
we
do
a
contributor
experience
survey.
Last
year
we
had
about
160
responses
really
trying
hard
to
get
over
200
this
year.
So
we
can
have
a
good
poll.
A
This
is
how
things
happen,
with
your
workflow,
how
we
communicate,
etc.
We
really
need
a
pulse
on
that,
so
that
we
can
make
improvements.
How
you
fill
out
that
survey.
If
you
are
on
the
kubernetes
dev
mailing
list,
that's
kubernetes
dev
at
Google
works
comm,
join
that
if
you're
doing
an
upstream
development-
and
please
take
the
survey-
and
yes,
there
are
some
swag
incentives.
A
C
Okay,
so
I
started
contributing
to
Cuban.
It
is
before
the
Chuseok
google
Summer
of
Code
in
2018
I
wanted
to
give
it
a
try
before
I
apply,
and
it
went
very
well.
The
first
it
was
something
related
to
API
machinery.
Staff
answered
is
like
writing
a
new
test,
or
something
like
that.
It
was
quite
fun
and
I
like
how
the
process
looks
like
it
was
a
little
bit
hard
the
beginning
and
that
challenge
kippie.
Okay,
I
want
to
give
it
a
try,
was
to
get
it
to
see.
C
I
ended
up
applying
for
google
Summer
of
Code
getting
accepted
that
even
further
motivated
me
to
continue
later
on
after
I
have
I
really
liked
it
at
communities,
and
the
community
is
really
really
awesome,
like
one
of
the
best
out
there
and
I
really
loved
working
with
all
the
forks
and
I
just
decided.
Okay,
this
is
what
I
want
and
I
will
continue.
C
A
D
The
main
reason
I'm
here
is
I
would
say
in
the
community
and
I
like
the
people
and,
of
course,
all
the
cool
things
that
you
can
do
and
learn.
I'm
still
learning
and
I
logged
a
lot.
So
I
cannot
comment
about
the
development
here,
but
I
can
say
that
the
community
engagement
is
awesome.
Andy
Kindler,
although
there
are
like
more
things
that
are
than
just
coding
like
program
management
reaching
out
to
people
helping
each
other
mentoring
and
mentoring
is
a
big
thing
that
keeps
me
going
like
people
mentored
me
like.
D
A
B
I
was
working
at
Red
Hat
on
open
shift
before
kubernetes
existed
and
some
of
the
folks
there,
Clayton
Coleman
got
involved
with
the
kubernetes
project,
pretty
early
on
and
and
so
as
part
of
that
I
got
I
got
pulled
into
this.
I
actually
went
and
pulled
up.
My
very
first
contribution
and
I
think
it's
a
great
testament
to
how
little
the
kubernetes
development
experience
has
changed
over
time.
B
E
E
Like
and
like
he
wasn't,
mad
I
wasn't
mad,
but
it
was
like
we
could
both
tell
that.
There
was
like
a
missed
opportunity
there,
where
it's
just
like
nuts,
you
know
so.
I
was
like
yeah
I'll
be
back
tomorrow,
so
you
know
it.
That's
kind
of
like
the
tip
I
learned.
Talk
hang
out
get
to
meet
people.
That
way
when
I've
noticed
when
you
talk
meetings,
sometimes
it
becomes
obvious
that
there's
a
need
for
something
and
then
later
you
can
go
on
psych
and
say:
hey
I,
noticed
people
we're
talking
about
this
I.
Think
I.
E
A
E
C
C
B
B
We're
fixing
bugs
and
so
I
actually
have
contributed
to
random
dependency
projects
like
our
JSON
library
and
at
CD,
and
run
C
and
container
C
advisor.
So
you
ask:
what
are
the
projects
I
contribute
to
ones?
That
kubernetes
depends
on.
Sometimes
the
right
answer
is
not
like
work
around
a
problem
in
Guber
Nettie's.
It's
actually
go
to
the
upstream
project
and
fix
it.
A
A
B
B
F
B
B
B
B
That
can
be
helpful
for
sort
of
understanding
their
attitude
towards
open
source?
Is
this
a
thing
that
they
are
already
happy
with
sponsoring
people
to
do?
And
then
one
of
the
great
things
about
open
source
projects
is,
you
can
actually
talk
to
individual
people,
so
once
you
find
things
like
this,
you
find
a
project
with
people
from
a
particular
company
that
are
making
kind
of
recent
open
source.
You
can
reach
out
to
those
people
and
say
hey:
what's
your
experience
been
at
this
company
like?
B
E
E
Well,
you
know,
and
getting
involved
with
these
people
will
kind
of
like
get
you
known,
and
it's
a
good
way.
It's
a
good
way
to
help
with
your
career
right.
If
you
got
a
cute
con,
there's
always
people
looking
for
expertise
and
things
like
that
and
I
noticed
a
job
board.
This
year
was
just
people
were
like
extending
stickies
and
stuff
and
the
opportunity
to
just
like
start
off
working
in
open-source
if
you're
young
and
getting
started
it's
just
the
opportunities
really
good
for
people
right
now
and.
D
D
You
can
be
an
active
contributor
and
sometimes
that
you
know
like
you,
are
doing
a
job
and
you
go
home
and
then
you
know
three
times
and
you
do
or
open
source
and
it's
the
passion
that
you
want
to
find
a
open
source
beta
role
or
like
it's,
the
it's
for
other
career
growth.
So
it
depends
and
it's
a
balance.
That's
all
I
want
to
add.
A
Definitely
that's
always
a
popular
topic
and
open
source
is
where
do
you
find
the
balance?
How
do
you
find
the
balance?
Where
do
you
find
jobs
that
support
it?
So,
yes,
always
the
continuous
question.
All
right,
Dimon's
in
the
media,
contributor
slack
channel
asks.
Where
do
you
see
kubernetes
as
a
project
/so
and/or
community,
a
few
years
from
now.
A
A
B
An
API
is
sort
of
reaching
stability
and
reaching
GA
a
lot
of
those
are
finishing,
and
as
more
and
more
things
get
built
on
top
of
kubernetes,
we
need
to
transition
more
to
like
this
sustainable,
like
high
quality
foundation,
which
is
different
than
how
you
operate
when
you're
like
we're.
Building
everything
and
everything
is
new
and
we're
just
grow,
grow,
grow,
grow,
grow
and
so
practically
I
think
that
will
probably
change
how
we
do
development
change.
B
How
we
do
testing
to
be
more
concerned
about
remaining
a
stable
foundation
and
I
think
that
will
help
some
of
the
scalability
concerns
because
it
lets
people
build
on
top.
It
lets
people.
Do
things
at
different
paces
do
experimental
things
or
rapid
development
things
or
use
kubernetes
in
new
and
interesting
ways,
without
sort
of
needing
to
graft
themselves
into
this
very,
very
large
development
process?
B
A
B
I
mean
did
three
cigs
in
particular:
had
a
lot
of
API
related
work
over
the
last
year,
or
so.
Six
storage,
sig
windows
and
cig
networking
and
all
three
of
those
SIG's
had
people
within
the
sig
get
familiar
with
the
process
and
the
standards
and
and
do
a
really
great
job
of
doing
first
pass
reviews
or
catching
things
early,
so
that
they
could
iterate
rapidly
make
progress.
So
by
the
time
things
bubbled
up
to
sort
of
the
official
final
API
review
a
lot
of
things
that
already
been
caught.
A
B
So
when
we're
reviewing
a
storage
feature,
we
do
that
with
one
or
two
people
from
the
storage
sig
present.
So
they're
kind
of
hearing
us
talk
through
like
I'm
thinking
about
this
I'm
asking
this
question
I'm
looking
at
this
and
checking
for
this
here's,
the
checklist
and
things
that
I'm
looking
for
they
and
we
tried
to
do
this-
live
right
so
like
over
videoconference,
so
that
they
have
an
opportunity
to
ask
questions
and
say:
wait,
wait
a
minute!
You
said
this
and
I,
don't
understand
why
you're
checking
for
this!
B
Why
is
that
important
so
that
that's
the
shadow
process
and
then
over
time
that
sort
of
flipped
to
where
the
sig
members
would
do
first
pass
reviews?
And
then
the
official,
reviewers
or
approvers
would
kind
of
come
in
and
do
cleanup,
say:
yep
looks
good
you
caught
that
contact
cut
back
cut
that?
Oh
you
missed
this,
and
so
like
the
set
of
things
that
the
sig
members
we're
needing
to
adjust
was
shrinking
over
time.
A
C
C
Include,
like
I
said,
like
you,
should
go
a
little
bit
stable
and
folks
that
we
provide
stable
API
since
everything
that
we
don't
really
have
situations
that
something
disappears
or
something
like
that,
and
what
I'd
like
to
say
also
is
that
we
pay
a
little
bit
more
attention
to
getting
the
contributor
experience
and
also
the
user
and
that
user
experience
battery
too.
If
you
want
to
scale
and
grow
a
larger
community,
we
want
to
be
sure
that
people
can
easily
get
on
board
start
contributing,
but
also
that
they
can
start
using
Cuban.
A
A
E
However,
over
over
the
break,
we're
having
Twitter
conversations
with
people
in
the
community
on
how
do
we
do
a
better
job
of
communicating
to
some
users
where
stuff
is
just
changing
so
rapidly
in
core
and
there's
really
no
way
for
them
to
like
figure
out,
you
know,
what's
changing
other
than
having
to
like
subscribe
to
all
these
lists
and
like
really
actively
pay
attention
does?
Does
anybody
have
any
thoughts
on
on
that
kind
of
user
experience?
As
far
as
keeping
track
of
the
platform,
I
guess
itself,
I
have.
B
Thoughts,
there
were
sort
of
three
ways:
I've
been
thinking
about
this
from
a
user
perspective
from
a
cluster
administrator
perspective
and
then
from
sort
of
a
documentation,
consumer
perspective,
sort
of
documentation.
Consumer
perspective
today
looks
like
read:
50
pages
of
release,
notes
every
three
months
very
carefully.
I
mean
we.
B
It
still
requires
people
to
actively
sort
of
cold
documentation,
and
so
the
other
two
aspects
I'm
thinking
about
are
from
a
user
perspective
and
from
an
admin
perspective
from
an
admin
perspective,
I'd
like
to
see
metrics
around
usage
of
deprecated
things,
so
we
have
metrics
for
monitoring
when
we
publish
via
Prometheus
I
think
it
would
be
great
to
say
when
something
gets.
Deprecated
register
a
metric
for
that,
and
if
that
deprecated
thing
gets
used,
it
shows
up
in
metrics
and
then
an
admin
who
cares
to
know
like
are
people
using
deprecated.
B
Things
in
my
clusters
has
a
tool
that
they're
already
using
for
other
monitoring
things.
They
can
just
pull
that
and
say,
like
deprecated
usage,
good
bad,
and
we
can
segment
it
out
by
like
this
API
this
operation.
You
know
this
flag,
whatever
I
think
that
would
make
it
way
easier
for
an
administrator
to
say.
B
Is
it
safe
for
me
to
upgrade
or
do
I
need
to
go,
hunt
down
the
people
who
are
using
deprecated
things
you're
going
to
be
broken
when
I
upgrade
to
1/16,
so
for
that's
from
an
admin
perspective
from
a
user
perspective,
I
would
like
to
see
things
like
warnings
surfaced
back
the
acute
control,
so
I
just
threw
a
link
to
a
pull
request.
I've
had
sort
of
in
progress,
I
guess
for
a
year
now,
that's
depressing!
B
That
would
give
a
mechanism
for
the
server
to
say:
hey,
you
just
created
something
to
be
a
deprecated
API
like
it
still
works,
it's
fine,
but
just
so
you
know
you're
doing
this
because
the
problem
we
see
a
lot
of
the
time
is
people
are
using
deprecated
things.
They
don't
realize
it
like
they
might
be
using
a
manifest
that
was
provided
to
them
by
somebody
else.
They
didn't
even
define
it
and
it
uses.
B
You
know
an
extension
to
be
one
beta,
one
deployment
and,
if
you
like,
if
you
upgrade
and
that
stops
working,
they
didn't
define
the
manifest.
So
like
they're,
not
even
aware
they
have
this
issue,
but
if
for
three
releases
they
got
a
warning
every
time
they
created
that
saying,
hey
you're,
using
this
deprecated
thing,
it's
gonna
go
away
like
that,
would
give
them
time
to
go
bug
the
source.
For
that
manifest
to
say,
I'm.
Getting
these
warnings.
Do
you
need
to
do
something
here
so.
B
So
that's
actually
probably
a
good
place
for
someone
who
already
contributed
looking
for
kind
of
a
longer
term
sort
of
intermediate
project.
Both
of
those
things
would
touch
a
lot
of
areas.
So
it's
probably
not
a
great
first
issue
type
of
thing,
but
but
it's
would
be
a
very
useful
and
immediate
project.
I
would
say
I.
B
A
Was
violently
fight
me
because
when
we
have
an
outreach
intern
right
now,
shout
out
and
she's
working
on
some
website
stuff
for
us,
like,
hey,
hey,
hey,
API,
deprecation
like
so
that
was
one
and
all
types
of
other
stuff.
So
know
the
metrics
thing
was
really
interesting
for
me,
so
that
I
think
that
is
a
fabulous
idea.
I
don't
know
like
I
thought,
I
thought
I
saw
George
like
shaking
his
head
in
unison,
I.
E
B
We
have
some
of
that
already,
like
the
struggle
with
metrics
is
always
like
how
much
information
do
you
retain
how
expensive
are
the
metrics
to
accumulate,
and
so
we
sort
of
have
to
start
the
balance
between
like
they're,
not
an
audit
log
right.
So
we
do
some
aggregation,
so
you
can
already
see
like
API
groups.
People
are
using
what
versions
people
are
using,
but
explicitly
like
that.
That
requires
administrators
to
again
read,
release,
notes
and
figure
out.
B
What's
deprecated
and
then
go
craft
metrics
query
is
to
say,
like
let
me
ferret
out
the
particular
things
that
are
deprecated.
We
we
write
it,
we
know.
What's
difficut
should
put
those
in
their
own
metric,
which
is
a
if
you
see
this
here.
It's
bad
and
I
would
I
would
even
augment
that,
with
this
you're
using
a
deprecated
thing
that
will
be
removed
in
the
next
release,
like
there's.
B
D
Truly,
this
happened
to
me
yesterday,
yeah
so
I
was
upgrading.
One
of
my
clusters
and
I
didn't
realize
the
ingress
extensions
were
duplicated
and
we
know
it's
going
to
be
duplicated
soon
and
we
have
to
start
using
the
networking
guard
gates
that
I.
If
I
forgot,
what
the
the
kind
and
I
was
I
went.
I
did
do
a
research
and
I
had
to
read
a
lot
on,
find
the
documentation
in
to
Jordan's
point
I
as
a
cluster
admin.
I
would
definitely
appreciate
a
pH
which
say
is
deprecated.
D
I
would
also
appreciate
a
page
which
would
have
tabs
telling
that
this
is
gonna,
be
duplicated
in
two
releases
or
three
releases
or
like
four
releases
from
now,
so
that
I
can
warn
the
users
or
when
I'm,
making
a
breaking
change.
That
I
would
want
to
tell
all
the
uses
of
my
cluster.
Hey
guys.
I
noticed
this
increased
as
your
application
redeploy
whatever
that
the
processes,
so
that
would
be
my
another.
That
would
be
my
suggestion
it
wrong
with
the
duplicated
page.
If
we
could
get
another
page
that
says
soon
to
be
duplicated.
E
In
that
thread
with
in
cold
water
we'd
actually
talked
about
what,
if
you
had
API
that
kid
said,
I,
oh
and
the
docs
were
just
integrated
into
that.
So
when
you
had
to
look
up
an
API
there's
a
little
banner
at
the
top,
you
know
that's
like
hey.
This
API
is
deprecated
or
you
can
have
little
announcements
because
I
don't
know
we're
we're
tossing
around
a
bunch
of
ideas.
If
anybody
out
there
is
interested
in
working
on
this,
though
that's
just
piling
issue
and
slap
I
hope
wanted
label
on
it
yeah.
E
Well,
you
know,
there's
a
difference
between,
like
everyone's
Theory
crafting
on
Twitter
and
being
actually
like,
write
it
down
in
like
a
cohesive
thing.
So
we're
still
kind
of
you
know.
I
mean
it's
like
a
good
thing,
where
you're
talking
in
the
hallway
right,
you're,
not
quite
ready
to
like
write
a
kept
me
half-baked
issue.
A
All
right,
I
believe
that's
it
for
questions.
Oh
no
put
up,
I
apologize
ding-ding-ding
on
slack
diems!
Oh,
we
have
is
a
famous
question,
which
is
what
can
I
do
to
start
contributing
code
wise
for
kubernetes.
So
this
is
a
pretty
general
question
that
can
be
tackled,
obviously
multiple
ways.
So
if
you
are
a
go
developer,
for
instance,
and
you're
looking
to
contribute
code
to
kubernetes,
where
would
you
start
and
please
yes,
I
know
that
some
it's
like
there's
so
many
places.
B
So
if
you're
a
networking
person
go,
ask
in
the
sig
Network
select
channel
or
show
up
at
a
sig
net
work
meeting
and
say:
hey
I
want
to
contribute.
I
have
this
much
time
I
can
I
can
put
a
couple
hours
in.
Is
there
someone
who
could
point
me
at
a
bug
or
point
me
at
a
clean
up
issue
or
just
something
to
kind
of
get
me
oriented
and
sort
of
be
on
the
hook
to
review
my
contribution
review.
B
My
pull
request
making
a
personal
connection
is
really
helpful,
both
for
you
to
get
oriented
and
not
spin
your
wheels
getting
started
and
to
make
sure
that
the
thing
that
you
open
up
or
request
for
actually
matters
to
someone
who
is
able
to
review
it
and
give
you
feedback
and
sort
of
Shepherd
you
through
that
process.
So,
but
if
it's
Signet,
working
or
scheduling,
maybe
you're
sort
of
a
low-level,
Linux,
keek
and
so
sig
node
is
good
for
you,
maybe
you're
a
high
level
like
server
api
geek.
B
D
I
agree
with
Jordan.
That
was
a
great
answer
and
to
add
to
that,
I
would
also
say:
subscribing
to
the
mailing
list.
I
got
an
opportunity
to
write
code
contribute
to
curve,
because
there
was
this
mentorship
program
component
config.
What
keep
from
work
component,
config
migration
working
group
I-
might
get
the
name
wrong,
I'm.
Sorry,
too
many
groups.
So
there
was
his
mentorship
program
and
they
were
actually
they
had
made.
C
Today,
go
on
the
meeting,
some
slack
try
to
reach
out
and
say
that
you
want
to
start
take
a
look
at
the
metric
opportunities.
I
think
we
have
a
few
now
like
if
you're
coming
to
Cuba
con
in
the
past.
There
was,
if
you
are
a
student,
you
can
take
a
look
at
google
Summer
of
Code
Beach.
You
can
work
over
the
summer
project
such
as
Cuban,
it
is
I,
am
Not
sure
I'm
going
to
participate
here.
I
think
the
call
will
be
in
adoption
or
something
like
that
for
projects.
C
Also,
we
have
outreach,
is
sometimes
participating.
So
you
have
a
lot
of
opportunities
to
get
started
and
take
a
look
at
them
and
see.
Are
you
likeable
for
safa
cadet
and
for
me,
google
Summer
of
Code
worked
pretty
well
and
I've
managed
to
learn
a
lot
about
the
project
and
it
helped
me
to
stay
here
and
coach
with
even
more.
A
B
If
you
look
at
the
message
that
the
bot
puts
in
when
test
fails,
it
asks
to
find
and
reference
a
an
issue
for
the
test
that
failed,
I
recognize
that
the
test
that
failed
is
probably
not
your
fault,
but
a
thing
that
you
can
really
do
to
help.
The
community
is
to
open
issues
for
specific
tests
that
are
failing,
and
if
you
are
looking
for
something
to
do,
find
an
issue
for
a
specific
test
that
is
failing
but
isn't
owned
by
someone
yet
and
see.
B
B
D
I
just
have
a
quick
advice
that
the
it's
not
related
occurred.
It's
like
it's
from
experience.
It
might
feel
overwhelming,
because
the
community
and
the
everything
seems
huge,
but
how
I
got
over.
It
was
just
to
find
a
Help,
Wanted
or
good
first
issue.
Although
it
took
me
like
eight
months,
because
I
was
just
hanging
out
and
seek
release
call,
which
is
a
good
thing
that
you
get
to
learn
people
in
what
process
and
how
it
is
going,
but
don't
hesitate
to
go
to
the
flood
child
and
say
hey
I'm
new.