►
From YouTube: Backdrop Weekly 12/12
Description
Backdrop Weekly 12/12
A
Recorded
you
can
go
ahead
and
turn
off
here,
video
all
right,
so
same
general
format.
As
last
week,
a
quick
introduction.
It
looks
like
people
who
are
on
this
call
today
is
my
self
gen,
Lampton
and
nate.
I
see
you're
here
we're
the
funding
for
cursive
backdrop.
It
also
looks
like
we've
got
andy
with
us
today,
which
is
great
thank
you
for
joining
us
again
and
we'll
just
kind
of
run
through
generally,
if
we
can
drop
these
goals
before
too
long,
because
I
think
people
are
starting
to
get
an
idea
of.
A
Why
we're
here
in
what
we're
doing,
but
we're
trying
to
create
a
a
content
management
system
that
has
comparable
features
to
Drupal
8,
but
an
architecture,
that's
more
similar
to
Drupal
7.
Ok,
we're
going
to
have
bug
fixes
that
we've
incorporated
from
Drupal
7
and
from
tripoli
and
any
other
ones
that
haven't
been
included
in
those
two
systems.
Yet,
as
well
as
if
it's
possible,
we
can
add
simul
occation
of
existing
systems
in
new
features,
but
only
when
it
doesn't
require
very
much
api
change
to
do
so.
A
A
Our
timeline
is
that
we're
going
to
try
and
relief
re-release
backdrop,
one
point:
oh
just
before
Drupal
8
comes
out
or
as
soon
as
possible,
but
we've
got
a
bunch
of
really
big
things
on
the
agenda
in
order
to
get
done
and
those
include
and
back
porting
all
of
the
patches
that
have
currently
gone
into
both
Drupal
7
and
Drupal
8
that
we
need
to
account.
For
so
not
every
patch
will
apply
to
backdrop.
A
As
am
I
using
core
and
ideally
we'll
get
a
blocks
and
layout
system
in
as
well,
if
we
can
get
those
three
things
wrapped
up,
we
can
release
those
are
no
small
task,
so
we've
definitely
got
to
get
cranking
on
those.
So,
in
terms
of
our
progress
last
week,
I
know
Michelle
had
created
a
ton
of
new
issues
on
github
for
all
of
the
patches
from
Drupal
7
that
needed
to
be
included
in
a
lot
of
stuff
from
Drew
Boyd
she's
got
documented
as
well
and
Andy.
B
B
I
was
looking
to
how
you
split
these
up
and
it's
good
to
know
that
their
by
day,
that's
that's
helpful,
because
I
was
wondering
how
they
were
actually
divided.
I'll
work
on
on
reviewing
these
as
soon
as
possible,
thanks
thanks.
So
much
for
getting
all
of
them
together
is
a
great
plan.
Just
go
through
get
all
the
easy
ones
narrow
down
the
list,
and
then
you
go
back
through
and
get
that
get
the
harder
ones.
A
B
Yeah,
so
there
isn't
any
significant
update
in
the
cmi
area.
The
only
real
remaining
task
that
needs
to
be
done.
Functionality
wise
is:
we
need
to
write
the
upgrade
path
for
image
module
and
for
system
module
to
convert
the
settings
that
used
to
be
variables
and
image
styles
into
into
cmi
files,
and
that's
the
only
functionality
piece.
That's
missing.
Victor
Kane
has
been
working
on
some
functionality.
B
Tests
basically
he's
going
through
and
checking
all
of
the
various
pieces
that,
like
just
manual
testing,
basically
and
he's
writing
them
all
up,
although
he
hasn't
submitted
them
to
the
issue.
Yet
writing
them
all
up
and
documenting
all
of
the
things
that
he's
testing
and
then
any
deficiencies
that
we
have
in
our
simple
test
coverage:
we're
going
to
make
sure
that
his
functionality
tests
are
covered
by
the
simple
tests,
but
it
sounds
like
so
far.
He
hasn't
actually
encountered
any
problems
he's
just
writing
it
all
up
all
of
the
areas
that
he's
testing.
That's.
A
Great
okay,
so
in
terms
of
conversion
you
mentioned
system
module
and
image
tiles.
Is
there
anything
else
in
core
that
needs
cmi,
stuff
that
the
men
that
doesn't
have
an
upgrade
path
like?
Do
we
have
a
I,
don't
know
I
thought
there
would
be
like
a
hundred
different
things
to
convert.
Do
we
have
a
plan
for
a
metaphor
that
it
is
that
something
just
gonna
take
on
as
well
yeah.
B
I
think
that
I
think
I'd
like
to
encourage
him
to,
but
I'm
not
sure
that
if
it's
actually
on
his
plate
or
not
but
yeah,
obviously
there's
there's
a
ton
of
things
that
can
be
converted.
You
know
I'm
the
most
obvious
ones
being
like
content
types
and
fields
and
then
then
his
views
comes
along.
That
alot
basically
be
there
too,
but
yeah
there's
tons
and
tons
of
things
you.
B
A
If
Victor
isn't
interested
in
kind
of
managing
all
of
the
moving
pieces,
for
that
way
should
make
me
find
someone
else
who
is
I
know
he
sold
probably
wants
to
be
kind
of
more
hands-on
but
yeah
just
so
that
we
can
kind
of
release
you
from
seeing
my
world
and
let
you
start
working
on
blocks
and
layout
stuff.
So
the
next
major
thing
that
we're
working
on
is
is
fusing
core
and
I
know.
A
Last
time
we
talked
about
it,
Matt
2000
had
picked
it
up
and
you
guys
were
talking
about
how
to
handle
an
equivalent
of
Drupal
8
plugins
in
backdrop
or
if
we
even
needed
to
if
I
didn't
know
if
that
had
gotten
result
or
if
you
had
started
working
on
other
parts
of
the
conversion
rather
than
that
I
don't
know
if,
if
that's
obviously
not
here
again
today,
I
don't
know.
If
neat,
you
know
more
about
where
that
stance.
B
Yeah
I
think
I'm
in
the
process
of
trying
to
convince
him
that
that
a
plug-in
system
isn't
needed,
I'm,
not
really
sure,
if
he's
conceded
to
that
or
not
yet,
it
seems
kind
of
like
he
initially
said
that
the
plug-in
system
/
autoloader
issue
was
a
was
a
blocker
force,
but
now
he's
kind
of
rescinded.
That
claim
so
I
think
I
think
that
worked
unblocked,
because
I
he's
decided
that
it's
not
actually
needed.
B
A
You
would
find
out
if
we
have
more
people
who
are
interested
in
helping
with
either
of
those
two
things.
So
if
we
have
someone
who
wants
to
work
on
busen
core,
it
sounds
like
Matt
could
probably
use
some
help
with
that,
since
he's
also
busy
with
the
API
website
or
if
we
have
someone
else
who
wants
to
do
work
on
the
API
website,
we
should
try
and
make
sure
that
we
don't
use
all
of
Matt's
time.
I
get
him
some
help
on
either.
One
idea.
A
The
next
thing
on
our
list
is
blocks
and
layouts.
We
don't
have
any
updates
on
that
yet,
but
we're
hoping
that
as
soon
as
TMI
gets
closer,
we'll
start
having
updates
on
that.
So
we're
going
to
leave
it
on
the
agenda
and
just
as
a
kind
of
a
encouragement
for
us
to
get
there
and
same
thing
with
in
theme
system.
Cleanup
I
haven't
gotten
any
actual
tickets
created
for
that,
yet
I
don't
think.
A
But
what
I
want
to
do
is
create
a
spreadsheet
much
like
the
one
we
did
for
Drupal
8
that
just
lists
all
the
stuff
that
we
need
to
either
convert
or
consolidate
or
remove.
I've
noticed
there's
not
a
lot
of
removal
of
stuff
already,
which
kind
of
effects
theme
functions
like
that
I,
don't
know
just
a
bunch
of
stuff,
so
I'd
like
to
kind
of
put
it
all
into
one
master,
spread:
cheeks
I
know
people
like
removing
stuff.
We
can
have
a
list
of
all
of
those
things.
A
There
might
be
a
whole
bunch
of
people
to
jump
in
to
help
out
with
that
too.
So
I'll
try
and
get
that
done
either
this
week
or
next
and
then
we'll
at
least
have
a
little
more
progress
there
as
well
and
in
terms
of
the
other
things
we're
working
on.
We
talked
a
little
bit
about
the
API
site,
which
sounds
like
maybe
Matt's
working
on
that,
but
we
could
probably
use
some
help
on
for
him
on
that
as
well,
but
we
also
need
our
own
primary
website
backdrop.
A
B
B
I
haven't
seen
any
actual
progress
yet,
but
yeah
there's
been
some
movement.
In
the
backdrop,
CMS
org
is
shook
you
for
anyone.
That's
interested
in
helping
it's
important
to
realize
that
in
the
github
brook
in
our
github
account,
there's
two
sets
of
issue
queues,
there's
one
for
backdrop
itself
and
then
there's
backdrop
CMS
org.
So
if
you're
interested
in
helping
on
backdrop,
CMS
org,
there's
a
separate
issue,
queue
for
that,
where
discussion
is
going
on
around
so
bring
up
things
like
like
this
API
website,
I
think
I
have
been
mentioning
something
about.
B
B
B
It's
clear
that
at
some
point
we're
going
to
have
a
centralized
repository
somewhere
that
update
module
can
check
with
the
update
status.
Module
can
check
with,
but
project
module
comes
with
a
PHP
script
that
generates
an
XML
file.
That
is
that
can
return
like
the
current
version
and
the
stable
release
and
the
last
time
it
was
updated
of
individual
modules,
but
that
that's
bound
into
project
module.
B
Since
I
mean
we're
not
going
to
be
using
project
issue
cues,
we
don't
think,
but
we
could
still
end
up
using
project
module
or
variant
a
project
module,
that's
heavily
modified
towards
github
on
backdrop,
CMS
org,
so
setting
up
an
update
server
basically,
is
nothing
but
a
domain
that
points
at
the
PHP
script
that
comes
with
project
module.
So
all
of
setting
up
an
update
server
is
probably
hinged
upon
setting
up
our
primary
site
and
then
the
update
server
will
probably
be
nothing
but
a
hosts
entry
that
that
points
at
that
PHP
script.
B
A
A
All
right
and
then
obviously
in
the
same
thing
as
the
update
server,
we
need
to
register
backdrop
CMS's
an
official
github
service
so
that
anyone
who
creates
a
backdrop
CMS
module
on
github
can
list
that
and
then
we
can
figure
out
later
how
that's
going
to
integrate
with
our
primary
website
in
our
update
server
and
all
that
a
good
stuff
too
again.
That's
that
probably
isn't
a
lot
of
work,
but
it's
something
that
probably
most
drupal
developer
stand
a
lot
of
experience
with
that
looks
like
fun.
A
B
On
that
on
that
issue,
there's
a
vision
issue
about.
You
know
how
we
want
to
handle,
can't
rib
and
I'm,
not
even
sure,
I,
think
it's
in
the
CMS
org
or
backdrop
CMS
org
issue
key
rather
than
then
the
backdrop
is
uq
and
it's
indecisive
right
now,
at
least
in
the
issue-
queue
like
what
solution
we
want
to
pursue
like
if
we're
going
to
use
composure,
packages
or
github
hooks
or
anything
like
that
and
I
wrote
up
a
lengthy
response,
but
then
I
lost
it
somewhere
in
my
browser
tabs
before
I.
B
B
Think
that
that
were
drawn
to
using
github
exclusively
for
for
package
management
as
well
as
issue
management,
just
because
it
makes
a
consistent
user
experience
for
everybody
that
wants
to
participate
with
backdrop
or
any
of
our
contributed
modules
so
and
end
it
similar
to
drupal.org
in
terms
of
releasing
a
package
as
opposed
to
you
know.
If
we
switch
to
composer,
everybody
would
have
to
include
a
composer
dot,
JSON
file
and
all
of
their
packages,
and
then
they
would
also
need
to
go
and
submit
like
they
would
need
to
have
a
github
account,
a
backdrop.
B
Cms
organ
count
and
a
command
a
packages
toward
account
in
order
to
submit
a
module
and
I
mean
it's
already
bad.
If
we've
got
backdrop,
CMS,
org
and
and
github
that
things
are
split
between
them
and
package,
just
just
might
be
too
much
so
anyway,
so,
like
Jen,
said
initial
rollout
or
planning
on
just
doing
a
github
service.
So
if
anybody's
interested
in
doing
it's
probably
going
to
be
nodejs
because
that's
what
github
seems
to
be
their
their
preferred
API
and
that's
what
the
continuous
integration
server
is
already
running.
B
A
Like
twist
his
arm
or
anything,
but
just
some
teeth
likes
to
play
with
gab.
That
might
be
good,
okay,
a
place
to
dry.
Ok,
so
I
guess
that's
the
end
of
our
not
backdrop
CMS
project
but
backdrop
CMS
other
important
stuff.
We
need
list,
and
then
next
up
is
is
Prince
we're.
Obviously
it's
Thursday.
So
after
the
meeting
today,
you
know
both
being
IRC.
A
If
you
have
any
questions
about
anything,
you
can
jump
in
there
and,
if
you're
working
out
stuff-
and
you
want
people
to
work
with
today's
probably
get
date,
night
I'm-
actually
not
sure
how
much
backdrop
stuff
you're
going
to
be
able
to
do
today.
Do
you
have
time
to
work
on
stuffer?
Are
you
busy
yeah.
A
A
C
A
C
A
We
were
thinking
that
we
might
have
other
people
who
showed
up,
and
maybe
you
weren't
interested
in
working
on
core
but
wanted
to
build
us
a
website.
So
if
we
have
someone
new
who
comes
in
in
there,
you
know
really
interested
in
working
on
content
strategy
or
something
we
want
to
make
sure
that
they
knew
they
had
a
place
where
we
needed
their
help
as
well.
So
we've
got
those
on
the
list
as
well.
We
need
all
the
stuff,
oh
wherever
we
can
take
anyone's
help
would
be
really
useful.
A
B
B
So
that's
that's
great
to
get
those
up
to
date
and
then,
once
we
get
through
like
the
early
Drupal
8
back
parts,
once
things
start
diverging
significantly,
then
we're
going
to
take
another
look
at
that
rename
Drupal
to
backdrop
everywhere
throughout
the
code
issue
which
I
feel
like
is
important
for
the
long-term
sustainability
of
the
project
that
we
actually
call
ourselves.
Backdrop
everywhere,
like
in
the
code
and
in
on
the
front
end
for
consistency
and
for
the
longevity
of
the
project.
B
That's
really
important,
but
I
don't
want
to
lose
the
compatibility
that
we
have
currently,
at
least
with
with
all
these
patches,
so
getting
these
patches
solved
makes
it
so
that
we
can
rename
that
at
so
that
way
we
actually
identify
ourselves
with,
with
you
know,
an
actual
brand
consistently.
So
I
think
your
current
work
is
fantastic
and
anybody
else
that's
interested
in
doing
back.
Porting
stuff,
Andy
you're
rocking
the
d7
backports,
but
nobody
started
on
the
d8
ones.
So
anybody
that's
interested
that
would
be
a
great
place
to
help
so.
A
We
also
got
an
update
from
Michelle
via
IRC.
She
said
that
she
should
have
the
master
list
of
all
of
the
Drupal
8
issues
that
need
to
be
back
boarded
in
the
next
week
or
two.
So
if
she
is
she's
not
done
with
that
yeah,
we
do
have
some
done
already
and
she
said
she
should
have
the
rest
of
it
in
the
next
week
or
so
so.
That'll
probably
help
us
with
people
interested
in
fact
boarding
from
Tripoli
when
we
get
that
list
done.
B
Different
yeah
I
know
some
people
join
in
and
immediately.
The
first
thing
they
want
to
do
is
rename
like
they
can't
handle
it
like
OCD,
like
of
the
project
being
called
backdrop,
but
Drupal
functions
being
everywhere,
but
yeah
we
come
in.
We
need
to
hold
off
on
that
at
least
I.
We
get
those
back
ports
complete,
ok,.