►
From YouTube: SIG Contributor Experience Meeting 20180919
Description
Developing and sustaining a healthy community of contributors is critical to scaling the project and growing the ecosystem. We need to ensure our contributors are happy and productive, and that there are not bottlenecks hindering the project in, for example: feature velocity, community scaling, pull request latency, and absolute numbers of open pull requests and open issues.
Join us: https://github.com/kubernetes/community/tree/master/sig-contributor-experience
A
A
D
A
C
So
they,
the
kind
of
goal,
is
that
people
who
are
taking
part
and
had
to
profess
they
have
to
make
five
contributions
to
any
open
source
project
on
github
and
then
their
contributions
are
tracked
and
if
they
make
five
contributions
across
the
month
and
they
get
a
free
t-shirt,
it's
kind
of
a
nice,
a
nice
little
initiative
in
order
to
increase
people
getting
involved
with
open
source.
So
I
thought
it
might
be
something
that
the
coronaries
project
would
like
to
get
involved
with.
We.
C
Actually,
we
don't
actually
have
to
do
anything
to
get
involved
with
it
any
it's
kind
of
down
to
the
people
taking
part
to
decide
which
projects
they
want
to
contribute
to
and
any
kind
of
public
contribution
on.
Github
just
gets
counted
towards
that,
and
but
there
are
a
couple
of
things
that
we
could
do
to
help
smooth
the
process.
C
C
A
C
It's
the
way
that
they,
they
list
kind
of
things
that
you
can
get
involved
with
on
their
website.
Is
you
there's
like
Hector
professed
and
issue
labels,
so
you
add
Hector
professed
as
an
issue
label
to
anything
that
you
think
would
be
suitable
and
then
I
think
it
like
comes
up
on
the
website
or
they're
the
people
who
are
taking
part
an
actor
professor
told
to
search
for
that
label
specifically.
So
if
you
wanted
to
kind
of
advertise
as
hey,
you
know
we're
involved
with
Oktoberfest
if
you're
interested
and
you're
going
for
Oktoberfest.
C
A
F
I've
seen
previously
with
hecto
Rusk
has
been
going
for
a
few
years
now
is
they
will
highlight
issues
that
have
label,
but
the
general
idea
participation
is
that
it's
just
getting
me
people
involved
in
open
source
period
and
like
they
will
any
any
repo
that
is
like
that?
Doesn't
you
can
explicitly
opt
out,
but
any
repo
that
doesn't
opt
out
is
eligible
for
for
participating.
F
If
it's
like
a
public
open
source
repo
on
github,
we
we
do
have
good
first
issue
stuff,
we
it
might
be
worth
looking
and
and
highlighting
and
adding
that
the
problem
is
the
way
our
permission
set
is
laid
out.
There's
only
certain
people
who'd
be
able
to
manually,
add,
and
otherwise
we
need
to
create
automation
to
be
able
to
apply
the
label.
I,
don't
know
that
we
necessarily
have
cycles
to
do
that.
F
To
add
all
the
automation
pieces
just
for
like
a
first
month
thing
but
like
yeah,
air
air
is
kind
of
suggested,
we're
at
where
I
will
just
go
in
with
us
like.
Maybe
we
could
even
tie
it
in
with
the
good
first
issue
plug-in
to
like
also
add
that
label
as
well,
and
then,
when
Oktoberfest
is
done,
we
just
retire.
The
label.
A
F
A
I'm
kind
of
leaning
toward
cons,
I
feel
like
making
labels
for
events
is
like
I,
don't
know
like
I
feel,
like
I'm
a
hacked
oversight
or
wherever
we
start
wherever
we
announce
this,
we
just
linked
to
the
good
first
issues,
labels
right
and
then
like
I,
feel
like
using
a
label
as
a
symlink.
It's
a
temporary
send
link.
I,
don't
know,
is
that
fine
I
mean
I,
don't
know
if
we
have
the
you
know
in
cycles
being
Christophe
spare
time
like.
If,
if
we
want
to
do
that
or
if
we
just
want
to.
G
G
I
have
a
question
for
Tim,
and
now
me
you're
I,
know
in
previous
installations
of
Oktoberfest
you
had
featured
projects.
Is
that
something
you're
gonna
do
this
year
as
well?
I
can't
find
any
any
documentation
on
your
site
regarding
the
label
where,
like
how
what
type
of
issues
we
should
add
there
or
how
to
do
it,
I
can't
find
anything
right
now.
Do
you
have
a
link
to
that
documentation?
So
we
can
just
take
a
look
at
that
yeah.
C
Yeah,
so
I
think
we
just
thought
it
would
be
a
kind
of
cool
thing
to
potentially
do,
but
we
actually
know
very
little
about
like
exactly
have.
We
need
to
get
involved
so
really
wanted
to
put
in
front
of
people
and
something
to
look
at
okay,
yes,
answer
like
documentation,
I
have
no
idea.
Sorry,
this
baby.
A
D
That
would
be
considered
fine,
so
they
don't
heavily
track
any
sort
of
abuse
of
the
system
unless
you
like,
create
an
account
and
then
create
a
new
repo
in
your
own
account
and
do
five
random
commits.
They
might
be
able
to
track
that.
If
you
do
that
on
stale
repos,
they
generally
won't
police
that
at
all,
okay,
my.
A
Concern
there
is
because
we
do
have
a
trivial,
a
trivial
content.
Edit
policy
like
we
don't
want
pull
requests
from
people's
fixing
one
sentence.
However,
the
policy
basically
says:
if
you're
gonna
touch
that
file,
give
it
a
once-over
to
check
for
all
fours.
You
know,
can
part
of
it
be
rewritten
all
that
kind
of
stuff
I'm,
just
cognizant
of
absenting,
because
I
have
had
like
real
complaints
from
developers
that
are
like
some
of
these,
but
like
in
the
community.
Repo
and
I'm
kind
of
handling
I'll
see
one
and
I'll.
A
F
If
somebody's
make
like
honestly
so
five
trivial
pull
requests,
it's
not
not
that
big
a
deal
it's
when
people
make
large
numbers
to
game
the
system
in
some
way
that
we
end
up,
pushing
back
and
say:
hey,
can
you
combine
these
like
15
pull
requests
into
one?
Please
do
that
and
we
have
done
that
before
I
know,
specifically
with
Oktoberfest.
Unfortunately,
their
documentation
like
I've,
through
a
link
in
the
notes
of
their
current
site,
but
their
documentation
from
previous
years
doesn't
appear
to
be
up
there
anymore.
F
I
know
in
previous
years,
though,
from
a
maintainer
side,
they
do
have
some
like
abuse
mechanisms
that
you
can
throw
in
there
to
be
like
hey,
I'm,
getting
lots
of
trivial
pull
requests
for
things
and
I
just
want
to
opt
out
of
hacked
over
fast
and
I.
Don't
want
anything
on
my
repo
to
be
eligible
for
hacked
over
fest.
F
So
then
you
just
opt
out,
and
then
people
don't
want
to
go
to
your
repo
to
make
trivial
pull
requests
because
it
doesn't
get
them
points
anyways,
because
you're
you're
opting
out
so
they
kind
of
have
that
as
far
as
an
abuse
mechanism,
but
I
don't
know
again,
I
don't
know
specifically,
if
they're
doing
something
like
that
this
year,
because
all
their
documentation
were
previous
years
doesn't
exist
and
they
don't
have
that
and
stop
for
this
year.
Yet
so.
G
A
We
did
run
the
community
repo
through
a
404
link
checker,
and
there
are
so
many
broken
links
that
we
can
have
people
fix
like
I
Bob's,
not
here,
but
I
could
talk
about
Bob
like
we
can.
We
can
almost
do
a
tag
called
hacked
over
fests
and
only
do
fixing
broken
404s
in
the
community,
repo
and
I'm
willing
to
bet
they
won't
get
through
it.
It's
something
like
457,
broken
links
or
something
it's
like
this
ridiculous
amount
of
stuff.
Do
you
want
me
to
investigate
that?
A
F
H
F
F
Also
make
sure
that
you
take
the
time
to
validate
the
new
the
new
place
that
it's
going,
don't
just
take
it
to
take
a
guess
to
fix
it,
so
it
goes
to
something
that
to
hundreds
like
we,
we
want
those
links
to
actually
be
valid
and
actually
update
that
the
right
content
is
at
the
right
destination.
Yes,.
A
F
So
those
goes
to
be
kind
of
the
two
asterisks
that
I
put
when
reviewing
those
PRS
so
that
what
it
doesn't
waste
our
time
reviewing
a
PR
and
it
not
be
going
to
the
right
destination.
Anyways
I
would
also
put
in
there
that,
like
something
that
already
three
hundreds,
probably
you
shouldn't
be
eligible
because
there's
plenty
of
things
that
we
have
like
purposeful
redirects
like.
F
A
And
some
of
them
are
just
it's
not
just
search
into
replaced
to
like.
Sometimes
the
sentence
doesn't
make
sense
and
you
have
to
fix
that
thing
and
I
think
having
a
human
there.
That's
run
enough
to
like
look
at
context,
will
help
all
right,
so
I
could
down.
I
could
take
that
item.
That's
like
an
East
like
running
these
sort
of
for
report
for
report.
I
think
it
would
give
them
a
place
to
go.
A
C
I
was
gonna
say
so,
so
this
is
kind
of
great,
but
like
we
have
some
issue
that
makes
perfect
sense
for
this,
but
it
might
be
nice
to
kind
of
maybe
publicize
this
across
the
organization
a
little
bit.
So
if
there
are
six
who
you
know
yes,
first
of
all
to
say,
people
hey
make
a
bit
more
of
a
push
to
make
sure
you're,
labeling
good
first
issues,
because
we
might
have
some
more
people
over
October
getting
involved
with
these.
C
A
F
It
might
just
like
a
ke
dev
email
as
well
as
Aaron
was
also
mentioning
in
the
chat
if
we're
able
to
like
if
we
have
a
snippet
and
we
can
get
it
reviewed,
like
we're
cool
with
the
snippet.
That's
created,
then
yeah.
If
we're
able
to
send
out
to
2k
dev
and
just
mention
in
the
community
meeting
like
hey.
If
you
have,
if
you
have
a
thing,
that's
good
for
this,
throw
good
first
issue
on
it
and
then
once
like,
once
they
come
out
with
documentation
about
like
how
they
might
be
highlighting
things.
F
Then
we
can
look
at.
Is
there
automation
or
something
that
we
want
to
do
that's
worthwhile
doing,
because
they
just
don't
have
any
documentation
up
for
this
year
yet?
But
if
we
just
highlight
things
that
are
good
for
this
with
good
first
issue,
then
at
least
we
have
that
kind
of
consistent
across
all
the
different
repos
New
York
yeah.
A
C
A
B
B
B
B
Also?
You
can
view
local
changes
in
your
tool
in
in
the
code
review
tool.
You
don't
have
to
push
the
code
to
like
github
just
to
see
that
if
there
is
a
multi
repo
CLI
tool,
that
comes
handy
with
it
for
some
useful
commands
and
it
works
with
multiple
off
providers,
because
it's
based
on
on
firebase,
so
it
works
with
github
Google
and
there's
others
like
firebase
support.
Some
multiple
authentications.
B
So
yeah
a
lot
of
stuff.
This
is
the
architecture,
so
all
of
the
metadata
is
stored
in
fire.
Store
which
is
firebase
is
cloud
storage
and
your
web
app
takes
the
metadata
from
there,
but
takes
the
code
and
the
dish
from
your
local
machine
from
a
local
gr.
Pc
server,
that's
getting
the
content
from
get.
B
Similarly,
the
CLI
tool
can
get
metadata
first
or
and
accesses
I
get
directly
and
there's
also
a
cloud
service
to
do
some
stuff,
like
sync
comments
with
github
and
stuff,
like
that,
I
can
talk
about
this,
but
I
I'd
focus
more
on
this
part
I
couldn't
because
we
don't
have
a
lot
of
time.
So
this
is
what
it
looks
like
I
guess,
it's
kind
of
similar
to
pro
that
you're
working
with.
B
B
B
B
You
can
see
all
the
changes
in
the
tool,
then
you
start
a
review.
The
reviewer
shows
up
in
your
view,
per
viewer
is
like
needs
attention
area.
Nano
reviewer
can
start
the
review
standard
review,
but
they
can
only
see
the
files
that
are
on
their
own
machine.
So
if
you
have
like
a
private
repo
repo,
they
can't
see
the
code
and
then
they
approve
and
then
once
approve
you
can
submit.
B
Now,
how
do
private
repos
work,
so
the
private
repo
CIA
checks
that
if,
if
the
ref
is
not
breaking,
the
CI
is
automatically
approved
by
the
basically
liked
by
the
repo
by
the
repo
CI,
if
it
does
break
so
so,
the
owner
of
the
private
repo
needs
to
join
the
DIF
and
apply
the
changes
to
their
own
private
repo
and
participate
in
the
discussion
if
needed,
apply.
These
fixes,
until
its
passing
and
and
then
I,
can
continue
to
merge
it
joining
a
def
after
has
been
submitted.
B
So
actually,
even
if
the
DIF
has
been
submitted,
you
can
join
the
the
review
afterwards
with
like
a
late
3po
and
that's
good.
If,
like
there's
a
breaking
change
and
you're
one
of
the
dependents,
and
then
you
add
your
changes
and
then
other
people
can
see
what
fixes
need
to
be
made
for
that
breaking
change.
So
it
adds
like
more
examples
for
the
community
for
how
to
fix
breaking
changes,
so
people
don't
have
to
figure
out
on
their
own.
They
can
see
like
what
other
people
and
basically
copy
paste.
B
B
Yeah
and
yeah
I
don't
have
time.
Yeah
I
can
show
you
that
if
I
add
it
locally,
it
actually
I
can
actually
see
it
in
the
UI.
But
just
trust
me
that
that
happens
and
that's
it.
That's
what
I
wanted
to
show
if
this
is
interesting
for
you
for
kubernetes
or
even
like
for
your
own
use,
please
let
me
know
and
I
I'm
interested
in
like
community
contributions.
So
all
the
code
is
open
source
and
the
issues
are
updated
with
good
first
issues
and
there
was
a
board
with
what's
going
on
currently
and
that's
it.
F
B
If
you're
a
developer-
and
you
want
to
like
do
changes
yourself,
so
you
would
install
and
you
want
to
work
with
the
system,
so
you
would
install
like
the
local
server.
So
it
can
see
your
local
changes
and
then
see.
Even
if
you
don't
push,
everything
is
immediately
visible.
If
you're
not,
then
for
public
repos,
at
least
it
can
host
the
files,
and
so
you
don't
have
to
installing.
F
Okay-
and
the
second
question
is:
what
does
it
just
like
discussion
pieces?
So
when
there's
things
that
are
reviewed
and
people
leave
comments,
do
those
appear
on
any
of
like
the
backend
sources
so
like?
How
does
that
it
look
as
far
as
a
github
PR?
If
somebody
was
not
looking
at
this
review
tool,
would
they
be
able
to
see
those
comments
or
those
comments
locked
into
this
particular
review
tool
right.
B
F
Right
to
address
your
so
Josh
just
put
up
a
note
in
the
chat
about
like
what
what
kind
of
problem
does
it
solve?
It's
a
it's,
a
different
way
of
approaching
reviews
for
features
that
end
up
touching
multiple
different
repos
within
our
org.
We
have
like
right
now
the
the
primary
way
we
solve
this
for
things
that
need
to
be
really
super
tightly
coupled
is
the
staging
setup
in
in
kubernetes,
which
has
its
own
set
of
trade-offs.
F
So
I'd
be
really
interested
to
see
what
that
looks
like
again
and
get
updates
on
it.
As
that
feature,
is
there
and
able
to
be
rolled
out,
so
we
can
take
a
look
at
how
those
how
comments
and
and
would
be
able
to
be
synced
back
and
forth
between
a
like
Multi,
multi,
repo
review
tool
and
github
itself,
if
you're,
just
like
scrolling
through
your
PRS
and
getting
notifications
through
the
regular,
the
regular
github
means.
B
A
You
have
you
shown
this
to
Tim
Hawking.
The
reason
I
ask
is
we
used
to
have
reviewable
enabled
on
the
kubernetes
repo
and
he
really
liked
it,
but
ended
up
being
too
expensive,
and
some
people
wanted
to
use
github
and
some
people
like
at
one
point
I
accidentally
spammed
every
kubernetes
developer
by
clicking
on
the
wrong
thing
and
it's
a
tool
like
this.
You
almost
have
to
have
like
yeah
yeah,
so
I'd
be
happy
to
sing
with
him.
A
A
It
was
before
my
time,
I
think,
maybe
a
year
I'm,
not
sure
how
many
people
used
it,
but
it's
one
of
those
things
where,
like
you're
gonna,
like
you're
gonna,
have
to
kind
of
market
it
to
each-
and
this
is
this
is
something
I
feel
like
contributes,
could
never
make
a
decision
on
like
we
would
have
to
have
an
overwhelming
consensus
from
developers
to
say
that
we
want
to
move
away
from
this.
To
this,
like
yeah
and.
F
It's
something
that
we
would
need
to
get
a
lot
of
buy-in
for
I
know,
like
I,
invited
offer
to
this
meeting
to
kind
of
present
it
initially.
He
presented
it
to
seek
testing
yesterday,
and
they
also
saw
saw
a
lot
of
potential
in
it
as
well.
That's
kind
of
where
it
is
for
us
is
there's
there's
potential,
because
it's
trying
to
solve
a
problem
that
we
very
much
do
have
in
a
way
where
we're
looking
at
different
trade-offs
from
the
staging
system.
Yep,
because
the
staging
is
is
still
like
it.
F
You
know
as
we're
looking
for
a
dependency
management
and
moving
to
you
know
Vigo
or
go
mod
again.
Every
time
we
do
things
like
that,
the
staging
system
always
kind
of
trips
us
up
so
having
a
way
of
being
able
to
review
code
that
goes
into
different
repos
track.
All
the
CI
testing
that's
happening
in
those
different
repos
and
being
able
to
like
give
a
green
light
for
everything
to
merge
all
at
once.
There's
there's
definitely
potential
value
in
that.
F
A
F
So,
once
that's
in
place,
then
I
think
we
can
start
like
talking
to
to
the
community
and
in
particular
around
developers
who
are
doing
doing
those
kind
of
big
features
entering
around
cloud
providers
and
api's
and
stuff
like
that,
are
like
big,
big
things
that
touch
a
whole
lot
of
things
in
core
I.
Think
those
are
the
people
that
we
would
want
to
that.
We
want
to
talk
to
and
kind
of
wrap
into
this
conversation
about
like
what
are
the
things
you
really
need
out
of
a
tool.
F
A
A
Okay,
business
or
hosting
the
meeting
I'm
gonna
toss
the
the
spreadsheet.
It
feels
like
we're
kind
of
getting
in
a
rut
with
hosts.
So
if
anyone
wants
to
host
the
kubernetes
community
meeting,
this
is
the
thursday
meetings.
This
is
the
upcoming
schedule
here
and
these
things
I've
filled
out
for
the
next.
We
should
be
good
through
November
as
far
as
SIG's,
giving
their
status
reports
and
as
Jonas
is
finding
out
they.
Usually
oh,
that's
this
week,
so
we
got
a
the
host
still
has
to
continue
to
kind
of
chase
after
SIG's.
A
A
Let's
see
office
hours
is
going
to
be
the
after
the
this
morning
session
went
well.
We
had
a
bunch
of
food
volunteers,
both
Jeff,
Bob
and
Mario
cannot
do
office
hours
on
the
west
coast.
So
if
any
of
you
have
any
engineers
sitting
around
doing
nothing,
uh-huh,
please
feel
free
to.
Let
them
know
that
we
could
use
them
at
this
afternoon's
session
and
meet
our
contributors
with
the
steering
committee
when
it
was
the
highest
amount
of
traffic.
We've
ever
seen
it
to
me
they're
contributors,
so
the
traffic
there
continues
to
grow.
So
that's
the
recurring.
A
A
Can
everyone
see
that
yep
all
right?
How
do
I
mix
well
on
my
maximization
button
is
like
under
those
in
overlay,
I,
hate
computers,
so
much
keyboard
shortcuts
worth
see,
how's,
that
is,
that
better
yeah,
okay,
all
right
and
he
completed
I've,
actually
never
run
one
of
these
at
this
meeting
this
was
parents
last
time.
So
how
do
we
go
left
to
right
right
to
left
anybody.
A
A
Before
I
get
through
those
any
any
notable
completions
that
happened
this
last
week
that
we
should
discuss,
or,
as
everyone
generally
thumbs
up
my
zoom
Windows
now
minimize
all
I
can't
see
I
can't
see.
So,
if
someone's
like
waving,
let
me
know:
okay,
let's
go,
let's
go
through
block
ones
here,
remove
direct
access
from
the
repo.
This
is
you
Aaron.
F
F
So
there
was
a
few
things
like
that
that
he
was
able
to
to
highlight-
or
like
tagging
tagging
releases
without
you
know,
release
automation
like
we
have
a
bunch
of
release,
automation
for
KK
but
other
other
repos
that
don't
necessarily
have
all
the
ANA
Co
release,
automation,
the
the
those
pieces
just
weren't
weren't
available.
So
we
did
get
some
more
information
or
a
continuing
to
work
on
okay,
cool.
A
E
So
I'm
working
with
Lukas
on
this
to
update
the
readme
right
now,
people
are
landing:
dev,
stats
and
they're
trying
to
use
dev
stats
for
things
that
it
shouldn't
be
used
for.
So
essentially
they
don't
understand
how
terms
are
defined
and
they
don't
know
to
go
down
to
the
bottom
of
the
page.
That's
where,
like
the
definitions
are,
and
so
we
want
to
make
a
readme
that
makes
that
the
sends
them
to
the
github
repo
that
makes
that
really
explicit.
E
A
A
The
only
thing
we're
waiting
on
now
is
more
feedback
on
the
morning
sessions
which
you
want
to
be
kind
of
like
driven
by
the
SIG's
sustainability
style
talks.
So
like
the
first
one's
gonna,
be
a
sig
arch.
Talking
about
you
know,
overviewing
overarching
style
things
and
then
the
afternoon
is
going
to
be
uncomfortable.
A
H
I
mean
Chang
guys
got
kind
of
its
own
team
right,
you're,
acting
a
lot
with
other
teams
because
we're
in
kind
of
radically
different
time
zones,
but
we
do
have
a
team.
Six
people
I
think
they're,
organizing
it.
We
have
we're
pretty
much
pinned
down
the
logistics
for
the
contributor
social
that
happens
the
evening
of.
H
To
talk
about
you
know,
being
a
Chinese
contributor
to
kubernetes
and
what
the
main
roadblocks
are
and
ways
to
get
around
those
and
other
things.
Okay,
so
we'll
be
announcing
that
soon,
so
that
current
contributors
will
know
about
it,
since
they
won't
be
attending
the
events
for
the
rest
of
the
day.
H
A
H
A
Communication
and
collaboration
platform
is
a
Paris
one,
but
there
was
a
contributor
I
didn't
recognize
before
who's
been
organizing
a
spreadsheet
that
has
a
list
of
all
of
our
communications
platforms
and
then
we're
gonna
figure
out
oughta
consolidate
who's
in
charge
of
what
and
who
owns
what,
but
that's
more
of
a
Paris
thing.
Unless
anyone
has
anything
to
add
on
that
front
or
is
been
working
on
this
and
knows
about
it.
A
Alright,
audit
zoom
license
holders.
That's
like
an
ongoing
process.
Paris
isn't
here
so
she'll.
Just
talk
about
that
next
week,
moderation
dr.
mailing
list,
I,
need
to
I
need
to
reprioritize
this
because
I
don't
feel
we
don't
really
need
it
because
the
next
card
archiving
Kay
users
are
moving
to
discuss,
is
done,
I
closed
it
on
Wednesday,
Bob,
PR
and
all
the
multiple
repos
and
got
everything
merged
as
far
as
sending
users
to
the
right
thing.
Instead
of
a
closed
mailing
list,
so
I
consider
that
done.
I'll
go
ahead
and
update
those
issues.
F
Quickly,
just
speak
to
the
three
github
management
items,
so
23
23,
21,
26
and
23
24.
No,
no,
like
substantial
update
on
them.
Those
are
still
like
to
do
items
that
we
want
to
advance
forward,
there's
a
bunch
of
like
other
kind
of
automation,
work
that
has
been
prioritized
above
those
for
the
time
being,
but
they're
still
they're
still
in
progress.
Mm-Hmm,
no
substantial
update
right
now.
Okay,.
A
G
So
we
we
have
our
next
meeting
here
later
today.
So
one
of
the
things
that
we
talked
about
last
time
was
to
add
a
few
new
roles
to
the
contributors,
role
board
and
Nicole,
whose
men
she
is
going
to
post
an
example
of
that
she
wants
some
feedback,
so
she'll
be
posting
one
of
those
and
the
cig
country.
Beck's
channel
just
get
some
feedback.
This
is
for
a
discussed
role.
Essentially
our
conversation
instigator
or
a
conversation
starter
role,
making
sure
that
we
and
we
get
some
good
discussions
going
Josh.
G
The
so
we
did
add
the
the
non
code
talks
to
the
the
repo
one
thing:
that's
on
me
right
now
is
to
add
a
segment
and
link
to
the
non
code,
doc
from
the
regular
contributors
guide
and
also
while
I'm
doing
that,
to
make
it
a
non-trivial
contribution
is
to
go
through
the
rest
of
the
document
to
make
sure
that
it
looks
good
as
well.
So
that's
on
me
and
then
today
we
also
are
doing
a
final
review
of
the
form
letter
and
essentially
final
review
will
be
done
by
Noah.
Okay,.
A
A
What
I
figured
let's
just
go
through
tracking
umbrella,
real,
quick
mentoring
programs?
That's
para
she's!
Not
here,
community
maintenance
tasks,
I
get
the
feeling
we'll
just
end
up
being
for
all
of
2018,
but
I
feel
from
looking
at
with
doing
the
zoom
stuff.
A
lot
of
that
was
like
changed
now
because
of
the
way
we
change
we
do.
Github
I'm
gonna
need
to
go
back
and
scrub
to
see
which
one
of
those
makes
sense.
Does
anybody
have
I
get
the
feeling
that
people
would
agree
that
a
lot
of
these
don't
make
sense
anymore,
yeah.
F
Kind
of
wit,
what
the
state
is
that,
when
we,
when
we
started
those
community
maintenance
tasks
like
a
lot
of
like
github,
had
zero
policies
around
them
for
doing
any
of
these
audits,
and
we
didn't
have
access
in
many
cases
to
do
these
audits.
Lots
of
things
have
changed
in
the
last
nine
months
or
so
so,
and.
A
Umbrella
issue
for
reviews:
oh
that's
the!
We
still
need
a
review
section
for
the
contributor
guide
move.
That's
that's
a
hard
one!
Let's
skip!
It,
though,
is
right
in
here
developers.
Guy
I
need
to
sync
up
with
him
and
see
how
that's
going
I
do
want
to
mention
quit
the
lection
things
while
we
get
to
the
card,
I
am
planning
on
opening
SIDS
and
everything
right
after
this
call
with
a
and
sending
out
ballots
and
things
like
that.
F
A
F
Is
you
right,
I'll
speak
to
those
two
quickly
for
Eric,
because
he
can
speak
so
the
first
one
is
removing
some
work
wide
github
labels,
yeah,
there's
not
really
any
discussion,
but
it's
a
heads
up
of
something
that's
already
been
sent
to.
Kade
of
these
are
all
labels
that
are
deprecated
in
our
current
process.
A
lot
of
them
had
to
do
with
the
submit
queue
and
munge
github,
which
is
no
more
rest
in
peace,
lunch
github,
so
we're
gonna
rip.
Those
labels
out
of
I
would
have
the
org
because
we
just
don't
need
them
anymore.
F
If
anybody
has
any
comments
or
concerns
replied
the
mailing
list.
Second,
one
is
standardizing
the
automation
on
kubernetes
incubator.
This
is
again
a
continuation
of
the
github
management
sub-project,
doing
things
to
standardize
things
across
our
org.
We
did
something
similar
like
this,
similar
to
dis
for
kubernetes
SIG's,
to
have
consistent
automation
and
plugins,
enabled
across
all
the
different
repos
that
was
successful
and
there
wasn't
really
any
hiccups
in
that.
So
the
were
doing
the
same
thing
with
incubator.
F
We're
not
getting
rid
of
incubator
just
yet
Josh
it
is,
is
legacy,
though,
in
that
we're
not
kicking
anybody
out
and
forcing
them
over
to
SIG's,
but
we're
also
never
adding
anything
new
to
incubator
incubators
kind
of
like
frozen
where
it
is
now
we
just
there,
isn't
a
drive
to
force
everybody
over
into
kubernetes
SIG's
and
to
adopt
that
model.
Yet.
A
B
A
Like
I
can't
tell
what
that,
are
you
good,
okay,
good,
all
right
all
right?
Anybody
else
have
feedback
for
Christoph
on
this
one,
all
right.
Let's
see,
elections
are
already
covered,
spread
the
word
about
your
networks
about
the
survey
Oh
nuts
Jonas.
Can
you
add
a
contributes
survey
mentioned
to
the
community
meeting
for
tomorrow.
We'll
need
to
announce
that
and
I
already
talked
about
kubernetes
users.
We
have
seven
minutes
left.
Does
anyone
have
any
outstanding
questions?
Sorry,.
A
On
dev
and
contributes
the
mailing
list
probably
wouldn't
hurt
to
mention
it
tomorrow
is
there?
Is
there
anything
else
we
should
mention
tomorrow
to
people
I
know,
I
know
we
sent
the
labels
stuff
and
to
cover
done
he's
dead,
but
it
probably
doesn't
hurt
to
mention
it
in
the
announcements.
Cuz
repetition
seems
like
the
only
thing
that
works
sometimes.