►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20230505
Description
[SIG ContribEx] Weekly Marketing Meeting for 20230505
A
Hello
and
welcome
everyone
to
the
Friday
May
5th
edition
of
the
contributor
comms
team
meeting
and
I'm
having
some
docs
difficulties
here.
I
might
have
to
close
and
refresh
my
whole
window
but
refreshing
the
tab
didn't
work,
but
I
might
have
to
do
that
anyway,
reminder
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.
A
B
A
C
D
A
B
A
B
A
A
Right
back,
yeah
sounds
good.
All
right,
I
will
get
us
started
here.
Let
me
bring
up
okay
cool,
oh
another
thing
we
usually
do
at
the
beginning.
If
I
remember
is
to
offer
the
opportunity
for
anyone
new
to
the
call
to
introduce
themselves.
Is
anyone
new
and
would
like
to
introduce
themselves?
If
so
you
may
unmute
and
say
hello
now,
totally
optional,
you
can
also
say
hello
in
chat
also
totally
optional.
F
Hey
everyone:
I
am
sonipon
I'm
a
final
year
undergrad
currently
pursuing
Bachelors
of
technology
and
information
technology
and
I
have
been
a
Linux
Foundation
mentee
last
fall
in
the
celium
project
and
I
am
not
actually
new
to
this
meeting.
But
I
am
joining
after
a
long
time
that
I
can
say
and
I
have
been
maintained.
The
Community
manager
group
mentoring,
cohort
in
2021,
so
I
am
good
to
be
back.
A
A
All
right,
Feel
Free
at
any
time
to
just
hop
in
say,
hi
type
in
the
chat,
always
welcome
right.
So
with
that
we
will
hop
into
updates
and
big
wins.
First
off
I
wanted
to
mention
that
sujay
you
submitted
some
PRS,
which
I
haven't
actually
approved
yet
and
I
doubt
that
anyone
else
has
and
I
do
apologize
for
that,
because
it's
my
first
week
after
kubecon,
but
thank
you
so
much
for
submitting
this.
Do
you
want
to
talk
a
little
bit
about
the
PRS
that
you
submitted.
E
I
think
the
pr
is
a
is
in
draft
mode
like
it's.
Not
okay
and
I
need
to.
You
know,
make
some
decisions
like
in
which
area
we
should
change,
because
in
some
cases
the
the
name
is
in
you
know,
old,
meeting
mine
minutes
and
some
other
things
which
we
are
not
you
know,
maintaining,
maintaining
so
I,
don't
think,
there's
still
worthy
to
change
them.
Indeed,.
B
A
B
B
A
C
A
The
recording,
but
speaking
of
Frederico,
one
of
the
updates,
big
wins
definitely
in
the
big
wins
category
that
I
wanted
to
mention
today
is
congratulations
to
Frederica
who's,
not
on
the
call
before
or
a
successful
kubernetes
contributor
Summit.
He
was
the
operations.
On-Site
operations
lead
for
the
first
time,
I,
don't
think
he
even
shadowed
or
anything
right.
A
A
But
kubecon
Shanghai
is
back
so
kubecon
Shanghai
used
to
be
a
yearly
thing,
though
it
was
only
in
2018
and
2019,
actually
I
guess,
but
it
was
in
Shanghai
both
of
those
years
and
is
coming
back
to
Shanghai.
Now,
obviously
it
didn't
happen
during
the
pandemic,
so
they're.
Finally,
bringing
that
back
this
year,
it's
going
to
be
in
September
I
think
is
that
right.
C
A
A
A
C
A
B
A
B
I
mean,
and
that
idea
kind
of
emanated
from
like
a
work
project
that
I'm
taking
on
that.
You
know:
hey
we're.
Just
gonna
offer
our
help.
You
know
like
the
Upstream
contributors,
we
was
going
to
put
it
out
there
that
we're
here
to
help
you
with
your
cfps.
So
this
is
just
kind
of
a
natural
thing
for
us
to
do.
I
feel
like
if,
if
we
want
to
pursue
it.
B
B
B
C
B
B
A
I
think
it'll
be
fine
yeah,
but
I
will
look
into
the
making
that
a
thing
anyway,
I
feel
like.
There
are
other
things
we
should
talk
about
in
updates,
big
wins
anything
else,
but
I
don't
actually
have
any
on
the
list.
Cube
Shanghai
happening
from
September
25th
to
27th.
Thank
you
new,
ditch
for
looking
it
up.
Thank
you
and
N.
A
is
November
6
to
9th
or
something.
A
B
B
B
B
A
G
A
B
B
G
B
A
G
A
Yeah
we
have
our
own
the
contribexcoms
channel
as
you
posted
in
about
the
same
Spotlight,
so
we're
a
sub
project
of
Sig
contributor
experience
so
contributor
experience.
Has
this
really
Broad
View?
That
includes
managing
a
lot
of
our
GitHub
workflows
and
automation
for
contributors
throughout
the
project?
A
Right,
so
you
would
so
the
basic
process
for
Sig,
Spotlight
and
I
know
in
a
tissue
you're
interested
in
doing
one
of
these
as
well.
So
probably
a
good
thing
to
go
over
and
Federico
mentioned
that
he's
trying
to
get
folks
started
with
these
so
periodically.
We
do
these,
but
so
the
basic
process
for
a
Sig
Spotlight.
Is
you
come
up
with
some
questions?
There
are
some
example
questions
in
the
repo
that
you
can
use
as
some
guidance.
A
We
usually
recommend
that
you
write
up
those
questions
in
a
Google
doc,
and
then
you
use
that
Google
doc
to
conduct
the
interview
asynchronously.
So
you
reach
out
to
the
Sig
channel
that
you
want
to
interview.
Sorry
throughout
you
reach
out
to
the
Sig
channel
that
you
want
to
interview
so
like
Sig
networking,
for
example
the
one
that
we
just
finished
on
slack
and
you
say
hi
I'm
part
of
the
contributor
comms
team.
A
G
B
A
Might
be
worth
it
just
yeah,
because
the
Sig
Spotlight
series
is
something
that
is
always
present
for
our
group.
There
are
so
many
sigs
that
we
have
in
three
years.
We've
managed
to
do
a
very
small
portion
of
them,
even
if
we
did
manage
to
do
them
all
by
the
time
we
did
them
all.
It
would
be
time
to
do
them
again,
so
that
is
an
evergreen
task,
that
anyone
is
welcome
to
pick
up
at
any
time.
So
so
that
is
a
great
Point
Chris
that
we
should
put
that
explanation
somewhere,
I.
D
Just
yeah
I
just
wanted
to
ask
this
one
like
what
are
the
factors
that
are
taken
in
consideration,
while
picking
up
which
seed
needs
to
be
interviewed
or
not,
for,
for
example,
if
we
go
through
it,
we
find
that
signal.
Is
there
say,
Quantity
X
is
there,
and
what?
If
someone
actually
wants
to
write
a
blog,
some.
A
Basically,
basically,
the
criteria
for
picking
a
Sig
for
these
spotlights
is:
does
it
sound
cool
and
also
have
we
done
one
recently
recently
being
within
the
last
like
year
year
and
a
half?
Maybe
if
we've
done
one
within
the
last
year
year
and
a
half
probably
don't
need
to
do
another
one
on
that
Sig.
A
A
A
So
one
of
the
reasons
that
it
takes
so
long
for
us
to
do
Sig
spotlights
usually
is
the
release
cycle.
If
we're
at
an
awkward
point
in
the
release
cycle
like
near
code,
freeze
or
something
and
all
the
co-chairs
are
trying
to
get
their
enhancements
in
for
the
next
release.
That
means
that
they
probably
won't
fill
out
your
questions
for
your
Spotlight
blog
post.
B
A
That's
a
great
idea:
yeah
yeah
and
there's
a
couple
ways
that
we
could
go
about
finding
the
right
people
for
that
you
could
do
the
usual
and
just
go
to
Sig,
release,
Channel
and
say:
hey
I'm,
part
of
contributor
columns.
I
want
to
write
a
blog
post
about
sick
release.
Who
should
I
talk
to?
We
were
thinking.
Maybe
the
Emeritus
leads.
You
could
just
post
that
in
their
Channel
and
they'd
probably
tell
you
who
the
Emeritus
leads
are
right.
Now.
B
A
D
A
This
one
wonderful,
thank
you
for
keeping
an
eye
on
that
by
the
way
I
did
just
submit
the
annual
report.
Firstly,
contribex
annual
report
is
another
thing
that
we
usually
try
to
help
out
with
by
spreading
the
word
that
the
annual
report
exists
and
particularly
calling
attention
to
the
help
wanted
section.
So
the
annual
report
is
not
done
yet
it'll
be
a
while
before
we
have
that.
A
D
F
A
D
A
Does
anyone
actually
do
it
most
of
the
time
no
I,
don't
know
if
that's
true
for
Sig
release,
maybe
they're
a
little
bit
better
about
updating
things
than
most
since
they
do
cycle
out
so
frequently
cycle
in
and
out
so
frequently,
but
for
most
sigs
they
do
not
keep
their
sigdi
yaml
and
owner's
files
up
to
date
in
a
timely
fashion.
Yeah.
A
A
C
B
A
Be
cool,
it
would
be
very
distracting
while
running
the
meeting,
though
so
yeah
sorry,
it's
probably
for
the
best,
but
it
would
be
fun
right.
Also
context
for
folks.
Since
Chris
mentioned
this
earlier,
we
used
to
track
all
of
our
work
in
this
notes.
Dock
in
like
a
table
at
the
top
of
the
dock,
and
it
was
multiple
pages,
long
and
kind
of
terrible
in
many
ways,
so
we're
trying
out
doing
it
in
this
board.
This
is
relatively
new,
so
this
is
how
we're
tracking
our
work.
A
A
A
B
A
A
D
B
B
B
A
B
A
B
B
B
Mean
it's
I
I
am
keeping
track
of
things
and
so
again
for
on
this
one,
especially
because
work
asked
me
to
so.
If
it
does
involve
us
I'll,
let
you
know
I
feel
like
we
could
probably
say
it's
done
for
now.
I,
don't
think,
there's
anything,
that's
not
being
done
in
the
open
that
we
need
to
like
say
something
again.
You
know.
A
B
A
C
A
C
A
Thank
you
very
much
to
everyone
who
contributed
to
that
Micah.
You
are
a
new
contributor,
the
Tish
you
gave
yeah,
you
did
a
bunch
of
new
stuff.
Thank
you.
Nitish
and
sujay
notation
sujay
took
up
some
of
the
like
learning
how
the
management
of
that
project
goes
and
we're
wonderfully
helpful.
So
I
should
have
added
that
as
a
big
win
over
here
and
I'm
gonna.
Do
that
right
now.
Awesome.
A
A
A
B
G
A
B
A
A
A
B
A
B
C
B
A
Oh
yes,
yeah.
Definitely
true,
definitely
true,
anyway,
so
if
you
do
want
to
help
out
with
figuring
out,
what's
going
on
with
the
slackbot,
that
means
interacting
with
another
sub-project
within
contributor
experience.
It
means
getting
familiar
with
automation,
it
means
meeting
a
lot
of
folks
and
it
means
slogging
through
a
mess
of
documentation
that
we
that
may
or
may
not
exist.
F
B
C
A
C
A
B
B
A
Wonderful
and
then
for
the
to
Do's
column,
we
have
the
spotlight
Sig
API
Machinery,
which
has
been
called
out
as
one
that
we
don't
have
yet,
and
someone
would
be
welcome
to
take
on.
There
are
lots
of
others,
but
we
just
put
a
few
in
here-
promote
new
contributor,
Workshop
content.
We
are
still
waiting
for
GitHub
workspaces
on
that
before
we
really
do
comms
blasts
on
it.
Yeah
yeah,
I,
just
synced,
with
Bob
on
that
yesterday.
So
oh.
B
A
Comms
guidelines
for
sensitive
security
topics-
that's
something
that
we
would
like
to
come
up
with.
At
some
point,
there's
also
one
thing
that
we
were
discussing,
which
I
don't
really
want
to
cover
in
a
minute,
is
that
we
periodically
have
to
cover
sensitive
Communications,
not
just
security
topics,
but
losses
in
the
community,
as
we
had
to
do
this
week
and
various
other
kind
of
sensitive
topics
that
might
affect
end
users.
So
there
are
a
number
of
sensitive
topics
that
we
cover,
Communications,
for
which
we
need
better
guidance
and
documentation
around.
B
A
A
Just
put
a
ping
and
contrabix
and
see
who
bites
notify
comms
team.
When
a
new
issue
is
created,
we
had
a
number
of
things
that
we
were
doing
there.
It's
kind
of
on
the
back
burner
from
the
tech
team
as
they're
working
on
zapier,
stuff
and
I
also
have
been
out
for
a
while
man.
Slackbot
is
still
broken.
We
just
moved
that
one
into
two,
so
we
were
one
minute
over,
but
that
is
kind
of
our
work
in
progress.
Sorry
for
the
long
break.
A
It
was
three
weeks
before
we
had
a
meeting
due
to
kubecon,
but
I'm
really
glad
to
see
everyone
back
and
we'll
see
you
all
again
next
week
and
on
slack
so
I'm
gonna
go
ahead
and
stop
the
recording.
But
if
anyone
has
any
questions,
they
want
to
hang
out
a
little
bit.
That
is
perfectly
fine.
Goodbye,
YouTube.