►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2023 in Amsterdam, The Netherlands from April 17-21. 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.
Lightning Talk: From Novice to Maintainer: Reflections on One Year of Contributing to Knative - Paul Schweigert, IBM
Ever wanted to contribute to Knative (or open source) but couldn’t quite figure out how to get started? In this session, Paul will use his experience as a relatively new contributor to Knative to draw out some helpful ways to begin getting involved with the project. This talk will cover useful topics for new contributors like getting to know the various roles on the project, how to find good issues to work on, how to make the most of the various community meetings, and some helpful tips and tricks for getting your PRs merged. The session will also cover ways for non-coders to get involved. At the conclusion of this session, someone thinking of contributing should feel confident that they can help make Knative a better project for all.
A
A
A
This
is
to
be
a
k-native
mentor,
but
someone
who
will
help
encourage
you
kind
of
as
you
get
started
in
open
source,
someone
that
knows
the
value
of
it
can
kind
of
help.
Keep
you
moving
forward
for
me.
I've
been
trying
to
work
in
open
source
for
a
long
time.
I
had
a
lot
of
fits
and
starts,
but
my
mentors
of
Martin
hickey
from
IBM,
who
kind
of
really
helped
encourage
me
to
contribute
and
keep
going
and
kind
of
solve
the
value
in
it.
A
So
something
that
I
personally
found
helpful
was
having
somebody
to
kind
of
encourage
me
along
the
way.
Number
two
actually
use
the
project.
You
know
we
all
kind
of
want
to
get.
You
know,
get
our
hands
dirty
in
the
code
kind
of
very,
very
early
on,
but
being
able
to
use
the
project
know
how
the
things
work,
build
things
I
think
also
was
very,
very
helpful.
A
I
read
the
docs
that
used
to
look
like
this
a
long
time
ago
back
when
I
joined.
They
don't
look
like
that
now,
but
you
know:
read
the
docs.
Jacques
Chester
wrote
a
really
great
book
called
k-native
in
action,
which
I
think
VMware
still
offers
for
free,
but
it's
a
really
really
great
kind
of
overview
of
kind
of
all
the
components
how
they
work
together
and
a
lot
of
other
things
and
then
I
build
things.
A
This
is
a
little
repo
I
have
it's
just
anytime
I
read
about
something
in
Canada
want
to
learn
how
it
works.
I
build
a
service,
put
it
out.
There
apply
it.
You
know
getting
your
hands
dirty,
seeing
how
they
work.
I
think
is
a
really
really
good
thing
to
do.
Number
three
clone
the
repos
build
from
Source.
If
you're
going
to
be
contributing
something
you're
going
to
do
quite
a
lot,
so
it's
good
to
kind
of
learn
how
to
do
that.
A
Early
fun
fact,
I
found
a
bug
in
Apache
spark
a
couple
of
years
ago
was
trying
to
push
the
pr
out,
couldn't
get
it
to
build
locally
lost
out
on
the
commit,
because
I
didn't
know
how
to
do
these
kinds
of
things.
So
it's
good
to
kind
of
do
that
kind
of
thing.
Early.
Here's
me
cloning.
The
repos
I've
got
there's
a
little
script.
I've
got
that
kind
of
I.
A
Can
one
line
boom,
deploy
from
Source
just
getting
that
kind
of
workflow
up
and
early
is
a
very,
very
useful
tool
to
have
documentation.
Number
four
you
know:
okay
native
can
be
a
little
complex.
You
know,
there's
these
duct
types,
there's
throttlers
and
Breakers.
There's
all
these
kinds
of
you
know
strong
components
in
there
that
can
be
kind
of
difficult
to
figure
out
what
I've
found,
particularly
when
I'm,
getting
my
feet
wet
on
a
new
project
working
on
documentation
can
be
a
nice
kind
of
easy
way
into
the
project.
It's
a
little
bit.
A
You
know,
lower
Stakes
technically,
but
still
has
meaningful.
Contributions
still
is
a
worthwhile
thing
and
still
has
people
that
want
to
help
and
particularly
kind
of
as
a
new
user
you're
learning
things.
You'll
have
a
fresh
perspective
which
can
be
helpful
here.
It
can
be
fixing
links,
it
can
be
rewriting
things.
It
can
be
noticing
that
something's
out
of
date,
all
those
are
kind
of
wonderful
ways
to
get
contributions
in,
but
again
it's
kind
of
a
little
bit
of
a
lower
technical
bar
number.
Five
attending
working
group
meetings
meet
the
leads.
A
A
So
when
I
joined
these
were
the
kind
of
the
leads
Carlos
and
Omer
were
the
documentator,
the
doc
was
it
the
Ducks
documentation,
work,
user
experience
working
group
very,
very
nice,
friendly
people
help
me,
you
know,
get
involved
kind
of,
encourage
me
and
we're
helpful
to
see
new
contributors
say
anything
to
Tops.
The
serving
working
group
leaves
Dave,
Jules
and
Marcus.
Again,
all
good
people,
but
going
to
the
weekly
meetings
was
helpful
for
them
to
get
to
know
who
I
was
to
help.
You
know
when
there's
work
comes
hey.
A
A
Volunteering
number
six.
You
know
if
there's
something
you
want
to
work
on
volunteer
for
it
when
I
first
got
started,
my
local
development
I
built
on
Mini,
Cube
and
so
I
was
setting
up.
You
know
k-native
on
minicube
and
looked
at
the
documentation,
hey,
there's
not
an
option
to
set
up
on
minicubing
here.
So
I
pushed
a
PR
out.
Here's
how
you
set
up
on
minicube
and
it
came
back.
A
Actually
we
don't
want
to
include
that
in
the
documentation,
because
we
don't
want
to
keep
you
know
every
single
you
know
install
option
up
there
documented
and
supported,
but
one
thing
we're
looking
at
doing
is:
building
a
quick
start
plug-in
so
that
you
know
people
can
come
in
hit
a
one-liner
and
have
an
up
and
functioning
local
k-native,
environment
and
so
kind
of
by
volunteering,
a
PR,
a
mini
Cube.
It
turned
into
a
stream
of
work
building
this
plug-in
that
we
still
support
and
I.
A
A
Review,
PRS
and
I've
got
review
in
quotes
here
because,
as
a
new
contributor,
no
one's
expecting
you
to
go
out
there
and
you
know
review
every
PR
that
comes
in,
but
one
thing
that
is
nice
about,
quote
unquote,
reviewing
PR's
what
I
mean
by
is
really
just
kind
of
look
at
them.
Is
that
you'll
see
where
the
code
is
being
changed?
What
impacts
something
else?
You'll
see
the
comments
that
reviewers
are
leaving
on
it.
It
helps
get
you
involved
in
the
code
base
in
a
way
that's
kind
of
low
stake,
so
here's
an
example.
A
This
is
one
where
Marcus
and
Jules
were
kind
of
going
back
and
forth
on
something
or
they
were
changing.
Readiness
Behavior,
but
kind
of
when
I
came
in
I.
You
know,
I
would
read.
Every
PR
that
came
in
I
would
look
at
it
see
what's
being
changed.
It
was
a
very,
very
helpful
way
to
get
up
to
date
on
the
code
base
without
having
to
do
a
lot
of
technical
work
myself.
Something
that
I
found
super
helpful.
A
Similarly
triage
issues
and
again
this
is
in
air
Quotes.
No
one's
asking
you
to
become
a
project
manager
for
k-native,
but
reviewing
the
PRS
that
come
in
seeing
hey.
If
it's
a
bug
can
I
reproduce
it
it's
an
issue,
can
I
reproduce
can
I
fix?
It
do
I
know
how
this
works,
if
someone's
having
a
problem
with
something
is
another
kind
of
low
stakes,
kind
of
less
technical
way
to
help
get
involved
in
the
project,
but
still
show
meaningful
contribution.
A
This
is
one
Evan
had
found
a
bug
in
I
think
in
terms
of
our
progress
deadline.
You
know
you
deploy
a
failing
revision.
It
wasn't
failing
immediately,
in
fact
here's
how
I
could
reproduce
it.
Here's
some
things
that
I
found
and
it
led
to
a
back
and
forth
in
there
so
again,
kind
of
helpful
ways
to
you
know
get
involved
without
necessarily
having
to
you
know,
write
a
thousand
line.
Pr
number
nine
pay
attention
to
the
bigger
stack.
You
know.
A
K-Native
runs
on
top
of
kubernetes,
which
runs
on
tops
of
container
runtime,
there's
a
lot
of
things
that
are
happening.
This
is
a
very
fast
moving
space.
You
know
kubernetes
releases
every
four
months,
there's
new,
there's
the
new
things
that
come
in
there's
deprecations
paying
attention.
Is
there
something
you'd
like
to
see
in
k-native?
You
know
maybe
opening
it
as
an
issue
like,
for
example,
user
name.
Spaces
is
one
that
just
came
out
in
kubernetes
125,
which
provides
a
nice
kind
of
a
you
know
a
bit
of
more
of
a
secure
sandbox
around
containers.
A
So
let's
open
an
issue
about
that
and
see
what
we
can
do
about
that
or
you
know
deprecations
horizontal
pod,
Auto
scaler
was
supposed
to
be
deprecated
in
125
I.
Don't
think
they
actually
deprecated
it
yet,
but
again,
another
way
that
you
can
show
involvement,
engagement
with
the
project
without
necessarily
having
to
write
a
ton
of
technical
code
to
get
started
with
and
the
last
one
have
fun
it's
open
source.
You
know
you
get
to
contribute
in
the
open.