►
From YouTube: Panel Discussion: CNCF Mentees - Kunal Kushwaha, Ihor Dvoretskyi, Divya Mohan, Uchechukwu Obasi
Description
Panel Discussion: Cloud Native Computing Foundation Mentees - Kunal Kushwaha, Civo; Ihor Dvoretskyi, Cloud Native Computing Foundation; Divya Mohan, HSBC; Uchechukwu Obasi, Grafana Labs
The CNCF community has proven that open source is for everyone and every contribution counts. To support this statement, there have been numerous opportunities provided by the CNCF community to get more young people and new contributors get involved in the project. Namely, GSoC, GSoD, LFX Mentorship programs, CROSS, Outreachy. Although, the problem of lack of awareness about these opportunities still exists. As well all saw, over 69% of the attendees were first-timers, and many students joined as well. This panel consists of ex-CNCF mentees & CNCF program managers. They are going to share their experiences & tips, regarding how they got started with CNCF, their journey with the internship opportunities & mentorship programs. In addition to that, viewers would also learn how to get started with CNC projects, right from picking an organisation, to making their first contributions. In the end, the panel will share some community best practices and resources.
A
our
hybrid
experience
here
so
for
those
for
those
of
us
who
join
us
you're
in
los
angeles,
for
joining
us
remotely
live
so
welcome
everyone.
This
is
the
student
track
of
cubecon,
and
here
we
have
a.
We
will
have
the
brief
conversation
with
people
who
are
building
our
community
who
have
started,
who
have
started
being
their
contributors
to
our
community
to
the
cloud
native
community
almost
from
scratch.
A
B
B
C
Hello,
everyone-
I
am,
I'm
a
team
lead
with
hsbc,
unfortunately
not
a
student
any
longer,
so
my
involvement
with
open
source
began
last
year
with
kubernetes
and
thereafter
with
it
was
chaos.
As
you
know,
it's
sick,
don't
sleep,
but
coming
to
the
aspect
of
mentoring
and
mentorship
programs.
My
whole
experience
with
it
has
been
you
know,
being
on
both
sides
of
the
coin.
C
Previously,
as
a
mentee
on
the
google
season
of
talks
and
this
year
as
a
mentor
again
on
google
season
talks
with
mosquitoes
so
yeah,
I
love
working
on
open
source
projects
apart
from
my
day
job,
because
it
gives
me
a
lot
of
exposure
to
things
that
I
would
typically
not
have
exposure
to.
So
that's
a
bit
about
me,
but
yeah
I'll
hand
it
over
to
this
bit.
D
Yeah
awesome
so
hi
everyone,
my
name,
I'm
a
software
at
grafana
labs
and
I'm
a
past
mentee
at
thanos,
I
actually
participated
in
the
lfx
mentioned
at
the
time,
was
called
community
bridge
and
yeah,
I'm
also
the
co-organizer
of
the
cncf
mexico
and
also
the
humanities
communities
africa.
I'm
super
passionate
about
creating
like
a
very
safe
space
for
newbie
contributors
to
contribute,
learn
and
collaborate
within
the
cncf
community
and
yeah.
I'm
super
excited
to
be
on
this
panel
land
yeah.
I
can't
wait
for
us
to
kickstart.
The
conversations
thank
you
awesome.
A
I
believe
that
you
have
you
you've
been
one
of,
if
I'm
not
mistaken,
you,
probably,
if
not
the
first
one,
but
one
of
the
first
mentees
with
the
cncf
community
bridge
and
lfx
programs
from
africa-
and
you
know
also
our
the
cnc,
the
first
cncf
ambassador
in
sub-saharan
africa.
So
can
you
share
some
some
some
more
details
about
your
experience
and
how
did
the
the
co-native
mentoring
experience
impacted
your
your
life
in
this
case.
D
Yeah
yeah
I'll
text
iho.
For
that
awesome
question,
so
yeah
I
mean
I,
I
really
can't
emphasize
this
enough.
I
think
open
source
really
changed
my
life,
so
I
would
maybe
share
a
little
bit
of
like
a
very
short
story
of
how,
like
I
joined
the
open
source,
especially
the
cloud
native
computing
foundation,
how
I
entered
that
tunnels
and
how
I
ended
up
like
final
lab,
so
I
will
try
to
make
it
as
short
as
possible.
D
So
when
I
was
like
in
second
year
in
college,
that
was
when
I
got
introduced
to
open
source
because,
prior
to
that
time,
my
goal
was
just
to
like
build
a
small
agency.
You
know
here
in
nigeria
and
just
like
meet
small
businesses
and
build
websites
for
them.
But
when
I
learned
about
open
source
I
was
like
okay.
Let
me
just
try
this
out
and
try
to
know
what
exactly
is
this
open
source
and
at
the
time
there
was
this
conference
that
was
happening
in
lagos?
D
D
Unfortunately,
I
didn't
get
it,
it
happened,
but
you
know
I
wasn't.
I
didn't
let
my
gut
down.
I
continued
pushing
and
think
at
some
point
I
learnt
about
the
community
bridge,
which
was
the
lfx,
so
I
I
learned
about
the
lfx
I
applied
as
well,
and
I
got
into
the
lfx
program
at
the
time
I
was
meant
to
joined
the
thanos
community
at
the
time
to
work
on
on
a
project
at
thanos.
D
So
my
experience
at
thanos
was
like
it
was
an
unbelievable
experience,
because
that
was
the
very
first
time
I
was
working
on
a
real-life
project
that
had
real-life
users
and
what
it
meant
was
that
I
had
the
opportunity
to
like
make
a
huge
impact
not
just
to
the
project
but
then
to
the
community.
So
at
the
time
it
was
a
three-month
program.
You
know
I
worked
closely
with
my
mentors.
D
We
are
super
amazing
I
mean
like
I
think
one
of,
and
I
think
I
was
to
come
to
that,
but
I
think
one
of
the
best
things
that
open
source
gives
to
you
is
they
give
you
access
to
quality
mentors.
You
know,
people
that
are
always
looking
out
for
you.
People
that
are
always
wanting
to
you
know
make
you
better
at
whatever
you
do.
Awesome.
C
My
story
is
not,
as
you
know,
interesting,
probably
because
I
started
off
wanting
to
contribute
to
you,
know
the
kubernetes
documentation
last
year
and
I
actually
did
end
up
making
a
few
documentation
edits
and
then
voila.
I
actually
discovered
that
there's
something
called
as
google
season
of
dogs,
so
a
fun
fact.
It's
I
think
my
ninth
year
in
I.t,
so
I've
passed
out
like
really
long
back
a
decade
back
almost
so.
At
that
time
there
were
no
open
source
projects
in
general
to
contribute
to.
C
So
I
recently
realized
that
I
wanted
to
start
contributing
to
open
source
understand
kubernetes
as
a
product
in
general,
and
I
somehow
stumbled
upon
across
google
season
of
talks
and
kubernetes
was
there.
As
you
know,
one
of
the
projects
that
was
listed.
So
I
approached
the
mentors
and
the
very
first
thing
that
they
asked
me
was:
are
you
a
technical
writer
like?
No?
I
just
you
know,
work
on
systems
and
I
really
like
contributing
to
documentation,
and
you
know
I
can
write
english
perfect.
B
I
mean
for
me:
I
started
with
open
source
ever
since,
like
I
was
in
my
freshman
year,
I
didn't
know
much
about
cloud
native
or
anything.
I
was
just
looking
for
projects
related
to
java,
so
I
found
red
hat
metal
there's
cuban
is
java
client
and
I
was
like
okay
I'll
start
contributing.
I
was
very
overwhelmed
because
at
first
I
only
knew
like
bit
of
java
and
maven
and
bit
of
web
development.
When
I
first
heard
about
kubernetes
and
docker
and
containers
and
stuff,
I
was
like
okay,
it's
very
overwhelming.
B
Then
I
went
to
the
issues
and
everything
it's
very.
Every
student
faces
this
when
they
look
at
a
big
project
right,
so
code
base
is
really
large
and
you
don't
understand
many
things
right
at
you
know
right
at
once.
I
think
that's
fine,
because
it's
it's
a
it's
a
long
process.
You
know
contribute
to
such
big
projects.
It's
not
going
to
happen
overnight.
You
have
to
give
it
give
it
time.
That's
when
I
realized
that
you
know
the
community
was
really
helpful,
so
it
was
all
about.
I
know
how
they
helped
me.
B
They
were
like
okay,
you
can
learn
this.
You
can
learn
that
here
are
the
resources
here,
the
good
first
issues
and
whatever
then
I
started
contributing
started
with
like
some
documentation,
some
basic
code
structure
and
then
I
started
adding
some
examples,
test
cases
and
features,
and
then
I
I
got
selected
in
google
summer
of
code
with
the
same
project.
Then
I
stayed
on
with
that
project.
I
was
then
a
google
summer
code
mentor
and
then
I
was
a
gsoc
mentor
again
last
year.
B
So
I
think
it
was
a
great
experience
and
one
thing
that
I
have
you
know
realized
from
contributing.
After
that
I
wanted
to
do
quite
a
few
projects.
Even
you
know,
outside
cncf,
so
and
inside
cncf,
as
well,
both
code
and
non-code
contributions,
for
example.
Recently
I
was
a
part
of
the
shadows
program,
which
was
great
so
non-code.
Contributions
are
also
a
great
way
to
get
involved
in
the
community
and
also
very
important
contributions,
so
make
sure
you
check
out.
We
have
a.
B
We
have
a
talk
on
that
as
well
during
this
cute
con
rocking
rocking
non-code
contributions,
but
yeah.
That's
when
I
realized
that
it's
all
about
you
know
the
community,
because
if
the
community
wasn't
there
to
help
me,
I
would
have
found
it
much
more
difficult
and
overwhelming
to
contribute.
That's
when
I
sort
of
realized
that
okay,
once
you
know
how
to
contribute,
you
can
help
others
get
started.
B
That's
when
you
started
the
channel
and
local
communities
and
student
programs
and
cncf
community,
and
so
many
other
things
ambassadors
program,
and
you
know
cnc
ambassadors.
So
I
think
these
are
great
resources
to
help
people.
The
only
thing
better
than
helping
people
is
helping
people
who
help
people.
So
I
think
yeah
that
has
been
my
journey
and
that's
what
we
are.
You
know
as
a
collectively
as
a
entire
community.
B
A
Awesome
yeah.
I
was
actually
about
to
ask
about
ask
about
your
suggestions
for
the
students
about
like
how
to
be
involved
and
and
so
on,
but
canal
has
basically
provided
a
professor
discretion
so
uchi
do
you
have
any
any
suggestions
for
for
the
prospective
students
or
prospective
mentees
would
like
to
get
started
with
the
open
source
journey
here.
D
D
But
for
me
I
would
if
I'm,
to
give
this
advice,
I
would
suggest
you
know,
try
to
apply
to
different
open
source
mentorship
programs,
for
example
gsog
lfx
altitude.
You
know
google,
summer
or
socks.
I
think
the
good
thing
about
these
different
programs
is
that
they
provide
you
with
a
structure.
You
know
for
you
to
learn
and
grow.
You
know,
as
maybe
as
a
software
engineer
or
as
a
writer.
You
know
as
depending
on
what
areas
you
definitely
have
currently
focused
on
so
yeah.
D
I
would
say:
try
and
embrace
these
different
mentorship
programs
apply
to
them
and
I
think
the
good
part
about
the
good
thing
about
some
of
these
open
source
mentorship
programs
is
that
they
are
also
paid
so
like
they
give
you
opportunity
to
like
get
stupents.
You
know,
and
all
of
that
and
secondly,
I
would
say
one
of
the
good
ways,
which
is,
of
course,
the
non-code
side
of
things.
One
of
the
good
ways
you
can
you
know
contribute
to
the
community
is
by
writing
blogs.
D
Writing
articles,
so
you
you
mustn't,
necessarily
have
to
write
code
in
order
to
contribute
to
the
community
or
contribute
to
open
source.
So
maybe
you
have
like
you
know
this
particular
tool
you've
been
hearing
about
and
you
you
want
to
contribute.
You
can
basically
just
write
an
article
about
this
particular
tool
in
one
way
or
the
other
you've
actually
impacted
to
someone
else's
life,
because
someone
would
definitely
read
that
article
or
that
blog
so
yeah,
I
would
say
mentorship
programs
and
writing
blogs
is
one
of
the
ways
you
can
contribute
to
open
source.
D
C
C
More
often
than
not,
you
are
going
to
find
it
difficult,
irrespective
of
wherever
you
are
in
your
career,
whether
you're
a
student,
whether
you're,
a
working,
professional
or
whether
you're,
even
just
taking
care
of
you're,
going
to
find
it
difficult
to
make
time
because
life
gets
in
between
and
we've
all
witnessed,
the
pandemic
over
the
past
two
years.
So
it's
going
to
get
difficult.
C
There
are
going
to
be
difficult
times,
but
one
way
to
sort
of
ensure
that
you
get
the
most
out
of
this
journey
is
to
ensure
you
put
in
your
best
efforts
set
aside
time,
maybe
just
a
couple
of
hours
every
week
it
doesn't
even
need
to
start
at
you
know
five
six
hours,
I
work
crazy
hours.
I
don't
recommend
it
to
anyone.
C
You
know:
have
your
work
speak
for
you
rather
than
you
know,
go
around.
You
know
battling
every
picking
up
every
issue
and
just
you
know
assigning
it
to
yourself,
because
you
can
put
your
hands
into
different
projects,
pick
up
multiple
issues.
All
of
that
will
give
you
exposure
and
you
probably
might
even
get
a
bit
of
visibility,
but
to
gain
your
life
experience
to
understand
the
project
and
to
help
navigate
the
ecosystem.
C
What
you
require
is
consistency,
and
you
know
you
showing
up
to
the
meetings
or
the
standups
within
slack
for
that
particular
project
or
particular
area
of
the
project
that
you're
contributing
to.
So
that's
that's
what
has
worked
for
me
and
I,
I
think,
maybe
you
know
canal
and
uche
if
you
all
have
anything
further
to.
B
I
totally
agree
with
the
point
you
mentioned,
like
the
best
way
to
get
started.
Is
you
know
just
get
started
because
you
wouldn't
know
what
is
there
unless
you
get
involved,
so
even
just
attending
the
meetings
and
just
being
active
and
listening
to
other
people?
That
is
also
a
valid.
You
know
contributions
because
you're
actually
getting
started
in
kubernetes.
You
know
sig
meetings,
for
example,
try
to
attend
one.
You
would
not
understand
anything.
Try
to
attend
the
second
one.
B
You
may
understand
something
three,
four
five
after
that
you
will
sort
of
like
understand
and
actually
get
started
with
it.
That's
actually
what
happened
with
me.
I
was
attending
the
marketing
meetings
initially
one
month
I
did
not
get
much,
but
then,
after
in
the
fifth
meeting,
people
were
like
okay.
This
is
what
you're
doing.
Would
you
like
to
help
out
or
whatever
so
yeah.
A
B
I
just
think
like
before
contributing
you
should
know
like
what
your
interests
are,
and
this
is
for
any
project
you're
contributing
to
you
should
definitely
know
what
it
does.
If
you
want
to
be
like
a
member
of
that
community
and
to
be
honest,
yeah,
I
don't
think
anyone
is
there
who
knows
like
every
single
project
of
the
cncf
landscape
in
detail,
because
there
are
a
lot,
so
the
projects
are
also
divided
into,
like
you
know,
categories
like
monitoring,
deploying
or
security
or
whatever.
B
D
A
Yeah
well
so
I
have
another
question
to
you
which,
yes,
so
you
mentioned,
that
you
had
experience
with
google's
room
of
code
and
lfx
previously
community
bridge.
So
what
are
the
best
approach
like?
When?
Are
you
selecting
when
you're
selecting
the
metronome
programs
where
you'd
like
to
participate
in?
A
So
obviously
there
are
not
so
many
mentoring
programs
that
are
offering
some
similar
opportunities
but
drive
here
and
like
what
are
the
tips
and
tricks
you'd
like
to
give
for
for
the
prospective
mentees
of
these
programs,
like
first
of
all,
how
like
which
program
to
select?
What's
what
are
the
brief
differences
between
them
and
basically
some
tips
and
tricks
for
for
those
mentees
who
are
selected?
But
they
are
not
that?
Don't
really
don't
know
what
to
do
next.
D
D
D
D
D
So
at
the
time
I
knew
nothing
about
cloud
native,
but
then
I
felt
like
you
know
this
could
be
an
opportunity
for
me
to
learn
a
new
skill
or
for
me
to
like
learn
something
entirely
different,
so
I
scanned
through
again
throughout
through
the
projects
list,
and
then
I
found
this
particular
project
on
and
I
think
it
was
basically
versioning
during
the
russian
plug-in
on
the
channels
documentation
site.
I
knew
nothing
about
this
particular
project,
but
then
it
sounded
interesting.
D
It
sounded
like
something
that
could
be
fun
and
something
that
could
have
a
lot
of
impact.
You
know
to
people
because
me,
I'm
super
driven
by
you
know
impact
you
know
if
this
had
would
have
impact
on
people.
I'll
definitely
do
that
so
and
for
me,
because
I
had
I
had
interest
in
that
particular
project.
D
I
you
know
reached
out
to
the
different
maintainers
and
I
started
you
know
doing
research
on
my
own
at
the
time
I
wasn't
selected
yet,
but
then
because
I
had
interest
in
the
project,
I
was
doing
research
on
my
own.
I
was
you
know
talking
on
the
issues
I
was
joining,
the
weekly
calls.
I
was
commenting
on
slack.
You
know
I
showed
a
lot
of
interest
in
that
particular
project
and
yeah.
I
wanted
to
use
that
project
to
you
know,
learn
the
skill
sets
around.
You
know,
building
like
a
documentation.
Plugin,
that's
like
bash
hugo.
D
You
know
a
bit
of
golang.
At
the
same
time,
I
also
wanted
to
use
that
project
to
like.
Have
it
back.
So
I
because
the
maintainers
had
seen
how
interested
I
was.
I
think
that
was
one
of
the
reasons
why
they
decided
to
give
me
the
opportunity.
Trust
me,
I
was
scared
I
mean
I
did
have.
I
had
zero
skills
when
it
comes
to.
You
know
the
different
technologies
that
were
used,
but
then
because
I
was
interested
and
because
I
was
willing
to
put
in
the
time
to
learn
and
to
work
on
that
particular
project.
D
C
C
So
it
sort
of
sets
the
baseline
from
where
you
need
to
start
from
and
honestly
it
really
helped
like.
I
know
it
would
sound,
really
horrible
if
I
say
this,
but
that
rejection
really
helped
me
because
it
just
it
made
me
realize
that
I'm
not
a
technical
writer
right.
So
how?
How
would
anybody
choose
me
if
I'm,
not
a
technical
writer
and
I'm
not
proficient
in
right?
You
know
doing
that,
but
particular
job
for
a
project.
C
It
redirected
me
into
a
better
route,
because
it
showed
me
avenues
that
I
could
explore
and
honestly,
even
when
we
were
taking
in
applications
for.
Let
me
give
us
this.
This
season
of
google
talk.
Google
season
of
talks,
we
were
looking
out
for
applicants
with
similar
sort
of
a
mindset,
because
you
you
don't
need
to
be
you
don't
need
to
be
specifically
skilled
in
one
area,
for
every
there
is
no
one
stop
shot
is
what
I
need
to
say.
C
A
Perfect,
yeah
and
canal.
I
believe
that
there
are
so
many
so
many
prospective
mentees
in
the
students
community
that
you
you
help
drive
in.
So
I
believe
you've
had
enough
conversations
with
people
who've
been
interested
in
in
a
similar
question
like
which
program
to
select
some.
Some
suggestions
like
what
to
do
next
and
so
on.
So
from
your
from
justin
point
as
a
community
leader.
So
do
you
have
any
insights
and
anything
to
share.
B
Yeah,
that's
a
good
question
and
I'd
like
to
add
on
my
answer
to
what
you
said
before,
which
I
mentioned.
He
didn't
get
selected
in
google
summer,
of
course,
for
the
very
first
time,
but
that
did
not
stop
him
from
you
know
contributing.
So
these
programs
are
great.
You
get
like
mentorship
and
you
get
some
nice.
You
know
you
get
step
in
you
get
you
get
more
streamlined
way
of
contributing
and
all
these
things,
but
it's
not
like
a
student,
cannot
contribute
to
such
open
source
projects.
B
B
So
that's
what
the
mentors
are
also
looking
for
people
who
are
actually
there,
for
you
know
open
source
stuff.
So
the
best
way
I
would
recommend
for
you
to
get
started
is
just
get
involved,
find
the
project
you
want
to
contribute
to.
Like
we
already
mentioned,
there's
so
many
projects
you
can
get
involved
in,
because
the
project
get
involved
start
solving
issues
and
complexities
of
the
issues
will
then
grow
and
get
involved.
B
A
Yeah,
it's
almost
time
for
us
to
wrap
up.
So
probably
it's
it's
the
best
way
to
spend
the
domain
in
like
two
or
three
minutes
to
to
share
the
last.
The
last
insights
and
like
the
last
suggestions
for
for
the
perspective
of
the
prospective
mentees
and
for
the
perspective,
are
contributors
to
to
the
cloud
native
platforms.
Community.
D
Yeah
sure
yeah
I
mean
like
I,
I've
always
been
saying
this
and
I'll
continue
to
say
it's
open
source
has
changed
my
life,
I
mean
like
I'm
african.
I
live
in
africa,
but
having
the
opportunity
to
work
on
software
that
impacts
millions
of
lives.
It's
it's
an
opportunity
and
it's
never
something
I
take
for
granted.
So
if
open
source
can
change,
my
life
just
know
that
it
can
change
yours
too.
D
D
One
of
the
things
I
did
very
important
was,
I
always
share
things,
I'm
learning
the
things
I'm
doing
within
the
slack
and
also
on
social
media.
You
know
I
was
on
twitter
at
the
time
anything
I'm
doing
you
know
at
the
time
we
had
this
tunnel
specified.
They
hang
out.
So
at
each
point
I
would
always
tweet
about
the
things
we
learned
every
week.
You
know
on
twitter
and
stuff
like
that.
D
I
think
you
know
if
you
want
to
succeed
within
the
open
source
space.
I
think
you
need
to
imbibe
that
culture
of
taking
responsibility
so
basically
what
it
means
is,
you
know
if
you
happen
to
join
a
community.
Try
as
much
as
possible
to
you
know,
take
a
tax
or
an
issue
and
be
responsible
for
that.
You
know
help
out
make
sure
that
you
see
it
from
start
to
finish.
A
C
C
It
was
very
intimidating
for
me
to
go
ahead
and
you
know
sort
of
approach,
people
to
understand
how
how
an
open
source
community
works
and
I'm
very
sure,
students-
and
you
know
people
who
are
professionals-
I
like
face
the
same
sort
of
you
know
fear
as
to
how
am
I
going
to
approach
that
person
or
how
am
I
going
to
speak
and
speak
at
this
meeting,
but
please
be
please
be
aware
that
there
are
no
stupid
questions.
There
are
no
stupid
on.
C
You
know
concerns
that
you
are
racing
because
everybody
started
out
as
a
beginner
right.
Nobody
came
came
into
this
world,
knowing
everything,
so
please
don't
be
intimidated.
If
you
are
looking
to
contribute,
please
just
you
know,
assess
your
skills,
and
you
know
all
these
tips
that
have
been
shared
by
the
other
panelists.
Please
use
those
tips
and
use
them
to
get
started.
That's
it
for
me.
B
B
If
you're
contributing
to
a
big
project,
big
project,
it
will
take
time
so
give
it
time
have
an
open
mind
to
learn
new
things
to
one
more
important
point:
learn
how
to
ask
good
questions
and
ask
questions
in
public,
because,
if
you
get
stuck,
then
just
join
the
mailing
list
or
slack
channel
of
the
project
or
whatever
getter
slack
whatever
they're
using
ask
your
questions
in
public.
Ask
good
questions,
and
you
know:
google
is
your
best
friend
google,
a
lot
of
things
if
you
are
not
able
to
figure
it
out.