►
From YouTube: Backdrop Weekly Aug 3rd
Description
Today’s development agenda: http://bit.ly/2w4CGpj
A
A
Ok,
community
wise,
we
have
a
new
member
in
backdrop
kinship
this
week,
who's
offered
to
help
with
documentation
to
start
with
and
then
wants
to
get
into
code
later.
So
that's
great!
Thank
you.
Steve
for
offering
your
services
we'll
try
and
figure
out
how
to
get
you
on
board,
with
whatever
you
need
in
the
world
of
can
trim.
A
There
are
a
ton
of
new
projects
that
have
come
out
this
month
already
and
particularly
I
want
to
highlight
co2
review
encoder
upgrade,
so
anyone
who
is
working
on
upgrading
from
triple
7
might
benefit
from
having
those
those
are
based
on
the
Drupal
coder
modules
that
everybody
knew
and
loved.
So
Dhokla
is
working
on
those
thank
you.
God
for
making
everybody
else's
lives
easier
again
as
usual,
and
we
also
have
a
new
project,
SEO
meta
or
maybe
a
new
release
for
the
project.
Seo
meta.
A
A
So
now
we
have
a
really
easy
way
to
create
lists
of
commits
that
of
having
a
gerbil
that
we
need
to
track
and
compare
for
backdrop,
and
so
now
there
are
a
ton
of
new
issues
typed
with
the
172
milestone,
it'll,
just
kind
of
help
keep
us
up
to
date
with
what's
been
going
on
with
Drupal.
Lately,
we've
missed
the
last
few
triple
releases,
and
so
we've
got
a
couple
of
meta
issues.
We
need
to
sort
through
there's
a
lot
of
pull
requests
out
there.
We
need
a
lot
more
pull
requests.
A
Those
are
generally
pretty
easy
to
apply
to
backdrop.
So
if
anyone
wants
some
nice
kind
of
low-hanging
for
issues
that
might
be
a
good
place
to
start
so
check
the
1.7
milestone
to
find
knows
that
they
are
issues
number
twenty,
thirteen,
twenty
seven,
seventy
four
twenty
seven,
seventy
five
and
twenty
seven
seventy
six,
and
that
should
get
us
up
to
date
with
everything
that
your
goal.
That's
now
I
started.
B
A
We
should
probably
create
a
list
somewhere
somewhere
public,
like
maybe
on,
like
backdrops.
You
must
at
work
or
something
that
just
contains
like
these
are
all
the
modules
that
have
been
put
in
backdrop
core.
That's
something
that
people
have
asked
me
for
several
times
and
I'm
surprised
we
don't
have
document
and
somewhere.
That
would
be
good
to
have
and
then
also
every
time,
there's
a
new
release
of
those
projects
we
should
be
creating
metas.
Just
like
we
have
four
core
that
contain
updates
to
those
projects.
A
I
don't
have
a
good
process
for
how
we
should
handle
that
I.
Think
having
the
list
of
those
projects
would
be
a
good
first
step
and
then
seeing
it
because
a
lot
of
those
projects
when
they
get
moved
into
core,
they
get
significantly
changed
like
they
usually
don't
remain
separate
modules.
They
actually
become
part
of
corn,
salt,
bunch
of
names,
change
and
so
patches
from
the
contributions
won't
cleanly
apply
to
core
not
as
well
anyway,
is
Drupal,
7
and
patches
apply
to
core,
but
I
think
it'll
be
good
to
keep
our
eye
on.
A
What's
going
on
in
those
issue
cues
as
well,
just
to
make
sure
that
if
there
are
any
bugs
that
are
getting
fixed
and
we
can
benefit
from
those
bug
fixes,
we
should
do
that,
but
I
don't
know
that
we
necessarily
need
like
a
meta
issue
with
each
commit.
So
much
as
we
need
somebody
who
can
review
everything,
that's
happened
and
see
if
those
changes
are
relevant.
Jeff
just
linked.
A
Link
module
commits
from
Drupal
8,
so
these
definitely
aren't
gonna
apply
to
backdrop.
It
might
be
better
to
look
rather
than
looking
at
commits.
We
just
might
need
a
different
format
for
this
list.
That's
like
just
the
issues
in
general
where
we
can
try
and
figure
out
if
the
issues
are
relevant
and
then,
if
we
are,
we
can
look
at
the
code
and
see
how
we
might
come
up
with
a
similar
solution,
because
the
commits
aren't
going
to
be
relevant,
especially
if
they're
to
Drupal
8.
A
A
If
maybe
we
could
do
like
a
like
Evan
I,
don't
know
how
to
get
the
lists
we
need
if
what
would
be
useful
but
like
trying
to
find
all
of
the
Triple
E
issues
that
are
tagged
with
like
me,
it's
backport
might
be
one
way
to
do
it.
Take
it
pull
out
the
stuff
in
here
that
we
want
for
7
or
4
backdrop
that
could
be
tricky.
A
A
A
Other
things
we're
working
on
or
backed
up
one-point-eight,
but
I
should
mention
that
code
freeze
for
backup
1.8
is
September
1st,
which
is
now
less
than
a
month
away.
So
usually,
what
that
means
is
that,
right
now
we
have
kind
of
a
pickup
in
the
amount
of
work.
That's
happening
on
backup
core
and
we'll
have
a
whole
bunch
of
people
will
work
like
crazy
for
like
a
month
and
then
we'll
see
what
gets
into
the
end
of
the
month.
So
I'm
looking
forward
to
that.
A
I
know
I
started
working
on
a
couple
of
issues
related
to
media
lately
that
I'm
hoping
to
see
get
in,
and
hopefully
I
meant
to
put
up
one
last
leak,
I'll
try
and
do
it
today
on
how
to
upload
a
file
separate
from
the
file
filled
interface,
and
it
also
includes
a
edit
for
editing
existing
files.
Hopefully
I'll
get
that
posted
today
and
then
that'll
be
ready
for
review
and
we'll
try
and
kind
of
inch
closer
towards
a
full,
comprehensive
media
solution,
which
I
think
is
going
to
be
killer
for
backdrop.
A
So
media
stuff.
There
is
also
issue
number
26
32,
which
is
how
to
create
feel
the
bowl
file
NTP
bundles.
So
this
would,
for
example,
allow
you
to
include
a
caption
or
a
photo
credit
along
with
an
image
you
upload
or
a
publication
date
along
with
PDF.
So
if
you
wanted
to
add
fields
to
files
as
uploaded,
just
pretty
common
use
case,
that
is
coming
soon,
number
26,
32
I
think
needs
some
more
feedback,
as
well
as
some
more
review.
A
A
Other
than
media
library
stuff
we're
also
working
on
expanding
the
abilities
of
the
layout
system
in
core
layout
relationships,
number
2130
for
something
that
dr.
moment
started
working
on
I
think
two
releases
ago,
and
it
was
originally
just
kind
of
wrapped
up
to
see
how
it
would
work.
He
looked
at
the
poll,
requests
and
loved
it
and
wanted
to
put
it
in
the
last
release,
in
fact
below
it's
like
no,
that's
not
ready
yet
so
I
think
what
we
just
need
on
that
as
more
testers
to
figure
out.
A
If
it
is
indeed
not
ready,
can
we
catch
any
problems
with
ahead
of
time,
so
we
don't
put
it
in
and
then
discover
after
the
fact
that
it
is
not
ready.
So
if
somebody
wants
to
review
that,
we
can
figure
out
where
the
hiccups
might
be
in,
we
can
probably
get
that
in
41.8
was
almost
ready
for
long
fight
time.
We
just
need
more
confidence
in
the
code.
That's
there
sorry.
A
A
There's
a
there's
already
a
relationship
in
the
underlying
structure
of
the
classes,
there's
just
nothing
on
the
user
interface
to
be
able
to
hook
them
up
and
so
building
the
user
interface
and
hooking
them
up
then
might
reveal
problems
with
the
underlying
relationships.
So
we
should
want
to
make
sure
that
we
test
that
pretty
well,
but
it
should.
It
should
enable
a
lot
of
really
cool
things
in
the
front-end.
So.
A
So
right
now
there's
this
context.
So
if
you're
on,
like
a
node
page,
there's
a
context
of
node
or
a
context
of
the
user,
this
basically
allows
you
to
add
a
second
context
through
a
relationship
so
user
off
a
relationship
or
node
reference
relationship
and
it's
it's
the
same
context
that
was
available
in
panel.
So
you
could
have
multiple
contexts
and
you
better
sign
them,
but
we
didn't
have
a
user
interface
for
that
in
backdrop,
yeah,
and
so
this
should
add
that
this.
C
C
It
kind
of
seems
like
it
the
reason,
the
bar
and
what
the
reference
module
needs
to
do
to,
because
now
it's
like
you
know,
people
expecting
like
to
be
able
to
like
oh
I,
want
to
add
the
context
of
this.
You
know
user.
Are
this?
Like
you
know,
one
knows
that
the
other
note
is
referencing
or
something
like
that
or
the
file
I.
A
C
A
Pingree
agenda.
Sorry:
everyone,
okay,
so
we
out
relationships,
issue,
number
2130
for
a
lot
of
more
people.
Look
at
it
I
think
the
initial
implementation
is
fairly
straightforward
and
fairly
simple,
but
it
would
be
a
indicator
of
what's
to
come
and
then
the
other
issue,
that's
currently
targeted
for
1.8
is
configuration
translation
issue.
Number
704
Nate
has
a
pretty
solid
idea
of
how
he
wants
to
handle
that
he
is
looking
for
feedback,
especially
from
people
who
might
have
multilingual
sites
about
how
they
want
to
see
that
happen.
A
A
That's
all
that's
currently
scheduled
for
1.8
I
mean
there's
a
whole
bunch
of
other
issues
in
the
1.8
milestone.
If
you're
looking
for
things
to
work
on
that
aren't
necessarily
quite
as
heavy
as
those
3,
but
any
of
those
that
don't
get
done
will
get
bumped
to
1.9
or
possibly
2.0.
Although
I
would
guess
that
if
we
don't
have
a
plan
for
2.0,
when
1.8
comes
out,
we
will
have
a
1.9.
A
Don't
think
we
have
enough
time
to
figure
out
2.0
on
one
release,
let's
see
if
anyone
is
curious
that
our
2.0
plans
we've
got
I
thought
we
created
a
new
issue
last
before
our
found
one,
but
I
didn't
link
it
in
the
agenda.
So
sorry
about
that,
we
have
a
couple
of
things
on
the
roadmap
that
we
might
like
to
see
in
2.0
things
like
automatic
updates
things
like
importing
from
WordPress
or
things
like
supporting
boat
with
wanna
X
into
X
kindred
projects.
At
the
same
time,
all
of
those
are
theoretical
at
the
moment.
A
If
you
want
to
try
importing
nodes,
though
there
is
a
module
called
BN
or
bi
in
module,
that
will
let
you
import
existing
content
in
contribu
want
to
give
that
a
shot.
That
could
give
you
a
idea
of
what
the
future
might
be
like.
There's.
Also
a
project
called
a
curator,
which
is
what
we're
probably
gonna,
be
using
for
automatic
updates.
A
So
if
you
want
to
give
that
a
look,
it's
currently
a
platform
agnostic
and
what
should,
in
theory,
work
on
Drupal
as
well
as
backup
and
maybe
any
other
open
source
Eve
PHP
project
as
well.
Sorry,
this
meeting
has
been
a
little
disjointed
guys.
Is
there
anything
else
you
want
to
talk
about
today
that
wasn't
on
the
agenda
that
you
thought
of.
While
we
were
going
through
the
agenda.
A
Okay,
well,
it's
not
I,
have
a
lot
of
fun
stuff
to
do
today
in
media
land
and
I'm,
happy
to
jump
off
and
do
that.
If
anyone
thinks
of
anything
that
we
should
talk
about,
you
can
feel
free
to
jump
in
our
Gator
channel.
Just
to
reiterate,
there's
really
only
one
Gator
channel
where
backdrop
people
are
talking
right
now
and
it
is
backdrop
/
issues,
it's
linked
from
our
resources
page
on
my
drive,
CMS
org,
if
you
need
help
finding
it,
and
you
can
also
ask
how
thanks
Jeff
for
updating
the
agenda.