►
From YouTube: Ecosystem Weekly Meeting 2019-10-09
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
Alright
I
have
the
first
item
just
wanted
to
say
that
Patrick
and
I
went
through
and
did
a
scheduling
pass
on.
Twelve
five
and
so
I
opened
up
a
scheduling
issue
in
our
team
tasks
board
for
us
to
discuss
things
like
priority.
Whether
there
are
other
things
we
want
to
suggest,
moving
in
or
moving
out
of
the
out
of
the
release.
So
this
this
isn't
for
discussion
of
the
issues
themselves.
We
should
still
have
those
discussions
in
the
issues,
but
it's
more
discussion
around
the
scheduling
of
12:5
and
just
the
ability
to
have
that
asynchronously.
A
So
yeah
take
a
look
at
it.
When
you
get
a
chance
next
item,
I
just
wanted
to
update
that
I
applied
the
group
ecosystem,
labeled
2/3
of
our
Toros.
Mr
s,
he
let
me
know
they
made
a
handful
of
small
M
ours
to
testing
stuff
in
the
main,
get
lab
repo
that
were
merged
in
weren't,
necessarily
related
to
work
that
we
had
scheduled
but
sort
of
reef
actors
and
improvements
that
he
had
found
kind
of
in
between
work
that
he
was
doing
so.
A
So
that's
awesome
and,
and
yet
nice
job,
Arturo
and
I
also
just
wanted
to
call
out
that,
in
order
for
Mrs
to
count
as
part
of
our
team
throughput,
they
have
to
have
one
of
the
labels
described
in
this
in
this
handbook,
page
that
I've
linked
sorry-
and
actually
it
looks
like
this
link-
is
incorrect.
So
I
will
change
that,
but
it's
a
handbook
linked
to
workflow
labels,
so
I
believe
they
have
to
be
either
community
contribution
or
feature
or
bug
or
backstage
in
order
to
be
counted
as
part
of
a
team's
Mr
throughput.
A
All
right,
moving
on
just
one
other
update
from
me,
just
wanted
to
say
that
I
updated
our
ecosystem,
workflow
board
and
I
noticed
that
the
workflow
scheduled
label
was
deprecated.
So
it's
deprecated
in
favor
of
the
workflow
ready
for
development
label.
I,
guess
those
those
both
existed
side
by
side,
and
so
the
preference
is
to
use
workflow
ready
for
development.
So
our
board
now
reflects
that
school
and.
B
That's
it
for
me,
awesome,
so
just
an
update
on
the
group
level
integration
stuff
that
I've
been
working
on
I've
got
a
couple
more
customer
interviews
that
I'm
working
hard
to
get
scheduled
to
hear
in
the
next
couple
weeks.
My
goal
is
to
have
five
done
by
the
end
of
the
month.
I've
got
one
done
so
far,
so
I
need
to
get
crackin.
B
I've
got
three
weeks
to
get
four
more,
so
I've
got
some
interesting
customers
who
want
to
chat
I,
think
I've
got
two
or
three
leads
that
I'm
pretty
sure
I
can
get
closed
this
month,
so
I
just
need
to
get
more,
and
then
I've
also
done
a
ton
of
updates
to
that
to
the
issue.
So
I've
really
tried
to
flesh
it
out
and
start
making
it
really
clear
what
we're
talking
about
if
you
want
to
click
on
that
link,
mm-hmm
just
so
we'd
have
to
switch
screen
share
yeah,
so
I
fleshed
this
out.
B
B
If
you
want
to
take
a
look
at
it,
I
think
the
the
thing
that
I'm
starting
to
think
through
here
that
I'd
ask
from
this
group
is:
if
we
could
start
thinking
about
and
in
it's
our
policy
as
a
company
like
we
don't
spend
a
ton
of
time
on
weight
like
very
specific
weighting,
but
I
think
it'd
be
valuable
to
kind
of
think
through.
How
do
we
think
from
the
back
end?
We
need
to
do
this.
What
is
gonna
be
our
approach
to
it,
because
today
there
are,
no
group
integrations
really
with
anything
right.
B
So
what
will
be
involved
in
creating
that
is
that
we're
gonna
require
new
data
structures.
Is
that
gonna
require
creating
some
new
Ruby
objects
like?
What
does
that
look
like?
So
it's
just
something
to
work
like
worth
that
is
worth
beginning
to
think
through.
It
may
be.
We
may
say,
like
we
need
to
break
this
up
into
a
couple
issues
where
we
have
one
where
we're
gonna
establish
the
you
know
a
group
group
service,
because
right
now
we
have
project
services.
B
So
do
we
need
to
establish
group
services
as
a
thing
first
and
then
go
create
the
first
group
service
with
shira,
or
what
are
we
gonna?
What
are
we
doing
there
and
I?
Think
I
also
want
to
make
sure
I
need
to
add
a
section
here,
I'd
like
to
add
a
section
about
like
reusability
considerations
or
something,
and
because
there
are
a
bunch
of
other
issues
that
this
has
been
talked
about
like
setting
up
matter
most
at
an
integration
at
a
group
level
can
follow
the
same
pattern.
B
So
it's
a
good
consideration
as
we're
working
through
this,
and
there
are
a
lot
of
little
places
where
we're
gonna
want
to
make
sure
that
this
is
fungible
and
reusable
future,
and
so
we're
setting
up
a
really
solid
foundation
for
for
work
that
we
are
going
to
do
ourselves
right
like
this
is
not
just
for
forget
lab
as
an
organization
like
this
is
our
team
you'll
be
doing
more
and
more
of
these
things
over
time.
So
it's
important
that
we
set
up
our
house
the
right
way,
the
first
time
so
yeah.
So
that's!
B
A
B
Great
work
everybody
like
Carter
is
doing
awesome.
Stuff
I
saw
Justin,
has
started
looking
at
I
wanted
to
call
out
Justin
good
job.
I
saw
that
he's
already
picked
up
an
issue
around
changing
the
banners
on
alerts
and
I
was
very
tickled
that
that
would
affect
him
in
our
application.
Like
second
week,
I
already
work
up
things
that
affect
the
entire
app
that's
cool.
It's.