►
From YouTube: 2023-02-01 Foundations data sync
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
Can
let
me
just
check
it
here,
I,
don't
know
I
guess
I
had
to
leave
for
my
appointment
and
then
I
stopped
watching
it
to
see
if
it
was
done.
Refreshing
foreign.
A
A
C
C
B
A
A
B
Haven't
initially
set
to
this
month,
but
after
it
rolled
over
to
February
1st,
then
it
suddenly
was
useless
again
because
there
was
no
data
for
February.
A
B
Yeah
and
I
I
have
a
merge
request
in
review
right
now
to
add
the
fly
out
menu
options
for
the
merge
request
to
The,
Click
tracking,
so
right
now,
they're
not
fully
represented
here
that
merge
request.
One
would
be
higher.
A
Trying
to
see
if
these
are
sorted
by
size,
but
they're
not
so
it
kind
of
looks
like
in
terms
of
usage
projects
is
the
biggest
Mrs
and
groups.
This
is
groups
yeah
or
kind
of
in
the
I
guess
I
have
to
look
oh
yeah,
so
Mrs
is
bigger.
Groups
is
just
right
on
its
tail,
but
yeah
it
looks
like
projects
is
the
big
one.
C
C
B
I
think
edit
I
mean
I
suppose
this
is
how
we
want
it,
though
we
want
to
have
the
most
queer
or
the
most
clicked
on
ones
near
the
top
right
I
mean,
maybe
maybe
that
doesn't
matter,
but
it
kind
of
turned
out
mostly
that
way,
with
issues
making
the
outlier.
A
B
B
You
know
I
could
probably
throw
together
a
graph,
because
we
do
track
clicks
on
the
top
nav
for
for
the
the
equivalent
items
for
like
to-do
list
and
issues
and
and
assigned
merge,
requests
and
things
like
that,
and
we
can
see
how
they
compare
as
far
as
people
clicking
it
on
the
left,
nav
versus
on
the
top.
A
Yeah
I
wonder
too
where's
my
Snapchat
I
might
be
able
to
just
do
the
comparison
off
existing
graphs
and
just
do
it
by
hand
too
like
if,
if
we
don't
want
to
get
in
there
and
kind
of
put
them
both
in
the
same
graph,
we
could
just
kind
of
hover
on
each
or
take.
You
can
export
to
spreadsheet
and
kind
of
see
what
the
difference
is.
C
A
So,
where
are
we
at
with
we've
got
that
size
sense
up,
oops
I'll
put
the
sender
Christian.
Where
are
we
at
with
the
what's
happening
right
now
in
terms
of
this
release,.
B
Didn't
get
the
this
indentation
got
a
little
weird,
but
so
the
I
have
a
bunch
of
merge
requests
that
are
either
in
flight
or
just
recently
merged
the
the
top
nav
events
based
on
the
stuff
we
discussed
last
week,
just
auditing
those
adding
some
event
tracking,
where
it
was
previously
missing
in
a
couple
of
like
the
things
in
the
help
drop
down
and
and
the
a
few
other
things
as
well
as
like
the
new
like
the
edit
frequent
items,
you
know
buttons
and
all
that
stuff,
so
I've
added
events
to
all
of
those,
as
well
as
adding
the
common
navigation
underscore
top
property
to
all
the
events
in
the
top
nav.
A
B
So
that's
the
second
point:
I
have
that
was
a
the
that
bug
I
fixed
in
a
separate,
merge
request
that
has
already
merged,
so
that
should
make
those
event
labels
a
more
predictable
and
easier
to
query
now.
I
have
not
yet
done.
We
were
gonna
differentiate
because
they
were
all
tagged
as
frequent
items.
Even
if
you
entered
a
search
query
which
doesn't
make
a
lot
of
sense,
I
have
not
fixed
that
differentiation,
yet
that'll,
be
a
forthcoming
merge
request,
but
at
least
it's
not
it's
not
putting
private
data
into
our
license.
A
B
A
B
Yeah
I
suppose
all
I
did
was
truncate
the
end
of
it,
so
we
couldn't
just
instead
of
saying
equals.
Well
I
guess
we
probably
already
had
like
a
query
that
looked
like
label
is
like
this
and
it
had
like
it.
C
B
Okay,
so
yeah,
basically
just
using
like
and
having
the
percentage,
would
would
do
that
for
the
historical
data.
Now
we
can
use
an
is
for
data
going
forward
because
it
will
just
be
the
same
label.
B
Yeah
yeah,
so
yeah
I'm,
not
sure
if
there's
an
issue
open
for
for
that
or
if
there's
a
graph
where
you
know
where
it's
broken
and
I
could
just
hop
in
and
try
and.
A
Issue
right
here:
I'll
post
the
issue,
so
let's
wait
and
see
I,
don't
know
the
best
way
like
you're
saying
like
we
need
to
start
writing
the
specs.
So
maybe
on
an
issue
description,
we
start
listing
all
of
the
things
that
will
need
to
change
as
we
get
them
one
by
one
and
then
the
data
team
would
Implement
that,
because
they're
asking
me
what
needs
to
change
in
the
SQL
so
as
we
find
something
we
could
either
like
I,
don't
know
one-off
fix
it
in
real
time.
A
B
Okay,
yeah
I
guess
I'd
have
to
know
what's
missing
to
know
what
to
tell
them
to
add
so
I
gotta
I'll.
A
A
B
And
that's
that's
the
goal
you
were
kind
of
talking
about
modifying
the
queries
to
capture
Legacy
data
that
we
were
missing,
which
is
maybe
a
separate
topic
almost
as
far
as
like
reaching
back.
B
Yeah
no
I
I
agree.
So
if
we,
if
we
fix
that
one
where
the
the
label
was,
you
know
not
being
queried
correctly,
that
that
will
fix
our
historical
graphs
but
as
far
as
like,
like
I
just
added
events
to
a
couple
of
you
know
like
things
in
the
help
drop
down
that
didn't
have
events
before
there's
no
way
to
add
that,
to
our
historical
query,.
B
And
so
what
we'll
do
with
that
is
basically,
if
we're
just
trying
to
get
a
total
number
of
number
of
clicks
on
the
top
nav
bar
is
just
have
that
whole
complicated
queer.
We
have
for
our
historical
data
and
then
just
say,
or
property
equals
navigation
underscore
top,
and
that
will
capture
everything
going
forward.
B
I
I
was
hoping
that
that
would
be
merged
today,
so
that
it
would
be
cleanly
like
on
the
first
of
February,
but
but
yeah
in
any
case,
yeah.
That
should
be
simple,
going
forward.
C
A
I
was
gonna,
so
the
next
one
on
metadata
for
tracking
events
to
segregate
users.
This
was
a
topic
I
wanted
to
ask
like.
Maybe
we
should
just
drop
cohorts
in
any
of
the
user
tracking
stuff
other
than
whether
they're
got
the
toggle
on
or
not
okay,
because
I
think
we're
running
out
of
time.
B
Well,
we
had
an
issue.
We
wanted
to
track,
specifically
gitlab.org
users
as
a
specific
cohort
and
I
was
just
talking
with
Sam
in
my
previous
meeting
about
how
to
do
that.
Now
that
we
have
the
ability
to
enable
feature
Flags
by
group.
A
B
A
B
Could
we
could
decide
if,
if
the
user
is
part
of
gitlab
org
or
not
and
track
that
separately
for
each
event,.
A
I
would
prioritize
above
that,
but
if
it's
like
easy
to
do,
I
think
we
should
just
go
for
it
any
of
those
consistent
things
we
can
just
add
in
that
are
kind
of
simple
across
every
event,
when
I
was
doing
this
on
like
a
different
product
in
the
past,
I
worked
with
seisance
and,
like
our
front-end
team
made
these
things
called
data
packs
like
three
variables
in
a
almost
like
an
include
that
just
got
like
it
was
like
a
backpack
that
got
put
on
every
event.
C
A
So
they
let's
say
you
wanted
to
change
the
feature
flag,
stuff
or
the
maybe
like
the
high
level
or
like
the
version
of
the
navigation
you'd,
be
doing
it
just
in
one
spot
and
then
every
event
would
just
pull
in
that
yeah.
B
We
have
something
like
that
in
the
the
code
that
kind
of
sets
up
snow
plow
in
the
front
end.
It
automatically
adds
a
few
things
that
are
always
added.
Mostly
it's
like
things
about
like
the
the
browser,
and
you
know
the
size
of
the
window
and
things
like
that,
but
it
also
well,
for
instance,
now
I've
I've
set
it
up
to
add
the
state
of
the
feature
flag,
not
the
feature
flag,
the,
whether
the
new
nav
is
enabled
or.
A
B
A
B
A
B
Yeah
one
of
the
other
things
I,
you
have,
we
had
an
issue
in
the
issue
where
we
were
talking
about
tracking
the
the
state
of
the
the
new
nav
toggle.
B
We
you
also
wanted
to
track
whether
a
user
had
ever
had
the
toggle
enabled
like
the
historical
data
about
that.
Is
that
something
we
still
want
to
do?
Let's.
B
Closing
that
issue
we
could
like
we,
we
did
leave
the
the
preference
as
like
a
was
the
word
ternary
state.
It
was
like
a
three-state,
it's
either
true
false
or
null,
so
we
can
track
whether
the
user
has
expressed
a
preference
yeah,
for
instance
in
the
future.
If
we
enable
it
by
default
for
a
certain
group
of
people,
we
will
be
able
to
determine
if
they
have
toggled
it
off
or
on
manually
versus
just
had
it
on
by
by
the
default.
B
If
that's
something
that's
useful
to
track,
I
can
I
can
find
a
way
to
add
that
to
the
metadata
too,
but.
A
A
B
Let
me
pull
up
the
Epic
I.
Have
it
in
one
of
these
I
just
shared
screened,
oh.
B
B
C
A
B
That's
the
thing
we
couldn't
necessarily
do
it.
We
could
do
an
approximation
of
it
like
if
we
could
tell
that
the
navigation
is
on
by
default
for
them,
but
they
have
turned
it
off.
We
know
that
at
one
point
it
was
probably
on
and
we
could
then
you
know
treat
it
as
such,
so
it's
kind
of
like
making
inferences
based
on
the
the
current
state
of
things
right.
B
Important
not
but
otherwise
yeah
if
we
wanted
to
actually
tell
for
certain
whether
they
had
it
on
or
off
in
the
past
and
they're,
contrary
to
what
the
current
state
is,
we
would
have
to
save
it
in
the
database.
Somehow.
A
Should
we
have
like
an
like
just
a
graph
from
the
back
end?
That
is
those
three
states
like
a
query
against
current
users
that
have
it
on
by
what
was
it
like
on
by
default
off
or.
B
C
B
B
Sure
there
is
some
way
to
do
that.
I.
Imagine
we
track
certain
back-end
metrics
over
time.
Maybe,
like
you
know,
I,
don't
know
trying
to
think
of
an
example
but
I'm
sure
we
do
this
somewhere.
I
should
probably
just
contact
the
the
product,
intelligence
team
or
the
data
team
or
something
and
see
where
we've
done
something
like
that
in
the
past
and
use
that
as
a
model
I.
C
Was
I'm
wondering
if
well
how
we
then
would
detect
or
determine
if
what
a
user's
default
is
because
currently
like,
we
have
a
table
with
rows
of
users
or
user
preferences,
and
that
is
true,
false
or
nil.
But
if
we
have
some
code
that
says,
if
member
is
part
of
that,
50
rolled
out
feature
flag,
that
it's
not
something
that
is
super
easily
variable
from
the
database.
At
the
same
time.
So.
B
Yeah
we
will
have
to
find
a
way
to
kind
of
like
I,
don't
know
yeah,
we
would
have
to
be
able
to
query
the
feature
flag
status
in
a
way
that
could
be
kind
of
combined
with
that
and
doable.
That
would
actually
be
because,
like
we
were
going
to
use,
we
haven't
even
really
done
this.
Where,
where
we
were
going
to
one
option
for
setting
the
default
state
was
to
use
a
featured
flag
right,
we
I
guess
we
I
don't
know.
A
I
think
that
when
we
move
from
the
git
lab
cohort
into
like
production,
maybe
defaulted
to
off
and
then
defaulted
to
on,
I,
don't
know
that
we
would
need
to
track
to
that
level.
I
think
we
would
just
bring
gitlab,
along
with
us
to
production,
right
and
kind
of
lose
the
other
feature
flag,
the
one
that
just
I'd
get
lab
in
it,
but
I
don't
know.
B
A
B
B
So
now
I
guess
I
saw
that
and
I
thought
that
this
was
so
I
wasn't
sure
if
this
was
like
gitlab.org
users
or.
A
A
I
have
to
jump
to
my
one-on-one
here.
Okay,
is
there
any
other
I'm
just
trying
to
see
if
we
jump
through
anything.
B
I
was
going
to
ask
really
quickly
I
know.
There's
the
navigation
weekly
sync
in
about
an
hour.
Do
you
want
me
to
be
present
in
that
meeting?
Otherwise,
I
have
a
lunch.
Engagement
I
might
go
to
early.