►
Description
[SIG ContribEx] Weekly Contributor Comms Meeting for 20230915
A
As
usual,
we'd
like
to
offer
an
opportunity
at
the
beginning
of
the
meeting
for
anyone,
who's
new
to
our
group
to
unmute
and
say
hello
and
tell
us
a
little
bit
about
yourself.
You
can
also
type
in
the
chat,
and
it's
also
totally
optional.
So
you
don't
have
to
at
all,
but
I
will
leave
that
open
for
a
minute.
If
you
would
like
to
unmute
and
say
hello
or
chat,
or
you
know
whatever.
B
I'm
Vishal
I
am
new
in
this
meeting
today,
so
I
am
a
bachelor
student
currently
pursuing
my
computer
science
in
engineering
and
I'm,
also
one
of
the
communities
member
and
City
docs
in
the
localization
official
reviewer,
so
I'm
I'm
really
excited
to
just
get
involved
with
this
sick
country
mix
and
just
help
with
all
of
the
contributions
coming
with.
All
of
you,
I'm
really
excited
to
contribute
in
sick
contradicts,
so
I
just
wanted
to
know
how
can
I
get
involved
with
with
this
work
or
just
give
my
contributions
based
so
far.
A
B
C
C
A
A
A
C
D
C
D
C
D
A
D
E
A
A
A
All
right-
and
that
will
come
up
again
anyway,
because
it's
in
the
board,
so
the
only
other
thing
I
added
in
here
is
kubecon
tweets,
which
is
also
in
the
board.
So
I
didn't
need
to
put
it
here,
but
I
did
anyway.
I
already
had
this
open
whatever
now
I
have
it
opened
twice,
I'll
close
that
one
we'll
go
with
this
one.
A
So
several
of
you
on
here
today
are
interested
in
helping
me
out
with
managing
the
kubecon
tweets
process
for
those
who
are
new.
This
is
one
of
your
two
projects
that
would
could
use
your
help,
so
I
created
a
kubecon
in
a
2023
tab.
Last
time
we
were
on
this
call
last
week,
I
spent
some
time
last
night
and
this
morning
setting
up
this
page
essentially
and
I
just
copied
this
one
over
I.
Don't
actually
want
to
leave
it
here,
but
I
wanted
to
leave
it
here
for
this
meeting.
A
C
A
We'll
need
to
spread
this
around.
We
want
lots
of
folks
to
join
in
with
this.
This
is
really
approachable
project.
If
folks
are
interested
in
helping,
you
would
take
a
look
at
the
sheet.
We
have
a
description
in
for
each
of
the
posts
that
we
need
to
write
about
kubecon
and
you
would
put
yourself
as
owner
and
then
you
would
write
that
tweet
one
thing
I
want
us
to
talk
about
today
is
the
yeah.
Thank
you
nutish.
A
We
need
to
talk
about
the
deadline.
We
want
to
set
a
deadline
for
folks
contributing
posts
to
be
done,
writing
their
posts
and
any
posts
that
are
not
written
by
that
point.
It
will
be
up
to
us
who
are
managing
this
process
to
write
those,
as
you
can
see,
I
started
changing
the
dates
to
match.
Kubecon
North
America
I
just
copied
all
of
this
stuff
from
the
kubecon
EU
one.
A
So
that's
how
I
got
the
colors,
and
also
all
of
these
descriptions
are
just
copied
over
from
there
and
the
dates
most
of
the
times
are
the
same.
Like
I
took
a
look
at
just
at
this
first
day
of
the
actual
event
itself.
On
the
maintainer
track
block
times-
and
these
were
right-
there
was
one
extra
one
for
this
day,
but
oh
no
I,
don't
think
there
was.
Even
maybe
there
was
one
extra,
no
I
think
it
was
all
the
same.
A
A
Yes,
we
absolutely
should
share
it
in
slack
to
ask
folks
to
write,
tweets
I,
usually
post
it
in
contribex,
if
you
have
other
ideas
for
places
where
you'd
like
to
put
it
I'm
good
with
that,
we
did
just
create
a
new
contributors
channel
of
some
sort,
yeah
kubernetes
new
contributors,
so
that
might
be
a
good
place
for
us.
To
put
it,
let
me
put
that
in
the
notes.
D
D
A
F
A
C
H
Yeah
so,
while
you're
working
on
the
last
year,
2023
I
saw
that
many
I
mean
some
schedule
was
not
matching
to
the
previous
ones,
and
since
we
are
just
copy
and
pasting
it,
we
should.
We
should
first
and
said
the
I
mean
yeah.
We
should
just
first
save
the
times
date
and
times
from
the
schedule.
Then
we
should
ask
folks
to
write
the
tools
if.
C
E
A
E
C
So
so
we
did
talk
I
think
yesterday
we
talked
about
kubecon
China
coming
up
and
that
we
weren't
like
there's
people
there
that
are
going
to
cover
it.
Not
us
particularly
yeah.
We
mentioned
that
briefly.
So
if
you
go
to
the
contributor
site
and
you're
like
oh
China,
we're
not
doing
anything
for
that.
Well,
there's
people
in
country
that
will
so
yeah.
C
D
A
C
A
G
C
D
E
A
C
A
Yeah
bishal,
so
you
will
want
to
be
one
of
the
contributors
of
posts,
is
where
we
would
need
your
help.
Like
we
said
we
don't
have
all
of
the
dates
completely
sorted
out
yet,
but
I
think
most
of
them
at
least
through
here
I
think,
is
right.
I
went
through
and
checked
these,
so
we
just
need
to
change
these
dates
to
November,
6th
and
November.
D
A
A
Yeah
or
just
or
just
put
your
name
in,
however,
you
would
like
to
indicate
I
am
going
to
write
this
post.
Take
a
look
at
the
descriptions,
whichever
ones
are
most
interesting
to
you.
If
you
need
any
help
reach
out
to
me
perfect,
so
yeah
you
can
go
ahead
and
do
that
now
through
through
the
November
seventh
block.
So
all
these
blue
ones
here
once
the
screen
starts,
I
haven't
actually
checked
that
these
are
correct,
but
that
won't
take
us
long.
A
A
D
A
A
For
whichever
ones
you
want
to
do,
if
you
want
to
write
the
badge
pickup
reminder,
then
you
put
your
name
there.
If
you
want
to
write
the
reminder
about
the
kubernetes
contributor
Summit
in
Day,
Zero
events
there,
if
you
want
to
look
at
the
kubecon
schedule
and
see
which
of
which
talks
are
happening
at
11
in
the
maintainer
track
and
then
write
a
tweet
about
that,
then
you
put
your
name
there.
C
A
E
A
C
A
A
A
A
A
We
would
like
those
posts
to
be
written
by
October
20th,
and
then
that
gives
us
two
weeks
one
week
without
me.
One
week
with
me
to
get
any
Unwritten
posts
written
so
I
will
probably
not
remember
what's
going
on
at
all
when
I
get
back,
but
I
will
try
to
make
sure
to
put
it
on
my
calendar
all
over
the
place,
to
spend
a
little
bit
of
time.
Checking
over
these
making
sure
that
we've
got
all
the
tweets
written
yeah.
E
C
D
D
A
C
A
C
A
A
C
D
A
A
A
A
Thank
you.
Thank
you.
Everyone
who's
interested
in
helping
with
that.
This
is
a
great
project
for
new
contributors.
So
if
you
know
folks
who
want
something
to
do
within
the
project,
Point
them
our
way,
you
don't
have
to
understand.
Github.
You
write
something
small,
with
guidance
on
exactly
what
you
need
to
write
and
then
it
gets
shared
with
everyone,
and
we
thank
you
publicly.
So
great
work
for
new
contributors.
C
A
C
A
A
A
A
F
A
D
I
C
D
D
C
A
A
D
E
A
Yeah
Michelle's
you're,
ahead
of
us
already
interested
in
the
spotlight
blogs
yep.
That
is
the
other
thing,
the
other
project
that
I
mentioned.
That
would
be
a
good
fit
for
you.
We'll
talk
about
those
momentarily
yep,
oh
I,
accidentally
locked,
my
computer
I
added
the
link
to
that
PR
and
the
board
item
for
updating
the
owners
files,
but
that's
already
done
it's.
A
D
A
I
I
I
Oh
yeah,
exactly
so
that's
actually
a
placeholder
for
the
for
this
five
different
ones,
so
one
is
as
in
PR,
the
other
is
in
fmd.
The
third
one
is
is
being
worked
on
and
as
content
in
docs,
there
are
two
missing
which
I
can
I
contacted
the
the
authors
this
week.
One
is
organization,
the
other
is
enhancements
and
they're
well,
their
Delights
I've
I've
shared
our
roadmap.
I
So
we
plan
to
have
one
of
this
out
once
per
month
and
we
started
now,
so
this
at
least
provides
a
more
rigid
deadline
which
I
think
people
actual
actually
actually
like,
because
it's
it's
something
palpable
that
they
have
to
work
towards
and
that's
it
I
I
can
update
that
link
or
you
can
do
it
as
well.
So
that's
done
that's
done,
then.
The
one
on
on
enhancements
is
the
other
one
being
worked
on,
which
leaves
us
the
either
two.
D
A
E
I
A
A
A
C
A
A
A
This
is
a
great
project
because
for
you
you
get
to
interview,
usually
the
co-chairs
of
the
Sig
and
learn
about
what
they're
all
about,
and
then
you
teach
other
people
what
that
Sig
is
all
about.
So
it's
a
great
opportunity
for
you
to
learn
and
to
help
the
project
by
hopefully
encouraging
more
people
to
get
involved
with
those
special
interest
groups.
A
Also
Sig
stands
for
special
interest
group,
so
each
Sig
covers
topics
like
we've
got
it's
like
architecture,
we've
got
to
say,
testing
Spotlight
article
in
play,
which
we'll
go
over
in
a
minute.
We've
got
the
one
for
Sig
release
that
Tish
is
working
on
in
our
to
do
column.
We
have
a
couple
yeah
a
couple
called
out
that
haven't
been
done
yet
if
you're
interested
in
Sig
API
Machinery
sounds
boring,
actually
very
interesting
thing
in
my
opinion,
and
we
also
have
Sig
Kate's
infra,
which
is
so
critical
to
the
project.
A
Also,
each
stick
is
interesting
in
its
own
unique
ways,
but
here
are
a
couple
that
no
one
has
taken
on.
So
if
you
want
to
just
grab
one
of
these
two,
those
are
up
for
grabs
but,
like
we
said,
you
can
also
go
through
the
Sig
list
and
tell
us
what
you're
interested
in
so
the
process.
Basically,
like
I
said,
is
you
claim
it?
A
Then
you
reach
out
to
those
whoever
they
pointed
out
as
your
contact
directly
and
set
up
an
interview
with
them.
You,
we
usually
recommend
writing
out
your
interview.
Questions
in
a
doc
and
then
working
on
it
asynchronously,
because
that
makes
writing
the
blog
post
easier
later
and
also,
if
you
do
it
in
a
call
and
then
record
it,
then
you
have
to
transcribe
it.
So
it
adds
some
friction
to
the
process.
Generally
kind
of
depends
on
how
you
work,
though,
there's
no
rule
so
write
up
some
questions.
E
A
B
Thank
you
for
the
explanation
of
regarding
the
six
Spotlight
and
I'm
really
looking
forward
to
it
to
just
contribute
and
let
you
know
actually
whatever
suggest,
I'm
choosing
right
now
on
the
slack
itself
and
we'll
move
forward
to
this.
Try
to
down
all
the
questions
regarding
the
interview
and
send
you
all
the
questions
for
the
review.
If
you
like
it,
you
just
move,
move
ahead
and
schedule
the
interview
with
the
coaches
as
well.
A
A
A
E
C
Have
answered
that
question
more
quickly
for
Kate's
second
for
I
think
it'd
be
important
to
touch
on
they're
the
folks
behind
the
registry
change
they're,
the
folks
behind
all
these
URLs
and
back-ends
changing
and
managing
cdns
and
the
project
spend
and
everything
else
like
that.
Yeah
probably
be
a
major
highlight.
A
A
I'm,
just
not
gonna
even
type
that
yeah
all
right
anyway,
we
have
less
than
10
minutes
left
eight
minutes
left
so
I'm
gonna
see
if
we
can
run
through
the
in
progress
stuff
quickly.
Apologies
to
everyone,
I,
usually
love
hearing
everyone's
updates,
but
I'll
ask
you
to
keep
your
updates
short
and
we'll
see
how
many
we
can
get
through
Sig
testing
Spotlight
article.
G
I
D
I
Book
reading
club
talked
with
Carlos
early
in
the
week.
It
said
it
was
interested
and
adding,
but
it
was
still
a
bit
Delight
told
me
to
check
again
in
two
weeks:
okay
and
I
and
I
I'm
to
Ping
him
into
more
or
less
three
two
weeks,
I'm
going
to
ask
him
what's
the
status
and
if
he
needs
a
couple
more
days
or
not,
so
you
can
put
two
weeks
there.
I
What's
the
scenario
we
do
the
interview
and
if
it's
not
adequate
well,
it
isn't
I
mean
we'll
see
I.
It
still
has
the
kubernetes
focus
completely
it's
for
me.
The
only
thing
that
changed
was
that
now
it
has
cncf
sponsorship
and
one
of
the
things
that
I
ask
is
exactly
what
exactly
does
that
change
in
terms
of
the
book
club,
but
the
content,
the
scope,
the
people
there,
it's
it's,
it's
all
around
kubernetes.
E
C
C
A
A
E
A
C
A
E
C
D
A
A
J
J
J
A
C
Stick
with
me
here,
so
a
pod
by
definition
in
the
kubernetes
like
docs,
is
one
or
more
containers,
and
you
know
the
Pod
being
the
lowest
level
of
work
in
kubernetes.
You
could
have
your
application
and
a
front
end
for
it
running
the
same
pod.
That
front
end
would
be
a
sidecar
essentially,
but
you
can
also
add
things
like
service
meshes
as
a
sidecar
or
monitoring
or
Telemetry.
A
A
Kubernetes
will
take
care
of
that
application
for
you,
so
you
generally
think
of
a
pod
as
like
a
single
thing,
but
istio
and
other
things
use
the
sidecar
thing
to
put
things
like
monitoring
and
other
stuff
right
there
with
the
workload
nice
thing
about
two
containers
in
a
pod
or
terrible
thing,
depending
on
how
you
try
to
use
it
is
that
both
containers
or
as
many
containers
are
in
that
pod
share
the
same
storage
space.
They
share
the
same
IP
address.
A
They
share
the
same
networking
they
share,
basically,
all
of
all
of
the
resources,
and
so
that
means
that
if
you
put
a
container
right
next
to
the
application
you
actually
care
about,
if
traffic
is
coming
in
trying
to
get
to
your
application,
you
can
use
a
sidecar
to
intercept
that
traffic
and
say
hey.
Are
you
allowed
to
talk
to
this
application
before
it
actually
gets
to
the
application
itself?
A
E
D
C
J
A
G
J
J
C
A
A
F
There
have
been
no
updates
for
that.
I
talked
with
Marco
regarding
the
same,
and
he
said
like:
let's
focus
on
what
we
are
building
right
now
and
it's
better
because,
along
the
way,
you'll
be
learning
about
what
are
what
are
the
rules
of
the
release
managers
and
along
the
way
you
will
be
also
we'll
be
figuring
out
the
question
that
needs
to
be
asked.
So
it's
better.
You
focus
on
the
current
mentorship
and
along
the
way,
you'll
be
having
bunch
of
questions
to
ask
the
release
managers.
A
C
A
The
the
repo
is
a
living
space.
She
sees
the
things
that
need
fixing
or
could
be
clear.
Let
us
know
we
appreciate
the
input.
Tech
lead
chatter
requirements,
so
today
we
should
talk
about
that
at
some
point.
Don't
have
to
worry
about
it
right
now.
It'll,
basically
be
updating
the
tech
lead
role,
I'm
just
going
over
what
we
have
for
that
I'm
going
to
skip
that
steering
election
comms
as
needed.
Thank
you
very
much
our
pit.
A
C
A
A
D
I
E
I
I
A
C
A
C
D
A
Yeah
steering
wheel
will
be
there,
so
we
can
talk
to
them
about
that.
We
can
discuss
what
we
want
it
to
look
like
yeah.
What
we
think
it'd
be
most
useful
for
it
to
look
like
cool,
we'll
talk
more
about
that
next
week.
Maybe
we
should
talk
about
it
on
slack
and
figure
out
yeah
a
strategy
see
if
we
can
set
up
a
meeting
with
Bob
new
contributor,
Workshop
I
think
you
already
mentioned
that
we.
C
Planning
not
not
thinking
but
I,
did
see
a
lot
of
activity
earlier
this
week
around
the
discussion
of
running
workspaces
inside
KK,
which
is
kind
of
a
sticking
point
right
now
they
have
those
disabled
like
all.
The
extra
GitHub
features
are
disabled
in
kubernetes
kubernetes
on
GitHub,
but
that
discussion
is
happening.