►
From YouTube: GMT 2017-11-06 Community WG
Description
Agenda and Notes
https://docs.google.com/a/mesosphere.io/document/d/1vgi434dYkkZHs49EK4F4eMmM-3JG4f3qg-N5En-4ubg/edit?usp=drive_web
A
A
A
A
A
C
B
A
A
A
B
C
B
B
B
C
B
C
B
So
I
I've
been
hounding
York
for
like
I'm
trying
to
get
whatever
notes
he
had
from
the
previous,
like
we
sent
out
a
round
of
emails
there
committers
and
got
some
feedback
and
I
think
you
were
kind
of
jock
in
progress,
but
I
haven't
been
able
to
get
a
response
from
them,
so
I
guess
I'm,
just
gonna
start
over,
so
I'm
gonna
get
in
touch
with
Jay
and
we
can
just
send
out
some
more
emails
and
try
to
get
something
written
up
soon.
So
that's
just
continuing
I
apologize
for
the
delay.
B
A
I
would
bring
up
something
I'm,
not
sure
if
it's
totally
related
to
community
but
I
feel
like
developer.
Community
anyway
is
a
relation
here.
I'm
wondering
how
we
could
improve
like
getting
external
contributions
right
now
me,
especially
as
an
external
contribute
into
the
codebase
right
like
a
lot
of
open
source
projects
but
live
or
die.
A
Based
on
how
easy
it
is
to
get
an
extended
developer
community,
where
it's
not
just
the
core
people,
I
like
say,
Mesa,
Sphere
working
on
it,
but
other
people
committing
well
contributing
and
getting
key
part
getting
their
contributions
actually
looked
at
in
in
I.
Just
know.
From
my
side,
like
I
know,
most
of
my
sister
people
are
busy,
which
is
understandable,
right,
like
of
course
they
have
their
own
stuff,
but
it
makes
it
difficult
to
get
Shepard's
to
get
patches
in
I
mean
at
least
from
me.
It
can
sometimes
take
weeks
or
more
I.
A
Think
one
of
my
co-workers
that
looking
at,
like
four
weeks
of
bugging
people
to
look
at
some
patches
and
I'm
certain-
it's
not
just.
Do
you
look
at
these
two
external
contributors
over
here
at
Microsoft,
but
that
I
mean
you
guys
are
all
crunched
for
time
and
I'm
just
wondering
if
we
could
like
figure
out
how
to
make
it
easier
for
external
contributors
to
get
in
like
yeah.
C
A
C
A
minute
we
were
talking
about
that
in
an
internal
meeting
with
a
little
bit
of
the
Mesa
steam
in
it.
What
we
talked
about
was
basically
different
ways
to
more
or
less
enforce
people
to
actually
Shepherd
the
patches
that
they
are
supposed
to
be
shepherding.
So
I'm
yeah
I
think
that
that
might
be
a
good
idea.
C
It
takes
I.
Think
I
asked
at
one
point
if
we
could
actually
allocate
some
time
for
that,
and
the
engineering
leadership
said
yes,
so
I'm
not
sure
if
that
filtered
down
over
anywhere,
but
we
might
I
saw
there,
was
like
a
may.
Sews
like
working
time
on
the
calendar
on
Wednesdays
I,
think
Greg.
Do
people
actually
like
sit
in
a
room
together
and
hack
on
stuff
during
that
time,
yeah.
B
C
A
A
Yeah
and
I
mean
hey.
I
am
stubborn
and
we'll
go
to
60%
and
find
people
until
he
gets
stuff
committed
for
me
and
I.
Thank
all
of
them
for
that.
But
I
can
imagine
a
lot,
especially
for
people
who
aren't
quite
like
me
will
just
be
like
well,
the
Shepherd
didn't
get
to
it.
So
clearly
they
don't
want
it
and
give
up
and
leave
the
community
and
we've
lost
a
developer,
which
is
not
what
you
wanted.
An
open
source
project
yeah.
B
Yeah
so
I
I
mean
I,
think,
certainly
for
folks
for
the
folks
working
here
at
Mesa
sphere.
It's
you
know
the
constant
struggle
of
trying
to
be
up-to-date
on
your
internal
commitments
and
also
serve
the
community,
so
I
think
I,
guess
what
comes
to
my
mind
is
that
it
would
good
to
have
to
maybe
help
apply
a
little
pressure
to
one
another.
We
could
have
some
kind
of
organized
events
like
Judith
you're
talking
about
using
this
thing.
We
have
a
very
internal
calendar
as
a
forcing
function
to
get
some
reviews
done.
B
I
think
it
might
like,
since
that's
a
running
thing
that
isn't
regularly
used,
it
might
make
sense
to
establish
a
new
event,
but
I
do
like
the
idea
of
having
some
kind
of
regular
organized
event
where
committers
and
contributors
could
gather
and
I,
don't
know,
I
guess
so.
I
could
imagine
having
like
a
work
group
style
thing
where
people
get
together
for
a
couple
hours
and
actually
work
on
reviews.
I
could
also
imagine
just
like
a
committers
meeting
where
committers
are
meeting
and
trying
to
go
through
the
tickets
that
they're
responsible
for
reviewing.
A
Both
of
your
ideas,
I
think,
have
merits,
like
both
forms
of
meetings
and
I,
think
they
both
accomplish
one
of
the
main
things
that,
like
mesosphere,
that
being
the
main
maize
those
developers
there's
other
committers
to
maysa,
but
obviously
the
majority
of
them
are
amazed.
The
sphere
getting
that
sort
of
external
commitment
of
yeah
we'll
work
with
the
community
in
the
form
of
this
weekly
or
bi-weekly
meeting
something
that's
accomplished
with
the
media
and
I.
A
In
the
other
hand,
I
am
also
like
the
fact
I
also
like
the
idea
of
a
meeting
where
the
non
committers
are
in
the
meeting
too
and
can
be
like
hey
I
have
these
patches
and
this
Shepherd
was
gonna
work
on
it,
but
it's
kind
of
fallen
can
I
get
one
of
you
guys
who's.
Currently
in
this
meeting
and
a
to
do
this,
so
you
feel
like
you
may
might
need
a
little
it
bowls.
I
would.
C
Definitely
advocate
for
them
we're
open
version
of
it
at
first,
at
least
I
mean
I,
think
that
it's
it's
nice
to
be
able
to
say
like
hey,
you
can
come
in
and
anyone
can
join
this
and
talk
about
the
open
stuff
that
needs
reviewing
I
guess.
My
main
question
is
like:
how
long
does
it
actually
take
to
do
one
iteration
of
or
like
one
round
of
review
its.
B
C
So
I
guess
for
me:
I
would
like
to
see
maybe
every
two
weeks
like
a
two-hour
meeting
where
everybody
just
sits
down
and
works
on
it.
We
could
put
a
video
call
on
it
and
we
could
just
say
here's
our
time
to
work
on.
Turning
through
your
reviews,
if
you
have
so
many
reviews
that
you
can't
make
progress
on
them
with
just
this
meeting,
you
might
consider
handing
them
to
somebody
else
or
even
cutting.
C
B
A
B
How
could
we
get
that
set
up
so
I
think
for
it
to
be
useful?
We
need
to
get
some
buy-in
from
committers
and
get
get
people
to
actually
show
up,
so
we
could
get
some
work
done.
I
could
all
own
talking
to
the
knowed
about
this,
and
maybe
I
can
sync
with
him
could
send
out
an
email
and
try
to
get
people
on
board
if
we
could
get
kind
of
a
tentative
commitment
from
people
to
show
up
every
other
week,
I
think
we
could
actually
get
a
lot
of
work
done
in
that
period
of
time.
B
Cool
yeah,
thanks
for
thanks
for
the
initiative
on
that
and
yeah
I
know.
That's
that's
just
something
that
we
and
a
lot
of
other
communities
struggle
with
constantly
and
I
think
we
just
have
to
keep
putting
in
little
effort
continually
and
come
up
with
some
good
ways
to
like
force
ourselves
to
do
what
we
need
to
do.
Yeah.
A
I
know
it's:
it
is
an
open
source
problem.
Riley
I've
worked
in
open
source
for
I,
don't
know
how
many
years
now,
as
since
at
least
early
college,
and
it's
just
that's-
either
either
it's
a
small
project
and
the
author's
themselves
just
kind
of
give
up
on
the
project
and
get
busy
and
low
mold
project
dies
or
it's
big
project,
but
the
committers
on
the
project
are
busy
with
their
own
internal
things.
So
again,
still,
yes,
it's
open
source,
but
the
community
is
kind
of
dicing.
A
It
is
a
tough
problem
to
solve,
because
it
takes
the
time
commitment
and
that's
not
always
something,
especially
for
stuff
that
seems
intangible
like.
Why
should
we
be
committing
time
for
these
other
people
to
get
work
done?
Well,
there
are
I
think
there
are
tangible
benefits
to
it,
but
it's
not
always
easily
sold
to
management,
which
can
be
a
problem
for
like
company
driven
sort
of
community
open-source
communities,
yeah.
C
A
A
When
we
were
looking
to
open
source
it,
we
had
a
couple
PM's
who
really
did
understand
the
value
of
creating
this
open
source,
community
and
process
and
like
from
the
get-go,
they
had
a
weekly
meeting
to
review
all
the
pull
requests
coming
in
from
the
external
community
that
the
engineers
it
has
worked
really
well,
actually
so,
plus
one
for
huge
amounts
of
process
coming
out
of
a
large
corporation.
Rightly
it.