►
From YouTube: Backdrop CMS weekly call 4/10
Description
Backdrop CMS
A
A
As
long
as
those
last
two
things
can
be
done
without
changing
very
many
aps,
propping
release
backdrop
sometime
this
summer
and
that's
the
first
release,
but
we
will
then
continue
to
have
iterative
releases
a
reporter
or
we
can
add
new
features
until
the
next
major
version.
So
those
will
be
new
features
that,
of
course,
don't
require
any
API
change.
Since
last
week,
I
went
through
seven
thousand
issues
or
seven
thousand
commits
that
were
made
to
Drupal
8.
A
Since
the
day
we
forked
between
then
and
last
week
and
I
tried
to
organize
them
in
some
way
that
made
some
sense.
I
removed
things
that
were
conversions
that
we
didn't
want.
I
removed
things
are
related
to
modules
that
we've
removed
from
backdrop.
I
separated
out
CSS,
JavaScript
and
cmi
issues
into
their
own
issues,
so
that
people
could
kind
of
tackle
those
separately.
There's
a
whole
bunch
of
conversions
that
are
like
changing
CSS
identifiers
or
changing
the
way
that
we
target
things
in
JavaScript.
A
So
this
is
for
things
like
converting
subsystems.
We
need
to
convert
the
subsystems.
We
can't
use
the
same
patch,
but
we
need
to
solve
the
same
problem.
So
those
are
also
pulled
out
into
a
separate
meta
issue
which
we
can
review
decide
which
ones
we
need
which
ones
be
down
and
then
also
work
on
in
the
same
way,
I
think
it's
going
to
be
good
to
refer
to
the
Drupal
that
work
issue
to
figure
out
how
to
solve
the
problem.
A
Even
if
we
can't
use
the
same
code
that
they
arrived
at
so
Drupal
8,
meta
issues,
1
2,
3,
&,
4
are
hopefully
updated.
Not
all
of
them
will
apply
as
easily
as
Drupal
7
patches,
but
there
are
a
bunch
of
really
good
minor
changes
in
there.
That
I
think
we
should
just
move
forward
with.
One
thing
to
keep
in
mind
is
that
some
of
the
issues
in
those
Drupal
8
issues
are
the
patches
in
this
report.
A
Issues
we've
already
merged
in
from
the
Drupal
7
equivalent
fix,
so
I
would
check
as
you're
going
through
the
issue
queue
check.
The
issue
see
if
there
was
a
Drupal
8
version
that
would
urge
upon
7
version
that
was
committed
and
if
there
was,
if
we
probably
already
have
that
change.
So
we
don't
need
to
include
that
one.
So
I
removed
as
many
as
I
found
last
week
when
I
was
working
on
the
Drupal
7
metas,
but
there
might
be
some
that
predate
that
that
are
so
in
both
lists.
A
That's
one
thing
to
know
so:
Drupal
8
lists
already
ish
I'm
a
lot
more
ready
than
they
were
in
the
last
few
weeks,
which
is
good,
and
this
is
there's
250
issues
roughly
on
each
one
of
these.
We
have
7,000.
So
obviously
not
all
dishes
are
created,
but
I
figured
the
farther
I
or
the
question
to
present.
We
get
the
less
likely.
Those
patches
are
going
to
be
to
apply
anyway.
A
So
I
figure
we'll
start
with
these
four
and
then
we
can
kind
of
pick
and
choose
out
of
the
remaining
4,000
to
use
which
ones
we
actually
want,
or
the
remaining
five
thousand
devil
in
your
left
and
make
sure
that
we
get
this
taken
care
of
also
but
didn't
want
to
put
them
all
up
there,
we're
not
going
to
be
doing
them
all
alright,
drupal
7
cross
sports.
We
have
one
full
request
left
on
Drupal
7
s
meta
to
number
134,
which
I
think
is
ready
to
be
merged.
A
It
just
needs
a
little
review
from
Nate
to
make
sure
that
there's
anything
funky
going
on
in
there
like
adding
tests
twice,
apparently
I'm
habit
of
doing
and
then
beyond
that.
All
that's
left
for
today
is
my
plan
for
taste
to
get
that
last.
Drupal
7
meta
done.
It's
mostly
done
anyway,
because
of
the
most
of
the
work
that
Andy
did
on
it,
but
closing
out
those
previous
2
is
great,
and
now
we
can
focus
on
the
drooooid
stuff,
which
is
good
and
there's
also
I.
A
B
B
A
B
I
mean
there's
progress.
Rolling
along
I've
been
pushing
up
my
changes
as
as
I've
been
making
them.
We
have
more
configuration
pages
now,
so
you
can
do
things
like
you
can
edit
the
menu
permissions
and
we're
starting
on
getting
screens
for
editing
the
arguments
so
as
I'm
making
progress
and
pushing
them
up
into
my
branch.
So
if
you
look
at
that
issue
and
then
look
at
my
branch,
you
can
see
where
I'm
at
currently
you
can.
B
A
And
using
hoard
we
have
using
core.
We
are
working
on
all
the
conversion
issues
that
go
along
with
that.
We
still
need
some
help
with
those,
but
the
most
part
you
can
have
using
forum
backdrop,
which
is
great
and
same
with
config
management.
We've
got
cmi
in
there
are
things
that
need
conversions.
We've
got
comparable,
gerbil
issues,
we
won't
be
able
to
exactly
use
the
patches.
We
have
examples
of
how
it's
done
same
thing
with
views.
There's
examples
of
how
lots
of
these
things
are
already
converted
and
Drupal
8.
A
We
can
look
at
those
as
a
guide,
but
obviously
the
resulting
toad
won't
be
the
same
and
minor
projects.
We
also
have
a
bunch
of
user
experience
improvements.
I
created
a
bunch
of
issues
last
week
and
I
was
really
impressed
with
the
amount
of
feedback
we
got
in
the
queue
a
bunch
of
people
weighing
in
saying.
Yes,
no
I,
like
it
I,
don't
like
it,
which
I
think
is
good
I
doesn't
worry.
I,
wasn't
aware
that
I
would
create
an
issue,
and
there
would
be
that
much
conversation
around
it.
A
So
I
think
that's
great,
and
some
of
the
things
are
like
obvious
no-brainers
and
other
ones
are
things
that
we
probably
shouldn't
do
so
I
think
it's
good
to
have
that
kind
of
conversation
to
see
how
the
rest
of
the
community
feels
about
changing
names
of
things.
For
example.
It's
it's
obviously
a
bike,
shedded
issue
in
in
Drupal
very
frequently,
so
it's
good
to
have
our
same
little
conversation
over
here
in
backdrop
and
make
sure
that
we
are
going
to
change
the
name
of
something
we
have
a
good
reason
for
doing
it.
A
We
can
fit
it
all
actually
benefit
more
than
a
dull
hinder.
So
we've
got
a
couple
of
issues
there
that
are,
you
know
pending
conversation
in
really
long,
which
is
good
and
then
there's
a
bunch
of
little
tiny
improvements
that
you
know
that
patches
in
the
trip
with
you
for
forever
that
I've
gotten
in
I
think
it's
good
to
clean
this
up
in
back
Joe
theme
system
clean
up.
A
This
is
something
that
I've
gone
a
lot
of
feedback
on
in
the
last
few
weeks
with
people
who
wanted
to
work
on
it,
but
we
weren't
quite
ready,
because
we
wanted
to
wait
until
all
the
drupal
7
stuff
was
done,
but
now
that
we're
coming
to
the
end
of
all
the
drupal
7
cross
ports,
I
set
up
a
bunch
of
meta
issues
for
theme,
changes
that
we're
going
to
work
on
and
where
relevant
links
to
the
drupal.org
issue.
Where
we
did
the
same
thing.
A
But
at
some
point
we
should
kind
of
come
up
with
a
list
of
you
know
what
are
the
layouts
that
we
want
to
provide
in
core
and
then
have
a
sub
issue
of
people
creating
those
either
taking
them
from
panels.
Or
maybe
panels
is
so
bad.
You
don't
want
to
start
there.
You
want
to
write
different
minecraft
and
have
some
kind
of
a
fun
places
for
people
to
get
their
hands
dirty
on
on
mark
up
there
to
any
would
also
be
good
and
other
stuff
we're
working
on
the
backdrop.
A
A
We,
you
know
taking
down
the
manifesto,
we're
trying
to
turn
a
page
and
make
it
really
positive
and
we've
got
new
plans
for
the
website
in
the
future.
But
just
so
you
know
it's
there
now
I
think
that
would
be
kind
of
good
to
let
everybody
who's
interested
in
knowing
what
we're
doing,
let
them
know
we're
doing
and
then
the
API
site.
Last
week,
I
asked
nate
for
access
to
the
server
and
he
gave
it
to
me
and
then
I
forgot
that
he
gave
it
to
me.
A
A
We
haven't
done
any
work
on
that
or
really
thought
very
much
about
it
for
a
while.
If
you
have
someone
else
who
wants
to
own
that,
that
would
be
pretty
cool
and
we
are
working
on
a
github
service.
I
know
I've,
been
in
a
couple
of
other
people
been
thinking
about
that
for
a
while
all
how
to
get
it
going,
how
we
want
to
have
it
interact
with
our
projects,
all
that
stuff,
so
hopefully
we'll
get
that
done
pretty
soon
too.
A
Obviously,
we
have
much
work
to
do
on
the
drop
main
project,
but
once
we
get
done
with
that,
we
should
start
thinking
about
how
we
want
the
github
integration
controlled.
To
look
like
so
getting
that
service
setup
would
be
key
prints
every
Thursday.
After
this
meeting
we
have
a
little
sprint
and
IRC.
A
We
sit
down
and
we
hammer
on
issues,
and
we
talk
to
people
and
trying
as
much
done
as
we
possibly
can
we're
also
going
to
try
and
do
a
sprint
at
drupalcamp,
Mexico
they're,
not
sure
yet
that
they're
having
a
sprint
day,
but
if
they
are
we're
happy
to
work
with
whoever
on
it
and
will
force
be
there,
so
we
can
be
working
on
it.
Even
if
we're
not
officially
sprinting,
we
can
print
in
spirit
and
and
we're
definitely
going
to
do
a
sprint
at
a
Drupal
corn
camp.
This
summer
backdrop
is
sponsoring
this
print.
A
A
Since
his
decisions
made
particularly
about
backdrop
usually
from
his
issues
that
came
up
in
the
queue
were
escalated
pmc
for
a
decision.
This
would
be
where
we
would
announce
our
decision
and
then
put
that
back
into
the
issue
queue.
So
people
could
work
on
it.
We
don't
have
any
escalated
issues.
The
moment
we
don't
really
have
a
large
enough
PMC
the
moment
either.
We
did
want
to
add
that
to
the
agenda
so
that
one
thing
start
coming
up.
A
We
can
talk
about
the
minute
in
a
public
forum,
so
everyone
will
know
what
our
decisions
are
and
if
anyone
wants
to
bike
shed
us
in
real
time
they
can
join
the
meeting
and
do
so,
though
we
are
looking
to
at
getting
some
more
became
numbers.
We've
got
some
people
we
would
like
to
nominate,
but
we
need
to
make
sure
that
everyone's
on
board
before
we
get
that
going
so
keep
your
eye
there
in
the
future.
A
For
hopefully
more
interactivity
for
mackynzie
we've
got
a
bunch
of
stuff
going
on
this
summer,
a
whole
bunch
of
drupal
camps,
drupal
events,
HTML
events,
web
events.
These
are
groups
that
are
just
for
people
with
the
PHP.
People
are
talking
about
WordPress,
whatever
we're
just
going
to
be
trying
getting.
Our
word
out
because
backdrop
came
from
backdrop.
Is
for
the
Drupal
community?
That
is
obviously
where
we
are
starting
in
terms
of
our
audience,
but
that
is
not
where
we
are
ending
I.
A
Think
it's
really
important
that
backdrop
be
something
that
everyone
else
in
the
world
also
wants.
So
just
open
source
developers,
people
use
WordPress.
People
who
are
you
know
just
want
to
content
into
a
system.
That's
cheap
and
easy,
and
does
really
cool
stuff
as
we're
going
to
try
and
reach
out
to
all
of
those
groups
as
well,
so
hopefully
well
end
up.
Creating
a
little
community
of
our
own
and
drupal
won't
be
too
upset
about
it,
and
we've
got
article
coming
out
this
summer
in
Drupal
watchdog,
which
turns
out.
A
Writing
is
hard
working
on
it
for
a
while,
and
it's
it's
hard
to
say
what
you
mean
in
a
way:
that's
eloquent.
They
have
a
really
great
editorial
team.
That
was
like
feature
you
wanted
to
use.
This
word
like
no,
actually
those
not
the
word
I
want
to
use
sweet,
a
really
great
process
of
back
and
forth.
I
also
have
no
artistic
talent
whatsoever,
so
I
was
trying
to
like
figure
out
how
to
give
them.
A
Visuals
the
air
like
drawing
on
the
back
of
an
envelope
like
something
that
looks
like
this
I'm
gonna,
take
a
picture
of
it
with
a
camera.
That
email
is
that
really
can
your
artists
fix
this,
so
I'm
look
really
looking
forward
to
seeing
the
magic
that
they
can
work
with
our
ideas,
I
think
it'll
be
really
good.
I
think
the
article
itself
is
pretty
compelling
it
kind
of
sets
the
record
straight
in
terms
of
why
we're
doing
this.
A
It's
not
because
we're
angry
it's
because
we
love
Drupal
without
Drupal
7
in
particular,
and
we
want
to
make
it
easier
for
people
and
so
we're
just
starting
there
and
trying
to
take
a
step
down
which
I
think
will
be
good
new
features
easier
to
use
faster.
Hopefully,
people
will
be
able
to
see
that
the
upside
of
this,
rather
than
just
it
being
natural,
which
is
what
I
think
a
lot
of
people
have
seen
lately
so
I'm
really
excited
about
that,
and
we've
reached
the
end
of
our
agenda.
A
A
A
If
you're
coming
to
California,
you
can
go
to
the
html5
developer
conference
in
see
like
what
the
rest
of
the
world
is
doing
and
you
have
I
don't
know
we
could
do
some
kind
of
extended
sprint
in
between
and
then
we
could
have
like
that
bad
camp,
which
is
the
triple
comments
at
the
other
end,
that's
something
we
think
Morton
did
last
year
and
a
bunch
of
people
are
interested
in
in
both
of
those
events.
I
think
they're
both
really
well
done.
A
The
guy
who
runs
the
or
one
of
the
guys
who
runs
the
html5
developer
conference,
is
a
a
long
time
Drupal
person
and
nut
trees,
as
invoked
in
Drupal
anymore,
but
has
been,
and
and
they
get
a
ton
of
really
really
great
speakers
from
google
and
firefox
telling
you
about
like
what
web
browsers
are.
Thinking
about
doing
in
the
future,
which
is
really
fun,
but
also
from
a
whole
bunch
of
people
all
over
the
world.
We
were
like
look
at
this
cool
javascript
stain.
A
I
wrote
and
that's
where
angular
was
debuted
a
couple
of
years
ago.
So
it's
the
kind
of
thing
where
you
new
ideas
come
out
of
this
conference
and
it's
really
fun
to
kind
of
go
and
see
what
the
rest
of
the
world
is
doing.
That's
not
your
books.
If
you're,
like
a
lot
of
times,
we
get
stuck
in
in
Drupal
and
so
much.
We
forget
that
well
stuff
everywhere.
A
C
A
Bad
camp
we're
currently
working
on
trying
to
do
like
a
three
or
four
day
long
drupal
8
core
sprint,
and
that
would
be
at
bad
camp
itself,
but
we
could
do
something
backdrop
related
nearby,
if
not
in
the
same
venue,
so
we
can.
We
can
definitely
figure
out
how
to
make
that
happen.
We
don't
have
exact
dates
for
that
yet,
but
we'll
figure
it
out
or.
A
Thank
you
for
all
of
your
work
on
the
CSS
issues
and
yeah.
We've
totally
figured
out
the
pull
request.
Workflow
I,
just
kind
of
at
right,
where
we
are
right
now
like
as
much
as
you
guys
can
do,
is
good.
So
if
you
get
to
a
point,
we've
hit
an
issue
and
there's
some
problem
with
it.
Just
skip
it
and
move
on
to
the
next
Miss
goes
for
you
too,
and
I
know
you're
pretty
good
at
that.
A
Get
more
progress
on
faster,
so
yay,
okay!
Well,
if
there's
nothing
else,
I
have
a
goal
for
myself
to
start
on
that
last
issue.
Today,
I'm
not
sure
how
many
I'll
be
able
to
get
through,
hopefully
all
of
them,
but
we'll
see,
and
then
we'll
be
done
with
the
drupal
7
for
a
sport
until,
of
course
they
can
make
some
luck.
Mr.
A
Drupal
7
in
case
okay
and
probably
our
long-term
plan
for
staying
on
top
of
what
Drupal
is
doing,
and
we
should
talk
about
this
too,
but
I
think
our
long-term
plan
should
be
to
continue
to
include
all
the
improvements
that
go
into
drupal
7.
So
if
there's
bug
fixes
and
minor
documentation
improvements,
all
of
that
stuff,
we
just
keep
it
keep
going
with
a
Drupal
7
stuff
and
with
the
Drupal
8
stuff.
A
At
some
point,
we'll
just
stop
and
say
you
know
what
none
of
these
patches
are
going
to
work
for
us
anymore,
we're
not
going
to
say
on
top
of
the
patches
anymore.
Instead,
we'll
just
look
at
what
they're
actually
doing.
Instead,
a
you
know,
jubilate
decides
that
there's
a
problem
with
how
users
are
handled
and
they're
going
to
fix
it.
This
way,
we
should
think
about
that
problem.