►
From YouTube: Backdrop Weekly July 27th
Description
Today’s development agenda: http://bit.ly/2uE8Rib
A
All
right,
Ronnie,
happy,
Thursday
July,
just
make
it
some
time
more,
but
it
idiot
you're.
There
sorry
I
was
sitting
up
next
weeks
me
I'm
right.
Okay,
so
today
on
the
agenda,
a
pitch
from
the
PMC
we're
still
working
on
an
agreement
between
us
and
the
software
freedom,
Conservancy
I
sent
them
an
email
last
week.
What
what
what
I
thought
was
all
the
information
they
needed,
that
they
haven't
gotten
back
to
us
yet
so
I
reach
out
to
them
again,
just
like
asking.
A
If
there's
more,
we
can
do
to
help
move
things
forward
or
if
we
have
to
wait
for
the
legal
document
from
their
team.
So
hopefully
that
will
resolve
here
quickly,
but
I
can't
guarantee
that
community-related.
We
have
a
new
community
member
who
has
been
creating
a
ton
of
fantastic
for
cuts
and
new
kinship
projects
that
aren't
being
contribute
that
are
still
out
there
and
available
for
people
which
is
great
ob
from
the
drupal
france
community.
A
It's
not
working
on
backdrop
stuff
too,
so
welcome,
o
p
and
thanks
for
all
of
your
amazing
contributions
already
contributed
projects.
It
looks
like
we
have
a
new
control.
I
am
c
e
nick
directory
and
that
was
ported
by
daniel
rose,
and
that
was
his
first
port.
I
think
so,
unless
a
congratulations,
Daniel
rose.
Thank
you
for
helping
us
with
more
new
backdrop,
kinship
prejudice,
so
wait
it
related
to
backdrop
CMS
org.
Last
week
we
talked
about
adding
a
security
mailing
list.
A
We
have
since
deployed
it
tested
it,
and
then
this
week
with
this
week's
security
announcement
that
came
out
yesterday
confirmed
that
it
is
working
as
anticipated.
So
anytime
we
publish
a
security
announcement
on
dr
pc,
masta
org
emails
will
go
out
to
anyone
who's
curious
about
receiving
those
letters.
So
if
your,
if
you
want
to
sign
up
for
backdrop
security
mailing
list,
you
can
edit
your
user
account
page
and
there's
a
new
checkbox
there
for
receiving
those
messages.
B
In
our
list
of
thanks,
I'm
sure
you
just
covered
this
in
the
outreach
meeting
that
was
just
before
this,
but
newsletter
went
on
today
covering
our
community
spotlights
which
was
written
up
by
Tom
thanks
Tom
that
looks
the
the
spotlight
is
awesome
and
the
newsletter
yeah,
it's
so
exciting,
yeah,
it's
great
that
we're
actually
utilizing
that
okay,
so
back
drop
CMS.
Let's
talk
about
software,
so
our
current
version
is
back
dropped,
one-point-seven
one
and
one
points
up
to
be.
The
next
bug
fix
release
right
now.
There
are
a
number
of
issues
that
we
know
about.
B
Of
course,
something
we've
got
hundreds
of
issues
that
could
be
fixed
at
any
given
time,
but
none
that
are
outstanding.
That
would
necessitate
a
new
bug
fix
release.
So
you
can
get
a
list
of
all
the
more
important
items
for
the
bug
fix
or
for
bug
fixes
by
checking
into
1.7.2
milestone.
A
huge
number
of
these
are
needs
review
which,
if
I
have
availability
I
will
go
through
those,
but
it
also
really
helps
tremendously
if
we
can
get
across
peer
reviews
happening
between
people
that
are
filing
pull
requests
reviewing.
B
B
You
know
heading
into
August,
which
basically
means
we
have
a
month
of
development
remaining
on
the
1.8
version
right
now,
1.8
1.7,
a
really
pretty,
regardless
of
how
much
progress
would
make
on
1.81
point
it
will
be
coming
out
and
it
will
just
have
more
less
functionality
in
it,
depending
on
how
many
changes
would
get
in
the
items
that
we
have
slated
for
1.8,
as
as
a
focus
include
layout
relationships,
which
is
your
2134.
There
hasn't
been
any
progress
on
that
since
last
week,.
B
A
A
B
B
Great
and
lastly,
config
translation
is
issue
704
this
one
I'm
trying
to
take
a
lead
on,
but
there
still
hasn't
been
any
updates
there.
No
no
demonstratable
code
as
I
do
still
feel
that
that
functionality
is
straightforward
to
add,
but
actually
going
through
and
converting
all
of
our
implementations
might
take
a
little
bit,
but
we
could,
you
know
start
with
including
the
implementation
and
then
go
through
and
actually
updates
all
of
the
integrations
once
we
have
it
in
place.
B
B
B
2.0
I
mentioned
this
last
week
that
unless
we
have
something
new
to
discuss
on
2.0,
I
think
we'll
just
continue
past
that
section
it
may
be
coming
up:
January
15th
2018,
what
exactly
is
included
in
it
and
whether
or
not
that
it's
API
breakage,
all
those
things
are
still
open
for
discussion.
Do
we
have
an
issue
tracking
discussions?
42.0
I
know
we
do,
but
I
can't
remember
where
it
is.
We
should
include
that
in
the
agenda,
if
we're
gonna
be
bringing
up
2.0
on
a
regular
basis,
I.
B
B
C
These
were
five
before
we
had
the
ability
to
individually
place
fields
through
the
block,
UI
and
I
just
had
an
idea.
They
haven't
ironed
out
everything.
You
know
that
we've
spent
a
lot
of
time
on
every
bump
it
via
the
manage
fields
UI,
but
I.
Think
now
that
we
can
individually,
like
I,
don't
know
how
we
can
bring
the
the
blocks.
C
Now
that
we
have
oh,
it's
like
when
I
wrote
when
event
when
I
went
through
the
old
tickets,
those
old
tickets,
they
were
mentioning
ideas
that
people
had
of
how
they
should
work,
and
the
first
thing
that
came
to
my
mind
was
wait.
A
minute
we
have.
We
can
you
can
place
individual
fields
in
in
regions,
because
this
this
relates
having
irenna
everything
that
relates
to
that.
But
I
think
it's
a
cool
idea
that
maybe
we
can
target
for
2.0.
B
A
Is
like
kind
of
we
talked
about,
didn't
like
any
layouts,
where
you
could
do
something
like
at
the
ball
footer
with
a
bunch
of
different
stuff
in
it
that
same
concept
that
apply
to
like
a
teaser
play
out
great,
where
you
might
want
the
image
on
the
left
and
the
content
on
the
right,
or
something
like
that.
So
if
we
can
find
a
way
to
do
the
manage
displays
UI
as
the
layout
UI,
that
concept
could
be
really
useful.
Other
places
too.
C
C
Want
the
main
content
region
by
default,
and
then
people
I've
been
interacting
with
Drupal
8
setups.
They
a
lot
as
well
and
have
separated
media
it's
regularly
of
the
fields
and
the
display
of
the
form
they
can't
form
display
and
maddux
won't
just
play
something
like
that.
I,
don't
know
how
much
value
that
as
an
Arab
and
I,
don't
think
that
you
need
to
set
up
the
target
audience
with
what
I
have
you
can
defend
over
giving
with
the
yields
and
then
what
they
have
that
actual
display
but
yeah?
D
C
That,
oh
I,
don't
like
all
of
the
tickets,
but
when
I
when
I
hear
field
UI,
it
reminds
me
the
the
mock-ups
that
Wes
has
put
together
with
the
instead
of
selecting
via
dropdowns.
The
available
fields
would
select
by
a
tiles
which
sort
of
like
visually
represent
what,
but
the
field
is,
and
so
I
didn't
recall
if
it
was.
If
B
placement
was
brought
into
that
discussion,
I,
don't
but
yes
it
don't!
That
is
interrelated.
It
will
improve
the
experience.
B
B
B
E
B
E
We
want
to
treat
that
the
same
way
we
have
been
do
we
want
to
perhaps
do
another
day
also
as
like
a
planning
day
or
something
like
that.
I
feel
like
the
summit
is
going
to
be
sort
of
like
a
thing
for
anyone
at
that
camp
to
come
join,
but
we
sort
of
have
some
Direction
issues
and
like
deciding
what's
going
to
go
and
the
the
2.0
release
and
stuff
like
that.
A
I
mean
I
think
if
we're
gonna
have
a
bunch
of
people
at
the
same
place
at
the
same
time,
that
would
be
really
valuable
conversation
to
have
with
all
of
us
in
person.
I
agree
that
that
doesn't
necessarily
seem
like
something.
Then
we
need
to
invite
anyone
in
who's
at
that
camp
to
participate
in
I,
don't
know
about
timing
like
we
might
I'll
check
in
with
Anne,
we
will
figure
out
what
the
is.
Usually.
We
do
one
day
of
summit
and
one
day
of
training
and
then
there's
two
days
of
camp.
A
If
we
aren't
doing
a
training,
it
will
be
possible
to
do
that
on
the
training
day
if
they
did
half
day
trainings,
it
might
make
more
for
that
core
thing
to
be
a
half-day
event
rather
than
a
full-day
event.
We
could
also
try
and
do
it
like
a
day
before
or
the
day
after,
like
this
Sunday
after
bad
camp.
A
E
In
any
case,
I
think
that
we
should
start
maybe
regularly
reminding
people
that
this
is
coming
up,
because
it's
coming
up
in
three
months
now.
So
if
people
are
planning
on
coming
from
out
of
the
area
to
come
to
our
backdrop
thing,
then
they
might
need
to
start
looking
at
like
transportation
and
lodging
and
stuff
yeah.