►
From YouTube: [SIG ContribEx] Biweekly Meeting for 20230802
Description
[SIG ContribEx] Biweekly Meeting for 20230802
A
Hello
and
welcome
everyone
to
the
August,
2nd
we're
in
August
now
August
2nd
2023
edition
of
the
Sig
contribbeck's
bi-weekly
meeting
as
usual
yeah.
How
is
it
August
already
if
it's
usual,
a
reminder
that
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?
A
A
B
The
good
news
is
we.
We
are
experimenting
in
a
good
way,
this
time,
which
is
we're
going
to
open
proposals
way
earlier
than
we
have
for
any
other
contributor
Summit
we're
not
going
to
close
them
early,
we're
just
going
to
open
them
really
early
and
we're
going
to
see
if
that
has
any
results
in
more
people
suggesting
things.
So
the.
D
B
B
B
B
This
time,
no
there's
more
there's
more
than
there
were
in
Amsterdam.
Oh,
the
cncf
event
seems
to
have
completely
abandoned
their
attempt
to
consolidate
the
Colo
events
and
have
allowed
have
have
accepted
Colo
events
that
are
kind
of
in
direct
conflict
with
each
other.
So
and
I
don't
know.
What's
up
with
that,
I
haven't
been
able
to
talk
to
the
chairs.
C
C
C
C
E
C
B
Yeah
so
amazing,
the
answer
I
mean
because
this
is
particularly
a
kubernetes
concern
right,
which
is
to
say,
hey.
You
know
the
impact
on
the
contributor
Summit
right,
I,
don't
actually
personally
care
that
much
about
the
rest
of
the
co-list
yeah,
but
the
impact
on
the
contributor
Summit
is
is
noticeable
again,
and
we
need
to
talk
about
that.
A
C
Have
a
feeling
that
will
be
the
general
feedback
after
North
America
yeah
yeah,
because
a
lot
of
that
was
again
centered
around
travel
and
not
around
the
larger
companies.
You
know
wanting
to
do
their
own
things,
because
now
there's
going
to
be
even
more
competition
like
if,
if
your
company
is
doing
something
like
you're
now
competing
with
all
the
colos
and
the
summit
and
the
various
other
activities.
E
E
A
A
B
B
A
A
E
E
B
B
D
C
B
B
C
C
F
C
C
C
E
D
B
G
E
A
Clear
process
or
like
a
well-defined
thing
that
we're
doing
I
think
maybe
the
best
thing
that
we
could
do
for
this
would
be
to
put
something
in
the
contributor
Summit
repo
about
what
has
been
done
in
the
past.
That
way,
people
in
the
future
could
decide
if
they
want
to
follow
precedent
for
any
future
situations.
Yeah.
D
C
B
If
you
follow
me
because
I,
among
other
things,
I
think,
there's
a
pretty
substantial
geographical
bias
in
that,
and-
and
you
know,
if
we're
doing
something
for
the
summit-
and
this
will
obviously
be
Nigel's
final
decision,
then
I
would
like
to
actually
do
a
call
in
case
there
are
people
like,
for
example,
a
major
contributor
from
India
who
passed
away
that
I.
Don't
just
don't
know
about.
A
A
We
had
to
get
increased
funding
because
we
added
Mastodon,
so
we
have
both
Twitter
and
Mastodon
or
zitter
or
whatever
people
are
calling
that
website
and
and
Mastodon,
and
so
we
had
to
change
our
billing
for
that
which
we
requested
through
the
cncf
and
that
got
approved
but
didn't
actually
get
updated.
So
things
got
wonky
with
buffer
for
a
minute
there,
a
very
long
minute
and
it's
fixed
now,
yay.
E
B
D
B
B
A
C
B
E
E
E
G
C
C
B
A
One
other
thing
in
contributor:
comms
that
I
want
to
mention
is
we
were
working
on
putting
together
some
materials
for
the
Sig
spotlight,
video
that
will
go
in
the
Keynotes
for
kubecon.
At
this
point,
it's
like
a
week
away,
so
I
have
sent
that
over
to
the
leads
to
decide
exactly
who's
going
to
be
on
that
video
and
like
finalize,
what's
going
to
be
in
it
and
all
of
that
kind
of
stuff,
I
figure
that's
relevant
to
share
in
this
meeting.
E
B
G
B
Actually,
honestly,
like
everybody,
saw,
the
the
whole
emergency
thing
took
a
declaration
by
Merrick,
Etc
and
CD
is
actually
in
a
lot
better
shape.
Now
part
of
what
was
going
on
with
the
project
is
as
long
as
Sam
and
joho
were
in
charge
of
it.
They
did
everything
in
the
good
and
ask
for
help.
Oh
rough,
and
you
know,
there's
been
FCD,
has
had
a
bunch
of
minor
contributors
for
a
while,
and
it
turns
out
that
if
you
just
ask
them
a
bunch
of
those
minor
contributors
are
willing
to
do
more.
C
B
A
A
G
Did
yeah
and
so
I
finally
picked
back
up
trying
to
do
the
configuration
for
kubernetes
for
enabling
Dev
containers
to
make
it
easier
to
contribute
yeah
set
up
Dev
environments
very
quickly
and
I
shared
with
Chris
Kessler
and
Bob.
The
my
essentially
POC
and
I'm
now,
finally,
actually
really
getting
ready
to
make
a
PR
the
next.
G
G
Okay,
yeah
I
have
a
lot
to
learn
and
then
I
will
write
it
up.
But
the
awesome
thing
is
I'm
also
creating
a
new
pattern
for
Dev
containers,
the
around
the
container
image
build
because
it
speeds
things
up
in
general,
and
so
we
want
it
to
be
a
kind
of
General
pattern.
So
I've
got
two
areas
of
innovation
to
try
to
write
out
the
simultaneously,
which
is
lots
of
fun.
G
E
E
E
G
C
It'll
it'll
probably
be
like
what
we
do
with
the
other
images
like
image
promotion.
The
nice
thing
again
is
like
that
means
it
will
like
automatically
be
bumped
with
every
kubernetes
release.
It
will
be
able
to
stay
in
lockstep
with
the
Go
version
and
all
the
dependencies
that
are
being
like
baked
into
it,
because,
like
there's
some
other
stuff
that
will
essentially
like
Auto
bump
things,
it
should
just
like
theoretically
make
it
easier
to
maintain
long
term.
E
B
A
B
A
A
A
A
But
yeah
so
he's
very
active
about
starting
to
learn
things
and
exploring
projects
that
he
could
do
and
we'll
probably
do
something
about
that
at
the
contributor
Summit
again
as
well,
because
last
time
at
the
contributor
Summit,
we
had
a
little
working
session
where
folks
got
together
and
made
a
little
bit
of
progress
on
that.
So.
E
A
A
C
C
C
So
what
I
think
we
should
wind
up
doing
is
like
we
can
rename
the
channel
to
raise
new
contributors
or
something
like
that.
So
that
way,
people
still
have
a
place
they
can
go
to
and
we
create
a
new
channel
like
conveys
maintainers
or
something
like
that,
and
that
is
specifically
for
essentially,
if
you
are
actively
contributing
the
project
like
I'll,
we
can
even
add
a
little
warning
message
when
you
join
like
hey.
C
C
And
basically,
then,
just
like
invite
our
known
maintainers,
like
we'll
toss
out
like
the
chair
in
tech,
leads
meeting.
We
can
ask
the
the
leads
themselves
to
bring
it
up
in
their
reading.
Hey,
please
join
this
since
I'm
at
the
kdev,
but
like
I
I
at
this
point,
I
think
we
just
need
to
kind
of
abandon
that
channel
for
messages
towards
our
major
contributor
base.
C
E
C
C
C
A
F
A
F
F
It's
not
happened
on
an
extremely
large
scale.
Luckily
we
caught
the
issue
early
on
at
like
stop
the
bleeding,
but
in
case
it
has
happened
to
you
just
like
feel
free
to
reach
out
on
GitHub
management
and
we'll
re-add
you
back
for
the
time
being.
We've
we've
deployed
a
fix
for
now,
so
as
soon
as
the
next
run
of
Parables
kicks
in,
that
should
reconcile
whatever
was
lost
and
like
just
to
make
sure
it
doesn't
happen
in
the
future
by
Monday
or
by
Tuesday.
B
C
A
F
G
B
Okay
for
elections,
nominations
are
open
for
the
code
of
conduct
election
committee
election.
This
is
the
first
time
that
they're
going
to
be
having
that
using
Electro,
which
is
a
change
because
in
the
past,
steering
has
not
wanted
to
have
the
election
in
public,
but
this
time
they're
trying
that
out
the
for
the
main
steering
election
and
by
the
way,
so
the
code
of
conduct
elections
happening
before
the
steering
election.
B
This
time,
because
we
want
to
avoid
the
problem
that
somebody
gets
elected
to
steering
and
then
runs
for
a
code
of
conduct
committee,
the
the.
However,
we
discovered
that
the
information
that
you
can't
be
on
both
is
not
actually
clearly
spelled
out
in
in
our
official
documentation
of
the
two
groups
and
so
expect
some
PRS
relatively
soon
to
clean
that
up.
B
B
B
C
B
A
A
C
B
C
One
other
thing
this
is
less
like
doesn't
I,
wouldn't
necessarily
say,
send
this
out
in
comms,
but
the
people
on
the
cocc
don't
need
to
be
org.
Members
First,
we've
pulled
in
people
in
the
past
that
have
not
been
org
members,
but
have
previous
cocc
experience,
and
you
know
sort
of
like
some
knowledge
of
the
space,
and
all
that
is
is
definitely
required,
but
it
like,
if
they
have
previous
experience
in
that
space,
like
it's.
Okay,.
B
Because,
like
I
can
reach
out
to
the
fosty,
you
know
new
community
because
we
had
a
whole
track
on
this
sort
of
thing
at
Fosse,
and
so
there's
going
to
be
some
potential
candidates
there,
but
reaching
out
to
them
and
saying
hey.
If
anybody's
interested
in
this,
the
deadline
is
in
due
days,
it's
not
going
to
produce
a
lot
of
results.
Look.
A
C
We
had
to
do
it
like
automated
to
like
pull
everything
before
to
like
migrate
kdev,
for
example,
but
that
was
the
big
blocker
for
us
to
move
forward
with
getting
everyone
to
shift
over
to
kubernetes
to
I
o
managed
groups
and
for
like
before
we
ask
everyone
to
start
doing
that
should
do
with
contravex.
First,
the
group
and
all
that's
created
just
need
to
decide
a
timeline,
but
we
can.
We
can
do
that
out
of
band.
C
Sending
out
comms
that,
like
hey
like
and
we
have
to
update
six
Dot
yaml
and
basically,
if
people
have
shared
things
with
the
old
list,
they
need
to
know
to
share
them
with
a
new
list.
I
have
shared
all
the
contrabec
stuff
that
I
know
of
already
anything
that's
on
our
shared
drives,
but
if,
if
anyone
else
has
shared
docs
the
list
that
needs
to
change?