►
From YouTube: Backdrop Weekly 4/6
Description
Today’s development agenda: http://bit.ly/2mTNtlW
A
A
We
have
a
section
the
beginning,
this
meeting,
where
the
PMC
can
have
provide
any
updates
to
the
general
community
and
the
one
thing
that
I
wanted
everybody
to
know
that
we're
working
on
right
now
is
our
code
of
conduct
and
we
have
a
public
github
repository
which
is
under
the
backdrop,
ops
group
called
concept
that
has
a
current
draft
of
the
code
of
conduct.
It
has
an
issue
queue
if
anyone
has
thoughts
on
ways
that
we
can
improve
that
glowed
upon
that,
I
would
encourage
everybody
to
participate
there.
A
A
All
right
for
backdrop:
CMS
org
we've
been
working
on
rolling
out
a
redesign
of
our
homepage
for
the
last
few
months.
Updates
on
that
front,
wes
is
back.
He's
gonna.
Take
the
rain
its
back
from
us
on
trying
to
figure
out
how
to
get
from
what
we
have
now,
where
we
won't
want
to
be
and
I'm
working
on
sending.
B
A
The
stuff
he
needs
to
get
up
to
date,
and
then
we
will
continue
to
move
forward
with
that.
The
forum
website,
I
I,
applied
the
fixes
that
we
thought
would
fix
the
problem
last
week
and
they
can't
tell
if
they
like,
fix
half
the
problem
is
that
but
I
did
some
testing
and
it
doesn't
seem
entirely
fix.
So
we're
going
to
keep
working
on
that
that
same
fix
that
we
applied
to
the
forum
site
I,
put
on
the
translation
site
as
well.
The
localized
backdrop
sea-mester
work
and
it
I
didn't
do
any
testing.
A
Their
I
only
did
testing
on
the
flan,
but
I
would
have
expect
similar
results.
So
I
don't
know
if
I
also
need
to
apply
that
hatch
to
backdrop,
semester,
org
the
main
site
or
if
we
should
I
didn't
look
at
it
in
complete
detail,
but
we
do
need
to
do
some
more
follow
up
and
figure
out.
What's
going
on
and
try
and
get
our
user
experience
of
logging
in
unsub
sites,
more
seamless,
I
think
before
we
start
promoting
those
sets
too
much
translation
server.
A
A
Ok,
so
other
stuff,
we're
working
on
is
mostly
related
to
backdrop
see
in
this
tub
product
as
opposed
to
the
websites
and
meat.
Do
you
want
to
take
it
over
from
you.
C
Me
Wow
yeah.
We
really
did
trim
down
the
app
schedule,
so,
okay,
yay,
okay,
so
status,
updates
for
backdrop
the
product
so
but
fix
releases
their
next
bug-fix
release
is
one
point
six
point:
four
there's
no
major
issues
that
are
currently
outstanding
for
were
the
1.6
release
and
so
bug
fixes
are
just
up
being
merged
in
on
an
as
is
needed
basis,
so
yeah,
nothing
new
in
the
1.6
realm
items
for
1.7,
so
1.7
is
coming
out.
C
May
fifteenth
that
is
a
little
over
a
month
from
now,
but
we
have
until
the
end
of
April,
to
implement
all
of
our
changes.
So
we've
got
three
weeks
remaining.
Basically
in
the
1.7
development
cycle,
we
have
a
number
of
features
that
we
would
like
to
get
slated
for.
1.7
some
items
have
already
been
merged
and
there's
a
bunch
of
items
that
you
can
find
them
at
github.
C
C
C
The
status
message
Ron
it's
not
really
like
a
redesign
or
even
like
a
designing
of
the
entire
page.
I
know
drupal
8
dot
3
came
out
yesterday
and
they
also
did
a
redesign
of
the
status
report.
So
perhaps
this
is
what
Gregory
will
got
his
inspiration,
but
our
version
is
it
really
a
design
of
the
status
report?
So
much
is
bringing
the
status
report
page
in
line
with
the
rest
of
the
administrative
theme.
So
it's
not
really
restructuring.
So
much
is
just
making
it
look
the
same
as
every.
A
Well,
there's
also
some
competition
about
like
whether
we
should
be
changing
the
sort
order
like
do.
We
put
the
it's
like
a
user
experience,
design
thing
so
more
than
like
a
beauty
design
thing
like
we're
not
trying
to
like
put
icons
on
the
PHP
version
like
drupal
8
did
but
trying
to
think
like
when
you
come
to
this
status
report.
C
C
D
Well,
I
didn't
I,
think
Jen
did
but
yeah,
so
basically,
I
apparently
know
that
view
7
and
views
8
and
views
and
ripple
some
of
using
Drupal
8,
maintain,
errs
well
and
so
I'm
going
to
try
and
redesign
each
of
them
all
kind
of
in
tandem.
As
my
next
big
thing
that
I
want
to
do
other
than
helping
out
with
backdrops
EMS
work.
So
I
just
talked
to
the
views.
8
views
in
Drupal,
8
guy
and
we'll
be
meeting
with
him.
D
A
D
A
Talked
about
it
yeah,
but
then
his
issue,
he
just
he
actually
liked
filed
a
poor
request.
It's
just
like
removed
borders
like
it's
pretty
straightforward,
but
I
would
encourage
us
if
you're
like
whoa
I'm,
about
to
do
this
also
like,
if
there's
anything
in
there,
that's
not
in
line
with
what
you
would
do.
We
maybe
shouldn't
do
it,
but
it
does
look
super
minor
and
so
me,
maybe
not
as
unrealistic
as
it
sounds
this
first
one.
C
So
yeah,
okay
boy,
that's
a
new
one
to
look
at,
but
I
guess
so
awesome.
It
looks
like
we're.
Gonna
have
some
refreshed
attention
on
that
issue
that
issues
been
around
for
quite
a
while.
So
what
up
great
yeah
yeah?
If
it
happens
it
happens.
That
would
be
great
I'm,
not
really
sure
that
this
is
a
real
high
priority
thing
for
1.7,
but
awesome
yeah
I'd
like
to
see
a
shoot
or
progress
on
any
1.7
issue
or
any
issue
really
stead
up
awesome.
C
Let's
see
a
couple
of
items
that
we
talked
about,
that's
been
brought
up
pretty
much
since
the
1.6
release
are
two
issues
related
to
layouts.
Actually,
I
guess
not
three
issues
related
to
layouts.
One
of
them
is
1704,
which
is
making
all
page
elements
into
blocks.
I
saw
Lauren
did
a
review
of
that
one
testing
it
out
and
saying
that
it
worked
well
for
the
most
part,
but
occasionally
resulted
in
the
view
or
the
layout
on
saving
correctly.
C
Let
see
that
was
1704,
so
that
also
could
use
more
eyes
and
looks
like
we
need
to
reroll
in
a
pull
request
layout
relationships,
it's
issue,
21,
34,
I.
Don't
think
those
are
the
updates
since
last
week
on
that
one
and
then
port
views
layout
pane
displays
this
makes
it
so
that
blocks
views
that
are
configured
to
display
as
blocks
have
settings
available
when
you
place
them
in
a
layouts
and
that's
issued
2433.
That
issue
is
in
the
needs.
C
Work
states-
probably
not
functional
at
this
point,
but
it
kind
of
makes
the
lays
the
groundwork
for
implementing
that.
We've
only
got
three
weeks
to
go
before
code
freeze
for
1.7,
so
we've
got
some
work
to
put
in
to
move
these
issues
forward.
There's
a
bunch
of
other
items
that
are
tracked.
1.7
are
tagged
for
1.7
as
well
that
we
don't
bring
up
in
a
meeting,
but
it
would
be
nice
to
get
into
1.7
nonetheless,
and
you
can
find
those
in
the
github
issue
tracker
under
the
1.7
point:
Oh
milestone.
C
A
It
so
it
looks
like
we
skipped
over
the
localisation
server
so
fast
we
miss
Olaf's
update.
So
if
you
want
to
jump
in
now
and
tell
us
what's
going
on
it,
I
be
great
yeah.
E
Last
week
tough
wrote
a
little
script
to
get
all
the
language
files
from
Drupal
and
it's
very
nice,
so
I
can
get
automatically
get
all
the
files
also
for
modules
like
views
from
terminal.
So
when
we
made
some
progress
there
and
today,
as
I,
can
go
login
again
to
the
translation
said:
I
wanted
to
country
continue
my
work
and
but
I
got
blocked
again
from
another
issue
and
I
think
that's
quite
critically
at
the
moment,
because
I
can't
continue
and
it
has
to
do
with.
E
A
B
E
C
E
C
So
it
sounds
like
step
one.
We
don't
even
have
that
much
reported
to
backdrop,
so
it
sounds
like
step
one
is
we
need
to
port
that
module
the
p.o
TX
module,
which
is
4p
OT?
That's
the
translation,
template
file
in
X's
exports
over
Phoenix,
and
so
once
that
module
is
available,
then
we
could
at
least
manually
like
have
a
backdrop,
release
and
then
export
the
template
and
then
upload
that
to
the
translation,
server
and
the
longer
term.
We
could
automate
that
so
that
on
every
release
it
would
automatically
export
an
update.
C
It's
not
a
terrible
amount
of
labor,
though,
to
just
it
stopped
to
have
a
backdrop,
installation
and
use
the
p.o
TX
module
to
do
the
exporting.
You
know
it
basically
a
summary
of
what
that
module
actually
does
for
those
centres
and
where
is
it
it
actually
literally
parses
the
code
base
and
finds
all
T
strings.
All
the
functions
that
have
the
calls
to
the
T
function
as
well
as
places
that
are
slightly
ambiguous.
E
A
E
C
It
looks
like
well.
C
It
probably
is
not
difficult
like
is
it
usually
with
the
in
the
world
of
backdrop,
the
more
specialized
and
cussed
like
custom.
A
module
is
kind
of
the
easier
it
is
to
port,
because
the
like
more
specialist,
it
is
it's,
it
doesn't
have
as
many
integrations
with
other
parts
of
the
system.
So
you
end
up
port
of
less
because
the
specialized
parts
don't
have
to
change
at
all.
C
C
C
C
And
we
have
to
say
thank
you
again
Oliver.
You
can
sit
continued
persistence
on
working
on
this
translation
server.
This
is
like
a
it's
huge
like
is.
It
would
be
absolutely
fantastically
huge
to
have
translations
available
for
backdrop
core
and
for
four
modules.
So
this
is
a
really
really
critical
effort
that
I'm
really
happy
to
have
you
taking
the
lead
on
wickham.
A
Okay,
we
are
going
to
try
I,
think
this
shortened
meeting
format
again
next
week.
So
if
you
have
updates,
let
us
know
when
we
start
the
meetings.
We
can
get
them
written
into
the
agenda,
so
we
don't
actually
accidentally
skip
areia
and
then
yeah
or
if
you
have
edit
access
to
the
google
doc,
you
can
drop
them
in
it
anytime,
you're
working
on
stuff
today,
alright!
A
Well
thanks
everybody
for
joining,
we
will
run
off
to
the
issue
queue
and
trying
to
tear
the
things
that
needed
to
be
taken
care
of
come
in
will
see
it
won't
online.
Alright,.