►
From YouTube: 2021-01-21 Create:Editor 13.9 Milestone Kickoff Meeting
Description
In this meeting, we talk through the overall plans for the milestone.
We did mostly not share the screen, as everyone was using the teams main Document to keep track of discussions.
A
A
B
A
Cool
then,
with
all
this
center,
so
let's
jump
into
our
agenda
by
the
way
enrique
is
like
out
on
vacation
today
and
tomorrow
he
has
enjoying
a
long
weekend
this
time.
So
that's
great
and
I'm
not
sure
denny
should
be
here
any
second.
I
would
guess,
but
let's
start
with
the
update
on
the
directional
items
and
first
one
is
jet.
D
D
Maybe
some
of
the
factors
refactors,
I
did
weren't
strictly
necessary,
but
I
think
the
code
is
in
gonna
end
up
in
a
much
better
place
and
also
be
better
positioned
for
some
things
that
we
need
to
do
like
filling
some
of
the
holes
that
are
existing
issues,
a
lot
of
the
code
dead
around
the
issues
spam
and
recapture
implementation,
as
well
as
some
other
things.
People
like,
including
instead
of
showing
interest
in
like
alternate
captcha
implementations,
besides
google.
D
So
it's
taking
a
long
time,
but
I
definitely
understand
it
better
and
it's
gonna
end
up
in
a
lot
better
place.
I
think-
and
I
think
it's
basically
done
right
now-
I'm
just
writing
some
front-end
tests
and,
like
I
told
paul
on
the
thread
today,
I
think
this
is
the
first
view
test
two
tails
test
I've
ever
written
greenfield
from
an
empty
file,
so
I
just
am
climbing
the
learning
curve
of
that
api.
A
For
sure,
for
sure,
I'm
quickly
filling
in
for
enrique
in
this
case,
so
we
were
able
to
deliver
the
poc
for
the
setting
search
functionality
to
kind
of
search
on
page
I
will
drop
the
link
or
so
to
one
of
the
pages
where
it's
implemented
right
now,
so
you
can
actually
try
it
out
in
production.
It's
working
like
super
nice
in
a
very
kind
of
good
implementation,
and
we're
now
ready
to
move
forward
with
this
and
rolling
it
out
in
this
milestone
for
all
the
settings
pages.
D
No,
I
was
gonna
say
like
if
this
is
gonna,
be
the
regular
thing
for
the
kickoff
meeting,
maybe
a
blurb
on
the
team
page
of
like
exactly
what
you
want
here
like
everything
that
is
on
the
workflow
board
that
is
assigned
to
you
is
what
should
be
here
or
like.
I
just
searched
for
the
word
direction
on
there
and
there
wasn't
anything
specific
about
what
you're
supposed
to
put
in
this
meaning.
In
this
section.
A
So,
in
this
case,
I
think
the
direction
item
up
to
be
part
of
all
meetings.
We
do
and
are
mostly
focused
about
the
issues
that
actually
have
a
direction
label
on
them
if
you're
working
on
it,
so
those
are
the
ones
or
so
that
we
try
to
communicate
to
our
kind
of
like
users
and
customers
or
so
and
a
part
of
the
kickoff
and
in
general,
like.
I
think,
it's
good
for
the
whole
team
to
stay
informed
and
where
we
stand
as
like
major,
very
impactful,
directional.
A
A
A
A
So
it's
kind
of
really
cool
to
see
kind
of
other
teams
kind
of
like
following
our
example,
and
that
only
works
because,
like
each
and
every
one
of
you
like
take
this
really
seriously
and
kind
of
make
this
like
super
well
and
it's
a
good
pattern.
That's
like
really
useful
and
resourceful
and
big.
Thank
you
big.
Thank
you.
That
is
exciting.
A
So
for
me,
like
a
big
learning,
is
I
will
do
a
way
better
job
on
this
in
the
next
quarter.
So
don't
feel
bad
about
anything.
So
we
say:
oh,
we
didn't
hit
this
as
a
team.
It's
fine
like
it's!
This
guy's
totally
my
fault.
What
I
would
hope,
though,
if
by
kind
of
any
chance
or
so
you
still
remembered
or
so
some
okr
stuff,
I
would
really
appreciate
if
you
have
like
any
issues
or
mrs
or
so
that
are
related
to
some
of
these
okrs.
A
If
you
can
drop
them
on
their
issues
directly
there,
it's
kind
of
a
comment
link
and
some
description,
because
I
need
to
kind
of
go
through
them
next
week
in
terms
of
value,
each
and
one
of
them
or
so
how
much
progress
we
made,
and
that
would
just
make
a
lot
of
things
very
much
easier
and
there's
like
still
time
so,
potentially
till
the
end
of
this
milestone.
It's
how
much
time
I
usually
take
for
these
okras.
D
E
E
A
A
A
E
A
A
Now
that's
another
thing
that
I
do
on
the
side
or
so
where
I
need
to
kind
of
fill
in
reports
and
how
many,
mrs
were
shipped
as
a
team
per
person,
and
this
is
kind
of
thing.
We
also
measuring
a
overall
kind
of
growth
and
I
did
a
reset
with
like
the
start
of
november,
because
we're
basically
a
new
team,
so
it
didn't
take
previous
numbers
into
account
and
now
the
whole
team
is
like
constellated
differently.
So
I
have
very
different
numbers.
A
E
A
A
A
So
there's
a
high
chance
that
we're
going
to
focus
on
a
little
more
and
I
think,
there's
like
some
values
or
so
for
us
like
to
define
on
the
ux
level
or
so
on.
What
we
want
to
do
so,
there's
a
lot
of
kind
of
cool
things
we
can
do,
and
I
definitely
want
to
kind
of
work
closely
with
eric
on
this
one
because,
like
eric,
will
also
have
to
work
on
his
product
okrs
at
one
point
and
we
try
to
align
the
engineering
and
the
product.
A
A
A
A
C
A
Exciting
very
very
cool,
and
then
I
just
want
to
kind
of
answer
the
question,
because
I
kind
of
could
ask
once
or
so-
and
I
think
it's
like
a
general
important
question,
so
why
we
do
it
in
this
way
like
roll
out
this,
like
small
step
in
between
but
kind
of,
implement,
search
in
this
way
on
every
page,
because
it
feels
like.
Oh,
that's
like
a
lot
of
rinse
and
repeat,
and
it's
kind
of
not
helping
us
search
through
all
settings
pages
and
just
to
give
everybody
context
on
this.
One.
A
That's
something
I
kind
of
talk
through
as
eric
and
kind
of
strategically
just
makes
the
most
sense
to
do
in
this
incremental
way.
Just
for
the
fact
that
there's
a
high
chance
that,
like
some
of
the
settings
pages,
are
going
through
like
some
rework
in
the
future
and
how
like
some
of
the
settings
are
grouped
how
they
come
together,
there's
still
a
lot
of
ux
discovery
that
needs
to
happen
and
how
it
will
kind
of
eventually
kind
of
turn
out
and
where
settings
will
live.
A
And
the
other
thing
is
like
it's
incredibly
complex
to
do
currently.
Cross-Setting
search
because
we
just
don't
know
which
settings
are
there
in
any
kind
of
like
normalized
way
where
we
could
have
like
a
way.
Okay,
this
is
potentially
there
so
just
like
implementing
it
in
a
in-page
way,
and
you
can
search
on
this
page
using
like
something
like
jquery.
A
In
this
case,
it
makes
just
a
lot
of
sense
for
the
implementation
itself,
because
we
also
countered
the
localization
issue
where
settings
can
be
called
different
languages
and
how
whatever
kind
of
like
language
ui
have
kind
of
currently
configured,
and
that
was
the
reason
why
we
kind
of
like
chose
it
in
this
way,
and
I'm
I'm
super
super
happy
with
how
the
whole
thing
turned
out
to
be
currently
here
so,
and
I
think
that's
a
super
flawless.
Pragmatic
implementation
makes
me
incredibly
happy.
D
A
F
F
You
know,
capability
of
doing
quickly
and
cleanly
and
and
across
all
the
pages
that
do
exist,
and
it
doesn't
interfere
with
future
plans
which,
whether
it's
our
group
or
another
group,
the
settings,
there's
there's
a
lot
of
room
for
improvement
there,
and
I
see
later
on
in
the
open
agenda.
Paul's
got
an
idea.
This
is
not
something
that's
off
the
table.
F
There
have
been
other
ideas
that
michael
and
I
have
tossed
around
about
like
how
we
can
create
objects
that
are
reusable
settings
chunks.
That
could
then
be
surfaced
elsewhere
in
that
app
and
globally
searched
and
and
all
these
bigger
ideas
are,
are
still
on
the
table
and
until
we
have
that
it
kind
of
would
it
would
be
a
lot
of
rework,
I
think,
to
implement
search
again
under
this
new
structure.
So,
given
our
current
structure,
this
is
probably
the
the
best.
A
And
then
the
final
thing
I
want
to
highlight-
and
maybe
denise
wants
to
talk
a
little
more
to
this
or
so
the
web
ide
is
like
also
a
big
focus
for
us,
because
we're
not
dropping
it
in
this
case,
we'll
kind
of
move
forward
with
like
leveraging
finally
added
to
light
within
web
ide
and
that's
incredibly
exciting.
That's
like
such
a
major
milestone
for
our
journey
and
what
we
thought
about
like
added
to
light
how
it
should
be
not
only.
A
This
is
if
we
ever
come
to
the
place
now
we
say
hey,
it
would
be
cool
if
our
editor
could
have
functionality.
Xyz
then
it's
like:
oh
that's
a
plug-in.
We
can
do
it
this
easily
and
now
it's
rolled
out
for
a
single
file
editor
and
like
static
or
kind
of
like
the
web
id
as
well
and
wherever
we
ever
else,
we
use
edit
to
light.
So
that's
like
super
super
cool.
It
makes
me
very
happy
and
maybe
denise
you
want
to
add
something.
E
It's
there's
not
that
much
to
to
add
here,
like
I've,
linked
the
to
the
to
the
issues
that
have
to
be
tackled
during
this
milestone
in
general,
the
poc
is
out
there.
The
performance
measurements
are,
I
believe,
in
the
poc,
not
in
the
issue.
Let
me
just
double
check.
Yes,
the
performance
yeah,
yes,
the
performance.
A
E
E
One
task
and
yeah
like
delivering
either
light
to
everybody
would
be
a
perfect
celebration
of
one
year
effort
with
eddie
light,
like
I,
I
believe
first
eddie
delight
has
been
presented
at
one
of
these
meetings
actually
roughly
exactly
one
year
ago,
yeah
something
like
end
of
january,
beginning
of
february,
so
yeah
that
would
be
perfect.
One
year
trip.
A
C
C
Is
my
settings
even
from
the
what
we
present
to
the
user
in
the
web
interface
is
I'm
editing
a
glorious,
json
file
and
what
makes
this
interesting
is
rather
than
having
to
search
for
the
key
I'm
interested
in.
I
just
type
in
the
key
that
I
want
to
configure
away
from
the
default.
So
I
think
that's
interesting,
so
we
would
have
like
a
user
settings,
a
project
settings
and
a
group
settings
and
admin
settings,
but
rather
than
I
have
to
search
for
the
field.
D
C
That's
the
main
user
goal
is
I'm
trying
to
find
the
key
I
want
to
change,
but
when
I
change
a
file
I
just
type
in
the
key,
I
want
to
change
and
there's
like
really
smart,
auto
completing
things
when
I
start
entering
keys
of
the
possible
types
of
keys
that
I
can
add
to
there.
If
you've
never
used
vs
code,
changing
your
settings
and
source
graph
does
this
too
source
graph?
Does
it
really
well,
I
like
the
way
sportscraft.
Does
it.
C
Yeah,
I
don't
that
I'm
not
sure
what
happened
there.
I'm
sorry,
chad,
I
think
when,
when
I'm
trying
to
change
the
settings
right
now,
our
settings
are
just
spread
everywhere
and
I
have
to
go
find
the
field.
But
when
I'm
editing
a
file,
that's
going
to
override
defaults,
I
just
type
in
the
field
I
want
to
over
override,
which
is
much
and
it's
the
actual
field.
I'm
not
looking
for,
like
some
sort
of
descriptive
name
that
could
have
collision
with
other
things.
It's
the
actual
field,
so
yeah.
C
D
Okay,
I
think
we're
talking
about
two
different
things.
I
was
yeah.
I
know
what
you
mean,
how
vs
code
works
and
you
actually
go
in
and
edit
the
json
file,
but
I
was
sort
of
thinking
like
expanding
this
approach,
we're
going
with
where
there's
like,
scraping
the
html
on
the
page
to
sort
of
do
this
dynamic
search,
but
extracting
that
and
moving
it
to
the
back
end
at
build
time
like
at
build
time
generate
and
scrape
all
of
these
pages
make
a
json
file.
D
C
Yeah,
I
think
I
think,
though,
like
there's.
There's
an
opportunity
like
searching
users
have
a
hard
time
finding
a
thing
so
searching
can
help
with
that.
But
searching,
isn't
a
perfect
they're,
not
they
still
have
to
type
in
the
right
thing
to
search
for
they're
going
to
have
collisions
of
things
they
want
to
look
for.
C
I
think
I
think
if
we
try
to
get
to
the
what
the
user
is
actually
trying
to
do,
they
know
I
want
to
change
something
with
a
source
graph
or
I
want
to
change
some
sort
of
merge
request
settings
the
way
vs
code.
Does
this
because
there's
just
one
place,
I'm
updating
settings
when
I
type
in
a
key
and
I'm
going
to
share
my
screen
so
we're
all
looking
at
the
same
thing.
C
I've
gone
light
mode.
That's
a
personal
update!
Okay,
so
here
they
have
this
cool
like
okay,
you
get
to
see,
you
know
a
glorious.
You
know
things
like
this
and
it's
all
one
page
and
there's
my
settings,
but
I
can
hit
this
awesome
json
thing,
and
these
are
only
settings,
I'm
overwriting
the
defaults.
C
It
is
interesting,
and
I
think
it
also
makes
like
our
documentation
for
oh
here's,
how
you
want
to
update
this.
It's
just,
oh
just
add
this
key
to
your
settings
file
and
it's
no
problem,
and
I
think
this
can
just
be
a
presentation
layer.
I
don't
think
it
has
to
be
an
actual
file
on
the
back
end,
although
that
would
be
great.
I
think
that
you
can
we
we
can
get
here
just
by
presenting
the
settings.
This
way.
D
C
E
C
F
I
think
the
this
is
interesting
for
a
couple,
different
topics
that
we've
discussed
over
the
past
couple
months
related
to
settings.
But
one
thing,
not
everybody
even
knows-
is
that
global
search
did
introduce
the
ability
to
search
some
settings
and
they
ran
into
some
challenges
because
they're
basically
manually
indexing
our
our
settings
files,
and
so
they
chose
some
of
the
ones
that
they
felt
were
through.
Research
and
common
sense
were
most
important
and
most
commonly
accessed.
But
it's
not
a
scalable
solution
and
a
maintainable
solution.
F
F
I
think
the
challenge
that
we
have
with
something
like
a
flat
file
or
or
global
view
is
that
some
of
our
settings
views
are
rather
complex.
They
have
tables
that,
have
you
know,
you're,
managing
multiple
entries
in
a
table
and
deleting
records
and
rows
from
that
table,
not
that
that
can't
be
managed
in
a
structured
data
format
like
json,
but
I
think
the
the
needs
of
our
specific
settings.
E
F
Then
we
can
consume
it
in
both
contexts
right,
so
we
could
have
a
global
settings
view
that
just
pulls
all
of
these
objects
in
and
lets
them
be
searchable
but
say
in
a
merge
request.
There's
like
three
or
four
settings
that
you
might
want
to
have
accessible
there.
Maybe
something
in
that
file
could
show
that
like
show
it
on
these
views
right
like
now,
you
have
a
little
settings
gear
or
something,
and
it
pulls
up
the
three
most
accessed
and
most
relevant
features
that
you've
identified.
C
I
think
I
think
it's
a
great
idea,
I
think,
for
even
when
I'm
describing
a
prerequisite
will
be
to
we.
We
need
to
have
a
lot
of
metadata
around
every
setting,
and
I
think
that
alone,
no
matter
how
we
want
to
present
it
is
going
to
be
a
really
great
idea.
The
more
we
could
do
define
a
setting,
not
with
any
presentation,
but
just
this
is
all
the
metadata
around
it
and
then
automate
the
presentation
of
it.
That
sounds
really
nice
cool.
D
Yeah,
that's
exactly
what
I
was
gonna
say
like
this.
You
can
have
both
you
just
you
need
to
add
metadata
and
as
far
as
being
able
to
represent
it,
like,
I
know,
there's
some
complex
ui
but
under
the
covers
everything
is
either
stored
in
a
relational
database
or
redis
in
some
data
structure.
So,
theoretically
it's
possible
to
represent
everything
in
json,
yeah,
arrays
and
hashes.
C
No
100
and-
and
it
is
and
like
some
of
the
more
complex
things
I'm
thinking
about
is
like
we
have
like
some
funky
protected
branches
views
and
we
have
like
our
approval
rules.
What
makes
those
inputs
interesting
is
they
they
do
have
like
some
sort
of
validation
with
them,
but
these
what
I've
seen
like
with
source
graph
and
other
ones
like
it'll,
do
that
validation
as
I'm
entering
the
data
like
it'll
red
squiggly
and
be
like
hey.
C
F
C
Yeah
now
that's
that's
interesting
on
a
really
positive
note,
this
kind
of
thing,
which
seems
like
super
daunting
nathan
friend
just
he
started
doing
this
for
shortcuts
itemizing
all
of
our
shortcuts
into
one
glorious
like
file,
which
is
really
great,
and
it's
so
powerful
having
all
that
metadata
in
one
place,
it's
a
really
god.
I
appreciate
this
conversation
it's
because
I
think
in
the
name
of
iteration,
we've
done
not
a
whole
lot
of
forward.
C
A
Like
out
of
curiosity
or
so
because
you
thought
a
lot
about
this
and
I
added
the
questionnaire,
do
you
know
any
other
like
non-editor,
apps
or
so
recess
kind
of
like
really
leveraging
like
configura
like
the
setting
stuff,
because
it
feels
like
it?
Probably
in
our
space,
where
we
say
we're
kind
of
very
developer
focused
it's
kind
of
something
where
okay,
it's
kind
of
expected
or
so.
But
I
wonder
if,
like
yeah,
it's
just
a
pattern.
That's
more
used!
Yeah.
C
Well,
you
know
gitlab
yaml,
like
like
we
kind
of
do
it
for
a
pipeline
configuration,
but
there's
some
other
reasons
behind
that
source
graph
is
interesting
because
source
graph,
isn't
I
mean
it's
in
the
space,
it's
in
the
developer
space,
but
it's
not
an
editor
and
it's
not
necessarily
a
developer
tool,
although
it
is
just
totally
focused
on
code,
I
don't
know,
but
I
really
like
I
really
liked
it
and
I've
had
a
really
good
experience
with
it.
But
I've
noticed
too,
like
I
think,
a
number
man.
E
C
Have
to
think
of
I'm
gonna
try
to
see
if
I
can
find
one.
That's
not
a
dev
product
that
does
this
because
I
was
thinking
of,
like
I
think
digital
ocean
and
other
things
like
that.
Do
it
as
well.
So,
no,
not
I'm!
Thinking
of,
I
think
I
wonder
if
wordpress
does
like.
I
bet
there's
some
cms
too,
like
for
content
creators.
I
bet
they
have
some
as
well
I'll
have
to
do
some
research
on
that's
interesting.
D
A
I
started
to
use
webstorm
to
give
it
a
try
for
javascript
development.
I
really
like
the
editor
but,
as
you
say,
like
the
settings,
they're
horrible
like
I
constantly
need
to
search
for
everything
and
still
they
do
not
make
any
sense
to
me,
and
I
wish
they
would
have
like
a
json.
I
just
have
a
markdown.
D
F
F
F
A
F
C
A
D
F
C
F
F
Provide
access
to
relevant
settings
in
context
with
a
feature
that's
more
about
getting
it.
You
could
probably
create
an
issue
in
the
search
all
settings
across
gitlab,
okay,
because
that's
kind
of
an
x
approach
to
that.
So
I'll
put
that
in
the
agenda
the
link
to
that
epic.
I
don't
think
that
epic
has.