►
Description
[SIG ContribEx] Weekly Contributor Comms Meeting for 2023090
A
Welcome
everyone
to
the
first
edition
of
the
context
calls
for
the
September
Edition.
My
name
is
Natasha
and
I'll
be
your
host
today,
Castle
is
of
course
not
available
today,
so
before
starting
further
I
would
like
to
inform
you
all
that
this
call
is
under
the
cncf
code
of
conduct,
which
generally
seems
to
be
respectful
and
but
towards
each
other
and
on
each
other's
considerations
along
the
call,
even
before
moving
further.
A
C
A
B
B
That
was
the
new
endpoints.
You
know
a
lot
like
the
registry
change.
It
was
announced
in
you
know
August,
which
is
weird
to
say.
That's
the
last
month
now,
but
yeah
mid-august,
it
was
announced.
Packages.Case.Io
was
it
was
the
place
to
go
and
due
to
reasons
it's
those
older,
yum
and
apt
dot,
kubernetes.io
domains
are
disappearing,
so
the
blog
post
went
out
yesterday,
I'll
paste
it
here
in
chat.
I'll
put
it
in
the
notes
too.
B
C
B
And
read
and
consume.
Basically,
the
impact
is
not
nearly
as
impactful
as
the
registry
change,
because
it's
not
everything
it's
just
those
folks
that,
like
installed
Linux
and
then
installed
kubernetes
from
their.
You
know
normal
package
manager
of
choice.
So,
like
vanilla
kubernetes,
we
did
Bob
looked
at
some
stats.
It
was
like
under
10,
right
or
so
of
all
clusters.
B
Kind
of
thing
is
what
it
looked
like,
so
yeah
the
the
amount
of
traffic
it's
getting
indicates
that
we
could
kind
of
broadcast
the
message
out
a
little
ahead
of
the
official
announcement,
so
the
email
went
out
yesterday
before
the
blog
post
and
people
started
posting
on
social
media
about
it.
There
is
some
talk,
some
discussion
in
the
thread
there
I
was
fine
with
it.
Given
that
I
basically
said
the
like
the
moment
this
came
up.
I
was
like
you
know.
B
D
B
Thought
it
went
well
surprisingly
well,
but
if
you
see
the
people
that
were
on
it,
it's
kind
of
like
oh
yeah,
okay
makes
sense,
you
know
so
Marco
was
running
it
and
then
Tim
Bob
Jeremy
myself.
We
all
kind
of
came
in
and
said
change
this
to
that
blah
blah
blah
and
out
the
door.
It
went
so
yet
again,
someone
coming
to
us
saying:
hey,
we
need
messaging
and
comms
and
we
provided
so
yeah.
It
was
a
very
short
notice.
B
B
C
B
Been
yet
to
maybe
you
know
we
have
the
well,
maybe
you
don't
know
the
new,
the
new
contributor
kubernetes
Channel
versus
the
kubernetes,
like
org
members
Channel
like
we
should
probably
put
it
out
there
for
sure
if
the
bot's,
not
in
that
new
account
yet
we'll
need
to
add
it
or
that
new
channel
we'll
need
to
add
the
Channel
with
so
forth,
so
yeah
it
might
be
good
to
broadcast
some
stuff
in
slack.
We
definitely
need
to
get
some
tweets
together
about
it.
Obviously,
zapier
did
its
thing
and
sent
it
out
the
door.
B
So
I
found
that
was
interesting,
so
the
registry
change
was
like
the
first
time
we
really
kind
of
pressed
Amazon
Microsoft
everybody
else
to
kind
of
figure
out
where
their
customers
are,
or
just
send
out
a
blanket
message
that
these
changes
are
happening
to
the
registry.
It
impacts
all
of
us
that
I,
don't
think,
is
necessary
on
this
one.
This
is
very
much
people
like
kubernetes
the
hard
way.
Actually,
that's,
not
even
kubernetes
the
hard
way.
B
It's
people
that
are
like
oh
I'm,
using
ansible
to
install
my
clusters
on
all
my
you
know,
spoke
Linux,
OS,
distro,
thingy,
that
kind
of
thing
so
or
yeah
I'm,
using
terraform
and
packages
and
so
forth,
so
on,
as
opposed
to
pulling
down
binaries,
which
is
what
a
lot
of
our
people
do.
It
seems
like
and
the
the
athenium
repos
are
just
the
bear
is
kind
of
it
almost
feels
Legacy
to
be
honest
with
you
and
nowadays
to
just
have
I
mean
yeah.
B
You
could
do
a
one-line
install
of
a
Kind
cluster
I
guess
it
makes
sense
to
do
a
one-line
install
of
a
kubernetes
cluster
at
some
point.
But
then
there's
all
the
configuration
everything
behind
it,
so
I
don't
know
anyways.
My
opinion
does
not
matter
any.
The
big
thing
is,
is
the
comms
is
out
the
door
and
we
needed
to
light
it
up
next
week.
A
All
right,
I
think
we
can
proceed
further.
The
next
item
we
have
generally
in
in
the
updates
are
the
big
wins,
is
Spotlight
blog
for
the
release
team
project.
The
pr
is
out
and
I
think
Frederico
suggested.
A
bunch
of
changes
at
first
were
minor
changes
and
I
think
this
is
the
Pia
that
we're
talking
about
right,
I've
linked
it
in
the
notes
as
well.
So
regarding
this
PR
Frederick
I
have
mentioned
all
the
points
whatever
we
need
to
consider
something
that
we
were
concerned
about
this
thing.
A
The
release
team
is
the
only
is
the
only
way
I
have
confirmed
it
from
the
release
time
itself,
and
they
have
suggested
that
this
is
one
of
the
ways
they
are
actually
trying
to
say
it
and
I
think
we
can
modify
this
thing
as
well.
We
have
Tim
as
well
Tim
actually
reviewed
this
blog
completely
Tim
thanks
for
joining
in,
would
you
mind,
sharing
your
some
stuff
about
the
spotlight
blog
for
the
release.
E
A
D
Yeah
I
mean
we
can
discuss
what
you
prefer,
but
the
the
one
of
the
reasons
that
I
updated
the
documentation
last
time
was
because
I
was
doing
it
like
that
opening
a
placeholder
PR
for
websites
and
dealing
with
it
in
the
contributor
site.
First,
but
after
talking
with
Tim,
he
expressed
that
it.
It
was
better
to
start
with
real
content
on
both
sides
from
the
start
and
then
reflect
the
changes
again
in
the
in
the
website.
D
E
I'd
like
to
clarify
something
I
think
there's
different
roles
here
so
as
an
approver.
What
I
want
is
two
things
that
are
ready
to
go
as
an
approver
I
want
to
say:
okay,
this
contributor
site
thing
is
all
good.
The
date's
right,
it's
you
know
it's
ready
to
go,
and
one
of
the
things
that
I'll
need
is
that
the
the
other
blog
is
ready
to
go
so
that
I've
got
to
have
two
things.
E
You
know
whatever,
that's
what
that's
what
so,
when
it's
ready
for
approval,
you
want
to
have
both
sides
there,
but
if
you're
still
thinking
okay
well,
what's
the
story
we're
going
to
tell?
Are
we
going
to
have
these
pictures
we're
gonna
have
to
you
know,
like
you
weren't
you
like
whatever,
if
I'm
doing
early
editing
and
like
the
real
question
is
like,
maybe
this
is
still
almost
ready
for
review.
E
A
E
Then,
on
hold
when
we're
doing
reviewing,
then
I
think
you
know
get
one
get
one
thing
right
so
yeah
this.
This
might
need
a
bit
of
Polish,
but
you
know
we
we
know
the
date.
We
know
that
we
are
ready
to
go
like
this,
isn't
going
to
need
more
work
and
another
week
of
round
trips
not
going
to
happen
and
doing
that
twice.
That's
going
to
be
painful.
D
Well,
absolutely
I
mean
the.
What
we
have
at
the
moment
is
is
not
doing
it
twice.
So
I
completely
agree
in
general,
every
blog
that
we've
published
always
benefits
from
some
editing
one
way
or
the
other.
Well,
this
one
I've
commented
on
it.
You
you
suggested
changes
as
well,
so
this
is
the
kind.
This
round
of
editing
is
the
one
that
should
be
concentrated
on
a
single
place,
which
is
the
contributor
size.
That's
that's
absolutely
clear.
The
the
instructions
right
now
the
guidelines
are
that
we
pick
up
them.
D
So
we
prepare
things
that,
to
the
best
of
our
knowledge,
our
the
Creator,
the
interviewer,
the
person
that
did
the
markdown
are
okay
to
submit
and
we
submit
the
same
in
both
website
and
contributors.
It's
the
desired
outcome.
Obviously
some
things
do
not
go
into
the
website
at
all,
but
for
the
for
those
that
do
we
submit
the
same
content
in
both
we
put
the
website
on
hold
linking
to
the
contributor
site
discussion.
D
We
drilled
out
the
discussion
in
the
contributor
side
with
all
the
nits
and
spellings
and
clarifications,
and
once
that
one
is
done,
the
person
that
opened
the
PRS
needs
to
essentially
copy
the
content
from
one
and
the
other
and
make
any
metadata
adjustments
that
are
different
from
the
other,
but
in
in
principle
no
additional
editing
will
be
required
at
that
stage
because
it's
it's
been
done
in
in
the
other.
Nor
should-
and
it
is
I
think
this
is
a
concern.
D
Nor
should
you
fill
that
at
every
stage
of
the
editing
process
in
contributor
sites,
you
need
to
reflect
it
reflect
it
back
into
the
website.
Only
the
finalized
version
would
need
to
be
added
there.
The
difference
is
that
we
should
start
opening
boat
with
the
same
content
instead
of
opening
it
contributor
side
and
having
an
empty
file
at
the
at
the
website.
D
C
A
D
Yeah,
because
we're
still
so
I
I'm,
not
sure
if
what
I
generally
do
is
that
I
submit
things
with
around
one
week
of
work
plans,
because
I
expect
people
to
have
commits
changes,
not
not
hurry
about
it.
The
last
one
was
an
exception,
because
Tim
mentioned
and
and
and
and
and
and
well
that
we
had
a
release
coming,
so
we
need
to
do
it
in
one
day
or
something,
but
it
was
very
the
very
little
things
needed
to
be
to
be
changed.
D
So
if
you
have
a
Target
date
for
one
week,
then,
depending
on
it
progresses,
you
can
feel
if
it's
ready
or
not
if
there
are
still
open
and
likely
release,
we
don't
have
a
fixed
deadline.
So
if
it's,
if
for
some
reason,
we
can't
clarify
things
at
before
the
plan
dates,
you
can
just
change
it.
Two
days
ahead
right.
B
B
A
B
E
C
B
B
Let's
see
I
know,
netliff
I
can
get
stuck
and
just
cancel
the
job,
and
that
doesn't
necessarily
come
back,
but
it
says
it
completed
everything
successfully,
which
is
weird
so
yeah,
look
at
the
container
method
or
just
do
a
Hugo
serve
DF.
If
you
have
Hugo
on
your
machine,
if
it
works,
there
you're
good.
A
E
B
E
B
And
it's
not
an
absolute
link,
it's
it's
technically,
a
relative
link.
The
content
en
part
is
only
apparent.
You
only
see
that
in
the
repo
itself
on
the
website,
the
the
localization
is
done
automatically
based
off.
You
know,
browser
settings
or
you
know,
people
clicking
into
the
right
language.
So
if
you
take
off
content,
slash
en.
D
E
D
A
D
A
D
A
A
A
A
C
A
D
D
D
But
so
we
have
five
articles
on
sync
architecture
with
the
plus
one
which
is
is
to
be
made
after
I
have
a
one-to-one
ever
voice
conversation
during
the
cigarette
meeting
further
down
the
roads.
I
I
think
that
I
have
the
the
the
size
of
the
interviews.
I
think
are
is
enough
to
do
like
a
series
in
which
we
will
just
go
through
each
step.
Projects
individually,
perhaps
saying
that
this
is
part
of
a
six
six
Spotlight
series
focusing
on
the
architecture,
subprojects,
and
we
will
have
five
of
them.
D
Maybe
after
they
are
all
published,
we
can
edit
the
files
to
link
to
one
another.
I,
don't
know
if
this
is
usually
done
or
not,
but
I
mean
this
is
post-processing
more
than
anything
but
yeah,
that's
the
that
would
be
the
plan,
so
conformance
project
is
in
under
review
in
XMD
and
I'll
open
the
pr
for
that
one.
Next
one
will
be
production
Readiness,
which
is
also
done,
and
afterwards
we
will
have
API
and
code
organization
and
and
another
one.
D
A
A
D
D
The
reason
why
this
is
resurfaced
by
the
way
and
and
that's
part
of
the
question
that
I've
asked
in
the
interview
was
that
this
got
picked
up
as
a
cncf
sponsored
activity
so
cool.
That
was
why
it
changed
a
short
version,
no
updates,
because
we're
still
under
the
the
we
still
haven't,
reached
the
deadline
for
Carlos
to
reply,
but
I'll
I'll
ping
him
during
the
week.
B
So
we
need
to
get
together
on
that,
there's
a
lot
of
opaqueness
to
it,
because
we
don't
necessarily
have
access
to
the
Google
Drive
zapier
does
so
we
can't
see,
what's
necessarily
in
the
drive,
unless
zapier
can
present
it
to
us
as
like
a
sample
right
when
you're
making
the
thing.
So
it's
really
difficult
to
see
which
part
of
the
process
is
broken
here
versus
what's
working,
and
then
we
have
to
scale
that
out.
B
So
we
have
to
figure
out
why
it's
not
working
all
of
a
sudden
and
all
those
parts
and
pieces
need
to
come
together.
Shoejay,
Nigel
and
I
need
to
schedule
a
meeting
got
a
message
from
Nigel
last
night
saying
he
was
going
to
forward
me.
Something
for
me
to
look
at
I
haven't
looked
at
it
yet.
Obviously
the
first
thing
I've
done
today
work
wise
is
this.
So
it's
a
work
in
progress,
so
it
it's
not
complicated.
It's
just
opaque
and
we
have
to
work
with
that.
B
C
A
F
C
F
F
A
C
A
A
Engineering
subproject,
the
latest
updater
is
that
we're
going
to
attend
some
release
engineering
meetings
and
by
today
we
don't
have
any
specific
update
over
it.
But
the
fact
that
I
think
these
engineering
meetings
are
going
to
be
started
soon
from
Monday
itself
and
working
with
Marcus
and
Carlos
for
the
LFX
mentorship
will
be
a
great
point
to
understand
how
the
things
are
internally.
Working
for
the
release,
engineering
subproject
so
by
September,
one
I
think
there
are
no
updates
meetings.
C
A
C
B
Yeah
Castle
Learning
just
sit
down
and
like
just
go
through
these
things,
but
my
schedule
and
her
schedule
have
not
lined
up
at
all.
This
would
have
been
a
good
week,
but
she
was
at
Google
next
right,
like
you
know,
it's
just
how
it
goes
sometimes
so
yeah
we
need
to
sit
down
and
just
Hammer
at
him
at
some
point
and
I
hope
to
have
some
time
to
do
exactly
that
soon.
C
A
B
B
B
Emphasis
we're
putting
on
if
you're
a
shadow,
the
expectation
is
you'll,
become
a
lead
of
said
thing
you're
shadowing
and
we
just
need
to
make
sure
all
those
rulebooks
have
that.
Basically,
so
you
know
it
might
just
be
one
of
those
things
where
I
create
some
messaging
ship
it
to
caslin
and
then
see
what
everybody
else
thinks
and
then
we
just
kind
of
add
it
to
everything.
A
D
A
B
Obviously
I
did
markdown
and
not
HTML,
it's
just
that
for
starters,
but
yeah
you
just
since
it's
already
in
the
re,
the
directory,
it's
supposed
to
be
in
you
just
reference
that
the
subdirectory
and
the
image
and
this
works
on
my
machine
so
feel
free
to.
Let
me
add
this
to
the
notes
or
to
the
board.
I
should
say.