►
From YouTube: Backdrop Weekly - Nov 19th 2020
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).
B
A
We
are
live.
Everybody
today
is
thursday
november
19th.
A
This
is
the
weekly
developer
meeting.
We
skipped
the
design
meeting
today
because
everybody
who
is
here
was
really
busy,
but
we
have.
We
had
a
new
release
this
week,
so
we're
gonna
go
through
the
dev
meeting
anyway,
before
we
get
started.
Let's
have
everybody
here,
go
around
and
say
what
your
name
is
and
where
you're
from
and
if
you
want
to
share
something
fun
with
us
in
30
seconds
or
less
go
ahead
and
do
that
phil.
Let's
start
with
you,.
C
Hi
phil
ward
out
of
wichita
kansas,
basically
just
kind
of
here
to
provide
feedback
where
I
can
kind
of
help
with
some
testing
where
I
can
and
yeah
see
what
I
can
do
to
kind
of
help
out.
Jen.
A
I'm
jen
lampton,
I'm
calling
from
oakland
california,
where
it
is
beautiful
and
sunny
today,
which
is
very
exciting
because
it
rained
this
week,
but
we
started
winter.
That's
it
for
me
time.
B
Sorry
I
just
opened
up
the
the
live
link
as
I
was
talking
and
it's
got
a
20-second
delay
and
that
very
much
confused
me
anyways,
I'm
here
from
deerwood
minnesota.
My
the
fun
thing
I
just
mentioned
before
we
came
on
the
air
I
have
been.
I
have
bought
my
first
pre-owned
non-mac
computer
in
my
life
and
have
been
in
trying
to
configure
linux,
so
I
could
become
earn
some
geek
cred.
I
guess
anyways.
It
is
super
fast,
that's
what
I'm
liking
about
it
so
far.
B
So
that's
it
and
I
don't
know
if
w
panda
wants
that
peter
wants
to
introduce
himself
or
not.
If
he's
able
to
nope,
it
looks
like
he
does.
D
Let's
say
hi
so
peter
and
sarah
here
from
australia
just
lurking
in
the
background
today,
but
see
if
I
can
give
her
an
update
on
my
advocate
issue
later
great.
A
All
right
so
this
week
we
have
two
new
contributed
projects:
state
override
and
markdown
editor
for
bu
editor.
Both
came
out
this
week,
so
that's
pretty
cool.
I've
been
thinking
about
putting
markdown
editor
on
one
of
my
sites,
so
I
might
give
that
a
try
this
week.
A
B
I
think
we
should
acknowledge
the
work
being
done
on
organic
groups,
because
that's
exciting,
oh
yeah,
and
a
chance
if
people
want
to
help.
I
know
there
have
been
people
waiting
for
that
and,
if
anybody's
really
interested
in
organic
groups
and
wants
to
help
test
that,
I
think
it
would
be
really
helpful.
A
So
yeah
I
looked
into
that.
I
don't
know
a
month
ago,
maybe-
and
I
was
like
oh
man-
this
looks
like
it's
going
to
be
a
lot
of
work.
I
guess
I'll
just
put
it
on
my
calendar
for
like
december
and
then
two
days
ago
or
whatever
I
got
the
email
that
was
like
this
project
doesn't
move
to
contribute.
I
was
like
what
I
hadn't
paid
attention
for
a
month
and
then
it
just
appeared
right.
That
was
really
exciting.
B
C
I
know
tim's
kind
of
been
on
on
this
topic
a
little
bit.
I
don't
know
if
you
have
gin
the
kind
of
the
idea
of
the
telemetry,
in
the
backdrop
upgrade
status
module
honestly,
I
don't
know
if
here
is
a
good
place
to
talk
about
it.
I
kind
of
feel
like
this
is
kind
of
a
core
dev
decision
that
needs
to
be
made
on
doing
that
as
opposed
to
putting
it.
You
know
out
in
the
the
outreach
I
mean
it
kind
of
ties
into
both.
A
B
B
And
number
two
just
for
phil's
sake
and
anybody
else
that's
listening.
We
have
two
sort
of
official
initiatives
right
now
which
are
sort
of
issues
or
larger
issues
that
we're
trying
to
focus
on,
and
one
of
them
is
telemetry.
So
that's
automatically
on
this
agenda
every
week
to
talk
about
it.
You
know
some
weeks.
It's
there's
no
real
update,
so
we
don't
talk
much
about
it,
but
that
is
something
that
we
have
been
talking
about
on
this
call
already
and
we'll
get
to
it
on
the
agenda.
A
A
Okay,
let's
see
so
moving
into
core
this
week.
Yesterday
we
released
backdrop
one
17-3
that
was
a
security
release
co-released
with
drupal.
We
knew
it
was
coming
for
a
couple
weeks.
We
had
a
patch
in
the
security
queue
we
recently
set
up.
This
is
tangential,
but
hopefully
you
guys
will
see
where
I'm
going
with
this
recently
set
up.
Qa
sandboxes
on
the
public
issue,
queue
for
testing
sites
using
tugboat,
and
it's
going
really
well.
A
As
far
as
I
can
hear
that,
there's
also
a
attempt
to
try
and
switch
our
automated
testing
over
from
using
zen
ci,
which
is
something
that
gore
built
specifically
for
us,
and
it's
super
fast
and
really
great
to
maybe
one
of
these
other
standard
tools,
but
we've
got
some
concerns
around
how
fast
something
like
that
would
be.
We
because
we
know
that
that's
nci
is
super
fast,
but
I
was
thinking
as
we
were
working
on
the
security
issue
for
the
last
few
weeks.
A
It
would
be
really
great
to
use
the
security
queue
as
a
place
to
test
whatever
it
is
we're
working
on
for
automated
testing,
because
number
one
things
happen
over
there.
A
lot
more
slowly
like
most
of
the
activity,
is
in
the
public
queue
and
there's
only
a
few
issues
in
the
private
queue,
and
so
I
think
if
it
were
slower,
that
would
be
fine.
We
usually
visit
those
issues
less
quickly
anyway,
and
it
we
wouldn't
need
to
replace
what
we
have
with
it
either.
We
could
try
it
there
in
parallel.
A
So
anyway,
that
was
just
something
that
came
up
as
we
were
working
on
security
release.
I
was
like
oh,
this
could
be
a
good
place
to
test
alternative
test
environments
for
backdrop.
We
can
do
it
safely.
A
Okay,
included
in
1173
is
the
same
security
fix
that
was
in
drupal
7,
plus
we
included
one
fix
that
was
supposed
to
fix
a
regression
with
a
css
change
that
went
into
117
2.,
so
I
don't
think
the
fix
we
committed
and
merged
entirely
fixed.
The
problem,
there's
a
follow-up
issue,
and
I
have
a
link
to
it
here
in
the
1174
milestone.
It's
issue
number
4766,
but
this
is
a
prime
example
of
why
we
shouldn't
change
css
in
between
major
version
releases.
A
We
can
run
into
this
a
couple
of
times
this
one.
I
don't
think
is
that
bad.
It
will
only
affect
the
admin
side
of
things,
and
so,
unless
you
have
an
admin
theme
that
is
an
extension
of
seven
or
if
you're,
you
know,
you'll
see
it
if
you're
using
seven,
but
for
the
most
part
it
won't
affect
front
end
of
sites,
but
anyway,
I
thought
it
was
interesting
that
we
were
going
over.
How
do
we
handle
not
breaking
css
in
core?
A
At
the
same
time
as
we
wrote
css,
which
was
like
yeah,
we
never
really
know
until
we
release
what's
going
to
happen
there,
just
because
the
number
of
eyes
are
on
it,
so
that
was
all
for
117.3
I'm
going
to
check.
So
I
haven't
checked
before
this
meeting
on
any
of
these
other
issues
for
117.4,
but
I
expect
that
most
of
them
are
in
comparable
states.
They
were
last
week
so
this
first
one
is
issue
number
4745,
which
is
also
regression
from
117
to
for
civvy
crm
integration.
A
It
looks
like
we
have
a
pull
request
here
and
it's
labeled
as
needs
work,
but
this
is
something
that
happened
from
us,
including
mysql8
support.
So
I
think
that
you
know
we're
going
to
need
to
make
sure
civvi,
serum
and
mysql8
work
together
as
well.
So
I
I
think
this
is
a
good
thing
for
us
to
run
into
and
a
great
thing
for
us
to
try
and
fix.
A
Next
one
is
missing:
hd
access
rules
for
php7,
and
I
think
we've
finally
got
a
consensus
on
this
last
time
in
our
weekly
meeting,
someone
asked
well
couldn't
we
just
like
test
for
when
this
problem
happened
and
nate
said
yes
and
my
mind
was
blown
and
so
there's
a
new
pull
request
there.
That
now
will
log
an
error
if
your
site
runs
into
that
particular
problem
rather
than
sailing
failing
silently.
A
I
think
there
are
some
instances
where
we
like.
If
the
submit
button
is
what's
removed
from
the
form
it
might
still
fail,
but
I
think
we
have
at
least
some
good
tools
in
there
to
catch
it.
The
number
of
use
cases
that
we're
running
into
where
people
are
actually
going
to
get
hurt
by
this
are
getting
smaller
and
smaller
and
smaller.
So
I
think
we're
definitely
on
the
right
track
here.
A
This
one
looks
like
it
still
needs
code
review,
setting
reasonable
value
for
maximum
input
variables.
I
think
this
one-
oh
this
one
I
just
talked
about
this
is
still
worked
as
marked
as
needs
work,
so
I
got
two
issues:
confused
the
max
input
virus
one
and
the
missing
each
texas
rules
for
php
seven
are
related
because
they
both
involve
hd
access
rules,
but
the
missing
ones
for
php
seven
is
the
one
that's
rtbc
and
the
maximum
input
farce
is
the
one
that
needs
work,
but
I
think
we're
honing
in
on
a
conclusion.
A
Next
one
remove
block
title
for
search
box.
This
one's
been
around.
I
think,
since
we
made
the
last
change
to
search
box
issue
number
34.76,
it
looks
like
it's
also
marked
needs
work,
I'm
not
sure
what
work
it
needs,
but
I
think
that
one's
probably
close
fixing
views
or
behavior.
This
is
a
long-standing
bug
in
views.
C
Was
trying
to
kind
of
test
that
one
the
other
day?
I
think
my
logic
is
super
fuzzy.
I
don't
know
if
maybe
out
there
in
the
the
original
post,
that
maybe
we
can
put
an
example
of
what
is
known
to
to
not
be
working
versus
what
should
be
working.
That
way,
I
can
kind
of
reverse
engineer
to
help
test
that
but
yeah
I
was
kind
of
playing
around
and
out
of
the
patch
I'm
like.
I
really
don't
see
much
of
a
difference
here,
I'm
not
sure.
What's
going
on
so
I.
C
Is
bad
but
I'll
be
honest
getting
into
some
of
those
some
of
those
different
logics
with
those
filters
always
I
just
would
have
to
play
with
it
until
I
got
it
right,
so
I
think
some
of
it's
just
the
way
my
brain
is
trying
to
figure
it
out,
just
isn't
working
right.
So
maybe,
if
I've
got
more
of
a
real
world,
I
can
help
you
guys
test
on
that.
One.
A
Yeah,
so
in
the
top
issue,
there's
a
set
of
steps
to
reproduce,
but
it
might
be
good
if
we
could
like
attach
an
actual
views,
export
where
it'll
show
you
that
it's
broken,
because
I
know
sometimes
you
know
that
that
can
be
a
little
fuzzy.
I
wish
for
that,
pretty
commonly
I'm
like.
Oh,
I
could
just
build
this
view
and
export
it,
and
that
might
help
people
test
before
and
after
the.
B
Patch
phil
a
great
thing
to
do
a
great
contribution
to
an
issue
like
that
is,
if
you
do
in
that
situation,
if
you
try
it
and
you're
not
able
to
reproduce
it
say
that
and
say
you
know,
ask
ask
for
better
steps
to
reproduce
it.
I
do
that
fairly
often,
it's
like
I
want
to
test
this,
but
I'm
not
quite
sure
how
and
people
are
usually
generally
pretty
happy
to
you
know
to
help
me
with
that
right.
A
Okay,
next
issue
is
removing
blacklist
and
whitelist
from
core.
This
issue
got
fixed
since
the
last
time
we
talked
about
it
and
is
now
back
in
needs
review
status.
I
have
a
feeling
the
change
we
made
this
week
might
make
that
not
apply
anymore,
and
so
it
might
need
to
be
rebased,
but
we
can
work
on
that
and
then
similarly,
we
wanted
to
remove
master
slave
terminology
from
core
this
one's
currently
marked
as
rework.
A
I
also
expect
that
the
mysql8
support
might
make
the
pull
request
there
not
work
correctly
either,
so
both
of
those
are
probably
going
to
need
to
be
looked
at
again.
A
Next
issue
is
number
3213..
This
is
adding
automated
code
checks
in
core.
I
haven't
been
following
along
with
this,
one
looks
like
there
haven't
been
any
updates
since
august
27th,
so
I
don't
know
where
that
one's
standing.
A
All
right
for
ongoing
issues
with
core
there's
a
couple
of
issues
that
are
meta
issues
that
will
sort
of
go
on
forever,
that
have
a
bunch
of
changes.
One
of
them
is
including
crossboards
from
drupal
7..
A
So
every
time
a
drupal
7
module
that
we've
put
in
core
has
releases
or
drupal
7
core,
for
example,
this
week
had
a
release
we
like
to
have
an
issue
of
all
of
those
changes
that
were
included
in
drupal
and
make
sure
they're
also
included
in
backdrop
if
you
are
bored
one
day
and
are
looking
for
some
work
to
do.
A
Those
issues
of
porting
fixes
that
are
already
in
drupal
into
backdrop
are
great
for
failing
time.
A
A
A
If
you
were
to
visit
that
one,
you
could
see
in
the
sidebar,
it's
slotted
into
a
project
for
drupal
7
crossports,
and
you
can
find
a
bunch
of
stuff
over
there
that
we
would
like
to
add
in
if
anyone's
interested
in
working
on
those.
And
then
we
have
a
couple
of
meta
issues
for
user
experience,
improvements.
There's
one
for
flexible
templates!
That's
here
on
this
agenda.
We
also
have
one
for
ck
editor.
A
So
there's
just
a
couple
of
there's
one
for
a
layout
system,
there's
a
couple
of
collections
of
the
issues
that
could
be
fun
to
work
through.
Also,
if
you
find
that
sort
of
thing,
let's
see
so
our
next
release
is
going
to
be
backdrop
117.4.
We
don't
have
a
date
scheduled
for
that
yet
because
we
don't
have
any
stuff
in
it
or
stuff
urgent
stuff
done
in
it.
A
But
yes,
always
fixing
bugs.
If
you
find
bugs
that
can
go
into
and
it
gets
fixed,
it
can
go
into
any
release
all
right.
So
for
one
18,
which
has
feature
freeze
on
january
1st,
we
only
have
a
handful
of
issues
assigned.
B
A
A
Okay,
so
I'm
looking
at
the
118
milestone
instead
of
the
agenda,
it
looks
like
we
have
exposed
file,
name
filter
on
media
library.
That
would
be
fantastic.
A
We
have
my
that
one
is
currently
marked
help
wanted,
so
I
think
there's
some
javascript
trickery
that
we're
doing
with
the
exposed
filter
form
in
a
modal
that
we
need
some
help
with.
So
if
anyone
is
a
javascript
expert,
that
would
be
a
good
place
to
jump
in.
B
A
A
A
And
then
we
have
well,
let's
just
a
web
piece
support,
something
that's
been
underway
for
a
while.
This
one
doesn't
happen.
Oh
wait,
it
does
have
an
indigo
xlr.
A
Okay,
ambiozella
is
advocating
for
this.
One
webp
is
an
extension
that'll
help
you
with
image
generation.
So
right
now,
almost
all
backdrop
sites
use
gd,
which
is
a
built-in
image
handling
library
with
php
there
is
a
contrib
module
called
image
magic.
That's
a
lot
of
people
use
that
webp
is
an
extension
that
will
allow
gd
to
generate
images
in
next-gen
formats,
and
so
this
is
one
of
those
things
that
shows
up
on
your
report
of
problems
with
your
website.
A
When
you
look
at
it
in
a
google
search
console,
I
remember
what
it's
called
one
of
those
things
that
analyzes
why
your
site
isn't
performing
well
in
search
results
and
the
major
issue
there
is
with
how
fast
it
loads.
So
if
we
can
get
webs
to
p
support
and
core,
there
are
two
benefits
there.
A
One
of
them
is
that
the
pages
load
faster,
so
that'll
be
good,
no
matter
what
and
then
the
other
one
is
that
that
has
a
triggering
effect
that
makes
will
make
backdrops
rank
more
highly
in
search
engine
listings
because
of
the
pages
loading
faster.
So
I'm
really
excited
about
this.
One.
C
Can
I
bring
up
a
thought
on
that?
This
is
something
I
think
right
now,
just
getting
it
to
where
you
can
upload
the
webp
without
errors.
I
think
that's.
You
know
the
first
step
personally,
I
think
long
term.
What
we
need
to
do
with
that
is
try
and
set
it
up
with
a
fallback
where
you
can
upload
a
webp
or
a
jpeg
that
converts
to
a
webp,
but
you
still
retain
the
original
jpeg
image
and
there's
there's
a
fallback
mechanism.
C
I
think
personally,
I
think
you
know
give
or
take
the
next
five
years
just
kind
of
covering
a
little
bit
of
this.
This
backwards
compatibility,
I
think,
would
be
good,
but
that's
that's
kind
of
one
of
those
things.
I
know
it's
going
to
be
difficult
to
try
and
implement.
I
feel
like
core:
that's
something
the
core
needs
to
kind
of
handle
in
that
regard,
but
yeah,
I
think
right
now,
just
getting
it
into
core
is
definitely
the
the
first
step
on
that.
So.
A
Yeah
I
mean
we
aren't
going
to
put
anything
in
core:
that's
not
backwards,
compatible
until
backdrop
two.
So
that's
five
years
away.
So
if
this
does
have
any
issues
with
backwards,
compatibility
it'll
either
be
disabled
by
default,
so
no
one
will
get
it
unless
they
specifically
opt
in
or
it'll
be
postponed.
If
we
can't
make
that
happen,.
C
A
Upgrade
ui-
I
haven't
done
any
work
on
that
in
the
last
few
weeks,
but
it
is
happening
in
contrib,
where
there's
going
to
be
a
module
that
user
interface
very
closely
matches
what's
happening
in
drupal
8
that'll,
just
give
you
a
tool
for
importing
a
database
into
a
website
into
itself
advanced
drupal
caching.
This
is
something
that
gets
me
really
excited.
I
don't
know
if
it
has
an
advocate,
but
joseph
said
he
was
going
to
work
on
it.
B
A
Okay,
that's
fantastic
this,
so
this
is
cash
tags,
which
is
something
that
drupal
8
has
that
backdrop
doesn't
have,
but
there's
no
reason
backdrop
couldn't
also
have
it
there's
a
drupal
7
module
that
adds
it
and
I
think
that's
where
we're,
starting
with
reporting
that
triple
seven
module
the
backdrop
and
then
seeing
what
it
would
look
like
to
integrate
it
directly
in
core,
whether
it's
going
to
be
a
module
remain
a
separate
module
or
something
that
just
gets
smooshed
into
some
other
module.
I
don't
know
if
it
has
been
decided
yet.
A
Let's
see,
add
a
link,
token
sub
token
for
user
tokens,
so
this
is
merged
into
180,
which
is
fantastic.
A
Okay,
let's
see
there's
another
one
in
here
that
we
haven't
talked
about
yet
and
it's
adding
setting
to
menu
block
for
changing
the
break
point.
A
B
D
Okay,
so
yeah
needs
review
and
also
last
night
I
noticed
that
greg
had
posted
a
few
suggested
changes
to
it.
So
I'll
look
up
those
today,
but
basically
it
just
needs
people
to
go.
Look
at
it
test.
It
make
sure
it
doesn't
break
anything
and
then
report
back
into
what
you
find.
A
Okay,
I
also
had
a
crazy
idea.
The
other
day,
I
don't
remember
what
I
was
doing,
but
it
was
doing
something
where
my
brain
wasn't
busy,
and
I
had
this
idea
about
how
to
add
css
to
existing
sites
without
breaking
anything.
But
I
want
to
test
it
before.
I
write
it
down
anywhere
sure,
like
oh,
my
gosh.
That
would
be
so
easy
to
just
fix
in
2.x,
but.
B
My
issues,
the
full
html
to
raw
html
there's
been
no
update
on
that.
So.
A
A
C
Any
idea
what
happened
to
issue
4600,
which
was
the
basically
the
the
admin
description
admin
label
for
blocks.
C
Week's
yeah
last
week's
agenda-
the
third
was
talking
about
you
know
I
guess
trying
to
make
the
admin
and
label
and
description
for
blocks
a
little
bit
more
user
friendly.
C
A
D
A
B
Well,
the
other
thing
is
phil
is
the
way
this.
This
part
of
the
agenda
gets
made
is
basically
that
the
issues
that
show
up
are
the
ones
that
have
advocates
and
if
you're,
not
aware
of
this,
you
can
advocate
for
an
issue.
So
an
advocate
doesn't
have
to
solve
or
fix
the
issue.
They're
just
sort
of
helping
provide.
Updates.
Yes-
and
you
know,
keep
the
issue
up
to
date,
and
maybe
you
know
remind
people
what
needs
to
be
done.
B
So
if,
if
there's
something
you
want
to
get
on
this
part
of
the
agenda
sort
of
automatically,
you
can-
and
everybody
can
just
advocate
for
one
issue
at
a
time.
So
if
there's
an
issue
that
you
really
want
to
work
on
or
see
progress
and
you're
willing
to
at
least
sort
of
project,
manage
it
go
ahead
and
identify
that
and
and
then
that'll
that'll
help
it
get
on
the
agenda
and
get
more
attention.
C
I'm
honestly
debating
on
whether
or
not
I
want
to
advocate
for
that
one.
It's
I
put
out
there
on
on
zulu
about
taking
that.
Actually,
no,
I
did
do
it
in
the
issue.
C
Queue
itself
create
more
of
an
api
around
that
admin
interface
to
where
it
it's
extended,
pretty
much
everything
as
opposed
to
you,
know,
kind
of
piecemeal
and
views
and
piecemeals
and
blocks
setting
it
up
to
where
it
literally
is
it's
just
part
of
core
that
you
know
you
could
set
those
things,
so
I
don't
know
I
I
do
know
that
would
take
a
lot
more
work
than
just
fixing
what's
in
that
issue,
so
I
just
I
don't
know
what
the
general
consensus
is.
I'm
trying
to
expand
on
that.
So.
A
We've
done
that
in
a
couple
of
other
places
too,
and
usually
what
happens
is
we
add
something
entirely
new
and
then
we'll
switch
a
couple
of
interfaces
over
from
all
the
way
to
the
new
way,
but
we
leave
the
old
way
there,
and
so
that
way,
anyone
who's
done.
Anything
with
the
old
way
will
still
be
able
to
do
that.
But
if
someone
wants
the
new
like
cohesive
thing,
it's
there
too.
I
think
we
did
this
with.
A
Oh,
like
adding
new,
like
date
formats
when
the
date
format
like
html
stuff,
changed
like
when
you
put
in
put
in
dates
using
your
keyboard
or
whatever.
There
was
an
interface
change
there
and
we
added
a
new
one
that
he
did
date
and
time
together.
I
think,
and
then
we're
also
working
on
it
with
like
the
display
of
how
a
machine
name
and
a
label
and
the
description
come
out,
because
that
same
pattern
is
replete
repeated
all
over
core
and
so
rather
than
having
a
bunch
of
unique
ways.
A
We
do
it
trying
to
have
like
one
cohesive
tool
and
then
switching
the
places
that
use
it
to
use
the
cohesive
tool.
I
think
is
really
useful.
So
if
we
can
do
something
similar
here,
where
we
create
a
user
interface
element
that
can
be
recycled
across
lots
of
interfaces,
that's
great
but
yeah,
I
think
it's
hard
to
change.
The
whole
thing
like
right
now.
We'd
have
to
wait
till
backdrop
two,
but
we
can
put
in
like
little
reusable
components.
A
B
I'm
fine
with
moving
into
that,
because
it
can
go
pretty
quick,
I'll
repeat
pretty
much
what
I've
said.
The
last
two
weeks,
which
is
we've,
got
some
pull
requests
that
need
testing.
I
think
also
the.
I
don't
know
that
we've
actually
created
an
issue
for
this
yet,
but
we
have
like
an
important
follow-up
issue
to
prevent,
contributed
modules
from
using
this
new
up
api.
I
don't,
I
don't
think,
we've
solved
that
problem
yet
have
we
and
we'll
need
to
before
this
goes
in,
but
basically
I
don't.
B
I
don't
know
that
any
work
has
happened
in
the
last
two
weeks
and
I'm
trying
to
get
to
the
stage
where
I
have
time
to
just
do
some
testing.
If
anybody
else
has
time
there
are
some
detailed
instructions
in
the
issue
on
how
to
test
it,
but
it
doesn't
require
that
you
set
up
a
local
environment
so
and
I've
actually
been
trying
to
get
up
like
a
testing
environment
on
a
dev
server
that
I
could
share
with
other
people
who
wanted
to
help
test
it.
But
I
haven't
got
to
that.
C
Regarding
testing
where's,
the
where's,
the
information
going.
B
B
We're
trying
to
do
with
this
initiative,
the
the
data
is
currently
the
idea
for
the
current
pull
request
is
that
the
data
will
be
pulled
into
backdrop
cms.org
it's
stored
there
and
I
don't
think
another
thing
that
has
to
happen.
Is
we
don't
really
have
a
display
for
it
yet
right
now,
the
current
pr,
I
believe,
just
pulls
the
data
in
and
stores
and
will
also
have
to
create
a
you
know
some
sort
of
visualization
or
make
it
expose
it,
but
that
you
know
that
could
happen
later.
B
The
other
thing
is,
you
know
you
talked
about
like
additional
data
we
could
collect
and
we
have
a
whole
list
of
like
possible
things
we
might
collect
in
the
future.
But
what
we've
decided
so
far
is
that
phase
one
is
just.
I
think
three
things
we're
collecting
is
the
mvp
and
that's
what
we're
trying
to
get
to
now
where
it
collects
the
user's
operating
system,
I
think,
or
the
the
server
like
the
version
of
php
they're
using
and
one
other
thing.
I
forget
off
the
top
of.
C
B
C
No,
I
agree,
I
think
the
back
end
needs
to
be
set
up
and
implemented
for
the
telemetry
first,
so
you
know
the
getting
the
the
a
place
where
the
data
can
go
to
and
it
can
be
aggregated
and
you
know,
read
in
a
human
friendly
form
right.
That's
definitely
going
to
have
to
take
place
first,
so
yeah,
we'll
kind
of
put
put
that
on
the
back
burner
for
that
module.
So
that
particular
module.
C
I
mean
it
is
it's
separate
it
kind
of
ties
into
the
overall
telemetry,
but
to
a
certain
degree
it
is
kind
of
off
in
its
own
little
world.
So
I
mean
the
information
that's
being
pulled
from
that
me
personally,
it
could
live
in
its
own
little
world.
It
doesn't
necessarily
have
to
be
a
part
of
the
the
telemetry
initiative.
So.
B
I
may
have
missed
the
final
point
you
were
making.
I
will
say
that
there
has
been
discussion
about
like
whether,
where
this
data
is
stored-
and
we
talked
about
like
storing
it
externally,
I
think
right
now.
The
idea
is
we're
trying
to
keep
things
simple,
and
so
that's
why
the
decision
has
been
made.
But
again
that
could
change
in
the
future
right
yeah
and
you
brought
up
something
like
this
week
or
in
the
last
10
days.
The
idea
of
like
storing
error
messages
that
people
are
getting
on
a
voluntary
basis.
B
I
don't
know
that
that's
something
we
had
talked
about
before.
It's
something
we
can
talk
about
moving
forward,
but
I
think
we're
not
adding
anything
to
the
mvp.
Just
yet.
First
get
that
working
and
then
we'll
you
know
we
can
talk
more
siri.
I
mean
we
can
have
that
discussion
now.
It's
just
it
won't
be
part
of
the
mvp.
C
C
B
C
As
far
as
testing
goes,
I
mean,
if
there's
a
place
where,
on
the
the
backdrop
side
there's
a
place
where
you
know
we
can
kind
of
lock
in
and
be
able
to
see
one-to-one
data.
As
far
as
that's
that's
being
pulled
in
that
hey,
I
just
sent
this
this
you
know
sent
this
over.
Did
it
show
up?
Is
that
piece
of
it
working
and
kind
of
build
up
from
there?
That
might
be
something
to
think
about.
So,
okay.
B
Well,
I
just
haven't
had
time,
but
my
goal
is
to
to
test
it
myself
first
and
then
I
can
give
people
until
I've
actually
tried
it.
I
don't
really
know
what
to
tell
other
people
in
terms
of
what
how
that
testing
is
going
to
go.
I
know
that
nate
put
some
pretty
detailed
instructions
on
how
to
set
up
a
testing
environment.
If
you're
able
to
do
that
and
want
to
get
ahead
of
me.
That
would
be
great.
Otherwise,
it's
like
high
on
my
list
of
things
to
do.
I've
just
been
overwhelmed.
A
Yeah
sorry,
do
we
want
to
kick
it
over
to
luke.
E
F
Yeah
all
right,
so
so
I
I
I
got,
I
got
squat,
but
but
but
look
I've
been
at
this
at
this
stage
of
being
a
few
hours
work
from
mvp
for
like
a
long
time
and-
and
things
kicked
up
in
the
last
couple
weeks,
but
I've
got
I've
got
time
now
so,
actually,
today,
tomorrow
tim,
why
don't
I
help
you
with
with
with
your
thing
and
and
kind
of
simultaneously
that
we
can
figure
out
how
to
bring
this
to
bed?
F
A
So
I
don't
think
we're
starting
documentation
yet
since
it
is
still
pre-thanksgiving,
but
there
is
a
bunch
of
interest
in
that
coming
soon.
A
Is
there
anything
not
on
the
agenda?
Anyone
wants
to
add.