►
From YouTube: Backdrop Weekly - Sep 19th, 2019
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
We
also
have
some
open
issues:
Rebecca
I'm,
so
messed
up
Lord.
It
looks
like
one
that
we
talked
about
recently.
I,
don't
know
if
we
have
a
status
update
on
its
this
idea
of
the
nightly
releases
when
I
was
wondering
I
think
it's
quite
something
but
I,
don't
remember
what
it's
locked
by.
So
sorry,
if
you
could
put
a
note
here
that
says
what
we
need
in
order
to
do
that.
B
See
I
mean
we
need
to
set
up
the
web
hook,
the
github
webhook
to
fire,
not
just
on
releases
but
on
every
commit,
and
then
we
need
the
project
module
to
respond
to
that
new
commit
has
been
created
things
so
so
that
I
don't
think
this
is
blocked.
Currently
it
just
requires
some
work
in
a
project
module.
Specifically,
you
could
set
this
up
even
with
that
backdrop
see
most
org,
because
project
module
is
generic,
so
it's
possible
to
do
this
just
by
improving
project
module
and
then
we
would
deploy
a
new
version
of
project
module.
B
C
A
A
So
there's
a
bunch
of
other
issues,
director
of
CMS,
org
I,
don't
think
anything's
gotten
very
much
attention
lately,
because
we've
been
working
on
it
backdrop
the
product
itself,
but
I
didn't
want
to
talk
about
the
translation
site.
Just
cuz
I
saw
that
woluf
already
has
a
114
translation
file
up,
so
I
was
really
excited
back
up,
which
is
great.
I
also
noticed
that
we're
getting
new
languages
and
main
language
containers,
which
is
really
exciting,
Lana
Lang,
looks
like
translations
all
right.
Let's
go.
Nobody
need
to
talk
about
the
project.
B
Hey,
alright,
so
I
don't
think
I
was
in
the
meeting
last
week
because
I
haven't.
Oh,
you
know
what
it
is
is
that
sorry
I
thought
we
already
celebrated
the
release
of
backup
114,
but
this
is
the
first
meeting
since
backup
114
has
come
out.
So
that's
what
I'm
so
confused
about
and
that's
it's
only
been
four
days.
Oh,
my
goodness,
it
just
seems
like
it's
been
a
lifetime
already
yeah
backdrop:
114
came
out.
B
And
it
turned
out
to
be
a
pretty
pretty
good
release.
We
had
lots
of
great
new
stuff
in
there.
I
think
feel.
Double
files
and
flexible
layouts
kind
of
taking
the
headlining
slots
I'm
also
really
excited
to
see
that
our
release
process
went
really
well.
This
time
around,
like
and
Jim,
you
played
a
large
part
in
that
I
think
getting
all
of
our
our
blog
posts
and
or
tweets
all
of
our
basically
public
facing
stuff
all
lined
up
and
shipped
out
promptly
after
the
release
itself
came
out
so
yeah.
B
B
B
Now
what
this
means
is
that
all
bug
fixes
that
didn't
get
into
the
114
didn't
get
into
113.
Previously
113
is
basically
not
only.
Maintenance
mode
will
still
be
applying
security
patches
if
they
come
out
for
the
next
four
months.
114
is
receiving
all
bug
fixes
from
here
on
out,
though,
that
are
not
security
release,
not
security
related,
so
so
a
couple
of
those
ones
that
have
carried
over
the
first
item
for
114
one,
the
first
bug
fix
release.
B
Oh
I
should
also
add
that
we
haven't
seen
like
it's
been
quiet
in
the
issue:
queue
regarding
regressions
introduced
in
114,
like
it's
been
four
days
now,
like
114,
specific
issues
or
just
like
pretty
negligible.
So
that's
been
awesome,
so
I'm
really
just
happy
that
we've
had
a
the
114
release
came
out
and
it
for
the
most
part,
has
been
really
pretty
stable,
like
the
parts
that
we
released.
Tim
found
something
that
was
talked
about
specific.
B
We
think,
but
that
was
my
fault
not
know
not
doctor
up
114
s,
release
problem
so
anyway,
114
one
bug
fixes
that
we
can
pursue.
We've
had
this
long-standing
issue
that
the
views
is,
none
of
operator
has
been
broken
for
quite
some
time.
It's
issued
3614
gen,
there's
some
updates
that
you
have
done
documents
as
well.
Can
you
summarize
the
state
of
that
yeah.
A
A
A
A
D
D
A
Like
we
already
have
sites
that
have
to
apply
this
patch
every
single
time,
we
have
an
update,
so
every
single
time
we
update
their
sites
for
opener,
we're
inconveniencing
these
people
or
I
feel
like
a
lot
of
the
other
bug.
Fixes
that
are
going
in
are
for
like
kind
of
obscure
things,
but
there
is
none
of
operator
is
something
that's
commonly
used.
So
I
think
that
it's,
you
know
more
important
than
a
lot
of
the
other
ones.
I,
don't
think
we
should
wait.
You
know
another
release
or
two
before.
D
So
the
meta
reviews
meta
has
like
eight
subtasks
and
we
only
have
gotten
20
of
them
if
we
get
it
at
this
rate,
it
means
that
this
weeks
will
be
delayed
right
so
yeah.
If
we
can
get
committed
to
okay,
I
could
get
committed
to
creating
the
cross
ports,
that's
it,
but
we
need
someone
to
review
if
we
can
get
commits
to
have
them
reviewed,
because
some
of
them
are
really
simple
as
well
and
commuted
by
the
string.
D
Then
yes,
let's
delight,
but
otherwise
I
think
that
if
we
can
verify
at
least
a
couple
of
people
can
verify
that
we
fix
the
problem
for
them
and
it
has
been
that's
that's
the
template.
We've
been
getting
for
some
time
now,
then.
The
thing
that
we
shouldn't
delay
any
longer
like
it's
been
fixed
seems
fine,
but
yeah.
It's
maybe
a
couple
of
weeks
is
now.
You
know
before
1:13
right.
B
D
D
So
a
but
I've
also
added
the
40
46
minute
for
the
flexible
layout.
There's
a
few
issues
there
and
my
the
reason
why
I
added
the
fair
is
I'm,
not
sure
if
we
can,
how
many
or
if
we
can
get
any
of
those
things
done
in
the
next
one,
but
we
have
but
more
as
a
general
thing
as
in
these,
don't
have
to
wait
for
the
next
one.
Love
minor
third
release
right:
the
115
yeah.
D
D
And
also
I
think
4052.
Sorry,
there's
only
45
is
affecting
the
list
that
we
have
the
block
list
in
the
reports
like
if
you
visit
that
page
other
screenshot
on
that
ticket.
So
I've
noticed
that
if
you
got
to
be
the
list
that
we
have
of
the
blocks
where
we
report,
which
layout
is
using
them
in
which
region,
because
the
regions
have
random
names,
it's
like
the
whole
layout
of
the
table
is
talking
now,
because
it
has
this
huge
yeah
links
to
the
respective
place
where
the
blocks
are
being
used.
D
E
A
A
A
That
we
don't
allow
anyone
to
add
IDs
anywhere
else
and
that
people
aren't
supposed
to
be
using
their
IDs
for
this,
so
I,
don't
know,
I
mean
so
like
jump
into
places
in
content.
The
ID
should
be
in
the
content,
not
in
the
layout,
but
so
your
use
case
is
not
the
use
case.
I
thought
you
were
having
I
thought.
It
was
for
writing.
Css
and
I
was
like
I,
think
a
class.
A
A
F
A
E
A
G
E
A
C
A
E
C
Mean
to
me
that's
one
of
the
big
benefits
of
the
flexible
layouts
is
the
ability
to
do
something
like
this,
so
I
had
not
I
think
the
thing
that
I
hadn't
gotten
to
yet
that
Olaf
has
is
the
menu,
the
navigation
for
that
page
right,
I
was
I've
been
more
focused
on
just.
Can
I,
through
the
UI
sort
of
create
these
banded
regions
and
quite
excited
about
some
of
the
things
we've
done
that
make
that
possible,
but
it
hadn't
occurred
to
me
that,
like
okay,
how
do
I
navigate
map
down
on
this
page
yeah.
A
G
E
Okay,
but
then,
when
you
want
to
place
some
blocks
there,
for
example,
I
want
to
place
a
views
block
the
with
some.
You
know
some
posts,
for
example:
that's
not
possible
when
I
have
a
blog
as
a
row.
I
can
put
these
blocks
in
a
block
or
maybe
it's
possible,
the
very
special
configuration
but
I
think
it's
too
complicated.
You
see.
E
A
E
D
C
B
I'm
with
all
that,
like
in
my
head,
but
I,
haven't
tried
it
right,
so
yeah,
I'm
kind
of
fitting
the
same
way
that
it's
like
it
seems
like
the
ID
that
we're
adding
right
now
is
completely
worthless.
It's
a
big
UUID.
So
what's
the
value
that
it's
like
you
know
replacing,
it
seems
like
it
would
be
a
good
thing,
but
I
also
see
that
we
don't
have
IDs
in
a
lot
of
other
places
like
blocks.
You
can't
specify
the
ID.
Okay,
that's
by
the
class,
so
yeah
I
mean.
A
A
B
D
B
D
C
May
have
to
say
that
the
flexible
layouts
module
has
got
me
thinking
about
experimental
modules
in
core,
because
I
feel
like
we're
in
covering
things
that
might
be
a
little
bit
difficult
to
fix
that
just
our
heart.
That
would
have
been
hard
for
us
in
the
regular
cutting
process
to
uncover
I.
Don't
know.
D
A
Because
it
was
a
new
module
was
just
added
to
layout,
so
that
would
wouldn't
have
worked.
That
way.
I
mean
I.
Think
the
real
problem
here
is
that
not
enough
people
are
testing
the
preview
and
I.
Don't
I
wouldn't
want
to
introduce
a
something
that
would
affect
her
and
users.
If
the
problem
is
with
our
process.
A
Hey
I
installed
the
preview
and
a
bunch
of
sites,
but
I
don't
use
the
layout,
though
there's
some,
but
my
clients
got
to
edit
site
so
that
they
didn't
have
any
friends,
but
yeah
I
mean
I.
Think
like
when
we
put
in
big
new
features
like
this.
It's
tough
because
there
are
four
new
users,
and
so
installing,
like
a
preview
version,
is
something
that's
not
a
new
user
does
yeah
hello,
checking.
D
D
And
also,
we
could
luck
with
this
newsletter.
We
could
draw
attention
to
the
things
that
we
actually
mean
tested
like
no
problems
was
reported,
of
course,
as
expected
with
the
ckeditor
update,
which
was
done
a
little
bit.
This
time
was
done
a
little
bit
last
minute,
but
I
would
like
to
say
to
people
that
a
we
are
updating
component
x.
So
can
you
please
just
yeah,
try
to
kick
the
tires
and
see
if
anything's
broken.
B
Okay,
yeah
I
also
want
to
say,
there's
another.
The
next
item
on
the
agenda
actually
is
another
thing
related
to
flexible
layouts,
that
some
classes
that
are
on
other
layouts
are
not
on
flexible,
that's
including
el
header
and
footer,
and
that's
causing
it
so
that
things
like
the
hero
and
menu
block,
don't
show
up
correctly,
unless
you
add
those
classes,
and
so
there's
some
discussion
happening
on
that
issue
over
in
48
66
looks
like
there's
some
options.
There.
B
I
was
a
middle
of
posting,
a
comment
there
as
well
like
saying,
which
way
I
would
take
that.
So
it's
good
that
we've
got
some
approaches
in
progress.
There
there's
also
a
bigger
meta
issue
at
forty
forty
six.
That
is
like
a
checkbox
meta
of
follow-up
issues
for
flexible
layouts,
but
there
are
some
other
items
listed
in
there
as
well,
but
that's
yeah,
looking
at
the
one
fourteen
one
list,
maybe
I
was
a
little
too
optimistic
at
the
beginning
of
this
meeting.
I
was
like
oh
it's
so
great.
B
I
B
Let's
see
also,
we
don't
have
this
in
the
agenda,
but
we
could
find
that
issue.
We
bump
to
an
issue
from
114
that
was
related
to
field
about
files
that
there's
a
managed
file,
display
tab
right
now
on
the
file
types
and
that
really
it
would
be
preferable.
That
was
just
under
the
the
display
modes
page
itself
like.
B
B
A
B
A
A
A
Let's,
let's
talk
about
when
we
get
to
115
zero,
because
I'm
happy
to
be
that
advocate
for
that
issue
of,
but
not
also
that
the
other
issue
and
the
other
issue
we
think
already
has
a
patch,
that's
like
in
a
near-complete
status.
So
if
you
guys
don't
want
that
issue,
I'll
just
remove
myself
and
only
do
this
one
and
you
guys
do
want
that
issue.
Then
I'll
do
this
one!
Next,
okay,.
B
They
don't
have
any
progress
updates
on
this
one.
This
past
week
you
know
or
two
actually
it's
been
getting
114
out
the
door
and
unfortunately
like
just
with
working
through
all
the
other
pull
requests
and
review
and
stuff
like
that.
I
didn't
have
any
time
to
actually
invest
development
time
into
updating
project
module
further,
so
same
statuses
before
working
on
project
module,
we
need
to
do
some
additional
merges
into
project
module
and
then
make
a
new
release
of
that.
B
B
C
So,
where
this
got
left,
it
was
Nate
your
your
concerns
about
I
think
how
we're
generating
some
of
the
output
and
it's
a
little
bit
stalled.
Just
because
I
feel
like
well
I,
don't
know.
I
could
try
to
dig
in
and
see.
If
that's
something
I
can
fix
myself.
Jeff
was
the
most
active
helper
on
this
and
he's
just
been
a
little
busy
lately.
So
he's
not
been
around
to
help
he's.
C
D
A
A
D
C
A
Ask
me
to
fix
the
control.
I
could
do
that
and
then
you
could
go
back
to
Jeff
like
can
you
make
them?
You
do
this
thing
with
the
module
and
that
might
be
a
more
palatable
thing
for
him
because
he's
probably
like,
oh
god,
it's
gonna
be
a
lot
of
work
because
I
don't
know
any
of
that
code
right.
If
I
do
that
part,
he
can
do
it
here.
Any
knows
really
well
right.
B
A
So
this
was
a
dribble
7
module
called
image.
Cache
tokens
that
basically,
for
every
image
token
you
have
it
gives
you
one
for
each
image
style.
I
use
this
all
the
time,
because
I
use
a
meta
tag.
All
the
time
and
I
want
it
to
happen
that
when
you
share
a
version
of
your
post,
it'll
put
an
appropriately
sized
image
in
there.
So
the
og
image
tag
in
the
header
needs
to
not
necessarily
point
to
the
default
image,
which
is
what
it
would
do.
A
If
you
use
the
normal
image
tag,
you
want
to
use
special
image
style
for
that
I.
Don't
know
if
this
is
an
80%
use
case,
which
is
why
I'm
like
I'll
advocate
for
it,
but
I,
don't
know
if
you
guys
are
gonna
want
to
in
or
not,
but
I
wrote
it
as
an
image
style
patch,
because
I
was
hoping
that
it
wouldn't
be
a
big
deal
to
put
it
in
court.
A
If
you
guys
don't
want
it
or
I'll,
probably
just
make
a
new
module
called
English
style
tokens
instead
of
image,
cache
tokens
or
I,
don't
know,
what's
worth
keeping
the
image
cache
tokens
name
around,
but
yeah
it
don't
get
some
sell
for
a
forward
and
I
come
aunt.
Has
tests.
I
I
A
A
A
You
probably
won't
notice
until
you
try
and
share
one
of
your
posts
on
social
media
and
the
image
it's
entirely
the
wrong
size.
So
for
me,
and
it
seemed
like
it
wasn't
necessarily
that
like
image
cache,
though
this
isn't
80%
use
case,
but
sharing
content
once
Media
is
that
you
should
do
everything
we
can
to
make
that
process
work
better
and
background.
That
makes
sense
to
me.
Yeah.
B
Is
there
maybe
a
lot
of
thing
you
might
make
it
not
so
clickable
is
that
for
the
most
part,
once
social
media
sources
like
accept
any
size
image
as
long
as
it's
big
enough,
like
images
that
are
too
big,
they
already
make
their
own
thumbnails
for
you
when
they
show
it
inside
of
Twitter
or
Facebook
or
whatever,
and
so
giving
a
really
big
image
to
those
social
media
outlets
doesn't
seem
like
it's
usually
a
problem
because
they
make
their
own
thumbnails
anyway,
yeah.
A
But
sometimes
you
might
want
to
give
them
an
image
that
matches
their
like
exact
requirements
like
the
Facebook
is
pretty
tough
requirements.
I
ran
into
this
recently
because
I
had
a
site
that
had
original
images
that
were
like
900
pixels
and
they
need
to
be
1400
or
something
like
that
and
so
I
had
to
go
through
and
like
replace
the
actual
content
with
other
content,
and
then
I
didn't
want
to
use
the
big
files
on
this
site
and
one
of
the
little
files
on
the
site.
A
Which
service
it
is
there,
so
that
would
be
like.
Oh,
if
it's
not
the
right
dimensions
create
derivative
image
where
it
gets
fuzzy
just
because
of
the
process
of
creating
the
derivative
image
where,
if
you
give
them
exactly
the
same
image
and
exactly
the
same
sizes,
they
don't
create
a
derivative.
So
it's
not
fuzzy
yeah.
B
A
B
D
This
is
we
had
it
so
I'll
try
to
dig
up
this
issue
that
comes
to
mind
now.
I
can't
remember
the
exact
issue
and
what
it
was.
But
I
have
these
comments.
First
off
in
d7
talking
was
contributor.
Now
it's
in
core
and
then
I
recall
these
kind
of
tokens,
where
they
dig
deep
into
properties
of
things
mean
separate,
contribute
modules.
So
for
the
thing
is
that
we
have
a
very
putting
core
in
combination
with
token
I
feel
like
those
things
should
be
in
core.
Does
that
make
sense.
A
D
A
D
It
would
be
Colin
Colin
short
column,
because
then
I
was
in
court
cooking
it
in
court,
but
there
was
a
separate
module
that
would
provide
those
tokens
I'm
not
sure.
So
it
makes
sense
for
me
to
me
now
that
both
these
modules
are
in
court
to
actually
be
providing
those
tokens
like
it
would
be
expected.
I
guess.
A
B
B
C
A
So
I,
don't
know,
I'd,
be
fine
with
bumping
this
and
asking
for
more
feedback
and
seeing
if
other
people
have
other
use
cases
than
this
I
can
continue
to
play
the
patch
for
another
release
or
so
and
I
would
give
you
know
other
people
a
chance
to
be
like.
Oh
I
use
it
on
X.
It's
really
important
or
I've
never
used
that
we
don't
need
it,
and
maybe
we
can
also
work
on
the
image
sharing
problem
first
and
then,
if
it
turns
out
that
problem
was
solved,
we
don't
need.
A
B
I
would
probably
also
just
go
ahead
and
make
it
a
control,
rather
than
applying
a
patch
like
have
a
bacon
chair
module.
If
it
gets
me
moved
into
core,
then
we,
you
know
treat
it
like
all
the
other
modules
that
we
move
into
core.
You
know
we
put
it.
We
automatically
disable
it
on
upgrade
and
then
post
a
message
saying
you
can
delete
the
module.
Okay.
I
A
B
B
B
Yeah
and
all
of
the
so
many
things
that
are
like
you
know
things
that
show
up
on
the
note
form
that
are
like
in
the
vertical
tabs
down
at
the
bottom,
like
a
lot
of
those
things
that
could
be
moved
from
the
content
type
settings
to
the
form
settings
instead
in
suits
like
that.
That
way,
you'd
be
configuring,
it
all
in
one
place.
Instead
of
someone
that
content
type
and
someone
the
field
settings
yeah,
okay,.
B
All
right
yeah,
but
man's
file
display
being
the
immediate
problem,
because
it's
like
a
big
big
new
UID
like
well
thanks
going
on
here,
yeah
yeah,
okay,
let's
see
so
accept,
is
provide
a
way
to
bring
in
abil
disabled
text
formats
issue
1575,
there's
something
advocate
listed
here,
but
I'm
guessing
that's
Gregory
Gregory
can
use
an
update
on
them.
D
The
text
formats
so
there's
a
UX
issue
that
we
need
to
solve,
and
that
is
the
problem
of
saying
telling
people
that
if
they
move
on
with
the
action
of
disabling
the
text
format,
we
actually
remove
it
from
the
user
interface
at
least,
but
then
the
we
dug
a
little
bit
deeper
into
that.
And
then
we
thought
that
maybe
we
should
also
allow
them
to
be
able
people
things
that
could
so
that
it
sounds
like
a
feature
because
it's
something
new.
It
was
not.
D
It
was
not
there
before,
but
the
you
think
the
problem
is
a
bag.
So
the
specification
is
classified
as
a
bug
report
at
the
moment
and
that's
for
the
UX
bit
like
that.
We
tell
people
that
we're
going
to
disable
things
that
we
actually
remove
them
with
no
way
for
them
to
we
enable
them
unless
they
go
into
Poli.
D
A
D
And
it
sounds
really
logical
what
he
suggested.
We
just
keep
things
as
they
are
mostly
and
we're
just
introducing
new
function
that
gets
the
all
formats
or
for
the
purpose
of
listing
them
in
the
admin
page
where
we
enable
them,
and
this
then,
for
the
rest
of
the
places
we
just
keep
using
the
old
the
old
function,
that
it
says,
the
results
that
we
want.
It
sounds
sacred
yeah.
B
A
B
B
Well
we
have
the
ability
to
select
an
image
from
the
library
as
well
as
doing
an
upload,
so
I
mean
it
seems
really
straightforward
and
even
from
a
UI
perspective,
it
might
be
pretty
straightforward,
but
from
a
technical
implementation,
we
probably
have
some
debt
to
pay
down
here
that
we
took
some
shortcuts
with
the
image
modal
when
we
integrated
it
into
the
editor.
So
I
am
feeling
that
implementing
this
into
image
fields,
you
know
it
will
probably
need
to
do
some
consolidation
and
make
it
so
the
same
code
is
used
in
both
places.
B
I
do
some
tidying
up
there
from
what
I've
seen
I,
don't
think,
there's
any
there's
no
pull
request
here.
This
is
just
like.
Yes,
this
is
a
good
idea,
so
we're
in
the
stage
of
like
you
know,
we
have
to
figure
out
how
we're
gonna
approach
this
from
a
technical
perspective,
maybe
also
figure
out
some
UI
problems
with
like
how
is
the
link
going
to
be
showing
to
select
from
library
versus
upload
and
things
like
that.
So
yeah
I'm
excited
about
this.
This
is
such
an
obvious
thing
that
should
exist.
A
Also,
this
isn't
related
well,
this
isn't
on
our
agenda,
but
it
is
related.
I
was
also
thinking
that
we
might
end
up
needing
something
like
inline
entity
form.
Now
that
we
have
filled
up
old
files
when
you
upload
a
file,
you
can't
add
any
fields
to
it
in
the
same
way
that
when
you
upload
an
image
you
can't
like
choose
from
the
library,
it's
like
we're,
adding
features
and
some
places,
but
not
others,
I,
don't
know
what
that
looks
like
yet
so
I
haven't
created
an
issue
but
same
sort
of
thing
where
it's
like.
B
B
A
B
A
B
B
B
D
D
C
D
B
Okay,
great
all
right:
let's,
let's
wrap
it
up
yeah.
Thank
you.
Everybody
great
release
on
114
very
excited
to
have
that
out
there
and
in
the
wild.
Now
it's
blue
sky
time
for
115
and
what
we
can
potentially
do
before
January
15th.
So
thank
you
guys
all
for
joining
me
today.
Thank
you
guys
all
for
the
great
release
and
see
you
guys
on
the
internet.
Yeah
I.