►
From YouTube: [SIG ContribEx] Biweekly Meeting for 20230830
Description
[SIG ContribEx] Biweekly Meeting for 20230830
A
Hello:
everyone
welcome
to
the
August
30th
edition
of
the
bi-weekly
kubernetes
contributor
experience
meeting
before
we
head
on
to
the
agenda
of
the
meeting
a
couple
of
points
this
meeting
has
been
recorded.
So
please
be
aware
of
what
you
say
and
do
in
this
meeting,
and
another
thing
is
that
we
are
covered
by
the
kubernetes
code
of
conduct,
which
essentially
boils
down
to
just
be
nice
to
everyone
which
is
called
and
don't
hurt.
Anyone
sentiments
with
that.
Are
there
any
new
attendees
in
the
call?
A
So,
let's
move
it
events
Nigel.
Do
we
want
to
take
over.
B
Yeah
sure
yeah
we
had
our
meeting
this
week.
We
started
working
on
the
room,
layouts
and
so
that's
pretty
exciting.
It
feels
like
things
are
getting
closer,
at
least
on
Monday.
We
were
70
days
away,
so
we're
today
minus
that
minus
Monday
minus
as
we've
established
in
the
banter
period.
My
brain
is
not
working
this
morning,
but
yeah
we're
getting
close
to
kubecon.
We
seem
to
be
on
track.
B
The
things
that
we
are
waiting
on
now
is
to
hear
back
about
the
short
list
of
spots
for
where
the
celebration
is
going
to
be.
We
also
have
a
registration
open
if
you
haven't
registered
for
the
contributor
Summit.
You
may
now
do
that.
We
also
have
the
cfp
open
for
the
contributor
Summit
and
we
really
would
like
for
to
get
more
submissions.
B
So
I
will
put
links
in
for
all
that
stuff,
but
we
definitely
are
looking
to
get
more
participation.
More
people
signed
up
on
reg,
more
talk
submitted
to
the
cfp
other
than
that
everything
is
moving
along
pretty
smoothly
from
what
I
remember.
B
Right
right
right
so
yeah
the
the
kubecon
acceptances
went
out
and
so
yeah
we
once
we
make
the
next
announcement
and
people
have
more
of
an
idea
that
travel
is
going
to
be
approved
or
you
know
whatever.
What
have
you
for
like
what
the
blockers
have
been
so
far
might
get
more
participation,
and
it's
been
interesting
as
well
like
talk
to
people,
you
know
telling
them
about
it
and
they're,
like
oh
I've,
never
gone
before
and
like
trying
to
figure
out
like
why,
so
that
we
can,
you
know,
make
it
an
experience.
A
Nice
also,
a
couple
of
people
asked
about
like
what
kind
of
topics
can
be
submitted
to
the
contributor.
B
B
A
Nice,
if
they
can
submit
so
I,
pointed
like
anything
which
is
related
to
kubernetes
contributions
specifically
or
kubernetes,
is
a
project
if
it
helps
the
project
in
any
way.
Yeah.
B
B
Not
right
now,
I
will
prepare
more
remarks
for
next
time.
Yeah
I
haven't
really
summarized
the
notes
or
anything
but
yeah.
If
you
have
not
registered
please
register.
If
you
have
ideas
for
talks,
please
submit
them,
and
please
tell
your
colleagues
and
and
Associates
to
submit
as
well.
A
Food,
something
from
Bob
on
the
chat
and
I
think
it's
mostly
related
to
coupon
and
not
just
the
contributor
Summit
people
should
look
out
for
hotel
rooms
if
they
did
not
get
one
near
the
venue,
as
people
would
be
canceling.
C
D
B
D
Everyone
like,
as
soon
as
the
Roblox
announced
Booker
room,
and
then
you
know
when
you
know
if
you're
you're
going
or
not
cancel.
E
Yeah
for
people
who
are
trying
to
be
conservative
about
budget
I'll
point
out
that
you
can
stay
in
the
loop,
which
is
the
center
of
downtown
in
Chicago,
and
there
are
both
a
train
and
an
express
bus
that
go
to
McCormick.
E
D
E
So
yeah
yeah,
but
but
just
as
a
comparison,
I
hotels
in
the
loop
in
November
are
in
the
range
of
150
to
250
a
night.
It's
a
big
difference,
huge
the.
E
And
I
was
that's
what
I'm
going
to
be
eating
eating
the
so
and
and
I
figured
even
if
I
took
a
cab
every
day,
it
would
still
come
out
of
my
favor
yeah,
the
I'm
staying
in
the
Citizen
M.
If
anybody
wants
to
make
it
Citizen
and
built
a
brand
new
hotel
in
the
loop-
and
it
looks
nice,
the
so
and
and
we've
already
got
a
couple
of
other
cncf
people
staying
there.
So.
A
Awesome,
let's
move
on
to
mentoring.
Does
anyone
have
any
updates
there.
E
Checked
in
the
group,
mentoring
for
customize
should
be
the
the
cohort
should
be
done
by
now,
but
I
haven't
checked
in
on
the
results.
No.
D
A
I
think
we
had
a
couple
of
projects
in
LFX
as
well.
I
know
that
release
engineering
proposed
that
project.
Do
we
know
of
any
other
projects
that
are
there
in
LFX
this
cycle.
A
Okay,
we
can
probably
check
later
and
if
they
need
any
help,
we
can
probably
go
ahead.
A
It
looks
like
none.
Let's
move
on
to.
E
Contribution
we'll
make
one
remark,
which
is:
we
had
the
first
part
of
the
128
retro
yesterday
for
the
release
team,
and
we
had
a
long
discussion
about
how
the
shadow
program
runs
for
the
release
team,
because
there
continued
to
be
problems
with
low
low
completion
among
the
Shadows.
E
The
and
the.
E
Honestly,
I
think
part
of
it
is
nothing
to
do
with
mentoring
and
more
is
that
a
lot
of
the
release
team
has
not
felt
authoritative.
E
And
we're
discussing
that
in
Sig
release
as
an
as
in
they
didn't
feel
like
they
had
the
individual
authority
to
say,
dismiss
a
shadow
who
was
flaking
out
and
I'm
like
no
you're
the
lead,
you
can
dismiss
them
yeah.
There
isn't
someone
else
but
right,
but
the
problem
is
actually
it's
goofy,
because
when
the
release
team
was
kind
of
ad
hoc,
we
all
felt
that
we
had
as
much
Authority
as
existed
because
we
put
it
together.
E
But
since
the
release
team
is
a
system
now
people
are
worried
about
sort
of
going
outside
of
their
Lane,
and
so
we
need
to
sort
of
pull
it
back
and
say
no
already.
D
Do
you
know,
did
it
ever
get
merged
the
like,
if
you
flake
out
you're,
getting
removed
from
the
org.
E
Honestly,
no
rules
at
all
about
dismissing
shadows
and
for
that
matter,
dismissing
section
leads,
never
got
wrote
down
and-
and
that
was
one
of
the
main
things
we
addressed
is
that
it's
always
been
implied
that
people
could
get
dropped,
but
nobody
ever
actually
wrote
it
down
or
wrote
down.
You
know
what
the
process
is
I
think
so.
A
So
about
that,
I
was
going
to
say
that
Grace
has
I
think
a
PR
drafted
which
notes
down
what
would
happen
if
either
a
role
lead
or
a
shadow
is
inactive.
I
think
what
happens
if
a
shadow
is
inactive
is
written
was
already
written
somewhere,
but
this
release
cycle
there
were
topics
brought
up
on
what,
if
a
role
lead
is
inactive
and
I,
don't
think
we
ever
had
written
down
any
punitive
actions
like
getting
remote
from
the
org.
Those
were
only
corrective
measures
being
written
down
in
the
docks.
A
I
think
I'll
also
go
through
the
discussion,
which
happened
yesterday
and
yeah.
This
sounds
like
a
nice
opportunity
to
write
down
certain
things.
Yeah.
D
E
E
To
yeah,
so
no,
but
we
have
had
people
who
did
not
become
Oregon
members
until
they
became
section
leads
now
in
some
cases
it's
just
because
they
didn't
get
around
to
it.
But
there
have
been
a
few
cases
where
becoming
a
release.
Team
section
lead
was
the
only
reason
they
qualified
for
Oregon
membership
and,
and
that
would
be
one
we
would
consider
if
somebody
flaked
down
by
flight,
that
I
mean
not
quit
a
section
lead
but
sort
of
just
vanished
without
notice.
A
G
Right
yeah,
so
all
Shadows
are
part
of
the
or
or
are
made
org
members
to
join
those
certain
groups
in
the
forgot
that
I
forgot,
the
yaml
that
was
so
yeah
so
I
do
want
to
bring
I.
Do
want
to
talk
about
that
discussion
with
that.
G
Bob
brought
up,
maybe
not
at
this
meeting
Matt
sometime
later
about
if,
if
Shadows
are
dropped
and
if
Shadows
are
added
to
the
org,
because
they
were
because
they
are
because,
through
from
the
release
team
like
what
do
we
do
with
the
org
membership
I
think
that
should
be
discussed.
Maybe
in
a
I,
don't
know
this
meter
or
another
meter.
D
About
it,
it's
been
brought
up
multiple
times
like
there's,
open
discussions,
where
there's
comments
explicitly
stating
that
they
should
get
the
boot
I.
Just
don't
think
it's
ever
been
like.
This
has
certainly
been
discussed
multiple
times
before
yeah
in
various
retro
notes,
various
GitHub
discussions
and
issues
I.
Just
don't
think
it
made
it
to
a
guideline.
Yeah.
D
G
A
E
E
There
is
the
reason
why
we
originally
went
from
one
to
two
Shadows
per
section
for
110
was
because
Shadows
drop
out
and
that's
considered
normal
the,
and
so
we
want
that,
and
then
we
also
want
a
sort
of
general
rule
for
us
for
contribex,
because
well
the
release
team
is
the
biggest
place
where
people
get
sort
of
accelerated
org
membership.
E
It's
not
the
only
time
that
people
get
accelerated,
org
membership
and
and
I
feel
like.
We
need
sort
of
a
general
rule,
because
you
know
we
can
enforce
it
and
say:
hey
look
if
you
got
your
organ
membership
specifically
in
order
to
do
a
task,
and
then
you
don't
do
that
task.
The
organ
membership
disappears.
D
So
well,
it
doesn't
explicitly
call
out
the
the
task
stuff
like
if
you're
becoming
an
org
member
for
a
task.
We
did
increase
the
requirements
for
becoming
an
org
member
in
general.
D
E
It
happens
for
comms
the
because
I
mean
the
problem
with
you
know
is
that
you
need
to
have
organ
membership,
to
interact
with
the
Bots
and
and
if
somebody
volunteers,
to
do
certain
things
that
can
be
a
problem.
No.
D
You
don't
need
org
membership
to
interact
with
most
of
the
Bots
things
can
be
assigned
and
all
that
without
being,
if
you're
open
a
PR,
it's
okay
to
test,
but
like
assign
a
lot
of
the
other
things
labeling
that
that
works
without
org
membership
and
as
far
as
I
I
know,
we've
not
had
anyone
accelerated
in
comms
in
quite
some
time.
Okay,.
G
Oh
in
the
past,
I've
seen
folks
working
on
localizations
have
have
have
been
brought
into
been
bought,
been
brought
into
become
org
members
like
in
at
accelerate
rates,
because
localization
require
a
certain
number
of
approvers.
But
at
this
point
in
time,
we're
not
accelerating
people
working
on
localizations
anymore,
a
weird
adhering
to
the
same
policy
for
org
membership,
but
I've
seen
that
in
the
past.
D
Yeah,
the
the
only
other
place,
I
know
that
gets
accelerated.
Org
membership
is
when
a
project
is
being
donated
to
kubernetes,
in
which
case
there's
like,
if
they
did
not
previously
have
org
membership,
but
it's
still
contributed
the
project.
D
Somehow,
usually
they
will
just
be
brought
in
at
that
point
in
time,
like
a
few
like
select
people,
essentially,
if
it's
the
project,
they're
working
on
that
project
becomes
part
of
us,
they
then
have
this
track
record
of
all
the
PRS
and
all
that
anyway,
but,
like
I'd,
say
in
in
general,
we've
gotten
a
lot
better
as
a
project-wide
about
not
doing
not.
D
On
approved
memberships
and
US
says,
like
GitHub
admin
slash
like
new
member
coordinators,
we
are
actively
pushing
back
much
more
on
people
that
do
not
have
linked
I
like
a
good
enough
linked
items
for
for
organ
membership.
D
I'm
hoping
like
with
all
of
that,
this
going
forward
we're
generally
in
a
a
better
spot.
H
E
It
would
be
nice
if
it's
only
the
release
team
because
that's
easier
to
keep
track
of
since
we
actually
know
exactly
who
was
a
shadow
for
each
cohort,
the
because
that's
one
of
the
things,
one
of
the
reasons
why
they
need
a
process,
because
it
occurs
to
me
that,
even
in
earlier
release
teams
where
we
were
being
diligent
about
scrubbing
Shadows
who
dropped
out
I,
don't
know
that
anyone
outside
of
the
release
team
was
ever
notified
of
that,
and
so
you
know,
for
example,
the
org
membership
wouldn't
be
revoked
because
they
wouldn't
have
done
anything,
and
so
the
release
team
really
needs
a
written
process.
E
H
A
With
the
listing
and
the
GitHub
admins
as
well,
because
we
need
to
define
a
process,
maybe
something
like
hey.
These
are
the
list
of
people
who
have
not
progressed
towards
the
lead
role
in
the
release
team
or
are
not
selected
as
a
shadow
further,
and
they
have
gotten
credentials
the
kubernetes
or
credentials
just
because
of
their
involvement
as
a
shadow.
And
maybe
you
should
remove
them
something
like
that.
But
we
should
probably
discuss
this
further.
G
A
Yeah
anymore
comments.
E
Yeah,
it
did
occur
to
me
that
independent
of
that
discussion,
we
can
also
so
I,
mean
normally
we're
sort
of
bouncing
where
we're
removing
people's
organ
membership,
if
they
haven't
done
anything
in
18
months
a
year
now
a
year.
Okay,
we
might
want
to
also
look
at
people
like
if
we
could
craft
this
query,
which
would
be
hard
like
one
of
the
things
I
would
want
to
look
at
is
people
who
get
their
organ
membership
and
then
have
no
significant
activity.
E
You
know,
like
they've,
got
their
org
membership
in
the
last.
You
know
three
months
or
whatever
and
they've
had
no
significant
activity
since
then,
wouldn't
necessarily
be
an
automatic
removal,
but
it's
definitely
something
to
look
at
and
maybe
ping
their
sponsors
and
act.
Ask
what's
going
on
a.
F
D
Yeah,
the
the
one
issue
like
issue
with
automation,
we've
talked
about
this
a
bit
as
get
about
get
abandons
is
that
we
do
explicitly
have
roles
that
we're
that
do
really
interact
with
GitHub
directly,
like
our
code
of
conduct
committee
are
slack
admins
outside
of
you
know,
approving
requests
for
new
channels,
but
not
every
slack.
Admin
is
on
the
the
list
to
to
do
that,
and
then
there
are.
D
There
are
like
leadership-ish
type
things
where
you're
not
might
not
be
super
like
you'll
still
have
activity
in
GitHub.
Well,
this
doesn't
apply
to
new
new
people,
so
never
mind.
Oh,
it's
like
there
are
some
at
least
cases
where
a
automated
process
would
not
would
not
work.
E
A
Let's
say
it
can
be
done,
but
we
have
to
see
how
much
time
it
takes
and
what
what
do
we
get
out
of
it.
But
we
also
need
to
like
Define
things
like
what
do.
A
We
consider
a
significant
contribution,
because
this
was
also
brought
up
when
we
amended
the
new
membership
guidelines,
because
somebody
can
work
on
a
cap
for
maybe
two
years,
which
is
a
significant
piece
of
work,
and
people
can
also
work
on
like
multiple
PR's,
which
can
be
moderate-ish,
which
can
be
considered
significant,
so
yeah,
but
but
again,
like
just
a
quick
time
check
on
this
I
think
we
shall
for
sure
like
take
it
up
as
a
follow-up
item,
and
this
would
require
a
long
deliberation.
A
Okay,
none
moving
on
to
contributor
forms
does.
F
We
are
working
on
sorry,
I
lost
the
notes
working
on
the
deprecation
of
the
Yum
and
apt
dot,
kubernetes.io
repos,
getting
that
messaging
kind
of
squared
up
and
out
the
doors,
not
a
little
bit
of
time
on
that
yesterday,
as
did
Bob
yeah
we're
also
working
on
automation
directory
that
will
help
document
how
things
are
automated
and
where
they're
automated.
F
That
kind
of
thing
when
it
comes
to
comms,
because
there's
a
lot
going
on
kind
of
behind
the
scenes
and
we
have
one
blog
in
Flight,
I
didn't
see
another
one
about
the
release
team.
So
that's
what's
getting
worked
on
in
columns
any
questions
for
us.
C
A
Thank
you,
Chris
moving
into
contributor
documentation,
Bob
Craig.
D
H
So
make
good
progress
in
getting
various
folks
to
test
the
configuration
I
had
in
the
fork
with
the
container
image,
the
I
kind
of
put
what
I
was
going
to
say
in
the
notes.
I
had
the
array
in
case
you
don't
want
to
verbatimize
the
the
the
blocking
issue.
H
Kind
of
right
now
is
that
I
had
kind
of
tried
to
bite
off
too
much
in
the
first
Fork,
which
was
not
only
to
create
the
configuration,
but
also
to
pre-build
that
configuration
as
an
image
and
that
way
it
improves
startup
time
and
also
reproducibility,
as
well
as
allowing
Forks
to
easily
pull
that
exact
same
container
image.
H
The
you
know.
Obviously,
the
container
build
process
requires
prow
and
Google
Cloud
builds,
which
I
don't
know
and
have
no
expertise
in
so
other
folks
were
trying
to
help,
and
the
question
came
up
about
whether
or
not
you
know
where,
essentially
that
configuration
should
live
and
how,
whether
that
configuration
should
be
Consolidated
across
multiple
projects
or
be
specific
to
kubernetes.
There's
a
whole
bunch
of
unanswered
questions
that
we're
working
with
Kate's
infra
to
get
good
answers
to,
but
that'll
take
a
little
bit
more
time.
H
So
in
order
to
unblock
getting
the
configuration
into
KK,
I've
just
decided
to
go
ahead
and
essentially
not
do
the
pre-build
and
leave
the
configuration
in
place,
which
means
that
every
time
you
start
a
session
with
a
Dev
container,
whether
that's
local,
encoder
or
in
code
spaces,
it
will
build
the
container
from
scratch,
which
will
take
a
little
bit
more
time.
But
it'll
get
the
configuration
there
and
it
decouples
the
effort
to
get
the
container
pre-built
published
so
we'll
Endeavor
to
get
that
done
also
before
kubecon.
H
H
Then
I
guess
the
next
step
would
be
to
update
the
gates.gov
onboarding
training
to
also
reference
that.
A
No,
do
we
want
to
discuss
the
devil,
docs
location
thing.
Bob
I
saw
your
comment.
A
couple
of
hours
about
yeah.
D
All
right
I
forgot
to
put
my
My
Name
by
this
one,
so
we
have
gone
back
and
forth
on
this
for
a
while,
there's
been
some
pushback
on
moving
docs
outside
of
k,
Community
to
other
places,
but
frankly
like
it
is.
It
is
hard
to
find
and
discover
this
stuff
there.
It's
part
of
the
reason
why
we
started
serving
stuff
up
on
the
website
to
make
it
more
discoverable
part
of
the
the
problem
is:
there
are
limitations
with
the
current
method
of
like
ingesting
it
from
other
locations.
D
D
This
is
mostly
because
it
like
it
stays
versioned
with
the
project
it
would
like
when
you're,
when
you're
searching
for
stuff
like
and
you're
looking
for
scope
stuff
in
there,
you,
like
you're,
looking
in
the
repo
you're,
not
going
to
go
to
k
Community
to
search
for
this
stuff,
and
it's
even
more
difficult
with
how
you
know
it
works
for
us
with
everything
broken
down
by
Sig
in
terms
like
organizing
the
information,
but
that
doesn't
work
for
someone
that's
coming
in
and
trying
to
actually
like
you
know,
hunt
down
some
devil
docks.
D
The
other
thing,
like
the
alternative
that
I
think
of
of
it
being
sort
of
version
alongside
KK,
would
be
to
just
push
everything
to
kate's.dev
and
have
all
our
docs
regarding
at
least
our
core
contributing
to
kubernetes,
be
there
I
would
also
like
I
would
love
to
move
our
just
general
contributor
guide
there,
instead
of
having
to
like
move
like
pull
them
in,
but
for
that
we
will
probably
need
to
get
a
bit
more
consensus
and
need
to
get
sort
of
at
the
community
at
large.
Just
because
moving
this
stuff
is
a.
D
It
is
a
community-wide
thing.
I
personally,
think
at
this
point,
gates.dev
has
kind
of
you
know
proven
itself
to
be
a
good
thing.
More
people
are
linking
to
it
directly.
Instead
of
you
know,
to
a
markdown
file
in
in
k,
Community,
but
but
I
recognize
I
recognize
my
own
bias.
There.
A
One
other
thing
that
I
felt
with
moving
docs
is
SEO
or
discoverability
of
the
new
location.
I
have
personally
faced
problems
finding
products
since
it
they
were
moved
from
the
distant
prayer
report
to
a
new
repo
and
there's
a
new
website
for
products,
often
when
I
Google,
something
they
don't
result
in
a
query
to
the
new
site.
I
have
to
go
to
the
GitHub
and
then
I
get
a
link
to
the
new
Docs.
So
things
like
this
have
to
be
taken
care
of
when
we
move
Docs.
D
Yeah
that
is
actually
like
a
again.
We
should
follow
up
with
them
about
boosting
the
SEO
of
that
one.
It's
also
a
little
hard
because,
like
prow,
is
literally
inside
K
test
infra,
instead
of
being
its
own
separate
thing
and
there's
a
lot
of
sort
of
like
interdependency
and
links
in
that
right
now,.
A
Yeah,
due
to
this
reason,
I
was
favoring
using
the
like
the
generate
content
thing
in
contributor
site
and
keep
the
markdown
where
they
are
right
now,
so
they
would
be
surfaced
at
two
two
places
at
the
same
time,
but
I
do
like
like.
If
you
can
get
the
SEO
right,
then
I
think
we
can
move
the
docs
to
kds.f.
D
Yeah
that
the
one
pro
like
well,
there
are
multiple
issues
with
the
a
little
ingest
script.
D
D
The
reason
why
we
wrote
the
markdown
style
guide
was
to
make
it
so
that
way
it
would
work
in
both
places
so
like
if
we
have
had
this
happen
before,
where
people
make
changes
in
the
original
location,
it
gets
pulled
into
the
website,
and
then
it
breaks
the
the
page,
because
it's
not
it
doesn't
render
correctly
or
just
has
like
broken
links,
and
things
like
that.
A
D
Yeah
I
I
am
both
very
proud
and
also
not
proud
of
that
crazy
amount
of
bash.
That
I
wrote.
D
That
understands
markdown
to
be
able
to
pull
out
the
links
that
way,
because
a
lot
of
the
the
complicated
mess
is
trying
to
deal
with
all
the
different
kinds
of
ways
of
linking
in
markdown.
D
So
if
just
using
a
a
library
that
already
understands
it
and
can
break
out
the
links
and
can
basically
you
know,
do
the
substitution
that
would
be,
you
know,
simplify
things
significantly,.
A
Makes
sense
any
more
comments
on
the
devil,
Ducks
location.
A
Cool,
let's
move
it
back
to
Nigel
moderation
in
Media.
B
Hello
yeah,
the
main
update
is
that
things
are
not
as
bad
as
they
seemed
before.
B
B
My
guess
is
that
duplicating
the
zap
so
many
times
like
something
got
worked
inside
of
it
and
like
for
some
reason
like
re-authing,
wasn't
worth
turning
it
on
and
off.
Wasn't
working,
so
I
just
like
made
a
whole
new
one
from
scratch
and
that
resolved
the
issues
of
the
contracts.
I,
don't
know
what's
going
on
with
spline,
but
I
did
see
that
the
release
meeting
went
up
from
yesterday
and
so
that
seemed
to
work.
B
And
then
there
was
a
networking
video
that
went
up
and
I
messaged
in
the
networking
Sig
channel
to
just
be
like
hey,
y'all,
I,
haven't
seen
any
uploads
in
ages.
Like
are
you
all
still
doing
things
the
same
way
and
didn't
really
get
a
response?
Just
one
person
I
was
like
yeah.
No
I
see
recent
videos
in
there
I'm
like.
Could
you
link
them
to
me?
B
Please,
because
I
don't
see
them
and
I
didn't
get
a
response
there,
but
essentially
looking
at
the
volume
of
videos
I'm,
just
like
something's
going
on
I,
don't
know
what's
happening,
but
for
now
I
know
that
the
automation
that
we
have
the
zapier
stuff
is
working
for
the
parts
that
we
turned
it
on
for.
F
B
F
But
Europe
I
mean
yeah
yeah.
B
Okay,
you
need
it
yeah
just
doing
some
traveling
around
before
Bilbao
open
source
Summit,
but
still
working
yeah.
We
can
definitely
take
a
look
at
it,
but
there's
not
much
that
we
can
see
like
something's,
fairly
opaque
from
from
our
side
and
so
like
I
have
to
I
guess
individually,
reach
out
to
these
six
and
just
like
yo.
What's
going
on
with
your
recordings,
like
maybe
networking
Gateway
API
decided
that
they
were
going
to
record
differently,
maybe
when
you're
up
on
a
holiday
over
the
summer,
nobody
was
having
meetings.
B
B
And
then
for
the
slack
stuff,
I
don't
know
if
Bob
wants
to
say
a
word
about
the
org
Channel
org
members
Channel.
Oh.
D
Yeah,
so
we've
discussed
the
the
problems
of
the
slack
channels
here
in
the
past,
and
we
decided
to
move
forward
with
basically
just
taking
the
old
careers
contributors
Channel
and
changing
that
to
kubernetes
new
contributors,
just
because
people
would
basically
pop
in
there
and
then
be
like
hey
I'm
new.
Please
help
me
and
most
of
our
maintainers
had
essentially
turned
it
off
and
left,
and
we
have
a
new
channel
kubernetes
org
members.
D
D
The
slack
moderators
have
also
been
told
to
be
very
aggressive
with
the
moderation
in
there
in
terms
like
if
someone
Pops
in
just
like
asks,
you
know
hi
I'm
new.
Some,
please
Mentor
me
to
like
remove
the
message
and
like
essentially
remove
them
from
the
channel
and
direct
them
towards
the
kame's
new
contributors.
Channel.
B
D
We
have
we
have
similar,
not
the
booting,
but,
like
you
know,
here's
don't
ask
you
know
like
look
at
these
resources
before
you
ask
questions
in
the
the
new
the
careers
new
contributor,
one
similar
thing
when
you
join
the
channel,
but
that
does
not
stop
people
from
from
from
doing
that.
So
is.
B
It
is
it
a
channel
that
you
have
to
manually
join,
or
is
it
one
that
you're
popped
into
when
you
join
the
the
works
you
have
to
you
have
to
manually
join
it
interesting.
Okay,.
H
I
I
just
went
there
and
says
you'll
join
this
channel
when
you
send
this
message
see
a
join
button.
Interesting.
D
B
H
D
Weird
that
one
we
might
have
to
follow
up
on
the
actually
the
other
follow-up
action
that
we
have
at
this
point
would
be
to
update
our
Docs,
for
we
have
you
know,
locations
that
say:
join
crease
contributors,
okay,
ray
just
joined
and
did
not
get
have
a
send
message
thing
so.
H
D
C
B
B
E
Yeah
yeah,
since
you
have
to
be
an
organ
member,
to
attend,
you're
gonna
need
to
either
be
an
org
member.
Well,
we
do
make
exceptions
because
we
have
guest
speakers.
D
Yeah
we
we
have
had
like
previously
members
of
the
TOC
and
some
other
groups
attend
to
do
sessions
yeah,
but
that
is
like
you're
you're
gonna
have
to
be
very
like
have
something
killer
to
be
able
to
to
do
that.
A
F
B
D
A
No
questions
awesome.
Moving
on
to
GitHub
management,
we
have
10
minutes
and
three
more
topics
of
discussions
just
to
try
and
check
Bob
Priyanka.
Do
you
want
to
add
anything.
D
D
One
thing
I'm,
sorry,
the
one
thing
I
I
think
would
be
like.
We
do
actually
have
a
kubernetes
Enterprise
account.
Now
that
can
it's
the
the
GitHub
account
that
you
can
basically
join
multiple
orgs
to
oh,
okay,
yeah,
but
we
we
are
like
we
haven't
pursued,
you
know
integrating
all
the
orgs
and
all
that
yet.
A
I
think
one
other
thing
would
be.
This
is
a
BSA.
The
org
audit
would
probably
happen
next
month.
We
plan
to
give
like
two
weeks
of
Headway
after
we
generate
the
list
that
if
anyone
feels
like
they
should
be
part
of
the
arc
but
are
going
to
be
incorrectly
removed,
they
should
come
in
there
and
we
probably
won't
mention
people
in
the
issue
deliberately
just
so
that
we
know
who
is
part
who
is
like
actively
looking
at
announcement
should
Dev
and
who
is
not.
A
It's
at
this
point
we're
just
auditing
the
list
of
people
to
be
removed,
because
the
number
is
quite
large
and
we
have
to
do
some
checks
before
we
publish
the
list
Priyanka.
Please
go
ahead.
A
E
And
the
steering
action
is
currently
in
progress,
and
this
is
actually
the
first
time
we
have
done
two
elections
concurrently.
So
it
was
nice
to
see
that
that
worked.
E
E
The
and
it's
a
good
Slate.
From
my
perspective,
we
have
11
candidates
for
the
Ford
steering
committee
positions.
So
not
only
you
know,
will
we
get
a
good
steering
committee
out
of
this,
but
we
then
also
effectively
have
a
bench
in
case
anybody
needs
to
drop
out
of
steering
before
the
term
is
up,
which
is
a
concern
that
we
always
have
if
we
don't
have
a
lot
of
candidates,
the
so
so
that's
in
good
shape
and
and
in
fact,
I
have
it's
in
good
enough
shape.
E
E
I
the
I
mean
in
cncf
land
I'm,
trying
to
actually
get
some
help
for
building
up
the
test
infrastructure
for
electo,
because
there
are
a
bunch
of
things
that
we
don't
have
automated
testing
for
right
now,
such
as
the
container
image
build,
and
that
came
up
as
a
problem
when
starting
the
steering
election
the
so.
A
E
Yeah,
that's
exactly
like
I
mean
I'll.
Tell
you
with
within
the
community.
We
had
a
few
people
who
are
like
okay,
I'll,
throw
my
hat
in
the
ring
for
steering
if
we
don't
have
enough
candidates
and
none
of
those
people
had
to
step
forward.
E
So
it's
great
to
have
that
many
people
who
really
want
to
do
steering
this
time
around
and
can
make
the
time
it's
awesome.
E
Resolved
so
that
people
know
about
it,
is
we've
had
a
de
facto
rule
for
a
while
that
people
can't
be
on
Code
of
Conduct
committee
and
steering
at
the
same
time,
but
that
rule
has
never
been
formally
documented
anywhere,
and
that
became
a
real
issue.
This
election,
when
we
had
a
candidate
running
for
both
Stephen
drafted
something
for
it,
but
it
had
some
issues
so
we're
still
working
on
text.
For
that.
A
Yeah
I
think
we
need
to
work
on
it
essentially
stating
yeah.
A
Cool,
if
there
are
no
questions
for
elections,
we'll
go
back
to
priyanka's
point,
so
Priyanka
wanted
to
update
on
The
Parables
incident.
So
the
recent
report
management
changes
are
stable.
A
Now
there
were
some
teams
who
were
getting
removed
from
repos
due
to
bad
configs,
but
they
have
also
been
resolved
and
just
as
a
PSA,
if
you
still
see
any
problem,
if
anyone
is
seeing
the
recordings
just
spoke
on
GitHub
Management
on
how
like,
if,
if
you
are
removed
or
not
at
some
point
from
my
side,
probably
in
the
next
year,
certain
PLS
meeting
in
September,
we
should
raise
this
up
changes.
A
D
A
D
For
working
through
it,
that
was
that
was
I,
know
difficult
to
get
through.
A
A
D
Yep
and
that's
pretty
much
it
probably
Friday
after
or
Thursday
afternoon,
Friday
morning,
I
will
you
know
export
the
list,
move
everyone
over
to
the
new
one
and
essentially
lock
down
the
the
previous
one
and
then
we'll
all
be
using.
You
know
a
career's
dial
address
for
everything.
D
Yeah
think
about
like
when
we
migrated
kadev,
we,
it
was
actually
like
a
very
smooth
transition,
so
hoping
there
won't
be
won't
be
any
issues.
A
Nice
and
with
that,
we
just
have
one
minute
left
and
we're
at
the
end
of
the
agenda.
Does
anyone
want
to
bring
up
anything
which
is
not
on
Legend.
C
Yes,
so
I
was
looking
for
always
to
contribute
and
get
involved
in
the
seek
continuous
committee
and
I
came
across
these
two
things
called
epic
coordinator
and
new
contributor
Ambassador
in
the
role
handbooks
and
so
I
was
interested
in
how
I
can
get
get
involved
in
that
roller.
Is
that
still
relevant,
because
I
see
that
they
have
not
been
updated
for
a
long
time.
A
I
can
tell
about
epic
coordinators.
Epic
coordinators
hasn't
largely
met
in
the
last
three
years.
Does
anyone
have
any
thoughts
on
new
contributed
ambassadors?
We
can
also
potentially
take
this
up
async
in
the
channel.
D
D
A
I
think
you
should
just
poke
on
this
contribute
Channel,
and
we
can
take
things
forward
on
the
initiatives
that
we
are
currently
working
on
and
who
needs
help.
That's
that's
a
great
way
to
like.
Let
people
know
that
you
want
to
work
on
things
and
personal
suggestion.
Also
do
let
like
what
are
your
interest
areas
like
if
you
have
any
specific
area
that
you
want
to
work
on
in
contributes.
That
would
be
really
helpful.
Then
people
can
help
you
much
better.