►
From YouTube: Kubernetes Meet Our Contributors November 2018 Session
Description
When Slack seems like it’s going too fast, and you just need a quick answer from a human...
Meet Our Contributors gives you a monthly one-hour opportunity to ask questions about our upstream community, watch interviews with our contributors, and participate in peer code reviews.
For more information: https://github.com/kubernetes/community/blob/master/mentoring/meet-our-contributors.md
A
All
right,
hi
everyone,
my
name-
is
Harris
Pittman
I
work
at
Google
in
open-source
strategy,
specifically
on
kubernetes.
This
is
me
our
contributors.
This
is
our
second
and
last
meet
our
contributors.
Episode
of
the
day
today,
we
convene
here
on
the
first
Wednesday
of
every
month
at
two
different
times
one
in
the
morning,
one
in
the
afternoon,
and
one
is
always
a
steering
committee
AMA
and
another
is
always
a
contributor
extreme
mentor
panel.
Today
is
the
same
as
every
other
month.
A
We
have
an
awesome
panel
of
folks
on
the
line
who
are
at
different
stages
of
their
contributor
journey,
which
is
perfect
for
all
of
your
questions.
That
leads
me
to
the
next
thing
questions.
How
do
you
ask
them
in
the
meet
our
contributors?
Slack
Channel,
however,
I
get
most
of
the
questions,
direct
message
to
me.
A
Some
of
them
add
a
little
bit
of
personal
Flair
and
folks
may
not
want
to
be
public
with
that,
and
that
is
more
than
acceptable,
so
feel
free
to
DM
me,
land,
slack
or
Twitter,
and
my
handle
and
Twitter
is
paracin,
be
more
and
then.
Lastly,
we
do
have
a
code
of
conduct
that
would
include
all
of
our
panelists.
That
would
include
people
who
are
in
the
meet
our
contributor
slack
channel
TLDR.
There
is
be
excellent
to
each
other,
so
now
we'll
go
into
quick
intros.
A
D
C
Hello,
everyone
I
mark
mod
range,
I
am
a
student
from
Serbia
as
well
as
software
developer
is,
would
see.
I
am
working
with
kubernetes.
Tough.
Currently,
most
default
is
adorned,
see
past
life
cycle.
It
costs
API.
This
year,
I
was
also
google
Summer
of
Code
student,
and
today,
I
am
excited
to
be
here
on
meter
contributors.
A
E
A
E
A
All
right,
thank
you
very
much
for
joining
us
today.
Everyone
all
right
and
the
google
Summer
of
Code
was
actually
a
good
intro
into
our
first
question
and
it's
just
a
general
question
from
someone
who
wants
to
know
how
you
all
got
involved
with
kubernetes
and
that
there
are
many
open
source
projects
out
there.
So
why
contribute
to
this
one
who
wants
to
go
first.
B
Of
tectonic
about
how
how
I
could
better
contribute
to
the
community,
so
I
started
off
in,
say,
kasher,
because
I
was
working
on
tectonic,
fresher
and
and
then
from
there
I
just
kind
of
got
sucked
in
you
know
we
have
such
a
vibrant
community.
You
know
if
the
if
the
question
is
around,
why
why
contribute
to
Cooper
net
is
over
any
other
open-source
project.
I
think
that
we
have
one
of
the
best
communities,
people
like
Paris
and
or
to
kind
of
make
everything
really
smooth
for
new
contributors
that
yeah
that's
yeah.
That's
me.
C
First
project
I
worked
on
that
was
related
to
kubernetes
was
cubicle
and
it
was
I
started
on
it
last
summer
and
I
really
liked
it
kubernetes
how
it
works,
what
it
does
and
at
the
end
I.
It
ended
up
like
a
dog
community
and
how
everyone
is
good,
then
I
just
was
impressive
and
I
decided
to
see
how
can
I
get
involved
and
I
wanted
to
contribute
to
ops
in
kubernetes
and
I
found
out
that
there
is
google
Summer
of
Code
and
that
it
brings
students
to
up
research
projects
and
I.
C
Like
that
idea,
a
lot
then
decided
to
try
for
kubernetes
and
I
can
say
that
it
was
definitely
the
best
decision.
I
could
make,
because
that
3
months
of
summer
of
oddballs
also
made
I
can
learn
it
really.
A
lot
before
I
applied
for
google
Summer
of
Code
I
started
contributing,
and
the
first
thing
I
worked
on
was
some
test
case
and
like
it
was
like
wow
there
is.
C
A
E
When
there
is
a
spare,
my
job
I
don't
need
to
know
it.
For
me,
a
great
way
to
know
how
project
works
is
fighting
through
the
codes,
so
I
have
been
looking
for
opportunities
to
contribute,
and
it's
a
really
big
project
and
I
have
been
telling
people
hey.
You
know
looking
for
something.
Let
me
know
if
there
is
a
like
a
first-time
contributor
type
of
issue
and
somebody
somebody
zipping
me
and
so
I
I
contribute
liked
to
minor
things
and
I'm.
Looking.
D
So
I
got
involved
in
kubernetes,
starting
from
beat
test
infrastructure
rather
than
the
core
product
itself,
and
because
Trouw
our
CI
system
and
such
were
interesting
for
this.
The
first
thing
I
ended
up
working
on
with
kubernetes
dropper
was
actually
I,
was
working
on
our
conformance
coverage
and
how
to
measure
vats
and
fats
for
a
bizarre
series.
Events
devolved
into
doing
some
hilarious
things,
kubernetes,
dropper
and
I've
just
been
kind
of
keeping
going
working
on
tests
of
structures
like
we
met
it's
fun
very.
A
Cool
so
Marco
tell
me
a
little
bit
about
your
onboarding
process
with
API
machinery.
What
did
you
do
to
get
yourself
up
to
speed
with
everything
that
is
that
just
machine
and
all
the
just
complexity
of
it
do
you
have
any
tips
for
others
who
might
be
in
the
same
boat,
who
are
looking
to
get
more
involved
with
API
machinery
and
and
trying
to
ramp
up
quickly.
C
Can
you
help
me
with
this,
because
we
have
really
awesome
community
and
everybody
is
looking
to
help
it
to
answer
your
question
aid?
It
is
really
important
to
just
ask
ok,
I,
thought
sure
cookies
and
how
do
can
help
me
to
see
to
show
me
how
EPA
machinery
looks
like
and
where
I
can
start,
and
this
is
not
just
for
API
machinery
for
anything
you
want
to
pick
up.
C
A
What
has
been
the
most
helpful,
whether
it's
doc
or
communication,
channel,
to
to
kind
of
help
you
with
your
career
contribution
journey
so
far
and
that's
a
question
for
all
of
you
what's
been
like
one
thing
that
you've
either
found,
maybe
say
in
a
doc
in
a
repo
somewhere
where
you
had
a
moment
or
or
a
slack
channel
where
you
said
wow.
This
is
super
helpful.
Does
anything
any
of
those
ring
a
bell
for
anybody?
Any
examples
for.
C
My
case
in
the
community
repository
somewhere,
there
is
the
introduction
how
to
contribute,
and
this
these
Doc's
are
very
well
written
and
for
API
machinery
stuff.
There
is
a
document
de
explains
how
Cubana
this
API
works
like
how
to
create
an
API,
and
this
is
maybe
an
important
thing
to
started
working
with
such
stuff,
because
document
is
very
detailed
and
can
help
you
to
understand
by
API
is
made
like
that,
and
also
wanting
that
I
have
is,
if
you
are
not
sure
how
to
something
works.
C
Well,
you
can
just
try
debugging
that,
like
when
I
started,
I
was
not
sure.
Okay,
when
this
get
executed
or
hobbies
works,
but
the
tip
I
got
when
I
started
his
just
remitted
debugger
and
let
it
see
how
that
get
executed,
and
that
was
a
fine
tip
to
get
started
if
you're
not
sure
how
everything
is
fitted.
E
A
D
Theoretically,
if
our
tests
are
good,
so
I
initially
started
navigating
them
using
some
documentation,
I
afraid
a
common
where
it
is,
but
there
was
some
handy
instructions
on
how
to
get
started,
using
cube
test
to
create
a
cluster
and
run
your
tests
on
them,
and
those
instructions
are
accurate
and
we
have
been
updating
them.
So
I
know
they
are
still
accurate
and
I'll
say
it
again
started
running
them.
That
is
an
easy
way
to
go
about.
It.
D
So
the
efforts
to
figure
out
how
to
cover
them
better,
I,
think
probably
so.
What
I'm
working
on
is
the
efforts
to
figure
out
what
what
conformance
tests
we
have
and
what
conformance
tests
we
still
need
and
I
would
say,
but
probably
asking
in
again
either
SiC
testing
or
Kate's
conformance
is
probably
the
best
way
to
get
a
handle
on
that.
B
I
would
I
would
say
additionally,
there
are.
There
are
conversations
I
think
every
week,
every
other
week
in
say,
architecture
around
what
conformance
looks
like
so,
if
you're,
if
you're
curious
about
the
structure
of
conformance
for
kubernetes
or
like
what
shape
that's
supposed
to
take
in
the
future,
also
hang
out
in
sake
architecture.
Those
are
some
like
really
deep
level.
Conversations
from
the
from
the
kubernetes
elders.
A
The
elders
that
they
were
on
this
morning
on
the
steering
committee
am
a
call
good
question
actually
came
up
that
session,
that
I'd
like
to
throw
out
to
this
one
and
it
was
about
influence
and
how
you
gain
influence
and
to
a
community,
and
the
question
was
really
stemming
from
an
individual
who
has
some
kind
of
idea
and
is
currently
going
through
a
technical
dispute
and
they
feel
like
they
don't
have
enough
influence
because
they're
not
I,
guess
changing
it.
You
know
changing
whatever
they
need
to
change.
A
B
B
So,
if
you
are
unsure
of
what
you
can
be
doing,
it's
it's
stuff,
so
hang
out
and
flag
hang
out
and
hang
out
on
github
attend.
The
sig
calls
ask
questions.
Please
always
feel
free
to
ask
questions,
because
you
know
like
it
doesn't
matter
who
the
questions
coming
from
really
doesn't
write.
It
sits
as
long
as
it's
all
for
the
betterment
of
the
community,
we're
about.
B
E
Very
clear
is
to
on
the
term
knowledge
of
the
company.
She
is
the
approvers
I.
Guess
it's
very
important
to
it's
very
helpful
when
they
have.
They
know
that
people
when
I
give
continuity.
They
we
need
to
invest
time
and
coat,
and
you
know
help
those
who
are
really
showing
that
they
want
to
keep
being
involved
with
the
project
and
as
much
as
you
can
get
to
know,
people
whether
you
know
their
kubernetes
people
who
work
in
your
company
contributors.
A
Then,
what
about
the?
What
about
technical
disputes,
you
example
you
are,
you
do
not
agree
with
a
current
proposal
and
you
think
that
your
way
is
the
better
way
and
you
entered
into
a
technical
spute.
How
do
you
result?
What
are
some
of
the
steps
and
tips
that
you
give
the
folks
to
resolve
that
so
that
both
parties
come
away
with
without
I,
guess,
anger
or
bad
bad
feelings
or
emotions
or
things
along
those
lines?.
B
So
I
think
it's
really
important,
and
this
is
kind
of
like
to
echo
some
of
the
stuff
that
was
said
in
the
steering
the
steering
session
earlier.
One
I
think
Sara
says
it's
pretty
often
that
there
are
people
behind
the
keyboard
right.
So
every
decision
that
is
made
every
every
line
of
code
that
is
committed
to
kubernetes
repos
has
had.
B
Of
technical
vetting
at
some
point,
our
and
and
some
decision
around
an
API
was
made
or
around
the
way
a
test
should
be
implemented
was
made
at
some
point
right,
so
so
be
sure
that
if
you
have,
if
you
have
opinions
that
are
contrary
to
those
to
those
decisions,
that's
fine
try
to
understand
the
way
the
decisions
were
made
in
the
first
place
and
come
at
it
from
a
perspective
of
again
you're
talking
to
human
right.
So
it's
it's!
B
It's
less
about
the
technical
decisions
and
and
like
conflict
is
conflict
is
more
human
than
it
is
technical
right.
You
know
it's
like
inherently
technology
doesn't
have
conflict
right.
That's
you
right
at
a
certain
way
right,
so
so
talk
to
the
human
try
to
get
a
better
understanding
of
where
they're
coming
from,
and
you
know
in
doing
that,
you
might,
you
might
get
swayed
to
their
side
right.
So
it's
really
I
think
it's
about
having
open
and
honest
communication
throughout
the
process.
E
Yeah
I
love,
Forrester,
Stephanie,
decides
and
so
I
also
extend
on,
adds,
not
gonna,
see
something
completely
different.
Every
solution
has
a
technical
implementation
and
it's
going
to
be
one.
It
might
not
be
yours
but
anyhow
to
understand
why
not-
and
that
goes
to
these
two
who
are
lost
and
you
have
to
have
an
it-
helps
to
have
an
understanding
of
the
leadership
and
what
they
are
trying
to
accomplish
and
why
the
goals
are
short-term
and
long-term.
So
because,
if
you
you,
the
man
and
I
have
a
good
chance.
E
E
For
example,
you
might
have
an
amazing
proposal,
but
it
might
contradict
a
short-term
priority
that
the
project
has
so
that
understanding
is
crucial
to
know
why
people
at
stake
could
be
saved
to
your
proposal.
They
are
members
of
your
proposal
so,
and
it
takes
time
it
takes
a
lot
along
a
lot
of
time
to
to
know
what
the
project
the
projects
goals
are
and
how
how
people
behind
the
project
in
our
ties,
things
and
boy
placing
in
different
aspects
of
the
projects.
C
C
I
have
idea
about
that
proposal.
We
have
any
objections.
Is
there
anything
you
want
to
see
in
that
proposal
or
Congress
wanted
to
be
that
done,
because
that
is
reported
a
dead
pay?
You
can
make
sure
that
your
proposal
is
going
to
be
good.
Then
it
is
ready
for
sharing
because
Emma
debt.
Maybe
there
is
some
feedback
that
is
going
to
be
a
guys
that
proposal,
but
maybe
you
can
make
it
better.
For
the
first
time
you.
B
Yeah,
so
I'm
to
that
point
and
and
kind
of
stepping
away
from
just
strictly
technical
decisions,
don't
be
afraid
as
a
new
contributor
to
propose
a
solution.
Our
drive
forward
on
on
something
III
think
that
a
lot
of
the
times
you
will
you
will
get
support
just
for
not
necessarily
like
making
perfect
the
enemy
of
good
kind
of
situation,
where
it's
better
to
have
stuff
in
checked
into
repo
that
we
can
iterate
over
as
opposed
to
bike
shedding
over
a
PR.
For
you
know
for
months.
B
G
C
B
That
that
carries
across
all
the
communication
channels
that
we
have
so
github
slack
discuss.
You
know
the
mailing
lists.
Everything
really
write
as
well
as
a
set
of
values
that
could
rid
of
these
as
a
community
tries
to
hold
sure
right.
So
you
can
you
can
review
some
of
that
stuff
within
the
community.
B
Repo
I
would
say
the
community
repo
is
one
of
the
best
resources
they
could
possibly
have
to
review
things
for
project
and
that's
across
a
lot
of
open
source
projects
that
I've
seen
from
the
perspective
of
a
you
know
what
to
do
to
submit,
submit,
submit
PRS
or
to
talk
about
issues.
I
would
say
a
lot
of
the
repos
that
we
have
in
place.
Right
now
also
provide
issue
templates
and
PR
templates.
B
To
give
you
a
great
idea
of
how
you
need
to
structure
your
issue,
the
amounts
of
the
amount
of
labels
that
you
need
to
actually
get
an
issue
with
debt
by
someone
they're
certain
there's
certain
bot
commands
that
you
need
to
be
aware
of
that.
You
can
review
and
test
infra
and
I
mean
I
mean
overall,
it's
it.
There
is
a
there's,
a
modicum
of
documentation
read
through
that.
You
have
to
do,
and
I
would
say
that
the
community
repo
is
the
best
place
to
do
it.
A
E
Anomalous
or
in
slag
and
somebody
was
you'll,
see
a
pattern
of
people
responding
the
way
they
were
you're,
finding
weird
you're
not
effectively
pull
someone
aside
might
not
be
Depp
to
put
someone
else
aside
and
I
say
so.
I
said
this,
and
this
person
replied
with
this
and
that
sounded
odd
to
me,
because
someone's
up
in
and
maybe
they'll
say
always
because
in
arts,
these
information
that
it's
it's
available
and
people
are,
they
expect
that
from
you,
you
know
as
someone
you
might
learn
something
and
maybe
I'm.
E
A
Asked
them
for
a
follow-up
to
to
get
a
little
bit
more
specific
on
their
other
question,
so
well
in
that,
so
in
the
same
breath,
but
all
from
a
technical
perspective
from
a
github
standpoint,
lgt,
em
and
approve
catherine,
is
smiling.
He
took
because
we
do
have
regular
conversations
on
Nam
and
creature
and
what
that
word
means
exactly
it
compared
to
what
role
you
are
with
an
organization
and
for
those
that
are
that
are
listening
and
saying
what
roles?
What
does
that
mean?
A
That
is,
can
our
community
membership,
so
that
would
be
member
reviewer,
approver
sub
project
owner.
But
newcomers
see
this
language
all
the
time
when
they're
going
through
our
repos.
What
is
some
good
ways
for
folks
to
really
understand
what's
going
on
there,
so
especially
it
because
it
deals
with
our
CI
Catherine.
You
want
to
take
that
one.
How
can
folks
like
get
into
the
know
quickly
as
far
as
white?
All
of
that
good
info
is
like
what
LG
TM
is
and
provers.
D
Families
documentation
but
I
would
point
out
if
I
knew
where
it
was
but
I
don't
know
off
the
top
of
my
head
and
saying
URLs
is
far
I
guess
I
could
just
describe
the
general
upshots
yeah.
A
Yeah
and
for
those
that
are
following
Stephen
is
actually
putting
a
ton
of
links
in
the
slack
channel
for
those
that
are
following
along
and
in
going
what's
coming.
What
documentation
documentation
is
in
the
Select
channel,
thanks
Stephen,
all
right
all
right
and
then
so
on
that
same
tip
up
Stephen,
you
want
to
add
something:
yeah.
B
I
was
gonna
just
say
a
note
about
reviewers
and
approvers,
so
and
in
general,
again,
it's
people
behind
a
keyboard
right.
So
when
you
part
of
the
way
that
we
do
definitions
of
the
the
owner
files
and
owner
aliases
and
things
like
that
is
essentially
there's
a
there's,
a
hierarchy
right.
So
there
there's
a
top-level
owners
file
and
then
within
directories
there
may
or
may
not
be
additional
owners
files
right.
B
So
something
to
be
aware
of
is
that
you,
if
you
make
a
change
to
a
top-level
owners
file,
that
person
has
higher
power
over
that
over
that
repo
than
then
the
people
in
the
subsequent
and
the
and
the
lower
hangar
files
right.
So
something
to
be
aware
of
is
is
that
some
of
the
historical
kubernetes,
reviewers
and
approvers
are
in
a
lot
of
top
level
owner
files
and
they
are
their
bandwidth
short
often.
B
So
something
to
be
aware
of
is
when
you're
requesting
a
coke
review,
make
sure
that
you
are
following
some
of
the
processes
and
the
links
that
up
in
the
channel.
And
if
someone
asks
you
a
question
for
for
clarity
or
with
regards
to
the
weight,
you
implemented
a
function
or
something
try
to
try
to
answer
it
in
a
very
a
succinct
manner
so
that
when
they
come
back
to
review
it
we're,
you
know
we're
being
respectful
of
everyone's
time
involved
in
the
process.
A
And
then
also
for
those
who
are
interested
in
what
some
of
those
terms
are,
the
bots
on
the
issues
sometimes
has
links
to
like,
for
instance,
so,
label
definitions,
and
what
have
you
feel
free
to
click
on
other
people's
bot
links?
It
does
not
need
to
be
your
issue,
but
the
the
links
should
get
you
two
definitions
and
glossary,
Xand
documentation
and
things
along
those
lines
and
Carly
see
you
at
last.
E
I
was
going
to
speak,
to
was
just
stuff
and
just
say
about
it
was
its
own
expert
I'm.
The
best
PR
is
that
I
have
ever
encountered
to
review
artisans,
who
add
an
explanation
to
the
submission
for
in
sections
where
there
could
be
any
questions
or
misunderstanding
just
adds
to
the
descriptions
you
know
wow.
It
is
change
this
way
because
saves
a
lot
of
time,
because
the
person
who
is
reviewing
the
PR
might
say.
Oh
this
change.
You
know
this
is
the
way
it's
work
properly.
A
A
D
B
So
I
would,
once
you
become
part
of
the
kubernetes
org
I,
would
check
out
there's
an
there's,
an
older
email
thread
about
like
Tim
Hawkins
github
filters
for
his
email.
If
I
had
known
about
that,
why
Olivia,
once
you
start
following
certain
repos
and
and
and
checking
out
issues
and
getting
reviews
or
submitting
PRS
for
things,
there
is
a
deluge
of
email
that
comes
from
from
the
kubernetes
org
and
they
associated
words.
B
So
having
a
good
way
to
manage
that
as
well
as
your
time
as
you
get
deeper
and
deeper
into
the
project,
is,
is
really
important.
I
say
that
don't
try
to
learn
it
all.
There's
not
like
you,
you
can't
do
it.
There.
Kubernetes
is
like
two
too
wide
of
a
surface
area
at
this
point,
to
try
to
learn
and
understand
it
all.
B
So
if
you're
interested
in
contributing
I
would
say,
join
a
bunch
of
the
mailing
lists
and
hang
out
hang
out
the
mailing
list
and
see
what
excites
you
and
and
then
pick
a
sake
or
two
right
and
try
to
go
deep
in
that
cig
and
and
it
kind
of
bolster
your
status
within
that
sake
and
then
and
then,
maybe,
if
you're
interested
in
something
else,
are
there
something
that
specifically
pertains
to
work
and
kind
of
move
around,
but
definitely
start
in
one
place
and
try
to
make
meaningful
contributions.
There
first.
A
E
It's
my
internet
connection.
I
need
to
I'm
having
issues
okay.
So
when
I
had
a
chance,
what
are
you
good
now
yep
good?
There
is
a
lag
when
I
had
a
chance
to
make
a
contribution.
The
first
one
that
people
pointed
me
to
was
a
code
change
and
I
needed
to
build
communities
and
I
needed
to
tested,
because
it
was
code
related.
E
It
wasn't
just
documentation,
I
wouldn't
be
worried
about
building
cover
name
is
fredrik
mutation
change,
so
I
had
a
hard
time
building
it
and
I
wish
I
had
done
before
that
chance
to
make
a
contribution
showed
up
because
they
needed
that
change
really
fast
Eddy.
Did
you
guys
get
this
part
yeah,
so
they
got
done
cuz
and
I'm
glad
they
did.
You
know
that
I
could
have
been
repaired
a
regardless
whether
there
was
an
issue
for
me
to
work
on.
Oh
no,
so
there
was
a
I
could
have
been
one
step
ahead.
C
Just
don't
be
scared,
because
when
I
started
contributed
to
Cuban,
it
is
like
it
was
not
going
well
and
I
could
just
not
get
it
working
yet
because
I
was
applying
for
Summer
of
Code.
It
was
like,
oh
look:
how
bad
is
it
going
on?
I
will
never
get
accepted
for
this,
but
it
is
just
supported
to
stay
calm
down
and
if
you
are
starting,
it
is
totally
okay
that
if
you
not
go
well
because
kubernetes
is
complex
project
and
getting
around
stuff
takes
a
lot
of
time.
D
B
So
one
more
for
the
don't
be
scared
of
people
honestly,
I
see
occasionally
on
sick
meetings,
that
new
new
people
will
be
very
quiet,
don't
be
afraid
to
ask
questions,
don't
be
afraid
to
ask
white
like
these.
All
these
channels
for
communication
are
for
all
of
us,
not
just
for
people.
Who've
been
doing
it
for
a
while,
and
the
only
way
for
you
to
get
more
ingratiate.
It's
a
project
is
to
is
to
really
ask
those
questions
and
find
ways
to
do
stuff.
So
please
please,
please,
please.
A
B
I'd
be
remiss
if
I
don't
try
to
plug
sake
p.m.
on
every
call.
So
if
you,
if
you
have
checked
out
keps
in
the
kept
process
and
everything
that's
happening
around,
that
caps
are
essentially
the
means
that
we
write
proposals
to
improve
kubernetes
right.
So
it
stands
for
kubernetes
enhancement
proposals.
So
if
you
haven't
seen
a
cap
or
you're
interested
and
curious
about
some
of
the
changes
that
are
happening
in
the
project
definitely
check
out
the
the
caps.
C
A
B
So
p.m.
again
release
release,
testing
Doc's
contributes
great.
Those
are
it's
so
Kerber.
Nettie's
has
broken
into
this
idea
of
kind
of
like
horizontal
and
then
also
vertical
cigs
right.
So
some
vertical
cigs
examples
might
be
sakes
that
work
on
cloud
provider,
interests
so
say
cloud
provider,
say
kW,
esacash
or
seek
GCP,
and
then
there
are
horizontal
sites
which
touch
a
little
bit
of
everything
within
the
Kerberos
ecosystem.
Right
so
sake,
architecture
is
concerned
with
doing
if
you
have
refused
in
making
sure
of
of
code
and
the
repose
that
we
maintain
are
well
formed.
B
I
guess:
contra
Beck's
is
contra
bucks
spins
up
all
of
these
wonderful
opportunities
to
hear
from
contributors
sake
sake,
testing
catherine
was
speaking
quite
adept
about
SiC
testing.
Sic
testing
handles
all
the
CSE
deals:
magic
wizardry
that
happens
behind
the
scenes,
as
well
as
has
a
hand
in
some
of
the
scenes.
Yes,
infrastructure
that
we
maintain
and.
B
One
of
the
craziest
ways
you
can
contribute
and
like
this
is
only
if
you
have
how
I'm
honestly
like
it
is
a.
It
is
a
significant
time.
I
won't
say
time
suck,
but
time
commitment
is
joining
the
release
team
right.
If
you
find
a
way
to
shadow
on
the
release
team
for
a
cycle
and
eventually
take
over
as
one
of
the
leads
for
the
release
game,
that
was
a
huge
opportunity
to
to
get
to
get
a
better
understanding
of
the
way.
B
All
the
different
pieces
of
the
project
work
because
you're
you're
kind
of
an
able
to
speak
to
everyone
across
the
project,
who's
working
on
features,
who's
submitting
tests
and
tests
are
failing,
who's
doing
XYZ
winner-winner
your
Doc's
coming
in,
and
it's
like
asking
all
these
questions
and
I
found.
I
found
it
personally
to
be
a
really
great
opportunity
because
you
get
to
meet
people
or
you're
forced
to
meet
people.
B
By
way
of
kind
of
you
know,
executing
your
duties
on
releasing
like
you
have
to
you,
have
to
kind
of
reach
out
and
and
and
understand
what
people
are
working
on.
So
that
is,
if
you
have
the
time
to
contribute
to
it,
I'm
happy
to
talk
about
it
as
well,
but
I
can
drop
some
links
in
the
channel
as
well.
B
A
F
C
You're
looking
to
work
on
provisioning,
kubernetes
clusters
and
setting
up
kubernetes
and
stuff
stuff
cluster
api,
maybe
interesting
thing
to
check
out.
It
is
a
work
in
progress
project.
We
are
actively
working
on
making
it
better
and
bringing
new
features.
I
am
so
if
you're
interested
check
it
out,
I'm
actively
working
on
custom
API
provider
for
digital
ocean.
C
We
have
made
it
part
of
kubernetes
six
organization
last
week,
so
it
is
a
new
kubernetes
project
and
there's
some
good
fresh
new
interests,
and
if
you
would
like
to
work
on
setting
up
kubernetes
on
digital
ocean,
that
is
a
good
thing
to
check
out
and
you
can
always
bring
me
to
talk
about
it
or
if
you
have
questions
or
if
you
want
to
get
introduced
it.
So
there's
that.
A
D
A
E
If
you
like
to
go
into
kubernetes,
we
contribute
to
a
project
that
expands
cover.
Ladies
talk
to
me,
the
code
base
for
arc
is
very
the
way
structure.
It's
very
similar.
Thank
you.
I'm
good
I
know
it's
very
similar
to
the
way
cover
this
codes
code
base
is
structured.
The
test.
The
way
we
test
is
very
similar.
If
not
exactly
the
same.
The
coronaries
uses
us
stay
and
arc
is
going,
is
getting
a
little
traction
out
there
and
definitely
needed
in
these
a
fun
project
so
and
I'm
there
so
and
that's.
A
A
Definitely
good
plug
there
as
well.
Alright,
now
I'm
going
to
do
a
really
quick
plug,
which
is
for
contributor
experience
even
already
plug
to
that
one
of
the
activities
that
we're
working
on
that
we
help
with
is
mentoring.
That's
why
we're
all
here
right
now
we
need
scalable
mentoring
initiatives.
We
have
several
at
six
or
seven
now
that
are
in
some
kind
of
incubation
stage,
if
not
implemented
stage
already,
please
come
and
help
us
if
setting
up
mentoring
program
sounds
good
for
you.
We
have
a.
A
We
have
one
that
is
getting
brewed
up
right
now
called
the
one-on-one
hour
that
will
link
people
up
to
do
pair
programming
and
things
like
that
super
helpful,
and
this
program
itself
is
a
scalable
mentorian
initiative.
We
have
awesome
folks
on
the
line
right
now,
who
are
taking
their
time
out
to
answer
questions
that
you
would
normally
ask
a
mentor
and
that's
my
blog
for
contributor
experience
and
that
is
our
November
meet
our
contributors.