►
From YouTube: 2020 02 18 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
All
right,
let's
see
so
for
today,
just
a
few
updates
in
there.
It's
a
bunch
of
contribute
updates
that
are
coming
through
yourself.
Please
watch
the
pages
read
up
on
it:
the
sessions,
the
excursions
it
will
open
tomorrow
tomorrow
on
the
20th
and
then
I'm,
not
sure
about
signing
up
for
daily
track
sessions.
I
still
need
read
up
on
it.
So
anyway,
read
up
on
the
contribute
page
for
the
team
day.
I
guess
this
only
applies
to
you
and
Reyes.
We
need
to
figure
out
what
we're
doing.
A
There's
a
group
for
the
team
day
by
you
should
figure
it
out
by
tomorrow.
So
just
put
some
feedback
on
the
issue
there,
and
now
we
can
figure
something
out
with
folks
that
are
going
in
case.
You
missed
it,
and
this
is
the
first
time
for
Pat.
We
hit
our
iacv
target
for
January,
so
you
can
spend
a
hundred
bucks
on
a
meal.
If
you
want
to,
you
have
clients
you
want
to
take
out,
or
you
can
take
out
your
family
so
take
them
out,
enjoy
yourself
and
just
expense
it
and
there's
instructions.
A
Actually,
I
can
link
the
instructions
somewhere
on
how
to
expense
those,
so
you
have
until
the
end
of
February
to
submit
that
and
then
after
actually
starting
now
so
end
of
January
they're
gonna
switch
to
quarterly
cadence
instead
of
a
monthly
cadence
so
and
I
can
find
the
details
on
that
I.
Don't
remember
how
it's
gonna
work,
but
it
changes
any
questions
on
any
of
those.
A
B
B
A
C
C
A
C
B
A
A
So
twelve,
nine
still
focusing
on
partitioning
charting
the
output
from
the
working
group
will
help
drive
priorities.
There's
still
a
lot
of
questions
that
andres
and
I
have
asked
about
you
know
what
are
the
expectations?
What
are
the
implementation
steps?
We
should
prioritize
what
are
people
expecting
from
this
working
group,
so
that
could
shift
our
priorities
around
a
little
bit
for
12:9
and
for
partitioning
in
general.
So
that's
that's.
Why
I
called
this
out?
C
Yeah
I
would
expect
that
we
that
we
were
gonna
spend
quite
a
few
a
bit
of
time
on,
like
exploring
these
options,
discussing
them
and
sort
of
creating
more
detailed
issues
for
the
individual
work.
That's
going
to
come,
I,
don't
think
it
can
do
much
actual
work
on
partitioning
this
milestone
is
we
don't
have
things
like
structure,
sequel
and
that
that
just
makes
it
hard
to
implement
anything,
but
I
think
there
is
a
lot
of
discovery
to
do
so.
C
A
C
C
B
Yeah
I
mean
I,
guess
it
sort
of
depends
with
the
dislike
the
discovery,
that's
ongoing.
How
much
of
that
will
be
to
me
because
yeah,
a
lot
of
these
I
think
are
probably
more
minor.
Things
that
are
gonna
need
to
be
addressed
so.
C
A
And
then,
if,
if
we
run
out
of
work
in
this
column,
we
can
always
pull
in
or
chrome
that
top
50
report
if
we
need
to
or
we
can
pull
in
from
future
milestones-
and
we
only
have
twelve
ten
listed
here-
I
can
add
one
for
twelve
eleven
as
well,
but
yeah
definitely
pair
up
with
ondrea's.
I'm
the
partitioning
charting
work,
because
there's
gonna
be
a
lot.
That's
going
to
come
out
of
that,
and
let
us
know
if
there's
not
enough
work
in
there.
A
C
A
C
Wanted
to
bring
that
up
again,
because
I
think
this
is
sort
of
a
question
for
us
to
to
answer
how
we,
how
we
handle
things
like
that
in
general,
because
in
this
issue,
sort
of
all
the
things
that
our
database
related.
This
is
readily
available,
like
it's
really
just
just
about
fixing
or
adding
a
foreign
key
constraint,
and
we
have
quite
a
few
issues
like
this,
where
the
model
is
missing.
A
I
think
to
your
point:
in
the
other
conversations
we've
had
about
this,
the
back-end
team
should
own
this
eventually
and
if
we
have
documentation
or
examples
of
how
they
can
do
this,
then
we
could
certainly
point
that
to
them
in
the
cases
where
we
don't
have
examples
like.
Maybe
they
don't
have
the
expertise
to
even
do
this.
A
We
could
probably
take
on
the
first
issue
and
setting
up
the
examples
or
documentation
guidelines
on
how
to
do
it
right
or
if
it's
super
urgent
and
they
don't
have
the
bandwidth,
and
we
can
talk
about
picking
it
up,
but
ultimately,
yeah
back-end
team
should
own
examples
like
this.
So
in
this
case
for
the
foreign
key
constraints,
do
we
have
an
example?
Do
we
have
things
that
we
can
point
them
to
so
they
can
implement
themselves?
Oh,
yes,.
C
C
A
I
can
see
you
were
it's
difficult
to
understand.
If
this
one's
urgent
or
not
right,
it
would
have
solved
an
outage
shift.
This
was
in
place
ever
would
have
prevented
an
outage
if
this
was
in
place,
at
least
that's
my
understanding
prevent
an
outage.
So
while
it's
not
day-to-day
urgent,
it
could
be
urgent.
So
it's
hard
to
prioritize
this
one
I.
C
C
It's
a
it's
fairly
standard,
I
think
we
would
have
to
find,
or
we
would
have
to
agree
on
how
we
deal
with
that
issue.
So
the
inconsistencies
that
we
had
where
we
have
dangling
namespaces
without
a
parent,
you
probably
can't
just
delete
them
most
likely,
and
then
we
do
immigration.
We
we
delete
them.
We
put
a
foreign
key
in
place
with
another
migration
and
so
yeah.
It's
not
it's
not
a
lot
of
effort.
I
was
just
a
good
example
to
think.
Ask
that
question
we
have
you
have
plenty
of
these
examples
as
well.
C
A
A
B
D
Any
progress
on
it
since
then,
but
I
posted
a
PDF
of
it
onto
under
the
slack
channel,
so
I've
been
mulling,
whether
no
not
actually,
it
might
make
more
sense
to
use
an
issue
to
track
that
data
instead.
So
whenever
I
decide
to
go
and
look
for
database
related
tickets
and
anything
that
looks
interesting,
I
could
tracking
an
issue
and
then
close
it,
and
then
we
can
put
that
somewhere
where
we
can
all
see
it.
So
it's
hidden
on
the
private
with
you,
man,
yeah.
A
C
D
We've
got
like
a
support
metal
project
that
we
use
for
sort
of
improvement
of
processes
and
issues
that
arise
doing
this
at
all.
So
that's
a
possibility,
but
as
its
I
kind
of
like
the
idea
that
in
principle
somebody
else
could
come
and
do
this
role
and
they
wouldn't
need
to
know
where
it
was.
And
you.
C
D
A
D
C
A
A
B
A
C
D
So
the
content
I
the
content
I
put
in
there
I
specifically
made
all
public
compatible,
so
I,
don't
I,
don't
name
customers,
I,
use
the
self
or
Salesforce
link
which
we
use
extensively
when
we're
linking
customers
onto
tickets,
other
issues,
sorry
and
ticket
numbers.
Similarly,
it's
not
a
problem
putting
those
somewhere
bad
Nick.
So
it's
really
yeah
beyond
that,
if
they
kind
of
just
notes
about
what
was
interesting
about
their
database
setup
beyond
that,
so
there
shouldn't
be
anything.
D
C
It's
really
good
if
we
make
the
discoverable
and
public
could
be
useful
for
anybody
evaluating
Oh.
What
are
the
issues
that
you
run
into
with
it?
Lavon
Mahmoud,
yes,
burn.
Stop
I,
don't
I,
wasn't
sure
if
the
development
track
car
is
good
fit
for
it,
because
we
also
like
to
think
we
do
also
to
be
also
triage.
Those
and-
and
you
know,
though,
so
rather
may
be
actionable
things
that
we
still
have
to
deal
with
sort
of.
It
sounds
more
like
a
knowledge
base
of
things
that
you
encounter
yeah.