►
From YouTube: 20230202 SIG Arch Enhancements
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
A
Not
earlier
than
I
thought,
so
this
is
the
enhancement,
film
Project
meeting
of
State
architecture
and
we
are
under
the
kubernetes
code
of
conduct.
So
please
follow
it
and
be
kind
to
each
other.
If
you
have
any
problems,
you
can
also
contact
me
after
this
meeting
and
I
guess
we
can
begin.
We
have
an
agenda
just
so.
Everyone
knows
like
I,
have
a
meeting
at
10
30,
so
I
have
to
run
and
yeah,
so
I
I
just
wanted
to
give
a
little
bit
of
an
update
on
the
process.
A
Cap
like
that
was
something
I
was
working
on,
but
then
it
kind
of
got
set
to
the
side
a
little
bit,
because
I
was
changing
jobs,
so
I
I
lost
I
lost
the
threat
of
it
a
bit.
So
my
goal
is
to
have
I'm,
basically
compiling
a
bunch
of
notes
on
it.
A
Right
now
and
I'm
gonna
attend
the
State
architecture
meeting,
probably
next
week
to
get
just
some
ideas
from
them
since
they're,
some
of
the
major
people
that
have
made
process
gaps
and
I'm
also
going
to
reach
out
to
a
few
people
that
I
know
recently
have
also
made
process
cups.
As
well
like
James
did
one
I,
don't
I,
don't
think
I
got
accepted,
but
he
actually
went
through
the
process
of
using
the
traditional
template
for
other
things.
A
Whole
whole
template
and
just
some
notes,
and
then
hopefully,
I
will
have
some
feedback
on
all
of
that
to
share
in
the
next
meeting
or
a
draft
something
to
share
and
review
it's
more
of
like
a
niche
topic.
But
basically
the
idea
is
that
there
are
people
who
want
to
memorialize
changes
to
some
processes
that
they
have.
They
might
be
like
standards
and
kubernetes.
A
It
might
be
how
their
Stig
does
something,
and
so
far
all
we
have
is
just
a
traditional
cap
template
which
is
fine
except
like
there's
a
lot
of
things
that
don't
really
it's
all
just
like
n
a
and
it's
such
a
drag
to
go
through
and
na
it.
But
then
also
changing
processes
and
policies,
kind
of
have
a
different
set
of
questions.
A
The
regular
cap
template
is
more
about
features
and
like
technical
changes
that
are
going
into
kubernetes,
so
those
are
very
much
beholden
to
a
release
cycle,
whereas
a
process
cap
is
more
of
a
collaborative
change
or
a
change
that
I
think
relies
more
on
conversation
and
feedback
from
the
Sig
or
potentially
the
kubernetes
community
at
large.
So
one
of
the
things
I'm
thinking
about
is
when,
like
the
Cadence
was
changed
right
like
some
of
the
problems
there,
it
wasn't
indicated
so
change.
It
was.
How
was
that
rolled
out?
How
are
people
notified?
A
It
felt
really
last
minute
and
people
didn't
necessarily
feel
included
so
providing
some
guard
rails
depending
on
the
like
the
scope
of
the
change,
obviously
like
if
it's
a
like
small
Sig
change,
how
they
do
it
or
maybe
they
just
want
to
memorialize
how
they
do
things
just
so
that
people,
you
know,
have
an
understanding.
That's
one
thing,
but
if
we
want
to
achieve
something
that
you
know
affects
the
entire
project,
how
do
we
roll
that
out?
Like?
A
Does
it
necessarily
make
sense
to
say
you
know
like
just
announce
it
all
at
once
at
the
end
of
a
release
cycle
and
just
kind
of
spring
it
on
everybody?
Or
is
there
a
better
way
to
do
that?
So
I
think
that
you
know
removing
some
of
the
N
A
sections
so
that
you
know
we
can
remove
kind
of
some
of
the
noise
and
then
thinking
through
some
of
the
things
that
would
be
really
beneficial
to
include
for
more
process
procedural,
less
technical
feature.
A
A
Know
like
what
do
we
need
as
a
community
to
make
sure
that
people
can
roll
out
those
kinds
of
changes,
so
that's
kind
of
like
my
framing
of
it,
and
hopefully
I
I
really
want
to
get
it
done,
but
I
got
really
just
back
there
by
life
and
the
holidays,
so
it
kind
of
went
off
the
rails
a
little
bit,
but
that's
kind
of
the
overview
of
it
and
yeah
I
know
I,
know:
Tim
is
pretty
active
too
so
I'll
love
to
get
Joseph's
feedback
as
well.
A
That
was
all
I
had
I
just
wanted
to
share
a
day
to
keep
myself
accountable
and
put
it
out
there
and
yeah.
So
I'm
gonna
stop
babbling.
Now.
B
I
will
say
that
the
only
cap
I've
done
is
a
process
cap.
Really
it
was
a
policy
camp
for
Sig
dogs,
so
yeah
there's
a
lot
in
there.
You
know
I.
C
A
Cool
well
I'll
definitely
reach
out
to
you,
because
I'd
love
to
also
just
make
that
process
not
process.
I'd
hate,
I'd
love
to
make
it
less
of
a
drag
because
I
think,
like
some
people
want
to
do
it,
but
then
they're,
just
like
oh
God,
so
Tim
can
give
me
the.
Is
this
a
drag
or
not
so
yeah?
Thanks
to
that.
C
Yeah
and
I
I
have
a
few
clarifications
as
questions
as
well.
On
process
cap,
like
I've,
seen
it
I've
seen
some
documentation
around
how
you
could
create
a
sub
project
using
a
cap
or
most
in
my
from
my
knowledge,
most
sub-projects
so
far
that
I've
been
involved
with
have
not
used
that
the
kept
process
or
how
do
we
or
if
we
could
formalize
or
clarify
that
also
like
actually
just
a
great.
A
A
For
for
tips,
like
it's
obvious,
like
hey,
this
is
a
change
like
into
like
kubernetes
code
base,
but
you
know
like
and
I
guess
we
suggest
that
people
use
them
for
other
things.
But
if
we
have
this
other
template,
then
we
can
more
clearly
say
like
okay,
like
now
it's
now,
it's
definitely
applicable
to
you
like
so
we're
gonna
have.
A
So
let
me
put
that
as
a
notes,
because
maybe
I
was
just
assuming
that
yeah
okay,
I'm
just
typing
I'm,
sorry
and
you're
you're
in
Sig,
docs
too
right
so
I
know
that
there's
there
might
be
things
like
this
might
be.
The
type
of
template
that
is
more
applicable
to
your
sink.
Cool
I
was
just
about
to
type
something
but
I
can't
I
drank
a
lot
of
coffee
and
I.
Try
to
type
and
I
try
to
talk
at
the
same
time
and
it's
not
working.
A
Okay,
yeah,
please
so
yeah
I
think
that
would
be
good,
yeah
and
I
think
that
that
I
think
Joe
best
before
in
the
past,
like
also
putting
some
guard
rails
on
I.
A
Think
right
now
you
know
like
the
technical
caps
go
through
Alpha
Beta,
And
GA,
but
like
a
process
cap,
like
you
know,
usually
it
has
a
feeling
of
straight
to
GA
and
I
think
that
that
makes
a
lot
of
sense
for,
like
small
things
like
a
stigdoc
says
like
Hey,
we're
doing
something
that
only
affects
the
docs
or
we
want
to
immortalize
the
thing
that
we
already
do,
or
you
know
we're
gonna
make
a
change,
but
we
already
have
this
consensus
within
our
Stig
like,
and
it
doesn't
necessarily
majorly
affect.
Other
people
like
that.
A
That's
straight
to
GA
idea
is
really
good,
but
you
know
like
if
we
have
changes
that
affects
the
entire
kubernetes
Community,
maybe
put
some
guard
rails
on
like
well.
What
does
a
rollout
mean
for
a
process?
Change
then,
like?
Are
you
behold
into
a
release
cycle
or
you
behold
into
some
other
sort
of
adequate
time
period?
A
You
know
I
mean,
like
I,
think
for
the
process
there's
this
idea
of,
like
kind
of
in
my
mind,
like
feedback
and
an
adequate
time
period,
to
get
this
consensus,
but
then
an
adequate
time
period
to
notify
people
as
well.
Right
so
like
you,
can
make
the
change.
But
if
you
end
up
telling
people
at
the
last
minute
that
might
be
a
real
drag
if
it
requires
them
to
also
do
something
differently,
so
I
think
it's
like
I
think
that's
the
part.
A
That
probably
is
going
to
be
like
kind
of
interesting
and
then
the
idea
of
like
you
know.
Well,
if
you
submit
your
process
at
the
beginning
of
a
release
cycle
since
we
have
what
three
a
year
and
you
do
an
adequate
amount
of
notification
and
sure,
maybe
that
for
that
major
catch,
that's
enough
to
like
let
people
have
it
go
into
place
in
an
extra
week
cycle,
but
maybe,
if
you
don't
or
if
you
just
introduce
it
whatever
you
want
to,
then
you
know
you're
going
to
need
a
greater
period
of
time.
A
So
that's
kind
of
something
that
I'm
interested
in
hammering
out
like
as
we
get
a
draft
and
and
trying
to
come
up
with
some
guard
rails
on
those
like
bigger
sort
of
more
widespread
effect,
sort
of
policy
or
process
changes,
but
scope
to
obviously
the
impact.
A
It's
a
lot
easier
for
us
to
change
things
for
themselves
than
you
know.
The
entire
kubernetes
Community
or
maybe
a
Sig
doctor,
also
had
to
like
it's
going
to
affect
another
Sig.
A
lot
then
you're
gonna
have
to
make
sure
to
give
them
enough
feedback
time
and
change
as
well.
So
yeah.
B
A
The
idea
is
just
like
collaboration
and
community
and
being
thoughtful
about
how
changes
affect
other
people.
Yeah
I,
really
like
that
point
right,
so
cool
yeah
that
was
all
I
had
for
myself,
I'm
wondering,
if
does
anybody
else,
have
anything
that
they'd
like
to
talk
to
talk
about
or.
A
Okay,
cool!
Well,
none
for
you,
Tim,
okay,
cool,
okay,
cool
I!
Guess
we
can
leave
it
at
that!
I
wasn't
sure
if
somebody
else
is
gonna
come
but
I
guess
not
so
yeah
I'm
gonna
start
working
just
on
like
a
more
freeform
draft,
because
I
I
try
to
make
like
a
template.
Draft
and
I
was
like
this
isn't
a
great
way
to
collect
ideas
at
all.
B
A
Let
me
look
at
a
working
kind
of
world
of
just
like
an
idea
document
to
kind
of
put
them
into
categories
and
solicit
some
feedback.
I
know
that
sometimes
people
submit
cats
and
other
ideas
that
they're
very
opinionated
on
and
then
they
get
feedback.
But
then
you
kind
of
at
the
redo
everything
so.
C
A
A
Like
Alpha,
being
a
ga
technical
kind
of
have,
though
I
suppose
like
there's
still
an
idea
of
like
Alpha
GA
or
beta
GA
in
it
so
like
a
very
large
change,
but
defining
that
I
think
would
be
pretty
interesting.
B
A
B
So
like
one
thing
to,
maybe
capture
is
Flag.
Day
changes
like
you
know
before
today,
kubernetes
contributors
could
wear
any
hats
they
like.
After
doing
all
kubernetes
contract
contributors
must
wear
sailor.
Hats
and.
B
It's
it's
an
on
or
off
thing
you
know,
and
sometimes
it
won't
be
with
Hats
which
we
could
roll
out
gradually,
but
sometimes
we
would
you
know
we
would
have
to
have
a
change
where
everyone
agrees
like
we
used
to
do
this,
and
now
we
do
that
and
we
have
to
switch
on
the
same
day.
So,
just
just
like
you
know,
I
think
that's
what
that
sort
of
that's
like
a
user
story
for
the
for
the
policy.
A
Yeah
yeah,
no
I
think
that
that's
a
great
Point,
especially
like,
and
that
comes
down
to
you
like
making
sure
that
people
are
giving
people
heads
up
like
time,
but
also
making
them
aware
that
the
change
exists
and
then
what
they
have
to
do
and
so
I
think.
That's
like
exactly
what
I'm
thinking
or
it's
like
notification
and
coordination
and
communication
is
kind
of
the
most
important
part
you
know.
So
it's
like
everybody
has
to
switch
the
Sailor
hats.
A
B
A
B
A
Yeah,
that's
that's
exactly
it
that
that
was
actually
I'm,
so
happy
that
you're
saying
this,
because
those
were
things
that
I
was
thinking
of
like
in
my
like
brainstorming
was
not
just
say:
hey
you
have
to
let
people
know,
but
especially
with
the
magnitude
of
the
change
or
the
the
impact
of
the
change
like.
How
do
you
have
to
do
that?
You
know
like
not
just
because
it
might
not
be
like
sufficient
to
just
send
an
email
to
kdev
right
like
or
write
something
in
slack.
A
It
might
be
something
where
you
really
need
to
you
know.
Utilize
blogs,
you
might
need
to.
You
know,
use
a
lot
of
social
media
accounts.
You
might
really
need
to
publicize
these
changes
or
not
just
the
change,
but
that
you
are
in
the
process
of
soliciting
feedback
for
that
change
right
like
because
that
is
telling.
A
Especially
as
if,
if
the
change
is
massive,
you
really
need
to
work
to
solicit
feedback
on
that
change,
and
especially
if
it's
outside
of
just
like
you
know
a
thing
changing
how
they're
doing
something
you
really
have
to
be
able
to
kind
of
advertise
that
discussion.
A
If
that
makes
sense,
and
then
by
advertising
new
discussion,
you
also
build
awareness
if
it
goes
through
to
the
thing
that's
going
to
happen
so
you're
also
like
prepping
your
audience
and
participants,
so
yeah
I
100,
agree
that
you
can't
hide
the
change
and
and
avoid
the
if
it's
a
massive
change,
you
kind
of
probably
need
massive
feedback.
Unless
there's
you
know
some
reason,
some
compelling
reason
that
it
doesn't
doesn't
matter
but
yeah,
definitely
yeah.
B
I
I'm
going
to
use
another
made-up
example.
Don't
worry
people
watching
the
video.
B
But
you
know,
let's
say
that
we
we're.
Actually
some
of
this
process
is
relevant
for
big
changes
that
are
code
changes,
so
I'm
gonna
say
we're
going
to
deprecate
the
node
API
discussion,
I'm
going
to
get
deprecated
where
we're
going.
We
don't
need
nodes
and
so
we're
going
to
deprecate
node,
but
we
don't
just
use
the
normal
cap
process.
We
would
follow
some
of
these
same
things
about
putting
a
banner
up
having
a
discussion
making
sure
people
feel
included
in
that
conversation
and
not
saying
right.
Well,
that's
the
code.
Merge.
B
Yeah
I
mean
Ray.
You
were
involved
in
in
the
work
to
make
sure
that
we
did
publicize
the
dockershim
removal
from
kubernetes
and
shift
to
CRI,
docketing
and
I
think
this
process
would
have
helped
us
yeah
I.
C
A
Now
I
have
a
really
good
point,
but
it's
also
great
to
hear
that
other
people
have
kind
of
the
same
same
idea
like
the
same
like
this
is
what
I've
seen
this
happen
like
I've
seen
a
happen
before,
and
I
would
really
wish
that.
I
really
wish
that
b,
c
and
d
happened
before
the
sent
into
effect.
A
I
really
wish
I
mean,
because
that's
also
the
worst
feeling
is
like
when
an
active
person
I
mean
if
you're,
if
you're
kind
of
inactive
in
the
community
well
yeah,
like
things,
are
going
to
take
you
by
surprise,
but
I
think
it's
the
worst
feeling
when
somebody's
like
active
and
engaged
and
they're
still
just
taken
aback
by
something
they're
still
like
wait.
What's
happening
like
what
I
thought,
I
thought
somebody
would
have
told
me
like
how
did
I
miss
that
I
I?
A
Don't
think
that
active
members
should
miss
miss
things
that
are
very
important
to
them
so
yeah
and
it's
also
just
a
way
I.
Think
of
giving
the
community
a
heads
up.
Even
you
know
like
Downstream
consumers
or
or
projects
that
rely
on
our
project.
I.
Think
that
you
know
we
can't
just
say
like
well:
I
mentioned
it
over
here
and
this
whole
entire
universe
of
other
people
will
just
find
out
whatever
it
is,
that
they
left
out.
B
I
think
there's
a
benefit
because
you
know
rather
than
say
do
something
and
then
a
very
keen
participant
sticks,
something
on
there
on
their
Forum
or
a
journalist,
picks
it
up.
If
we
go,
oh
we're
going
to
stick
a
banner
on
on
the
on.
You
know
this
site.
It
becomes
much
more
obvious
to
the
to
the
Sig
in
question
that
hey,
okay,
right,
you
know,
there's
going
to
be
a
publicity
angle,
so
it
it
calls
out
the
publicity
before
we
need
to
worry.
A
Of
a
surprise,
yeah
no
I
think
that
that's
like,
because
I
think,
like
most
of
the
surprise,
obviously
is
because
people
just
like
truly
aren't
aware
and
there's
almost
like
a
problem
when
that
happens
because
you're
like
well.
If
people
weren't
aware
like
would
this,
would
this
change
look
different?
A
Our
future
is
GA
now,
and
everybody
knows
but
I.
Think
for
other
changes,
like
you
kind
of
don't
want
the
first
time.
People
are
hearing
about
it
to
be
like
at
this
one
point
in
time
when
it
it's
live
now,
like
that's
just
a
very
like
subpar
way
to
let
people
know
about
a
change
like
that,
so
yeah,
no
I,
love
that.
So,
let's.
A
Let's
think
through
the
minimum
communication,
I
don't
know
avenues
for
both
okay,
yes
back
and
letting
me.
B
So
this
will
also
be
good
for
a
lot
of
information
security
things.
So
if
we
changed
our
support
period,
if
we
changed
our
policy
on
How,
we'll
publicize
issues
that
you
know
these
are
all
policy
change.
These
are
more
policy
changes
than
they
are
technical
things.
A
A
Cool,
does
anybody
have
anything
else,
though,.