►
From YouTube: Kickoff 15.0 - Ecosystem:Foundations
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
A
A
They'll
document
that
in
the
search
that
they
use
to
find
it
whether
it
was
found
in
js
or
whether
hamel
and
then
also
so
we'll
get
a
number.
So
for
this
we
may
find
30
popovers,
then
that
number
would
contribute
to
the
backlog.
We'd
create
30
conversion
issues
that
would
create
the
backlog
for
the
200..
A
The
engineers
also
create
a
conversion
guide
where
they
kind
of
explain
what
they
saw
and
how
they
suggest
that
you
fix
it.
So
they'll
give
like
a
code
example,
and
I
actually
used
that
guide.
I
did
some
checkbox
conversions
on
pajamas
migrations
migration
day
and
it
was
really
cool
because
it
explained
it.
It
really
well
and
you
could
tell
that
they
really
thought
it
through.
So
all
I
had
to
go
in
and
do
is
really
just
do
the
conversion
and
then
merge.
A
So
that's
another
really
big
focus
for
the
team
and
our
goal.
Let
me
just
say
with
that
too
we're
getting
close.
I
think
this
will
take
us
to
just
over
halfway
of
conversion
or
disc
or
component
conversion
discovery
and
we'll
get
more
of
a
read
on
how
long
we
think
it
will
take
us
to
kind
of
discover
the
entirety
of
all
of
the
components
and
actually
get
a
solid
number
on
when
we'd
be
done.
The
conversions
and
when
we'll
have
the
backlog
actually
completed.
A
For
14.9
and
1410,
we
delivered
three
fixes
to
gl
featured
search,
which
is
the
search
bar
that
you
use
to
filter
mrs
and
issues
and
we're
going
to
continue
that
and
do
one
one
more
issue.
This
release
around
the
word,
multiple
words
getting
splitting
unexpectedly
when
you
hit
them.
So
you
can
see
here
in
this
example.
The
not
connected
is
getting
shifted
outside
of
the
label
token,
and
we
have
three
proposed
solutions
for
this:
the
team's
going
to
figure
out
which
one
we
do.
A
In
tandem
with
that,
we
want
to
start
thinking
about
an
actual
new,
filtered
search
bar
that
supports
everything
that
we
want
it
to
do
and
will
work
better
and
scale
better.
So
we
don't
have
an
issue
for
that.
Yet
I
should
probably
get
one
going
as
well
as
a
maybe
even
a
canvas
around
an
opportunity
canvas
around
having
a
very
consistent
search
experience
across
objects
that
filters
well
and
does
everything
we
want
it
to
do
in
the
ui
and
then
finally,
the
last
part
is.
A
I
grouped
three
navigation
and
settings
changes
which
I'm
just
gonna
go
through.
So
one
is
a
carryover
from
fortino,
and
that
is
switching
packages
and
registries
with
monitor
on
the
left,
sidebar
and
what
that
will
do
will
get
them
in
line
with
devops
and
what
you
would
expect.
A
The
second
one
is
getting
consistency
between
the
settings,
order
between
projects
and
groups.
So
you
can
see
here.
Web
hooks
on
groups
is
way
down
at
the
bottom.
We're
simply
going
to
move
that
up.
So
those
are
at
parity
with
each
other
and
we've
kicked
off
one
other.
We
got
some
feedback
that
the
top
nav
menu
the
term
menu
with
the
hamburger
the
menu
might
need
to
be
considered
to
be
something
else.
A
So
it's
just
an
issue
that
I
opened
to
investigate
the
decision
to
call
it
that,
because
we
did
have
a
handoff
from
another
team,
so
we'll
understand
the.
Why
and
we're
just
going
to
look
in
to
see
if
there's
a
maybe
another
word
that
might
work
and
just
get
to
the
bottom
of
that,
so
that
our
team
kind
of
understands
that
in
the
direction
and
why
and
why
it
was
taken.