►
From YouTube: Geo Team Meeting 1/2
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
B
Okay,
I
think
off,
yes,
I
I
can
lick
it.
So
I
am
currently
reading
the
Mistborn
trilogy
the
final
Empire,
which
is
a
fantasy
thing,
and
it's
really
good.
So
I
started
like
a
friend
of
mine
I,
like
reading
science
fiction,
a
lot
and
when
I
don't
read
science
fiction
and
fantasy
and
other
things,
but
a
friend
of
mine
recommended
it
and
it
is
absolutely
spectacular.
B
It
has
a
really
cool
magic
system
which
has
to
do
with
metals,
but
I'm
not
going
to
go
into
detail,
but
it's
just
really
like
enjoyable
to
read
and
I
started
before
going
on
vacation
and
then
yeah
now
I'm
in
book
three
and
they're
like
chunky
books
like
800
pages
and
I'm.
Just
like
so
it's
great.
That's
me.
Let
me
link
it
because
I
think
you
should
read
it
if
you
like
fantasy.
A
Well
then,
I'll
follow
on
next,
because
I
also
really
enjoy
fantasy,
and
while
the
current
book
that
I'm
reading
is
actually
about
the
birth
of
Pixar,
it
doesn't
have
enough
dragons
in
it.
For
me
to
properly
enjoy.
The
book
is
the
last.
The
last
set
of
books
that
I
really
enjoyed
was
an
extension
of
the
Farseer
trilogy
by
Robin
hobb.
A
So
if
you've
read
them
all
you'll
pick
up
on
these
little
things
that
come
along
the
way,
and
it
gives
you
that
warm
fuzzy
feeling
of
you
know
ever
having
seen
it
all
I've
seen
all
these
things
that
she's
talking
about
them,
there's
a
that
was
my
favorite,
but
I.
Think
the
last
one
I
read
was
probably
about
9
9
to
12
months
ago,
so
I
mean
so
I'll
go
and
have
a
look
at
funneling
ponics
owed
about
you.
Get
real.
C
I'm
trying
to
remember
the
book
that
I'm
reading
right
now,
because
it's
on
Kindle
so
don't
always
see
the
like
the
cover
but
I
think
it's
the
history
of
everything
or
something
like
that.
It's
is
not
collection
of
like
it
goes
telling
you
that
history
about
geology
and
it's
a
compilation
of
a
lot
of
historical
things
more
or
less
related
to
science.
C
It
has
been
like
a
great
reading
and
I
also
really
enjoyed
the
hitchhiking
guides
to
the
galaxy
at
home.
If
I'm
serious,
it's
actually
I,
read
them
in
Portuguese,
but
I'm
here
just
to
get
them
in
English
again
and
the
Portuguese
translation
is
so
good
that
I
think
III
don't
want
like
to
get
like,
perhaps
a
different
feeling
with
the
English
version.
It's
the
original,
but
the
puns
in
Portuguese
are
so
well
made
as
well.
So
I
think.
A
That
same
in
it's
the
same
in
the
English
version,
I
almost
feel,
like
they've,
tried
very
hard
to
make
it
work
in
your
in
your
first
language
and
for
someone
like
it.
Sometimes
when
you
using
your
second
language,
you
don't
quite
get
all
of
the
puns
and
the
play
on
words
and
I.
Think
if
I
read
it
in
my
second
language,
I,
definitely
miss
out
on
a
whole
bunch
of
stuff
ya,
know
I.
D
A
That's
okay:
well,
there's
only
a
couple
of
things
on
the
agenda
but
feel
free
to
add,
as
as,
if
you
think
of
anything,
I
seem
to
have
most
of
them,
but
I'll
get
started
and
if
anyone
has
anything
to
add,
please
she's
adding
the
first
thing.
It's
just
an
advert
that
the
infrastructure
team
is
looking
for:
seed
engineers
for
the
performance
team,
that's
being
created
and
the
usual
disclaimer
that
goes
I.
A
You
know
I
really
enjoy
working
with
everyone,
but
it's
just
about
making
sure
that
people
are
aware
of
opportunities
that
exist
outside
of
geo
and
then
I
wanted
to
just
give
a
quick
update
on
the
things
that
are
happening
around
so
I
mentioned
at
the
beginning
of
August.
That
I
was
keen
to
do
a
round
of
informal
360
review
feedback,
so
I'm
busy
working
with
Jessica
to
get
a
culture,
and
so
they
set
up
for
that
I
realized
I
could
go.
A
I'll
just
go
back
to
Google
Docs,
and
so
that
should
come
out
in
the
next
week
or
two
when
I
get
through
that,
then
a
fabian
and
I
working
on
planning
for
the
team
and
the
department
for
next
year,
so
Fabian's
working
on
setting
up
what
the
product
goals
are,
that
we
would
like
to
achieve
by
the
end
of
the
year
and
then
I'm
working
that
I'll
work
with
him
to
figure
out
how
we'll
actually
get
that
done,
and
what
the
proposal
needs
to
look
like
in
terms
of
you
know.
Do
we
need
more
people?
A
A
So
also
I've
said
that,
unlike
other
teams,
he'll
actually
be
reporting
in
to
me
so
that
we
will
be
a
cross-functional
team
rather
than
having
reports
in
separately.
Pretty
sure
that
that's
going
to
be
fine
this,
but
there's
one
the
other
team.
That's
doing
that
model
and
I,
don't
see
there
being
any
problems
with
that
and
the
offer
will
go
out
this
week.
A
So
we
should
hear
back
make
sweet
if,
if
it's
been
successful
and
last
thing
is
that
there
is
an
and
retrospective
item
around
change,
the
change
to
the
new
process
and
I'm,
looking
forward
to
hear
back
any
feedback
that
anyone
has
around
the
changes
we've
made.
Now
that
we've
been
running
it
for
two
months,
I
have.
C
A
Happen
well,
we
can
still
happen,
but
because
his
time
is
split
between
us
and
other
teams,
it
can
be
difficult
to
try
and
coordinate
when
it's
our
turn
and
when
it's
their
turn
and
so
just
to
try
and
give
people
a
bit
more
focus.
A
lot
of
that
shared
Ness
is
starting
to
change
where
people,
instead
of
being
shared
across
multiple
teams,
are
being
focused
to
specific
teams.
So
kachelle
will
now
be
able
to
focus
on
his
other
team
and
will
be
able
to
get
someone
to
focus
on
our
team.
I.
C
Also
have
something
else
to
ask
for
the
front
end
engineer.
I
know
this
is
super
rare
or
maybe
weird
to
ask,
but
we
should
have
someone
that
may
also
be
able
to
improve
our
play.
Is
it
front-end
code
so
someone
that
may
be
able
to
to
make
like
the
the
things
that
running
in
the
terminal
also
beautiful
in
a
way
because
we.
D
C
A
C
On
not
on
that,
if
you
use
a
few
terminal
tools
like,
for
example,
yarn,
they
have
like
this
nice
progress
bar
and
they
do
some
kind
of
terminal
animation.
Other
tools
also
pay
some
attention
to
how
like
the
use
of
colors
our
baby
used
using
some
that
singles
er
some
ASCII
art
or
this
kind
of
stuff
like
to
improve
the
tool.
Okay,.
A
Understand
what
you
mean,
I
think
that
that's
probably
I
can
see
that
that's
actually
quite
a
different
skill
set
from
a
front-end
engineer
and
I
think
that
someone
who's
got
experience
in
the
front-end
technologies
might
not
actually
know
how
to
even
go
about
making
those
changes
into
in
the
terminal
in
terminal
world.
But
I
take
your
point
that
that's
something
that
would
actually
be
quite
nice
to
have
in
gitlab,
because
a
lot
of
it
is
actually
done
through
the
terminal.
Annie
I
agree
with
Ashley.
A
It
sounds
like
we're
talking
more
about
UX
and
I
don't
mean
the
first
thing
we
need
to
do
is
figure
out
from
a
UX
perspective.
What
do
we
actually
mean
by
making
it
nicer
and
with
all
of
the
different
personas
that
use
the
terminal?
I
mean
there's
developers,
there's
systems
administrators,
you
know,
there's
the
users
of
get
there,
the
administrators
of
get
calm
and
then
here's
the
administrators
of
the
self
managed
and
I
think
we
need
to
figure
out
exactly
what
nice
and
means
and
then
figure
out
the
skill
set.
B
I
think
there's
also
a
little
bit
of
additional
good
news,
though,
because
we
are
getting
a
product
designer
in
November
and
that
person
has
at
least
she
does
not
have
a
ton
of
experience
with
command-line
UX.
But
I
spoke
in
the
interview
about
the
need
for
us
to
take
a
look
at
our
all
sort
of
user
experience
when
it
comes
to
the
terminal
and
I.
Think
I
personally
think
that's
actually
really
important,
because
in
some
scenarios
we
may
just
not
have
a
user
interface
available,
and
so
I
see
your
point.
B
But
I
also
think
that
we
need
to
think
like
quite
carefully
on
like
what
we
actually
try
to
achieve
and
what
is
important.
But
it
may
be
really
important
in
for
some
but
disaster
recovery
scenarios
right
where
you
can't
access
the
the
graphical
user,
interface
anymore,
potentially
right
and
then
figuring
out.
What
are
people
actually
looking
for
when
they
are
interacting
with
the
command
line
in
in
that
scenario
or
during
installation?
Right
where
you
know
there
tons
of
terminal
commands
right.
B
I
know
that,
for
example,
ash
has
posted
I,
think
some
sort
of
like
run
book
style
applications,
but
I
think
there's
a
lot
of
like
interesting
opportunities,
but
I
also
think
we
don't
fully
or
if
I,
don't
fully
understand
what
the
user
need
is
at
the
moment
and
what
their
expectations
are
right.
I
think,
but
I
do
think
it's
an
important
part
of
geo,
because
people
like
that
first
contact
with
the
product
is
probably
through
the
command
line
right
and
there's
a
lot
of
like
you
know
like
gee
or
check
to
your
status.
B
A
C
A
A
A
A
B
E
B
Essentially,
this
is
something
that
written
I
have
quickly
touched
on,
and
now
that
I've
been
here
for
a
little
while
and
I
had
more
more
time
to
sort
of
look
at
the
issues.
Right
and
I've
started,
creating
a
road
map
and
all
of
those
things
using
using
ethics,
but
I
think
what
I'm
going
to
do
in
the
future
and
that's
also
a
call
for
feedback
is
I.
Think
at
the
moment
we
have
some
pretty
chunky
large
epics,
that
I
think
frankly,
thought
would
be
smaller
when
I
wrote
them,
but
the
more
I
interact
with
him.
B
Let's
say
within
a
month
right
board
like
a
month
or
two,
but
that's
kind
of
it,
and
if
we
can't
chunk
it
down
to
that
size,
then
we
we
should.
We
should
think
about
it.
A
little
bit
more
I
think
that
that's
something
that
I've
been
thinking
about
in
the
last
few
days,
because
I
would
like
to
avoid
a
situation
where
we
sort
of
have
issue
creep
in
these
these
ethics.
We
look
at
things
and
we
understand
them
better
and
then,
while
we
understand
them,
we
understand
them
many
more
problems
that
we
ought
to
fix.
B
So
we
create
more
issues,
we
add
to
the
epics
and
then
they
they
just
expand
indefinitely
right
and
so
I
think.
My
my
plan
is
in
the
next
few
few
days,
slash
like
until
the
end
of
September,
also
to
make
sure
that
the
epics
that
we
have
contain
sort
of
smaller,
sub
epics
that
are
like
very,
very
clearly
sort
of
this
is
what
we're
going
to
do.
And
then
maybe
we
can
try
to
deliver
that
for
a
specific
release,
or
at
least
we
can.
B
We
can
be
very
strict
in
when
we,
when
we
we've
done
these
five
things,
we're
done
with
this
epic
and
we
are
closing
it
and
if
there's
more
stuff
right,
we
are
going
to
open
a
new
thing
and
say,
like
that's.
The
next
iteration
right
and
I,
think
that
will
allow
us
to
close
things
off
a
little
bit
more
more
easily.
But
it
also
means
I
slash.
D
B
Can
you
see
this
okay,
so
I
think
the
good?
A
good
example.
Is
this
one
here
so
like
add
and
replicated
data
types,
I
I
started
with
this
alright
and
I.
Think
in
the
beginning,
also
out
of
ignorance,
I
thought
there
are
not
that
many
data
types
left
right,
but
it
turns
out
there.
There
is
a
really
long,
long
list
of
items
that
actually
still
need
to
be
replicated
and
aren't
right,
namely
this
year.
So
that's
a
large
amount
of
work
right,
even
like
every
individual
piece.
B
Here
is
a
large
amount
of
work
right,
so
I
think
stating
on
a
high
level
that
we
want
to
replicate
all
unreplicated
data
types
is
still
valid
right,
that's
the
ultimate
goal,
but
this
is
not
something
that
is
achievable
in
one
iteration
right,
and
so
when
we
started
and
it's
still
a
little
bit
messy
right,
let's
say
the
support
for
design
repositories
was
one
single
issue,
but
it
was
not
broken
down
further.
It
was,
you
know
like
one.
B
B
They
are
individual
features,
but
they
still,
they
still
are
a
lot
of
work
and
they
can
probably
be
broken
down
quite
like
easily
into
or
not
easily
quite
significantly
into
different
things.
So
that
is
what
I'm
talking
about
so
that
that's
one
of
the
examples,
the
other
one
was
for
upload
verification.
B
So
that's,
maybe
even
a
little
bit
big,
but
there
we
are,
but
that
again
goes
to
like
an
effort
on
a
like
sort
of
genetic
level
that
we
have
the
intention
to
verify
all
the
data
sources.
I
think
I
think
in
the
beginning,
I
thought
this
was
sort
of
epic,
if
you
level
but
I,
don't
think
that's
true
and
I
think
so
we
need
sort
of
this
additional
layer
to
to
a
console
that
I.
B
That's
a
that's
a
good
question
and
I
think,
philosophically
speaking,
actually
I
think
I
should
probably
add
like
verify
all
currently
replicated
data
sets
like
at
this
point
in
time,
because
this
is
probably
going
to
be
a
never
ending,
never
ending
story.
I
think
this
was
necessary,
at
least
for
me,
to
like
write
down
why
this
is
a
problem,
was
worth
solving
right
and
why
we
should
do
it
and
why
it's
relevant,
but
I,
think
there
should
be
an
understanding
in
general
right
like
after
this
that
for
a
new
data
source
we
will.
B
We
will
do
this
and
I
think
actually,
as
part
of
the
work
that
we're
doing
for
replicating
data
I.
Think
there's
an
understanding
in
in
geo
sort
of
growing
that
going
forward
for
everything
new,
but
we
always
want
to
verify
things
as
well
right,
so
it
will
be
become
sort
of
a
thing
for
for
new
data
types,
I
think.
D
The
the
key
there
is
that
we
need
we
need
to
be
involved.
The
Geo
team
need
to
be
involved
in
the
early
discussions
of
a
new
type
of
data.
Yes
type,
that's
added,
so
you
have
a
team
that
comes
out
of
and
so
yeah
it's
the
the
sort
of
male
style
approaches
to
know
so
pick
it
up
after
it's
been
implemented,
which
is
kind
of
how
we've
been
doing
it
yeah.
D
The
next
iterative
kind
improvement
could
be
that
we
we
try
and
get
more
involved
at
the
earliest
stages
of
these
new
data
types
and
I.
Think
in
parallel-
and
we
interesting
for
us
to
try
and
see,
is
there
a
way
we
can
structure
our
code
or
put
something
in
place
that
makes
it
really
easy
for
new
data
types
that
are
being
created
that
automatically
get
geo
support.
So,
instead
of
kind
of
retroactive
you
know
sort
of
making
it
work.
We
say:
well
he's
a
his
own
framework.
We
have
four
data
types.
D
B
One
I
think
that's
a
yeah,
but
I
think
that's
a
that's
a
that's
again.
I
think
it's
sort
of
a
separate
epoch
right,
which
is
probably
to
say,
make
it
easy
or
incredibly
easy
to
support
Geo
when
adding
a
new
data,
type
right
and
I.
Think
that
is
I.
Think
then
we
would
need
to
look
like
okay.
What
does
that
actually
entail
right?
And
can
we
break
that
down
further
into
sort
of
sub
epochs
right,
because
I
mean
little
bit
of
my
out
of
depth,
because
I
can
imagine
that
that
is
sort
of
POC
territory?
B
D
B
B
B
Like
I
personally
think
we're
moving
in
the
in
the
right
direction
with
how
we
are,
we
are
like
improving
our
process
and
how
we're
spending
more
time
like
planning
our
activities
and
trying
to
break
them
down,
but
I
I
think.
The
summary
is
that
I
think
there
is
still
like
a
little
bit
to
go
in
order
to
arrive
at
a
system
that
allows
us
to.
You
know:
deliver
individual
chunks
right
and
also
get
the
satisfaction
of
like
finishing
something,
and
rather
than
having
to
deal
with
sort
of
creep,
scope,
creep,
right
and
I.
B
Think
that's
that's
kind
of
mostly
what
I
want
to
say
and
I
think
that's
that's
interesting
in
its
own
right,
because
I
think
many
many
other
folks
as
far
as
I
know,
are
not
utilizing
like
epochs.
In
that
way,
there
are
other
ways
of
doing
it,
but
I
think
that
that
can
be
quite
powerful
and
frankly,
I've
enjoyed
having
also
sort
of
engineering
partners
in
the
way
to
handle
these
issues
on
a
more
technical
level,
because
I
I
think
my
understanding
is
very
limited
on
what
is
actually
needed.
D
Yeah
I
mean
that
I
throw
around
some
IDs.
There
would
be
left
field
some
of
them,
but
you
know
that
Sergio
sits
kind
of
to
the
side
of
the
rails
app
and
that
we
may
get
some
benefit
by
putting
it
deeper
into
the
stack
yeah
like
a
sort
of
model
they
or
even
at
the
connector
or
the
adapter
layer.
So
you
know
something
like
that,
would
possibly
give
us
and
then
there's
the
other
extreme
as
well
the
extracting
the
service
out
into
a
separate
jam
or
something
but
yeah.
A
D
A
Well,
I
very
much
like
to
talk
further
about
the
more
longer-term
architectural
things
that
we
probably
need
to
be
taking
a
look
at,
but
I
am
a
way
that
we're
at
the
half-hour
now
so
I
think
I
will
put
in
some
more
time
to
have
an
actual
like
video
chat
about
some
of
the
architectural
things,
I'll
figure
out
how
to
do
that
across
the
the
time
zones.
Maybe
we
have
the
conversation
twice
in
different
forms,
but
I
think
it's
a
good
for
us
to
be
talking
about
those
things
now
to
try
and
figure
out.
A
When
is
the
right
time
to
do
those?
When
is
there
a
time
to
make
the
changes
and
then,
secondly,
how
we
will
actually
go
about
doing
that
and
so
I'll
put
in
some
time
where
we
can
have
some
of
those
discussions
and
get
started
there,
but
I
think
we
also
need
to
just
look
at
the
finish
looking
at
the
one
that
Douglas
has
proposed
and
seeing
where
that
takes
us
and
I
think
that
needs
to
start
driving
the
conversation
going
forward.
A
So
I'll
put
in
some
time
for
that
yeah
since
it's
the
half
hour,
I
want
to
wrap
up
now.
So
thank
you
very
much
everyone
for
joining
and,
if
anyone's
able
to
join
the
call
later,
obviously
yes,
you
might
be
but
late
for
you,
but
looking
forward
to
seeing
everyone
else
if
you
can
join
the
call
Pacific
or
later
on.
So
thanks
very
much
for
your
time
and
I
hope
you
will
have
a
great
day.
Thank
you.
Bye,
bye,
see
ya.