►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 2023-06-02
Description
[SIG ContribEx] Weekly Marketing Meeting for 2023-06-02
A
A
B
C
D
D
Slack
I'm,
so
okay.
So
let's
take
a
step
back
for
me
to
understand
where
we
are
I,
made
a
series
and
increase
as
well
a
series
of
initial
comments.
Then
I
actually
went
and
did
actual
changes
in
the
documents
in
terms
of
adding
sections
and
structure.
Different
structure,
Etc
and
I
asked
you
in
the
in
the
threads
which
I
will
share
here.
D
C
C
C
D
C
F
A
B
C
D
D
So
obviously
there
are
no
and
Chris,
but
I'm,
not
sure,
because
I
think
that
a
lot
of
people
could
have
made
changes
without
necessarily
marking
them,
like
I
did
so,
for
example,
so
ping
me
anyone
that's
hearing
if
if
they
did
any
kind
of
change
there
and
I'll
add
them
as
as
co-authors,
in
the
at
least
in
the
commit
I.
Don't
know
if
you
want
to
add
to
change
the
authorship
of
the
blog
itself,
I.
D
D
Yeah,
so
that's
a
good
one
Chris
does
it
make
sense
for
us
to
go
through
fmd
first,
because
in
my
I
I
understand
the
the
idea,
but
in
my
last
experiences
with
it,
I
always
got
zero
feedback
on
the
XMD
file.
Oh
okay,
because
most
of
the
people
that
will
say
something
like
Tim
yeah
Will
are
more
than
okay
with
submitting
stuff
in
the
in
git,
because
that's
where
he
spends
most
of
his
time,
fair
enough
yeah
so,
and
we
already
had
the
discussion
around
the
Google
Docs,
so
yeah.
F
B
D
But
but
well
there's
nothing
lost
because
I
need
to
do
the
markdown,
so
I
can
create
an
fmd
today
and
then
early
next
week
open
the
pr-
and
this
gives
us
two
three
days
just
for
anyone
to
actually
do
any
kind
of
markdown
flavor
changes
to
the
to
it.
So
there's
nothing
lost.
So,
let's,
let's
follow
the
process
then,
and
and
I'll
do
it
like
that
cool.
B
B
B
A
A
A
B
A
E
F
F
A
B
B
B
A
A
Moving
on
from
that
item,
sujay
had
a
PRN
I,
don't
think
he's
on
today,
but
so
Jay
had
a
PRN
to
fix
some
Upstream
marketing
text
in
some
various
places
to
contribute
your
comms
I
also
realized,
as
I
was
approving
that
PR,
that
that
is
like
a
Sig,
contribex
level.
Pr
so
I
have
that
access
because
of
that.
A
A
A
There
was
one
thing
that
came
up,
I
think
avinashi
weren't
there
last
week,
but
one
thing
that
came
up
that
would
be
an
events.
Lead
thing
is
Twitter
spaces.
We
have
a
Kate's
contributors,
Twitter
account,
but
we
have
literally
never
thought
about
Twitter
spaces.
Someone
in
one
of
the
last
meetings
mentioned
that
I
should
have
written
down.
Who
said
that
was
very
smart
idea.
A
Is
some
yeah?
There
is
some
precedent
for
this?
Actually
they
we
used
to
have
like
meet
our
contributors
sessions
which
would
be
live
I
think
they
were
on
YouTube
live
stream
sessions
where
Paris
would
interview
maintainers
and
folks
could
like
ask
questions
and
stuff.
We
also
used
to
have
like
office
hours
where
folks
would
be
on
live
to
answer
questions
so
there's
definitely
precedent
for
doing
live.
F
A
B
Work,
do
we
want
to
put
into
this
yeah
I,
don't
know
how
much
investment
we
should
put
into
Twitter
it'd
be
nice
if
we
could
come
up
with
like
a
bi-weekly
or
a
monthly
kind
of
space
where,
like,
if
there's
some
planned
content,
there's
some
office
hours
vibe
to
it,
but
yeah,
it's
it's!
It's
feasible!
I
just
want
to
make
sure
that
we
have
a
good
content
plan
for
it.
B
D
E
G
D
Could
find,
for
example,
someone
some
project
Etc,
especially
someone
who
has
a
large
follower
counts,
because
we
were
talking
about
making
this
somewhat
more
known.
I
think
that
we
could
like
make
a
space
about.
Let's
talk
a
bit
with
X,
that's
and
and
learn
how
it
starts
to
contribute
to
kubernetes
and
also,
if
you
have
any,
if
you
want
to
to
learn
how
to
join
and
how
can
we
help
join
in
and
we
were
there.
So
maybe
it
sort
of
depends,
but
in
the
Swedish
places
that
I've
been
to
there's
this.
D
So
there's
a
topic,
but
there's
the
the
actual
structure
in
preparation
is
reasonably
light
right.
It's
like
we
have
a
couple
of
people,
let's
talk
about
the
topic
and
then
it
mostly
opens
up
to
questions
and
answers
from
the
from
the
community
which
which
I
think
it's
it's
actually
fine,
because
I
don't
think
that
we
we
should
like
spend
lots
of
time
preparing
stuff
right.
B
E
D
D
B
Yeah
yeah,
like
you,
could
just
take
the
recording
and
slap
it
somewhere
and
post
that
as
a
blog
post
right,
like
hey,
take
a
listen
to
this.
If
you
so
choose
the
the
the
possibilities
are
endless.
Yes,
we
do
I
mean
we,
the
case
contributor.
Folks,
don't
have
a
channel,
but
there
is
a
kubernetes
channel.
I
have
access
to
it.
That
kind
of
thing.
B
F
A
F
F
B
F
A
I
did
make
some
updates
in
the
repo,
but
yeah
did
not
do
that
one
yet,
but
we
want
to
update
the
sub
project
role
handbook
to
say
that
you
should
be
a
current
lead
in
the
sub
project
in
order
to
become
a
shadow
for
the
sub-project
lead
position.
So
anyone
who
is
the
current
lead
if
you're
interested
in
becoming
a
sub-project
lead.
Let
us
know
we'd
happy
be
more
than
happy
to
have
you
as
a
shadow
yeah.
B
B
Yeah
put
some
documentation
behind
that.
So
that
folks
understand,
if
your
Shadow,
the
expectation
is
you'll,
become
a
lead
at
some
point
and
those
leads
then
become
sub-project
leads
so
that
Aslan
can
go
on
and
do
her
Sig
contribex
Sig
leadership
thing
as
a
full-time
job,
I
suppose
I
mean
I.
Guess
you
would
show
up
here.
Sometimes
too,
just
like
Bob
does
but
yeah
Bob
did
yeah,
there's
there's
a
ladder
and
it
needs
to
be
documented.
A
Also
offered
to
make
this
change,
but
I
wanted
to
do
it
myself,
but
thank
you
nitish
for
offering
we
may
yet
need
your
help.
I
was
just
thinking
earlier
that
I
would
love
it
if
all
of
the
leads,
if
you
would
go
through
your
handbooks,
Your
Role
handbooks
and
add
a
section
of
clear
Shadow
requirements.
So
what
we
have
right
now
is
we
have
the
requirements
to
become
a
lead
which,
as
we
were
thinking
about
it
when
we
were
building
it
like
that,
seemed.
A
A
You
should
have
done
these
things
kind
of
thing,
which
is
a
little
bit
different
from
the
requirements
of
like
being
the
lead,
because
some
of
those
things
you
build
as
your
Shadow
or
at
least
you
can
build
as
your
Shadow,
but
some
of
them
you
need
to
have
before
you
apply
to
be
a
shadow
as
if
there's
an
application
process
aside
from
just
ping,
maybe
there
should
be
an
application
process.
I,
don't
know
I,
don't
think
we're
at
that
point
yet,
but.
A
A
B
B
So
all
that
stuff
will
be
in
one
place.
Finally,
and
maybe
we
can
actually
look
into
GitHub
to
Twitter
through
zapier
now,
since
we
have
multi-action
available
and
all
those
other
things
someone
had
some
kind
of
demo
I
forget
who
someone
gave
me
a
recipe
at
one
point,
but
I,
don't
know
what
happened
to
it.
So
I
need
to
go
dive
through
my
discussions
and
figure
that
out.
B
Yeah
so
there's
a
there's,
a
lot
of
automation
that
needs
to
happen
behind
the
scenes
and
Sig
contribex
has
a
lot
of
meetings.
You
know
we
have
a
lot
of
sub
projects,
a
lot
of
meetings,
so
for
so
on.
So
whenever
the
Sig
contributes,
Zoom
account
records
a
meeting
to
the
cloud
it
gets
automatically
stored
in
Google
Drive,
and
then
you
know
titled
and
everything
else
in
another
job
to
push
it
from
drive
to
YouTube.
B
So
that's
how
these
meetings
end
up
on
YouTube
and
I've
noticed
that
they're
labeled
as
marketing
meetings,
not
contributor,
comms
meetings
last
week,
so
add
another
thing
to
the
list
of
crap.
We
need
to
fix
yeah.
So
getting
all
these
automations
into
one
place
has
been
a
goal
for
a
little
bit.
It's
finally
now
capable,
and
now
we
can,
then
you
know
start
to
look
at
replacing
the
the
whatever
bot
we
used
for
GitHub
and
Twitter
and
use
zapier.
Instead,
now
they
we
have
an
official
account
with
multi-step
actions.
B
F
A
A
B
C
B
B
A
B
D
D
Oh
yeah,
perfect,
so
I've,
I've
elected
the
issue
itself,
just
to
confirm
and
I
didn't
add
links,
because
the
the
documents
have
that
the
links
are
for
the
editors,
so
everyone
that
clicks
on
them
can
change
the
documents,
but
all
the
different
five
sub
projects
are
working
on
the
answers
which,
let
me
read
before.
Remember
it's
code
organization,
Apu,
API
governments,
production
readiness,
enhancements
and
confirm
conformance
testing.
D
A
D
A
G
Yes,
so
the
first
one
I'm
going
to
talk
about
is
the
Sig
release.
I
drafted
the
questions
after
this
exams
are
over
created
the
group
with
the
coaches.
Everyone
liked
the
idea
and
I
got
a
respond
back,
that
they
will
definitely
answer
the
question
that
have
been
treated
for
the
docs,
so
I'm
just
waiting
for
the
response
to
the
questions.
I'm
looking
forward
to
reframe
a
log
out
of
it
yeah.
A
A
A
A
I
also
wanted
to
try
to
engage
with
some
of
the
other.
Contourbacks
leads,
one
of
the
other.
The
other
contribbeck's
co-chair
has
been
traveling
also,
so
it's
not
just
me
I
could
say
so.
I
need
to
reach
out
to
the
other
co-chair
and
get
that
going
of
the
co-chair
as
well.
I
think
it's
nice
to
have
a
variety
of
perspectives.
Also
the
tech
leads,
the
tech
leads
for,
say.
Contribex
are
so
on
point.
A
F
A
A
A
F
B
B
A
A
G
Regarding
the
same
signal,
I
think
I
personally
observed
this
one
and
I
think
at
this
moment,
I
wanted
to
focus
on
the
the
sick
release
as
of
more
specific
because
it
consists
of
two
blogs,
so
it
if
I
consider
the
Sig
node,
it's
gonna
be
three
at
a
time
and
I
personally
think
that
it
would
be
very
difficult
to
manage
all
the
three
at
the
same
time.
So
if
anyone
is
wants
to
take
up
the
six
portrait
block
for
the
Sig
note,
he
or
she
can
otherwise
I'll.
A
A
F
A
F
F
G
A
A
A
A
A
B
F
A
F
A
A
Excellent.
Thank
you
very
much.
What
other
things
do
we
have
update
contributor,
comms,
GitHub
team,
maybe
someday.
We
have
one
minute
left
so
it's
time
to
rush
through
these
update
storytelling
resources
to
blogging
resources,
Frederico
reminder
on
that
migrate,
very
sapier
jobs
to
new
contributors
at
account.
So
you
do
have
that
on
there
wonderful
promote
new
contributor,
Workshop
content,
still
waiting
comms
guidelines
for
sensitive
security
topics,
maybe
someday
I
guess
I
should
put
that
over
there
that
there.
E
A
F
B
Was
does
anybody
have
like
any
red
flags
about
the
registry
blog
or
the
registry
announcement
and
how
it
went
like
one
red
flag,
I
got
was
many
people
I
know
that
are
like
kubernetes
users
didn't
see
this,
they
just
they
knew
about
it
when
their
cloud
provider
told
them
about
it
kind
of
thing.
So
that's
interesting.
A
A
A
F
F
So
when
we
were
doing
the
registry
comms,
there
were
typically
about
their
blogs
or
content
creation.
There
were
places
like
to
do
I
I,
remember
that
there
were
three
places
where
blogs
were
written
and
all
the
documentations
were
here
there
here.
Federico
was,
you
know,
jumping
over
documentations
and
he
was
catching
up
those
things,
so
maybe
a
structuralized
manner
of
handling
that
thing
could
be
something
that
we
could
think
of.
A
E
A
So
we're
going
to
be
updating
that,
because
we've
been
having
these
conversations
in
these
meetings,
a
requirement
for
becoming
a
sub-project
lead
is
going
to
be
to
be
a
different
lead
first.
So
if
you
are
interested
in
climbing
up
the
ladder
as
a
contributor,
we'd
recommend
going
for
events
or
blogging
or
Tech
leadership
instead
of
sub-project
leadership
for
now.