►
From YouTube: Backdrop Weekly - March 5th 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
B
A
A
E
I
am
Nate
limped
in
from
Oakland
to
California,
and
today
we've
got
some
updates
on
config
overrides,
which
are
exciting,
but
I'm
also
here
to
hear
what
what
issues
need
need
feedback,
usually
dark,
Wilmont,
grading,
a
whole
bunch
of
Seidman
requesting
Knights,
my
balls
so
yeah
we'll
see
we'll
see
you
as
we
go
through
them.
Hi.
A
A
All
right,
I
am
Jen
I'm
from
California,
and
I
am
looking
forward
to
seeing
what
issues
need
attention
this
week.
So,
let's
see
before
we
get
to
the
issues,
let's
do
some
updates
from
the
project
management
committee.
There's
one
very
exciting
announcement
that
we
didn't
get
to
last
week:
I,
don't
think
Olaf,
Caribbean
ski
has
joined
the
project
management
committee,
so
I
think
we
announced
the
other
two
members
last
week,
but
not
Olaf.
So
just
give
him
a
warm
welcome
and
say
we're
very
excited
to
have
him
in
the
near
future.
E
E
There
are
a
number
of
issues
that
are
in
the
115
one
milestone
that
could
be
given
the
tension.
We
don't
have
any
to
raise
up
during
this
meeting
other
than
Joseph's
issue
4306,
making
tests
faster
and
some
better
visibility
into
tests.
That's
been
it
needs
review
for
the
past
week.
It
looks
like
it's
all,
just
nice
minor
improvements
to
the
testing
system,
and
you
know
we
could
just
use
some
eyeballs
on
that
to
see,
if
that's
all,
ready
to
go
Thank
You
Joseph
for
getting
that
all
prepared.
E
116
116
will
be
the
next
minor
version
will
come
out.
May
15th
with
feature
freeze,
may
1st
for
me
personally.
At
least
it
feels
like
now
that
we're
in
March
you
know
we're
at
least
in
the
same
season
as
as
the
as
the
next
release,
which
makes
it
feel
more
imminent,
so
things
that
we've
got
cooking
for
116
include,
allow
any
config
value
to
be
overridden
via
setting
stop
PHP,
that's
2805.
E
This
has
been
our
TBC
last
week
and
I
merged
it
just
earlier
today.
So
that's
great.
It's
now
completed
next
up
is
enabling
autocomplete
on
all
link
and
path
fields
issued,
36
or
sorry,
37,
64,
BW,
panda
or
Peter
is
the
is
the
advocate
for
that,
and
it's
been
our
TBC
by
dr.
Elmont
just
in
the
last
couple
of
days.
So
that
looks
excellent
and
it's
probably
eminently
going
to
be
completed.
E
Next
up
is
base
and
sub
install
profiles.
Profiles
right
now,
currently
don't
have
the
ability
to
inherit
from
other
profiles
and
issue.
Thirty-One
74,
also
from
BW
panda,
makes
it
so
that
functionality
as
possible
joseph
said
that
he
reviewed
that
just
just
earlier
today,
joseph
it
has
that
been
marked
re
TBC,
or
did
you
just
provide
an
additional
feedback?
E
F
E
D
This
issue
was
raised
like
really
on
it's
one
of
the
early
issues,
just
like
back
in
2015.
So
the
problem
with
the
text
formats
is
that
we
have
three
different
sets
of
settings
which
are
canta
bedded
and
they
are
presented
in
the
user
interface
via
a
set
of
a
series
of
checkboxes
which
then,
if
depending
on
whether
they're
checked
or
not,
they
make
other
controls,
draggable
table
or
rows
and
vertical
tabs
appear,
and
the
user
experience
is
not
that
great.
D
D
So
the
feedback
that
has
been
going
back
and
forth
between
and
the
theater
myself
is
that
the
current
implementation
is
that
the
Forbes
was
figuring,
its
filter,
I'm
reloaded
in
the
single
page
and
then
they're
hidden
their
JavaScript.
And
then,
when
you
click
the
buttons
to
load
individuals,
individual
configuration,
then
the
portion
of
the
form
gets
loaded
in
a
dialogue.
D
So
there's
a
bit
of
this
is
the
bit
of
implementation
that
needs
feedback,
whether
it's
appropriate
or
not,
and
ideally
it
shouldn't
work
that
way,
but
the
difference
between
that
and
how,
for
example,
the
dialogues
in
layouts
work
is
that
so,
if
you
disable
JavaScript
the
dialogues
for
layouts
and
other
other
places,
they
have
a
path
so
that
these
settings
will
load
in
the
different
planes.
But
this
doesn't
happen
with
the
filters.
E
E
E
A
E
A
D
So
there
there's
other
things
that
are
sort
of
like
satellite
issues
too.
That
cannot
be
if
the
dialogue
is
open
and
then
we
submit
the
dialogues,
we
need
to
make
sure
that
this
validation
going
on
or
whatever
we
save
and
then
I'm,
not
sure,
because
I
haven't
explored
any
options
like
may.
Maybe
we
could
hide
and
show
those
settings
like
in
a
way
like
that,
similar
to
fields
it's
expanding
and
collapsing
so
that
it's
not
a
huge.
You
know
set
of
many
forms
comprising
a
huge
form
yeah.
E
Yeah
yeah
you're
right
things,
like
validation,
would
be
a
big
issue
yeah
that
you'd,
really,
you
really
would
want
to
form
to
validate
before
you
close
the
dialog.
You
know
that
that
and
exposing
errors,
if
you
tried
to
submit
the
form
and
the
form
fields,
were
hidden
that
the
validation
error
occurred
on.
That
would
be
bad
okay.
So
it
sounds
like
that.
So
it
sounds
like
there's.
Some
actual
user
interface
repercussions
from
the
approach
that's
been
taken
that
possibly
need
to
be
need
to
be
solved
and
possibly
aren't
possible
to
solve.
D
E
D
E
D
Otherwise,
that
pull
requests
were
worked
as
expected,
so
yeah,
only
a
few.
A
few
minor
wishes
that
I
mentioned,
but
I
think
it's
on.
If
what
did
not
already
fix
that
was
there
and
his
radar,
like
small
things
like
when
disabling
a
filter,
a
checkbox
for
a
filter,
the
the
respective
buttons
for
ckeditor.
They
still
appear
there,
even
though
they
should
and
things
like
that.
But
it's
just
time
things
that
we
can
solve.
Yeah.
E
D
E
Yeah
I'm,
starting
to
think
really
strongly
that
that
doing
the
state
approach
is
the
right
thing
to
do,
because
it's
starting
to
there's
so
many
steps
involved
that
configuring
a
text
format
is
that
is
not
less
complicated
than
a
layout
in
a
lot
of
ways.
You
know
like
it's.
It's
a
similarly
complicated
task
that
that
pattern
of
using
state
and
updating
a
temporary
object
might
be
the
way
that
we
should
proceed.
I
think.
D
D
E
I
think
that
still
it
still
needs
to
function,
even
though
without
JavaScript,
even
today,
just
because,
if
there's
only
if
we
move
fully
to
dialogues
at
or
multiple
pages
for
steps
like
like
views
or
layouts,
we
need
like
just
leaving
the
current
page
as
it
is.
If
that's
only
used
for
non
JavaScript.
That
seems
very
unusual,
like
we
need
the
non
JavaScript
version
to
act
the
same
way
so
that
we
can
have
test
coverage
on
it.
So
it
would
step
through
the
same
process
as
though
it
were
in
dialogues
only
their
separate
pages.
E
D
B
E
E
I
feel
like
when
this
happens,
we
should
have
another
person
just
speak
as
though
they
were
that
person
in
mufon's
actually
maybe
not
I
take
that
could
be
a
terrible
okay.
All
right.
It's
the
next
up,
better
workflow
States
issue,
1475
also
dark
moments:
beer
headed
issue-
we
were
talking
about
this
before
the
recording
started
so
Gregory.
You
just
raised
your
hand,
yeah.
D
So
this
is
temporarily
parked.
We
need
to
formulate
before
we
start
getting
into
an
endless
discussion
and
implementation
and
reverting
the
implementation
and
changing
that
all
over
again,
we
and
by
we
I
mean
ten
team
and
myself
for
trying
to
sell
about
formulate
in
a
shared
document
like
Word
document.
D
What
the
objective
is,
what
the
goal
is,
and
once
we
have
finalized
that
and
terminology
that
is
going
to
be
used.
We're
gonna
pass
it
on
to
to
document
sort
of
like
finalize
the
implementation,
or
maybe
it
would
be.
People
need
to
be
a
totally
different
pull
request
so
yeah
and
there's
certain
aspects.
Certain
features
that
team
has
mentioned
would
like
to
see
that
this
should
be
split
out
to
follow-up
issues
specifically
being
able
to
specify
States
for
forward
or
backward
revisions.
B
B
E
Yeah-
and
it's
also
posted
to
the
issue
1475,
which
has
been
helpful.
Okay,
next
up
this
new
issue,
which
I
haven't
looked
at
yet
at
all,
but
Tim
you
are
the
advocate
for
issue.
23
79,
allow
the
customization
of
author
and
date
display.
Can
you
give
us
an
update
on
what
that
issue
is
and
its
current
status.
B
Sure
the
this
issue,
I
think
has
been,
or
the
PR
has
been
around
for
a
little
while
now
and
it
basically
allows
in
each
content
type
for
the
editor
to
select
a
custom
date
format
and
have
some
control
over
the
the
author
display
right
out
of
the
box,
and
we
have
a
PR
that's
working
nicely.
The
status
appears
to
be
that
it's
working
Gregory
has
expressed
a
couple
of
comments,
but
he
seems
to
be
looking
for
comments
on
his
comments.
If
I
understand
correctly
Gregory
like
you
wanted
you
weren't
sure.
B
B
I
I
have
been
really
held
back
by
the
lack
of
this
feature
in
the
past,
and
recently
we
had
somebody
looking
for
this
feature
in
in
the
forum
like
basically
how
do
I
customize
the
date
format
and
it's
kind
of
complicated
right
now,
so
this
would
really
make
that
easier
and
I
often
say
it's
like
one
is,
if
I
open
a
raw
backdrop
site.
It's
like
one
of
the
first
things
that
jumps
out
to
me
is
the
the
format
it's
like
I
want
to
change
that
right
away,
and
it's
not
easy.
B
B
E
Be
really
neat
because
honestly,
posting
by
usernames
is
no
like
for
for,
like
something
like
you
know:
computing
oriented
websites,
sure
aliases
might
be
used
for
authors,
but
in
the
most
situations
of
content
authoring
and
even
blog
posting,
you
use
people's
real
names.
That's
the
author,
not
a
not
a
user
name!
There.
D
Are
cases
where
you
allow
the
email
to
be
used
as
a
username
as
well,
and
that
exposes
a
risk.
So
we
had
a
situation
in
dev
CMS
where
dumb
woman
emails
were
exposed
because
of
meta
anyways,
so
having
the
real
name
or
some
first
name
and
initial
of
the
last
name
instead
of
the
emails
or
the
user.
Names
is
better
because
if
you
expose
user
names,
then
what
you
can
use
those
to
brute
force.
So
it
becomes
a
security
issue.
So.
B
E
B
A
This
in
one-
and
there
were
some
issues
with
breaking
template
files,
so
we
just
need
to
make
sure
that
I
mean
it
sounds
to
me
like.
It
should
be
fine,
because
in
template
files
that
should
just
be
printing,
they
like
submitted
variable,
but
if
there
is
like
a
theme
function
that
actually
includes
like
user
name
by
whatever,
like
I,
think
there's
like
a
theme-
I,
don't
remember,
but
there
were
two
places
in
core
that
use.
This
one
was
like
on
Notes.
One
was
on
comments
and
I.
A
D
E
Yeah
they
would
have
to
translate
every
format
of
the
authored
by
line
yeah,
which
is
the
same
for
everything
that
is
starting
config,
like
as
you
change
like
the
label
in
the
fields.
Well,
then,
you
have
to
update
the
translations
yeah,
okay,
cool.
Well.
That
sounds
really
neat.
Thank
you,
Tim
for
posting
that
update
and
being
the
advocate
for
it.
E
D
Yes,
sorry,
there
has
not,
there
hasn't
been
more
activity
there.
I
think
it
meets
quarterly
at
some
point,
I
think
that
dr.
would
cut
that
out
was
waiting
for
me
to
do
it,
and
then
he
just
didn't
find
the
pull
request
against
chance.
So
this
needs
to
be
tested
and
reviewed,
but
where
we
were
left
was
that
the
implementation
that
we
had
varied
back
in
August
and
then
we
missed
the
114
in
the
115
deadlines.
D
Future
freezes
was
that
we
were
changing
so
many
things
that
it
was
affecting
the
way
that
text
formats.
Actually
so
we
were
affecting
the
text
formats
and
what
was
allowed
and
what
not.
So
the
current
accommodation
is
like
it
has
far
less
changes
and
because
it's
less
things
so
it's
more
simple
and
has
less
risk
of
messing
with
formats.
E
Okay,
yeah
so
needs
code
review
sounds
like
that's.
That's
where
red
and
and
I
think
last
we
looked
at
this
I
think
we
were
all
like.
Yes,
that's
that
sounds
like
it's
the
way
to
go
so
it
sounds
like
it.
Just
needs
needs
eyeballs,
okay,
anything
else
that
anyone
would
like
to
bring
up
for
the
116
releases
being
an
issue
that
is
likely
to
happen
that
we
have
an
advocate
for
or
that
we
should
discuss.
C
E
And
also
just
like
I
totally
understand
the
and
they
even
encourage
the
like
just
the
distribution
of
like
people
having
personal
control
over.
You
know
what
it
is
that
they
find
interesting
going
on
and
like
I,
think,
the
more
sources
that
we
have
saying
and
talking
about
doc
drop
the
better
actually
but
I
do
agree.
That
backdrop
see
mr.
org
should
have
the
canonical
in
a
blog
post
and
announcements,
and
things
like
that.
D
So
this
was
triggered
by
a
comment,
a
feedback
that
I
got
in
24
32.
So
this
pattern
has
a
really
simple
pull
request,
but
then
I
touched
the
view.
Stop
Inc
file
and
I
got
freaked
out.
My
OCD
started
kicking
in
with
the
comments,
so
it
ended
up
like
there
was
a
single
line
that
I
needed
to
change,
but
then
I
changed
like
385
lines
of
commands,
and
you
know
me
so.
Here's
the
thing
I
understand
that
I
haven't
seen
so
far
as
opening
issues
specifically
for
fixing
comments.
Would
that
be
the
best
thought?
D
E
D
D
The
issue
was
I
filed
that
issue
back
in
2016
15,
and
it
was
every
configuration
file
in
views
has
has
a
key
in
it
that
says
core,
and
then
it
has
a
version
and
the
version
could
be
one
or
no
or
ace
or
like.
It
has
arbitrary
things
that
you've
already
discovered
that
it
has
been
removed
in
theatres.
Well,
because
it's
not
big,
Youth,
England
and
I,
don't
think
we
use
it
anyway.
So
initially
the
pull
request.
Yeah.
D
The
full
request
was
to
remove
every
occurrence
of
that
from
mutation
files,
existing
change
the
plans
and
then
also
from
install
files
that
do
the
updates
so
that
we
don't
end
up
with
with
that
and
specifically
the
doc,
the
Inc
file.
What
I
changes
I
make
it
so
that
next
time
that
you
save
a
file,
if
it
includes
that
line,
sort
of
like
strips
it
out
and
it's
being
done
sinking
by
removing
a
single
line
yeah
that.
D
So
what
I'm,
asking
in
general
not
to
be
specific,
but
in
general,
when
we
want
to
fix,
solve
like
satellite
things
like
these
comments,
which
are
extensive
changes,
but
not
substantial
to
the
specific
pull
request,
though
we
split
it
up
in
a
specific,
separate
issue
to
fix
the
comments,
though
we
keep
it
in
the
same
pull
request,
but
have
a
separate
committee
so
that
people
can
cure
that
commit
separately.
What
will
be
the
best
approach?
Yeah.
E
D
D
D
D
C
Our
car
quickly
I
got
stuck
on
Zen
CI
stuff,
I,
wonder
if
we
could
me,
how
do
you
feel
about
having
a
Travis
file
just
for
PHP,
CS
and
Zen
CI,
for
so.
E
E
One
thing
we've
been
looking
into
and
I
think:
we've
already
opted
in
the
backdrop
organization
to
is
github
actions
so
github.
How
has
a
CI
integrated
into
it
of
some
sort
I
think
that
I
would
I
would
like
to
investigate
that
as
our
primary
Avenue
and
then,
if
that
doesn't
pan
out,
then
we
can
look
at
alternatives,
but
in
any
case
it's
usually
the
the
process
of
for
setting
it
up
is
usually
figuring
out.
E
The
scripting
and
the
commands
that
need
to
be
run
and
then
adapting
it
to
an
individual
CI
platform
is
pretty
trivial,
like
the
it's
usually
the
same
thing,
just
in
a
slightly
different
format
for
each
CI
platform.
So
if
you
wanted
to
or
if
you
found
Travis
to
be
more
accessible,
getting
it
working
on
Travis
would
be
a
very,
very
strong
start
to
make
it
so
that
we
could
adapt
it
to
actions
so
either
either
approach
be
fine.
Can.
C
D
A
C
B
D
Usually,
like
there's
two
ways
that
I
could
do
it
either
if
I'm
editing
the
code
of
a
form,
for
example
I
just
mock
up
before
it
will
won't
work
when
you
submitted,
but
the
form
elements
that
I
add
are
actual
code.
Otherwise
the
mock-up
is
just
you
know
when
you
right-click
on
Chrome
and
you
select
page
inspector
heat
and
add
butylated
any
HTML,
so
I
usually
do
either
one
of
those
and
then
a
screenshot
and
there's
a
time.
B
E
Yeah
no
I
what
I
usually
do
is
take
the
entire
form
element
and
copy
its
HTML
and
then
add
another
thing
and
then
paste
in
the
whole
HTML
and
then
selectively,
like
hack,
individual
things
and
so
sometimes
I'll
even
go
to
another
form.
That
is
a
select
list,
for
example,
and
copy
its
HTML
out
and
then
paste
it
into
the
other
one
and
sure
the
name.
The
name
and
attributes
of
stuff
like
that
are
all
messed
up.
But
it
doesn't
matter
because
it's
just
a
picture.
D
E
Okay,
well,
that's
it!
Then
it's
just
two
o'clock,
so
let's
call
it
time.
Thank
you
guys
all
for
for
joining
the
meeting,
as
always
really
appreciate
you
guys
being
here
and
even
more
all
the
work
that
everyone's
been
putting
in
day
after
day,
we
really
been
seeing
a
lot
of
activity,
particularly
in
the
pmc
and
leadership
side
like
there's
been
a
lot
of
really
great
momentum
there
and
a
lot
of
shifting
and
changing
around,
but
we're
still
seeing
the
regular
all
the
time
you.