►
From YouTube: Open Match Community Meeting April 2019
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
You
can
always
go
back
and
get
a
copy
of
the
previous
meeting
if
you
missed
one.
So
all
right.
Well,
it's
a
way
of
saying
hello.
Thank
you
all
for
being
here
and
joining
us.
There
are
herbs
and
eating.
My
name
is
April.
We
haven't
connected
yet
before,
and
you've
probably
seen
me
on
some
of
the
emails
and
the
sort
of
other
fun
things
and
I
am
an
open-source
strategist
here
at
Google
Adam,
so
I'm
specifically
focused
on
open
source
awesomeness,
specifically
with
our
game.
A
Whimmy,
open
source
project,
so
open
match,
and
the
gona
is
moment
so
I'm
happy
to
help
with
any
sort
of
questions
or
ideas.
You
have
around
getting
involved,
contributing
all
of
that
great
stuff
just
feel
free
to
reach
out
I.
Believe
my
email
is
in
the
dock.
Yes,
it
is
so
anytime.
You
need
anything.
Just
shoot
me.
An
email
happy
to
help
out.
A
I
have
a
couple
of
announcements,
but
I
just
wanted
to
call
out
to
folks
and
again
the
links
are
in
the
working
doc,
but
the
first
is
that
there's
this
really
exciting
thing
happening:
we've
been
working
with
the
Linux
Foundation
on
this
interest
that
we're
seeing
now
with
gaming
and
open
source,
there's
been
a
lot
more
discussion
around
this
and
kind
of
talking
through
some
of
the
things
that
we
can
do
to
make
this
a
bigger,
broader
community.
So
the
Linux
Foundation
has
an
event
in
August
this
year.
A
It
is
the
open
source
summit,
North
America.
It
takes
place
in
San
Diego.
Apparently
this
year
seems
like
all
the
conference's
are
in
San
Diego,
so
it's
in
August
and
right
now
there's
a
call
for
papers.
So
if
you're
interested
in
speaking,
the
CFP
is
closing
May
4,
so
that's
next
week
highly
recommend
applying
right.
Now,
it's
basically
a
half-day
event.
A
Sessions
run
about
thirty
five
minutes
if
you've
never
presented
at
a
Linux
Foundation
event
before
they
do
a
really
great
job
with
speaker,
prep
and
kind
of
helping
out
making
sure
you
know
that
you've
got
all
the
resources
you
need.
As
a
speaker
so
bring
up
your
first
time-
and
you
know
not
sure
about
speaking
I
highly
recommend
going
ahead
and
submitting
a
talk,
and
we
are
always
happy
to
help.
A
You
know,
review
and
kind
of
help
you
prep
up
as
well
so
highly
recommend
checking
that
out
and
if
nothing
else
check
out
the
link
and
please
do
join
us
I
think
it's
going
to
be
great.
This
is
a
really
great
kickoff
for
getting
this
kind
of
involvement
going
around
it's
open
source
and
gaming.
So
the
second
thing
is
season
of
dogs,
if
you're
at
all
familiar
with
the
Google
Summer
of
Code,
which
is
where
different
open
source
projects
apply
to
have
folks
work
on
their
projects
during
a
summer,
it's
usually
usually
students.
A
Season
of
Docs
is
very
similar,
except
it's
all
about
box
and,
as
lindsay
indicated,
we
need
some
help
with
those.
So
we've
applied
to
be
in
season
of
dogs.
The
process
for
reviewing
is
happening
now
and
we
should
know
by
the
end
of
the
month
if
we're
accepted,
and
then
if
we
are
accepted,
we
will
get.
A
You
know
whoever.
Then
the
process
goes
where
writers
will
go
and
apply
to
be
part
of
the
program,
and
the
process
is
that
we
have
a
document
of
basically
our
wish
list
for
documentation.
So
any
ideas,
you
have
anything
that
you
think
gosh.
We
really
need
this
I
highly,
encourage
you
to
put
it
in
that
doc,
because
people
that
are
applying
as
writers
in
the
program
are
going
to
use
that
doc
to
determine
what
cool
project
they
can
work
on.
A
So
that'll
also
give
them
some
help
as
they
write
their
application,
and
should
we
not
get
accepted,
don't
your
work
is
not
in
vain,
we'll
turn
that
end
to
issues
for
a
documentation
repo
as
we
go
forward.
So
please
do
if
you've
got
any
ideas
for
cool
stuff.
That
would
make
your
life
easier
to
use
or
develop
on
open
match.
Please
add
it
there
and
we'll
get
it
on
the
list.
B
A
B
A
C
So
I'll
presented
or
not
do
I
just
go
present.
How
does
okay.
D
C
Good,
perfect,
okay,
so
yes,
I
was
gonna
start
with
exactly
that,
so
I
guess.
Right
now
we
had
an
RC
for
open
mic
dot
v
and
that's
the
current
state
I
a
big
in
the
documentation
to
kind
of
reflect
all
the
changes
that
have
happened
in
RC
and
as
a
part
of
that
update.
What
went
through
was
the
updated
future
roadmap
as
well.
C
So
now,
if
you
kind
of
go
on
the
open
mic
documentation
page
for
the
roadmap,
it
kind
of
reflects
what
what
the
current
thinking
around
the
roadmap
is
quick,
quick
context.
1.5
itself,
although
we
are,
we
are
already
close
to
shipping
it
on
the
internet,
dot
v
to
be
a
usability
kind
of
release,
so
the
goal
at
the
end
of
dot
v
was
supposed
to
be.
Somebody
could
just
pick
it
up.
Try
and
have
concrete
to
do
that.
C
We
intended
to
me
builds
a
lot
simpler,
deploying
simpler,
so
essentially,
the
end-to-end
experience
for
somebody
in
trying
open
match
for
the
first
time
was
intended
to
be
a
lot
simpler
in
dot
v
with
the
change
documentation.
I
urge
everybody
to
kind
of
go
try
this
out.
It
should
actually
by
design
not
take
so
much
time.
It
should
actually
also
not
require
the
basic
set
of
steps.
Don't
even
require
you
to
pull
the
code
down.
They
should
actually
just
using
artifacts
posted
in
google
storage.
C
So
so
you
should
try
those
out
and
give
us
feedback
while
we
are
in
RC,
so
that
we
are
intending
to
fact
the
actual
release
tomorrow,
but
if
folks
run
into
any
glitches,
please
let
us
know
so:
that's
dot,
five,
some
of
the
key
things
that
also
went
into
dot
v
worth
noting,
are
gr
pc-based
serving
or
like
a
harness.
So
now
we
have
completely
deprecated
the
mechanism
to
actually
schedule
MMF
as
kubernetes
jobs.
The
only
thing
now
supported
is
to
stand
up
your
MMF
as
a
harness
and
open
match.
C
We
called
into
that
harness.
The
same
goes
with
the
evaluator,
so
basically
there
was
a
component
which
was
the
orchestrator.
That's
been
completely
deprecated
now
for
now,
the
evaluator
itself
is
also
a
persistent
service
that
stands
up
and
essentially
it
does
the
evaluation
periodically.
But
again
there
is
no
triggering
to
the
evaluator.
So
those
the.
F
C
Reason
I
mentioned
those
as
the
critical
is
because
that
has
significantly
changed
the
examples
and
the
the
test,
clients
and
n
stuff
we
had
so
folks
who
are
using
the
old
ones,
should
take
a
look
at
the
new
ones
and
kind
of
work
from
there,
and
also
note
there
is
now.
We
only
have
Bowlin
examples
for
now
I
wish
like.
If
there
is
interest,
we
can
kind
of
have
contributions
to
build
other
language
harnesses
and
and
take
it
from
there,
but
right
now
we
just
have
the
:
harness
check
it.
C
That's
not
5.6
I
try
to
high
level
the
goal
4.6
now
that
we
have
not
five
as
usable
is
you've
been
discussing
a
lot
of
like
the
futuristic
requirement,
like
with
respect
to
scale
and
production
ization
with
the
unity
folks
and
based
on
their
experience,
using
open
back
so
far
as
well,
and
so
what
we've
come
up
with
is
a
set
of
like
a
proposal
that
is
essentially
a
set
of
changes
to
the
API,
a
data
model
fodder
or
a
match.
I've
created
a
proposal
for
this
have
added
the
actual.
C
If
you'd,
like
the
API
surface
and
the
new
data
model
and
the
justification
for
that
appear
in
there,
I
was
talking
about
it
with
each
last
week
as
well,
so
just
go
or
that
we
would
love
feedback
on
that.
It's
a
to
be
clear.
It's
kind
of
a
significant
breaking
change
from
dot
five
in
terms
of
just
the
API
surface,
we
may
even
end
up
renaming
the
services
as
as
we
know
them
so
internally.
We
still
need
to
discuss
and
suggestions
are
welcome,
but
we
don't
want
to
kind
of
discipline
one.
C
So
we
can
actually
do
like
a
not
an
in-place
change,
but
like
a
parallel
services,
kind
of
kind
of
a
thing
to
yy-you
know
the
current
ones
are
still
still
up
and
running
right
now.
The
goal
4.6
is
essentially,
this
is
kind
of
should
hopefully
be
like
you
know.
We
still
have
room
to
change.
The
API
is
still
one
dot
off,
but
for
a
major
like
this
is
what
we
think
is
like
the
future
direction.
This
intends
to
be
that
I
made
you're
breaking
it,
be
I
change.
C
So
hopefully
we
should
all
agree
on
how
the
changes
and
if
not,
we
can
like
get
feedback
and
and
iterate
on
them.
But
basically
the
idea
is
I
thought
six.
We
should
have
like
a
solid
API
surface,
which
can
then
have
minor
tweaks,
but
folks
should
be
comfortable
building
their
matchmakers
against
this,
with
a
hope
that
it
doesn't
completely
break
them
in
between
this
end
rock
wall.
So
that's
kind
of
the.
F
C
Here
the
other
thing
I
mentioned
there
is
maturity,
so
what
that
really
means
is
we
would
be
actually
adding.
So
today
we
aren't,
there
aren't
many
test
cases
end
to
end
test
cases,
unit
tests
and
stuff
like
that,
so,
hopefully,
with
as
we
are
kind
of
building
these
new
API
surfaces,
we
we
intend
to
like
add
testability
is
be
authoritative
about
like
what
the
best
framework
should
be
like
a
test
for
each
of
these
components.
C
End-To-End
tests
we
already
have
CI,
set
up
in
this
current
version,
so
we
hopefully
have
the
test
like
three
summits
and
err-
that's
wired
up
into
into
the
CI
and
stuff
like
that,
so
we
kind
of
get
a
better
quality
releases
out
in
future.
Outside
of
that,
let
me
see
if
anything
pops
up
I
spoke
about
the
test.
Yes,
obviously
with
the
epi
change,
I
could
make
sure
that
all
of
the
existing
examples
is
the
hardness.
The
the
new
tools
and
stuff
like
that
addresses
like
with
like
the
API
changes.
C
The
one
thing
I
would
want
to
make
sure
is,
is
on
the
radar
is.
If
4.5
we
build
more
harnesses
for
different
languages,
then
those
would
need
to
potentially
be
ported
to
whatever
changes
happen
in
dot
six,
so
I
just
put
want
folks
to
be
mindful
of.
If,
if
you
really
need
something
for
not
five-year,
we
can
work
and
make
sure
that
we
can
port
it
later.
If
you
can
wait,
then
it
might
as
well
talk.
Six
might
be
the
the
version
you
kind
of
build
stuff
against.
That
might
be
that's
unethical.
G
It
was
a
small
matter
from
our
end
is
we've
been
building
on
the
we've
been
building?
On
top
of
where
we're
headed
with
the
dot
six
API,
it
seems
to
be
working
pretty
well,
we
have
some
kind
of
into
in
testing
that
we've
been
doing
it
so
far.
Everything
seems
to
be
moving
pretty
good,
so
this
is
really
exciting.
Perfect.
Thank
you.
C
Okay,
so
beyond
that,
the
the
one
note
on
here,
4.7
and
Beyond,
is
since
that's
a
little
further
out
and
actually
let
me
speak
to
the
release
cadence
first,
so
we
started
off
with
like
a
six-week
release,
cadence,
and
that
was
something
we
were
working
like
you
know
as
like
a
principal
I
think
4.5.
We
made
it
much
shorter,
like
it
was
three
weeks
kind
of
turnaround,
three
or
four
weeks
and
4.6.
It
might
be
slightly
longer
a
little
longer
than
that
we
will
see.
C
We
will
try
to
shoot
for
six
weeks,
but
based
on,
like
the
the
magnitude
of
changes
and
pretty
much
the
changes
to
all
the
examples
and
harnesses
and
everything
it
might
have,
we
might
have
some
bigger
room
there
after
that,
hopefully
we'll
settle
in
into
like
of
specific
release.
Cadence
April
I'm,
not
sure
if
the
release
cadence
for
open
match
and
a
goodness
and
everything
kind
of
tired
in
the
same
foundation
should
necessarily
match
or
whether
is
there
any
guidance
there
with
just
the
cadence
itself.
C
A
Weeks
is
usually
a
good
routine
for
folks,
but,
like
you
said
you
know,
sometimes
it's
shorter
and
that's
good,
so
there's
no
hard
dependency
at
the
moment.
I
just
think
it's
you
know
it's
good
to
kind
of
have
a
standard
that
we
keep
spoke,
keep
the
folks
to,
but
I
just
got
questioned
last
night
on
another
project.
If
why
the
releases
were
all
in
a
weird
cadence,
okay,
good.
C
So
that
said,
I
think
yeah
so
4.7.
Hopefully
we
will
have
like
a
good
breeze
cadence
by
from
between
dot,
seven
and
dot
poem
apply.
My
thoughts
are
not
seven
right
now,
I
have
everything
that
we
think
is
required
for
production.
Izing
should
be
in
dot
seven.
So
the
reason
I
don't
call
it
a
one
dot
o
yet
is
I'm
sure
between
now
and
finishing
dot,
six
we
will
have
a
lot
of
other
feature
requests
and
things
will
get
prioritized
out
of
there.
C
But
if
you
see
the
list
4.7
that's
kind
of
a
lot
of
things
there
to
actually
get
open
match
to
a
point
where
books
could
host
it
in
production
and
of
those
are
the
kind
of
features
there.
So
again,
the
reason
I'm
saying
that
is,
we
may
have
more
feature,
work
that
gets
front
loaded
and
some
of
those
things
get
pushed
out
to
the
dotted
lines
or
whatnot,
but
right
now,
dot.
Seven
is
like
my
bucket
for
everything:
that's
on
the
horizon,
the
so
just
to
go
over
them
really
quickly.
C
There
is
like
load
testing,
that's
kind
of
a
key.
There
is
some
test
dashboards
and
like
more
mature,
like
testability
monitoring,
metrics
collection
and
other
takes,
and
a
bunch
of
these
things
are
already
there.
I
just
think
they
haven't
kind
of
like
you
know,
we
haven't
had
like
a
sorrow.
How
do
these
fit
in
into
the
big
picture
like
there
is
I,
remember,
Caleb
and
I
spoke
about
like
the
event.
C
B
is
mechanism
for
triggering
all
they
sing
stuff,
that's
happening
in
open
match
stuff
like
that,
could
all
be
on
the
track,
seven
roadmap,
and
we
can
then
break
it
down
once
we
are
closer
to
that
mean
to
you
know,
final
milestones
between
dioxide
and
water.
All
the
other
features,
like
the
other
feature
that
I
listed
out,
are
so
these
are
basically
stuff.
That's
gonna
keep
happening
by
the
side.
C
I,
don't
think
they
I
want
to
tie
them
to
a
specific
release,
but
like
it's
documentation,
building
the
harnesses
and
whatnot
I'll
have
issues
for
these,
and
we
can
like
just
pick
them
up
on
on
any
release
like
we
need
to
change
in
addition
for
every
release,
but
hopefully
these
a
nice
little
amount
is
that
one
dot,
oh
I'm,
hoping
we
have
like
a
really
good
user
guide.
Some
tutorials,
like
the
things
listed
here,
should
kind
of
be
really
solid
by
one
order.
C
They
can
keep
happening
through
the
intermediate
releases,
but
I
would
not
go.
They
need
to
really
be
solid.
So
that's
why
it's
kind
of
listed
in
the
market.
A
last
word
about
1.1.
It's
it's
interesting
because
it's
not
really
like.
We
are
thinking
about
1.1,
just
yet
other
right
now.
In
my
mind,
1.1
is
a
bucket
of
things
that
are
not
1.2,
essentially
or
not
don't
fit
in
the
definition
of
open
match.
As
a
frameworks
wonder
now.
That
said,
the
reason
I
mentioned.
C
That
is
because
some
of
the
things
here
are
may
be
very
interesting
to
folks
and
I.
Don't
necessarily
think
they
should
be
done
after
open
match
it's
one
dot.
Oh,
they
can
totally
be
picked
up
family
after
dot
six,
hopefully
because
what
six
will
kind
of
said,
the
new
API
is
and
stuff
like
that.
But
after
that
let's
say
director
now
you
could
pick
up
the
director.
While
you
got
seven.
H
C
Don't
think
that
falls
under
open
matches
like
open
match,
one
righto
would
not
block
because
and
an
Adonis
director
is,
is
missing
or
so
so
it
kind
of
falls
in
my
mind
beyond
their
enough
open
match
as
of
framework,
so
there
would
actually
be
a
lot
of
other
services
here.
Books
may
be
interested
in
like
a
group
service
potentially
and
then
stuff
like
that.
I
feel
free
to
add
more
ideas
here
and
I
I
mean
feel
free
to
even
like
bring
them
up
start
working
on
them.
C
C
B
B
Sorry,
Lindsey,
okay,
yeah,
so
I'm
Anthony,
Fedderson
I'm,
a
software
engineering
manager
here
at
Kirkland,
I
helped
start
the
cloud
gaming
team
in
December.
The
team
has
grown
pretty
quickly
and
our
time
was
kind
of
split
between
working
on
the
iguana's,
open
source
project
and
open
match
measure
concede
everybody
here
in
the
room.
Are
the
developers
for
hope
met
from
the
Google
side?
So
everybody
here
is
full-time
and
be
working
on
all
the
things
that
are
mentioned
just
really
quick
Lindsey.
Are
you
a
user
of
the
match
or
yeah.
H
Gervais
birds
I've
been
working
up
in
match
since
about
January
of
this
year,
and
so
serving
I've
been
working
to
you
know
beef,
it
up
turtle
or
it
is
now
a
good
future.
You
don't
look
back,
I
mean
fine.
I've
been.
C
G
A
A
Excuse
me,
we
have.
This
project
was
founded
by
Google
and
unity,
so
as
far
as
the
decisions
that
get
made
about,
for
instance,
what
goes
in
a
roadmap
and
what
constitutes
our
release
things
like
that.
Those
are
done
by
a
technical
steering
committee
and
which
right
now
is
consisting
of
folks
from
Google
and
folks
from
unity,
as
others
get
more
involved.
With
actual
you
know,
contributing
to
the
project
whether
that's
code,
documentation,
like
you,
know
any
of
the
varied
ways
you
can
contribute,
we'll
look
at
adding
others
to
the
steering
committee.
A
So,
if
you're
not
on
the
TSC
but
you're
interested
in
getting
there
we'll
have
more
details
on
what
that
looks
like,
since
we
are
still
a
new
project
haven't
quite
figured
out
like
what
the
criteria
is
yet
ideas
are,
of
course,
welcome,
and
even
if
you're,
not
on
the
committee,
of
course,
when
we
have
like
the
API
proposal
is
a
great
example.
We
want
to
hear
your
feedback,
so
we're
setting
up
meetings
now
they
will
probably
be
public,
will
talk
about
it
and
depends
on
what
all
you
know
get
set
in
it.
A
But
the
idea
is
that
you'll
be
able
to
join
the
same
thing
if
we
get
to
the
point
later
on
down
the
road
where
you
want
to
create
a
working
group
again,
we're
still
very
early,
probably
not
meeting
that
just
yet,
but
at
a
certain
point
like,
for
instance,
yeah
we
mentioned
looking
at,
maybe
other
frameworks
like
then
we
would
potentially
create
a
working
group
for
that.
So
again,
if
there's
ever
something
that
you
think
you
would
like
to
split
off
and
kind
of
focus
more
on.
A
If
you're,
just
a
you
know,
a
government
nerd
like
I
am
that's
a
good
opportunity
to
put
some
of
the
skills
to
use
right
now.
One
thing
that
I
just
want
to
highlight,
especially
as
we're
talking
about
you,
know,
proposals
and
things
like
that.
If
we
can
keep
as
much
of
the
conversations
in
github
as
possible,
that's
going
to
make
life
so
much
easier
for
all
of
us.
It's
great
you
know.
Slack
is
a
some
people
love
it.
A
That's
a
very
quick
high-level
overview.
Does
anybody
have
any
big
questions?
The
other
big
thing
is
that
we
are
in
the
process
of
we're
going
to
move
open
match
to
its
own
at
github.
Well,
not
its
own,
but
we're
going
to
create
a
new
github
organization
for
kind
of
all
of
these
open
source
gaming
projects,
so
open
match
will
have
its
own
repo
within
that,
and
the
reason
for
that
is.
It
gives
us
a
lot
more
flexibility.
We
can
do
some
of
the
cool
stuff.
A
Like
you
know,
some
of
the
great
thoughts
and
things
like
kubernetes
has
built
that
streamlines
their
workflow.
It
also
is
going
to
allow
us
to
create
you
know
a
separate
repo
just
for
government
just
for
community
just
for
dock,
just
for
the
website.
Things
like
that,
so
it'll
make
it
a
lot
easier
for
those
of
you
who
want
to
get
involved
and
places
other
than
poor
code.
It'll
be
a
lot
easier
for
you
to
jump
in
and
get
involved
there,
so
not
on
something.
A
B
B
A
I
think
the
only
other
thing
we
really
had
was
Lindsay.
You
had
made
a
question
in
the
doc
about
documentation
which,
yes,
absolutely
agree:
I
love
your
idea
about
a
branch
and
I
wanted
to
put
that
to
the
core
team
and
see
what
they
thought.
I,
don't
know.
If
you
guys
saw
the
question
it
since
master
is
fluid
right
now.
Could
there
be
a
branch
that
edirect
new
users
to
so
we
can
continue
to
investigate
open
match
without
experiencing
delay.
It's
due
to
the
volatility
all
right.
D
So
we
are
going
forward
for
every
point
release
there
will
be
a
new
branch
and
then
we'll
have
the
release
hands
down
there
and
then
the
official
release
for
the
point
release
and
then
we'll
have
hot
fixes
going
that
wrench
as
well.
So
the
latest
point
release
should
have
this
on
branch
with
all
minima
should
be
more
stable
and
then
master
is
going
to
be
the
working
branch
perfect.
A
Yeah,
that's
awesome.
That's
really
helpful,
yeah
and
Lindsay
if
there,
especially
since
you
are
someone
who's
trying
to
use
it.
If
you
go
through
the
process,
if
there's
something
that
you
come
across
and
you're
like
wow,
this
was
really
painful.
Let
us
know
we
can
add
that
to
that
documentation
wish
wish
list,
and
that
gives
us
a
great
indicator
of
what
users
are
meeting
so
Schamberg.
C
D
A
A
F
F
H
C
B
Lindsay
I
was
gonna,
say
you
know
one
dot,
o
or
general
availability
or
alpha
beta.
They
all
kind
of
have
different
meanings
to
different
people.
So
I
think
you
know
as
we
move
along
if
you're
not
seeing
stuff
go
in
that
you
think
is
important
for
you
to
launch
your
game
like
just
please
let
us
know
so
and
just
let
us
know
what
your
requirements
are
and
you
can
see
if
we
can
accelerate
those
things.
Okay,.
A
Nobody
said
anything
else:
we
can
wrap
this
one
up
lettuce
if
these
will
be
monthly,
so
you
should
have
it
all
on
your
calendar
for
the
last.
That
would
Google.
Does
it
weird
it's
the
fourth
Wednesday
of
every
month
you
can't
just
say
the
last
Wednesday,
so
fourth
Wednesday
of
every
month
same
time
we
can
always
adjust
the
time
Lyndsey
never
chatting
about.
A
You
know
time
zones
people
are
in,
but
it
seems
like
for
this
group
at
least
this
is
a
good
one,
but
we
can
always
adjust
as
we
go
forward
for
the
fun
of
time
zones.
If
you
have
any
questions
or
anything
that
you'd
like
to
share
in
a
future
meeting,
always
add
it
to
the
dock.
You're
always
welcome
to
reach
out
to
me,
of
course,
with
any
help
or
anything.
But
this
is
your
meeting.
So
anything
you
want
to
show
chair
talk
about,
feel
free.
The
floor
will
be
yours.