►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220729
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220729
A
So
I
set
up
the
notes
below
our
usual
table
of
active
action
items
which
is
so
long
at
this
point.
It
makes
me
proud
to
see
it
honestly,
it's
great
but
I,
don't
see
any
updates,
big
wins
or
new
items
for
us
to
go
over
before
the
table.
So
if
that's
accurate,
I
guess
we'll
go
ahead
and
jump
into
the
table.
A
I
feel
like
we
usually
find
more
stuff,
while
we're
going
through
the
table
anyway
than
we
do
at
the
beginning,
but
just
in
case
you
never
know.
Sometimes
folks
have
requested
something
on
slack
during
a
week
or
something
it's
good
to
go
over
that
first
Hina
isn't
here,
so
we'll
go
ahead
and
Skip
her
item.
B
I
mean
kind
of
a
win
and.
B
I
think
to
you
yesterday,
caslin
so
I
was
in
the
GitHub
management.
C
B
Yesterday
anyways
earlier
this
week
and
believe
it
or
not,
there
was
a
GitHub
employee
there
and
they
want
to
contribute
to
kubernetes
and
they
were
like
I
work
on
the
projects
board
team.
But
if
you
need
help
elsewhere,
let
us
know
and
I'm
like
oh
contributor:
comms
could
use
help
with
projects
maybe
and
maybe
Hina
could
get
plugged
in
there.
That's
what
popped
it
into
my
mind,
but
it's
Omer
I
can't
say
his
last
name.
That
has
a
door.
That's
Dory!
C
C
C
B
B
A
No,
that's
continue,
lovely
something
we've
been
talking
about
for
a
while
is
coming
up
with
different
roles,
and
one
of
the
roles
that
we
had
considered
is
like
a
PM
type
role,
plus
all
of
the
various
issues
that
we
have
with
GitHub
project
management
tooling.
A
So
it
sounds
like
they
could
potentially
be
really
helpful
person
there.
I
have
to
get
them
in
to
a
future
meeting.
A
C
A
Alrighty,
so
the
next
item
is
that
whole
thing
that's
been
going
on
for
a
while
on
Chris's
article
on
the
squash
command
Frederico.
Did
we
decide
if
you
were
going
to
go
ahead
and
open
up
a
PR
or
hold
on.
D
Yes
and
I
I
I've
looked
into
it,
but
I
I
haven't
yet
opened
it
because,
okay,
before
doing
it
there
there's
a
couple
of
comments.
There
then
I
think
it
makes
sense
to
address
them
before
submitting
a
new
PR.
So
my
plan
would
be
to
clone
or
Fork
the
the
the
existing
file
from
Chris
and
reflects
some
of
those
additional
changes
that
were
requested
on
that
PR
and
then
open
a
new
one
and
I
actually
worked
on
this
in
the
morning.
A
D
Okay,
no
absolutely
yeah,
but
I
I
will
I'll
try
to
advise
major
questions,
because
otherwise
you
would
be
doing
that
in
the
VR
itself.
So
true
yeah,
but
I'm
when
I
come
when
I
have
something
more
more
final,
I
likely
ping
you
just
for
you
to
have
a
very
close
review
and
see
if
it
makes
sense
and
then
I
will
take
it
from
there.
B
A
A
B
So
when
you
do
that
squash
I'm,
starting
to
learn
the
the
edge
cases
like
in
GitHub
management,
it
like
totally
ruins
like
the
messaging
for
the
commits,
where
it's
like
added
so
and
so
to
this
repo,
like
that's
the
commit
message
and
it
just
completely
mingles
that
so
yeah
can't
use
that
tool
there
for
adding
people
to
GitHub.
So
that's.
A
I
should
also
find
that
issue.
A
C
B
Update
the
comments
like
from
the
user
perspective,
yeah
I,
don't
know
because
the
squash
command
puts
like
an
extra
squash
commit
in
so
it's
like
actually
just
invalid
data,
so
you
got
like
three
good
pieces.
C
C
B
Non-Optimal
right
like
for
adding
people
in
in
the
with
our
prescribed,
you
know,
guidance
for
adding
folks
and
I'm.
Sorry,
my
camera's
freaking
out
I
have
no
idea
why?
Okay,
so
with
our
guidance
for
adding
folks,
like
one
person,
gets
added
to
whatever
Sig
per
commit
right.
So
if
I
wanted
to
do
like
10
people
to
KK
I
would
do
that
as
10
different
commits
and
one
PR
and
each
commit
message
is
adding
username
to
Sig
and
they
like,
we
want
individual
commits
for
each
and
every
member
ad.
That's
the
guidance
there
so
yeah!
B
A
C
B
C
A
B
B
A
bunch
of
other
places,
this
isn't
going
to
apply
I,
don't
think,
although
it
could
right
like
we
would
have
to
what
a
they
have
to
figure
out
a
solution
and
then
B
move
over
to
it
and
then
spread
it
across
the
different
orgs,
GitHub
org,
specifically
and
I.
Imagine
that's
just
something
we
can
do
after
the
fact
right
like
please
add
this
bot
to
so
and
so
repo
right,
like
dumb
I'm,
not
sure
I,
know
nibroon
is
he
he
was
he's
involved
with
this,
but
yeah.
B
A
B
I'm
actually
going
to
bookmark
this
just
in
case
it's
my
day.
This
might
come
back
to
us
at
some
point,
I
feel
like
because
we
may
want
that
feature
in
capability
at
some
point.
A
A
B
Being
a
QA
engineer,
it
was
not
like
testing
yeah
and
then
there's
test
infra,
which
is
like
all
it's.
Basically,
all
the
infrastructure
that
makes
kubernetes
run,
calling
it
test
and
for
I
think
they
want
to
do
an
aim
change
to
be
honest
with
you,
because
it's
way
more
than
just
test
infrastructure.
At
this
point,
yeah.
A
Alrighty
so
we'll
move
on
from
that
item.
The
next
item
is
buffer
status.
So
I
mentioned
last
week,
I
had
just
come
back
from
devops
day
Seattle
and
I
noticed
during
that
week.
A
Bob
had
made
an
update
that
someone
from
the
cncf
is
ready
to
put
the
billing
information
on
a
buffer
account
for
us,
but
it
sounded
like
we
needed
to
create
a
buffer
account
and
I
confirmed
that
with
Bob
this
week
and
yesterday,
I
created
a
buffer
account
with
my
own
email
address
to
just
kind
of
start
testing
things
out,
and
so
now
today,
I'm
gonna
ask
Bob
if
we
can
use
that
account
and
like
change
the
owner
on
it
to
something
more
appropriate
or
if
we
need
to
create
an
account
using
some
kubernetes
email
address
or
how
we
want
to
handle
like
the
the
email
address
that
the
buffer
account
is
attached
to
I
guess
this.
B
A
So
once
we
get
that
worked
out,
we
will
have
buffer
and
we'll
need
to
start
learning
it.
Well,
once
we
get
the
science
yeah
person
in
to
fix
it.
B
Yeah,
like
I,
am
here
for
buffer
training.
So
just
let
me
know.
B
A
A
Next
item
Auto,
generating
blog
tweets
and
scheduling,
tweets
I,
said
last
time
that
I
was
going
to
combine
these
and
then
I
didn't
because
they're
kind
of
separate
things
but
they're
both,
hopefully
going
to
be
resolved
once
we
get
buffer,
so
we're
on
the
verge
of
them
being
looked
at
as
separate
items
again.
A
Nice,
so
I'll
just
kind
of
skip
over
these
as
usual,
because
hopefully,
next
week,
we'll
have
we're
in
the
next
couple
of
weeks
at
least
we'll
have
buffer
and
be
able
to
start
looking
into
how
we
fix
these
couple
of
items.
Well,
scheduling,
tweets,
I
think
will
just
be
fixed
by
it.
Auto-Generating
blog
tweets
will
take
a
looking
into
still.
B
Yeah,
the
auto,
regenerating
blog
tweets
I,
think
we
just
need
to
tie
the
RSS
feed
and
with
zapier
to
buffer
and
off.
It
goes
alrighty
just
reach
out
to
Nigel
for
that
I
think
I
think.
B
C
C
B
A
Yeah
and
that's
the
note
on
this-
is
that
rajula
was
blocked
on
this
process
on
getting
it
working
with
the
GitHub
actions
wave
of
posting
to
Twitter,
because
he
needed
to
use
another
open
source
tool
RSS
to
issues
which
was
an
action
that
someone
had
already
created,
but
it
couldn't
be
used
directly
because
we
wanted
to
be
able
to
modify
The
Tweak
content,
so
we
just
kind
of
were
like
actually
we're
just
going
to
switch
to
buffer
anyway.
So
let's
not
worry
about
this
and
we'll
fix
it
once
we
get
buffer.
B
I
will
put
this
bug
in
everybody's
head,
real,
quick,
think
about
how
often
the
Kate's
contributor
account
should
tweet
and
what
times
of
days
it
should
tweet
right
like
because
we'll
build
a
schedule
and
buffer
and
it'll
just
Auto
tweet
out
at
those
times.
So
that
is
something
to
consider.
I
mean
there's
a
lot
of
data
that
we
can
and
research
that
could
throw
at
you
to
say
these
are
the
good
times.
These
are
the
bad
times,
but
in
general,
during
sunlight
hours,
someplace
on
Earth
is
what
we
want
to
follow.
A
A
We'll
figure
that
out,
which
is
actually
our
next
item
is
talking
about
roles,
so
social
media
coordinator
events,
coordinator
Avinash,
you
had
a
hack
MD
out
in
draft.
You
haven't
done
a
PR
for
that
yet
either
have
you.
C
A
I,
wouldn't
cool
I,
don't
think
I
ever
actually
properly
reviewed.
This
I
need
to
do
that
really
finding
things
I
haven't
done.
A
All
right
and
project
manager,
so
the
new
GitHub
person,
might
have
some
interesting
tips
on
how
we
should
design
that
role
and
there's
this
one
that
we've
been
talking
about,
that
atartha
came
up
with,
which
is
like
an
approver
leader
type
role,
who
would
have
kind
of
a
more
broad
overview
of
the
contributor,
comms,
repos
and
and
things
that
we
do
I'm
thinking
they
may
also
be
the
meeting
leader.
A
A
Oh,
the
devsite
role,
yeah,
that's
true,
I
think
when
I
think
we
had
brought
that
up
in
the
last
meeting
where
you
were
here
Chris
and
the
idea
was
to
create
a
role
for
like
ownership
of
the
developer
site
from
the
contributor
comms
group
perspective,
and
you
have
the
most
experience
with
the
site.
So
you'd
be
the
best
person
to
scope
out
kind
of
what
that
role
should
be
I.
A
B
Yeah
true,
how
do
you
want
to
do
it?
I
mean
I,
don't
know
what
do
you
need
for
me?
Exactly
is
just
how
to.
A
B
Cool
I
would
encourage
multiple
people
from
multiple
disciplines
on
that
role
as
well.
C
Okay,
so
Tim
Tim
banister,
we
have
Bob
and
so
Jiffy.
These
are
people
who
are
working
on
contributed
sites,
yeah.
A
A
A
So
yeah,
but
anyway,
the
concept
of
the
developer
role
is
bringing
someone
into
our
group
who
is
more
familiar
with
coding
activities
in
the
project
kind
of
in
a
general
sense,
someone
who
probably
works
as
a
developer.
They
do
a
lot
of
development
type
work
and
they
have
some
understanding
of
where
things
are
in
the
kubernetes
repos.
That's
something
that
we
haven't
really
had
in
our
group
and
I
know.
A
number
of
our
members
are
more
interested
in
learning
about
those
types
of
things.
It
also
comes
up
in
our
work
periodically.
C
C
A
A
C
A
Anyone,
of
course,
is
welcome
to
contribute
to
that.
If
you
like,
create
a
document
somewhere
and
other
folks
can
add
into
it
their
wishlist
items
for
things,
they
would
like
to
learn
that
we
can
kind
of
parse
out
what
the
skills
of
this
person
would
need
to
be.
We
need
to
start
figuring
that
out
at
least
somehow
I.
C
C
B
A
A
So
this
would
be
managing
collaboration
with
the
blog
sub
project.
Making
sure
review
and
other
blog
tasks
are
on
like
our
lists
and
are
getting
completed
and
working
with
storytellers
who
are
working
on
blogs.
A
C
C
Yeah
just
one
thing
about
the
developer
role,
which
I
think
Imran
asked
the
same
thing,
but
what
sites
are
we
looking
at
to
contribute
to
yeah?
What,
because
I'll
contributor,
as
a
contributor
comes,
we
basically
have.
C
We
basically
have
some
what
contribution
to
the
contributor
side,
but
apart
from
that,
what
are
the
other
things
other
repositories
there
are?
There
was
this
contributors
to
it,
Repository.
B
I
mean
and
the
the
actual
case.io
site
is
an
out
of
scope
per
se.
It's
just
not
something
we
publish
to
all
the
time.
Does
that
make
sense
like
we
would
love
to
publish
there
for
publish
it
on
kdev
a
week
later,
two
weeks
later
publish
it
on
kubernetes
dot
IO
with
a
canonical
link
back
to
the
dev
site,
so
it
helps
with
our
search
engine
optimization.
B
A
C
A
Whole
concept
of
this
list
of
roles
is
just
brainstorming.
This
is
not
the
list
of
roles
we
will
have.
This
is
the
list
of
concepts
of
roles
we
might
want
to
have
yeah,
so
combined
yeah,
they
can
be
combined,
they
can
be
changed.
The
developer
role
in
particular,
is
a
very
nebulous
concept
that
was
just
like.
We
don't
have
anyone
to
help
Mentor
these
people.
What
would
that
person
need
to
look
like,
so
it's
fine
to
find
overlap?
A
A
That's
what
it's
sounding
like
to
me
honestly.
Maybe.
B
C
B
B
A
Yeah
I
think
that
stuff
falls
solidly
into
this
approver
leader
type
role
that
we're
Building
Concept
of
cool,
so
I'm
thinking
I
might
just
get
rid
of
this
developer
role
right
now,
because
it
sounds
like
we're
pretty
much
leaning
toward
it
being
consumed
by
the
leader
concept,
as
well
as
the
contributor
site
concept.
I.
C
A
B
A
A
Indeed,
alrighty
so
we'll
move
on
from
that
next
item:
changing
the
contributor
comm's
name,
so
I
checked
up
on
this
this
week,
I
checked
with
harshita,
who
is
the
one
who
created
the
PRS
to
make
sure
that
she
was
all
good
to
go
with
it
and
had
seen
the
recommendation
from
Nate
W
made
a
suggestion
on
how
we
should
do
that.
A
Slightly
differently
sounds
like
we're,
probably
just
going
to
go
forward
with
what
we
have
right
now,
where
you've
got
that
suggestion
later
or
something,
but
the
Blocker
on
that
was
that
Josh
just
needed
the
go
ahead
to
approve
all
of
those
commits
and
he's
currently
at
scale.
So
we
can't
do
that
right
now.
He
suggested
asking
Bob
or
someone
else
if
we
want
to
go
ahead
and
do
that
so
I'll
check
into
that
today.
That's
the
status.
A
A
A
C
A
Atarva
I
gave
you
the
overview
of
what
you
need
to
know
about
creating
a
sick
Spotlight.
Had
you
selected
a
Sig
to
do
yeah.
C
I've
decided
I
will
be
going
with
six
testing
testing,
but
I
haven't
started
anything
yet.
C
B
Frederick,
hello,
now
you're
really
loud.
D
C
C
D
D
So
very
differently
and
slowly
to
avoid
any
sort
of
standing.
The
sixth
challenge,
one
is
still
so
it's
ready,
but
it's
waiting
for
a
problem.
I
guess
that's
even
PR.
It's
it's
done!
I'm,
just
waiting
for
the
okay.
D
D
Architecture,
closure,
so
that's
ongoing.
The
sixth
security
one
I
haven't
shot
back
from
the
person
where
I've
contacted
before.
So
it's
it's
a
nice
at
the
moment.
A
Sounds
good
and
there
was
a
question
while
you
were
out.
It
sounds
like
for
your
interview
with
Sig
architecture
and
I'm.
Guessing
for
six
storage
as
well.
Did
you
do
a
Google,
doc,
back
and
forth
type
thing,
or
what
method
did
you
choose
for
your
interview?
Can
you
still
hear
me.
D
Suddenly
it's
came
to
life,
so
the
question
was
around
the
method
that
I
used
for
my
interview
with
Sig
architecture.
D
As
well
might
as
well
yeah,
so
what
I've
in
the
beginning,
I
wasn't
sure
if
I
should
do,
for
example,
a
live
interview
in
terms
of
a
call,
a
a
video
I
I
haven't
done
that,
like
that,
what
I've?
What
I've
done
for
both
of
them
was
to
use
an
initial
Google
Docs
pile
with
an
initial
set
of
answers
of
questions.
D
Then
they
do
a
first
pass.
I,
add
more
questions,
because
sometimes
for
the
interviews
to
be
interesting,
you
must
really
reflect
the
the
answers
and
do
a
follow-up
Etc,
so
I
I
do
this
two
three
times
do
a
final
reordering
of
of
themes,
because
sometimes
they
make
more
sense.
D
When
you
look
when
you
do
a
final
reads,
questions
that
you
made
in
the
beginning
make
more
sense
at
the
end,
Etc
and
and
that's
it
I
I
review
the
final
form
with
the
with
the
person
that
I've
interviewed
and
then
I
opened
the
pr.
D
B
Stuff
like
that,
that
and
that
when
who
did
it,
anyways
I
did
a
video
in
everybody
with
somebody
and
handed
it
off
to
somebody
else,
and
it
was
a
nightmare
for
them.
Even
though
I
had
like
a
good
transcript
so.
C
B
D
That
that
is
exactly
what
I've
I
thought
in
the
end,
if,
if
it's
to
be
on
YouTube,
it
makes
absolute
sense
to
go
that
route.
If
it's
not,
then
I
prefer
to
add
the
conversational
aspects.
By
doing
these
interactions,
yeah.
A
A
Yeah
I
instead
kind
of
added
that
conversational
element
by
kind
of
giving
my
thoughts
on
each
response
in
between
a
little
bit.
D
True
and
and
and
nice
drawings,
that's.
C
A
C
D
That
note
I'm
not
sure,
if
there's
a
specific
action
item
on
this
later
on,
but
I
did
push
that
change
to
the
blogging
instructions
that
we
have
in
the
contributed
side
around
actually
committing
to
to
opening
the
pr
in
the
right,
repo
and
also
added
some
instructions
around
first
create
a
Google,
Docs
or
hack
MD
for
to
avoid
the
large-scale
reviewing
process
in
GitHub
and
then
follow
with
the
pr
and
the
pr
should
be
open.
First
in
the
contributed
site.
Etc
so
can.
D
It
was
here,
I
have
already
have
had
some
feedback
from
Tim
Bannister
I've.
Also
added
you
as
a
reviewer,
caslin,
perfect.
C
C
B
C
B
They're,
switching
over
to
GitHub
spaces
and
there'll
be
an
Apec
blog
series
about
it
out
this
week,
apparently
good
it's
cool.
C
A
Indeed,
will
be
interesting
all
right
next
item
annual
report,
tweets
I,
realized
way
through
this
week
that
I
totally
dropped
those
tweets
off
of
my
radar
I
know
they're
sitting
there
ready
to
go
so.
Oh.
C
B
A
D
Then,
and
circling
back
to
something
that
Chris
mentioned
a
while
ago,
around
time
zones
and
the
time
of
day
to
tweet,
it
would
be
interesting
as
well
to
see
if
we
could
identify
interesting
ways
that
are
not
overly
invasive,
to
promote
the
tweets
that
we
make
like
having
the
sigs
themselves
retweeting
or
for
the
six
that
have
presents
or
the
other
kubernetes
accounts.
D
B
B
D
B
No
other
cigs
have
Twitter
accounts
and
I
think
that's
by
Design.
The
case.io
account
is
controlled
by
cncf,
but
we
can
always
hit
up
the
social
media,
channel
I.
Think
in
the
cncf
slack
and
drop
our
tweet
in
there
and
we'll
get
picked
up
by
whomever
wants
to
pick
it
up.
I
think
media
channel
in
there.
C
In
charge
of
the
main
kubernetes
Twitter
Twitter
cncf,.
A
And
I
also
often
share
the
links
to
the
tweets
when
we
have
a
new
tweet
in
the
contributor
experience.
A
D
B
B
D
Yeah
and-
and
it
could
even
be
like
once
a
week
or
once
a
month
in
very
specific
ones,
because
just
doing
that
once
in
a
while,
it
would
also
raise
the
amount
of
followers
which
will
then
build
up
and
so
yeah.
So
it's
not
like
asking
for
Retreats
of
everything
that
we
say,
but
in
someone
in
some
specific
ones
it
could.
It
could
be
interesting
to
to
use
that.
B
C
A
Edit
that
in
migration
annual
report
validate
command
is
broken
on
GitHub
at
astrojula,
about
that,
but
rajula
has
been
swamped
with
work,
so
he
hasn't
been
able
to
help
out
with
that.
This
is
another
one
of
those
things
that
would
be
in
that
in
one
of
those
Tech
leadership
roles.
A
A
Based
on
time,
we'll
go
ahead
and
skip
that
there's
an
issue
with
the
developers
site
yeah
on
yeah,
which
is
a
scheduling,
issue,
petition
I.
C
It's
like
a
in
kubernetes
IO.
They
have
the
same
without
this
flag.
So
if
you
just
do
it,
this
will
feature.
So
it's
made
fun
it's
for
the
preview.
This
flag
is
used
for
the
preview.
It
forces
too
so
yeah,
let's
cut
out
the
details,
so
it
might
work
I
guess
it
could
be
simple,
but
I
just
want
to
know.
If
he's
still
working
on
its
assigned
to
him,
I'm
not
sure
I'll
ask
him,
maybe
in
the
GitHub
Bob.
C
A
A
Just
not
here.
Leave
that
to
him
keep
track
of
sick
dog
sub
project
changes
ongoing
thing.
Tweet
content
on
squashing
commits
no
movement
on
that
security.
Comms
guidelines
Avinash.
If
you
want
to
continue
working
on
that,
and
if
you
need
any
help,
you
can
ping
me
on
slack
and
then
Hina
had
that
thing
open
where
she
was
trying
a
couple
different
methods
to
make
sure
that
we're
tagged
when
a
label
is
applied
there
we
go
it's
not
901,
yet
so
I'm
going
to
call
it
good
laughs.