►
From YouTube: Backdrop Weekly June 8th, 2017
Description
Today’s development agenda: http://bit.ly/2rq13MV
A
A
There's
no
updates
from
the
PMC
this
week.
There
are
a
couple
of
new
contributed
projects,
including
web
form,
validation
in
redirect
403
to
user
login,
which
is
a
popular
Drupal
module.
So
it's
exciting
to
have
it
for
backdrop.
First
item
on
the
list
is
a
translation
server
update
and
there
is
now
a
fantastic.
A
Document
in
gist
that
people
can
refer
to
if
they
want
to
or
off-road
up
a
bunch
of
notes
about,
what's
been
done,
where
we're
stuck
where
we
could
use
more
help,
there's
a
recommendation
in
there
to
try
and
get
a
more
concentrated
effort
working
on
the
translation,
server
and
I.
Think
we've
got
two
great
opportunities
for
that.
A
Coming
up,
there's
going
to
be
a
sprint
after
the
Montreal
Drupal
camp
and
a
sprint
after
the
Twin
Cities
Drupal
camp
and
that's
a
place
where
we
could
see
if
there
are
any
people
there
that
have
experience
with
translation
in
Drupal
7
that
we
could
work
on
or
work
with
to
get
us
some
moving
something
some
progress
on
that.
So
that
might
be
good
if
we've
just
got
a
couple
of
hours
to
focus
on
it
too,
to
try
and
unblock
ourselves
on
making
progress
here,
I'll
left.
C
A
All
pretty
well
documented
in
this
gist,
so
I
put
a
link
to
it
in
the
agenda.
You
can
see
it
now
on
the
screen,
but
there
are
a
couple
of
great
ideas
about
how
to
unblock
us
and
move
forward
on
getting
the
translations
are
very
working.
You.
D
So
generally,
the
problem
is
the
general
problem
that
we
still
rely
on
Drupal
on
the
drupal
translation
server
and
which
has
a
few
drawbacks.
Like
backdrop
is
continuing
to
make
progress
and
so
changes
a
lot
of
translation,
a
lot,
a
lot
of
language
strings
and
and
so
would
make
small
it's
difficult
for
people
to
get
the
drupal
files
and
then
to
work
with
them.
So
we
put
let
out
well
to
have
our
own
translation
server
and
we
started
to
build
it
Jeff
and
me,
but
only
we,
we
we're
good
team,
but
not
the
bests.
D
D
Put
pipe
would
be
ideal
who
know
the
technical
concept
of
translation
in
Drupal
7
so
and
yeah.
That's
a
my
some
ideas:
how
to
get
some
people
to
work
with
us
and
first
idea
is
to
ask
quick
sketch,
if
you
could
do
that,
but
I
guess
there's
no,
not
enough
time
and,
and
so,
but
he
still
whited
and
but
yeah.
D
If
we
don't
manage
through
that
very
fast,
we
could
at
least
build
sort
of
Booty
language
community
or
a
separate
PETA
channel
with,
for
example,
the
Russian
guys
who
are
around
maybe
some
spanish-speaking
people
and
so
on
and
and
there
you
begin
to
manage
something
and
maybe
even
only
to
upload
our
personal
translated
files
and
to
to
the
language,
server
and
so
on.
So
then
yeah.
If
you
want
to
have
look
at
the
document
and
post
some
comments
there,
and
so
we
can
go
on
but
I'm
also
curious,
curious.
D
B
E
This
is
this:
is
my
quick
sketch
I
know
I'm
just
a
document
screen
sharing
right
now,
but
for
those
listening,
so
yeah
I,
really
I
would
really
like
to
be
able
to
help,
but
you
write
them
on
time
constraints,
there's
a
lot
of
different
things
or
not.
So
if
I
think
your
suggestion
I'm
trying
to
solicit
more
help
from
those
that
have
experience
in
this
realm
and
from
Drupal
7
would
be
the
best
path
forward.
E
And
if
we
get
those
volunteers
like
I'm,
definitely
more
than
happy
to
empower
them
in
any
way
possible
like
whether
that
means
server
access
or
you
know,
I'm
not
quite
sure,
one
other
things
that
we
could
potentially
need
other
than
you
know,
direct
access
to
the
server's.
Everything
right
now
is
fairly
open
and
everything
is
coordinated
on
Khadafi
I
guess
if
you
need
github,
contriving
any
volunteers
in
that
manner
as
well,
but
but
actually
for
the
1.8
like
go
like
I've,
been
as
we'll
get
to
in
the
product.
B
E
B
As
in
the
intermediate
collaboration
help,
can
we
just
create
a
new
key
hub
repository,
so
people
can
upload
the
Codex
files
is
if
they
start
uploading
their
own
files
in
a
forum
or
github
issues?
It's
gonna
stop
message.
It
get
messy
and
if
they
have
been
on
github
repository,
people
can
make
contributions
like
pull
requests
on
the
existing
products.
Mm-Hmm
yeah.
E
E
That's
good
idea
should
we
put
that
in
backdrop,
ops,
gem
or
a
crop
can
trim
I'll,
say:
hey,
hey,
listen!
She
yeah
I,
mention
it
that's
great
idea
and
yeah.
We
can
make
a
real
simple
repository.
That's
just
yeah!
We
could
probably
take
Jeff's
PRT
x-file
right
generate
one
against
the
current
work
on
core
and
then
and
then
upload.
That
is
the
template.
E
D
D
B
E
E
Yeah,
that's,
unfortunately,
exactly
what
I
was
thinking.
Oh
gosh,
wait.
Actually,
yes,
I
feel
like
that
is
like
a
mixed
bag.
You'd
be
able
to
get
more
developers,
but
I
have
a
feeling
like
a
lot
of
people
that
know
how
languages
probably
wouldn't
really
be
comfortable
with
git,
although
you
know
like
Gregory,
you've
written
up
that
excellent
article
and
like
how
you
managed
to
make
patches
against
a
backdrop
without
without
doing
anything
without
any
local
check
out
like
it's
all,
just
your
github,
a
blanket
of
like
yes,
yeah.
E
E
E
D
A
Alright,
so
next
on
the
list
is
vector
up
CMS
project
progress
report.
So
Nate,
do
you
want
to
talk
about
one-seven-one,
a
sure.
E
E
State
I
do
have
some
availability
in
the
next
couple
of
days,
so
I
am
hoping
we'll
make
a
little
bit
of
progress,
getting
some
bug
fixes
into
the
1.7
branch,
but
yeah
there's
really
no
substantial
items
for
1.71,
and
so
just
as
as
we
accrue
issues
and
start
putting
them
in
there
when
it
feels
right
for
us
to
make
a
release,
then
we'll
push
out
or
release
with
latest
fixes.
I
mentioned
during
the
last
day
of
meeting
that
we
did
push
up.
E
1.7
point
o2,
Pantheon's
upstream
and
if
we
have
not
yet
done
so,
should
check
the
checklist
done.
If
we
have
not
yet
done
so
updated
like
the
doctor
images
and
any
other
up
streams
that
we
potentially
have
do
you
have
any
idea
what
the
status
of
the
doctor
images
are.
Are
they
up
to
date,
no
I'll
go.
E
E
E
Sorry
September
15
2017,
and
we
have
a
couple
of
items
here-
that
we've
got
slated
for
focus
in
1.8
release
cycle,
one
of
which
is
a
piece
of
functionality
that
has
been
put
together.
That
is
in
a
place
that
needs
review
the
concept
of
layout
relationships,
which
is
issue
21,
34
I,
haven't
looked
at
this,
but
I,
don't
believe.
There's
activity
has
happened
here,
nope,
but
that's
a
yeah,
an
issue
that
needs
review,
slash
work
hasn't
been
any
update
since
last
week
saw
rehash
that
better
media
supports
its
issue
1448.
E
So
this
issue,
14:48,
is
a
meta
issue
that
includes
a
bunch
of
subtasks
and
dagger.
Heart
was
kind
enough
to
split
it
all
up
into
a
slightly
more
granular
set
of
tasks
than
what
we
had
last
week.
He
already
had
put
forth
a
substantial
pull
request
to
add
several
pieces
of
functionality,
but
it
was
a
little
bit
like
too
comprehensive.
E
It
was
like
all
of
a
bunch
of
different
issues
all
at
the
same
time,
and
now
that
he's
broken
these
up,
we
have
a
lot
better
opportunity
to
handle
these
items
one
at
a
time
and
go
through
them.
It's
also
better
for
giving
up
the
work.
I
know
that
we
had
some
of
these
issues
like
this
guy
here
that
al
Rose
rose
cough
has
been
kind
of
staking
these
out
as
well.
E
So
they
have
some
good
opportunities
now
to
to
distribute
this
work
across
different
people,
but
it
does
look
like
our
Rose
coffin
de
guardar
kind
of
carrying
the
flag
there
towards
improving
that
and
I'm
sure
there's
plenty
of
opportunity
for
increased
collaboration
there,
as
as
code
starts
coming
in
or
if
you're
interested
in
putting
forth
code.
But,
let's
you
know,
keep
an
eye
on.
E
Another
item
that
is
the
least
of
personal
interest
to
me,
is
issue
704,
which
we
mentioned
slightly
earlier
in
the
meeting
about
adding
configuration,
translation
yeah.
That
issue
is
in
it
needs
feedback
states,
there's
no
code,
yet
mostly
just
kind
of
concepts,
and
so
we
can
kind
of
get
some
feedback
on
the
basic
battle
plan
there
and
then,
hopefully,
in
the
in
the
coming
weeks,
I'm
planning
on
putting
forth
the
some
code
to
move
that
forward.
E
And
of
course,
if
there's
any
interest
in
somebody
else,
volunteering
to
take
the
plan
that
is
in
there
and
run
with
it,
then
yeah
hop
in
there's
a
the
opportunity.
Is
there
to
jump
in
and
take
the
the
lead
on
code
implementation
there
and
those
are
the
items
that
we
have
slated
for
1.8
that
we're
putting
focus
towards
of
those
present
here.
Do
we
have
anything
else
that
we
would
like
to
add
to
the
1.8
hit
list.
A
A
Not
sure
we'll
get
all
the
issues
in
1448
in
for
1-8,
but
I
think
if
we
could
get
like
that
super
solid
base
of
like
having
file
entities
and
having
a
browser
like
we
can
add
other
stuff
later
like
field
Bowl
files
or
whatever,
but
I
would
love
to
have
a
better
user
experience
of
managing
files
and
I
know.
We
started
on
that
in
the
last
release
and
I'd
love
to
see
that
make
some
progress.
So
there's.
A
A
it
so
that
but
they're
on
they're
on
the
same,
like
sort
of
roadmap
of
like
we
want
media
stuff
in
core
and
so
I
think
it's
kind
of
kind
of
important
for
us
to
do
the
same
thing
like
in
the
same
way.
We
don't
have
to
get
all
of
it
in
already,
but
I
think
that'll
also
be
useful
for
people
who
are
like
coming
from
Drupal
8
and
already
think
that
MIDI
is
in
core.
We
could
do
the
same
sort
of
thing,
so
yeah.
E
E
E
E
A
Let's
go
Victor.
Our
meeting
was
right
on
time
this
week,
so
I
guess
I
mean
we've
got
not
a
bunch
of
work
to
do
in
the
issue
queue,
but
nothing!
That's
on
fire,
which
is
nice.
So
maybe
we
will
wrap
the
meeting
and
then
move
to
get
her
and/or
issues
and
then
meet
again
next
week.
Oh
wait
so
next
week.
Just
so
you
guys
know
Nate
and
I
are
going
to
be
doing
a
backdrop
training
on
Thursday.
So
we
won't
be
here
for
these
meetings.