►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20221209
Description
[SIG ContribEx] Weekly Marketing Meeting for 20221209
A
Hello
and
welcome
everyone
to
the
Friday
December,
9th
Edition
of
the
contributor
comms
team.
It's
getting
close
to
the
end
of
the
year.
I
have
asked
Bob
by
the
way,
just
go
ahead
and
say
this
now,
because
it's
on
my
mind,
I've
asked
Bob
to
remove
the
last
two
meetings
of
ours
of
the
year.
So
we'll
have
a
meeting
next
week,
but
then
the
next
two
we
won't
have
one
and
then
the
first
week
of
January.
We
also
will
skip
oh.
A
So
yeah
aside
from
that,
remember
that
we
do
have
a
code
of
conduct
that
basically
says
to
be
respectful
of
your
fellow
speakers
and
attendees
and
generally
be
excellent
to
each
other,
and
with
that
I
think
we
can
get
started.
I,
don't
see
any
new
names
on
the
call,
so
I
think
we
can
dive
right
into
it.
Today.
A
There
it
is
cool,
so,
let's
start
off
with
our
daily
notes,
with
updates
and
big
wins,
I
added
one
thing
on
here
from
the
Sig
control
X
meeting
this
week
we
have
a
bi-weekly
meeting
for
the
whole
state
in
case
anyone
didn't
know
that
and
it
was
about
labels
since
we've
been
talking
about
labels
so
much
lately,
I
thought
it'd
be
pretty
interesting
for
us,
it's
a
PR
where
someone
wants
to
do
some
work
to
improve
label
automation.
A
It
would
be
really
good
if
we
could
do
it.
I
think
the
the
opinion
in
the
meeting
was
that
it
would
be
quite
difficult
to
do
it,
but
if
someone
wants
to
dedicate
their
time
to
figuring
out
the
the
challenges
of
it,
that's
all
the
better
for
us.
A
So
this
person
wants
to
add
five
additional
labels,
which
are
automatically
added
based
on
criteria
to
make
it
more
quickly
visible.
What
state
the
pr
is
in
and
what
kinds
of
reviews
and
approvals
it
needs.
A
There's
been
One
reviewer,
who
has
lgtmed
I,
think
that
should
say,
but
the
pr
has
not
been
approved
by
an
approver
from
the
owner's
file
waiting
on
author
reviewer
has
provided
feedback,
and
the
author
needs
to
address
it
abandoned
the
mirror
has
been
in
wait
on
author
state
for
an
extended
period
of
time
and
tests
fail.
So
one
or
more
tests
are
failing.
C
A
label
this
is
the
in
the
in
this
release:
retro
one
of
the
things
that
I've
added.
It's
not
very
far
from
this,
because
in
in
this
release
tracking
feature
blocks,
it
becomes
a
bit
more
often
art
than
a
science
to
know
when
things
are
ready
have
been
reviewed,
are
still
waiting
so
having
some
more
formal
indication
of
things
would
especially
make
them
much
easier
to
to
filter
out
and
track
right.
C
So
I
I
haven't
had
any
look
into
this,
but
actually
I
will
because
it's,
it
seems
interesting.
A
Yeah,
there's
a
bunch
of
comments
on
here
to
kind
of
dive
into
the
the
challenges
of
this
one
that
I
see
here.
That's
easy
to
pull
out
is
Josh
mentioned
that
PRS
that
touch
multiple
directories
may
require
approval
from
multiple
owners,
so
that
could
make
the
owners
one
a
little
bit
tricky
and
clearly
there's
a
bunch
of
other
things
that
are
going
to
be
a
little
bit
trickier
to
figure
out
but
I
think
it's
a
great
concept,
foreign
I
think
everybody's
pretty
excited
about
it.
A
E
A
C
You
updated
on
that
it
is
I,
am
I'm
yeah,
it's
exactly
like
that,
and
it's
planned
to
go
early
U.S
morning.
So
it's
right.
B
C
A
B
A
A
And
it's
helping
I
think
compared
to
where
we
were
before.
If
the
newer
folks
can
believe-
and
this
is
better
here-
cool
any
other
updates
and
big
wins.
A
A
A
A
B
A
I
think
that's
probably
good
aside
from
updates
on
spreadsheet
stuff,
so
we'll
move
into
the
table
after
I
ask
for
new
items
this
time
of
the
year.
I
hope
there's
not
really
any
new
items
coming
up
at
least
nothing
big,
but
any
new
items
that
people
have
heard
of
that
need
help.
Oh
actually
in
the
contribex
meeting.
They
were
talking
about
the
community
meeting
I
think
they're
not
going
to
have
one
this
month.
No.
A
Yeah
there
was
a
little
bit
of
there's
something
that
came
up
where
we
were
like.
Oh
that
would
be
a
good
topic
to
have
in
the
community
meeting
and
Laura
was
having
trouble
getting
topics
for
it.
A
So
she
was
saying
that
she
wasn't
going
to
have
the
community
meeting
this
month,
but
there
was
a
topic
on
the
back
burner,
so
there'll
probably
be
one
in
January,
I,
guess
nice,
so
I
guess
I'll.
Add
that
to
updates
really.
E
I
have
two
things
one
you
know
gotta
share
my
new
family
member,
since
everybody
who
has
been
around
me
knew
how
awful
it
was,
but
that's
not
really
why
it's
just
she's
in
my
office
and
wanting
to
eat
my
trash
can
but
I
I
wanted
to
let
you
know
that
so
I'm
also
part
of
the
cncf
tag,
contributor
strategy,
and
so
this
is
lack
of
sleep.
E
Catherine
and
I
presented
a
proposal
to
them
on
on
how
to
how
to
help
projects,
Implement
non-code
contributions
and
the
importance
of
non-con
contributions
through
the
contribution
ladder.
So
Noah
was
on
that
call.
I,
don't
know
if
he's
on
this
one,
and
he
was
talking
about
the
work
that
kubernetes
had
also
done
so
I
wanted
to.
E
Let
you
know
that
Catherine
from
boyant
and
I
are
starting
that
project
with
cncf
and
we'll
be
sharing
it
here
with
this
team
as
well
as
we
do
that
you
know,
because
if,
for
those
of
you
that
know
me,
you
know,
my
passion
is
really
helping.
People
understand
that
both
community
and
marketing
and
visibility
is
as
important
to
a
project,
as
you
know,
as
code
contributions.
E
Well,
in
my
opinion-
maybe
not
in
yours
so
and
I
know
that
kubernetes
did
some
work
and
we'll
be
using
some
of
your
work
within
that
tag.
So
just
kind
of
letting
you
know
that
I'm
also
working
on
that
and
I'll
be
bringing
that
information
to
this
group
group
as
it
is,
as
you
tell
me
that
it's
important
and
makes
sense.
A
Wonderful,
what
was
the
the
name
of
the
tag?
Cncf
tag.
E
Right,
there's
like
no
sleep,
yeah,
sorry
about
that
and
I
can
add
a
couple
notes
in
there
based
on
what
our
action
items
are
and
I
can
add
a
link
to
our
Google
slide.
If
this
team
is
interested
in
that
you
know,
our
goal
is
to
make
this
available
for
all
projects,
and
not
just
you
know,
yeah
to
all
projects,
so
that
projects
that
do
want
to
recognize
non-code
contributions
have
some
guidance
on
how
to
do
that.
A
E
Sounds
like
yeah
well,
I
would
love
that
if
that's
appropriate,
but
you
can.
Let
me
know
if
that
is
appropriate
or
helpful
to
this
group
or
not
I'm.
Still
learning
about
you
know
what
each
group
yeah.
Don't
don't
judge
me
I
know
I'm
from
cncf.
I
still
just
don't
know
what
all
these
different
groups
do,
but
if
that
is
of
value
to
this
group,
I'll
definitely
be
happy
to
to
share
whatever
you
all
would
like
on
that.
Our.
A
Charter
is
about
sharing
information
that
the
contributor
Community
should
know
about,
and
also
sharing
the
word
outside
about
the
wonderful
work
that
contributors
are
doing
so
I
think
this
makes
sense.
A
lot
of
contributors
within
the
project
will
move
around
throughout
the
course
of
their
time,
with
the
project
and
I.
Think.
That's
always
a
good
message
for
folks
to
hear
that
these
types
of
opportunities
exist
and
they
are
important.
So
we
could
do
something
like
kate's.dev,
blog,
post
or
yeah,
maybe
help
out
with
something
yeah.
E
We're
not
close
to
that
at
all
yet,
but
thank
you.
A
A
A
And
we
need
to
move
stuff
over
into
that.
Other
drive
also,
which
I
still
haven't
done
so
sounds
like
a
good
opportunity
opportunity
to
make
a
new
note
stock.
A
Automatically
adding
a
comment
tagging
our
comms
team
when
things
when
a
label
is
applied
that
is
still
kind
of
on
the
back
burner,
I
think
unless
anybody
particularly
wants
to
pick
it
up
here
at
the
end
of
the
year.
Otherwise
we
can
look
at
it
again
in
January.
A
Next
item
moving
our
kubecon
tweets
sheet
into
the
new
Drive
I
still
haven't
done
that
yet,
but
I
do
have
the
link
to
do
it
here.
So
maybe
that'll
be
a
nice
easy
task
for
me
to
do
later.
Today,.
B
A
A
F
A
A
A
Noted
next
item-
frederico's
blog
post
I
reviewed
it
on
Monday
Frederico
I
made
it
all
comments,
because
most
of
it
is
just
little
nitpicks.
So
you're
welcome
to
ignore
them.
There's
one
thing
where
I
kind
of
rewrote
a
piece
and
that
might
be
useful,
but.
C
It's
done,
it's
wonderful
for
this
meeting,
I,
reflected
your
changes
and
also
a
quiz
once
and
I
resolved
all
the
issues.
So
wonderful.
C
No,
no
but
I
I,
I
I,
reflected
especially
that
one
on
adding
a
bit
more
insight
into
why
we
don't
have
wants
to
have
this
long
history
of
commits
I
added
a
link
to
the
GitHub
workflow
process
and
and
made
a
new
paragraph
on
that.
Apart
from
that,
it
was
just
the
Nets
I
reflected
them
all.
A
B
A
A
Update,
okay,
I
just
won't
even
comment:
you
can
go
ahead
and
do
that
maybe
ping
in
chat
when
you're
done
it
probably.
C
A
B
B
A
And
we
also
need
to
update
the
Upstream
contributor
comms
GitHub
team
Avi
Nash
had
offered
to
help
me
out
with
that.
He
pinged
me
this
week
on
it
and
we
discussed
what
we
could
do
there
I
think
the
main
thing
that
I
needed
there
was
someone's
just
to
kind
of
keep
me
accountable
and
make
sure
that
I
kept.
That
on
my
mind,
so
we
were.
B
B
We're
just
gonna
have
to
list
out
like
who
else
is
I
mean
actually.
A
E
A
To
need
to
do
the
same
work
for
both
cool,
so
Avinash
I
think
you're
off
the
hook
for
this
one
really
me
and
Chris
will
work
together
on
it,
but
I
know
that
I
can
reach
out
to
you
if
I
need
help.
Thank
you.
A
C
Sorry,
what
day
should
I
change
this
to
today,
next
Wednesday
somewhere
in
between.
A
F
G
B
A
C
That's
yeah
there
are,
there
are
feature
blogs
that
are
going
to
the
only
day
that
they
are
not.
There
are
no
feature
blogs.
It's
Wednesday,
so.
C
Yeah
so
Monday!
No,
let
me
rebase
and.
F
I
Yeah,
so
I
got
approval,
so
the
pr
got
merged.
At
least
they
have
been
added
to
the
team.
So
now
I
can
code
and
Export
and
I
got
the
yeah.
I
got
help
from
Mark
as
well.
Last
week,
Mark
reached
out
for
the
shadowing
role
for
the
tech
tech
part.
They
also
reached
out
to
me
to
help
on
this
dashboard
and
it
probably
will
work
on
it
together.
Actually
this
week
onwards,
I'm
actually
on
vacation,
so
I
don't
plan
to
work,
but
that's
not
the
Year
I
hope.
Oh.
I
B
F
D
Sorry
I
had
a
quick
question:
I
got
a
drop
at
11
30
for
a
conflict,
but
I
was
thinking
about
doing
a
spotlight
on
16
scheduler.
Do
you
know
anyone
who's
working
on
that
already
or
not?
I.
D
D
C
Yeah,
no,
it
started
with
the
blog
with
the
six
Spotlight
and
other
stuff
so
and
I
will
just
share
here.
My
idea
I
have
this
on
my
private
repo,
just
waiting
for
a
PR,
but
I
wanted
to
have
more
more
ideas.
It's
been
my
experience
since
writing
that
one
around
hack,
MD
and
Google
and
then
open
the
pr
that
there
are
essentially
two
different
audiences
here.
C
One
is
those
which
are
not
a
part
of
sick
docs
and
whose
work
is
actually
to
review
stuff,
and
that
and
and
for
those
hack,
MD
and
Google
Docs
is
seems
to
work.
So
the
camera
off
seems
to
work
fine
to
address
the
initial
set
of
ideas,
but
the
actual
people
from
sick
docs.
They
live
by
get
them
itself,
so
anything
that's
outside
it
actually
becomes
more
complex.
C
If
you,
if
we
need
their
immediate
support,
the
only
thing
that
I
that
I
would
change
to
the
process
is
that
I
think
that
it
would
be
useful
to
open
a
even
if
it's
a
placeholder
PR
or
something
like
that
immediately
when
we
have
the
confirmation
that
we're
working
on
on
something,
why
it's
been
my
experience
as
well,
that
without
APR
with
people
who
assigns
and
a
deadline,
the
thing
that
is
happening
with
my
spotlights
on
Sig
architecture
and
others
in
the
past
will
continue
to
happen
because
faced
with
this
list
of
things
that
actually
get
pinged
on
Gmail,
Gmail
and
slack,
and
it's
there
and
with
something
which
is
on
a
repository
somewhere
with
someone
just
pinging
them.
C
F
C
It
would
also
help
with
our
work
in
progress
perspective,
because
we
could,
if
we
think
about,
for
example,
adopting
GitHub
boards
project
boards.
We
could
just
have
this
on
the
on,
like
a
kanban
style
kind
of
thing
in
which
this
are
open,
but
are
on
Ice.
These
are
ongoing
and
this
one
are
are
published,
and
these
are
done
so
in
a
way
we
would
also
have
the
work
in
progress.
C
Visibility
of
what
was
is
in
flight
and
what
is
not
I
can
write
this
better
I
just
wanted
to
put
the
idea
out
there,
because
it's
it's
it's
based
on
my
more
more
recent
experience
as
consulate,
because
the
I
I
noticed
some
behaviors
that
I
think
it's
useful
to
to
adapt
to.
A
I
think
that's
a
good
point.
I
know
that
Rey.
When
he
was
attending
this
meeting,
he
was
saying
that
the
blog
sub
project
was
looking
to
change
their
process
to
incorporate
the
hack,
MD
Google,
Docs
style
of
reviews
at
the
beginning,
and
he
wanted
to
base
that
change
on
your
doc
that
you
had
put
together.
So
it
might
be
good
to
chat
with
him
about
it
as
well.
I
think
you're,
probably
right.
It
is
probably
a
good
idea.
We
did
used
to
do
this
and
then
those
those
issues
would
end
up
going
stale.
A
C
B
C
A
F
Update
to
just
really
slow.
A
Okay?
The
next
item
was
the
role
descriptions.
The
only
one
left
here
is
sub-project
lead,
which
we
need
to
do
in
our
meeting,
which
we'll
set
up
for
next
week.
In
addition
to
all
of
the
the
team
updates.
B
A
I'll
grab
it
and
put
it
in
the
in
the
chats.
I
A
B
A
I
I
A
And
Imran
I
think
that
should
be
you
since
you
are
Tech,
lead
and
also
kind
of
this,
like
sub-roll
of
kate's.dev
lead
for
us.
So
we
should
try
to
look
into
that.
Yeah.
I
C
By
the
way
you
need
to
lgtm
at
least
again,
because
since
I
pushed
another
one,
it
was
removed.
B
Let
me
open
now,
I'll
start
a
conversation.
Concervix.
A
A
I
I
A
There
was
the
deployment
preview
last
time,
so
this
is
just
still
in
preview.
State
they
haven't
pushed
it
is
that
the
current
states.
B
I
did
kick
the
tires
a
little
bit
on
the
code.
Spaces
and
I
mean
it
worked.
First
of
all,
which
is
great,
I
am
a
little
concerned
right,
like
they're,
free
tier
right.
Now,
it's
very
generous.
That
might
not
be
the
case
if
lots
of
folks
do
this
all
at
once
right
like
that,
they
could
probably
they
probably
have
a
free
tier
like
limit
for
the
entire
service.
So
that'd
be
interesting.
If
we
ever
hit
that
like
how
that
would
work
out,
because
you
need
the
largest
code
space
that
they
provide
so
yeah.
B
F
B
A
B
A
Cool
added
that
note,
update
to
contributor,
comms,
name
I,
don't
think
there's
anything
active
waiting
here,
so
I
think
I'm
going
to
remove
this
actually
from
the
table.
We've
said
a
couple
of
times:
if
you
see
something
say
something
and
that's
about
what
we're
at
here
sound
good,
I
think
so.
I'm
gonna
delete
that
route.
Yay
I
love
when
I
get
to
delete
a
row.
C
A
Nice
so
another
Spotlight
on
the
list,
I'm
guessing
from
what
you
were
saying
earlier:
Frederico
architecture.
C
We
we
shouldn't
take
it
off
just
because,
if
someone
asks
have
you
thought
about
doing
something
insecurity.
The
answer
should
be
yes
at
this
point
in
time,
and
this
is
where
the
the
persons
so
please
leave
it
there
for
the
time
being.
What
I
will
also
do
is
that
I
will
play
a
bit
with
the
idea
of
creating
a
project
board
and
I
will
add
some
of
this
there,
just
as
a
a
way
to
see
if
it
works
correctly,
which
can
be
great,
for
example,
if
people
want
to
necromance
some
something
into
into
life.
C
A
D
B
A
C
Yeah,
it
feels
that
I'm
I'm
well
I'm
I'm
well,
surrounded
by
notorious
people
when
I
start
to
recognize
them
from
the
outside
world,
because
I
I
used
to
I
I,
listened
to
that
quite
a
while
yeah
but
I.
Yesterday,
I
was
reading
the
what
went
wrong
and
I
gave
up
halfway
because
it's
tags
Milestones
logs
and
it's
it's
way
beyond
my
pay
grade.
But
it's
fascinating
stuff
to
see
the
complexity
of
of
cutting
a
release.
A
C
A
C
A
At
the
bottom
of
the
the
daily
template,
there's
articles
tracked
here,
so
that
is
one
that
we
used
to
use.
Is
this.
A
Track
our
articles
that
we
were
working
on
and
that
was
how
Matt
did
it
when
Matt
was
running
this
group,
then
once
he
moved
on
I
was
not
good
at
this.
Certainly,
so
we
moved
to
doing
it
all
within
the
dots.
So
if
you
wanted
to
spin
it
back
up,
I
think
Canal
at
one
point
tried
to
spin
it
back
up.
No.
C
A
B
C
C
C
A
H
I
A
H
I
think
I
can
add
it,
so
maybe
everyone
can
do.
I
Yeah
so
because
this
is
that
thing,
I
also
want
to
provide
update.
So
actually
the
the
updates
from
the
coaches
has
been
done
so
they're
very
kind.
So
they
gave
me
all
the
updates
which
I
needed
so
I
just
need
to
write
some
intro
and
I
started
doing
the
draft
version
of
it.
I
just
started
putting
the
hack
somebody
document,
so
hopefully
I
don't
know
if
it's
possible
position
to
share
or
early
next
year
somewhere
all
this
time.
So
it's
the
first
thing
I
think
it
will
go
probably.
A
A
I
On
that
yeah
I
did
something
but
I
didn't
I
didn't
touch
this
piece
for
a
long
time,
so
I
need
to
yeah
check
this
one
yeah.
Okay,
there
are
so
many
things
going
on
this
one.
You
need
to
fix
the
version
and
so
on
so
far,
I
didn't
touch
it
because
otherwise
had
some
updates,
while
fixing
them
got
broken
but
yeah.
So
we
need
to
I
need
to
look
at
it
again.
Actually.
G
I
So
we
have
also
a
item
to
track.
You
know
the
to
schedule
tweets
automatically
to
the
buffer.
Maybe
we
should,
if
you
could
find
the
prioritize
that
feature,
then
maybe
you
don't
need
this
yeah,
all
this
extra,
tooling
and
Automation
and
coding
and
stuff
foreign.
I
Yes,
yeah
exactly
this
is
the
one
yeah
yeah
exactly
so
yeah
I
mean
these
things
yeah.
So
this
big
since
buffer
is
the
key
beautiful
part.
So
somehow
GitHub
should
stick
to
the
buffer.
Then
it's
I.
G
I
I
F
I
F
I
H
H
It
was
back
way
back,
and
so,
as
soon
as
there
is
a
Blog
goes
out,
you
get
you
get
a
email
done
on
the
one
of
the
accounts
before
having
those
discussions,
but
I
I
think
the
RSS
one
was
a
bit
more
complex
because
I've
worked
with
the
RSS
Gita
viruses
and
yeah.
It's
a
bit
complex.
A
Project
worth
looking
into,
but
it
sounds
like
it
might
be,
a
little
tricky,
but
we
have
directions
to
check
out.
So
that's
good
yeah.
F
A
I
keep
pinging
on
this
blog.
That
devil
was
helping
out
with
that
didn't
move,
I
I,
don't
think
it's
going
anywhere.
A
I
guess
it
can't
hurt,
be
like
hey
you
had
this
blog
around.
Did
you
still
want
to
try
to
push
it
through.
A
A
Today
is
a
day
for
that:
let's
move
on
and
keep
track
of,
Sig
Doc's
blog
sub
project
process
changes
like
mentioned
Ray
was
interested
in
basing
the
blog
sub
projects
new
processes
off
of
what
you
wrote,
fredericoso
definitely
check
in
with
him.
You
needed
to
do
that
anyway.
F
A
Let
us
know
what
you
find
out.
Maybe
we
can
remove
that
one
from
the
table.
Maybe
they've
done
it
probably
yeah.
A
Possibly
next
item
this
one,
maybe
someday
we'll
do
that.
Let's
look
at
it
early
next
year.
A
The
idea
of
creating
a
separate
guide
for
security
comms,
some
high-level
pointers
on
how
we
should
organize
those
requires
working
with
the
security
co-chairs
to
sort
out
what
those
need
to
be,
and
it's
going
to
be
a
significant
amount
of
work.
So,
let's
not
start
it
at
the
end
of
the
year
and
we've
had
other
stuff
going
on
all
year,
so
maybe
next
year,
when
I
tried
to
do
it
in
the
past,
there
was
also
stuff
that
got
in
the
way.
So
maybe
someday
scheduling,
tweets
for
non-contributor
comms
members.
We
talked
about
that.
A
You
can
look
into
it.
Let's
see
what
the
challenges
are.
At
least
mophie's
exploration
into
directly
connecting
to
buffer
didn't
seem
to
work
out.
A
I
think
you
might
have
actually
mentioned
something
about
zapier
instead
and
then
kind
of
dropped
that
thread.
So
if
you
wanted
someone
to
work
on
that
with
Mophie
would
be
interested
in
helping
I'm
sure
next
item
Chris,
you
had
your
notes
about
admin.
B
A
A
Regardless
of
the
new
Drive,
which
I
have
a
link
for
higher
up
in
the
table,
I'm
not
going
to
grab
that
right
now
because
we're
already
at
time-
and
then
these
other
two
are
just
the
things
that
we
already
talked
about.
Actually
so
good
I
think
we
can
finish
up
any
other
last
minute
items.
We
are
at
time.
A
Sounds
good
I'll
put
a
meeting
on
your
calendar
Chris
for
us
to
go
over
the
team
updates
owners
updates
and
subproject
Lead
definition
thanks
everyone
for
joining
today.
We
really
appreciate
you
spending
time
with
us
and
we'll
see
you
next
week
for
our
last
currently
planned
meeting
of
the
year.
If
you
need
any
help,
you
know
where
to
find
us.