►
From YouTube: Backdrop CMS Weekly Meeting 4/9/15
Description
Come join us for the weekly status meeting of Backdrop CMS! We get together every week to talk about the progress of the next release, infrastructure, and community.
A
A
It
is
Thursday
april
9th
I'm
happy
backdrop
day
of
the
week
as
usual.
Today
we're
going
to
talk
to
you
about
the
current
status,
the
backdrop
and
all
of
the
infrastructure
that
we
need
to
support
the
vector
of
CMS
project
as
well
to
start
same
update
from
the
pants
he
as
the
last
few
weeks
back
drop,
has
a
bunch
of
phpstorm
licenses
to
give
away
to
this
community
members.
A
You
go
through
the
process,
you
agree
to
our
Terms
and
Conditions,
and
then
we
can
get
you
added
to
the
page
of
contributors
and
that's
what
phpstorm
uses
to
determine
how
many
licenses
we
should
have.
So
if
you
want
a
license,
you
gotta
be
a
contributor
and
part
of
the
kid
group
which
is
I,
think
great
for
us
to
be
able
to
have
those
licenses
for
everyone.
A
A
Since
then,
but
I'm
super
excited
to
see
how
it's
going.
If
anyone
else
is
super
excited
to
work
with
josh
and
backdrop,
we've
got
a
good
starting
point.
Therefore,
for
getting
some
major
progress
done
on
that
too.
So
I'm
super
excited
about
that
other
stuff
that
we've
been
working
frantically
on
for
the
last
past
few
weeks.
Organism
working
frantically
on
is
update,
checking
for
backdrop,
which
involves
a
lot
of
different
pieces.
A
That
includes
version
string
information
just
like
drupal.org
does
we
need
to
have
all
of
that
information
stored
somewhere
that
the
update
server
can
check
and-
and
that
is
a
much
bigger
process
of
taking
what
github
usually
does
modifying
it,
for
backdrops
needs,
pulling
a
lot
of
that
information
aggregating
onto
our
primary
website
and
then
so
much
of
other
stuff.
We're
doing
with
that
information
like
building,
I
use
your
interface
with
people
can
five
modules
and
things,
and
all
of
this
stuff
is
tied
together
and
knee.
A
B
Last
week
we
had
projects
and
releases
functioning
and
create
able
as
content
types
and
nodes
on
on
any
site
that
has
project
module,
installed,
project
modules,
just
in
the
github
contribs
group,
there's
just
a
project
called
project
and
includes
a
bunch
of
modules,
including
project
project
relief,
project
usage
and
the
new
module
since
last
week
is
the
project
github
module
which
integrates
to
train
project
and
or
which
integrates
during
your
back
job
site
and
get
up
which
is
pretty
sweet.
It
currently
does
things
like.
B
B
The
parts
that
are
missing
is
that
when
a
new
project
is
created
within
the
backdrop
contribute
it
should
automatically
create
a
project
node
on
back
to
FCMs
org.
So
I
haven't
gotten
that
part
of
project
module
built
out
quite
yet
and
more
importantly,
the
scripts
are
generating
the
xml
/
project
like
project
updates,
isn't
completed
yet
so
that's
probably
the
big
thing
and
that
will
ultimately
make
our
updates
over
function.
B
So
lots
of
lots
and
lots
of
progress
there
I
expect
been
saying
this
for
last
week
that
a
couple
weeks
and
then
we'll
probably
have
something
that
will
actually
be
up
on
backed
up
CMS
touareg,
instead
of
instead
assistant
project
module,
we're
meeting
with
Darius.
This
kind
of
in
the
later
part
of
the
meeting
two
remaining
with
there
is
later
today
talk
about
design
from
back
top
CMS
org
itself,
so
that
we
can
actually
see
how
these
project
pages
should
actually
look
on
backed
up
CMS
torgue's
right
now.
B
A
Think
that
we're
trying
to
look
at
all
of
the
good
things
the
drupal.org
does
and
take
all
of
the
stuff
they
do
successfully
and
then
we're
going
to
try
and
also
look
at
some
other
projects
like
wordpress
and
other
places
that
list
plugins
and
try
and
figure
out
how
to
search
how
to
searching
work
really
well.
And
how
can
we
do
that
on
our
site
too?
A
That's
also
really
helpful,
so
I
think
that
will
get
a
chance
to
look
at
these
new
designs
today,
which
will
be
fantastic
and
we'll
be
able
to
start
building
that
out
and
I
think
that,
even
if
we
get
I
interface
for
searching
done
before
we
get
our
updates
overdone,
that's
still
going
to
be
a
huge
ones.
I
feel
like
that's
kind
of
a
huge
hole
in
terms
of
what
we
provide
our
community
today,
so
hopefully
we'll
be
able
to
learn
from
everything.
A
A
Cms
org
is
running
back
track
and
I
know
that
there's
a
bunch
of
other
people
who
are
working
on
websites,
because
we've
got
a
bunch
of
reporting
modules
and
writing
themes,
but
I
would
love
to
give
people
a
place
to
display
those
sites.
On
that
I
think
backdrop,
main
site
is
a
great
place
to
do
it.
So
Drupal
has
a
pretty
good
showcase.
Where
you
can
put
up
a
site,
you
can
say
who
did
it
give
yourself
a
little
credit?
A
You
can
talk
about
any
of
the
modules
with
you
used
or
any
of
that
and
I
think
we
should
do
the
same
kind
of
thing
for
backdrop
where
we
can.
Let
people
show
off
the
work
that
they're
working
on
so
that
as
people
create
stuff,
they
can
post
it
for
everyone
else
to
see,
and
that
will
help
sell
backdrop
as
a
product
to
new
people,
which
is
good,
and
it's
also
really
fun
to
to
kind
of
show
it
from
week.
A
So
hopefully
we'll
get
that
up
shortly
after
the
modules
themes
and
layouts
pitches,
all
right,
so
other
things
we're
working
on
our
backdrop
itself,
so
we've
got
a
bunch
of
infrastructure.
We've
got
to
do
to
support
our
community,
but
you
know
mostly
what
we
spend
time
working
on
is
backdrop
the
product
and
we've
got
a
couple
of
great
things
in
the
pipeline.
A
Next
up,
we're
probably
going
to
be
doing
another
patch
release
or
bug-fix
release,
and
we
don't
yet
have
a
date
scheduled
for
that,
because
we
don't
have
any
urgent
fixes
that
you
know
someone
found
something.
That
was
something
we
consider
critical.
We
need
to
get
right
away
so
far.
It's
just
a
whole
bunch
of
a
little
tiny
bug
fixes,
as
you
know,
as
things
get
fixed,
they
get
merged
in.
So
we
don't
have
a
scheduled
date
for
the
next
bug-fix
release,
but
we
do
have
a
tag.
A
That'll
be
106
when
that
comes
out,
I.
Think,
more
importantly
than
those
bugs
which
will
of
course
fixes
we
find.
There
has
been
a
new
release
of
Drupal
and
we've
got
a
whole
bunch
of
patches
that
went
into
the
latest
version
of
Drupal
7
we'd
like
to
get
those
same
changes
into
the
next
version
of
backdrop,
just
so
that
we
don't
end
up
slipping
behind
any
problems
that
your
will
may
have
fixed.
So
hopefully
we'll
get
those
into
one
point:
06
as
well,
and
they've
got
a
meta
issue
for
that.
A
It's
number
8
43
on
github
and
those
are
actually
pretty
easy
for
anyone
who's
new
to
back
up
back
up
to
pick
up,
because
every
one
of
those
issues
has
patch
in
those
patches
usually
apply
fairly
cleanly
to
backdrop.
So
it's
just
a
process
of
going
through
each
patch
that
was
committed
to
Drupal,
applying
them
to
backdrop.
A
Out
at
one
point,
one
which
is
super
exciting,
we're
gonna
have
a
backdrop
1.1
release
party
on
the
evening
of
the
15th
near
drupal,
con
la
it
will
be
drupalcon
le
will
be
ending
on
friday,
so
we're
gonna
do
some
kind
of
a
bar
a
brewery
friday
evening.
Everyone
could
kind
of
come
out
and
meet
each
other
in
I
celebrate
the
release
of
want
lunch.
Thankfully,
so
super
exciting.
A
A
We
would
like
to
get
both
token
and
path,
auto
module
into
court
token
I've
been
working
on
tirelessly,
sometimes
fruitlessly
the
past
few
weeks,
and
so
far
we've
got
tokens
working
correctly,
like
a
browser
comes
up
the
insert,
but
not
all
the
tokens
are
being
replaced
correctly
and
there's
a
couple
of
tests
from
within
token
modulator
still
feeling
I
went
through
and
got
most
of
them
working
last
week,
there's
two
that
still
fail
and
that
I
will
resolve
today.
So
I
think
we're
almost
done
with
that
and
Jeff.
A
If
you
wanted
to
start
playing
with
that,
I
can
give
you
a
link
to
my
bro.
If
you
want
I
think
it's
probably
close
enough
that
you
could
start
trying
to
use
it
with
Pat
bato
if
you
wanted
to,
and
then
of
course
next
is
to
try
and
figure
out
where
to
integrate
path,
auto
and
decor
to
actually
use
those
tokens.
There's
only
a
few
places
in
court
that
use
tokens.
A
Currently
the
email
messages
that
get
sent
up
to
users
have
a
bunch
of
tokens
in
them
and
there's
a
couple
of
other
places
where
we
just
added
them
with
the
addition
of
token
module
like
into
field
descriptions
and
stuff
like
that,
but
those
those
should
be
coming
along
I
think
we're
probably
on
schedule
to
get
both
of
those
into
11.
We
have
a
month
a
little
over
a
month
left,
which
I
think
is
enough
time
to
start
doing.
Some
testing
get
it
in
get
everybody
start
using
it.
A
Seeing
if
that,
if
it
actually
does
what
we
said,
it
would
wishes.
I
ain't
gonna
be
good
and
then
other
things
we're
also
working
on
are
getting
a
new
administrative
feeling
theme
changes
done
for
1.1.
We
got
a
lot
of
feedback
when
we're
at
least
one
point,
oh,
that
it
looks
just
like
drupal
and
I.
Think
that
that's
good
and
a
lot
of
ways,
because
it
is
just
like
drupal
but
long
term.
A
We
need
to
start
separating
our
identity
from
Drupal's
identity
and
we
want
when
people
are
using
our
product
it
to
feel
like
a
different
product
than
using
Drupal.
Even
though
the
code
is
mostly
the
same,
so
I've
got
a
bunch
of
progress
going
on
on
administrative
style
guide
and
implementing
all
of
those
changes
into
a
branch
that
we've
got
going
on
and
where
we
can
see
all
of
the
little
changes
coming
together
and
I.
A
Think
we've
got
a
bunch
of
pull
requests
in
the
queue
for
that
and
a
a
few
more
we've
got
a
meta
issue.
It's
issue
number
7,
36
a
few
more
underway
as
well.
The
one
thing
that
I
think
we're
not
likely
to
get
into
one
point:
one
is
the
built
in
rich
text
editor,
which
is
something
that
is
super
important,
but
also
super
trixie
to
get
figured
out
and
integrated
in
and
so
I
think.
That's
probably
going
to
get
pushed
to
the
one
point
to
release
the
whole
focus
on
getting
token
path.
A
Auto
and
a
new
admin
look
and
feel
into
11.
Unless
someone
should
show
up
in
the
next
week
or
so
and
say,
11
needs
rich
deck,
editing,
I'm
going
to
commit
to
figuring
out
getting
in
and
getting
it
done,
and
you
know
crank
cranks
that
out.
High
speed,
I
think,
is
the
way
we're
going
to
be
able
to
get
that
in
511,
but
I'll
leave
it
on
the
list
here
for
a
couple
more
weeks
and
see
if
a
magical
persons
and
show
up
and
start
working
on
it.
A
But
but
for
now
that's
looking
a
little
unlikely
and
then,
of
course,
we
have
a
whole
bunch
of
other
stuff
that
we're
always
working
on
in
backdrop
at
bugs,
of
course,
as
they
come
up,
we'll
find
them
and
fix
them
and
they
get
merchan
all
the
time
user
experience
issues
as
people
are
using
backdrop
they
might
report.
Oh,
you
know,
I,
don't
understand
how
to
use
this
widget
or
you
know.
Could
you
update
the
tech
description
text
on
this
field?
A
You
know
stuff
like
that
that
it
would
make
more
sense
to
have
a
button
instead
of
a
drop
button
or
whatever
it
is.
We
can
update
a
whole
bunch
of
user
interface
stuff
without
breaking
any
api's
all
the
time.
So
as
long
as
we
consider
that
it's
an
important
change,
we
can
get
those
changes
into
one
dot,
one
as
well
and
developer
experience
issues,
and
if
you
need
a
backwards
compatibility
layer
for
something
or
a
wrapper
function
to
make
your
life
easier
as
a
developer.
We
want
to
hear
about
it.
A
We've
got
you
know
a
history
and
Drupal
of
things
being
developer
friendly.
We
want
to
keep
that,
especially
in
the
process
of
getting
people
who
are
moving
from
Drupal
the
backdrop
we
want
to
make
that
transition
as
seamless
as
possible.
So
as
much
as
we
can
make
things
make
sense
to
people
I
think
that's
going
to
be
good,
not
all
developer
experience
issues
can
get
salted
1.1
because
some
of
them
are
going
to
need
API
changes
and
we'll
have
to
get
pushed
a
backdrop
to,
but
I
think
that
we
want
to
hear
about
them
anyway.
A
We
want
to
know
what
problems
that
we're
having
with
backdrops
so
that
we
can
fix
them,
whether
it's
now
or
in
the
future,
and
then
every
Thursday.
After
this
meeting,
we
usually
have
a
little
sprint
where
we
get
together
and
work
on
backdrop,
so
we'll
all
meet
in
IRC,
our
IRC
channel
is
pound
backdrop
or
if
you
don't
have
IRC,
you
can
just
work
with
us
in
spirit
and
we'll
work
on
some
of
these
remaining
tasks
that
we're
doing
for
backdrop.
A
So
if
you
want
to
work
on
our
paths
auto
or
starve
under
rich
text
editor,
you
can
grab
an
easy
task
from
the
latest
version
of
Drupal
port
in
a
patch.
If
you
want
to
do
that
and
or
you
if
you're
a
friend
or
you
want
to
work
on
the
admin,
look
and
feel
with
you,
some
help
with
that.
Anyone
who
has
an
hour
to
give
a
week
or
two
hours
or
a
day
join
us
on
Thursdays
and
you'll,
find
that
you'll
get
a
lot
of
help.
A
There's
a
ton
of
people
that
are
working
on
backtrack
on
thursdays,
hangout
and
IRC.
Talking
about
problems.
If
IRC
is
too
nerdy
for
you,
you
can
also
use
reddit.
It's
it
for
different
kinds
of
nerds,
I.
Suppose,
there's
a
really
great
forum!
We've
got
going
on
there
I
subreddit
at
what
is
it
reddit
com,
/,
r,
/
backdrop?
So
if
you
just
want
to
ask
in
kind
of
a
more
forum
setting
or
raise
a
topic
for
discussion,
that's
a
good
place
to
do
it.
A
And
if
you
have
a
question
and
it
doesn't
get
answered
right
away,
people
in
there
will
actually
paying
other
people
who
are
working
on
backdrop
who
might
have
answers
to
come
on
in
to
answer
the
questions
too.
So
it's
a
good
place
for
for
people
to
have
a
little
more
conversation.
That
is,
you
know,
not
IRC,
something
it
gets
logged
in
as
googleable
and
all
that
good
stuff.
A
It's
also
listed
on
the
reddit,
so
if
you
can
get
to
the
reddit,
you
can
find
a
link
to
the
ical
feed.
I
also
think
it
might
be
on
the
backdrop
contribute
page,
but
if
not,
we
should
add
it
there
I'll
double
check
there
and
see
if
that's
going
to
be
definitely
much
easier
for
people
to
find
and
then,
in
addition
to
having
these
weekly
meetings,
we
also
have
a
fortnightly
design
meeting
which
starts
an
hour
earlier.
A
So
if
you're
in
our
students
solving
some
of
the
design
problems
for
backdrop,
we've
got,
you
know
we
need
stickers
t-shirts
as
well
as
what
design
you
can
definitely
drop
in
on
that
meeting.
We
need
help
there,
and
then
we
have
a
couple
of
drupal
friendly
events
scheduled
on
event
calendar
as
well
right
now,
there's
only
one
on
there
and
it
is
the
Twin
Cities
drupalcamp.
So
this
is
a
sorry
backdrop
friendly
Drupal
event
at
one
suitable
camp
in
June.
A
If
anyone
else
is
going
to
be
attending
any
other
drupal
camps,
that
I
feel
like
it's
going
to
be
a
fun
place.
To
talk
about
backdrop,
let
us
know-
and
we
can
add
that
to
our
calendar
as
well.
So
that's
all
I
have
for
today's
meeting,
but
I
did
wanted
to
open
this
meeting
up
and
find
out.
If
anyone
here
has
any
questions
or
anything
they
wanted
to
talk
about
this
week.
A
A
A
So
that's
good
to
know,
and
we
did
also
officially
decide
on
bad
camps
dates.
Last
night,
it's
going
to
be
November
fifth
through
eighth,
so
I'll
put
that,
on
our
backdrop,
calendar
today
to
we're
trying
to
organize
a
backdrop
day
which
will
probably
be
like
the
Thursday
and
where
we
can
do
a
kind
of
a
little
mini
summit,
we're
trying
to
figure
out
where
we're
going
to
do
it,
but
that'll
that'll
be
fun.