►
From YouTube: SIG Chairs and TLs Monthly 20200114
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
I
wasn't
even
on
yet
all
right
cool
all
right
here
we
go
so
let's
just
go
ahead
and
start
today
is
Tuesday
January
14th,
my
name
is
Parris.
Thank
you
for
joining
me
today
is
the
first
edition
ever
of
kubernetes,
chairs
and
tech
leads
hang
out
chill
session
kick-off
shindig
that
we'll
do
monthly,
hopefully
have
two
time
zones.
Hopefully
we
can
figure
out
how
to
make
this
make
this
sync
and
make
this
flow
for
both
folks.
A
Thank
you
first
off
for
joining
me
today.
Cool
I
did
add
the
agenda
in
the
zoom
channel
or
zoom
chat
rather
I'm.
Sorry,
if
you
could
add
your
name
to
the
attendees
list,
that
would
be
great
and
also
there
is
a
open
discussion
at
the
very
end.
If
you
would
like
to
say
anything,
especially
so
I'm
not
talking
at
all
of
you,
that
would
be
wonderful.
A
That
would
be
great
and
of
course
we
do
have
a
code
of
conduct.
Please
be
excellent
to
each
other
there's
sixteen
of
you
right
now
that
are
joining
and
I
think
others
are
going
to
be
joining
us
momentarily
and
throughout
the
call.
So
if
we
do
have
some
discussions,
either
raise
your
hand
or
just
ping
in
slack
that
you
want
to
say
something
just
because
it's
a
large
meeting
and
that's
really
it
it's
for
the
welcome.
So
what
I
wanted
to
do?
First
off
is
intros.
A
I
know
everybody's,
like
cringes,
when
we
do
like
intros
at
Google,
it's
like
not
again,
but
some
of
you
don't
know
each
other
and
that's
legit
I
guarantee
you
there's
at
least
one
of
you
right
now
and
all
that
doesn't
know
who
the
other
person
is
that
they're,
looking
at
or
like,
if
you
don't
have
a,
if
you
don't
have
your
face
up,
don't
your
name
or
what
you
represent.
So
I
did
put
a
little
template
in
the
agenda
for
musts
as
far
as
intros
is
concerned,
so
we
have
a
little
bit
of
a
template.
A
A
If
you
want
to
do
pronouns
your
employer,
your
job,
your
favorite
food,
color,
animal,
a
challenge
that
you're
currently
having
that
you
want
to
tell
other
chairs
and
tech
needs
about
an
announcement
that
you
think
that
this
group,
it
would
be
applicable
and
would
be
sharing
applicable,
sharing
and
that's
it
so
I'm
just
going
to
go
first
base
off
of
my
zoom
window
here
and
that
is
I,
think
the
Google
room
I
think
that's
Betty
and
Walter.
If
I
can
see
all
right,
why
don't
you
only
kick
off
the
intros
hi.
B
C
E
D
E
That
I
did
want
to
bring
up
is
at
Keuka
in
north
america
last
year,
or
I
guess
a
few
months
ago,
I
realized
there's
a
lot
of
things
going
on,
contributes
and
in
the
release
team.
That
kind
of
overlaid
with
Docs
and
there's
a
lot
of
communications
there,
but
I
think
there
could
be
better
communication
between
the
chairs
and
maybe
some
sort
of
status
out
that
the
chairs
do,
but
for
another
discussion.
F
F
Yes,
one
major
pain
that
were
healing
this
is
more
of
a
windows
thing.
It's
a
lot
of
times.
Windows
is
almost
like
a
second-class
citizen
in
the
kubernetes
communities
were
trying
to
always
change
that
stigma
and
ended
up
front
and
center
for
when
people
are
thinking,
functionality
and
areas
of
investment,
I
guess
orange
is
a
color
out
pick.
G
I'm,
Tim
pepper,
Zig
release
we're
group
LTS
around
support,
also
on
the
patch
release
team
or
a
branch
manager
best
way
to
contact
to
me.
I'm,
tea,
pepper
on
all
the
things
generally
I
would
say:
no
github
notifications
are
gonna
catch,
my
eyeballs,
probably,
but
it's
yeah,
that's
a
known
problem
in
the
community.
I
work
for
VMware
favorite
food
at
this
point
would
have
to
be
tacos.
Considering
it's
lunchtime,
and
it's
been
mentioned
and
I'm
hungry
an
issue
dealing
with
the
battle
fire.
G
That
is
our
release,
scripting
and-
and
this
goes
to
what
Jim
mentioned-
I
think
as
well.
One
of
the
things
we're
dealing
with
right
now
is
a
issue
around
how
we
versioned
our
open,
API,
Swagger,
JSON,
spec
and
dog
skied
off
of
that
and
it
causes.
This
is
causing
multiply
multiple
dimensions
of
problems
and
we're
trying
to
sort
out
a
fix
to
it.
Yeah.
H
H
The
optional
pronouns
he
him
they
them
worked
for
the
Linux
Foundation
challenge,
we're
having
just
a
+1
Jim
and
Tim
on-the-go
fire.
That
is
our
reference
stock
generators
and
all
of
the
pain
associated
with.
Oh,
it's
so,
as
we
add
localizations,
we
add
an
increasing
number
of
contributors
with
right
access
to
the
repo
medicine
deeply
on
sustainable
practice.
That
does
not
scale,
and
we
need
to
fix
that
sooner
rather
than
later.
I
I
All
right
to
release
one
of
the
pet
release:
team
members
as
well
p.m.
as
ur
working
on
Cluster,
API,
stuff
and
github
management
stuff
on
the
lower
tier,
occasionally
best
ways
to
reach
me
are
slack
really.
You
can
reach
out
I'm
on
all
platforms
as
just
Augusta,
so
that's
kubernetes,
flats
and
skins
get
slack.
I
My
email
is
Steven
sthe
and
dot
Kate's
at
a
GSD
us.
If
you
want
to
reach
out
to
me
via
email
for
kubernetes
stuff
pronouns
are
he/him.
I
am
employed
at
VMware
as
a
lead
for
the
cloud
native,
tooling
and
advocacy
group
favorite
color
is
ox
blood
and
the
challenge
that
we're
having
is
also
plus
wanting
to
all
of
the
Bosch
fire
that
is
happening
in
release
and
Docs,
and
pretty
much
everywhere.
We're
working
on
refactoring
a
lot
of
that
stuff
to
go
tools
which
is
working
nicely
so
far
on
the
release.
Engineering
side.
I
Additionally,
on
the
PM
side,
the
big
pain
I
guess
is
I
would
love
to
see
us
move
towards
global
planning
events
or
individual
planning
events
that
fed
into
something
that
turned
into
a
kubernetes
roadmap.
We
don't
have
one
of
those
today
but
it'd
be
great
to
eventually
see
yeah
I
talked
about
all
right.
A
J
I
J
I
J
So
boring
but
I'm
easy
to
find.
But
if
it's
not
a
direct
message
in
in
slack
and
if
it's
a
github
notification,
it
will
never
be
seen,
there's
just
too
much,
as
some
of
you
know
as
far
as
favorite
things,
I
don't
have
any,
which
is
why
I
was
getting
trouble,
there's
no
favorite
colors
or
favorite
animals,
none
of
those
things
and
and
problems.
J
It's
probably
getting
more
people
up
the
contributor
ladder
and
getting
more
people
interested
in
involved,
and
it's
not
that
we
don't
have
that.
It's
that
it
requires
mentoring.
It
requires
it
requires
time
from
people
who
are
already
very
busy.
And
how
do
we
encourage
that?
That's
probably
the
biggest
problem
that
I
see
right
now.
I've.
M
Hi
everyone,
my
name,
is
Krista
flicker
steering
I,
do
a
bunch,
quarterback
stuff,
usually
playing
with
github
bots
or
putting
out
bash
hires.
The
best
way
to
reach
me
bard
on
is
slack
I
actually
do
get
around
to
github
notifications
eventually,
but
if
you
want
something
in
a
timely
manner,
definitely
slack.
N
Not
a
chair
I
own
one,
though
backup
out
with
just
just
observing
today
so
but
favorite
color
is
definitely
test
grid
red
as
well
acne
I
know
everyone
says,
don't
get
me,
but
please
at
me
and
I'll
get
back
to
you
really
just
looking
at
how
I
can
help
out
more
across
cig
Doc's,
blog
sub-project,
cig
release
and
synchrony
of
X,
but
have
to
see
all
your
faces.
That
sounds.
O
You
may
have
seen
we
just
launched
the
bug
bounty,
so
I'm
excited
to
grow
the
security
side
of
things.
What
it's
kind
of
terrifying,
though
I'm
tall
Claire
at
most
things,
email
or
slack,
is
best
favorite.
Animal
is
a
penguin
and
I'd
say
my
biggest
pain
point
is
PR
use
both
as
a
reviewer
I
feel
like
I'm,
always
dropping
the
ball
and
as
a
contributor
I
feel
like
I
can
never
get
anything
done,
because
it's
so
hard
to
find
someone
to
review
the
could.
A
A
R
Right
and
then
George
hi,
I'm
george
castro
mystic
contributor,
experienced
most
of
you
know
me
as
the
person
who
helps
you
fix
your
YouTube
videos,
so,
generally
speaking,
I'm
available
for
signatures
to
just
help.
You
do
your
job.
Take
the
load
off
help
with
automation.
That
sort
of
thing
some
of
you
take
more
advantage
of
me
than
others,
but
you
all
should
be
taking
advantage
of
me.
So
I'm,
basically
here
to
be
available
to
y'all.
S
That
working
now
can
you
guys
hear
me:
okay,
yeah
I'm,
Shawn,
Sullivan
I'm,
the
co-chair
of
six
Eli
I
work
at
Google
and
I.
Guess
one
of
the
challenges
we've
been
working
on
for
quite
a
while
is
trying
to
get
the
inappropriate
dependencies
of
control
out
of
coop
control
so
that
we
can
we
can
pull,
could
control
into
its
own
repository
I've
been
working
out
that
a
long
time
and
we've
almost
completed
that
that's
I,
guess
that's
it.
L
L
But
then
on
top
of
that
the
review
bath
walk
way
behind
those
the
best
option
to
reach
me:
it's
definitely
direct
slack.
So
don't
be
afraid
to
add
me:
that's
the
best
way
to
reach
me
out,
get
have
notifications,
I
might
get
to
it
eventually,
but
it
might
take
a
couple
of
weeks
or
even
months.
Unfortunately,
it
takes
that
long.
For
me,
I
get
hop
slack
and
basically,
every
other
handle
is
soldiers.
I
put
it
down
in
video.
The
agenda.
A
A
The
first
off
is
the
contributor
experience
survey,
the
other
being
the
new
community
meeting
cadence,
which
has
switched
to
monthly
for
the
contributor
experience
survey
right
now
we
have
about
a
hundred,
and
seventy
responses,
which
means
we
have
hit
are
at
least
2018
target.
The
2019
target
hopeful
was
at
least
200,
so
we've
also
extended
the
deadline
until
Friday,
so
I
think
we'll
hit
our
target,
which
is
awesome.
That
means
we'll
have
good
survey.
Data
CNCs
is
also
going
to
be
giving
us
a
good
contributor
report
as
well
from
that
data.
A
You
can
even
look
to
see
there's
an
issue
that
I
can
link
inside
of
here,
where
you
can
see
just
the
raw
questions.
So
if
you
have
any
have
anything
that
you'd
like
personally
analyzed
that
might
help
you
or
say
like,
for
instance,
any
of
those
release,
questions
on
there
there's
obviously
testing
questions
and
things
like
that.
So
we
can
pull
those
out
separately.
We
can
even
do
a
whole
meeting
or
a
whole
meeting
on
the
analysis
of
the
results.
A
If
that's
something
that
would
help
you
all
and
things
like
that,
so
the
only
favor
that
I
have
to
ask
of
you
is,
if
you
have
not
had
a
meeting
yet
to
please
add
this
to
your
agendas
this
week.
Also,
if
also,
if
you
have
already
had
a
meeting
but
have
not
passed
this
news
to,
please
pass
it
to
your
mailing
lists.
I
know
Christophe
definitely
sent
that
out
for
like
a
million
mailing
lists
yesterday,
but
if
there's
any
that
we
missed
and
again
we're
just
trying
to
get
the
upstream
community.
A
A
All
right
and
if
you're
interested
in
building
this
and
helping
build
like
or
getting
a
pulse
out
of
your
own
communities,
we
can
help
with
surveys
or
Taylor
next
year's
survey
questions
that
you
think
you
want
to
get
a
pulse
on
so
I
want
you
to
keep
that
in
the
back
of
your
heads
for
planning
and
as
you
roll
out
programs
and
things
for
your
SIG's.
If
you
want
to
measure
them,
this
is
a
great
way
to
get
a
pulse
on
quality
kind
of
data.
A
R
So
the
TLDR
attendance
was
kind
of
declining
when
we
ask
people
they're,
like
hey
I've,
got
way
too
many
meetings,
I'm
busy,
I'm
a
sick
chair,
so
we
cut
down
the
cadence
of
that
to
once
a
month.
The
problem
was:
is
that
we
kind
of
had
to
wrestle
a
little
bit
with
the
governance
as
far
as
meeting
our
transparency
requirements
like
we
want
users
to
be
able
to
look
at
your
notes
and
see
what's
going
on
and
stuff
so
the
way
we
did
it
is
I
did
a
pull
request.
R
I
modified
it
a
little
bit
so
that
if
you
do
a
status
report
and
you're
up
to
go
that
month,
if
because
of
travel
or
both
co-chairs
are
not
available,
or
you
can't
find
anybody,
you
can
just
take
the
same
slide
deck
slides
that
you
use
for
the
community
meeting
and
just
post
those
to
the
mailing
list.
Or
you
know
you
can
hop
on
YouTube
or
post
say
status
during
one
of
your
meetings
and
record.
That-
and
you
know,
let
us
know
when
that
is
so.
R
I,
basically
want
to
give
you
more
options
of
places
where
you
can
talk
about
your
status
and
have
that
count
as
your
transparency
requirement.
Also,
we
notice
a
lot
of
chairs
we're
using
the
same
content.
They're
like
why
do
I
have
to
do
this
Yukons
in
a
month
and
I
have
to
get
the
same
content.
So
if
it's
your
turn
to
come
up
and
queue
kobzar
on
the
corner
and
you
have
a
set
schedule,
that's
a
status
that
you're
gonna
give
the
community.
R
Let
me
know:
I'll
grab
the
YouTube
video
and
that
gets
published
by
the
CDF,
and
that
will
count
as
your
as
your
status
for
the
quarter.
The
reason
I'm
bringing
this
up
is
lots
of
things
got
used
to
not
ready
this
week.
Let
me
put
this
two
next
week
and
we
would
move
the
schedule
around,
but
since
we're
only
doing
monthly,
we
can't
really
afford
to
have
a
cig
mr.
status
update,
so
I've
kind
of
just
giving
you
more
avenues
to
spam.
R
That
and
hopefully
that
will
work
for
you
and
it
should
be
less
work
for
you
overall,
you
only
have
to
do
these.
You
know
we're
only
having
four
six
going
per
month
so
that
should
cut
down
significantly
the
amount
of
status.
Does
anybody
have
any
questions?
Anyone
hate
this
or
I?
Don't
haven't
gotten
any
feedback
other
than
thanks
for
getting
rid
of
meetings,
which
I
guess
is
awesome,
so
that's
pretty
much.
All
I
have
question.
G
R
Well,
in
order
to
fill
out,
if
we
were
to
try
this,
we
would
have
to
commit
to
at
least
August
for
this,
for
every
signature
go
once
so
I
think
it's
worth
revisiting,
I,
don't
know
every
cute
con.
We
could
put
it
in
the
contributor
summit
survey
or
you
know,
I
mean
one
of
the
next
surveys
that
we
have
so
far.
People
seem
to
be
pretty
good
with
getting
rid
of
a
weekly
meeting.
G
The
reason
I
ask
is
is
I,
think
back
to
two
and
a
half
years
ago,
when
I
got
involved
in
the
community.
That
meeting
was
my
first
touch
point
and
it
really
helped
me
ramp
up,
but
I
think
if
the
same
content
is
monthly,
I
could
probably
have
done
the
same
thing,
but
it
was
like
a
useful
iteration
that
kind
of,
even
though
there
was
repetition
in
it,
I
wasn't
able
to
see
or
hear
the
repetition
from
a
new
contributor
side.
G
R
Well
think,
there's
a
long
discussion
bug
that
we
had
is
when
this
format
for
this
meeting
first
started.
We
didn't
have
things
like
caps,
we
didn't
have
the
contributor
summit
and
really
you
had
to
go
to
the
meeting.
Otherwise
you
would
miss
something
now
that
we
have
caps
and
you
know
we're
meeting
regularly.
F
A
Other
thing
about
check
point
is
in
contributor
experience
and
our
bi-weekly
updates.
We
do
have
the
stand
up
for
the
community
meeting,
so
George
I
feel
like
if
we
just
you
know,
watch
not
only
the
viewership
but
maybe
check
in
with
the
chairs
during
these
meetings
and
get
a
like
a
pulse
for
like
what
people
are
feeling
where
they're,
the
folks
that
we
know
need
the
communication
pipeline,
the
most
I
think
that's
fine.
So
let's
just
keep
the
door
open
there,
but
I
agree
that
we
should
totally
have
a
check
point
as
well.
Yeah.
R
And
one
thing
we're
able
to
do
now,
since
its
monthly,
this
would
have
worked
if
it
was
weekly.
Is
we're
gonna
publish
the
meeting
notes
directly
to
the
mailing
list
right
after
the
meeting,
so
that
that's
like
a
place
of
record.
We
kind
of
stopped
doing
that
during
the
weeklies,
because
for
a
while
it
would
just
there
was
just
too
much
you
know,
and
then
people
just
weren't
reading
it,
but
I
figure.
A
A
So
George
so
I
put
yourself
in
a
chair
and
like
pretty
much
go
like
just
as
an
example
like
say
you
know,
whatever
sing
foo,
like
your
sake,
food
chair.
What
would
you
do
like
this
like
right
now
today?
So,
for
instance,
like
maybe
check
the
schedule
for
the
community
meetings
right
to
get
like
a
little
step
by
step
like
that
ooh
I.
R
Should
definitely
link
I
should
definitely
link
the
schedule.
The
way
it's
working
now
is
I
have
a
host
and
the
meetings
a
third
Thursday
of
the
month
and
we
have
I,
have
a
timer
that
goes
off
on
the
first
of
that
month,
where
the
host
will
come
to
your
sig,
you
usually
on
slack,
because
that's
where
mostly,
where
people
respond
then
say:
hey
you're,
due
to
give
a
status
this
month,
and
that
gives
you
like
a
three
weeks
to
get
started
in
the
past.
You
know
we
gave
you
three
days.
R
We
would
tell
you
on
the
Monday
of
so
we're
kind
of
hoping
that
you
know
that
will
give
you
more
time
to
get
prepared
other
than
vats.
Let
me
link
up
the
community
meeting
notes
which
has
the
link
to
the
schedule,
and
we
went
ahead
and
updated
all
the
docs
to
kind
of
reflect
how
this
is
going
to
work.
So
everything
is
always
linked
from
this
document.
But
there's.
R
If
you
look
at
the
like
fifth
sentence,
it
says
sig
co-chairs,
readme
and
both
that
will
take
you
to
this
spreadsheet
and
then
what
this
is
is
just
the
month.
The
four
things
that
are
going
to
go
that
month
and
then
we
I
basically
put
in
all
the
SIG's
to
schedule
us
out
and
then
we
repeat,
and
then
we
take
into
account
if
there's
a
cubic
on
holidays.
Things
like
that.
R
So
if
you're
gonna
go
in
February,
if
you're
sick
windows,
Multi
cluster
Code
of
Conduct
committee
and
off,
you
should
be
Friday
afters
when
I'm
gonna
have
the
next
house
start
to
kind
of
send
you
reminders
and
things
like
that,
and
then
the
notes
also
link
to
the
slide
template,
which
I
am
90%
sure.
Most
of
you
have
seen
because
I've
seen
most
of
you
give
status
reports.
R
What
what
do
you
mean
like
you
would
so
so
here's
the
template
right
so
usually
for
the
meeting
you
make
a
copy
of
this
and
you
fill
in
with
your
sig
information
and
let's
say
you
can't
make
the
meeting
for
some
reason.
You
could
just
send
a
mail
to
ke
dev
with
a
link
to
this
and
say:
hey
everybody.
R
This
like
template
by
the
way,
is
for
all
y'all.
So
if
you
want
to
change
it,
adapt
it
it's
also
optional.
I
know
some.
You
know
I'm
not
here,
to
tell
you
what
to
do
so.
If
you
want
to
cut
and
chop
this
up,
whatever
is
useful
for
you
yeah.
We
do
have
a
lot
of
sig,
saying:
hey
it'd,
be
better
if
you
just
gave
us
a
template
to
fill
in
stuff
and
that's
how
we
came
up
with
this.
A
It
might
be
good
for
chairs
who
are
super
swamped
to
have
like
a
checklist
for
compliance.
Like
a
hey,
it's
February.
You
should
probably
send
an
email
to
kada
I'm,
seeing
a
lot
of
thumbs
up
like
hey,
it's
February.
You
should
probably
send
an
email
to
k-dub
about
your
update
status
or
like
hey.
It's
March
you're,
going
for
community
update
something
on
the
something
along
those
lines.
A
R
I
R
They
could
start
with
a
checklist
if
it's
stuff,
like
you
know,
remember
to
do
introductions
at
the
beginning
of
your
meeting
so
I
know
some
SIG's
have
different
structured
notes
than
others.
Some
are
empty
and
some
you
know
they
have
a
nicely
filled
out
detail
section
in
the
front.
That's
like
here's.
Our
list
is
here's.
Where
goals
are
here's
our
back?
You
know
here's
our
yeah,
we
nice.
I
L
A
Like
SIG's
the
animal
working
group
time
out,
yeah
I
know
it's
like
yeah
birds
are
important
here.
I
mean
like
working
group
within
this
little
crew
of
people
right
here
and
you
all
are
working
on
a
collaborative
like
slack
DM,
so
George
I,
don't
know
why?
Don't
you
just
like
take
an
action
that,
like
there's
look,
sounds
like
there's
people
in
here
that
like
want
to
help
out
with
similar
causes,
so
yeah.
A
All
right
and
then
all
right,
let's
timebox,
that
any
other
questions
concerns
comments
specifically
about
how
you're
gonna
operate.
Your
meat,
not
not
I'm,
sorry
not
operate.
How
you're
going
to
give
the
community
updates
as
far
as
what
your
community
group
is
doing,
and
why
I
just
want
to
tell
you
you
should
just
overly
communicate
right.
Tldr
is
in
this
project.
It's
so
huge
if
you
feel
like
wow
I
haven't
talked
about
our
cig
in
like
30
days.
A
A
I
would
definitely
err
on
the
side
of
always
the
updating,
right
and
always-
and
you
always
have
your
cube,
con
intros
and
deep
dives.
Please
link
those
places
like
that's
the
other
thing
link
them
to
Kate
of
what
have
you.
We
can
figure
that
out
too,
as
we
go,
maybe
there's
a
collective
resource
that
we
can
all
pull
together
for
that
who
knows
TLDR,
but
the
future
looks
great,
so
less
meetings
as
well.
A
So
thanks
to
George
and
everybody
that
has
put
time
into
that
and
trying
to
figure
that
out,
we
got
a
lot
of
feedback
from
people
too.
So
feedback
again,
look,
it's
always
appreciated
and
clearly
it
goes
into
action.
So,
thank
you.
Everyone
is
there
any
other
announcements
that
people
think
is
really
crucial
that
they
get
out
to
this
body
of
folks.
A
All
right,
well,
one
there's
always
next
time
to
you
now
know
about
slack
channels,
mailing
lists
and
things.
Please
use
them.
Alright,
open
discussion.
Three
topics
looks
like
we've
got
little
less
than
20
minutes
this
first
one
is
obviously
the
meta
question
on
deck,
which
is
what
value-add
would
you
get
out
of
this
meeting?
Obviously,
all
of
you
are
extremely
busy.
People
I
want
this
to
be
as
valuable
to
you
as
possible.
You
all
are
different,
like
experienced
personalities,
etc
and
all
require
different
information
at
different
times,
but,
for
instance,
we
can
bring
in
guests.
A
A
Anybody
want
to
like
just
start
a
discussion
about
what
you
want
to
see
out
of
this,
and
this
is
not
necessarily
something
we
have
to
talk
about
now.
Either
we
can
talk
about
it
like
post
the
January
meeting,
but
anything
that
comes
to
your
mind
right
now
that
you
want
to
spark
and
I
see
a
hand
from
Jim.
E
Yeah
I
would
love
to
have
a
kind
of
ongoing
discussion
just
about
contributor
capacity.
Sustainability,
you
know,
is
brought
up
earlier
mentorship
just
generally.
What
are
other
folks
doing?
What
has
been
successful?
What
has
worked?
What
hasn't
worked
in
ways?
We
can
do
better.
Just
a
kind
of
a
touch
point
on
that
think
would
be
great.
A
Definitely
and
I
clearly
have
not
communicated
well
on
some
of
the
stuff
that
we
have
and
don't
have
and
why
we
don't
have
it
and
things
like
that,
so
I'm
also
going
to
be
using
this
meeting
to
do
that
so
expect
more
and
I
will
happily
do
it,
like
I,
said
any
trainings,
and
things
like
that
that
we
can
do
step-by-step
to
help
make
that
better.
Anybody
else.
A
Looking
for
hands,
I,
don't
see
any
hands,
no
all
right
and
then
getting
in
contact
with
you.
Obviously,
during
the
intros
we
said
it
late,
I
asked
like
with
the
best
contact.
You
all
heard
that
it's
all
across
the
board
right
I
mean
you
have
Farina
who's
like
send
me.
A
pigeon
you've
got
Walter
who's
like
I.
Don't
care,
send
me
whatever?
Hey
hey,
so
you've
got
folks
who
are
all
across
all
across
the
room
right.
So
the
question
is,
and
now
it's
not
a
question
now
people
are
filing
issues
about
it.
A
How
do
we
get
acknowledgments
from
40
community
groups
on
matters
that
we
need,
especially
like
security
things,
for
instance,
whether
it's
security
related
to
all,
first
security
related
to
like
zoom
settings
and
trolls
like
how
can
like
we
get
what's
the
best
way
for
us
to
get
an
acknowledgment,
for
instance
github
issues,
and
we
just
label
it
all
the
SIG's?
And
then
you
know
that
that's
an
area
that
you
need
to
go
to.
Let's
talk
about
this
so.
I
So
I
think
that
we
should
just
be
doing
what
we're
supposed
to
do
and
reading
those
emails,
whether
it's
don't
you
know,
make
sure
it's
marked
as
important
make
sure
it
doesn't
go
to
spam.
Make
sure,
like
you,
have
a
special
filter
or
something
like
you
should
just
be
reading
the
I
think
that
should
be
simple.
A
H
A
Feel
like
there's
some
kind
of
automation
here,
that
we
could
like
pooled
issues
that
are
tagged
as
such
into
the
digest
for
emails
or
something
along
those
lines.
I
don't
know,
y'all
are
rocket
scientists
with
this
recipe
stuff
we
can
I
feel
like.
There
is
a
solution
there
where
we
could
do
both,
but
it
would
require
folks
either
beyond
the
digest
or
looking
at
the
an
IC
Tim
with
a
hand
up
go
ahead.
G
G
Maybe
if
we
were
to
agree
that
there
was
some
particular
place
for
actionable
things
versus
just
notifications,
that
are
a
sea
of
all
things
that
that
could
widdle
things
for
us
and
if
we
agreed
whether
it
was
the
email
list
or
issues
assigned
to
people.
If
there's
an
expectation
like
like
what
like
most
even
were
saying
like,
we
need
a
baseline
expectation.
What
is
the
way
that
we
communicate
and
act.
I
Yes,
I
think
I
think
probably
a
combination
of
both
could
work,
I
think
for
instances
where
it's
meant
to
be
an
announcement.
This
thing
is
happening.
That
say
leaves
need
to
know.
It
probably
makes
sense
for
the
mailing
list,
as
opposed
to
a
github
issue.
If
it's
something
where
we're
seeking
consensus
then
maybe
initially
is
better.
We
also
have
to
consider
that
there
may
be
times
that
we're
dealing
with
sensitive
issues
that
should
not
necessarily
be
on
github
just
yet
okay,
so
that
would
be
a
place
where
the
mailing
wants
to
be
used
instead,.
A
A
A
A
I
So
we're
actually
running
into
this
are
about
to
run
into
this.
I
guess
see:
Tim
with
the
pivotal
acquisition
the
passaic
release
chairs
are
now
all
VMware
and
I'm
I
think
Tim
and
I
were
digging
around
to
find
where
this
is
listed,
but
I'm
not
sure
if
it's
actually
a
thing
or
something
that
we
just
thought
was
a
thing
that
there
should
be
employer
diversity
across
big
shares.
I
So
we've
been
wrestling
with
a
and
ideas
who
could
be
potential
successor
and
I,
actually
I
actually
posts,
one
of
the
coupon
nights
or
something
posted
to
some
of
the
sig
release
members
and
it
was
kind
of
as
a
well.
If
you
could
have
someone
right
now,
not
thinking
about
it
too
much
like
who
comes
to
mind
right
and
and
there
weren't
any
good
answers
we
have
like
I,
think
you
know,
Tim
and
I
were
talking
about
this.
I
That's
also
a
time
commitment
right
and
the
and
I
and
I
think
what's
being
positive
about
communication
is
that
we
we're
failing
to
communicate
in
certain
venues
because
we're
we're
oversubscribed
right.
So
so
adding
one
more
thing
to
the
list.
Mentoring,
you
know,
mentoring,
replacement,
I
think
is
striking
people
as
hard
I
do
I
think
there
are.
There
was
also
a
mention
of
like
term
limits
and
I.
I
Don't
I'm
like
I'm
I,
don't
know,
I'm
conflicted
like
I
feel
like
we
I
feel
like
there
should
be
a
are
you?
Do
it
like
a
checkpoint?
Are
you
doing
a
good
job?
You
feel
like
you're,
doing
a
good
job.
Are
you
oversubscribed
in
some
way
and
making
a
decision
partially
based
on
that
I?
Don't
think
it
needs
to
be
a
hard
limit
necessarily
but
I.
If
I
can
interrupt
you.
A
You're
going
deep
on
us
right
now
that
wasn't
the
question.
The
question:
was
you
like?
What
are
you
Steven
doing
to
find
successors
like?
Would
it
meant
to
you,
do
you
answer
the
would
mentoring
program?
So
that's
that's
to
check,
but
it's
like
that's
like.
We
already
know
the
problems
right.
It's.
How
can
we
like
today
like
take
action
and
help
you
all
and
like
I,
start
out
right.
I
So
we're
trying
to
essentially
mold
some
leaders
on
the
release
engineering
side
so
that
there
are
many
hands
in
turning
churning
occur.
Bananas
release
I,
think
that
you
know
some
of
that
will
we'll
tease
out
people
who
have
leadership,
qualities
that
we
need
we're.
Also
spinning
up
a
new
sub
project
for
CI
signal
to
focus
on
some
of
that
stuff
and
I.
Think
that
should
also
speckle
so
I
mean
like
I
would
look
to
you.
I
I
Team
role
leads
and
release
team
leads
and
their
shadows
as
potential
leaders
for
this
stuff
and
and
then
you
know,
of
course,
the
people
who
have
done
phenomenal
jobs
over
the
last
few
cycles,
just
in
doing
work,
I
think
that
this
isn't
a
good
opportunity
for
you
know
we,
you
know
we
initially
said
like
oh
well.
This
is
not
really
a
it's,
not
really
something.
That's
like.
I
A
I
Okay,
not
X,
clicks
exclusion,
not
exclusively,
no,
no,
not
exclusively
so
so.
The
the
lists
of
people
would
be
the
sub-project
owners,
the
the
people
who
have
served
on
the
release
team
as
role
leaves
or
team,
leads
and
I'm
people
who
have
been
doing
except
exceptional
jobs
lately.
So
it's
a
set
of
a
bunch
of
people,
not
exclusive.
A
H
Ma
so
with
DOCSIS
a
bit
of
an
IM
legend
situation
and
that
I
am
like
the
the
only
technical
writer
who
is
in
Sigma
X,
so
in
terms
of
replacing
myself
I
mean
Jim
is
wonderful,
Jim
is
stepped
up
and
is
doing
really
powerful
work
as
a
chair,
and
we
have
two
shadows
right
now:
Caitlyn
Barnard,
who
is
leading
the
blog
working
group
and
Brad
Topol
at
IBM.
H
So
we
have
like
a
an
incredibly
deep
technical
bench
for
for
Docs,
but
in
terms
of
people
who
do
Docs
professionally,
have
the
professional
expertise
to
wrangle
documentation.
We
don't
really
have
anyone
right
now,
so
I
would
I
would
love
to
step
away.
Part
of
me
would
love
having
a
hard
time
limit
so
that
I
could
jetpack
out
of
the
role
whether
I
was
replaced
or
not.
H
H
But
yeah
it's
not
just
about
well
I,
guess
the
for
for
Docs
it's
finding
people
who
are
dedicated
to
documentation
as
such
and
who
can
who
can
wrangle
like
information
architecture
and
you
can
who
can
look
at
documentation
as
as
a
whole
piece
and
make
a
meaningful
contribution
and
provide
meaningful
leadership.
There.
H
And
for
us
I
would
say:
that's
like
participate,
so
we
do
have
a
hard
requirement
for
chair
leadership
that
participating
in
the
release
cycle,
either
as
the
release
lead
or
as
a
shadow
is
a
hard
requirement
because
there
are
so
many.
There
are
so
many
moving
pieces.
The
docks
portion
of
the
quarterly
release
cycle,
something
always
breaks
and
it
breaks
it
never
breaks
the
same
way
twice.
So
the
ability
to
come
in
and
diagnose
and
repair.
H
What's
going
on
to
support
the
the
quarterly
release
lead
in
doing
that,
that's
one
of
the
primary
things
that
a
chair
doesn't
support
and
I
think
that
was
actually
what
like
raised.
Jim's
visibility
to
me
as
I.
Could
that's
just
an
awesome
person
but
like
as
a
chair
candidate?
Was
that
Jim
mentored
I
think
like
three?
Were
these
cycles
at
really
successfully
and
they
got
the
the
release
piece
in
a
much
better
place
than
it
was,
but
the
effort
for
cig
Doc's,
it's
it's,
the
the
difficulty
really
is
in
finding
candidates.
H
A
See
we're
all
learning
from
each
other
already,
and
what
about
everybody
else
we
have
like
1,
we
have
time
for
one
more
I
already
have
questions
and
notes
and
stuff
to
send
out
one
more.
What
are
you
all
doing
for
how
to
plan
your
success?
What's
your
succession
strategy
here
I
know
I'm
not
asking
you
to
leave
tomorrow.
A
I
want
to
talk
about
that
yeah
yeah
and
that's
what
we're
here
for
it's,
what
we're
here
to
learn
from
each
other
and
help
each
other
too.
So
clearly,
this
is
a
point
where
we
should
definitely
expand
on
maybe
even
have
a
separate
session
on
it.
As
far
as
the
chair
roll,
in
particular
in
succession,
not
even
from
a
holistic
contributor
angle,
which
you
know
yes,
you
all
are
trying
to
grow
your
contributors
as
well,
but
we
should
definitely
have
a
session
on
you
and
growing
the
chair,
roll
and
things
like
that.
A
Well,
alright,
yeah
I
already
see
like
room
for
improvement
and
things
so
I'm
really
happy
that
y'all
joined.
We
had
19
at
our
high
today,
which
was
awesome,
but
you
all
we
have
90
chairs
and
tech
leads
90
I'm
not
gonna
lie
I
think
you
all
are
very
active.
That's
just
from
my
TLDR,
like
my
TL
DR
is
this
is
a
very
active
crew
that
is
on
the
phone
today.
So
thank
you
very
much
for
being
chairs
really
appreciate
you.
A
It's
so
much
just
like
unsung
stuff,
especially
like
organizational
like
administrivia,
like
I'm
I,
really
like
troubleshooting
zoom,
especially
like
Googlers
or
like
we
like
hangouts
everybody's,
like
we
like
blue
jeans,
it's
just
like.
Oh
my
gosh.
Anyway.
We
really
appreciate
you
all
thanks.
So
much
we'll
see
you
soon,
bye.