►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20230317
Description
[SIG ContribEx] Weekly Marketing Meeting for 20230317
A
B
B
B
A
A
My
time
it
was
like
I,
don't
remember
like
3
P.M
hour
Federico
time,
but
like
the
urgency
at
that
point
for
me
was
like
getting
it
done
before
5
PM
Federico
time,
and
we
almost
pulled
it
off
like
just
a
few
minutes
over
and
that
was
awesome
and
if
I
could
give
you
an
award,
I
would
right
now.
So
thank
you,
Frederico.
That
was
an
enormous
amount
of
work
and
thank
you.
A
Everyone
else
that
contributed
to
it
that
is
comms
doing
something
well,
I
feel
like
right,
like
we
had
so
much
input
on
that
dock
and
having
all
that
knowledge
put
together
and
out
there
in
a
way
that
anybody
can
understand,
made
talking
to
literally
the
entire
Community
much
easier.
So
thank
you
Frederico,
and
thank
you
to
everyone
that
contributed
to
the
registry
change
blog
post.
C
Well,
thank
you
very
much
for
the
kind
words.
I
would,
however,
say
that
obviously
I
think
it
was
relatively
straightforward
because
we
already
had
done
some
of
the
groundwork
in
terms
of
the
process
right,
so
the
the
the
overall
mechanism
of
getting
it
out
the
door
was
already
understood
by
by
everyone.
C
B
C
It
was
interesting
that
there
are
some
lessons
learned
there
as
well
around
the
need
to
to
how
to
use
the
tracking
boards
with
others,
because
at
a
certain
point
in
time
we
also
have
a
conflict
of
tracking
boards.
Different
tracking
boards
are
looking
into
the
same
thing
and
it's
a
bit
like
standards.
If
you,
if
you
have
more
than
one,
then
it's
it's
yeah,
either
F1
or
it
doesn't
really
matter,
and
it's
the
same
with
tracking
boards
right
I
I
think
that
some
people
were
updating
their
own.
C
A
Yeah
the
the
thing
I
would
like
to
do
in
hindsight
once
this
rolls
out
over
the
course
of
the
next
week
is
I
I
told
Sig
Kate's
end
for
this
morning.
You
know
like
how
do
you
want
to
communicate
this
out?
I
just
asked
him
and
I
was
if
and
Bob
pretty
much
everyone
said,
let's
just
amplify
what
other
people
are
saying
when
it
happens,
so
social
media,
like
I'll,
be
on
top
of
that
like
but
they'll
be
sending
stuff.
A
A
And
I
still
have
like
I
I
have
a
lot
of
stuff
to
add
to
various
rulebooks.
Still
so
I
might
add
some
things
and
then
social
media
around
hackyderm
and
kind
of
like
Christoph
blecker,
brought
up
a
point
of
hachyderms
policy
around
like
corporate
and
open
source
projects,
and
things
like
that
and
my
take
on.
It
is
X
and
you
know
somebody
else's
take
on.
It
might
be
why?
A
So
please,
you
know,
send
stuff
our
way
or
you
know
amplify
it
yourself
and
I'll
catch.
It
kind
of
thing,
I'll
make
sure
my
cloud
native
list
is
being
watched
heavily
that
day,
so
yeah
great
job
would
really
like
to
run
a
retrospective,
because
the
process
is
there
how
we
could
tweak
it
or
enhance
it
or
make
it
I,
don't
know
for
me,
Monday
Tuesday
last
week
was
stressful,
like
seriously
stressful,
so
getting
through.
A
B
A
With
you
know,
even
even
dims
internally
is
like
Hey
What,
Can
contributor
comes
to
and
I
was
like.
Let's
take
it
to
the
Kate
slack,
you
know,
let's,
let's
talk
about
it
in
there,
so
everybody
knows
right.
I,
don't
want
to
have
the
same
conversation
three
four
times
so
yeah.
It
was
just
a
really
good
job.
B
B
A
A
That
mentions
cage.gcr.io
and
we
can't
fix
all
of
it,
but
I
mean
working
internally
right
like
it
was
nice
to
have
my
team
on
board
with
like,
let's
get
the
blog
updated
with,
you
know
no
mentions
of
Kate's
registry.io
it
was.
It
was
cool
to
see
that
internally
too,
right
like
there
was
an
understanding
between
company
and
community
of
the
urgency
of
this.
B
Indeed,
so
definitely
check
that
out.
If
you
haven't
heard
about
it
very
big
deal,
so
we
will
continue
to
focus
on
that
over
the
next
week.
The
redirect
that
we're
talking
to
talking
about
in
this
post,
oh
I,
already
had
that
open
is
happening
on
was
beginning
on
Monday.
It's
going
to
be
happening
throughout
next
week.
B
It
will
impact
some
users,
but
this
is
from
what
I'm
hearing
yeah
yeah,
so
case.gcr.io
is
also
going
to
be
frozen.
So
this
is
going
to
be
fairly
disruptive
for
the
world,
for
lots
of
folks
who
still
use
case.gcr
dot.
Io
folks
need
to
switch
over
to
registry.case
dot,
whatever
it
is
for
the
good
of
the
project.
So
it's
important
that
we
let
folks
know
that
they
need
to
do
that
very,
very
important
for
budgetary
reasons,
all
right.
B
A
D
D
D
D
D
B
B
D
B
E
B
Sense,
tarva
added
these
notes
in
asynchronously.
Thank
you,
so
I
guess
I'll
just
roll
over
these.
Unless
anyone
else
has
more
context
than
I
do
because
I
don't
have
much
context.
Okay,
I'll,
just
roll
over
them
run,
run
over
them
talk
about
them,
and
then
we
can
talk
about
them
more
so
zap.
Your
automation
updates,
might
need
a
dedicated
meeting
to
discuss
more
on
zapper
automation,
to
discuss
briefly
about
Its
Behavior
and
also
it
isn't
possible
to
share
the
zap
if
it
has
the
paths
functionality
which
I
don't
know
what
that
means.
B
B
We
would
like
to
have
a
GitHub
workflow
for
members
of
the
contributor
Community
to
be
able
to
write,
tweets
and
share
them
with
us
through
a
platform
that
they're
already
very
familiar
and
working
with.
So
we
were
going
to
use
zapier
to
implement
that
because
there
were
issues
with
Twitter
together
and
also
there's
the
whole
API
thing.
There's
many
things
to
consider
with
connection
GitHub
to
our
Twitter
account.
Anyway,
so
atava
has
a
basic
layout
for
this
app
that
we
want
to
create
that
workflow
would
be
to
create
a
PR
within
the
character
limits.
A
E
A
A
B
This
was
an
issue
with
Twitter
together
because
Twitter
together
limited
you
to
the
character
limit
on
Twitter,
but
Twitter
automatically
shortens
links
when
you
put
them
in
directly
on
Twitter,
which
means
that
you
can
create
much
longer
tweets
with
more
information
in
them,
plus
a
link
than
if
you
have
a
solid
280
character
limit.
Because
if
you
do
that
on
Twitter,
then
it
counts
the
entire
link
as
part
of
the
280
or,
if
you
do
that
on
GitHub,
it
counts
as
the
the
280
characters.
A
B
B
A
B
As
soon
as
possible,
then
it
would
be
this
not
scheduled
one
I'm
going
to
put
ASAP
and
Prince
here
and
then
scheduled.
He
says,
need
some
discussion.
Author
applies
a
label
to
schedule
it
for
some
date.
Once
the
approved
label
is
applied,
push
it
to
schedule
and
buffer.
All
right
would
love
to
hear.
Why
he's
looking
at
labels
for
communicating
that
information
to
buffer
I
think
we
might
have.
A
Talked
probably
because
of
a
zapier
limitation
like
this
is
not
a
direct
like
one-to-one
thing.
This
is
a
mutation
and
we
need
certain
things
on
the
pr
before
it
actually
just
gets
picked
up.
It's
a
lot
and
like
I,
looked
at
a
sample
workflow
on
one
of
my
accounts
and
I
couldn't
figure
out
how
to
do
it.
So
the
fact
he
has
is.
B
A
That,
anyway,
so
it's
not
really
impressive,
how
it's
actually
yeah
yeah
yeah,
like
it's
actually
zapier
pulling
in
fields
from
GitHub
and
there's
no
way
to
say,
like
PR
merged,
actually
did
something
right,
like
that's,
not
a
field
that
you
could
see,
PR
status
or
something
like
that.
So
or
maybe
he
didn't
look
at
that.
I
don't
know,
but
like
there's,
there's
got
to
be
some
limitation
he's
dealing
with
and
he
can't
export
the
the
zap
so
like.
We
need
to
figure
out
how
to
like
just
screenshot
it
somehow
maybe
I.
A
D
B
C
D
A
B
A
B
B
A
A
Open
to
it
as
well,
like
just
you
know,
from
a
teaching
perspective,
because
we
can
just
use
the
example
from
the
case.io
site
and
kind
of
imported
in
yeah
I
mean
Hugo's
not
hard,
but
R.
Hugo
is
a
little
bit
harder.
Once
you
wrap
your
mind
around
the
Headless
part
of
it,
it's
kind
of
easier
in
general.
B
D
A
B
B
We
still
need
to
move
a
bunch
of
stuff
over
here,
but
yeah.
It's
a
process.
Everything
is
slow.
That's
how
we
do
all
right.
So,
let's
start
with
in
progress,
do
to
do
at
the
end,
so
in
progress
items,
I
assume
that
any
of
the
blogging
stuff
has
not
really
moved.
Well.
We've
been
working
on
the
registry
stuff,
but
yeah.
C
Not
not
much,
although
I've
had
a
quick
update
on
the
Sig
architecture,
one
additional
discussion
about
the
new
focus
of
it.
So,
instead
of
asking
it
directly
interviewing
the
the
Sig
shares,
it
was
proposed
that
the
focus
goes
into
the
project
leads
that
do
right,
apparently
much
of
the
work
there.
So
there's
a
change
and
with
that
change,
I'm
rewarding
the
the
questions
and
and
that
that
was
the
extent
of
of
my
work
on
this
they're
doing
this
with.
B
Like
I
said,
I
think
we
talked
about
that
a
little
bit
before,
and
our
process
at
least
used
to
be
just
like
go
into
the
slack
for
that
Sig
and
ask
who
the
right
people
are
to
interview
and
it
always
ended
up
being
the
chairs.
But
there's
no
rule
that
it's
supposed
to
be.
The
chairs,
just
always
has
happened
to
me
so
yeah.
A
C
B
F
C
B
Nice,
rocking
and
rolling
these
can
take
a
while
so
good
that
you're
moving
along
awesome
so
make
sure
to
update
this
with
any
notes.
If
you
want
to
update
it
with
the
link
to
your
current
draft,
if
you
want
additional
feedback
on
that
or
just
update
it
with
the
pr
when
you
have
that,
let's
make
sure
to
do
that,
there's
also
six
CLI
Spotlight,
which
was
our
pits
our
picture
on.
B
Good
stuff,
wow,
moving
right
along
with
so
many
spotlights
right
now,
so
awesome,
it's
not
always
that
we
have
so
many
in
progress,
so
I'm
excited
to
see
it
at
all
use
cases
for
zapier
information
or
zapier
automation,
tracking
issue
for
zapier
automation
of
GitHub
to
Twitter.
So
this
is
related
to
the
stuff
that
we
talked
about
in
the
daily
notes.
B
But
they
were
doing
some
work
to
remove
some
of
the
old
issues
related
to
that
project
and
Imran.
Isn't
here,
I'm,
not
sure
if
we
need
to
move
that
to
done
or
if
there's
still
work
that
they
need
to
do
since
he
worded
it
as
add
all
use
cases
I'm
guessing,
there's
still
work
to
be
done.
What
did
you
describe
this
to
address
and
discuss
the
ongoing
effort
yeah
so
since
it's
ongoing
I
think
that's
where
it
should
be
cool,
so
I'll
move
into
to
Do's
I
assume.
C
C
D
B
So
there
is
work
available,
keep
cutting
you
tweet
planning!
Thank
you
so
much
sujay
for
getting
the
spreadsheet
in
order.
I
haven't
actually
fully
reviewed
it,
but
I
did
take
a
quick
look
at
it
and
it
looked
good
to
go
so
look
at
it
now.
So
what
sujay
did?
Thank
you
very
much.
It
was
quite
a
bit
of
work.
I
always
struggle
to
get
it
done
in
time.
B
Is
he
went
through
this
spreadsheet
and
added
in
the
time
slots
for
each
block,
so
what
we
usually
do
is
we
tweet
about
the
maintainer
track
blocks
happening
at
kubecon
as
they're
happening
to?
Let
folks
know
who
are
attending
the
conference
that
live
talks
are
about
to
be
happening
that
might
be
relevant
to
contributors
they're,
not
just
kubernetes
contributors.
B
The
maintainer
track
block
is
about
an
ecncf
maintainers
but
still
relevant
to
the
contributor
community,
so
so
Jay
went
in
and
put
in
the
times
that
those
blocks
are
happening
and
the
times
that
we
would
like
the
tweets
about
those
blocks
to
go
out.
I
also
did
a
draft
of
one
of
them,
so
you
can
see
an
example.
There
are
also
a
ton
of
examples
from
previous
years,
so
this
is
now
at
the
point
where
we
need
help.
B
B
Awesome
this
one,
it's
blue
cool,
so
if
you'd
like
to
help
out
with
those
that
is
where
that
is,
please
share
with
your
friends
if
folks
want
to
get
involved
with
contributing.
This
is
a
super
lightweight
task
where
you
just
need
to
look
at
the
schedule,
write
a
tweet's
worth
of
of
writing
and
add
it
in
here.
B
B
A
A
A
B
B
B
A
C
B
C
B
C
This
one,
what
you
need
to
know
this
one
is
the
one
that
I
added,
which
is
the
actual
PR
that
was
opened
right
for
the
change.
But
if,
before
this,
we
already
had
a
draft
there,
so
it's
I've
kept
both.
But
maybe
when
this
happens,
the
it's.
We
should
just
delete
the
the
draft
and
keep
the
this
one,
because
this
one
has
the
actual
information.
The
draft
is
just
a
placeholder.
C
B
D
D
B
Okay,
thanks
for
calling
that
out
promoting
the
new
contributor
Workshop
content
is
still
in
to
do,
because
we
are
still
waiting
on
GitHub
workspaces
to
be
worked
into
that
content
before
we
spread
it
around
widely
comms
guidelines
for
sensitive
security
topics.
It
might
be
a
good
time
to
pick
up
the
guidelines
for
sensitive
comms
type
of
work,
because
we're
gonna
probably
want
to
write
some
more
stuff
about
the
registry
change
and
what
we
learned
from
that
yeah
should
I
add
a
separate
one
for
that.
B
That
makes
sense
retrospective
on
registry
comms.
That's
something
that
we
want
to
do.
We
should
work
on
getting
that
together,
we'll
want
to
talk
with
contribex,
more
broadly,
because
so
many
folks
were
involved
with
that
about
setting
up
that
retro
I.
Think
cool,
so
I'll
leave
that
in
to
do
when
we
try
to
figure
out
how
we
would
set
that
up
and
naming
update
in
contributor
tweets,
I
think
this
is
okay,
and
this
one
went
in
like
a
while
ago
right.
B
B
B
A
B
B
B
B
B
B
B
Yeah
cool,
so
this
first
one
I
think
this
is
just
on
the
sidelines
de-prioritized
as
we're
working
on
the
zapier
stuff
yeah,
because
this
is
about
making
sure
that
we
know
when
there
are
issues
in
PRS
that
we
need
to
know
about,
on
GitHub
kind
of
on
the
back
burner,
blogging
process
updates
and
restarting
the
kanban
board
in
progress.
Thank
you.
Frederica.
B
B
B
A
A
A
B
A
B
B
B
A
D
A
A
B
D
D
B
B
All
right,
I've
noted
it
not
that
we'll
get
done,
because
I
did
that,
but
I
tried.
Thank
you.
Slackbot
issues
prioritized
below
zapier
updating
the
repo
with
role
descriptions.
This
is
good
for
now.
I
left
it
here
for
us
to
discuss,
but
since
we're
moving
to
the
board,
I
think
I'll
just
delete
this
and
we'll
do
it
ad
hoc
whenever
folks
feel
the
a
role
is
in
need
of
updates,
we'll
figure
that
out.
B
Oh,
this
was
a
note
for
Imran.
He
wanted
to
move
this
onto
the
board
and
Mark
as
I
won't
fix,
contributor
site
updates,
but
we
do
have
other
contributor
site
stuff
that
needs
updating
now
so
probably
need
some
stuff
on
the
board
for
the
contributor
site,
Hugo,
stuff,
migration
from
katakota
to
GitHub
code
spaces.