►
From YouTube: Backdrop Weekly 5/18
Description
Today’s development agenda: http://bit.ly/2q70nxr
A
A
That's
a
much
better
whoo,
okay,
so
in
today's
agenda
we
have
no
updates
from
the
PMC
I
have
followed
up
with
our
lawyer
on
getting
the
fiscal
spawn
to
film
Lidl
legal
sponsorship
from
the
software
freedom
Conservancy,
but
I
haven't
heard
back
from
him
yet
so,
hopefully
we'll
see
where
we
are
next
steps.
With
that
getting
our
contract
signed
this
week,
we
had
a
new
applicant
to
the
backdrop,
contribute
Robert.
A
Garrigus
has
offered
to
port
the
user
tabs
module,
so
I
wanted
to
call
out
a
specific
thank
you
to
getting
some
activity.
There,
that's
fantastic,
and
we
have
two
new
context.
This
week,
both
the
draggable
views,
module,
which
have
been
kind
of
enough.
It
started
a
while
ago,
got
wrapped
up
today,
which
is
good
not
today
yesterday,
maybe
which
is
great
and
block
refresh,
which
is
a
module.
I
ported
that
I
could
use
some
testing
on
if
anybody
wants
their
blocks
or
a
brush.
That
also
has
a
release.
B
You
already
got
a
celebrate,
but
yeah
since
last
was
at
that
meeting
at
we
released
1.70,
which
is
totally
amazing,
a
we
have
release,
notes
up
and
blog
post
if
you
want
to
get
more
information,
but
we
knocked
out
towards
the
end
there
we
had
probably
had,
like
five
features,
that
we
were
trying
to
knock
out
prior
to
release.
We
got
four
of
those
completed,
so
that's
pretty
exciting
that
we
as
we
narrow
down
the
list
we
at
least
accomplished
almost
everything
that
we
wanted
to
do
there
at
the
end
of
April
so
yeah.
B
B
B
So
in
1.7
l
real
quickly,
we
have
layout
and
views
improvements
and
better
integration
between
the
two.
Several
ckeditor
updates,
including
a
new
theme
for
CK
editor
clipboard
support
to
make
it
so
you
can
paste
images,
upload
them
directly
into
c
canada,
and
you
can
add,
links
to
images
now.
So
some
nice
improvements
there,
we
updated
styling
of
the
seven
theme
in
three
different
areas:
two
views
status
report
and
update
a
project
list,
and
we
had
over
a
dozen
well,
not
over
a
dozen
UX
improvements,
the
same
time
so
nice
a
good
release
and
exciting.
B
B
We're
not
aware
of
problems
that
need
to
be
fixed
1.71,
so
we
don't
have
any
real
high
priorities
there,
however,
we
started
and
that
did
not
get
fully
completed
a
bunch
more
cross
ports
from
Drupal.
Many
of
those
are
just
like
documentation,
updates
and
small
fixes
in,
like
miniscule
little
edge
cases,
but
we
have
a
long-standing
issue
at
twenty
thirteen.
That
is
a
series
of
cross
ports
from
about
six
versions
of
Drupal.
That
we'd
like
to
get
all
of
those
fixes
ported
over
from
Drupal,
so
that
we
don't
have
the
same
problems.
B
Several
more
issued
or
more
versions
of
Drupal
X
have
come
out
sorry
751
through
754,
and
we
haven't
even
created
an
issue
to
tackle
across
ports
on
those.
Yet
so
as
far
as
bug-fix
releases
go,
you
know
we
have
a
lot
of
issues
already
that
are
slated
for
1.71,
but
the
cross
ports
from
Drupal,
7
I
think
would
be
a
good
thing
for
us
to
just
get
caught
up
on
and
make
sure
that
we're
not
falling
behind
Drupal
7
fixes.
B
1.8
1.8
will
be
the
next
minor
version
and
it
will
come
out.
September,
15,
2017
and
September.
1St
will
be
our
feature.
Freeze
two
weeks
prior
to
the
release
date
and
the
agenda
for
1.8
is
is
kind
of
a
blank
slate.
At
this
point
we
have
some
things
that
didn't
make
it
a
1.7,
such
as
layout
relationships.
That
was
the
one
item
that
slipped
out
that's
issue:
21,
34
and
layout
relationships
would
make
it
so
you
could
do
really
cool
things
make
it.
B
So
you
could
do
things
like
reference,
the
user
entity
from
a
node
entity
and
then
place
blocks
related
to
that
user.
Braun
note
page,
for
example,
there's
PR
that
establishes
the
basic
functionality
and
layouts
has
already
been
written
in
a
way
that
it's
it's
stubbed
out
waiting
for
relationships,
support
and
so
that
issue
probably
almost
almost
definitely
needs
additional
work,
but
we
could
review
the
current
approach
in
that
issue.
So
Toronto
34
is
place
to
go
media
support,
better
media
support.
B
It's
non
project
number
six,
that
is
a
bucket
of
media
related
tasks
and
to
that
into
actually
achieving
that
dagger
heart
has
put
together
four
requests
that
kind
of
implements
a
whole
bunch
of
the
suggestions,
but
perhaps
not
in
a
very
incremental
way
kind
of
my
steps,
several
steps
ahead,
but
it's
still
pretty
exciting
to
see
all
of
that
work
coming
together
and
Jen
I
think
you've
had
some
discussions
in
this
issue.
26:33.
A
A
1448
is
probably
the
best
place
to
start
that's
sort
of
the
file
management,
meta
issue
that
includes
all
the
things
that
we
eventually
want
to
do
to
files
like
field
of
all
files,
different
file
types
and
a
user
interface
for
adding
file.
It's
not
part
of
either
image,
upload
dialog
or
a
seek
editor
image
plug-in.
A
A
It
was
creating
a
new
node
type
called
media,
but
there
were
a
lot
of
really
great
ideas
in
there
about,
like
the
other
thing,
so
we'd
already
talked
about
in
this
meta
issue
that
I
don't
think
Jonathan
had
seen
like
a
separate
interface
for
adding
files.
He'd
included
that
in
there
he'd
added
he'd
already
started
like
setting
up
the
view
that
we
want
to
use
for
the
actual
browsing
to
find
the
files
in
the
file
browser.
A
So
I
think
it
was
great
that
he
did
like
a
quick
proof
of
concept,
but
it's
going
to
need
to
sort
of
be
refactored
to
fit
in
with
all
the
stuff
that
we
already
have
in
core
like
our
existing
file
entity
and
our
existing
files
listing
page
but
I,
think
it's
a
great
start.
I'm
excited.
We've
got
a
bunch
of
people
who
are
really
into
working
on
this
right
now
on
both
out
and
Jonathan
are
committed
to
making
some
progress
on
it.
A
We've
got
a
lot
of
different
things
that
I
think
that
we
want
to
include
for
file
management
and
trying
to
get
a
handle
on
the
scope
of
what
we
want
in
one
8
is
going
to
be
important,
but
I'm
super
excited
that
we've
got
a
bunch
of
different
people
who
are
excited
about
it
and
working
on
it.
Right
now,.
B
B
So
those
two
items
are
great
items
for
41.8.
What
else
question
mark?
We
could
do
lots
of
various
things,
but
we're
not
calling
them
out
yet
as
being
like
you
know,
these
are
areas
of
focus
or
things
that
were
really
beelining
for
in
1.8
there's,
as
always
like
minor
things
that
we
would
like
to
slate
for
the
next
release
and
there's
already
about
a
dozen
of
these
in
the
1.8
milestone.
A
A
I
heard
it
was
really
exciting
for
those
who
were
there
a
lot
of
great
conversations,
I
know
afterwards,
so
a
bunch
of
new
people
trying
to
be
serum
and
backdrop
together,
I
kind
of
like
to
hear
how
that's
been
going
to,
but
I,
don't
know
any
more
than
that
so
general
discussion.
Anyone
here
have
anything
in
particular.
They
want
to
add
for
today's
meeting
and.
A
B
A
A
We
started
on
that
yeah,
yes,
okay,
well,
I,
don't
have
any
new
feedback
since
last
week,
so
I
don't
know,
hopefully
should
you've
to
argue
at
it.
I'm
excited
about
it,
though,
and
I
think
that
if
we
are
gonna
do
it
in
January,
we
need
to
start
making
a
plan.
So
I
don't
want
the
decision
to
get
pushed
to
a
point
where
we
have
to
make
a
decision
because
we
didn't
make.
We
didn't
do
it
early
enough.
B
All
right,
yeah,
there's
even
just
thinking
about
that
infrastructure
implications
of
this
would
be
there's
a
lot
of
work
to
be
done,
because
we
don't
have
a
really
broad
support
for
branching
yeah
and
for
downloads
and
for
dependencies
and
project
browser
and
all
in
theory,
all
those
things
are
already
functioning
for
an
API
break
version.
But
if
we
pursue
a
route
where
there's
not
an
API
break,
you
know
that
backdrop
to
can
run
back
up
one
modules.
Then
we
have
a
much
bigger
infrastructure
problem
because.
A
A
A
How
do
we
want
to
have
that?
Okay,
so
I
think
I
asked
this
last
week
to
like
if
we
wanted
to
open
an
issue
for
PMC
or
if
we
wanted
to
have
like
a
like
a
video
meeting
specifically
for
anyone
interested
talking
about
it
or
how
like,
where?
What
is
their
process
for
making
this
kind
of
decision
I,
don't
think
we
know
that
yet.
Oh.