►
From YouTube: GMT 2018-01-29 Community WG
Description
Agenda and Notes:
https://docs.google.com/a/mesosphere.io/document/d/1vgi434dYkkZHs49EK4F4eMmM-3JG4f3qg-N5En-4ubg/edit?usp=drive_web
A
B
So
the
first
thing
I
wanted
to
talk
about
was
something
that
came
up
and
some
conversations
around
our
office
the
other
day.
That
seemed
like
a
really
good
idea
to
me
as
a
way
to
improve
community
development,
get
more
involvement
and
maysa
open-source
community,
and
that's
just
to
renew
our
efforts
at
Mesa
sphere
to
push
as
many
conversations
as
possible
into
open
source,
maysa
forums
and
really
try
to
make
especially
the
working
groups.
B
B
I
think
if
we're
going
to
be
doing
any
API
work
in
the
future,
having
an
API
working
degree
would
be
great
and
I
think
what
the
API
working
group.
It
might
also
be
a
situation
where
we
could
have
a
working
group
established
that
doesn't
necessarily
have
regular
meetings
but
could
meet
on
an
ad-hoc
basis
as
it's
appropriate
to
handle
new
issues
or
features
that
come
up
like
one.
B
One
thing
that
came
up
recently
was
I,
think
Yan,
Yan
Schlicht
was
adding
a
new,
yet
operations,
API,
call
and
I
think
just
the
fact
that
a
new
API
call
was
being
added.
It
kind
of
occurred
to
us
like
it
would
be
nice
if
we
had
some
single
entry
point
for
people
who
are
adding
or
changing
any
API
is
where
they
could.
Let
the
maintainer
--zz
stakeholders
know.
B
We
could
have
some
kind
of
review
process
that
makes
sure
that
all
of
these
changes
to
the
API
are
happening
in
a
consistent
way
away.
So,
like
a
an
an
API
working
group
might
be
the
kind
of
thing
where
the
organizer
of
that
working
group
could
be
a
maintainer
who's
notified
of
all
such
API
changes.
And
then,
when
we
have
a
couple
items
to
discuss,
they
could
let
people
know
and
we
could
hold
a
meeting
to
discuss
those.
B
So
that's
just
one
specific
example,
but
I
think
the
overall
message
is
that
we
here
at
Mesa,
C,
are
going
to
and
I
think
increase.
Our
efforts
to
push
development
into
working
through
James
I
would
be
interested
to
hear
from
you
like
how
much
you
guys
at
Apple,
make
use
of
working
groups
and
other
open-source
forums
versus
internal
discussions.
Do
you
think
that
you
guys
have
any
room
that
you
can
improve
there,
or
are
you
doing
a
pretty
good
job
of
that
already
I.
E
E
E
B
B
C
E
Would
be
I
really
I,
really
really
hopeful
Canada
resource,
because
number
of
people
who
are
gonna
consume
the
API
and
the
number
of
other
projects
that
can
give
you
input
to
the
API
is
much
larger
than
kind
of
almost
all
the
other
working
groups,
so
I
think
I.
Think
the
API
working
bird
would
be
very,
very
helpful.
I
actually
think
there
might
be
a
couple
of
people
at
Apple
who
would
be
willing
to
participate
in
that
oh
I.
Think
Darwin.
C
A
C
Guess
we
need
to
ask
on
the
on
the
mailing
list
or
slack
channel,
to
see
who
would
be
willing
to
do
that.
Sevilla,
HTTP,
API,
Channel,
I'm,
guessing
most
of
the
interested
stakeholders
are
already
on
that
channel.
So
then
you
can
ask
on
a
channel
to
see
or
take
up
that
if
someone
wants
to
do
the
day-to-day
of
it,
I'd
love
to
participate,
yeah
I'm,
just
trying
to
have
time
to
set
agenda
and
trying
to
choral
folks
into
talking
about
stuff
and
all
that
good
stuff
worried
about
this
particular
working
group.
C
So
I'm
going
to
the
next
action
item
should
be.
We
should
ask
this
question
on
the
slack
channel:
should
it
be
a
base
like
channel
and
see
if
there's
anyone
who
is
willing
to
go
on
it
or
the
day-to-day
of
it
and
but
yeah
I
think
I
agree
with
James
and
Greg.
That
is
a
PR.
You
know
some
things
that
we
going
to
be
really
useful
to
have
a
wider
participation,
because
it's
gonna
impact
schedulers
operators,
users,
everyone!
A
Cool
Andy
and
Gilbert,
if
you
just
joined,
we're
talking
about
potentially
doing
more
work
in
public,
even
public
working
groups
and
spinning
up,
maybe
API
working
group
as
the
first
one
to
meet
ad
hoc
when
people
want
to
make
changes
and
we're
trying
to
figure
out
who
might
want
to
be
the
working
group
leader.
So
if
you
guys
are
interested,
let
us
know.
F
G
G
Working
Committee,
because
if
you
identify
all
facing
surface
immediately
missiles,
which
I
think
many
people
cannot
ingest,
not
that,
and
especially
for
with
this
so
I
know,
this
may
have
been
a
quick-fire
a
little
empty.
So
those
are
API
change,
changes
reaching
who,
like
sleep,
light,
application,
big
guy
who
or
introducing
some
a
new
big
guys,
I,
would
say
like
if
we
have
some
API
working
to
information
posted
online.
G
Then,
what's
our
plan
on
the
v2
API
and
some
companies
like
uber
they
want
to,
like,
though,
or
if
their
job
is
he
so
they
would
like
their
other
API
like
the
weather
scare,
there
are
some
others
they
would
like
to
investigate
if
it
is
possible
to
rely
on
GRDC
codes
to
talk
to
his
master.
So
those
are
some
potential
discussion
on,
but
I.
C
I
was
just
chatting
before
you
joined
the
burn,
so
we
yeah
I'll,
probably
send
an
email,
first
mailing
lists
and
maybe
miniature
slack
channel,
to
float
the
idea
and
see
20
volunteers
and
then
we'll
see,
maybe
I'll
start
off
with
leading
it.
The
first
few
meetings
before
we
find
someone
else
to
lead
it
or
maybe
I-
can
collate
it
with
someone
else
to
share
the
Time
Lord
but
yard
I'd
love
to
spin
it
up.
C
B
C
H
B
I
think
that
would
be.
That
would
be
really
cool
if
there
were
like
I
guess.
First
of
all,
I
user
are
too
interested
in
owning
it
like
someone
who's
actively
operating
a
significant
deployment
who
wants
to
own
it
and
then
even
just
a
few
interested
attendees.
I
mean
that
could
be
a
good
place
for
operators
to
share
concerns
and
common
experiences
that
might
actually
lead
to
good
communications
to
other
working
groups
in
terms
of
needed
features
or
bug
reports,
but
it
it
seems
to
me,
like
it's
dependent
on
sufficient
interest
from
from
the
relevant
people.
E
D
A
A
Sounds
good
so
maybe
I
guess
it
might
be
a
good
place
to
start
to
either
email
directly
people
who
we
think
might
be
interested
in,
leading
it
or
just
put
out
a
call
on
the
mailing
list
and
say:
hey.
Would
you
I'd
be
interested
in
participating
in
this
city
if
it
existed
just
to
see
if
we
would
get
enough
participation
to
make
it
we're
spinning
up.
B
B
B
Also
wonder
about
a
storage
working
group
I
feel
like
some
of
the
features
that
were
implemented
for
storage,
went
were
discussed
in
a
containerization
working
group,
but
not
all
so
it
might
be.
G
was
actually
someone
who
brought
this
issue
up
in
a
meeting
the
other
day,
so
I'll
reach
out
to
G
this
week
and
ask
him
if
he
thinks
that
would
be
valuable
or
appropriate.
I
suspect
there's
enough
development
still
going
on
there.
That
would
be
a
useful
thing
to
have
and
to
bring
out
into.
H
B
A
B
A
C
Yeah
I,
don't
think
people
using
maintenance
either
they're,
probably
order
to
companies
using
hit
suicide,
no
once
it
becomes
more
popular
and
to
what
being
then
I
think
probably
worthwhile
thinking
about
it,
then
that's,
probably
all
something
that
could
be
it
gets
talked
about
in
operate.
This
working
group
too,
because
it's
kind
of
related
to
operations
itself
mostly
will
be
used
by
operators
when
doing
maintenance.
So
that's
something
that
part
of
operated
working
group
our
operations,
whatever
you
call
it.
E
B
Yeah
I
think
that's
a
great
idea
for
the
monthly
email.
That's
actually
the
next
agenda
item
that
I've
put
down
was
to
discuss
that
email
and
I
would
certainly
be
interested
in
including
working
group
updates
and
that
I
think
then
haven't
you've
been
sending
out.
Some
updates
regarding
the
performance
working
group
is
that
right,
I.
H
And
we
could
send
another
one,
but
people
have
just
been
too
busy
to
do
that,
but
yeah
I
mean
I
called
it
a
performance
report
but
I
think
I
think
actually
in
retrospect
it
maybe
would
have
been
better
too
title
bat,
as
the
thing
that
we
did,
rather
than
as
a
report
like
title
it
as
faster
master
failover
is
in
1/5
or
something
like
that.
Instead
of
you
know,
December
performance
report
just
get
more
interest.
Yeah
yeah.
A
H
B
G
A
D
B
So
yeah
I
guess
what
I
wanted
to
ask
my
plan
for
the
January
email
was
to
link
to
the
1
5
release
blog
post,
but
since
that
has
not
come
out
yet
I
was
trying
to
figure
out
what
I
should
do.
I
would
love
to
squeeze
something
in
for
this
month,
just
to
keep
it
going,
but
actually
contacting
people
about
working
groups
and
including
some
brief
summaries.
B
You
know
that
we
had
an
RC
in
a
boat
and
that
an
email
is
forthcoming
and
then
I
could
just
have
links
to
the
working
group
agendas.
With
a
few
notes
on
progress
and
the
working
groups.
Does
that
sound
like
a
reasonable
email?
Do
you
guys
have
any
other
thoughts
on
what
I
might
include
in
the
last-minute
email
here
at
the
end
of
the
month?
I.