►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220603
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220603
A
Hello
and
welcome
everyone
to
the
friday
june
3rd
edition
of
the
upstream
marketing
contributor
comms
team,
we're
working
on
changing
the
name
to
totally
contribute
our
comms,
but
that's
not
done
yet.
So
this
is
our
first
meeting
back
after
kubecon
reminder
to
everyone
that
we
are
a
part
of
sig
contributor
experience,
which
is
part
of
the
kubernetes
project,
which
is
presidency
and
cf,
which
is
part
of
the
linux
foundation,
which
means
that
we
have
a
code
of
conduct
so
basically
be
excellent
to
each
other
and
be
respectful
of
your
fellow
participants
and
speakers.
A
A
B
Hey
so
I
am
right
now
hello,
I'm
kind
of
new
to
this
meeting,
so
hello,
everyone
I
am
jaish
I've
been.
I
am
currently
working
in
a
company
called
spectrocloud.
I
have
been
driving
the
meta
contributors
apec,
block
series.
I've
heard
for
some
time
now
yeah,
so
I
actually
made
a
draft
document
for
our
third
blog,
which
focuses
on
china
region
and
actually
I
wanted
a
review
on
that
and
I
have
posted
the
link
in
the
contravix
channel.
B
So
if
folks
can
review
it,
that
would
be
great
and
then
we
can
publish
the
blog.
A
A
A
The
only
thing
I
put
in
there
is
that
kubecon
is
done
yay,
it's
always
a
big
rush
leading
up
to
kubecon,
and
I
know
a
lot
of
folks
were
very
busy
beforehand
with
other
things
as
well,
but
we
did
get
the
tweets
done
just
barely
we
got
the
polls
scheduled
chris
and
I
had
intended
to
go
over
some
of
our
other
work
at
kubecon,
which
didn't
really
happen,
but
we'll
go
over
all
of
that
in
our
table
as
we
go
through
our
campaigns
in
progress
and
we'll
discuss
that.
A
Aside
from
that,
just
thank
you.
Everyone
for
your
work
on
cubecon.
I
still
need
to
send
out
a
thank
you
tweet
to
everyone
who
wrote
tweets.
I
apologize
for
not
doing
that.
Yet
it's
been,
there
was
kubecon.
A
A
So,
let's
start
going
through
our
campaigns
in
progress,
then
and
again,
new
item
is
the
contributor
blog.
So
if
you
have
a
chance,
definitely
make
sure
to
do
that.
I
guess
I'll
go
ahead
and
add
that
into
our
table
now,
because
I
like
our
table,
even
though
I
feel
like
I've
been
kind
of
bad
at
keeping
it
up
lately,
but
now
that
cubecon
is
done.
Hopefully
that
will
change.
A
Would
anyone
like
to
claim
that,
while
I'm
putting
it
into
the
the
table,
like
I
like
to
assign
people
to
things
if
they
think
that
they'll
be
able
to
do
it,
so
that
we
can
at
least
check
in
in
the
next
meeting
to
see
if
that
was
done,
if
they
need
help?
If
someone
else
needs
to
take
it
over
or
anything
like
that,
anyone
think
that
they're
going
to
get
through
you
reviewing
this
blog.
A
A
A
We've
been
working
on
trying
to
create
a
team
within
github
for
issues
to
be
assigned
to
so
that
we'll
all
get
alerted
when
we
actually
have
issues
that
we
need
to
look
at
in
github,
which
has
been
a
problem
because
we
have
a
couple
of
places
where
issues
could
be
created.
That
would
be
intended
for
our
team
and
we
have
to
like
go
and
manually
check
those
or
preferably,
and
what
actually
works
is
people
ping
us
on
slack
to
let
us
know
that
the
issues
are
there
and
then.
D
A
Take
care
of
them
so
we're
working
on
fixing
that
by
creating
a
team
and
hina
has
made
some
progress
on
that
she
finished
the
first
one,
the
last
time
that
we
had
a
meeting
which
I
could
delete
off
of
here,
but
I
think
I'm
gonna
leave
it
on,
because
it
is
a
prerequisite
to
the
next
one,
and
I
want
to
kind
of
keep
those
two
parts
of
this
thing
together.
A
F
Yes,
well,
I
can't
define,
but
it's
it's
been.
The
best
just
like
the
best
way
to
program
is
to
actually
do
some
program
here.
The
best
way
to
learn
is
to
actually
find
some
some
obstacles,
not
really
obstacles.
So
a
very
short
update
on
this.
So
the
initial
I
had
a
a
new
conversation
with
tim
bannister
around
some
of
the
concerns
that
he
had
as
mentioned
here.
It
was
nothing,
it
was
not
an
obstacle.
F
It
was
more
of
a
general
concern
on
some
edge
cases
that
can
emerge
eventually
and
that
specifically
reviewers
should
should
ask
contributors
in
those
specific
cases
to
manually
squash
their
commits,
but
this
is
like
a
a
relatively
rare
case,
so
I
went
forward
with
the
tweets.
As
you
know,
the
then
the
the
policy
around
not
linking
to
external
sites
popped
up
so
which.
F
The
issue
exactly
yes,
true,
if
that's
not
documented,
I
could
certainly
also
have
a
stab
at
edit
because
to
solve
this,
I
ended
up
proposing
a
change
to
the
to
the
community
pages
and
there
is
already
a
reference
about
these
methods
that
is
mentioned
in
the
tweets
on
the,
but
an
additional,
a
more
explicit
introduction
in
terms
of
the
actual
contributing
guide
is
not
a
bad
idea.
F
I
made
an
initial
suggestion:
tim
went
there
and
proposed
some
some
some
some
corrections
and
I've
already
accepted
and
squashed,
and
it's
there
now
it's
waiting
for
someone
else
to
go
there
and
review
it.
I
think
that's
if
I
understood
the
process
correctly,
someone
needs
to
do
to
to
do
the
okay
to
test
thing
there,
and
then
I
would
assign
to
paris
for
final
review.
A
Lovely
thank
you
we
did
actually
have.
I
was
trying
to
find
it.
We
did
have
some
guidelines
on
tweets.
A
It
looks
like
we
have
some
guidelines
on
emails,
which
is
cool,
didn't
realize
that
things
I
should
look
at
more
are
repo,
so
we
did
actually
have
some
guidance
on
that,
but
I
think
it
was
part
of
the
role
definition
of
the
social
media
lead
role,
which
we're
totally
reworking
our
concept
of
roles
right
now,
the
quick
overview
of
the
history
on
that
when
we
initially
started
out
as
a
team,
we
had
specific
roles
because
we
were
created
by
paris
and
she
came
up
with
what
she
thought
the
roles
would
be
over
the
next
like
two
years.
A
It
came
down
to
a
group
of
folks
who
were
generally
in
the
meetings,
and
we
just
kind
of
did
everything
so
the
roles
weren't
really
being
useful
and
they
weren't.
So
like
the
page
where
we
defined
our
roles
wasn't
really
defining
how
our
group
actually
worked.
A
So
we
changed
it
to
be
closer
to
how
our
group
was
actually
working,
and
then
we
got
a
lot
of
people
who
wanted
to
actually
do
roles
and
have
shadowing
and
every
all
these
awesome
wonderful
things
to
actually
keep
this
group
going
for
a
longer
period
of
time.
So
we're
now
in
the
process
of
undoing
those
changes
and
kind
of
redefining
what
role
should.
F
My
side,
if
I,
if
I
can
be
of
help
in
any
of
that,
I
should
surely
am
open
to
it.
Some
of
this
stuff
does
require
some
more
contextual
knowledge
of
what
exists
and
what
is
the
desired
outcome,
and
some
of
that
I
don't
actually
possess
right
now,
but
anyway
I
I
can
at
least
assist
on
some
of
the
stuff
being
done.
A
A
A
F
So
right
now
for
my
side,
I'm
on
waiting
mode,
because
I
think
that
I've
done.
I
think
that
cpr
needs
a
reviewer
to
do
it,
the
okay,
the
tests
and
then
I
would
do
the
assigned
to
paris.
That
is
my
expectation,
but
maybe
there's
a
practice
in
which
the
okay
test
is
not
needed,
and
I
can
just
assign
paris
to
it
right
now
that
that
is
something
that
I
would
love
to
to
hear
about.
Oh
yeah,
just
so
that
the
pr
isn't
there
with
no
one
doing
anything,
because
everyone
is
waiting
for
something.
A
Yes,
you
should
be
able
to
assign-
I
don't
seem
to
be
logged
in
right
now,
so
I'll
have
to
fix
that
you
should
be
able
to
do
slash,
assign
in
a
comment
slash
a
sign
in,
and
that
should
do
it
does
that
matter.
F
I
just
didn't
just
to
be
sure
I
just
didn't
do
it,
because
the
ever
helpful
kubernetes
ci
robot
told
me
that
first,
a
kubernetes
member
would
would
need
to
verify
the
patch.
If
so
they
should
reply
with
okay
to
test
and
and
only
after
that
would
I
assign
to
paris
pitman
for
review.
F
A
A
A
A
I
had
myself
on
that.
Thank
you
all
right.
We
should
move
on
to
the
next
thing,
which
I
don't
think
virgil
is
here,
and
I
don't
know
if
any
of
the
rest
of
you
will
have
updates
but
auto
generating
blog
tweets.
This
is
something
yeah.
This
is
something
we're
gonna
work
on
once
we
get
a
buffer
account
which
we
don't
have
yet
so
I'm
just
gonna
go
ahead
and
skip
that
unless
you
all
want
to
add
anything
in
there,
you
can
post
it
in
the
chat
or
something
interrupt,
feel
free.
A
This
is
just,
I
think,
the
yeah.
This
is
yeah.
A
This
is
the
automation
issue
that
we
have
with
our
github
repo,
where
we
currently
do
tweet
automation,
it's
really
nice,
because
anyone
can
submit
a
tweet
that
they
would
like
to
have
tweeted
from
kate's
contributors,
but
it's
unfortunate
because
we
can't
actually
schedule
those
when
those
tweets
go
out
right
now,
because
of
limitations
and
automation.
A
So
we're
trying
to
fix
that
by
getting
an
account
for
a
tool
called
buffer
same
thing,
same
fix
as
the
last
one.
So
we
should
be
getting
that
very
very
soon,
but
I
haven't
heard
anything
yet
so
I'm
gonna
move
on
from
that
role.
Description
avanesh!
You
had
some
updates
there.
I
believe.
D
Yep,
so
I
I've
shared
you
what
paris
did
shared
me
about
her
suggestions.
I
knew
that
you
were
some
you're
busy.
You
have
to
keep
going
so
I
didn't
wanted.
A
D
A
Yeah,
I
generally
think
it
looks
good
and
these
roles
are
not
set
in
stone.
Even
when
we
decide
on
definitions
for
them,
we
can
always
change
them,
so
we
shouldn't
treat
it
as
too
heavy
of
a
barrier,
so
it
looks
good
to
me
what
should
be
our
next
step
with
this.
Do
you
feel
like
this
is
something
you
would
be
ready
to
go
ahead
and
put
on
the
page?
A
D
I
I
can
go
for
the
pr,
but
I
think
it
would
be
much
more
better
if
someone
helped
me
in
writing
it
in
a
proper
way.
Okay,.
A
A
Sounds
good,
hopefully,
that'll
kick
off
a
wave
of
new
role
descriptions
for
us.
This
is
something
we've
been
talking
about
for
several
meetings
for
anyone.
Who's
new
is
defining
these
new
roles
and
getting
shadow
processes
worked
out
and
kind
of
figuring
out
the
processes
so
that
everyone
can
learn
and
grow
and
own
things
here.
A
So
this
is
part
of
that
process.
We'll
get
there
so
I'll
move
on
to
the
next
thing,
tweet
about
feature
blogs
that
will
come
out.
We've
still
got
work
to
do
there.
Oh
boy,
are
we
probably
behind?
A
So
there
was
a
thread
in
the
contributor
experience
slack
right
before
kubecon,
where
the
pr
lead
of
the
last
release
sent
us
all
of
the
feature,
blogs
that
were
expected
and
their
dates.
But
the
issue
with
it
was
that
we
didn't
have
the
public
links.
You
can
get
them
from
the
pr's
which
we
had,
but
it
was
kind
of
a
process
to
go
in
and
find
what
the
public
links
were
going
to
be
for
each
one
and
it
was
kubecon.
So
we
didn't
have
time
to
do
that.
A
So
there
are
still
some
feature
blogs
that
are
probably
out
now
that
we
haven't
tweeted
about,
and
I
have
assigned
myself
to
that.
Thank
you.
Past
caslin.
A
So
what
needs
to
happen
here
right
now
is
someone
which
is
probably
me
since
I've
assigned
myself
to
it
needs
to
go
through
the
list
of
the
feature
blogs
that
we
had
from
before
see
which
ones
we've
tweeted
about
and
figure
out
which
ones
we
haven't
tweeted
about
and
just
get
tweets
going
on
the
rest
of
those.
I
think
there
might
still
be
a
couple
that
haven't
gone
out
yet,
or
did
they
finish
up
by?
A
May
I'm
not
sure
if
there
are
a
couple
that
haven't
gone
out
yet
then
kind
of
watch
for
those
and
make
sure
that
we
tweet
about
them.
If
you
see
them.
A
A
We
did
do
the
special
history
of
docker,
shim
blog
and
the
release
blog.
We
did
tweet
about
those
two,
I
think,
and
then
we
did
tweet
about
several
of
the
feature
blogs,
but
there
were
several
of
them,
which
is
not
fully
reflected
here.
I'll
just
remove
this
part
because
we've
kind
of
finished
all
those.
A
And
I'll
on
review
repo
look
into
adding
descriptions
of
various
roles
chris
and
I
were
going
to
do
that
at
cubecon,
but
it
ended
up
taking
us,
basically
the
entire
contributor
summit,
to
get
all
of
the
the
rest
of
the
tweets
scheduled.
I
really
should
have
done
that
before
I
got
to
cubeca
notes
for
the
future.
A
Well,
in
the
future,
this
won't
be
a
problem
because
we
will
hopefully
have
buffer,
which
will
allow
us
to
actually
schedule
the
tweets,
so
it
won't
just
be
on
one
of
the
folks,
with
the
keys
to
the
the
twitter
account
to
do
all
of
that
scheduling,
we'll
be
able
to
work
together
to
do
it
in
the
future,
which
will
be
very
nice
yeah.
So
this
roles
thing
is
still
open,
as
we
mentioned
everyone's
experiences
factor
into
it,
and
your
feedback
is
always
welcome.
A
A
So
I'm
gonna
go
ahead
and
just
remove
that
row
because
it
is
done
technically.
I
do
still
have
one
thing
to
do
there,
which
is
the
thank
you
tweet,
because
I
keep
mentioning
it
because
I
want
to
make
sure
that
I
do
it,
but
I'm
just
gonna
do
that
after
this,
so
I'm
not
gonna
even
bother
putting
it
on
the
table.
A
Next
thing
update,
github
repo
to
contribute
your
comms
name.
There
is
an
issue
out
for
that.
A
Well,
there
is
an
issue
out,
though,
for
the
the
name
change.
I
need
to
make
sure
that
I
get
the
proper
link
for
that
from
chris,
so
I'll.
Try
to
update
that
these
got
created
this
one
and
one
other
related.
One
got
created
right
before
kubecon,
so
they've
kind
of
just
been
sitting
around
for
the
last
couple
of
weeks,
but
chris
and
I
talked
about
them
briefly
this
week
and
we'll
make
sure
that
they
get
going
again
like
put
this
buffer.
A
Thing
up
here
into
the
two
issues
that
are
solved
by
buffer
and
remove
it
from
here
cool
next
thing:
new
sig,
doc,
sig,
spotlight
furnace
laura
wanted
to
do
an
interview
of
sig
docs,
which
will
be
ray.
E
Yeah
I
I
would
like
to
get
get
the
co-chairs
also
yeah.
D
E
Can
set
up
a
time
next.
E
A
A
E
A
A
There
you
are
yes,
I
was
like
it's
one
of
the
folks
who's
like
regularly
here.
I
think
so.
I'll
put
your
name
into
this
as
well.
Let's
have
a
dm
conversation
after
this
or
at
your
convenience
sometime
soon
and
I'll,
make
sure
that
you
have
all
the
resources
for
these
blog
posts
and
we'll
get
you
started.
A
And
then
you
write
a
blog
post
about
what
you
learned
from
the
interview.
We
have
a
few
examples
of
cases
where
folks
from
this
group
have
created
those
in
the
past.
We
have
a
few
resources,
like
example,
questions
that
you
can
use
and
talking
to
the
chairs,
we
recommend
doing
it
asynchronously
over
a
google
doc.
All
of
these
kind
of
high
level
points
I
can
guide
you
through.
A
If
you
want
to
do
one
just
reach
out
to
me,
I
think
I
will
are
there
any
sigs
that
are
still
missing
from
the
from
the
list.
No
just
cycling
around
a
lot.
F
Be
something
something
interesting
because
speaking
with
people
about
sex
is
an
excellent
way
to
actually
not
only
learn,
but
it's
it's
something
that
I
I
would
like
to
do.
So
I
will
ping
you
on
this.
F
A
Of
track,
but
all
these
folks
are
interested
working
on
it.
Anyone
else
at
any
time
feel
free
to
ping
me
and
I'll
get.
You
started
on
this
stuff
cool
and
there
was
a
request
for
a
review
of
the
karakota
by
harshita
yeah
frederico.
You
had
volunteered
to
try
that
out.
Yes,.
F
I
I
did,
and
so
I
haven't
replied
directly,
replied
to
a
architect
yet,
even
because
I
wanted
to
sync
with
avinesh
first,
so
two
two
points
here,
one
I
did
an
initial
review
on
it.
I
have
a
couple
of
comments
about
it.
Specifically,
I
I
liked
it
I
think,
for
me
it
would
be
super
useful
if
it's,
if
you
could
go
over
a
specific
example
of
like
a
mock
contribution,
just
to
see
that
part
of
the
process.
F
But
I
will
I
will
go
to
apologies
for
the
for
the
sound
because
it's
something
is
happening
in
the
street,
but
so
I
will
share
those
notes
in
perhaps
in
the
in
the
slack
channel,
for
example,
and
at
avinash
as
well,
but
there's
another
a
more
structural
change
that
I
I
mentioned
in
this
in
the
that
was
mentioned
in
our
in
our
slack
channel,
which
is
katakana
itself,
is
going
to
to
be
to
disappear
in
terms
of
an
open
platform.
F
So
it's
going
to
be
really
learning
internal,
and
so
I
think
that's
the
my
comments
and
avinash
comments
would
still
apply
in
principle
and
in
concepts,
but
the
actual
playgrounds
thing
will
have
to
be
done
elsewhere
because
katakana,
I
think
it's
one
month
from
being
closed.
E
So
the
the
catego-
we
very
also
we
use
kataka
a
lot
around
kubernetes
dot,
io,
so
they've
reached
out
the
maintainers
of
catacota
they
reached
out
and
said
that
they
actually
put
this
all
the
things
for
kubernetes
dot,
io
on
a
separate
server,
so
that
the
stuff
on
kubernetes.io
that
uses
katakoda
will
still
remain
oops
still
and
deba
asked
for
a
specific
one
as
well.
I
think
it's
the
one
that
that
contrabex
uses,
if
that
is
included
as
well.
I
haven't
heard
a
reply
about
that.
E
So
there's
a
possibility
that
okay,
that
that
catacota
will
still
be
available
for
our
for
for
contrabex
use
and
the
date
is
going
to
close
down
as
june
15th.
So
it's
actually
like
13
days.
E
E
Excuse
me
yeah,
so,
but
but
hopefully
it
the
the
one
for
for
this
and
for
for
country
backs,
will
still
will
still
be
alive
after
june
15.
A
A
I
will
and
often
and.
F
D
I
I
did
initial
reviews
for
her
work
and
I
also
give
the
give
the
feedback,
so
something
strange
was
happening.
Actually
that
catacorta
was
not
reflecting
the
changes
done
in
the
pr.
Oh,
so
I
really
don't
know
what
issue
it
was.
I
I
informed
deva
as
well
about
the
issue
and-
and
I
think
he's
quite
busy
seems
to
be-
is
there
a
pr
for
this
yep?
We
do
have
a
pr
for
this
I'll
share.
You
I'll
share
the
ring.
D
F
D
A
D
A
Oh
hey,
that
was
a
thing
that
happened
yay
way
to
go
ray,
so
our
next
item
is
tweeting
about
the
upcoming
release,
webinar,
which
is
not
upcoming
anymore.
It's
already
happened
thanks
to
ray
who
created
the
the
issue
for
that
and
chris
went
ahead
and
approved
it.
So
we've
already
done
a
tweet
on
that
claps
I'll
go
ahead
and
remove
that
item
from
the
table.
A
Deleter
there
we
go
next
thing:
marketing
team
to
contributor,
com's,
name,
github,
repo
to
contributor
com's,
name
marketing
team
to
contribute
a
commons
rename.
This
is
it's
the
same.
I'm
gonna
merge
these
into
one
cell.
There's
something
slightly
different
about
these
two.
I
think
so
we're
working
on
updating
the
github
repo
to
the
contributor
comms
name
instead
of
upstream
marketing,
which
means
that
we
need
to
change
it
in
several
places.
So
chris
was
working
on
some
automation
to
go
through
and
find
all
those
places
where
it
needs
to
change
and
doing
that.
A
A
A
A
I
guess
we'll
grab
that
link
and
put
it
in
here
yeah.
It
is
now
live,
so
this
is
a
really
big
deal
for
the
community
and
it's
something
that
we'll
want
to
make
sure
that
we're
promoting
we'll,
probably
want
to
break
out
a
few
pieces
of
it
and
create
additional
tweets,
which
we
can
try
to
work
out
now
or
we
can
hold
for
a
little
bit
later.
I
guess,
but
basically
the
annual
report
goes
through
a
lot
of
what
the
kubernetes
community
is
doing
and
what
we
are
and
how
we
do
what
we
do.
A
I
guess
there's
a
lot
of
detail
in
it
and
a
lot
of
it
is
really
useful
for
contributors
to
see
because,
for
example,
one
thing
that
we
really
want
to
point
out
is
the
help
wanted
section
which
we
do
in
this
tweet,
because
each
sig
has
things
that
they
want
to
do
or
that
they're
working
on
and
they
need
some
help
with,
especially
from
people
with
specific
skills.
A
A
And
there's
also
accolades
for
folks
who
did
really
awesome
stuff
over
the
last
year
and
themes
which
I
don't
even
know
what
that
means,
but
I
guess
I'll
look
at
it
later
and
find
out.
So
this
is
a
big
deal
and
we've
got
a
tweet
out
on
it,
which
is
wonderful,
like
I
said
we
might
want
to
do
a
couple
more.
A
A
Cool,
so
the
question
is:
what
else
do
we
want
to
tweet
about
or
promote
or
do
with?
The
annual
report,
like
I
mentioned,
the
help
wanted
section
is
really
important,
and
the
annual
report
folks,
like
paris,
would
probably
particularly
appreciate
another
tweet
or
two
at
least
about
the
help
wanted
section,
so
we
could
go
ahead
and
create
some
drafts
for
those
and
just
put
them
in
the
contributor
tweets
repo.
For
now,
I
can't
wait
until
we
get
buffer.
I
hope
that
will
be
very
soon.
A
Thank
you
and
anyone
else
want
to
volunteer
for
that
or
to
that's.
The
other
thing
that
I
would
ask
people
to
do
is
just
kind
of
skim
through
the
annual
report
and
let
the
group
know
with
an
at
message
on
slack,
if
you
see
anything
that
you
think
you'd
particularly
like
to
see
promoted
from
it.
F
A
E
Amping
up
kubernetes
security.
How
now
we
generate
s-bombs
and
compliance
with
salsa
sauce
to
level
three
artifact
signing
all
the
things
about
having
a
more
secure
soft
software
supply
chain.
That
section
comes
up
to
mind
some
some
of
the
enhancements
that
have
gone
to
ga,
but
I
kind
of
like
the
the
amping
up
too
many
security.
A
E
Wanted
there's
no
there's
a
good
number
of
six.
Each
help
wanted
for
each
sig
could
be
its
own
tweet
yeah.
E
A
A
We'll
see
what
we
can
do
before
next
week
and
whatever
we
haven't
gotten
done
we'll
come
back
to
you
sounds
good.
Anybody
want
to
clean
the
s-bomb
security
section
of
the
annual
report.
Tweet.
D
A
A
New
ga
stuff,
I
won't
really
worry
about
I'll,
try
and
do
that
if
I
can,
because
I
want
to
skim
through
it
anyway,
and
I
think
we
don't
need
to
assign
anyone
to
the
the
skimming
really
just
if
you
do.
Oh,
we
already
did
the
frederico.
A
Cool
and
guess.
A
B
B
Can
you
please
tell
me,
tell
me
what
happened
actually,
because
the
table
and
stuff.
A
Yeah,
I'm
a
big
fan
of
it
personally,
so
that's
a
big
reason
why
we're
using
it
but
anyway,
so
a
couple
months
ago,
I
guess
we
were
discussing
the
need
for
kind
of
more
project
management,
of
all
the
work
that
we
have
going
on
in
here,
and
we
were
discussing
some
of
the
issues
with
the
tools
that
we
had
at
the
time
for
tracking
this
kind
of
work.
We
would
talk
about
it
in
the
notes.
I
started
doing
this
thing
where
I
would
bold
people's
names
with
action
items
and
that
kind
of
helped.
A
A
So
hina
was
a
new
person
who
joined
our
group
and
started
coming
to
our
meetings,
who
had
some
project
management
experience
and
she
recommended
that
we
try
using
this
table.
So
we
added
the
table
to
the
notes
that
was
hina.
Thank
you
so
much
tina
for
creating
the
table
and
what
we've
been
doing
with
it
is
what
you
were
just
seeing.
Is
we
put
all
of
our
active
tasks
into
the
table?
A
Obviously
I
like
to
assign
people
to
them.
If
we
can
and
then
the
next
week
we'll
go
over
them
and
see
what
was
completed
and
removed
them
from
the
table,
so
it's
a
way
that
we're
tracking
our
active
work
now
and
I've
really
been
liking
it.
Aside
from
that,
I
moved
around
a
couple
of
things
in
the
regular
day-to-day
notes,
just
to
make
sure
that
we
have
kind
of
a
flow
to
our
meetings.
We
go
through
updates,
big
wins
new
items
and
then
we
just
go
through
the
table.
A
We
used
to
have
this
section
where
we
do
the
the
working
session
items
where
we
go
through
a
calendar
walk
to
look
for
email
announcements
that
we
should
be
sending
out.
Look
at
draft
prs,
which
we
can
always
do,
and
then
we
try
to
go
through
like
that
that
task
board,
but
we
kind
of
don't
really
need
to
do
that
anymore
with
the
table,
which
is
nice
yeah.
Those
are
the
updates
that
I
can
think
of.
Does
that
make
sense.
B
Yeah,
that
sounds
good.
I
had
one
more
question
like:
is
there
any
updates
regarding
the
youtube
automation
stuff
like?
Are
we
still
going
to
use
plane
or
like
previously?
I
remember
me
and
nigel
were
working
on
that,
but
I
had
to
drop
off
because
of
some
personal
reason
so
yeah.
I
just
wanted
to
check
on
that.
B
Okay,
there
was
also
pr
which
I
ljpm.
Actually
he
was
adding
himself
back
to
the
youtube
and
zoom
admins.
D
Yes,
and
also
there
was
a
discussion
in
said,
contrabex
meet.
I
guess
I
don't
remember
when,
but
I
think
laura
along
with
someone
was
working
on
some
tool,
I'm
really
not
sure
which
which
tool,
but
there
was
some
update
where
paris
and
laura
they
were
discussing
about
a
new
tool
which
laura
and
some
some
person
was
working
on
it.
So
yeah,
that's
all.
I
remember
from
the
automation
part.
A
A
A
A
I
think
I
saw
at
least
one
other
new
person
joined
at
the
beginning
of
the
meeting.
We
offered
an
opportunity
for
any
new
folks
to
introduce
themselves
and
tell
us
about
why
you're
here
what
you'd
like
to
get
out
of
being
here,
I
guess
it's
a
good
way
to
say
it
so
new
folks.
If
you
would
like
to
type
in
now
and
introduce
yourself
you
are
welcome,
but
it
is
optional.
A
Cool,
so
with
that,
we've
got
five
minutes
left
any
other
last
minute,
discussion,
items
or
things
that
folks
want
to
discuss
before
I
close
the
recording.
D
A
Yeah,
so
we
talked
about
that
a
little
bit
there
was
that
issue
which
atarva
posted
I'll
grab
that
again.
A
If
I
do
this,
it's
gonna
open
it
isn't
it.
No,
it
doesn't
nice
okay,
so
I
just
posted
in
the
chat
yeah
renaming
the
marketing
team
petition
also
just
asked.
So
this
is
the
issue
I
think
yeah
renaming
marketing
team
to
contributor
comms
impact
survey.
A
A
So
this
issue
is
just
kind
of
to
make
sure
that
this
is
going
to
be
okay,
make
sure
that
nobody
has
any
issues
with
us
doing
that
it
doesn't
have
a
whole
lot
of
yeah.
So
this
is
in
the
same
issue.
The
thing
I
was
mentioning
earlier:
the
automation
to
figure
out
where
we
actually
reference
the
repo
name
and
would
have
to
change.
It
is
also
included
in
this
issue,
which
is
nice.
A
A
So
I'll
put
it
in
the
chat
yeah
too
many
things
have
been
going
on
the
last
few
months
right.
I
agree
with
that,
but
we've
been
getting
so
much
done.
It's
been
wonderful,
anything
that
we
don't
get
done
either
comes
back
or
goes
away.
That's
my
philosophy,
but
I
put
in
the
link
here
that
would
be
changing.
A
So
you
see
it's
github.com
kubernetes
community
tree
master
communication
marketing
team,
so
that
last
bit
of
that
link
would
change
to
what
did
we
say:
contributor,
comms?
Yes,
contributor.coms
we
were
going
to
have
a
separate
channel
as
well.
On
slack,
I
remember
yes,
that
was
the
other
thing
which
I
should
totally
put
a
row
in
the
table
about
or
something
I
will
do
that
add
a
new
row
below
yes.
So
this
is
something
I
mentioned
also
briefly
with
chris
this
week.
I
think
didn't
we
talk
about
that.
A
Maybe
we
didn't,
because
I
kind
of
mix
it
up
with
this
repo
name
change
in
my
head,
but
yes,
separate
from
that.
We
do
want
to
create
a
new
slack
channel
specifically
for
this
group.
B
If
I
remember
correctly,
I
think,
like
contributor
forms
is
a
sub
project
of
contributor
experience.
Yep.
A
Exactly
so,
what
we
have
been
doing
is
just
using
the
contributor
experience
channel
in
slack
and
then
adding
contributor
comms,
but
there
were
a
couple
of
cases
right
before
cubecon,
especially
with
creating
the
tweets
for
kubecon,
where
there
was
a
lot
of
discussion
that
needed
to
happen.
So
I
ended
up
creating
separate
direct
messages
to
the
people
who
were
working
on
that
project
and
the
issue
with
that
was
that
I
couldn't
add
people
to
those
direct
messages
without
completely
recreating
the
room.
A
So
all
the
messages
from
before
would
be
removed.
When
I
added
a
new
person
who
I
wanted
to
send
those
initial
messages
to
and
connect
with
everyone
else,
so
there
are
some
use
cases
like
that,
where
we
thought
it
would
be
useful
for
our
sub
project
to
have
its
own
consistent,
always
available
room
within
slack
channel
within
slack.
B
Also
video,
I
also
saw
that
video,
where
you
and
chris
were
feeling
about
contributor
comments
during
cubeco.
How.
B
It
was
great
okay,
actually
like
how
many
takes
how
many
takes
did
it
take.
A
The
first
take
was
fantastic,
of
course,
the
camera
wasn't
on
for
that
take
so
you
didn't
get
to
see
that
one.
So
then
it
took
two
more
takes
after
that.
So
three.
A
A
But
yes
also,
I
should
grab
that
link.
I
think
chris
sent
it
to
me,
so
I
should
be
able
to
find
it
pretty
quickly.
It's
already
nine
so
feel
free
to
drop
off
if
you
would
like
to.