►
From YouTube: Steering Committee 20180606
Description
Chat log (times may be off):
00:00:57 Clayton Coleman: ohai
00:11:22 Timothy St. Clair: What’s the count for us to vote on stuff? Totally forgot.
00:11:36 Timothy St. Clair: the # ^
00:11:48 Sarah Novotny: I think It’s simple majority… which means we have quorum.
00:33:42 Timothy St. Clair: We should have guidelines, but I don’t think we should block
00:34:48 Timothy St. Clair: Thank you for not forking.
A
D
I
guess
a
couple
of
standing
things
we
had
were
the
Code
of
Conduct
committee
nominations
and
whether
when
we
wanted
to
close
that
and
whether
we
had
enough
nominations
and
then
the
Charter
reviews
I
guess
we
never
started
an
email
thread
on
the
mailing
list
about
that.
But
sig
apps,
for
example,
is
asking
about
their
Charter
and
I.
Do
want
to
make
sure
that
we
look
across
at
least
a
few
charters
before
we
decide
to
move
forward
with
them.
So
we
really
need
to
get
moving
on
that
yeah.
B
B
D
After
that,
and
we
have
a
bunch
of
new
SIG's
being
proposed
which
are
developing
their
own
and
they're
kind
of
moving
ahead
in
the
process.
But
at
the
same
time,
the
cloud
provider
there's
a
proposal
for
a
cloud
provider
sig-
and
you
know
so-
that's
sort
of
underway-
and
it's
muddying
the
water
about
whether
we
should
have
liked
sig
by
two-
and
you
know
some
of
the
others
that
have
been
proposed.
I,
don't
remember
the
full
full
list,
but
there
been
multiple
other
providers
proposing
SIG's.
D
C
A
We
do
have
the
proposals
for
new
SIG's
I
think
you
should
another
thing
related
to
this.
It's
return
approval.
We
should
find
a
process
to
be
able
to
make
the
call
on
that,
like
I,
think
you
know
we're
still
we're
kind
of
blocked
in
terms
of
how
to
make
progress
with
the
what
were
they
calling
it.
I'm
gonna
call
it
sig
SDK,
which
is
like
the
platform
tools,
provider,
stuff,
I,
think
you
know,
some
of
that
is
like
what
should
be
in
scope.
D
A
Well
and
again
again,
so
my
objection
there
at
least
you
know,
I,
don't
want
to
I,
don't
want
to
delve
into
the
details
here
without
the
right
folks
necessarily
putting
their
best
foot
forward.
But
but
my
objection
was
not
queue
builder
per
se
as
much
as
like.
Does
it
make
sense
to
have
a
sig
that
does
these
ancillary
systems
like
queue
builder,
when
really
the
elephant
in
the
room
is
that
we
need
an
SDK
that
actually,
that
actually
sort
of
looks
across
the
entire
developer
experience,
including
client,
go
and
I?
D
So
I
actually
think
that
all
the
client
libraries,
including
well
I,
would
say
all
the
client
libraries
should
be
in
the
SDK
sick
I
agree
with
that.
Whether
the
existing
client
go
or
not
should
be
something
we
actually
tell
other
users
that
they
should
use.
I
think
that's
an
issue
that
we
need
to
figure
out.
I
think
the
people
who
are
proposing
the
SDK
or
PDK
or
whatever
you
want
to
call
it
sync
didn't
want
to
make
it
look
like
they
were
trying
to
grab
stuff
away
from
API
machinery
and
that's
an
uncomfortable
discussion.
E
D
B
D
B
As
probably
the
most
probably
the
most
active
member
of
the
SDK,
maybe
the
only
member
of
the
SDK
group
I'd
be
happy
to
regen
like
if
we
gen
to
go
clients
and
I'd
be
happy
to
lift
or
re-implement
whatever.
We
need
to
produce
a
go
client
that
looks
more
like
the
Java
and
c-sharp
SDKs.
But
though
your
your
being
engineers
yeah.
A
Who's
bosun
because,
like
I
like
looks
I,
want
to
have
this
discussion.
We
should
have
this
discussion
and
I
want
to
respond
to
all
of
that.
I'm,
not
sure
this
is
the
time
and
place
for
that.
What
I
think
we
need
to
do
is
we
do
need
to
actually
be
able
to
have
a
conversation,
perhaps
as
part
of
these
sort
of
this,
the
steering
committee
to
office
hours
where
we
have
the
folks
making
that
case
in
we
actually
have
a
process
for
them
to
make
the
case,
and
then
we
make
a
call
yeah.
D
A
A
B
D
B
F
B
That's
trickier
right
because
it's
sort
of
like
that
requires
that
somebody
understand
the
union
of
everything
and
make
sure
there's
not
overlaps
and
I
feel
like
there's
a
few
of
these
things.
Like
I,
wouldn't
say
we
should
do
it
for
everything,
but
I
feel
like
there's
a
few
small
things
where
it's
worth
just
explicitly
delegating,
instead
of
having
the
Charter
implicit.
D
A
D
D
C
C
A
C
F
C
A
Do
we
want
to
take
a
you
know,
and
maybe
we
discussed
this
before
and
I
apologize?
Do
we
want
to
take
nominations
from
the
wider
committee,
because
we've
been
keeping
this
whole
sort
of
nation
process
a
little
bit
a
little
bit?
Scoped
I
may
be
seeding
it
to
the
first
time
we
actually
want
to
be
a
little
bit
more
careful.
Is
that
the
idea.
D
Well,
I
I,
don't
know
if
we've
established
how
these
folks
will
be
replaced,
but
committees
are
other
than
the
steering
committee.
The
committee's
on
the
project
are
not
necessarily
don't
have
membership.
That's
chosen
the
same
way
as
6,
for
example,
citizen
working
groups,
where
it's
open
to
everybody
I
think
we
do
need
to
be
selective.
I,
don't
want
it
to
be.
You
know.
Oh
yeah,
on
our
set
of
ideas
is
fine
but
I.
Think
handpicking.
The
folks
is
a
reasonable
thing
to
do.
A
D
E
D
D
D
A
B
A
D
A
A
A
That's
a
fair
point:
we
don't
have
anything
else
on
the
agenda
we
can,
we
can
leave
early
I
did
want
to
ask
one
quick
question:
I,
don't
want
to
rat
hold
on
it.
So
please
there's
this
idea
of
being
clear
about
what
powers
that
are
dedicated
to
say,
architecture
and
others
and
Brennan
was
going
to
take
a
note
on
I'm,
putting
together
a
fact
there.
One
question
that
came
up
and
I'm
not
quite
sure
who
to
ask
this
up
is
in
terms
of
do
different.
Six
and
different
sub
projects.
A
D
A
D
I
think,
ultimately,
it
needs
to
land
and
Sega
released
science.
A
good
architecture
could
say
that
the
project
should
be
doing
this,
but
signal
release
would
need
to
own
it
and
work
out
the
details.
That
has
definitely
come
up
that
thing
binaries
are
produced
and
pushed
and
that
we
don't
have
any
kind
of
clear
guidelines
or
rules
about
where
they're
allowed
to
live,
whether
they
have
to
be
signed
or
not
about
they're,
like
all
kinds
of
implications
about
this
every
sub
project,
that's
outside
of
kubernetes
communities.
Does
this
a
different
way.
B
A
So
so
what
I'm
taking
away
here
is
that
is
that,
whether
or
not
we
should
be
doing
off
cycle
releases
and
who
does
what?
Where
and
where
that
code
has
to
live.
That's
kind
of
a
policy
thing
that
probably
lands
in
sig
architecture,
the
mechanics
around
signing
and
how
and
where.
And
you
know
that
stuff-
that's
a
sig
release,
type
of
thing.
Yeah.
F
Sure-
and
it
well
run,
the
Related
Topics
can
I
give
him
a
quick
update
on
the
core
DNS
issue
that
was
up
a
few
weeks
ago.
So
the
the
decision
that
I
took
from
there
was
not
to
fork
your
DNS
into
our
space,
so
I
took
their
continued
images
that
they
published
to
docker
hub
as
they
manifest
this
and
I
mirrored
them
into
our
GCR
for
the
111
released.
So
anybody
can
pull
Kate's
GCR,
that
io
/,
core
DNS
:,
1,
1,
3
and
accordian
s.
D
D
That
to
cig
release,
honestly
I,
don't
think
that
should
be
in
our
wheelhouse.
Exactly
yeah
I
mean
sick
architecture
is
kind
of
responsible
for
consistency
across
the
project
and
overall
guidelines,
and
things
like
that.
But
yeah.
The
technical
details
of
things
that
are
owned
by
specific
SIG's
and
I
think
does
fall
under
sig.
Release
are
up
to
those
things.
D
C
You
and
I
had
been
talking
about
some
of
the
people
and
groups
in
different
parts
of
the
community
that
are
asking
for
things
without
providing
support
and
chopping
wood
and
carrying
water
for
the
project,
and
this
might
be
a
really
good
way
to
get
them
involved
in
something
that
the
project
needs.
That's.
D
Bugs
to
fix
and
things
like
that-
that's
gonna
fall
on
through
the
cracks
ideals
and
we
still
like
I
was
reviewing
trying
to
make
my
way
through
some
of
the
caps
and
I'm
proposin.
We
still
have
people
who've
never
submitted
a
PR
before
whose
companies
never
submitted
a
PR
before
show
up
with
such
a
massive
proposal,
and
it's
clear
they
don't
understand
the
system
or
the
basics
or
the
expert
so
clarifying
some
of
that
I.
D
At
the
contributor
guide
and
the
language
is
in
somewhat
muddled
area
about
how
to
get
started
like
it
does
say,
show
up
at
a
cig
and
the
faster
the
guidance
about
how
to
get
faster.
Pr
reviews
used
to
be
more
clear
about
this.
You
know
don't
show
up
with
10,000
long
small
or
something
like
that,
and
it's
it's
no
longer
as
clear
yeah.