►
Description
[SIG ContribEx] Weekly Contributor Comms Meeting for 20230721
A
Hello
and
welcome
everyone
to
the
Friday
July
21st
edition
of
the
contributor
comms
team
meeting
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.
To
start
off
the
meeting
we'd
like
to
try
and
offer
an
opportunity
for
anyone,
who's
new
to
the
call
to
introduce
themselves
totally
optional.
You
don't
have
to
you,
can
use
either
chat
or
you
can
unmute.
A
You
have
an
opportunity
to
do
that
now.
If
you
would
like
to
say
hello
and
tell
us
a
little
bit
about
yourself
and
why
you're
here.
A
A
B
A
So
that
we've
covered
that
so
Frederico
posted
in
the
chat
just
before
we
got
started,
he
said
that
he's
still
caught
in
a
meeting,
so
he
isn't
over
here,
yet
I
assume
he
might
join
in
later,
but
his
updates
were
that
the
six
CLI
Spotlight
has
been
published.
Wonderful
thank.
A
And
he's
confirmed
that
he
does
have
Shadow
criteria
written
in
the
role
description,
so
no
major
update
still
ongoing
okay.
So
that's
frederico's
updates.
A
Enough
and
our
first
update
and
big
win
definite
big
win
in
our
notes
was
that
the
six
Spotlight
is
out
again.
C
A
You
do
you
want
to
say
anything
about
the
six
CLI
Spotlight
or
anything.
A
Yeah
release
can
really
take
up
more
of
your
time
than
you
expect
at
the
beginning.
D
A
What
happened
there
is
I
had
a
PR
that
I
had
opened
to
change
the
readme
just
update
some
text
in
there
and
I
lost
it
for
like
two
months
and
I
finished
found
it
for
us
again.
Thank
you,
and
so
we
finally
got
that
added
in
which
means
that
the
readme
change,
which
is
what
you're
trying
to
update
so
now,
you're.
C
Your
yeah
you're
out
of
science
yeah.
A
E
A
A
So
we
discussed
that
you
have
don't
have
a
whole
lot
of
experience,
working
with
a
lot
of
like
the
tools
that
we
use
and
doing
a
lot
of
the
tasks
that
the
social
media
lead
needs
to
do
so
I
think
we
should
start
with
just
like
some
mentoring
on
social
media
stuff
and
see
how
you
like
it
and
then
maybe
do
the
lead
part.
Does
that
sound
okay
and
we
can
like
do
some
mentoring?
You
can
learn
some
skills
and
then
we'll
reassess.
A
E
E
A
It'll
also
be
the
first
time
if,
whenever
we
do
end
up
having
someone
take
on
the
shadow
role
and
move
into
a
lead
position,
there
it'll
be
the
first
time
that
one
has
changed
hands
from
me
to
someone
else.
So
I
need
to
make
sure
that
I
I
know
what
I'm
doing
there.
So
this
will
help
me
figure
that
out
as
we
go
along
as
well,
I.
A
E
A
Yeah,
because
one
of
the
reasons
I
wanted
to
do
the
update
on
clarifying
what
a
shadow
is
is
because
I
think
a
lot
of
folks
come
in
and
they're
new
to
the
project
and
they're
looking
for
mentorship
and
they
feel
like
Shadow
is
how
they're
going
to
get
mentoring,
which
is
one
way
to
do
it.
But
usually
it
starts
with
other
mentoring,
which
is
usually
not
clear
to
folks.
So
maybe
we
can
make
that
better.
A
Okay,
I'm
gonna
keep
going
down
the
updates
and
big
ones,
and
then
we'll
do
the
new
item.
What's
next?
Oh,
yes,
Avinash
was
mentioning
that
we
had
needed
to
update
the
reviewers
since
we
have
new
lead.
So
we
were
discussing
that
before
we
started
the
recording.
A
What
we
need
to
do
there
is
there
are
owner's
files
in
the
repos
that
we
own,
which
the
repos
that
we
own
are
the
contributor
tweets
repo
and
the
regular
contributor
comms
where
all
of
our
stuff
lives,
so
both
of
those
have
an
owner's
file
and
we
need
to
update
those
owner's
files
in
order
to
update
who
gets
pinged
for
reviews
on
things
when
they
come
in.
A
B
Have
yeah
I'll
show
you.
B
So
I
put
Avinash
in
as
the
subproject
lead
Shadow
the
owner's
file
Avinash
is
an
approver,
so
that
gives
you
and
a
reviewer
so
yeah
should
we
be
pinging,
forget
the
name,
but
the
handle
is.
I
m
n
o
still.
C
A
B
B
A
Than
I
am
so,
as
your
sub
project
leave.
C
B
A
C
B
C
E
A
We
should
update
the
ones
in
the.
We
should
update
both
the
contributor
tweets
one
and
the
comms
one,
because
techley
does
have
have
the
higher
privileges
in
the
tweets
repo
as
well,
because
the
tech
lead
is
in
charge
of
the
Automation
in
that
repo,
though
we're
not
doing
anything
with
it
right
now,
so
Jay
still
needs
those
privileges
in
case
he
wants
to
do
anything
with
that.
At
any
point,.
A
B
Yeah,
if
we
do
it
right,
we
should
be
able
to
say
hey.
This
is
an
approved.
You
know
like
message:
issue
PR,
whatever
we
could
keep
a
running
log
of
tweets
or
something
and
just
say:
hey.
This
tweet
is
approved,
and
hopefully
we
can
get
zapier
to
trigger
on
the
approval
and
then
push
it
to
buffer,
which
would
then
throw
it
in
both
cues
to
be
scheduled.
B
B
We
yeah
or
something
crazy.
We
do
with
like
Sig
kids
infra,
that's
entirely
possible.
If
we
have
the
skills
and
want
and
desire,
we
could
have
something
doing
this
for
us
too.
A
A
A
A
I'm
just
gonna
go
into
new
items.
A
social
media
handbook
needs
update
Avinash.
That
was
good
catch.
You
already
talked
to
me
about
it,
but
would
you
like
to
explain.
F
Yeah
so
currently
the
social
media
handbook
talks
about
Twitter
together,
which
was
our
previous
tool,
and
we
are
not
using
it
anymore.
I.
B
B
That's
a
very
good
point:
social
media
handbook,
all
right.
B
A
C
A
But
the
other
hand
looks
I
think
still
need
updates.
There.
I
should
put
that
on
my
physical
to-do
list.
A
Cool,
so
that's
the
social
media
handbook
updates
and
also
a
reminder
that
the
other
handbooks
need
updates,
also
for
getting
rid
of.
We
decided
in
the
end
to
get
rid
of
events
lead
for
now.
Did
we
so
we
need.
B
F
A
B
Toss
it
on
top
of
the
handbook
and
say
it's
deprecated
for
now,
and
you
know
as
of
last
week
or
whenever
we
made
the
decision,
you
can
go
back
in
the
notes
and
that's
the
update,
just
pull
it
from
the
readme
and
update
the
handbook.
A
B
Yeah,
it
might
as
well
because
of
the
way
we're
listing
things.
Yeah
just
say
you
know
deprecated
either
at
the
beginning
or
end
probably
the
beginning.
A
A
Yeah
and
at
the
beginning
and
add
a
line
to
the
handbook
at
the
top
saying
it
is
deprecated
as
of
mid-2023
or
whatever
you
want
to
say,
yeah.
That's.
B
A
A
A
Right
and
oh
yeah,
I
added,
as
we
were
talking,
that
we
should
put
some
more
information
about
mentoring,
skills,
mentoring
and
skills
development
in
our
repo
somewhere.
That's
something
to
Noodle
on.
A
C
A
D
No
actually
I
just
sent
him
a
DM
like
how
much
he
has
progressed
so
I
also,
don't
know
that
he
has
prepared
doesn't
so
maybe
I
should
ask
him
for
that.
Yeah.
E
A
B
A
B
F
A
B
All
right
so
here's
the
member
which
is
entry
level
requirements
active
contributor
in
the
community,
sponsored
by
two
reviewers
and
multiple
contributions
to
the
project.
E
D
Think
last
time
I
asked
for
that,
but
we
actually
never
got
into
it
and
who
conversation
after
it.
B
A
Even
non-github
things,
if
you've
like
written
a
tweet
in
buffer
or
done
any
of
I,
don't
know
any
stuff
that
is
community
related
that
you
think
might
count.
Just
let
us
know
we'll
let
you
know
if
it
counts,
otherwise,
we'll
make
sure
to
get
you
in
on
kubecon
tweet
planning,
because
we
need
to
work
on
your
skills
on
that
anyway,
because
we
were
going
to
do
that
and
we
also
we're
going
to
work
on
other
Social
Media
stuff.
A
Okay,
very
good,
so
we
should
I
need
to
can
I
just
remove
right
now.
Yes,
okay,
update
comment
all
right,
so
we'll
chat
more
over
slack
and
make
sure
to
get
you
a
couple
more
contributions
in
and
then
we'll
do
your
Arc
membership.
A
A
Like
I
mentioned
Sid
contrerbeck's
FICA
had
written
those
questions
quite
a
while
ago,
and
I
have
finally
answered
most
of
them.
I
also
sent
it
to
the
other
co-chairs
and
tech
leads
within
Sig
and
tripex
I.
Don't
think
any
of
them
have
answered
any
of
it.
So
I
might
just
end
up
being
an
interview
with
me
anyway,
but
we
are
actively
working
on
that
Sig
release
spotlight.
A
A
A
B
C
A
Yeah,
even
if
it
is
someone
else,
it
should
go
through
Frederico,
so
that
should
be
fine,
create
an
automation
folder
in
the
comms
repo.
B
C
B
B
C
B
B
C
C
A
A
You're
going
to
be
at
the
contributor
Summit
and
you
want
to
take
on
one
of
these
yeah
last
time-
I
took
notes
for
them
during
their
session
and
they
had
cute
little
enamel
pins
of
turtles
stacked
on
top
of
each
other.
So
I
was
just
saying:
they're
a
cool
group.
B
A
That's
true
knowing
them
well
enough
to
be
able
to
say
that
is
take
some
some
doing
laughs.
A
B
B
No,
we
implemented
mermaid.js,
okay,
stuff,
video,
blog
and
sight.
There
was
a
Blog
about
it
and
then
somebody
to
talk
I.
A
B
E
A
C
A
B
F
B
A
Cool
other
to-do
list
items,
Sega
machinery,
guidelines
for
sensitive
end
user
impacting
comes
always
a
an
important
thing
to
work
on
someday.
A
B
Sorry
Luna
was
barking,
so
I,
muted,
it
Bob
was
going
to
reach
out
to
Craig.
Let
me
reach
out
to
Bob
see
if
he
did
that
yet.
C
C
A
Update
very
good
all
right,
so
new
contributor,
Workshop
content
should
actually
move
before
kubecon
's
guidelines
for
sensitive
security
topics
in
particular
someday.
If
someone
joins
the
group
that
is
super.
B
B
This
came
like
this.
One
came
from
the
whole
Kate's
dot,
registry.io.
B
A
Stuff,
like
that,
those
kinds
of
things,
thank
you,
yeah
and
I-
think
part
of
the
documentation
would
be.
That
would
be
like
make
sure
it's
going
through
this
process.
A
Nice
cool,
so
I'm
gonna
go
ahead
and
deprecate
this
one
or
should
I
deprecate
that
should
I
delete
it
should
I,
don't
done
it
should
I
won't
fix
it.
It's
not
really
won't
fix
it's
just
that
we're
moving
it
to
something
else.
Whatever
we're
never
going
to
look
at
it
again,
so
I'll
put
it
into
won't
fix.
A
So
we
were
doing
a
bunch
of
exploration
into
this
a
while
ago,
things
we've
already
done.
We
updated
the
kubernetes
community,
repo
issues
template.
So
when
you
go
to
create
an
issue
in
kubernetes
community,
one
of
the
options
is
a
comms
request,
so
we
added
yeah
see
if
we
can
look
at
it.
We
added
a
like
a
tag
to
our.
F
Oh,
that
that
is
the
team
created
for
the
comms
team.
We
would
have
there's
a
section.
B
A
C
B
B
A
C
A
So
we
wanted
to
just
like
put
in
the
body
of
the
issue
like
just
something
that
tags
our
team,
so
that,
when
a
new
issue
does
get
created
with
that
template,
it'll
tag
our
team,
assuming
that
someone
doesn't
remove
that
from
the
issue
which
they
could
totally
do.
So
we
were
looking
for
other
ways
to
do
it.
That
would
be
more
robust.
A
I
think
that
would
be
really
cool
if,
like
an
issue,
gets
created,
and
then
we
get
a
ping
on
slack
that
an
issue
was
created.
Oh.
B
This
is
pretty
much
done.
If
you
just
want
to
copy
pasta
it
and
off
you
go.
A
What
do
you
want
to
send
out
yeah
it
used
to
have
this
in
there
like?
What
do
you
want
to
send
out?
Please
include
a
link
to
the
draft
and
like
some
other
stuff
in
here,
which
this
looks
broken
whatever
is
going
on
there
I
guess
we
should
look
at
this
anyway,
but
none
of
that
was
in
it.
When
I
looked
at
the
issue.
A
A
A
B
Don't
we,
the
idea
is
for
other
people.
The
ideas
yeah
like
other
people
would
use
this,
but
that
is
a
very
valid
question.
Two
people
actually
use
this
and
no
I
think
the
reason.
Why
is
because
there's
no
more
contributor
tweets,
there's
no
more,
like
people
just
come
to
the
channel
and
ask,
and
if
we
really
wanted
to
have
a
trackable
process
to
this,
which
we
kind
of
do
on
the
board.
B
A
A
A
F
F
E
C
B
E
A
B
A
Yeah,
well,
we
want
this.
A
B
E
E
E
E
That
is
see.
A
It
explicitly
that
was
also
something
we
were
trying
to
figure
out
before
is
like
how
does
the
sick,
which
is
a
label
that
we
made
right?
We
ended
up
making
that
label
comms
like
introduction,
so
yeah
I'm,
pretty
sure
label
yeah,
so
the
label
doesn't
exist
in
all
repos.
It
only
exists
in
like
the
communications
or
the
community,
one
which
makes
sense.
A
C
A
A
Do
we
want
to
continue
expecting
them
to
go,
find
our
Channel
and
slack
and
tell
us
there
do
we
want
to
make
any
changes
to
the
tools
that
we
have
available
in
GitHub
for
them
to
request
work
from
us,
our
questions
that
we
need
to
answer
and
then
make
a
blog
post
about
it.
A
E
C
A
Just
I
think
that
wouldn't
be
a
bad
thing,
because
whatever
work
that
comes
in,
we
generally
discuss
as
a
group,
especially
if
it
comes
in
through
slack,
it's
good
for
everyone
to
know
what
work
is
coming
in
for
us,
so
that
if
someone
is
really
interested
in
it,
they
can
ask
to
be
part
of
it.
So
I
would
say
that
notifications
on
slack
would
be
a
good
thing
for
any
GitHub
requests.
A
A
A
All
right,
thank
you
all
for
the
wonderful
conversation
on
that
useful
discussion,
and
that
was
the
last
thing
in
art
to
do,
and
we
have
two
minutes
left.
Wow
wow.
C
A
A
A
A
E
A
We
would
want
to
just
announce
in
our
Channel
yeah
single
single
Channel
yeah,
but
it
might
involve
a
slack
bot
of
some
sort.
I,
don't
know
what
the
actual
doing
of
this
will
require.
Maybe
not
our
slack
bot.
The
term
slackbot
is
extremely
confusing,
because
it's
both
a
generic
term
for
a
bot
that
is
in
slack
and
it's
the
term
that
we
use
specifically
to
mean
that
one
bot
that
pings
to
all
of
our
channels,
not
good
terminology.
Here
we
are
at
time
any
last
items
that
folks
want
to
talk
about
before
I.
A
Going
once
going
twice
and
good
I'm
gonna
go
ahead
and
stop
the
recording
and
say
goodbye
to
YouTube.
Let's
see
here
all
right,
Goodbye
YouTube.