►
From YouTube: Ecosystem Staff Meeting 2020-01-26
Description
Kickoff Ecosystem Staff Meeting
B
C
C
Hey
patrick,
hey
cool,
so
first
question
was
like:
shall
we
record
this?
I
tori
says
yes,
and
I
agree
I
mean
the
agenda
is
public.
If
you
know
someone
has
something
to
discuss
that,
they
don't
want
on
the
recording.
Just
you
know,
put
it
at
the
end
of
the
agenda
and
say
you
know.
Obviously
the
agenda
is
also
public,
so
don't
put
it
there,
but
you
know
say
I
have
something
that
I
want
to
discuss,
not
only
okay
cool
should
we
have
a
standing
agenda.
I
think
this
can
evolve.
C
B
Awesome
all
right.
Well,
I
put
a
few
things
in
here,
just
fyis,
mostly
sorry.
I
was
distracted
by
all
the
a's
from
patrick,
but
the
first
one
I
just
want
to.
Let
you
all
know
I
created
a
ux
foundation's
interest
label,
which
is,
I
guess,
my
way
of
tracking
things
that
ux
foundations
really
wants
to
schedule
that
are
in
the
backlog,
so
I
don't
have
to
continuously
go
through
the
backlog.
All
the
time
I
can
kind
of
just
use
that
label.
B
There
are
issues
that
need
front-end
support,
so
we
wouldn't
really
be
able
to
do
it
just
ourselves
on
the
ux
side.
So
I'd
be
all
of
the
issues
that
we
moved
out
of
thirteen
eight
and
thirteen
nine.
I
added
that
label
to
so
we
can
just
easily
go
through
and
find
what
if
we
have
capacity,
what
we
can
pull
in.
C
B
Know
and
then
my
second
one
so
some
the
ux
foundation's
members
have
been
having
to
reach
out
to
outside
of
the
team
for
front-end
support
and
they
are
starting
to
feel
a
little
bit
bad
about
asking
a
lot
of
the
same
people
who
were
from
the
gitlab
ui
working
group
for
help.
So
thanks
ip
for
building
that
tool
for
the
reviewers.
B
So
I
wanted
to
say
thanks
for
that,
because
it
kind
of
gives
them
a
view
of
who
doesn't
have
merch
requests
assigned
to
them,
and
then
I
also
just
wanted
to
throw
out
there
if
anyone
has
any
other
thoughts
or
ideas
of
how
the
ux
foundations
team
can
get
front-end
support
over
time.
If
you
have
anything,
then
just
let
me
know.
D
I
mean,
I
think,
just
in
I
have
continued
to
champion
getting
more
head
count
for
foundations
every
time
I
get
the
opportunity
to
say
so
in
general,
if,
if
you
and
ib
can
kind
of
help,
give
me
data
to
back
up
like
the
growing
backlog
and
how
there's
kind
of
continued
continued
and
growing
debt
to
address,
like
just
anything
that
gives,
gives
me
more
ammo
to
take
to
product
leadership
and
say
look.
This
is
important
and
this
is
a
growing
problem
and
it
is
not
properly
supported
today.
D
C
Yeah,
additionally,
we
also
have
people
who
would
be
interested
in
the
work.
So
there
are
a
few
engineers
that
are
interested
in
helping
out
on,
and
you
know
would
be
glad
to
be
on
our
team.
It's
it's
unfortunate
that
the
head
count
that
yeah
that
the
head
count
doesn't
necessarily
match
what
we
need.
C
You
know
it's,
it's
it's
fluctuates,
but
I
I
would
say
both
yeah
I
I
don't
know
if
it
would
make
sense
for
the
people
who
would
be
interested
in
helping
out
to
basically
create
a
list
of
those
people
right
to
not
just
fall
back
on
the
working
group
members
but
be
like
hey.
Are
you
interested
in
contributing
more
to
gitlab
ui
to
accessibility?
C
Here
is
a
direct
thing
and
you
know,
and
then
also
getting
buy-in
from
the
other
front,
end
managers
and
product
managers
to
be
like
hey.
I
mean
it
always
feels
like
the
smartest
idea
would
be
to
find
something
that
relates
to
front-end
foundations
and
their
product
group
right
to
be
like
hey,
we're
going
to
improve
accessibility
of.
I
don't
know
the
pipelines
view,
so
your
people
from
verify
would
be
interested
in
doing
that
and
verify
would
benefit
from
it.
You
know.
B
C
B
C
In
the
handbook,
or
maybe
even
the
team
in
the
team
yammer
right
so
if
we
would
add
it
as
a
role
to
that
tool,
you
know
you
could
basically
be
like.
I
don't
know,
ux
foundation's
buddy
or
whatever
right.
You
could
click
it,
and
then
you
see
it
and
ask
people
to
add
and
to
be
honest
like
it
has
been.
C
C
It's
not
always
seen
and
people
don't
appreciate
it
all
the
time
because
it's
like
hey.
I
have
the
fear
that
my
people
want
to
the
deliverables
or
hey.
Maybe
even
that
person
is
underperforming.
You
know,
I
really
don't
want
them
to
focus
on
their
stuff.
So
I
will
ask
the
other
managers
what
they
think
and
you
know
creating
them
all
or
to
the
handbook
as
a
first
step
and
get
the
other
managers
involved
and
yeah.
B
Sounds
good
cool
cool
awesome
and
then
my
last
point
here
is
just
kind
of
an
fyi
that
the
ux
foundation
team
has
an
okr
to
complete
this
26
hour.
Accessibility
course
we'll
write
up
outline
of
kind
of
what
we
learned
and
how
it
relates
to
gitlab.
So
we
can
share
that
with
everybody
who's
interested.
B
It
would
be
cool
if
front-end
foundations
went
through
the
course,
but
I
know
that
I
don't
know
what
the
budget
of
time
I
mean
it's
a
pretty
significant
time
investment
so,
but
something
to
keep
on
your
radar
for
either
next
quarter
or
something
in
the
future.
If
you
don't
have
time
this
quarter,
we
if
foundations,
ux
foundations,
go
through,
goes
through
it
and
then
says
like:
oh,
it's
really
valuable,
then
maybe
it's
something
front
end
does
next
quarter
or
something
like
that.
D
Yeah,
so
I
just
fyi,
I
made
a
bunch
of
scope
labels
for
integration,
actually,
it's
scoped,
so
it's
integration
just
make
it
easy
to
find
stuff
just
fyi
in
case
you're
y'all
digging
around
and
looking
for
things
associated
to
a
thing.
There
should
be
much
better
labeling
for
individual
integrations.
D
It's
just
gotten
to
a
point
where
my
original
concept
was.
I
would
have
this
kind
of
series
of
epics,
where
I
could
just
kind
of
put
everything
in
a
library
and
that
became
unmanageable
over
time.
So
this
is
much
much
more
reasonable
way
to
approach
it.
It's
just
also,
I
liked
being
able
to
browse
through
the
epics.
It
gave
me
a
hierarchical
structure
that
made
it
easy
to
understand
where
things
were
at
and
what
was
next
to
what,
but
it
was
just
unmanageable.
So
anyway,
that's
where
I'm
at
that's
all.
I
have.
C
D
C
D
Them
yes,
many
of
which
don't
have
anything
in
there,
but
they
exist
in
case
we
need
it.
So
every
integration
that
is
listed
in
the
docs
has
one
there's,
also
a
meta
one
for
like
integration,
colon
colon
new
for
requests
of
new
integrations
that
one's
actually
been
around
for
a
while.
I
think
I
renamed
it.
It
was
like
new
integration
previously
or
whatever,
but
yeah,
so
it
just
makes
it
much
easier
for
me
to
review
what's
out
there
and
what
the
total
volume
of
requests
is,
and
actually
I
have
a
board.
D
C
We
do
not
own
like,
for
example,
there's
the
kubernetes
integration
or
the
whatever,
so
there's
like
some
stuff
that
monitor
used
to
own
and
it
came
up
in
a
retro
recently,
so
we
have
like
a
list
of
stuff.
You
know
in
case
it
appears
in
the
integrations
overview,
but
it's
not
actually
maintained
by
us.
A
D
We
don't
there
is
it's
one
of
those
like
how
do
you
define
integrations
for
our
purposes?
What
we
mean
is
what
we
used
to
call
project
services,
and
there
are
a
number
of
literally
integrations
that
are
not
formerly
known
as
project
services.
Take
like
the
integration
with
gke
right,
like
totally
unrelated
to
ecosystem,
but
is
very
clearly
an
integration.
It's
just
not
so
yeah
we
don't.
We
don't
have
a
good
list
of
what
those
are
no.
C
Yeah,
so
what
do
you
folks
want
to
get
out
of
this
meeting
that
you
cannot
get
out
of
the
integrations
weekly?
I
really
don't
want
to
go
in
here
and
be
like.
I
want
to
cancel
it
right
away.
I
think
it's
just
like
something
to
keep
in
mind
I
mean
my
personal
motivation
is
like
to
have
three
one-on-ones
less,
but
you
know.
C
D
For
specifics,
I
I
think,
just
in
general,
it's
something
I
know
I
think
I
talked
individually
to
all
all
three
of
you
at
the
end
of
the
year
about
especially
with
matt
joining
the
team,
making
sure
that
we're
able
to
talk
to
both,
I
am
able
to
talk
to
both
matt
and
ip.
At
the
same
time
as
valuable,
especially
you
know,
we
don't
have
anything
right
this
second,
that
is
a
good
example,
but,
like
that's,
gonna,
be
valuable.
D
Similarly,
right
like
for
for
tori's
needs
like
same
thing,
I
know,
generally
speaking,
it's
gonna,
like
anything
that
foundations
needs,
is
gonna
fall
under
your
purview,
ip,
but
that's
not
necessarily
always
gonna,
be
the
case
and
and
always
valuable
to
to
just
have
that
broader
audience,
and
just
make
sure
that
all
four
of
us
are
kind
of
lined
up
on
things.
It's.
A
D
A
Yeah,
I
can
see
benefit
too
around
as
we're
doing
milestone
planning
you
know
just
sitting
down.
The
four
of
us
together
can
kind
of
figure,
some
of
that
out
around
resources
and
what
the
priorities
are
instead
of
can
I
could
I've
had
success
with
that
in
the
past
of
you
know,
it
goes
faster
if
we
just
sit
down
and
kind
of
go
through
a
high
level
overview
versus
all
of
us
individually
talking
to
each.
D
C
I
really
agree.
Yeah
I
mean
the
integrations
weekly
also
is
with
so
many
people
involved.
You
know
sometimes
there's
really
like
hey.
There
are
going
to
be
topics
that
don't
you
know,
interest
a
lot
of
people.
I
mean
this
is
the
downside
of
meetings,
but
you
know
it's
always
good
to
have
it
from,
and
I
think
it's
the
same
thing
here.
Probably
there
are
a
few
discussions.
C
You
know
that's
interesting
to
tory
and
patrick,
and
there
are
some
that
are
more
interesting
to
you
know
and
me,
and
there
are
some
that
are
interesting
to
met
me
and
patrick,
but
yeah.
You
know
so
good
cool
yeah.
That
being
said,
we
can
also
end
the
call
early
right
yeah.
It
was
great
seeing
you
all.
I
hope
you
had
a
nice
weekend
and
I
hope
that
everything
that
needs
to
be
done
before
the
end
of
the
quarter
goes
well
for
you.