►
From YouTube: 2020-08-27 Istio Community Meeting
Description
Introduce the new Istio steering committee charter and elections
A
So
we're
supposed
to
have
this
this
community
meeting
last
week,
but
we
scheduled
it
to
this
week
for
because
there
was
kubecon
last
week,
but
and
the
timing
also
works
out
great
for
us,
because,
as
many
of
you
probably
already
seen,
we
updated
the
steering
committee
charter
and
as
part
of
that
charter,
a
couple
of
you
know
a
few
extra
seats
opened
up
and
we're
holding
elections.
For
so.
The
first
thing
we
wanted
to
cover
in
this
call
is
an.
A
B
Yeah,
I'm
happy
to
do
that.
The
the
I'll
start
with
the
duties
of
the
of
the
toc
in
the
steering
committee.
The
steering
committee
is
first
of
all,
the
toc
is
the
committee
that
is,
as
this
says,
composed
of
individuals.
Those
seats
aren't
granted
to
companies,
those
are
granted
to
people
and
they
are
people
who
have
shown
leadership
in
the
project.
B
Is
in
charge
of
the
administrative
aspects
of
the
project
is
also
in
charge
of
communications,
and
I
will
say:
marketing
I'll
put
finger,
quotes
right
on
that,
because
we
really
don't
do
much
real
marketing,
but
it's
really
administrative
and
and
marketing
guidance
for
the
project.
So
how
do
we
speak
publicly?
We
we
do
write
the
kind
of
orders
of
the
you.
B
The
bylaws,
if
you
will
and
in
the
steering
committee
as
as
you'll,
see
as
craig
and
as
rom
go
over
it,
we
have
always
had
seats
for
companies
and
and
in
in
doing
that,
we
want
to
encourage
companies
to
invest
in
the
project.
So,
on
the
technical
side,
we
are
rewarding
individuals
who
are
you
know,
dedicating
time
to
the
project
and
and
showing
leadership
in
the
project
and
in
the
steering
committee.
B
Our
attempt
is
to
reward
companies
for
for
dedicating
resources
to
the
project
and-
and
that's
the
steering
committee
as
you'll
see,
is
a
combination
of
different
seats.
But
some
of
the
seats
on
the
steering
committee
will
be
granted
to
the
companies
who
are
essentially
spending
a
lot
of
money
on
the
project
in
the
form
of
employee
time.
A
A
Right
right
so
I
mean,
as
dan
said,
and
the
steering
focuses
on
governance
aspects,
so
the
bylaws
of
they're
responsible
for
the
bylaws
of
the
steering
committee,
as
well
as
the
technical
oversight
committee
they're
responsible
for
the
community
itself.
So
like
the
the
developers,
the
contributors,
the
vendors
they're,
also
responsible
for
the
community
tools,
such
as
slack
discuss.
A
You
know
running
meetups
when
we
had
them
the
blog
et
cetera
trademark
issues.
So
the
ouc
owns
this
year
trademark.
So
if
there's
any
issues
with
that,
the
the
steering
committee
is
responsible
for
advising
the
ouc
marketing
and
advocacy
as
dan
covered,
and
then
they
also
control
the
the
resources
that
it
takes
to
run
these
to
your
project.
A
So,
as
we
said,
you
know
it
takes
a
lot
to
for
istio
to
be
successful,
not
just
you
know,
developers
and
contributors,
but
also
there's
advocates
marketing
dollars,
writers,
etc.
So
and
there's
many
companies
that
that
make
this
investment,
so
the
the
new
charter
is
created
so
that
we
reflect
as
much
of
that
as
possible
and
give
voice
to
as
many
of
those
contributors
and
and
companies
as
possible.
A
A
couple
of
the
other
goals
of
the
charter
is
that
no
single
company,
regardless
of
how
much
they
they
contribute
in
terms
of
percentage,
has
the
ability
to
to
single-handedly
win
a
vote
or
single-handedly
veto
a
decision
we
know
without
the
rest
of
without
other
people
from
the
the
community
there
are
13
total
seats.
These
are
going
to
be
made
up
of
contribution,
seats
and
community
seats.
A
A
The
contribu
the
contribution
seats,
so
this
makes
up
nine
out
of
the
13
total
seats,
and
the
point
of
these
contribution
seats
is
to
give
voice
or
give
seats
to
companies
that
make
the
most
most
measurable
contributions
right.
There
are
multiple
ways
to
measure
a
company
contribution,
and,
and
for
this
term,
we've
decided
that
just
going
by
the
pull
request
from
a
company
for
the
last
12
months
would
be
a
good
starting
point
now,
the
next
term.
B
B
B
There
was
some
concern
that
metrics
could
be
gained,
and,
and
so
we
decided
to
not
kind
of
formalize
in
the
charter.
What
the
metric
would
be
because
if,
if
we
feel
like
anyone
is
gaming,
I
don't
think
it's
very
likely.
Frankly,
we
think
this
is
pretty
good.
We
looked
at
much
more
complicated
formulas,
none
of
which
seemed
to
add
value
or
turn
into
a
what
would
have
resulted
in
anything
different.
So
we
are.
B
C
B
A
This
also
involves
a
cap
of
five
total
contribution,
seats
that
are
allowed
per
company,
so,
regardless
of
what
their
percentage
contribution
would
be
with
like
merge
pull
request,
they
would
be
capped
at
five
and
then
the
remaining
seats
can
go
down
to
the
the
the
next
set
of
companies.
So
this
with
the
current
formula
would
equal
out
to
be
five
from
google,
three
form
ibm
and
red
hat,
and
then
salesforce
now
gets
a
seat.
C
Yeah
two
little
things
that
I'll
add
there
it's
a
minimum
of
three
companies.
We
deliberately
did
not
make
that
a
maximum.
So
in
the
event
that
there
are
a
lot
more
contributions
from
other
companies,
you
could
imagine
nine
different
companies
each
getting
one
seat
each
if
the
numbers
added
up
that
way
and
we're
not
only
talking
about
merge,
pull
requests
in
terms
of
code.
This
is
not
just
on
the
stostea
repository.
A
Okay,
so
moving
on
to
community
seats,
so
four
out
of
the
thirteen
total
are
community
seats.
There
are
contributors
to
istio
that
or
there's
contributions
to
istio
that
are
not
just
pull
requests
to
to
the
source
code
or
to
the
documentation,
there's
large
and
small
companies
that
contribute
to
istio.
In
other
ways
these
this
could
be
from
like
leadership.
A
You
know
whether
they're
reviewing
design
documents,
whether
you
know
they're
talking
about
istio
they're,
community
leaders,
they're
talking
about
istio
and
and
conferences,
etc,
and
we
wanted
to
give
voice
to
these
these
individuals,
it's
large
and
small
companies
as
well.
So
the
four
seats
that
are
the
community
seats
are
to
be
voted
by
the
istio
community
in
in
an
election
and
that's
the
election
that
we're
going
to
talk
about
next.
C
I
don't
think
we
explicitly
say
it
might
come
up
in
the
elections,
but
there's
a
we
should
actually
check
and
see.
If
it's
gonna
come
up.
You
cannot
have
a
community
if
you're
employed
by
a
company
that
has
a
contribution
seat
so
googlers
and
people
from
ibm
red
hat
salesforce
aren't
eligible
for
this
and
there
is
a
maximum
of
one
community
seat
per
organization.
So
there
are
four
seats.
There
will
be
four
different
organizations
represented
here.
A
A
So
that's
this
election.
The
point
of
this
election
is
to
appoint
those
four
those
four
seats,
those
four
you
know
community
members
to
the
steering
committee,
craig
from
google
who
was
just
talking
and
I
ram
or
the
election
officers
were
just
there
to
kind
of
help.
This
election
process
craig's
doing
most
of
the
work.
I'm
just
tagging
along
graham
says.
A
If
they
accept
your
your
nomination
or
they
accept
their
own
nomination,
they
will
submit
a
pull
request
with
a
short
like
300
word,
biography,
into
the
same,
like
istio
community
you'll,
see
in
elections
in
the
2020
folder,
where
you'll
see
a
list
of
all
the
names
and
they'll
submit
their
bio
and
markdown
format.
So
you
can
go
see
what
are
all
the
candidates.
A
The
voting
process
who's
eligible
to
vote
any
project
member
who's
submitted.
A
pull
request
in
the
last
12
months
gets
automatically
added
to
the
eligibility
list.
You
could
have
contributed
to
istio
in
other
ways.
That's
not
a
pull
request.
So
if
you
feel
like
that's
the
case
with
you,
there's
this
voting
exception
form
that
you
can
fill
out
and
then
I
get
submitted
to
the
steering
committee
and
we'll
review
it
and
then
see.
A
A
Missed
the
schedule
the
candidates
will
submit
their
bios
and,
if
you're
a
voter-
and
you
want
to
the
voting
exception-
forms
if
you
want
to
vote,
they
are
all
due
by
september.
6Th.
The
exact
time
is
documented
in
the
in
that
markdown
file
that
I
have
linked
on
the
bottom
september.
14Th
is
when
the
election
begins
using
email
ballots
september.
27Th
is
when
the
election
closes
and
then
the
week
of
september
29th
we'll
process
everything
and
then
announce
the
winners.
B
C
B
Recognize
the
names
of
many
of
the
partners
that
I
expect
to
be
interested
yeah.
I
I
will
say
a
little
bit
behind
the
philosophy
here
of
the
community.
Since
I
did
talk
about
the
the
contribution
seats
and
the
contribution
seats
are,
as
I
said,
exist,
to
ensure
that
the
the
companies
who
are,
who
are
really
you
know
putting
putting
their
money
in
in
terms
of
employee
time
making
sure
they
get
represented.
B
B
But
there
are
also
a
lot
lots
of
good
things
about
the
project
as
much
as
we
try
to
stay
out
of
twitter
flame
wars.
I
think
that,
as
a
result
of
that,
there's
a
lot
of
miscommunication
about
the
project
that
by
far
the
most
diverse
set
of
contributors
like
a
much
larger,
set,
whether
you
look
at
just
raw
numbers
of
people
or
you
look
at
the
number
of
companies
contributing.
C
B
Those
companies
who
we
want
to
make
sure
are
represented
as
well,
and
that's
why
the
community
seats
really
exist
is
to
ensure
that,
even
if
they're,
not
in
the
top
three
contributors
to
source
code,
they
still
can
help
us
shape.
How
how
the
the
the
project
is
viewed
in
the
community
and
then
finally,
with
the
company
like
salesforce.
It's
great
because
they're,
neither
of
those
there's
just
a
user,
but
they
have
a
real
just
a
user,
but
they
have.
B
B
A
A
A
A
couple
of
the
highlight
features
that
stood
out
for
me
is
vm.
Integration.
Istio
has
had
mesh
expansion
to
vms
for
a
few
releases
now,
but
in
one
seven
it
was
it's
greatly
improved
from
a
security
perspective.
There's
a
new
workload
api
that
treats
vms
as
as
like
kubernetes
pods,
so
you
can
control
it
using
apis.
A
A
The
operator,
the
operator's
canary
control,
plane
updates,
has
been
improved
on
the
last
community
called
steve
showed
a
quick
demo
of
this.
So
if
you're,
using,
if
you're,
upgrading
istio,
you
know
you
can
do
like
canary
rollouts,
where
you
test
out
a
new
control
plane
and
go
back
or
you
can
do
like
a
b
versions
where
you
deploy
a
new
control
plane
and
then
slowly
migrate,
traffic
to
the
new
control
plane
and
then
remove
the
old
one.
A
For
delaying
your
application
start
until
envoy
until
sidecar
is
started,
so
if
you've
noticed
issues
where
your
application
starts
up
really
fast
before
envoys
starts
up,
you
might
have
noticed
that
it's
not
able
to
communicate
like
outbound
until
the
sidecar
was
ready.
So
this
flag
will
delay
your
application
start
and
a
couple
more
things.
So
this
talks
about
running
the
gateway
as
not
root.
I
I
believe
we
also
run
istio
d
as
non-root
by
default.
Now
in
one
seven,
the
the
now
that
the
gateway
is
running
is
non-root.
A
If
you
had
any
custom
ports
that
you
were
exposing
from
the
gateway,
so
not
the
target
port
pointing
to
your
application,
but
your
if
you're
exposing
ports
on
the
gateway
service
itself.
I
I
believe,
if
you're
starting
to
see
some
problems,
keep
an
eye
out
that
you
know
this
might
be
due
to
something
related
to
to
non-root,
but
for
for
majority
of
the
cases
this
shouldn't
have
any
effect
on
you
and
then
last
but
not
least,.