►
From YouTube: Ecosystem Weekly Meeting 2019-10-16
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).
B
Yeah
so,
first
is
to
say:
welcome
to
the
weekly
echo
system
team
meeting
right,
so
I
have
four
points
in
the
agenda,
so
the
first
one
is
one
thing
that
maybe
we
can
improve
as
a
team
is
to
make
say
the
calendar
invitation
open
to
like
to
everyone.
So
maybe
we
can
move
that
one
to
a
little
app
team
meeting
calendar
as
I
think
other
teams
do
right.
Why
not?
Really?
We
should
keep
this
like
a
smaller
cities
or
yes,
open,
but
yeah
so
feel
free
to
a
whatever
we
consider
is
the
rest.
B
So
we
are
trying
to
resolve
one
issue
that
we
have.
That
is
de
the
different
configurations
for
JIRA.
Right
now
we
say
the
configuration
at
the
player
level
and
then
we
have
the
service
template.
That
is
something,
and
that
is
like
the
default
settings
that
they
are
going
to
be
pre-populated
for
the
new
projects
and
we
are
talking
out
to
half
a
projects
like
the
in
tourism
settings
at
the
player
level
of
the
rule
11
and
then
of
the
service
template.
B
What
are
they
thoughts
that
and
how
do
you
spit
up
words?
I
was
talking
with
me
yesterday
and
I
think
that
they
for
us
makes
sense
to
have
a
pepperin
pepperin
like
first
player
level,
then
group
level,
and
then
the
service
template
for
me
should
behave
in
the
same
way
that
the
other
levels.
So
it's
not
just
a
template
to
pre-populate
the
theme,
but
it's
just
like
a
global
setting,
so
changing
the
they
behave
a
little
bit
from
pre-populated
settings
to
yes,
no
one
sitting.
So
what
are
you
thoughts
about
that?
B
C
So
a
really
high
level
I
think
that
what
I
would
like
to
see
from
a
UX
standpoint
is
more
parity
between
the
project
integration,
the
group
integration
and
the
instance
integration.
Whatever
we
end
up,
calling
them
because
right
now
instance,
integration
is
service
templates
right,
but,
like
I,
think
that
across
the
board,
I'd
really
like
to
see
a
pretty
close
parity
in
how
those
features
work
and
how
they
interact
with
individuals.
C
I
think
what
we
see
today
is
there
is
such
a
disparate
connection
between
how
projects
work
and
how
service
templates
work,
although
they
seem
to
do
pretty
approximately
the
same
thing
like.
Where
is
that
data
getting
applied
and
when
is
it
getting
applied?
Do
we
need
to
have
to
reapply
it
on
an
ongoing
basis?
It'd
be
much
simpler.
C
If
that
worked
much
more
like
an
active
integration
work
and
as
we
meet
in
the
middle
with
group
level,
integration
I
think
that's
where
it
really
becomes
key
to
make
sure
that
there's
some
parity
so
that
we
see,
if
I
add
it
at
the
instance
level.
All
that
is,
is
the
scope
of
what
it
applies
to
if
I
added
it
to
group
level.
It's
just
a
difference
in
scope
and,
if
I
add
it
at
the
project
level,
it's
just
a
very
small
scope
right.
C
So
that's
generally
what
I'd
like
to
see
out
of
that
as
far
as
how
we
prioritize,
which
one
comes
first
I
I'll,
leave
that
to
my
betters
to
decide
like
I,
don't
know
where
it
makes
sense,
because
I
think
that's
more
of
an
engineering
concern
I'd
like
to
get
all
of
them
done
in
in
the
near
term
future,
but
I
think
we're
how
we
approach
it
and
where
we,
where
we
go
from
an
order
of
operations.
Standpoint
is
more
along
the
lines
of
I.
C
Don't
know
what
the
backend
code
looks
like
I,
don't
know
where
it
makes
the
most
sense
to
start.
Maybe
it
makes
the
most
sense
to
start
at
service
templates
and
fix
it
at
service
templates
and
then
might
agree
that
to
the
group
and
then
migrate
that
to
project
I
I,
don't
know,
but
I
think
my
goal
here
and
my
my
personal
take
on
it
is
purely
around
I.
Want
to
see
a
more
consistent,
your
experience,
I
wanted
to
be
more
easy
to
use.
C
B
In
the
product
and
we
are
going
to
change
the
behavior
one
thing-
that
is
a
service
template
that
right
now
is
say
something
that
you
enter
the
details
and
that's
it
and
you
have
the
details
pre-populated
in
there
in
other
places.
So
now
we
want
to
sing
that
into,
like
instance,
level
settings
right.
So
it's
a
kind
of
a
settings
of
the
panelling
that
we
have
right
now.
I
think
it's
better
I
mean
it's
a
good
change,
but
I'm.
B
Having
that
in
mind,
I
can
start
to
investigate
what
are
the
implication
of
follow
that,
because
maybe
we
cannot
say
maybe
here
just
for
the
deal
I
think
maybe
you
know
a
service
template,
become
instance,
a
settings
or
instance
level
settings
is
like
that
should
apply
for
all
the
services,
not
just
for
one
specific,
so
yeah.
Having
that
in
mind,
I'm
going
to
I
have
an
issue
to
investigate
what
are
the
implications
of
all
of
these,
and
maybe
some
like
they
are
thinking
in
the
architectural
level.
C
D
C
C
Somebody
who
has
multiple
jury
instances
would
find
it
extremely
valuable
to
be
able
to
have
all
of
those
integrated
at
the
instance
level.
I
think
it
has
a
lot
of
really
interesting
implications,
and
so,
if
you
think
of
it
in
terms
of
also
access
control,
that
may
allow
like
a
JIRA
admin
or
a
get
lab
admin
to
integrate
their
their
three
JIRA
instances
right
at
the
instance
level,
forget
lab
and
then
the
individual
project
owners
can
just
pick
from
which
one
is
relevant
to
them
without
having
to
have
access
to
those
credentials
which
is
valuable.
C
D
C
One
way
of
doing
yeah-
that's
a
really
good
point.
That's
probably
something
that
needs
to
get
noted
in
acceptance,
criteria
and
I.
Think
that's
noted
in
the
issue.
Maybe
it's
not
yeah.
That's
a
really
good
consideration
for
us
to
take
into
account,
just
like
keeping
in
mind
that
we
may
want
to
be
able
to
do
this
in
the
future
is
really
valuable,
make
sure
yeah
a
class
that
can
be
reviewable
I.
Definitely.
A
A
B
C
No,
it's
that's
on
me.
I
need
to
go
update
that
I
know.
For
example,
the
I
had
it
somewhere
and
I
need
to
make
sure
to
go.
Do
it
the
gitlab
group
level
integration
that
issue
just
got
promoted
to
an
epic
so
that
no
longer
goes
to
the
appropriate
link.
So
I
need
to
go
update
that,
but
it's
yeah
I
can
I
can
take
action.
I'm
gonna
do
that.
B
C
B
Sometimes,
in
the
middle
quest
ie,
we
can't
find
like
things
like.
Okay,
this
is
a
ticket
in
thin
disc,
about
two
different
things,
for
example
in
this
is
specifically
a
someone
is
talking
about
having
feedback,
post-mortem
discussion
or
and
is
more
like
a
general
question
that
say
I
don't
know
about
will
not
like
where
we
can
find
you
notice
a
compensations
or
most
post
Morton's,
or
you
know
different
things
related
to
that
below
some
things
we
have
information,
but
then
we
don't
keep
track
or
link
into
the
issue.
B
C
C
Yeah,
you
and
I
think
Zendesk
by
default.
Everyone
has
access
to
I,
think
now
through
octa.
So
you
ought
to
be
able
to
get
into
send
us
and
maybe
wrong
on
that,
and
someone
can
correct
me
if
I'm
wrong,
but
but
yeah
you
should
definitely
have
access
to
Zendesk.
Salesforce
is
a
little
more
complicated
and
we
do
tend
to
it's
not
that
we
restrict
the
number
of
licenses,
but
we
pay
per
seat.
C
D
A
E
B
B
D
A
D
It
was
just
like
a
very
small
question:
I
was
looking
at
to
contribute
like
dogs
and
registration
starts
like
next
week.
Yay
and
I
I
saw
some
that
beams
like
these
cups,
if
they
should
have
like
extra
time
before
and
after
the
contribute.
So
that's
pretty
much
the
same
question
for
our
team,
like
what
do
you
guys
think
yeah.
F
Awesome
yeah
I
just
saw
me
for
more
information
there
about
the
contribute,
because
I
attended
so
I.
Take
that
you
know
yeah,
but
basically
the
company
sponsors
the
the
cost,
if
you're
in
a
during
the
event
post
after
the
the
event
I.
Guess
it's
probably
going
to
be
difficult,
the
if
everybody
arrives
early.
Definitely
you
can
do
something
because
everybody
is
already
here
so
yeah,
but
the
other
information
I
just
provided
there.
So
sorry
Patrick,
you
had
something
to
say
no
I
just
say.
F
A
So
there
is
okay,
so
there
is
some
dedicated
team
time
and
then
anything
before
after
would
would
be
extra
cool,
yeah,
I
guess
yeah,
we'll
get
a
discussion
going
about
that.
It
would
be
great
to
ya
figure
out
everyone's
scheduled
and
try
to
get
some
extra
team
time
and
I'm
very
much
looking
forward
to
it.
Yep
awesome
all
right
yeah,
thanks
for
bringing
that
that
up,
Justin
good
good
time
to
start
thinking
about
it
and
yeah
I
think
thank
you,
Justin
and
Arturo
for
being
proactive
about
adding
agenda
items.
A
It's
always
nice
to
open
this
up
and
and
have
discussion
points.
So
thank
you.
Just
a
quick
update
there.
12
for
and
tomorrow,
17th
and
12
5
begins
on
Friday
the
18th
I'm
still
trying
to
figure
this
out
and
learn
it
all
myself.
But
from
what
I
understand
so
the
13th
is
when
we
we
should
have
had
the
release
scope
finalized
with
the
deliverable
labels.
A
I
think
I
was
using
those
incorrectly
at
first,
so
I've
adjusted
it
so
that
the
deliverables
map
to
I
guess
issues
that
have,
mrs
with
with
work
that
will
that
have
mrs
that
will
go
into
the
release.
So
we
we
have
one
issue
with
an
mr
that
currently
can
review.
I
wasn't
sure
that
if
we
were
trying
to
finalize
the
release
scope
by
the
13th,
but
we
still
got
the
mr
like
merged
in
before
the
17th,
if
that
would
count
for
12.
A
You
know
I
think
that
that's
something
that
I'm
a
little
unclear
on
being
being
our
first
release,
milestone
so
I
I
think
I'm.
Reading
the
the
product,
workflow
timeline-
that's
the
case,
but
if
anyone,
if
anyone
knows
or
knows,
if
that's
a
correct
or
incorrect,
let
me
let
me
know:
I
guess
I'll
whole
assume
that
I
that
I've
got
that
set
up
that
I'm
understanding
that
correctly,
if
no
one's
chiming
here
awesome,
okay
and
then
yeah
just
an
update.
We
also
have
this
other,
mr
that
Justin
made
it's
in
us
to
review.
E
A
Yeah
well,
the
UX,
reviewer
I
looked
and-
and
they
were
out
on
the
last
few
days.
So
that's
why
it's
it's
taken
a
while
yeah
they're
I
guess
there's
a
chance
that
that
it
could
make
it
in
so
we'll
see.
But
if
not
twelve
four,
it's
definitely
going
in
12:5
and
and
yeah
awesome
job
for,
as
Patrick
pointed
out
getting
getting
in
Mr
Murchison
that
affects
the
entire
code
bases
there.
Your
first
one.
A
So
just
a
heads
up
on
that
and
then
I
have
the
next
item
as
well,
and
this
is
just
a
reminder
to
fill
out
the
culture
app
survey
that
was
sent
out
by
people
group
Eric
VP
of
engineering
posted
in
his
channel
on
slack
just
a
reminder
and
and
a
little
bit
of
the.
Why
of
why
it's
important
to
fill
it
out?
It's
a
at
least.
In
his
words.
It's
one
of
the
best
methods
to
positively
influence
change
at
your
company.
C
Yeah,
a
few
things
I
just
want
to
say,
I'm
working
on
the
fiscal
year,
21
hiring
updates
trying
to
let
everybody
now
that's
what
I'm
working
on
you'll
see
a
lot
of
movement
and
some
new
issues
and
I'm
asking
people
for
back
and
input
and
trying
to
get
us.
Some
more
support
add
more
people
to
this
lovely
team.
So
we
can
get
some
more
awesome
stuff
done.
So
that's
exciting!
That's
really
cool!
C
Let
me
know
if,
if
there's
anything
any
issues
that
I
open
up,
please
give
me
your
feedback
I'd
love
to
understand
better
what
we're
doing
and
kind
of
linking
in.
Maybe
these
are
in
the
wrong
order.
Linking
into
the
last
item
I've
added
a
new
epoch
for
the
API
and
SDK
work
and
that's
been
something-
that's
been
historically
kind
of
underserved,
and
so
my
focus
has
been
as
you
all
have
started
on
the
outstanding
bugs
and
security
issues
and
trying
to
just
get
that
short
up.
C
But
one
of
the
things
that
we're
gonna
have
to
focus
on
over
the
next
year
is
expanding
our
work
to
the
API
and
SDK
support
for
developers,
making
it
easier
for
developers
to
engage
with
build
upon
or
build
in
get
laughs,
and
so
that's
it
gonna
be
a
huge
focus
for
us
over
the
next
year
and
I've
started
to
stand
up
what
those
epics
should
be
inspired
to
flesh
out
those
issues.
So
there's
all
the
stuff
in
there
I
really
love
feedback.
I
really
love
your
input.
C
You
know
we
are
the
people
who
are
making
these
things
happen.
So
it's
really
valuable
to
me
to
make
sure
that
everybody's
getting
a
voice
in
there.
So
please
go
in
through
those.
Please
look
at
them
and
please
provide
feedback
where
you
have
any
thoughts.
I,
really
love
to
get
all
of
your
voices
in
those
threads
and
then
kind
of
fire.
Moving
back
up
to
be
and
we've
got,
the
customer
advisory
board
is
happening
right
now
and
we'll
be
getting
an
official
output
from
that
sometime.
C
The
next
week's,
but
the
one
of
the
one
of
the
notes
to
mention,
is
the
API
and
SDK
support
better
support
for
CLI
tooling.
All
of
those
developer
needs
have
emerged,
as
is
one
of
the
top
items
of
focus
from
our
cab
members
that
were
in
attendance.
This
is
a
really
big,
really
important
thing
for
them,
and
the
way
to
think
about
this
is
the
work
that
we're
doing
with
things
like
JIRA
is
important.
C
C
They
want
to
have
hooks
into
our
system
where
they
can
pull
in
information
from
everything,
and
so
those
those
developer
resources
are
going
to
be
increasingly
important
over
time
as
we
address
more
and
more
customers
like
that,
and
so
that,
and-
and
that
is
that
is
definitely
emerging
from
the
research
that
we're
doing
there-
we're
absolutely
seeing
customers
saying
the
same.
So
so
it's
really
exciting.
It's
really
cool
to
see
that
they
are
interested
in
the
things
that
we
are
making.
So
that's
fun.