►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20230127
Description
[SIG ContribEx] Weekly Marketing Meeting for 20230127
A
A
So
usually
I
try
to
remember
and
usually
fail
to
remember,
to
offer
an
opportunity
at
the
beginning
of
the
meeting
for
anyone
who's
new
to
our
group
to
say
hello
and
tell
us
a
little
bit
about
why
you're
here.
So,
if
there's
anyone
new
on
today,
who
would
like
to
say
hello,
feel
free
to
unmute
or
to
Ping
in
the
chat
totally
optional,
though,
if
you
don't
feel
comfortable
introducing
yourself,
that's
okay,
too,.
A
A
A
What
is
it
called
contributor
tweets
repo,
so
we
had
decided
to
add
Kim
in
as
someone
who
could
approve
and
get
pinged
to
review
PR's
in
that
repo
generally,
if
you
are
interested
in
being
someone
who
is
asked
for
your
review
when
a
new
tweet
comes
in,
you
might
want
to
be
part
of
the
contributor
tweets
owners
file.
A
So
since
we
had
wanted
to
add
Kim
to
that,
Kim
needs
org.
Membership
and
McMahon
needs
org
membership.
In
order
for
that
to
go
through
because
apparently
it
will
put
a
hold
on
the
pr,
because
it
considers
the
owner's
file
to
be
invalid
without
Kim
being
part
of
the
the
org.
So
I
sent
Kim
a
message
about
that
I
don't
think
she's
on,
but
that
is
one
thing
that
is
holding
that
PR
back,
although
it
does
exist
now.
A
Any
questions
about
that
yeah
I
also
was
chatting
with
atarva
this
morning.
Oh,
you
can
be
a
sponsor.
Thank
you.
Ray.
Likewise
happy
just
sponsored
Kim.
Oh.
B
C
D
A
Else
I
think
I,
don't
know,
but
I
pinged
her
the
the
link
to
the
members
or
remember
info
page
but
yeah,
maybe
maybe
that'll,
take
a
bit
I,
don't
know
if
we
should
adjust
that
PR
in
the
meantime
and
just
add
her
in
once.
She
gets
that
maybe
yeah.
C
A
A
And
the
other
item
that
I
wanted
to
talk
about
was
this
morning.
I
was
chatting
with
atarva
atarva
wanted
to
take
on
some
responsibility
with
regard
to
reviews
and
approving
things
as
well.
So
I
wanted
to
discuss
a
little
bit
what
you
would
like
to
help
out
with
atarva,
so
basically
what
we
have
for
owner's
files.
This
is
a
good
review
for
everyone,
which
is
another
good
reason
that
we're
bringing
this
up,
because
I
wanted
to
make
sure
that
we
got
these
right
and
everyone
knew
what
they
were
getting
signed
up
for.
A
A
A
It
kind
of
not
really
I
feel,
like
that's
the
usual
case
when
it's
broken
anyway,
so
but
the
options
for
the
owner's
file
that
we
have
here
are
basically
reviewers
or
approvers.
So
if
you're
in
the
reviewers
block,
that
means
that
you're
going
to
get
pinged
when
a
new
PR
is
added
to
this
repo
at
random.
It
won't
be
everyone
all
the
time,
but
folks
from
this
list
will
be
pinged
to
review
it
when
a
PR
comes
in,
which
is
separate
from
approvers.
A
Approvers
are
folks
who
have
permission
to
approve
PRS
in
this
repo.
So
there
is
a
difference
in
this
repo
for
that,
because
Imran,
as
our
Tech
lead,
needs
permission
to
this
repo
hello
cat
needs
permission
to
this
repo
to
be
able
to
fix
the
the
automation
when
it's
broken
and
add
new
things
to
it
and
generally
mess
around
with
that
part.
This
is
kind
of
a
no-brainer
yeah
yeah.
A
A
Oh
yeah
yeah,
so
we
can
talk
about
that
a
little
bit
later
yeah.
You
know
it
is
like
not
here
so
I
guess,
I'll
just
go
find
it.
A
Perfect,
so
this
is
the
other
owner's
file
that
we
have,
that
we
are
updating
that
is
updated.
So
again
it
has
the
reviewers
and
an
approvers
section.
These
are
both
the
same
in
this
case,
so
this
is
for
any
updates
to
our
contributor
comms
team
repo,
where
we
have
things
like
our
roll
handbooks,
storytelling
resources,
our
Charter,
all
of
that
basic
description
of
our
team
kind
of
stuff,
so
atarba.
What
kind
of
responsibility
would
you
like
to
have
within
the
team.
C
F
At
this
point,
I'm
just
pretty
pretty
much
generalizing
things
so
I
think
I've
been
around
in
this
contributed
comes
for
a
while,
so
I
think
it
this.
Who
knows
this
under
Community
ownership,
I
think
I
can
be
a
part
of
it,
but
I
don't
know
exactly
that.
Twitter
together
would
be
my
kind
of
thing,
because
that's
fine.
F
C
G
It
was
a
little
bit
outside
to
grab
a
cup
of
tea,
so
what
was.
G
C
C
I
can
give
one,
let
me
just
get
one,
so
the
tarver's
done
a
lot
of
work
for
the
group
and
has
been
here
a
long
time
would.
C
B
B
G
A
C
Are
many
ones
part
of
the
problem?
Oh,
there's
tons
of
owners
file
and,
and
essentially
like
the
way
the
owner's
file
model
works,
just
attack
a
piece
real,
quick
right
like
it's
an
inherited
model.
So
if
there's
no
owners
file
in
a
directory,
it
will
inherit
the
up,
go
up
a
directory
levels
owner's
file.
Otherwise,
if
there
is
an
owner's
file
in
there,
it
will
say
only
these
people
need
to
be
able
to
do
things
in
this
part
of
the
repo
kind
of
deal
so
contributor.
A
C
D
C
Like
it's
weird
I'll,
just
leave
it
at
that.
It's
like
we
have
to
have
the
lines
drawn
in
certain
places
for
certain
reasons
and
owner's
files
do
that
for
us
essentially.
A
F
F
D
A
All
right
sounds
good.
We
can
get
to
that
in
the
table
or
we
can
discuss.
C
F
C
F
F
C
F
Repeatedly
Chris
I'll
bring
you
about
it,
I
think.
Let's
go
with
yeah,
anything
that
seems
fine,
I
am
I,
don't
have
an
opinion
for
it
right.
A
C
A
C
Chris,
can
you
go
like
immediately
need
help
kind
of
thing
calendar
admins.
A
C
So
calendaring
Administration
is
a
thing
so
yeah
we.
A
D
C
The
larger
contributor
comms
team
I
need
to
CL
there's
so
many
issues
open
on
Twitter
together
right
now,
I
just
want
to
consolidate
them
all
right
like
go
see
this
one
goes,
you
know
like
at
the
bottom
of
each
one
just
be
like
go
see
this
one.
This
is
the
one
we're
actually
working
now.
A
A
C
So
yeah
like
it's
a
lot
of
sprawl
right
now,
because
I
feel,
like
everyone's
pointed
out,
something
different,
that's
broken
and
we
might
have
some
repeats
too.
So
yeah
I'll
go
through
that
and
clean
it
up.
But
then,
last
week
after
the
meeting
I
asked
cncf
hey:
how
do
we
do
the
whole
zapier
thing
and
they're
like
hey?
All
you
need
to
do
is
get
a
issue
open
and
K
funding
and
approved
and
we'll
create
an
account
for
you
and
hand
off
credentials.
F
I
mean:
is
it
only
limited
to
that
only
one
zap
or
is
it
for
the
whole
account
of
zapier?
It's.
F
C
Like
I
actually
have
a
weird
zapier
account
because
they
like
my
newsletter
when
I
set
it
up,
and
that
just
gave
me
like
the
access,
that's
pretty
cool,
so
I
have
like
five
zaps
and
50
000
executions
of
those
zaps
that
I
can
do
and
they're
like
you
can
do.
Multi-Steps,
where
it's
like
you
know,
hey
I,
need
to
actually
transform
this
and
then
put.
F
So
while
we
are
in
zapier,
then
I'll
just
go
ahead
and
tell
you
about
the
update.
So
we
had
a
location
how
to
validate
the
length
of
the
character
length
of
the
retweight.
So
as
Grace
told
us
previously,
the
there's
a
field
in
zapier
when
you,
where
you
can
just
apply
the
Restriction
of
getting
the
length
of
the
tweet
and
then
I
can
I
created
a
path
where
only
continue
when
the
length
is
between
that
tweet
character
limit.
So
for
now
it
is
totally
working
right.
C
F
We
for
every
age
case
we
occurs
like
the
Tweet
character
length
or
any
new
case
we
work
on
we
find
across.
Then
we
can
just
mention
that
in
the
issue
I
have
created.
Let
me
get
that
for
yeah.
G
C
G
G
F
F
G
Team
I
mean
there
are
some
things
we
need
to
ask
the
team,
because
the
current
workflow
which
we
used,
which
was
I,
was
looking
at
it
like
we
have
an
issue,
then
we
create
a
VR.
Then
it
goes
to
it.
We
have
two
workflows
like
issued
to
PRT
tweets
and
there
is
a
PR
to
tweets.
So
these
are
the
two
things
covered
within
the
GitHub
action.
So
we
need
to
look
at
it
and
yeah
take
the
ones
which
is,
let's
say
feasible
to
the
current
use
case.
G
C
The
mechanics
of
it
all
yeah,
that's
a
good
point,
because
now
it's
you
open
an
issue
and
it
auto
creates
a
PR
for
you
based
off
that
issue.
Yeah.
B
G
C
C
F
So
the
top
I've
been
working
for
just
works
like
this.
You
create
an
issue.
It
validates
the
Twitter
length
of
the
character
length
if
it's
work,
it's
within
the
character
limit,
it
just
schedules
or
add
it
to
buffer,
and
that's
it
no
need
to
create
another
PR
or
anything
like
that.
But
the
point
here
is
the
Tweet
will
go
out
and
it
will
be
posted,
but
it
won't
be
stored
in
any
folder
like
that.
So
do
we
want
to
store
every
tweet
that
goes
out
yeah.
G
F
How
do
I
find
this?
There
are
labels
in
the
kubernetes
repository
right.
So
are
there
labels
that
cannot
be
applied
that
are
available
in
issue
level
that
are
available
as
issue
level
labels
that
cannot
be
applied
in
PRS.
F
C
F
B
D
C
They
actually
I
know
where
yeah
it's
labels.yaml
I
just
forget
where
it
is
and
I
bookmarked
it
for
a
reason:
prowl
labels.
There
we
go
so.
F
What
I
was
thinking
was
if
there
is
no
label
for
approvally
for
issues
we
can.
We
can
ask
the
testing
people
to
give
us
a
new
level
for
issues
for
tweet
approval
and
one.
F
G
F
Yeah
I.
C
But
for
issues
so
I've
dropped
a
link
in
chat
for
the
labels.md
file
and
it
literally
tells
you
what
labels
can
be
used
where
and.
C
Does
not
look
like
it
can
be
used
in
issues,
so
we
would
probably
need
to
go
the
pr
route.
F
D
B
D
D
D
C
B
C
Pr's
that
already
have
the
prow
plug-in
set
up
for
approved
and
everything
else
I
think
that's
probably
the
right
way
to
go
and
we
can
hold.
We
can
do
whatever
it
is.
We
need
to
do
with
those
particular
things
we
just
need
to
pull.
We
need
to
clean
up
the
issue
so
that
the
issue
text
is
only
the
tweet
and
then
that
PR
gets
created.
Well,
I,
don't
know
if
we
have
to
do
that,
but
the
pr
gets
created
with
the
Tweet.
C
F
Or
what
we
can
do
is
instead
of
creating
issue.
Let
we
tell
all
the
people
that
create
a
PR
for
to
it,
so
yeah.
G
So
we
can
also
enable
that
so
it's
also
possible,
so
it
is
also
possible,
but
we
don't
use
it
because
we
have
a
diff.
We
have
been
using
the
workflow
of
issue
to
PR
to
pit,
but
prte
is
also
possible
with
let's
say:
okay
get
a
passion.
So
if
that's
also
yeah
I've
actually
commented
out
those
two
lines
in
the
issue:
the
289
yeah
for
discussion.
But
it's
good
that
we
are
already
speaking.
So
we
can
also
I'm
also
in
favor
of
PR
to
tweet,
rather
than
creating
issue.
C
A
Made
a
good
point
in
chat
that
we
also
need
to
consider
how
tweet
writer
would
edit
their
tweet
yes
I
need
to
or
if
we
would
leave
that
to
the
reviewer.
F
C
C
C
G
F
H
C
B
C
C
A
C
B
A
C
Yeah
it
like
having
a
bunch
of
stuff,
we
need
to
go
approve
after
it's
already
been
approved,
isn't
a
good
use
of
our
time
right
like
if
it's
approved
in
GitHub,
we
shouldn't
have
to
also
go
approve
it
in
buffer,
like
buffer,
won't
tweet
it
out.
If
it's
too
long
right,
like
yeah,
that
kind
of
thing
it'll
catch
that
and
be
like.
No
I
can't
do
this.
C
C
Might
because
it
is
like
a
little
Nu
launched
using
zap.
A
Our
Slack
fedrico,
since
you
mentioned
that
you
had
updates
on
Reviving
the
tracking
board.
Let's
go
ahead
and
discuss
that
here,
yeah.
E
Actually
I
didn't
make
use
of
the
previous
one,
because
I
think
that's
a
there
was
an
update
in
terms
of
the
boards
and
I
think
they
are
a
bit
different.
Now.
E
A
D
E
Idea
here
of
the
of
the
boards-
and
please
click
on
the
drop
down
there
on
the
blog
PR's
log,
PRS,
there's
a
drop
down
and
put
list
the
table
table
so
table
view
first,
okay.
So
what
is
the
the
goal
here?
And
this
has
been
I'm
bringing
some
of
the
stuff
that
I've
been
working
in
terms
of
the
kubernetes
release,
because
this
is
being
used
more
and
more
there
as
well
and
yeah.
E
The
idea
here
is
essentially
to
have
a
more
one-to-one
mapping
between
issues,
pull
requests
and
actual
activities
that
we
are
having.
What
I
did
here
was
essentially
to
add
the
spot.
Most
of
the
last
six
months
of
the
blogs
in
the
sites
are
there,
so
these
are
automatically
added
because
the
the
you
can
select.
E
This
is
at
the
top
level
kubernetes
level,
so
you
can
select
any
repository,
that's
underneath,
including
the
contributor
sites,
one
and
eventually
any
other
that
we
have
for
the
contributor
site,
one
I've
added
most
of
the
last
six
months
in
terms
of
of
of
Articles.
You
can
see
that
automatically
the
assignees
and
Etc
is
information
that
gets
pulled
from
from
the
actual
pull
request
or
the
issue.
You
can
add
both
issues
and
pull
requests.
E
The
status
one
is
the
so
you
you
can
also
add
custom
built
bespoke
columns
in
this
case
I've
just
added
one,
which
is
the
status
and
each
field
in
the
status
essentially
is
one
of
the
columns
in
the
in
the.
In
the
other
view,
if
you
can
change
the
other
view
now
back
to
the
board
yeah,
so
it's
the
same.
The
difference
is
that
now
each
status
is
a
column
and
it
allows
this
kind
of
view
there's
a
an
additional.
E
Let's
call
it
the
object
in
here,
which
is
the
ones
that
are
on
the
two
line,
which
are
this
draft
thing.
This
are
the
only
ones
that
only
have
existence
in
the
projects
and
not
an
actual
reference
in
terms
of
the
kubernetes
repository.
So
there's
no
actual
issue
rpr
named
Spotlight
book
reading
club,
for
example,
this
lives
only
inside
the
project
like
I,
think
this
is
similar
to
most
of
the
entries
that
we
had
in
the
previous
ones
why?
E
These
are
this
is
useful
because
it's
not
it's
not
always
that
you
want
to
open
an
issue
just
for
a
placeholder
idea,
although
that
is
possible.
E
There
are
such
things
as
placeholder
issues
in
place
of
aprs,
but
in
terms
of
making
this
operational,
there
are
several
ways
that
I
can
think
the
one
that
is
the
the
least
amount
of
work
is
essentially
following
what
we
have
right
now
and
what
do
we
have
in
terms
of
blog
posting,
there's
a
separate
discussion
that
we
can
go
afterwards,
which
is
if
we
should
review
or
not
the
the
blogging
guidelines,
in
terms
of
who
opens
the
push
request?
E
Etc,
let's
keep
it
keep
that
on
ice,
but
we
do
not
have
an
issue
based
approach
for
blogging.
What
I
mean
by
this
is
that
we
do
not
open
an
issue
saying
blog
about.
We
need
to
blog
about
Sig
architecture
spotlights,
and
then
this
issue
in
turn,
is
referenced
in
a
in
a
pull
request
with
the
actual
Spotlight
that
closes
the
the
the
the
the
issue.
We
are
not
doing
this,
should
we
do
this
I'm
not
opposed
to
it,
because
I'm
used
to
to
that
when
working
with
code.
E
So
for
me
it
flows
naturally,
and
also
since
we
have
more
than
a
push
request.
For
example,
we
are
speaking
about
hack,
MD
reviews
stuff,
like
that
these
leaves
outside
of
the
of
the
pull
requests
that
we
need.
We
are
currently
adding
that
information
to
the
pull
requests,
because
it
makes
sense
it's
there,
but,
but
speaking
in
terms
of
the
the
pull
request,
it's
completely
separate.
So
just
like
an
issue
in
a
kubernetes
enhancement
can
have
like
the
link
to
the
to
the
cap
and
to
the
implementation.
E
Then
each
pull
requests
is
a
part
of
that
we
could
also,
and
and
I'm
I'm
I'm,
describing
ideas
just
for
joint
criticism
of
it.
We
can
also
move
because
if
you
click
on
one
of
these
drafts,
you
can
immediately
say
create
issues,
so
you
can
actually
prompt
these
drafts.
You
can
create
an
issue
if
that
issue.
We
could
follow
up,
for
example,
the
the
initial
hack
MD
or
the
the
initial
discussion
around.
Where
will
it
be
published?
Etc
then?
E
This
would
give
birth
to
a
PR
which
is
going
to
close
that
issue,
and
we
would
track
the
issue
here
or
or
the
pr
alternative.
We
don't
use
issues
we
just
use
PRS,
which
are
also
tracked
here
automatically
actually
automatically
it's
too
strong
of
awards.
Maybe
with
the
with
with
the
tech,
leads
that
we
have
here.
We
can
look
into
ways
of
making
this
a
bit
more
automated,
specifically,
if
we
could
add
some
specific
label
to
the
pull,
requests
or
or
something
maybe
it
will
make
sense.
E
E
So
this
could
be
actually
done
as
a
manual
review,
but
we
could
obviously
move
things
from
one
lane
to
the
other,
just
to
have
an
overview
moving
things
here
that
do
not
does
not
act
on
on
the
pull
request
itself,
so
it
doesn't
change
labels
as
far
as
I
could
it
could
tell
it?
E
Doesn't
really
you
you
don't
well,
it
might
be
possible
to
do
it,
but
as
it
is
you
you'd
just
by
moving
the
sick,
instrumentation
Spotlight
one
to
done
it
doesn't
close
the
the
the
issue,
it's
more
of
a
metadata
kind
of
thing
that
lives
within
the
project
still
I
think
that's
this.
E
This
has
one
good
advantage
of
this
is,
is
that
it
has
a
good
one-to-one
mapping
with
actual
stuff
that's
going
on
in
the
repository,
and
it
does
allow
us
to
have
a
quickly
an
overview
in
terms
of
the
of
the
the
blog
specifically
I
thought
of
this.
For
the
blogging
efforts
we
now
we
do
not
have
a
lot
of
blogs,
but
if
we
are
going
to
change
that
and
that's
another
part
of
the
projects
for
2023,
so
increased
number
of
logs
cover
more
stuff,
you
have
more
ideas.
B
E
I'm
yeah
I'm
having
them
manually,
and
that
was
the
part
that
I've
said
that
it
could
be
interesting
to
to
check
how
to
automatically
import
them.
This
is
being
done,
for
example,
for
the
enhancements
tracking
in
kubernetes,
so
there
are
ways
to
run
something
every
day
that
just
goes
into
everything
and
and
adds
them.
D
E
Would
just
have
so
I'm
not
overly
concerned
about
the
technical
ability
to
do
it,
I'm
more
thinking
about
what
is
the
data
that
that
automation
would
work
on
but
I,
because
without
that,
there's
no
automation
that
will
work
so,
the
speaking
another
different
level?
Should
we
have
like
a
a
label
around
the
country,
contributor,
blogging,
spotlights
or
I,
wouldn't
yeah
or.
D
E
And
for,
for
example,
is
that,
can
you
open
the
seek
instrumentation
spotlights
one
which
Imran
just
separated.
B
E
E
We
don't
have
that
label,
should
we
add
it
that
so
we
are
just
going
down
the
rabbit
hole
in
terms
of
when
is
that
label
added,
because
it's.
E
That's
great
that
then
I
would
say
this
if
we,
if
we,
if
we
add
it,
if
everyone
adds
it
automatically
when
it's
something
that
requires
an
attention,
I
I,
don't
think
that
we
even
should
concern
ourselves
with
the
blogging
aspect.
We.
D
D
D
E
Yeah
I
I,
England,
I
I
can
refer
you
later
on
to
the
stuff,
that's
being
done
on
the
on
the
on
the
release.
Cycles,
because
that's
what's
being
done
in
terms
of
capturing
the
Milestone
and
stuff
like
that,
there's
like
a
I,
don't
know
if
it's
a
bash
script
or
something.
C
D
E
D
D
F
It
will
require
someone
who
has
knowledge
of
Bash
according
to
knowledge
of
bash
I,.
C
G
E
B
B
E
Programming
part
is
the
complex
one.
We
can
bash
this
out
exactly
it's
more
of
thinking
of
where
what
is
what
is
the
information
that
we
want
to
act
on
and
what
is
the
end
result
that
we
wish
I
think
that
we
have
a
good
starting
point.
The
information
that
we
want
to
act
on
is
everything
that
has
a
specific
label
and
the
end
result
is
adding
it
to
the
specific
project
View
second
stage.
E
We
could
look,
for
example,
into
the
status
of
the
PRS
and
the
and
the
issues
and
automatically
move
them
into
the
correct
Lane.
If
someone
closes
the
PRS
or
issue,
it
makes
sense
for
it
to
move
automatically
to
to
the
move,
but
I
think
this
is
the
second
step
and
we
can
go
little
by
little
just
by
having
everything
with
our
label
present
in
a
list.
E
I
think
we
have
a
lot
of.
We
have
the
material
to
do
a
lot
of
interesting
stuff.
Even
if
we
don't
go
crazy
with
additional
automation.
A
E
A
A
C
B
E
And
I
I
miss
I'm
easily
bribed.
So
it's.
A
So
you'll
be
great
to
work
with
sounds
like
that's
what
it
sounds
like
to
me.
We've
only
got
five
minutes
left
I.
Think
we'll
skip
the
table
for
today,
just
if
anyone
else
has
any
items
that
they
wanted
to
talk
about
today
bring
those
up
now.
I
think
these
were
some
awesome
discussions.
I'm
really
excited
about
these
projects
and
I'm,
so
glad
that
you
all
are
here
to
help
with
them
hope
you're
having
fun
with
it.
F
E
C
E
B
A
Cool
I'm
still
gonna
put
it
in
the
the
notes
as
a
win.
B
H
I
was
going
through
this
one
little
roll
handbook
for
the
com
events
and
just
found
a
couple
of
broken
links
for
the
skills
and
requirements.
Section
I'll.
A
So
yeah
go
ahead
and
and.
H
I
need
to
raise
the
pr
in
the
same
repo.
Yes,.
D
H
A
A
All
right,
let
me
add
that.
B
Nitish
broken
links
to
fix.
A
All
right,
we
are
like
at
time
also
initial
PR,
so
much
stuff
today.
So
awesome,
you
all
know
where
to
find
us.
If
you
need
any
help
at
any
point,
you
can
ping
Us
in
the
contributor
comms
slack
Channel,
and
you
can
also
ping
anyone
directly
often
a
better
way
to
get
people's
attention.
Sadly,
but
if
you
need
any
help
with
anything,
let
us
know
we
should
set
up
an
additional
meeting
to
talk
about
the
workflow
from
Twitter
to
buffer
to
from
GitHub.