►
From YouTube: Backdrop Weekly Dev Meeting - July 29, 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).
B
Oh
hey
it's
thursday
july
29th,
and
this
is
our
weekly
developer
check-in
meeting
for
backdrop.
Before
we
get
into
the
agenda,
we
should
go
around
and
do
some
quick
introductions.
I
will
start
my
name
is
jen
lampton
and
joining
us
from
less
warm
and
unusual
oakland.
California-
and
I
just
mentioned
before
we
started
this
meeting,
but
I'm
really
excited.
I
was
looking
in
the
backdrop
contrib
queue
and
we
have
this
pinned
issue
called.
B
How
are
we
doing
so
far
and
I
realized
that
there
were
like
10
or
15
modules
on
there,
that
we
had
that
weren't
checked
off
in
our
checklist,
so
that
made
me
really
excited
this
morning.
We're
doing
a
lot
better
than
I
thought
we
were
so
yay.
Let's
see
luke,
let's
go
with
you
next.
C
I
usually
do
business
analysis
and
product
management
type
things,
but
I've
been
doing
some
coding
lately,
so
I'm
actually
poking
around
looking
for
a
little
more
coding
style
things
than
I
normally
do.
One
thing
that
brings
me
here,
I'm
I'm
basically
looking
for
for
stuff.
I
might
be
able
to
do.
D
I'm
joseph
flatt
from
las
vegas
nevada
back
in
developer,
working
on
all
kinds
of
things.
Just
you
know
hoping
to
help
out
where
I
can
and.
E
Olaf,
I'm
olaf
grovinski
from
hamburg
in
germany
and
I'm
back
from
vacation,
and
it
was
very
nice
and
now
I'm
yeah
chiming
in
again
and
have
one
issue
which
which
I
would
like
to
discuss.
It's
about
a
small
regression
which
we
had
in
the
last
release.
A
All
right
yeah
and
I'm
nate
lampton
from
oakland,
california,
I'm
court
committer
and
that's
all
today
back
to
you
jen.
B
Welcome
back
from
vacation,
where
I'm
personally
really
glad
to
steer
back
so
hey,
let's
see
in
community
this
week,
we
have
a
new
application
to
join
our
contrib
group.
Somebody
named
james
scott
ported,
the
membership
entity,
module
and
the
port
looks
amazing.
So
thank
you
james
for
working
on
backdrop
and
contributing
your
projects
back.
This
is
an
addition
to
we
had
a
new
controversial
last
week
too,
so
I
think
it's
great
that
we're
getting
a
whole
bunch
of
new
people
contributing
stuff.
B
So,
based
on
issues
requested
to
be
added
to
the
agenda
this
week,
the
first
one
is
issue
number
5138,
which
is
that,
on
the
main
configuration
page
we're
now
seeing
strange
icons,
I
don't
know
nate
noel.
If
you
were
just
working
on
this
to
either
one
of
you
wanna
give
us
an
update.
E
Yeah,
okay,
so
after
the
last
release,
yeah
several
people
noticed
that
on
the
main
configuration
page
and
where
we
have
it's
quite
a
special
administration
page
because
it
has
particular
icons
for
each
section,
and
these
icons
now
look
very
strange.
So
they
are
displayed
repeatedly
and
also
very
big.
And
you
can't
read,
actually
read
the
headings
of
the
sections,
and
this
was
introduced
by
a
commit
of
the
last
release
where
we
fixed
the
dashboard
page.
E
E
Yeah
me
and
few
other
people
discussed
how
to
fix
that,
because
indigo
sailor
who
made
the
commit
for
the
dashboard
page,
I
said
he
didn't
want.
He
was
a
bit.
E
She
was
a
bit
frustrated
because
yeah
handling
with
css
in
the
themes
in
the
core
themes
is
always
a
bit
dangerous,
and
so
she
said
I
won't
make
it
pr,
and
so
we
discussed,
however,
a
bit
about
an
approach
how
to
fix
it,
which
is,
I
think,
quite
important,
and
so
the
current
approach,
which
is
which
I
like,
is
to
partly
revert
the
last
comment
regarding
the
dashboard
and
but
not
totally
and
add
some
lines
and
I've
tested
it
locally.
It
works.
A
Yeah
I
I
was
leaning
towards
totally
reverting
it
just
because
when
we
have
a
regression
like
that's
the
option
that
is
always
available
to
us
is
fully
reverting
it.
But
if
you
think
you
already
have
a
solution
that
will
work,
and
that
is
easy.
Then,
let's
file,
if
if
you
would
file
that
pull
request
and
then
we'll
review
that
first
and
if
it
and
if
it
like,
has
other
issues,
then
we
can
look
at
just
doing
a
full
revert
yeah.
A
But
I
totally
understand
your
frustration
there
that
we're
sharing
the
same
css
between
two
different
pages
and
there's
no
like
specific
class
to
differentiate
the
two
of
them.
And
so
that's
why
we're
getting.
B
A
Trouble
so
a
longer
term
fix
would
be
better
specification
on
the
wrapping
divs
to
like
differentiate
between
like
slash
admin,
admin
config,
which
are
the
two
pages
that
we're
seeing
these
weird
icon
issues
on
and
and
the
dashboard,
because
right
now,
they're
both
sharing
the
class
admin
panel
and
that's
where
we're
getting
into
all
of
these
troubles.
A
E
Different
icons
for
each
each
section
but
and
it's
a
h3
heading
and
on
the
dashboard,
the
h3
heading
is
at
another
place
without
any
icons.
So.
E
There
are,
they
are
both
special
cases,
it's
only
in
the
dashboard
in
the
welcome
block,
which
is
has
three
headings
in
it,
which
is
not
the
case
on
other
pages.
So,
and
this
one
would
get
the
icons
if
we-
and
that
was
a
commit
for
the
dashboard.
E
E
It
would
be
good
if
every
admin
page
or
at
least
the
special
ones
like
dashboard
and
game
configuration,
got
a
body
class
of
their.
B
It
might
also
be
good
if
we
added
the
class
to
the
thing
that's
different
so
like
obviously,
the
welcome
block
is
a
special
case
so
that
maybe
we
should
add
a
class
to
those
h3
tags.
So
we
can
identify
them
differently
from
all
other
h3
tags,
rather
than
the
page
might
be
too
far
away.
E
It
would
be
possible,
but
now
currently
this
situation
is
the
the
dashboard
block
s
class,
which
is
usable
on
the
configuration
page.
We
have
classes
like
admin
panel,
people,
h3
admin,
panel,
content,
h3
and
so
on.
So
there's
not
a
general
class
and.
E
Yes,
but
there
are
a
lot
of
them
for
each
section,
so
it's
not
a
solution
based
on
that
would
be
a
lot
of
code
so
and
yeah.
Also,
if
you
compare
these
pages,
the
classes
on
the
single
elements
are
handled
very
differently,
because
I
think
they
were
added
in
different
situations,
and
the
person
in
question
found
a
special
solution
in
this
moment.
So
I
think
we
should
now
fix
it
in
this
easy
way,
like
I
suggested
and
then
later
in
a
follow-up
yeah,
compare
these
admin
pages
and
look
for
a
better
long-term
solution.
E
A
A
A
119.2
recently
was
that
that
was
last
wednesday.
Yeah,
that's
right.
So
a
little
over
a
week
ago,
we
released
that
and
that
included
a
security
update
and
several
other
changes
that
had
been
pending.
This
is
119.2
is
the
is
the
release
that
has
this
display
issue
on
some
of
the
admin
pages.
So
it's
not
a
bad
regression,
but
it's
one
that
looks
bad
because
you
know
our
css
is
going
all
wonky,
so
we'll
try
to
work
on
fixing
that
issue
as
it's
a
regression
and
119.3.
A
That
issue
that
olaf
and
jen
were
just
talking
about
is
5138
other
items
for
1193.
We
don't
have
any
that
are
highly
prioritized.
I
say
highly
prioritize
ones
that
we
talk
about
during
the
meeting.
However,
there
are
75
open
issues
that
are
tagged
with
1193,
so
I
can't
really
say
that
there
aren't
any
that
are
are
not
that
are
important.
A
We
do
have
one
two,
three,
four,
five
rtpc
issues.
Thank
you.
Everybody
for
pushing
items
towards
that
status,
I'll,
take
a
look
at
these
and
get
them
in
as
soon
as
possible
looks
like
these
are
all
five
of
them.
One
119.3
issues.
A
So
it's
very
exciting.
Let's
see,
I'm
not
sure
any
of
these
need
mentioning
if
they're
all
rtbc,
then
maybe
they
don't
need
to
be
discussed
because
they'll
all
be
going
in
soon.
A
Let's
see,
we
have
full
php
8
support,
issue,
50
76
that
could
use
some
attention.
Luke.
If
you
I
heard
you
mentioned
the
beginning,
that
you
were
looking
for
something
to
do
full
php
8
support
would
be
a
great
issue
to
undertake
it's
issue:
50
76.,
the
process
that
we
have
there
for
php
eight
fixes.
A
A
There's
also
some
drupal
issues
that
we
can
directly
cross-port
that
haven't
been
pulled
in
yet
as
well
that
issue
5076
gregory
linked
over
to
an
issue
that
covers
some
of
those,
so
some
straightforward
cross
ports
that
could
be
done,
but
yeah,
let's
get
all
of
the
tests
working.
A
Okay,
that's
it
for
119.3,
no,
no,
really
big
items
there.
A
A
A
Current
status
on
it
is
unchanged.
Indigozella
gave
a
pull
request,
review,
there's
a
couple
of
issues
with
the
implementation,
but
we're
getting
really
close
there.
It's
it
inserts
one
image,
but
if
you
try
to
cancel
it
and
then
select
a
different
one,
then
it
runs
into
a
javascript
error.
So
there's
some
small
front-end
js
issues
that
need
to
be
worked
out.
A
A
Okay,
it's
gonna
be
a
quick
meeting
today,
okay
and
lastly,
outside
of
individual
features
that
are
being
promoted,
we
have
initiatives
that
are
longer
running
projects
that
might
not
be
done
all
in
one
single
release,
and
that
is
the
only
initiative
we
have
active
right
now
is
telemetry,
so
telemetry
is
285
in
the
backdrop
issue
queue
current
status
of
telemetry.
Is
that
it's
looking
good?
We
have
all
the
pieces
ready
in
for
project
module
and
the
core
module
is
ready
for
testing
as
well.
A
Let's
see,
but
the
next
steps
that
we
have.
We
need
a
code
review
on
the
pull
requests
that
are
submitted
to
that
issue.
285..
A
We
need
to
figure
out
how
to
incorporate
into
the
installation
profile
whether
we
add
a
check
box
to
the
standard
profile
or
leave
it
off
by
default
and
then
have
it
turn
on.
Like
give
some
kind
of
message:
encouraging
people
to
turn
on
telemetry
module,
all
those
things
have
yet
to
be
sorted
out.
We
could
potentially
separate
that
discussion
out
into
another
one
yeah.
A
It's
all
a
matter
of
how
we
want
to
approach
that
and
then
there's
an
open
question
about
charting
that
we
would
like
to
get
some
kind
of
better
display
on
backdrop
cms.org
to
display
the
statistics.
That's
not
tied
solely
to
telemetry.
There's
like
a
kind
of
big
question
of
how
should
we
do
all
display
of
charting
on
backdrop
cms.org,
because
whatever
we
use
for
telemetry,
it
would
also
be
nice
to
have
that
on
the
project
usage
pages,
so
that
we
could
have
a
histogram
of
backdrop
usage
over
time.
A
So,
like
the
project
slash
backdrop,
slash
usage,
I
think
it
is
that
shows
you
how
many
installations
of
backdrop
we
have
out
there
in
the
wild
it'd
be
nice
to
have
a
chart
there
too.
A
So
yeah
I'm
kind
of
open,
I
think
we're
all
kind
of
open
to
options
there
for
how
we
want
to
display
charting
whether
we
use
the
there's
a
backdrop.
Module
called
charts
that
I
think
right
now
only
integrates
with
high
charts
and
google
charts,
both
of
which
are
proprietary,
and
I
kind
of
think
that
you
know
we
should
be
trying
to
find
a
fully
gpl,
fully
open
source
charting
library.
For
that
purpose.
A
They're
using
d3-
and
I
don't
think
that
they're
using
any
additional
library
on
top
of
d3,
so
it
seems
like
it's
just
kind
of
a
custom
thing.
That's
specifically
for
drupal.org.
A
That's
of
course,
a
viable
option
that
we
could
just
go
and
grab
whatever
drupal's
doing
from
their
usage
repository,
because
that's
a
a
public
repository
as
well
and
then
just
copy
that,
and
I
think
that
that
is
not.
I
think
that
that's
not
using
a
contrib
module,
maybe
not
even
a
custom
module,
might
just
be
right
in
the
drupal.org
theme
and
I'm
just
taking
a
wild
guess
out
there,
because
it
just
doesn't
look
like
it's
anything.
That's
intended
to
be
generic.
A
Well,
anyway,
so
telemetry
is
actually
looking
really
good,
as
well
biggest
item
here
is
that
we
need
additional
testing.
A
Possibly
we
should
start
moving
towards
making
it
easier
to
test,
and
I
think
this
happens
every
time
we
have
something
that
is
like
there's
a
server-side
component
and
a
client-side
component
that
you
know
it's
a
hard
thing
to
get
set
up
for
testing
and
usually
when
this
happens,
I
propose
that
we
move
forward
the
server
side
component,
get
it
deployed
onto
backdrop
cms.org,
and
then
that
makes
testing
a
heck
of
a
lot
easier,
because
the
server
side
component
is
already
there
and
the.
Then
we
just
have
to
deal
with
the
the
part.
A
And
that's
it,
that's
all
I
have
on
telemetry
and
that's
all
there
is
on
the
agenda
today.
So
it's
a
really
short
one.
You
guys
have
anything
else.
You
guys
would
like
to
banter
about
or
bring
up.
E
A
small
thing
today
I
saw
just
before
the
meeting
that
red
bulger
an
updated.
E
A
Yeah
brad
bulger
looks
like
he
recently
updated
this
pull
request.
That's
awesome.
A
I'm
gonna
have
to
look
over
this
okay,
thanks
for
bringing
that
up.
Olaf.
A
Oh,
I
see
what
hap
what's
happening
here.
Brad
has
he
made
a
commit
in
a
repository,
but
it
hasn't
opened
a
pull
request.
Yet
that's
what's
going
on
here,
I'm
like
there's
something
that's
referencing
it
here,
but
it's
not
actually
as
a
pull
request.
There's
a
closed
pull
request
and
brad
is
branch
that
suggests
the
fix,
but
hasn't
been
pull
requestified.
Yet.
A
Okay,
all
right,
I
think,
then
we
can
call
it
a
meeting.
Thank
you
folks
for
joining
the
meeting.
As
always,
yeah
excited
to
see
those
new
contrib
modules
and
new
contrib
authors
joining
in
that's
very
exciting
and
thanks
for
another
great
week.
So
thanks
everybody
see
you
guys.