►
From YouTube: Kubernetes SIG Architecture 20190228
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).
A
While
recording
welcome
to
cig
architecture
for
February
28
2019
chase,
what's
the
friendly
or
is
it
bit
dot,
Lee
/,
sig
architecture
for
the
notes
that
is
correct,
yep
I've
got
a
memorized,
so
you
can
get
the
notes
there
if
you're
listening,
otherwise
I
just
paste
them
into
chat
the
first
item.
Paris
have
you
had
a
chance
to
join
yet
all
right,
then
we'll
go
ahead
and
we'll
jump
to
the
second
item
and
I'll
go
ahead
and
move
that
down
the
agenda.
The
next
one
item
on
the
agenda
was
intros.
Who
are
you?
A
Why
are
you
here?
Jace
I
think
you
put
this
on
there
and
the
idea
is
we
wanted
to
know
who
are
the
people
who
come
right
now?
We've
got
what
twenty
four
connections
into
here
and
more
people
than
that,
because
we
have
rooms-
and
there
are
some
of
us
who
talk
a
lot
in
here,
but
there
is
a
wonderful
assortment
of
people
who
are
here
who
we
don't
hear
from
very
often,
and
so
we
wanted
to
open
it
up
and
learn
a
little
bit
about
you
and
we've
allocated
here.
C
It
wasn't
the
dress
that
got
you
hello,
I'm,
lucky
Lachlan,
Evensen,
I,
work
for
Microsoft,
just
kind
of
listening
in
listening
to
process
Craig's,
saying
hello
there
as
well.
Just
listening
to
the
process
and
I've
been
just
very
interested
in
the
happenings
in
the
community
and
understanding
where
things
are
and
how
I
can
help.
So
really
just
recon
and
understanding
more
about
the
community.
I
will
pass
the
baton
to
Craig.
D
I
may
not
be
next
on
Bryan's
list,
but
I'm
Craig,
Peters
I
work
in
the
same
team
as
Lackey
upstream
here
at
Microsoft
and
I'm
here
in
the
first
order
for
making
sure
that
there
are,
if
there
are
any
windows,
related
issues
or
Windows
nodes.
That's
my
near-term
goal
is
to
make
sure
that
we
can
land
back
correctly
upstream
and
beyond
that.
I've
had
a
long
term
interest
in
how
communities
works
and
how
the
evolution
of
api's
is
changing,
and
you
want
to
understand
how
I
can
contribute
to
that
better.
F
Hi
I'm,
Pablo
and
forest.
You
see
I
got
interested
in
this
group,
mostly
because
all
the
changes
in
the
architecture
of
donated
around
adopt
insecurities
as
a
first
class
citizens,
so
aspected
a
lot
of
changes
in
the
overall
architecture.
So
my
my
first
intention
here
is
just
to
decay
myself
and
how
this
process
goes
and
I'm
most
interested
in
that
topic
on
this
ongoing
work
off
on
making
coastal
resources,
first
class
cities
and
then
changing
the
way,
the
full
API
around
that
concept.
B
F
B
F
F
B
G
A
All
right,
thank
you.
So
then,
the
next
that
I
think
I
have
on
here,
I
didn't
know,
will
go
in
order
with
my
screen
here
then
I
guess
Aaron
of
cig
beard.
H
Hi
I'm
Aaron
of
sig
beard.
You
may
know
me
as
Aaron
of
the
steering
committee
Aaron,
the
1:14
release
lead
and
the
chair
of
cig
release,
Aaron
the
owner
of
github
administration
project
I'm
here
principally
as
a
reviewer
on
the
conformance
definition
sub-project
that
cig
architecture
has
as
well
as
any
of
the
other
cross-cutting
concerns
that
end
up
in
cig
architecture.
With
regard
to
moving
the
ball
forward,
so
things
like
making
sure
the
right
people
are
included
in
caps
here.
C
A
B
A
Yes,
angel
in
chat
says
hi
guys
my
mic
isn't
working
properly
today,
but
just
to
say,
hi
I'm
angel,
Ramirez
I
run
a
company
called
B,
I'm,
probably
poorly
pronouncing
that
on
I
apologize,
we're
small
company
trying
to
bring
cloud
native
and
kubernetes
to
Florida
and
South
America
Colombia
for
now
I'm.
Listening
and
learning
from
all
you
guys.
Thank
you.
J
L
Some
changes
that
we
made
to
how
who
watches
instead
of
poles
for
secrets
and
come
big-match
are
bringing
the
way
jobs
work
in
ones
well
for
across
all
clusters
and
that's
type
of
information
that
those
changes
are
what
occurred
here
and
most
of
the
time
we
end
up,
propagated
up
to
our
users
via
the
workforce.
Express.
B
L
Have
Tim
rockin
a
long
time
most
most
I
know
most
faces
on
here.
I
still
pay
attention
mostly
to
networking,
storage,
multi,
cluster,
low
level
topics
and
I'm
here,
because
I
try
to
keep
an
eye
on
the
project
overall,
API,
reviewer
and
architectural
II,
making
sure
that
things
are
consistent
across
all
different
groups.
Daniel.
B
K
Like
after
the
Brian
and
Tim
and
Joe
and
resid
like
next
person,
hands
on
keyboard
and
currently
I'm
coach,
Eric
OTO,
we
didn't
really
make
it
stinking
API
machinery
and
I
like
to
come
to
the
cig
architecture.
The
two
reasons
I
am
a
peer
reviewer
behind
the
name
areas
at
the
moment,
and
also
it
seems
like
there's
often
discussion
of
like
well,
should
think
these
securities
or
should
they
be
other
things
so
opera
perspectives
or
be
aware
of
what
yeah.
B
N
Is
a
Dom
and
I
am
that
here
of
the
signal
and
the
code
here
and
another
tear
signal
is
the
direct
from
the
Red,
Hat
and
I
joined
his
team
before
we
open
source
kubernetes
and
the
reason
I
attend.
I
didn't
attend
the
AutoStick
architecture,
but
I
always
look
at
the
agenda
and
also
the
meeting
notes.
But
occasionally
I
will
join
the
readings
because
the
node
it
is
the
integration
of
the
heart
and
others
kind
of
teacher.
If
you
really
want
to
fly
in
a
kubernetes
you
in
some
way.
C
G
Hi
I
work
on
OpenStack,
cig,
OpenStack
related,
you
know,
repositories
and
from
starting
from
there.
I
ended
up
doing
like
code,
reorganization,
stuff,
conformance
testing,
and
you
know
generally
involved
in
things
happening
in
contrib,
X
and
suggesting
also
on
the
steering
committee
as
well
I'm
here
to
absorb
the
history
and
try
to
figure
out.
G
B
P
Sure
so
I'm
Ryan
better
check
I
work
for
cray
the
supercomputer
company,
so
we
have
quite
a
few
interesting
use
cases
for
our
application,
so
I'm
coming
here
just
to
both
absorb
and
see
you
know,
if
any
input
we
could
provide,
can
help
and
I
also
open
the
multi-tenancy
working
group
as
well.
So
I
guess
be
nice.
An
answer
for
that
as
well.
So
are
using
four
days.
Yes,
yeah.
We
we
are
using
kubernetes
extensively
on
I
guess
with
HPC
as
well
as
a
lot
of
other
internal,
tooling
cool.
B
R
Hey
hi
I'm
the
wall
I'm,
an
engineer
at
remember:
I
started
contributing
to
kubernetes
from
1.2,
and
we
spear
cloud
providers.
Kubernetes
is
an
was
a
very
interesting
project
for
me
back
then,
and
still
it
is
right
now,
I'm
destined
for
shadow
and
this
release.
Team
of
1.14
I
was
also
on
1.13
and
observing
in
one
article.
R
I
am
also
Co,
organizing
for
working
group
ideas
and
I
regularly
visit
I
mean
frequently
with
it
siga
architecture,
because
I'll
get
to
learn
a
lot
about
the
project
and
understand
the
decision-making
and
from
very
key
people
in
the
project
directly
who
endless
meetings.
That's?
Why
participate
in
this
meeting
Andrew.
S
S
O
T
Sorry,
hey,
hey
Brian,
Matt
and
Joyce
good
to
see
you
guys
do
here.
My
name
is
Forrest.
You
guys
hear
me.
Yes,
okay,
cool
I've
worked
in
different
places,
a
double
yes
Microsoft
and
no
with
VMware
happy.
Oh
I
was
with
this
channel
for
a
long
time
and
then,
because
last
year
was
a
pull
out
to
a
high
priority
project.
So
I
didn't
come
for
WoW
and
today
is
my
first
day.
T
So
that's
very
interesting
and
also
I
mean
other
sick
channel
like
Earth
and
API,
because
those
are
areas
I,
I'm
interested
in
as
well
and
now
I'm
directly
working
on
ku
Bonetti
related
products,
so
I'm
also
looking
for
opportunities
to
engage
more
and
contribute
more
and
pretty
much.
That's
me.
If
you
have
any
questions,
just
you
can
ask
me
now
in
the
future
thanks
Brian
thanks.
B
E
B
B
This
state
was
actually
created
after
the
committee's
Leadership
Summit
a
couple
years
ago
in
order
to
try
to
spread
out
more
of
the
knowledge
and
work
responsibilities
which
is
being
done
on
a
more
informal
basis
by
a
small
issue.
Number
of
people,
including
folks,
like
Tim
Hakan
and
clean
Coleman
and
Jordan,
look
at
Daniel
Smith
and
myself
that
API
Cooper's.
B
B
E
E
The
emeritus
release
lead
for
1.8
1.10,
Meredith
sig
chair
for
sig,
as
your
sig
release,
and
probably
something
else,
I'm
forgetting,
but
so
I've
been
deeply
involved
in
the
community
since
day,
one
and
and
super
passionate
about
architecture,
as
as
a
way
to
broaden
our
horizon
past,
just
one
release
and
to
think
about
how
we
make
this
project
sustainable
and
sometimes
it's
technology,
sometimes
as
people.
Sometimes
it's
the
Nexus
of
the
two.
So
that's
really.
What
I'm
here
to
do
is
serve
the
community
in
this
in
this
capacity,
so
that.
A
A
I
co-founded,
sig,
apps
and
I've
worked
a
lot
with
apps
and
and
all
of
the
things
are
on
that
in
the
workloads
api's
and
that
space,
but
I
like
hard
problems
and
sega
architecture
is
a
hard
problem
for
a
lot
of
what
we're
doing
and
so
I
like
helping
out
with
our
problems,
which
is
why
I
got
involved
here,
because
Jason
Brian
had
too
much
to
do
and
I'm
trying
to
help
them
do
some
of
that
stuff.
That's
just
the
gist
on
me.
A
G
G
So
we
are
very
happy
today
so
I'm
here
to
learn
from
all
of
you
guys
right
so
and
also
keep
as
I
hear
some
of
the
leaders
here
who
talk
about
the
various
needs
and
I
go
and
talk
to
the
team
and
see
what
we
can
do
and
the
goal
of
my
team
is
to
help
our
community.
We
are
separate
from
the
products,
so
our
sole
focus
is
helping
of
the
community
and
that's
why
I'm
here.
S
Say
a
quick
hello
hi,
my
name's
Travis
Rodan
I've
been
joining
for
a
little
while,
but
I
work
at
VMware
and
I'm,
mostly
here
to
be
a
fly
on
the
wall
and
learn
from
everyone.
Here.
I
tend
to
be
most
active
within
six
storage
currently,
but
usually
not
much
to
contribute,
but
always
like
to
follow
along
and
see
what
the
long-term
trends
are
set.
For
me,
you're.
U
Do
a
brief
one
I
think
I
know
most
of
you
so
very
short:
I'm
Quinton,
I,
technical
VP
at
Huawei
and
focus
money
around
public
cloud
open-source,
so
including
communities,
but
quite
a
lot
of
other
stuff
as
well,
and
the
reason
I'm
here
is
to
try
and
keep
track
of.
You
know
the
high
level,
the
changes
in
architecture
and
a
lot
of
the
you
know.
U
Most
influential
sig
leads
are
here,
so
it's
good
to
hear
from
from
their
mouth
directly
what's
going
on
and
what
the
thinking
is
and
help
out
where
I
can
I
come
from
background.
I
was
at
Google
for
five
years
before
that
and
Amazon
versus
other
places
so
and
we
have
a
variety
of
products
based
on
kubernetes.
So
in
some
cases
we
need
input
from
some
of
those
perspectives,
so
I
make
myself
available
for
that.
If
it
is
required
from
me.
V
A
Going
twice
going
three
times
with
that,
we
can
move
on
to
the
next
agenda
item
an
update,
though
unfortunately,
Paris
won't
be
able
to
make
it.
Today
she
had
an
emergency
come
up
and
we're
gonna
have
to
pump
that
to
a
future
meeting,
scheduled
it
for
our
next
meeting,
which
is
March
14th,
but
we'll
have
to
tie
off
with
her
on
scheduling.
Just
to
be
sure.
The
next
item
we
have
in
the
agenda
looks
like
Brian.
B
So
that
conformance
working
group
met
yesterday
and
several
meeting
this
meeting
I
in
the
meeting,
say
architecture
meeting
notes,
I
dropped.
The
group
meeting
notes
from
yesterday's
meeting
only
to
the
named
project
or
a
spreadsheet
that
has
a
list
of
issues
for
tests
that
test
for
areas
that
we
want
to
get
in
a
cover
job,
in
conformance,
that
need
to
be
integrated
with
that
product
floor
and
the
state
of
architecture.
Final
review
approval
project
board
that
we
have
been
using
to
identify
tests
that
we're
ready
for
final
approval
for,
in
addition
to
the
conformance
sweets.
B
We
just
one
of
the
main
things
we
discussed
yesterday
is
how
do
we
improve
the
process
for
getting
more
tests
into
this
week,
because
we
desperately
need
more
coverage
for
areas
that
are
high
risk
for
implementations
at
distribution,
services
of
communities
that
might
not
be
on
a
%
compatible,
because
the
components
are
pluggable
or
people
will
swap
them
out
in
the
community
or
even
in
products
like
just
as
the
the
primary
example.
I
use
is
qubits,
which
has
several
plug-in
interfaces
here.
Si
si
si
and
I,
and
so
on.
So
you
know.
B
So
how
can
we
improve
the
process
more
obvious?
Where
areas
where
could
help
and
on
board
more
people
for
for
identifying
tests
that
should
be
added
or
for
writing
new
tests?
They
should
be
added
or
and
for
reviewing
the
tests
that
are
in
the
pipeline.
So
that
was
the
main
topic
so
that
working
room
meets
once
a
month,
and
these
are
the
primary
place
to
discuss
this
there's
also
enough
airing
the
low
traffic
mailing
list,
and
we
want
to
get
more
activity
on
for
people
who
are
involved
or
interested
in
getting
involved.
B
H
It's
to
me,
the
question
comes
down
to
you:
do
the
bright
minds
and
they
conform
its
definition,
subprojects.
Their
architecture
do
that
is
somebody
from
the
conformance
working
groups
supposed
to
volunteer
to
take
their
best.
Guess
it's
just
like
at
some
point
here
either
we
need
to
give
authority
to
a
sole,
individual
or
a
select
group
of
individuals,
or
we
need
to
find
a
way
to
come
to
consensus
on
an
agreed-upon
prioritization
that.
B
Is
the
question
I
would
say
just
in
general,
you
know,
as
we
on
we
need
to
on
board.
More
people
onto
the
effort
is
definitely
something
other
people
could
help
out
with,
and
this
is
where
you
know
clarifying
the
process.
If
you
want
to
use,
would
help
a
lot
so
that
if
we
want
to
follow
the
process
you
just
described,
then
basically
you
need
to
translate
the
high-level
priorities
into
a
sufficient
understanding
that
you
know
someone
could
own
this
and
do
it
on
a
regular
basis.
So.
B
A
B
A
couple
of
people
who
came
to
yesterday's
working
group
meeting
expressed
interest
and
I
will
follow
up
with
them
soon
as
I
get
a
chance
within
the
next
couple
of
days.
You
know
if
more
additional
people
are
interested,
they
can
speak
up
now
or
they
can
just
email,
the
conformance
working
group
mailing
list-
or
you
know,
II
or
I'm-
not
going
to
put
it
on
Erin,
but
doing
much
of
this
so
far,
but
I
would
recommend
really
use
the
mailing
list.
So.
A
H
I
think
there's
there's
that
if
you
are
interested
in
just
kind
of
diving
in
and
helping
out
with,
what's
already
there,
there
are
lots
of
pull
requests
that
need
to
be
shepherded
and
there
are
also
lots
of
for
requests
that
need
to
be
reviewed.
The
way
you
can
signify
your
intent
to
review
pull
requests
is
to
add
yourself
to
the
owners
file
for
conformance
tests
so
that
you'll
automatically
get
selected
as
a
reviewer.
The
idea
is
conformance
or
so
like
what
Andrew
Weil
here
to
do
right.
H
The
idea
is
you,
if
you
don't
have
the
subject
matter,
expertise
to
read
the
PR
about
a
conformance
test.
You
figure
out
well
or
what's
this
thing,
that's
responsible
for
this,
and
then
you
go
poke
them
and
unfortunately,
to
the
nature
of
this
project,
you
don't
just
like
ask
them
on
github.
You
actually
have
to
go,
find
a
human
being
and
talk
to
them.
That's
why
I
call
it
shepherding
PRS
and
there
are
many
open
PRS
out
there.
H
B
Yeah
so
I
think
there
are
two
sides
of
the
informants
test
abused.
One
is
the
domain
expertise
which
was
just
touched
on
and
that's
where
you
know.
Sometimes
you
need
to
ask
for
help
from
the
relevancy
or
some
projects
that
help
make
sure
that
that
it's
reviewed
in
a
timely
manner
and
there's
something
special
to
that
in
the
working
group
notes
about
a
suggested
way
to
go
about
doing
that.
The
other
side
are
conformance
tests
themselves,
have
a
number
of
requirements
and
criteria,
they
should
follow,
and
Aaron
wrote
up
some
documentation
about
that.
B
It
is
not
complete.
So
you
know
if
there
are
things
which
are
at
all
any
dubious
or
unclear,
raising
that
as
an
issue
to
the
other
set
of
approvers,
so
that
we
can
make
a
decision
about
that
specific
issue
and
make
sure
it
gets
documented
and
added
to
those
documents.
That
criteria
is
really
really
important
as
part
of
scaling
the
supper.
B
G
Matt
I
had
a
quick
question
to
the
team
here.
Did
we
at
some
point
approve
a
windows-only
tag?
I
remember
we
did
a
linux
only
tag
in
the
conformance
test,
but
I
don't
remember
doing
a
Windows
only
tag.
So
there
is
an
issue.
That's
open!
Seven,
four,
seven,
four
zero!
Just
now!
If
anybody
remembers
something
or
I
can
go,
look
look
through
the
notes.
I.
H
Use
help
on
that,
because
I
feel
like
there
was
discussion
and
say
testing
about
this
decision
in
the
conformance
working
group
about
this
decision
here
in
sega
architecture
about
this
decision.
I
don't
know
if
three
different
decisions
were
made
or
if
we
ignored
them
and
made
another
decision
later
on
or
what's
actually
documented,
but
the
current
windows
only
tag
does
not
seem
like
an
approach
that
is
favored
from
a
state
testing
perspective.
I
have
not
yet
had
the
time
to
dig
into
this.
So
thank
you
for
raising
it.
B
D
G
E
Just
wanted
to
call
out
what
I
wrote
in
the
chat
real
quick,
just
as
if
somebody
like
myself,
who
suffers
from
rampant
impostor
syndrome,
it's
actually
a
safe
bet
to
say
that
something
you're
bringing
to
the
table
is
extremely
valuable
to
the
effort.
So
even
if
you're,
not
an
expert
in
testing
and
one
night,
just
as
Zarin
said,
there's
plenty
of
work
to
help
with
just
communications
and
coordination
and
things
that
anybody
can
do
so.
Sometimes
that
helps
lift
an
extra
burden
off
of
people
who
can
do
the
test,
reviews
and
those
sorts
of
things.
A
Thank
You
Jase.
Okay,
with
that,
we
have
one
final
thing
in
the
formal
agenda,
and
that
is
a
pull
request.
I'll
share
my
screen
on
it.
Hopefully
we
can
remove
the
the
hold
on
it
and
I
get
it
going.
So
in
the
last
meeting
we
had
discussed
a
change
to
sig
architecture,
which
was
moving
the
meeting
to
be
bi-weekly
moving
the
kept
sub-project
over
to
sig
p.m.
and
removing
the
two
dues,
and
in
this
we
got
a
bunch
of
looks
good
to
me,
including
one
from
a
who
is
a
chair
on
sig
p.m.
A
A
B
C
B
And
just
you
know,
in
terms
of
repeated
guidance
on
how
to
communicate
a
lot
of
the
people
who've
been
on
the
project
for
a
long
time.
Notifications
are
mostly
noise.
I
am
subscribed
to
literally
tens
of
thousands
of
PRS
and
issues
and
I
haven't
yet
figured
out
how
to
write
a
tool
that
will
unsubscribe
to
all,
but
the
ones
I
care
about
that.
B
So
I
brutally
filter
most
of
them
and
it
is
actually
popular.
Twitter
mentions
now
it
actually
didn't
even
used
to
work
because
they
may
have
didn't
index
it
or
whatever
and
I
know
it's
not
a
pink
unicorn,
but
but
in
general
it's
a
really
really
really
bad
mechanism
for
looping
in
senior
people
on
the
project.
I
also
cannot
watch
slack
unless
explicitly
mentioned.
That
is
not
yet
most
noise
I
saw
has
a
relatively
high
signal
ratio.
Sing
architecture.
Mailing
list
is
low
enough
traffic.
That
I
am
able
to
look
at
that.
B
H
So
yeah
I
agree
with
using
the
mailing
list
for
the
first
quick
thing:
I'll
just
make
up
a
plug
that
maybe
can
be
explored
further
in
contributor
experience.
We've
recently
turned
on
octobots
for
a
bunch
of
the
github
works.
To
attempt
to
find
a
better
way
of
doing
get
up
notifications.
It
seems
like
it
has
improved
significantly
since,
like
it
was
last
examined
a
year
ago.
H
So
if
anybody
wants
to
try
giving
okto
boxes
shot
at
octo
box
that
I,
oh,
it's
supported
on
kubernetes
and
kubernetes
sticks
and
all
that
stuff
and
lets
you
do
a
lot
of
fancy
filtering
of.
Why
are
you
being
notified?
What
are
the
labels
on
all
the
things
so
on
and
so
forth?
I
haven't
personally
used
it,
but
people
who
used
to
be
skeptical
of
it
who
started
using
it
on
taking
that
a
signal.
H
Second
thing,
if
we're
using
the
mailing
list,
I
feel
like
one
of
the
things
that
I
took
away
from
last
week's
meeting
was
that
it's
kind
of
unclear
if
we
have
accurate
representation
of
the
workload
that
this
sake
does
and
how
that
is
distributed
amongst
this
six
membership.
So
I
think
the
mailing
list
will
certainly
prevent
will
ensure
productive
use
of
our
time
here.
I
was
kind
of
curious.
What
we're
doing
from
good
perspective
of
visualizing
our
work
and
making
sure
we
understand
who's
doing
what
work?
H
Perhaps
it's
too
early
for
us
to
have
that
conversation
like
there
are
four
different
project
boards
in
every
so
called
architecture
tracking,
and
we
just
link
to
that
other
project
board
for
conformance,
which
is
an
organization-wide
project
board
and
the
kubernetes
thing,
and
then
there's
the
mailing
list
so
I
can
we
reduce
any
of
that
at
all?
But
do
you
what
do
y'all
think.
B
B
H
B
The
good
thing
about
project
boards
is
that
they
are
good
for
polling
and
because
they
support
things
like
ordering,
which
give
a
fine-grained
prioritization
can
be
an
efficient
way
to
work
through
a
sequence
of
items,
but
it's
very
asynchronous
since
it's
polling
based
so
I,
don't
know
that
emails.
That
would
better
practice
because
can
only
look
at
it
so
frequently,
but
yeah
I
don't
know
how
other
thoughts
there
I
mean.
If
we
say
you
have
another
board
or
raising
issues
or
something
yet
another
place.
Oh
like
us,
I
know,
I.
H
Guess
perhaps
I'm
raising
the
question
by
proxy
for
Craig
and
lucky,
as
representatives
of
sake
p.m.
since
I
think
there
was
discussion
of
having
sake
p.m.
offer
like
grooming
services
to
sakes
or
groups
that
are
cross-cutting
across
the
project,
and
so
like?
Are
there
areas
they
could
be
helping
us
with,
or
are
we
gonna
just
kind
of
try
and
handle
it
ourselves
for
now
with
them
as
observers
to
potentially
successful,
we
could
be
doing
better
well.
B
That's
a
totally
different
story
and
yes,
we
totally
need
help
creating
the
process
for
components.
For
example,
like
Aaron
Jordan
is
working
on
the
process
and
the
tooling
and
whatnot
for
API
review.
We
don't
have
someone
as
far
as
I
know,
working
on
something
large
conformance
that
will
actually
work
so.
B
D
Can
definitely
use
process
and
automation,
code
and
I
wanna
speak
up
there
a
little
bit.
I
think
the
the
goal
is
definitely
to
get
there.
The
challenge
is
to
have
enough
people
focused
consistently
enough
over
time
on
processes
for
particular
SIG's
or
working
groups
to
contribute
materially,
as
opposed
to
just
drive
by
and
say
here.
Here's
some
advice,
let's
change
this
thing
here
and
there,
and
so
in
in
sync
p.m.
D
I,
think
we're
really
trying
to
step
up
and
let's
start
doing
that
and
I
think
the
best
way
we
could
do
that
is
to
make
an
agreement
that
some
of
the
SIG's
or
some
of
the
working
groups
want
that
help,
get
involvement
from
optional,
sig
p.m.
and
and
do
that
on
a
consistent
basis
over
time
and
show
that
as
a
good
working
pattern
and
then
replicate
where
where
it
makes
sense.
So
the
question
is:
where
is
the
need
greatest
and
then
we
can
be
directed
there
so
that
make
sense.
A
A
There
Quentin
also
raised
a
question
that
actually
went
back
to
the
last
topic
here.
It
looks
like
he
got
into
the
final
review
on
the
pull
request
and
Quentin's
question
was:
why
were
the
two
do's
removed-
and
he
pointed
at
you
Jase,
the
two
duze
were
the
question
on
lack
of
consensus
in
the
sig
regarding
the
need
for
company
diversity,
and
then
it
remains
unspecified
how
sig
architecture
gets
involved
in
resolving
technical
conflicts
within
and
between
other
SIG's
and
the
sub-project
Jase.
Can
you
you
did
the
pull
request?
Can
you
respond
to
that
sure.
E
E
A
And
I
think
I'll
add
as
well
I
think
if
somebody
wants
to
be
more
involved
in
insig
architecture
and
helping
doing
some
of
these
things,
please
get
involved,
reach
out
to
myself,
Jase
or
Brian,
because
more
help
would
be
greatly
appreciated.
So
so
please
we
want
it.
It
just
hasn't
happened
and
then
the
other
when
it
comes
to
how
to
get
involved
in
resolving
technical
conflicts.
At
least
my
take
on
this
is
most
of
the
parts
of
code
have
owners
and
people
involved
at
certain
levels
and
then
ended.
A
We
have
the
kept
process
which
were
really
starting
to
double
down
on
in
using
caps
and
some
of
the
previous
meetings.
We've
talked
about
how
everything
that's
going
in
to
114,
to
be
a
cup
and
through
that
process
is
how
we
can
engage
on
these
forms
of
things
in
order
to
provide
that
and
and
the
real
technical
ownership
is
documented
in
the
owners
files.
Quite
frankly
who
owns
what
code
and
what
controlling
to
make
those
decisions
and
those
guidance,
and
then
we
have
certain
patterns,
we're
starting
to
use
things
such
as
CR
DS
controllers.
A
There's
certain
patterns
that
have
emerged
undoing
things
that
provide
a
lot
of
guidance
on
their
own.
They
give
us
consistency,
and
so
a
lot
of
it
comes
down
to
that
or
into
SiC
architecture
being
responsible
for
the
scope
of
the
project
and
then
those
kinds
of
things
we
can
bring
out.
But
much
more
of
that,
we
want
to
push
to
the
mailing
list.
So
then,
we've
got
a
good
documented
path.
People
can
do
stuff
asynchronously.
A
U
Yeah
I
think
the
answers
were
not
to
my
question.
This
is
my
my.
There
was
a
discussion
about
whether
we
want
diversity
in
the
same
leadership,
which
is
a
different
question
than
whether
we've
found
volunteers.
So
there
was
one
campus
that
we
did
not
want
to
camp
company
diversity
and
there
was
another
camp.
That
said,
we
did
and
that's
why
the
wording
said
there
was
a
lack
of
consensus.
So
that's
differently.
We
tried
to
find
people
and
nobody
stepped
up,
and
so
we've
given
up.
So
that
was
the
first
question
so.
U
Correct
well,
those
are
two
different
things,
but
yes
do
we
want
it
that
the
wording
of
the
stuff
that's
being
deleted
is
that
there
remains
lack
of
consensus
regarding
the
need.
My
other
question
was,
you
know.
We
discussed
the
other
stuff,
that's
contained
in
this
PR
in
this
meeting
last
week
and
we
agreed
to
change
the
frequency
of
the
meeting
and
the
and
the
cap
stuff.
But
I,
don't
recall
us
discussing
removing
the
two
dues.
It
kind
of
looks
like
that.
Got
slipped
in
I
stand
corrected,
but
that's
what
it
looks
like
from
the
outside.
E
B
So
it's
more
about
a
proactive
distributed
approach,
as
opposed
to
you
know.
Having
every
single
issue
raised
to
seed
architecture,
you
know
my
Jordan
went
through
the
35
caps
or
enhancements
a
few
meetings
ago,
for
example,
even
with
one
meeting
a
week,
there's
no
way
we
could
run
that
mini
through
that
mini
in
the
six
meetings
we
have
before
code
freeze
and
it
usually
cycle,
for
instance,
for
instance
right.
So
you
know
really
going
back
to
the
original
motivations
for
creating
staggered
architecture
in
terms
of
finding
a
better
way
to
achieve
our
goals.
B
It's
more
aligned
with
sustainability
like
avoiding
burnout.
The
Jason
mentioned
effectiveness
actually
being
able
to
successfully
ensure
that
all
of
these
efforts
are
moving
toward
the
way
that
we
want
and
in
line
with
the
projects,
values
which
I
do
recommend
going
to
look
at
the
products.
Values
are
documented
in
terms
of
decentralization.
B
Versus
centralization,
and
so
on,
so
so
anyway,
you
know
making
the
the
two
activities
currently
and
activities
of
the
state.
The
API
governance
and
review
process
and
the
conformance
efforts
to
be
well
runs
some
projects
that
more
people
can
get
engaged
with,
especially
more
people
in
the
other
SIG's,
where
those
folks
have
actually
an
expertise
in
the
variance.
That's
that's
really
ever
current.
Our
current
focus
for
our
current
goals.
A
A
It
was
about
who
would
show
up
and
do
things
as
far
as
work,
sig
architecture
gets
involved
in
a
conflicts
and
and
to
what
extent
I
think
in
the
way
that
we're
trying
to
disseminate
things
out
and
in
some
of
the
other
processes
like
the
cap
process
and
some
of
the
desire
to
document
the
architecture
patterns.
Those
kinds
of
things
start
to
fall
out
through
those
capacities
and
that's
how
it
happens,
but
does
that
at
least
help
or
is
there
something
else
you
wanted
to
push
back
on
and
bring
into
the
discussion.
U
U
A
U
E
So
I
I
would
just
say
that
you
know
we
can
frame
this
in
terms
of
solutioning
and
that's
again
skewing
toward
a
can,
but
I'm
really
reluctant
to
see
this
yet
again,
wind
up
in
a
mire
of
yes/no
decision-making
that
doesn't
even
there's
no
consensus
framework
for
us
to
make
a
decision
in
around
so
I
would
just
caution
against.
You
know
that
yeah.
B
I
would
like
to
follow
up
on
what
Matt
said,
which
is
we're
really
trying
to
double
down
on
cap.
So
I
think
caps
are
the
place
where
we
want
to
agree
on
how
to
move
forward
or
whether
to
move
forward
on
proposals.
So
that's
really
where
this
needs
to
get
addressed,
and
the
cap
is
moving
to.
Thank
you.
B
A
And
if
there's
something
that
comes
up
as
a
technical
issue
within
the
caps,
that's
architecture
related,
then
that's
definitely
fair
game
to
bring
up
here
in
the
mailing
list
or
in
some
other
capacity
that
we've
talked
about,
because
there
may
definitely
be
times
where
a
sig
wants
to
go
in
a
direction
that
doesn't
make
sense
and
it
doesn't
work
within
the
architecture
or
it's
an
API
change
that
isn't
being
brought
into
the
API
review
process.
Something
like
that,
but
most
of
the
time
there.
A
All
right:
well,
we
are
at
time
we
removed
a
20-minute
segment
and
we
still
filled
the
whole
hour.
Thank
you,
everybody
for
coming
and
being
involved
and
having
a
wonderful
conversation.
The
video
for
this
will
be
online
shortly
and
we'll
see
you
back
here
again,
two
weeks,
not
the
normal
one
week
time,
March
14th
have
a
wonderful.
Two
weeks,
see
you
all
online
thanks.