►
From YouTube: Backdrop Weekly July 20th
Description
Today’s development agenda: http://bit.ly/2ueRYub
A
All
right,
we
are
on
air,
happy
Thursday
everybody.
It
is
July
20th.
This
is
a
meaning
to
check
in
on
active
development
tasks
for
backdraft
CMS.
Before
we
start
talking
about
development,
stuff
updates
from
the
PMC.
The
period
of
time
that
we
allowed
everybody
to
comment
on
the
software
Conservancy
is
over
ended.
Last
Friday
I've
contacted
Karen
and
Tony
their
lawyer
to
figure
out
what
our
next
steps
should
be.
So,
hopefully,
we'll
have
an
update
on
that
shortly,
but
Nate
had
an
interesting
idea.
A
B
So
the
agreement
that
the
software
freedom
Conservancy
has
in
place
and
we
could
negotiate,
but
we
don't
really
want
to
because
I
think
it's
a
good
idea
anyway.
It
requires
that
there
be
no
collusion
or
conflicts
of
interest
between
like
multiple
people
on
the
on
a
projects
PMC,
so
the
project
management
committee
and
any
projects
that
are
under
the
umbrella
of
the
Conservancy
and
so
right
now
we
would
not
qualify
under
their
normal
agreement,
because
Wes,
Rove
and
I
are
both
employed
by
the
same
company
at
level,
bot
and
so
to
free
ourselves.
B
Up
of
that
particular
snag
and
to
put
to
rest
any
worries
about
like
John
and
I,
also
been
kind
of
like
a
block
votes
in
any
PMC
issues.
I'm
going
to
step
off
of
the
PMC
but
remain
a
committer
for
the
project
just
like
Jeff
is
a--,
is
a
committer,
but
we're
thinking
about
creating
some
kind
of
like
advisory
like
non-voting
role.
A
So
I
don't
know
if
anyone
here
has
any
feelings
about
that
like
if
you
think
it's
a
good
idea.
My
one
concern
one
Nate
brought
up.
This
idea
is
that
if
we
ended
up
having
something
like
core
committers
should
be
able
to
weigh
in
on
decisions
about
direction
of
the
project
so
that
they
can
talk
about
like
how
much
you
know.
Change
is
involved
and
stuff
like
that.
A
We
might
accidentally
be
creating
a
situation
where
the
voice
of
the
core
committers
becomes
more
powerful
than
the
voice
of
other
constituents
that
we
may
have
on
the
PMC,
and
so
we'd
have
to
do
this
kind
of
carefully
to
to
set
up
like
well.
Who-Who
are
the
non-voting
PMC
member
or
like
whatever
we're
gonna
call
them?
Who.
A
What
is
the
purpose
of
having
them
there
and
making
sure
that
that's
pretty
clearly
outlined?
So
it's
not
just
like
well
Nate's,
not
on
the
PMC,
but
he
is
on
the
PMC.
And
what
does
that
mean?
It's
just
trying
to
figure
out
like
where
the
value
is
in
making
sure
that
we're
really
clear
about
stating
and
what
those
rules
are
yeah.
B
A
B
A
All
right,
that's
it
for
PMC
stuff
contributed
projects.
There
are
two
projects,
older
projects
that
have
new
releases
this
week,
date
all
day
and
content
menu
working
on
backup,
seamless
to
org.
The
website.
Jeff
has
been
working
on
a
for
quest
that
gives
people
the
option
to
subscribe
to
a
security
mailing
list
so
that
every
time
we
publish
a
security
advisory,
that
advisory
was
out
via
email
to
anyone.
Who's
opted
into
that
list.
I
know
on
drupal.org,
you
get
sort
of
a
digest
of
all
of
the
day's
security
releases.
A
I,
don't
think
we
have
enough
security
releases
coming
out
for
backdrop,
that
that
makes
sense,
so
I
think
for
short
term.
This
is
a
good
solution.
It
gives
us
something
right
away.
Our
plan
is
to
push
best
to
production
later
today
and
test
it
and
then,
if
it
works,
well
kind
of
unleash
it
to
the
wild.
But
if
anyone
is
curious
about
that,
there's
a
paw
request
in
the
queue
feel
free
to
take
a
look
at
it
before
we
do
that.
B
Could
I
make
one
suggestion
there
I
mean?
Maybe
it's
already
been
that
we
have
them
mailing
want
to
sign
up
on
every
page
of
the
website
right
now
down
at
the
bottom
and
just
to
make
it
clear
that
you're
subscribing
to
the
security
mailing
list?
If
you're
on
slash
security
like
maybe
we
should
remove
the
normal
mailing
list
sign
up,
because
I
could
be
confusing
to
people.
A
A
B
Sure
spent
on
quiet
week
for
backdrop
code
changes.
A
current
version
of
backdrop
is
backed
up
1.71
and
we
don't
have
any
outstanding,
critical
items
that
would
force
us
to
make
a
1.7.2
issue
release.
There's
lots
of
discussion
happening
around
lots
of
issues
need
to
be
fixed,
though
I
know,
Jen
brought
up
before
the
meeting.
B
So
that
would
be
an
awesome
change
to
have
made
and
gathered.
The
next
vote
fix
release,
but
no
items
of
notes.
There's
the
1.7.2
milestone.
You
get
the
list
full
issues
on
github
1.8
1.8
is
the
next
minor
release
that
comes
out.
September,
15,
2017
and
our
feature
freeze
for
any
release
is
the
first
of
the
month.
So
that
gives
us
about
six
weeks
before
feature.
Freeze,
we've
got
all
of
August
and
the
rest
of
July
to
make
some
progress
on
the
1.8
release.
B
There
hasn't
been
any
new
activity
on
this
and
a
few
weeks,
so
I'm
not
going
to
recap
that,
but
again
like
it
needs
needs
feedback,
testing
and
just
people
validating
with
the
approach
that
is
being
undertaken
there
is
is
one
that
we
can.
We
can
actually
implement
media
library
or
just
generally
improved
meeting
I
doing
is
issue
14
48.
That
wants
a
meta
issue
as
a
bunch
of
sub
items.
B
B
We
can
track
what
strings
need
to
be
translated
within
configuration
files,
and
that
issue
is
704
and
I'm
volunteering
to
take
that
one
on,
although
I
haven't
put
up
code
of
any
kind
yet
actually
demonstrate
the
implementation,
it's
just
discussion
about
how
it
could
potentially
implement
it.
At
this
point,
those
are
the
main
items
for
1.8.
B
There
hasn't
been
much
since
last
week,
so
I
don't
think
that
we
need
to
cover
it
any
further.
There's
also
the
1.8
issue,
tracker,
of
course,
on
github.
You
can
check
the
milestone
for
other
items
that
we're
hoping
to
get
implemented
before
the
next
release
and
I
know
in
the
general
Q&A.
Olaf
has
some
things
that
we
want
to
talk
about
this
release
regarding
regarding
1.8,
let's
see
so
items
fruit,
2.0
we've
covered
these
the
past
couple
of
weeks,
I
a
backdrop.
B
B
D
Many
people
follow
it
because
it's
the
modules
and
contraband,
it's
even
not
on
the
project
quite
pages
because
of
a
technical
problem,
I
think
and
so
I
had
the
idea,
if
so,
I
remembered
the
discussion
to
to
not
put
it
in
koihime
deity
and
I
think
it
was
yeah
generally
a
good
idea.
But
now
it
turned
out
that
so
progress
is
more
or
less
stopped
on
the
module
and
so
yeah
I
had
the
idea.
D
If
we
that
we
move
it
in
Coram
more
quickly
to
get
more
more
feedback
and
also
maybe
more
people
who
could
have
helped
with
it
not
only
mike,
because
I
personally
can't
can't
hurt
technically,
I
can
only
get
feedback,
but
I
can't
write
some
code.
Yeah,
that's
more
or
less
than
idea
and
and
I
saw
that
as
I
said,
references
is
very
popular
and
I.
Think
many
people
and
don't
move
to
reference,
because
they
have
a
lot
of
features
in
references
which
they
don't
find
in
reference
and
so
obey
they
can't.
D
They
can't
move
reference
and
that's
potentially
a
lot
of
people
who
would
also
hate
to
make
progress
in
the
module
yeah.
So
the
idea
was
to
move
it
in
Cobb,
I,
don't
know
when,
but
I
think
from
the
functionality.
Question
would
be
good
to
to
have
the
goal
to
to
gain
feature
feature
parity
with
references
and
put
it
down
into
call,
maybe
as
an
idea
I.
A
A
A
If
we
don't
like
it,
but
I,
don't
know
I,
don't
I,
don't
like
personally
know
what
the
issue
is
with
my
sites,
the
ones
that
are
using
references
or
using
references,
because
they
were
out
before
a
reference
existed
and
I'm,
not
moving
them,
because
I'm
not
working
on
those
sites
at
all,
they're
sort
of
in
a
done.
State
I
haven't
run
into
the
problems
that
you're
running
into
right
now
on
new
sites.
A
I,
don't
know
if
that's
just
the
new
sites
aren't
using
any
kind
of
reference
feature,
but
I
think
that
the
things
that
you
pointed
out
are
things
that
we
should
work
towards
feature
parity
on.
Not
all
that's
gonna
be
easy,
like
just
the
architectural
decisions
that
we're
dealing
with
in
reference
are
a
little
different,
Mike
I,
don't
know
if
you
want
to
speak
to
any
of
this,
because
you
have
a
lot
more
experience
with
how
reference
works.
Yeah.
E
E
Basically,
if
you
can
create
lists
of
items
that
are
referencing
the
current
node,
as
opposed
to
just
things
that
it
references.
So
we
sort
of
knew
about
that
and
we
need
to
get
done.
That
was
sort
of
like
one
of
the
main
blockers
that
I
wanted
to
finish
before
we
do
a
official
full
release,
he
wrote
to
add
more
widget
types,
which
might
be
helpful
right
now.
D
E
Reference
which
basically
is
an
entity
general
purpose,
reference
module
for
all
entities
and
though
it
basically
is
the
same
place
as
any
reference.
So
if
there's
any
features
that
entity
reference
supports
that
are
commonly
used
for
many
sites,
we
kind
of
need
to
support
those
that
we
want
people
to
switch
from
using
and
any
reference
and
backdrop
to
reference
in
in
any
reference
in
Drupal
to
back
to
reference
in
backdrop,
so
yeah.
So.
E
E
So
if
anyone
actually
wants
to
help
with
the
the
code
part
of
the
module,
that
would
be
helpful
since
I
haven't
had
a
chance
to
do
it.
We
just
finished
moving
and
I'm
getting
back
up
to
speed,
so
I
might
be
able
to
return
to
that
soon,
but
yeah
any
additional
help
would
be
helpful
if
it's
a
it's
a
priority
for
the
community.
Let's
try
to
you
know:
do
some
commits
or
pull
requests.
A
I
think
we
just
need
more
people
involved.
It's
a
lot
to
ask
one
person
to
kind
of
stay
on
top
of
a
ton
of
stuff,
so
I
think
you
have
a
good
idea
of
like
reaching
out
to
people
that
are
already
using
reference
for
backdrop
and
try
and
get
them
to
to
switch
to
reference,
get
that
backwards.
Use
of
references
and
switch
to
reference.
A
I
am
definitely
one
of
those
people
I'm
not
working
on
a
native
sites
right
now,
but
if
I
can
just
get
back
to
them
and
then
be
like
okay,
we're
do
anything
else.
I'm
gonna
switch
you
to
reference
and
then
we'll
see.
What's
going
on,
yeah
people
are
busy
it's
hard,
but
I
agree.
It's
important.
We
just
need
to
figure
out
how
to
make
this
time.
A
D
Maybe
and
I
have
an
idea.
We
could
that's
a
small
idea,
but
maybe
we
could
update
the
issue
and,
in
the
backdrop,
in
the
backdrop,
queue
which
might
have
been
titled
like
move
reference
to
call
or
something
and
there,
and
we
could
update
that
issue
so
because
a
lot
of
people
with
vector
of
issues
and
so
they're
up
to
date,
mm-hmm.
D
A
E
B
E
So
this
is
sort
of
gonna
tie
in
with
what
I
was
talking
about
before
about
perhaps
doing
some
doing,
some
user
interviews,
so
I
might
be
asking
I
think
I
have
to
interview
like
10,
10
users
or
customers,
so
I
might
be
contacting
you
guys
and
asking
for
recommendations
on
who
else
to
talk
to
amongst
people
using
the
product,
yeah
and
I'm,
hoping
to
put
together
sort
of
a
product
overview
presentation
that
maybe
I
can
get
at
the
October
get
together.
That'd.