►
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Panel Discussion: OSS101 - Introduction to Open Source for Students - Savitha Raghunathan, Red Hat; Joe Kutner, Salesforce; Mritunjay Sharma, JSSATE Noida; Anushka Mittal, Ramaiah Institute Of Technology
But this is such a huge Open-Source project, where to start?, "Oh, I am from a non-coding background, Open-Source is not for me", "I am fixing a typo, is this even an Open-Source Contribution?" Okay, okay - if you have any such questions in your mind and if Open-Source feels daunting to you - you are not alone. This talk aims to allay all your fears and doubts related to Open-Source. Whatever skills you have - Open-Source is open for you and this talk will help you learn how you can make your first move with any of them. From fixing a typo to designing a logo or writing a blog post, asking a question in the community, or maybe simply hosting a local-community meetup related to even a huge open-source project like Kubernetes or Helm - Open Source has a lot of doors for you to enter and this talk aims to knock a lot of them for you! This talk will make you more confident in open-source and help you understand the value of your contributions to the open-source communities.
A
A
My
name
is
avita
and
I
am
an
active
contributor
to
the
kubernetes
ecosystem
for
about
two
years
now,
and
recently
I
led
the
1.22
release
team
along
this
journey.
I
have
learned
quite
a
lot,
starting
with
my
get
improvement,
improving
my
good
skills,
making
friends
along
the
way
and
even
getting
through
the
first
rough
portion
of
the
pandemic,
all
was
possible
because
the
open
source
community
and
I'm
here
to
share
my
experiences.
I
would
like
my
fellow
panelist
joe
to
introduce
himself.
B
Hi,
I'm
joe
cuttner,
I'm
a
software
architect
at
salesforce.com,
I'm
also
the
co-founder
of
the
cloud
native
build
packs
project,
which
is
a
cncf
incubating
project,
and
that's
how
I
met
some
of
the
panelists
here
as
part
of
my
job
at
salesforce.
I
work
a
lot
with
the
open
source
community
and
I
have
for
for
many
years.
B
You
know
contributing
to
projects
steering
projects,
but
a
lot
of
it
is
also
working
with
the
people
and
with
the
community,
and
I
think
those
are
equally
important
parts
as
the
technology
and
I'm
looking
forward
to
talking
about
why
that
is
and
how
you
can
become
a
part
of
those
communities
today.
So
I'll
turn
it
over
to
tinjay.
C
Thank
you
so
much
joe
and
savita,
and
thank
you
so
much
to
all
the
viewers
who
have
joined
us
today
introducing
myself.
I
am
writing
sharma,
and
I
am
currently
in
my
final
year
and
I
am
pursuing
computer
science
engineering
in
india.
At
the
same
time,
I
think
that
it
is
because
of
open
source
only
that
I
have
got
the
software
engineering
internship
at
hackathon.
So
currently
I
am
an
intern
there,
other
than
that.
C
I
have
been
contributing
to
multiple
communities
like
communities
and,
in
fact
joe
I
met
joe,
so
one
such
community,
which
she's
the
founding
member
of
that
is
called
cloud
native,
build
tax,
so
I
was
mentally
with
him
and
google
summer
before
2021.
I
have
been
I've
been
a
cncf
intern
for
communities
as
well
in
the
spring,
and
I've
made
lot
of
lot
of
amazing
friends
from
that
community
as
well,
and
as
everybody
mentioned,
that
the
open
source
is
always
always
always
more
about
the
people.
The
people
make
the
code.
C
D
D
I've
learned
a
lot
from
the
open
source
community
as
a
software
developer
as
a
programmer
as
a
person
really-
and
here
I
am
with
my
fellow
panelists,
helping
trying
to
help
our
audience
get
started
with
their
journey.
So
let's
get
started
right.
The
first
topic
our
panel
would
like
to
address
discuss
is
why
why
should
one
do
open
source
contributions?
Why
what
would
be
the
right
motivation?
B
Sure,
I
think,
there's
a
lot
of
a
lot
of
reasons
for
for
students
both
to
grow
their
skills,
but
to
also
build
their
network.
You
know
it.
It's
also
fulfilling
right,
so
being
an
open
source
contributor
is
something
you
can
put
on
your
resume,
but
it's
also
something
that
gives
you
a
great
deal
of
satisfaction.
B
But
even
if
you
have
experience
already
it's
it's
something
that
can
sort
of
expand
the
the
scope
of
what
you
know
and
how
you
do
things
if
you've
already
been
working
with
other
developers
or
even
in
a
job,
you
learn
one
way
of
doing
something,
but
when
you're
exposed
to
the
open
source
community,
you
learn
new
processes,
new
ways
of
doing
things,
and
so
like
I
like
to
say
that
software
developers
are
perpetual
students
and
we're
always
learning
so
yeah
returns.
Idea
of
anything.
To
add
to
that.
C
Yeah
I
mean,
as
joe
mentioned
like,
we
are
all
students
right,
and
I
think
one
of
the
biggest
thing
that
I
have
learned
as
an
open
source
contributor
is
that
we
all
have
a
learn.
It
all
mindset,
and
basically
because
of
this,
there
are
various
like
people
usually
find
motivation.
I
how
to
buy
to
contribute
to
open
source,
how
to
contribute
to
open
source.
C
The
second
thing
is
that
the
kind
of
mentorship
open
source
programs
offer,
even
when
you
are
a
student-
that
is
something
that
is
you
know
something
unique,
very
unique
because
in
colleges
like
there
is
theoretical
knowledge
and
abundance.
But
when
you
need
practical
knowledge
that
are
being
used
in
the
real
world,
we
require
something
we
are
required.
Some
motivation,
as
well
as
some
programs
that
can
help
us
get
mentored.
C
A
A
A
In
addition
to
that,
there
are
few
things
that
you
will
learn
being
a
part
of
the
open
source
ecosystem
like,
for
example,
a
project
spans,
the
entire
world,
which
means
you
will
learn
how
to
collaborate,
how
to
communicate
how
to
asynchrony
asynchronously
work
with
your
peers.
These
are
really
great
skills
and
please
bear
in
mind
that
contributing
to
open
source
projects
being
a
part
of
it
is
a
no
judgement
zone,
which
means
that
you
can
start
something
small.
A
You
can
learn
along
the
way
and
it
is
okay
to
make
mistakes,
don't
be
afraid
of
them.
I
have
made
a
lot
of
mistakes.
For
example,
I
was
a
docs
lead
for
1.19
release
team
and
I
messed
up
an
entire
set
of
deadlines.
I
swapped
them
and
I
didn't
catch
it
until
the
end
and
we,
as
a
team
got
through
it.
It
taught
me
how
to
take
responsibility
for
something
that
I
clearly
missed,
and
it
helped
me
work
with
my
team
to
get
the
issue
communicator
to
the
wider
audiences.
A
So
I
have
learned
quite
a
bit
of
things
just
by
making
mistakes,
so
don't
be
afraid
of
them
and
personally,
for
me,
the
real
motivation
is
the
community.
I
get
strength
from
them
and
I
learn
a
lot.
I
learn
something
new
every
day
which
keeps
me
going.
So
that's
that's
something
that
I
want
to
add
and
I
don't
have
anything
more
to
add.
I'm
just
gonna
ask
my
friends
here.
D
B
B
You
know
that
make
that
hard,
including
imposter
syndrome
and
just
feelings
of
inadequacy,
but
you
know
when
we
asked
on
social
media.
We
asked
for
questions
for
the
panel
for
for
this
discussion
and
one
of
the
questions
that
we
got
and
actually
more
than
once
was
you
know
what,
if
the
maintainers
think
I'm
stupid
or
what?
D
Thank
you,
I
am,
I
think,
I'm
the
most
new
person
to
the
open
source
community
out
of
all
of
us
in
love
in
the
panel.
So
I
absolutely
understand
it's
just
very
recently
that
I
have
you
know,
come
out
of
my
comfort
zone
and
addressed
this
overwhelming
well
by
the
looks
of
it
overwhelming
community
code
and
you
know
open
source
softwares.
D
I
think
something.
That's
really
stuck
with
me,
something
that
joe
a
panelist
here
has
said
once
is
we
were
all
babies
once,
and
that
makes
sense,
because
you
know
it's
natural
to
make
mistakes
when
you
start
off
with
something
new,
let
it
be
anything
and
well
open
source
contributions
and
just
contributions
to
software,
as
in
general,
is
well
a
big
thing
and
you
will
have
to
start
and
you
will
make
some
mistakes.
It's
natural.
D
I
think
the
right
way
to
deal
with
this
is
to
accept
it
as
a
part
of
your
learning
learning
curve
and
get
your
hands
dirty.
Make
mistakes.
You
have
the
community
to
ask
questions
to
to
get
help
from
there's
a
lot
of
source.
There's
a
lot
of
material
available.
You
know
to
help
you
guide
you,
so,
yes,
just
accept
the
mistakes,
be
happy
start
contributing
sabitha.
Would
you
like
to
add.
D
A
To
my
heart,
because
I
have
been
there,
I
have
felt
like
an
imposter
there.
I've
tried
few
things
to
come
out
of
the
feeling
of
like
what
would
folks
think
what
what
if
this
question
is
like
not
even
a
big
deal,
it's
all!
Okay,
it's
fine
to
ask
you
can
ask
the
maintainers.
You
can
ask
in
a
project
discussion
forum,
whatever
question
that
you
have
don't
think
if
it's
gonna
be
a
silly
question.
A
A
Just
the
first
step
that
you
can
take
is
to
ask
ask
for
help,
and
there
is
nothing
wrong
in
that.
It
takes
a
bit
of
courage
and
to
even
ask
like
what
is
going
on
and
if
you
see
like
big
projects
like
kubernetes,
there
is
a
lot
of
things
going
on.
If
you
think
like
you,
want
to
know
and
learn
everything
in
one
day
or
couple
days,
it's
not
possible
at
all
start
to
make
changes
to
teach
and
start
reading.
A
Documentation
like
you
can
familiarize
yourself
or
start
attending
the
meetings
right.
So
every
communities
has
verticals
special
interest
group.
You
can
start
attending
the
meetings
and
it
is
it
is
this.
This
pattern
is
applicable
to
any
other
open
source.
Every
open
source
project
has
community
meeting
calls
they
have
their
own
discussion
forum
in
the
form
of
slack.
A
Who
would
would
be
there
to
welcome
you
and
help
you
through
the
first
few
days
of
your
journey
till
you
feel
comfortable
and
don't
forget
to
pass
it
on
right.
So
one
once
you
have
that
thing
going
on
once
you
start
contributing
once
you
feel
comfortable
written
the
favor
like
please
be
welcoming
to
the
new
contributors.
You
can
guide
them
and
also
one
other
thing
that
I
want
to
mention.
A
A
A
They
expect
the
expectation
like
okay,
wait
for
a
couple
days
or
wait
for
like
a
week
just
to
make
sure
that
you
get
the
reply
that
you
want
before
jumping
in
and
are
having
the
fear
that
oh
no
one's
responding,
which
means
that
it's
not
my
place
to
be.
I
have
read
all
those
things
and
that's
the
reason
I'm
sharing
there
might
be
so
many
things
that's
going
on.
That
is
not
in
the
control
or
also
the
control
of
everyone.
A
C
So
so
yeah
I
mean
I
totally
agree
with
savita's
last
point,
especially
like
everybody
is,
you
know
doing
it?
Quite
you
know
empathetically,
so
both
the
contributors
as
well
as
the
maintainers
everybody
have
to
give
it
towards
each
other,
and
the
another
point
that
I
wanted
to
add
like
one
of
the
most
important
points
when
we
discuss
about
imposter
syndrome
is
like
people,
you
know
are
very
afraid
of
asking
questions.
So
one
of
them.
C
I
know
I
mean
this
might
be
just
my
opinion,
but
I
feel
that
asking
questions
in
a
community
channel
in
itself
is
an
open
source
contribution.
Why?
Because,
when
you
are
asking
a
particular
question,
you
are
indicating
that
there
is
something
that
is
a
link
that
is
not
being
connected
with
a
new
beginner
and
with
the
community
documentation,
or
maybe
the
structure
process
or
something
there
is
something
that
there
is,
that
blacks
gap
between
someone
who
is
just
trying
to
begin
and
someone
who
already
knows.
B
C
Because,
usually
people
who
build
the
documentation,
they
might
think
that
this
is
quite
normal.
Person
must
be
knowing
it
while
building
those
documentation.
It
is.
It
is
very
much
possible
that
they
might
have
missed
on
some
steps
which
a
beginner
might
not
get,
and
that
is
where,
if
you
ask
a
question
in
public,
especially
in
a
public
channel,
why
I'm
saying
in
a
public
channel
because
then
not
only,
you
will
be
getting
responded
early,
because
whoever
knows
about
the
issue
they
will
reply.
C
There
is
a
learning
happening
for
everyone
in
that
community,
because
everybody
will
look
into
that
question.
Everybody
will
try
to
answer
that
question,
or
maybe
someone
another
who
is
on
offense
who
is
offensive
is
still
not
asking
the
question
they
can
have
their
question.
Get
answers
so
totally
agree
with
that
and
I
think
another
doubt
that
people
have
which
I
would
like
to
come
to
other
panelists
right
after
this
is
that,
can
I
contribute
to
open
source?
C
B
Technical,
you
know
for
coding,
but
also
marketing
and
project
management,
and
things
like
that,
so
lots
of
opportunities
to
contribute
documentation
fixes
documentation
itself.
You
know,
writing
blogs,
to
promote
the
project,
helping
organize
meetings
and
record
meetings
and
take
notes,
yeah,
creating
content
that
the
marketing
team
can
use
on
social
media.
I
can't
stress
how
many
different
possibilities
there
are.
That
said,
if
you
want
to
learn
the
language
there's
always
going
to
be,
you
know
resources
to
help.
You
do
that
too.
D
Yes,
joe,
that
was
a
really
informative
answer,
joe.
Thank
you
very
much,
so
my
first
contribution
was
to
the
korean
release
of
kubernetes,
where
I
changed
this
one
link
in
the
documentation
in
the
readme
and
even
though
back
then
it
didn't
seem
like
a
big
contribution,
because
I
just
changed
this
one.
Little
line
of
the
go
of
the
read
me
even
a
couple
of
days
later,
when
I
saw
my
name
in
the
release
and
when
I
realized
that
you
know,
there's
been
a
project
like
kubernetes
of
that.
D
Well,
that
bigger
project
going
out
with
my
name
in
the
release,
because
I
have
fixed
something
I
am
going
to
be
somehow
impacting
how
people
are
using
that
application,
that
software
right,
that
was
beautiful.
Really
that
made
me
realize
how
important
non-coding
contributions
are,
because
anybody
trying
to
familiarize
themselves
with
that
project
we'll
go
through
the
readme.
You
know
go
through
those
steps,
try
to
go
to
the
link
that
I
changed
that
I
corrected,
so
it
open.
D
Non-Coding
contributions
are
a
big
part
of
open
source
contributions,
and
you
know
to
address
what
open
source
contributions
are
they're,
just
contributions.
That's
helping
the
software
become
better
right,
become
easier
to
use
more
accurate,
just
better.
So
all
the
contributions
that
you
make
making
a
blog
to
you
know
help
someone
get
started
with
the
project
or
correction
in
a
readme.
All
of
them
are
welcome
and
just
think
about
the
impact
it's
making
thousands
of
people
using
the
software
getting
helped
by
whatever
you've
corrected
or
whatever
you
have
contributed
to
the
project.
D
A
A
So
it's
really
really
important
to
have
a
good
documentation
and
that's
a
great
place
to
get
started
with
familiarizing
the
project
and
also
like
it's
a
non-code
contribution,
and
you
don't
have
to
be
afraid.
If
you
don't
know
the
language
and
you
can
always
do
a
translation,
you
can
do
localization.
A
That
way,
you
can
help
a
set
of
people
who
don't
know
or
who
are
not
native
english
speakers,
and
they
would
want
to
understand
the
technology
and
they
would
want
to
start
on
with
their
own
native
language
and
then
move
up
the
ladder
by
learning
english
later
or
contributing
back
and
forth.
So
there's
always
opportunities
to
start
a
localization.
If
it
doesn't
exist
and
if
it
exists,
you
can
always
contribute
more
towards
it.
A
In
addition
to
that
joe
mentioned
about
marketing
any
project,
any
open
source
project
is
always
in
need
of
people
who
can
help
with
marketing
marketing.
As
unlike
even
publishing,
the
project
starts
the
number
of
new
contributors
or
the
issues
like
in
figuring
them
out
and
then
making
sure
that
it
reaches
public
in
a
consumable
way
right.
That
is
a
talent
to
present
all
the
details
and
stats.
A
A
You
can,
if
you
have
great
social
media
skills,
which
I
don't
possess
at
all
or
for
whatever
reason
that
I
cannot
be
a
social
media
person,
you
can
help
making
posts
in
twitter
or
other
official
channels
of
the
particular
project
that
you're
contributing
to
you
can
do
that.
What
else
there
is
program
management.
So,
if
you're
interested
in
program
management
project
management,
you
want
to
learn
what
it
is.
You
can
contribute
there.
You
can
do
triaging
of
issues.
A
D
A
Thanks
anushka,
I'm
gonna.
Take
you
up
on
that,
I'm
so
bad,
like
every
everything
that
I
type.
Sometimes
it
goes
into
a
wider
reach,
and
I
realize
that
there
is
a
spelling
mistake
or
there
is
like
important
thing
missing
from
the
post
and
after
I
make
it
and
it
gets
shared
multiple
times
and
I
realized
okay.
There
is
a
mistake
in
there,
and
so
it's
it's
it's
the
story
of
my
life.
A
So
moving
on
to
the
next
one,
we
have
discussed
a
little
bit
about
how
to
get
started,
how
to
overcome
the
imposter
syndrome
and
how
what
kind
of
contributions
that
you
can
do
how
to
learn
the
language.
What
language
is
right
for
me,
and
so
many
things.
The
next
question
is
more
on
the
focus
of
which
project.
How
can
I
choose
a
project
and
what
is
the
right
way
like?
A
C
Yeah,
so
I
mean
that's
a
beautiful
question
because
start
is
almost
always
the
most
difficult
thing.
You
know
the
most
difficult
thing
at
the
beginning
itself,
once
you
have
pushed
yourself
towards
the
start,
then
nothing's
stopping
you
usually
if
you
are
consistent,
so
I
have
like
from
my
personal
experiences
as
far
as
I
can
share,
or
to
the
students
or
the
folks
whom
I
know,
people
should
try
to.
First
of
all,
self-evaluate
like
what
kind
of
projects
are
they
interested
into?
C
And
you
know
I
mean
there
are
road
maps
these
days
available,
but
I
personally
feel
that
we
should
have
a
more
of
an
exploratory
journey
rather
than
a
particular
theoretical
one.
So
people
should
explore
first
of
all
like
what
is
their
interest
in
where
their,
where
interest
their
lives
and
interest
should
not
be
based
on
the
popularity
of
projects.
C
That's
my
personal
opinion
as
well,
as
I
feel
that's
important,
because
you
know
humanities
is
a
huge,
huge,
huge
open
source
project
and
a
lot
of
contributors,
but
at
the
same
time
there
are
many
other
cncf
projects
which
are
doing
amazing,
but
they
have
less
contributors
just
because
they
aren't
that
famous.
That
doesn't
mean
that
they
aren't
doing
good
or
they
are
not
making
the
community
or
the
software
world
very,
very
valuable.
C
You
will
get
the
opportunity
to
learn
a
lot
there,
so
don't
be
don't
put
yourself
in
a
particular
comfort
zone,
first
of
all,
and
try
to
explore,
try
to
self-evaluate
first
before
moving
on
to
first
your
first
open
source,
video.
That's
what
I
wanted
to
say
and
next
I
would
like
to
say,
like
my
mentor
joe,
can
add
more
to
it
because
he
has
been
my
favorite.
He
has
been
mentoring
me.
I
think
he
he
will
be
able
to
answer
it
from
the
other
side.
B
Yeah,
I
mean,
I
think
the
best
project
to
contribute
to
is
the
one
you
can
contribute
to
whether
that
means
you
understand
it
or
you're
able
to
engage
with
the
community.
So
the
only
way
you'll
figure
that
out
is
is
kind
of
by
diving
in
right,
asking
questions
which
we,
you
know,
we've
talked
about.
Why
that's?
Okay
to
do,
but
also
just
you
know,
trying
to
use
the
project.
D
I
guess
I
was
on
mute,
so
I
those
are
really
good
points.
Joe.
Thank
you
so
much.
I
think
the
only
thing
I
would
like
to
add
is
since
I
was
a
beginner-
and
I
saw
this
happening
with
me-
go
look
for
you
know
good
first
issues
or
issues
that
have
mentioned.
You
know
help
wanted
or
such
issues.
These
issues
are
usually
simpler
and
you
know
you
would
find
yourself
understanding
more
of
the
code
and
being
able
to
contribute
more
easily.
D
So,
yes,
that's
one
thing
and
the
other
being
that
we
will
be
sharing
some
resources
at
the
end
of
the
session
and
please
feel
free
to
go
check
them
out
and
find
the
projects
you
like
and
contribute
to
it.
All
projects
usually
also
have
guidelines
to
how
they
would
you
know
like
you
to
contribute,
maybe
something
specific
like
they
want.
A
signed
off
comment
comment.
D
Sorry
and
right
so
do
read
the
guidelines
having
some
basic
knowledge
of
git
github
will
help
you,
and
I
think
I
think
we
have
covered
all
the
points
here.
If
not,
please,
I
would
request
the
panel
members
to
add
something
that
they
would
like
to.
We
could
have
those
our
concluding
remarks,
as
I
believe
we
have
about
five
to
ten
minutes
of
our
session
left,
so
starting
with
savitaji.
A
So
to
add
more
to
it,
please
don't
be
a
stranger
say
hi
to
us,
and
we
would
link
our
handles
and
slack
ids
later
in
the
presentation
feel
free
to
reach
out
to
us.
If
you
have
any
questions
and
it's
okay
to
feel
overwhelmed,
it's
okay
to
feel
like
everything
that
you
feel
before
getting
started
with
something
really
big
or
like
something
out
of
your
comfort
zone.
Just
remember.
A
Take
one
step
at
a
time
and
help
us
just
to
ask
away
like
all
you
need
to
do
is
just
ask,
and
someone
will
always
be
there
to
help
in
one
way
or
the
other,
and
we
we.
We
had
a
great
discussion
I
feel
like.
But
if
you
have
follow-up
questions,
please
feel
free
to
ask
us
in
the
q,
a
or
in
the
twitter
or
in
the
slack
anywhere
that
you
feel
comfortable
with
moving
on
rich
to
joy.
C
Yeah
I
I
would
just
like
to
say
first
of
all,
thanks
to
all
the
fellow
panel
members,
because
all
of
your
point
were
you
know,
I
guess
a
learning
experience
for
me
as
well
as
for
everyone
in
the
audience
I
and
this
has
been
a
fantastic
discussion
and
we
will
definitely
like
you
all
to
connect
with
us
even
later
on.
After
this
talk,
we
are
all
here
to
help.
You
don't
forget
to
ask
your
questions.
B
D
Grateful
for
this
panel-
really,
it
gave
me
an
opportunity
to
be
here
and
you
know,
share
my
experiences.
Open
source
community
has
been
nothing
but
great
to
me,
and
I
wish
to
be
this
same
to
whoever
would
need
help
and
whoever
is
a
newcomer
to
the
community.
So
please
do
reach
out
and
we're
all
here
to
help.
Thank
you
so
much
for
being
here.
I
hope
our
panel
did
give
you
something
that
you
were
looking
for.