►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220930
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220930
A
Hello
and
welcome
everyone
to
the
September
30th
edition
of
the
contributor
comms
meeting
a
reminder.
We
do
have
a
code
of
conduct
in
place
so
generally
it
says
to
be
respectful
of
your
fellow
speakers
and
attendees
and
generally
be
excellent
to
each
other
and
for
today,
I've
already
got
us
down
in
the
notes
which
I
have
a
bunch
of
notes
for
today,
since
I
actually
was
able
to
attend
the
regular
contribex
meeting
and
they
wanted
us
to.
A
So
we
talked
about
a
lot
of
Calm
stuff
in
there
I
added
a
couple
of
new
things
to
the
table,
just
one
new
thing
to
the
table:
I
think
but
we'll
start
by
going
through
updates
and
big
wins.
But
before
we
do
that,
trying
to
be
better
about
remembering
to
offer
for
anyone
new
to
the
call.
Please
introduce
yourself
now
if
you
would
like
to
totally
optional.
But
if
you
are
new
to
our
group,
we'd
love
to
meet
you
and
know
a
little
bit
more
about
what
you're
looking
for
here.
A
A
A
A
Transition
to
actual
contribution
from
that
for
folks
who
attended
those
new
contributor
workshops.
So
since
2020
we've
been
trying
to
work
on
putting
that
content
together
into
a
virtual
self-paced
format,
so
that
work
is
ongoing.
There's
a
contributor
guide
and
a
developer
guide
and
there's
also
a
non-code
contributor
guide
in
the
works.
The
non-code
contributor
guide
hasn't
really
been
started
yet,
but
the
plan
is
to
start
that,
basically,
after
kubecon
contributor
guide
and
developer
guide
are
in
progress
and
Bob
is
working
on
the
contributor
guide
and
I.
A
A
A
A
A
And
a
couple
of
comms
updates
the
steering
committee
election
voting
is
now
closed
as
of
early
this
morning,
it
technically
closed
September
29th,
the
at
the
end
of
the
day,
September
29th
anywhere
in
the
world
so
early
in
the
morning.
My
time
and
the
contributor
Summit
cfp
closes
today.
So
if
anyone
was
interested
in
putting
anything
together
to
give
at
the
contributor
Summit
today
is
your
last
day.
A
B
D
A
A
But
the
last
I
heard
we
did
not
have
many
cfp
submissions,
I'm,
hoping
that
that
has
changed
this
week
as
we've
been
running
a
more
aggressive
marketing
campaign
for
it
comes
campaign
for
it,
we
did
send
out
a
message
on
that
already
early
this
morning,
Pacific
time
at
least
and
I
think
we
have
at
least
one
more
planned
for
later
today.
Hopefully,
I
don't
know
we'll
have
to
check
buffer
on
that
I
guess.
A
A
A
A
And
there
was
one
like
I
said
that
went
out
early
this
morning.
So
if
you
wanted
to
do
something
similar
to
that,
if
you
wanted
a
reference
but
also
not
too
complicated,
of
a
message
to
put
together
so
I
think
you
can
come
up
with
something
probably
diving
into
new
items.
There
was
one
specific
new
item
request
from
the
contrabx
meeting,
which
was
creating
comms
about
the
new
area,
Community
meeting
label.
A
B
D
A
Yeah
much
appreciated,
there's
one
other
item.
That
is
not
a
new
item
that
I
should
have
put
into
updates.
Big
wins
that
I,
somehow
missed
this
morning,
didn't
need
that
to
be
pulled
which
we'll
mention
in
the
table
as
well,
but
kubecon
tweets
created
the
spreadsheet
already
a
couple
weeks
ago
and
Kim
already
wrote
one:
that's
the
only
one,
that's
in
the
dock
because
we
forgot
to
mention
it
last
week.
A
There
is
a
link
in
the
table
up
near
the
top
of
the
table.
So
we'll
see
it
here
in
a
second,
but
please
please,
please
help
with
kubecon
tweet
planning.
We
have
a
spreadsheet
that
lists
out
all
of
the
tweets
that
we
think
that
we
need
go
ahead
and
claim
them
look
up
the
schedule
and
look
at
the
example
tweets
from
previous
years
and
get
things
written
up,
questions
comments.
B
A
A
A
A
D
A
B
B
C
Yeah
close,
not
plan
is
now
a
command
that
you
can
issue
to
the
KCI
robot,
which
will
then
close
the
ticket
or
issue
and
then
Mark
it
as
like.
We
have
no
plan
to
do
this
as
opposed
to
just
like
rotten
or
stale,
or
you
know
the
normal
life
cycle,
things
that
you
see
as
issues
get
older,
so
you
can
now
close
something
as
not
planned,
as
opposed
to
close
with
no
real
explanation.
C
C
A
A
D
C
A
C
B
A
A
D
D
A
D
A
A
A
C
E
So
I
did
discuss
this
briefly
with
with
Chris
offline,
but
what
I'm
planning
to
do
it's
what's
updated
there
with
the
in
the
GitHub
PR,
is
to
well
take
my
own
experience
in
in
terms
of
the
the
comments
that
were
made
there
and
add
something
around
that
on
the
on
on
the
blog
post.
If
that
is
adequate,
fine,
if
it's
not,
then
I
mean
the
we
can
likely
close
it
and
just
be
move
on
right.
Yeah.
E
A
A
D
This
point
I
just
yeah
yeah,
no
I'm,
not
on
this
exact
approval
stuff
on
GitHub
I
just
want
to
also
ask
about
the
you
know:
there
is
a
slack
board
stuff
which
we
have
teams
as
well.
You
know,
maybe
you
can
just
do
it
as
a
single
task
or
somehow
we
can
yeah,
because
there's
also
a
team.
I
know
that
rajula
want
to
add
me
into
that
or
when
we
had
discussion,
but
unfortunately
he
could
not
do
it.
I
guess
so.
Maybe
that's
something
yourself
or
yeah.
A
D
A
D
D
D
A
There
was
a
there
was
a
change
recently
that
broke
the
slackbot
yeah,
so
I
attempted
to
use
it
this
week
to
send
a
message
about
the
cfp
for
the
contributor
Summit
and
it
didn't
work.
You
didn't
miss
it.
Okay,
it
seems
to
not
be
in
all
of
the
channels
of
the
slack
because
you
have
to
like
add
the
slack.
C
D
So
should
it
should
I'm
interested
to
test
this
channel
out
test
this
bot
to
make
it?
You
know,
okay,
so
that
it's
usable
you
know
so
I
can
so
because
I
see
that
also
like.
If
no
one
is
using,
then
it's
it's
sitting
right
there,
so
maybe
I
can
test
it
further,
but
in
our
test
that
I
need
the
permission
to
you
know.
I
should
be
in
the
team
tour
yeah.
A
A
A
Next
item
rolls,
so
we
have
roll
PR's
out
for
events
coordinator,
Tech,
lead
and
blogging
lead.
Like
I
said,
we
want
to
update
the
title
of
the
events
coordinator,
one
to
include
comms.
We
also
want
to
update
the
tech
lead
role.
Similarly,
and
he
didn't
mention
the
blogging
one
I
don't
know
that
we
need
to
include
comms
in
the
blogging
one,
but
maybe
we
should
anyway
just
to
just
for
consistency
and
maybe
update
the
social
media,
one
as
well.
A
I
was
going
to
make
sure
to
review
these
after
the
session
and
I
didn't
get
around
to.
It
said
like
three
weeks
in
a
row
that
I
need
to
chat
with
you
about
this
and
make
sure
that
we're
all
good
to
go
on
on
Josh's
comments
before,
but
we'll
need
to
update
the
name
of
the
role
too
so
I'm
just
gonna
put
that
in
right
now,
I
want
to
name
two.
A
D
A
E
E
A
E
A
D
The
new
contributor,
Workshop
stuff
I,
mean
yeah,
so
I
mean
you
gave
updates
so
I
think.
Maybe
I
should
just
link
to
this
just
yeah.
This
information
discussed
in
the
contracts
and
then
we
can.
Maybe
this
issue
can
do
close
I,
don't
see
it
will
come
separately
as
a
I
think
separate
documents.
So
I'll
just
add
this
thing
for
this
issue
and
then
maybe
we
can
close
this
thing.
I.
F
A
D
A
C
A
E
Yep
that
one
is
still
in
progress,
I've
been
weekly
pastoring,
the
the
the
the
the
sick
architecture,
sales
for
updates
and
though
it's
while
delayed
I,
do
have
feedback
on
that.
So
it's
so
it's
ongoing
still,
not
so
much
for
the
six
security
one
and
on
that
one
I've,
just
added
a
a
comment
saying
that
I'm
going
to
put
it
on
on
ice
for
the
time
being,
because
there's
really
no
advantage
in
me
going
insisting
every
every
week
without
any
any
feedback.
E
C
C
E
D
A
D
A
E
A
E
It
well
thank
you,
but
it
actually.
It
was
actually
very,
very
useful
for
me
because
the
more
I
got
into
the
docs
blogs
Etc
it.
It
really
helped
me
in
understanding
the
trying
to
to
go
through
the
process
and,
as
you
know,
it's
often
said
Sometimes.
The
best
way
to
learn
is
to
try
to
to
teach
others
so.
A
A
A
A
C
C
A
D
A
D
D
A
C
D
C
D
A
D
D
E
Yeah,
absolutely
and
I
think
that
that
was
one
of
the
things
that
I've
learned
when
I
was
writing.
Is
that
it
wasn't
when
I
started.
It
wasn't
obvious
to
me
even
the
difference
in
contributed
to
one
or
the
other,
so
I've
tried
to
reflect
that,
but
certainly
specific
one
can
add
more
stuff
there
and
I
and
I'll
I'll
more
than
happy
to
to
to
continue
to
be
involved
in
it.
Obviously,.
D
A
I'll,
add
you
in
as
one
of
the
owners
of
this
too.
Then
you
will
be
involved,
one
way
or
another
all
right.
Next
item
security,
comms
guidelines,
this
is
on
hold,
so
I
assume
no
updates
there
right,
ivanish,
yep,
perfect
and
scheduling
tweets
for
non-contributor
comms
members.
This
still
has
not
been
updated.
There's
a
new
PR
darn.
It
I
found
the
new
PR
last
time
and
I
apparently
didn't
update
this
link,
but
Twitter
together,
like
moved
repos
and
so.
C
A
So
we
found
that
last
time
and
I
commented,
it
seems
like
they
grabbed
the
wrong
issue.
For
this.
They,
like
grabbed
a
different
one,
that
referenced
the
issue
that
we
had
as
the
main
one.
It
was
like
a
dupe
kind
of
thing
where
they
were
like
actually
look
at
this
other
PR,
and
that
was
the
one
that
they
moved
into
the
new
org,
so
I
mentioned
that
in
their
new
new
org
somewhere.
D
C
A
C
D
F
B
D
D
C
A
F
Maybe
I
discussed
this
with
Avinash
and
Imran
offline
somewhere,
but
if
we
have
the
time,
can
you
talk
about
like
what
we're
trying
to
unhaul
at
a
specific
time
like
there
is
a
like
a
peer,
that's
open
and
you
on
GitHub.
You
want
to
unhold
that
at
a
specific
time,
or
is
it
like
more
of
tweets
because.
A
F
A
We
have
a
GitHub
contributor,
tweets
repo
which
has
Twitter
together
on
it,
and
so
we
also
have
the
ability
to
if
you
create
an
issue.
It'll
automatically
create
a
PR
from
that
issue,
so
it'll
create
a
PR
of
a
tweet
and
once
that
tweet
is
approved
and
LG
TN
and
merged
it'll
go
out
on
the
Twitter
account.
Okay,
it's
contributors,
so
we
have
the
the
prowl
bot.
If
we
do
slash
hold
in
a
comment.
A
F
C
F
A
Know
probably
more
complex,
because
what
we
have
right
now
is.
We
have
automation
that
can
create
the
pr
from
the
issue
and
then
once
the
issue
once
the
pr
is
merged,
then
it
sends
out
the
Tweet,
so
we'd
have
to
change
that
instead
of
using
Twitter
together,
we'd
have
to
use
this
new
action
that
sends
it
to
buffer
instead
and
uses.
A
F
F
C
F
F
Know
because
it's
just
like
holding
and
unholding
it
just
seems
like
such
a
like
a
roundabout
way
of
doing
the
thing.
We're
actually
trying
to
do.
I
mean
it.
Will
it
works,
but
not
the
way
it's
intended
to,
but
again
I
I
might
be.
This
might
be
my
naive
optimism
on
computer
things,
but
again,
I
will.