►
Description
This is our monthly livestream where Kubernetes developers share information on how to contribute to the project. For more information check this page: https://git.k8s.io/community/mentoring/meet-our-contributors.md
A
All
right
welcome
to
today's
edition
of
meet
our
contributors.
This
is
actually
our
second
session
and
it
is
a
special
session
today,
as
we
have
some
steering
committee
members
on
board
with
us
and
first
things.
First,
what
we're
gonna
do
is
go
through
some
quick
bios
of
who
these
folks
are
what
they
do
for
the
project,
but
first
rules.
If
you're
listening
out
there
on
the
library,
you
have
questions
for
us.
Please
go
to
the
meet
our
contributor
slack
channel
or
you
can
DM
me
directly
if
you
would
like
to
remain
anonymous.
A
Meet
our
contributors
as
part
of
our
mentoring
on
demand.
Series
mentoring
does
take
up
a
lot
of
time
for
both
parties,
and
this
is
a
quick
way
for
us
to
get
information
out
and
address
any
questions
or
concerns
that
the
community
might
have
first
things.
First
Thank
You
panelists
for
joining
us
today.
I'm
super
excited
to
talk
about
all
things
steering
committee
related.
My
name
is
Parris
I
work
at
Google,
I
do
kubernetes
community
things
things
with
a
quote.
A
B
C
I'm
Brendan
burns,
I
guess
I'm,
one
of
the
people
who
kicked
off
this
whole
thing
with
Craig
and
Joe
a
long
time
ago,
I've
done
I've,
worn
a
ton
of
different
hats
throughout
the
the
years
lately
been
focused
a
lot
on
governance,
as
we've
put
the
steering
committee
together
and
also
done
a
lot
of
work
on
kubernetes
client
clients
and
tools
on
top
of
kubernetes
that
allow
people
to
make
it
easier
for
people
to
develop.
On
top
when.
A
A
D
A
Stricter
before
we
get
started
to
all
of
our
listeners
that
are
participating
on
our
various
communication
platforms
with
questions,
we
do
have
a
code
of
conduct
that
is
under
the
cloud
native
compute
foundation.
Please
be
excellent
to
each
other,
no
matter
what
communication
platform
you're,
using
whether
it's
like
Twitter,
etc
and
then
same
with
our
panelists
as
well.
Please
be
excellent
to
each
other
and
think
alike.
One
more
thing:
oh
yes,
and
we
will
have
two
more
panelists
join
us
at
the
30
minute
mark.
A
D
I
think
that's
also
some
color
to
that.
The
steering
committees
made
a
bunch
of
really
busy
people
and
anything
that
isn't
covered
otherwise
find
something
else
in
the
community
rolls
up
to
the
steering
committee,
and
so
we
try
to
delegate
as
much
as
possible
to
individuals
earn
committee
that
is
not
contentious
to
just
take
care
of
or
to
other
other
states
or
or
those
things.
Yeah.
C
Consensus
means
we
try
and
get
everyone
to
agree,
but
we
assume
that
if
somebody
doesn't
say
something
they
agree,
I
think
that's
all
right.
So
that's
the
right
summary.
Basically,
it's
like
we're,
not
gonna
block,
because
consensus
consensus
in
general
can
be
very,
very
slow
as
you
try
and
get
an
explicit
yes
from
every
single
member,
and
so
the
lazy
part
of
lazy
consensus
is
that
after
a
point,
we
will
be
lazy
and
assume
that
silence
is
a
set.
A
Alright
next
question:
what's
the
difference,
what
I
actually
have
five
questions
of
this
variety?
So
this
is
a
mixture.
What's
the
difference
between
a
steak,
a
working
group,
a
sub-project
and
a
committee,
lots
of
different
group
types
if
you
will
and
the
project
and
all
of
those
groups
seem
to
call
it
some
kind
of
stir
within
the
community
of
not
knowing
like
especially
the
addition
now,
it's
the
the
terms
sub
project,
and
so
does
anybody
want
to
break
some
of
those
down,
and
you
know
I.
B
C
What
were
the
others
committee
right
and
I
think
they
don't
I,
think
there's
only
two
committees
and
that's
the
steering
committee
and
the
code
of
conduct
committee
and
I
think
that
it
was
I.
Don't
know
why
we
chose
it
actually,
but
I
guess
I
think
we
chose
it
because
it's
like
a
croc
they're,
both
cross-project
things
that
have
they
don't
really
have
to
do
with
the
details
of
organising
the
project
but
hard
to
do
with
running
the
project.
A
C
Obviously
we
have
a
meeting
and
that
takes
a
little
bit
of
time,
but
we
have
discussions
on
the
mailing
list
and
then
we
have
activities
that
we
need
to
get
done
in
terms
of
helping
organize
things
or,
like
you
know,
the
incubation
work
that
we
did
I
think
in
general,
I
feel
and
I.
Think
a
lot
of
us
feel
like
we're.
C
Actually
we're
not
moving
fast
enough
and
that's
part
of
why
we
delegate
but
like
there's
all
of
these
open
questions,
and
we
understand
that
some
of
these
things
need
to
be
answered
in
order
for
the
community
to
move
forward
and
their
people
effectively
waiting
on
the
answer.
But
we
have
trouble.
You
know
finding
the
time
to
get
a
the
answer.
A
D
Would
say
that
yeah,
the
the
steering
committee
part
takes
around
blood
print
print
inside
of
a
few
hours,
but
then
I've
been
trying
to
muster
up
more
time
and
energy
into
getting
some
of
the
things
that
we've
all
agreed
upon
need
to
be
done
done,
and
so
that's
that's.
Taking
up
quite
a
bit
more
time.
The
most
pressing
thing
recently
I
think
he's
just
kidding
all
of
the
state
charters
in
the
place-
and
this
goes
back
to
in
order
to
allocate
stuff
from
the
steering
to
made
SIG's.
D
We
have
to
have
documentation
on
what
the
Signac
Chua
Lyon
know,
what
their
responsibilities
are.
Essentially
a
job
description
and
I
think
that's
a
pretty
important
thing
to
learn
about
where
our
gaps
are
once
every
every
state
has
this
top
level
job
description,
and
that
just
takes
more
time,
because
it's
a
lot
of
cat
hurting
and
killing.
B
There's
one
thing
that
I
found
challenging
in
addition
to
the
things
already
mentioned
is
when
trying
to
come
up
with
decisions
that
are
going
to
impact
everyone
on
the
project
and
figuring
out
a
way
of
rolling
those
out
right
and
being
like
whoops.
If
that
was,
maybe
we
shouldn't
do
that
right
on
and
we're
just
trying
to
do
that
with
the
charters,
and
we
can
see
that
oftentimes.
We
don't
get
it
right
on
the
first
time
and
have
to
revisit
decisions.
A
D
So
we
essentially
have
a
backlog
of
stuff
that
has
been
going,
that
we
know
our
issues
and
then
we
kind
of
discussed
the
rough
priorities
/.
What
people
are
interested
in
working
on
and
one
pink
are
the
most
pressing
and
kind
of
divide
up
into
smaller
teams
and
go
tackle
that
this
was
worked
for
the
last
few
months,
but
I've
also
been
out
maternity
leave
for
four
months.
So
maybe
maybe
things
have
changed,
but
that
was
the
rough
process
early
in
the
year.
Yeah
mother.
C
Gonna
put
air
quotes
are
in
process
because
I
think
we
I
think
it's
much
more
yeah,
there's
a
lot
of
like
the
things
that
are
pressing
on
our
minds.
I
think
we
definitely
do
feed
all
those
urgency
around
places
where
the
community
is
blocked
right,
and
so
we
try
and
like
you
know,
try
and
hit
down
the
things
where
we
know
that
there
are
people
waiting
on
the
decision
or
where
we
can
see.
C
C
So
I
guess
another
thing
to
say,
then
in
that
context
is
if
at
any
point
anybody
in
the
community,
you
know
really
feels
like
a
chunk
of
the
community
is
blocked,
because
the
steering
community
community
hasn't
done
something.
That's
definitely
something
you
should
raise
to
us
slack
or
email
or
whatever,
wherever
you
can
reach
a
hold
of
us,
because
that's
definitely
something
you
want
prioritize,
make
sure
we're
not
in
the
way
and.
A
C
A
D
So
I
guess
the
charters,
they're
going
I
would
say,
probably
and
so
cigs
have
tried
to
put
a
charter
up
the
thing
that
I
think
we
all
realized
pretty
quickly.
Is
that
the
copy
and
paste
model
of
charters
it's
getting
really
really
hard
to
review.
We
essentially
wanted
the
outline
rough
guidelines
and
enable
the
states
to
make
adjustments.
So
what
we
found
was
that
the
rough
outlines
that
everyone
had
copied
and
pasted
actually
needed
improvement,
and
now
we
have
like
1000
requests
that
are
all
slightly
diverging.
A
A
C
Yeah
I
can
I
actually
not
sure
that
there's
anything
that
we
are
like
that,
I,
don't
think
that
we're
aware
of
and
I'm
sure
that
we
could
probably
be
moving
faster
but
like
it
comes
down
to
the
fact
that
we
have
other
jobs
and,
and
so
I'm
not
like
upset
and
I,
mean
I.
Think
we're
we're
trying
to
balance
things
especially
I.
C
A
D
So
there's
a
git
repo,
github.com,
slash
humanity,
slash
steering
and
you
can
find
the
nameless
archive
list
and
initially
backlogs
that
we're
working
against
those
issues
and
then
the
recordings
of
the
meetings
that
we
hold.
So
that's
the
best
way
to
get
a
sense
of
what's
going
on
and
where
our
heads
are
at
yeah.
D
A
C
Well,
I
think
one
of
the
big
things
when
we
saw
this
today,
actually
one
of
the
big
things
we're
struggling
with,
is
I
think
as
we
have
gotten
larger
and
higher
profile,
we're
figuring
out
our
communications
mediums
more
and
we're
seeing
more
abuse
on
our
communication
mediums
I
think
that's
something
that
you
know.
I
mean
again.
C
We
delegate
I
think
in
many
respects
to
contributor
experience
and
people
like
that
to
help
handle
it,
but
I
think
ultimately
the
responsibility
for
ensuring
that
you
know
our
forums
clean
and
things
fall
on
the
steering
committee
and
that's
something
I
think
that
we
have
been
looking
at,
but
we're
gonna
need
to
continue
to
push
on
I.
Think
as
we
go
forward
to
ensure
that
you
know
sort
of
the
broken
windows,
don't
turn
into
giant
gaping
holes.
F
C
C
F
C
Guess
the
only
thing
I
would
say
is
that
I
want
to
be
really
clear
about
the
fact
that
to
the
degree
to
which
people
are
unaware
of
what
we're
doing
or
feeling
like
it's
mysterious,
that
is
a
mistake
on
our
part
or
a
mission
on
our
part.
We
really
try
not
to
hide
things
in
any
way,
shape
or
form,
and
so
please,
let
us
know
like
it's,
not
it's
not
like
we're
trying
to
shut
people
out.
E
A
All
right
next
question
has
to
do
with
the
values
they
found
the
value
stock
inside
of
the
steering
committee
repo.
They
think
it's
awesome,
but
they
also
think
that
it
should
be
shared
across
SIG's
and
more
discoverable.
Any
plans
to
spread
this
or
encourage
SIG's
to
write
their
own
values
in
the
same
spirit,
I.
B
C
A
Put
it
on
your
backlog
at
this
point,
it's
probably
Hardy
time.
Wow,
oh
I
did
miss
a
question,
and
this
was
this
is
for
Brendan
Burns
someone
had
deemed
me.
You
made
a
statement
that
was
like
if
somebody
in
the
community
wants
to
help
write
docs.
Essentially
they
are.
Where
is
it
here?
It
is.
How
do
they
ask
the
steering
committee
to
write
a
doc
or
help
out
with
Doc's
I.
C
Guess
it
said
this
is
not
Doc's,
specifically
in
a
sense
of
like
urban
eighties
doc
because
there's
a
whole
separate
sig
associated
with
documentation.
But
this
is
things
like
you
know
the
charter
process
or
whatever
we
have
an
idea,
but
we
haven't
really
down
I,
think
you
know
probably
just
sending
a
note
to
the
steering
Aelia
saying
hey
I'm
available,
and
this
is
what
I've
done
is
probably
a
good
way
to
start
I.
Don't
think
we
have
anything
else.
C
That
way
we
know
like
I
mean
and
that's
effectively
how
like
Paris
and
George
have
gotten
involved
and
Jace
too.
For
that
matter.
Basically,
they
said
hey.
What
can
we
do
to
help
and
then
then
the
steering
committee
says
well
now
that
you
asked
you
know,
look
at
our
backlog.
Yeah
so
I
mean
yeah.
That's
another
thing
like.
C
If
you
look
at
the
backlog-
and
you
say
hey
that
looks
like
something
I'm
interested
in
like
in
many
cases
it
isn't
even
necessarily
you
know
authoring
it
as
much
as
it
is
just
collecting
a
bunch
of
ideas
from
people
and
collating
it
together.
So
you
don't
have
to
feel
like
you're
an
expert
in
this
area
or
that
you
have,
you
know,
been
empowered
to
make
the
right
decisions
in
this
area,
although
in
some
cases
actually
we
have
just
been
like.
E
A
A
E
D
Oh
so
I'm
Aaron
I
work,
Microsoft
I
spend
most
of
my
time
on
the
sick
service.
Catalog
group
there's
some
kind
of
ancillary
stuff
outside
of
the
kubernetes
commit
community
that
I
do
as
well
thats
related
to
sixers
catalog,
and
then
we
kind
of
have
some
stuff
that
we
do
ancillary
to
that
in
sick
architecture
as
well.
D
We
are
absolutely
looking
for
new
contributors
proactively,
actually
there's
a
couple
members
of
our
group
that
just
go
around
the
slack
community
coop
con
anywhere
else.
They
can
get
their
hands
on
and
actively
ask
folks
if
they
want
to
contribute.
If
you
are
a
new
contributor
and
you
want
to
take
that
initiative,
that's
amazing.
The
one
thing
I
would
say
if
you're
interested
in
getting
involved
with
Service
Catalog
come
to
our
weekly
meetings
on
Mondays
1
p.m.
Pacific.
D
E
A
C
Say
the
kubernetes
client
orgs
are
definitely
looking
for
people.
If
you
have
you
don't
even
need
deep
communities,
knowledge
really,
because
it's
all
client
libraries
on
top
stuff.
You
have
an
interest
in
a
particular
language,
and
you
want
to
see
there
be
a
community's
client
for
it
or
you
want
to
work
on
an
existing
client.
That's
a
great
place
to
get
started.
D
C
Come
all
yeah
and
in
fact,
in
that
specific
one
there's
actually
a
new
new
work
that
is
happening
to
create
a
generated,
go
client
instead
of
the
handwritten
one
to
make
one
something
that
is
way
lighter
on
the
dependency
import
front,
which
is
a
common
complaint
from
people
when
they
start
to
use
client
go
so
and
and
they're
there's
a
ton
of
work
is
it's
basically
greenfield
development
definitely
come
check
that
out.
That's
all
under
the
kubernetes
client
github
organizations
of
github.com,
slash,
kubernetes,
client.
A
Alright
and
then
the
next
question
has
to
do
with
code
reviews,
they
are
current
contributor
and
they
want
to
know
a
what
makes
a
good
reviewer
be
how
they
can
like.
How
do
they
have
the
conversation
about
being
a
reviewer
and
then
see
I
guess,
let's
just
start
with
those
know,
we'll
work
from
there.
E
Or
how
can
they
make
something
better
things
like
that
and
after
you
have
demonstrated
that
you
have
rebuked
reviewed,
a
bunch
of
code
and
you're
at
the
core
reviewer
of
several
different
PRS
for
a
specific
code
base,
and
you
can
I
think
you
can
ask
the
curl
reviewer
to
vote
and
to
vote,
for.
You
can
propose
that
you
want
to
be
the
reviewer
and
they
can
vote
a
plus
one
to
support.
You.
D
Yeah
we
do
something
pretty
similar
generally
in
service
catalog.
We
definitely
look
for
some
expertise
and
at
least
one
sort
of
specific
part
of
our
code
base,
but
we
place
a
lot
of
emphasis
on
having
reviewed
a
lot
of
code
and
being
able
to
show
it.
You
can
communicate
what
you
want
change.
What
your
opinions
are,
that
you
can
debate
in
a
civil
manner
as
well.
It's
pretty
important
to
me
specifically
as
well
and
then
in
our
Charter
I
think
this
is
something
that's
kind
of
encouraged
in
other
sig
charters
as
well.
D
A
A
D
So
right
now
we're
in
this
position
where
we
definitely
have
a
shortage.
We
have
actually
we
have
a
shortage
of
contributors
in
one
specific
area
in
Service
Catalog.
So
it's
kind
of
similar
what
I
said
before
we're
actively
going
out
into
the
community
and
asking
folks
hey:
are
you
interested
in
Service,
Catalog,
Ebro,
curry
kinds
of
things
and
getting
them
involved
with
sort
of
a
good
first
issue
kind
of
thing?
D
E
C
E
Close
though
ozs
and
were
close,
most
people
in
see
gaps,
they
can
have
their
own
different
tools
like
compose
or,
and
those
doesn't
need
to
go
through
communities,
approver
or
reviewer
process.
If
you
have
your
own
project,
you
want
to
showcase
demonstrated
in
the
sea
caps
meeting,
and
you
are
welcome
to
do
that
and
we
can
put
on
those
projects
in
to
see
caps.
A
E
G
D
Yeah,
sorry
yeah,
maybe
I,
don't
know,
maybe
five
years,
whatever
I
kind
of
discovered
docker
I
thought
it
was
really
cool.
Cuz
I
was
tired
of
waiting
for
VM
to
spin
up
and
using
packer
to
wait,
30
minutes
to
create
a
at
the
time
it
was
an
AMI
Creedy
Asher,
don't
tell
anyone
so
docker
containers
were
cool,
I
thought.
You
know
this
is
gonna,
be
a
thing.
D
C
D
Away
etc
so
I
kind
of
stumbled
on
kubernetes.
It
was
a
gke
style.
Kind
of
thing
didn't
seem
like
it
was
more
than
just
a
Google
project
at
the
time,
but
I
kind
of
saw
it
was
gonna,
be
because
it
was
a
really
good
idea,
so
I
started
playing
around
with
it.
I
think
the
first
thing
I
saw
was
the
replication
controller,
and
that
was
when
I
was
kind
of
sold,
because
it
did
all
the
things
that
I
wanted
to
do
for
me,
kept
containers,
running,
etc.
C
D
I
asked
why
I
couldn't
scale
up
a
replication
controller
in
some
certain
situation,
don't
remember
what
it
was
and
then,
after
that,
I
kind
of
just
fell
into
it
as
a
full-time
gig.
Honestly,
the
first
thing
I
did
was
building
a
pass
on
top
of
kubernetes
and
then,
after
that,
that
kind
of
a
couple
years
later,
I
kind
of
just
got
involved
with
hooking
up
kubernetes
two
brokers
and
having
kind
of
external
services
be
more
native
inside
of
kubernetes,
and
that's
where
I
kind
of
joined
the
cig.
D
G
D
I
had
about
five
years
ago,
it's
six
years
ago,
my
friend
and
co-founder
of
coral
s,
Alex
and
I
had
been
working
for
a
long
time
and
system
software
and
we'd
spent
a
lot
of
effort.
Every
time
we
wanted
to
get
something
running
provisioning
the
servers
installing
the
operating
systems,
keeping
the
operating
systems
up
to
date,
all
this
stuff.
C
It
might
have
actually
been
Joe
chose
it
CD
I,
can't
remember,
it
was
kind
of
a
consensus
decision.
I
think
we
just
sort
of
had
seen
it
in
it,
but
I
guess
I
can
say
why
I
am
why
I
was
interested
in
it.
I
was
really
interested
in
this
thing,
because
I
really
feel
strongly
I
mean
it's
echoed
and
other
people
said,
but
the
task
of
building
these
systems
is
just
too
hard.
It's
too
complicated.
We
do
the
same
things
over
and
over
and
over
again.
We
never
really.
C
You
know
computing
is
all
about
building
abstractions
and
we
weren't
building
abstractions,
really
in
this
space,
and
so
suddenly
with
docker
containers.
We
had
the
ability
to
go
and
build
some
new
abstractions
and
really
enable
and
empower
people
in
ways
that
hadn't
existed
before
in
the
cloud
and
and
so
that
was
sort
of
the
motivation
for
getting
that's
starting
the
whole
thing
and
then
building
the
community
was
always
a
goal
from
the
get-go
like
I
knew.
We
would
only
be
successful
if
we
had
a
really
strong
ecosystem
and
a
really
strong
community
and
I.
C
A
D
It's
an
acronym
stands
for
special
and
literally
no
I
mean
that's
true.
I
actually
do
view
it.
Quite
literally
though
it
is.
A
working
group
in
the
criminales
community
is
a
little
bit
of
a
loaded
term,
but
it
is
a
group
of
folks,
a
fluid
group
of
folks
people
can
come
and
go
that
are
interested
in
one
special
area.
One
specific
area
of
kubernetes,
the
technology
and
we've
seen
them
be
very,
very
specific.
We've
seen
them
be
very
general
and
we've
seen
them
grow
from
one
to
the
other,
and
it
can
go
either
way
right.
D
So
the
part
that
I've
been
most
interested
in
and
most
kind
of
astounded
by
actually
is
how
fast
these
things
can
grow
from
like
in
a
matter
of
weeks,
from
an
idea
to
you
know
fully
functioning
sig
that
is
kind
of
presiding
over
working
software,
that
is
in
master
of
the
core,
or
that
is
a
big
part
of
the
ecosystem
along
side
of
the
core,
and
so
the
way
that
I
see.
It
is
really
just
this
group
of
folks
kind
of
a
birds
of
a
feather
that
come
together
and
they
grow.
E
A
Spurred
another
question:
that's
sort
of
related
to
steering
committee,
so
both
B's
listen
up
to
this
one.
What's
the
state
of
working
groups
today,
it
says
that
they're
temporary,
but
it
looks
like
some
of
these
working
groups
have
been
around
for
a
long
time.
Do
they
have
charters
and
what's
the
deal
there
well.
C
In
general,
a
working
group
is
supposed
to
have
a
concrete
outcome
right,
like
it's
supposed
to
have
something
that
it
is
driving
towards,
and
once
that
is
done,
it
ceases
to
exist.
Some
of
those
outcomes
are
perhaps
a
little
more
nebulous
or
longer
term
than
others.
What's
a
little
working
group
survive
for
a
while
I,
don't
know
that
we've
really
come
up
with.
Like
a
you
know,
I,
you
know
you
must
be
done
with
your
work
by
this
period
and
I'm,
not
sure
that
we
should
I.
C
A
George
has
made
a
sign
for
his
meeting.
Salford
4
plus
1,
so
I've
been
actually
thinking
about
making
actual
schwag
of
those
and
passing
them
out,
but
we
haven't
gotten
that
far.
Yet,
if
you,
the
next
question,
is
from
a
current
contributor,
if
you
had
one
bit
of
advice
to
give
to
a
current
contributor,
something
that
you
either
think
is
a
great
resource
and
underutilized
resource
or
anything
else.
What
would
it
be.
D
The
first
one
I
think
is
right:
Doc's
they're
the
most
appreciated,
and
maybe
one
of
the
least
contributed
things
in,
at
least
in
the
areas
that
I
work
and
the
other
one
is.
If
you
can
go
to
meetups
conferences,
etc,
sort
of
the
hallway
track
air
quotes.
If
you
will
that's
just
a
great
resource
to
just
talk
to
people
doesn't
even
have
to
be
technical,
but
just
having
that
connection
next
time
you
talk
to
them
on
slack
or
go
to
a
cig,
weekly
meeting
or
whatever
it
is
in
sort
of
the
virtual
space.
E
Janet,
what
about
you
and
I
would
+1
on
whatever
it
said
and
also
think,
and
a
lot
of
people
are
posting
great
on
tutorials
or
blog
post,
and
you
can
just
search
for
them
or
you
can
follow
some
kubernetes
people
on
twitter
and
they'll
post
those
things
and
you
can
know
which
articles
to
look
at
and
those
are
great
resources
and
also
there
I
believe
there
are
many
local
meetups
everywhere
from
kubernetes.
So
if
you
can
join
those
meetups
and
meet
the
people
who
are
interested
in
kubernetes,
that
would
help
as
well.
A
C
I
would
say
you
can
always
achieve
more
than
you
think
you
can
alright
I
think
that
any
time
we've
run
into
people
who
think
that,
like
the
camps
like
that,
the
community,
if
they
don't
have
enough
experience
or
they
don't
have
enough,
you
know
whatever
to
do
a
particular
thing.
I,
don't
think
that's
ever
really
true,
except
for
in
some
very
specialized
areas.
D
Yeah
I
would
say
that
we
have
we've.
We
have
a
lot
of
great
contributor
Doc's
that
people
can
read
through,
but
also
also
a
lot
of
them
are
out-of-date
and
incomplete,
so
use
them
as
a
rough
guide,
and
then
please
jump
in
and
ask
questions.
Most
people
would
be
helpful.
I
can
at
least
give
you
some
framework
to
start
from.
Yes,.
A
I'm
also
going
to
+12
that,
for
selfish
reasons,
being
contributor
experience,
just
a
quick
story
for
those
who
don't
know,
we
had
a
contributor
last
fall.
Who
said
that
her
contributor
guide
was
not
great
I
think
there
was
other
words
in
there,
but
she
completely
revamped
the
contributor
guide
that
we
have
today,
along
with
George
and
many
other
volunteers.
So
that
is
a
great
way
to
not
only
get
involved,
but
stay
involved
with
committees.
A
Itself
is
the
contribution
process
and
we
are
actively
looking
for
other
contributors
to
work
on
the
developer
guide
to
that,
and
that
is
a
lot
of
very
out
very
out
of
date,
information
that
was
community
driven
at
some
point.
So
please
does
a
contributor
experience
slot
channel
if
you'd
like
to
help
out
with
any
of
the
above,
but
that's
it
for
time
and
I.
Just
looked
at
questions
and
I
think
I'm
good
with
my
direct
messages
and
I'm
good
with
direct
messages
on
Twitter.
So
let's
just
go
ahead
and
wrap
this
session.
A
Thank
you
so
much
to
all
of
you
for
joining
us.
Erin
Janet
Brendon
Brendon
both
of
the
bees
and
it's
been
a
great
session
thanks
again,
I
know
your
time
is
super
valuable,
so
I
know
everybody
greatly
appreciates
it.
This
recording
will
be
live
on
YouTube
later
and
feel
free
to
to
star
this.
As
a
playlist,
we
have
made
our
contributors
as
a
playlist
all
right.
Thank
you
very
much
and
see
you
next
month,
everyone
first
Wednesday
of
the
month,
except
for
this.
This
month
we
did
the
second
because
of
the
u.s.