►
Description
speakers: Craig Peters and Rishit Dagli
Contributing to open-source is fun, rewarding, and full of learning but sometimes it could just get really difficult making contributions. Some projects might require you to navigate the labyrinth of setting up a very specific environment to build the project or some high-powered hardware or some test infrastructure or some super complex setup. What if this process could be made easier and faster while solving these pain points?
Enter GitHub Codespaces and .devcontainers
In this talk Rishit, a Kubernetes contributor who often uses GitHub Codespaces, and Craig, a product manager on the GitHub Codespaces team will show how they leverage cloud environments created with Codespaces to contribute to open-source CNCF projects with a special focus on using it to contribute to Kubernetes. They also demonstrate how one can leverage .devcontainers to further customize and standardize using Codespaces. The speakers not only share their personal experiences and tips to make the most out of Codespaces but also be well suited for folks new to Codespaces and demonstrate how it can be used.
Though we greatly focus on how Codespaces make contributing to Kubernetes easier the audience for this talk could also apply these insights to contribute to other open-source projects easily and faster! This talk will have useful content for new contributors, maintainer as well as seasoned contributors.
A
Hello,
I
am
Richard
and
we'll
be
talking
about
for
the
next
25
minutes,
contributing
to
kubernetes
made
easier
than
ever
with
Coach
faces.
That's
a
big
claim,
but
we
will
in
this
talk
we
will
see
how
we
can
simplify
the
process
of
contributing
to
kubernetes
and
something
that
has
worked
well
for
us.
We
have
made
a
few
peers
using
GitHub
coach
pieces
and
we'll
also
show
some
demos,
not
just
slides,
so
hello,
I
am
rishit
I'm
a
I'm,
a
student
at
the
University
of
Toronto
and
Greek.
B
Thanks
Richard
I'm,
Craig,
Peters
I
am
a
product
manager
at
GitHub
and
I
want
to
thank
Rishi
very
much
for
inviting
me
to
join
him.
For
this
talk,
I
think
my
preamble
to
this
is
that
the
topic
is
really
relevant
to
all
the
previous
topics,
because
we've
heard
a
lot
about
succession
and
the
need
for
bringing
up
new
contributors,
and
in
order
to
have
new
maintainers,
you
have
to
have
new
contributors
to
have
new
contributors.
A
Sure
so
I
most
of
you
have
contributed
to
open
source,
which
is
fun,
and
we
all
share
a
common
passion
for
open
source
where
it
has.
It
always
been
easy.
So
I
I
would
like
to
say
that
I'd
like
to
ask
a
show
of
hands
how
many
of
you
have
set
up
an
environment
to
contribute
to
you
a
project?
Probably
everyone?
Yes,
yes,
and
have
you
always
done
it
flawlessly?
A
C
A
B
A
Slack-
and
this
is
just
one
of
the
examples-
I
saw
in
slack
quite
some
time
ago,
which
motivated
me
to
look
into
Dev
containers
and
GitHub
coach
pieces
too.
So
this
is
just
something:
I
saw
in
Sig
Docs,
pretty
hard
to
set
up
the
environment
for
Sig,
docs
or
contributing
to
Sig
docs.
Not
everyone
might
feel
the
same,
but
definitely
the
case
for
a
few
systems.
A
lot
of
people
had
been
facing
problems
with
this,
even
the
original
message-
the
thread
so
this.
A
So
this
can
bar
a
lot
of
new
contributors
for
making
their
first
step
just
because
it's
pretty
difficult
to
set
up
a
working
environment,
and
so
one
other
thing
I
noticed
was
well.
This
was
actually
the
kubernetes
website
setting
up
the
environment
for
kubernetes
website,
which
is
essentially
Hugo
and
think
about
what
you
would
want
to
do.
If
you
wanted
to
build
a
KK,
that
would
be
any
webmaker
task
and
I
just
showed
some
problems.
People
were
facing
building
website.
A
B
B
Now
this
is
going
to
get
a
little
confusing
because
we
probably
will
reuse
the
dot
later
on
when
code
space
is
available
to
everyone,
because
it's
a
nice
shortcut
that
everybody
knows
and
replace
just
the
visual
studio
code
that
does
not
have
a
debugger
does
not
have
a
terminal.
It
doesn't
have
compute
behind
it.
It
just
caches
the
code
locally
in
your
vs
code
web
so
that
you
can
do
some
contributions
directly
from
the
web.
What
code
spaces
is?
Is
it
puts
compute
behind
that?
So
it's
actually
a
VM
running
a
Dev
container.
B
That
then
allows
you
to
take
advantage
of
configurations
that
are
in
the
repository.
That's
the
thing
way
over
on
the
far
right
and
that's
what
I'll
probably
spend
the
bulk
of
my
time
talking
about
today,
but
that
configuration
can
allow
you
to
have
a
specific
environment
set
up
for
working
in
a
repository
or
a
set
of
repositories,
so
that
two
things
one
is
that
you,
as
a
maintainer,
don't
spend
your
time
with
people
with
basic
setup
sets
steps
on
their
own
machines.
B
How
many
of
us
have
like
gone
through
a
review
cycle
with
people
where
they're
struggling
to
run
the
local
tests
before
moving
a
PR
from
draft
or
work
in
progress
like
raise
a
hand
yeah,
okay,
yep,
that's
time
that
actually
isn't
valuable
for
anyone?
It's
not
valuable
for
you.
It's
not
valuable
for
the
new
contributor,
that's
just
pain,
so
one
is
get
rid
of
that.
B
The
second
is,
as
a
new
contributor
I,
don't
want
to
have
to
read
through
the
readme's
on
five
different
repos
that
I
don't
know
where
they
are
I,
don't
know
which
ones
matter
for
the
particular
work
I'm
doing.
That
should
be
a
part
of
the
project
and
that
knowledge
that
know-how
is
actually
mundane.
It's
not
valuable
to
the
maintainer
and
it's
not
valuable
to
the
contributor,
and
so
the
premise
is
that
we
should
codify
that
and
that's
what
the
configuration
is
here.
B
What
that
does
then,
is
that
triggers
the
whole
chain
of
events
all
the
way
back
to
the
left,
so
I've
got
extensions,
the
terminal,
the
tools,
all
the
packages
and
dependencies
that
allow
me
to
use
the
debugger
that
allow
me
to
get
access
to
the
source
and
whatever
editor
I
want.
So
one
thing
I'll
tease
here
is
that
today
people
equate
code
spaces
and
the
editors
in
GitHub
with
vs
code
that
don't
think
of
it
anymore.
That
way.
B
Code
spaces
is
a
cloud-based
environment
that
we
are
working
to
make
sure
you
can
bring
your
own
Editor
to
we
already
support
anything.
You
can
connect
to
a
remote
container
with
via
SSH,
so
emacs.
Anybody
like
emacs
Vim
anyway,
not
too
many
people
there
I'm
a
I,
saw
a
boom
hand.
So
yes,
okay,
so
there's
at
least
a
few,
but
coming
is
much
broader
support
for
more
editors.
Come
talk
to
me
if
you're
interested
in
what
those
are
I
can't
announce
it
yet,
but
it's
coming
soon.
B
So
what
does
that
look
like
from
a
user's
perspective?
It
means
I,
go
into
a
repository.
I
get
one
click.
It's
actually
two
and
I'll
show
you
that,
but
in
theory
one
click
configuration
of
an
environment
because
we
integrate
with
DOT
files
and
things
like
that.
It
brings
all
your
favorite
shortcuts
and
aliases
and
extensions
into
the
environment.
For
you,
it
is
the
environment.
It's
actually
really
important.
B
We
GitHub
manages
it
for
you,
so
we
do
everything
from
Secrets
management
to
cost
managements
of
policies
like
timeouts
and
deletions
to
you
know,
making
sure
it's
up
and
running
that
your
your
work
has
persisted
between
sessions
and
I'll
demo.
That
too,
and
really
importantly,
really
really
importantly,
the
configuration
that
we're
talking
about
here
isn't
just
for
the
cloud
environment.
It
works
cloud
and
local,
so
you
don't
have
to
be
afraid
like
well.
What,
if
github's
down
I
can't
do
my
work?
Contributors
can't
do
their
work.
A
A
If
you
want
to
run
all
of
that
or
build
all
of
that,
and
Craig
also
has
some
nice
demos,
which
he'll
now
come
up
with
so
first
we'll
start
off
with
K
website,
which
is
which
has
shown
to
be
a
great
place
for
big
notes
to
contribute
to
so
I
thought
this
would
be
pretty
useful
to
demo,
but
you
can
also,
of
course,
try
out
the
other
configurations.
So
I
just
went
to
the
GitHub
repository
opened
up
a
code
space,
and
this
is
already
a
pre-configured
Dev
environment.
A
For
me,
the
way
I
the
way
I
do
this
is
I,
have
a
DOT
Dev
container,
which
runs
all
which
runs
all
the
installations.
I
need
to
do
so.
This
is
already
configured
with
everything.
I
need
to
do
to
build
the
website
locally
and
now
I'll
just
start
building
the
website
locally.
Oh,
could
you
zoom
in
a
bit
sure.
B
A
A
C
C
B
A
A
A
So
we
actually
got
the
change
working,
so
a
quick,
build
and
so
now
Craig
do
you
want
to
show
one
of
the
more
involved
demos
and
I
mean
you
can
feel
free
to
experiment
with
other
configurations.
We
have
there's
also
Cube
test
too.
If
you
want
to
run
that
the
python
client
and
now
create
will
show
an
interesting
demo
too.
B
Thanks
Rishi,
so
what
I'm
thinking
about
is
the
main
the
life
of
the
maintainer,
so
your
life
is
working
in
lots
of
different
repositories.
You
don't
necessarily
know
all
of
those
repositories
all
the
time,
because
you're
not
working
on
them
all
the
time,
but
as
a
maintainer,
you
often
have
to
work
across
repositories,
and
so
getting
kind
of
back
up
to
speed
and
new
stuff
is
always
a
challenge.
So
what
I
want
to
do
real
quickly
is
start
a
new
code
space
on
KK.
B
So
what
this
does
is
this
button
allows
me
to
have
a
configuration
that
says
what
kind
of
machine
do
I
want.
So
in
this
case,
KK
is
actually
pretty
big
to
build
right.
Not
everybody
even
has
a
machine,
that's
capable
of
building
it.
So
you'll
see
here.
I've
got
an
eight
core
machine.
We've
got
access
to
a
lot
of
different
kinds
of
resources.
B
But
I
could
configure
that
to
be
any
number
of
repositories
that
I
need
to
be
able
to
have
access
to,
and
then
it
brings
up
my
nice
little
getting
started
with
code
spaces
which
I
have
here,
and
what
does
that?
Do
that
allows
me
very
quickly
to
just
pick
a
command
so
to
demonstrate
the
power
of
this
like
pre-configured
environments?
This
is
a
cloud
environment.
I
can
just
copy
and
paste
a
command
have
to
allow
pasting
into
the
browser.
B
Zero
config
is
a
user
like
I
I,
don't
have
to
worry
about
what
the
versions
of
the
tools
are
and
how
does
that
work?
What's
what's
the
magic
behind
it,
the
magic
is
configuration
is
code
which
we're
all
very
familiar
with
for
cicd
for
infrastructure.
What
we're
we've
done
is
we've.
You
know.
Docker
files
have
actually
done
a
lot
towards
moving
us
towards
the
idea
of
configuration
as
code
for
all
kinds
of
environments.
We've
layered
on
top
of
that
and
open
source
spec
called
Dev
containers
development
containers
that
spec
defines
a
Json
file.
B
So
this
was
originally
a
part
of
Microsoft
Visual
Studio
code.
The
GitHub
team
has
worked
together
with
vs
code
to
extract
the
vs
code,
specific
stuff
right
out
of
it
and
create
an
abstraction
that
works
across
multiple
editors.
So
the
idea
is:
I
have
a
configuration
that
wraps
around
my
Docker
files,
my
compose
files,
whatever
I,
already
have
and
provides
the
metadata
required
to
set
up
the
entire
environment,
not
just
the
editor
itself
or
right.
So
all
of
the
dependencies.
All
the
tools
so
you'll
see
in
here
I've
got
information
about
the
docker
file.
B
So,
for
example,
there's
a
bunch
of
tests
that
you
run
when
you
run
kubernetes
tests,
the
open
ports
code
spaces
will
try
to
expose
those
ports.
Just
like
Rashid
was
demoing
and
click
on
a
browser
and
pop
that
up.
You
don't
need
to
do
that
with
this,
so
I'm
going
to
ignore
that
right,
like
that,
that's
a
whole
bunch
of
noise
that
nobody
needs
and
then
Dev
containers
have
what
are
called
Dev
container
features.
B
So
these
are
reusable
bits
and
in
this
case
I
want
to
use
Docker
and
doctor
because
kubernetes
build
requires
Docker
and
I'm
sitting
inside
a
Docker
machine.
On
top
of
a
I
mean
we're
talking
layers
on
layers,
I
need
to
go
and
I
need
a
specific
version
of
go
right
and
so
I
can
then
specify
exactly
what
those
are.
But
this
is
in
the
very
kind
of
straightforward
format.
The
only
things
that
I've
added
for
this
particular
environment
that
didn't
already
exist
and
I'm
working
in
the
community
to
make
these
more
common.
B
Our
kind,
hcd
and
Cube
test
two.
So
in
the
future,
I
want
to
talk
to
you
all
about
how
to
best
get
those
into
the
into
the
community
to
make
those
easy
and
then
yeah
I
just
have
a
customization
which
file
should
I
open
when
I
start.
So
that's
essentially
the
build
there.
I
also
have
a
repo
that
allows
you
to
do
stuff,
like
that's
more
of
the
maintainer
side
of
things.
B
I
also
have
a
repo
here
that
allows
you
to
one
click,
get
an
environment
up
and
running
for
somebody
who
just
wants
to
play
around
this
is
a
totally
different
kind
of
thing.
I
don't
need
an
eight
core
machine
just
to
run
kind
right
and
learn
a
little
bit
about
kubernetes.
So
this
gives
a
different
kind
of
playground
for
people
to
just
kick
the
tires
with
kubernetes,
learn
the
basic
tools
and
we're
working
them
with
the
community.
B
It's
to
turn
this
into
reusable
training,
and
this
is
where
I
think
we
have
an
opportunity
to
kind
of
standardize
the
workflow
around
how
new
people
come
into
the
community.
Get
simple
access
to
just
the
right
tools
with
just
the
right
configurations,
and
the
time
to
Joy
should
be
much
slower
exactly,
and
the
pain
for
maintainers
and
people
who
are
like
trying
to
help
Mentor.
The
next
generation
of
contributors
should
be
much
lower.
B
So
you
know
Rashid
of
two
years
from
now,
shouldn't
have
to
go
through
the
same
paper
sheet
two
years
ago
had
to
go
through
to
get
to
where
he
is
taking.
So
this
is
nice
because
it
just
allows
me
to
you
know:
do
stuff
like
concrete
cluster
right
away
right,
like
I.
Don't
have
to
worry
about
installing
any
of
that.
Maybe
I
don't
have
a
pre-build
on
that
one,
but
boom.
B
Let's
check
in
the
time,
I
really
want
to
have
time
for
discussion.
So
what
is
our
work
in
progress
right
now?
There
is
a
pull
request
that
you
know.
I
want
to
make
from
my
my
Fork.
So
I
have
an
issue
already
open
to
add
a
Dev
container
configuration
to
KK.
This
is
actually
being
done
in
combination
with
supertrubex
related
to
some
training
that
is
being
developed
for
new
contributors
that
will
go
on
cates.dev.
B
The
next
thing
is
I've
started
an
issue,
and
you
know
I've
started
I've
got
like
a
POC.
Basically
in
my
repo
of
the
dev
container
feature
for
kind,
I
need
to
do
the
same
thing
for
SCD
and
Cube
Test
2
and
any
other
set
of
tools
that
are
needed,
that
people
want
to
be
able
to
run
and
what
I
didn't
demo
is.
I
can
actually
run
all
the
end-to-end
tests,
all
the
integration
tests,
all
that
stuff
works
in
that
code,
space
for
the
the
Fork
that
I
have
here,
there's
a
bitly
link.
B
If
you
want
to
go
test
it
out
file
issues,
let
me
know
how
that's
going
and
then
in
the
future.
The
idea
is
that
everyone
should
have
access
to
code
spaces,
that's
actually
as
a
product
manager.
That
is
what
I'm
working
on
and
I
would
then
want
to
work
with
kubernetes
sigs
for
playground
for
cube
tests.
You
know
Sig
testing
a
bunch
of
other
communities
to
make
sure
that
you
know
if
this
is
the
right
thing
for
the
community,
that
we
get
those
things
done
and
get
some
documentation
updates
done.
A
Sounds
great
I
have
also
been
working
on.
We
already
have
an
issue
in
K
website
to
add.
Dev
container
configuration
and
GitHub
coach
pieces
I've
been
working
on
a
PR
for
that.
The
demo,
which
I
showed
today
was
kind
of
the
beer
at
the
PRN
action.
So
yeah,
that's
some
of
the
things
we
have
been
working
on
and
thank
you
so
much
for
listening
to
us.
D
B
That
depends
on
your
level
of
expertise
with
containers
going
in
my
experience
with
the
kubernetes
community
is
the
level
of
experience
is
very
high,
and
so
it
should
be
a
matter
of
hours
at
most.
It
took
me
because
I'm
all
thumbs
and
as
you
can
see
from
my
typing
I'm
more
of
a
PowerPoint
engineer
that
doesn't
show
in
my
slides
than
I
am
a
software
engineer.
B
B
It's
pretty
straightforward
and
we're
building
tooling
for
people
who,
like
there
is
already
Tooling
in
Visual
Studio
codes
extension
for
Dev
containers
to
create
those
configurations
is
kind
of
a
wizard
that
walks
you
through
the
basic
steps
and
gets
you
to
a
basic
level,
but
we're
also
building
Tooling
in
github.com
to
make
that
easier
for
new
people
too.
But
if
you're
expert
in
containers,
it's
easy.
B
C
Hi
so
I
just
had
one
question
so
in
case
we
want
our
communities
cluster
to
also
come
with
some
other
dependencies.
Pre-Installed
such
as
Helm
or
Prometheus,
so
is
it?
Will
it
be
possible
to
also
configure
that
when
we
are
setting
up
a
code
space
with
any
of
the
like,
if
you're,
choosing
kind
or
k3d
any
other
kubernetes
disturb
to
also
have
these
additional
dependencies
already
pre-installed?
Yes,.
B
The
there's
there's
actually
an
existing
Dev
container
feature
for
minicube
and
Cube
cuddle
or
cube
petal
depending
on
your
preferences,
but
that's
that
already
exists
in
the
dev
container.
Community
has
been
maintaining
that
one
of
the
things
I
want
to
work
on
is
getting
the
the
maintenance
of
these
things
actually
into
the
communities,
because
I
don't
believe
that
that
Dev
container
Community
should
be
domain
experts
in
each
of
those
tools
and
the
way
in
which
they
should
be
best
consumed
by
consuming
development
environments.