►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20221014
Description
[SIG ContribEx] Weekly Marketing Meeting for 20221014
B
B
Not
squared
away,
but
nothing
that
a
meeting
would
necessarily
fix.
I.
Think,
okay,
that
we
can
debate
that
as
we
go
through
our
items
today,
I
think.
B
All
righty,
oh
I've,
got
to
do
my
code
of
conduct.
Reminder
reminder.
We
have
a
code
of
conduct
be
excellent
to
each
other,
be
respectful
of
your
fellow
speakers
and
attendees.
B
D
B
B
That
is
true.
There
is
quite
a
bit
of
readme
updating
that
needs
to
occur,
and
also
we
need
to
do
another
round
of
updates
to
our
team
in
GitHub,
which
has
been
on
our
list
for
a
couple
of
weeks,
but
with
kubecon
coming
up.
I
certainly
haven't
had
time
to
do
it
so
I
figured
that
would
kind
of
happen
after
kubecon
I.
C
A
B
A
C
A
B
I
also
added
the
note
here
about
updating
the
readme,
because
we
now
have
our
team.
B
If
anyone
wants
to
help
out
with
that,
you
would
need
to
look
for
a
marketing
team.
I
know
the
charter
is
going
to
need
updating
as
well
and
replace
any
places
where
we
say
marketing
team
with
contributor
comms.
B
B
B
A
B
Maybe
he
proactively
went
through
or
someone
proactively
went
through
and
got
rid
of
all
of
the
probably
yeah
all
of
the
during
kubecon
week,
meetings.
B
For
context,
folks,
one
time
Chris
was
having
power
washing
done,
could
not
hear
it
at
all.
It
was
very
impressive
foreign.
B
A
D
C
C
E
Read
it
just
before
joining
and
I
didn't
really
I
understood
what
was
expected
for
me
so
should
I
change,
the
content
should
I
just.
A
Change
the
you
could
just
do
a
good
fetchup
stream,
rebased
Upstream
to
master
and
I'll
rebase,
that
to
your
branch
and
make
sure
to
place,
make
sure
it
just
confirmed
that
this
is
under
the
new
subdirectory.
The
contributor
comes
if.
B
B
And
me
because
I
don't
want
to
deal
with
it
yeah
anyway,
so
you've
got
some
options
there,
Frederico
for
how
you.
A
B
On
the
quest,
I
was
also
looking
at
your
requests
this
morning.
Any
updates
you
want
to
give
on
it
while
we're
at
it.
B
Know
the
the
sorry,
the
blog
coordinator,
handbook.
E
Well,
nothing
new
from
my
size.
A
B
Cool
so
I'll
just
go
ahead
and.
A
B
Lovely
so
I'll
delete
that.
B
B
I
believe
that
was
a
tarfa.
You
wanted
to
share
an
update.
D
B
So
this
is
contributor
Summit
email
that
just
went
out
yesterday.
A
D
B
D
We
were
just
going
to
do
a
regular
social
and
registration
comr
right,
but
then,
after
drafting
the
my
email,
I
I
got
to
know
that
the
schedule
was
also
alive
now
so
Bob.
B
Lovely,
oh
one
thing
that
Josh
mentioned
around
that
time
was
that
we've
had
at
least
one
or
two
people
say
something
about
attendance
for
the
social
if
you're
not
attending
the
contributor,
Summit
or
yeah,
so
making
sure.
Maybe
writing
a
tweet
or
writing
a
reply
to
that.
If
we
can
just
be
aware
that
if
we
get
any
questions
about
that,
you
have
to
be
part
of
the
contributor
Summit
to
be
able
to
go
to
social.
D
A
B
Cool
any
other
updates,
big
wins.
B
B
It's
in
the
the
table,
but
so
this
year
we
only
had
one
new
person
volunteer
and
actually
write
some
tweets
and
they
only
wrote
three.
They
did
put
them
in
buffer,
but
they
put
them
in
in
the
wrong
time
zone
which
I
keep
forgetting
to
tell
them
which
we
can
fix.
But,
like
there's
a
lot
that
is
not
covered,
I
was
talking
with
Bob
about
this
yesterday
and
he
said
he
was
going
to
walk
off
some
time
and
write
some
tweets.
B
So
what
I
usually
ask
folks
to
do
is
like
here
is
the
maintain
your
track
block
and,
let's
just
do
an
overview
of
what's
happening
with
that
block
Bob,
with
his
excellent
context
of
the
contributor
Community
actually
went
in
and
checked
for
sessions
that
he
thought
would
be
particularly
interesting
to
contributors
and
did
specific
session
promo
tweets.
Also,
one
thing
we
were
talking
about
last
night
is
that
we
should
probably
do
more
Communications
campaigns
around
kubecons
to
encourage
contributors
to
write
their
own
tweets,
promoting
their
sessions
and
submit
them
to
us.
B
So
there
are
a
lot
that
are
not
covered:
I
noticed
Frederico.
You
went
in
and
grabbed
ownership
of
some
right
before
this
meeting
and
imrano
did
the
same.
Much
appreciated
so
yeah
any
help
that
you
can
give
with
writing
tweets.
We
need
them.
Asap
I
have
four
work
days
before
kubecon.
B
F
B
F
F
A
B
Yeah
much
appreciated
when
I
first
created
this
and
presented
in
this
presented
it
in
this
meeting
I
had
mentioned
that
I
didn't
fix
up
the
timing
of
the.
B
In
this
one,
so
if
you
are
looking
to
help
out
with
maintain
a
track
block,
tweets,
Imran
and
Frederico,
you
volunteered
for
those,
do
you
watch
out
that
the
timings
are
not
necessarily
accurate,
go
by
the
block
one,
two,
three,
whatever
make
sure
that
you
just
cover
all
of
the
blocks
and
okay
yeah.
Thank
you.
B
C
C
B
C
B
B
Yeah
yeah,
so
if
there
are
any
issues
with
that
I
know,
one
of
the
other
items
we'll
cover
today
is
Imran
has
been
working
on
fixing
up
the
validate
command.
B
F
F
F
F
But
but
what
I
felt
like
we
have
a
complete.
We
need
to
have
take
the
content,
the
Tweet
file
and
then
based
on
some
specific
merge
to
a
main
branch,
and
then
we
take
the
content
file
to
the
buffer.
Actually,
this
I
checked
at
least
it's
not
possible
with
zapier.
Maybe
we
have
to
think
about
other
Solutions.
Maybe
we
could
create
some
sort
of
RSS
speed
to
zapier,
so
that's
possible.
We
can
with
our
automation,
we
can
publish
the
contents
with
RSS
feed
like
some
XML
or
something.
Then
you
can.
F
B
A
A
B
I
feel
like
there's,
probably
something
we're
missing
there,
but
hopefully
we'll
find
it
all
right.
Coming
back
up
to
the
top
of
the
table,
hello,
Hina-
you
are
here
today
so
for
your
items.
We
were
looking
into
automatically
adding
a
comment
that
tax
comes
when
the
comms
team
label
is
applied,
I.
B
A
I
mean
I,
don't
I'm
gonna
restart.
This
I
had
an
unexpected
travels
and
crazy
work
and
a
broken
laptop.
So
now
yeah,
so
I'm.
D
C
A
Up
the
new
laptop
and
then
I'll,
get
back
onto
this
I
will
mess
something
up
very
likely
and
then
stress
out
about
it.
But
this
time
I'm
gonna
ping
people
in
slack
and
not
just
sit
there
and
stress
yes,.
A
A
Well,
when
everyone
is
back,
I
will
Sage
I've,
never
actually
saged,
but
maybe
this
is
a
sign
an
honor.
Can
you
see
your
resume.
D
So
I
dig
in
some
of
the
test
info
repository
and
I
had
some
few
interesting
things
to
bring
up.
Firstly,
do
we
really
want
to
focus
on
just
building
up
a
solution
where
we
just
tag
add
contact?
If
someone
tags,
they
will
click
on
two
bags
and
only
for
the
people
who
are
in
this
at
contrabix
coms.
Do
we
really
need
to
do
a
solution
where
only
they
should
get
notified
on
slack,
because
we
don't
have
a
private
group
for
only
the
members
of
AD
contributor
comms,
so
we.
B
Goal
here
is
to
make
sure
that
when
there
is
something
that
needs
our
team's
Attention,
our
team
is
getting
alerted
about
it
because,
currently,
if
like
our
label,
is
applied
to
either
an
issue
or
PR,
because
we
added
our
our
GitHub
team
into
the
issue.
Template
so
that
if
someone
creates
an
issue,
we're
hoping
that
that
will
alert
us
that
someone
created
an
issue
that
needs
our
attention.
B
B
D
So
the
good
news
is
that
we
there's
a
solution
for
that
for,
but
it
is
not
just
for
user
groups
like
our
contributor,
comms
user,
who
brought
there
is
a
solution
for
mentioning
channels.
So
in
case
a
Sig
is
mentioned
in
the
GitHub
GitHub
issue
or
PR.
Then
they
there's
a
there's
a
slack
message
on
that
particular
Channel,
which
we
can
Define.
If
there
is
a
label
for
contributor
comes,
then
we
can.
Then
we
get
a
message
for
NC
context.
Comms
we
can
do
that,
but
if
we
want
to.
C
D
C
C
C
C
C
C
C
C
A
D
D
C
A
B
All
right
so
we'll
move
on
to
the
next
item
then,
which
is
Keep
Calm
tweets.
We've
already
talked
about
that
quite
a
bit,
so
not
much
more
to
say
there
kubecon
is
imminent.
If
you
have
capacity
to
help
write
a
few
of
these
tweets
over
the
next
few
days.
Please
please
please,
please
grab
some
and
do
so
because
we
really
need
the
help.
C
Dims
forwarded
an
email
to
CNC
ftoc
about
the
new
code
of
conduct
committee
thingy
that
has
spun
up
so
they're
organized
they're,
putting
together
code.
It's
out
there
I.
A
C
A
B
E
E
E
According
to
the
feedback
that
I
got
at
the
time,
I
made
some
changes
to
the
original
documents
and
I'm
going
to
solicit
some
additional
comments
to
see
if
they
adequate
and
if
they've
solve
the
main
objections
that
were
conveyed.
That's
it.
B
E
E
About
okay,
that's
the
one
with
the
so
yeah
I
need
to
go
there
and
add
a
comments
as
a
reply
and
as
well
saying
this
is
the
new
version
and
I
addressed
it
like
this
and
that,
but
the
new
version
as
additional
structuring
around
what
was
essentially
already
there.
But
in
order
to
make
some
of
the
examples
more
so
focusing
more
on
a
couple
of
two
or
three
use
cases
and
then
just
having
the
rest.
E
B
B
Alrighty
so
I'll
move
on
to
the
next
item,
which
is
that
we
need
to
update
the
owner's
file.
We
already
mentioned
that,
like
I,
said
I
at
least
will
not
be
able
to
work
on
that
until
after
kubecon.
So
probably
just
wait
on
that.
B
So
I'll
go
ahead
and
move
on
to
the
next
item:
updating
the
GitHub
team.
So
there's
two
things:
there's
the
owner's
file
and
there's
the
GitHub
team
I
think
we
decided
that
it's
just
updating
the
GitHub
team
contributor,
comms,
GitHub
team,
yeah.
B
And
I'll
move
on,
oh
yeah,
the
slackbot
thing
being
still
broken
Imran.
You
said
you
were
gonna.
Try
to
look
into
that.
A
little
bit
were
you
able
to
so
yeah.
F
I
I
didn't
progress,
anything
on
that
because,
as
I
said,
I
need
some
access
on
it,
so
but
I
chatted
with
Josh.
So
not
yet
we
haven't
got
any
information
or
maybe
he's
still
busy,
but
I
decided
to
I
have
the
source
course
I
tested
with
me
private
slacker
and
try
to
check
the
what's
actually
failing
and
yeah
and
so
on.
So
I
just
start
doing
something
on
it.
So
it
could
be
useful
by
the
time.
Charles
has
someone
reports.
What's
the
actual
problems
I
can
able
to
map
it
and
fix
the
problem?
B
F
You
have
to
someone
has
to
manually,
add
it
so
someone
has
the
rights
someone
who
is
member
of
that
particular
team.
Yeah
can
add
the
chance
which
I'm
not
in
so
probably
charges
already
there.
So
he
can
do
that.
It.
B
So,
generally
speaking,
we
should
be
able
to
add
the
slack
bot.
I,
don't
know
what
the
slackbot's
user
is.
There's
a
couple.
Actually
that
say
slash
bot.
It's.
F
F
D
Yeah,
there's
a
slag
just
a
second:
there
is
slack
config
User
Group.
So
that's
where
you
that's,
where
yeah,
where
you
can
add,
so.
F
C
B
B
A
D
Imran,
did
you
talk
with
rajula
after
the.
F
D
F
Think
the
bot
is
not
in
use.
Let's
say
there
is
some
problem
which
is
hindering
as
to
use
the
body
just
one,
as
mentioned
the
manually,
adding
to
several
channels.
That's
one
thing
that
feature
is
missing
and
maybe
something
else
so
I
need
to
capture
what's
missing,
and
maybe
so
meanwhile,
we
can
I
think
after
the
knowledge
transfers
or
we
can
also
privately
test
with
her.
B
Means
if
you
try
to
post
a
message
to
what
I
was
trying
to
do
is
I
was
trying
to
post
a
message
to
a
bunch
of
channels
and
the
bot
was
just
like
you.
Don't
have
access
to
this
channel
so
delete
that
channel
and
it
would
be
like
you
don't
have
access
to
this
channel
because
it
wasn't
in
any
of
the
channels.
A
C
C
C
B
D
Okay,
so
just
one
more
thing,
so
why
don't
what's
the
problem-
and
we
can
just
manually-
add
that
bot
in
that
channel
and
it's
it's
done
so
what's
the
not
working
thing.
B
B
Know
what
that
was
just
that
was
fixed.
B
D
F
A
C
B
C
This
is
the
the
slack
User
Group.
You
know
how
you
tag
at
contributor,
comms
it'll
right
now
it
will
still
say
Upstream
marketing.
When
it
you
know,
Auto,
populates,
right.
B
C
C
E
B
C
E
A
B
Our
initial
set
of
PR's
was
to
address
places
where
we
have
the
URL,
so
we
fixed
a
bunch
of
places
that
have
the
URL
and
by
fixed
I,
mean
broke
until
now.
Now
they
are
fixed,
but
the
terminology
we
did
not
do
like
a
cohesive
PR
for
so
that
will
be
all
over
the
place.
C
C
F
B
B
A
And
just
one
more
question:
should
we
title
case
contributory
comms
as
we
refer
to
like
contributor,
comps
team?
We
have
it's,
it's
mixed.
It's
a
mixed
bag
of
title
case
and
a
lowercase
for
a
marketing
team
or
Upstream
marketing
I've,
seen
both
just
I.
C
B
All
right,
so
we
have
nine
minutes,
left
we'll
do
what
we
can
to
get
through
the
rest
of
this
events.
As
usual,
there
are
still
several
PR's
out
I
know:
I
haven't
had
a
chance
to
go
through
and
approve
a
lot
of
them
and
I
feel
bad
about
that
I
apologize
qcom,
but
we
do
still
have
out
PR's
on
the
events.
Roll
Josh
had
requested
that
we
update
this
to
the
comms
event.
Lead
name
and
Avinash
had
gone
through
and
made
some
changes
last
week
after
our
meeting.
B
I
think
Josh
was
also
interested
in
more
information
in
the
shadowing
section,
which
I
should
talk
with
Avinash
about.
B
Great
opportunity
there
for
folks
interested
in
website
management,
static
sites,
so.
F
A
F
F
F
I
haven't
done
any
meat
stuff
in
Hugo,
but
I
think
so
I
was
just
thinking.
Maybe
this
could
be
a
task
like
so
to
sync.
The
blog
post,
you
know
like
yeah,
could
also
tweet
something
so
I
think
we
don't
have
this
stuff
ready
right.
I
mean
whenever
we
have
new
blog
posts
coming
in
okay,
start
IO:
okay,
start
Dev.
We
don't
have
a
direct
sync
mechanism,
so
this
is
also
rssp
could
help
and
do.
C
C
Is
something
we
also
tweet
out
yeah,
but
for
lack
of
a
better
term?
It's
in
Nigel's
personal
account,
which
we're
gonna
get
paid
and
turned
into
an
official
contribex
like
zappy.
F
F
F
C
A
B
The
next
role
that
is,
oh
okay,
so
we
got
that
one
merged,
so
the
tech
lead
role
is
merged.
I
had
approved
that
last
time.
A
B
Cool,
so
we
have
two
open
roll
PR's
events
and
blogging.
B
Keep
moving
those
forward.
We
have
four
minutes
left
so
kind
of
run
through
the
rest
of
these,
creating
a
project
overview
page
for
the
contributor
site,
Imran
any
updates
there.
I
think
this
is
just
kind
of
on
hold
right.
F
So
I
I-
maybe
I,
can
change
this
to
this.
So
as
I
said
so,
I
got
some
inputs
from
what
Chris
said
last
time.
So
I
spoke
with
Bob
and
I
got
some
material
from
the
external
lines
Gateway
or
externals.
There
I
think
content
for
the
course
so
I
will
span
out
so
so
the
code
base
tool
is
missing
from
their
document
that
part
one
day
I'm
working
on
it,
so
I
have
some
insight
on
it.
C
C
B
As
we
know,
the
GitHub
repo
name
has
been
updated.
You
see
something
file,
a
PR,
six
spotlights
Frederico
is
still
working
on
architecture
and
actually
got
some
movement
on
security
and
Ron
wanted
to
work
on
instrumentation.
There
are
a
few
other
people
who
wanted
to
work
on
some
six
spotlights
so
Frederico
kicks
off.
E
Yes
quickly,
so
the
situation
reversed
a
bit
from
last
week,
so
we
have
some
additional
movement
in
Sig
architecture,
so
the
with
content
being
added
to
the
to
the
docs
file,
not
a
lot,
but
still
its
movements,
which
is
good.
Six
security,
I
I.
Last
time,
I
I
got
the
attention
of
another
share
and
I'm
I'm
I've
insisted
I'm
still
waiting
for
the
confirmation
that
I
can
start
with
the
with
the
interview
and
that's
the
status
for
the
for
these
two.
E
B
Sure
sounds
good
anyone
else
actively
working
on
any
six
spotlights
in
here.
E
Yep
I
am
thinking
to
work
on
six
CLI
awesome.
Currently,
I
am
understanding
it,
so
yeah
I
can
work
on
it.
B
Sounds
good
excited
to
see
you
back?
Okay,
if
you
need
any
help
as
you're
pursuing
that,
let
us
know
in
our
Channel
I
shared
with
you:
the
resources,
for
example,
questions
and
how
to
create
the
the
blog
post
and
everything
right.
So
if
you
lose
any
of
those,
if
you
need
any
help,
Reach
Out
sound
like
a
plan
yep.
B
So
the
way
that
I
did
this
when
I
did
my
last
six
Spotlight
quite
a
while
ago,
was
I
reached
out
to
the
Sig
in
their
Channel
I,
said:
hey
I'm,
part
of
the
contributor
comms
team,
I'm,
looking
to
write
a
spotlight
on
your
Sig.
Who
should
I
talk
to
about
it?
Then
I
came
up
with
kind
of
some
general
questions,
because
I
already
knew
a
little
bit
about
that
area.
B
So
you
don't
have
to
know
a
lot
about
the
Sig
to
write
the
questions
it
sounds
like
Imran
is
going
above
and
beyond
with
exploring
his
Sig
and
trying
to
create
specific
questions,
but
they
don't
have
to
be
that
specific.
The
example
questions
that
we
have
in
the
repo
are
fairly
generic,
so
you
could
ask
fairly
generic
questions
whatever
you
are
curious
about
about.
Sig
CLI
would
be
relevant
questions,
so
you
could
go
from
there.
You
can
start
the
interview
without
having
deep
knowledge
of
the
Sig
would
be
my
advice.
D
E
Okay,
I
I
had
some
some
some
some
guides
guidelines
with
Imran,
maybe
yeah.
B
B
But
one
thing
to
note
is
that
your
audience
here
might
not
know
anything
about
the
Sig.
Just
like
you
so
make
sure
that
you
are
learning
interesting
things
about
the
sick
and
your
audience
will
too.
B
Cool
anyone
else
working
on
Sig
spotlights
we're
already
two
minutes
over,
but
I
do
want
to
check
in
on
six
spotlights
before
we
go
sounds
like
not
so
thank
you
so
much
everyone
who
is
working
on
six,
spotlights
everyone
who's
working
on
anything.
We
really
appreciate
you
I
think
we'll
stop
there
for
now.
I,
don't
think.
There's
anything
particularly
pressing
down
in
here
anyway.
F
I
just
want
to
update
one
stuff,
so
maybe
we
all
touched
one
yeah,
this
validate
command
stuff,
I
yeah,
it's
kind
of
a
reflective
thing,
yeah,
so
I
just
fixed
it.
So
it
could
be
a
expression
which
I
fixed
it
I
mean
fixed.
It
I
created
a
PR,
so
I
don't
know
if
this
is
the
wrong
one.
That
is
the
wrong
one
I
created
on
the
new
one,
so
yeah.
F
So
yeah
but
anyway,
so
if
anyone
as
we
spoke
today,
so
if
newcomers
want
to
use
it
or
anyone,
who's,
gonna
use
the
GitHub
way
of
creating
the
tweets,
I'll
have
a
view
on
the
validate
and
all
the
things
going
on.
I'll
have
eye
on
it.
So
if
anything
broken,
if
anything
is
broken,
it
needs
to
fix
I
think
my
packs
would
work.
So
it's
not
very
urgent
to
fix
this
one
because
it's
kind
of
like
it
happens,
I
have
not
seen
it
happen
happens
very
rarely.
F
B
B
Cool
so
we'll
grab
the
right
PR
for
that
maybe
also
put
it
in
the
channel
in
case
anyone
wants
to
take
a
look
yeah.