►
From YouTube: Backdrop Weekly Dev - 2021/09/16
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
This
is
our
weekly
developer
check-in
meeting
and
before
we
get
into
the
agenda
items,
we
should
go
around
and
do
a
quick
set
of
introductions.
I'm
happy
to
go
first.
A
My
name
is
jan
lampton,
I'm
joining
from
oakland
california,
and
I'm
so
thrilled
with
all
of
the
collaboration
that
happened
from
the
larger
backdrop
community
in
the
last
two
weeks
before
this
latest
release.
I'm
also
super
excited
about
what's
coming
in
the
future,
particularly
around
recipes,
and
I
look
forward
to
working
on
that.
Some
more.
Let's
see
robert
go
next.
C
Oh,
who
goes
next
luke.
D
D
F
Hi
I'm
greg
I'm
joining
from
greece.
I'm
super
excited
about
the
new
release
as
well,
there's
so
many
goodies
that
went
in
and
so
much
collaboration
with
the
the
people
of
the
community
and
I'm
like
it's
been
great
to
be
a
part
of
over
the
past
month
or
so.
G
G
One
of
the
releases
I've
been
more
involved
in
the
most,
so
I
enjoyed
that
so
nate
is
not
here
for
our
meeting
today
so
and
a
couple
of
people
here
I
know,
are
busy
working
on
other
things
during
the
meeting.
So
this
meeting
might
be
a
little
less
focused
than
usual,
but
jen
did
you
want
to
do
some
other
stuff
just.
A
One
quick
announcement,
also
tim-
you
might
want
to
change
your
name.
You
know
interesting
good
idea,
but
I
did
want
to
mention
that
we
had
three
new
contributed
projects
that
came
out
this
week,
two
of
which
are
recipes,
which
makes
me
very
excited.
There's
faq
recipe
and
a
testimonial
recipe
and
there's
also
a
new
module
called
web
form.
Add
more
so
thank
everybody
for
continuing
to
work
on
backtracking
trip
too.
G
G
G
Our
final
bug
fix
release
of
the
1.19
release
and
the
1.20
release.
If
anybody's
not
aware
that
always
happens,
there's
always
one
final
release
with
bug
fixes
to
the
previous
version.
Before
we
do
a
new
miner
version
with
new
features,
but
basically
those
things
all
come
out
on
the
on
the
same
day.
G
So
as
greg
was
pointing
out
in
our
previous
meeting
or
in
between,
you
can't
just
look
at
the
release,
notes
for
the
1.20
version
to
understand
all
the
work
that
happened
in
the
last
two
weeks,
because
a
lot
of
changes
happened
in
the
1.19
version
that
will
also
be
inherited
by
1.20.
G
I
think
we
should
spend
a
little
bit
of
time
just
well
a
couple
of.
Let
me
do
this
a
couple
of
things
in
our
outreach
meeting
today
for
those
who
who
didn't
watch
or
weren't
able
to
attend.
We
talked
a
little
bit
about
civvie
crm
and
our
future
use
of
that
for
the
background
community.
We're
planning
to
integrate
civic
crm
with
backdrop
cms.org,
if
you're
interested
in
that
topic.
G
Please
watch
the
previous
meeting
the
outreach
meeting
for
today
and
or
there
is,
if
you
check
and
zoom
up,
there's
links
to
to
a
github
topic
where
we're
talking
about
these
improvements
and
please
let
us
know
if
you're
interested
and
you
want.
There
are
separate
meetings
that
are
happening
just
on
civ
crm
and
if
you
want
to
be
a
part
of
those,
let
us
know
the
other
thing
is
we
did
talk
about
promoting
in
the
last.
G
The
last
10
or
15
minutes
of
the
last
meeting
were
just
sort
of
talking
about
what
the
things
were
excited
about
in
the
in
one
point
too,
oh,
and
I
think
maybe
we'll
rehash
that
a
little
bit
during
this
meeting,
just
because
this
is
the
depth
that
you
know.
This
seems
like
a
good
meaning
to
do
that.
D
I
I
want
to
hijack
just
for
a
second,
please,
please,
I,
and
this
might
actually
tie
into
the
other
place
and
and
end
up
being
like.
I
don't
actually
pull
a
little
outreach
vibe
into
this
one.
I
I'm
just
I
wanna
go
back
to
when
jen
was
talking
a
second
ago
saying
that
there
were
new.
You
know
two
new
contributed
modules
this
week
right.
D
So
so
I
feel
that
that
feels
like
an
opportunity
for
me.
It
seems
like
like,
rather
than
just
like
slide,
that
in
in
the
development
meeting
which,
however
many
people
will
watch
that
I'd
be
like,
let's
do
press
release
about
each
of
those.
Let's
be
like
look
at
this
module.
Look
at
this
great
thing
that
it
does
it
solves.
This
problem
was
written
by
this.
It
comes
from
you
know
these
kinds
of
things
it
comes
in
nine
colors
I
mean
we
can.
D
F
I
know
that
tim
did
an
awesome
screencast
of
like
showcasing
the
sort
of
like
what
we
are
able
to
do
with
it
now
so
one
version
of
it.
Maybe
that
can
be
included.
I'm
not
sure
did
you
upload
that,
to
the
backdrop
youtube
channel
team,
or
is
it
your.
G
It's
directly
uploaded
to
my
channel,
but
we
can
sort
of
add
it
to
a
list
on
background
network
or
on
the
back
youtube
channel.
I
didn't
do
that
yet
though,
so
yes,
I
did
do
a
little
screencast,
just
sort
of
showing
off
the
two
recipes
that
I
did.
Let's,
let's
talk
about
that
a
minute
because
it
very
much
pertains
to
the
topic
yesterday
and
the
issue
that
we
raised
well.
G
We
talked
about
this
a
bunch
last
week
in
the
usability
meeting
and
we
talked
about
it
briefly
in
the
outreach
meeting
today,
which
is
exactly
how
we're
messaging
about
like
recipes
right
now,
because
we
haven't
completely
solved
that
problem
right.
We're
still
not
entirely
sure
what
what
or
if
we
should
define
what
a
recipe
is.
G
All
we
did
so
far
is
solve
the
fix,
a
bug
that
now
allows
us
to
to
sort
of
more
easily
use
something
called
a
recipe,
but
we
haven't
made
any
policy
decisions.
We
haven't
created
a
new
project
type
yet
and
so
and
immediately
you
know,
some
people
did
raise
the
question
today.
For
example,
one
of
my
recipes
is
called
faq
and
olaf
pointed
out
that
there's
a
drupal
project
called
faq,
which,
if
that
ever
reported
to
backdrop
we
would
the
namespace
would
be
taken.
G
And
so
you
know
if,
if
we
had
a
different
project
type
for
recipes,
maybe
there
would
be
less
of
a
likelihood
of
names,
although
I'm
not
even
sure
that
that's
true,
because
it
would
still
we'd
still
have
the
same
problem
so
yeah
and
I
don't
think
that's
a
a
recipe
problem.
But
it
is
a
good
reminder
that,
as
we're
opening
new
projects,
it's
a
good.
G
I
don't
think
there's
any
rule
that
says
we
have
to
do
this,
but
it's
certainly
a
good
idea
to
check
and
see
if
there's
a
group,
any
group
of
projects
that
might
sort
of
have
a
claim
to
that
name.
Space
just
because
we'd
like
to
keep
that
you
know
the
portability
of
drupal
modules
and
themes
as
open
as
possible.
G
So
I'm
interested
in
ideas
on
like.
If
we
should
be,
you
know
we
could
adopt
some
convention
for
recipes
in
terms
of
naming
them.
That
just
makes
it
less
likely
that
we
use
up
name
spaces,
but
I'm
just
I'm
nervous
about
that
too,
because
I
don't,
I
still
don't
know
exactly
what
how
a
recipe
is
different
from
a
module,
and
so
you
know
I
I
think
the
examples
I
did
today
are
pretty
clear.
G
A
Yeah,
I
would
say
a
lot
of
this:
we
just
have
to
figure
out
as
we
go
through
it
right
now.
There
is
no
difference
between
a
recipe
and
a
module.
The
recipe
is
functionally
a
module
works.
Just
like
a
module.
I
think
for
your
specific
problem.
It
might
be
good
to
change
the
name
of
the
project
just
so
it
doesn't
conflict
with
the
drupal
project,
but
you
know
it's
up
to
you.
What
you
want
to
call
it
like.
You
could
call
it
frequently
ask.
A
It
have
like
a
really
long
name
or
you
could
call
it
faq
recipe
or
whatever
you
want.
I
think
that's
fine.
I
don't
have
any
thoughts
on
whether
we
should
adopt
a
naming
convention
in
general.
I
feel
like
if
we
do
probably
only
half
the
people
would
use
it
anyway,
so
I
don't
think
it
would
necessarily
be
a
solution,
but
we
could
mark
it
as
like
a
best
practice.
So
that's
good
go
ahead.
Greg.
You
have
a
better
thought.
F
If
the
recipe
is
meant
to
replace
the
previous,
what
previously
was
a
module
in
drupal?
So
if
the
recipe
provides
the
same
features
as
the
faq
module
in
this
case
in
drupal,
then
I
think
that
there's
no
problem
with
the
namespace
collision.
You
just
need
to
explain
to
people
that
you
don't
need
that
module
anymore.
It's
all
configuration
yes,
basically
that
but
other
yeah,
which
the
upgrade
path
would
probably
like,
would
need
to
migrate
content
as
well,
so
yeah
anyways
just
wanted
to
throw
that
out
there
real
quick.
A
Yeah,
that's
a
good
point.
There
are
a
lot
of
things
that
were
done
one
way
in
drupal
that
don't
have
to
be
solved
the
same
way
in
backdrop
now
that
we
have
configuration.
A
I
think
this
is
more
common
for,
like
older
projects
like
drupal,
5
and
drupal,
6
modules
used
to
do
a
lot
of
stuff
that
can
be
accomplished
with
configuration
and
drupal
7
and
background,
but
yeah
I
you
know,
faq
is
one
of
those
modules
that's
been
around
for
a
long
time
and
I
don't
know
what
the
module
offers
beyond
the
fields
or
known
types
or
whatever,
but.
D
I
I
think
in
in
terms
of
branding
we
we
would
want
like
for
recipes
while
we're
building
them
up.
I
would
think
we
would
want
recipe
in
the
name
so
that
you
can
search
for
okay.
What
recipes
are
there
and
you
know.
E
A
And
long
term
week
we
are,
you
know
we
could
create
a
new
project
type.
The
course
supports
called
recipe
where,
instead
of
being
type
equals,
module
would
be
type
equals
recipe,
and
that
would
give
us
a
really
easy
way
to
search
for,
like
modules
themes,
layouts
recipes,
but
they
are
still
all
gonna
live
in
the
github
repository
one
group
and
that
we
are
still
gonna
have
namespace
conflicts.
The
same
way
right
now,
you
can't
have
like
a
module
in
the
theme
with
the
same
name.
It's
gonna
be
the
same
problem
going
forward
so.
G
Well,
I
I
already
have
done
that.
I
I
think
my
reluctance
to
including
the
word
recipe
and
the
machine
name
was
just
again
that
we
don't
have
an
official
definition
yet
of
what
a
recipe
is,
but
I'm
not
too
worried
about
that,
because
I
think
this
is
about
as
recipe-ish
as
you
can
get
this
particular
one.
So
I'm
okay,
I'm
fine
with
that,
but
we
I
asked
for
an
input
last
a
week
ago
and
the
input
a
week
ago
was
to
leave
recipe
out
of
the
machine.
G
B
Seem
like
if,
if
it's
a
recommendation
or
a
best
practice
to
end
it
in
underscore
recipe
that
that
should
solve
similar
problems
and
if
we
ultimately
decide
to
do
something
wildly
different.
That
seems
a
lot
easier
to
back
out
of
than
having
starting
out
calling
it
fact
and
then
figuring
out
now.
What
do
we
do.
G
Okay,
well,
I
don't
want
to
spend
all
the
time
on
config
recipes,
but
I
I'll
I'll
just
emphasize
that
to
me
that
we're
in
this
stage
of
just
trying
things
out
and
and
then
solving
problems
that
we
we
haven't
figured
out
recipes.
Yet
we
just
one
step
along
the
path
we
can
do
more
now:
okay,
let's
just
go
ahead.
A
And
just
add
one
more
thought
I
was
just
thinking
like
there
are
a
lot
of
drupal
modules
that
solve
common
problems.
That
would
be
really
well
solved
by
recipes,
I'm
just
thinking
of
the
ones
that
are
on
my
list
to
make
I'm
like,
there's,
probably
a
landing
page
module
and
there's
probably
a
gallery
module
like
all
these
things
are
just.
G
Because
is
somebody
able
to
so?
It
was
briefly
brought
up
in
the
last
meeting
when
we
were
talking
about
things
we
were
excited
about.
I
think
joseph
mentioned
test
improvements
in
testing,
which
isn't
something
that
necessarily
went
into
core,
but
it
seems
appropriate
to
talk
about
that
because
it
was
a
big
deal
in
this
last
release.
G
E
Technically,
it
did
go
into
core
because
the
github
actions
are
managed
by
a
file
in
your
code
base.
I
can
talk
a
little
bit
about
this,
although
actually
indigozella
did
most
of
the
work
on
this.
So
I
don't
have
all
the
details.
E
So
the
big
thing
is
that
we
are
now
using
github
actions
to
as
our
test
runner
platform
instead
of
zen,
ci
and
so
indigozella
did
a
lot
of
work.
Many
of
the
bug
fixes
in
1.9,
119,
4
and
120
are
related
to
that
yeah.
So
this
allows
us
to
have.
We
have
more
control
over
our
test
environments
and
we
have
a
better
way
of
seeing
like
what
happened
in
the
process
and
it's
just
generally
more
consistent.
E
F
It's
that
plus
also
we
fixed
a
couple
of
previously.
There
were
random
failures
that
were
happening
and
they
were
usually
like.
We
had
a
meta
issue
which
was
listing
all
those
random
failures
and
actually
nate
figured
out
that
an
underlying
basically,
maybe
nate,
can
speak
to
it.
It's
the
bats
system
that
was
basically
was
flawed
and
it
was
causing
all
these
random
failures,
so
he
actually
provided
a
fix
which
fixed
most
of
these
random
failures
and
then
indie
gazelle
plus
others
fixed
many
other
that
were
not
caused
by
that.
F
So,
basically,
we
have
more
consistency.
It's
more
stable
things
that
were
randomly
happening
before
started
happening
consistently,
like
the
failures
were
happening
consistently
with
github
actions,
so
it
gave
us
the
opportunity
to
actually
figure
out
why
that
was
happening
and
fix
them
and
and
another
thing
that
I
find
really
important
as
well,
because
one
of
the
the
open
issues
that
we
have
is
full
php
8
support
is
actually
we
can
specify
versions
of
databases,
it
could
be
maria
db
or
it
could
be
mysql
and
specific
versions
of
it.
E
F
Yeah
and
even
and
even
the
operating
system
we
had
some
people
reporting
certain
bugs
one
that
comes
to
mind
is
some
nails
not
being
able
to
be
generated
on
a
specific
linux
distribution.
So
if,
if
github
provides
alternative
other
than
ubudu,
then
we
can
also,
in
theory,
change
the
operating
system.
D
Yeah,
I
mean
I
mean
not
just
the
besides
fixing
the
bugs
that
have
been
haunting
us
and
that
that's
that's
nice
to
have
but
necessary,
not
necessarily
something
you
want
to
talk
about
much.
The
the
ability
to
specify
specific
tests
seems
like
like
a
like
a
big
new
improvement
yeah
and
it,
and
it
opens.
F
Up
one
of
my
favorites
it
open
up
opens
up
the
path
for
linting
automatic
lending,
so
see
how
often
we
say.
Oh
you
missed
the
space
here
or
you
added
an
extra
space
there.
So
now,
instead
of
having
spending,
you
know
human
brain
power
to
pick
up
those
tiny
things
now
we
can
automate
it
and
potentially
in
the
future,
I
don't
know
eventually
fix
it
with
like
an
automated
permit
on
top
of
what
the
person
has
found.
So
it's
good.
It's
exciting.
I
Well,
you
guys
covered
it
pretty
extensively,
I
think,
but
yeah
I'm
very
excited
about
the
switch
just
having
our
tests
run
consistently
and
yeah.
Indigozala
has
really
been
doing
an
amazing
job
fixing
those
random
failures
and
she
did
all
of
the
work
to
do
like
the
switch,
the
figuring
out
the
github
actions,
and,
just
yesterday
we
did
a
follow-up
task
of
upgrading
from
1804
ubuntu
1804
to
the
latest
2004
ubuntu.
I
So
now
we're
running
the
latest
version-
and
somebody
already
mentioned
this
in
passing-
that
now,
in
addition
to
selecting
php
versions
like
we're
running
php,
five,
three
and
7
4
right
now,
both
at
the
same
time,
but
she
also
added
my
sequel
versions
into
the
matrix
of
options
up
at
the
very
top.
So
we
can
also
now
run.
You
know,
a
combination
of
different
mysql
and
mariadb
versions
as
well,
so
yeah
lots
of
lots
of
great
new
flexibility
here.
I
do
think
that
it
would
be
great
to
put
up
a
blog
post.
I
I
think
probably
myself
for
indigozella
would
be
the
best
people
suited
for
that,
but
but
I'm
really
bad
about
writing
things.
So
so
I
basically
would
like.
I
would
like
to
volunteer,
but
if
someone
else
would
like
to
volunteer
instead,
I
would
love
that
even
more
nobody's
forthcoming,
so
I'll
say
I'll.
Do
it
just
because,
like
exactly
describing
how
we
can
leverage,
this
has
got
all
kinds
of
things
that
we
should.
I
We
could
describe
actually
maybe
separately
documentation
page
could
even
be
applicable
here,
because
I
know
github
actions
like
it's
obviously
like
widely
used
amongst
other
projects,
but
there's
the
way
that
we
are
using
it
in
particular
could
be
helpful
to
document.
You
know
like
if
finding
the
poll
requesting
a
different
php
version.
Here's
how
you
do
it
type
thing,
because
that's
not
exactly
standard.
I
Yeah
we
have
a
little
bit
of
cleanup
to
do
to
like
turn
off
like
remove
all
the
zen
stuff
from
our
code
base,
because
it's
still
there,
I
left
it
there
in
case
we
wanted
to
like
turn
it
back
on,
like
as
a
safety,
but
so
far
like
the
last
week,
two
weeks
that
we've
been
running
it,
it's
just
been
a
huge
hit.
So
I'm
very
happy
with
that.
Yeah.
G
So
nate,
I
don't
know
if
you're
prepared
to
sort
of
take
over
the
meeting
we
just
prior
to
you
getting
here.
We
just
talked
a
little
bit
about.
We
started
talking
about
the
last
releases
and
we
talked
a
little
bit
about
recipes
and
then
we
started
talking
about
this.
So
that's
all
we've
covered
so
far.
I
Cool,
let's
see,
I'm
not
really
totally
prepared.
Our
1.21
milestone
is
empty
entirely,
which
is
because
we
at
the
end
of
things,
we
didn't
actually
bump
anything.
This
release
from
120
to
121.,
which
is
amazing,
I
mean
we
did
like
halfway
through
or
two-thirds
of
the
way
through.
I
It
was
clear
that,
like
some,
some
of
the
things
had
lost
some
steam,
and
so
we
took
them
out
of
the
milestone,
because
people
would
delayed
working
on
them
or
just
decided
to
do
something
else,
and
the
features
that
we
moved
up
into
that
continued
to
be
in
1.20.
I
We
completed
all
of
them,
and
so
that
makes
it
so
we
didn't
actually
have
anything
to
bump
into
the
next
milestone.
The
only
thing
that
was
left
was
php
8
support,
full
php,
8
support
and
that
doesn't
really
need
to
go
into
a
minor
release.
So
I
moved
that
one
into
1.20.1.
I
Yeah
in
that
one
in
that
meta,
the
php
aids
support.
Since
we
do
have
these
new
capabilities,
I
filed
a
pull
request
that
uses
php
8
on
our
test
suite,
and
so
you
can
go
and
look
at
the
test
results
on
php
8
and
see
what
failed
individually
and
so
there
is.
There
is
more
to
do
there
and
then
the
gazelle
also
listed
them
as
a
comment,
but
we.
A
Okay,
I'm
just
going
to
copy
this
list
to
the
parent
issue.
I
A
Also,
we
did
have
one
issue
that
was
bumped
to
the
121
milestone.
I
think
greg
found
it
in
120
and
bumped
it.
I
just
removed
it
because
it
didn't
have
an
advocate,
but
I
left
it
on
today's
agenda.
This
is
the
issue
about
adding
a
user
interface
to
specify
an
additional
class
to
rows
and
regions
for
flexible
layout
templates.
So
if
that
issue
does
have
an
advocate-
and
it
just
wasn't
listed
in
the
issue-
feel
free
to
put
it
back
in
the
milestone,
but
I
couldn't
find
any
information
about
an
advocate.
C
A
Yes,
thank
you.
Should
we
talk
about
issues
for
1
21,
like
next
steps
in
selecting
issues
for
our
next
milestone,.
I
Yeah,
I
think
it
would
be
good
to
go
ahead
and
start
thinking
about
our
planning
meeting.
You
know,
for
those
that
aren't
aware,
are
planning
meetings
around
like
the
next
feature.
Release
usually
happen
a
couple
of
weeks
after
the
the
the
release
time.
I
So,
let's
see
that
would
be
like
maybe
september
7th
would
be
the
first
meeting
after
like
first
first
meeting
next
month,
and
that
would
be
usually
when
we
roughly
say
hey
we're
going
to
get
together
and
just
like
brainstorm
ideas
and
like
go
through
things
like
the
survey
results
and
things
like
that.
We
solicit
opinions
for
or
solicit
volunteers
for
advocates,
but
as
always
that
we
don't
really
have
the
power
to
say
this
is
going
to
be
in
the
next
release.
I
The
only
thing
we
can
do
is
solicit
volunteers
for
things
that
people
are
excited
about
and
then
get
them
to
become
an
advocate
on
on
a
corresponding
issue.
So
the
process
for
all
releases
is
always
the
same,
that
anything
that
a
developer
would
like
to
see
in
the
next
release,
or
actually
anyone
would
like
to
see
in
the
next
release.
I
We
need
an
advocate
for
that
issue
and
the
process
for
that
is
finding
the
issue
or
creating
the
issue
and
then
putting
your
handle
in
the
issue
summary
saying,
advocate
colon
and
then
and
then
your
github
handle.
And
then,
if
you
there
is
an
is
an
issue
that
has
an
advocate,
then
you
can
market
milestone
candidate,
minor
and
then
another
person
will
come
in
and
second
that
you
don't
need
to
be
a
developer
to
be
the
advocate.
But
every
feature
request
for
a
minor
version
needs
an
advocate.
A
A
good
time
the
candidate
minor
milestone
on
there,
so
that
people
know
that
that
was
previously
supported
to
be
on
master.
F
I
think
it's
a
it's
a
good
opportunity
now
to
reopen
the
poll.
I
think
it
worked
well
previous
time
the
the
one
with
what
people
want
for
the
next
release,
so
certain
items
have
been,
can
now
be
removed
from
that
list,
because
they've
been
added
and
then
we
can
move
on
to
next
ones.
A
So
how
do
we?
How
do
we
pull
in
those
issues,
because
I
think
we
wanted
to
automate
that
process
a
little
bit
so
that
we
don't
have
to
manually
enter
all
those
nodes?
Is
it
all
the
issues
on
github
that
are
marked
as
milestone
candidate,
minor.
F
Not
all
of
them,
I
think
that
the
ones
that
are
have
recent
were
you
know
many
many
comments
or
I
think
team
can
speak
to
that.
G
Sure
I
I
think
it
was
actually
pretty
random.
I
think
I
just
sort
of
like
took
the
most
commented.
You
know,
feature
requests
or
something
and-
and
I
did
like
the
top
30
of
them
and
then
like
people
nominate
others,
so
people
could
manually
have
them,
but
some
sort
of
a
an
importer
would
work.
That
would
be
nice
if
we
want
to
do
that
again,
and
I
have
considered
that
as
well.
Three
of
the
top
10
issues
on
that
made
either
got
into
where
we
made
big
progress
on
this
issue.
I
A
G
No
problem,
no
decisions
have
been
made.
I
have
concerns.
I
I
I
feel
like
the
poll
is
much
more
effective.
If
there's
a
voting
period,
then
if
it's
just
open
all
the
time,
I'm
afraid
sort
of
people
will
ignore
it,
and
I
also
there's
other
logistical
problems
with
that
that
it
doesn't
mean
I'm
not
open
to,
like
figuring
out
a
way
to
make
it
work.
G
But
to
me
you
know
right
now
I
kind
of
feel
like
it's
going
to
have
more
impact
if
we
open
it
up
for
a
short
period
of
time
once
in
a
while,
we
can
reach
in
terms
of
integrating
it
with
the
forum
or
another
site.
That's
all
fine.
It's
just
like.
I
was
able
in
an
afternoon
to
spin
up
a
new
site,
integrating
it
with
back
to
the
forum.
I
don't
know
how
much
work
is
involved
in
that,
and
so
I'm
not
against.
C
F
Regards
having
it
open
all
the
time,
the
whole
idea
was,
I
think
we
took
it
from
the
classic
press
petitions
sort
of
like
system
that
they
have
and
we
try
to
implement
something
similar.
We
can
reach
out
to
the
these
guys
and
ask
them
how,
because
they
do
have
it
open
all
the
time
how's
that
working
for
them
and
whether
what
you
expressed
as
a
concerned
team
is
actually
a
thing
like
if,
if
people
stop
voting
it
because
they
had
it,
you
know
open
for
a
prolonged
period
of
time.
F
My
my
main
argument
for
having
it
open
all
the
time
is
that
when
we
usually
open
it
for
like
a
week
or
two
or
maybe
a
month
right,
so
if
a
new
person
registers
an
account
on
backdrop,
cms.org
and
eventually
they
come
across
this
list,
they
they
get
the
feeling
of
damn
it.
You
know
I
wanted.
I
lost
my
chance
to
voice,
so
I
don't
want
them
to
get
that
feeling
I
I
would
like
them
to.
Even
if
we
could,
you
know
as
soon
as
someone
creates
a
new
account
say:
hey.
F
Would
you
like
to
take
part
on
you
know
making
sort
of
like
influencing
the
decisions
that
we
make?
Please
take
the
time
to
vote
in
this
list
for
what
feature
you
would
like
to
see.
Next,
it
sort
of
like
engages
them.
E
So
I
don't
know
if
anyone
heard
me
before
when
I
was
trying
to
say
this,
but
the
classic
press
people
don't
actually
use
their
petition
system
anymore.
They
moved
everything
to
a
forum
because
they
were
dependent
on
a
third
third-party
tool
that
removed
their
free
plan.
I
Yeah
kind
of
like
with
other
tools
I
feel
like
with
other
websites.
I
mean
that
in
the
end
it
seems
like.
Usually
we
end
up
using
backdrop
for
things
just
because
for
us,
it's
what
we're
the
most
familiar
with,
and
it's
the
most
sustainable
for
us,
yeah
and
classic
press
had
been
using
a
host,
like
you
said,
a
hosted
version
of
a
product
which
probably
would
be
fine
for
us.
But
then,
of
course,
things
like
this
happen.
You
know
where
the
thing
you're
dependent
upon
stops
their
service.
I
F
I
would
like
to
bring
up-
and
I
know
that
already
the
disadvantages
of
it-
that
we
have
github
and
basically
its
feature
is
already
a
github
issue
and
all
their
projects
use
reactions
on
the
yes
thumbs
up
reactions
on
the
first
comment
of
each
issue.
The
problem
with
that
is
that
people
need
to
have
github
accounts
and
that's
a
developery
thing.
F
F
Having
said
that,
we
can,
we
can
encourage
people
if
they,
like
a
certain
feature
to
upload
it
on
github,
and
that
would
help
us
be
able
to
collate
the
list
of
you
know
most
popular
feature
requests.
I
Let's
see
well,
I
do
want
to
say
that
not
not
related,
but
I
do
want
to
say
also
like
the
the
thing
that
we
have
directly
in
front
of
us
like
right
now.
We
of
course,
have
the
the
the
bug
fist
bug
fix
list,
so
the
items
that
didn't
get
done
in
119.4
they
got
moved
into
a
new
milestone,
1.20.1,
and
so
that
will
be
the
next
bug
fix
release
of
backdrop
and
there's
a
still
70-some
issues
in
that
list.
I
We
did
knock
out,
I
think
26
or
more
items
in
the
119.4
list,
which
I
think
was
one
of
our
bigger
bug
releases
that
we've
had.
That
was
really
just
great
to
get
so
many
fixes
all
together
in
there.
So
we
already
have
ways
to
move
forward
and
I
think
one
item
in
particular
that
it
seems
really
obvious
to
me
at
least,
is
additional
telemetry
data
that
we
can
start
collecting
and
greg.
You've
opened
up
an
issue
for
like
a
big
meta
of
telemetry
details
like
things
that
we
could
start
collecting.
I
I
see
we
also
had
some
new
suggestions
come
in,
like
you
know,
detect
like
offline
capabilities
and
stuff.
Like
that,
so
all
kinds
of
things
that
we
can
start
collecting
now,
although
the
issue
to
include
telemetry
in
the
installer,
got,
hung
up
so
right.
Now,
it's
really
just
on
it's,
it's
a
very
small
number
of
sites
that
are
going
to
be
sending
any
data,
because
it's
only
sites
a
that
have
upgraded
to
120
and
have
gone
to
the
modules
page
and
turned
on
telemetry
manually.
F
So
yeah,
I
would
like
to
point
out
that
we
have
a
label
dedicated
for
metrics
in
github
issues,
which
is
called
needs
more
metrics.
So
if,
if
there
is
a
an
issue
where
we're
sort
of
like
have
resistance,
because
we
think
that
that
there's
people
that
might
be
using
the
feature
that
we're
trying
to
remove
or
people
it
might
be,
a
setting
that
we
want
to
change
like
a
reason
that
comes
to
mind,
was
whether
the
the
admin
bar
was
gonna,
be
sticky
or
not
right.
F
F
I
Yep,
and
so
those
are
the
things
I
see
that
are,
are
right
in
front
of
us,
but
yeah,
I
think,
maybe
helping
we
didn't
actually
design
our
timeline
before
tim
had
to
drop
about
getting
the
survey
website
back
open.
I
guess
we'll
kind
of
need
to
discuss
that
through
the
week
and
figure
out
how
we
can
do
that.
I
I
think
it
would
be
good
for
us
to
decide
if
we
need
that
data
before
we
have
the
planning
meeting,
or
maybe
we
use
the
planning
d
meeting
to
get
the
survey
website.
I
You
know
options
back
in
there.
I
I
don't
know
you
know
which.
C
I
F
F
I
did
want
to
ask,
though,
eventually
getting
the
telemetry
ui
and
how
we
allow
people
to
opt
in
or
opt
out
and
cleaning
up
the
the
making
it
part
of
the
installer
and
cleaning
up
decoupling.
The
setting
of
of
usage
statistics
does
it
does.
It
seem
like
a
feature
to
you
like
something
that
would
need
to
go
in
the
next
minor.
Really
so
would
have
to
wait
another
four
months
or
something
that
could
happen
in
the
next
five
fix
in
a
minor
release.
I
think.
A
It
depends
on
what
the
solution
is
nate,
and
I
were
talking
about
this
the
other
day
too,
and
I
came
up
with
some
ideas
I
haven't
yet
put
in
the
issue
but
like
I
think
we
should
add
a
block
to
the
telemetry
module
for
the
dashboard.
That's
the
new
feature,
so
that
would
need
to
probably
go
in
later
because
it
would
need
testing.
But
if
it's
a
change
to
an
existing
user
interface
that
could
go
in
at
any
time
if
it's
enabling
the
module
by
default
on
new
installs.
A
I
Yeah
agreed
and
I
kind
of
think
that.
I
We're
having
some
like
difficulties
regarding
like
the
installer,
because
we
don't
want
to
make
the
installer
longer
or
more
complicated
or
more
scary,
really
in
any
way,
and
so
not
enabling
telemetry
in
the
installer
in
120..
You
know
that
gives
us
a
longer
time
to.
A
There's
also
like
a
lot
of
different
problems
that
I
think
we're
trying
to
solve,
and
I
think
if
we
can
sort
of
separate
them
out
into
like
do,
we
want
to
combine
usage
data
and
telemetry
or
not,
and
then
how
would
we
handle
that?
Technically,
if
you
like,
want
to
turn
off
checking
for
modules
or
updates
or
not,
and
then
once
we
have
that
figured
out,
then
we're
like
okay.
How
do
we
build
the
user
interface
for
that?
And
then,
where
does
it
live?
A
There's
sort
of
like
six
questions
we
need
to
answer
before
we
can
arrive
in
a
solution
and
I
think
because
it
was
so
close
to
120.
We
were
like
build
a
solution
and
we
didn't
even
think
about
like
what
the
original
crush
questions
were,
and
now
we've
sort
of
been
through
that
and
we're
like.
Okay,
let's
slow
down
a
minute
and
figure
out
the
questions
and
figure
out
how
we're
gonna,
what
what
all
the
possible
solutions
are
gonna
be
and
then
which
one
we
like
the
best.
F
It's
time
that
I
had
a
nice
experience
with
any
other
software
requesting
enabling
telemetry,
I
was
taking
grabbing
screenshots
when,
where
they
were
doing
it,
you
know
in
a
polite
and
thankful
way,
I
think.
Well,
I
don't
wanna
because
we're
being
reported,
I
don't
wanna
name
products
but
I'll
I'll
see.
If
I
can
collate
all
that
and
put
it
in
a
relevant
issue.
F
But
I'm
not
sure
if
you
saw
my
sort
of
mock-up
screenshot
10
with
the
you
know.
Thank
you
thingy.
So
one
of
your
concerns
was
that
it's
we're
telling
people
that
we're
doing
something
that
is
bad
and
scaring
them
away
or
yeah.
F
A
I
don't
think
I've
seen
that
screenshot,
yet
I
had
to
like.
I
A
F
It
was
just
that
most
of
the
software,
where
I
I
considered
to
have
a
nice
experience
instead
of
saying
enable
this
to
to
help
us
do
that.
They
were
basically
saying
thank
you
for
enabling
this,
even
though
it
wasn't
ticked,
and
it
was
basically
prompting
you
and
you
haven't,
enabled
it
it's
like.
Thank
you
for
considering
enabling
it.
F
You
hope
you
help
us
build
a
better
product
and
that
sort
of
like
urges
me
to
you
know
help
out
to
to,
instead
of
instead
of
telling
people
that
the
checkbox
basically
does
the
action
of
enabling
or
disabling
a
module
which
does
whatever
it
does.
We
explain
to
them
how
they
help
us
by
making
that
selection,
which
is
more
it's
it's
friendlier.
A
F
Yeah
and
and
if
we
provide
links
to
our
privacy
policy
and
a
detailed
sort
of
like
bullet
point
list
of
what
gets
sent
out
to
sort
of
like
put
them
at
ease
that
you
know
it's
anonymous,
it's
completely
anonymously
and
so
on
and
so
forth
and
what
it's
being
used
for.
I
think
that
will
have
more
chances
for
people
to
opt
in.
I
Yeah,
well
lots
of
things.
I
kind
of
I
wonder
that
the
issue
that
we're
talking
about
is
3168
and
it
has
a
ambiguous
title.
The
title
is
separate
checking
for
updates
from
collecting
anonymous
data.
I
I
think
it
would
be
good
if
we
separated
this
out
and
like
made
an
issue
for
turn
on
telemetry
module,
something
like
that.
You
know
ui
for
turning
on
telemetry
module,
because
this
issue
kind
of
kind
of
has
gone
off
the
rails
a
little
bit
because
it's
meshing
into
too
many
areas,
all
at
once.
Yeah.
A
Do
we
already
have
a
meta
follow-ups
for
telemetry?
Is
that
the
one
you
made
right.
F
So
so
I
haven't
looked
at
the
meta
in
a
while.
I
know
that
we
that
I
raised
children
issues
to
that,
for
which
metrics
we
need
to
gather
or
what
I
thought
were
useful.
But
I'm
not
sure
if
I
have
a
specific
one
for
that
for
whether
we
enable
it
how
we
enable
it
and
so
on.
I
I
A
E
Have
a
I
have
a
question
about.
Actually
this
is
the
plan
to
make
it
so
that
reporting,
which
modules
you
use
and
checking
for
updates
for
your
modules
is
separate
processes.
What's
that.
A
Unfortunately,
they
already
are
separate
processes,
so
we're
trying
to
figure
out
how
or
if
we
want
to
combine
the
user
interface
for
those
two
things
into
one
interface
or
yeah.
We've
got
a
little
cleanup
on
that
yeah.
D
I
Yeah,
so,
okay,
so
that's
what
this
issue
is
3168
is.
Can
you
have
update
module,
turned
on
and
check
for
updates
without
being
reported?
That's
the
option
that
is
in
discussion
here.
This.
E
F
Yes,
exactly
so
that's
a
similar
thing
with
cup
cms
cup
cms,
because
the
department
of
finance
in
australia
manages
the
updates
for
the
entire
platform
for
sas
customers
and
because
they
don't
want
to
have
400
sites.
At
the
same
time,
checking
for
updates
even
like
you
can
still
have
limited
permissions
so
that
the
users
don't
see
the
notifications
about
security
updates,
but
they
don't
even
want
the
platform
doing
traffic
like
getting
implications
either
in
performance
or
in
cost,
because
they
are,
you
know,
causing
traffic
outgoing.
F
A
Exactly
but
maybe
like,
if
we're
so,
if
you
check
for
updates
every
hour
every
day
or
something
your
usage
report
could
be
like
every
month,
and
that
would
help
with
traffic,
I
don't
know
for
400
sites.
Maybe
it's
still.
I
It
could
be
to
to
reach
your
solution
joseph
we
could
do
a
combination
of
issues
that
we're
already
discussing
one
one
issue
we
already
have
open
for
update
module
is
to
remove
the
big
blaring
notifications
across
the
top
and
just
refer
people
to
the
status
report,
because
we
already
have
the
red
dot.
I
So
if
we
did
that
remove
the
notification
system
and
then
second
of
all,
we
also
have
an
issue
for
dismissible
status
report
messages.
You
could
silence
the
update
message
to
silence
the
red
dot
and
those
two
things
combined
might
be
able
to
get
the
solution
that
that
you
want
to
be
able
to
report,
but
not
bother
users.
I
I
C
F
And
it's
for
contribute
as
well
that
this
may
be
useful.
For
example,
there's
the
the
norm
or
the
the
most
usual
thing
is
that
a
module
is
a
single
thing,
but
there's
modules
that
have
sub
modules
and
then
people
wonder
like
hey
is
every.
Is
anyone
using
this
sub
module?
I
want
to
deprecate
it,
they
will
never
get.
They
will
never
get
information
because
the
project,
the
update
module
reports,
the
main
project,
not
the
sub
modules.
I
Well,
we
are
all
out
of
time
today.
So
I'll
say
it
again,
since
I
missed
the
beginning
of
the
meeting.
Thank
you.
So
much
for
all
of
the
hard
work
on
1.21.20
is
an
awesome
release.
Tons
of
new
stuff
in
there
lots
of
back
end
things,
lots
of
user
interface
facing
things
it's
a
great
release,
also
our
collaboration
and
the
number
of
contributors
I
had
that
we
had.
I
I
didn't,
do
a
total
count
which
I
should
go
back
and
check,
but
I
am
I'm
feeling
pretty
sure
that
this
was
probably
one
of
the
highest
contributor
counts
that
we've
had
in
any
release
of
backdrop
ever
so
it
was
a
really
great
release:
lots
of
activity
and
lots
of
new
community
members,
all
stepping
forward
lots
of
new
roles
that
are
being
filled
and
lots
of
new
ways
that
we're
working
together.
So
it's
great
and
exciting
time
in
the
world
of
backdrop,
and
thank
you
so
much
everyone
for
your
work
on
1.20.
I
Okay,
well,
thank
you
all
we'll
catch
you
guys
all
next
week,
folks
next
week,
bye.