►
From YouTube: 2020 01 27 Database Team meeting
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
So
we
have
a
team
meeting
cut
down
this
dock.
So
typically
the
first
section
of
the
updates
that
are
don't
really
need
to
talk
about
them,
just
updates
that
people
can
read
about
offline
and
then
bring
in
work
items.
Anything
that's
important
to
discuss
for
the
week
like
blockers.
Anything
folks
are
working
on
what
the
memory
team
has
chosen
to
do.
A
Is
we
have
a
memory
team
by
member
a
memory
board
by
team
member
where
everyone
can
walk
through
the
individual
items
that
they're
working
on
and
especially
for
the
milestone,
talk
about
what
they're
working
on?
If
they
need
me
help
or
any
click
discussions,
and
we
can
take
em
asynchronously
right,
because
we
only
have
a
half
an
hour
and
you
don't
want
a
rathole
on
anything
for
too
long.
A
So
that's
what
we
do
on
the
memory
team
and
then
we
have
any
async
follow-up
items
that
we
review
from
the
previous
week
and
we
set
up
for
the
next
week.
So
that's
the
structure,
the
memory
team
uses
yeah,
but
that
being
said,
I'm
happy
to
use
whatever
structure
we
want
for
this
team
and
we,
you
know,
we
don't
have
to
be
perfect.
First
time
we
can
iterate
on
as
we
go
through
these
weekly
meetings,
so
any
thoughts
on
how
we
want
to
do
this
or
anything.
That's
worked
well
with
other
teams
and
companies.
B
B
A
Start
so
we
have
the
database
team
board,
which
is
linked
in
the
doc
here.
This
is
by
my
stone.
So
typically,
we
try
to
organize
top-down
priority
order
right
and
a
couple
weeks
before
the
start
of
the
next
milestone.
I
will
put
together
the
planning
issue
for
the
next
milestone.
So
we
already
have
a
database
planning
issue.
It's
just
at
the
template
level.
Right
now,
I
hadn't
put
any
materials
into
it.
A
A
B
A
B
C
A
A
lot
of
times
when
issues
come
through,
they
will
just
have
the
database
level
database
label.
So
that's
what
I
do
when
I'm
premier
the
entire
backlog
to
see,
if
there's
any
better,
just
database
label
that
don't
have
our
team
label
on
them
so
that
they
will
I
will
add
them
if
it
makes
sense,
so
they
do
show
up
on
the
board.
A
A
Pat,
you
may
not
have
access
to
periscope
yet,
but
it's
pretty
easy,
probably
just
have
to
open
an
access
request
for
it.
If,
if
you
can't
see
that
link,
ok,
I'm,
not
concerned
I,
think
I've
said
this
to
both
you
about
the
M,
our
throughput
for
this
team.
Being
that
you
are
everything
database
related
is
gonna,
go
through
this
team,
so
I
think
velocity
and
throughput
is
going
to
be
just
fine,
looks
like
something's
broken.
This
is
probably
due
to
the
way
they
import
data
from
production.
A
Well,
that's
another
toughie!
You
can
come
back
to
so
Pat
I'll
get
on
here.
Everything
here
is
reflective
of
andreas
right
now,
so
the
number
of
merger
cut
everything
saundra
assume
there'll,
be
another
color
for
you,
Pat
one
request:
I,
don't
know
that!
There's
an
issue
out
there-
and
this
is
not
how
we
organize
as
a
team
but
periscope.
A
It's
it's
a
very
defined
way
that
they
bring
the
data
over
and
whenever
there's
a
schema
change
that
whenever
there's
ways
that
schema
changes
can
break
the
periscope
imports.
So
there's
been
an
ongoing
ask
from
the
data
team
to
proactively
notify
them
when
schema
changes,
happen
and
I.
Don't
know
that
there's
a
way
to
do
that
and
I.
Don't
know
that.
B
Remember
that
discussion
I
think
it
also
went
a
long
ways
having
diagrams
for
our
our
schema
rights
or
a
bit
more
documentation.
That's
also
important
for
the
analytics
import
to
know
how
the
model
looks
like
yeah
I
think
it
should
be
fairly
doable
to
have
some
kind
of
notification
service,
because
all
the
data,
all
the
schema-
changes
a
dealership
with
migrations
anyway,
so
we
should
have
a
good
grasp
of
when
they
happen.
A
A
A
B
Have
one
question:
I
was
always
a
bit
confused
by
is
actually
assignments
to
two
issues:
I
think
there
is
different
ways
we
do
that
across
the
company
and
what
assignment
means
in
the
end?
What
I
prefer
to
do
is
assigning
myself
to
two
issues
and
keeping
myself
assigned
to
the
issues
that
I'm
actively
working
on.
B
A
B
A
Agree,
every
team
is
different.
Some
teams
kind
of
follow
more
of
a
traditional
scrum
methodology
where
they
assign,
at
the
beginning
of
the
milestone,
like
everything
the
person
is
committing
to
for
the
milestone.
Others
pick
up
as
they
go
along
right.
They
just
try
to
outline
here's.
Here's
what
we
think
we're
gonna
deliver
in
this
milestone
and
even
put
the
deliverable
labels
on
it
and
leave
them
open
so
that
anybody
else
can
pick
them
up.
A
The
memory
team
gone
with
the
50/50
model,
so
at
the
beginning
of
a
milestone,
we
make
sure
about
half
of
them
issues
are
assigned,
and
then
we
leave
the
other
half
for
people
to
pick
up
yeah.
So
it's
it's
not
consistent,
so
we
can
do
what
we
want.
Okay,
I
think
the
model
that
you've
been
following
works.
Well,
so
that
people
know
this
is
the
one
that's
actually
being
worked
on
and
the
rest
are
out
there
waiting
to
be
picked
up
by
someone.
C
C
A
C
A
That's
fine
you're,
the
one
in
sadness
against
firehose,
but
there
is
a
workflow
board
that
the
memory
team
doesn't
use
at
all,
but
it
was
created
before
I
joined,
and
this
is
mostly
to
walk
through
the
labels
to
make
sure
that
issues
are
labeled
where
they
are
in
the
workflow
stage
and
you'll
learn
about
them
later.
I
think
it's
on
your
onboarding
issue.
What
each
of
these
labels
mean
and
if
it's
not
I,
continue
another
link,
that's
a
little
more
detailed.
A
C
B
Sure,
maybe
starting
from
the
bottom,
so
this
is
a
this-
is
a
follow-up
to
the
changes
we
did
in
the
last
months
on
to
the
API
projects
API-
and
this
is
halfway
done-
we
basically
waiting
for
a
deployer
before
we
can
bat
it
at
this.
I
think
it's
on
staging
already,
and
the
goal
is
that
we
so
once
this
has
been
deployed,
we
can
we
can
remove
some
of
the
indexes
that
we
created
in
the
last
milestone,
so
they
were.
They
are
not
needed
anymore.
If.
C
B
B
They
were
sort
of
specialized
to
a
Nita.
We
don't
have
any
more
after
this
change.
We
changed
a
bit
of
behavior
there,
but
that
was
very
much
in
the
details
like
it's
barely
barely
noticeable,
but
in
this
case
we
don't
need
those
indexes
anymore.
I
created
them
in
the
last
milestone,
because
this
special
behavior
sort
of
needed
these
extra
indexes,
and
now
we
don't
need
any
more
hopefully,
and
the
reason
why
we
removed
them
is
just
see
the
overhead,
so
we
don't
have
to
maintain
them.
Okay,.
B
The
the
era
500
is
something
I
picked
up
coming
out
of
the
a
projects
API
API
work.
We
have
a
data
inconsistency
that
is
very
rare,
but
we
have
it
on
good
luck.
There
are
three
projects
affected
by
that,
and
that
means
the
endpoint,
basically
always
when
there's
500,
if
you
sort
by
last
activity
at
I,
think
so
there
were
three
projects
that
somehow,
if
there's
an
inconsistency,
we're
not
even
sure
why,
but
we
don't
have
the
validation
in
place.
B
B
Standard
schema
be
so
abstracting
away
from
the
specifics
of
the
database
system,
and
we
want
to
use
more
advanced
features
and
posters
like
petitioning,
but
also
triggers
tables
constraints,
and
all
that
you
can't
use
that
with
standard
rails
and
the
idea
there
is
that
we
use
we
move
over
to
structure
sequel,
which
is
sort
of
a
plain
sequel,
schema,
DOM
and
I've
I've
prepared
this
some
changes
for
CI
and
necessary,
and
it's
sort
of
ready,
I'm
polishing
this
up
today
and
I.
B
Do
expect
a
bit
of
discussion
for
that,
because
it's
a
fairly
like
substantial
change
for
our
development
workflow,
because
people
have
not
to
work
with
sequel
schema
instead
of
what
they
are
used
to
with
Ruby
schema,
so
I'll
polish,
it
up.
I'll
put
it
to
the
back
end
call
tomorrow,
I,
think,
and
also
on
slack
and
get
the
discussion
going.
A
B
This
is
totally
unrelated
to
production.
Okay.
This
is
all
me
the
way
we
track
the
latest
schema
in
the
codebase
and
it
is
only
being
used
for
development
purposes.
So
when
you
set
up
your
local
environment,
you're,
not
running
all
the
migrations,
but
your
instead,
you
just
load
the
latest
schema
and
it's
also
being
used
for
new
installations.
So
when
you
install
goodlow
from
scratch,
we
use
this
schema
to
to
get
you
started.
This
is
actually
something
where
I'm
not
sure
about
where
we
should
probably
also
get.
B
A
B
C
Yeah
I,
don't
know
you
know,
I
think
the
first
one
is
pretty
minor
change.
Just
looking
at
these
auditing
queries
that
are
timing
out,
I
was
talking
on
drea
so
earlier
that
I
need
to
set
up
they
eat
and
eating
license.
I
guess
so.
I
can
test
this
because
it's
using
some
e
functionality,
okay
and
then
the
next
two
are
related,
which
is
the
free
text,
search
of
the
issues
and
projects
and
things
so
that
one
maybe
I'll,
have
more
questions.
We
talked
about
that
a
little
bit
earlier
this
morning,
but
just
kind
of
balance.
A
B
I
have
one
question,
but
I'm
not
really
prepared
for
the
background,
but
I
still
still
going
to
ask.
We
just
discussed
it
earlier
today,
so
I
have
coming
from
the
infrastructure
side.
I
still
have
quite
a
bit
of
access
to
the
database
specifically
and,
on
the
other
hand,
I
realized
that
not
all
back
and
engineers
have
access
to
the
database.
B
A
B
B
A
A
Database
training-
yes,
sorry,
hymns
cross-posting
in
my
brain
with
the
Ruby
on
Rails
training
latest
with
him,
if
I'm
still
targeting
April.
Well,
we
have
the
budget
for
it.
Actually,
some
of
the
budget,
we're
gonna
steal
for
machinery
else
can
be
budgeted
three
times
as
much
as
we
need
it
for
a
database
because
it
was
based
on
the
first
vendors
estimate
and
this.
This
company
that
we're
gonna
go
forward
with
is
a
lot
cheaper.
B
A
They
have
about
a
ten
hour
window
where
we
get
it
for
the
base
price.
If
we
need
to
extend
outside
those
windows
will
charge
us
a
little
bit
more,
but
we're
still
within
budget
two
sessions
a
day
same
topic,
it'll
be
for
a
week
straight
so
they'll
do
it
every
day,
five
days
in
a
row,
the
number
of
attendees,
so
anybody
can
join
it's
more
of
a
classroom
setting
where
they're
sharing
information
with
us.
They
were
still
working
on
the
active
record
portion
of
it.
A
A
We
were
just
finalizing
the
details
and
I
think
it
was
a
week
of
it
was
the
middle
of
April
so
give
us
a
couple
weeks
after
contribute
and
April
13th
I
believe
was
the
week.
So
I
could
just
about
three
weeks
after
contribute,
so
that
people
can
come
off
vacation
stuff.
We're
not
jumping
right
back.
In
the
training
yeah.
A
A
A
I
just
know
that
they
couldn't
do
like
the
last
two
weeks
of
April
and
we
didn't
want
to
try
and
cram
it
into
March,
because
the
Ruby
on
Rails
training
will
go
from
February
24th
right
up
until
the
week
before
contribute
and
that's
a
it's
a
different
layout,
but
I
didn't
want
to
cram
too
much
in
there.
So
still
moving
forward
still
finalizing
a
few
details,
but
I
will
make
sure
to
keep
that
issue
up
to
date
with
everything
that
we
talked
about.
B
A
We
can't
record
any
of
that.
Training
goes
against
their
policy,
but
they
will
share
I,
think
they
will
share
all
the
slides
and
we
can
share
that
internally
and
it
may
be
a
book
that
they
give
us
too
so
we'll
have
some
materials
to
share,
but
I
gotta
jump
off
I
have
another
meeting
to
join.
So
thanks.
Everybody
right
thank.