►
Description
Speaker: Guinevere Saenger
A
A
A
Cool,
so
this
is,
this
is
gonna
be
kind
of
more.
This
is
gonna,
be
less
of
me
talking
and
more
of
you
just
trying
out
stuff.
I
may
have
mentioned
that
we
have
a
contributor
playground
repository
in
kubernetes,
cigs
org,
and,
if
you
haven't
done
so
I
recommend
that
you
go
ahead,
and
actually
you
know
what
we're
going
to
talk
about
the
workflow
first,
so
filing
issues
is
actually
one
of
the
really
important
ways
in
which
you
can
contribute
to
the
community.
A
So
it's
it's
kind
of
this
thing,
an
open
source
where,
if
something
bothers
you
people
are
basically
gonna
say
show
what
are
you
gonna
do
about?
It
go
fix
it
and
it's
wonderful.
If
you're
in
a
position
to
do
so,
I
know
that
it's
not
everyone's
story
and
that
can
sometimes
be
frustrating,
but
that's
not
going
to
be
our
story
today.
A
A
For
for
things
like
the
things
you
want
to
file
issues
for
there's,
basically,
three
different
kinds
of
issues
did
I
miss
something
nope.
I
did
not
sorry
and
with
an
example.
If
a
bug
report,
your
first
step
is
finding
the
bug:
oh
something's,
not
working,
then
the
next
step
is
where
is
it
broken?
And
that's
basically
your
your
queue
right?
That's
the
repo
where
you
want
to
file
a
poet,
an
issue
in
and
then
you
are
going
to
create
a
complete
and
detailed
bug
report
with
the
correct
labels.
A
This
is
one
of
the
templates
in
the
project
for
filing
an
issue
and
just
you
know,
follow
the
template
instructions
as
best
as
you
can
they're,
not
the
be-all
end-all.
There's,
no,
there's
no
there's
there's
very
few
hard
and
fast
rules
here,
just
try
and
be
as
complete
as
you
can.
If
some
of
the
questions
don't
make
sense
then
skip
those,
not
all
repos
have
issue
templates,
so
there's
also
that,
but
some
of
them
do
so.
A
A
A
This
is
the
folder
in
which
we're
going
to
do
all
of
our
work.
This
is
going
to
be
more
important
later,
as
we
do.
The
poll
requests
I'm
getting
a
little
ahead
of
myself,
so
I
want
to
go
ahead
and
have
on
each
table.
I
want
to
have
two
or
three
people,
depending
on
the
size
of
your
table,
go
ahead
and
open
an
issue
on
the
contributor
playground
repository.
A
These
issues
can
be
for
right
now
they
can
just
be
a
practice
issue.
Saying
like
you
know,
hi
I,
think
I
think
the
folder
looks
you
know,
I
think
the
folder
looks
great
or
can
we
have
you
know,
think
of
something,
but
try
to
open
an
issue.
Other
possibilities
are
we
have
in
fact
you
have
an
exercises
folder
and
we
have
some
hidden
typos
in
that
folder.
So
maybe
you
can
file
an
issue
that
involves
hey,
there's
something
broken
fix.
A
A
I
already
see
a
few
labels
on
there
so
now
I
want
the
other
people,
the
ones
that
didn't
open
an
issue
on
their
table
to
find
their
table
mates
issues
and
go
ahead
and
make
comments
on
there.
I
want
the
people
who
opened
the
issue.
Try
to
assign
someone
using
this
I'm
going
to
demonstrate
right
here,
I'm
going
to
assign
Josh.
A
A
A
A
A
A
A
A
A
A
And
fantastic,
okay,
so
from
the
sounds
in
the
room
at
the
lack
of
pants
in
the
air
I
consume
I
said
everyone
opened
successfully
opened
issues
and
also
got
to
know
some
of
the
more
fun
parts
of
the
bot
automation.
It
is
time
for
the
next
part
of
this
exercise.
I
have
a
couple
more
slides.
There.
I
have
no
idea
where
that
just
went
here
we
go,
and
so
filing
issues
is
an
odd
to
be
underestimated.