►
Description
[SIG ContribEx] Weekly Contributor Comms Meeting for 20230728
A
Hello
and
welcome
everyone
to
the
Friday
July
28th
edition
of
the
contributor
comms
team
meeting.
As
usual,
we
do
operate
under
a
code
of
conduct
which
essentially
says
to
be
respectful
of
your
fellow
attendees
and
speakers
and
generally
be
excellent
to
each
other
to
start
things
off
this
morning
we
usually
like
to
offer
an
opportunity
for
anyone,
who's
new
to
the
call
to
unmute
or
type
in
chat
and
say
hello
and
tell
us
a
little
bit
about
yourself,
totally
optional.
A
A
A
A
A
Don't
know
if
I
ever
updated
this
group,
but
the
leads
of
Sig
contribex
said
that
they
would
like
for
one
of
the
new
leads
to
do
it,
since
we
just
got
new
leads
in
good
chance
to
tell
everyone
like
hey,
there
are
new
leads
in
the
Sig,
so
it'll
probably
be
one
of
the
new
co-chairs.
Or
tech
leads
we're
not
sure
who
will
do
it
yet,
but
Chris
has
been
working
on
getting
that
content
together,
he's
not
going
to
be
on
today.
So
I'll,
sync
with
him
offline
on
that.
A
If
you
have
any
questions
about
that,
you
are
welcome
to
ask
them.
Other
item
that
I
wanted
to
put
into
updates
and
big
wins
is
buffer.
Is
fixed,
I,
don't
know
if
anybody
knew
that
buffer
was
broken,
but
I
think
we
went
over
it
yeah.
So
we
added
Mastodon
to
our
buffer
account,
which
meant
that
it
increased
the
amount
we
had
to
pay
each
month.
A
So
we
had
to
file
a
request
with
the
cncf
to
make
sure
that
asking
for
a
little
bit
more
money
would
be
okay
and
they
said
that
was
fine,
but
they
didn't
actually
update
the
payment
on
file,
and
so
the
account
lapsed
and
I
had
to
work
with
the
cncf
to
get
the
billing
fixed
and
I
just
went
in
this
morning
and
actually
reactivated
the
the
page
part
of
the
account.
So
everyone,
if
you
log
into
your
own
buffer
account,
you
should
have
access
to
the
kubernetes
contribex
team.
A
Again,
if
you
had
that
to
begin
with,
and
we'll
talk
more
about
that
in
a
minute,
because
I've
got
some
social
stuff
to
talk
about
in
new
items,
but
there's
one
more
update
here.
Natish
said
that
he
wouldn't
be
able
to
join
in,
but
he
said
that
he'd
put
these
notes
in
here
for
us,
so
we'll
just
go
over.
Those
updates
related
to
six
Spotlight
series
that
natish
is
working
on
he's
still
working
on
the
Sig
release,
Sig
Spotlight,
so
he
still
hasn't
gotten
answers
on
the
questions.
A
A
A
There's
details
about
exactly
how
it
all
works
and
everything
in
the
repo
I.
Don't
remember
how
many
steering
committee
seats
will
be
up
for
election
this
time.
I'll
have
to
check
on
that.
But
at
least
a
few
will
be
up
for
election,
so
starting
on
August,
eighth
we'll
be
announcing
the
election
and
will
be
starting
to
collect
candidacies.
I.
Guess
it's
a
good
way
to
say
that
folks,
who
want
to
run
for
steering
committee
and
will
start
telling
us
about
that.
A
So
we
will
need
quite
a
few
comms
there.
I
am
one
of
the
election
officers,
which
means
that
I
will
be
deeply
involved
in
this
whole
process
and
I
volunteered
to
be
the
comms
liaison,
which
I
find
very
amusing
for
the
election.
So
I'll
be
asking
for
some
help,
especially
because
the
candidate
nominations
are
due
and
the
the
voting
begins
during
a
week
that
I
am
out
for
an
event,
so
I'll
need
some
help.
There
and
arpit
I've
already
asked
you
for
your
help,
and
you
said
that
would
be
okay.
A
I'll
work
with
you
on
that
yeah,
so
to
give
a
general
sense
of
what
we'll
need
to
do
for
that.
This
is
my
second
time
as
an
election
officer.
I
wouldn't
say
that
I
did
a
great
job
the
first
time,
but
we
will
improve
with
the
second,
so
we'll
need
to
do
social
media
posts
saying
that
the
election
is
happening,
that
you
can
find
more
information
on
GitHub,
but
we'll
need
to
be
careful
with
Social
Media
stuff
to
make
sure
that
we're
only
saying
things
that
are
publicly
accessible.
A
Only
folks
who
are
eligible
will
be
able
to
vote
so
there's
an
automatic
system
that
figures
out,
if
you're
eligible
to
vote,
based
on
the
contributions
that
we're
able
to
see
in
Dev
stats.
It's
just
this
automated
process.
That's
like
you've
had
this
many
comments
on
PRS
and
PR's
made
and
all
sorts
of
stuff
like
that,
and
so
you
are
eligible
to
vote
because
you
are
doing
things
in
the
community.
A
It
counts
a
lot
of
things:
I,
don't
know
how
it
works,
but
I'm
always
shocked
at
the
number
of
things
it
says
for
me
when
I
don't
do
that
much
on
GitHub,
but
there
are
still
those
who
do
stuff
for
the
community
whose
work
isn't
tracked
very
well
by
that
system.
So
there
will
also
be
an
opportunity
for
folks
to
request
an
exception
to
be
able
to
vote
so
we'll
need
to
do
some
Communications
about
that.
A
A
So
this
is
wrapping
up
before
I'm
out,
which
is
actually
kind
of
nice,
because
it's
often
really
close
to
kubecon
and
then
all
the
things
are
happening,
and
so
hopefully
yeah.
This
timeline
will
work
out.
This
hasn't
been
officially
accepted
yet,
but
I
wanted
to
give
you
all
a
heads
up
around
what
will
be
happening
with
the
steering
from
the
election,
because
I
might
be
asking
for
help.
Hopefully
our
pet
will
be
able
to
help
me
with
everything,
but
just
in
case
we
need
additional
help.
I
wanted
everybody
to
know
about
it.
A
A
D
C
Worth
the
same,
of
course,
just
a
note
that
I've
deleted
the
draft
that
we
had
there
in
the
board
and
replaced
it
with
this
open
PR,
because
it's
the
same
topic,
yep
nice.
So
essentially,
this
is
a
follow-up
from
last
week's
meeting
in
which
we
discussed
the
topic
of
requirements
for
shadows
in
in
blogging.
It
it
I
I
was
correct
in
that
there
was
already
content
there,
but
that
being
said,
what
I
did
was
to
make
it
I
expanded
on
it
a
bit
and
made
it
more
and
obvious.
C
What
are
the
typical
tasks
that
the
shadow
would
be
asked
to
perform
in
order
to
to
be
a
elite
in
the
future?
So
obviously
this
is
up
for
review.
I
can
change
things.
This
was
just
what
I.
This
is
based
on
what
was
already
there
and
previous
discussions,
but
as
with
any
improv,
any
change
I
welcome
feedback
in
those,
and
eventually
we
just
just
commit
that,
and
and
and
that
should
do
it.
A
D
Yeah
so,
based
on
our
previous
discussion,
as
we
decided
to
deprecate
the
new
rule,
which
was
the
events
lead,
so
this
PR
does
that
also
there
was
some
links
that
were
not
pointing
out
to
the
current
documentation
of
not
documentation.
This
is
the
meeting
yeah
yeah
in
the
Sig
contrabacks,
so
I
changed
that
as
well
and.
B
D
A
D
A
B
A
C
Minor
ones,
nothing
to
write
about
really
some
more
feedback
on
I'll,
be
finishing
it
up
next
week
and
stuff
like
that,
some
people
are
still
out.
Others
are
returning,
I've
made
a
list
of
I
I,
don't
think
I've
published,
but
I
have
a
list
of
the
the
the
ones
that
are
already
done,
because
this
is
a
there
are
several
sub
steps
right,
so
I
will
update
the
the
with
that
lists
with
the
currents
with
the
current
situation,
which
is
slightly
better.
C
A
Randy
then
notify
the
comms
team
when
a
new
issue
is
created,
we
had
a
little
conversation
about
that
last
time.
This
is
like
a
an
old
task
that
we
were
trying
to
figure
out,
looks
like
you
edited
it
of
anesh
I,
don't
remember
exactly
what
we
decided.
We
were
going
to
do
that.
Put
this
into
active
work.
B
A
A
A
A
So
move
on
to
the
next
one.
The
Sig
can
trip
X,
One
Becca
isn't
on,
but
I
did
a
bunch
of
work
on
answering
those
questions
not
this
week,
but
the
week
before
I
got
them
in
a
pretty
good
State
I
think
I
talked
with
FICA
about
it
and
she
said
that
she
was
waiting
for
answers
from
the
other
co-chairs
and
tech
leads,
because
we
were
hoping
to
represent
at
least
a
couple
of
perspectives
from
the
leadership
of
the
sick,
so
I
think
that's
moving
along.
Okay.
A
Cool
and
then
for
Sig
release
we
already
went
over.
Those
updates.
Natish
is
still
waiting
for
a
response,
hoping
that
other
folks
will
help
him
get
that
within
a
Sig
release,
and
we
have
all
of
these
things
that
still
need
to
update
our
shadow
requirements
for
review.
We
Are
trying
to
update
our
language
to
make
it
a
little
bit
clearer
what
a
shadow
is
and
a
shadow
is
someone
who
is
aiming
to
take
over
a
lead
position.
A
So
someone
who
probably
has
been
involved
with
the
community
for
a
little
bit
and
understands
a
little
bit
about
that
role
knows
that
they
want
to
do
that,
and
so
I
was
working
with
the
lead
in
order
to
take
over
so
we're
updating
the
requirements
to
just
make
that
really
clear
everywhere
within
our
repo
theoretically,
at
least
some
of
us
are
a
little
self-jab.
I
need
to
do
that.
C
That
one
is
ongoing
as
well.
The
contributor
Summit
one
I've
sent
the
it's
the
same
as
last
week,
I've
I've
shared
the
document
with
with
Noah
perfect,
the
first
batch
of
questions
and
and
I'm
waiting
on
on
that
initial
feedback.
Actually,
I
will
update
that
with
with
the
questions
not
with
the
link,
because
the
way
that
I
work
is
that
I
I
just
create
a
link
with
everyone.
Everybody
with
a
link
is
an
editor.
A
D
C
C
Yeah,
it's
a
zombie
or
it's,
it
was
never
killed.
I,
remember
more
seriously!
I
remember
Carlos
telling
me
that
maybe
there
would
be
an
update
on
on
that.
So
maybe
the
rumors
of
the
book
book
club's
death
have
been
widely
exaggerated,
so
I'll
I'll
ping
Carlos
and
see
if
it
still
makes
a
sense
and
if
so,
I'll
rescue
this
from
the
one
fixed
queue.
C
A
C
B
C
A
A
A
E
A
C
E
C
C
E
A
And
to
review
the
basic
process
for
anyone
who
might
be
interested
in
it,
you
basically
interview
the
Sig
leads.
Usually
you
can
ask
them
if
they're
the
best
folks
to
interview-
and
you
put
all
that
into
a
doc,
preferably
there
are
other
ways
to
do
it,
but
we
recommend
a
doc,
and
then
you
turn
that
into
a
Blog.