►
From YouTube: Backdrop Weekly - March 19, 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).
B
Okay,
this
is
the
weekly
meeting
on
march
19th,
2020
and
starting
with
introductions.
I
think
everybody
this
year.
This
meeting
was
also
here
last
meeting,
but
it
would
be
good
to
go
through
and
get
injection
from
Nate
because
you
weren't
here
last
time
what
we
did
at
the
last
meeting
was:
what's
your
name.
Where
are
you
from
and
if
you
have
something
interesting
to
share
this
30
seconds
or
less
go
ahead.
A
B
Right
Greg
do
Nayak's
yeah.
C
D
E
Oh
Jimmy
I'm
Tim
and
I
Tim
Erickson
symposium
on
the
Internet
I
am
temporarily
in
Deerwood,
Minnesota
I,
think
I
said
Brainerd
earlier,
but
if
I
get
more
specific
deer
would
be
would
be
the
local
vicinity
and
I'm
hanging
out
with
my
parents
here
for
the
next
few
weeks
it
looks
like
so
and
working
working
remotely
as
I
do
anyway.
It's
just
not
from
a
coffee
shop.
B
B
B
Theme
yeah
that
lets
you
select
from
various
color
schemes,
fantastic
color
support
in
there
too,
and
then
there
are
two
modules:
site,
verification
and
file
entity,
embed
filter.
So
thanks
to
all
the
people
are
continuing
to
create
and
release
new
modules.
For
backdrop,
there's
also
been
a
bunch
of
activity.
An
existing
core
system
contributed
modules
as
well,
but
I
didn't
take
time
to
list
all
of
the
releases
for
those
also,
and
so
let's
turn
it
over
to
neat
to
talk
about
release
updates.
G
A
Their
current
minor
version
of
backdrop
with
the
next
bug
fix
release
being
1:15
one.
As
of
yesterday.
We
have
an
impetus
to
make
a
release
for
1:15,
one,
which
is
yesterday
Drupal,
released
an
update
of
security
release,
Bridger
Bowl
and
notice
for
the
ckeditor
module
for
Drupal
7.
So
the
issue
is
related
to
CK
editor
created
a
new
version
of
their
editor.
114
and
114
includes
some
security
enhancements.
A
Unfortunately,
as
noted
in
the
name,
114
is
not
a
bug
fix
release.
It's
a
new
minor
version
for
seek
editor,
so
it
could
include
some
breaking
changes.
Back
drop
is
currently
running.
Ck
editor
112
1,
so
it's
actually
jump
of
2
minor
versions
for
us,
and
so
we
were
a
little
slow
on
the
uptake
yesterday,
getting
a
corresponding
release
out
for
back
drop.
A
But
although
we
have
the
opportunity
to
have
a
release
yesterday,
that
was
you
know
coordinated
with
Drupal
that
big
of
a
jump
in
seek
editor
version
seemed
likely
to
cause
breakage
and
it's
not
really
a
security
release.
That's
in
the
normal
sense
that
we're
fixing
a
vulnerability
in
backdrop.
It's
just
that
we're
updating
a
third-party
library,
CK
editor
with
the
security
enhancement
in
it
and
so
kind
of
what
we've
been
kicking
around
as
an
idea
is
that
we'd
like
to.
A
Instead
of
rushing
out
that
release,
we
did
make
a
pull
request
in
the
security
queue,
but
considering
both
Drupal
have
made
a
release
and
that
this
version
of
seek
editor
is
been
out
since
March
4th,
there's
not
really
any
secret
here
so
we'd
like
to
move
it
to
the
public
queue
to
get
wider
testing
on
that,
and
also
the
security
team
doesn't
have
live
sandboxes
and
that
makes
testing
more
tedious
for
the
security
team.
So
move
that
into
a
public
issue.
A
I
think
we
actually
have
an
ongoing
issue
all
the
time
for
like
keep,
seek
avid
or
up
to
date,
I'm,
not
I'm,
honestly,
not
really
much
of
a
fan
of
updating
seek
editor
to
a
new
minor
version
inside
of
a
bug-fix
release,
but
I
guess
the
you
know.
This
is
a
presence
in
a
weird
place
that
they
only
included
the
security
enhancement
in
the
newest
minor
version.
A
B
A
E
C
A
G
A
We
don't
have
an
issue
for
this
particular
thing.
Yeah
I
think
we
have
the
big
metaphor:
seek
editor,
keep
it
up
to
date.
It
might
be
good
to
make
a
specific
one
for
this
particular
issue
and
describe
the
overall
situation
about
how
we
probably
need
to
be
at
least
seen
as
being
responsible
and
updating
at
the
same
pace
as
Drupal
8,
which
faces
the
same
problem
and
then
and
then
move
the
pole
request.
That
is,
in
the
security
queue,
which
is
just
a
typical.
A
That's
that's
I,
don't
have
any
real
firm
suggestions
other
than
try
to
use
all
of
the
features
you
know
that
are
in
veteran
Sikandar.
The
integrations
are
a
common
thing
that
would
be
likely
to
break
things
like
seeing
if
you
can
copy
and
paste
an
image
making
sure
all
the
dialogues
work.
The
links,
work,
link,
dialogue,
the
image
dialogue
and
things
like
that.
Okay,.
E
A
A
Okay,
so
so
that's
going
to
be
115,
one
which
is
probably
going
to
come
up
next
Wednesday,
like
that's
generally,
what's
probably
going
to
be
happening
in
the
near
future
115.
It
looks
like
we've
created
this
milestone
to
kick
things
into
that
are
just
general
bug,
fixes
that
aren't
related
to
the
security
update.
However,
I,
don't
think
that
these
changes
necessarily
need
to
be
held
out.
A
H
A
I
see
it
looks
like
this
was
regression
from
the
switch
from
language
to
length
that
it
just
changes
that
to
match
it.
Just
is
matching
up
the
keys
and
that
fixes
that,
let's
see
next
one
is
parameter
three
to
views.
You
I
build
form
state
expected
to
be
a
reference
value
given
and
views.
Ui
Ajax
form
it's
a
mouthful,
but
the
issue
is
4323.
It's
cross
port
from
Drupal,
seven
views
so
again,
a
low,
a
low.
A
Because
it's
already
in
the
Drupal
seven
version
of
views
and
then
lastly,
an
issue
that
we've
been
talking
about
for
a
couple
of
weeks
4306
this
issue
that
makes
tests
run
faster
and
includes
time
indicators
on
each
test
to
saying
how
long
it
takes
to
execute,
which
should
allow
us
to
optimize
tests
as
we
build
them
out
in
the
future
currant
sauce
on
that
one,
it
might
need
work,
there's
some
intermittent
failures
or
a
and
intermittent
failure
that
seems
to
be
caused
by
one
of
the
changes
so
yeah.
We
want
to
avoid
that
was
magic.
A
A
Next
up
is
the
minor
version.
Next
minor
version
is
116,
116
will
be
coming
out.
May
15th
with
feature
freeze
on
May
1st
there's
some
features
already
implemented
into
116
and
we'll
go
over
the
ones
that
are
currently
in
progress.
First,
up
is
color
modules.
Support
is
not
inherited
by
child
themes.
This
issue,
33:48,
is
currently
marked
RIT,
BC
I.
Think
that
one
speaker
still
here,
no
oh
yeah
I-
think
that's
oh
I
thought
Peter
was
the
forward
quest
creator,
but
Joseph
is
great
so
that
one's
Mike,
Dirnt
TBC
fantastic.
I
A
F
F
They
doc
will
monters,
contacted
me
and
offered
to
do
that.
The
screen
share
session
and
sort
of
walking
through
how
to
do
that.
So
we
do
that
soon
and
I'm
not
be
able
to
get
around
to
doing
that,
but
otherwise,
if
someone
else
was
jumping,
then
just
just
to
move
it.
Otherwise
it's
ready
to
go.
I
think,
yeah.
I
was
about
to
say
that
if.
G
G
E
I'm
at
topic
a
while
back
people
were
asking
that
we
do
a
view
of
a
virtual
user
group
on
writing
tests
and
the
problem
was
always
getting
someone
to
believe
it
and
I
you
know
so.
I
would
just
recommend
it
would
be
great
if
we,
if
we
did
something
like
that
to
just
publicize,
doesn't
have
to
be
at
a
certain
time,
but
whenever
you
do
it,
if
you
could
share
that
I
think
there's
a
broader
interest
in
in
writing
tests
and
it
does
seem
to
be
a
big
roadblock
on
a
number
of
issues.
F
A
F
Yeah,
so
he
contacted
me
when
he
saw
my
face
develop
that
I
can't
write
just
currently
to
put
on
I
can't
get
my
head
around
simple
test
or
know
where
to
start
feel
for
distance
in
a
screen
share
with
me
person
and
just
sort
of
walking
through
he
reckons
I
can
pick
it
up
in
five
minutes.
Once
it
sort
of
shows
me,
the
basics
got.
E
E
That
is
a
community.
We
really
need
something
more
public
about
tests
as
well.
You
know
if
that
takes
longer
to
pull
together,
that's
okay,
but
let's
get
that.
Let's
also
make
that
happen
and
I
don't
know
native.
If
you
are
somebody
that
needs
to
be
involved
in
that
bigger
thing
or
who
else?
Who
are
our
test?
Experts
right
now,
you
and
Jeff,
and
and
dot
Wilma.
E
C
A
C
Yes,
so
that
don't
wilmut
has
provided
a
new
pool
requested
and
just
need
to
test
I
haven't
tested
it.
So
the
objection
there
was.
We
mentioned
this
during
the
release
that
meeting
that
we
were
loading,
the
separate
form
bits
in
dialogues,
and
then
we
were
once
the
dialogue
was
sent.
We
were
passing
those
values
back
to
the
main
form
where
the
the
the
fields
were
hidden
via
JavaScript,
and
we
agreed
that
that's
not
the
best
way
to
do
it.
A
Pulling
this
up,
cuz
I'm
I
want
to
see
it.
Oh
okay,
that's
very
exciting,
so
yeah
a
whole
lot
of
new
things
happening.
There
currently
needs
code,
review
and
testing
cool
thanks
doc
moment
again.
If
you
watch
this
for
all
of
your
hard
work
on
this
and
other
issues
Gregory,
do
you
want
to
give
us
an
update
on
the
next
issue
which
is
permanently.
E
B
I,
don't
think,
there's
any
update
on
the
issue
itself.
It
hasn't
progressed
for
a
while
I
think.
It's
currently
labeled
needs
more
feedback,
I'm,
not
sure
it
needs
more
feedback.
I
think
it
just
needs.
An
issue
summary
update,
so
I
think
the
plan
was
to
try
and
refocus
this
issue
on
to
only
the
features
were
sure
were
and
concluding
in
court
right
now
and
then
create
another
issue.
That
was
the
addition
of
the
kinship
features
and
then
reevaluate
that
later
for
a
core
involvement.
If
we
want
it,
I.
E
C
Right
in
the
few
details
that
we
didn't
have
a
solid,
not
agreement,
we
have
an
agreement,
but
it's
like
terminology
and
things
there's
one
sub
issue
that
was
created
to
consider
renaming
revisions
to
versions
and
then
I
started.
It's
one
in
one
of
my
oftentimes
I,
a
big
issue
about
what
we
call
the
current
or
doable
or
active.
Whatever
version
and
I
started,
making
a
list
of
possible
things
and
pros
and
cons
why
some
of
them
are
can
be.
This
can
be
use
and
I'm
gonna
open
that
for
discussion.
But
these
are
details.
C
E
B
B
B
B
C
A
A
E
I
think
the
big
update
is
last
week.
It
just
needed
more
eyes.
We
wanted
to
get
some
more
input
Jen
jumped
in,
and
she
raised
the
issue
of
backward
compatibility,
which
I
don't
know
if
it
that's
been
tested
very
well.
So
I
think
that
is
our
next
step
in
this
is
testing
it
on
some
websites
to
make
sure
that
it
doesn't
break
anything
I'm,
not
I,
haven't
thought
about
it
enough
to
know
how
likely
it
is,
but
Jen
seem
to
suggest
that
there's
at
least
some
concern
of
that
right.
John.
Do
you
yeah.
B
So
I
I
just
looked
at
the
previous
code
and
the
current
code,
and
because
the
previous
code
just
used
a
T
variable
and
now
we've
just
swapped
out
with
something
else.
The
only
way
you
could
have
changed,
that
is
by
pre-processing
that
value
and
if
you've,
pre-press
this
that
value
and
a
theme
is
gonna
override
the
new
thing
in
the
same
way,
too
bright
we're
building.
B
No
issue
here
with
Cody
and
I:
don't
know
if
that's
something
that
we'd
fixed
in
backdrop
or
because
I
think
when
I
was
working
on
this
when
we
were
doing
Drupal
7
to
Drupal
8
and
there
was
a
function
that
was
like
theme
submitted
by
that
was
part
of
the
problem,
and
we
don't
have
that
in
backtrack.
So
I
think
we
might
have
done
a
little
cleanup
initially
that
may
be
possible.
So
that's
good.
Ok,.
B
I
think
we
just
need
to
address
some
of
the
other
issues
in
there
like
there
was
a
recommendation
that
this
should
probably
be
done
with
filled
with
forum
settings
on
pseudo
fields.
Instead
of
the
way
it's
done
and
I
wondered
how
big
a
difference
that
would
be
if
we're
gonna
be
doing
that
pseudo
field
change
anyway,
and
then
there
was
another
issue
about
not
so,
if
we
put
in
this
feature-
and
you
can
only
customize
it
per
content
type-
and
that
means.
B
B
This
is
because
you
have
a
like
developer
level
tool
that
would
allow
you
to
do
it
for
every
content
type
just
with
a
node
pre-process
node
function,
but
I
just
wanted
to
throw
that
out
there
that
we
are
taking
something
that
can
be
changed
in
one
place
for
everything
and
now
replacing
with
something
that
has
to
be
customized
for
every
content
type
which
I
probably
is.
Okay.
I
just
wanted
to
make
sure
that
everybody
was
aware.
That's
what
we're
doing
and
then
I
add.
B
Another
comment
here,
I
think
like
five
minutes
ago,
which
is
that
when
we
introduced
the
default
page
title
menu,
settings
I
erased
the
same
thing.
Is
that
a
token
we're
putting
a
token
on
a
user
out
of
form
and
most
people
who
use
use
other
forms,
probably
won't
use
tokens
anywhere
else
and
so
I
had
rejected
the
idea
of
using
tokens
on
the
like
menu
link
creation
form,
because
that
would
be
something
before
into
these
people.
We're
gonna
run
into
the
same
problem
here,
probably
never
seen
a
note.
B
:
submitted
:
date
bracket
thing,
but
I
notice
that
on
the
date
formats
page,
we
have
some
JavaScript
that'll
like
automatically
calculate
your
PHP
date
format
as
you're
typing
in
those
weird
letters.
So
we
already
have
sort
of
a
mechanism
for
working
with
something
that
you'd
be
sort
of
blind
use.
It
like
you,
don't
know
what
the
output
of
that's
going
to
be
and
if
there's
a
way
I
don't
know
if
we
can
do
a
token
replace
in
JavaScript
but
I.
B
Imagine
we've
probably
done
this
somewhere
in
core
before,
but
if
there's
a
way
that
we
could
show
the
actual
output
of
that,
then
I
would
feel
okay
using
tokens
because
at
least
we're
giving
people
like
you
don't
know
what
this
tool
is.
But
you
can
see
the
results
of
the
box
that
you're
putting
stuff
into
you
can
see
what
it's
like
on
the
way
out.
So
that's
something
that
we
could
if
we
can
figure
out
how
to
do
that,
then
I
think
it
reduces
the
craziness
of
what
a
token
is
problem.
B
C
A
B
So
I
was
talking
to
lorina.
She
came
to
the
drupal
san
francisco
drupal
users
group
last
thursday,
where
I
presented
on
doing
an
update
from
Drupal
the
backdrop
and
she
showed
me
this
module
in
Drupal
8
that
I
hadn't
seen
before
called
them
migrate.
Ui
I
posted
some
screenshots
of
it
in
this
issue.
I
created
four
backdrop:
it
is
issue
number
43,
45
and
I'll
post
a
link
here
and
in
zou.
B
Which
essentially,
will
allow
people
to
install
and
brand
new
backdrops
a
drop
in
all
of
the
modules
they
had
on
their
Drupal
7
site
connect
their
backdrop
site
to
a
second
database
and
then
it'll
run
sort
of
a
report
and
be
like
this
is
the
status
of
all
the
things
that
you
have
so,
for
example,
you
have
a
node
type
in
here
that
doesn't
have
a
module
that
defined
it
or
your
module
doesn't
have
an
upgrade
path
or
I.
Don't
know
information
like
that
and
I
figured.
We
could
do
exactly
the
same
thing
in
backdrop.
B
That's
in
Drupal
8
and
it's
probably
gonna
be
more
useful
to
our
target
audience
than
the
kinds
of
people
who
are
doing
upgrades
to
Drupal
8,
because
we
have
a
lot
of
people
who
are
gonna
want
to
excuse
a
user
interface
for
this
rather
than
people
who
are
comfortable,
writing
migrated
scripts
or
doing
things
on
the
command
line,
and
because
we
already
have
a
bunch
of
tools
that
do
these
kind
of
comparisons.
For
example,
we
have
the
backdrop
module
update
status
module,
which
you
can
plug
into
a
triple7
site
and
it'll.
B
Tell
you
the
status
of
all
the
modules
you're
running
for
backdrop.
I
figured
we
could
sort
of
marry
those
two
things
together
and
say:
okay,
we
know
the
status
of
all
these
triple
seven
modules.
We
can
tell
you
if
they're
ready
or
not,
then
when
you
have
your
backdrop
site
ready,
we
can
run
the
same
report
again
and
be
like
okay.
This
is
this
is
the
status
of
all
those
modules,
but
now
this
is
how
they
would
upgrade
or
not,
and
so
it
seems
like
I
know,
we
can't
reuse
the
code
butts
in
true.
B
C
B
You'd
have
a
brand
new
backdrop
site
connected
to
an
empty
database,
just
the
way
that
you
would
normally
install
backdrop
and
then
you
plunk
plunk
in
all
the
modules
you
need
that
match
what
were
in
Drupal
7
and
then
enable
this
module,
and
then
it
would
say:
hey
these
are
the
upgrade
cats
are
supported.
This
is
the
stuff
we
have
found
in
your
drupal
seven
database
that
doesn't
have
an
upgrade
path.
B
So,
what's
in
the
modules
table,
that's
enabled
that
you
don't
currently
have
and
its
status,
so
it
would
be
sort
of
like
this
spreadsheet
that
I
make
before
I
do
an
update
where
it's
like
this
is
the
status
of
everything
I
want
to
automate
that
so
that
there's
a
way
that
we
can
get
all
of
that
data
for
people
ahead
of
time.
So
it
would
do
the
module
status.
It
would
do
your
content
type
field
to
module.
B
B
It's
a
fairly
big
project.
I
spent
some
time
yesterday,
fixing
up
the
back
drop
module,
back,
drop,
update
status,
module
I,
just
muddle
update,
module
status,
module,
and
so
that
should
have
all
of
the
74
modules
that
are
included
in
core
are
now
represented
in
that
module.
I
had
the
pork
press
for
that
yesterday
and
it
it
works.
So
that
was
step.
One
was
making
sure
that
we
had
everything
that
was
in
core
to
find
that
module
also
reaches
out
to
github
to
find
out
if
they're,
stable
release
of
the
any
other
contributor.
B
What's
missing
is
like
the
user
interface
part
and
hooking
all
the
tools
we
have
up
into
it.
So
I
want
to
copy
that
from
Tripoli.
I'm
gonna
have
a
meeting
with
a
Rina
later
today
to
go
over
this
issue,
I
created
for
a
backdrop
and
make
sure
that
we
note
anything
in
particular
that
needs
to
be
covered
like
in
backdrop,
source
and
I
would
like
it
to
have
a
upload.
Your
database
button
I'm,
not
sure
that'll
work.
B
You
know
if
you're
doing
on
an
external
web
host
or
something
with
a
file
in
it,
but
I
think
that
would
be
a
killer
feature
too
and
then
I
would
like
to
stray
and
start
building
it.
The
goal
is
to
have
something
in
a
demonstratable
state
by
a
Stanford
web
camp,
which
is
next
week.
Okay,
okay,
watch
your
how
close
that'll
get
but
I
told
her
I
would
put
some
time
into
it
and
see
if
we
can
get
there
so.
A
B
It
does
the
upgrade
and
then
it
gives
you've
gotten
to
push
it
will
actually
do
it.
For
you
and
I,
don't
know,
I
haven't
done
this
with
a
Drupal,
8,
say:
I,
don't
know
if
it
has
the
C
CK
style,
like
forward
backward
Bert
thing.
I
wasn't
planning
on
adding
anything
like
that.
It
was
more
like
here's
all
the
information
you
need
to
know
before
you
upgrade
type
tool
that
what
if
you
check,
if
all
the
boxes
are
checked,
it
then
also
gives
you
the
button
to
run
an
upgrade.
B
B
If
we
think
it's
something
that
belongs
in
core,
if
it
goes
into
core
I
would
imagine
it
would
integrate
more
Tice
tightly
with
our
current
update
dot
PHP
process,
so
I
will
probably
be
like
calling
a
bunch
of
those
functions
from
the
Kindred
module.
But
I
don't
know
if
the
end
results
is
going
to
be
like
replacement
for
that
process
or
just
an
alternate
way
to
do
it.
B
C
Now
that
we're
talking
about
migrations,
they're,
making
it
easier,
ideally
with
one
button,
the
thing
is
they're,
just
the
best
Oh
green
gold
thing,
and
what's
the
last
video
recording
of
the
virtual
user
group
and
I
noticed
that
one
of
the
major
bottlenecks
when
you
is
trying
to
figure
out
which
layouts
to
map
to
templates
or
whatever
he
had
in
d7.
This
has
been
in
my
head
for
a
while,
and
your
comment
now
has
sort
of
like
triggered
to
throw
that
idea
on
the
table.
C
We,
the
problem,
is
that
we
had
up
to
recently,
we
had
specific
layouts
in
core
and
people
had
to
write
their
own
layouts,
but
now
we
have
the
flexible
layouts,
which
can
sort
of
like
so
I
always
thought.
Can
we
possibly
scan
a
template,
see
what
it
does,
what
regions
so
like
it
creates
or
whatever
and
then
create
a
flexible
template
out
of
it.
B
I
think
this
is
something
coder
module
might
be
able
to
do
it's
a
little
tricky
because
in
Drupal
7
you
could
name
your
theme
regions,
whatever
the
heck.
You
wanted,
there's
obviously
some
standard
things
that
need
to
be
printed
out
like
messages
and
tabs
and
whatever,
and
we
can
tell
where
those
are
gonna
go,
but
we
might
end
up
creating
Regents
for
every
variable.
That's
printed
in
the
template,
even
if
it's
not
our
region,
variable
or.
C
B
C
B
B
So
I
was
also
thinking
that,
if
you
wanted
to
do
the
code
or
upgrade
path
you
could,
it
might
be
easier
to
create
a
new
template
from
the
current
template
than
to
create
a
new
configurable
layout
template
from
the
current
template.
But
that
would
be
part
of
a
theme
upgrade
so
like,
rather
than
using
coder
operate
every
time
module,
which
is
what
it
does
now.
If
you
use
coda,
upgrade
to
upgrade
a
theme,
we
could
convert
a
page
template
file
into
a
layout
template
file
pretty
easily,
but
I.
B
Don't
know
how,
like
the
fact
that
the
CSS
moves
things
around
like
you
might
have
like
a
content
first,
where
all
your
sidebars
or
like
at
the
bottom,
but
then
they
render
with.
Yes,
that
does
make
it
really
hard.
We
could
make
a
configuration
layout
that
exactly
matches
the
order
and
the
code,
but
I'm
not
sure
that
people
will
find
that
recognizable
either
once
we
get
it
into
configuration.
C
A
I'm,
not
sure
you
contemplated
doing
stuff
like
making
most
of
this,
be
like
Drupal
7
module
instead
and
then
like,
because
a
Drupal
7
site
would
be
much
more
capable
of
telling
if
it's
ready
for
backdrop
than
trying
to
import
a
database
into
a
backdrop
site
and
then
somehow
read
that
Drupal
7
database,
which
is
in
a
much.
You
know
harder
to
read
thing
because
it's
an
unobtainable
backdrop.
B
B
So
the
backdrop
upgrade
status
module
is
a
Drupal
7
module,
I'm
gonna
grow
links
that
in
here
right
and
that's
the
one
that
gets
all
the
information
on.
You
know
whether
your
Drupal
modules
are
ready
for
backdrop
or
not
and
it'll
list,
like
all
the
ones
that
are
included
in
core
now,
as
well
as
anything
that
it
prints
on
doctor
of
CMS
Network.
B
B
That's
what
I
was
working
on
yesterday
to
make
sure
that
that's
up
today
so
I
think
that's
the
first
step?
Okay,
but
once
somebody
gets
enough
green
on
their
report.
From
this
thing,
it
also
be
good
to
get
the
same
kind
of
experience
you
get
from
Drupal
8
with
you
know,
essentially
connecting
one
site
to
two
databases
and
having
it
run.
A
couple
of
raw
sequel
queries
on
the
old
database,
because
we
know
what
format
it's
gonna
be
in,
and
I'm
happy
to
spend
some
time
on
this
in
kinship.
B
A
Okay,
that's
great
first
of
all,
but
I
think
the
Drupal
7
module
for
it
should
be
would
make
things
a
lot
easier
for
checking
the
status
another
crazy.
This
might
be
crazy.
Is
that
if
you
have
a
module
on
your
Drupal
7
site
that
provides
like
this
update
status
thing
either
as
a
separate
project
or
part
of
this
one,
you
can
also
put
a
companion
module
in
there.
A
B
So
it
seems
like
also,
if
I've
already
researched,
all
this
stuff,
like
finding
a
way
to
share
that
with
everyone
else
would
be
really
good
and,
in
particular,
I
have
a
column
on
my
spreadsheet,
of,
like
work
necessary
to
get
the
module
from
Drupal
to
backdrop
and
I
would
love
to
find
a
way
to
communicate
that
to
people
where
it's
like.
Okay,
you're
coming
from
CK
editor
module
in
Drupal
7,
we
have
a
CK
editor
module
in
fact
wrap.
Your
settings
will
not
upgrade
like.
B
B
It
or
surely
their
support,
and
then
you
get
it
in
your
surprise.
Just
having
that
information
ahead
of
time
is
gonna
be
valuable
to
people
so
yeah
I'm,
trying
to
figure
out
if
there's
a
way.
I
can
add
that
to
the
current
report,
that's
like
work
required
and
upgrading
and
then
have
like
yeah
so
I
like
the
idea
of
exposing
the
data
you
need
like
here.
Your
know
types
in
here
the
modules
that
are
required
for
fields
and
whatever
that's
really
fascinating.
So
I
look
at
that
to
look.
C
C
It's
it's
a
long
time
like
we
have
a
one
and
a
half
year
until
d7
becomes
end-of-life
and
the
easier
we
make
it
for
people
to
migrate.
The
more
people
will
migrate.
So,
although
it's
these
are
crazy
ideas,
but
maybe
we
should
see
I
always
remember,
Jeff's
words
that
we
thought
the
things
were
gonna
be
like
the
automatic
updates
are.
It
was
easier
than
we
thought.
After
all,
so
I.
C
A
E
If
nobody
comes,
you
haven't
lost
anything
so
or
we
could
do
something
more
formal
if
anybody's
in
specially
I.
Think
if
you
have
a
particular
topic
or
something
you
want
to
work
on
that,
you
really
need
help
on
you
know,
and
this
is
something
I'm
always
happy
to
help
with
in
the
organizing
of
stuff.
So
somebody
like
feels
like
they'd,
really
like
to
do
a
sprint
on
a
specific
issue.
A
C
A
Things
things
there's
already
been
things
merged
into
one
15
and
everything.
That's
in
the
one
15
branch
right
now
will
go
out
the
same
time
as
the
security
release,
and
so
it
yeah
anything
up
until
Wednesday.
Basically
point
it
will
want
to
be
extra
cautious.
You
know
with
the
kinds
of
things
that
we
put
in,
because
introducing
regressions
in
security
releases
is
people's
least
favorite
thing.
So
yeah
of.