►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220722
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220722
A
Hello
and
welcome
everyone
to
the
friday
july
22nd
edition
of
the
contributor
comms
team.
We
are
a
subproject
of
sig
contribex,
which
is
part
of
kubernetes,
etc,
etc,
and
that
means
that
we
have
a
code
of
conduct
that
we
abide
by.
It
essentially
means
be
excellent
to
each
other,
be
respectful
of
your
fellow
speakers
and
attendees
of
the
meeting
and
that's
pretty
much
it.
A
So,
let's
go
ahead
and
hop
into
our
schedule
for
today,
I'll
start
off
underneath
the
table
in
our
notes,
doc,
with
our
notes
not
that
we
use
them
that
much
anymore,
but
any
updates
big
wins
that
anyone
wants
to
shout
out
today.
We'll
start
there.
A
A
A
Into
our
our
format,
somehow
note
that
we
go
to
the
table
at
that
point:
alrighty
up
at
the
top
of
the
table
is
hina
as
usual,
so
hina
we
made
a
little
bit
of
progress
last
time.
I
think,
in
figuring
out
where
to
ask
for
suggestions
on
other
ways
that
we
could
alert
the
team
when
a
new
github
issue
is
filed,
that
we
need
to
pay
attention
to
currently
well.
A
A
A
We're
talking
about
hina's
work
on
making
sure
that
we
get
alerted
when
a
new
issue
is
filed,
that
we
need
to
pay
attention
to.
She
said
that
you
gave
her
a
great
tip
and
it.
C
Yeah,
so
the
I'm
not
sure.
If
that
I
mean
we
need
to
test
the
the
original
idea,
which
was
the
template
one,
but
if
that
doesn't
work,
what
we
can
do
is
we
can
we
can?
We
can
ask
folks
who
are
creating
the
issue
to
add
labels
to
it
and
in
response
to
that
labels
we
can
tag
the
entire
group
so
that
we
are
notified.
So
we
can
get
notified
that
way
as
well
yeah
that.
A
Sounds
like
a
good
idea,
I
think,
generally,
I
know
when
I
create
a
new
issue
in
any
repo,
I'm
always
like
what
labels
do.
I
need
to
be
adding
to
this,
so
I
try
to
find
other
example
issues
to
to
do
that
based
on,
but
if
we
told
people
I
think
that
would
be
really
helpful,
so
maybe
that's
just
something
we
should
do
in
general,
good
suggestion.
Thank
you.
A
All
right,
so
it
sounds
like
that's
in
progress
for
now
we're
just
gonna,
wait
and
see
how
this
goes
for
a
couple
weeks.
Maybe
you
think
about
this
other
idea.
Maybe
we
should
do
both
honestly,
it's
kind
of
what
I'm
thinking
granted
hina
is
going
to
be
up
for
a
couple
weeks
yeah.
I
I
think
it
would
be
cool
to
do
both.
A
A
Alrighty,
so
we'll
move
on
from
that
one
next,
one
contributor
tip
tweet.
Are
we
gonna
do
something
specific
about
this?
We
were
working
with
chris's
article
and
getting
that
going
on
the
dev
site.
He
said
that
we
were
up
for
us
taking
over
that,
but
I
don't
think
we
started
doing
that.
Did
we
frederico.
D
D
Then,
if
maybe
there
was
some
action
on
my
part
in
that,
I
honestly
if
there
was,
I
didn't
capture
that
I,
because
I
think
that
the
the
the
the
thing
that
needs
to
be
done
is
to
cover
the
the
suggestions
and
the
reviews
that
exists
in
in
the
in
the
in
the
pr
from
from
chris
and
move
it
from
there.
So
what
would
you
think
would
be
the
next
step
for
us
to
take
over
that
open
a
new
one,
because
I
don't
think
that
we
can
actually
make
changes
to
that
right.
A
D
No
perfect
yeah,
I
just
need
to
have
things
clearer.
So
yes,
so
put
that
on
my
on
my
tab
and
I
will
I
will
create
a
pr
hopefully,
while
mentioning
the
other
one
and
incorporating
some
of
the
changes
that
are
there
to
the
best
of
my
ability.
Right,
because
some
of
the
comments
and
some
of
the
things
that
are
mentioned,
I
I
will
likely
need
some
additional
assistance.
But
for
that
I
will
talk
with
you
and
and
cruise
as
well.
A
A
Alrighty
next
item
are
the
two
buffer
ones,
so
there
was
progress
on
that
this
week.
I
think
I
mentioned
last
week.
I
was
running
an
event
in
seattle
this
week,
so
I
was
kind
of
out
of
it
for
basically
the
whole
week
outside
of
monday.
Well,
it
was
still
out
monday
afternoon
so
basically
the
whole
week
I
was
out
and
about,
but
I
did
see
some
movement
on
the
buffer
thing.
I
think
in
the
contrabex
channel.
Anybody
else
see
that.
C
A
I
need
to
check
in
with
bob
on
that,
so
how
do
I
want
to
do
this?
I
think
I'll
actually
like
grab
these
two
items.
A
A
I
think
we
have
approval
from
the
cncf.
Now
we
have
someone
to
give
us
the
funding
to
get
the
account
he
was
asking.
I
think,
if
we,
if
there
was
an
account
that
they
wanted,
that
they
were
supposed
to
add
the
billing
to
which
it's
not
like,
we've
created
an
account
already
for
them
to
do
that
too.
So
I
need
to
work
with
bob
to
figure
out
what
to
do.
There.
C
A
Okay,
well,
I
didn't
combine
them,
but
I
did
make
them
smaller.
That's
where
we're
at
past
me.
I
had
a
comment
on
the
notes
to
do
that.
All
right!
Next
item,
roll
description,
avanesh,
I
know-
there's
been
an
update
there.
C
Yep,
so
I
I've
shared
my
draft
and
looking
forward
for
some
feedbacks.
I
think
paris
did
said
something
she.
A
All
right
next
item
review
repo
look
into
adding
a
description
of
this
is
just
the
more
general
roles
thing
which
is
also
funny.
I
should
split
that
out
atarva
I
do
have
something
to
work
with
you
on
that.
I
keep
not
pinging
you
about.
I'm
really
sorry
about
that,
but
I'm
glad
you're
here
today,
yeah
yeah,
so
you
had
this
idea
of
like
this
approver
role
and
we've
been
trying
to
kind
of
work
out.
A
What
that
should
look
like
it
might
have
some
overlap
with
some
of
the
other
roles,
because
I
have
a
hack
md
out
and
now
I
need
to
put
the
hack
empty
over
here.
I
really
need
to
just
I'm
just
going
to
move
all
of
this
to
this
one
and
delete
this
line.
A
Sorry,
okay
anyway,
so
I
have
a
hackmd
out
for
the
social
media
coordinator
role
and
the
social
media
coordinator
would
include
ownership
of
the
contributor
tweets
repo
specifically,
but
I
think,
there's
probably
more,
that
goes
into
this
approver
role
that
you
were
thinking
about,
for
example,
approving
tweets
to
our
team
repo
kind
of
general
ownership
responsibilities,
particularly
as
it
pertains
to
github,
but
maybe
beyond
that,
maybe
like
running
this
meeting,
so
that
could
be
more
like
a
kind
of
general
leadership
role.
What
do
you
think
guitar.
B
Yeah,
I
was
thinking
more
the
first
time
I
approached
you.
I
was
thinking
of
more
like
getting
in
approval
ship
getting
in
an
approval
ship
for
the.
B
A
Yeah
we've
got
to
come
up
with
a
definition
of
what
the
role
would
be,
though,
if
you
want
just
like
the
the
tweet
approval
thing
and
like
to
to
manage
the
tweet
process,
that
would
I
think
that
would
follow
under
this
social
media
coordinator
role.
I
brought
this
back.
A
That's
why
it
exists
by
the
way
is
I
I
actually
submitted
a
pr
for
this
like
a
year
ago
or
something
and
I
totally
messed
up
submitting
the
pr,
because
I'm
really
bad
at
git
and
so
and
then
our
group
decided
that
we
wanted
to
go
to
this
leadership
council
thing
because
we
had
been
shrinking
and
now
we
are
not
shrinking.
So
so
I
brought
that
pr
back
as
a
hack
md,
and
so
that's
why
this
kind
of
happened
so
take
a
look
at
that
hackmd.
B
No,
I
I
was
just
you
said
about
more
nuanced
role
about
hosting
a
meeting
or
just
more
than
what
approving
a
tweet
for
the
github.
I
want
what
was
that
all
about?
I
wanted
to
know
more
about
it.
A
Right
so
you
had
mentioned
this
role
of
approving
tweets
and
I
kind
of
I
wrote
that
in
the
notes
as
approver
and
that
that
role
idea
came
from
you,
then
I
revived
the
social
media
thing
and
we
realized
that
approving
the
tweets
specifically
is
kind
of
part
of
the
social
media
role.
But
I
thought
this
approver
role
could
mean
more
than
what
you
originally
intended.
So
I
was
thinking
we
might
generalize
it
into
something
a
little
bit
different
from
what
you're
originally
thinking,
and
I
wanted
to
get
your
feedback
on.
B
You
know
what
we
can
just
create
two
different
roles
for
this,
then
right,
one
for
the
social
media,
coordinator
role
and
the
other
for
a
superior
type,
approver
thing
where.
A
B
Would
he
or
she
or
they
would
just
shadow
on
working
with
the
hosting
meeting
or
anything,
beyond
that?
A
Cool,
so
if
you
want
to
be
involved
in
creating
that
other
role
definition,
we
can
sync
asynchronously
on
slack,
and
I
should
just
go
ahead
and
ping
you
about
that,
whether
we're
going
to
or
not
because
it
will
start
the
conversation
if
we
want
it.
C
B
A
B
In
the
context
of
leadership,
we
have
very
what
we
can
say
experience
contributors
out
here
we
have
a
village,
we
have
frederick.
We
have
also
many
other
people,
so
we
can
just
create
these
rules
and
give
them
a
particular
batch
around
them
so
that
they
also
feel
some
kind
of.
C
B
A
B
A
C
D
It
was
yeah,
we
were
discussing
the
spotlight
stuff
and
the
process
of
writing,
blogs,
etc,
and
I
think
that
it
was
chris
that
that
said
well.
That
actually
might
be
interesting,
interesting
to
document
in
terms
of
a
role,
so
content
creation,
interviews,
etc.
Just
an
idea
because
it
was
suggested
back
then-
and
I
do
need
a
place
to
put
some
ideas-
that
I've
been
playing
with
and
some
lessons
learned
of
from
the
process.
D
A
A
Yeah,
it
was
basically
like
a
content
creator
role,
but
I
think
what
you're
talking
about
might
be
a
little
bit
deeper
than
that,
because
there's
considerations
around
collaboration
with
the
blogging
team
like
right
now
we're
trying
to
track
the
changes
that
they're
making
to
their
process.
A
So
someone
who
could
track
that
and
kind
of,
let
us
know
when
there
are
outside,
like
blogs
that
have
been
written
outside
of
our
group.
That
might
need
our
help
with
review
or
something
like
that.
Someone
to
coordinate
that
would
be
really
awesome
to
have,
and
I
think
that's
a
little
bit
beyond
the
storyteller
yeah.
A
B
A
Kdev
one
thing
we
mentioned
was
that
we
might
want
someone
to
kind
of
own
kdev
stuff,
which
currently
chris,
is
like
the
only
person
who
really
understands
that,
so
we'll
have
to
work
with
him
to
figure
out
how
we
can
shadow
and
define
that
role.
Development.
A
And
then
we
also
mentioned
a
developer
role,
because
we
know
a
number
of
members
of
the
team
would
really
like
more
hands-on
coding
technical
stuff,
and
we
just
haven't
had
the
leadership
to
help
people
get
familiar
with
those
types
of
tasks.
But
if
we
could
develop
that
internally
and
create
a
role
for
it,
that
would
probably
be
really
good.
B
So
just
a
general
question,
our
subproject
contributor
comms
marketing
thing,
which
are
the
other
repositories
that
that
have
apart
from
golang
code
base,
if
you
understand
so
we
have
the
contributor
to
its
repository
right
right.
Apart
from
that,
what
else
do
we
have
under
us.
A
Yeah,
I
think
we'll
keep
that
in
later
role
for
now,
so
I
started
a
list
here.
A
A
B
B
Mainly
looking
forward
was
the
same
thing
about
getting
approvalship
getting
the
ownership
of
the
contributors
to
it
thing
the
first
method
I
texted
you
was
about
getting
ownership
for
the
contributors
to
it.
So
where
do
this
road
get
into
it?
Will
it
get
into
the
social
media,
contribute
coordinator
role
or
the
approver
coordinator
rule
approval
rule.
A
That
would
be
primarily
the
social
media.
So
let
me
write
that
as
a
note.
As
I
say,
it
so
manages
tweets
repo,
but
I
think
should
the
leader
roll.
B
A
C
A
Whereas
with
this
approver
leader
type
role,
you
would
be
a
collaborator
with
any
changes
to
any
repos
that
our
group
owns,
so
you
could
be
an
alternate
approver
on
the
tweets
repo,
because
we
need
that
to
not
just
be
one
person
right
and
possibly
also
on
the
k,
dev
and
definitely
on
our
team
repo.
A
A
A
A
Working
with
storytellers,
which
basically
anyone
in
this
group
has
has
the
storyteller
role
by
default,
is
kind
of
the
concept
of
that
role.
Because
it's
like
a
content,
creator
role,
you
can
write
blogs,
you
can
write
tweets.
So
basically
everyone
is
that,
but
there
are
some
additional
notes
in
our
handbooks
about
the
storyteller
role,
for
example
in
the
social
media
coordinator.
I
also
include
any
like
storytellers,
who
particularly
want
to
focus
on
creating
tweets.
A
I
include
some
information
for
them
there
like,
where
to
find
our
social
media
guidelines
on
creating
tweets
and
stuff.
That's
also
in
the
social
media
coordinator
role,
handbook.
A
Alrighty,
there's
a
lot
more
for
us
to
discuss,
of
course,
on
roles.
I'm
really
excited
that
we're
starting
to
create
these
roles,
starting
to
get
them
drafted
up
and
defined
once
we
have
them
defined.
We
can
clearly
state
like
which
person
is
in
charge
of
which
roles
and
also
start
doing
shadows
of
those
which
I'm
really
excited
about.
A
Any
other
questions
comments
about
roles
before
we
move
on.
We
can
always
come
back
to
it.
C
Basically,
I
was
not
getting
a
lot
of
time
to
explore
more
on
the
code,
biz
and
stuff.
So
the
next
week
I'm
gonna
explore
more
of
the
code
base,
mostly
the
kdf
site,
and
I
think
imran
is
someone
who
is
also
interested
in
exploring
along
with
me.
So
maybe
me
and
imran
will
be
working
on
this.
A
Sounds
great,
thank
you,
and
one
thing
we
discussed
last
time
when
we
came
up
with
this
concept
of
the
developer.
Role
is
not
really
that,
like
the
leadership
of
it,
is
not
really
just
having
developer
skills,
it's
understanding
the
kubernetes
code
base
and
how
to
get
around
it
where
things
are,
how
to
help
people
make
changes
in
various
repos
and
things
that
matter
to
us.
So
that's
really
the
trickiest
part
about
this
developer
role
and
why
we
haven't
had
someone
to
help
others
get
familiar
with
all
of
this.
A
So
thank
you
avanesh
for
starting
to
do
some
exploration
there.
If
anyone
has
any
tips
for
how
we
can
develop
that
expertise,
please
share
either
here
or
in
the
contributor
comms
slack
channel,
because
we
would
appreciate
the
guidance.
A
C
A
C
B
C
C
A
C
B
By
the
way
the
kids.dev
website
is
for
is
on
the
contributor
site
repository
so.
C
C
B
A
A
A
Let
us
know,
in
the
slack
any
questions
comments
at
any
time
about
that.
It's
really
important
work
that
we
need
to
get
done
and
make
sure
that
everyone
is
included
in,
because
it's
about
having
ownership,
making
sure
that
people
understand
responsibilities
like
really
making
this
contributor
thing
a
benefit
to
you
and
to
everyone
else
more
solidly.
A
All
right
I'll
move
on
to
the
next
one
update,
github
repo
to
contributorcom's
name.
I
went
over
this
with
chris
last
week
and
realized
that
it
had
basically
all
been
done
already.
He
just
didn't
really
understand
that.
So
now
it's
pretty
old,
so
I
think
it's
going
to
be
problematic,
but
I
put
a
comment
on
the
the
issue
which
is
there
in
the
notes
saying
basically
it
looks
like
all
of
the
needed
changes.
Are
there
there's
one
suggestion
there
about
making
this
a
little
bit
clearer.
A
So
there
are
several
in
progress.
I
know
that
I
reviewed
the
sig
docs
one
as
well
as
the
sig
storage
one
on
friday
last
week
I
think
frederico
you
went
ahead
and
created
a
pr.
Purnasoir
was
also
going
to,
but
I
don't
think
he's
here
right
now
so
frederico
any
updates
on
your
sig
spotlights
yeah.
D
So,
starting
from
from
the
storage
one,
I
did
open
the
pr.
I
initially
opened
it
in
the
wrong
place,
because
I
went
directly
into
the
well.
I
actually
followed
the
instructions,
but
the
instructions
led
me
to
the
wrong
way.
D
In
the
in
the
wrong
place,
so
maybe
that's
something
that
I
can
also
assist
in
at
least
updating
the
blogging
instructions
that
you
have
and
that
you
shared
with
me
some
time
ago.
So
but
anyway,
I
that's
on
hold.
I
opened
in
the
in
our
own
repository,
and
I
think
that
I
already
have
the
so.
I
got
some
review.
D
Reviews
requests,
simple
stuff
actually
from
both
the
the
xingyang
and
also
from
from
tim
and
I've
committed
them
and
I've
assigned
to
the
to
the
final
approver,
which
let
me
see
who
it
is.
C
D
Link
to
that
as
well-
yes,
I
will.
I
will
I'm
I'm
I'm
I'm
getting
there
so
yeah.
In
the
meantime,
the
I'm
I'm
I'm
writing
the
the
sig
architecture,
one
which
we
got
to
go
ahead.
So
I'm
I
have
the
questions
and
I'm
I'm
sharing
them
with
with
the
with
the
shares,
so
that's
ongoing.
I
would
I
would
say
that
it
will
be
ongoing
for
the
next
one
to
two
weeks,
because
it's
to
actually
come
up
with
good
questions
which
are
not
just
a
repeat.
D
It
takes
a
bit
more
of
time.
Obviously,
and
I'm
I'm
reading
up
on
some
of
the
of
the
stuff
that
I
I
think
is
important
for
having
an
interesting
interview
and
the
six
security
one.
I've
I've
shared
some
examples
of
previous
spotlight
interviews
that
was
requested
for
them
to
get
an
idea
on
before
saying
yes
or
no,
and
I've
just
asked
again
if
they
they
are
okay
with
proceeding,
I
didn't
have
any
confirmation
yet,
but
that's
the
status
of
that
one.
D
So
one
it's
near
the
finishing
line,
the
storage
one,
the
other
is
ongoing.
The
architecture
and
the
six
security
one
is
still
pending
a
definitive
confirmation
from
the
from
the
security
shares
and
the
person
who
is
responsible
for
this
is
yes,
it's
bob
killen.
C
D
I
I
I
I
came.
I
did
a
full
circle
so
for
the
six
storage
one,
which
is
the
only
one
with
any
visibility
in
terms
of
github,
that
is
oh.
D
A
C
D
Vice
versa,
so
okay,
interesting.
A
D
Okay,
so
I
didn't
do
that,
let
me
see
what
was
the
other
one.
A
It's
not
a
bad
thing
to
have
it
on
the
contributor
site.
Sometimes
we
do
put
blogs
on
both
to
increase
seo,
make
more
links
between
the
two.
It
helps
the
contributor
site,
not
sure,
if
that's
what
we
should
do
here
or
if
we
should
start
putting
these
on
the
contributor
site,
that
would
be
a
task
for
the
blog
coordinator
role
person
to
figure
out.
C
And
there's
a
new
process
involved
with
both
contributor
site
blogs
and
kubernetes.io
blogs.
The
process
is
still
a
work
in
progress.
It's
leaning
towards
opening
up
a
a
google
doc,
making
a
google
doc
first
creating
an
issue
and
putting
the
link
of
the
google
doc,
so
the
edits
will
go
into
google
doc
before
making
a
pr.
C
The
reason
being
with
this
is
that
is
that
there's
it's
hard
to
deal
there's
a
lot
back
and
forth
between,
like
edit
or
kind
of
comment
and
requested
changes
on
github
versus
a
google
doc,
where
folks
can
just
quickly
make
the
change
and
kind
of
do
like
the
last.
The
last
step
is
pr
so
there's
things
that
are
still
in
flight
about
changes,
but
just
just
a
heads
up
on
that.
A
Yeah,
we
actually
have
a
an
item
in
our
table
for
keeping
track
of
that
change.
Those
changes
and
that's
kind
of
what
we
have
been
doing
is
doing
it
in
a
hackmd
or
a
google
doc
first
and
then
creating
the
pr,
but
that
was
just
like
within
our
group.
So
this
is
a
more
official
thing
and
that's
very
exciting.
So.
D
I've
also
added
the
first
pr
that
I
opened
and
yes,
the
first
one
was
on
the
kubernetes
website
directly.
D
D
D
Telling
you
what
what
I
was
told,
so
it's
not
it's,
not
something
I'm
suggesting
I'm!
I
I
received
this
as
a
done
thing
and
I
followed
the
recommendation
so
yeah.
A
I
think
it's
a
good
recommendation,
so
sounds
good
to
me.
I
was
actually
gonna
ask
like
ray
if
you
had
opinions
on
if
we
should
do
that
or
if
we
should
just
be
posting
on
the
contributor
site
or
something
but
sounds
like
tim
has
already
weighed
in
so
sounds
like
a
good
plan
to
me.
A
All
righty-
and
I
should
grab
that
note
and
I've
added
the
note
about
where
they'll
be
posted
into
the
notes
as
well
and
then
there's
one
other
item.
I
want
to
do
on
the
six
spotlights
which
is
atarva
since
you're
back
yeah.
B
I
was
just
going,
would
you
still
like
to
do
one
of
these
yeah?
I
was
I,
I
went
through
all
the
sigs
that
have
been
taken
and
that
are
being
worked
on.
So
I
think
I
will
take
the
sig
testing
one
sec
sounds.
B
A
A
Yes,
I
can
give
you
the
the
basic
instructions,
through
slack
yeah,
to
kind
of
review
it
here.
What
you'll
need
to
do
is
to
reach
out
to
that
stake.
Generally,
I
find
the
sig
channel
in
slack,
and
I
put
a
post
in
that
channel-
saying:
hey,
I'm
from
contributor
comms,
I'm
looking
to
do
a
spotlight
on
your
sig.
Who
should
I
talk
with
to
do
the
interview
generally
that'll,
be
the
sig
chairs.
You
can
also
just
kind
of
reach
out
directly
to
them.
If
you
want,
I
find
it
easier
to
find
them.
A
If
I
just
do
it
that
way
anyway,
either
way
some
way
you'll
get
to
the
chairs.
Probably,
and
then
I
recommend
doing
your
interview
asynchronously
in
a
google
doc,
because
then
you
have
all
of
their
responses
written
down
and
it's
kind
of
easier
to
convert
that
into
text,
though
some
folks
have
done
their
interviews
via
video
calls
and
like
recorded
them
and
converted
that
into
text
and
had
success
with
that
as
well.
A
So
either
way,
basically,
the
steps
are
figure
out
who
to
interview
interview
them,
create
a
draft
doc
in
hackmd
or
google.
Docs
sounds
like
that
might
be
preferred
in
the
future,
get
some
reviews
on
that
and
then
create
a
pr
and
I'll
give
you
all
these
instructions
on
slack
so
that
you
have
them
all
listed
sound
good.
B
A
Right,
usually,
there's
co-chairs
of
each
special
interest
group,
so
you'll
generally
be
interviewing
two
people:
okay
cool
yeah.
Generally,
we
are
trying
to
make
it
more
for
contributor
experience.
We've
traditionally
had
two
all
of
the
ones
that
I
know
of
have
to,
but
we
want
to
have
three
to
four
in
the
future,
but
that
hasn't
been
implemented
yet.
B
B
A
It's
more
like
an
ongoing.
We
used
to
have
an
umbrella
issue
for
it
in
github,
but
it
became
stale
frequently
because,
like
people
would
have
time
to
work
on
it,
so
they'd
work
on
it
and
then
people
wouldn't
have
time.
So
it
would
just
kind
of
get
left
there,
but
it's
always
something
that
we
can
do.
A
So
it's
just
one
of
those
things
that's
like.
If
you
want
to
write
a
sig
spotlight,
blog
post
have
at
it,
and
there
is
some.
There
are
some
resources
for
this
in
our
repo
that
I'll
be
sending
to
you
later
so
yeah.
A
All
righty
we're
gonna
move
on.
We've
only
got
10
minutes
left.
So,
let's
see
if
we
can
rush
through
these,
I
kind
of
doubt
why
not
get
through
everything.
Today,
let's
see
migration
from
katakota
to
killer
coda
this
one
we
have
on
here,
basically
just
to
kind
of
keep
track
of
this
very
interesting
thing.
That's
happening
in
our
space.
Katakota
was
deprecated,
let's
say,
and
so
it
sounds
like
the
plan
now
is.
Moving
to
this
new
thing
called
killer
coda
any
updates
on
that
right.
I
think
you're,
probably
the
closest.
C
No,
no
updates
doing
it
also
for
the
kubernetes
io
main
website
as
well.
So
for
for
that
website
is
it's
odd.
The
counter
code
is
still
is
still
available,
but
I
really
want
to
have
a
migration
path
moving
forward
in
case
something
happens,
and
I
mean.
A
A
C
D
C
I
haven't
done
that
yet
okay,
so
they
have
a
blog
on
it,
how
to
migrate
from
katakura
to
killer
buddha,
which
ideally
I
was
in
conversation
with
deba,
but
for
that
I
need
some
credentials
to
be
or
access
to
the
main
repo.
C
A
A
C
A
D
A
Appreciated,
thank
you
and
a
reminder
to
everyone.
There
is
a
document
on
all
the
stuff
that
we
need
tweeted
from
the
annual
report.
Well,
not
all
of
it.
There
is
room
for
more
if
anyone
wants
to
tweet
things
about
the
annual
report,
but
if
you
want
to
help
out
with
that
effort,
there's
a
doc
to
check
out
and
I'll
move
on
from
that.
A
Yeah,
I
think
that's
fine,
validate
command
was
broken.
I
pinged
rajula
about
this
and
also
pinged
him
about
mentoring,
folks,
on
the
knowledge
that
he
has
on,
like
the
slack
bot
and
the
github
for
for
tweeting,
like
he
has
some
really
nice
technical
knowledge
that
would
fit
into
that
developer
role.
So
I
chatted
with
him
about
making
sure
that
that
knowledge
gets
shared
that
other
folks
can
take
on
those
responsibilities.
A
He
said
that
he's
been
really
really
busy
with
work
stuff.
So
that's
why
he
hasn't
been
able
to
do
that,
but
he
is
excited
about
the
idea
of
passing
on
that
knowledge.
So
that's
kind
of
where
we're
at
there.
B
Was
something
going
on
in
the
past
with
avinesh
me?
I
think
nigel
and
rajiv,
but.
A
A
A
A
Yeah,
I
actually
just
deleted
the
the
note
that
was
you
all
working
together
on
that
pretty
sure
it
was
the
auto
generating
blog
tweets
thing
that
will
still
need
to
happen,
but
we'll
be
using
a
totally
new
tool
for
it.
So
you
won't
need
visualize
help
as
much
for
that
in
the
future.
We
help.
A
Not
planning
to
deprecate
or
remove
the
current
workflow.
We
still
want
to
have
it
around
because
it
has
its
uses,
but
we're
hoping
to
have
this
other
workflow
for
our
group
to
use.
But,
for
example,
if
we
wanted
to
have
another
group
within
kubernetes
create
tweets
for
us,
we
would
probably
want
to
use
our
existing
github
workflow,
because
that's
more
integrated
into
the
way
the
other
sigs
work.
C
A
Yep
all
right
I'll
move
on
to
the
next
item.
We
only
have
a
few
minutes.
Let's
see
what
we
can
get
through
review
requested
for
apac
meet
our
contributors
blog
any
updates
on
current
medar
contributors,
blogs
that
need
help
or
anything.
C
So
in
the
contrabex
meeting,
the
recent
one,
I
think
josh
said
that
something
is
wrong
with
kdel
scheduling.
A
A
A
Okay,
I
know
that
we
had
given
british
some
advice
on
how
to
find
info
about
where
to
find
the
right
code,
but
I'm
not
sure
how
that
went
and
he's
not
here
to
update.
A
All
right
there
was
a
blog
that
deborah
wrote
that
needed
review
it
was
reviewed.
Is
this
one
done
still.
A
Okay,
is
there
any
active
action
needed
from
us
on
that?
Do
you
know.
C
I
think
now
the
the
blog
is
in
k,
seg
docs
blog
team
sub
project.
So
I
think
they
are
reviewing
that
thing.
I
don't
know
if
we
should
track
this
from
our
side
or
not,
because
I've
done
the
review
and
the
person
who
wrote
this
blog.
She
has
changed
the
stuff
that
I
suggested.
Maybe
so
I
don't
know
if
we
should
review
this,
if
you
should
try
this
okay.
A
I'm
gonna
move
on
to
the
next
item
because
we're
already
at
time
next
item
is
the
sig
docs
blog
subproject
process
changes
which
we
already
discussed.
So
I'm
gonna
move
on
past.
That
tweet
on
squashing
commits
rashid,
wanted
to
do
some
work
on
that,
but
he's
not
here
so
we'll
move
on
past
that
security
comms
guidelines.
This
was
the
concept
of
an
ish.
We
can
work
together
offline
on
this.
If
you
need
any
help
with
it,
yep.
C
A
Good
and
hina
added
an
item
on
that.
We
talked
about
earlier
yeah
because
she's
gonna
add
the
other
method
here,
suggesting
adding
the
label
to
those
issues
as
well.
All
right,
it's
not
901!
So
does
that
count
as
on
time.