►
From YouTube: Ecosystem Weekly Meeting 2019-10-23
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
Okay,
also
I
will
have
the
first
item.
I
just
want
to
make
a
very
quick
clarification
if
I
caused
any
confusion
last
week,
so
about
the
contribute.
There
is
a
per
head
dollar
amount
for
the
team
farm
budget
so
that
you
can
expense
any
time
during
the
contribute,
and
if
you
plan
team
activity
before
the
contribute
or
after
the
contribute
asking
that
come
to
be
a
channel
contributor,
twenty20
channel
for
the
expense
coverage
there,
there
will
be
some
limitations
there
and
especially
post
of
the
contributor.
A
A
C
Yeah
so
I
have
the
next
item,
which,
which
is
a
follow-up
to
what
John
was
talking
about
with
contribute
2020,
so
I've
gone
ahead
and
created
an
issue
in
our
team
task
board
for
us
to
discuss
our
contribute,
2020
plans
and
schedules.
So
there's
nothing
in
the
issue
right
now.
I
did
make
it
confidential
and
I'll
write
in
a
little
placeholder
and
ping,
everybody
on
it,
but
I
figured
yeah.
We
should
make
it
confidential
just
between
all
of
us
since
we'll
be
discussing
travel
schedules
and
that
sort
of
thing.
C
C
C
So
you
can
check
out
the
enablement,
ok,
ours
and
ones
for
other
teams
and
kind
of
see
what
what
they
all
have
planned
for
next
quarter,
and
this
is
something
that
I
y'all
might
know
this,
but
I
just
found
it
out
in
this
process
is
that
our
fiscal
year
begins
in
February
and
not
January.
So
I
was
like.
C
Why
is
everyone
talking
about
q4,
ok,
ours
just
now
like
shouldn't
that
be
done
in
October,
and
it
turns
out
that
since
the
fiscal
year
starts
in
February,
the
the
fourth
quarter
would
then
be
like
November
through
January.
So
people
probably
already
knew
that,
but
it
was.
It
was
a
new
tomb
news
to
me
so
that
I
mentioned
that
as
well.
I.
B
C
I
didn't
know
there
was
a
difference
there,
but
yeah
I
see
everyone
kind
of
used.
Thee
yeah
the
FY
before
things
so
seems,
seems
like
what
everybody
people
are
generally
on
the
same
page
about
that,
but
yeah.
There's
there's
got
to
be
some
some
resource
in
the
handbook
about
that
I'll.
Try
to
dig
it
up
just
so
that
we're
all.
On
the
same
page,
there.
C
Awesome,
alright,
that's
it
for
announcements.
Discussion
looks
like
I
only
had
one
thing
to
put
on
the
work
items:
it's
we're
working
on
a
lot
of
security
types
of
issues
right
now,
it's
a
little
confidential
and
we
can't
really
talk
about
them
here,
but
there
is.
There
is
one
epic
to
follow
that
I
linked
to
that's
currently
blocking
something
that
Arturo
is
working
on.
C
So
I
think
it's
a
good
one
for
all
of
us
to
follow
because
I'm
guessing
that
whatever
sort
of
conventions
are
decided
there
are
how
we'll
want
to
implement
these
sorts
of
application
limits.
So
I
think
that's.
Okay
to
say
the
the
epic
I
believe
is
is
publicly
viewable.
So
that's
that's.
What
it's
about
is
is
how
we
go
about
setting
various
limits
in
the
in
the
application.
E
E
So
that's
been
cool
I'm
like
currently
under
this
like
deluge
of
email
and
issues
and
all
sorts
of
stuff.
So
if
there's
anything
that
I
haven't
followed
up
on
or
you
have
outstanding
questions,
please
please
feel
free
to
ping
me
and
remind
me,
there's
just
so
many
moving
pieces.
So
if
I
drop
something
coming,
that's
not
great,
but
I
think
it's
it's
something
that
I'm
aware
is
happening.
So
just
please.
Let
me
know
if
there's
anything
you're,
not
gonna,
offend
me.
If
you
go
hey.
C
E
At
least
there's
one
person
hey
and
Justin,
just
since
we
have
some
time
and
we're
sitting
here-
and
this
is
the
the
usage
ping
stuff
makes
sense.
Now
it's
pretty
much
ready,
okay,
cool
yeah
and
I,
don't
like
as
much
as
I
deeply
hate
duplicating
data
yeah
at
the
same
time
like
it's
just
it's
so
hard
to
consume.
E
Today,
like
we
can't
like,
especially
if
we
want
to
go
in
and
add,
you
know
what
we've
got
three
integrations
track
there
today
and
we
want
to
add
basically
22
right
to
support
the
rest
of
the
integrations
like
it's
just.
It
has
to
have
a
sensible
common
home
and
actually
I
just
added
an
issue
as
well
for
adding
usage
ping
to
the
plugins
interface,
which
I
know
is
kind
of
a
weird
one
that
most
people
aren't
aware
exists.
E
So
that's
something
to
look
at
as
well,
so
I,
don't
know
how
that
one's
gonna
work,
that
one's
gonna
be
a
little
more
tricky
because
it's
not
it's
not
stored
in
the
database.
It's
a
it's
a
system
hook
that
fires
every
time
an
event
is
called
and
like
checks
to
see
what
the
other
files
are
there,
that
one
will
be
a
little
bit
anyway,
cool.
E
E
E
E
B
I
mean
this
iteration.
We
have
a
lot
of
a
comprehensive
issues.
We
have
a
caller
that
is
working
in
another
computational
issues
and
he
set
up
like
different
services,
say
fishing
issues,
and
maybe
we
can-
or
maybe
we
can
trade
it
to
combine
in
a
document
or
somewhere
like
do
you
know
how
to
access
to
the
different
services
know
how
to
set
up
locally.
For
example,
we
already
know
about
the
data,
a
stance
that
we
have,
but
maybe
we
have
I,
don't
know
more
services
that
somewhere
we
have
an
instance.
Oh,
we
have
something
working.
E
E
All
that
lab
info
is
because
there
was
kind
of
a
debate
around
whether
like,
maybe
it
just
belongs
in
one
password
like
we
could
set
up
a
one
password
group
and
then
have
all
of
that
info
store
there,
because
it
is
potentially
confidential
information,
but
I,
don't
know,
and
so
great.
Let
me
know
how
I
can
help
I,
don't
necessarily
have
an
opinion
on
where
that
needs
to
be
stored.
That's
probably
something
for
our
like
IT
Oz,
but
yeah.
If
there
is
access
to
labs,
though
that
you
need,
let's
get
it
going,
I.
D
Think
there's
two
sides
of
it
right,
like
one
side,
is
actually
what's
the
workflow.
If
you
want
to
test
integration
with
one
service
like
what
what
let's
say,
you
have
a
dear
instance
right
like
how
do
you
connect
it
or
like
how
how
you
do
it
on
development
and
the
other
side
of
it
is
the
computational
side
which
is
like
what
is
the
actual
credentials
of
the
URL
this
instance,
so
I
think
one
wants
this.
The
sign
is
like
in
terms
of
workflow.
You
can
probably
consider.
E
B
D
E
And
you
know
I
know
we
had
talked
about
a
while
back
about
the
duplicated,
your
instances
it's
actually
going
to
interesting,
because
that
the
existing
one,
the
the
one
that's
currently
at
the
Brendan
O'leary
administers,
is
on
Atlassian
cloud
and
then
the
one
we
have
set
up
for
this
team
is
actually
self
hosted.
So
we
actually
probably
do
need
both,
because
those
are
two
completely
separate
products,
or
at
least
they
have
their
own
needs
so
for
what
it's
worth
also
I'm,
not
too
worried
about
it,
because
we're
on
like
a
tiny
plan.
E
E
C
E
C
E
With
starting
on
Friday,
it
seems
cool,
well
cool,
well,
that's
exciting,
and
then
we've
got
I,
don't
want
to
like
discuss
it
directly
here,
because
I
think
we're
Nick's,
probably
don't
for
the
Sun
YouTube,
but
y'all
are
welcome.
I
have
a
number
of
issues
right
now
about
headcount
planning
that
are
that
are
in
various
places.
I'd
be
happy
to
talk
more
about
that,
but
I'm
super
excited
I
have
gone
through.
E
The
headcount
numbers
that
have
been
projected
have
been
now
reviewed
by
someone
from
research
and
from
tech
rating
in
from
UX
and,
of
course,
from
engineering
thanks,
Nick,
and
so
all
of
the
individual
parties
have
kind
of
signed
off
on
it.
Well,
tentatively,
I
guess
the
tech
writing
I.
Take
that
back
a
little
bit
in
case
Mike
sees
this
and
tech.
E
Writing
has
looked
at
it
and
is
currently
reviewing
it,
but
it
sounds
like
those
it's
going
to
be
up
to
our
our
managers
and
our
leadership
to
decide
whether
or
not
we
execute
against
that
plan.
But
it
does
sound
like
we've
got
pretty
good
buy-in,
probably
on
what
that
is.
So
we
should
be
expecting
some
amount
of
growth
for
next
year,
so
that's
pretty
exciting.
E
Definitely
I
mean
I,
don't
think
it's
gonna
be
right
because
it's
gonna
be
for
next
year
for
fiscal
year,
21,
so
it'll
be
a
little
bit
ways
out,
but
yes,
I
would
definitely
say:
y'all
need
to
make
sure
to
go
through
interview
training
here
in
the
next
couple
months.
There's
gonna
be
a
lot
of
that
in
the
first
half
of
next
year,
at
least
so
yeah
make
sure
that
that
gets
done
sometime
before
before
little
rush,
I
mean,
and
also
this
is
the
small
but
no
rush,
but
sometimes
the
next
few
months
for
sure
yeah.
C
E
E
So
there
it
is,
if
you
have
any
more
feedback,
I
know
Nick
and
I
worked
a
ton
on
it,
but
please
send
me
feedback
open
issues.
If
you
have
a
problem
with
it,
there's
anything
you'd
like
to
see
added
changed
matured
you
catch
typos,
whatever,
please
and
I
know
it's
been
called
out
a
number
of
times
recently
and
in
various
different
places,
but
these
category
vision
pages
are
maintained
by
the
product
manager,
but
that
does
not
mean
that
we
are
not
interested
in
input
and
feedback
from
everybody
and
everyone
can
contribute.
E
So
if
there
is
something
you
would
like
to
see
added
to
our
vision,
please
open
an
mr.
Please
send
it
over
I'd
love
to
get
your
ideas
and
thoughts
into
it
as
well,
and
so
don't
don't
ever
feel
like
you're,
not
welcome
to
edit
that
page,
like
everything
else
in
the
company,
you
are
welcome
to
edit
that
page.