►
From YouTube: Backdrop Weekly - December 10th, 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).
A
Okay,
we
are
live
on
youtube
today
is
thursday
december
10th.
This
is
our
weekly
development
check-in
meeting
before
we
jump
into
the
agenda.
Let's
have
everybody
go
around
and
do
introductions?
Oh,
I
forgot
again.
Most
of
you
guys
have
been
here
before,
but
if
you
don't
want
to
be
on
the
live
stream,
which
is
happening
right
now,
you
can
turn
off
your
camera
and
or
microphone
and
watch
that
you
can
also
participate
in
the
chat
here.
If
you
want
to
have
no
record
of
you
being
on
the
internet,
that's
fine!
A
So
before
we
move
on
to
the
agenda,
let's
go
ahead
and
start
with
introductions.
Nate.
Let's
start
with
you,.
B
C
I'm
here
my
name
is
tim
erickson,
st
paul
tim,
I'm
up
here
in
deerwood
minnesota
and
have
been
super
busy
lately
and
really
trying
to
find
time
to
help
with
the
the
crunch
for
the
next
release.
But
hopefully
we'll
do
better
this
weekend.
We'll
talk
about
I'm
here
and
want
to
talk
about
some
sprinting
opportunities.
C
We'll
do
that
later
in
the
meeting
gregory.
D
Hi
greg
from
greece,
usually
in
australia,
but
now
in
greece
you
recover
and
things
I
haven't
joined
the
past
three
or
four
meetings.
So
just
catching
up.
I've
been
a
bit
active
this
week
in
the
issue
cube
and
yeah,
since
we
have
another
three
weeks
or
so
until
future
freeze
interested
to
get
some
things
out
of
the
way
and
also
interested
in
the
upcoming
sprint.
E
Hey
I'm
phil
ward
out
of
wichita
kansas
here
to
just
kind
of
see
what
we
can
get
figured
out
with
telomere
telemetry
initiative
and
kind
of
see
where
that
sits,
also
see.
If
maybe
I
can
advocate
for
a
very
small
addition
to
some
some
of
the
more
more
recent
compression
logarithms
called
broadly
pass
it
over
to
lars.
F
Oh
hi,
I'm
justin
chris
jefferson,
I'm
in
denver
colorado
and
I
just
poke
with
the
server
once
in
a
while
to
keep
it
rolling.
B
All
right
is
that
everyone
yeah
I'm
not
sure
if
luke's,
actually
desk
or
able
to
unmute
or
or
whatnot.
So,
let's
go
back
to,
let's
see
first
up
on
the
agenda
is
updates
from
the
pmc
tim.
Your
list
on
the
agenda
is
giving
some
updates
here.
Can
you.
B
A
D
Sure
yeah,
so
we
have
been
discussing
for
some
time.
There
was
a
few
issues
with
the
permissions
that
contrib
module
themes
and
layouts
authors
were
getting
once
they
they
migrated
or
moved
their
projects
once
they
were
ready
into
the
contrib
group.
So
how
we
used
to
resolve
this
is
they
would
come
to
zulip
and
and
complain
about
the
problems
that
they
were
having,
and
then
one
of
us
would
jump
and
sort
it
out
for
them.
D
So
there's
a
general
sort
of
like
goal
to
automate
as
much
as
possible
that,
but
first
we
needed
to
decide
what
kind
of
permissions
each
group
of
people
would
have.
So
there's
a
there
was
a
voting
in
the
private
pmc
repo.
There
was
a
voting
still
going
on
right.
Then
you
know:
that's
that's
why
the
the
announcement
then
okay,
so
we
decided
that
the
permissions
that
we
should
go
with
is
that
let
me
just
actually
open
the
the
issue
or
actually
remember.
D
Yes,
so,
basically
we're
being
more
permissive
for
country
bothers,
we
are
giving
them
admin
access,
and
this
will
allow
them
to
add
other
people
as
maintainers
as
they
step
down
or
if
they
want
command
tiers,
and
this
was
a
bit
that
was
missing
and
then
the
bug
squad
and
the
security
the
bug
squad
has
right
access
which
makes
them
gives
them
a
permission
to
step
in
as
required.
D
If
there's
issues
that
are
unattended,
did
they
contribute
for
a
long
time
and
the
security
team
also,
although
always
has
admin
full
admin
access
so
that
they
can
act
on
security
issues,
the
the
authors
group
remains
as
as
was
they:
they
should
have
access
to
triage
tickets,
which
means
that
they
can
respond
to
the
tickets.
They
can
create
new
tickets
sign
labels,
things
like
that
and
then
everyone
that
doesn't
have
a
an
account
on
github
has
view
access.
D
A
It's
a
little
tricky
because
there
isn't
actually
a
group
of
maintainers
each
maintainer
has
to
be
added
individually
to
their
project,
so
that
does
make
the
process
of
updating
it
a
little
tricky.
I
spent
some
time
going
through
the
list
of
contributed
projects,
but
we
have
hundreds
of
them.
A
So
I
think
we
we
discussed
previously
how
we
can
use
the
github
api
to
do
some
of
this
cleanup
for
us
when
new
projects
are
released,
so
we
won't
be
doing
it
like
per
batch
for
all
projects,
but
as
soon
as
a
project
gets
a
new
release,
we'll
be
able
to
retroactively
retroactively
fix
that
project,
so
make
sure
that
all
the
groups
are
set
at
the
right
level
and,
if
possible,
to
determine
the
maintainer.
A
We
can
adjust
the
maintainer,
so
my
plan,
for
that
was
to
figure
out
who
created
the
release
and
if
that
person,
if
we
can
give
that
person
maintainer
access
through
their
github
user
account,
then
we'll
do
that.
But
I
don't
know
if
that's
going
to
be
reliable
in
all
cases,
so
we'll
see.
D
If
we
need
humanize,
what
helps,
for
example,
with
the
forum
is
that
we
have
an
integration
with
a
zulip
and
it's
time
that
there's
a
new
forum
posts,
something
gets
added.
If
we
could,
if
we
could
have
a
similar
reaction
to
when
projects
are
added
in
their
contrib
group,
then
one
of
us
which
has
permissions
can
go
and
double
check
because
it's
not
like.
Maybe
we
have
like
five
new
projects
this
week
right
so.
A
So
since
we
made
this
decision,
we've
been
said,
I've
been
sending
it
correctly,
but
anything
that
was
created
before
that
won't
get
the
right
permission
set,
and
I
think
we
can
also
do
this
through
the
api
too,
when
new
projects
are
created,
but
I
haven't
figured
that
out.
Yet
we
do
have
a
project
for
new
releases
fixing
with
new
releases,
and
I
think
that's
I
mean
I
guess
yeah
it
will
be
best.
Even
we
can
find
like
a
way
to
give
someone
a
button.
That's
like
fix
my
project.
That
would
be
great.
D
D
If,
if
you
receive
such
a
notification-
and
you
don't
have
time
to
check
just
ping
me
on
on
zulip
with
a
link
to
the
project
and
that
I'll
do
it.
A
B
Has
another
idea
to
get
that
that
fixed
you
mentioned
the
github
api
is
something
that
could
solve
this,
that
we
could
probably
make
a
shell
script
or
something
like
that.
That
can
be
run
that
retrieves
all
the
information
gets
all
of
the
releases
and
then
updates
the
permissions
for
all
of
them
and
sure
it
might
take
like
a
long
time
to
run
like
10
minutes
or
something
like
that
to
run
through
every
contrib
project.
B
But
once
we
have
such
a
thing,
then
we
could
just
run
it
on
a
regular
basis
to
you
know,
re
correct
all
the
permissions
for
new
projects
as
they
come
in
rather.
B
C
B
A
F
A
Of
the
time,
people
have
not
added
themselves,
so
they
accidentally
remove
their
own
permissions,
which
is
tricky.
The
only
thing
that
I
think
this
isn't
going
to
catch,
and
maybe
why
nate's
option
will
be
better
is
that
some
of
us
do
not
create
a
repository
in
our
own
private,
like
our
own
github
account
and
then
transfer
it
like.
A
If
we
already
are
part
of
backdrop,
can
trip
we'll
just
create
the
new
project
directly
and
contrib
and
those
don't
trigger
a
notification
email,
so
anyone
who's
doing
that
who
might
have
accidentally
forgotten
to
set
the
permissions
the
way
they
want
they're
going
to
get
trapped
too.
So
having
that
retroactive
script,
I
think,
might
be
the
way
to
go.
B
We
found
recently-
or
I
found
recently
on
one
of
my
other
projects-
that
github
actions,
besides
being
able
to
run
on
pull
requests
and
on
issues
and
things
like
that.
It
also
you
can
just
set
it
up
to
run
intermittently,
so
you
can
use
it
basically
as
a
cron
job,
and
so
we
could
set
up
something
at
the
backdrop,
contrib
organization
level.
I
think
that
is
a
github
action
that
just
runs
intermittently
that
just
fixes
things.
A
B
A
B
Sure
other
than
that
are
there
any
other
pmc
updates.
A
B
Okay,
well,
let's
run
quickly
through
the
project
update
project
update
or
current
version
that
we're
working
on
is
117.5.
That's
the
next
bug
fix
release.
B
It's
probably
worth
noting,
since
this
is
only
the
second
meeting
that
we've
had
since
1
17
4.,
that
117
4
was
released
the
day
before
thanksgiving
apologies
again
to
everyone
who
felt
their
holiday
may
have
been
disrupted
by
that
in
the
united
states.
The
timing
really
was
poor,
but
we
were
coordinating
with
drupal
who
was
coordinating
or
responding
to
a
third
party
library,
security
updates.
So
a
little
cascading
effect
of
poorly
timed
security
releases
all
happening
all
at
once.
B
So
117
4
is
has
been
out
for
about
two
weeks
now,
and
so
117.5
is
the
next
thing
that
we're
working
towards
and
we've
got
a
couple
of
issues
to
bring
up
during
the
meeting
that
have
been
making
some
progress.
B
One
of
them
is
issue
4745,
an
issue
with
database
prefixes.
B
The
mysql8
support
that
we
added
in
backdrop
117.2
makes
it
so
that,
if
you're
doing
database
queries
across
databases,
then
that
functionality
does
not
work
in
the
newer
versions
of
backdrop.
In
particular,
this
has
been
affecting
civic
crm
users
when
they
install
civi
in
one
database
and
backdrop
in
another.
Doing
queries
across
them
is
not
working
currently,
so
that
issue
is
47.45.
B
There
is
a
pull
request
there
that
fixes
the
issue
lauren
this
week
marked
it
works.
For
me,
there's
still
some
discussion
happening
about
the
overall
approach
that
we
should
use.
The
pull
request,
that
is,
there
is
affixed
to
the
backdrop,
implementation
there's
some
suggestions,
though,
that
we
adopt
drupal
7's
approach,
which
is
a
different,
a
different
set
of
code.
Basically,
to
accomplish
the
same
thing
also,
it
did
make
me
feel
slightly
better
that
drupal
7
when
they
implemented
mysql8
support.
B
They
made
the
same
mistake
that
testing
querying
across
databases
was
not
something
that
they
had
anticipated
either,
but
it
is
something
drupal
has
always
been
able
to
do
so.
Getting
it
fixed
everywhere
is,
has
been
a
an
issue
or
has
been
a
priority
for
people.
B
Next
up
is
field
set,
css
issue,
47.66
collapsible
field
sets
there.
The
css
for
field
systems
in
general
is
really
difficult
and
we
caused
a
regression
in
a
recent
version
of
backdrop.
B
Actually,
hang
on
there
were,
there
were
a
lot
of
problems
with
field
sets
initially
and
we
fixed
a
bunch
of
problems
with
field
sets
and
we
didn't
fix
all
of
them,
and
so
4766
is
finishing
the
job
that
issue
has
been
marked
rtbc
this
week,
indigo
zello,
zella
and
gregory.
You
guys
have
been
tag
teaming
back
and
forth
on
that
one.
Do
you
have
any
anything
additional
you'd
like
to
say
about
that
issue?.
D
No,
the
the
latest
feedback
is
that
there
are
there's
a
spacing
issue
that
comes
up
in
dialogues
like
in
views
dialogues.
I
think,
but
that's
browser
specific
and
then
into
godzilla
mentioned
that
they
they
don't
want
to
touch
the
the
code
as
it
is
now
and
I'm
happy
to
move
that
to
a
follow-up
like
it's
a
small
issue.
D
B
B
I
think
I
saw
that
there
was
a
forum
post
that
somebody
was
encountering
this
as
well
recently,
so
it's
something
that
would
be
nice
to
to
get
some
eyeballs
on
and,
lastly,
the
one
I
want
to
bring
up
is
setting
them,
setting
the
max
input,
variables,
value
or
actually
warning
people
about
a
max
input.
Variable.
That's
too
low
issue.
3824.
B
A
Yeah
because
there's
a
disagreement
in
the
issue
as
to
whether
we
should
warn
people
before
your
site
fails
or
warn
people
when
your
site
fails,
and
so
I
would
like
more
people,
especially
anyone
hasn't
seen
that
just
to
weigh
in
on
like
how
you
feel
about
the
warning
on
the
status
report
like
does
it
bother
you,
and
would
you
fix
your
site
if
you
knew
it
was
configured
incorrectly?
A
So
I
think
that's.
The
issue
is
that
a
lot
of
people
are
like,
even
though
my
site's
configured
incorrectly
I'm.
I
would
much
rather
run
the
risk,
or
maybe
I
wouldn't
be
able
to
make
the
change
as
required,
and
so
I
don't
want
to
see
the
I
don't
want
the
site
to
tell
me
there's
something
wrong
with
it,
and
so
I
would
love
some
feedback
from
people
who
work
with
a
status
report
page
on
how
you
feel
about
warnings
like
what
does.
What
does
it
mean
to
you
that
there's
a
warning?
A
D
Then,
while
added
like,
if
you
have
some
spare
time
over
the
weekend,
there's
conflicts
with
hd
access.
So
if
people
want
to
spin
that
up
locally
might
cause
them
problem,
if
you
want
to
fix
that
up,
and
it
will
help
with
like
the
the
pr
sandbox-
doesn't
spin
up.
B
Okay,
those
are
all
the
items
I've
got
for
117.5.
There
are
some
other
issues
in
the
agenda,
but
there
have
been
updates
on
them,
so
we'll
skip
right
on
to
the
next
minor
version
of
backdrop,
which
is
118.
B
118.
The
feature
phrase
is,
at
the
end
of
this
month:
it'll
be
coming
out
january,
15
2021,
let's
run
through
the
items
that
we've
got
here,
exposed
file,
name
filter
for
the
media,
library
dialog.
This
is
issue
3293.
That
lauren
is
advocating
for
this
issue.
Mostly,
this
involves
a
bug
fix
of
some
kind
that
we
need
the
ability
to
be
able
to
add
an
ajax
exposed
filter
into
the
media,
library,
dialog,
and
there
seems
to
be
a
problem
with
that.
B
Once
we
get
that
figured
out,
we'll
also
enable
it
by
default
for
new
installations
of
backdrop,
we
got
a
new
contributor
this
week,
el
muche,
which
just
signed
up
this
week,
apparently
on
github,
just
to
post
a
comment
making
some
suggestions
about
how
we
can
solve
this
problem.
So
that
is
super
awesome.
Welcome
to
the
backdrop
community,
we're
really
happy
to
have
you
and
thanks
for
signing
up
for
github
account
just
to
post
those
suggestions
on
how
we
can
fix
that
problem.
So
that's
really
awesome.
B
So
it's
possible
wait.
There
hasn't
been
any
other
updates
after
that
comment,
but
if
we
follow
those
suggestions
that
were
made
by
el
muche,
possibly
will
be
able
to
get
that
issue
rolling
a
little
bit
next
up
is
adding
a
setting
to
the
menu
block
module
to
the
menu
block
for
changing
the
break
point
which
the
hamburger
shows
up
issue
46
63
bw
panda
is
the
advocate
for
this
there's
been
a
lot
more
activity
again
on
this
issue.
B
I'm
not
sure
if
this
was
peter
who
actually
updated
this
in
the
agenda
here,
but
there's
been
several
reviews
from
jen
lampton
and
into
godzilla
and
new
updates
from
bw
panda
yeah
continuing
to
work
through
this
issue.
Let's
see
I
haven't
checked
in
on
this,
it
looks
like
gregory
you've
been
active
most
recently.
Can
you
give
us
an
update
on
this.
D
So
yeah
all
right.
So
sorry
I
was
typing.
I
was
typing
further
down
the
basically
yeah,
so
I'm
the
main,
the
main
pain
point
there.
So
everything
works
as
expected,
we
need
a
final
chord
review.
What
I
there's
a
new
setting
that
is
being
introduced,
and
I
would
like
it
like
to
split
that
up.
That
was
the
latest.
It
can
be
a
follow-up.
D
I
don't
want
to
be
a
pain,
so
I
was
saying
that
the
minimum
width
setting
is
now
a
text
field
and
I
was
proposing
it
to
be
a
separate
number
plus
a
combo
drop
down
which
allows
you
to
put
a
number
and
then
select
the
css
units
so
that
we
don't
need
specialized
validation
or
rejects
to
pick
up
if
it's
a
correct
thing
or
allow,
or
and
also
disallow
setting
a
an
invalid
value
there.
D
D
So
yeah
great,
if,
if
other
people
from
the
community,
like
they're,
enthusiastic
about
you
ux
and
ui
jen,
I'm
looking
at
you
by
the
way
as
well.
When
you
get
a
chance,
if
you
look
through
that
in
time
in
and
then
we
can
sort
of
like
resolve
the
discussion
and
get
it
done.
B
Cool
okay,
great,
we'll
go
on
to
the
next
issue,
which
is
tim's
issue
for
renaming
the
full
html
text
format
to
raw
html
issue:
44.99
tim!
Are
there
any
updates
this
week.
C
Just
what
I
typed
in
the
agenda
last
week,
we
talked
about
this
and
we
seemed
pretty
comfortable
and
optimistic
that
we
could
change
the
machine
name
without
any
problems
and
then
nate.
You
did
a
search
of
all
the
contrib
modules
and
found
a
bunch
of
contrib
modules
have
tests
that
rely
on
the
existing
machine
name
for
the
text
format
so,
and-
and
my
reading
from
your
comment-
was
that
that
meant,
we
probably
shouldn't
change
the
machine
name.
B
C
C
I
mean
I
don't
know
what
the
the
real
real
world
impact
of
that
would
actually
be,
which
might
be
pretty
negligible,
but
so
then
the
decision
is
well.
C
C
The
problem
with
tests
is
not
going
to
affect
site
builders,
yeah,
that's
what
I
was
referring
to.
Yes,
no,
that's
my
point.
The
the
the
the
end
issue
is
primarily
going
to
affect
site
builders,
but
yeah.
So
can
we
or
should
we
change
the
machine
name
and
do
people
feel
comfortable,
changing
the
display
name?
If
we
don't
and
I
I've
gotten
the
sense
that
people
don't
love
the
idea
of
changing
display
and
not
the
machine
name,
but
I
haven't
heard
anybody.
D
C
C
And
you
care
if
we
break
a
bunch
of
tests
in
control
modules,.
B
Modules,
that's
not
totally
true,
there's
some
there's
some
modules
that
actually
like
include
like
defaults.
That
say,
full
html
is
my
default
text
format
for
some
settings
and
stuff
like
that.
So
it's
not
just
tests.
It's
mostly
tests,
but
there's
like
maybe
five
modules
that
also
have
full
html
hard
coded
in
some
place
or
another.
It's
not
a
test.
A
A
D
What's
dope
notices
so
that
we
we
can
say
that
we
have
given
country
buffers
plenty
of
time
to
sort
of
export
the
issue
and
fix
it,
either
make
their
modules
machine,
name
agnostic
when
it
comes
to
the
the
formats
or
use
the
new
one.
E
Is
is
it
possible
for
both
to
live
in
the
same
space,
to
have
the
old
and
the
new
and
then
basically
kind
of
phase
out
the
old
so
give
people
time
to
switch
over
to
the
new
but
still
have
be
backwards,
compatible
with
the
old
machine
name?
And
then
it's
like
on
this
date.
We're
gonna,
kill
the
old
machine
name.
A
B
Yeah
and
as
always,
we're
not
even
affecting
existing
sites
if
they
have
full
html
and
it's
called
flight
html
it'll
stay
that
way.
This
is
all
only
something
that
would
affect
new
sites.
It
just
so
happens
that
new
sites,
like
the
tests
that
are
run
for
contrib
modules,
they
are
run
on
fresh
installations
that
assume
that
full
html
exists
and
same
with,
like
some
of
those
configuration
options
that
assume
full
html
exists,
which,
admittedly,
now
that
I'm
saying
it
out
loud.
B
D
Yeah,
the
other
thing
is
that
we
can
look
at
the
usage
stats
of
those
modules
and
then,
if
it's
five
modules
out
of
700.
G
G
Go
ahead,
joseph
so
could
we
change
the
ui
in
1.18
issue,
a
change
record
and
then
change
the
machine
name
in
1.19.
A
A
E
B
But
but
I
I'm
with
everybody
else,
I'm
struggling
with
the
what
I
want
versus
what
we
say
that
we
do
you
know,
and
so
I
I
mean
based
on
our
policies
and
our
philosophy,
like
we
shouldn't,
be
changing
something
that
could
break
someone's
site
at
all
during
a
minor
release,
and
our
2.0
policy
is
that
you
know
we
have
a
long
time
before
2.0
comes
out,
so
I
think
we're
all
trying
to
figure
out
how
to
make
things
work
in
the
meantime.
C
So
could
we
change
this
pull
request
to
just
change
the
display
name
and
open
up
a
new
issue
to
solve
the
other
question,
assuming
that
at
the
minimum
it
gets
changed
in
2.0.
But
if
we
can,
you
know
that
maybe.
C
B
And
we
could
possibly
make
a
change
record
that
says
that
you
shouldn't
never
be
hard-coding
text
format,
names
in
tests
or
in
your
module,
and
then
we
could
recommend
the
alternatives
which
is
like
set
up
the
text,
format
in
your
test
setup
function
or
if
you're,
a
module
like
on
hook,
install
get
the
default
text
format
and
use
that,
based
on
the
current
site,
setting
rather
than
hard
coding
in
your
config
file.
So
there's
definitely
like
solutions
that
are
out
there.
B
F
B
E
A
quick
question
on
this:
if
have
any
tests
been
done
to
check
to
see
if
that
h,
the
machine
name
already
exists.
B
E
No,
no,
no.
What
I'm
saying
is,
for
example,
on
one
of
my
sites.
I've
got
a
filter,
a
text
filter
that,
for
me
it's
labeled,
html
and
then
quotes
I've
got
raw
and
I
was
sitting
there
thinking
about
it
going
man
did
I
create
one,
that's
called
raw
html.
Do
I
have
a
machine
name
that
is
now
raw
html?
So
I
I
don't
know
if
there
may
be
other
folks
out
there
who
have
done
that
and
something
to
think
about
for
changing
the
machine
name
in
the
future
is
doing
a
check
on
that.
Hey.
A
B
B
All
right,
let's,
let's
move
on
from
that
one
yeah.
C
C
C
A
Something
you
go
to
the
process
for
a
not
good
developer
like
I
don't
watch
change
records
because,
like
I'm
working
on
something
on
one
of
my
own
modules
and
something
breaks
and
I'll
like
take
a
string
off
of
my
broken
website
and
I'll
plunk
it
into
the
search
box
on
the
api
site,
and
if
there
is
a
definition
of
that
function,
it
comes
back.
A
If
there's
a
change
record,
it
also
comes
back,
and
so,
if
I
see
a
change
record,
it'll
be
like
oh
aha,
something
about
this
thing
has
changed
and
you
click
on
it.
And
then
it
says
this
is
your
code
before
this
is
your
code
after
so
I
copy
and
paste
the
after
code
into
the
place
in
my
site,
that's
not
working,
and
then
I
hope
it
works,
and
so
I
don't
necessarily
have
to
know
that
there
are
change
records
there,
I'll
stumble
across
accidentally
by
using
this
little
box.
B
Approach:
okay:
next
up
is
advanced
caching
issue
4127.
joseph
you're.
The
advocate
for
this.
Do
you
have
any
updates
this
week.
B
Okay,
we'll
move
on
then
next
up
is
adding
webp
support.
A
new
image
format,
issue
4509
indigo
zala
is
the
advocate
for
this
issue.
It's
been
rtbc
now
for
over
a
week,
so
that's
super
awesome
that
that
issue
looks
like
it.
It
mostly
just
needs
the
last
set
of
eyeballs.
Sorry
justin.
I
couldn't
tell
whether
or
not
you
were
showing
us,
your
daughter
or
your
pie
that
you're
eating
so.
B
All
right,
let's
see
next
up,
is
update
ui
issue
4345
jen
lampton
you're.
The
advocate
for
this
any
updates.
B
Okay
and
next
up
is
broadly
support
for
css
and
javascript
compression
phil,
okay
you're
still
here.
I
saw
that
you're
interested
in
this
one
possibly
becoming
the
advocate
for
it,
so
that
we
can
start
bringing
up
and
mentioning
it
during
these
meetings.
Does
that
sound.
E
Yeah,
it's
it's
basically,
a
very
small
fix
that
needs
to
happen
in
the
htaccess
file,
and
I
know
we
all
hate
when
there's
htaccess
changes,
because
that
means
you
literally
have
to
touch
every
single
site
that
you
deal
with
the
nice
thing
is
that
if
your
hosting
platform
does
not
currently
promote
broadly
as
the
compression
method,
it
doesn't
affect
you
to
not
add
the
change
and
for
kind
of
a
quick
backup
to
explain
what
broadly
is
for
those
of
you
that
don't
know
so.
E
1992
gzip
came
out
and
from
1992
until
2013
it
was
the
de
facto
for
the
compression
logarithm
2013
google
came
out
with
brockley
as
a
contender
as
a
faster,
smaller
file,
size,
alternative
to
gzip
and
so
doing
some
research.
It
is
supported
on
all
kinds
of
servers.
It
is
supported
on
pretty
much
every
major
browser
as
being
from
the
the
dynamic
side
you
know.
So
if
the
server
is
dynamically
compressing
the
file
as
it's
being
sent
most
your
browsers
can
handle
it
right.
E
So,
in
the
issue
that
I
created
on
this
there's
a
little
bit
of
back
and
forth,
I
I
believe
the
gentleman
that
I
was
kind
of
going
back
and
forth
with.
I
don't
think
he
fully
understood
what
I
was
trying
to
accomplish
with
this,
and
so
he
was
kind
of
advocating.
Well.
Why
are
we
trying
to
add,
for
you
know
all
these
different
compression
logarithms
and
my
thought
is,
we
need
to
add,
we
need
to
add
them
so
z,
standard
which
is
by
facebook.
E
That's
another
contender
in
this
space
that
does
not
have
browser
or
server
exposure
yet,
but
it
may
come
up.
You
know
down
the
road,
so
that's
something
else.
We
may
need
to
look
at
and
say
hey.
Yes,
we
need
to
add
this
for
z
standard
if
hosting
companies
start
to
provide
that
as
as
the
compression
method.
So
anyway,
it's
very
small
change
in
hd
access.
All
we
need
to
do
is
basically
tell
the
htaccess
or
tell
apache,
don't
double
compress
the
the
gzips
files.
E
You
know
the
the
css
and
the
the
javascript
just
like
what
we're
currently
doing
with
the
gzip.
So
that's
it's
a
small
change.
I
don't
know
how
to
create
the
pull
request
and
github
since
I'm
not
a
coder
by
trade.
So
basically
I
what
I'm
requesting
is
somebody
can
kind
of
come
in
and
say:
oh
yeah,
that's
easy
fix.
I
can
get
the
pull
request
done
and
I
I'd
like
to
I'd
like
to
see
it
come
in
fairly
soon.
You
know
it
does
affect
new
sites
that
are
on
newer
hosting
platforms.
E
I
believe
it's
cloud
fair,
I
think
they're
pushing
broadly
by
default,
so
you
know
for
new
users
that
are
new
to
to
backdrop
or
you
know
this
affects
drupal
as
well,
but
you
know
you
put
this
out
on
site:
it'll
flat
out
break
the
site,
your
your
themes,
just
don't
work
and
it's
kind
of
like.
Why
are
my
themes
not
working?
Well,
it's
because
of
this
double
gzip
problem
got
it.
D
B
This
is
actually
a
bug
like
that.
If
your
web
server
is
using
broadly
that
backdrop
has
some
problems,
yeah
right,
yep,
and
so
this
isn't
really
even
adding
broadly
support-
it's
literally
just
made
so
that
the
css
and
javascript
compression
that
we're
doing
right
now
doesn't
conflict
with
broadly,
if
your
server
has
it
and
so
yeah
yep,
I
you're
right
in
all
counts
here.
Phil,
and
this
doesn't
even
look
like
it's
it's
difficult.
It's
I
mean
just
a
couple
of
lines
so.
B
Looks
great-
and
I
also
think
it's
nice
that
I
mean
sure
people
will
need
to
update
their
hd
access
files
you're
totally
right
people,
don't
like
updating
those
things.
However,
if
they
don't
update
it,
it's
probably
not
an
issue
for
them
like.
F
D
D
And
if
we
get
the
hd
access
chains
for
the
minimum,
advising
people
are
going
to
change
their
hd
access
files
anyway,
in
this
release,
this
might
be
a
good
chance.
B
To
do
them
all
at
once,
yeah
yeah
sounds
great.
This
doesn't
need
to
be
a
118
issue.
This
should
be
in
in
the
117
5
issue,
because
it's
not
it's
it
does.
It
doesn't
have
any
api
issues.
It's
a
bug,
fix
and
yeah.
We
can
make
hd
access
files
in
bug
fix
releases
if
they
are
indeed
fixing
bugs,
which
this
is.
C
Good,
although
could
we
argue
that
we
want
to
double
up
the
htaccess
stuff
and
release
them
at
the
same
time.
So
if
the
next
bug
fix
release
comes
out
before
the
next
major
release
we
might
be
needing
or
is
the
other
fix
going
to
be
in
the
bug,
fix
release.
D
A
A
B
Okay,
okay!
Well,
in
any
case,
there's
there's
a
really
good
chance
that
the
next
bug
fix
release
and
the
next
minor
release
are
going
to
be
the
same
thing
anyway.
So.
C
B
Too
much
stress
yep,
all
right,
let's
see
and
a
new
one
here
that
has
been
added
to
the
agenda,
merge
all
of
the
update
core
module
theme
layout
pages
into
a
single
page,
gregory
you're.
The
advocate
for
this
one
status.
D
Yeah,
so
I'm
I'm
pretty
close,
like
99
close
to
a
pr
I'm
trying
to
ignore
my
ocd's,
because
that
we
are
doing
like
we
have
inherited
horrible
things
from
drupal,
so
I'm
trying
to
I'm
trying
to
get
the
minimum
things
fixed
so
that
this
can
work.
I
currently
have
only
a
screenshot
from
my
local,
but
I'm
almost
there
and
over
the
weekend
I'll
file,
a
pull
request
and
request
for
feedback
and
testing
yeah
and
there's
going
to
be
a
lot
of
follow-ups.
That's
what
I'm
saying
so.
D
B
You
can
put
that
at
deprecated
doc
block
to
use.
D
One
one
important
thing
is
that
that
I
saw
is
that
the
function
that
retrieves
the
the
helper
functions
that
retrieve
the
available
updates
for
separate
project
types
like
the
themes,
modules
and
layouts.
They
repeatedly
do
the
same
thing
for
core,
so
there's
an
unnecessary
anyways.
But
it's
not
it's
scope
crypt
for
that.
But
it
was
right
on
my
face
when
I
was
fixing
things
but
yeah
like.
D
B
Okay,
well,
that's
it
for
the
118
issues.
We
also
have
initiative
updates.
I
think
the
well
luke
is
here
as
well.
Maybe
we
should
just
ask
you
first
luke
anything
on
ready
to
wear.
D
H
No,
no,
no,
no,
no
believe
it
or
not.
There
is
okay
I'll
I'll.
Do
the
the
quick
version
of
what
we
did
a
more
extensive
thing
in
the
outreach
meeting,
but
but
the
the
the
short
story
is.
Is
we
had
a
a
a
meeting
on
tuesday
to
sort
of
shuffle
around
and
see
how
close
it
was
and
and
with
with
with
a
little
bit
of
sort
of
aggressive
scope
management?
H
We
we
took
what
was
had
been
a
pretty
amorphous,
unmoving
blob
of
vague
ideas
and
peeled
off
a
bunch
of
things
that
had
just
been
done
already.
Then,
since
we've
been
kind
of
looking
at
it,
just
people
have
gone
and
fixed
things
and
pieces
that
we
could
push
to
later
mvp
and
arrived
at
a
perfectly
reasonable
mvp.
H
That's
were
half
done
making,
which,
which
is,
is
basically
going
to
be
just
a
a
website
running
on
simple
that
that
answers
that
that
that
ready-to-wear
question
of
how
do
you
create
a
backdrop
site
without
having
to
write
custom
themes?
The
answer
will
be
like
go
to
the
website
and
here
use
one
of
these
themes.
H
Here's
what
they
are
plug
them
in
so
so
once
and
and
the
the
website
that
we're
we're
working
on
currently
has
you
uses
the
theme,
switch
module
that
you're
supported
for
us
and
and
it's
not
bad
for
for
subsequent
versions.
There,
there's
user
interface
improvements
that
that
are
bouncing
around
and,
and
you
know,
other
issues
that
we're
going
to
tackle,
but
to
sum
it
up
kind
of
quickly,
the
the
initial
mvp
is
an
external
website
that
we're
have
done
building.
H
If,
if
it's
a
hit,
we
can
eventually
roll
it
into
like
the
core
backdrop
site.
If
it's
not,
we
can
just
forget
about
it,
but
either
way,
we'll
have
something
to
look
at
soon.
If
I
manage
to
stick
with
it
like
a
week
or
two.
B
Great
great,
so
it
sounds
like
also
if
people
are
interested
there's
the
previous
meeting
prior
to
this
one.
That
has
a
lot
more
information
on
that
topic
as
well.
Awesome
thanks,
luke.
B
Information
and
let's
see
lastly,
we
have
telemetry-
is
the
other
update
or
another
initiative
that
is
in
progress.
Tim
any
changes
this
week.
C
Unfortunately,
not
I
know
that
phil
has
some
ideas
about
telemetry
phil
I'd
just
like
to
say,
I
think
we're
I
think
you've
got
some
interesting
ideas,
but
for
the
initiative
our
goal
is
just
to
really
mvp
for
for
the
next
release
and
we
want
it
and
those
are
like
in
the
in
the
queue,
your
ideas.
So
I
don't
know
if
you
want
to
mention
them
real,
quick.
E
Yeah,
the
the
main
idea
that
I
have
is
to
add
telemetry
into
the
backdrop
upgrade
status
module
itself,
pretty
much
set
it
up
as
an
inclusion
to
be
able
to
send
the
the
telemetry
back
to
backdrop.
But
the
question
I
think
we
need
to
decide
on
is:
do
we
handle
the
telemetry,
so
you've
got
the
backdrop
telemetry
and
then
you've
got
this
upgrade
status,
module
telemetry.
Do
we
want
all
of
that
handled
in
one
place,
or
is
it
worth
breaking
the
the
collection
into
two
separate
places
that
way?
E
E
So
I
I
think
if
we
did
two
pieces,
it's
a
little
bit
more
work.
Yes,
but
it
also
means
that
we
can
focus
on
the
telemetry
here,
I'm
sorry
the
upgrade
status.
We
can
focus
solely
on
that
and
then,
when
we
get
time
to
deal
with
the
overall
backdrop
telemetry,
then
you
know
that
that
can
be
handled
on
a
on
a
separate
type
of
an
issue.
E
But
the
nice
thing
about
putting
them
together
is
it
begins.
Creating
that
foundation.
It's
just
going
to
take
longer.
You
know
to
get
the
upgrade
status
up
and
rolling
into
this
whole
idea.
So
the
main
idea
with
upgrade
backdrop
status
is,
I
know
I
said
that
wrong,
but
the
main
idea
is
to
figure
out
who's
using
what
modules
on
drupal
and
start
collecting
that
information
over
the
next
say
six
months
to
a
year
and
then,
as
people
begin
to
join
into
the
community,
they
can.
E
We
can
take
a
look
and
say:
hey.
You
know
these
modules,
they
need
a
lot
of
attention,
whereas
we
get
one
person
that
comes
in
the
forum.
Oh,
I
use
this
module
and
we
come
over
and
look
at
it.
It's
like
yeah,
there's
three
people
that
use
that
entire
module
and
I'm
not
saying
that
we
should
push
those
three
people
out,
but
it
I
think
it's.
E
B
Maybe
I'm
I'm
missing
something
phil,
but
I
mean
with
the
update
module
already
tracking
installs
of
projects.
Don't
we
have
that
information
already
about
like
who's
using
what
contrib
projects
we
we
can
tell
how
many
people
are
using
a
contrib
project.
That's
a
backdrop
right,
yeah
yeah,
at
a
certain
level,
yeah.
E
C
Which
modules
need
to
be
reported?
The
idea
is
that
the
only
people
running
that
are
people,
considering
that
our
drupal
user
is
considering
backdrop,
so
this
would
be
a
way
of
like
finding
out
what
prospective
drupal
or
backdrop
users
on
drupal
are
looking
for
when
they,
when
they
run
the
module.
It
seems
like
an
interesting
idea
to
me.
I
just
can't
wrap
my
head
around
it
right
now
because
of
all
the.
C
B
Yeah,
I
see
it's
it's
it's.
A
B
B
Yeah
interesting
because
the
telemetry
api
can
send
it,
any
information
actually
gets
a
little
bit
complicated,
because
the
source
of
the
data
would
actually
be
coming
from
a
drupal
site,
not
from
a
backdrop
site,
but
it
would
probably
be
possible
to
do
anyway.
You
just
wouldn't
be
able
to
use
like
telemetry
module
and
backdrop.
Core
would,
of
course,
be
the
one
sending
the
requests.
So
that
would
only
exist
within
backdrop,
but
there
could
be.
A
E
So
my
my,
I
guess
my
main
question:
what
I'd
like
to
try
and
figure
out
do
we
want
this
to
go
ahead
and
go
into
the
the
api
of
the
telemetry
and
build
out
have
that
part
of
the
telemetry
foundation?
Or
do
we
want
to
treat
this
as
kind
of
a
separate
thing
create
just
a
really
small,
very
pointed
place
where
this
information
gets
collected
that,
yes,
it
is
telemetry,
but
it's
not
part
of
the
actual
telemetry
initiative.
So
it's
not
going
to
build
on
the
foundation
and
the
apis
of
the
telemetry
initiative.
E
A
E
F
A
B
It
is
it's
I
mean
in
the
issue.
There
is
a
pull
request
over
to
project
module
and
a
pull
request
against
core
and
the
pull
request
against
project
module
is
where
telemetry
server
lives.
I
think
it's
called
project
telemetry
is
the
because
it's
getting
added
to
project
module,
but
yes,
that
exposes
new
rest.
Apis
that
backdrop
backdropcms.org
will
provide
and
fill
it.
B
But
if
it
turns
out
to
be
like
a
big
barrier
or
hindrance,
then
we'll
probably,
you
know,
be
like
well.
You
know
we
looked,
you
know
we
probably
won't
hold
up
everything
over
it,
but
if
it's
easy
to
accommodate
for
something
in
the
future,
we
should
definitely
be
planning
for
it,
but
yeah
and-
and
all
that
we
need
to
do-
is
look
at
the
the
json.
Apis
really
are
the
main
key
thing
here
and
that
module
does
expose
like
rest
api.
E
So
again,
just
for
being
on
the
record
here,
I'm
not
a
code
or
nothing,
so
I
may
throw
out
some
goofy
lingo,
but
I
guess
the
way
I
would
approach
the
the
backdrop
upgrade
status
is
to
take
a
take,
a
poll
of
the
modules
that
are
on
the
drupal
website
and
then
just
fire
off
a
json
file.
E
Maybe
maybe
that's
where
the
rest
comes
in
and
and
I
kind
of
understand
how
that
works,
but
I'm
not
real
familiar,
but
basically
we
just
send
a
json
file
over
to
the
collection,
server
and
just
upload
that
file
and
from
there
it's
like.
Okay,
we're
now
going
to
extrapolate
what's
in
this
json
file
and
then
put
it
into
a
pretty
table.
So
we
can
look
at
it.
I
mean.
E
I
guess
the
kind
of
cut
and
dry
of
what
I
would
envision
this
thing
to
to
do
so
I
don't
think
it'd.
D
E
E
So
we
can
make
better
informed
decisions
on
the
backdrop
side
so
that
we
can
try
to
get
backdrop
more
to
a
migration
status
for
these
drupal
users,
and
you
know,
instead
of
a
year
and
a
half
out
hey,
we
got
a
bunch
of
these
ported
and
now
we
can
get
a
whole
bunch
of
websites
over
in
one
fell
swoop,
because
a
lot
of
these
have
been
ported.
So.
D
Yeah,
it's
not
only
contribute
there's.
These
features
that
we
are
discussing.
They
are
currently
in
contribute
in
seven,
but
we
have
issues
on
our
queue
for
inclusion
in
core.
So
we
might
need
to
prioritize
that
if,
if
we
realize
that
a
lot
of
sites
have
those
control
modules.
F
B
Okay,
all
right
anything
else,
tim.
A
A
B
Of
wrap
things
up
last
thing,
I'd
like
to
discuss
on
the
call,
or
at
least
on
the
video
is
sprints
and
tim
you're.
Also,
our
point
person
for
organizing
code
spreads
for
the
next
couple
of
weeks
before
code.
Freeze,
anything
you'd
like
to
say.
C
Yes,
real
quickly,
people
could
give
me
feedback
in
zulu.
I
went
ahead
on
my
own
calendar
and
penciled
in
two
sprints
and
I
just
want
feedback
if
people
have
better
ideas.
Just
a
second
I'm
trying
to
remember
which
keystroke
to
get
me
to
my
calendar,
I
was
gonna
suggest
that
we
do
one
the
13th,
which
would
be
this
coming
saturday.
The
sunday
excuse
me
and
another
one.
C
The
january
2nd,
on
saturday
the
day
after
new
year's
day,
and
if
people
have
quick
thoughts
right
now,
they
can
share
them.
Otherwise
we
can
talk.
I
mean
I
can
just
start
public
publicizing
them
and
give
me
feedback
if
a
different
day.
You
know
if
sunday's,
just
I
did
one
on
saturday
and
one
and
sunday
if
people
feel
like
saturdays
are
better
and
we
should
do
them
both
on
saturdays,
that's
fine
with
me
or
vice
versa.
D
Yeah,
I
was
thinking
that
a
few
weeks,
like
maybe
two
or
three
weeks
prior
to
the
feature
freeze,
we
may
want
to
do
consecutive
weekends
and
alternate
between
saturdays
and
sundays,
so
that
we
give
the
option
to
be
for
people
that
cannot
join
on
sundays
to
join
on
saturdays.
The
next
weekend.
C
Sure
so
we
could
do
more
of
them,
although
with
not
the
expectation
that
everybody
participates
in
everyone,
but
if
we
do
that,
you
know
I'd
want
people
to
sort
of
volunteer
to
to
be
the
host
for
some
of
the
extra
ones.
The
other
thing
is
I've
been
thinking
about,
resurrecting
the
office
hours
time
slot
for
for
sprinting
and
looking
for
volunteers.
That
can
be
there
during
that
time.
So
that's
wednesdays
at
three
o'clock
or
wednesdays,
at
1
p.m.
Pacific
time.
C
Does
anybody
feel
like
having
that
time
available
just
every
week
would
be
useful
again?
My
idea
there
is
it's
more
about
people
having
having
somebody
around
if
anybody
has
questions
or
wants
to
kind
of
like
core
mentoring
was
for
drupal
sort
of
like
a
core
mentoring
office
hours.
So
it's
not
so
much
that
I
expect
a
bunch
of
people
to
show
up
on
a
given
wednesday,
but
that
we
have
somebody
available
to
answer
questions
and
to
help
people.
B
I
think
it's
a
positive
thing,
having
the
regular
hours
and
and
separately,
I
like
the
schedule
you
proposed
of
the
first
one
being
on
sunday
and
then
the
next
one
being
on
saturday,
okay,
and
that
that
one
january
2nd
the
saturday
one
it's
preceded
by
friday,
which
is
also
a
holiday
january
1st,
so
and
and
then
proceeded
by
another,
followed
by
another
day,
sunday,
the
the
third.
So
I
think
I
think
that's
a
great
day
to
to
to
do.
I
I,
like
your
schedule,.
C
Good,
I'm
just
gonna.
Actually
I
think
I
already
just
put
these
things
on
the
backdrop
google
calendar,
which
only
jen
and
I
look
at,
but
but
I
will
publicize
them
more
widely,
get
them
on
backdrop.org
and
yeah
again
they're,
just
some
they're
an
opportunity
for
folks
to
come.
C
People
can
obviously
sprint
whenever
they
want,
and
I
think
that
final
weekend,
that
probably
some
people
will
be
sprinting
all
weekend,
but
by
picking
a
focused
that
you
know
a
focus
day
that
that
will
be
helpful
for
some
people
so
yeah
exactly
on
this
similar
topic,
we
did
a
a
I
just
like
some
quick
feedback.
If
I
should
do
this
again,
it's
in
zulup
last
release
cycle.
C
I
did
a
blog
post
saying,
help
wanted
for
the
1.17
release
and
gave
everybody
the
opportunity
to
say
here
are
my
favorite
issues
and
the
response
to
that
idea
was
pretty
enthusiastic.
We
we
we
published
it.
We
unpublished
it
after
the
release,
because
the
data
seemed
kind
of
old
and
I
just
want
to
know
people
feel
like
that's
worth
trying
again.
C
I
don't
know
if
it
had
much
of
an
impact
on
anybody,
but
I
have
a
draw
draft
blog
post
ready
to
go.
Does
anyone
object
to
trying
that
one
more
time
and
seeing
okay?
So
the
only
thing
I
need
from
people
is
just
to
give
me
their
issues.
What
are
the
issues
that
you
really
want
people
to
look
at
in
this
release
cycle
so
and
then
we
can
tweet
about
it
and
it's
just
in
theory.
C
It's
a
place
to
to
sort
of
draw
in
new
folks
or
folks
that
aren't
coming
to
these
meetings
and
show
them
what
you
know.
What's
on
all
of
our
agendas,
and
it's
also,
in
my
view,
just
a
chance
for
us
all
to
think
about
beyond.
Maybe
the
issue
we're
advocating
what
are
the
one
or
two
other
things
that
we
would
really
like
to
see
get
in?
C
Okay,
that's
all!
We
don't
need
to
discuss
that
any
further.
Just
ping
me
on
and
zulap
with
your
with
your
issues.
B
Okay,
I
think
that's
it
justin.
I
think
we
still
want
to
talk
about
server
stuff,
but
we
can
do
that
after
the
official
meeting
ends.
You
guys
have
anything
else.
You
guys
would
like
to
talk
about
before
we
close
okay.
Well,
thank
you
guys
all
for
joining,
really
appreciate
presence
here
today
and
all
the
feedback
and
all
the
work.
That's
happened.