►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20230120
Description
[SIG ContribEx] Weekly Marketing Meeting for 20230120
A
Hello,
all
Welcome
to
the
January
20th
2023
contributor,
comms,
meeting,
I'm,
Chris
short
co-lead
of
contributor,
comms
and
I'll
be
leading
today's
meeting
at
caslin
is
out
due
to
work
things.
I'll
just
leave
it
at
that.
A
Any
updates
and
big
wins
to
start
things
off.
Well
wait
a
minute.
First,
we
abide
by
the
code,
the
cncf
code
of
conduct,
please
don't
say
anything
you're
going
to
regret
later.
I'll
find
your
mother
and
tell
her
about
it.
Trust
me
I've
done
it
before
the.
A
B
Sure,
yeah
I
haven't
been
able
to
come
back
since
the
beginning
of
well,
since
the
end
of
working
on
Detroit
but
I'm
Roger,
Corey,
so
I'm
glad
to
be
back
and
who
knows,
we
could
have
a
miracle
and
they'll.
Let
me
go
this
time.
A
Who
knows?
Welcome
back
all
right,
updating
big
wins,
fermentation,
spotlight.
C
Yeah,
so
actually
yeah.
So
there
was
a
spotlight
which
was
going
on
sometime
before
the
release,
126
so
yeah.
So
now
it's
basically
I
got
everything
needed,
so
I
created
a
markdown
and
a
PR
for
it
for
the
boat
plus
I
started
with
the
dev,
probably
to
have
to
for
the
kx.isl.
So
yeah
feel
free
to
give
your
comments
and
it'd
be
nice
to.
D
A
Well
never
mind.
I
won't.
Add
that
to
my
to-do
list
right
now,
cool
great
work,
I'll
take
a
look.
Catherine
will
take
a
look
where
I'll
take
a
look.
Anybody.
A
To
look
at
it
feel
free
now
that
I've
lost
the
notes,
let's
find
them
again
anything
else
for
updates
on
big
wins.
I
know
it's
early
in
the
year:
I'm
not
expecting
like
a
ton
of
stuff,
all
right,
cool,
good
work
on
that
Imran
new
items.
I,
don't
think
this.
D
A
Back
in
the
swing
of
things,
Twitter
together
is
the
jobs
right
now
are
being
skipped
for
some
reason.
Don't
know
why
exactly
I'm
I
think
atarva
you've
got
some
more
info
here.
G
Yeah,
so
jobs
aren't
exactly
skipping,
they
are
just
waiting
for
slash,
validate
command
to
go.
So
after
you
slash
validate
a
issue.
Then
it
starts
the
job
again.
It.
C
Maybe
yeah
yeah
I,
don't
think
so,
so
what
I
I
actually
looked
up
before
until
the
meeting,
so
the
let's
say
the
possibility
or
the
certainty
of
the
validation
command
is
still
not
correct.
After
fixing
the
GitHub
actions,
you
fix
the
validate
expression,
but
it's
still
like
it
increased
the
yeah,
I
I
can't
say:
let's
say
it
didn't
improve,
so
that's
yeah,
so
it's
similar
to
the
previous
time
previous
time
as
well
for
I,
don't
know
for
what
reason
the
validate
didn't
work
and
with
this
fix-itab
action.
Also
it
didn't
help
either.
C
So
now
the
question
is
so
I
expect.
We
need
to
look
I
mean
that's
my
understanding.
We
need
to
look
into
the
the
node.js
into
the
script,
which
has
this
yeah
the
script
which
takes
the
input
and
then
process
it
and
so
on,
and
then
probably
we
need
to
I,
don't
know
remote
debugging
or
we
need
to
debug
and
see
what's
actually
exactly
happening
so
that
that's
the
right
fix
to
see
that
how
to
how
could
we
we
could
fix
the
validate
command.
C
H
C
A
D
C
B
E
A
Will
but
what's
happening.
E
I
Yeah,
so
the
question
I
have
is
you
said
in
the
in
the
issue.
You
have
said
that
jobs
are
skipping
right.
I
A
A
The
the
validate
command
is
not
happening,
so
the
job
doesn't
run
right.
So
we
have
to
run
validate.
A
I
My
understanding
to
this
thing
is
be
in
fact
me
and
there's
a
new
Folks
at
that
we
tried
to
you,
know
debug
a
little
bit
more
with
the
entire
project
and
we
we
kind
of
found
that
is
it
really
broke
cause
the
jobs
are
running,
the
pris
are
being
created,
I,
don't
know
if
the
validate
thing
has
been
happening,
but
that
when
you
create
an
issue
right,
the
PRS
are
being
created,
so
I'm
still
confused
for.
I
G
The
idea
is
the
issue:
I
have
the
pr
I
have
just
linked
down
in
the
comments
is
we
have
to
just
revert
it
to
the
previous
changes
and
it
will
just
work
smoothly,
but
the
thing
is,
the
validate
command
will
still
not
work
right.
H
G
So
if
you
want
to
go
back
to
automatically
create
the
pr,
then
we
have
to
just
revert
this
change.
The
one
I
posted
in
the
chat.
G
Yeah,
that's
why?
So,
if
you
are
just,
we
have
to
fix
the
validate
command
and
not
the
process
of
the
validate,
not
the
process
of
just
after
an
issue
is
created.
We
have
to
manually
write,
slash
validate,
we
don't
have
to
fix
that.
We
have
to
fix
how
we
validate
command
should
work.
A
C
Yeah,
that
was
the
early
assumption.
I
had
so
maybe
it's
just
a
regular
expression,
but
exactly
so
the
GitHub
expression
try
to
increase
the
certainty,
but
something
goes
inside
the
script
which
really
need
to
be
debugged
in
the
validate
I,
think
it's
happening
in
this
index
JS
and
it's
about
a
node.jscript
and
yeah.
So
this
is
what
the
actual
problem
I
I,
also
feel
that
that's
the
problem
advice
in
the
script
rather
than
other
actions
and
some
other
part
so
yeah.
G
So
while
we
are
on
this
topic,
I
I
just
wanted
to
share
this
template
of
this
app
I
just
created,
but
for
some
reasons,
happier
doesn't
support
the
path
thing.
If
you
have
a
path
thing
to
your
exam,
you
don't
you
can't
share
it
locally
to
everyone,
so
I
had
these
have
created
for
it.
So
if
I
at
the
end,
if
you
have
time,
I
can
just
share
the
screen
and
just
show
you
how
the
workflow
is
work.
A
G
E
D
G
So
the
basic
idea
of
zapier
for
this
app
is
just
look
through
the
repo
and
find
the
newest
find
the
new
age
find
only
the
new
issues
and
for
every
new
issue
only
continue
if
the
title
contains
the
title
starts
with
to
it
all
right.
So
the
title
exactly
starts
with
wait
word
and
if
the
in
that
issue
in
that
weight
issue,
if
the
label,
if
there
is
a
label
named
approved,
we
can
change
it
to.
However,
we
want,
if
the
label
con
has
the.
C
C
G
Can
do
a
lot
of
stuff
in
here
all
right,
so
I've
created
this
and
there
are
three
parts.
So
first
is
we
have
the
approve
and
we
want
to
schedule
it.
So
we
can
create
a
Zap
for
that
if
the,
if
there's
an
approved
label,
but
it
it
is
not
scheduled,
then
we
have
another
thing
for
it
and
if
it
is
not
approved,
we
can
just
reply
with
a
dummy
text.
Saying
hello
thanks
for
opening
it
with
PR
and
assign
someone
from
the
owner's
file.
G
We
can
do
this,
and
this
is
just
for
the
approved
thing.
I
have
not
yet
looked
into
the
character
to
its
size
thing
I.
D
A
E
A
You
hit
just
hit
the
plus
sign
right
below
this
action.
I
want
to
see
this
okay,
no,
the
below
the
close
that
plus
sign
and
then
there's
like
a
transformation
step
that
you
can
add
a
filter,
yeah
or
format.
No
change
go,
go
back
and.
F
H
J
A
G
A
A
G
A
G
A
C
C
I
I
can
I
have
some
I've
seen
the
source
code,
maybe
for
older
automation,
so
I
can
explain
all
the
use
cases
valid,
timestamp
length
and
so
on.
I've
seen
it,
but
I
haven't
debugged
the
code,
so
maybe
you
can
get
all
the
cases
what
need
to
be
done
or
implemented
in
the
zapier.
So
we
can
have
a
look
and
then
maybe
we
do
it
in
exactly
so.
That's
I
see
it's
it's.
Maybe
it's
possible.
A
G
A
C
Or
maybe
I
can
also
create
an
issue
explaining
what
are
the
use
cases
we
currently
have.
Then
we
can
yeah.
We
can
eventually
work
it
out
on
that
day,
so
that
yeah.
So
what
are
the
use
case?
We
currently
have
with
this
automation,
node
script
and
then
what
possibly
could
be
implemented
by
the
zapier
attention.
So
that
way,
it's
also
easier.
C
I
Also
I
just
wanted
to
know
us,
so
validation
isn't
that
shouldn't
that
be
a
part
of
buffer
itself,
I.
A
A
G
D
G
A
G
E
F
C
D
C
A
E
A
A
A
Yeah
yeah,
it's
a
lot
like
he's,
got
a
lot
of
test
cases
that
are
all
GitHub
based
too.
It
seems
like
so
yeah.
It's
interesting.
E
A
Oh
yeah,
the
Twitter
or
not
Twitter
slackbot,
like
adding
us
GitHub.
H
I
I
I
actually
did
some
progress
on
this,
so
I
I
did
explore
the
entire
thing,
because
I
was
not
aware
with
what
all
things
are
we
have
been
doing
here
now.
The
thing
is
we,
we
tried,
we
we
build
a
team
on
GitHub
and
the
idea
was
to
you
know,
create
a
template
and
tag
there.
Wasn't
there
is
an
issue
template
created
and
we
we
wanted
to
tag
contributor
comms
in
it,
but
I'm
really
not
sure.
If,
if
tagging
contributor,
com's
team
will
work,
I
tried
for
my
personal
accounts.
I
I
am
not
sure
if,
if
that
is
something
that
will
work,
so
the
idea
is
you
you?
Basically
you
you,
you
create
a
custom
template
where
you
tag
the
team
itself,
which
is
not
working
for
me.
I,
don't
know
if,
if
that
could
be
a
thing,
I
would.
A
I
A
G
G
G
A
G
D
G
And
we
can
subscribe
or
unsubscribe
to
those
events
also.
So,
if
you
want
to
yeah,
cncf
has
been
pretty
good
in,
you
can
see
in
the
mentoring,
Channel
or
cncf
mentoring
or
some
general
Channel,
and
you
can
see
those
GitHub
Bots
yeah
messages.
I
Answer
to
yeah
go.
A
I
I
was
I
was
actually
having
another
question
related
to
this.
Do
we
really
want
this
thing,
or
just
we
are
adding
just.
I
G
A
Well,
that's
the
thing
right
like
I,
think
personally,
because
I
look
at
this
every
morning
at
9am
on
a
religious
basis.
That's
why
we
don't
need
this
I
stopped.
Looking
at
this
at
9am
in
the
morning
every
day,
I
think
we
would
need
this
see,
that's
it's
kind
of
like
yeah.
If
the
leads
don't
check,
it'd
be
nice
to
have
you
know
something
that
says:
hey
new
issue
right
like
if
somebody
puts
an
issue
over
the
weekend,
I'm
not
going
to
catch
it
till
Monday
right.
A
I
Yeah,
it
does
I
I
think
we
can.
We
can
instead
of
you
know,
I
mean
we
can
just
start
for
a
little
for
a
group
and
then
just
gradually
make
it
big
and
and
the
entire
kubernetes
Community
could
use
it,
because
for
now
what
I
have
heard
from
Bob
is
we.
They
usually
trash
things,
the
reviewers
trash
things,
but
we
could
create
a
notification
thing
that
you
know
tags
the
particular
Sig
if
they
want.
A
Keep
in
mind
like
every
system,
we
we
being
the
kubernetes
community,
touches
like
every
service.
We
pretty
much
stretch
it
to
the
Limit
right,
like
netlify,
has
a
separate
setup
for
our
website
same
with
slack
same
with
GitHub
right
like
it's
there's
a
lot
of
scaling
that
we
do.
That
causes
a
lot
of
churn.
So
it's
good
to
think
about
that.
Thank
you.
A
D
A
F
A
F
Do
need
to
set
up
that
doc
if
anyone
is
interested
in
How,
We,
Do,
Cube
gun
tweets,
we
might
want
to
like
set
up
a
meeting
together
and
just
kind
of
go.
A
So
like,
and
we
don't
know
exactly,
are
we
having
sick
meetings
yet
or
not,
and
that
kind
of
thing
so
it
might
be
that
a
lot
of
these
just
don't
end
up
being
needed.
Who
knows
we'll
see,
but
the
the
folks
on
the
my
Shadows
for
comms
for
the
contributor
Summit,
like
I,
think
only
one
or
two
of
them
have
like
social
media
presences,
so
yeah.
B
B
A
E
A
I
feel
like
yes,
we
did
that
so
I'm
going
to
remove
this.
How
about
that
done
gone.
A
A
C
That's
that's
not
the
real
issue,
so
it's
just
our
permission
is
the
real
part.
So
I
haven't
had
time
last
week
to
check
on
this,
but
now
it
seems
things
are
getting
started
with
that
great
content
runs
I'll,
have
a
look
upcoming
I
mean
next
week.
I
can
have
a
look
at
it.
I
have
all
the
permissions,
and
so
on.
I
need
to
find
the
automated
way
to
add
the
bar
to
all
the
channels.
So
that's
the
actual
issue.
Maybe
you
can
rewrite
the
issue
that
I
know
when.
A
We're
gonna
be
yeah
yeah
like
editing.
The
contributor
comms
group
happens
in
the
user
groups.yaml
file
for
Slack,
so
like
putting
this
in
all
the
channels.
You
just
do
that
here,
like
everything
has
a
thing
you
put
it
there
done,
but
like
our
member
list
probably
needs
to
be
updated,
those
kinds
of
things
right,
because
pinging.
A
Parish
about
it
well
helpful,
she's,
probably
getting
overloaded
by
things
already
right
same
with
Jason
right
so
yeah.
We
can
clean
that
up.
Add
it
through
more
channels,
I
think
it's
one
of
those
things
where
it's
like
it
makes
sense
to
add
it
to
not
necessarily
every
Sig
Channel,
but
the
channels
that
we
hear
from
the
most
so
like
contrivex,
Docs
releases.
Those
kinds
of
things
does
that
make
sense.
C
C
It's
the
ideas,
so
I
think
I
mean
the
idea.
What
is.
C
Okay,
yeah,
that's
not
yeah
a
postcard
announcement,
exactly
so
I
mean
now
it
actually.
We
have
the
bot,
we
have
the
code
and
we
have
the
bot,
but
it
doesn't
it's.
It
have
to
be
manually
added
in
all
the
sick
channels.
So
that's
I,
don't
know
how
many
of
them,
but
so
what
this
part
yeah
it's
a
lot.
So
this
part,
so
the
issue
is
actually
not
the
broken
slack
part
or
something
so
that
we
need
to
yeah.
C
D
I
Out,
oh
well,
yeah
I
just
wanted
to
add
a
thing
earlier.
So
I
came
down
I
just
remembered
by
listening,
seeing
this
word
rule
so
for
a
cubecon
contributor
submit.
Please
let
me
know
what
what
my
roles
or
what
my
I
should
help
you
folks
in
in
case
of
promoting
the
event
or
something
like
that,
not
as
a
shadow,
but
you
can,
you
know,
add.
A
D
C
A
C
J
I
did
not,
which
one
is
this
one.
J
Oh
process
changes,
yeah,
so
I
know
we
did.
Process
changes
were
published
on
the
cube
on
the
on
the
contributor
site,
but
I
think
we
should
probably
do
the
same
or
something
somewhere
on
that.
A
C
D
A
Right
gold
stars
for
achievements
like
the
leading
your
first
table
row
we'll
work
on
that.
D
Let
me
fix
this
formatting
real,
quick.
A
A
A
C
C
A
G
So
it
is
14
days
exclusive
features
and
after
that.
C
I
I
think
we
can
try
this
thing
because
I
remember
when
we
were
doing
YouTube
Zoom
thing
I
believe
it
was
with
JPI
itself,
so
Nigeria
did
get
access
to
it
and
we
tested
all
things
there
itself
if
I'm
not
wrong.
D
A
G
G
A
I,
don't
really
say
how
to
actually
engage
to
get
an
account.
That's
weird.
B
I
A
So
yeah
we
talked
about
this
in
the
signature
of
X
median
this
week.
Engagement
in
the
community
meeting
is
just
awful
right,
like
it's
almost
to
the
point
where
it
doesn't
make
sense
to
have
it
anymore,
so
I
mean
keep
in
mind.
I,
remember
when
hundreds
of
people
would
show
up
and
zoom
and
we
would
crash
it
and
that's
how
that's
how
I
got
into
live
streaming,
because
I
needed
to
live
stream,
the
community
meetings.
So
it's
an
interesting
Evolution
as
we've
gone,
you
know
different
formats,
different
styles,
different
everything
is
just.
I
A
A
I
A
There
are
a
lot
of
contributors
on
the
fringes
who
don't
or
don't
know
to
attend
the
new
meetings
yeah.
When
you
go
and
look
at
a
calendar
for
CNC
effort,
kubernetes,
it's
pretty
ridiculous.
Isn't
it.
A
We
need
to
put
this
in
the
developer
guide
and
highlight
it.
Maybe
I
don't
know
because
usually
people
started
like
this
is
how
it
worked
back
in
the
day
when
I
started,
contributing
people
would
go
to
the
community
meeting
and
say:
oh
that's,
fun,
I'm
gonna
go
work
on
that
and
that's
how
they
discovered
cigs,
and
you
know
things
they
could
do
and
so
forth.
So
on,
but
like
their
first
experience
was
often
the
community
meeting
so
yeah,
that's
that's
just
gone
to
the
Wayside
right,
like
people
don't
even
know
to
go
to
the.
A
B
B
A
So
yeah
I
know
Laura
reaches
out
every
week
to
folks
to
say
Hey,
you
know
give
me
your
Sig
updates
and
the
Sig
leaves
have
just
not
been
responsive
this.
This
goes
in
line
with
the
the
overall
kind
of
slow
down
in
contributions
as
a
cause
of
the
pandemic.
Right
like
it's
in
that
same
vein,
Community
engagement
is
down
because
of
stuff
from
the
pandemic
right
yeah,
it
kind
of
falls
in
the
same
categories
and
don't
get
me
wrong.
D
C
A
D
J
E
A
Sig
is
just
difficult:
some
cigs
are
better
represented.
H
A
So
you
know
we
did
discuss
in
the
meeting
right
like
having
a
release
community
meeting,
potentially
right,
where
it's
it's
based
on
sharing
new
features
or
something
like
dockersham,
for
example,
right
like
we
could
talk
in
depth
about
that
and
answer
questions.
Real
time.
Kind
of
thing
like
I
would
rather
see
that
three
times
a
year
as.
J
J
A
No
so
I
brought
up
the
example
that
I
did
at
Red
Hat
when
we
started
live
streaming
and
I
realized
that
we
were
doing
a
lot
of
similar
activities
for
our
internal
teams,
where
we
were
taking
our
collaboration
tools,
and
you
know
trying
to
put
it
out
in
front
of
hundreds
of
people
in
sales
and
solutions
Architects
and
things
like
that.
I
said:
why
don't
we
just
flip
the
script?
We're
an
open
company.
We
can
talk
about
new
releases
in
the
open
and
it
got
to
the
point
where
it's
like
all
right.
A
One
person
would
run
slides.
Another
person
would
run
like
Logistics
on
the
call
and
then
somebody
else
would
be
live
streaming
it
and
that's
pretty
much
how
it
worked,
and
we
could
do
that.
I
feel
like
once
a
release,
and
it
could
be
that
one
of
us
volunteered
to
do
the
whole
thing.
You
know
it's
entirely
possible
that
six
could
submit
updates
and
we
could
run
it
like
that's
a
thing
like
we
being
sick
and
tripex,
not
Australia,
contributor
comps,
but
you
know
we
can
definitely
have
an
active
role
in
it.