►
Description
[SIG ContribEx] Weekly Contributor Comms Meeting for 20230908
A
Hello
and
welcome
to
the
Friday
September
8th
edition
of
the
contributor
comms
team
meeting,
I'm
your
host
Jasmine
fields
and,
as
usual,
a
reminder
that
we
operate
under
a
code
of
conduct
which
essentially
says
to
be
respectful
of
your
fellow
speakers
and
attendees
and
generally
be
excellent
to
each
other.
And
the
cats
are
running
all
over
my
screen
and
popping
things
up
and
that's
fine.
A
Not
distracting
at
all
cats,
why
do
you
all
want
to
be
in
my
space
today,
but
to
kick
things
off?
We
also
like
to
try
to
offer
an
opportunity
at
the
beginning
of
the
meeting
for
anyone,
who's
new
to
unmute
and
say
hello
or
to
post
in
chat
and
say,
Hello
tell
us
a
little
bit
about
yourself
and
why
you're
here
and
you're,
it's
also
totally
optional.
A
A
B
I
mean
I
think
the
biggest
thing
from
last
week
was
the
Linux
repository
change
to
packages.case.io,
at
least
from
my
perspective,
that
got
out
the
door
very
quickly,
so
yeah
I'm
actually
I'm
actually
telling
telling
folks
about
that
in
a
way
of
like
yeah.
This
is
how
we're
doing
it
in
kubernetes
kind
of
thing.
Right,
like
you
know,
it's
pretty.
B
B
C
B
Yeah
yeah,
yes
totally,
so
the
I
think
the
biggest
thing
is
just
copy
paste
from
the
announcement
right
like
you
know.
Yes,
there's
this
thing
that's
happening
and
yes,
there's
the
outcome,
but
make
sure
you
like
just
take
the
language
that
already
is
crafted
because
yeah
there
was.
There
was
some
concern
about
calling
out
certain
organizations
and
not
others,
and
you
know
we
just
want
to
make
sure
that
folks
understand
that
the
thing
that
was
changing
to
the
thing
that
is
so
yeah.
A
A
B
B
It's
becoming
this
and
then
the
next
one
you
could
be
like
hey
our
apt
and
yum
repositories
are
changing
to
this.
You
know
it's
just
you
know,
mix
it
up
a
little
bit
and
like
I,
actually
throw
the
URLs
in
that
people
can
search
their
infrastructure,
for
you
know,
give
them
something
grepable.
You
know
that
they
can
find
and
be
like.
B
B
Yeah
feel
free.
We
worked
very
hard
crafting
this
messaging,
so,
as
you
can
see
the
folks
that
contributed
to
it
Bob
me
Jeremy,
Marco
Tim.
It
was
a
pretty
high
level
thing
that
like
they
walked
in
and
it's
like.
We
need
to
get
us
out
the
door
now
and
it
was
like
last
Thursday
I
think
is
when
they
came
to
us.
I
forget
but
yeah,
not
as
impactful
as
the
registry
change,
but
still
gonna
affect
some
percentage
of
users.
B
A
A
B
D
B
B
A
B
B
C
D
C
B
B
A
C
A
A
C
H
A
G
B
A
A
C
A
A
A
A
This
is
a
project,
that's
open
to
anyone
who
wants
to
contribute
to
it.
We
try
to
make
it
as
easy
as
possible
for
folks
unfamiliar
with
the
group
to
contribute
natish
and
oh
gosh,
so
Jay.
It
both
helped
me
last
time
with
some
of
the
management
aspects
of
it.
Our
pit
is
going
to
help
me
with
management
of
it.
This
time
nitish
as
well.
I
think
maybe
one
other
person
also
mentioned
interest
in
helping
with
management
of
it,
which
is
wonderful,
it's
one
of
our
kind
of
big
projects.
A
G
A
A
C
A
A
A
So
this
involves
going
through
the
schedule
and
figuring
out
what
we
want
to
talk
about.
Of
course,
at
the
beginning
of
the
event,
it's
mainly
like
a
general
reminder
that
kubecon
is
starting
and
I
like
to
send
out
information
about
when
registration
is
open
and
a
reminder
that
the
contributor,
Summit
and
colos
will
be
happening
before
the
main
event
granted.
Also,
nobody
understands
how
that
works,
and
then
the
day
of
the
colos.
In
this
year's
case,
the
colos
and
the
contributor
Summit
will
be
happening
at
the
same
time.
A
C
G
A
B
A
A
So
we'll
write
out
these
descriptions,
so
some
of
these
are
keepcon
begins
reminder
about
Day,
Zero,
Colo
events,
registrations
open,
also
reminder
for
reminders
for
things
that
will
be
happening
later
in
the
week
of
kubecon.
So
this
is
a
reminder
for
the
Sig
meet
and
greet
which
will
be
happening
much
later.
A
This
column
will
be
blank,
we'll
start
sharing
it
with
people
and
saying
hey.
If
you
want
to
write
a
tweet
for
us
for
kubecon,
just
put
your
name
in
the
owner
part
and
fill
that
out
by,
we
should
pick
a
deadline
for
people
to
write
their
treats
by
and
then
once
they've
written
their
tweet,
because
tweets
have
a
limit
I
like
to
make
sure
that
it
fits
in
the
Tweet
in
case
it
needs
rewriting
before
we
actually
schedule
it.
A
I
don't
always
use
this
column,
but
it's
something
for
me
when
I
manage
this
when
I'm
like
putting
them
into
the
tools.
So
if
you
find
it
useful,
if
you're
one
of
the
folks
who's
going
to
help
me
manage
the
the
Tweet
project,
you're
welcome
to
use
that
I
also
have
this
column,
which
I
think
in
future
ones.
I
have
changed
the
name
of
to
local
time,
because
before
I
did
the
changing
buffer
to
the
local
time
zone
of
kubecon
thing
I
had
to
like
translate
it
into
Pacific
time
and.
A
Was
not
good,
so
you
probably
won't
need
the
owner's
local
time
column
unless
it
helps
you
as
you're
writing,
tweets
or
anything.
It
is
there
for
your
use,
but
you
probably
won't
need
it
and
then
for
the
folks
who
are
helping
me
manage
this.
The
other
column
in
here
is
scheduled,
which
will
all
be
no
at
the
beginning,
and
it's
for
when
you're
going
through
and
actually
putting
these
tweets
into
buffer,
saying
yeah
I
already
did
that
one.
A
A
A
A
B
A
A
Perfect,
we'll
think
on
that.
After
this
call,
also
by
the
way
the
student
committee
election
is
still
going
on
for
anyone
who's
an
org
member,
you
might
be
eligible
to
vote
you're,
probably
eligible
to
vote
if
you're
not
you're,
welcome
to
file
an
exception
so
do
check
out
the
steering
election
for
anyone
who
is
involved
in
the
community
enough
to
care.
C
A
G
C
A
A
A
B
Oh
yeah,
sorry
I
meant
I
forgot
to
mention
that
I
yeah
I
was
in
here
tinkering
with
buffer
writing
these
tweets
and
such
they
have
an
AI
tool
in
there
now
under
the
create
section
and
I
just
typed
in
kind
of
what
we
do
and
who
like
who
to
Target,
and
it
spit
out
that
blurb
about
our
group,
which
is
like
beautiful.
It's
a
beautiful
blurb
right.
C
B
A
C
A
A
B
C
B
B
It's
really
useful
for
that.
I've
actually
coded
a
couple
programs,
almost
100
by
like
I've,
broken
out
the
functions
and
just
be
like
write
me
a
function
to
do
this
and
go
write
me
a
function
to
do
this
and
go
and
like
glue
it
all
together
and
then
say:
okay,
make
this
all
work
together,
and
it's
just
fixes
it.
It's
crazy.
A
B
D
A
C
A
A
B
A
B
A
G
A
B
D
I'm
getting
to
work
with
kids
I'm,
getting
to
work
with
the
release
team,
so
many
parts
of
the
project
just
through
lwkd
and
right
now,
I'm
even
working
to
bring
something
new
with
lwkd
like
not
just
summarizing
a
cap
but
also
bringing
in
the
authors
and
asking
them
why?
What
changes
does
it
make
in
people's
life
in
the
people,
for
the
people
who
are
actually
working
on
those
spots
and
stuff
like
that?
So
it's
something
clear,
really
really
exciting
and
we're
actually
enjoying
it.
A
B
E
D
G
G
B
B
Yeah
but
like
opening
up
to
a
Channel
with
more
than
just
the
initial
contributors,
I
think
is
a
very
smart
idea,
because
there's
people
in
that
channel
that
are
like
you
know,
oh
I-
could
help
with
that,
sometimes
and
yeah.
There
is
an
advantage
to
keeping
it
in
a
bigger
audience.
Channel
right,
like
you'll,
get
more
contributors,
but
you
might
also
get
some
stuff.
You
don't
want
to
so
there's
probably.
B
A
D
B
A
A
Around
and
code
Rangers
in
here
too,
but
good
range
are
also
not
usually
on
our
calls,
but
wonderful
I'm
so
excited
that
you're
having
fun
learning
about
it
and
doing
stuff
with
it.
We
were
talking
about
how
to
do
news,
which
is
something
that
I've
been
trying
to
learn
as
well,
so
we'll
learn
it
together.
A
D
A
Yeah,
oh
yeah
I
can
I
can
grab
that
it
was
I
inherited
it
I
did
not
create
that
list
either.
Thank
you,
but
when
we
inherited
the
podcast
there
was
a
whole
list
of
news
resources
that
we
use.
I'll
put
it
in
the
chat
for
now
like
oops
yeah,
it's
quite
long,
but
those
are
some
of
the
places
that
we
check
for
news
for
the
kubernetes
podcast.
B
B
C
C
G
G
A
Cool
we
do
have
less
than
15
minutes
left,
so
I
should
probably
actually
run
through
the
board
real,
quick
Frederico
by
the
way
posted
his
updates
in
the
channel.
If
anyone
needs
this
all
right,
let's
do
the
board
and
I
don't
have
my
GitHub
logged
in
so
I
won't
be
able
to
do
these
reviews
real,
quick.
C
A
A
A
B
A
I
thought
he
said
that
he
I
thought
he
meant
that
he
was
going
to
like
put
in
this
commit
and
then
do
another
commit
to
fix
those
things
which
I
was
like.
That's
totally
cool,
because
this
is
great
too
then
he
was
like
no
I'm
gonna.
Do
it
in
this
one
I
was
like:
oh
I
will
hold
so
at
this
point
it
should
be
ready
for
an
unhold
and
LG
TM
approve
it
is
kind
of
long.
So
it
might
take
you
a
little
bit
to
read
through
it.
C
A
B
A
C
G
A
Thank
you
all
right,
so
many
fewer
things
ready
for
review
the
update
owners
files,
one
of
these
is
in
which
you
were
just
approving
yeah.
We
should
probably
put
it
in
here.
This
is
just
like
a
update,
all
the
owners
files
things
thing.
We
should
put
the
actual
issue
in
here.
Yes,
I'm,
just
going
to
put
it
on
I
think
to
make
sure
that
board
is
updated
later.
G
A
A
A
Awaiting
response,
how
did
I?
How
did
I
do
this?
Oh
yeah
I
can't
update
things,
but
that
status
is
good
anyway,
there
we
go
all
right.
Thank
you,
sandipa.
Let
us
know
if
you
need
any
help.
Frederico
has
this
one.
Going
on
with
the
book
reading
club
Bob
had
asked
a
question
about
the
book.
Reading
club
being
cncf
focused
or
kubernetes
focused,
it
was
originally
kubernetes
focused,
but
it
recently
moved
into
the
cncf
book.
Reading
club
slack,
so
Frederico
was
asking
them
about
that.
A
C
A
B
A
A
A
E
A
A
A
A
B
A
C
A
C
D
D
A
F
A
A
I'm
gonna
write
that
down
and
I'm
gonna
have
no
idea
what
that
means
after
this
meeting,
but
if
we
don't
fix
it
this
week,
we'll
fix
it
next
week.
Thank
you
for
the
updates,
so
the
release
team
won,
though
ready
for
review
in
hack
MD.
It
should
be
mostly
reviewed,
you're,
probably
going
to
move
on
with
that
in
the
next
day
or
so
right.
Guessing.