►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20230512
Description
[SIG ContribEx] Weekly Marketing Meeting for 20230512
A
Hello
and
welcome
to
the
May
12th
Friday
May
12th
edition
of
the
contributor
comms
team
meeting.
I
was
just
thinking
before
this
meeting
that
every
time
I
still
feel
like
I
should
say
Upstream
marketing,
but
no,
we
are
contributor
comms
solidly.
Now.
A
So
welcome
to
the
meeting
as
usual,
we
do
operate
under
a
code
of
conduct
which
essentially
says
to
be
respectful
of
your
fellow
speakers
and
attendees
and
generally
be
excellent
to
each
other.
I've
shared
the
notes
in
the
chat
do
feel
free
to
drop
in
there
and
go
ahead
and
add
some
things.
A
C
Would
you
like
to
say
hello,
yeah,
absolutely
hi
everyone?
My
name
is
Hannah
Aubry
I'm,
the
community
manager
and
lead
of
fast
forward
fastly.
We
are
super
excited
to
be
super
fast.
Excuse
me
supporting
kubernetes
through
our
fast
forward
program
and
really
excited
to
talk
about
comms
regarding
kubernetes,
starting
to
switch
over
to
fastly.
A
All
right,
I
think
we
are
good
to
drop
into
it.
Then
first
we
usually
go
over
updates
and
big
wins
and
it
looks
like
we
do
have
one
sujay.
E
I
added
this,
but
it's
in
his
name,
because
obviously
he
was
the
one
pushing
this
forward,
so
yeah
congrats
to
that
I
think
that
it
was
it's
always
good
when
we
have
outcomes
of
the
work
that
we
start
and
we've
been
having
more
and
more
of
these
Spotlight
article.
So
I
think
it's
important
to
to
mention
the
work
of
social
in
this
and
and
and
well
it's
out
there
and
it's
a
good
example
for
us.
E
D
A
A
We
have
some
other
question.
I
wanted
to
ask
about
that.
How
long
did
that?
Take
you
CJ?
No,
that
was
quick.
E
A
Yeah,
that's
saying
something
awesome!
Thank
you.
So
much
for
doing
that
and
I'm
really
excited
to
see
us
making
progress
on
this.
So
from
that
we
will
dive
into
new
items
I'm
going
to
move.
The
events
lead
discussion
to
the
end.
Also
Avinash
isn't
here.
So
let's
go
ahead
with
Arno
and
Hannah.
F
Yeah
hi,
so
basically
I'm
gonna
restart
this
so
hi
I'm
Anno
I'm,
the
teacher
for
humanities
C
for
the
infrastructure
group,
so
basically
micro
operate
on
the
line
infrastructure
for
the
project
so,
and
one
of
the
things
we
are
responsible
for
for
is
the
case.io,
which
is
the
home
for
all
the
officials
binary
published
by
the
project.
F
We
in
order
to
migrate
and
have
full
ownership
for
the
community
we
reach
out
to
fastly
to
help
us
do
the
migration
to
a
community
infrastructure,
so
firstly,
I
agree
to
do
a
huge
donation
of
10
petabyte
per
month.
Thank
you
to
them
for
that,
and
we
need
to
make
the
migration
happen
in
order
to
do
that,
we
want
to
give
a
heads
up
to
the
community
or
an
abuser,
because
we
have
10.
We
are
close
to
seven
petabytes
per
month,
which
it's
huge
in
terms
of
egress
costs.
F
So
we
need
to
give
a
heads
up
to
the
community
and
user
by
that.
So
I
put
a
draft
here
to
basically
get
the
word
out
redoing
that
migration,
so
I
need
help
with
view
comments.
Stuff
also
ask
Anna
to
join
us
here,
so
we
can
talk
about
what
we
can
put
in
that
incoming
blog
posts
or
things
we
can.
We
can
do
I'm,
not
an
expert
at
communication,
so
this
is
my
call
file.
F
Don't
think
it
are
basically
it's
a
endpoint
mostly
used
to
either
download
Cube,
CT
or
battery,
or
mainly
used
by
CI,
to
download
any
official
binary
we
built
and
permission
so
every
time
you
cut
every
time
we
have
an
official
release.
We
publish
this
binary
there
and
basically
to
be
more
explicit
in
terms
of
infrastructure.
It's
a
GCS
packet
owned
by
Google
and
we
publicly
serve
and
that
go
to
retreat
owned
by
us.
F
The
I
would
say
the
only
difference
is
we
don't
do
a
redirect
from
Google
to
we
don't
do
a
reject
of
traffic
from
Google
to
us.
We
basically
do
a
that's
over.
That's
what
we're
doing
so.
The
idea
is
to
put
fastly
in
front
of
a
GCS
bucket,
either
owned
by
Google
or
owned
by
us
yeah.
We
serve
now
those
binary
through
the
fasting
Network.
F
Right,
it's
a
ritual
we're
doing
and
also
changing
the
backing.
At
the
same
time,.
A
F
We
want
to
do
that
basically
say:
Okay
redirect
fastly
and
we
Shield
the
bucket
with
fasting
and
that's
become
I
would
say
transparent
to
the
end
users.
Now
we
can
do
whatever
we
want
in
the
backend,
so
use
S3
use
cloud.
Cloudflare
Auto
you
use
the
new
fastly
Object
Store
service.
We
can
do
whatever
you
want.
F
E
C
E
Idea
of
decoupling
things
that
are
Quest
fixed
in
Google
resources
and
perhaps
making
it
less
a
couple
going
forward.
F
A
F
A
F
So
that's
that's,
I
would
say
the
main.
That's
why
we
need
to
give
the
notice
because
we
have
P.
We
have
entities
like
government,
slash
companies
having
strict
Network
boundaries,
so
we
need
to
basically
give
an
update
like
oh
yeah.
Your
CI
will
break
because
we
now
use
fasting.
Why
are
you
blocking
fasting
yeah.
A
A
A
A
I'm
curious,
you
don't
have
to
go
into
this
level
of
detail
right
now.
If
you
don't
want
to,
but
you
mentioned
that
wasn't
Cube
CTL
was
it
or
was
it
the
cubelet
that.
F
It
depends
on
how
you
install
the
cluster,
so
if
you
rely
only
on
binaries,
you
basically
say
in
your
bootstrap
system
downloads,
all
the
binaries
needed
to
I
started
cluster
I
would
say
if
you
pick,
for
example,
because
the
Eye
Tower
repo
pivot
is
the
right
way,
you're
going
to
use
that
endpoint
to
basically
done
the
old
binaries.
F
A
What
it
sounded
like
so
the
artifacts
hosted
in
dl.cades.io
are
completely
separate
from
the
ones
in
registered.
F
B
Totally
separate
from
registering
generally
bootstrapping.
F
A
A
My
teammates
just
recently
did
that
all
right,
I
think
I've
got
a
general
sense
of
what
it
is
and
what
it
does.
The
next
questions
I'm
going
to
ask
are
about
the
kinds
of
media
we
need
to
make
I
guess
we'll
go
ahead
and
do
that.
But
if
you
do
have
any
questions
about
how
this
works,
anyone
else
you
are
welcome
to
ask.
Of
course,.
D
F
F
B
F
A
I,
like
that
approach,
it
gives
us
a
bit
more
room
to
make
it
what
we
want
it
to
be
rather
than
like.
Okay,
it
needs
to
be
out
right.
This
second
gotcha,
which
often
happens
yeah.
F
F
F
A
So
it
sounds
like
we
need
to
start
this
process
of
figuring
out
what
we
want
to
put
in
the
blog
post
draft
drafting
it
all
of
that
and
as
we're
figuring
out
the
information
that's
going
to
go
into
the
blog
post
and
How
likely
it
is
to
affect
users
and
how
severely
you'll
be
able
to
make
some
decisions
on
exactly
how
much
notice
you
think
is
needed
for
the
change.
A
E
I
would
say
that
so
if
we
can
agree
with
a
specific
goal,
which
is
to
create
something
that
communicates
a
specific
change
that
the
community
needs
to
hear
about,
we
can
work
with
that
from
there
from
that
and
and
and
well.
We
just
need
someone
to
to
start
with
I
I
can
obviously
or
any
of
the
people
that
are
shadowing,
do
any
kind
of
specific
assistance
on
the
processes
Etc,
but
the
content
itself
Etc.
That's
the
thing
that
I
I
think
we
need
to
start.
E
F
E
No
I
haven't
read
it
yet.
I
I
I
have
not
saw
that
link.
So
what
I
will
do
is
that
in
the
next
couple
of
days,
I
I
will
go
through
them
and
we
can
continue
any
discussion
through
until
next
meeting
to
select
I'll
send
you
some
some
feedbacks
messages,
doubts
and
we
can
continue
to
to
work
on
this
I
seem
to
have
you
mentioned
something
that
around
any
kind
of
specific
deadline.
So
do
you
have
any
Targets
date
for
this
specifically?
F
F
G
F
B
A
And
a
bit
of
insight
into
the
blogging
process,
which
Rodrigo
made
a
wonderful
guide,
for
we
usually
start
the
draft
of
the
blog
post,
either
in
Google
Docs
or
in
hack
MD,
something
that's
really
easy
to
collaborate
on
and
then
once
it's
in
a
good
State
and
we
think
it's
pretty
much
ready.
Then
we
go
ahead
and
do
the
pr
we
want
to
make
as
few
changes
on
the
pull
request
as
possible.
A
A
F
B
E
The
same
kind
of
so
yeah,
so
we're
set
I'll,
take
a
look
first
me
and
the
rest
of
the
Cubs
team
and
I'll
just
ping.
You
back
with
any
initial
doubts,
so
that
we
can
then
advance
to
the
stages
which
will
eventually
end
with
a
PR
being
opens.
G
E
We
do
and
do
most
of
the
heavy
lifting
so
just
focus
on
the
content
and
I'll
see
some
initial
comments
in
the
in
the
next
week.
Okay,.
F
Next
week,
I'm
out
for
on
vacation
starting
I,
think
Wednesday.
So
if
you
have
like
any
question,
feel
free
to
Ping,
Anna
I'll
be
around
being
me
but
expert
Jillian
in
my
answer.
So
if
you
have
any
questions
regarding
fastly,
you
can
pick
and
after
this
she's
in
the
slack
channel
for
this
team.
D
A
That
would
write
this
in
the
node
says:
Next
Step,
so
I
know
you're
out
on
Wednesday
always
welcome
to
ask.
B
F
A
A
F
A
B
A
B
A
Oh
for
our
folks,
I
meant
to
mention
for
that
not
important
for
them
anyway,
but
for
our
folks,
if
you
are
excited
about
that
discussion
and
want
to
be
involved
with
it,
keep
an
eye
on
the
slack
Channel
control.
Xcom
sounds
like
we'll
be
doing
some
Communications
there
and,
of
course
you
can
work
with
Frederico
as
he
starts
the
getting
the
draft
together.
If
you
Frederico,
do
you
want
folks
to
particularly
volunteer
at
this
point
or
anything
else,
you'd
like
to
add
for
how
folks
can
help
you
yeah.
E
Well,
so
I'll
personally
take
the
take
a
stab
at
it
in
terms
of
reading,
but
anyone
that
wants
to
follow
up
with
the
process.
E
It
is
welcome
so
I'm,
not
necessarily
I'm,
not
necessarily
asking
for
for
people,
but
if
someone
wants
to
to
to
to
follow
the
follow
eight
along
and
eventually
take
even
a
more
active
role
in
it.
I'm
also
fine.
A
I
think
that's
perfect.
This
is
going
to
be
a
pretty
sensitive
communication,
since
it
is
end
user
impacting
so
it
might
be
a
good
one
to
follow
along
and
just
kind
of
watch.
B
A
Next
item
nitish
discussions
about
Spotlight
blog
on
Sig
release.
Please
tell
us
about
it.
D
I
joined
the
last
week's
Sig
release,
meet
and
discussed
about
the
plans
of
writing.
This
Spotlight
blog
and
sick
release,
I
explained
them
the
process
and
a
couple
of
questions
that
I
was
basically
asked
about.
What
like
what
is
a
spotlight
blog
and
another
thing
that
was
being
asked
about
was
how
many
times
you
need
to
update
the
six,
a
spotlight
blog
on
sick
release.
D
So
I
answered
this
question
depending
on
what
are
the
requirements
and
they
actually
provided
with
me
some
the
folks
that
I
can
reach
out
to
now
and
I.
Think
every
one
of
them
like
this
idea
very
interesting
and
is
ready
to
go
ahead
with
the
writing,
a
spotlight
blog
on
the
sick
release,
but,
as
a
certain
I
generally
have
some
questions
on
how
to
proceed
further.
With
writing
a
spotlight
blog
on
the
sick
release,
because
on
the
Sig
release
lag,
Channel,
I.
D
Guess
there
was
a
discussion
that
there
are
a
lot
of
things
that
are
happening
on
release.
So
are
there
any
chances
if
we
can
provide
with
a
dividing
the
blog
into
two
parts?
The
first
part
is
focusing
on
the
the
first
project.
Under
the
sick
release,
whereas
the
second
blog
is
focusing
upon
the
second
sub
project
on
the
Sig
release,
this
is
my
first
concern
other
than
that.
D
D
So
these
are
the
updates
for
up
till
now,
but
I
generally
have
some
question
like:
should
we
actually
move
with
dividing
the
six
release
blog
into
two
parts
and
another
thing
how
many
questions
should
be
like?
What
is
the
proper
length
of
the
blog
that
we
should
be
targeting
for
the
securities.
A
War
Rodrigo:
do
you
want
to
start
or
shall
I.
E
I
either
work.
We
can
open
them
you're
at
the
board.
B
E
A
So
the
questions
currently
are:
is
there
a
length
requirement
for
Six
Spotlight
blog
posts?
What
other
questions
do
you
have
that
we
should
answer.
E
A
B
E
Yeah,
so
the
goal
would
would
be
a
spot
like
a
spotlight.
Welcome,
seek
release
and
the
question
is
the
two:
what
would
be
the
two
topics
that
are
there?
B
E
B
B
D
Basically,
the
first
product
ideas
they
mentioned
about
the
release
process
and
the
second
one
was
basically
about
release
Engineering
Process.
So
do
we
actually
need
to
address
all
these
sub
projects
within
one
block,
because
I
have
seen
some
of
the
six
portrait
blogs
that
generally
have
explaining
the
process
of
the
two
sub-projects
within
the
one
block,
but
since
it
is
released,
do
we
actually
need.
E
Yeah,
you
I
understand
your
thing,
because
SQL
is
specifically
takes
two
different,
very
different
roles
because
of
the
way
that
kubernetes
released
happened.
They
are
like
a
normal
sick
in
some
ways,
with
their
monthly
with
their
weekly
meetings
Etc,
but
they
also
have
their
the
the
the
the
the
the
kubernetes
release
process
going
on,
so
they
are
actually
also
very
directly
involved
in
the
white
Active
Release
team
itself
works.
E
So
with
that
in
mind,
I
see
absolutely
no
problem
in
having
in
splitting
it
up
as
long
as
you
as
you
consider
with
as
per
yoga
questions
with
people
in
civil
list,
that
you
have
enough
content
and
people
participating
to
to
fill
them
up.
E
Obviously,
if,
if
you
have
two
blocks
two
blog
articles,
one
of
which
is
like
three
lines,
then
it
doesn't
make
a
lot
of
sense,
but
I,
don't
think
that's
the
case
right
you,
you
will
have
one
around
the
way
that
sieg
released
Works
out
mostly
outside
of
the
release
process
itself,
and
then
you
can
also
have
another
one
focusing
on
the
role
of
Sig
release
during
this.
The
kubernetes
release
process.
I
think
that's
the
the
idea.
E
If,
if
so
I
think
it
makes
absolute
sense,
you
can
Target
to
to,
you
can
run
it
too
and
if
at
any
time,
there's
a
drop
for
or
an
inability
to
proceed
with
one.
You
all
will
you
you
can
either
just
focus
on
one
or
integrate
some
of
some
of
the
information.
D
Cool,
so
is
there
any
blog
limit
that
I
should
consider,
while
writing
the
blog
and,
if
specific,
questions,
how
many
questions.
B
A
A
B
B
E
Link
incoming
oh
I'm,
not
in
I'm
on
my
mobile
I,
forgot
because
I'm
on
another
meeting
on
here
on
the
other
side
yeah.
How
will
I.
B
E
E
A
Long
answer
to
a
short
question,
but
yeah,
oh
good,
so
definitely
refer
to
that
for
guidance.
As
far
as
link
goes,
I,
don't
think
that
there's
any
specific
requirement
unless
you
added
one
Federico.
H
E
E
H
C
F
E
An
email
but
I
I
I,
don't
think
that
I
think
that
to
them,
if
I
understood
the
the
the
the
concern
here
is
not
so
much
that
that
the
that
it
can
be
too
small,
but
perhaps
that
it
can
be
too
extensive
and
you
need
to
split
it
up.
I.
Don't
necessarily
think
that
this.
E
You
need
to
split
things
up
in
series
for
it
to
make
sense,
because
I
mean
a
reading
when
you're
reading
you're,
not
you,
you
can
stop
and
resume
at
any
time.
But
obviously,
if
you
have
like
a
very
long
interview
that
you
we
want
to
publish,
we
haven't
had
that
yet
I
can
also
see
it
being
published
in
a
series
like
one
two,
three
whatever
until
then
I
I,
don't
think
that
I
don't
have
a
personal
opinion
on
how
long
it
should
be.
E
E
That
makes
it
a
bit
more
solid
than
a
couple
of
lines
and
I
would
only
be
concerned
with
being
excessive.
If
we're
talking
about
like
three
four
five
pages
of
stuff
there,
that
can
become
very
hard
to
read.
So
that
would
be
my
Approach.
What
do
you
think.
H
A
E
E
Obviously
the
the
duck
stem
will
have
their
own
say
on
this
right,
because
the
this
is
for
the
website.
So
it's
their
review
and
their
input
there
will
will
also
be
the
decided.
A
Federico
I'll
help
you
navigate.
It
also
I
want
to
say
that
this
doing
a
Blog
about
how
the
release
process
works.
It
was
actually
a
task
that
I
put
on
our
board
back
when
we
had
the
old
board
like
two
years
ago,
two
plus
years
ago,
that
I
always
wanted
to
do
and
I
wanted
to
make
illustrations
for
it
to
help
explain
the
process,
so
I
would
love
to
work
with
you
on
that
I.
Never
did
it
and
I
always
felt
bad
about
it,
and
now
it's
gonna
happen
because
of
you.
Thank
you.
D
Yes,
just
a
final
question:
is
there
any
specific
deadline
that
we're
considering
before
the
block
should
be
published?
I
just
have
a
thinking
of
keeping
in
mind,
making
the
blog
published
before
the
next
release
could
happen.
So
just
in
case.
What
do
you
all
think
of
this.
E
You
have
that,
for
example,
you
just
mentioned
the
until
the
next
release.
You
could
do
that
or
you
could
say
like
well
I
think
that,
realistically
speaking,
two
months
would
be
doable,
so
you
just
Target
that
and
if,
if
it,
if
it's
doable
perfect,
if
you
don't
actually
make
it,
it's
not
like
this.
E
Nothing
lost
right,
because
that's
the
self-imposed
deadline
that
it's
not
like
in
other
blog
articles,
in
which
we
have
an
external
like
the
one
we've
mentioned
before,
there's
a
change
and
we
need
to
actually
make
it
make
it
before
that
change
happens.
In
this
case,
it
doesn't
really
matter.
E
I
would
just
suggest
not
keeping
it
like
a
very
like
six
months
for
this,
it's
too
much
because
by
by
then
it
everyone
has
already
forgotten.
So
as
long
as
you
keep
a
a
realistic
deadline
in
mind
and
you,
if,
if
you
can't
communicate
it
with
those
that
you
interview,
sometimes
that
also
works,
because
people
tend
to
juggle
around
deadlines
and
if
you
don't
have
a
deadline
for
your
for
your.
For
your
part,
it's
like
those
projects
that
I
eat
at
the
set
end
of
a
kanban
Cameron
column.
E
They
never
get
done
it's.
So
it's
also
important
if
you
can
arrange
with
the
people
that
you
interview
a
specific
deadline
and
so
that
they
can
also
work
around
it.
E
Don't
feel
free
to
ping
me
directly
or
in
the
channel
at
any
time
right.
This
is
like
an
open,
Community,
Based
assets,
so
just
put
it
out
there
and
I'll
myself
and
others
will
will
do
our
best.
Just.
A
The
next
item
I
had
in
the
notes-
and
we
already
are
down
to
13
minutes-
left
and
also
Avinash
in
here,
but
we
were
going
to
have
a
discussion
about
the
events,
lead
role
and
how,
like
we
kind
of,
don't
really
have
events
to
manage
right
now,
because
we
got
rid
of
the
main
one
that
we
had
to
deal
with.
A
A
We
have
a
subproject
lead
definition
in
the
handbook
now,
so
anyone
is
ever
interested
in
that
you're.
Welcome
to
talk
with
us
about
it,
I
think
maybe
becoming
a
lead
and
then
becoming
sub-project
lead,
maybe
makes
sense
as
a
path
totally
figuring
this
stuff
out
as
we
go.
A
Don't
know
I
think
that's
a
strong
possibility,
so
whooping
Avinash
about
that.
As
always,
if
you
ever
have
any
questions
about
rolls
and
shadows
and
stuff
like
that,
reach
out
to
the
group
reach
out
to
the
specific
roll
leads
lead
roles,
people
that
you
want
to
learn
more
about
and
just
ask
questions.
A
All
right
and
with
that
I
think
we'll
move
into
the
board.
Another
word:
Yar,
yar
I,
think
that's
the
plank
anyway.
A
A
A
Back
they
said
as
soon
as
the
blog
post
goes
out.
They
want
to
ship
it
30
days
ish
after
that.
B
A
H
H
So
there's
notes
yeah.
Just
on
that
point,
I
will
say
that.
H
H
Like
we
sent
it
to
all
customers
because
of
the
ec2-ness
of
it
all,
and
we
can't
necessarily
identify
a
kubernetes
cluster
from
you
know
like
a
VMware
host.
H
A
B
H
B
A
A
All
right,
I'm
done
typing.
Thank
you
for
that
point.
Now
we
have
eight
minutes
left
to
go
through
the
entire
order.
Chris.
This
is
all
your
fault,
I'm.
Sorry,
very
much,
not
your
fault!
It's
very
much,
my
fault!
Why
are
meeting
so
long
when
I
run
them
anyway,.
A
I'm
gonna
skip
the
six
Spotlight
stuff
for
the
moment
we
can
come
back
to
it
at
the
end.
If
we
have
time,
we
have
talked
about
six
spotlights
a
lot.
We
can
also
update
on
those
asynchronously.
A
Also
zapier
automation,
Imran
hasn't
been
able
to
be
on
for
a
while.
Maybe
we
should
ping
our
Tech
lead
folks
see.
What's.
H
Over
I
suspect,
if
Bob
does
it
he'll
be
like
okay,
it's.
H
A
That
also
reminds
me
that
I
got
access
to
create
the
ticket
for
making
sure
we
have
enough
money
to
add
Masters
on
to
the
buffer
account
and
I.
Didn't
do
it
yet
so.
A
That's
not
too
bad,
but
yes,
it's
good
to
know
that
zapier
bits
are
in
motion.
A
A
A
Sounds
like
that's
still
in
the
right
spot
for
to-do
items.
Spotlight
new
contributor,
Workshop
still
waiting.
Also
there
forever
comms
guidelines
for
sensitive
security
topics
or
I.
Think
I
should
change
this
to
also
sensitive
end
user,
impacting
topics
foreign
things,
but
it'd
be
good.
If
we
could
record
some
of
the
things
that
we
do
for
this
dl.kates.io
change
as
guidelines
for
sensitive
end
user
impacting
stuff.
A
All
right
and
that's
going
to
be
in
progress
because
we're
going
to
work
on
stuff,
no,
not
ready
for
review
in
progress
cool
retrospective.
If
you
want
to
do
that,
you
gotta
make
it
happen.
I
guess
notify
comms
team
when
a
new
issue
is
created,
maybe
someday
we'll
figure
that
out
and
slackbot
is
still
broken.
All
right.
H
H
B
A
Frederico
any
other
updates
about
any
of
the
other
spotlights
that
are
in
progress.
Yeah.
E
So
I've
sent
an
an
update
to
description
of
of
some
of
the
topics
that
we
can
discuss
or
the
architecture
one
much
like
the
one
on
release.
It
will
be
based
on
different
topics
for
the
sub
projects.
Still
no
so
no
feedback,
but
I've
made
it
recently
anyway.
E
The
the
this
I
wasn't
here
last
week,
but
I'm
not
sure.
If
I
had
already
mentioned
this
or
I
guess
we
talked
that
during
in
kubecon
at
least
with
you
right,
because
I
I
didn't
max
geising
in
person
and
live
I
went
trying
to
find
you
Chris,
but
I.
B
E
But,
but
so
what
we
ended
up
gaining
from
from
that
that
I've
I've
talked
with
the
cap,
Reading
Club
lead
and
they've
stopped
doing
it.
So
obviously
that
one
is
out
and
I've
also
talked
with
Noah
about.
It
would
be
interesting
to
make
something
about
how
this
kubecon
contributors
Summit
are
organized.
E
E
I
know
that
we
also
have
like
a
c
contrabass
blog
Spotlight
article
being
worked
on.
This
could
be
in
parallel
with
that
one,
because
it's
a
specific
thing,
although
it's
made
by
sick
controvers,
so
I,
don't
think
it's
it
overlaps
with
it.
It
would
actually
be
interesting.
It's
much
like
the
what
we
just
discussed
about
Sig
release
right,
that's
the
normal
day-to-day
job
and
then
there's
one
specific
thing
that
requires
a
specific
attention.
A
Perfect,
we
have
just
a
minute
left,
nitish
and
FICA
you're,
both
working
on
six
spotlights.
Do
you
want
to
give
a
quick
update
on
your
status?
A
D
B
A
G
Updates
is
that
there
is
no
previous
blog
and
say
contribute,
so
this
is
going
to
be
the
first
time
someone's
gonna
write
a
blog
on
this,
so
I
need
to
research
a
little
bit.
That's
the
reason
that
I'm
reading
the
repository
and
all
the
documents
out
there
I
also
reached
out
Federico
about
the
same.
G
So
he
also
guided
me
over
the
same,
like
I
should
read
the
meeting
agenda
and
first
understand
everything
and
what
all
is
going
on
and
say,
contributes
and
then
I'll
frame
the
questions
around
it
since
I
don't
have
exactly
the
idea
of
the
questions
that
needs
to
be
framed
so
yeah.
That's
my
update,
I'm
still
standing
and
I've
framed
some
questions,
but
I'll
come
with
the
questions
once
I'm
done
with
all.
A
Yeah
I
think
we'll
bring
Bob
or
the
Bob
or
Josh.
The
Emeritus
leads
into
that
as
well.
G
E
You
will
end
up
with
that's
true,
but
in
the
end,
if
you're
asking
questions
about
things
that
what
are
the
next
step
forward,
what
is
the
direction
of
the
group
Etc?
This
will
technically
most
likely
end
up
with
with
being
people
that
are
shares,
or
at
least
are
sublets
of
some
projects.
A
Because
you
need
kind
of
a
broad
overview
of
the
sick
to
be
able
to
do
it.
And
if
you
have
that
level
of
overview,
you're,
probably
a
chair
or
about
to
be
one.
G
H
E
No,
this
is
the
kind
of
thing
that,
if
you
make
it
work
honestly
I
think
that
most
people
have
had
interviews
with
one
or
two.
That's
the
most
common,
but
I
don't
see
any
problem.
If
you,
if
you
have
more
people
yeah
it
can,
it
could
be
more
complex
to
make
it
to
edited,
but
it
can
also
be
more
fulfilling.
So
just
just
go
ahead
have
fun
and
we
will
all
learn
in
the
process.
A
G
A
And
also
the
annual
report
for
each
group,
my
Phuket
resource,
because
we
just
pr'd
in
our
annual
report
for
Sig
contribex.
So
you
can
see
information
about
stuff.
We
did
for
the
last
release,
which
isn't
really
anything
because
we're
sick
and
tripex
and
our
sub
projects,
and
some
of
the
like
major
updates,
are
in
the
annual
report
as
well.