►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20230113
Description
[SIG ContribEx] Weekly Marketing Meeting for 20230113
A
So,
as
we
mentioned
before
we
hopped
onto
the
recording,
we
have
moved
our
note
stock.
We
asked
for
that
to
be
updated
in
the
calendar,
invite
but
I
don't
think
it
has
yet.
So
we
might
have
to
remind
someone
on
that,
but
I
have
updated
the
old
node
stock
at
the
top
of
it
to
let
you
know
that
there's
a
new
DOC
for
2023
when
this
not
200
pages
long.
C
B
A
Well,
I
mean
we'll
get
to
that
in
the
table
too.
Okay,.
B
B
A
Yeah
so
we
updated
the
charter.
We
added
in
a
sub-project
lead
role
which
we'll
need
review
for.
Obviously
we
could
bring
that
up
once
we
get
to
it
in
the
table.
I
guess
yeah
we'll
need
to
find
that
link,
so
you
might
want
to
have
it
handy
and
we
also
updated
the
owner's
files
or
one
of
them
I
actually
still
haven't
gotten
the
PR
in,
for
my
other
one
I
was
going
to
wake
up
early
and
do
that,
but
that
has
not
happened
yet
so
after
this.
B
So
yeah
I
actually
have
I
need
to
pull
back,
that
owner's
fault
change,
that
I
did
and
redo
it,
because
I
forgot
the
freaking
Branch
it
so
welcome
back
to
the
New
Year
everybody
fork
and
Branch.
A
D
A
B
C
A
A
That
is
the
fair
exception
anyway.
So
that
is
an
update,
big
win
that
Chris
and
caslin
did
like
lead,
work
and
stuff
yeah.
A
D
Yeah
so
I
added
so
I,
don't
know
if
Mark
Evans
is
here,
so
there
was
a
PR
guys
for
the
tech
Shadow,
so
I'm
happy
that
comes
Tech,
Shadow
roll
Mark
volunteered
and
there
is
a
prized,
so
it's
I
can't
approve
it
still.
So
someone
from
the
community
has
to
approve.
A
A
B
Week,
anybody
in
the
kubernetes
org
can
lgtm
a
PR,
not
anybody
can
approve
it
and
there
is
no
inheritance.
So
it's
not
like
if
you're
a
prover
you're
automatically
an
org
member
or
anything
else
like
you
got
to
still
have
all
that
stuff
set
up
so
yeah
fun,
stuff
lots
of
Lessons
Learned
granted.
A
B
B
A
C
So
if,
if
anybody
goes
and
just
do
LG
team,
will
the
bot
respond
it
with
a
label
yeah.
A
A
B
C
B
G
A
Yay
happy
2023
excited
that
everyone
is
here,
of
course,
but
Ray's
not
been
here
for
a
while,
so
poor,
Ray,
so
I
think
there
are
so
many
people
today.
It's
wonderful
all
right.
So
if
there
are
no
other
updates
and
big
wins,
of
course,
they're
welcome
anytime,
but
any
new
items
that
folks
have
noticed
I
see
there.
E
So
there
will
be
an
incoming
Quests
for
new
tweets
I
assume
that
the
the
process
still
the
same,
where
we
created
an
issue
for
the
Tweet.
So.
A
E
Can
yeah
so
this
is
oh,
so
O'reilly
shut
down,
Public
Access
for
catacona
for
everyone,
except
for
kubernetes.io,
but
in
December
they
we
they
reached
out
and
said
we're
gonna
We
want
to
shut
it
down
and.
G
E
E
There's
reach
out
to
out
of
Kitty
as
well.
I
think
you've
seen
that
in
slack
channel
or
do
tweet
as
well.
We
have
a
GitHub
discussion,
that's
live!
We
we
want
to
invite
folks
to
to
give
us
options
as
well.
I
know,
kubernetes.dev
is
using
and
we'll
go
to
GitHub
code
spaces,
so
that's
awesome
option
and
also
things
like
what
what
what
kind
of
coded,
what
wasn't
there
in
catechota?
E
What
what
we,
maybe
some
some
ideas
of
what
we
would
like
in
the
future,
so
just
kind
of
have
that
just
get
that
discussion
that
place
for
folks
to
to
to
place
to
place
your
thoughts.
A
A
B
E
A
I,
don't
know
if
you
have
buffer,
but
we
could
also
give
you
buffer
access,
which
would
probably
be
easier
for
you
yeah,
because
we
have
buffer
our
newer
Twitter
tool.
It
has
the
ability
to
schedule
things:
it's
a
nice
UI,
so
if
you
would
prefer
to
do
it
through
that,
we
can
get
you
set
up
with
that
access
preferences.
A
All
righty
sounds
good,
so
reach
out
anytime.
You
want
to
tour
a
buffer.
You
know
where
to
find
us
on
Slack
and
I'm
excited
to
see
where
katakata
goes
quickly.
Foreign.
D
Maybe
I
have
a
question
before
we
jump
to
the
next
item
so
regarding
this
tweeting
using
GitHub
versus
the
buffer,
so
I
think
our
current
automation
has
some
issues
I.
Think
it's
a
long
like
a
since
last
quarter.
It
didn't
work
out.
So
should
we
prioritize
on
how
should
we
go
about
and
fix
it?
Should
we
directly
use
cover
and
I
think
last
time
when
we
spoke,
we
at
least
we
had
a
kind
of
consensus
that
we
would
use
the
buffer,
but
somehow
integrated
by
architect.
So
that
was
the
last
thing.
Yeah.
A
D
So
maybe
should
we
prioritize
it
because
I
think
the
current,
the
the
workflow
using
the
automation,
tool
and
yeah
stuff
with
the
we
have
some
script
to
generate
this
stuff
and
then
it
creates.
So
it
creates
a
lot
of
overhead
I.
Think
it's
somewhere.
We
are
at
least
in
the
last
time.
It
didn't
work
out
quite
well.
It
should
be
prioritize.
This
thing
to
find
a
simple
way
to
integrate
buffer
and
GitHub
I.
A
D
A
So
it
sounds
like
we'll
need
to
add
the
shadow
to
that
as
well.
So
maybe
it's
a
good
thing
I
haven't
put
that
in
yet
let's
go
with
that.
A
Indeed,
all
right
and
the
other
new
items-
yes,
there
is
one
other
one
I
think
that's
also
you
Imran.
D
Yeah
yeah
so
yeah,
so
this
is
the
other
one.
So
I
think
we
there
was
a
Jaws
started
the
discussion
in
Contra
books
channel.
So
we
have
a
bunch
of
yeah
issues
regarding
like
eight
step
upgrade,
so
it's
some
of
them
did
it.
Another
takes
authenticator,
Hugo,
stuff
and
Coke,
and
maybe
we
could
I
was
thinking
that
this
also
could
be.
We
can
that's
what
I
said
in
the
chat,
the
message
that
you
could
also
take
some
of
the
issues
and
we
could
work
it
through
and
I.
Think
Chris
was
also
interested
in
it.
D
D
D
You
hear
me
it's
better
now,
it's
better
now
yeah,
okay
yeah,
so
something
happened
on
the
internet.
So
where
did
you
lost
me?
This
is
so
I
just
want
to
confirm
that
we
can
assign
the
issues
for
ourselves.
So
that's
the
one
thing
I
want
to
say,
and
so
I
I
want
to
clarify
that
there
is
no
comments
in
most
of
the
issues.
D
So
do
we
need
to
dig
down
and
verify
the
issues
correct
and
we
need
to
before
we
solve
the
issue,
something
I
didn't
understand
from
the
issues
because
yeah
there
is
not
much
information
written.
Why
it's
needed
and
so
on.
So
the
Y
part
was
missing
to
me.
So
I
think
this
is
where
the
Josh
want
to
clarify
with
the
the
one
who
wrote
the
issue.
D
A
D
Yeah,
we
can
claim
them
and
before
that
yeah.
So
what
what's
my
question
is
like
is
it
is
it
issue
is
Triads
like
like
we
have
do.
B
D
B
Yeah
I
mean
you
like
in
general,
when
it
comes
to
open
source
projects,
you
can
take
issues
when
they
get
stale,
we'll
get
a
warning
all
right
like
we'll
get
an
alert
from
a
Kate
spot.
That's
like
hey!
There.
B
Here
in
90
days
or
whatever
so
feel
free
to
take
them,
if
you
somehow
drop
them
or
need
to
hand
them
off,
let
us
know
okay,
but
yeah.
Like
that's
a
good
point,
we
should
have
some
kind
of
triage
process
yeah
exactly
that's.
D
C
C
A
B
Are
excited
about
it
as
a
process,
I
wonder
if
we
should
just
copy
that
you
know
entirely
possible
potentially.
B
A
C
A
B
A
As
such
I
know,
atarva
had
been
interested
in
helping
out
with
this
remaining
action
item,
which
really
this
one
is
just
like
a
tracking
of
what
was
done,
and
this
one
is
the
only
actual
action
item.
I
think
maybe
I
should
combine
these.
A
Previously,
here
it's
going
to
be
a
lot
of
doing
things
with
the
table
today,
I'm
very
excited
about
it
all
right,
so
I
removed
that
first
row,
which
was
just
a
tracking
of
hina's
work,
setting
up
a
team
in
GitHub
for
us
and
setting
up
I
guess
the
the
issue
thing
I
think
that's
more
attractive
than
this
one
though,
but
what's
remaining
on
that
is
we
want
better
ways
to
make
sure
that
we
know
when
an
issue
or
PR
is
created
that
we
should
know
about
which
this
sounds
like
what
we
were
just
talking
about,
so
maybe
Imran.
A
So
you
could
look
over
that
element
of
the
table
for
more
context
on
what's
been
done,.
F
A
A
We
had
ideas
about
what
to
do.
I'd
have
to
read
through
all
the
notes,
to
figure
out
what
exactly
it
was.
I
know
that
we
had
added
an
at
our
team
into
the
issue
template,
but
we
also
I
think
we
wanted
to
try
to
find
a
way
to
automate
when
the
label
is
applied.
Also
pinging
us
as
a
team.
A
Yeah,
we
were
still
trying
to
work
out
if
there
was
existing
stuff
for
that
or
if
we
needed
to
create
something
or
what
the
best
way
was
to
do
it.
So
anyone
who
wants
to
work
on
that
I
know
atarfo
wanted
to
is
Tarvin
not
on
today,
I
don't
have
my
participant
screen
up.
A
Oh,
my
chart
was
not
on
today
and
he's
been
really
busy
lately.
So
if
you
are
interested
in
helping
out
with
this,
that
would
be
wonderful
and
Imran
sounds
like
relevant
to
you
so
I'm
putting
your
name
on
it.
C
A
A
B
A
G
A
A
A
B
D
B
A
Want
to
bring
up
the
issue
yeah
and
we
can
just
kind
of
go
over
it.
I
was
also
actually
thinking
about
taking
on
a
lead
role
that
was
not
comms
this
year,
so
I
would
be
in
the
same
boat
as
just
about
any
of
you,
except
that
I've
been
to
a
couple
of
contributor
Summits.
So
there's
that
much,
but
I
would
not
know
that
much
about
the
role
that
I
would
be
leading,
so
it's
possible
to
learn
a
role
as
you
lead
it.
Yes,.
B
A
A
B
Yes,
that
was
hard.
I
was
going
through
the
whole
thing,
with
my
niece
yeah.
A
B
B
There's
a
table
further
down,
so
we
need
a
lead
for
registration.
There's
a
we
need
a
lead
for
the
social
event
day
of
operations.
That
is
obviously
like.
You
need
to
be
there
kind
of
thing
leading
registration.
You
can
totally
do
remotely
social
event.
If
your
shadows
intend
to
be
there,
I
feel
like
you
could
lead
remotely
and
day
of
operations.
I
mean
right
now,
I'm
a
shadow
for
that,
but
it
could
very
well
end
up.
I
become
a
lead
registration.
A
Definitely
the
best
one
to
lead
remotely
and
it's
I
would
say
it's
not
like
it's
not
bad
to
learn
on
the
job,
because.
A
Your
job
is
to
make
sure
that
there
is
a
form
that
people
can
use
to
sign
up,
and
it's
got
the
information
on
it
that
you
need
to
know
which
the
rest
of
the
leaders
will
tell
you
about
what
they
need
to
know
and
make
sure
that
it
closes
at
a
reasonable
time
and
that
all
of
that
information
is
passed
on
I
guess
to
the
cncf
at
the
right
time,
which
you
can
figure
out
all
these
pieces
from
the
role
book
and
from
talking
to
the
other
leads
who've
been
involved
with
the
contributors
Summit
before.
A
So
it's
pretty
pretty
accessible
role.
If
folks
are
interested.
E
B
B
Have
questions
then
I
would
definitely
talk
to
Noah
or
Bob,
or
somebody
that's
done
reg
before
Jeff
has
done
reg
before
there's
a
lot
of
people
that
have
done
Rich
before
actually
so.
B
F
F
Pin
yeah
Josh
added
Adam
greet
coordinator:
anybody
know
what
that
is
so.
B
We
do
a
Sig
meet
and
greet,
but
it's
after
the
contributor
Summit,
it's
like
the
Thursday
or
Friday
okay,
but
basically
it's
just
coordinating
space
with
the
cncf
getting
the
leads
like
there
is
a
comms
component
to
that
that
I
have
a
shadow
that's
going
to
work
on,
but
you
would
work
with
them
to
talk
to
the
Sig
leads
to
figure
out
who
wants
to,
you
know,
have
a
table
or
representation
or
whatever.
B
E
G
B
Yet
because
I've
just
been
told,
changes
are
gonna
happen,
so
be
that
as
it
may,
I'm
in
a
kind
of
a
critical
position
for
the
team
kubernetes
here
at
AWS,
so
I
don't
see
how
I
wouldn't
go
we'll
see,
but
I
do
intend
to
be
there
at
right.
Now.
A
A
With
the
big
companies,
perhaps
I
don't
know
yes,
yes,
so
I
added
that
as
a
new
item
at
the
bottom
in
our
daily
notes,
I
probably
won't
add
that
to
the
table,
because
it's
not
technically
really
a
contributor
comms
thing.
A
So
definitely
check
that
out.
It's
a
great
opportunity
to
get
involved
with
kubecon
get
your
face
more
well
known
by
more
of
the
the
rest
of
the
folks
in
the
community.
A
lot
of
folks
who've
been
very
prominent
in
the
community
for
a
very
long
time
help
with
the
contributor
Summit.
So
you
start
to
get
known
as
a
person
who
does
things,
and
that
can
be
helpful
if
you
want
to
continue
to
move
up
into
leadership
and
help
out
with
the
project.
A
A
A
So,
let's
move
on
to
the
next
item
owners
file,
we
just
said
update
owners
file
because
we
were
not
sure
what
owners
files
would
need
to
be
right,
updated.
What
we
learned
in
this
is
that
6.
yaml
has
the
owner's
files
that
are
relevant
to
us
listed,
so
we
actually
don't
need
to
well.
We
actually
do
need
to
edit
sigs.yaml,
which
I
don't
think
we
did
when
we
had
our
meeting
right,
because
there
was
an
upstream
marketing
thing
in
there.
We
just
need
to
update
the
text
yeah.
B
A
B
A
A
A
C
A
It
didn't
I
thought
it
was
worth
a
try,
which
one
is
that
in
is
that
in
oh,
we
found
it.
It
was
in
it
was
that
one
in
kubernetes
community-
yes,
it
is
found
it.
So
if
we
find
contributor
comms
in
this
file,
I
thought
this
would
be
a
good
way
to
find
the
owner's
files.
But
now
it
is
a
giant
wall
of
text,
because
that
is
what
six
diamo
is.
B
A
A
So
interesting,
fun
fact:
in
six
dot
yaml
the
last
week
in
kubernetes
development
owners
file
is
listed
as
one
that
we
have
ownership
of
foreign.
B
Well,
I
I
think
I
knew
that,
but
I
didn't
remember
that
we
had
made
that
change.
It
was
just
one
of
those
things
where
it's
like
that
kind
of
falls
under
comms
and
Josh
was
like.
Let's
put
it
there.
A
Yeah,
so
we
have
had
discussions
in
the
past
about
our
team
having
more
ownership
of
last
week
in
kubernetes
development
which
frederico's
not
on
today,
but
that
would
totally
be
a
Frederico
thing
if
we
do
start
doing
more
with
that,
because
it
is
a
publication
where
Josh
has
generally
run
it
where
he
talks
about
what
happened
in
the
last
week
in
kubernetes
development,
with
our
mission
being
to
help
spread
the
word
about
the
wonderful
work
that
contributors
are
doing.
A
A
So
we
are
updating
the
like
our
main
contributor,
comms
repos
owner
file.
This
is
the
raw
link
forgot
about
that.
I
need
to
fix
that
later.
I'm,
just
gonna
leave
it.
For
now.
A
You
can
see
what
it
was.
There's
a
lot
of
folks
on
here
who
were
previously
involved
with
the
group
and
who
are
not
so
involved
right
now,
like
rajula,
many
of
you
have
met
was
basically
our
previous
Tech
lead
and
he's
not
so
involved
with
us.
Now,
though,
he
tries
to
help
out
when
folks
need
some
help,
but
we're
proposing
moving
him
into
Emeritus
pensu
into
Emeritus
only
doll.
We
don't
know
why
he
was
there
in
the
first
place.
He.
A
Yeah,
definitely
it's
been
a
while
so
we're
moving
a
bunch
of
people
out
into
Emeritus
he's
not
even
an
approver,
so
he
won't
even
be
a
emeritus
and
then
we're
updating
this
one.
Do
you
want
to
bring
up
the
issue
that
you
have
Chris?
If
you
have
it.
B
Here
we
go
and
that
one
okay.
A
That
you
will
be
pinged
pinged.
B
Automatically,
like
it'll,
be
a
random
selection
of
people
that
get
pinged
automatically
from
that
list.
When
a
new
PR
issue
comes
in,
the
approvers
are
the
one
that
can
actually
say
slash
approve
so.
B
A
Also,
another
change
that
we're
making
is
that
we're
updating
the
team
charter.
There
were
a
lot
of
mentions,
of
course,
of
Upstream
marketing,
so
we're
updating
those
to
make
sure
that
it
reflects
contributor.
Comms
we've
updated
some
information
about
how
the
team
works
with
all
of
our
beautiful
new
lead
roles
which,
like
I,
mentioned.
The
contribex
like
Sig,
asked
us
about
in
one
of
the
Sig
meetings,
because
they
thought
it
was
cool
that
we
were
doing
that
and
wondered
if
they
should
turn
it
into
a
process.
A
A
If
you've
never
checked
out
the
charter,
it's
a
useful
document.
It's
not
all
that
long
and
it
has
some
nice
information
about
it
like
it.
Has
this
decision
making
part
that
talks
about
if
there
were
any
particularly
contentious
decisions
here
is
the
theoretical
process
that
we
would
use
to
resolve
them.
We
ever
actually
use
it
pretty
much
never,
but
we
do
have
a
process
in
place.
A
Should
we
have
issues,
there's
also
information
about
how
to
leave
the
group,
not
that
there's
that
much
involved
with
it,
but
just
a
you,
are
encouraged
to
run
off
and
do
your
own
thing
if
you
want
to
we
love
to
have
your
your
support
as
long
as
you're
around
and
happy
to
give
it,
and
whenever
you
want
to
move
on,
we
are
happy
to
support
you
and
there's
some
stuff
about
like
our
general
goals
and
stuff.
A
B
C
A
A
This
one
is
the
old
link
that
has
marketing
team
as
the
repo
name,
which
is
now
contributor,
comms,
so
yeah.
That's
why
it's
broken.
Thank
you,
Kim.
A
A
B
F
A
So,
yes,
we've
looked
at
that
owner's
file
like
I
said
the
contributor
tweets
owner's
file
needs
to
be
updated
as
well,
but
I
don't
have
that
in
yet
because
I
messed
it
up
the
first
time
and
I
haven't
actually
taken
the
time
to
sit
down
and
create
the
proper
PR.
But
I'll
give
you
a
look
at
what
that
looks
like
I'm
just
going
to
paste
it
right
here,
so
you
can
see
it.
A
It
is
Tiny.
We
make
it
giant
momentarily.
A
Messing
with
the
table
so
yeah
we're
gonna,
update
the
contributor
tweets
owners
file
as
well.
The
plan
for
that
right
now
is
for
me
and
Chris
to
be
reviewers
as
social
media
lead.
Any
tweet
requests
that
come
in
through
the
repo
I
should
make
sure
that
I
know
about
since
I.
Don't
have
any
Shadows
or
particular
team
members
on
social
media.
A
I
was
just
going
to
have
Chris
as
my
backup,
but
if
anyone
particularly
wants
to
be
a
backup
for
reviewing
tweets,
let
me
know-
and
for
approvers
it's
going
to
be
myself,
obviously,
because
I'm,
a
social
media
lead
Chris,
because
he's
really
good
at
Social,
Media
stuff
and
he's
a
sub-project
lead
and
Imran,
because
you're
going
to
need
approver
access
for
any
updates
that
you
make
to
the
automation,
but
we're
not
planning
to
have
you
as
a
reviewer
so
that
you
don't
get
pinged
about
tweets.
You
can
just
do
your
own
stuff
with
it.
A
A
A
Cool
I
should
put
a
reminder
to
myself
to
do
that
and,
let's
add
you
as
a
an
approver
as
well.
I'll
put
your
actual.
Oh
sorry,
you
said
it
was
your
name.
It's.
A
So
we'll
be
putting
in
that
PR
six.yaml
needs
an
upstream
marketing
text
update
like
we
mentioned.
We
actually
haven't
created
that
PR
yet,
but
that's
on
me
and
Chris.
Unless
someone
else
wants
to
make
a
relatively
easy
pr206.yaml.
E
A
B
It's
a
real
pain,
sometimes
and
I've
already
closed
and
reopened
two
PR's
this
morning,
because
you
get
we.
A
A
A
And
if
we
cannot
help
you
with
a
get
issue
that
you
get
yourself
into,
we
will
make
sure
that
we
find
someone
who
can
absolutely,
and
you
also
saw
the
updated
Charter
that
needs
an
lgtm
I'm
guessing
someone
already
did
it,
probably
maybe
so
we
can
probably
go
ahead
and
prove
that
if
anyone
has
LG
tm'd
it,
if
you
haven't
looked
at
it
and
you
would
like
to
look
at
it,
please
do
make
sure
Josh.
B
B
B
A
A
I
think
you'd
be
able
to
or
get
issues
continue.
Yeah
I
know
right,
but
I'm
going
to
move
on
from
those
file
updates.
Unless
anyone
else
wants
to
talk
about
them.
A
B
A
We
didn't
do
that.
That's
another
task
for
us
to
do
like
highlight
that
one
so
we'll
skip
that
for
now.
D
Yes,
okay,
yeah,
so
I
I
I've
been
so
maybe
just
an
update
and
before
it's
also
good
too.
Yes,
please
yeah
to
prioritize
this.
To
before
we
go
so
I've
been
added
to
the
the
slack
admin
group,
so
I
can
add
them,
so
I
just
want
to
I
haven't
touched
it
so
far
because
to
get
it
up
in
automation,
I
think
I
need
to
spend
some
time.
Do
you
really
need
automation
or
shall
we
just
do
it?
Manually
I
mean
yeah
the
only
issue.
D
D
A
D
A
B
F
D
D
A
A
A
Yeah
good
good,
all
right,
so
we'll
move
on
from
that
one
update
repo
with
role
descriptions.
The
only
one
remaining
is
me
and
Chris.
A
Is
the
general
one
that
we
merged
so
I'm
gonna?
Remove
that
I?
Guess
it's
me
who
submitted
this
so
I'm
gonna
have
to
find
the
was
it
the
pr
that
I
submitted
I
wonder
if
it's
actually
wrong
too
and
I
need
to
redo
it.
It's
probably
on
a
branch
and
not
a
fork,
because
I
was
trying
to
use
the
UI
because
it's
so
convenient,
but
it's
terrible,
but.
A
A
Project
Lead
that
worked.
B
A
But
it
would
be
wonderful
if
you
want
to
review
what
we're
proposing
as
the
sub-project
lead
role.
One
of
you
all
very
likely
may
become
a
sub-project
lead
at
some
point.
A
This
is
being
slow
to
load,
but
it's
similar
to
the
other
role,
definitions
that
you
all
have
created
and
seen
it's
just
going
to
be
a
very
general
broad
role.
Kind
of
a
buck
stops
here
role
to
make
sure
that
things
get
done
for
our
sub
project.
A
So,
if
you're
interested
in
the
sub
project,
will
you
definitely
check
that
out?
Well,
it
takes
forever
to
load.
A
And
we
only
have
one
minute
left
so
I'm
going
to
skim
through
the
table
to
make
sure
that
there's
nothing
critical
that
we're
missing
contributor
site.
We
talked
about
the
new
issues
in
there
and
that
we
need
a
triage
process
for
that.
So
Imran
message
us
if
you
need
any
help,
Sig
spotlights
we
only
have
a
minute
left
so
I
think
we'll
skip
updates
on
these
here.
A
But
if
you
want
to
update
us
on
your
progress
ping
in
slack,
if
you
need
to
review
on
anything,
maybe
ping
me
directly
and
I
will
prioritize
that
migration
from
katakota
to
GitHub
code
spaces.
We
talked
about
that.
It
has
urgency
to
it
now
because
kubernetes
had
an
exception,
but
we
are
now
getting
kicked
off.
So
we
already
talked
about
that.
There's
more
notes
about
it!
In
today's
notes.
A
The
validate
command
is
sporadically
broken
for
the
GitHub
tweets.
We
talked
about
how
we
need
to
work
that
out.
Ray
is
going
to
probably
submit
an
issue
to
that.
If
it's
broken,
that's
fine,
we'll
just
put
it
into
buffer
as
a
social
media,
lead
it's
on
me
to
make
sure
that
that
happens,
but
prioritize
the
slack
bot
over
this
probably
deba.
Had
a
Blog
I
keep
pinging
on
that.
A
It's
fine,
Sig,
Doc's,
blog
sub
project
process,
changes
I,
don't
know
if
Rey
is
even
still
on,
probably
not
for
a
minute
over,
so
we'll
get
updates
on
that
another
day,
security
comms
guidelines,
maybe
someday
we'll
work
on
that
scheduling
tweets
for
non-members.
That
is
like
the
same
thing
as
the
other
one.
We
should
probably
merge
those
and
Chris's
short
notes
about
admitting
to
the
documentation
which
we're
basically
doing
with
the
sub
project
lead
role
theoretically,
but
we
should
probably
actually
confirm
that
I
think.
B
C
C
A
But
we're
already
two
minutes
over
Adam
Ron
to
the
approvers
list
for
kate's.dev.
That's
a
conversation
that
we
needed
to
have
with
like
Josh
and
folks.
So
as
part
of
your
exploring
those
issues,
you
might
want
to
look
into
owners.
Ownership
of
the
case.dev
I
want
to
add
that
as
one
of
the
owner's
files
that
we
should
have
access
to
I
don't
know
yes,.
A
And
Frederico
this
needed
review
if
it
still
needs
to
review
I'll.
Look
at
that
after
this
and
oh,
this
is
a
great
idea
that
we
should
pursue
at
some
point.
So
that
being
said,
we
are
three
minutes
over.
So
if
folks
need
to
go
definitely
to
go
on
ahead
and
go
if
you
have
a
couple
of
minutes,
I
would
love
to
hear
Frederico
any
updates
that
you
have,
especially
on
your
blog
process
updates
and
this
issue.
G
A
F
G
Close
that,
in
terms
of
the
blogging
process,
updates.
G
F
G
Yeah,
but
this
is
something
that
I
will
I,
will
work
on
during
this
week.
I
I
think
it
makes
sense.
So
what
I
think
that
the
the
board
that
we
have
the
table
that
we
have
in
the
notes
is
good
to
keep
us
in
sync
and
on
top
of
the
advance,
and
something
like
that,
cabin
board
is
good
for
work
in
progress,
visibility
of
things
that
come
and
go
so
what
I
will
do
is
I
will
reflect
the
ongoing
work.
G
That
I
know
exists
around
the
specifically
on
the
blogging
area
in
in
that
in
them,
and
I
will
share
the
the
link
to
it
in
slack
so
that
we
can
have
an
internal
view
on.
Is
it
useful?
Is
it
not
Etc,
on
top
of
that,
I
I
made
a
list
of
the
potential
Spotlight
targets
that
we
might
address,
that
are
not
specifically
the
sigs,
but
they
are
like
sub
projects
or
activities
of
the
six
that
could
be
still
interesting
to
cover
in
a
spotlight.
G
Article
and
I'll
I'll
commit
that
as
a
markdown
file
in
in
the
same
place,
where
we
have,
we
have
the
blogging
guidelines.
G
A
A
Course,
I'm
glad
to
see
that
you're
interested
in
getting
the
kanban
board
working
again.
We
did
primarily
have
it
as
like
an
editorial
kind
of
thing,
so
it
makes
a
lot
of
sense
for
you
to
start
it
up
as
like
a
blogging
Focus
kind
of
thing
again
and
more
work
on
Sig
spotlights
is
always
welcome,
also
a
great
place
for
new
contributors
to
get
involved.