►
From YouTube: [SIG ContribEx] Biweekly Meeting for 20230913
Description
[SIG ContribEx] Biweekly Meeting for 20230913
A
Also,
at
the
beginning
of
the
meeting
we
like
to
offer
the
opportunity
for
any
new
folks
on
the
call
to
introduce
themselves
I'm,
not
sure
if
we
have
anyone
new
today,
but
if
you
would
like
to
say
hello,
introduce
yourself
tell
us
a
little
bit
about
why
you're
here,
you
may
do
so
now.
You
may
also
do
so
in
the
chat.
You
also
don't
have
to
do
so
at
all,
because
it's
totally
optional,
so
I'll
leave
that
open
for
a
minute.
If
you
would
like
to
introduce
yourself.
A
A
B
That
that
seems,
accurate,
I
think
if
I
recall
correctly,
because
Monday
was
so
long
ago
that
things
are
progressing
smoothly.
The
only
major
issue
that
I
think
is
outstanding
right
now
is
getting
the
contributor
social
up
and
running
based
on
track
and
get
on
locations
that
are
not
yeah
looked
or
crazy,
expensive,
but
other
than
that
things
are
going
well.
Cfp
is
coming
to
a
close
soon,
so
there
should
be
reminders
about.
The
cfp
did
I
miss
anything
Josh.
C
D
D
C
F
A
D
A
E
A
G
A
G
G
F
F
So
we
did
a
whole
bunch
of
not
a
whole
bunch,
but
a
amount
of
social
media
around
the
Legacy
package,
repost
freezing
and
eventually
yeah
there's
some
on
the
schedule
still
so
I
think
we're
good
there,
but
feel
free
to
take
a
look.
We
discussed
on
the
last
meeting
other
social
networks-
there's
a
kubernetes
group
so
on
LinkedIn,
might
be
interesting
to
just
post
things.
There
see
how
it
goes
kind
of
thing.
F
A
A
E
F
F
H
F
G
H
H
So
like
NCD
was
previously
a
kubernetes
project,
I
started
under
core
OS
Pro
s,
donated
to
kubernetes
that
might
have
been
with
the
red
hat
acquisition.
I
I,
don't
remember,
but
then
there
was
enough
people
at
the
time
interested
in
at
CD
that
they
wanted
to
spin
on
be
their
own
thing
and
now
they're
coming
back.
C
Yeah
and
there
was
a
a
complete
and
total
change
of
maintainership
in
the
meantime,
oh
yeah,
Okay
cool,
so
and
and
really
there's
still
arguments
either
way,
but
our
lead,
maintainer
Marek,
is
also
a
kubernetes
contributor
and
when
he's
working
on
NCD,
he
really
really
misses
the
infrastructure
that
we
have
for
our
contributions
and
releases
and
everything
else
and
and-
and
that
was
the
main
reason
for
for
sort
of
deciding
to
come
back
to
kubernetes.
No.
H
C
Well,
you
might
find
people
in
there
who
are
lapsed.
Orc
members,
you
know,
but
they
have
been
at
some
time.
The
I
mean
the
nice
thing
is
that
from
the
time
that
Marek
posted
his
call
for
help
a
year
and
a
half
ago,
we
built
back
up
the
xcd
contributor
base,
not
that
we
couldn't
always
use
more
contributors.
C
Eight
or
ten
reviewer
level
contributors,
so
it's
no
longer
a
project
in
in
danger
of
falling
off
a
cliff
the.
But
you
know
the
the
weird
thing
about
it
is
going
to
be
that
we
do
have
like
20
of
our
user
base.
That
uses
that
CD
for
things
that
are
not
kubernetes,
that
that
set
of
use
cases
still
exists.
C
But
I
mean
that
said.
One
of
the
things
that
we
talked
about
is
that
the
test
coverage
that
we
do
have
for
etcd,
which
we
really
want
to
improve
in
getting
access
to
test
grid,
was
one
of
the
reasons
for
coming
back
I.
We
really
only
actually
routinely
test
the
functionality
that
kubernetes
uses
like
there
are
features
that
kubernetes
doesn't
use
of
at
CD,
and
they
don't
really
have
automated
testing.
C
Oh
yeah,
so,
like
we
did
a
user
survey
where
we
asked
about
one
in
particular
that
we
actually
kind
of
wanted
to
get
rid
of
to
find
out
if
anybody
was
using
it
because
we're
like
we
don't
know
that
this
actually
works.
Is
anybody
using
this
turns
out?
The
answer
was
yes,
so
we
can't
get
rid
of
that
particular
feature
the
or,
if
we
do
it's
going
to
need
to
be
phased
out
over
the
course
of
a
while
yeah.
So.
G
H
Themselves,
just
because
we
we
especially
like
prr
the
production
Readiness
review,
that
is
something
they
they
lack
and
having
like
a
lot
of
the
people
in
API
machinery
have
like
good
foundational
knowledge
of
how
you
know
what
the
edge
cases
would
be
if
something
is
being
implemented.
So
yeah,
it's
it's
just
a
better.
You
know,
pool
of
EX,
like
experts,
yep.
C
F
C
The
project
anyway,
they've
been
invited
to
the
contributor
Summit
they've,
already
submitted
a
couple
of
potential
sessions.
Early
Merrick
tells
me
that
they
have,
and-
and
you
know-
and
we
have
a
checklist.
One
thing
to
know
is
that
their
list
of
org
members
is
not
a
complete
listing
of
the
major
contributors
that
the
org
membership
process
for
FCD
was
a
new
thing,
and
then
you
know
when,
when
the
project
decided,
they
were
going
to
try
to
become
a
Sig.
C
We
start
kind
of
halted,
trying
to
get
people
to
sign
up
for
it,
because
we're
gonna
now
get
them
to
sign
up
for
kubernetes
work
membership
so
do
expect
a
several
org
membership
requests
related
to
NCD.
Now
that
it's
a
Sig,
although,
as
Bob
pointed
out,
not
very
many,
because
most
people
are
members
already.
G
C
H
C
G
C
C
Yeah
yeah,
the
big
bit
of
work
is
for
the
GitHub
admins,
because
we
need
to
get
all
of
that
under
the
kubernetes
system,
the
which
was
one
of
the
one
of
the
desired
features
in
in
becoming
a
Sig
again
because
again,
you
know
no,
no
ownership
management
tools
as
an
independent
project,
the,
but
the
repos
are
not
currently
set
up
to
use
kubernetes
owners
files.
So
we'll
need
to
clean
that
up
and
then
put
it
under
prow.
C
C
Not
required
the
answer
is
no
okay
good,
because
I
mean
for
our
current
contributors.
I
think
all
of
them
are
already
kubernetes
CLA
signatories,
but
we've
had
people
in
the
past
who
are
not
so
the
and
NCD
well,
it
was
an
independent
project
was
dco,
which
is
something
I
would
love
kubernetes
to
be,
but
this
would.
G
A
Be
wouldn't
it
no
hey,
shall
we
move
on
from
NCD?
We
can
always
talk
more
about
it
at
the
end,
there's
a
lot
of
interesting
stuff.
There
I
feel
like
we
covered
a
lot
of
it,
though
all
right.
Let's
move
on
to
our
next
agenda
item,
which
is
contributor,
documentation,
anything
new
there,
any
news
on
the
a
new
contributor.
G
A
A
F
F
A
A
All
right,
then,
moving
on
from
GitHub
management
to
elections,
we've
already
I
I
mentioned
that
the
comms
folks
are
working
on
stuff
for
the
steering
election.
I
didn't
mention
that
in
more
detail
we
are
wrapping
up
those
comms
really
because
the
Voting
is
going
to
end
at
the
end
of
this
month.
September
26th
I
think
is
the
last
day
to
vote.
23Rd
is
the
last
day
for
exceptions,
so
we've
got
several
comes
going
out
about
those
end
dates,
and
then
there
will
be.
What
do
we
call?
Those?
G
H
F
C
H
C
C
B
C
Actually
like
for
somebody
who
has
experience
working
on
flask,
I,
wouldn't
say
it
would
be
more
than
two
weeks,
the
so
in
two
weeks,
part-time
right,
the
so
the
because
some
of
it
is
like
we
need
one
of
the
areas
we
have
no
testing
at
all.
Is
we
have
no
automated
testing
for
the
container
image
and-
and
that's
what's
actually
tripped
us
up
a
number
of
times
is
that
I've
I've
had
subtle
issues
with
the
container
image
build
so.
D
C
G
C
D
C
G
A
H
However,
the
importing
users
feature
is
hard
locked
at
the
mailing
list
level
to
only
allow
a
hundred
people
added
to
it
per
24
hours.
It
doesn't
matter
it
doesn't
matter
who
you
are
it
doesn't
matter
if
you're
on
multiple,
like
different
owner,
that's
a
little
bit
and
I
sort
of
understand
the
the
reasons
why
to
try
and
avoid
some
of
the
the
spam
stuff
that
happens.
That
way
we
can.
H
H
H
The
other
method
and
which
sort
of
is
similar
to
what
we
do
right
now
is.
We
have
a
essentially
like
our
current
groups.
Script
script
like
little
little
tool
that
does
it
and
hack
that
up
and
you
basically
launch
it
in
a
part
of
this
access
to
the
secret
to
be
able
to
you
know,
do
these
that's
essentially
what
Kristoff
did
to
migrate
kadev
itself.
A
C
Yeah
registry,
the
one
thing
I
should
figure
at
some
point,
is
what
what
the
the
sort
of
workflow
is
and
then
share
somewhere.
It's
obvious
of
hey
I
want
to
create
document
X
that
needs
to
belong
to
the
community
like
like
for
me,
I
end
up
helping
with
a
lot
of
surveys
right
how
do
I
make
sure
and
for
those
it's
actually
kind
of
critically
important
that
they
belong
to
kubernetes.io,
because
otherwise
we
have
no
way
to
make
sure
that
say
the
data
expires.
C
The
and
that's
one
of
the
reasons
why
we've
been
pushing
people
towards
cncf
Survey
Monkey,
but
that
has
its
own
problems,
the
not
the
least
of
which
is
that
only
two
of
our
community
members
can
have
access
to
it.
So
the
it'd
be
nice
to
use
Google
Docs
more,
but
I
need
a
workflow
rate
where
somebody
requests
a
survey
and
they
get
a
survey,
that's
actually
owned
by
our
account
and
not
by
their
personal
account.
H
So
that
is
currently
possible
with
the
contribute
share
drive
as
long
as
it's
created
under
in
the
conjecture
drive.
It's
we're
good
on
ownership,
oh
cool.
What
I
would
like
to
do
long
term?
This
does
involve
discussion
with
like
steering
is
like
we
just
create
either
one
giant
shared
drive
for
all
the
sigs
or
each
Sig
gets
its
own
shared
drive
and
that
just
becomes
the
default
location
for
everybody
to
save
their
stuff
because
it
doesn't
matter
if
you're,
a
corporate
user.
H
C
C
The
and
and
that's
been
the
main
stumbling
block.
We
used
to
say
it
was
prohibited
because
China
has
uneven
access
to
Google
Docs,
but
it
turns
out
that
China
has
uneven
access
to
SurveyMonkey
as
well.
So
the
there's
there's
no
Advantage,
there's
no
Advantage
for
SurveyMonkey
anymore,
the
it's
not
even
particularly
cncf
branded.
When
you
actually
look
at
the
surveys.
C
C
No,
we
because
we
actually
specifically
looked
at
that
when
they
took
it
away,
because
we
wanted
it
for
a
specific
survey
and
we
talked
to
the
cncf
and
they
looked
at
Survey
Monkey
stuff
and
it
would
have
I
think
it
literally
would
have
ate
been
something
like
a
six
thousand
dollar
I
elevation
in
the
cost
of
the
account
in
order
to
get
access
to
that
feature
and
we're
just
like
no,
the
just
run
run
three
different
surveys.
Don't
don't
even
try
to
do
that?
The
so
yeah!
B
B
F
A
C
A
F
E
There's
like
the
thing
right
that
problems
that
go
away
on
their
own,
you
know
come
back
on
their
own,
but
all
of
the
automation
so
far
is
working.
Redoing.
The
sick
contracts,
like
I've,
seen
those
videos
show
up
working
group,
LTS
is
working.
Sig
docs
is
working,
I
haven't
seen
a
Sig
in
for
meeting
pop
up
since
I
asked
them
to
turn
off
the
auto
record,
so
either
they
haven't
had
a
meeting
or
they
forgot
to
turn
the
recording
on,
but
yeah
right
now,
things
seem
to
be
like
Smooth.
E
E
E
F
E
Got
it
got
it?
It
was
weird
because
it
only
disconnected
on
the
Sig
contracts
channel,
the
other
ones
were
taking
over
just
fine,
but
we're
probably
we're
probably
at
a
place
to
start
or
onboarding,
some
more
groups
on
to
zapier
I'm
in
a
little
bit
of
a
crunch.
Right
now
so
I
I
I'm,
hesitant
to
offer
that
service
until
after
open
source
Summit
is
over.
A
G
A
A
C
C
H
E
G
H
A
D
G
B
So
I
will
say
that
I'm
trying
to
get
the
there
was
interest
a
couple
weeks
ago
in
finally
getting
the
non-code
project
re-rolling
again
with
enough
people
showing
interest
and
I'm
trying
to
put
together
a
doodle
to
get
some
people
working
on
that
and
I
was
thinking
of
putting
a
session
together,
but
I'm
probably
going
to
do
it
through
the
unconference
instead
of
through
the
cfp,
because
I
think
it
would
make
way
more
sense.
That
way.
F
G
C
C
E
E
D
You're
interested
in
helping
with
it,
you
come
you
get
to
play
with
it,
you
get
to
work
on
it
and
then
maybe
people
can
pick
up
some
of
the
projects.
Like
the
contributor
Summit
session.
The
contributor
site
session
we
did
last
time
was
completely
me
going.
I
have
no
idea
why
we
proposed
this,
so
my
name
somehow
ended
up
on
it.
So
I
literally
just
stood
up.
There
said
here's,
the
repo
good
luck,
there's.