►
Description
Making Your First Contribution to SPIRE (optional session) - Ryan Turner
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2021 Virtual from May 4–7, 2021. Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
A
Hey
everyone
yeah.
So,
as
umer
said,
I'm
brian
turner,
I'm
a
software
engineer
at
uber
and
I've
been
a
contributor
in
the
spire
project
for
a
little
over
a
year.
Now,
so
let's
go
ahead
and
get
started
so
great.
You
might
be
interested
in
making
a
contribution
to
spire
for
a
variety
of
reasons
and
maybe
you're
just
interested
in
the
project
and
are
eager
to
get
your
hands
dirty
and
learn
more
about
it
and
get
deep
into
the
code.
A
A
A
A
A
great
place
to
start
is
to
look
through
the
github
issues
and
see
if
anybody
has
reported
this
issue
in
the
past
and
if
not,
I
would
highly
recommend
that
you
go
ahead
and
create
an
issue
and
just
in
the
issue,
just
kind
of
give
a
brief
summary
of
what
it
is
that
you're
facing.
Or
you
know
what
kind
of
issue
you've
seen.
That's
something
that
maintainers
the
projects
actively
monitor
every
week.
So
we,
the
maintainers,
try
to
get
back
to
folks
who
create
issues
in
a
pretty
short
time.
A
So
and
if
you
are
just
certain
unsure
about
whether
spire
works
in
a
certain
mode
or
whether
there
is
support
for
a
specific
kind
of
environment,
a
good
place
to
start
might
be
in
the
spiffy
slack
workspace.
A
A
A
A
Once
you
kind
of
review
those
this
is
some
prereqs
for
getting
your
dev
environment
set
up
for
perspire,
so
you'll
have
to
go
through
that
this
describes
kind
of
how
you
build
the
project,
how
you
run
tests,
how
you
run
and
build
docker
images
that
you
can
use
to
test
locally.
A
There
are
also
some
conventions
explained
here
throughout
the
project
of
you
know
where
code
lives,
so
there's
been
quite
a
bit
of
code.
That's
been
added
to
spire
in
the
past
couple
years,
so
if
you're
kind
of
newer
to
the
code
base,
this
is
a
good
place
to
start
to
see
how
things
are
laid
out.
So
you
can
find
the
particular
module
or
subsystem
that
you're
looking
to
modify
or
extend
and
then
there's
a
lot
of
conventions
that
are
established
at
the
project,
just
naming
conventions,
metric
name
conventions
and
how
metrics
are
emitted.
A
A
A
So
when
you
push
your
branch
to
your
remote
fork
and
generate
this
pull
request,
you'll
get
this
template.
It
includes
this
checklist
of.
Does
this
commit
conform
to
the
contributing
guidelines?
Does
it
include
the
proper
tests
and
regression
tests
and
is
any
documentation
updated
that
needs
to
be
updated?
If
this
feature
does
not
have
any
forward-facing
documentation,
then
this
could
be
optional.
A
You'll
just
want
to
kind
of
talk
about
what
is
the
affected
functionality
and
your
change
and
then
an
overall
description
of
what
the
changes
and
then
the
maintainers
of
the
project
are
automatically
included
in
the
reviews.
So
this
is
something
maintainers
monitor
every
week
and
try
to
give
timely
feedback
on.