►
From YouTube: Backdrop Weekly Dev - 2021/09/23
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
we
are
live.
It
is
thursday
september
23rd.
This
is
our
weekly
developer
check-in
on
active
issues
going
on
for
backdrop
core
and
related
projects
before
we
get
into
today's
agenda,
I'd
like
to
go
around
and
do
some
quick
introductions.
So
if
everyone
can
share
what
your
name
is
where
you're
from
and
if
there's
anything
exciting,
that's
not
currently
on
the
agenda,
you
want
to
share
with
us
30
seconds
or
less
we'll
go
ahead,
and
do
it
now
I'll
go
first.
My
name
is
john
lampton,
I'm
joining
from
oakland
california.
A
B
Hi,
I'm
tim
st
paul
tim,
I'm
in
deerwood,
minnesota
and
yeah
just
a
lot
of
stuff
going
on.
We
had
a
good
design
meeting.
I
encourage
people
to
go
check
that
out
and
give
us
their
opinion
on
the
homepage.
B
C
So
hi
I'm
greg,
I'm
joining
from
greece
and
yeah,
I'm
looking
for
a
bit
of
coordination
and
what
to
work
on
for
the
next
release.
So
robert
did
you
go
yeah.
E
Pass
it
to
justin
justin
christopherson
in
denver
colorado
now
pass
it
to
joseph.
G
I
think
I'm
the
last
one
and
I'm
nate
lampton
from
oakland
california,
quick
sketch
on
the
internet,
and
I
don't
have
anything
else
so
back
to
you.
Jen.
A
Muted,
just
a
quick
update,
there's
one
new
contributed
module
out
this
week,
the
cdn
module.
This
is
something
that
I
ported
a
long
time
ago
and
didn't
get
a
chance
to
use,
and
then
some
fantastic
person
showed
up
and
said.
This
is
working
great.
F
A
Doesn't
it
have
a
release
and
I
was
like
oh,
I
didn't
know
if
it
was
working
or
not
so
that
was
really
exciting
for
me.
So
let's
want
to
share
that.
Let's
see,
I
think,
that's
it,
there's
no
current
applications
or
anything
else.
We
need
to
talk
about.
So,
let's
turn
it
over
to
I
don't
know
mate.
You
want
to
talk
about
the
forum,
posts,
yeah,
sure.
G
G
So,
okay,
so
on
the
agenda
today,
we've
got
three
items
that
have
been
raised
either
before
the
meeting
or
in
the
forum
post,
and
so
the
first
one
is
this
request?
Indigo's
all
my
two
requests.
One
of
them
was
this
issue
provide
a
clean
method
to
suppress
layout,
and
this
is
spun
off
of
something
from
references,
dialogue,
contrib
module
lets.
G
You
create
node
references
within
it
within
a
modal
dialog,
and
we
have
a
pull
request
here
by
gregory
that
creates
this
new
function
that
suppresses
layouts
and
then,
when
inside
of
the
layout
route
handler
function,
it
like
checks
that
function
if
the
layout
should
be
used.
So
it's
really
simple
implementation.
G
My
thinking
on
this
is
that
this
is
like
a
really
good
idea
to
include.
We
probably
need
test
coverage
like
as
always
on
new
things,
but
but
one
thing
that
gives
me
pause
about
all
of
this
is
that
references
dialog
is
the
is
the
module
that
needs
it.
G
But
here
we
go.
Olaf
commented
here
that
there's
this
one
line
here
that
makes
it
all
unnecessary,
but
I
was
looking
at
this
module
and
I
really
think
that,
like
this,
module
probably
can
solve
the
problem
already
when
it
when
it's
doing
its
ajax
request,
it's
just
using
a
normal
post
callback
and
if
it
were
submitting
an
ajax
callback
that
either
was
a
backdrop,
ajax
callback
or
just
it
specified
a
different,
accept
header.
Then
it
would
already
bypass
the
layout
handling
in
the
first
place.
G
So
so
there's
a
way
to
like
solve
this
problem
already
for
references
dialogue
and
I'm
kind
of
worried
that
introducing
a
layout,
suppress
thing
like
this
will
just
allow
people
to
do
things
kind
of
incorrectly
a
different
way.
G
That's
what
I'm
a
little
worried
about
so
yeah!
I
don't
know
it's
there's
more
thinking
to
be
done
here,
but
I
don't
see
any
problem
with
the
way
that
this
is
providing
the
option
yeah.
Any
anybody
else
have
thoughts
on
that
greg.
You've
been
involved
in
this
olaf,
too,.
C
Yeah,
but
it's
been
a
couple
of
years
since
so
I
have
to
check
again
mostly.
I
think
I
was
just
trying
to
be
helpful,
so
the
initial
pull
request
was
by
gifad
and
then
that
person
was
not
available.
So
I
mainly
just
rebased
or
fixed
the
pull
request
and
I'll
do
that
again,
just
to
update
it
but
yeah,
I
don't
have
any
personal
use
for
it.
If
you
think
that
it's
a
way
that
allows
people
to
shoot
themselves
on
the
foot,
then
yeah,
I
don't
know.
G
Yeah,
well
I
mean
there's
lots
of
things
to
do.
Yes,
things
wrong.
You
know
in
backdrop,
and
maybe
that's
fine,
that
you
know
if
they
get
it
working.
Then
there
you
go.
It's
just
that.
I
see
even
from
like
the
the
code
in
references
dialogue.
G
Where
is
it
these
like
to
do?
What
was
that?
Okay,
if
I
just
reload
this
here,
we
go
so
you
can
see
here
that
this
is
what
happens
when
you're
trying
to
do
it
wrong
is,
like
I
tried
doing
it
wrong
this
way
and
then
that
stopped
working-
and
I
saw
I
tried
doing
it
wrong
this
way
and
there's
another
wrong
way
to
do
it
here,
and
so
it's
just
like
it's
just
like
every
way
that
you
could
possibly
have
done
this
wrong.
G
Where
he's
we're
changing
the
the
global
server
variables
to
change
the
way
the
request
was,
you
know
how
the
request
is
identified
when,
in
truth,
what
it
really
should
be
doing
is
just
when
the
request
is
made.
It
just
should
have
set
those
headers
in
the
first
place
like
that,
would
have
solved
the
problem.
You
know
if
headers
would
have
been
passed
here
instead,
but
yeah
yeah.
G
G
A
Yeah
I
I
also
looked
at
this
issue.
I
think
when
it
originally
came
around-
and
I
was
like
it
just
seems
to
me
like
this-
is
something
that
will
happen
when
people
come
to
backdrop
and
don't
know
layouts
yet
and
they're
gonna
be
like.
Oh,
how
do
I
turn
this
off
and
you're
like?
Well,
you
you,
don't
it's
not
like
panels
where
it
you
know
the
rest
of
your
page
will
work
without
it.
A
This
is
something
you
actually
need
in
almost
all
instances,
and
once
you
get
to
know
how
backdrop
works,
then
you
probably
won't
want
to
turn
it
off
anymore.
So
you.
A
Valid
uc
cases
for
not
having
it,
but
so
far
it
looks
like
we've
provided
the
solutions
for
those
so
yeah.
I
would
be
curious
to
know
if
there
are
other
use
cases.
People
are
working
with
that
they
can't
get
it
working
with,
and
rather
than
doing
it
now,
where
it
looks
like,
we
think
there
aren't
any.
G
Yeah,
so
I'm
on
the
fence
about
that
one,
because
it's
like
you
know
yes,
it
seems
like
a
pretty
reasonable
idea,
a
pretty
reasonable
suggestion
it
like
indigo's
l
points
out.
It
would
be
nice
to
have
some
easy
way
of
doing
that.
I
also
kind
of
wonder-
and
maybe
I'll
toss
this
to
robert.
If
the
new
hooks
that
we
provided
in
120,
would
they
help
at
all
with
this
problem
of
being
able
to
say,
hey,
a
request
is
coming
in,
don't
put
a
layout
on
it.
D
That
feels
like
it's
at
a
level
above
where
the
hooks
come
in
it's
when
you
were
flipping
through
the
code,
it
looked
like
it,
it
replaced
it
in
the
code
of
the
vr,
it
kind
of
it
got
in
yeah.
D
D
So
I
think
that
if
you
swap
out,
if
you
replace
the
layout
route
handler,
then
you'll
never
get
to
our
hook.
G
F
C
It's
not
much
trouble.
It's
not
much
trouble
for
me
to
update
it
rebase
it
at
least
so
that
it's
with
the
fresh
code,
because
it's
been
a
couple
of
years
and
then
we
can
make
a
decision
eventually.
But
if
there's
at
least
two
people
now
that
think
that
they're
that
it's
useful,
we
should
not
dismiss
it.
A
G
A
B
G
All
right,
let's
see,
we
usually
do
introductions
at
the
beginning
of
the
meeting
caitlyn.
If
you
want
to
give
an
introduction,
you
can
do
so
now
or,
if
not
that's
that's
fine
too.
I
Oh
sure
yeah,
I'm
kate
and
I'm
calling
in
from
eugene
oregon
and
I've
been
a
full
stack
developer
for
a
long
time.
But
about
five
years
ago
I
pitted
to
be
in
cyber
security.
So
I've
done
less
and
less
web
dev
more
and
more
cyber
security
stuff
here
over
the
last
few
years,
and-
and
I'm
just
observing
today,
just
here
to
check
out
the
dev
meetings.
How
do
they
work
and
what
they're
about.
G
Great
well
thank
you
and
welcome
kate
and
greg
jenna,
and
I
had
a
meeting
earlier
this
week,
just
getting
acquainted
so
welcome
to
the
weekly
call,
though
okay,
so
we'll
keep
going
here.
So
the
next
issue
that
we
have
brought
up
from
the
forum
post
is
issue
5245
using
github
actions
for
php,
cs
checks.
I'll
share
my
screen
again,
because
some
of
these
things
are
just
really
great
visuals.
G
Indagozella
again
has
been
working
on
this
gregory
or
greg.
I
see
you're
in
here
as
well
in
this
poll
request.
You
can
actually
see
under
godzilla
put
some
samples
where
here
it
is
put
some
samples,
like
a
test
php
file
in
here,
to
see
what
kind
of
result
would
happen
with
the
linter,
and
this
does
exactly
what
we
want.
We've
always
described
our
like
ideal,
like
if
only
we
could
get
x
and
now
it's
a
piece
of
cake
that
you
can
just
turn
on
this
github
action.
It
runs
phpcs.
G
It
deals
with
all
of
the
authentication,
the
setting
of
the
tokens.
You
don't
have
to
do
any
of
that
anymore
when
using
github
actions
and
it
per
line
makes
comments.
Saying
hey.
This
line
has
a
coding
style
problem.
Inline
comments
must
start
with
a
capital
letter
and
line
comments
must
end
in
a
period.
You
know
like
it's,
it's
exactly
what
we're
wanting
as
far
as
like
automating
the
process
of
like
making
sure
that
our
coding
style
is
enforced.
G
G
So
my
suggestion
here
is
that
maybe
we
sidestep
the
question
about
composer
and
just
like
curl
the
latest
tarball
release
and
then
use
the
cache
action
provided
by
github
to
cache
the
installation
of
a
coder
module
so
that
we
don't
have
to
download
it
every
single
pull
request.
I
mean.
A
G
A
But
no
coding
standards
like
that
they
have
the
old
drupal
voting
standards
that
work
with
the
previous
version
of
phpcs,
and
I
don't
think
we
have.
I
don't
think
we
have
a
up-to-date
version
of
what
we
need
and
I
don't
and
that
this
might
be
as
simple
as
like
putting
a
coder
project
into
backdrop.
That
is
what
we
need.
A
Yeah,
but
there
is
going
to
be
some
confusion
for
people
coming
from
drupal,
looking
for
the
coder
module,
finding
a
project
called
coder
and
having
it
only
be
coding
standards
and
not
a
module
so
yeah.
I
was
one
of
the
people
that
tried
to
do
this.
I
tried
to
get
coding
standards
running
on
one
of
my
own
kidship
projects
and
ran
into
this
immediately
and
was
like.
I
don't
understand.
C
Does
it
make
sense
for
that
quarter
then
to
be
living
under
the
main
backdrop
group
in
guitar
instead
of
serendipity?
That's
that's
all
I'm
saying
that
so
jeff
has
sort
of
like
not
been
active
for
a
year
now
or
more.
That's
was
that
was
basically
so
basically
just
move
the
repo
and
the
packages
thing
if
we
decide
to
go
down
the
composite
thing
and
move
it
under
the
backdrop
group,
we
currently
have
backdrop
the
main
repo
there
and
the
issues.
Maybe
quarters
should
go
there
if
not
in
trip.
C
A
So
I
don't
know,
I
think,
there's
a
lot
of
questions
we
need
to
test.
I
mean
you
that
starts
with
the
assumption
that
we
actually
want
to
use
composer,
and
if
we
don't
want
to
use
composer,
I
think
there's
a
whole
other
question
of
like.
Where
do
we
want
our
coding
standards
to
live,
and
maybe
the
coding
standards
should
live
in
core
and
not
in
something
to
do
with
composer,
because
that
way,
anyone
that's
running
backdrop
could
use
them
for
something
else.
I
don't
know
there's
just
a
lot
of
questions.
D
A
A
C
I
haven't
thought
of
what
jen
thought
about,
so
we
are
going
to
be
using
it
in
every
pull
request,
so
it
does
make
sense
to
be
part
of
core
and
then
maybe
the
contrib
module
can
take
advantage
of
it,
because
that's
what
we
we
are
going
to
be
using
across
core
and
contrib
right.
So
these
are
the
quality
standards,
so
maybe
a
good
way
is
to
be
enforcing
them
via.
G
Yeah,
I
have
only
a
slight
preference
for
moving
it
outside
of
core
because
it
alleviates
some
of
the
maintenance.
G
All
and
the
coding
standards
also,
if
they
were
separate,
then
a
separate
maintainer,
could
review
and
update
and
keep
the
coding
standards
up
to
date,
instead
of
it
being
core
issues.
C
Yeah
and
then
we
also
we
if
we
need
to
update
a
coding
standard,
mid
cycle
where
which
version
would
be
full,
because
we,
if
it
wasn't
contribute,
we
could
get
a
new
release
which
includes
the
latest
other
than
the
fixes,
whereas
in
core
we'd
have
to
wait
until
the
next
official
release
is
poor,
yeah
yeah,
I
think
yeah.
A
Okay,
yeah.
Well,
I
think
that
if
a
core
maintainer
says,
I
don't
want
it
in
core,
that's
a
good
enough
reason
and
my
second
preference
then
would
be
to
have
it
as
a
contrib
project
and
then
the
only
question
next
is
how
to
deal
with
name
spacing
and
which
version
do
we
want.
C
Currently
so
currently,
if
you
look
at
the
contrib
quarter
is
a
place
folder,
which
basically
says
what
you
need
is
coder,
update
and
coded
review.
We
could
just
reuse
it
and
say
you
know.
A
Yeah,
that
would
work
so
then
it
like
mirrors,
it
wouldn't
be
a
module,
though
right.
A
I
think
that
makes
sense,
because
that
sort
of
models,
what
happened
in
drupal,
where
they
threw
away
the
modules
and
had
only
the
standards
and
so
we're
like
okay,
well
we're
gonna
switch
to
standards
too,
but
rather
than
throwing
away
the
modules
we're
just
gonna
make
separate
projects
for
them.
So
I
think
that
having
coder
match
for
drupal
for
as
for
backdrop,
is
similar,
and
then
you
know
we
could,
even
if
we,
you
know,
wanted
to
include
the
composer
stuff
in
the
contrib
project
we
could.
A
A
Case
then,
probably
what
we
should
do
is
ask
jack.
If
he
can
move
that
project
into
the
contrib
space.
If
not,
we
could
fork
it
and
put
it
there.
H
A
Into
it,
and
I
would
love
to
have
his
blessing
on
that.
A
H
G
C
C
Thought
that
it
was
coming
from
coder,
so
I
started
looking
like:
where
is
that
coming
from?
Can
we
fix
it?
Maybe
it's
just
you
know
a
matter
of
putting
it
outside
the
comment
or
whatever,
but
even
if
we
locate
where
that
is,
then
we
wouldn't
have
much
like
access
to
it.
If
we
don't
have
access
to
the
repo
so.
A
Yeah
and
joseph's
here
now
too,
and
I
know
he
did
a
lot
of
work
on
this
also,
so
I
don't.
G
Okay,
well,
it
sounds
like
our
next
step.
It
seems
like
is
getting
that
repository
jeff's
repository
reviewing
it
to
see
if
it's
actually
different.
You
know
to
see
if
there's
stuff
that
needs
to
be
preserved
there,
we're
assuming
that
he's,
updated,
hpcs
coding
standards
to
be
the
new
version
and
then
move
it
to
somewhere
and
is
this
somewhere?
Is
that
I
didn't
quite
catch
where
the
somewhere
was?
Is
it
backdrop
contrib?
Is
it
a
separate
project?
Yes,.
C
Yeah
and
also
we
could
give
access
to
core
maintainers
for
the
maintainers,
and
on
top
of
that,
we're
gonna
have
the
the
people
from
the
bug
squad.
You
know
just
looking
after
it
so.
G
A
A
E
G
Okay,
well,
exactly
what
it
is
called
will
probably
be
determined
by
whoever
does
the
work.
That's
often
the
case
right.
G
Okay:
okay,
next
thing
I
want
to
do
is
talk
about
telemetry
a
little
bit
and
before
we
get
into
the
actual
discussion,
I
wanted
to
pull
up
this
page,
which
is
the
telemetry
page
on
backdropcms.org.
G
So
if
you're
on
backdropcms.org-
and
you
go
to
the
download
page-
there's
a
telemetry
tab
here
now
and
we
have
30.
We
should
put
a
number
up
here.
How
many
sites
are
counted
total?
Probably
because
right
now,
you
kind
of
have
to
just
add
them
all
up,
but
37
sites
have
started
reporting
their
data
and
we're
starting
to
aggregate
it
on
backdrop
cms.org,
which
is
super
cool.
Obviously
this
page
doesn't
have
any
styling.
It
would
be
better
if
it
was
like.
G
You
know,
graphs
and
all
these
things,
but
it's
still
like
super
exciting
that
these
these
numbers
are
starting
to
to
come
in
yeah.
So
that's
very
cool,
very
exciting.
To
have
these
kinds
of
statistics
available.
C
G
Yeah,
you
know
what
I
think
it
is.
I
think
that
we
have
the
pruning
happening
too
frequently
of
the
data,
and
so
sites
need
to
check
in
it's
like
to
check
in
once
per
day,
but
I
think
the
pruning
of
data
is
happening
more
frequently
than
that.
So
there's.
Actually
these
numbers,
like
they
drop
quicker
than
they
should
yeah.
I.
F
G
But
that's
that's
server
side,
like
preservation
of
data
that
just
could
be
improved
a
little
bit,
we're
not
maintaining
historical
data
right
now
to
see
how
things
change
over
time.
It's
just
just
this
is
the
current
state
of
things.
B
G
That
make
sense,
I
think
it
has
to.
I
mean,
look
at
the
way
that
these
things
are
distributed
unless
people
are
putting
in
a
lot
of
effort
to
spin
up
different
environments,
because
look
at
this
29,
my
sequel
5.5
sites
out
there,
but
there's
not
29
nearly
like.
You
know,
php
versions
that
are
out
there
they're
all
different.
F
I
think
that's
maria
db,
if
it's
five,
if
it
has
starts
with
the
five
it's
maria
db,.
G
A
B
Okay,
so
is
that
well:
okay,
that's
fine!
The
next
question
I'm
having
is,
should
we
be
encouraged?
Are
we
ready
to
encourage
other
sites
to
do
this?
Should
we
like
do
a
dashboard
notification
or
a
blog
post,
or
is
this
too
early.
A
F
B
To
can,
are
you
able
to
really
quickly
show
us
a
site
and
what's
what
information
we're
displaying
to
end
users
on
their
site
about
what's
being
collected?
I
haven't
looked
at
that
yet
or
if,
but
if
you
can't
that's
fine,
I.
G
Looks
like
am
I
logged
in
so
okay.
Here
we
go
nice.
C
Okay,
here's
a
here's.
The
thing
how
I
think
that
page
can
be
improved
is
provide
a
link
depending
on
the
module
that
provides
it
to
take
you
to
that
telemetry
with
the
rest
of
the
data.
Here's
the
stats
that
we
have
so
far
or
something
like
make,
one
of
those
things:
a
link
to
the
telemetry
module.
C
G
G
Yeah,
okay,
so.
B
G
G
Yep,
okay,
I
do
think
it
would
be
great
before
we
cause
like
some
panic
or
something
like
that
if
we
had
a
blog
post
explaining
like
the
details,
but
yes,
I
think
we're
ready
to
start
press
about
this.
That
would
be
great.
B
G
Okay,
let's
see
so
the
follow-up
issues
that
we
have
on
telemetry.
One
of
the
items
that
we
wanted
to
discuss
that
has
been
contentious
is
issue
3168,
so
this
issue
is
about
update
module.
G
So
there's
now
two
mechanisms
that
report
data
back
to
backdrop:
cms.org
update
module
has
been
doing
this
forever
because
it
collects
usage
statistics
how
many
times
a
module
has
been
installed
and
what
versions
there
are
telemetry
is
now
a
second
way
that
we're
collecting
data,
that
is
about
the
configuration
of
the
site
rather
than
just
what
projects
people
have
installed.
G
A
G
Yep,
and
so
where
this
shows
up
is
project
usage
backdrop
these
numbers-
this
is
update,
module
reporting,
usage
and,
if
you
check
for
updates
your
site
gets
counted
in
this
total,
I'm
not
even
sure
where
I
want
to
go
from
from
there.
Maybe
I'll
I'll
turn
it
over
to
greg
or
jen
to
to
talk
more
about
this,
because
it's
kind
of
gotten
into
a
little
bit
of
a
pickle
where
we're
not.
You
know
we're
we've
kind
of
chosen
opposing
sides
here.
A
A
If
backdrop
is
a
viable
off
option
for
them,
and
so,
if
we
all
of
a
sudden
give
people
an
option
to
opt
out
of
something
that
they
never
cared
about
before
now,
people
will
start
using
it
and
it'll
make
our
numbers
go
down
even
more,
and
we
already
made
a
handful
of
changes
to
project
module
that
make
our
numbers
smaller
than
drupals.
A
You
know
things
like
making
sure
our
tests
don't
count
and
making
sure
that
multiple
copies
of
the
same
site
don't
count,
and
so
we're
already
a
little
bit
apples
to
oranges
and
if
you
show
someone's
backdrop
numbers
and
they
are
used
to
seeing
drupals
or
like
oh
gosh,
that
doesn't
look
like
it's
working
at
all.
You're
like
it's
not
the
same
count,
and
now
we're
basically
going
to
be
making
that
worse.
So
I'm
really
concerned
about
giving
people
this
option.
A
A
I
appreciate
that
perspective,
but
I'm
not
sure
in
this
case
that
the
line
there
about
right
and
wrong
is
so
clear,
like
I
feel
like
the
wrong
thing
was
tracking
that
information
before
and
we've
fixed
that
and
now
it's
like
nate
also
had
some
thoughts
about
theoretical
use
cases
that
people
could
come
up
with
where
they
like
didn't,
want
the
numbers
counted
but
still
wanted
usage,
and
then
joseph
mentioned
a
real
word
use
case
where
he
didn't
want
usage
tracking
but
did
want
the
numbers
counted,
and
so
we've
got
like
these
scenarios,
where
it
could
be
useful
to
handle
this
differently,
but
because
all
of
those
scenarios
are
a
little
bit
different.
A
C
Yeah,
okay,
so
if,
if
nate,
you
could
share
the
screen
and
show
that
issue
again,
there's
a
a
comment
from
you
14
days
ago,
which
you
provided
three
screenshots
from
the
pull
request
and
then
comparing
the
the
installer
before
and
after
so.
If
you
scroll
it
up,
it's
the
first
comment
that
you
will
find
from
you.
C
So
yeah
so
from
the
whole
pull
request.
I
think
that
this
issue
says
separate
checking
for
updates
from
collecting
anonymous
data,
so
basically
that
checkbox
that
nate
has
added
there.
That's
the
one
thing
right,
so
that's
what
we're
talking
about
now.
Nade
also
changed
things
in
the
installer,
and
I
think
we
shouldn't
do
that
as
part
of
this
or
it
could.
But
if
we
did,
I
would
prefer
that
we
remove
the
update
notifications
thing
entirely.
C
G
F
G
Your
email
to
somewhere
else,
it's
literally
having
your
site
that
you
just
set
up
email
the
site,
the
email
address
that
you
just
entered,
so
it's
like
you're
already,
the
recipient
but
you're,
also
the
administrator
of
the
mailing
list.
So
it's
that,
like
privacy
concerns
and
all
that
stuff,
is
probably
not
something
that
we
need
to
be
exactly
worried
about.
C
A
C
Close
this
issue
and
pull
requests.
Yes,
okay
and
the
other
thing
is
the
counter
argument
when
it
comes
to
metrics
being
lower.
Is
that
and
I
understand
that
we
are
going
to
have
the
the
project
status
stats
be
less,
but
if
people
enable
telemetry,
we
said
that
we
will
be
counting
the
core
modules
that
are
enabled,
and
if
you
count
the
system
module,
then
you
get
an
actual
account
of
those
that
enable
telemetry
right.
C
C
Yes,
which
is
a
separate
issue
and,
as
I
said
in
the
last
in
the
last
comment
in
that
thread
where
you
are
made,
this
is
what
I,
how
I
summarized
it.
So
these
are
the
three
things
that
I
see
as
actioning.
There's
three
bullet
points.
A
I
still
don't
think
like
so
nate
had
a
pretty
good
point.
I
don't
remember
where
he
said
this,
that,
like
people
aren't
going
to
understand
the
difference
between
sending
these
statistics
and
sending
telemetry
data,
that's
something
that's
sort
of
a
like
backdrop,
internal
thing
that
just
happens
to
be
how
technically
the
systems
work
but
like
for
most
people.
It's
like
am
I
sending
data
or
not,
and
you
know,
they're
probably
gonna
want
to
either
send
data
or
not
send
data
and
not
think
about
which
kind
of
data
database.
C
B
No
yeah,
but
can
I
jump
in
because
I
rejected
that
argument.
A
lot
of
people
are
going
to
disable
that
not
because
they
want
to
because
they
just
think
they
think
that
any
collection
of
data
is
bad
and
if
you
give
them
an
option,
they're
going
to
turn
it
off
and
it's
not
because
they
care,
and
if
you
sat
down
and
explained
it
to
them,
they
might
leave
it
on.
B
C
A
H
A
C
Eighty
percent
of
the
people
might
not
want
to
be
tracked
or
send
information
that
that's
what
I'm
saying.
I
understand
that
it
will.
The
numbers
might
show
appear
to
be
less
and
it
will
hurt
the
project
and
normally
you
you
wouldn't
expect
someone
from
the
community,
you
know
and
being
as
such
an
avid
member
to
say
that
no,
I
still
want
this,
but
yeah.
A
You
know,
turn
set
this
up.
Turn
it
off
by
default,
not
provide
an
option
and
say
nobody
can
report
the
data
unless
they
deliberately
install
a
module
saying
they
do
want
to
report
the
data.
But
then
what
we
should
also
do
is
like
remove
project
usage
from
backdrop
cms.org,
so
that
people
don't
use
it
thinking.
A
It's
an
actual
measure
of
backdrop,
usage
right
and
I
think,
because
we
have
this
parallel
between
drupal
there's
like
an
assumption
there,
without
any
understanding
of
the
nuance
where
people
are
like,
I'm
gonna
look
at
the
drupal
numbers
and
like
backdrop,
numbers
and
compare
them
like
apples
to
apples,
but
I
think
that
if
we
are
gonna-
and
I
think
this
is
also
something
that
I
would
be
happy
to-
you
know
have
like
a
moral
decision
made
about
this
by
the
pnc
like.
Should
we
track
people
at
all?
A
I
think
is
a
good
question
and
if
the
answer
is
no,
we
can't
do
it
without
consent.
Then
I
do
think
we
should.
A
C
A
There's
other
stuff
going
on
here
too,
like
you
know,
if
we
want
to
enable
the
module
for
backdrop
121
or
if
we
want
like,
like
there's
other
things
that
we
could
still
move
forward
on.
Without
this,
this
locking
progress
like
we
could
add
the
dashboard
block,
like
there's
other
stuff
too.
So
I
think
this.
A
C
F
G
Yeah
I'll
repeat
something
said
earlier,
but
this
like,
if
we
ask
them
in
the
installer,
do
you
want
to
enable
telemetry?
That
is.
This
is
the
only
reason
why
I'm
in
favor
of
adding
this
option
in
the
first
place
or
the
primary
reason
is
because
if
we
have
a
way
to
disable
usage
information,
it
should
be
all
usage
information,
not
some
of.
F
G
And
so
that's
the
only
reason
why
I
think
that
we
need
this
option
in
the
first
place
is
because,
if
they
haven't,
if
we're
asking
them
the
question
in
the
installer,
it
should
be
absolute.
It
should
cover
all
usage
information
and
not
just
some
of
it
and
so
yeah.
I
mean
we
could
sidestep
these
problems
by,
like
you
know
not
asking
any
of
these
questions
in
the
installer
like
gregory
suggested,
but
then
it
comes
down
to
like.
Is
that
ethical?
You
know
to.
C
Do
this
we're
still
we're
still
not
going
to
be
doing
the
completely
ethical
thing
which
would
be
to
have
everything
off
by
default?
So
what
I'm
suggesting
is
remove
that
from
installer
have
everything
on
by
default
and
allow
people
to
opt
out
which,
which
I
know
that
jen
is
saying
people
are
going
to
be
afraid.
But
my
my
experience
is
that
some
people
are
also
going
to
be
not
bothered.
C
A
I
think
that
allowing
people
to
opt
out
is
fine
for
telemetry,
because
it's
really
easy
on
off
module
switch,
but
I
do
think
we
need
to
tell
like,
if
we're
going
to
enable
by
default,
we
need
to
do
a
better
job
telling
people
it's
on
like
we
have
it
on
the
status
report,
but
we
can
also
have
like
a
dashboard
block.
A
F
G
And
tells
you
a
little
bit
more
about
it
until
you
go
to
the
report?
Page
nice,
okay,
we're
almost
out
of
time,
so
let's
kind
of
table
that
one
for
now.
So
the
other
things
we've
got
here.
Telemetry
follow-up
issues,
there's
lots
of
telemetry
follow-up
issues
about
ways
that
we
can
improve
this
and
I'm
not
really
sure
what
to
say
about
this
other
than
you
know.
Let's,
let's
get
at
them,
you
know.
Almost
all
of
these
things
can
be
done
immediately,
like
in
the
bug
fix
release.
C
G
Yeah
and
what
these
look
like
are
really
simple.
Like
gregory,
I
mean
you've
been
following
these
pull
requests
and
they
just
look
like
well.
This
one
makes
some
things
but
yeah,
they
add
a
line
here,
saying
hey,
I
want
to
collect
this
information
and
then
it
says
what
is
the
information
that's
being
collected,
so
this
is
like.
F
C
Well,
the
only
the
only
thing
that
I
want
to
point
out.
Nate
is:
what
are
we
going
to
do
with
metrics
that
that
need
to
provide
multiple
things
like
do
we
pass
on
arrays
jason
decoded
like,
for
example,
I
want
so
currently,
the
things
that
we
are
collecting
is
a
single
thing
like
a
php
version,
my
sql
version.
If
I
want
to
report
back
a
list
of
modules
which
I've
tried
on
my
local,
do
I
pass
on
an
array.
G
Yeah,
we
don't
have
that
ability
right
now
right
now
it
needs
to
be
like
either
a
single
string
or
it
needs
to
be
a
number
and
numbers
can
be
aggregated
but
modules
right
now.
The
only
thing
that
we
would
have
like
immediately
available
would
be
like
each
module
might
say.
Like
you
know,
we
would
need
to
say
what's
the
list
of
modules,
we're
interested
in
tracking
and
then
have
a
separate
metric
for
each
one
of
them,
which.
C
Would
you
if
we,
if
we
go
down
that
path,
would
you
prefer
that
it's
its
module
provided
its
own
hook
instead
of
the
system
module?
You
know,
because
currently
we
put
everything
in
the
system
module.
Would
you
prefer
it
if
it
were
on
that
individual
module
and
then,
if
it
was
enabled
with
just
sending
information.
G
C
Yeah,
the
only
the
only
the
only
module
that
comes
to
mind
that
we
had
this
discussion
about.
You
know
whether
it's
going
to
be
focused
on
that,
because
how
much
people
use
it
is
what
you
call
it
contact
form
contact
module.
G
Yeah
yeah
stuff,
like
that
I
mean
if
we
have
specific
ones,
you
know
we
can't
add
them
now
and
then
you
know,
collect
the
data.
You
know
that
we
get
if
we
decide
to
change
it
later.
We
can
simply
stop
accepting
that
data
on
the
server
side
and
just
like
remove
it
from
the
aggregated
list.
Sites
will
still
be
sending
it
if
they
haven't
updated,
but
we
just
wouldn't
care
about
it
anymore.
G
C
So
that
was
a
long-standing
old
meta
that
says
that
lists
multiple
improvements
for
the
content,
module
and
one
of
the
questions
that
pops
up
all
the
time
is
how
much
people
do
use
it.
Do
they
use
it?
Should
we
have
it
enabled
by
default
things
like
that.
So
that's
why.
G
And
things
like
that,
I
think
definitely
should
be
well
actually.
Is
it
enabled
or
not
needs
to
be
not
in
contact
module?
Because
if
it's
not
turned
on
it
won't
report,
it
obviously
yeah,
but
but
like
is,
are
people
using
individual
contact
forms
or
just
the
site-wide
contact
form
could
be
a
great
entry
that
contact
module
itself
should
report.
G
G
Okay,
well
we're
at
the
top
of
the
hour,
and
I
we,
I
only
had
one
more
things
to
discuss,
so
we
have
a
civic
crm
server,
that's
being
set
up
thanks
to
justin,
but
I
think
that
we
may
need
to
table
that
for
a
later
time,
because
some
of
us
have
other
obligations
to
attend
to
so
I
think
let's
wrap
it
for
today.
Thank
you,
everybody
for
for
being
here
and
having
great
discussions
about
telemetry
and
everything
else.
Oh
tim.
We
wanted
to
talk
about
planning
the
next
version.
B
G
Yeah,
so
what
I
would
like
to
see,
if
possible,
is
that
we
reopen
the
survey
or
at
least
collect
new
questions
for
the
survey
and,
if
possible,
have
those
answers
like
the
survey
at
least
open
for
a
week
last
meeting,
I
said
that
we
should
have
the
discussion
on
october
7th
that's
two
weeks
from
today.
Okay,
but
exactly
what
discussion
that'll
be
whether
it's
talking
about
questions
that
should
be
on
the
survey
or
talking
about
the
results
of
the
survey
or
you
know,
depends
on
how
far
the
survey
process
is
gone.
G
So,
let's
kind
of
plan
a
big
128
one
planning
meeting
for
october
7th,
but
exactly
the
format
and
content
of
it
will
be
to
be
determined.
B
Okay,
can
we
just
mention
to
backdrop?
Live
is
in
four.
C
Weeks,
that's
also
there's
a
and
also
there's
a
cvc
area
planning
meeting
tomorrow.
Now
the
time
is
the
same
time
as
the
the
first
meeting,
the
ux
design
meeting.
What
is
it
at
1
pm
is.
It
depends
on
the
time
zone,
pacific,
1,
pm.
B
C
G
All
right:
well,
we
have
to
end
so
thank
you
all
for
for
being
here
again
and
we'll
see
you
guys
next
week
and
thank
you
out
there
on
the
internet,
all
right.
B
Wait
a
second
gregory
greg
wanted
me
to
stick
around
to
talk
to
him
and
now
he's
gone
well.
Okay,
does
anybody
else
want
to
talk
to
me?
I
get
nothing.
I
don't
really
have
much
to
say.
Okay,
I'll
just
joseph
in
particular
backdrop
lives
in
four
weeks
start
thinking
about
what
you
want
to
talk
about.
B
B
Okay,
say:
luke
greg
said
he
wanted
to
talk
to
us,
but
then
he
bugged
out
after
the
meeting.
B
Okay,
you
think
you'll
be
able
to
participate.
Well,
you
know
I'm
joking
about
the
pressure.
You
do
what
you
need
to
do
right,
but
I
also
remember
that
you
don't
have
to
do
a
lot
of
preparation
right,
just
right,
okay
to
just
think
of
a
topic
and
facilitate
it.
Okay,
we're
still
alive.