►
From YouTube: Ecosystem Weekly Meeting 2019-12-04
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
Cool
all
right
welcome
to
the
weekly
ecosystem
meeting.
Everyone
I
have
the
first
item,
so
I'll
go
ahead
and
that
is
to
suggest
that
we
split
out
the
announcements
and
discussion
section
so
that
the
announcements
will
be
read
only
meaning
that
we
don't
need
to
vocalize
them
on
the
call.
But
anyone
can
just
add
status
updates
anything
they
want
everyone
else
to
know
about
there
and
and
then
feel
free
to.
If
you
have
discussion
items
based
on
those
announcements,
we
can
add
them
to
the
discussion
section.
A
This
is
something
we
started
doing
on
the
enablement
staff
meeting
and
found
it
I
found
it
pretty
useful.
So
far,
since
a
lot
of
that
stuff
is
just
kind
of
going
through
and
reading,
what's
written
on
those
items
which
I
don't
think,
we
really
need
to
do
yeah.
That's
that's
my
suggestion
feel
free
to
suggest
alternate
ideas,
but
I
just
want
ahead
and
broke
those
out,
so
we
could
try
it
out
cool.
B
A
On
that
point,
yeah
that's
a
great
reminder,
and
it
especially
helps
for
that
situation,
where
maybe
a
couple
of
people
get
pinged
on
an
issue
just
to
know
like
just
to,
if
you
start
looking
into
it,
just
assign
yourself
so
that
the
other
person
knows
that
they
don't
need
to
do
that.
Otherwise
we
might
be
duplicating
works.
So
yeah.
Thank
you
for
for
heiling
that
and
just
wanted
to
add
that
I
have
seen
that
that
situation
happened.
A
B
And
so
the
next
one
is
a
we
have.
Oh
I
was
I,
was
peeing
into
a
different
issue
related
to
matter
most,
but
so
I'm
not
sure
if
I
need
to
jump
into
this-
or
you
know
like,
should
be
Patrick
the
point
of
contact
in
that
case
of
how
we
how
we
can
prioritize
this
work,
I
I
know
so
exactly
how
to
handle
things
basically
to
be
more
efficient
or
less
context.
Switching.
We
might
yeah
yeah.
C
Please
feel
free
to
just
ping
me
I,
I
peeked
at
him.
I
have
not
gotten
a
chance
to
to
really
review
them
yet,
but
yes,
I
am
anytime.
You
get
pulled
into
that
and
there's
a
question
around
like
what
needs
to
happen.
Please
just
ping
me
and
then
I
can
I
can
get
those
on
our
board.
So
I,
don't
wanna
speak
to
those
directly
at
the
moment,
because
I
haven't
actually
gotten
to
read
through
them
fully
and
I
just
kind
of
glanced
at
them
and
right
before
this
meeting.
B
C
B
Honestly,
I
also
tried
to
balance
balance.
My
time
do
you
know,
because
if
I
see
okay,
how
is
like
the
eight
I
am
going?
Do
you
know
like
we?
We
are
in
the
middle
right
now,
so
it
is
looking
good
or
we
are
like.
Do
you
not
like
to
just
focus
in?
Maybe
you
know
what
is
tougher?
Maybe
so
yeah
I,
let
you
know
if
I
have
a
question
or
I'm,
not
sure
if
I
spend
more
time
on
a
few
things,
wind
other
things,
yeah
cool
thanks,
I.
B
A
No
that's
good.
Yeah
I
was
just
going
to
say
that
that
reminded
me
about
that
one,
that's
block
and
sort
of,
including
with
our
retrospective
theme
of
kind
of
group
items
together,
more
I
think
would
probably
be
okay
too.
If
we,
if
we
end
up
having
it
in
iteration,
where
someone
like
you
is
focusing
on
matter
most,
we
can.
We
can
move
that
into
their
I.
Don't
think
it's
urgent
to
get
that
to
get
that.
One
looked
at
this.
A
This
milestone
correctly
from
Patrick
but
seems
seems
like
we're
not
really
getting
a
lot
of
pressure
to
keep
that
one.
Moving,
no
really
yeah.
D
So
most
of
the
Jenkins
issue
that
are
assigned
to
the
CI
team
doesn't
really
actively
looking
into
those,
and
he
suggested
to
have
like
a
like
a
sink
meeting
with
yeah
with
engineering
and
product
from
from
all
both
teams
and
see
yeah
how
we,
how
we
continue
with
with
the
Jenkins
integrations
and
which
issues
are
most
important,
and
he
also
suggested
if
that
works
out.
Well,
we
could
make
it
like
a
regular
thing.
C
Yeah
so
in
general,
I
think
that's
so
that
is
spot
on.
It
is
definitely
not
their
priority
and
shouldn't
be
that's
why
we're
here
and
our
job
is
to
worry
about
the
third-party
integrations,
so
they
can
focus
on
building
their
competitive
product
right
and
historically,
though,
those
individual
groups
have
been
responsible
for
those
integrations,
so
they're
a
really
good
resource,
and
we
should
lean
on
them
to
give
us
knowledge
and
help
us
understand
like
the
work
that
they
were
doing
previously
and
but
yeah.
C
C
If
y'all
are
interested,
I've
got
a
pretty
good
handle
on
the
prioritization
between
the
two
I
understand
what
their
priorities
and
their
backlog
looks
like
and
I
think
we've
got
a
pretty
good
understanding,
but
if
you
think
it
would
be
valuable,
I
do
more
than
happy
to
facilitate
setting
something
out.
C
More
broadly,
like
I
I'm,
totally
okay
with
that,
especially
if
we
can
get
their
engineers
in
a
room
with
our
engineers
and
get
everybody
to
kind
of,
do
a
sync
on
here's,
here's
what
they
were
experiencing
and
here's
what
they
they
view
is
like
the
best
path
forward
and
because
they've
got
much
more
experience
than
we
do
I'm
working
on
that
stuff
because
they
built
it
right.
So
if
that
would
be
valuable
for
you
all,
I,
Nick
and
I
can
absolutely
set
something
up
between
our
engineering
team
and
their
engineering
team.
Yeah
would.
C
D
That
together,
yeah
I
think
it
would
be
nice
I
think
maybe
we
could
start
with
with
one
meeting
and
then
see
yeah.
If
you
think
it's
useful,
then
we
can
make
it
regular,
but
yeah
I
think
one
one
would
be
cool
for
now.
Yeah
definitely
would
we
have
some
questions
to
ask
about
the
integrations
and
yeah.
The
tribe
was
with
what
J
was
already
very
helpful
and
yeah.
C
B
Runner
one
thing
that
we
can
do
is
like
a
kind
of
office
hours.
That's
a.
We
can
great
document
with
all
the
questions
that
we
have,
and
maybe
they
can
explain
to
us
about
different
things,
if
I'm
not
sure,
if
you
want,
if
you
already
have
a
kind
of
a
may
request
proposition
to
do
some
change,
so
maybe
they
can
also
take
a
look
mm.
Give
me
buggies.
That
is
the
right
direction,
or
maybe
we
need
to
take
different
one.
D
C
C
C
B
D
C
Let's
do
it
so,
let's,
let's
get
some
questions
down
first
and
then
let's
set
up
a
meeting
with
with
the
broadly
interested
and
relevant
parties
and
yeah.
Let's
set
up
a
chat.
We
probably
won't
be
able
to
do
it
anytime
right
now,
because
that
the
holiday
is
coming
up
in
the
next
few
weeks,
but
we
could
probably
get
that
sometime
early
January
yeah.
C
D
C
C
What
else
we
gonna
talk
about?
Oh
sorry,
I
assumed
since
there
were
only
two
people
on
the
call
last
week
leave
or
did
not
get
to
debase
myself
yet
nope,
okay
cool.
So
we
got
another
call
here
in
a
little
bit.
We're
going
to
talk
about
mass
integrations.
We
board
will
be
there.
Let's
make
sure
to
set
a
couple
seconds
aside,
so
you
can
introduce
themselves,
everybody
Justin!
Will
you
be
joining
us?
I
know
it's
getting
late
for
you?
Yes,
I
might
they're
not
on
video.