►
From YouTube: Backdrop Weekly - Jan 14th 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
All
right
we
are
live
today
is
thursday
january
14th
2021,
and
this
is
our
last
weekly
development
meeting
before
the
backdrop
118
release.
Let's
start
with
some
quick
introductions,
I
am
jen
lampton
joining
from
oakland
california,
I'm
also
joined
by
a
sleeping
cat
and
a
sunbeam.
So
I'll
turn
this
over
to
tim.
B
Oh
just
introduce
myself
tim
erickson,
I'm
st
paul
tim
in
deerwood
minnesota
and,
as
I
reported
before,
we're
having
a
nice
snow
today
and
I
want
to
get
a
camera
someday
that
I
can
point
out
the
window
when
I'm
doing
my
intro
anyways
just
here
to
find
out
what
how
things
are
looking
for
tomorrow,
the
release
justin.
D
Greg
hi
I'm
greg
and
usually
in
australia,
but
now
joining
from
greece
as
usual,
interested
in
anything
related
to
backdrop
and
also
joining
to
see
how
it
can
help
with
the
release
tomorrow.
B
E
F
Hey
bill
ward
out
of
wichita
kansas
yep.
Don't
have
anything
in
particular
to
just
to
discuss
today,
just
kind
of
wanted
to
see
how
things
progress
right
before
the
new
release,
yay
and
we'll
go
ahead
and
send
it
on
over
to
nate.
G
Many
of
us
americans
have
been
preoccupied
with
recent
events,
but
fortunately
everything
is
pretty
much
all
set
up
for
the
release
tomorrow
and
yeah.
I
I
think
that
we'll
have
a
pretty
easy
transition.
I
think
tomorrow
to
to
get
that
out,
although
we
do
have
some
issues
to
discuss
today
so
we'll
get
to
those
later
back
to
you.
Jen.
A
Okay,
first
up
on
our
agenda,
we
have
a
new
community
contributor,
rexel
format,
ported
the
grid
field,
formatter
module
and
is
applied
to
join
the
control
group,
though
so
welcome,
and
thank
you
for
your
work
on
grid
field
formatter.
G
So,
as
I
mentioned
last
week,
117.5
is
that
the
milestone
117.5
is
probably
where
a
lot
of
people
are
should
be
putting
their
efforts,
because
they
consist
of
the
bug
fixes
that
we
can
still
include
before
the
release
of
118,
and
I
see
that
there
have
been
a
lot
of
things
that
have
been
happening
over
the
past
week
to
further
that
goal
of
getting
some
issues
resolved
before
118
is
released.
G
Let's
see
so
there
are
some
new
items
and
some
old
items
in
this
list
the
site
getting
stuck
in
maintenance
mode
during
upgrades,
39
56
that
one's
been
marked
that
it
needs
testing
for
a
couple
of
weeks.
It
currently
still
is
that
state,
that's
there's
a
there's,
a
pull
request
and
we
just
need
confirmation
that
it
looks
okay,
I'm
sorry
that
it
works.
Okay,
it's
really
a
key
thing.
G
Let's
see
small
issue,
php
notices
when
installing
modules
that
have
sub
modules
issue
4640,
it
says
the
status
is
pr
works
for
me.
I
think
that
actually
got
moved
to
rtbc.
G
I
could
be
wrong
about
that
anyway.
Very
small
issue,
we're
getting
php
notices,
throw
a
warning
if
max
input.
Vars
is
not
properly
set
issue
3824..
G
A
I
think
we
have
consensus
on
that
one,
but
I
was
unsure
how
to
produce
a
pull
request
with
the
desired
result,
because
it
would
duplicate
the
message
on
the
page,
but
gregory
posted
a
pull
request
earlier
this
week,
where
he
called
backdrop
get
message
before
a
backdrop
set
message.
It
wouldn't
make
the
previous
message
disappear,
and
so
I
was
wondering,
which
is
why
we
have
a
core
committer
present.
If
that
would
be
an
acceptable
solution
or
if
there
were
danger,
was
danger
there
of
accidentally
deleting
other
messages
that
might
need
to
be
rendered
on.
A
No
so
in
his
case
it
was
the
preview.
The
preview
message
was
showing
up
when
the
node
form
was
saved,
and
so
we
wanted
to
remove
the
preview
message.
So
it
doesn't
say
this
is
only
a
preview.
We
have
saved
your
node.
G
D
Nate,
just
just
to
say
that
this
is
what
you're
referring
to
is
the
backdrop
set
message
that
has
a
second
parameter.
We're
talking
about
backdrop,
get
messages
without
any
parameters
which
all
it
does.
It
clears
a
certain
type
of
messages,
but
if
you
don't
pass
any
parameters,
it
clears
all
messages
yeah
before
printing
any
other.
D
Yeah
so
so
peter
did
a.
I
think
it
was
this
one,
because
there's
two
related
issues.
I
did
a
code
review
and
left
the
message
with
regards
to
only
doing
the
warnings
so
specifying
this
to
warning,
and
I
had
the
opposite
concern
that
if,
if
in
the
future
we
add
another
methods
in
the
preview
form
info
type,
for
example,
that
one
will
bleed
again
into
the
you
know
the
save
page
so.
G
F
G
Because
that
would
solve
this
particular
problem.
We
could
just
remove
that
one
message:
if
it
was
there
and
then
put
it
back,
but
we
don't
have
that
capability
right
now,
other
than
just
like
straight
up,
string
matching
or
something.
D
G
I
am
not
sure,
especially
yeah,
especially
because
we're
showing
this
message
after
something
has
gone
wrong.
You
know,
isn't
that
the
situation.
D
So
nate,
you
might
be
confused,
so
we're
talking
about
there's
a
warning
that
says
when
you
hit
preview
for
a
node
before
saving
it,
there's
a
warning
at
the
top
of
the
page.
That
says
this
is
a
preview.
Nothing
is
saved,
you
need
to
click
the
save
button
and
when
you
click
the
save
button,
there's
a
success
message
that
says
everything
has
been
saved
but
but
before
it,
we
repeat
the
warning
that
says
this
is
a
preview
which
is
totally
this.
G
A
Yeah,
it's
the
same
internal
mechanism,
that's
causing
the
double
message
got
it.
I've
saved
loads
form
before.
G
Okay,
I
wonder
if
it's
really
just
the
the
form
being
loaded
twice.
I
wonder
if
there's
some
solution
that
we
can
pursue.
That's,
like
you
know,
is
there
something
informed
state
values
or
something
like
that
to
just
to
press
the
message,
because
the
second
time
the
form
is
built,
we
should
be
able
to
detect
that
it's
being
built
for
the
reasons
of
submitting
the
form,
I
think.
A
I
had
a
really
hard
time
with
that
I
spent
about
an
hour
and
a
half.
It
depends
at
which
point
you
put
the
message
I
was
trying
to
put
it
in
process
form
and
process
form
doesn't
have
anything
you
can
access
in
there.
I
think,
if
you
did
it
on
like
build
form-
or
I
don't
know,
there's
a
couple
of
places
in
the
form
rendering
pipeline
where
you
do
have
access
to
that,
but
I
needed
to
be
at
a
particular
point
where
I
didn't
have
access
to
any
of
that.
A
G
Yeah,
so
the
the
short
answer
to
the
question
is:
is
that
I'm
not
really
comfortable
with
suppressing
messages?
I
I
really
would
find
it
to
be
less
than
well
less
than
acceptable
solution.
D
D
Just
for
a
backstory
with
regards
to
the
preview
page
specifically,
what
we
do
is,
instead
of
showing
the
messages.
Sorry,
instead
of
adding
the
the
backdrop
set
methods
when
rendering
the
the
preview
panes,
we
add
it
to
the
function
that
adds
the
the
ribbon
with
the
save
button
at
the
bottom
right,
and
we
have
a
note
there
that
says
we
have
specifically
added
this
here,
so
that
it
can
persist,
see
how
we
switch
display
modes.
There's
a
drop
down
that
switches
display
modes.
D
G
Okay,
so
that's
a
little
bit
of
a
can
of
worms.
I
might
also
in
the
case
of
3824,
where
it's
about
max
input
vars.
I
know
this
has
been
discussed
also,
but
possibly
if
we-
I
could
be
wrong
about
this,
but
if
we
don't
display
the
first
message,
but
only
to
display
the
second
message
like
that
is
also
an
option.
Isn't
it
where
we
only
show
the
message
when
something
has
gone
wrong
and
not
beforehand?
G
Yeah,
so
that
that's
also
a
possibility,
my
understanding
is
that
calculating
the
number
of
variables
beforehand
is
tricky
calculating
afterwards
after
the
error
has
occurred,
is
a
little
easier,
but
it's
also
like
after
a
problem
has
occurred
so.
A
B
Well,
here
I
can
read
it,
he
said:
can
we
just
unset
that
one
message
on
form
submit
or
can
we
do
like
layout
instead
of
themed
as
a
message,
instead
of
actually.
A
So
the
reason
we
can't
remove
only
the
one
message
messages,
because
we
don't
have
any
key
other
than
error
warning
info
or
whatever
our
options
are
for
messages,
but
I
think
that
was
the
issue
allowing
messages
to
be
alterable
that
was
posted.
Oh,
he
found
that
already.
A
D
G
G
Okay,
let's
yeah,
let's
keep
going
sorry,
I'm
a
little
short
on
time
today,
so
yeah,
okay.
So,
let's
see
some
other
issues
that
are
moving
along,
simple
decimals,
pat,
failed
to
pass
validation,
issue,
37
92.
G
I
actually
think
that
oh
interesting,
it's
just
like.
If
you
have
a
really
long
decimal,
then
like
the
the
higher
the
precision
the
decimal,
then
I
guess
sometimes
it
starts
failing,
which
is
crazy.
Anyway,
the
pr
is
marked
works.
For
me,
it
needs
code
review.
This
is
37.92
this
one's
interesting
gregory.
I
think
one
of
your
show
ck
editor
on
the
site
status
page
show
the
ck
editor
version
on
the
site,
size,
page
issue,
3360.
D
Yeah
I
had
some
feedback
from
from
people
that
were
reviewing
it,
so
maybe
I'm
doing
a
little
bit
too
much
but
like
there's
things
that
need
to
be
removed.
So
there
were
messages
about
assuming
the
that
the
message
was
being
seen
by
someone
that
doesn't
have
access
to
configure
ck
editor
and
then
asking
them
to
go
to
their
admin
site
admin
and
do
things
for
them
like
adjust
permissions,
and
we
we
decided
that.
Maybe
it's
a
better
idea
to
not
include
that.
So
it
just
needs
to
clean
up
removing
things
rather
than.
G
It
okay,
let's
see
another
one
related
to
canada,
the
the
administrative
display
for
rearranging
the
buttons
of
a
c
editor
toolbar
issue,
48
32..
They
do
not
work
correctly
in
rtl
languages.
Pull
request
is
marked
works.
For
me.
I
needs
a
code
review.
G
This
last
one
just
got
added
language
names,
not
translated
into
their
native
names
issue.
45
11..
B
So
I
thought
so.
D
We
could
we
could
resolve,
but
gregory
yeah.
So
the
last
discussions,
the
last
messages.
There
are
some
people
through
the
idea
of
using
a
third-party
library
that
handles
what
you
call
it
grading
the
strength
of
the
password
and
then
some
comments
being
added
there
saying
that
certain
of
those
libraries
require
php,
seven.
B
D
B
Yes,
but
in
the
last
several
days
herb
dual
said,
I
don't
think
this
goes
in
1.18
and
indigozala
said.
Well,
I
don't
care
just
so
it
goes
in
so
so
somebody
there
there's
a
discussion
about
whether
or
not
the
the
the
label
is
correct.
G
Yeah,
it
does
look
like
this
like
it
has.
An
update
hook,
adds
a
parameter
to
a
function
and
it
adds
a
field
to
when
you
set
up
a
language.
You
can
specify
the
native
language
name,
so
it's
definitely
adding
stuff
that
this
could
be
called
a
feature.
G
G
G
Okay,
well,
that
needs
some
more
looking
at
discussion
about
when
it
should
go
in
is
also
a
factor,
and
then
there
are
also
several
rtbc
issues:
increasing
the
password
strength
requirements.
Basically,
issue
4602.
G
I
like
that
this
issue
herb
dual
erased.
It's
because
or
sorry
jen
raised
it,
because,
according
to
the
standards
for
security
like
they
actually
have
like
specified
limit,
saying
how
many
characters
indicates
a
fair
versus
a
strong
password
and
that
we
should
be
following
those
indus.
Those
standards
regarding
our
own
password
strength
indicator.
So
4602
just
brings
backdrops
indicator
in
line
with
those
standards.
G
Let's
see
fixing
translated
parent
menu
items
when
you
select
a
parent
menu
item,
if
it's
been
translated,
then
it
doesn't
give
you
the
correct
options:
to
choose
its
parent
from
the
same
language
issue.
38-57,
sorry,
tbc
as
well
indicate
the
vocabulary
when
editing
a
term
issue
38-11.
G
I
like
this
one
that
it's
just
like
when
you're
adding
a
term
or
editing
a
term.
It
just
puts
in
the
title
what
vocabulary
you're
inside
of
when
you're
doing
that
operation,
great
little
usability
improvement
and
the
current
user
context
in
a
layout
does
not
contain
a
user
entity.
This
is
issue
2398.
G
This
occurs
when
you
add
a
field
for
sorry
when
you
try
to
add
a
block
to
a
layout
that
contains
a
user
field
on
the
current
user.
It
currently
throws
errors,
and
this
fixes
that
problem
to
make
it
so
that
you
can
pull
fields
off
of
the
current
user,
so
23.98
that
one's
also
marked.tbc-
and
there
are
also
a
couple
of
smaller
issues
that
just
fix
php
notices
that
have
also
been
marked
rtbc.
G
So
there's
a
good
number
of
items
that
are
in
the
queue
for
rtbc
that
will
we
or
I
will
go
through
and
get
all
those
merged
in
before
the
release
tomorrow,
because
all
of
these
are
really
trivial
good
fixes
that
don't
really
require
a
lot
of
effort.
That's
all
I've
got
for
the
117.5
milestone.
Those
are
issues
that
we
have
the
possibility
of
getting
fixed
before
the
release
tomorrow.
G
There
are
also
a
number
of
other
issues
in
the
117.5
mile.
1175
milestone,
if
you're
wanting
to
do
some
last
minute
fixes
that's
the
place
to
look
for
things
that
could
get
in
before
the
release
tomorrow,
all
items
that
were
in
the
go
ahead.
G
119,
because
there
is
nothing
else
for
118.
118,
we
don't
have
anything
any
any
changes
that
are
marked
specifically
for
118,
we're
now
in
feature
freeze
until
tomorrow.
So
the
next
things
that
we
have
to
work
on
are
119,
which
right
now
just
consists
of
the
things
that
were
carried
over
from
118.
G
It
is
a
good
time
to
start
thinking
about
119
issues
and
what
we'd
like
to
see
in
the
next
release
that
will
be
april,
15th
and
yeah
start
start.
Brainstorming,
wait.
G
Am
I
wrong
about
that?
May
15th,
I'm
sorry
may
15th.
G
So
it's
a
good
time
to
start
thinking
about
things
that
we
want
in
the
next
release.
Well
again,
I
think
we've
been
discussing
we'll
have
a
meeting,
probably
towards
the
end
of
january,
or
the
first
month
of
our
first
week
of
february,
to
like
get
together,
discuss
the
options
that
we
have
available
before
us
and
then
kind
of
set
priorities
for
set
priorities
and
try
to
solicit
advocates
for
119
features.
G
Let's
see
initiatives
before
we
close
out
the
telemetry
initiative
and
the
ready-to-wear
initiatives
are
active
initiatives
that
we
have
going
on
right
now
might
not
hurt
to
give
us
a
little
update.
If
anything
has
happened
on
those
items
as
of
late,
so
telemetry
tim
you're,
the
advocate
for
this
issue:
do
we
have
any
any
updates
on
it.
B
Not
two
weeks
ago
I
did,
I
did
finally
do
some
testing
on
it.
I
don't
believe
I
fully
updated
the
issue
yet,
but
we
kind
of
decided
that
we
weren't
going
to
get
anything
into
1.18
so,
but
but
we
did
move
the
ball
a
little
bit
forward.
So
I
think
the
next
step
is
really
to
update
the
issue.
We
have
to
start
making
some
policy
decisions
about
implementing
this
and
get
something
into
point,
one,
eight
or
one
one.
Nine,
that's
all.
G
All
right
the
ready
to
wear
initiative.
Luke,
do
you
have
any
updates.
E
E
But
the
big
thing
is:
is
we're
gonna
do
a
meeting
on
tuesday
to
try
to
finalize
some
things
at
the
moment,
looking
for
for
sample
content
that
can
be
used
to
to
test
ready-to-wear
themes,
looking
to
flesh
out
the
descriptions
and
sort
of
metadata
associated
with
a
chosen
set
of
themes
and
and
finally
to
create
a
little
content
about
the
sort
of
edge
issues
that
are
that
are
almost
but
not
quite
part
of
the
sort
of
like
central
theme
elements
of
of
reddit,
aware
just
so
that
the
mvp
prototype
site
explains.
E
You
know
the
things
that
are
covered
and
and
other
places
to
to
go.
We
I
I
talked
about
it
a
little
bit
in
the
design
meeting,
so
I
don't
want
to
like
overly
duplicate
things,
but
the
the
the
takeaways
there
are
meeting
on
tuesday
and
information
in
zulup
and
the
the
forums
coming
describing.
E
What
what
that
meeting
will
accomplish
and
next
week
a
report
about
where
we
are
after
the
meeting.
G
All
right
great!
Well,
that's
it
for
initiatives.
We
also
have
a
little
bit
of
time
here
for
just
general
questions.
If
you
guys
would
like
to
bring
up
anything
else,.
G
It's
a
good
question,
so
we
talked
a
little
bit
about
parties.
G
I
don't
think
that
I've
had
the
brain
space
for
parties
recently,
but
we
had
discussed
about
getting
the
release
out
earlier
in
the
day
so
that
if
there
were
parties
that
we
could
attend
them
afterwards,
obviously
with
the
pandemic
happening
and
raging
around
us,
it's
not
a
good
time
to
be
leaving
your
house,
but
we
could
still
have
an
online
party
of
some
sorts.
G
E
I
actually
want
to
throw
that
at
the
at
the
outreach
meeting
last
week
we
we
talked
about
sort
of
outreachy
things
that
come
around
the
the
the
release
that
the
currently
fall
on
the
shoulders
of
the
poor,
overworked
developers,
and-
and
so
so
I
at
this
point,
I
actually
just
kind
of
want
to
ask
like
like
what.
What
are
some
of
those
things
that
that
the
developers
are
are
ready
to
do
but
are
tired
and
looking
to
outsource.
E
D
G
B
A
A
F
G
And
well,
that's
smart!
That
would
be
good
of
us
if
we
did
that
yeah.
Oh,
I
also
want
to
give
props
again,
even
though
we
already
mentioned
this
last
week.
I
think
it
was
that
creating
the
release.
Notes
also
was
a
huge
hassle
like
that
always
took
a
long
time,
and
nobody
liked
doing
it
very
much,
but
thanks
to
some
recent
effort
by
bw
panda
that
has
now
become
automated,
where
the
release
notes
are
created
automatically
for
us.
G
G
It
also
can
do
things
like
give
credit
to
individuals
like
it
can
actually
aggregate
everybody
that
participated
in
that
release
and
then
generate
a
thank
you
list,
and
it
also
incorporates
things
that
were
fixed
that
were
marked
in
the
milestone
that
aren't
necessarily
code
related.
So
previous
work
was
all
based
about
reading
the
git
history.
Now
it
reads
the
issue
history
instead,
and
that
gives
us
better
opportunities
to
to
credit
people
and
to
note
work
that
we've
done
over
that
time
period.
So.
G
Anyway,
to
answer
the
question:
okay,
I
agree.
I
think,
if,
if
I
were
to
put
a
target
on
it,
I
would
say
before
5
pm
pacific.
B
Okay,
so
regarding
those
plannings
we
had
talked
about
doing
a
virtual
game
night.
I
didn't
do
any
prep.
I
did
post
last
night.
I
see
if
anybody
was
interested.
There
have
been
one
or
two
minor
hits
I'll
just
sort
of
leave
that
discussion
open.
If
we
want
to
do
something
spontaneously,
we
can,
but
there
haven't
been
any
big
plans.
B
I
know
that
indigozella
expressed
a
little
interest
and
she's
in
europe
so
late
tomorrow
is
probably
good,
not
good,
so
maybe
doing
something
on
saturday
afternoon,
just
for
fun
very
informal
for
anybody
who
wants
yup
so
just
speak
up
in
zulu.
If
you're
interested
in
getting
together
and
doing
something
this
weekend
tomorrow,
night
or
saturday.
G
The
great
which,
by
the
way
backdrop
turns
five
so
very
exciting.
It's
kind
of
surprising,
it
seems,
like
backdrop,
is
still
new,
but
five
years
is
a
long
time
already.
G
G
No,
I
I
I
like
it
that
way,
and
in
yeah
it's
like
okay
right,
well,
great,
let's,
let's
wrap
it
up
for
today.
Thank
you,
everybody
for
all
of
your
work.
As
always,
I
know
the
reviewing
backlog
that
falls
on
on
me
has
been
a
little
bit
bad,
but
I'm
hoping
I'll
get
through
the
issues
that
are
outstanding
there.