►
From YouTube: Backdrop Weekly - June 13th
Description
Today’s development agenda: http://bit.ly/2EQeU7q
A
All
right
we
are
on
air
today
is
Thursday
June
13th.
Today
this
is
a
meeting
to
check
in
on
active
development
tasks,
rector
of
CMS
first
announcement.
We
have
two
new
contributed
projects.
This
week,
the
metod
menu
editor
module
and
the
X
autoload
module.
So
thank
you.
Everybody
who's
been
working
on
those
one
update
on
backdrop,
CMS
two
org,
our
homepage
demo
button
is
up
so
I'm,
not
sure.
B
Yeah,
this
is
great.
Let's
see
we
didn't
have
a
meeting
last
week
is
that
is
that
right
that
was
princess
triple
K?
Is
it
backed
up
minicamp
the
backdrop
minicamp?
Yes,
that's
right.
Let's
see
you
probably
covered
that
in
the
outreach
meeting
previously
all
right.
There
wasn't
anybody
there,
except.
B
A
A
B
A
Let's
see
last
Thursday,
which
is
the
day
before
Twin
Cities
triple
camp,
we
had
a
mini
camp
specifically
for
back
trap.
I
think
there
were
thirteen
people
who
were
signed
up
for
it.
Two
people
or
people,
five
people
traveled
from
out
of
state
I,
don't
know
a
pretty
significant
number,
which
is
good
unlike
two
well,
actually,
if
you
count
us
and
then
West
I,
don't
know
it
sure
there
was
a
handful
of
people,
which
is
great.
We
had
a
bunch
of
different
presenters,
so
we
had
someone
present
on
upgrades.
A
Had
West
come
in
and
do
some
themeing
for
basis
just
kind
of
a
bunch
of
little
sessions,
which
is
pretty
good.
Most
of
it,
we
tried
to
do
live
streams,
for
so
some
of
you
might
have
been
aware
and
watching
this
we
did
that
if
you
didn't
get
chance
to
see
the
live
streams
and
still
want
to
see
the
videos
they
are
also
posted
on
our
YouTube
channel.
So
you
can
check
those
out.
A
There
were
a
couple
of
things
that
were
more
discussion,
oriented
and
not
so
suitable
for
the
live
stream,
video
format
and
for
some
of
those
we
got
Kevon
to
do
a
recording
on-site,
so
we'll
eventually
have
videos
for
those,
but
some
of
them
just
weren't,
really
suitable
for
videos
at
all.
So
there's
a
couple
of
things
that,
from
the
day
that
didn't
get
recorded,
but
most.
A
Hopefully,
that'll
be
good,
I
think
it
went
pretty
well,
it
felt
a
little
bit
like
a
summit,
except
for
that
we
had
maybe
a
few
more
speakers
than
a
summit
normally
has
most
of
people
who
were
there
got
a
lot
out
of
it.
A
couple
of
them
had
previously
attended
our
trainings
either
in
Chicago
or
Florida,
and
so
it
was
good
to
have
them
come
back
and
still
be
interested
in
backdrop.
A
Then
we
had
a
couple
of
local
people
talking
about
what
they
were
doing
with
it
and
a
couple
of
new
people
who
are
excited
about
what
they
could
do
with
it.
We
also
had
a
couple
of
people
reach
out
right
before
the
camp
saying
that
they
really
wanted
to
come,
but
they
couldn't
because
of
travel
or
timing.
So
I
think
it's
also
telling
that
there
are,
but
there
is
more
interest
than
what
we
actually
saw
at
the
camp,
and
it
was
just
you
know,
logistically
hard
to
make
one
particular
weekend.
A
So
I
think
that
was
good
and
I
think
we
should
shoot
to
try
and
do
more
many
camps,
we're
gonna,
try
and
be
when
a
bad
camp.
This
fall,
I'm,
not
sure
they've
got
their
summit,
training
Day
things
sorted
out
yet,
but
we
will
be
in
touch
with
them
about
that
too.
So
yeah
I
liked
it
no
no
need.
If
there's
anything,
you
wanted
to
add
yeah.
B
I'm,
just
like
one
thing
about
the
summit
and
that's
that
there's
I
about
the
minicamp
terminology
like
a
couple
years
ago
when
we
did
back
to
our
presentations
or
other
small
gatherings,
even
like
the
summit's
that
we've
done
at
bat
camp.
But
it's
a
lot
of
you
know
us
presenting
and
like
people
receiving
like.
Oh
I
wanna
hear
about
backdrop,
and
this
is
the
first
time
when
we
went
around
the
room
and
everybody
introduced
themselves.
B
It
was
the
first
time
that
we'd
had
this
like
really
everybody
coming
together
and
talking
to
each
other
and
not
so
much
like
us
presenting
to
them
so
I
found
it
to
be
really
wonderful.
You
know
that
was
great
yay
shot
to
him
for
making
that
happen,
because
he
really
I
mean
not
only
did
he
run
the
Twin
Cities
Drupal
camp
he
saw
so
I
took
on
this
mini
camp
idea
and
made
that
happen
so
yay.
Thank
you,
Tim.
B
Okay,
let's
talk
about
backdrop,
so
I'm
not
sure
if
it.
This
is
really
super
news,
not
because
it
seems
like
it
happened
so
long
ago,
but
one
13.2
was
released,
which
included
a
fix
that
made
it
so
that
backdrop
could
self
update?
Isn't
that
right,
like
we
had
an
issue
that
backdrop
when
updates
came
out,
it
couldn't
actually
update
core
because
the
missing
got
info
file.
B
B
A
It
might
be
worth
by
revisiting
our
policy
on
this
because,
in
terms
of
like
taking
care
of
users,
it's
definitely
better
to
have
a
fix
in
than
to
have
a
bug
that
we
know
it's
a
bug
that
we
just
don't
care
enough
to
fix
because
of
like
policy
issues.
I
understand
like
from
a
developer
standpoint
like
it
would
be
ideal
to
get
it
in
with
a
fix,
but
I
still
just
I.
Just
don't
feel
like
it's
better
to
have.
A
Software
we
know
is
broken
when
we
have
a
fix
waiting
for
it
and
I,
don't
know
how
we
would
then
enforce
the
creating
of
the
test
if
it
wasn't
tied
up
in
like
hurting
people
at
the
same
time,
but
I
feel
like
there's
gotta
be
some
way
to
do
this
and
it
might
be
worth
looking
at
like
what
other
software
projects
do
to
see.
If
there
is
some
kind
of
process
that
would
make
it
so
that
we
could
help
people
and
still
get
our
tests
in
and
then
maybe
not
the
same
time.
B
B
Let's
see,
they
also
are
a
lot
of
other
issues
in
1-3.
1343,
open
issues
that
are
of
various
priorities
are
the
items
that
we
consider
to
be
high.
Priority
I've
been
falling
behind
on
my
code,
reviewing,
though
it
looks
like
there's,
a
six
or
more
are
TBC
issues,
several
of
which
are
in
the
113
three
milestone,
and
then
there's
even
more
PR
works
for
me
tags,
which
are
kind
of
the
less
confidence
version
of
this
looks
like
it's
ready,
so
there's
a
bunch
of
things
that
need
to
be
caught
up
there.
B
I'll
do
my
best
to
get
through
them.
See
Jeff
is
here.
If
I
wait,
we
can
collaborate
as
well
to
get
as
many
of
these
things
through
I
know,
herb
also
likes
to
just
mark
things.
Ready
to
be
committed
did
not
actually
merge
them,
but
I'm,
not
sure
if
it
needs
to
be
said,
but,
like
you
know,
we
have
to
we
trust
each
other.
Like
everybody,
everybody
has
the
power,
or
at
least
sorry
all
of
our
commanders
stuff,
how
this
power-
and
it
doesn't
sometimes
we
fall
into
the
habit
of
just
like
oh
I'll.
A
B
Yeah,
we
don't
have
quite
the
capacity
to
guarantee,
like
multiple
reviews
at
this
point,
so
sometimes
like
I'll
move
stuff
from
I'll
go
through
the
needs
to
review
queue
and
actually
be
committing
that
of
that
as
well
and
I.
Think
for
the
time
being
that
that
level
of
directness
is
is
good
enough.
Why
couldn't
yeah
we.
B
B
Okay,
so
anyway,
one
thirteen
three
we've
got
some
things
to
catch
up
on.
There's
lots
of
great
stuff
that
is,
is
being
fixed
all
the
time,
one
in
1400,
as
for
113
threes
release
date,
we
don't
actually
have
very
many
changes
and
there
yet
so
we
don't
have
any
immediate
plans
for
when
the
next
bug-fix
release
will
be
coming
out,
that'll
be
on
it
as
is
needed
basis
or
once
enough
fixes
accrue
to
make
a
release
worthwhile
next
up,
114
dot
o
will
be
the
next
minor
bug
fix
release
that
will
be
coming
out.
B
C
B
The
first
time
I
know
that's
like
I
mean
I'm,
not
what
we
should
always
be
striving
for,
but
I
I
find
that,
like
it's
just
really
great
this
stuff
that
he's
put
together,
and
so
we
we've
been
making
some
progress
in
improving
project
module
because
we
have
to
fix
project
module,
which
is
on
bankruptcy,
most
org,
as
well
as
making
backdrop
itself
utilize.
The
changes
in
project
contra,
so
project
module
is
where
the
changes
are
happening.
Initially,
I
posted
a
general
gain
plan
into
that
package.
Signing
issue
which
is
1992
of
the
related
issues.
B
And
I
didn't
actually
post
a
comment
I'm
looking
at
and
I'm
like
where's
my
comment
anyway,
maybe
I
haven't
finished
it.
Yet
we
have
a
general
plan
that
will
improve
project
module
and
put
code
sign
the
mantra
he
wants
to
put
directly
into
court
put
code
sign
as
a
standalone
module
on
backdrop,
CMS
org.
B
First,
so
that
backdrop
CMS
org
can
start
signing
packages
and
generating
XML
feeds
that
are
signed,
and
that
will
make
it
so
that
the
testing
of
the
module
in
court
and
on
people's
locals
will
be
a
lot
easier
because
they
love
actual
data
to
work
with
for
actual
signed
packages.
Coming
from
backdrop,
CMS
stuff
work,
so
most
of
the
activity
is
actually
happening
in
project
module
right
now
with
the
objective.
Getting
that
onto
backdrop,
CMS
tough
work
and
then
will
continue
like
working
on
getting
the
functionality
into
court
itself.
B
A
So
I
have
a
core
quests
that
was
created
by
dr.
Elmont,
that
I
have
recently
rebased
I'm,
currently
working
through
some
of
the
weird
usability
issues
with
file
displaying
where
there's
like
a
file
display
mode
and
a
file
entity
display
mode
and
I'm.
Trying
to
merge
the
configurations
for
the
file
display
into
like
a
little
configure
like
a
cogwheel
boxy
thing
that
you
see
on
like
fields
configuration
settings
so
that
it
doesn't
have
to
be
an
entirely
separate
app.
So,
hopefully,
I'll
have
a
new
version
of
that
for
review.
Before
next
week's
meeting.
B
B
Trusted
knows
patterns
is
a
simple
cross
port
from
from
Drupal
to
make
it
so
that
the
site
domain
names
need
to
be
specifically
whitelisted
or
you
have
the
option
of
specifically
white
listing
it
that
a
status
this
one
is
that
it
needs
code,
review
and
testing.
The
cross
report
has
been
completed.
I
think,
there's
probably
still
a
little
bit
of
discussion
around
how
serious
or
how
firm
the
restriction
should
be.
We're
not
getting
rid.
B
D
A
A
B
Yeah
I
think
the
current
status
is
that
the
status
report
will
show
you
a
warning
saying
that
you
could
set
up
trusted
host
patterns,
if
you
don't
have
it
set
up
and
that
that's
kind
of
an
interesting
question
about
like
a
warning
is
something
that
doesn't
create
the
red
dot.
So
it
won't
show
up
as
like
an
error
in
the
overall
function.
Obviously,
but
it's
also
something
that
people
will
try
to
get
resolved
so
I,
don't
know.
B
A
It's
also
like
letting
them
know
about
a
new
feature
that
wasn't
there
before,
and
so
if
they
did
want
to
result,
but
they'd
be
like.
Oh,
hey,
I
have
this
thing
now
and
they
could
so
I.
Think
like
the
fact
that
it's
not
gonna
nag
them
with
the
red
dot
is
fine.
I
have
a
handful
of
sites
that
I'll
have
like
warning,
so
they
just
look
at
every
time.
You
go.
That's
fine.
I'm
gonna
ignore
those
yeah.
A
D
B
B
B
B
A
B
B
A
This
is
so
exciting,
okay,
so
in
panels
there
was
this.
Can
this
layout
that
was
called
flexible
layout
that
everybody
hated,
because
it
ended
up
building
this
layout
with
tables
where
you
added
rows
and
columns,
but
now
that
we
have
the
butcher
grid
system,
adding
rows
and
columns,
pre
creates
less
ugly
output,
and
so
documents
been
he's
had
this
contribute
for
a
while
that
allows
you
to
do
a
flexible
layout
and
I
was
working
on
refactoring
it
a
little
bit
to
fit
in
with
the
rest
of
core.
A
So
right
now
our
only
settings
form
our
only
question
on
the
settings.
Farmers
like
which
layouts
are
enabled
or
disabled,
and
so
that's
been
converted
into
a
table
where
every
layout
has
enable/disable
status
and
then
once
those
are
enabled
they
on
my
cleave
here
in
your
layout
selection
thing
and
then
all
the
ones
that
are
configured
will
have
I
have
a
configure
link
as
well,
where
you
can
go
and
you
can
add
rows
or
regions
at
any
given
part
of
it.
So
it's
coming
along
really
nicely.
A
Yeah
there's
a
meta
issue
at
the
top
of
the
issue.
If
you're
curious
about
what
it
is,
there's
a
bunch
of
things
that
are
kind
of
blockers
and
then
there's
a
bunch
of
things
that
are
nice
to
have,
but
we
could
go
in
or
not
and
then
there's
a
couple
things
we're
still
discussing
so
I
think
like
trying
to
figure
out
the
URLs
for
the
pages
is
still
under
discussion
and
then
figuring
out
how
to
add
rows.
It's
gonna
be
hard.
So
just
talk
about
it
so
yeah,
it's
just
you
wanted
somewhere.
B
B
B
You
say
I
would
like
to
be
an
advocate
for
this
issue
and
then
edit
the
summary
up
at
the
top
and
say
that
you
are
its
advocate
and
then
I
think
the
process
for
removing
things
into
the
current
master,
and
you
also
say
and
I
would
like
to
request
this-
be
the
next
minor
version
and
add
the
tag
master
candidate,
minor
and
I
have
someone
else
agrees.
Then
it
gets
prioritized
in
thanks
release.
Yeah.
A
B
C
This
has
other
advantages,
for
example,
if
one
day
we
want
to
have
a
code,
sniffer
package
or
a
coder,
or
anything
like
that,
it
could
be
inside
that
composer
file
as
well
and
automatically
check
the
the
code
syntax
that
gets
in
so
I,
don't
know.
What's
your
point
of
view
guys,
but
for
me
this
is
a
mandatory
step.
B
So
I
know
that,
first
of
all
that
Jeff
has
had
some
thoughts
on
this
as
well.
It's
too
badly.
He
hopped
out
answer
I,
know
that
I
think
you
you're
phrasing
that
correctly,
that
we
don't
want
to
have
a
build
process
as
part
of
backdrop
or
its
dependencies
will
run
down
the
same
kind
of
rabbit
hole
that
Drupal
has
gone
down
once
we
start
going
down
that
path,
but
you're
also
making
the
point
rightly
that.
A
I,
don't
really
see
a
downside
to
letting
or
beyond
packages.
I
think
that
the
only
thing
I
really
see
are
upsides,
for
that
I
mean
all
the
reasons
the
full
mentions,
but
also
there's
like
increased
visibility.
If
it's
like
that
on
packages,
I
just
think
I,
don't
know
my
my
concern
was
mainly
around
including
a
file
and
all
trim
projects
and
making
them
tied
a
core
that
I
wanted
to
avoid.
I.
C
Mean
yeah
the
great
I
posted
a
link
on
the
hangout
chat.
If
you
do
you
mind
having
a
look
at
it,
it
has
a
composer
file
inside
and
this
is
how
I
I'm
installing
backdrop
using
composer
right
now.
As
backdrop
is
not
available
on
packages,
I
have
to
fiddle
in
the
composer
fied
and
it
would
be.
It
would
be
so
much
easier
if
we
could
just
have
backdrop
listed
on
packages,
so
we
could
have
a
kind
of
automatized
build
somewhere
using
docker
or
anywhere
else.
C
I
think
it
think
it's
a
good
IDE
and
we
could
start
with
just
a
simple
composer
file
with
nothing
in
it,
ins
with
nothing
it
or
the
bare
minimum,
and
then
we
could
maybe
extend
it
at
wheelman
depending
on
what
we
want
to
do
with
it.
So
I
don't
think
it's
a
it's.
A
huge
deal
to
include
such
a
file
if
it
contains
just
a
name
and
a
description,
and
that's
it
so
up
to
you
I
think.
A
That's
a
reasonable
starting
point:
is
there
an
issue
on
but
in
the
backdrop
queue
already
for
just
adding
the
composer
file,
so
it
might
be
good
to
create
one
and
schedule
it
for
something
like
114
and
let
everybody
talk
about
in
that
issue
between
now
and
then
and
if
there's
no,
you
know
resistance
to
it.
We
put
it
in
that
day
and
that
way
like
we
can
see
what
more
people
think
like
I'd
like
to
have
Jeff.
Add
his
feedback
on
that
too.
A
B
B
B
Yeah,
it's
not
a
very
big
change
that
the
when
we
package
any
release,
whether
it's
captured
module
or
core
module.
It
runs
the
packager
and
it
modifies
to
dot
info
files
to
actually
include
the
version
number
of
something
actually
fork
or
not
sure
that
that's
necessary
because
it
uses
the
backdrop
version,
constant
soul.
A
B
The
long-term
I
mean
the
goal
that
were
working
on
right
now,
with
adding
digital
signing
for
automatic
updates.
That
is
something
that
the
packager
has
to
do
like
the
package
gets
validated
and
signed
by
backdrop,
CMS,
dot,
org
and
then
included
in
the
package
archive
course.
Composer
wouldn't
know
how
to
validate
signed
packages
by
itself.
So
we'd
also
need
to
teach
you
how
to
do
that
at
some
point.