►
From YouTube: GMT 2017-10-23 Community WG
Description
Agenda and Notes:
https://docs.google.com/document/d/1vgi434dYkkZHs49EK4F4eMmM-3JG4f3qg-N5En-4ubg/edit?usp=sharing
B
A
B
We
go
share
screen
here
we
go
so
we
now
have
that
covered
my
tab
bar
okay.
Here
we
go.
We
have
new,
getting
started
pages.
If
everybody
can
see
this
in
the
video
when
you
watch
it,
instead
of
this
being
a
bunch
of
building
documentation
on
all
your
platforms,
it's
just
like
here's,
the
home
page,
you're
new
to
meso
spec.
How
do
I
get
started?
You
click
it.
There's
nice
concise
amount
of
information.
It
tells
you
to
go.
Look
at
a
talk
on
YouTube
and
read.
B
The
white
paper
points
you
to
the
building
documentation,
which
is
what
the
old
getting
started
page
was,
and
then,
on
top
of
that,
with
Greg's
work.
We
have
our
beginner
contribution,
guide,
an
advanced
contribution,
guide,
being
totally
updated
and
like
easy
to
use
and
follow
to
figure
out
exactly
how
you
want
to
update
to
meso
stays,
we'll
teach
you
how
and
if
you
need
to
find
them
again,
click
getting
started.
There's
a
couple
links
no
muss,
no
fuss.
It's
great.
We
love
it.
Mm-Hmm.
B
There
was
other
stuff
from
the
docket
on
to
just
did
not
leave
anybody
out.
The
documentation
page
is
also
like
really
easy
to
follow.
Now,
instead
of
seeing
one
straight
line
of
Doc's,
it's
and
sections
this
was
been
Mahler's
work,
it's
yeah,
it's
also
very
great
and
awesome,
and
on
top
of
that
there
are
anchor
links
that
use
remote
fonts
that
I
have
blocked,
but
if
I
allow
them
any
fresh,
you
can
now
link
to
sections
in
the
documentation
as
well.
That
was
James
speeches
work
also
from
the
doc
athon.
B
A
A
C
B
It
that'd
be
a
good
cadence,
actually
to
continuously
get
documentation,
updated
right,
like
even
before
the
Dhaka
thon
happened.
Knowing
that
it
was
going
to
happen,
drove
me
to
write
a
bunch
of
Doctson
like
the
see
make
build
system
and
examples.
We
got
the
Isolators
stuff
documented,
better
yeah
I
think
this
should
just
happen
so
that
people
like
oh
yeah,
the
doc
thumbs
coming
up.
Let's
write
Doc's
happen
periodically,
and
you
know
some
of
us
don't
always
write
our
Doc's.
C
We
can
follow
up
on
our
previous
action
items.
Looking
below
I
had
want
to
sync
with
your
about
the
newsletter.
I
did
hound
him
relentlessly
I
just
heard
back
from
this
morning,
so
he
and
I
are
gonna
sink
tomorrow
and
I.
Think
I'll,
probably
just
take
over
publishing
the
first
newsletter
that
we
send
out
so
I'm,
going
to
sync
with
him
and
Jay
and
I'll
make
sure
that
happens
within
the
next
couple
weeks.
I.
C
A
A
C
Things
and
then
M
had
an
action
item
to
add
Dhaka
thon
event
to
Mises
calendar.
That's
over
I
think
we
can
consider
that
done.
Nice
laughs
nodes
start
an
email
thread
about
release,
got
on
some
blockers.
I,
don't
think
that
got
started.
Do
you
guys
remember
seeing
that
no
I
don't
think
I
saw
that
on
the
list
and
I
think
I've
been
paying
attention.
A
C
A
C
B
B
A
B
C
B
And
also
like,
what's
being
worked
on,
especially
with
regards
like
mesosphere
priorities
of
like
features
that
are
being
driven
by
different
parts
of
the
community
would
be
nice
like
I,
obviously
know
I
work
on
the
window
side
of
stuff
of
most
of
the
time
in
the
seem
excited,
stuff
and
I.
Think
I
know
what
some
other
developers
are
working
on
sometimes,
but
it
that'd
be
it
wouldn't
or
requesting
information
from
people
if
they
could
like,
give
us
an
overview
of
what
they're
trying
to
accomplish
with
their
changes,
because
there's
one
thing
that
be
like.
B
C
C
A
A
B
Is
that
Python
2
on
Windows
uses
the
ANSI
versions
of
the
Windows
API,
not
the
Unicode
versions,
which
is
work
I
had
to
do
for
Mase.
Let's
do
like
the
long
path
before
like
we
had
the
same
problem.
Python
3
did
the
work
that
brought
them
to
Unicode
versions
of
the
API
so
that
when
you
call
like
the
Windows
create
process
API,
you
can
have
non
ASCII
characters
in
it,
but
but
it
means
porting
the
scripts
up
to
Python
3,
and
it's
like,
if
he's
so
nice
to
have
but
who's
gonna
work
on
it.