►
From YouTube: [SIG ContribEx] Weekly Meeting for 20220706
Description
[SIG ContribEx] Weekly Meeting for 20220706
A
Hello,
everyone
and
welcome
to
the
july
6th
bi-weekly
sick
contributes
meeting.
This
is
a
general
reminder
for
folks.
These
calls
are
recorded
and
will
be
posted
sometime
later
on
youtube
and
we
abide
by
the
cncf
code
of
conduct,
which
essentially
boils
down
to
please
be
excellent
to
each
other.
B
A
It
is
very
much
appreciated
now
with
that,
let's
kick
right
into
business
office
hours.
I
don't
think
we
have
any
real
status
update
on
that.
So
let's
go
ahead
and
kick
over
to
community
meeting,
especially
as
laura.
I
know
you
have
to
go.
C
Yes,
unfortunately,
I
will
so
I
left
a
couple
notes
in
here,
but
there
is
some
initial
interest
in
new
hosts
new
blood,
so
yay,
that's
very
exciting.
We've
had
some
folks
in
the
contributors
channel
reach
out,
saying
they'd
be
interested
in
hosting
or
otherwise
helping,
so
I'm
going
to
be
reaching
out
to
them
this
week.
C
However,
I
wanted
to
bring
up
considering
the
current
charter
discussions
that
are
going
on
for
steering
I'm
wondering
if
an
experienced
host
should
be
hosting
this
upcoming
community
meeting,
because
I
highly
doubt
that
that
won't
be
talked
about
at
the
meeting.
Sorry.
C
Oh
sorry,
the
steering
charter,
okay.
A
A
Yeah
exactly
just.
A
As
a
general
fyi,
this
is
the
topic.
The
primary
topic
of
the
community
steering
meeting
this
thursday.
A
A
What
time
one
moment
so
tomorrow
at
11
or
11
30
a.m,
central
time
yeah!
Okay,
so
is.
C
C
One
big
thing
I
wanted
to
bring
up
was
also
that's
the
same
week.
I
I
think
I
have
the
right
week.
It's
the
same
week
as
dev
upstate
seattle.
I
think
I'm
gonna
be
online
for
it.
I
probably
will
be
on
just
my
laptop,
because
I
have
to
be
in
seattle
for
that.
But
with
that
in
mind,
helping
would
be
lovely,
but
if
I
can
be
the
host
I
figured
I
could
easily
pull
that
out
as
the
host
to
manage
grumpiness.
A
See
the
let's
see
the
the
community
meeting
is
set
for
the
21st,
I
believe
so
we
can.
We
can
keep
it
on
the
agenda.
Let's
let
us
we
will.
You
know,
go
for
some
experienced
hosts
the
clock
for
basically
feedback
on.
It
will
end
on
the
27th
okay,
so
maybe
by
then
at
least
a
lot
of
the
like
other
comments,
will
at
least
be
resolved.
C
Okay,
I
still
have
yet
to
curate
the
discussion
topics
so
far.
No
one's
really
flagged
anything
for
me.
Yet
so
I'm
gonna
have
to
go
digging,
but
I
figured
that's
gonna
likely
be
one
of
the
topics.
People
will
want
to
talk
about.
So
that's
why
I
wanted
to
ask
if
anybody
had
any
thoughts
or
comments
on
making
sure
this
upcoming
community
meeting
is
not
too
divisive
and
productive
is
really.
What
we
want
it
to
be.
Productive
is
important.
Yeah.
A
The
the
big
thing
we'll
just
be,
we
will
definitely
want
to
have
multiple
moderators.
Multiple
people
essentially
listed
as
co-hosts,
and
you
know
we
can.
We
can
talk
out
of
band
about
yeah,
getting
the
crew
together
for
that
one.
C
Correct
and
noah
I'm
still
trying
to
find
the
public
steering
list.
I
should
be
a
google
group,
but
I
don't
have
it
handy
so.
C
A
A
Steering
at
kubernetes
io
there.
C
C
C
D
C
D
That
we
need
to
figure
out
moderators,
yeah
I'll
sign
up
for
moderator.
I
think,
by
that
time
of
day
we
should
be
either
close
to
done,
or
I
can
step
away
and.
A
Then
jason.
D
B
C
It's
no
one's
really
commented
a
ton
on
the
issue
yet
so
I
still
have
that
open.
There
was
a.
I
have
not
gotten
a
chance
to
review
the.
What
was
it
labels
yeah?
It.
C
Yeah
I
haven't,
I
haven't
gotten
a
chance
to
swing
back
and
review
that
I
think
I
just
wrote.
Thank
you.
This
was
really
helpful,
but
I
haven't
actually
like
left
a
review,
so
we're
waiting
on
that
right
now,
no
one's
responded
to
my
thread.
Call
out
asking
for
topics.
C
C
F
Oh
no,
it
is
so
I
just
wanted
to
like
give
an
update
on
the
labels
thing.
So
I
created
that
pr,
I
that
sort
of
slipped
off
my
radar.
I
saw
that
bob
and
christoph
left
a
few
comments
there
so
christoph
had
con
like
had
a
point
about
following
the
necessary
process
and
bob's
suggestion
was
basically
creating
another
issue
template
in
k
community.
That
is,
would
this
label
be
used
outside
for
topics
outside
k
community.
F
So
I
will
respond
back
on
that
on
the
issue.
That's
sorry!
It
slipped
off
my
radar,
but
like
I'll
get
back
to
it
this
week.
E
A
Okay,
any
other
community
meeting
related
items.
A
Okay,
that
takes
us
to
summits
honestly,
I
have
not
kicked
off.
This
kicked
off
starting
things,
yet
I've
been
a
little
busy,
but
I'm
hoping
to
like
send
out
the
doodle
poll
and
all
that
other
fun
stuff
relatively
soon
by
end
of
week,
or
you
know,
I
should
say
end
of
monday
at
the
last
latest.
A
Okay,
mentoring.
A
I
don't
think
we
have.
Paris
is
not
on
the
line.
I
know
that
the
sig
app
6cli
thing
is
going
on
for
group
mentoring,.
G
I
don't
know
what
status
yeah.
H
So
we
are
planning
to
keep
off.
On
the
mid
of
august,
we
have
sent
the
the
pro
the
calling
for
the
mentoring
in
the
six
clients,
apps
mailing
list
and
yeah.
We
are
working
on
that.
I
Six
to
seven
members
for
each
of
the
six,
as
mentioned
and
by
the
end
of
july,
the
applications
will
be
closed
and
we're
planning
to
kick
off
around
in
the
middle
of
august,
as
I
think
I
said
so,
that's
the
status
of
it.
A
Sorry
I
hit
my
heart.
Remove
button,
that's
good!
That's
you
know
pretty
solid.
We
usually
aim
for
you
know
six
to
eight
total.
That's
you
know
turn
in
the
middle.
A
A
Okay,
go
over
to
community
management.
A
Okay,
we'll
kick
it
over
to
marketing.
Castling
cannot
be
here,
but
she,
like,
I
don't
know
who
would
drop
the
note
in
there.
H
So
I
have
dropped
it
here,
so
basically
the
comms
has
been
sent
for
the
engine
survey
and
at
present
we
are
doing
the
tweets
regarding
the
annual
survey.
The
help
wanted
section.
The
tweets
are
going
out
and
there
were
few
backlog
tweets
on
the
kubernetes
release
cycle
1.24
of
feature
blogs,
so
that
rules
that
were
also
out
this
week.
So
that's
that's.
The
update.
A
It's
basically
been
greenlit
by
the
cncf.
The
big
thing
that
we
have
to
find
out
right
now
is
actually
like
how
like
this,
the
scenes
have
has
greenlit
paying
for
it,
but
how
do
we
add
a
like?
Does
buffer
support,
multiple
people,
logging
into
the
same
account
or
like
a
group,
account
okay,
because
we
basically
need
to
set
them,
as
the
billing
manager
is
the
main
thing.
D
Who
is
them
the
lf?
Okay
yeah?
Last
I
checked
you
can
have
like
five
accounts
for
free,
I
think,
and
then
they
start
charging
you.
But
let
me
double
check.
Okay,.
A
A
Then
yeah
it's
it's
basically
just
kicking
off,
creating
the
account
and
getting
the
lf
in
there.
As
the
you
know,
billing
entity.
A
Now,
if
anyone
in
particular
wants
to
from
from
the
marketing
team
wants
to
kick
that
off,
we
can
also
start
that
discus
like
continue
that
discussion
in
slack.
If
we
want
to
go
that
route.
F
Yeah,
actually,
I
am
new
in
this
community
in
communities
and
contributing
to
the
communities
docs
in
the
contribute
section.
So
can
anyone
give
me
an
idea
about
what
this
meeting
about
like
I
attended
this
particular
weekly
meet
first
time.
A
This
is
the
bi-weekly
sick,
contrabex
meeting.
We
basically
do
a
like,
read
out
an
update
on
one
of
our
sub
projects
and
have
some
general
broader
discussions
on
things
that
impact
you
know
contrabex
or
the
project
as
a
whole.
A
Drop
a
link
to
our
notes
here,
but
right
now
we
were
basically
discussing
an
issue
regarding
our
contributor.coms
subproject
and
their
access
to
an
account
for
buffer
and
how
that's
going
to
get
essentially
like
paid
for.
F
Okay
and
one
more
thing
that
I
want
to
mention
here,
is
like
I
attended
the
monthly
meet
with
ray,
so
at
that
time
he
assigned
me
to
a
pr.
F
Wrangler,
but
the
person
with
me
I
got
like
ray
got
connected,
maybe
is
not
replying
so
what
I.
A
Have
to
do
now,
so
if
you
open
a
pr
the
easiest
way
to
do
it
is
to
look
like
it
look
at
the
other
reviewers
that
are
suggested
or
to
find
the
owner's
file
that
is
sort
of
the
parent.
For
the
thing
that
you
are
opening
a
pr
against
and
finding
some
of
the
other
reviewers
and
approvers
there
to
reach
out
to
usually
again.
The
kci
bot
will
also
suggest
people
for
like
approval
that
you
can
ping.
A
Okay,
contributor
docs:
I
have
no
updates
here.
J
I
I
want
to
say
that
I'm
going
to
be
picking
up
with
the
the
non-code
guide
again
in
a
next
couple
of
weeks.
J
The
first
time
around
we
did
a
whole
lot
of
enumeration
and
listing,
and
this
time
I
want
to
focus
a
lot
on
task.
Identification
maybe
see
if
we
can
possibly
do
some
github
integration,
how
we
can
get
people
to
actually
find
the
tasks
and
roles
as
opposed
to
being
as
generic
as
we
were
last
time.
A
I
know
there's
a
big
discoverability
issue
for
a
lot
of
this
stuff.
Anything
in
github
is
is
especially
like
docs,
it's
a
huge
thing
to
find,
which
is
one
of
the
big
reasons
why
we
try
and
surface
as
much
as
possible
on
the
contributor
site,
which
is
actually
much
better
indexed.
A
There's
also
still
an
outstanding
issue
in
the
contributor
site,
repo
regarding
rewriting
the
ingestion
script,
so
the
just
as
a
quick
thing
for
other
folks.
A
lot
of
the
content
on
the
contributor
site
is
not
actually
hosted
in
the
contributor
site
repo.
A
It
is
hosted
elsewhere
in
the
project,
and
it
is
unfortunately
like
markdown.
Well
is
it
it
is
sort
of
a
standard.
It
is
not
quite
a
standard
and
so
like
the
hugo
version
of
markdown,
which
is
what
the
contributor
site
uses
in
the
the
github
flavor
of
markdown,
don't
always
align
and
there's
also
issues
with
like
links
and
a
few
other
things.
So
there
is
this
thing
that
I
am
both
proud
and
terribly
disgusted
with.
A
In
that
I
wrote
a
bash
clergy
thing
that
pulls
all
this
stuff
in
and
basically
reformats
everything
correctly,
and
there
has
been
an
outstanding
project
to
like
rewrite
it
in
go
or
some
other
language.
That
is
a
little
bit
more
supportable,
preferably
one
that
actually
can
read
the
markdown
and
like
auto,
check
links
and
things
like
that.
Instead
of
a
bunch
of
regexes
that
I
have
okay.
B
I
was
going
to
say
you
know
one
of
the
one
of
the
bits
to
simplify.
That
task
is
to
move
content
to
the
contributor
site
repo
so
that
we're
pulling
less.
I
mean,
there's
some
things
that
we're
always
going
to
have
to
pull
from
elsewhere
yep,
but
we
could
limit
how
much
stuff
we're
pulling
yeah,
which
would
make
it
less
difficult.
A
Yeah,
I
think
the
last
there
was
we
we,
I
think
we
got
consensus
on
moving
the
guide
over,
but
there's
a
lot
of
other
things
that
we
potentially
want
to
include
that
will
not
necessarily
live
in
there.
A
So
like
it's,
it's
still
a
I'd,
say
a
general
outstanding
problem.
The
guy,
definitely,
I
think,
should
go
over
there.
D
A
Well,
yeah,
the
the
big
thing
is
that,
like
a
lot
of
this
is
like
breaking
the
links
that
that
you
know
there
is
one
issue
that
has
broken
but
like.
A
And
how
it's
to
tell
detected
but
like
how
it's
it
fixes
links
is,
is
an
issue
because
it
like
oh
okay
because
like
if
it
exists
in
other
repo
relative
links
and
things
like
that
will
be
different.
Since
it's
now
living
in
a
new
location.
And
if
the
content
is
not
relative,
it
has
to
know
to
update
the
link
to
point
towards
actual
location
hub,
there's
an
issue
in
the
contributor
site,
which
outlines
a
lot
of
these
issues.
D
A
You
can
do
aliases,
but
that's
it
as
far
as
I
know,
and
the
reason
for
a
lot
of
this
is
to
basically
make
it
multi-language
aware.
So,
if
you
so,
if
you
want
for
localization
purposes
and
how
that
part
works
like
if
I
recall
correctly
in
any
case,
if
anyone
wants
to
like
take
on
rewriting
that
terrible
bash
script
in
go
or
something
else,
it
is
in
that
linked
issue,
because
I
think
it's
that
that
issue
yep.
A
Okay,
moving
over
to
github
management,
the
one
big
update
I
have
here
is:
we
have
that
we
did
the
callout
for
new
member
additional
new
member
coordinators.
I
don't
know,
I
don't
remember
if
that
form
has
closed
or
not
yet,
but
I
believe
several
people
applied
and
hopefully
getting
get
going
on
that
soon.
A
K
Okay,
so
I
have
assigned
myself
this
particular
issue
where,
like
the
articles
are
publishing
earlier
than
it's
supposed
to
be
published-
and
I
just
wanted
to
know
like
how
is
the
publishing
mechanism
here
in
hugo,
it's
hugo.
A
K
Yeah,
okay,
like
where
can
I
find
the
like
scheduling
system?
It
must
be
under
the
hack
directly.
No,
no.
A
There's
there's
no
there's
no
scheduling
system.
Oh
there
is.
A
A
Yeah
so
the
well,
the
the
thing
there's
a
command
in
hugo
to
publish
like
when
you
have
it
build
a
site
to
build
future
that
will
basically
just
has
to
have
that
omitted.
So
it
knows
to
not
build
new
new
docs,
so
that'd
be
like
in
the
make
file.
K
Okay,
if
I
understood
that
correctly,
like
this
issue,
is
not
related
to
code,
all
right
like
this
is
not
in
the
code
or
the
hugo
site.
It's
with
the
netlify
no.
A
It's
it's
in
the
the
make
file
which.
A
A
Okay,
open
discussion,
josh.
B
Yeah,
so
I
have
the
work
in
progress
pr
for
creating
the
election,
subproject
open
and
there's
two
things
we're
looking
for
that
one
is
I'm
looking
for
a
little
feedback
from
the
sig
before
we
finalize
that,
because
it
adds
some
new
things
I
mean
obviously
adds
the
election
cell
project
itself
adds
the
eventual
service
that
we're
going
to
offer
preference
elections
is
a
service
to
the
sigs,
because
we
have
the
technology
to
do
so.
B
The
but
it'll
involve
people
in
the
sig
right,
because
sigs
will
request
one,
and
then
somebody
with
permissions
on
the
community
repo
needs
to
review
and
approve
that
the
and
the
other
part
of
that
is
I'd
like
to
hear
from
anybody
who's
interested
in
participating
in
the
election
sub
project,
either
on
the
policy
or
the
technical
side.
B
So
on
on
the
policy
side,
we're
obviously
gonna
be
taking
part
of
the
current
steering
discussions
and
if
you
look
at
the
steering
discussions,
the
oh
okay,
I
need
to
get
back
to
you
soon,
bob
on
that
one,
because
deadlines
might
matter
the
steering
discussions.
Those
are
flagged
number
of
areas
that
need
further
development,
even
after
the
current
pr
merges
or
whatever,
and
the
election
sub
project
should
be
actively
making
recommendations
and
word
smithing
on
that
kind
of
thing.
B
Second
thing
is:
we
actually
need
to
finish
selecting
the
elections
officers,
we
have
two
of
them
and
we
need
a
third
and
on
the
technical
side,
I'd
like
some
other
people.
I
need
some
other
people
who
understand
technically
how
alecto
works
and
can
help
support
it
and
can
help
review
elections
that
various
sigs
want
to
run
the
two
election
officers.
B
So
the
way
this
works
by
the
way
is
going
to
work
with
the
election
sub-project
is
the
election
cell
project
will
make
a
recommendation
to
the
current
steering
committee,
and
then
the
current
steering
committee
confirms
or
modifies
the
recommendation
on
who
becomes
the
election
officers
because,
ultimately
deciding
election
officers
is
a
power
of
the
steering
committee.
B
B
Oh
who's,
a
good
candidate,
you
know,
and
the
qualifications
are
basically
the
person
needs
to
be
a
long-time
trusted
community,
member
and
org
member
and
entitled
to
vote
and
and
for
any
of
the
new
people
we're
picking
given
what
they
know.
B
Now
they
have
to
be
offering
to
basically
do
this
for
two
years
I
mean
we
know
that
people's
life
circumstances
change
but
wow,
but
we're
we
need
at
least
one
election
officer
to
continue
next
year,
and
so
we're
going
to
have
two
new
election
officers,
one
we
need
to
at
least
keep
one
of
them.
So
we
don't
want
to
select
one
who
says
why?
B
No,
I
won't
be
able
to
do
it
next
year,
so
the
because
we
don't
want
noah
doing
it
again
next
year,
right
we're
trying
to
not
have
anybody
do
more
than
two
years
in
a
row
the
and
by
the
way,
that's
one
of
the
tasks
of
the
election
sub
project
is
document
all
of
this
stuff,
because
we
have
this
set
of
agreed
upon
rules,
but
they're
in
bullet
point
notes
form
in
a
kind
of
shorthand
deep
in
an
operational
document,
so
that
all
needs
to
be
surfaced
in
a
clear
way
and
eventually
end
up
on
the
contributor
site,
so
yeah
the
so
there's
a
bunch
to
do
with
the
election
subproject.
B
Even
if
you
are
never
going
to
be
an
elections
officer,
the
way
that
works
is
the
election
officers
automatically
become
part
of
the
subproject,
but
on
their
selection
as
officers,
if
not
sooner
than
that.
But
you
know
the
idea.
This
is
to
have
people
who
are
on
the
sub
project
who
are
working
on
election
stuff
for
the
project
year-round,
who
are
not
necessarily
directly
involved
with
the
steering
election.
B
The
so,
if
anybody's
interested,
I
yeah,
so
we
have
have
one
interest
there
and
if
anybody's
interested
put
it
down,
because
I'd
like
to
put
your
name
on
the
initial
sort
of
charter
and
then
we'll
go
from
there
based
on
the
work
that
people
can
actually
take
on.
Because
it's
a
sub
project
and
the
way
you're
a
member
is
that
you
actually
do
things.
B
If
not,
please
read
over
the
wip,
the
meat
of
it
is
the
two
readmes
there's
a
whole
bunch
of
files
being
changed,
but
it's
really
just
because
I'm
moving
a
lot
of
stuff
that
was
in
a
bad
file
structure
to
the
location.
Really
you
should
have
always
been
in,
but
the
two
things
that
you
actually
care
about
are
the
two
readmes
the
readme
directly
under
elections
and
then
the
readme
under
election
teams,
because
the
election
slash
teams
is
the
new
serve
elections
as
a
service.
B
A
Don't
remember
the
dates
on
the
top
of
my
head.
It's
in.
I
think
it's
in
the
code
of
conduct
the
cake
community
dirt,
but
I
know
it
is
soon
as
in
supposedly
kickoff
this
month
or
early
next
month,
or
something
like
that.
Okay,.
B
B
B
The
steering
committee
needs
to
prove
that
the
new
election
officers
need
to
set
a
timeline
and
that
all
needs
to
happen
by
like
august
1st,
so
we
don't
actually
have
a
lot
of
time,
the
and
on
top
of
which
there's
a
bunch
of
technical
stuff
to
be
done
with
our
instance
of
alecto
in
parallel
to
that
so
which,
by
the
way,
if
somebody's
interested
in
the
technical
side
of
the
elections,
I
am
would
be
thrilled
to
have
someone
shadow
me
on
that,
because
for
as
long
as
we're
running
on
a
system
where
I'm,
where
our
no
and
I
are
the
only
ones
who
understand
how
electro
works,
we're
always
in
danger
of
not
of
having
availability
problems.
B
B
B
A
B
So
we
need
to
follow
up
and
figure
that
out
right,
because
if
it's
not
true
that
everyone
in
the
project
can
see
it,
we
can't
do
it
in
the
same
electo
instance,
because
the
way
that
electo
is
designed
is
who
can
vote
in
election
is
restricted
according
to
rules.
But
everyone
in
the
world
can
see
the
election.
B
Which
is
on
purpose
right?
It's
what
we
want
for
steering,
but
it
might
not
be
what
we
want
for
a
code
of
conduct
committee,
previous
question
by
technical
society,
development
of
electo.
B
If
you
push
an
incorrectly
formatted
document,
either
nothing
will
happen
or
you'll
actually
break
that
particular
election.
So
so
that's
the
first
thing
later
on.
I
would
love
to
have
additional
people.
Helping
me
develop
a
lecture
right
now,
like
is
a
three
person
project,
which
means
we
could
desperately
use
more
because
it's
picking
up
usage,
it's
python,
flask,
so
easy
to
get
started
with
from
a
project
perspective
the.
But
the
first
thing
is
to
make
sure
that
our
oh
also
kubernetes
packaging.
B
You
know
because
we're
running
it
on
our
own
kubernetes
instance
the
so
but
but
the
first
thing
is
to
just
make
sure
our
own
use
of
electo
is
actually
operating
correctly.
B
B
Okay,
so
I
will
follow
up
with
everybody
expressed
interest
on
slack.
A
Then
we
can
call
it
there,
and
people
can
have
15
minutes
of
their
time
back.
Thanks
all
I'll
see
you
around
in
slack
and
see
you
in
two
weeks
on
this
call.