►
From YouTube: Backdrop Weekly Nov 30th
Description
Today’s development agenda: http://bit.ly/2zEWt0N
A
All
right,
we
are
on
air
happy
Thursday,
November,
30th
everybody.
This
is
a
meeting
to
check
in
on
active
development
tasks
for
backdrop
CMS
on
our
agenda.
We
have
no
updates
for
the
project
management
committee.
This
week,
it's
been
two
weeks
since
we've
had
a
meeting
and
there
are
a
lot
of
new
projects
out
there.
We've
got
free
screen,
email
contact,
form
layout,
wild
card,
CK
editor
autograph,
how
to
grow
in
a
new
theme,
bootstrap
light
since
the
last
time
we
record
it.
So
thank
you
to
our
amazing
kitchen.
A
Community
was
continuing
to
crank
out
fantastic
modules
and
themes
for
people
to
use
I.
Think
in
the
last
meeting
we
also
mentioned
that
the
forum
site
might
is
up.
It
looks
like
it's
been
getting
a
lot
of
attention,
even
since
the
last
meeting,
so
it
would
encourage
people
to
begin
to
use
it.
You
have
to
create
an
account
there
to
use
your
existing
account,
we'll
get
that
sorted
out
eventually,
but
you
can't
go
there
to
ask
questions.
It's
a
good
place
to
start
discussions
about
things
that
maybe
aren't
specific
issues
with
the
software
assistance.
A
Special.
Thank
you
to
dr.
Elmont
who's
been
doing
all
the
work
on
the
forum
for
the
last
month.
It's
been
kind
of
languish
like
it's
been
not
getting
the
attention
it
deserves
lately
and
I'm
really
glad
that
he
put
into
time
to
get
it
across
the
finish
line
back
to
him,
CMS,
org,
I'm
thinking
the
last
meeting.
We
also
announced
that
we
had
a
showcase
we've
gotten
a
bunch
of
people
who've
submitted
sites
they
built
on
back
up
into
the
showcase,
which
is
really
exciting.
To
have
actually
been
doing
the
backdrop.
A
The
past
few
years
I
would
encourage
anyone
else
who
has
a
backdrop
site
to
go
ahead
and
post
it.
There
were
accepting
submissions
from
the
general
community.
There
is
some
moderation
on
there,
so
we're
going
to
take
a
look
at
sites
and
make
sure
that
the
screenshots
are
adequate
in
that
there
isn't
anything
missing.
It's
not
spam
posts
that
sort
of
thing
we
are
trying
to
get
those
published
just
locally
as
possible
once
they
come
in.
A
B
Hey
folks,
so
in
the
world
of
backdrop,
things
backed
up
product,
things
have
been
relatively
static,
I
wouldn't
say
that
we're
not
doing
things
but
the
items
that
we
normally
pull
out
and
the
agenda
here.
There
have
been
many
changes
there,
so
I'm
not
going
to
recap
those
again
just
because
it
seems
like
we
do
that.
Every
week
we'll
say
new
items
that
have
been
coming
up.
It's
really
great
to
see
new
issues
going
into
needs,
review
and
new
items
going
into
our
TVC
as
well.
B
We've
got
four
items
in
the
our
TPC
list:
Thank
You
Opie,
for
going
through
and
doing
those
code
reviews.
That's
really
highly
appreciated.
We
also
have
a
good
number
of
needs,
review
tickets
and
those
have
been
piling
up,
which
means
that
they're
on
my
plate
to
start
going
through
and
really
getting
some
feedback
out
to
all
those
wonderful
people
that
have
been
filing
for
requests
for
us.
So
there's
definitely
a
lot
of
actions
happening
in
the
world
of
court,
just
not
in
the
items
that
we
normally
pull
out
for
regular
ongoing
maintenance.
B
B
B
A
primary
area
of
effort
is
around
better
media
handling
and
in
particular,
better
file
management
capabilities,
and
these
issues,
I
think,
are
just
generally
summarized
in
the
media
library,
meta
issue
at
issue
1448
and
the
three
main
issues
that
we're
working
on
here
are
the
ability
to
edit
an
existing
file
issue.
27
96,
making
file
entities
field
about
26,
32
and
uploading.
A
file
manually
separated
being
attached
to
any
other
kind
of
content
is
issued.
B
26:33.
All
three
of
those
are
in
progress,
kind
of
continuing.
There
hasn't
been
recent
activity
on
them,
although
2790
6
is
definitely
the
one
that
is
farthest
along
unblocked
and
capable
of
moving
forward
at
this
point.
So
if
anyone
is
interested
in
continuing
to
push
that
one
forward
leave
a
note
in
there
saying:
hey
I'm
working
on
this
and
go
for
it,
because
that
that
one's
not
far
at
all
from
being
completed
at
an
update
and
update
hook
and
some
minor
string
changes
and
that
one
is
pretty
much
a
completion
so
yeah.
B
Those
are
the
items
that
we
have
I,
wouldn't
say
that
yeah
there's
been
too
much
progress
on
those
recently,
so
still
would
love
to
have
some
movement
there.
We
are,
you
know,
closing
in
on
release
time,
but
I
still
think
you
know
one
month
that
still
lots
of
time
for
us
to
achieve
all
of
those
things
for
the
1.9
release.
B
Let's
see
next
up
items
for
backup
2.0,
followed
by
three
question
marks
here
in
the
agenda.
I
think
we
had
discussed
this
earlier
today,
just
right
after
the
outreach
meeting
we're
talking
about
paragraphs
and
how
to
deal
with
the
the
paragraphs
module
as
it
exists
in
Drupal
7
and
how
to
provide
upgrade
pads
and
I.
Don't
know
Jen.
Do
you
want
to
elaborate
on
this?
It
looks
like
maybe
you
added
this
to
the
agenda.
A
So
it's
something
they're
very
proud
of
it's
a
good
point
to
mention
that
paragraphs
module
is
getting
a
lot
of
attention,
both
in
with
the
72
Drupal
8.
It's
a
fantastic
tool
that
allows
people
to
add
content
of
different
types
in
repeating
actions
to
different
pages
on
their
site.
So
you
can
create
landing
pages.
That
way
you
can
structure
a
long,
complicated
content
or
post
that
way.
Video
or
photo
captions
are
advertisements
or
whatever
it
is.
You
want
using
this
tool.
A
The
reason
I
had
all
this
question
much
on
the
agenda
is
because
we
talked
about
it
being
kind
of
big
in
a
feature
that
we
might
want
to
sleep
at
or
something
like
backed-up
2.0,
but
after
I
added
this
to
the
agenda,
I
realized
that
it
could
be
possible
that
we
could
add
paragraphs
in
the
backdrop
1x
life
cycle,
because
it's
currently
just
a
captured
module
and
there's
no
reason
that
I
don't
yet
that
we
would
need
to
break
the
API.
In
order
to
add
that
functionality
it
exists
for
equal
7,
it's
very
likely.
A
It
could
exist
the
backdrop
in
the
same
way.
So
if
we
needed
to
find
a
killer
feature
for
two,
that
might
be
something
we
want
to
continue
doing
it
to
anyway.
But
if
we
want
the
feature
sooner
than
2,
there
might
not
be
any
reason
that
we
would
have
to
wait
for
it.
So
I
just
wanted
to
mention
that
as
well.
B
Paragraphs
by
its
very
nature
implies
that
you
have
a
design
that
is
going
to
accommodate.
You
know
the
specific
paragraphs
that
you
set
up,
which
means
that
paragraph
Speights
nature
means
that
it's
a
site
that
has
had
an
architecture
and
a
design
set
up
that
is
then
followed
strictly
based
on
the
configuration
of
the
site
by
the
editorial
team,
and
so,
by
its
very
nature,
paragraphs
is
a
module
that
is
suited
towards
at
least
having
had
a
custom
design
plus
a
dedicated
set
of
editors.
So
maybe
that's
even
just
one
editor.
B
So,
although
it
paragraphs
is
a
great
solution,
I
think
having
it
available
for
backdrop
is
a
really
great
idea,
I'm,
not
sure
about
the
overlap
or
the
the
the
level
of
accuracy
targeting
here
for
our
audiences
versus
the
product.
The
backdrop
provides
I,
don't
know,
we
could
probably
discuss
further
on
that.
Just
an
initial
thought.
Based
on
that,
you
know
you.
C
Reason
why
I
mentioned
this
is
because
official,
even
in
the
projects
in
the
digital
projects
fights
they
mentioned,
that
it's
intended
to
be
the
replacement
module,
the
book
to
module
instead
of
field
group,
and
we
have
a
ticket
for
inclusion
of
that
feature
in
for
so
it
would
sing
redundant
to
just
you
know.
Maybe
we
just
should
replace
that
ticket
but
says
provide
a
field
group
import.
C
B
Actually
that
you're
right,
that
that
makes
it
that's
a
much
broader
piece
of
functionality.
That's
like
I
would
just
want
the
ability
to
group
multiple
fields
together
and
I'm,
multiple
of
them
and
you're
right
that
that
is.
That
is
a
very
common
use
case,
and
if
people
want
to
take
that
ability
and
go
crazy
with
it
and
end
up,
not
crazy
with
it,
but
you
know
want
to
use
it
as
a
structural
tool.
As
you
would
paragraphs,
then
you
know
that
could
be
killing
two
birds
with
one
stone.
C
And
there's
people
that
want
to
include
sections
of
content.
That
is
not
simple
text
like
accordions
or
images,
but
you
know
be
able
to
move
that
around
with
their
content.
So
they
add
text
and
then
an
accordion,
then
again
text
and
then
an
image
and
they
then
an
editor
might
come
and
decide
that
they
want
to
move
these
things
up
and
down
doing
that
in
the
WYSIWYG
like
providing
volumes
in
the
WYSIWYG.
It's
kind
of
you
know
it
needs
a
lot
of
dev
work,
whereas
it
would
be
simpler
to
do
that.
I
like
them.
B
I'd
say
looks
like
Germans
okay,
the
moment
I,
don't
have
anything
further
I
think
to
discuss
on
that
I
think
it's
a
good
thing
for
us
to
consider
and
I
think
taking
a
look
at
paragraphs
as
I'm,
not
sure
full
continue,
calling
paragraphs
just
because
it's
a
kind
of
a
terminology
Drupal
ism
there,
but
continuing
to
look
at
that,
especially
as
an
option
for
handling
multiple
field
handling
grouping.
Then
yeah.
Let's
keep
keep
an
eye
on
it
and
just
continue
that
discussion
and
be
and
the
course
with
you.
D
D
C
Maybe
a
different
like
that,
or
maybe
it's
the
other
way
around-
it's
not
it's,
not
the
paragraphs
module
that
is
mentioning
to
build
field
collection,
but
it's
how
that
leads.
The
other
way
around
so
there's
some
modules
in
vivo
code
that
say
that
they
are
thinking
of
moving
towards
a
paragraph
solution.
That
was
the
main.
D
C
Done
if
I
can
be
used
for
various
use
cases,
but
for
the
specific
ones
that
we
have
decided
that
we
do
want
these
sort
of
features
in
core,
maybe,
instead
of
trying
to
do
it
to
do
the
port
of
the
field
group
or
field
collection
fields
that
maybe
we
should
just
consider
moving
to
paragraphs
instead,
which
is
more
flexible
as
a
more
include
user
interface
notice.
That's
my
opinion.
B
Okay,
it's
giving
me
nightmares.
Look
in
that
field,
collection,
project,
page,
okay,
all
right,
general
discussion,
last
item
of
the
agenda.
Today
we
have
some
discussion
about
translation
and
internationalization
things
that
we're
doing
to
kind
of
move
things
forward.
There
I
do
think,
maybe
just
giving
a
little
bit
of
a
general
summary
might
be
a
good
idea,
because
there's
been
some
movement
happening
in
that
area,
Olaf
is
there
anything
in
particular
you'd
like
to
mention
regarding
translation
internationalization,
since
your
present.
D
Yes,
shortly
I,
we
have
this
project
to
translate
the
backdrop
for
good
website
and
as
a
use
case
for
for
multilingual
or
a
better
multilingual
backdrop,
and
so
we
began
to
work
with
it
and
make
beginning
to
make
some
progress
and
yeah
found
some
of
the
first
issues.
And
now
we
in
the
last
day
is
we
had
an
example.
We
fixed
one
of
the
issues
and
which
wasn't
really
a
back
but
yeah.
It
didn't
make
sense
a
certain
behavior
and
off
backdrop.
B
Forward
to
it,
yeah,
that's
great
I
really
like
that.
We've
got
this
community
projects,
but
its
purpose-
and
you
know
basically
working
together
on
something
that
gives
us
this
opportunity
to.
You
know
test
out
these
use
cases.
A
backdrop
like
us
group
together,
so
I
think
it's
great
on
all
on
all
sides
and
to
summarize
yeah
the
field
that
we
were
the
option
we
were
talking
about.
Let's
see,
gosh
I
had
that
issue,
just
as
I
can
go.
Thank
you
is
this
you
six
little
into?
Oh
sorry,
yes,
this
is
a
different
one.
D
B
Backdrop
court
issue
just
suggesting
that
we
move
some
functionality
from
I
18
in
module
that
had
been
a
Drupal
7
just
directly
into
Drupal
court
backdrop,
court
and
yeah
great
idea.
I
mean
we
have
that
flexibility
and
backdrop,
and
that
wasn't
the
case
in
you
know
in
Drupal
7.
So
you
ended
up
with
modules
like
I,
18
and
macho
that
were
essentially
necessary
to
have
a
useful
internationalized
or
translated
website
so
yeah.
B
Also,
two
weeks
ago,
at
the
end
of
the
dev
meeting,
we
talked
about
the
p
OT
extractor
module,
Pio
TX
module,
which
is
in
backdrop,
can
trim
Jeff
did
a
great
job
porting
that
modules
over
tobacco
to
get
the
most
basic
functionality
working
at
the
end
of
the
meeting
last
two
weeks
ago,
I
opted
to
volunteer
to
fix
extracting
translation
strings
from
from
JavaScript
files,
and
so
that
is
now
fixed
and
working.
So
that's
great
I'm
continuing
to
do
some
work
today
on
it
just
kind
of
continue
removing
some
unnecessary
corrupt
from
the
module.
B
But
it's
looking
really
good.
I'm
really
glad
to
see
this
bundle
come
together
and
it
will
kind
of
hopefully
enable
us
to
start
using
that
wonderful
localization
server
that
we
have
set
up
that
doesn't
have
any
strings
on
it,
because
the
the
big
problem
here
is,
we
don't
have
the
module
setup
yet
to
do
the
parsing
and
then
to
upload
it
to
the
translation
server.
B
So
first
thing
is
to
get
the
template:
extractor
translation,
template,
extractor
working
and
then
and
then
from
there
automate
the
process
of
when
a
new
release
comes
out
due
to
the
template
extraction
and
then
upload
it
to
the
translation
server.
So
it's
great
to
see
the
first
step,
or
maybe
the
second
or
third
step
coming
along
so
nicely.