►
From YouTube: SIG Contributor Experience Weekly Meeting 20200805
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
Okay,
there
we
go,
we
are
recording,
welcome
everybody,
it
is
august
5th
2020,
and
this
is
the
weekly
contributor
experience
meeting
for
sig
contributor
experience.
I
am
pasting
the
link
to
the
notes
in
the
chat
and
we'll
be
publishing
to
the
list
right
after
this
meeting
I'll
be
your
host
today,
george
castro,
bob
your
other
co-chair,
isn't
training
and
not
supposed
supposed
to
concentrate
on
that,
so
we're
going
to
try
to
have
a
meeting
without
bob
helping
us
along
the
way,
and
I've
already
failed
at
that.
A
Please
put
your
name
in
the
attendees
section.
We
have
discussions
to
discuss
today,
mostly
around
the
root
owners
for
kk,
which
we
want
to
talk
about.
First,
I
see
tim's
here
so
we're
gonna
do
that
first
to
get
out
of
the
way
and
then
people
can
and
then
we'll
go
on
and
move
on
to
our
normal
business.
Real
quick,
the
kubernetes
code
of
conduct
is
in
effect,
so
please
be
excellent
to
each
other.
B
C
E
Oh
no,
okay!
How
much
of
that
did
you
get
here
from
the
open
second
foundation,
bridging.
C
Bridging
our
communities
together,
a
lot
of
what
I
do
for
openstack
is
very
similar
to
what
sig
contributor
experience
does
focusing
on
like
getting
people
into
the
community
and
lowering
barriers
and
documenting
all
the
processes
and
stuff.
So
I
figured
that
this
was
a
good
place
to
start,
in
addition
to
my
work
with
sig
cloud
provider
and
provider
openstack,
so.
A
Awesome
you're
most
welcome.
I
think
you'll
find
lots
of
open
stackers
here.
Yes,
good.
Welcome,
welcome
all
right
with
that
any
other
new
contributors
or
anybody
who
hasn't
attended
in
a
while.
That
wants
to
say
hello,
all
right.
Moving
on
to
the
open
mic
discussion,
nikita
is
going
to
grab
this
root
owners
for
kubernetes
kubernetes.
F
Yeah
I'll
just
give
a
brief
intro
on
what
my
conclusion
is
from
the
thread
and
then
others
can
speak
to
it
depending
on
what
they
think.
So,
if
you
haven't
already
seen
the
issue,
there
is
an
issue
which
talks
about
cleaning
up
root
owners
for
kk
and
structuring
it
properly.
Currently,
the
approval
plugin
how
it's
written
it
doesn't
allow
us
to
structure
approvals
in
a
way
that
we
would
ideally
want
to.
So
we
need
to
make
some
changes
to
the
plugin.
F
The
plugin
is
code
is
quite
complicated
right
now
and
making
changes
to
it
is
very
difficult
and
we
usually
try
to
avoid
baking,
which
you
understood
and
any
changes
that
will
be
made
to
that
plugin
will
require
quite
some
time
to
get
it
hashed
out
so
depending
on
so
as
per
the
thread.
This
is
what
I
I
got
from
it
that
like
please.
F
Let
me
know
if
that
makes
sense
or
if
anything
needs
to
be
added,
and
we
can
discuss
it
so,
given
how
complicated
the
approval
plug-in
is
right
now,
I
think
we
need
to
start
from
a
cap
and
like
get
the
design
out
first
and
then
work
on
the
implementation.
F
The
cap
would
cover
three
things
or
two
things:
two
or
three
things.
The
first
one
would
be
that
it
would
add
support
for
granular
approval.
So
if
I
have
a
proof,
if
I
have,
if
I
have
like
root
approval
in
a
repo,
then
I
and
I'm
also
in
some
sub
directories,
then
I
should
be
able
to
just
approve
certain
sub
directories
or
certain
files,
I
would
say,
approve
like
directory
one
or
file
one
and
it
like
it
would
just
approve
for
that
file
and
for
everything
else
we'll
need
up.
F
You
can
say
that,
like
I
need
some
more
extra
verifies
from
sigma
order,
say
whatever
it
is.
This
is
especially
useful
for
root
approvers,
because
right
now
like
correct
me,
if
I'm
wrong,
it
feels
like
the
approval.
Rights
are
extremely
empowering
and
we'd
want
to
limit
how
that's
being
used
and
encourage
more
views
of
it.
The
other
thing
we
want
to
add
is
also
rejects
filtering
for
approvers
and
owners
files,
so
defining
approvals
for
certain
files
like
go.mountgood.com,
so
we
can
have
dependency
approvers
approved
such
files.
F
The
trick
here
or
the
catch
here
is
that
would
still
need
to
define
a
set
of
like
complete
route
approvers,
because
what
if
we
need
to
make
change
to
the
sonos
file
or
whatever
we
need
to
add
other
files,
so
we
could
probably
have
an
opt-in
feature
which
says
that
there
is
one
set
of
approvers
who
will
only
be
approving
changes,
owners
chun
removal
or
additions
of
certain
directories,
but
I
think
we
could
debate
more
on
that
on
the
design.
I
don't
really
need
to
hash
it
out
here.
F
The
other
last
thing
would
be
that
we
would
also
need
a
way
to
track
usage
of
how
a
blank
root
approval
is
used
versus
granular
root
approval
is
being
used.
It
doesn't
really
have
to
be
in
the
approval
plugin,
but
we
need
to
make
sure
that
whatever
design
we
decide
for
the
plug-in
plays
nicely
with
dev
stats
and
we'd
create
the
feature
for
tracking
it
in
dev
stats,
it's
kind
of
it.
That's
all.
I
got
from
the
thread,
that's
what
I
think.
G
This
is
tim
as
someone
who
holds
root
approvers,
I
do
find
myself
sometimes
not
wanting
to
approve
a
pr
until
all
the
other
subdirectories
have
approved
it,
because
I
know
I
haven't
read
all
the
code
and
I
don't
have
a
way
to
say
well,
I'm
approving
the
api
change,
but
not
the
implementation,
and
so
I
I'm
a
huge
proponent
of
being
able
to
say
something
like
slash
to
prove
subdirectory,
and
that
would
be
super
useful.
For
me,
everything
else
you've
discussed
is
crazy,
like
they're
nice,
but
I
don't
really
need
them.
G
H
H
So
the
way
it
started
out
was,
you
know
the
old
two-year-old
issue
where
we
were
talking
about
the
older
owners.
Files
are
stale
and
you
know
people
are
there
who
are
not
active
in
the
community.
H
So
that
is
one
angle,
so
bob
and
others
have
done
plenty
of
work
on
trying
to
clean
up
trying
to
figure
out
who
is
not
active
in
the
org
and
stuff
like
that
so
owner
the
root
owners
file
was
definitely
one
of
those
and
we
ended
up
talking
to
brian
grant
and
brendan
and
they
they
volunteered
to
go
emeritus.
Just
like
you
know,
we
had
joe
step
down
as
emirates.
I
remember
george,
you
filed
the
pr
for
that.
H
If
I
remember
right
so
now
we
have
three
people
who
have
stepped
down
and
then
the
question
was
the
of
the
people
who
are
still
there.
How
many
of
them
really
need
this
permission,
and
is
there
an
alternative
way
to
empower
them?
H
What
do
they
do
with
it
and
how
do
they
do
it,
and
so
I'll
give
you
an
example
like
why
tech
helps
with
the
scalability
and
there's
a
lot
of
things
that
he
needs
to
revert
when
scalar
day
jobs
go
down
and
then
the
way
they
work.
As
you
know,
he's
in
europe
and
it
it
would
be
really
good
for
him
to
have
that
power
right.
H
Another
example
is
like
jordan,
he's
everywhere
and
he
he
does
tons
of
work
and
tons
of
reviews
so
going
and
adding
jordan
everywhere
is
probably
not
a
good,
a
good
practice,
and
we,
you
know,
I
would
love
for
jordan
to
continue
doing
what
he
is
doing
so
and
then
we
were
looking
at
like
the
other
people
right.
So
those
are
two
examples
of
scenarios
where
we
definitely
need
this
capability,
then
the
question
was
like:
do
we
this
we
haven't
added
anybody
to
it
right.
H
Do
we
need
to
add
anybody,
so
I
volunteered
to
add
myself
to
help
with
like
the
gomod,
gosum
and
related
files,
because
I'm
a
depop
approver,
I'm
listed
there,
but
I
can't
really
do
anything.
So
usually,
what
I
do
is
I
I
do
some
amount
of
you
know
due
diligence
there,
but
I
end
up
pinging,
tim
and
jordan
to
actually
do
the
approval
right.
So
that
was
the
third
question
saying:
okay,
do
we
need
to
add
somebody?
H
What
would
be
the
requirements
for
adding
somebody?
Then
some
part
of
the
feedback
was,
we
can't
really
add
people,
because
the
people
are
gonna
have
like
really
blanket
permissions
and
you
could
literally
change
everything
in
the
project.
So
you
we
shouldn't
be
adding
people
so
then
the
question
is
like:
can
we
prune
people?
H
Can
we
limit
the
what
they
are
doing
so
we
went
down
this
discussion
path
and
realized
that
we
are
actually
hampering
the
people
in
the
root
owners
file
because
they
are
not
able
to
do
their
work
because
they
can't
go
and
approve
things,
because
you
know
immediately
when
they
approve
something
somebody
could
lgtm
and
the
whole
thing
could.
Even
if
it's
a
whip,
you
know
it
could
just
merge
right.
So
then
the
quest
then
tim
and
daniel
and
others
came
up
with
this
idea
of
like
okay.
H
What
if
we
do
this
thing
where
we
can
only
approve
certain
parts
of
the
tree,
even
though
we
are
in
the
root
file,
then
so
immediately
the
thing
turned
to
oh.
This
is
like
a
useful
thing
for
everybody.
It
doesn't
have
to
be
for
just
the
route
owners,
for
example.
I
I
help
with
the
hack
golem
failures.
You
know,
because
I'm
in
the
hack
directory,
so
whenever
somebody
fixes
a
goal
in
failure,
they'll
come
and
ping
me
saying
james.
H
Can
you
approve
this
and
at
that
point,
even
if
I
have
approval
rights
in
other
directories,
I
don't
want
to
do
an
approve,
and
until
all
of
those
are
you
know,
approved
by
somebody
else,
and
the
only
thing
remaining
is
bullet.
So
that
gives
an
example
of
like
how
it
is
useful
to
me
as
a
non-root
you
owner
as
well.
H
So
so
that
was
the
thought
process
where
we
ended
up.
Some
of
it
was
on
an
email
thread
behind
the
scenes,
but
most
of
it
happened
on
the
issues
itself
which,
which
you
probably
saw
so
tim,
did.
I
structure
that
correctly.
G
Yeah
great
summary
agree
with
everything
you
said.
One
thought
came
to
mind:
there
are
files
in
the
root
directory
that,
like
you,
would
like
to
help
administer,
and
I
have
zero
objection
to
that,
but
they're
in
the
root
directory.
Can
we
trick
them
like
we
tricked
bazel
by
moving
the
files
into
a
subdirectory
and
then
sim
linking
it?
I
don't
know
if
go
would
follow
the
sim
links.
Go,
has
a
long
history
of
not
liking.
Sim
yeah.
I
G
Maybe
maybe
we
could
ask
the
goat
team
like?
Could
you
make
sure
that
this
stays
working?
This
is
a
really
useful
feature
for
delegated
code
trees,
like
I
know,
they've
in
the
past,
shot
down
sim
links
as
part
of
your
path
as
it's
just
too
complicated
to
make
work
right,
which
I
think
is
bull
crap,
but
that's
different.
This
is
like
within
a
go
tree.
I
We
could
I
I
feel
like
it
for
for
us
really
it's
a
workaround,
it
it,
and
I
honestly,
I
don't
think
that
they're
gonna
go
for
it.
If
I'm.
If,
if
I'm
frank,
there's,
we
could
try
like
it's
a
low
effort
thing
for
us
to
do,
to
kind
of
go
and
like
make
the
proposal
to
the
the
golan
team
and
see
what
they
say,
but
I'm
I'm
I
you
know
I
don't
wanna.
I
I
would
not
want
to
put
all
our
eggs
in
that
basket
really
like
there's
nothing
to
me,
that's
bad
or
off
about
if
we
were
doing
more
like
enabling
more
granular
approvals
in
the
approval
plug-in,
but
really-
and
this
has
been-
this
has
been
something
that
has
been
true
for
a
while
now
is
the
approved
plug-in
as
it
stands
today
needs
to
be
completely
rewritten.
I
The
way
is
the
way
it's
designed
the
way
it's
laid
out.
The
way
the
code
is
laid
out.
The
way.
The
way
it
makes
assumptions
is
wrong,
not
just
like
its
own
internal
logic
inside
the
plugin,
but
also
the
way
it
interacts
with
other
plugins
and
prow
and
owners
files
and
all
that
kind
of
stuff.
I
I
It
wouldn't
be
that
much
more
difficult
to
add
it
may
like
there
might
be
some
performance
issues
I
can
see
just
because
the
way
like
proud
plug-ins
are
designed
to
be
stateless.
I
So
when
it
reads
approvals
in
it
reads,
it
basically
reads
every
comment
in
the
issue
and
looks
for
ones
that
match
the
approved
regex
and
right
now
it's
just
kind
of
a
binary
like
is
approved
on,
or
is
it
proved
off
and
if
it
has
to
do
more
processing
there,
I
I
could
see
there
be
some
potential
performance
issues,
but
we
would
have
to
kind
of
cross
that
bridge
yeah,
it's
very
possible,
but
it's
not
possible
without
a
complete
and
total
rewrite.
I
So
we
have
to
look
into
options
for
that,
whether
that
is
like
you
know,
setting
it
up
as
like
a
gsoc
project,
whether
it's
setting
it
up
as
like.
Okay,
we
just
need
to
contract
somebody
because
right
right
now
the
problem
is-
and
it's
been
true
for
a
while-
the
venn
diagram
of
people
who
understand
what
the
approved
plug-in
should
look
like,
and
people
who
have
time
to
do
a
complete,
ground-up
rewrite
of
the
plug-in
is
zero.
I
There's
there's
no
overlap
between
those
circles
and
there
has
been
overlap
between
those
circles
for
a
good
couple
of
years
now,
so
you
know
if
we
just
need
to
like
get
a
contractor
or
something
to
do
it
then,
like
maybe
that's
the
road
we
go
down,
but
it's,
I
think
the
key
is
like
going
through
that
design
thought
process
and
getting
it
done.
It's
probably
like
again
because
it's
a
rewrite.
I
It's
not
like
an
immediate
term
solution.
So
if
we
need
immediate
term
solutions,
yeah
then
we're
looking
at
like
properly
grooming
and
setting
up
that
that
root
owner's
file
like
people
who
are
inactive,
pull
them
out,
as
I've
seen
happen,
people
who
are
active
like
like
dims
getting
them
in.
I
was
also
thinking
of
volunteering,
because
I'm
also
a
depth
approver
there.
I
But,
like
you
know
again,
it
just
comes
down
to
as
far
as
the
medium
to
long-term
solution,
properly
designing
and
scoping
out
what
the
approved
plug-in
will
look
like
in
the
future
and
then
getting
getting
something
on
it.
Yeah
just
calling
out
what
paris
said
in
the
chat,
so
gsoc
and
outreachy
will
have
us
waiting
for
a
while.
If
we
want
it
more
intermediate,
more
immediate,
it
might
be
like
hiring
a
contractor
to
do
it.
F
So
I
like,
in
my
current
role,
I
do
have
bandwidth
to
work
on
this.
I
mean
it's
definitely
not
going
to
be
a
solo
effort.
I
will
pull
in
other
folks.
I
know
there
are
some
folks
who
are
looking
to
work
on
what
tech
aspects
in
country
backs,
so
I'm
going
to
pull
them
in
and
we'll
see
how
that
goes.
We
can
have
contractor
as
a
another
option
in
the
end
for
sure,
if
that
doesn't
work
out.
J
We
still
have
some
there's,
there's
a
weird
historical
role
that
I
think
is
undercover
in
the
project,
which
is
some
level
of
caution
with
some
very
very
light
centralization
that
sig
arch
really
doesn't
own
right
now
and
that's
just
the
weird
separation
is
like
you
know,
contributor
ladder
you
know,
senior
code
owners,
slash,
sig
owners,
slash
sig
leads.
J
We
have
a
very
vague
structure
there.
I
would
like
to
see
that
clarified
and
refined
a
bit
because
cigar
aggressively
delegates,
but
then
we
don't.
We
do
not
have
a
fully
navigated
set
of
technical
resolution
things
outside
of
like
api
review
today,
so
I
think
that
that
aspect
of
it,
I
think,
can
be
separated
from
the
approval
part.
I
think
you
know
tim
covered
it
pretty
well
as
shrinking
the
shrinking
that
down
and
removing
the
need
for
it,
I
think,
is
a
good
goal.
D
D
G
Yeah
I
said
help
I
would
catch
you.
I
would
like
to
help
and
and
write
it
out.
I
would
like
to
not
write
it
completely
myself.
If
I
can
avoid
it
just
because
I'm
over
committed-
and
I
have
a
habit
of
doing
that-
but
happy
to
help-
write
it
out
and
try
to
make
it
as
precise
and
limited
as
possible.
I
Excellent
should
we
set
up
should
we
set
up
like
a
focus
design,
discussion
on
it,
because
that's
that's
something
that,
like
I
know,
I
have
notes
in
like
five
different
places
and
there's
also
some
stuff
in
my
head
that
I
haven't
written
down,
which
is
not
great
but
just
from
me
throwing
band-aids
on
that
plugin
over
the
last
few
years,
maybe
yeah.
K
Yeah
paris,
noting
on
me,
cough
flowery
because
so
I've
actually,
I
was
busy
kind
of
looking
at
the
release,
engineering
backlog
and
actually
there's
a
few
items
with
many
of
you.
I
will
ping
you
one-on-one
on
slack
about
it.
I
heard
the
d
word
delegation,
and
so
my
years
perked
up
and
so
basically
this
is
what
I've
been
focusing
on
as
program
manager
and
the
really
sig
and
release
team.
K
So
it's
great
that
some
of
you
are
already
aware
of
how
you
don't
want
to
over
commit,
because
this
is
a
huge
issue,
as
you
know
so
I
have.
I
can
give
you
some
pointers
on
how
to
shape
this.
I
think
you
really
want
to
be
careful
to
help
others
not
over
commit,
because
I
think
that
if
you
have
a
really
hot
topic
like
this
you're
going
to
have
a
bunch
of
committed
contributors
or
want
to
be
contributors
who
are
already
overstretched
on
10
different
topics.
F
Yeah
so
like
I
was
thinking
that
before
we
set
up
a
meeting,
we
do
a
little
bit
of
background
homework
on
yes,
justin.
Okay,
a
draft
to.
G
F
The
discussion
succeeded
I'll
laurie
I'll
work
with
you
to
get
okay
yeah.
I
think
we
can
one
up
and
then
yeah.
K
Yeah,
I
think
what
you
want
to
do
is
kind
of
like
figure
out
what
your
requirements
are
and
just
spin
up
a
simple
template
for
what
information
do
you
need
so
that
when
you
have
these
folks
come
to
a
session,
you
have
very
focused
questions
for
them
and
you
feel
like
you're,
totally
in
control
of
the
conversation
getting
the
info.
You
need
and
they
know
exactly
why
they're
there
and
then
they
go
off
and
do
their
other
things
so
yeah.
I
can
help
you
with
that.
K
K
No,
I
think
what
we'll
do
is
nikita
and
I
will
meet
we'll
come
up
with
a
template.
Then
she
will
shop
it
to
the
wider
circle
of
folks
speaking
up
here,
to
get
some
feedback.
I
think
you
know
that
would
be
her
plan
and
then,
after
everybody's
kind
of
like
comfortable
with
the
with
the
plan,
you
get
these
folks
who
are
not
attending
this
meeting
right
now
to
just
share
their
feedback
and
walk
away,
and
then
you
figure
out
a
way
to
update
them
on
progress,
a
communications
mechanism.
A
A
All
right,
we
are
moving
on
to
our
normal
everyday
business,
which
is
our
weekly
contributor
experience.
Meeting
first
sub
project
is
going
to
be
events
office
hours,
not
much
to
do
this
week.
So
I'm
going
to
skip
it.
Sorry
about
my
dog
community
meeting,
so
we
have
jenny
hosting
next
week
and
someone
else
or
next
month
and
the
week
and
the
month
after.
We
do,
however,
need
someone
to
host
this
month
to
get
the
work
started.
A
I
put
a
call
out
on
chat
if
you
have
anyone,
especially
I'm
looking
for
people
who
haven't
done
this
before
we're
kind
of
learning,
how
to
figure
out
how
kubernetes
work.
So,
if
you
have
someone
in
mind,
please
let
me
know
if
I
don't
get
someone
by
this
friday,
I'm
going
to
do
it
this
month
and
you
don't
want
that
contributor
summits,
not
much
to
report
here
steering
committee
election.
We
added
this
josh
and
ehor
are
to
the
election
officer.
We're
just
going
to
add
this
section
from
now
into
the
election.
L
Yeah,
so
we've
been
back
and
forth
with
the
steering
committee
on
dates,
we're
just
waiting
final
confirmation
on
dates.
The
election
officers
wanted
to
leave
more
time
in
the
two
sections
of
the
election
cycle
this
year,
because
people
are
distracted,
but
that
would
mean
changing
the
date
of
the
public
steering
committee
for
october.
L
A
Okay,
all
right
duly
noted,
community
management
need
to
know
chairs
and
tech
leads
email.
I
am
working
on
that.
I've
got
one
item
on
it.
That's
a
remind
oh
josh.
You
got
something.
L
L
A
Okay
and
I've
got
the
reminder
there
for
the
calendars.
Basically,
we
need
to
make
sure
that
they're,
inviting
their
own
project
lists
or
their
own
sig
lists
to
their
meetings
and
that's
what
gets
it
on
the
calendar
all
right.
Any
questions
around
community
management,
apac
coordinator
update,
is
no
status.
It
looks
like
they
canceled
the
meeting
last
time
so
I'll.
Add
that
in
there
anything
else,
community
management
wise
doesn't
look
like
it
github
manager.
I
have.
N
N
Go
yeah.
N
On
everything,
besides,
google
server
and
community
bridge
so
probably
have
no
updates
on
video,
contributes
and
other
stuff.
So,
with
community
bridge,
we
have
just
closed
our
key
to
q2
chapter
and
we
had
two
mentees
they've
been
working
on
kubernetes
project
and
both
of
them
have
successfully
passed
it
so
congrats
to
those
mentees
will
cnc
will
publish
the
announcement
and
all
the
details
about
this
program
later
this
month,
probably
next
week
or
so,
and
with
a
google
search
code,
we
still
have
pretty
good
progress.
N
So
we
have
a
bunch
of
monkeys
working
on
kubernetes
project.
We
have
just
passed,
we
should
have
just
finished
the
second
evolution,
and
most
of
them
are
still
working
on
their
assignments
and
will
have
their
final
news
about
the
google
stream
of
code
later
this
early
september,
and
that's
it
for
this.
F
Yeah,
so
the
product
security
committee
came
to
the
github
management
team
to
ask
about
setting
up
a
dot
github
repo
in
the
github
box
that
we
have
like
kubernetes
kubernetes.
If
you
already
see
a
signed
communities
client.
So
when
you
have
a
dot,
github
dot,
github
repo
in
any
oil
github
treats
that
as
special
and
any
files
in
those
in
the
dot
github
repo
are
considered
all
quite
so,
you
can
have
files
like
contributing
be
code
of
conduct
and
security.md.
F
Now
security.md
is
the
file
that
we
would
want
to
add
in
such
all
quiet
repo.
So
what
the
psc
was
doing
recently
was
that
they
were
adding
a
security.md
file
to
all
reapers
in
all
oils
and
creating
prs
for
it,
which
was
turning
out
to
be
cumbersome.
But
if
we
have
a
central
repo
like
this,
that
makes
it
easier
to
update
the
policy
if
we
ever
need
to,
and
we
don't
really
need
to
create
prs
for
all
arcs.
F
The
one
slight
catch
here
is
that
if
we,
if
you
clone
some
other
repo,
it
won't
like
the
security.md
file
won't
show
up
in
your
clone.
But
I
think
that's
fine,
and
the
other
thing
is
that
if
you
have
a
security.md
in
your
like
specific
repo
that
supersedes
the
oil
wide
one.
But
I
guess
that's
fine
too,
and
we
can
like
it's.
F
The
product
security
committee
said
that
they
take
responsibility
for
making
sure
that
all
of
that
is
in
sync
and
they'll
create
prs
to
update
it
if
needed,
we'd
be
using
the
oil
by
reaper
just
for
security.md
files.
For
now,
because
we
want
to
make
sure
like
code
of
conduct,
contributing
rfd
is
more
visible
and
is
also
available
when
people
clone
reverse
that's
kind
of
it.
So
joel
did
so.
The
issue
link
something
notes
in
the
chat
too
so
yeah,
so
joel
did
lgtm
it
from
a
psc
perspective.
F
I'd
like
to
get
an
app
from
country
beck's
perspective
as
well,
because
it
involves
kind
of
contributing
and
github
management
staff,
since
this
would
be
a
reaper
for
the
kubernetes
github
or
I
think
we'd
need
an
energy
dm
from
architecture
and
since
the
kubernetes
template
repo
is
owned
by
the
steering
committee.
I
guess
it
makes
sense
if
this
target
have
been
positioned
by
the
steering
committee.
But
I
like
from
the
steering
committee
headphone,
I
really
don't
have
like
concerns.
If
it's
on
someone.
I
Yeah,
I
was
just-
I
was
literally
just
gonna
say
that
same
thing
like,
I
think
that
the
siri
committee,
owning
the
template
is,
is
historical
at
lea,
at
least
from
my
perspective.
I
think,
with
this
one
I'd
say:
let's
make
it
owned
by
contrib
x
and
like
or
probably
like,
the
github
management
sub
project
or
something
like
make
it
owned
by
contrib
x,
and
then
I
would
be
supportive.
I
F
Cool
any
other
objections,
plus
ones
minus
ones.
For
us,
if
contrabax
is
okay
with
it
I'll
then
go
to
sig
architecture,
I'll,
probably
just
create
an
email
on
the
mailing
list
together,
lgtm
and
get
the
sweeper
created
and
at
the
psc
I
I
figured
it
out
like
I'll
sync
with
them.
For
this
one.
D
Actually,
I
actually
sorry,
I
have
one
thing
us
answering
a
message,
so
we've
begun,
starting
like
last
month,
we've
been
really
cleaning
up
the
orgs.
We
have
another
round
of
inactive
members
to
remove
the
pr
for
that
is
already
out,
but
the
thing
that
could
actually
use
some
help
with
is
opening
up
some
of
the
prs
to
remove
the
inactive
owners
they
have
all
been
linked
in
the
issue
in
there
and
if
you're,
like
people
want
to
look
at
examples.
D
So
the
the
other
open
issue
from
last
month
has
as
a
lot
of
them
nikita
actually
did
a
lot
of
legwork
there,
and
I
don't
know
how
many
pr's
he
opened
me
up
into
a
bunch
sort
of
cleaning
up
all
over
the
various
orgs,
but
any
help
there
would
be
appreciated.
F
Okay,
yeah.
I
think
we
could
just
stop
a
good
first
issue
later,
but
kind
of
feels
weird
slappy
good.
First
yeah.
K
Still,
I'm
still
compiling
my
spreadsheets,
I
love
spreadsheets.
So
basically
just
I've
put
the
link
in
the
agenda
for
anybody
who's
new
and
doesn't
know
what
dev
stats
are
there's
not
too
much
to
report
except
that
to
break
down
the
work.
I
spitballed
some
personas
that
were
floating
around
kind
of
in
people's
minds
and
made
a
tab
with
those
personas
in
the
doc.
K
So
if
you
click
on
the
link
where
it
says,
dump
your
data
points,
we
have
grants
helping
with
the
contributor
persona
in
april
on
the
company
program
manager,
our
officer
persona.
We
also
have
sig
chair
tech,
lead
steering
committee
and
process
minder
like
who's.
Looking
at
the
overall
health
of
the
whole
project,
and
then
the
last
one
is
cncf
persona.
A
Sorry
lori,
I'm
opening
my
can.
I
can
I
work
with
april
on
the
company
program
manager,
one.
I
know
it's
yeah.
You
want
one
person
per,
but.
K
Nope,
no,
I
think
the
more
the
merrier,
because
pairing
up
is
one
of
my
themes
for
the
week
relates
back
to
delegation.
So
we
need
just
the
chair
or
tech
lead
and
the
steering
committee
process
minder.
A
D
Like
more
engineering,
I
might
be
able
to
help
there.
It'll
just
depend
on
timing.
K
Sig
something
like
this
and
get
their
perspective
like
because
we
really
need
their
perspective,
we're
preaching
to
the
choir
here.
We
need
folks
that
are
currently
not
like
gung-ho
about
dev
stats
to
take
an
interest
in
what
data
they
could
collect,
and
so
I'm
gonna
just
reflect
back
what
josh
I
had
spoken
about
two
weeks
earlier.
We
want
to
try
to
pitch
dev
stats
without
talking
about
dev
stats,
because
it
hasn't
worked
in
the
past.
K
K
So
george,
would
you
like
to
craft
a
message
and
we
can
post
it
in
chairs
and
leads
channel
and
then
see
how
that
goes,
and
if
we
don't
get
a
response,
then
we
do
next
step
outreach.
I.
A
C
A
I
I
was
also
just
going
to
mention
some
of
the
steering
committee
kubernetes
process,
minder
persona,
whatever
message
that
you
send
out
to
the
chairs
and
tech
leads,
also
just
send
it
out
to
steering
a
case
at
io
and
then
like.
We
can
have
a
look
at
and
see
who
who
might
volunteer.
We
have
three
steering
committee
members
on
the
call,
but
also
there's
another
four
of
us
as
well
so
yeah
yeah.
K
Yeah,
I
mean
yeah,
if
you,
if
you
want
the
messaging
prepared,
we're
happy
to,
can
that
and
ship
it
over
to
you
to
share
with
them.
Otherwise,
maybe
your
personal
relationships
are
just
enough
to
get
somebody
to
absolutely
to
to
come
on
board
with
this,
like
their
involvement
here
actually
doesn't
have
to
be
that
we're
not
asking
them
to
actually
like
write.
K
Stats
or
anything
like
this,
we
just
want
to
actually
get
the
data
points
from
the
perspective
so
like
what
data
would
they
like
to
see,
and
then
they
would
have
maybe
at
your
next
meeting
they
would
carve
out
15
minutes
just
talk
about
that
and
and
again
populate
the
spreadsheet,
so
that
I
think
that's
really
the
only
ask
at
this
time
for.
A
K
A
Yeah
it's
just
some
days,
I
start
monday
and
then
it's
friday
before
I
know
it.
So
I'm
sorry
about
that
lori.
I
definitely
owe
you
more
time.
Don't
know
where
it
is
slack.
Infrared
do
have
a
quick
update.
We
had
this
bug
that
was
kind
of
popular
back
in
the
day
where
we
wanted
to
move
slack
in
for
into
its
own
sig
and
get
volunteers,
and
all
this
kind
of
stuff
and
noah
was
like
you
know
what
the
automations
are
running
smoothly,
we're
not
really
having
any
problems.
A
A
D
It's
just
a
quick
thing:
we
should
have
the
domain
transfer
soon
the
lf
has
done
their
part.
There
is
an
open
pr
and
kids.io
to
sort
of
finalize
that
we
should
be
fairly
close
to
launch.
O
O
There
love
to
get
that
closed
out.
I
probably
should
have
looked
at
it
this
morning
before
this
meeting,
but
I
have
not.
O
I
can
certainly
put
it
in
the
put
it
in
the
notes
after
I
stopped
talking,
because
I
can't
talk
and
click
at
the
same
time,
but
then
we're
gonna
move
on
to
the
testing
next,
one
of
the
kind
of
open
issues
with
that
is,
as
we've
talked
about
before
it
touches
the
docker
documentation,
and
it's
like
do
we
reach
out
to
docker-
and
you
know
update
that
just
so
that
we
can
be
more
effective
to
you
know,
because
the
user
is
what
matters
when
they
go
to
docker.
O
They
don't
care
that
it's
somewhere
else.
So
we're
kind
of
like
wrestling
with
that
and
I
don't
know
any
thoughts
on
on
how
you
guys
tend
to
solve
that
I'd,
be
curious
about
hearing
yes,.
A
A
O
We'll
we'll
wrap
that
up
into
the
neatest
package
of
spaghetti,
we
can
excellent
communicate
with
you
guys.
O
A
Okay,
awesome
contributor
site
bobbers.
I
think
we
just
we
just
went
through
this,
but
anything
to
add.
D
No
sorry,
I
think
I
mixed
up
in
my
head
contributor,
guide
and
contributor
site.
I
get
it.
A
All
right
other
business
tutorial
pr.
This
is
more
working
group
naming.
However,
I
ran
into
this
doing
a
workshop
in
the
weekend
and
there's
a
tutorial
page
in
the
docs
that
has
language
that
we'd
have
to
rewrite
the
whole
tutorial.
There's
no
way
to
just
like
fix
the
the
wording
there.
So
pulsar
did
a
pull
request
and
I
would
like
eyeballs
on
there
special
technical
ones,
because
we're
kind
of
replacing
an
entire
tutorial
we're
not
just
fixing
words.
So
if
you
have
cycles,
please
take
a
look
there.
D
So
this
we
should
try
and
like
move
on
sooner
rather
than
later.
I
I
hate
saying
this,
but
I
think
most
of
the
the
current
next
steps
is
on
you
kristoff
and
nikita,
but
like
we
also
need
to
flesh
out
like
fill
in
the
final
details
on
the
cap,
I'm
going
to
try
and
get
whatever
text
we
can
in
there,
but
once
that
is
in
a
happy
state,
we
will
really
need
to
start
blasting,
comms
and
doing
things
like
that
and
we'll
you
know
poke
the
the
marketing
team.
F
D
Do
we
what
deadline
do
you
think.
A
F
Works
for
me,
especially
since
august
25th,
is
the
1.19
release.
D
Yeah,
that's
that's
sort
of
why
there's
a
little
bit
of
urgency
on
it.
It's
it's
come
up
again
a
few
times.
I
know
a
lot
of
people
would
would
like
to
get
going
on
it
or
start
using
it.
F
Sounds
good,
so
I
guess
what?
What
are
the
next
steps
here.
D
D
It
is
then
just
like
updating
our
documentation
and
and
getting
the
word
out.
F
All
right
sounds
good.
I
can
take
a
look
at
stephen's.
I
was
staying.
We
looked
at
it
before,
but
I'll
do
another
run
through
stephen's
vr
and
see
what
we
need
to
update
there.
Can
someone
also
help
her
take
on
the
cap
stuff,
yeah.
F
A
Okay
and
then
I'll
add
that
here
normally
we
do
a
milestone
and
board
work
down,
but
we
have
like
a
full
agenda
we're
meeting
weekly
now,
so
I
don't
think
we
need
to
cover
that
now.
Last
thing
I
do
want
to
cover,
though,
is
we've
bob,
and
I
worked
on
our
introduction
to
contributor
experience.
We
went
in
my
basement
and
we
recorded
and
that's
going
to
be
a
cubecon
talk
during
virtual
kubecon
whenever
that
is
next
week.
Something
like
that.
A
But
anyway,
I
encourage
you
to
watch
it
because
it's
starring
all
of
you
in
here
so
please,
although
I
did,
I
did
want
to
mention
one
more
thing,
though,
is
that
thing
took
way
more
time
and
worked
than
I
thought
it
would
be,
so
they
are
going
to
this
virtual
kubecon's.
The
first
time
we're
doing
this
and
there's
going
to
be
a
lot
of
first-time
speakers
that
aren't
getting
like
the
normal
community
love
and
backing
that
they
do
when
they.
You
know
when
we
run
into
a
cube
content
to
do
a
great
job.
A
A
That
kind
of
thing,
I
think,
if
we
extend
a
little
bit
of
our
courtesy
and
our
love
more
than
usual,
I
think
it
will
help
a
lot
of
people,
because
I
know
a
lot
of
people
are
under
a
lot
of
high
stress
and,
as
usual,
I've
been
spending
a
lot
of
time
talking
to
people
just
listening
to
them.
Hanging
out.
A
I
know
things
are
rough
right
now,
so
if
you
just
need
to
talk
to
someone
or
whatever
my
plate's
always
open-
and
I
know
we've
we're
we're
doing
a
great
job,
I
think
talking
to
each
other.
I
know
a
lot
of
you
are
going
to
steven's
little
friday
friday
afternoon.
Let's
just
hang
out
and
shoot
the
breeze,
so
please
please
take
care
of
each
other
and
if
any
of
you
are
feeling
under
a
bunch
of
stress
and
just
want
to
yell
into
a
telephone
for
an
hour,
I
am
I'm
always
available.
A
A
A
A
All
right
great
welcome
newcomers
once
again
and
old
timers.
It's
always
good
to
see
you
stay
safe.
Everyone
and
we'll
see
everyone
in
a
week.
Give
you
six
minutes
back
yay
great
job.
Everyone.