►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting 20210305
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
C
A
A
D
A
A
We
can
do
a
working
session
on
that
and
just
collaboratively
get
those
out.
I
think
it's
always
fun
to
feel
like
we
accomplished
something
in
a
meeting.
I
know,
that's
goes
against
the
rules,
but
that's
my
favorite
kind,
cool,
okay,
going
into
other
sort
of
campaigns,
I
think
we
can
officially
looks
like
psp
is,
could
put
at
least
draft
one
and
it
definitely
sparked
a
important
conversation
with
communicating
yeah
with
getting
communications
out
there-
maybe
a
bit
earlier
next
time,
but
it
doesn't
really
matter
we're
getting
to
the
right
conclusion.
A
B
B
I
was
just
not
sure
if
my
sigs
were
correct.
I
know
ian's
on
sick
security.
I
wanted
to
make
sure
I
was
right
on
top
of
the,
but
anyway,
ian
and
tabitha
are
working
together
on
a
new
draft
for
that
blog
post,
since
they
felt
that
they
were
close
enough
to
a
new
solution.
That'll
replace
psps
that
they
wanted
to
make
sure
that
that
was
included.
A
And
in
that
way,
while
it's
absolutely
not
the
path
of
least
resistance
or
the
path
we
thought
we
were
going,
I
still
feel
like
we
did
a
really
good
marketing
mitzvah.
If
I
can
use
my
that
phrase
here,
because
we
got
people
talking
about
it
and
and
going
towards
the
right
work.
So
that's
wonderful,
but
yeah
I'll,
remove
that
for
next
week,
great
any
other
thoughts
or
questions
or
ideas
around
psp's
security
policy.
Things.
B
A
Yeah
yeah
I'd
love
to
show
them
the
support
along
the
way.
I
I
know
it
it
definitely
gets
into
this.
You
know
more
is
welcome.
I
I'm
sure,
like
the
blog
team
will
we'll
get
to
it,
and
that's
like
one
of
those
overlaps
that
I
think
with
taylor
being
busier
and
not
being
involved
in
our
group
here,
we'll
we'll
probably
want
to
revisit
who's
kind
of
tracking.
A
What's
going
on
in
the
blog
subgroup
as
well
of
docs
for
the
newer
folks,
like
we
team
up
with
them
or
like
their
pop,
their
process
overlaps
with
our
process.
When
it
comes
to
tech
review,
they
we
definitely
defer
to
them
because
we're
the
the
new
kids
on
the
block,
but
it
if
you've
seen
a
pr
on
the
website.
Everyone's
welcome
to
comment
and
offer
feedback.
So.
E
A
Joel
yeah
that'd
be
wonderful,
it's
really
just
making
sure
they
know
that
we're
here
to
support
them
and
not
to
kind
of
be
in
the
way.
I
don't
feel
like
anyone's
terribly
territorial
in
our
community,
which
is
amazing,
but
just
always
good,
to
have
people
explicitly
work
in
to
make
sure
we're
facilitating
that.
E
A
C
C
I
believe,
when
one
one
area
where
you
can
separate
those
stuff
is,
I
mean
the
way
release
comps
is
improving,
is
we
are
now
opting
in
for
feature
blocks
right,
so
we
wait
until
everybody
has
said
that
okay,
we
are
gonna,
write
this
feature
block
and
once
they
have
done
that
whatever
remains
is,
and
we
think
that's
important
people
need
to
be
aware
of.
We
go
ahead
and
write
it
right.
That
way.
There
are
no
intersections
to
say.
C
Yeah,
no,
so
the
way
comms
is
gonna
work
from
now
onward
says
we
would
ask
sigs
whoever
wants
to
write
a
blog
on
whatever
they
are
doing
right
for
that
particular
release.
Right
so,
let's
say
psp
is
getting
duplicated
and
if
somebody
is
already
interested
in
writing
it,
they
let
us
know
right
by
a
specific
deadline
and
by
the
time
let's
say
somebody
is
already
writing
it.
It's
good.
If
it's
not
writing
it,
and
we
think
it's
important.
A
A
E
B
A
D
A
Okay,
great,
I
incorporated
your
edits
on
mine.
Thank
you
so
much
they're
really
thoughtful
and
you
you
helped
clarify
some
of
the
wordier
parts,
which
I
always
appreciate.
I'm
going
to
work
on
a
pr
for
that
one
too
and
bob,
and
I
were
talking
about
making
like
a
a
very
short
announcement
article
that
says
like
what
what
is
this
and
have
it
be
able
to
cross
post
on
dot
io
as
well,
since
it
has
more
subscribers.
A
So
I
think
those
are
the
ones
that
are,
I
know,
are
outstanding
right
and
thanks
for
the
copy
editing
it
looks
beautiful
now,
oh
cool,
I
mean
I
love
your
story,
so
if,
if
any
of
y'all
haven't
read
it
it's
worth
poking
around
and
I
love
your
love,
others
feedback
on
like
what
the
strongest
angle
is
or
ph,
yeah,
no
rush.
If
you
want
to
think
about
it,
but
I
guess
there
are
two
kind
of
angles
you
could
approach
it
from
that
I
noticed.
C
A
A
Yeah,
so
we
can
give
it
some
time
whenever
you're
ready.
You
could
pr
that
in
as
well
and
I'll
get
a
yeah
that
short
kickoff
article
out
there.
I
think
our
our
like
hard
goal
is
to
get
a
series
going
by
kubecon
eu,
since
one
of
the
talks
that
was
accepted,
yay
team
has
to
do
with
contributor
articles,
so
it
would
line
up
well
if
we
had
something
published
by
then,
and
it
also
gives
us
some
runway,
which
is
nice,
but
while
we're
on
it.
B
I'm
I've
been
thinking
about
this,
since
I'm
also
going
to
be
helping
out
with
the
kubecon
piece
and
and
just
in
general
thinking
about
this,
I'm
thinking
I
saw
someone
on
twitter
post
something
about
their
contributor
journey
recently
and
I
was
like
wow.
I
wonder
if
they'd
be
interested
in
doing
one
of
these
posts,
so
I
think
I'll
reach
out
to
someone
external
and
see
if
they
would
be
interested
in
participating
in
this,
like
still
within
the
kubernetes
project,
obviously
but
right
external
to
our
group,
so
I'll
check
with
them.
On
that.
A
A
E
B
A
F
E
F
A
Great
question
we're
so
there's
there's
a
if
you're
a
github
enthusiast.
You
can
open
an
issue
in
the
website
where
we
want
to
post
it.
So
it
would
be
the
contributor
site,
as
an
issue
saying
like
you've,
got
this
article
you're
into
it
and
then
open
a
pr
for
it,
but
like
we're,
we're
still
kind
of
in
this
in-between
phase,
where
we're
just
tracking
things
in
this
google
doc.
Okay,.
F
E
C
A
F
A
Love
it
great.
Okay.
Next
up,
we've
got
yeah
the
kubernetes
policy
comparisons,
jason
said
he's
gonna,
take
a
look
at
that
and
he's
not
here
this
week.
So
no
problem,
you
know
it
sounds
like
the
first
article
is
still
coming
out.
So
this
would
be
a
future
hopeful
article
speaking
of
future
shifting
kubernetes
contributors
to
async
yeah
gotta
get
bob
on
that
good.
Any
other
article
ideas,
things
you've
been
thinking
about
writing
or
wanting
to
talk
about.
B
B
Just
an
item
to
talk
about
because
we're
gonna
have
to
do
articles
on
it.
We're
gonna,
be.
I
know
that
I'm
thinking
about
the
twitter
plans,
I
usually
tweet
out
pretty
much
as
much
as
I
can
fit,
as
is
happening
in
the
maintainer
track,
which
is
all
about
contributors
and
focused
on
contributions.
So
try
to
make
sure
that
the
arcade's
contributors
account
is
promoting
those
talks,
but
it
it
takes
some
planning
so
but
we'll
also
be
doing
blog
posts
and
stuff.
A
A
But
this
one's
fun
so
the
path
to
non-code
contribution
myself
will
be
in
that
one
and
then
pierce
me
chris,
and
I
don't
think
we
could
get
you
on
that
other
one
caslin
are
gonna,
be
on
another
one
about
writing
these
article
series,
so
pretty
pretty
pumped
that
we
get
to
share
these
stories
and
also
a
healthy
reminder.
If
you
want
to
speak
at
a
kubecon,
the
maintainer
track
is
when
you
team
up
with
teammates
here,
has
pretty
good
hit
rate
so
far.
B
B
I
usually
create
a
plan
a
little
too
close
to
time,
so
I'm
hoping
I'll
do
that
a
little
faster
this
time
and
maybe
put
them
in
a
spreadsheet
of,
like
which
I
usually
try
to
fit
several
sessions
into.
One
tweet
like
in
this
time,
block
they're
going
to
be
sessions
about
x,
y
and
z,
make
sure
you
check
it
out
on
the
schedule,
and
I
do
that
for
like
all
of
the
maintainer
free
a
day.
B
So
I
try
to
set
these
up
in
a
separate
tool
from
the
github
so
that
they
will
go
off
on
a
schedule,
because
our
twitter
together
has
an
issue
with
scheduling,
with
the
way
that
we
do
merging
of
of
new
stuff
into
repos,
because
we
always
have
to
fork
our
repo
and
do
the
pull
request
from
a
fork
and
that
kind
of
throws
off
twitter.
Together's
scheduling
thing.
B
Rajula
could
probably
explain
this
way
better
than
I
could,
because
I
don't
really
know
what
I'm
talking
about,
but
so
I
ended
up
doing
them
separately
outside
of
that
repo.
Sadly,
but
I'll
at
least
create
a
plan
and
probably
try
to
show
it
to
this
group
of
what
we're
going
to
be
tweeting
for
kubecon,
and
I
also
like
I'm
just
like
hey
sign
up
for
kubecon
leading
up
to
the
event
I
sent.
A
A
That's
always
a
nice
format.
If
you're
like
looking
to
hunt
down
some
additional
content
ideas,
but
I
feel,
like
we've
got
a
healthy
amount
of
stuff
in
progress,
so
I'm
not
too
worried
about
it.
Unless
the
request
comes
in
always
trying
to
balance
that,
like
input
versus
you
know,
just
us
outputting
on
our
own
but
yeah,
anyone
else
have
thoughts,
feels.
C
E
A
C
D
A
D
B
B
D
C
Yeah,
I
guess
nothing
others.
Now
we
have
got
the
deadline
done.
We
have
got
people
signing
up
or
opting
in
for
the
blocks
and
all
those
things
so
so
yeah.
I
think
we
are
good
on
that
front
once
things
started
getting
finalized
once
those
blogs
are
in
place,
so
probably
we
can
give
them
a
shout
out.
C
A
A
B
B
B
It's
not
my
tool
of
choice
and
I
submitted
one
where
I
accidentally
had
one
of
the
other
tweets
in
the
same
pr
and
I
had
to
delete
it
because
I
wanted
them
all
to
be
separate
prs
and
apparently
that
caused
problems
and
one
of
the
tweets
is
still
stuck
in
a
state
where
it's
it
has
a
label
from
our
our
prowbot
saying,
needs
rebase.
So
I
worked
with
bob
together
on
that
yesterday
and
we
tried
to
work
out
what
was
going
on
and
it's
still
stuck
there.
B
It
seems
like
a
bit
of
a
mess,
so
I'm
not
super
concerned
about
getting
that.
One
unstuck.
I
can
always
do
it
manually,
but
we're
trying
to
figure
out
how
I
got
into
that
state
and
like
make
sure
that,
if
that
has
any
implications
on
like
guidance
of
how
we
help
other
people
who
are
not
very
familiar
with
git
use
our
twitter
repo.
Hopefully
the
issue
to
pr
thing
will
totally
eliminate
this
problem,
but
we
are
figuring
that
out.
A
E
A
B
D
B
B
B
A
B
B
A
B
Looked
at
it
right
after
that,
push
and
for
a
few
minutes
after
and
it
didn't
go
away
yet
so
we
were
wondering
if
there
was
something
we
could
do
to
trigger
the
bot
to
look
at
it
again.
Okay,
so
that's
good
to
know,
it
was
just
that
it
was
slow
at
taking
away
that
label
after
we
had
done
the
rebase
interesting.
A
D
A
Cool
yeah,
I
would
say
I
would
bet
that
it
yeah
the
commit
history
got
out
of
whack
like
if
it.
If
you
need
to
rebase
it
means
like
you,
have
a
non-linear
commit
history,
I'm
probably
saying
something
you
already
know
and
you
don't
know
how
you
got
there.
So
I'm
not
adding
any
value
and
I'll
stop.
Speaking
now.
B
E
A
A
Yeah
I
like
that
it's
a
tool
that
has
like
a
an
easy
mode,
but
as
soon
as
you
get
out
of
it
like
you
could
spend
like
a
phd's
worth
of
time,
trying
to
figure
out
how
how
it
was
built
and
how
it
works.
Like
feels
like
a
game,
a
very
complex
game,
I'm
just
seeing
like
stairs
I'm
gonna
stop
outing
myself
as
a
get
enthusiast.