►
From YouTube: Backdrop Weekly Meeting - July 22, 2021
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
Okay,
we
are
live
today
is
thursday
july
22nd,
and
this
is
our
weekly
developer
meeting
for
backdrop
cms
before
we
get
into
the
agenda.
I'd
like
to
go
around
and
do
some
quick
introductions.
If
anyone
wants
to
share
what
your
name
where
you're
from
and
anything,
that's
not
on
the
agenda.
You'd
like
us
to
know
I'll
go
first,
my
name
is
jen
lampton.
I
am
joining
from
oakland
california
and
I
don't
have
anything
not
on
the
agenda,
so
I'll
go
ahead
and
pass
it
to
tim.
B
I'm
tim
erickson,
sometimes
known
as
st
paul
tim,
I'm
in
deerwood,
minnesota
and
yeah.
Just
we,
we
just
had
an
outreach
meeting,
talked
about
backdrop,
live
and
planning
the
next
one.
So
that's
what
I've
been
thinking
about?
Luke.
C
No
I'm
not
talking
quietly,
which
is
a
rare
issue
for
me,
luke
mccormick
in
san
ramon,
california,
I
used
to
be
a
programmer
I'll
pass
it
off
to
robert.
D
I'm
robert
lang
in
pennsylvania,
california,
bug
folder
on
the
internet
and
my
only
item
is
on
the
agenda
so
I'll
pass
it
to
joseph.
E
Hi,
I'm
joseph
I'm
from
las
vegas
nevada,
I'm
not
like
a
back-end
developer.
E
I
have
a
lot
of
things
I'm
working
on
at
the
moment,
some
of
which
we'll
talk
about
later,
but
yeah
unrelated
to
backdrop.
This
is
my
first
day
back
in
las
vegas,
because
I
took
a
one-week
trip
to
seattle
because
my
brother
got
married.
F
Yeah
me
too,
my
name
is
nate
lampton.
I
am
usually
in
oakland
club,
california,
but
I
am
today
in
nederland
colorado
and
my
name
is
quicksketch
on
the
internet
and
I'm
excited
to
go
over
the
things
that
we
have
listed
today
back
to
you,
jen.
A
Great
thanks
everybody
before
we
get
into
issues
with
the
project
itself,
a
couple
of
quick
updates-
I
think
nate
mentioned
this
last
week,
but
we
have
been
working
for
a
while
to
transfer
the
trademark
for
backdrop.
That
was
originally
in
neat
in
my
name
over
to
the
software
freedom
conservancy
to
hold
on
behalf
of
the
project
so
that
we're
not
necessarily
tied
to
it
and
we
finally
got
a
documentation
for
that
signed
and
sent
off
to
the
proper
authorities.
A
So
hopefully
that'll
go
through
quickly
and
we
also
have
opened
a
request
to
trademark
our
logo.
In
addition
to
the
name
backdrop,
because
since
we
created
the
logo
for
backdrop,
a
couple
of
other
companies
have
started
using
the
logo
for
other
things,
and
so
we
thought
it
might
be
good
to
have
that
trademark
too,
and
the
lawyers
told
us
that
they
thought
there
would
be
no
problem,
because
it
was
pretty
clear
that
we
were
using
our
logo
before
they
were
using
our
logo.
A
So
that's
pretty
exciting,
so
yeah,
it's
a
exciting
progress
that
had
been
stalled
for
a
while,
and
so
it's
really
great
to
see
it
moving
again.
A
In
the
last
week
we
got
a
new
application
for
joel
steidel
to
join
the
backdrop
contributed
group.
He
supported
the
send
grid
integration,
module,
which
is
pretty
cool,
and
his
application
has
all
the
required
information.
So
I've
sent
him
off
an
invitation
to
join
contrib.
A
We
also
had
one
new
contributed
module
release
in
the
last
week
and
that's
the
http
response
headers.
I
think
that
was
you
robert.
So
thanks
for
working
on
that
module
for
backdrop,
cms
properties,
all
sites
were
updated
to
backdrop
119.2,
which
came
out
yesterday.
I'm
sure
we'll
talk
about
that.
A
little
more
later
and
more
importantly,
we
created
a
new
release
of
the
borg
theme
and
updated
all
of
the
sites
to
use
the
new
borg
theme.
So
I
would
encourage
anyone
if
you
see
anything
on
any
of
backdrop's
websites.
That
looks
a
little
funny.
A
A
A
Also
on
backdrop,
cms.org
peter
bw
panda
mentioned
that
he
is
using
an
open
source
tool
called
key
cloak
at
work
that
helps
a
single
sign-on
across
a
lot
of
different
projects.
I
looked
at
it
a
little
bit
this
morning
and
it
didn't
really
look
like
it
added
anything.
A
It's
like
everything
that
backdrop
already
does
it's
user
roles,
permissions
fields
that
work
differently,
but
there
is
existing
drupal
8
integration,
so
it
looks
like
some
people
have
used
that
module
for
exactly
what
we
would
be
using
it
for,
but
obviously
there's
no
code
for
us
to
start
with.
If
it's
working
for
drupal
8.,
so
nate
you
had
thoughts
on
it.
I
think
we
have
opposite
thoughts
on
it.
So
I'd
like
you
to
share
yours.
F
Yeah
so,
first
of
all,
I
would
absolutely
love
a
single
sign-on
solution
for
the
backdrop
websites,
including
the
forum,
the
main
site,
the
ap
or
sorry,
the
docs
site,
the
events
site,
so
many
places
that
we
have
this
like
process
where
you
have
to
re-register,
and
I
think
that
sometimes
they
end
up
with
things
like
the
the
forum,
for
example,
has
a
lot
more
value
in
registering
for
an
account
than
backdropcms.org
itself.
F
I've
also
expressed
some
interest
in
trying
to
do
things
with
other
third-party
solutions,
and
I
can't
quite
remember
some
of
the
other
ones
that
I've
floated
in
the
past,
but
on
using
them
further.
I
decided
that
they
were
not
not
very
good.
I've
not
heard
of
key
cloak
before,
but
the
one
that
was
foremost
in
my
mind
was
there's
a
drupal
module
for
simple
saml
and
simple
sample
provider
and
simple
saml
is
a
php
library
that
handles
a
lot
of
the
authentication
problems
and
also
some
other
tasks.
F
Inside
of
it,
and
then
simple
sample
provider
makes
it
so
that
one
backdrop
website
becomes
the
repository
of
users
and
then
other
backdrop.
Websites
could
potentially
connect
to
that,
like
kind
of
mother
site
to
use
that
same
list
of
user
accounts
with
all
things,
though,
there's
multiple
barriers
that
it's
a
lot
of
work
to
set
it
up.
The
simple,
simple
sample
modules,
don't
actually
exist
for
backdrop,
yet
both
the
consumer
and
the
provider-
and
we
also
would
need
to
you,
know,
support
and
maintain
a
new
chunk
of
software.
F
So
I'm
really
curious
about
key
cloak
and
it
actually
looks
like
bw
panda
joined
the
conversation,
so
perhaps
just
in
time
peter
we're
we're
just
going
over
the
key
cloak
recommendation
or
discussion,
and
we
don't
really
know
much
about
it.
I
think,
too,
to
provide
much
information,
but
I'm
very
keen
on
hearing
information
and
what
sort
of
thing
it
can't
provide.
F
Just
from
looking
at
the
start,
I
can
see
that
it
supports
simple
saml,
which
is
great,
so
we
could
potentially
have
a
simple
saml
consumer
module
on
the
backdrop
websites
and
then
connect
into
some
central
server,
which
I'm
assuming
would
be
running
key
cloak
peter.
Are
you
able
to
speak
anymore
to
this.
G
Yeah,
I'm
not
sure
how
it's
like.
I
just
know
that
at
work
or
I've
only
been
like
a
few
months
now.
I've
discovered
that
they're
using
it
for
people
log
into
a
custom
gitlab
instance
where.
F
Yeah,
okay,
so
it
sounds
like
we
don't
have
a
whole
lot
of
more
information
there
either.
It
does
look
like
it
looks
like
it's
written
in
java,
which
might
be
a
little
barrier
for
us
in
in
setup,
but
it's
possible
java
applications
also
sometimes
they're
really
easy
to
run
because
they're,
often
in
jar
files.
You
know
java
archive
files
that
make
them
very
much
like
a
self-contained
product,
but
I'm
not
quite
sure
where,
like
what
kind
of
things
that
this
would
be,
providing
I'm
guessing
that.
F
Well,
I
don't
know,
I
guess
we'll
have
to
look
into
it.
I'm
hoping
that
it's
something
along
the
lines
of
like
jenkins.
You
know
jenkins,
is
a
java
application
for
running
intermittent
tasks
and
builds
used
to
be
very
popular
for
running
your
cron
jobs
and
for
running
like
software
builds
before
we
had
things
like
travis,
ci
and
github
actions.
F
But
if
it's
anything
like
that,
then
you
start
it
up,
and
then
it
provides
a
web
interface
for
like
configuring
and
changing
the
settings
and
installing
plugins
and
things
like
that,
and
I
I
think
that
that's
probably
where
we
need
to
start.
It's
probably
just
with
some
experimentation,
reading
the
documentation
and
seeing
what
kinds
of
things
it
would
provide.
F
My
guess
is
that
where
this
would
swap
in
is
instead
of
using
simple
saml,
which
is
a
php
based
solution
and
then
using
a
backdrop
module
that
connects
with
simple
saml.
This
probably
replaces
the
server
component.
That
does
what
simple
saml
does,
which
is
accepting
the
request
and
returning
the
responses.
A
F
Yeah,
it's
it's
not
clear
because.
F
A
Drupal
8
module
integration
like
I'm
and
it
looked
like
there.
They
had
also
set
up
like
two-way
interactions
between
the
two,
which
looked
pretty
handy
so
like.
If
you
enter
data
into
your
drupal
website,
it
would
automatically
transfer
over
to
the
main
data
store
and
if
you
entered
data
in
the
meta
store,
it
could
update
the
drupal
site.
So
it
looks
like
they're
like
the
api
on
is
pretty
good,
but
it
is
going
to
be
duplicating
everything
that
we
already
have
done.
So
I
don't
know
how
much
value
there
is
in
that,
like.
A
I
think.
The
piece
that
we
need
is
the
actual
like
logging
in
bit,
which
I
think
we
can
probably
get
with
simple
saml.
I
don't
think
we
need
any
of
the
rest
of
it.
It
looks
like
it
was
designed
for
websites
that
don't
have
authentication,
and
so
they
it
handles
the
authentication
and
all
of
the
data
that
will
go
along
with
that.
But
yeah
I
don't
know
well.
A
It
would
be
interesting
to
create
a
dedicated
issue
for
this,
where
we
can
talk
about
it
in
more
detail,
rather
than
just
in
the
meeting
where
it
might
get
lost.
So
maybe
I'll
I'll
copy
this
over
there.
A
F
Yeah,
I
I
think
that
these
are
almost
two
separate
things
that
yeah
single
sign-on
with
github,
while
useful
for
other
purposes,
would
allow
us
to.
You
know,
link
a
person's
account
with
the
git
github
account
making
it
so
that
we
could
show
them
like
their
projects
and
things
like
that.
But
I
think
that
that's
actually
different
than
then
single
sign-on
across
multiple
sites,
like
single-sided.
F
A
We
have
a
single
sign-on
with
github,
then
somebody
who's
signed
into
github,
wouldn't
have
to
sign
in
to
any
of
our
websites.
So
that's
that
was
key.
You
wouldn't
need.
You
wouldn't
need
to
go
through
the
process
of
creating
an
account
on
our
site,
because
your
github
data
would
come
over.
So
that
would
be
good,
but
I
also
think,
even
if
you
don't
have
a
github
account,
you
should
be
able
to
have
an
account
across
all
of
our
sites.
A
F
Yeah-
and
we
also
have
the
problem
of-
if
you
have
an
existing
account,
you
should
be
able
to
connect
it
to
a
github
account
right
so
authenticate
into
the
github
account.
So
that's
that's
like
a
different
yeah,
another
additional
scope-
yeah.
Okay,
so
we
don't
actually
have
at
least
not
that
I
can
find
dedicated
issue,
but
I
think
the
best
place
would
be
in
the
backdrop,
ops,
slash
backdrop
cms
channel
yeah.
I.
F
Yeah,
I
don't
think
that
I
don't
think
that
we
should
pursue
bakery
anymore,
like
bakery
is
what
drupal.org
uses
and
it's
like.
The
code
is
hard
to
follow
and
understand,
and
it's
also
at
this
point
like
reinventing
the
wheel
like
single
sign-on,
has
kind
of
become
solved
with
with
saml
and
open
id
too,
and
I
think
that
by
following
those
standards
will
be
a
lot
better
off
long
term,
because
just
the
number
of
connectors
and
providers
and
the
way
that
they'll
talk
to
each
other
there's
just
a
huge
market
for
them
out.
F
A
Does
that
mean?
Do
you
think?
Maybe
this
should
save
this
for
the
issue,
but
do
you
think
that
simple
sample
approach
would
work,
for
example,
for
git
hub,
in
addition
to
our
own
properties?
So
we
wouldn't
need
different
methods
for
handling
that,
or
do
you
think
it
probably
depends
on
what
github
provides
right,
yeah.
F
Yeah,
I
I'm
not
actually
sure
what
github
uses
in
its
capabilities,
but
I
I
do
think
that
there's
still
a
difference
here
that
I
think
we
need
our
own
simple
sample
provider
as
well
as
the
github
driven
one,
because,
like
you
say,
we
shouldn't
require
you
to
have
a
github
account
to
sign
up
for
the
forum,
for
example.
F
F
Real
bonus
about
simple
sample
2
is
it
works
across
domains
and
bakery
is,
is
tied
to
one
master
domain
and
sub
domains.
A
F
A
A
All
right,
so
it
looks
like
that
was
all
we
had
for
backdrop,
cms.org
related
issues,
so
let's
turn
it
over
to
unh
to
talk
about
itself.
F
Yeah
so
before
we
get
into
the
status
report,
which
can
be
somewhat
repetitive,
we
were
talking
before
the
meeting
that
could
be
fun
to
do
a
little
highlight
reel
of
things
that
have
happened
this
past
week
and
there's
lots
of
great
and
exciting
things
hang
on.
The
probably.
The
biggest
thing,
of
course,
is
that
there's
a
new
version
of
backdrop.
F
F
It
did
include
a
number
of
really
great
fixes,
especially
that
backup
and
migrate
regression
that
we
had
since
119
has
finally
been
out
and
put
into
a
release,
which
is
super,
exciting,
also
kind
of
an
exciting
thing
for
phil
sword,
or
is
that
right,
phil
sword
for
sorry
name
is
not
clicking
with
me,
but
for
the
phil
sword.
F
He
had
this
issue
for
disabled
brotly
for
css
and
javascript
and
he'd
been
hounding
us
on
that
for
a
couple
of
weeks,
a
while
back,
and
that
issue
is
fixed
in
there
as
well.
F
One
other
thing:
that's
kind
of
unusual
is
that
we
made
a
change
to
the
robots.txt
file
in
this
release.
So
this
is
one
of
the
rare
releases
where,
when
updating
it's,
not
just
replacing
the
core
directory,
you
can
of
course
leave
your
robots.txt
alone
and,
as
is
but
it'd,
be
a
good
idea
to
merge
in
the
changes
that
we
made
to
the
robots.txt
file.
F
It
was
a
kind
of
silly
problem
that
we
were
having
that
we
were
including
trailing
slashes
and
all
of
the
pads
for,
like
all
of
the
pads
that
are
in
robots.txt
and
because
backdrop
or
web
servers
remove
the
trailing
slash
things
like
the
user
login
and
the
administrative
pages
were
not
actually
being
excluded
from
search
indexes.
F
F
We
think
that
there's
we're
having
some
conversation
about
whether
or
not
it's
a
less
than
symbol
or
a
greater
than
symbol,
because
we're
dealing
with
time-
and
I
think
everybody
can
sympathize
with
whenever
you're
dealing
with
time
figuring
out
if
something
is
before
or
after
a
certain
second,
it's
it
can
warp
your
head
a
little
bit
so
5126.
If
we
can
get
that
fixed,
then
we
can
potentially
start
using
github
actions
for
running
our
tests.
F
Let's
see,
indigo
zella
has
been
working
on
a
really
great
feature
in
issue:
51,
sorry
50,
21,
making
it
so
that,
as
you
move
blocks
around
in
the
layout
ui,
we
use
the
new
capability
of
backdrop
announce
it's
a
javascript
function
that
can
announce
arbitrary
things
to
screen
readers,
and
so,
as
you
move
blocks
around,
it
announces
to
you
the
new
position
and
the
new
region
in
which
the
block
has
been
placed
through
a
screen
reader.
F
So
that
was
great
to
get
that
patch,
updated
and
checked,
and
then
mustafa
dogen78
came
in
and
validated
it
who
is
an
experienced
screen,
reader
user
and
so
big
thanks
to
indigozella,
mustafa
and
doc
welmont
for
their
work.
On
making
that
happen,
yeah
having
an
actual
user
validate
something
and
and
then
say
that
it
works
for
them
is
one
of
the
best
things.
So
we
still
have
to
do
a
slight
code
review
on
that.
Just
to
make
sure
that
everything
looks
good
in
implementation.
F
Improvement-
let's
see,
I
think
those
are
kind
of
the
updates
that
I'd
like
to
talk
or
that
I
would
like
to
mention
joseph
at
the
beginning,
the
meeting
noted
that
he's
been
working
on
some
interesting
new
things
for
backdrop
joseph,
do
you
want
to
talk
briefly
a
little
bit
about
your
stuff
you're
working
on
with
layouts.
E
Sure
so
this
kind
of
came
out
of
some
discussions.
We
had
at
backdrop
live
we're
talking
about
kind
of
just
the
experience
of
configuring.
E
Essentially
a
combination
of
the
in-place
editor
for
panels
from
drupal
7,
and
also
a
module
from
drupal
8
called
the
web
profiler
module,
which
I'm
not
using
any
of
the
code
of.
But
it's
more
like
the
idea
of
the
the
bar
at
the
bottom,
with
like
all
this
information
about
how
the
page
got
generated.
E
Although
the
the
web
profiler
module,
is
targeted
exclusively
at
developers
and
this
would
be
more
site
builder
information,
so
yeah-
that's
that's
kind
of
that.
It's
at
the
moment,
still
I'm
working
on
like
a
proof
of
concept,
just
making
sure
I
can
get
all
the
information
about
how
your
page
was
generated
and
then
providing
some
ui
to
move
things
around
and
at
the
start
I
hope
it
would
just
be
the
informational
stuff
and
then
the
ability
to
move
blocks
around.
E
But
I'm
hoping
at
some
point
that
I
can
extend
this
out
to
work
on
more
things
like
work
on
like
views
or
content
like
view
modes
or
forms
to
be
able
to
sort
of
have
like
a
drag
and
drop
interface
on
a
layout
style,
drag
and
drop
interface
on
like
editing
the
fields
on
your
nodes
or
other
things,
but
that's
kind
of
like
a
a
future
thing.
I
I
don't
know
if
this
is
a
core
thing,
it
would
probably
be
a
contrib
project
to
start.
E
E
F
E
F
As
as
the
things
come
along,
of
course,
yeah,
we
can
look
at
addressing
those
things
in
court
to
get
have
those
flexibilities.
Yeah.
The
renderers
are
things
like
that.
There's
the
admin
version
that
shows
you
the
admin
interface
and
then
there's
the
front-end
version.
That
shows
you.
You
know
what
you
see
as
a
visitor
but
yeah.
I
think
you're
right
that
it's
just
explicitly
hard-coded
use
this
renderer
here,
use
that
renderer
there
and
yeah
there's
no
way
to
flip
it.
E
F
Okay,
great,
thank
you,
joseph
yeah,
we'll
need
to
kind
of
move
along
here,
there's
also
an
announcement
here.
It
looks
like
from
tim,
possibly
about
a
virtual
user
group.
Is
this
your
item
tim?
B
But
sure
I'll
make
this
really
quick,
because
we
have
virtual
user
group
coming
up
it's
a
little
bit
more
advanced
than
most
of
our
virtual
user
groups.
It's
on
writing
tests
for
core
joseph
is
volunteered
to
delete
that
it
will
be
recorded
and
shared
afterwards.
B
B
G
F
Agenda
are
items
for
119.3.
That
will
be
the
next
bug
fix
release
with
119.2
just
having
come
out
yesterday,
1193
release
will
be
put
out
when
there's
a
sub
worthwhile
number
of
bug,
fixes
that
are
in
that
release.
So
the
only
items
we
have
for
119.3
listing
on
the
agenda
is
issue.
50
76,
which
is
full
php
8
support
we're
continuing
to
try
to
get
complete
coverage
there,
the
mechanism
again
for
getting
full
php
8
support.
Primarily
that
means
running
our
test
suite
on
a
php,
8
environment.
F
You
can
do
that
easily
through
lando
or
dev.
Now,
simply
by
changing
your
ini
file
in
those
projects
to
use
php
8,
that
can
be
an
easy
way
of
setting
up
a
backdrop
environment
for
testing
and
then
running
the
tests.
F
But
also
I
get
this
php
8
support
issue
kind
of
goes
hand
in
hand
with
switching
to
github
actions
that,
because
php
8
will
be
our
newest
version
of
php
to
support
we'll,
probably
move
the
upper
range
of
where
tests
are
run,
all
the
way
up
to
php
8
and
continue
to
run
the
lowest
end
as
well
to
make
sure
that
we
don't
have
any
regressions
on
this
newest
version
of
php.
F
Let's
see
190,
I'm
sorry,
1
20
is
the
next
minor
release.
The
next
minor
release
will
be
coming
out
september,
15
2021,
with
feature
freeze
on
the
first
of
that
month,
so
coming
up
on
august,
and
then
that
will
the
month
of
august
will
be
basically
the
last
month
of
work
that
we
do
on
the
next
minor
version.
F
F
We
haven't
had
any
movements
in
the
past
week
on
that
one,
but
we
continue
to
have
a
pull
request
that
almost
fully
works
continues
to
need
a
little
bit
of
work
to
solve
some
of
the
javascript
errors
that
are
occurring
after
selecting
an
image.
I
think
and
then
trying
to
select
another
one.
There's
some
problems
there.
F
Let's
see
jen
since
you're
here,
one
of
your
issues
is
in
the
1.20
release.
The
field
has
value
visibility,
condition,
issue
47-28.
F
Okay-
and
I
think
that
that's
kind
of
it
for
the
the
items
that
are
are
slotted
into
the
1.20
milestone
yeah,
we
continue
to
you,
know,
allow
any
features
that
anybody
is
interested
in
undertaking
process,
for
that
is
just
picking
an
issue
that
you
favor,
adding
yourself
as
an
advocate
by
editing
the
issue
and
then
putting
your
handle
in.
A
F
And
then
adding
a
tag
for
milestone
candidate
minor
and
then
another
person
will
come
along
and
second
to
that
request,
and
then
we
can
start
talking
about
it
on
these
weekly
meetings.
Anything
else
that
I've
missed
folks
for
1.20.
F
Okay,
all
right.
Lastly,
we
have
ongoing
initiatives.
The
one
ongoing
initiative
that
we
have
in
action
right
now
is
telemetry.
Telemetry
is
collecting
information
about
the
way
backdrop
sites
are
configured
so
that
we
can
make
better
decisions
about
what
features
to
include
in
the
product
and
the
telemetry
meta
issue
is
issue
285..
F
B
F
I
think
that
every
item
that
was
addressed
or
that
was
raised
during
backdrop
live-
has
been
addressed.
Now
we
improved
the
server
side
component
of
it,
so
that,
as
data
is
sent
to
backdrop
cms.org,
it
now
actively
checks
to
see
if
that
data
is
allowed
to
be
saved,
and
it
does
that
by
configuration
on
each
project.
So
on
the
project
node
on
backdropcms.org.
F
F
It
additionally
not
only
allows
what
stuff
can
be
saved,
but
lets
you
specify
a
human,
readable
label
and
lets
you
specify
the
precision
of
the
information
when
it
is
displayed
and
that's
really
useful
for
taking
different
php
versions
like
7.4.1
7.4.2
and
then
saying
the
precision
of
the
way
that
the
these
numbers
should
be
aggregated
is
one
decimal
point,
so
it'll
group,
together
all
of
the
7.4s
into
a
common
group,
so
that
ended
up
having
multiple
benefits,
putting
stuff
server
server
side
configuration
on
backdrop
cms.org,
because
we
both
locked
it
down
so
that
we're
not
saving
data,
we're
not
intending
to
and
we're
getting.
F
This
extra
benefit
of
being
able
to
configure
how
data
is
aggregated
and
presented.
So
yeah,
I'm
pretty
excited
about
all
of
those
capabilities.
F
The
there's
two
pull
requests,
one
for
backdrop
core
itself
that
adds
the
telemetry
module
and
that's
pretty
easy
to
get
set
up,
and
then
there's
also
a
pull
request
to
project
module
to
add
the
server
side
component
to
it.
There
are
some
instructions
for
setting
up
the
whole
apparatus
in
this
issue,
issue
285
and
yeah.
Some
some
additional
testing
would
be
needed.
D
F
F
You
know
that
we're
not
doing
anything
unreasonable.
We
need
to
incorporate
enabling
this
module
in
the
standard
profile
as
part
of
the
installation
process,
those
radio
button,
or
so
I
check
boxes
at
the
bottom.
That
say
enable
updates
and
send
emails
for
updates.
F
Probably
in
that
section
it
would
be
a
real
natural
location
to
also
ask
if
they
want
to
enable
reporting,
and
then
a
nice
to
have
would
be
better
charting
like
graphs
and
chart
display
on
backdrop
cms.org,
but
the
new
version
already
has
better
presentation,
because
it
aggregates
the
numbers
together,
so
we'll
definitely
get
a
much
more
useful
output
in
this
latest
version
than
we
had
before.
F
Thank
you
all
right.
That
is
the
end
of
the
agenda
for
this
week.
Do
you
guys
have
anything
else?
You
guys
would
like
to
bring
up
or
discuss
okay.
Well,
in
that
case,
we
will
close
for
the
week.
Thank
you
all
for
joining
this
meeting,
thanks
to
peter
for
hopping.
In
briefly,
I
I
will
take
a
little
bit
of
time
to
look
at
that
single
sign-on
solution.
I'm
excited
to
have
different
options,
even
if
it
doesn't
pan
out
just
to
broaden
our
options.
So
all
right.
Well,
thank
you.