►
From YouTube: GMT 2018-04-23 Community WG
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
A
A
A
A
So
for
them
it
would
probably
make
sense
to
host
it
down
there,
which
I
am
fine
with
I
would
make
a
trip
down
there
for
it,
and
you
know
folks
who
aren't
able
to
make
the
trip
down,
could
just
point
it
join
via
zoom
or
hang
out
or
whatever,
but
yeah.
It
sounds
like
they're
definitely
open
to
it,
and
maybe
we
could
also
couple
a
Twitter
I
think.
Maybe
we're
still
waiting
to
hear
back
from.
A
B
A
A
C
It
looks
like
existing
infrastructure,
an
existing
script
by,
like
the
Apache
infrastructure
guides,
for
integrating
some
of
this
stuff.
This
is
primarily
this
script.
Let's
do
you
like
reference,
an
issue
in
a
commit
and
when
the
commit
goes
into
your
ASF,
git
repo,
it
closes
The
Associated
issue.
So
there
is
some
existing
integration
here
and
a
script
we
could
borrow
or
improve
upon,
but
yeah
I
just
found
something
neat.
Oh.
A
A
A
B
No
I
have
not
done
that
yet,
but
I
did
talk
a
little
bit
to
the
marketing
teams
about
the
budget
and
it
sounds
like
they're
pretty
strapped
so
I
would
be.
B
A
Sounds
good
next
one
was
for
me
to
email,
Yelp
and
Twitter
about
blog
posts,
so
I
didn't
email
Twitter,
because
I
think
we
were
or
we
were
waiting
to
hear
back
from
folks
over
there,
like
vinod
kind
of
suggested.
We
could
just
wait
until
we
heard
back
about
the
dev
sink,
but
since
we
have
heard
back
from
them
about
that,
maybe
all
reached
out
about
a
blog
post
I
can
do
that
this
week.
A
I
did
contact
soon
Ellie
Yelp,
though
they're
actually
planning
on
doing
a
blog
post
in
the
near
future,
because
they're
doing
some
benchmarking
right
now
so
they're
planning
to
do
a
blog
post.
Whenever
that
benchmarking
work
is
done,
they
have
some
more
data
to
collect
and
he
said
they'll
reach
out
to
us
and
collaborate
on
the
writing
of
that
blog
post.
So
both
Yelp
and
uber
are
planning
on
doing
a
blog
post
in
the
near
future.
A
A
A
B
C
A
B
So
there
are
two:
there
are
two
users
that
I
met.
One
is
indeed
calm
and
they
were
interested
in
writing
a
blog
and
it's
in
progress
and
Robert
from
Milton
hardcourt
see
it's
possible
that
I
didn't
you
know
who
about,
but
he's
been
submitting
a
bunch
of
talks
to
places
about
hates
me
so
seems
because
so
I
might
just
well.
You
know
you
about
it.
Yeah.
A
B
We
will
be
in
our
new
space
for
the
doctor
pond,
but
where
it's
okay
for
us
to
have
it
there.
So
that's
good
and
I
started
a
topic
list
that
I
kind
of
just
naively
put
together
from
topics
that
it
didn't
look
like
anyone
had
ever
worked
on
on
the
other
that
were
proposed
for
other
coupons,
so
I
would
love
some
help,
filling
that
out
or
filling
out
details
with
it
or
correcting
it.
B
A
D
He
I
think
he's
been
busy.
He
hasn't
had
time
to
get
back
to
us,
I'm
hoping
someone
could
could
kind
of
pick
it
up
at
a
docket
on
or
something
in
I'll
finish
it,
but
we
had
some
feedback.
We
talked
to
him
made
like
hang
out
with
him
or
I.
Don't
remember
if
he
was
able
to
join
that
angle,
but
we
shared
some
feedback
with
him
and
he
said
he
was
gonna
update
it,
but
I
think
he's
just
been
busy
with
others.
Job.
D
Yeah
I
think
he's
you'd
have
to
return
remotely,
but
yeah
he's
on
the
East
Coast
I.
Think:
okay,
cool.
A
A
A
A
B
There
were
some
notes
in
the
docket.
Let's
see
here,
update
HTTP
API
Docs.
It
looks
like
Colton
signed
up
for
converting
existing
operator,
HTTP
API
circles
to
curl
commands,
but
then
always
add
offer
operations
to
the
API
Docs
alter
example
formatting.
To
avoid
displaying
examples,
it's
being
introduction
section
he's
scheduler
executor,
API
adoption
introduces
the
basic
scheduling,
executor
workflow,
so
that
was
is.
A
A
A
Think
executor
types
that
would
be
a
good
doc.
It
would
be
nice
like
something
like
the
left-hand
nav
menu.
I
I
feel
like
that's
something
that
might
just
take
a
little
longer
than
the
docket
onslaught,
but
if
somebody
did
a
little
research
ahead
of
time,
they
might
be
able
to
bang
it
out
during
that
period
of
time,
I
wonder
if
it's
worth
trying
to
do
a
little
groundwork
ahead
of
the
actual
docket
on.
A
D
D
So
if
we
put
things
in
here
that
require
homework,
and
people
ideally
realize
that
that
is
the
case,
and
then
they
do
a
little
bit
of
stuff
up
front
and
show
up
and
can
finish
it.
That's
still
a
great
how
come
right,
I
guess
you're
just
wondering
like.
Hopefully,
people
will
realize
that
they
might
want
to
spend
some
time
before
the
the
darker
phone
yeah.
A
B
A
D
A
B
A
B
I
talked
to
poppy
about
it
because
he
pinged
me
and
he
was
like.
Oh
we're.
Gonna
start
a
DCOs
documentation
working
group.
Is
this
the
same
thing
as
scheduled?
Something
and
I
was
like.
No,
it's
not
the
same
thing,
but
if
you
want
to
join
and
help
out
with
the
miso
stocks,
that
would
be
awesome
and
he
was
like
yeah
I'd
love
to
do
that.
So
he
seems
excited
he's.
B
A
B
A
A
A
So
he
suggested
that
I
reach
out
to
them
and
asked
if
they
would
be
willing
to
include
our
monthly
maysa
updates
here,
and
we
could
just
provide
them
with
a
link
to
our
mailing
list
archive
for
now
as
an
easy
way
to
do
it
and
I
thought
that
seemed
like
a
good
idea.
So
I
was
planning
to
do
that.
I'll,
add
an
action
item
for
myself
to
do
that.
D
What
I
know,
at
least,
is
that
at
least
for
some
stuff
on
there.
You
need
to
be
a
paid
subscriber
and
a
lot
of
companies
will
have
at
least
one
account
so
that
people
can
get
access
to
these
publications
or
these
articles,
and
in
my
past
experience,
it
was
always
like
the
colonel
team
that
has
a
couple
of
subscriptions
or
something
or
they
like
they
fix
subscriptions
expensable
just
that
people
can
keep
up-to-date
with.
What's
going
on
in
the
colonel
I'm,
not
too
familiar
with
the
other
side
of
this,
like
the
non
colonel
stuff.
E
D
A
D
A
B
A
A
So
I
think
my
exposure
has
pretty
much
been
to
the
the
larger
users.
You
know
like
the
handful
of
larger
users,
and
things
seem
pretty
good
there
with
active
development
and
people
participating
in
kind
of
public
discussions
and
such
and
then
I'm
not
really
sure
about
the
wider
community
of
like
small
to
medium
size
users.
D
D
Yeah
I,
don't
I,
don't
know
they
just
tend
to
be
a
bit
quiet.
I
guess
maybe
that's
a
good
thing
in
some
ways,
because
I
guess
things
are
mostly
working
and
so
on,
but
I
don't
know
they
just
use
the
software
I
guess
and
are
not
super
active
and
participating.
I
mean
now
that
there's
slack
I
see
a
lot
more
people
in
there.
Mm-Hmm.
D
But
yeah
I
don't
know,
I
would
maybe
agree
with
Craig
that
it
seems
like
there
may
have
been
a
decline.
I
don't
know,
I'm
curious
if
we
looked
at
like
mailing
list
subscriptions
over
time
and
so
on,
like
what
that
would
look
like
I
think
I
looked
at
it
recently
when
I
was
filing
the
board
report
for
bed
because
he
was
away
and
it's
it's
pretty
much
a
flat
line,
but
with
kind
of
like
a
very
slight
decline.
D
B
D
It's
hard
to
say
from
these
numbers
it's
just
kind
of
like
it
definitely
goes
down
and
goes
up
a
little
bit.
It's
a
little
bit
variable.
But
overall
the
trend
was
down
so
I'm
assuming
it's.
It
is
a
little
bit
of
what
you
said,
but
we
don't
actually
get
a
I'm
sure.
I
could
see
that,
but
I
can't
see
it
from
this
particular
graph.
B
D
I
I'd
be
pretty
curious
to
look
at
the
actual
raw
data
if
it's
accessible
and
see
like
you
know
which
companies
people
were
unsubscribing
from
or
subscribing
with,
like
just
so
I
could
see.
If
we're
like
it
looks
like
a
particular
company
stopped
using
it
or
whatever,
but
I,
don't
know
our
user
list
like
I.
Think
we
did
another
thing:
is
people
never
really
asked
to
get
removed
from
our
powered
by
mesas
list?
So
we
don't
really
know
if
all
these
particular
users
listed
here
are
still
using
it.
D
Yeah,
but
you
know
we're
a
big
project
and
a
lot
of
people
use
us.
It's
just
I
think
we're
kind
of
like
you
know.
If
you
look
at
something
like
Linux,
how
often
do
you
participate
in
the
user
list
or
anything
like
that?
It's
basically
never
right
unless
you're
actually
like
a
big
company
finding
bugs
or
whatever
and.
E
Crunched
some
stats
a
few
months
ago,
allowed
Regan
of
commits
by
company
or
how
many
controllers
for
company
there
are,
and
it's
mostly
stable
so
from
like
1.
This
is
1
1,
1,
5
I
see
one.
The
numbers
stayed
stable
and
maybe
even
declined
a
bit
that
I
posted
them
suggest
a
while
ago.
I
can
get
big
lean
if
you
before
interesting
that
it's
most
allowed
developers
not
about
users
but
I.
Just
look
at
I,
just
look
at
the
git
history
and
crunch
some
numbers.
If.
B
C
So
I
don't
have
a
ton
of
customer
interactions,
but
I
could
say:
I've
had
a
few
recent
ones
and
one
was
pretty
positive.
One
was
fairly
negative.
Actually,
so
the
positive
line
is
there's.
A
group
in
Azure
has
a
customer
that
wanted
to
migrate
some
service
that
they
were
using
on
Azure
on
top
of
mesas
to
make
it
fit
into
the
rest
of
their
existing
mesas
framework.
So
that
was
like
awesome.
C
They're
doing
this,
they
agree
to
it
and
I
know
they're
working
on
it,
because
the
dev
ran
into
a
bug
and
pinged
me
and
we
fixed
it
and
move
forward
and
I
haven't
otherwise
heard
from
them,
so
to
kind
of
echo
Ben
Maller
as
long
as
it's
working
they're
just
writing
a
framework.
They
don't
really
talk
to
me
too
much.
That
was
good
and
positive,
but
there
was
also
a
thread
recently.
Actually
in
the
Mesa
slack,
some
company
was
evaluating
using
a
source
on
astron.
This
isn't
Mesa,
sis
fault.
C
This
is
more,
they
were,
they
have
an
existing
mesas
Marathon
infrastructure
and
wanted
to
look
at
using
the
DCOs
marketplace,
offering
on
an
azure
which
is
actually
Mesa
spheres.
Offering
and
they
went,
why
is
this
so
old?
Where
is
the
information
on
this?
Why
is
it
not
been
updated
in
a
year,
and
why
does
it
look
like
Microsoft
says
that
they're
deprecating
it
and
I'm
like
I?
C
C
I
can
tell
you,
that's
not
true,
because
I
have
a
team
here,
as
you
guys
know,
working
on
Mesa
like
a
lot
of
people
using
it,
but
yeah
so
I
think
both
our
companies
need
to
work
on
external
facing
like
what
the
customer
sees
as
happening
versus
what's
actually
happening.
It
was
really
disappointing
to
not
really
be
able
to
tell
them
that.
Well,
no
they're
wrong.
When
they're
saying
ACS
is
getting
deprecated,
they
don't
quite
mean
that
they're
talking
about
something
different
but
I,
know
what
it
looks
like
to
you
yeah.
B
C
B
The
long
and
short
of
it
is
that
they
feel
like
updating
process
is
different
between
our
different
Microsoft,
like
platform
offerings,
and
some
of
the
update
processes
are
extremely
cumbersome
and
weird,
but
yeah.
We
can
talk
more
about
it.
If
you'd
like
to
know
more
about
it
all
right,
you
did
we'll
just
help
me
about
it.
C
C
A
Yeah,
that
is,
that
is
my
sense
as
well
sweet.
Well,
in
that
case,
we
can
all
get
back
to
crunching,
get
an
extra
five
minutes
back,
but
I
appreciate
everybody
shown
up
nice
community
meeting.
We've
got
a
bunch
of
action
items,
so
I'll
do
my
best
knock
down
the
ones
that
I've
got
and
I'll
see
you
guys
at
the
next
meeting.