►
From YouTube: Steering Committee 20180815
Description
Notes: https://docs.google.com/document/d/1qazwMIHGeF3iUh5xMJIJ6PDr-S3bNkT8tNLRkSiOkOU
Chat (times may be off):
00:58:47 Joe Beda: (I'm on vacay for 2 weeks starting next week)
01:03:24 Michelle Noorali: i have to drop in a minute too
A
A
B
B
There's
a
copy
of
the
steering
committee
election
voting
guide
that
is
checked
into
events.
Elections.
2018
read
me
here:
I
need
to
minimize
this
screen
real,
quick
and
I.
Think
maybe
this
is
the
thing
that
talks
about
sig
leads
eligibility.
Members
of
standing
are
defined
by
the
union
of
all
this
stuff
plus
active
members.
B
So
the
thing
that's
bugging
me
about
this
poll
request
is
that
we
also
have
documentation
over
in
the
steering
repo
kubernetes
steering
elections
MD
and
that
doc
is
out
of
date
and
does
not
include
any
of
the
verbage
around
the
dev
stats
based
criteria
for
members
of
standing.
It's
also
a
little
bit
more
verbose
about
maximal
representation
vacancies
and
a
couple
of
other
things.
I'm
of
the
opinion.
There
should
really
only
be
one
single
source
of
truth
for
the
elections,
processes
and
policies.
Where
should
that
be?
B
C
Yeah,
my
personal
feeling
is
that
we
defector
are
adjusting
the
criteria
every
year
based
on
more
experience,
more
data
available,
etc,
and
that
seems
fine
to
me,
so
we
publish
it
every
year
based
on
what
we
decide
that
year.
We
could
also
have
a
sort
of
an
overarching
policy
which
says
whatever
we
decide
to
do
in
a
given
year.
It
must
not
contravene
any
of
these.
You
know
golden
rules
that
we
think
should
always
apply.
B
B
D
C
C
D
C
C
B
Okay,
so
going
forward,
our
decision
is
just
dev
stats,
not
at
the
implicit
sigelei
stuff.
It
stands
course
exceptions,
s+,
exception,
sorry,
yeah
the
exception
process.
We
trust
that
the
election
committee
is
handling
and
Quinton
and
I
are
going
to
make
sure
that
we
are
reviewing
the
possible
the
documents
that
the
election
committee
puts
through
they.
They
need
to
be
made
aware
that
they
can't
just
merge
things
without
us.
Taking
a
look
at
that.
Well,
in
my.
C
E
B
C
Was
actually
a
question
from
from
the
election
group
asking
which,
which
of
the
two
we
prefer
they
had
them
in
the
community
repo
and
did
we
want
them
to
move
it
to
the
steering
committee,
repo
and
I
said
I
didn't
feel
strongly
enough
about
it
to
move
it,
so
maybe
I
should
have
moved
it.
I
was
unaware
of
the
kind
of
implications
of
it
just
I.
E
B
E
C
B
Okay,
just
walking
us
through
the
rest
of
the
board
real
quickly
documenting
how
working
groups
should
be
formed.
There's
been
no
movement
on
that
since
two
weeks
ago,
where
that
stands
well,
as
Brendan
was
supposed
to
open
up
a
pull
request,
but
the
contents
of
the
Google
Doc
that
James
put
together
if
nobody
picks
that
up
in
the
next
week,
I'll
get
it
PR
shortly
codifying
steering
committee
liaisons
for
SIG's
in
this
exam.
Oh
that's
on
me.
B
Charters,
the
meta
issue:
does
anybody
have
any
progress
or
updates
to
report
with
respect
to
their
charters?
I
went
like
I
can
start
and
say
that
I
went
through
and
updated
the
top
portion
of
this
issue
as
best
as
I
could,
prior
to
the
community
meeting
last
week,
and
gave
the
heads-up
that
these
three
had
been
merged
and
that
these
were
under
review
and
that
we
would
be
coming
to
other
SIG's
kind
of
ones
created
through
this
backlog.
B
D
D
I
think
I
need
to
come
to
a
meeting
or
something
to
discuss
that
I
said
you
know,
but
didn't
get
a
response
from
most
of
the
leads
or
chairs
or
whatever
they
are
now.
I
did
have
a
conversation
with
Ken
about
it,
but
I
want
to
make
sure
that
we
loop
in
the
other
sig
leads
as
well,
but
the
the
CLI
a
second.
D
B
Fire
engines-
okay,
I,
mean
I,
didn't
hear
a
ton
of
resounding
feedback
when
I
presented
on
this
at
the
community
meeting.
We
were
also
kind
of
tight
for
time,
but
let's
see
if
we
can't
make
some
more
progress
on
this
I
know
I'm
definitely
guilty
of
on
the
bottleneck
for
one
of
these.
So
let's
get
the
ball
back
in
other
six
courts
and
keep
it
moving
any
does.
F
B
I
said
Brian
I
went
through
and
I
updated
from
here
down
to
here,
prior
to
last
week's
community
right
before
last
week's
community
meeting,
so
I
haven't
touched
it
in
about
a
week.
I
will
actually
touching
it
when
I
have
something
to
change
on
land.
That's
on
this
is
a
real
pain
in
the
butt
to
keep
track
of.
It
really
is
I'd
like
to
find
a
better
way
than
this,
but
this
is
what
we
have
for
now.
D
D
Thing:
oh,
no,
no
I,
just
one
general
thing,
I
observed
about
these.
The
charters
I
looked
at
is:
there
was
somewhat
of
a
gap
between
the
things
the
sake
historically
did
and
the
things
that
align
with
the
project
or
and/or
that
were
being
documented
in
the
Charter
like
I,
do
want
to
try
to
avoid
sort
of
land
grabs
in
charters
that
the
six
haven't
actually
materially
been
doing
things
not
to
necessarily
say
yeah.
This
should
definitely
own
that.
So
that's
maybe
something
to
be
aware
of,
and
then
sig
apps
I
think
there
are
some.
D
The
biggest
debate,
I
think
was
around
things
in
scope
for
cig
apps
that
don't
strictly
ball
in
their
community
scope,
so
that
I
think
we're
gonna
need
to
resolve
and
I
initiated
that
discussion
in
a
couple
of
places.
But
if
other
people
want
to
talk
about
that,
we
can
discuss
it
at
a
future
meeting
or
in
a
separate
email
thread
or
something
it's.
B
D
D
And
to
some
degree
it
relates
to
my
earlier
thread
about
rationalizing
working
groups
which
are
irrational
today
and
we
haven't
even
got
to
working
group
charters,
but
one
sig,
that's
not
in
this
list.
I
think
is
sick,
big
data
and
one
of
the
things
I've
given
them
a
heads
up
about
is
that
I?
Don't
think
it
should
be
a
thing
so
and
it's
a
sink
for
historical
reasons,
not
because
it
actually
makes
sense
to
music
yeah.
It's
down
that
little
sickening
data,
so
I'll
raise
that
in
the
in
the
same
email
thread.
B
Okay,
so
we're
a
time
here
we
are
at
time.
So
speaking
of
rationalizing
I
kind
of
kicked
the
hornet's
nest
around
cloud
provider,
another
cloud
provider,
six
I
didn't
mean
to
kick
that
conversation
off
I'm
just
trying
to
go
through
and
get
every
single
repo
assigned
to
every
single
sig.
That's
the
meta
thing.
B
I
just
wanted
to
talk
about
real
quick,
because
Jase
can
yell
at
the
recording
later
I,
don't
know
which
issue
this
should
fall
under,
but
I'm
going
through
and
hitting
every
single
repo
that
we
manage
and
gradually
starting
to
turn
up
automation
for
all
of
them
make
sure
they
all
have
owners
files
make
sure
they're
all
tracked
under
60
ml,
so
I'm
keeping
track
of
it
in
a
table
here
that
I
will
keep
up
to
date.
I'm
gonna
announce
this
at
the
community
meeting
I
talked
about
it.