►
From YouTube: Backdrop Weekly - April 9, 2020
Description
This weeks Dev meeting was only two people, but we went through the full agenda with updates on several issues, including a discussion of the new "forward revisions" issue (in search of a better name). There is even a short screen share of that issue.
https://github.com/backdrop/backdrop-issues/issues/4354
A
B
B
A
John
Lambton
I
am
here
in
Oakland,
California
I've
also
been
doing
backup
for
a
few
years.
Let's
see
this
week
has
been
particularly
stressful
for
me,
because,
thanks
to
the
Cobra
pandemic,
all
of
the
work
I'm
doing
on
government
sites
seems
to
be
urgent.
There's
a
lot
of
need
to
update
people
on
current
status
of
stuff
and
changing
the
way,
meetings,
work
and
a
lot
of
just
website
change
stuff
which
isn't
really
interesting.
A
Based
on
how
a
lot
of
the
world
is
slowing
down
in
terms
of
industries,
it
makes
me
feel
grateful
to
be
in
online
web
stuff
where
I
feel
like
we
are
still
we've
got.
You
know,
we've
got
paying
jobs
and
roofs
over
our
heads
and
we're
in
a
good
position.
So,
even
though
the
work
is
stressful,
I
am
happy.
I
still
have
a
job.
A
Okay,
let's
see
for
today's
agenda.
We
have
a
couple
of
items
in
the
1:15
to
release.
Normally
quick
sketch
would
do
this
Nate,
but
he
is
unable
to
make
it
today
so
I'll
just
run
through
these
top
issues.
Here
looks
like
we
have
a
new
issue
added
today's
gendai,
which
is
number
34.
89,
which
is
an
old
issue
that
Larrin
wanted
us
to
take
a
look
at.
A
A
A
So
this
is
labeled
in
here
as
a
bug
and
a
bunch
of
other
bunch
of
people
are
reporting
the
same
thing
and
wondering
if
that
was
intended,
which
I
think
it's
not
and
then,
if
we
should
fix
it,
so
I
would
agree
that
that
is
fairly
important.
I'm
gonna,
add
the
bug,
fix,
milestone
candidate
label
and
we'll
take
a
look
at
how
hard
it
is
to
fix
so
much
if
anyone's
looked
at
that
yet,
but
that
could
be
a
trivial
bug
fix
that
could
go
in
at
any
time.
A
A
Okay,
Thank
You
Larry
for
bringing
that
up.
It
looks
like
we
don't
have
any
other
issues
that
are
specifically
highlighted
for
the
115
milestone,
but
there
has
been
a
ton
of
progress
made
on
all
of
the
bugs
and
then
115
a
milestone
that
I've
had
four
requests.
Chocolate
went
through
a
ton
of
them
and
made
sure
the
pork
was
still
applied
or
updated
with
they
didn't
closed
issues
if
they
weren't
relevant
anymore,
just
a
lot
of
triage
on
that
list.
A
B
A
You
dr.
Elmont
for
spending
so
much
time
on
our
bug
list.
It's
great
all
right
next
is
the
116
milestone,
which
has
a
tentative
release
date
of
May
15th,
which
is
coming
right
up
here.
Our
feature
freeze
date
for
that
is
May
1st.
So
any
of
these
issues
that
we're
working
on
now
that
we
want
to
get
in
by
May
1st
have
less
than
a
month
to
get
them
done,
so
just
to
kind
of
put
some
pressure
on
that.
A
A
We
had
an
autocomplete
option
in
a
couple
of
places
like
in
the
rich
text
editor
when
you
were
adding
a
link
you
could
type
in
something
and
it
would
autocomplete
on
the
top
and
give
you
a
link
to
internal
content,
but
we
had
a
bunch
of
other
places
where
we
had
linked
our
path
fields
that
didn't
have
that
functionality,
and
so
this
law
request
added
that
feature
consistently
through
these
our
interface
anywhere.
There's
a
length
field,
you
can
now
use
autocomplete,
which
is
pretty
cool.
A
A
Pheww,
panda,
I
think
that
went
to
the
list
and
they
did
ton
of
work
on
it.
So
thanks
Peter
for
spending.
So
much
time
on
getting
that
one
Yin
for
us
that'll
be
really
helpful
and
then
the
next
one
is
just
sort
of
an
annoyance
that
colones
recognized
a
long
time
ago.
We
have
the
ability
in
Drupal,
starting
in
Drupal
7
to
disable
a
text
format
and
when
you
do
that
it
disappears
from
these
your
interface
with
no
way
to
turn
it
back
on.
A
This
pull
request
just
provides
a
disabled
section
in
the
text,
areas
page
so
that
you
can
turn
on
one
that
you've
turned
off
before
and
so
that
it
is
visible
that
it
exists
and
it's
disabled.
So
it's
a
little
user
experience
improvement.
This
is
number
15
75
and
it
is
also
marked
our
TBC,
so
we've
got
that
ready
as
well,
which
is
great
the
next
one.
This
is
issue.
1032
adds
a
new
text,
format
interface.
A
So
still
in
that
text,
formats
page
most
of
the
page
is
unchanged,
but
we
used
to
have
these
weird
vertical
tabs
at
the
bottom.
They've
now
been
replaced
with
a
modal
system
that
works
a
little
bit
more,
like
filled
UI
with,
like
it
config
your
link
on
one
side,
an
you,
click
the
link
and
then
a
box
pops
up,
and
you
can
figure
it
and
you
save
it.
A
A
B
Sure
so
that
one
is
allowing
us
to
use
tokens
to
modify
the
like
the
submitted
by
person
and
date,
and
so
you
can
change
the
date.
Format
with
tokens
in
the
UI
and
I
have
been
updating
for
the
last
three
weeks,
but
I
didn't
update
the
issue.
My
mistake,
I
should
have
put
notes
in
here
what
we
talked
about
last
week.
I
think
this
is
we've
got
it
marked
as
works
for
me.
B
B
A
B
B
We
could
I
do
a
quick
screen
screen
share,
yeah,
okay,
because
then
I
can
I
have
the
the
PR
open
and
the
ish
one
of
the
issues
that
came
up
that
I'd,
like
your
feedback
on
I,
could
show
you
so
I'm
confused
going
to
the
wrong
app
here.
We
go
screen
share.
Okay,
let's
just
do
you
look
at
the
whole
desktop
I
think
I'm
sharing
right,
yep,
okay!
So
actually
let
me
switch
back
to
the
issue.
So
the
issue
here
is
a
workflow
issue.
B
We
want
to
create
the
ability
for
a
user
to
create
a
have
a
draft
of
a
published
node.
So
basically,
if
you
have
an
about
page
and
somebody
edits,
and
it
makes
its
changes,
they
can
save
those
changes
without
publishing
those
changes,
until
maybe
somebody
else
reviews
them
and
then
says:
okay
and
that
becomes
the
and
I
shouldn't
be
using
the
term
published
we're
using
the
term
current
right,
Chris
occurred.
The
current
version
is.
B
B
According
to
the
issue,
we
want
to
call
that,
yes,
the
approved
version
you're
right,
so
the
approved
version.
It
would
be
the
version
that
the
public
would
see
if
it's.
If
the
note
is
published-
and
you
can
have
a
draft
version-
that's
newer
than
the
approved
version
anyway.
So
if
we
actually
go
to
the
the
PR
one
of
the
questions
well,
so
doc,
Wilmont
earlier
this
week
had
a
concern
on
the
UI.
Let
me
just
click
on
the
edit
node
I
want
to
see.
B
Okay,
I
think
he
hasn't
done
this
part
yet,
but
we
we
have
some
suggested
changes
to
if
you're
saving
the
current
version,
so
you
can
like
well
again.
If
we
go
back
to
the
issue,
you
have
the
option
to
save
and
approve
or
save.
A
new
draft
is
what
we're
recommending
and
he
hasn't
fixed
like
to
save
and
approve.
B
He
had
a
concern
that
there
were
the
previous
incarnation
of
this
issue
that
we
were
looking
at
say
three
months
ago,
quick
sketch
had
raised
some
concerns
about.
Maybe
we
were
changing
the
UI
too
much
and
doc.
Wilmont
was
concerned
that
this
PR,
maybe
does
it
even
more
than
that
one
did
I,
went
back
and
sort
of
looked
through,
quick
sketches
concerns
and
I
think
most
of
them
just
were
that
they
weren't
working
right
at
the
time.
B
A
B
I,
looked
it
over
and
I
said,
I
think,
you're,
probably
safe
and,
and
you
know,
quick
sketches
certainly
have
the
opportunity
to
at
least
see
our
screenshots,
and
he
hasn't
said
anything
so
I
think
doc.
Wilbon
decided
to
go
ahead
and
do
some
work
on
it
and
he
did
I'm
not
seeing
the
changes
here,
but
where
we
are
seeing.
The
changes
is
on
the
revision,
and
this
is
where
Jen
I'd.
Like
your
opinion,
we
were
still
using
the
term
clone.
B
We
didn't
want
edit,
because
you're
not
editing
a
draft
right,
because
you're
actually
making
a
new
one
and
I
I
think
we
had
talked
about
some.
Some
wordier
versions
and
I
just
threw
out
this
idea
to
doc
Wilmot
and
he
liked
it
so
I
said
well:
go
ahead
and
implement
it
we'll
get
feedback.
So
it's
a
little
clone.
It's
copy,
a
medic
yeah.
A
A
A
B
A
I
feel
like
copy
and
edit
is
pretty
clear,
because
what
people
want
to
see
when
they
land
on
this
page
is
an
edit
link
and
the
fact
that
they
don't
get
to
edit.
Something
is
like
they
don't
necessarily
know
that
when
they're
looking
for
the
link
and
clone
might
be
confusing
so
like
I
just
want
to
edit
it,
this
at
least
gives
them
the
idea
where
it's
like.
Okay,
you,
what
you
want
is
edit,
but
you're
not
allowed
to
edit
this
one.
You
can
only
copy
and
edit,
so
to
sort
of
also
train.
A
So
I'm,
like
here's,
the
word
you're
looking
for,
but
here's
what
you
actually
get
so
I'm
I
am
happy
with
copy
and
edit
I
also
like
the
fact
that
the
act
of
what's
it
called
default,
current
publish
approved
one
just
says
edit
I
think
it's
also
really
clear
is
like.
If
you
want
to
edit
the
page,
that's
already
there,
you
can
all
of
the
other
ones.
You
have
to
make
a
copy.
So.
A
A
I
think
we
had
some
I
think
we
had
some
workflow
issues
about
that,
because,
right
now
you
can't
edit
a
current
version
I
like
the
ability
to
add
a
current
version,
but
I
don't
know
if
that
was
in
our
spec.
That
might
have
been
something
that
was
in
the
previous
iteration
I'm
buying
with
it
I
think
that
people
might
want
that.
B
A
A
B
B
So
good,
okay,
so
he's
made
this
definitely
some
forward
progress
on
this
yeah
and
and
probably
enough
the
people
could
go
like
a
week
ago.
I
would
have
said
it's
not
worth
looking
at,
because
there
was
so
much
that
we
changed
from
the
PR,
but
I
think
it's
getting
back
to
where
you
could
look
at
it
again
and
and
make
some
comments,
even
though,
but
if
you
are
looking
at
it
and
giving
comments,
I
recommend
reading
through
the
issue
summary,
because
there
are
some
things
that
we're
planning
to
change
that
aren't
reflected
yet
do.
A
B
A
Okay,
let's
see
I
seem
how
entered
full-screen
and
I
can't
get
my
agenda
back.
Okay.
Here
we
go
so
that's
great.
That
was
all
the
issues
we
have
scheduled
for
1/16.
There
are
two
issues
that
are
currently
in
the
milestone
that
will
roll
overs
from
the
previous
115
milestone
that
didn't
get
in.
One
of
them
is
the.
A
Signing
of
download
packages
so
that,
if
you
wanted
to
update
core,
for
example,
you'd,
be
sure
that
you
are
getting
the
actual
version
of
core
that
we
said
you
were
getting
and
that
issue
requires
some
changes
to
project
module
in
addition
to
changes
to
core,
and
so
it
hasn't
been
getting
a
lot
of
attention.
It's
on
Nate's
plate
to
take
a
look
at
that
one
and
the
other
one
is
on
my
plate,
and
that
was
the
file
file
field
display
settings.
A
Even
though
it's
not
technically
a
field
we'd
like
the
settings
to
be
in
the
interface
where
people
expect
to
find
them
and
that
same
thing
applies
to
I-
think
an
issue
you
are
working
on,
Tim
I,
think
is
on
the
date
date
format
configuration
that's
also
something
that
could
live
on
the
fields
UI
tab
rather
than
on
the
content
type
tab,
I'm,
not
sure,
if
that,
if
it's
better
there
or
not,
but
I
thought
I
mentioned
in
that
issue,
just
something
to
think
about
there
and
then
there's
the
file.
The
file
filled.
A
Display
settings
should
also
be
settings
on
the
file
field
itself,
not
on
a
separate
tab.
So
there's
a
bunch
of
stuff,
that's
all
kind
of
mixed
up
there,
I'm
not
really
sure
which
one
of
those
needs
to
go.
First
I've
been
working
on
that
file
filled
one
because
that
was
something
that
went
into
core
recently
and
I
feel
like
it's
gonna,
be
confusing
to
people
who
haven't
used
final
entity,
module
in
Drupal
7
or
are
new
to
backdrop.
A
So
where
I
am
right
now,
as
I
have
a
pseudo
field
with
settings,
but
only
has
one
field
on
it
and
it's
in
file
UI,
so
I'm
not
sure
that
one's
gonna
get
in
by
116
I
would
love
it
to.
But
I
haven't
had
the
time
to
work
on
it
lately.
So
that's
where
that
one
is
but
I
have
not
pushed
a
pull
request
for
that
and
I
think
that
if
I
did,
I
might
be
able
to
get
some
more
help
with
it.
So
I'll
try
and
at
least
get
my.
A
A
The
one
thing
we
wanted
to
mention
this
week
is
that
next
week
on
April
16th,
we
will
be
talking
about
the
initiatives
that
have
been
proposed
in
the
forum
and
they
don't
have
to
be
necessarily
final,
but
they
should
be
close
enough
that
we
can
submit
them
to
the
PMC,
and
if
there
are
a
bunch
that
we
like,
we
can
say
hey.
We
think
these
four
should
be
backtracks
initiatives
for
the
next,
really
so,
probably
not
116
but
117.
So
it
would
be
the
next
four
months
or
I.
A
Don't
know
how
long
a
year
whatever
it
is,
we
decide.
They
might
say,
and
then
proposal,
my
god,
but
just
something
we
make
are
good
ideas.
We
can
say:
hey
PMC,
the
community
thinks
these
are
solid
proposals
shouldn't
they
be
initiatives.
Yes,
no,
and
we
can
record
from
that.
So
if
anyone
is
watching
this
meeting
and
is
curious
about
proposed
initiatives,
please
check
the
forum.
B
Things,
one
of
which
is
doc
Wilmont
amongst
others,
have
been
raising
the
alarm
that
it
is
three
weeks
no
code
freeze
future
freeze
three
weeks
from
tomorrow
and
come
back
to
that
date
in
a
second,
and
that
he'd
certainly
like
to
get
some
folks
to
help
review
some
issues
and
make
some
progress
before
the
24
hours
before
feature
freeze.
So
some
of
us
are
talking
about
doing
a
sprint.
This
Sunday,
doc,
Wilmont
and
Jeff-
know
Gregory
and
myself
have
already
committed
to
it.
B
Others
might
show
up
to
just
try
and
focus
on
some
things
for
the
next
release.
That'll
be
this
Sunday
at
1:00
o'clock,
Pacific
time
for
a
couple
of
hours,
we'll
be
online.
So
if
anybody
is
available
to
help
with
that
great,
the
last
thing
would
be.
This
would
normally
be
an
outreach
meeting
Jenn,
but
should
we
talk
quickly
about
the
Phillie
camp
CMS
on
this
meeting,
I
think
you're?
Muted.
No,
sorry.
B
There
well
we've
exchanged
a
couple
of
emails.
We
asked
them
if
we
could,
if
they
would
sort
of
add
backdrop
to
their
list,
because
it's
a
that
we
used
to
be
Drupal.
Delphia
and
they've
been
working
with
the
local
WordPress
group
and
they
wanted
to
make
it
more
generic
to
CMS's,
so
they're
calling
I'm
at
CMS
Philly.
It's
going
to
be
a
virtual
event,
and
this
connects
to
the
last
agenda
item
because
it
is
scheduled
to
be
May
1st,
which
would
be
feature
freeze.
B
So
if
we
are
like
doing
a
heavy
participation
in
CMS
Philly,
we
need
to
think
about
that.
They
were
a
little
bit
short
of
sessions
and
they
were
hoping
that
if
we
could
one
they
were
excited
sure
they
would
add.
They
could
add
backdrop
a
little
more
prominently
on
their
site.
It
was
also
unclear
like
how
specific
they
wanted
sessions
to
be
like.
Could
they
be?
B
Their
suggestions
were
all
real
high
level
like
the
session
suggestions,
were
all
generic
not
specific
to
CMS's,
and
they
have
clarified
that
they
are
happy
to
have
what
backdrop
or
Drupal
specific
sessions.
They
were
just
trying
to
encourage
people
to
not
to
think
outside
of
that
they
seemed
very
eager
to
work
with
us.
Maybe
do
some
kind
of
panel
discussion
where
we
compared
the
various
CMS's,
so
I
think
there's
a
it's
a
great
opportunity
for
us
to
collaborate
with
them.
They'd
like
I,
think
they
are
committed.
B
Now
they
said
they've
got
enough
sessions,
we
have
I,
know
Gregory
and
Jeff
have
both
submitted
sessions
already.
Jeff's
is
not
backdrop
specific
at
all,
but
Gregory's
is.
It
would
be
great
if
we
could
get
a
couple
more
in
and
I
just
like
to
collab.
You
know,
I,
don't
want
three
of
us
awesome
in
the
same
session,
so
we
if
we
could
chat.
You
know
I'd
like
to
chat
with
you
Jenni.
We
could
do
an
hour
or
after
the
comm
or
tomorrow,
if
you're
too
busy
I
think.
A
B
If
anybody
else
is
watching
this
CMS
Phillie
bad
org
I
think
it
is
yeah,
you
can
go
there
and
there
submit
taking
sessions
through
Sunday
and
they're
very
interested
in
backdrop,
sessions
and
I,
don't
know
if
there
would
be
like
a
backdrop
track
or
how
that
would
be
organized,
but
we
could
potentially
have
a
good
showing
for
backdrop.
At
this
event,.