►
From YouTube: Backdrop CMS Weekly Status Meeting 5/21
Description
It's the first meeting after the release of 1.1.0! Come join us for an update on our first minor release and the plan for 1.2.0.
A
B
It's
nice
to
see
some
faces
anyway.
Also
we
were
at
drupalcon
last
week
and
we
distributed
almost
all
of
our
dragon
stickers.
They
were
a
huge
hit.
Everybody
loves
the
dragon,
even
if
they
don't
look
back
to
fill
of
the
dragon
and
we
distributed
all
of
our
t-shirts.
We
think
printed
about
75
of
them.
B
We
got
to
the
very
last
day
and
we
had
like
two
women's
smalls
left
and
we
ended
up
having
to
people
who
wanted
women
smalls
at
the
backdrop
hormone
release
party,
which
was
fabulous,
so
we
distributed
all
of
our
t-shirts
for
those
of
you
who
eagerly
wanted
a
t-shirt,
we
can
definitely
order
more.
We
will
be
ordering
more
and
I
think
right
now.
B
The
plan
is
to
order
t-shirts
with
dragons
on
them,
because
everybody
loved
the
dragon
so
much
and
will
probably
try
and
have
those
on
for
distribution
at
bad
camp
November
we're
going
to
be
doing
a
backdrop
summit.
So
if
anyone
who
wants
to
come
to
that
camp
can
we
can
distribute
shirts
there?
If
you
can't
come
to
bad
camp
and
you
are
overly
deserving
of
a
t-shirt,
let
us
know
and
we
can
probably
drop
them
in
the
mail
I.
B
A
A
B
B
B
Since
our
last
meeting,
we
had
a
very
brief
meeting
last
week
is
your
book
on,
but
since
our
last
real
meaning,
we
have
had
nine
new
contributed
projects
which
is
great
web
to
a
total
116.
We
have
34
contributed
module
authors.
Those
are
people
are
actually
part
of
the
kinship
group.
We
have
42
projects
with
official
releases
on
backdrop,
CMS
org,
so
these
are
projects
that
have
been
tagged
once
I
get
tagged.
B
They
get
pulled
into
the
primary
website
aggregated
and
that's
that
when
we
turn
on
update
checking
your
site
will
tell
you
to
update
a
module
and
you
will
have
a
version
to
go
and
update
to
that's
kind
of
important
too.
So
we've
got
a
total
of
forty
two
of
those
which
is
pretty
good,
we're
inching
towards
halfway
there
for
all
of
our
total
projects.
B
So
speaking,
of
update
checking,
that
is
the
first
thing
on
our
list
here
for
things
that
were
working
on
that
are
not
backdrop
itself
and
we
have
the
backdrop
CMS
dot,
org
website
integrated
with
github,
just
as
we
said
when
you
tag
your
releases,
1
dot
x,
dash,
1,
dot,
x,
dot
y
or
whatever
you
choose
to
tag
it
as
it
doesn't
match
our
official
tagging
thing.
It
might
not
appear
on
github,
but
I
think
nate.
B
A
Expect
for
the
most
part,
you
need
to
match
the
versioning
pattern.
Exactly
so
you
need
to
say,
yeah,
1,
dot
x,
dash,
you
know,
1
dot,
x,
dot
y
or
whatever
your
version
number
is.
If
you
don't
match
that
the
versioning
pattern,
then
you'll
get
a
packaging,
errorlog
dot,
txt
file
attached
to
your
release.
That
will
tell
you
what
went
wrong.
So
as
long
as
you
get
an
error
log,
then
that
means
that
it
worked
successfully
and
that
you've
made
a
release.
A
B
So
I
know
like,
as
I,
contributed
ma
module
author
I
am
definitely
not
going
to
be
as
diligent
about
making
releases,
as
we
are
with
backdrop
itself
and
probably
that
third
dot
won't
mean
anything
to
me
like
that's
likely
to
always
be
0
and
I
will
use
the
same
module
numbering
as
I
did
on
drupal.org,
which
would
be
like
one
dot.
One
dot
zero,
followed
by
10
to
20,
followed
by
one
two
three
got
0
0,
but
that
last
dot
is
there
for
packaging
script
purposes.
B
You
don't
have
to
use
it
like
you
intend
to,
but
if
you
have
a
bigger
project
as
a
lot
of
activity
on
it
and
you
want
to
use
it
semantic,
versioning
is
there.
So
hopefully
that
won't
chip.
Anyone
else
up.
You
don't
have
to
get
stressed
out
by
the
extra
duck.
I'm
saying
I'm,
not
letting
against
me
all
right,
so
the
rest
of
the
stuff
we're
doing
for
update
checking
on
project
usage.
B
It
needs
to
be
deployed,
but
it
is
ready
we're
just
waiting
to
turn
that
on
until
we
are
ready,
with
our
contributed
module
listing
on
backdrop
CMS
to
org,
which
should
be
any
day
now
and
then
the
next
thing
most
important
thing
that
we're
working
on
for
backdrop
is
drush
and
I.
Don't
know
Gus.
If
you
want
to
give
us
an
update
or
sorry
ejectment
against
an
update
on
where
we
are.
With
that
I
know,
you've
been
doing
a
ton
of
work
on
trying
to
get
all
of
the.
C
B
Okay,
I
know
it's
kind
of
complicated,
like
trying
to
figure
out
how
much
we
can
steal
from
triple
seven,
how
much
we
should
steal
from
Tripoli
and
how
much
we
need
to
do
our
own
stuff
of
and
especially
in
the
boot
phase,
because
it's
like
our
code
is
in
a
different
place,
but
it
it
mashes
Drupal
eights
location,
but
it
needs
to
function
like
drupal
7.
So
there
is
going
to
be
a
little
kind
of
magic.
We
have
to
do
to
figure
out
how
to
get
that
all
hooked
up
correctly.
Thank
you.
B
B
B
But
that
might
not
happen
until
after
we
have
backed
up
one
point
two
out
and
because
we
have
a
lot
of
fun
stuff
to
work
on
for
the
next
few
major
versions,
effective.
So
speaking
of
backdrop
itself
on
May
fifteenth,
we
released
backed
up
1.1
and
we
also
cut
another
release.
It
backed
off
one
point:
oh
so
backed
up
one
point:
0
point:
6
was
released
the
same
day
as
1.1,
and
that
was
just
that.
We
made
sure
that
all
the
stuff
that
was
available
for
1.1
was
also
available.
B
Sticking
to
our
guns
here
about
releasing
the
south
or
whether
we're
done
or
not,
trying
to
set
a
precedent
that
we
do
things
a
little
differently
than
how
happened
in
the
Drupal
community
I
think
we
did
a
great
job
with
that.
We
also
had
our
first
bug-fix
release
for
1.1,
which
came
out
yesterday:
Thank
You
Nate.
There
were
some
issues
with
field
tokens
which
we
managed
to
get
fixed
right
away,
which
I
think
was
fantastic,
so
really
happy.
We
got
those
out.
B
We
also
have
a
couple
of
other
things
in
the
queue
for
patch
releases.
One
point
one
point:
two
we're
hoping
will
include
all
of
the
changes
from
Drupal
7.36.
There's
a
pull
request
that
I
work
done,
I
think
on
release
day,
that
included
all
those
I'm,
not
sure
native.
You
had
a
chance
to
review
that,
but
it
might
need
some
work,
I,
just
kind
of
squished,
all
the
patches
in
so
they're
all
there.
But
how
much
are
they
are?
All
tests
are
passing
not
sure
all
the
bugs
are
actually
fixed
and.
B
B
Midnight
we'll
get
those
done
and
then
there's
another
issue
for
7.37,
which
I
missed
the
first
time
around,
but
I
did
find
it
later
on
which
I
put
all
of
the
next
patch
patches
from
triple
something
that
we
should
apply
in
there
as
well.
So
hopefully
we'll
get
that
done
as
well
and
get
both
of
those
included
in
one
point
to
point
or
one
point,
one
point
to
and
other
bugs,
obviously
we're
running,
open
source
software-
it's
not
perfect,
will
be
fixed,
doesn't
find
them
and
yeah
good
stuff.
B
So,
in
terms
of
new
features,
we're
going
to
be
aiming
to
release.
One
point:
two
point:
zero
on
September
15,
also
on
schedule.
We
hope-
and
that
will
include
some
big,
exciting
features.
We're
hoping
to
get
our
rich
text
editor
in
this
is
what
is
going
to
make
us
actually
be
able
to
compete
with
WordPress
until
we
have
that
people
seem
to
be
uninterested
in
and
doing
a
backdrop
sightings
of
a
wordpress
site,
and
but
we
also
want
to
start
putting
in
field
modules.
B
So
there's
a
long
list
of
a
whole
bunch
of
field
modules
have
been
included
in
Drupal
8.
We
want
to
get
a
comparable
list
of
field
modules
that
are
included
in
backdrop.
These
should
be
pretty
easy
to
port.
If
we've
got
filled
modules
in
contribute
that
are
working,
we
can
just
move
them
into
four.
It's
not
going
to
be
a
lot
of
work,
so
if
we
can
gets
imported
first
moving
them
into
course
should
be
fairly
straightforward.
B
We'll
do
a
little
code
review
and
make
sure
that
the
kinship
code
is
up
to
snuff
with
how
we
do
things
in
core
and
then
rich
them.
In
so
most
of
our
effort
for
1.2
is
going
to
be
on
getting
ck,
editor
module
or
ck
editor
editor
in
core
and
we're
not
basing
that
on
either
the
WYSIWYG
module
/
triple
7
or
the
ckeditor
module
for
drupal
7.
We
are
instead
making
it
more
similar
to
a
module
called
WYSIWYG
ckeditor
she's
WYSIWYG
underscore
ck,
under
that
it
exists
for
Drupal
7.
B
That
was
an
early
back
port
of
the
rich
text,
editor
that
went
into
Drupal,
8
backboard
a
did
rupal
7
and,
of
course
it's
changed
a
lot
in
jur
blade
since
then,
but
we
want
to
start
with
that.
Starting
point
and
kind
of
rethink
how
that
can
be
integrated
and
then,
of
course,
to
make
sure
we've
got
a
ck
editor
up
to
the
latest
version.
We've
got
integration
working
the
way
we
want.
All
of
that
good
stuff
can
be
built.
B
On
top
of
that
starting
point,
so
I
think
I've
got
a
couple
of
projects
that
need
rich
text.
Editors
in
Drupal
7,
I'm
going
to
start
with
that
WYSIWYG
ckeditor
module
and
see
if
I
can
get
it
up
to
date
for
drupal
7,
and
then
we
will
start
trying
to
port
that
to
backdrop.
So
if
anyone
wanted
to
start
on
that,
that
would
be
a
good
starting
place
for
getting
our
rich
text.
Editor
done
and
me
I
know
you
have
a
lot
of
strong
feelings
which
text
editors
in
court.
B
Alright,
so
other
things
we're
working
on,
there's,
obviously
a
ton
of
user
experience
issues
we've
got
in
the
queue
we
can
fix,
those
as
we
have
time
there's
a
ton
of
bugs
will
fix
as
they
come
up
developer
experience
issues
as
we
find
them.
We
want
to
note
them,
even
if
we
can't
fix
them,
some
of
them
might
require
API
changes,
but
we
want
to
have
them
in
the
queue.
B
So
if
you
find
something
you
find
difficult
as
you're
working
on
your
back
drop
site,
let
us
now
we
can
try
and
figure
out
ways
to
make
it
easier
for
you
in
backed
up
one
and
maybe
solve
an
entirely
impactor
too.
Yes,
documentation
issues
as
well.
I'm,
not
sure
we
have
a
tag.
I
think
we
do
I
think
we
have
an
actual
tag
in
the
github
issue:
queue
for
documentation
issues.
B
So
if
you
find
something
either
in
the
code
that
needs
documentation
and
to
create
an
issue
on
Drupal
that
work
and
say
or
sorry,
I'm
getting
on
and
say,
I,
I
found
this
code
and
understand
it
or
I
read
this
api
code
in
it
to
keep
doc
Walken.
It
doesn't
make
any
sense
with
the
code.
We
have
we're
trying
to
include
all
of
the
docs
updates
that
went
into
Drupal
7
also
in
backdrop,
but
there
may
still
be
tough.
B
That's
either
different
from
how
Drupal
7
does
it
or
still
lacking
that
we
would
love
to
get
those
two
if
the
documentation
issues
are
not
related
to
the
code
like
not
necessarily
our
code
base,
but
our,
for
example,
I
want
a
page
on
how
to
update
my
theme
on
those
issues
should
go
against
the
backdrop.
Api
site
issue
queue.
So
if
there's
a
page
you
want
with
documentation,
we
can
write
that
up
for
you,
but
it
needs
I.
In
theory,
the
issue
should
be
filed
against
the
UK
site.
B
If
you
don't
know
what
a
final
issue
pilon
issue
will
see,
it
will
tell
you
where
it
should
be
filed
on
is
in
the
wrong
place,
but
we
do
have
a
bunch
of
great
people
working
on
documentation
and
if
you
find
some
pages
that
need
updates
the
documentation,
we
also
have
the
ability
to
grant
you
access
to
update
yourself.
So
if
you
are
good
at
writing
documentation
and
want
to
help
with
that,
we
would
love
more
help
in
that
area
too.
So
weigh
in
where
you
think
we
need
stuff.
B
B
B
So
if
we
have
anyone
who
wants
to
work
on
change
records,
we
do
have
a
queue
in
the
github
issue,
key
which
is
now
linked
in
the
sidebar
for
issues
that
need
change
records.
We
could
get
someone
to
rough
draft,
those
change
records.
We
get
someone
else
to
review
them.
That
would
be
great
to
get
that
completed
to
as
people
start
using
about
drop
one
more
Wes,
I'd
love
it.
B
If
you
would
work
on
documentation
for
layouts,
we
definitely
have
a
bunch
of
new
magic
going
on
in
the
layout
world
and
not
a
lot
of
documentation
around
how
that
works.
We
have
one
video,
that's
pretty
old,
it's
from
when
we
first
have
the
layouts
for
ranch,
and
things
have
changed
a
little
bit
since
then
so
be
good
to
have
some
updated
documentation,
also
an
updated
video.
If
anyone
wants
to
play
with
layouts
to
make
a
little
video
that
might
be
fun
too.
B
Progress,
we
have
a
little
sprint
every
Thursday,
usually
all
day
thursday
is
backdrop
day.
If
anyone
has
any
time
they
can
get
from
their
job
or
from
themselves
their
self
employed.
There
is
a
good
day
to
spend
that
time,
because
there's
lots
of
other
people
in
IRC
channel
talking
about
backdrop
playing
the
backdrop
all
that
stuff.
If
thurzday's
don't
work
for
you,
that's
also
fine.
We
take
any
hour
of
any
day
from
anyone
so
contribute
whenever
you
can.
B
Nate
and
I
are
usually
an
IRC
there's,
usually
a
handful
of
other
people
in
there
too.
So
if
we're
sleeping,
because
you
work
in
Australia
you're
on
different
time
zone
or
what
have
you
there's,
often
other
people
hanging
out
there
as
well
so
feel
free
to
ask
any
questions
you
have
in
the
channel
on
and
if
the
IRC
channel
pound
backdrop
is
not
for
you,
we
also
have
read
it
a
subreddit
where
you
can
ask
questions
there
too.
B
We
try
and
keep
an
eye
on
what's
going
on
in
that
queue
and
get
those
questions
answered
reasonably
quickly
as
well.
So,
hopefully,
and
contribute
knows
how-
and
we
do
have
a
page
on
factor
of
semester
or
about
contributing
which
will
give
you
a
kind
of
a
good
entry
point
to
how
to
write,
pull
requests.
If
you
need
help
writing
poor
requests,
if
you
feel
like
you
can't
contribute
to
code,
we
obviously
need
a
lot
of
helpful
documentation.
We
would
love
assistance.
B
There
also
I
think
what
is
most
valuable
to
us
right
now,
if
you're
watching
this
video
wondering
how
you
can
help
is
to
just
use
backdrop,
try
it
out,
try
and
build
a
site,
see
what
kind
of
problems
you
run
into
and
let
us
know
if
you
don't
run
into
any
problems.
Let
us
know
about
that
too.
So,
yeah
I
think
we're
in
pretty
good
shape.
We've
got
people
building
sites
with
it,
which
is
great.
We've
got
people
porting
modules,
which
is
also
great
and
where
we've
got
some
good
momentum.
B
Fine,
so
I'm
super
excited
about
earlier.
If
you
are
interested
in
having
these
meetings
feed
into
your
normal
weekly
calendar,
we
have
an
ical
feed,
that's
available
from
google,
which
will
tell
you
about
this
meeting,
which
happens
every
week,
and
we
also
have
a
design
meeting
which
happens
fortnightly
next,
one
will
be
next
week.
B
It
starts
an
hour
before
this
one,
that's
usually
where
we
talk
about
and
the
modules
page
layout,
or
you
know
we're
gonna
jog
in
and
our
t-shirts
going
to
do
it
stuff,
like
that,
there's
also
a
lot
of
little
tiny
design
tasks
that
might
be
fun
if
you're
a
designer
and
you're
like.
Oh,
you
know,
I'd
like
to
make
a
background
image
for
your
Twitter
page
or
something
like
that.
Oh
that's,
pretty
pretty
easy
place
for
people
to
jump
in.
So
if
you
want
to
attend
those
meetings,
that
could
also
be
a
good
place.
B
I
watch
the
videos
and
we
also
have
a
calendar
where
we
are
posting
events
that
we
know
our
backup
friendly
right
now.
They
are
mostly
Drupal
events,
but
we
do
have
our
first
so
last
year
we
did
one
which
is
kind
of
HTML
conference,
and
we
have
one.
This
year,
that
is
called
nerd
summit,
which
is
a
Drupal
and
WordPress
event.
So
we
thought
it
would
be
perfect
since
we're
trying
to
sit
squarely
between
the
two
of
those
and
so
will
be
an
Ruby
I'll,
open
source,
fun.
B
Stuff
they'll
be
there
for
that
in
anyone
who
wants
to
attend
a
drupal
event
and
talk
about
back
job
if
you've
talked
to
the
organizers
and
event
they
want
to
hear
about
back
job.
Let
us
know
we
can
throw
that
on
the
calendar.
This
is
not
just
a
you
know.
Backdrop
tour
calendar
so
much
as
it
is
a
place
where
anyone
can
look
up
what
events
are
happening
near
me,
where
I
can
go
to
learn
more
about
back
job
as
well.
B
B
We
also
have,
as
Nate
mentioned
a
whole
new,
a
ton
of
stuff
people
talking
about
backdrop
this
week,
which
I
think
is
fantastic
under
publicity
here
1.1
is
out.
I
think
that's
made
kind
of
a
big
splash.
We
have
a
waterloo
regional
meet
up
tonight
where
people
are
talking
about
backdrop,
we
have
drupalcamp
colorado
coming
up
where
we
will
be
going,
we're
not
entirely
sure
we're
going
to
be
presenting
on
backdrop.
B
We've
submitted
a
session
we'll
see
if
they
want
to
hear
it
and
an
Twin
Cities
drupalcamp
will
almost
certainly
be
presenting
their
I
think
session
submissions
closed
yesterday.
So
hopefully
we
got
a
session
in
we'll
have
to
see
oh
and
then
nerds.
Some
will
definitely
be
in
nerd
summit
and
we
do
have.
Obviously
the
latest
group
of
watchdog
that
came
out
around
time.
Triple
Crown
has
RNA
7ph
backdrop
spread
in
it.
Anyone
wants
to
write
any
blog
poster
articles
about
backdrop.
B
We
would
love
that
will
throw
you
here
on
our
publicity
announcements
every
week
and
anyone
wants
to
give
talk
on
back
up
low
snow.
Put
you
on
calendar
yeah,
any
any
good
news.
Anyone
else
has
heard
share
with
us.
We
might
not
know
all
of
everything.
That's
going
on
yeah
I
think
things
are
looking
super
exciting.
Everyone
seems
to
be
optimistic
about
things
which
is
good
rather
than
having
any
naysayers.
We
seem
to
have
a
lot
more
people
that
are
curious
about
backdrop.
B
B
B
Let's
see
if
anyone
else
has
any
questions
or
anything
it
looks
like
Jeff
wants
to
know
if
we
have
config
inversion
control
for
vector
of
CMS
org.
This
is
a
great
question.
We've
had
a
couple
of
questions
in
the
issue.
Queue
we've
had
questions
on
reddit.
We
posted
something
in
the
article
in
Drupal
watchdog
about
how
to
manage
your
config
in
version
control.
We
currently
have
three
different
approaches
to
it
and
is
backdrop:
CMS
running,
never
version
their
config
out
of
version
control
me.
A
A
A
We
had
considered
doing
it
a
couple
of
different
ways
like
I
I'd,
considers
having
a
third
period
of
active
stating
and
then
one
that
is
version,
but
the
directory
that
we
ended
up
using
or
the
approach
we
ended
up
using
with
the
figure-eight
approach
that
Jen
documented,
and
so
what
we
do
is.
Instead
of
naming
our
directories
active
and
staging
what
we
do
is
we
named
one
of
them,
dev
active
and
one
of
them
product
is,
and
they
are
then
in
settings
by
PHP.
A
The
production
server
pointed
product
is
for
the
active
directory,
but
that
pointed
dev
active
for
the
staging
directory
and
on
the
dev
site,
its
flipped,
so
the
dev
site
points
a
dev
active
as
active
employment,
product
Avast
aging.
You
can
see
how
that
all
works
out.
If
you
read
that
that
that
thread
there,
but
it's
actually
working
really
pretty
well.
A
A
B
We
obviously
don't
have
on
pantheon
or
aqua.
It's
just
a
node.
I
think,
and
we
don't
have
that
money
developers,
so
we
figured
keep
it
straightforward,
make
it
as
easy
as
possible
to
manage,
come
on
and
eat
our
own
dog
food.
So
all
right!
It's
working,
yeah!
I'm
also
looking
forward
to
setting
up
config
and
version
control
on
the
Pantheon
site,
too.
I've
got
a
couple
of
flying
sites
up
there
that
I
want
to
try
that
on
and
see
if
we
can
get
it
to
work
through
their
dashboard.
B
D
B
And
Nate
correct
me:
if
I'm
wrong
here,
I
think
there
are
a
few
follow-up
issues
from
the
front
end
that
we
put
into
one
point
one
that
we
would
like
to
get
wrapped
up.
We
figured
none
of
those
were
released
lockers
and
we
could
just
handle
them
later.
Something
like
table
vinod
or
ever
sorted.
Getting
a
the
active
column,
sort
indicator
color
to
be
less
dark.
There's
just
a
couple
of
little
tiny
things
that
you
don't
notice
until
it's
all
together
and
then
you're
like.
B
Oh,
we
should
immediately
neta,
so
that
would
be
I
think
really
valuable
to
have
those
kind
of
just
knocked
out.
So
you
don't
to
think
about
them
anymore
and
on
the
modules
page
stuff,
it
is
definitely
back
top
CMS
or
modules.
Page
design
is
high
on
our
list
and
if
you
want
to
get
involved
with
that,
we
should
add
you
to
that
repo.
So
you
can
make
whatever
for
requests.
You
want
over
there
or
get
I,
don't
know
how
we
want
to
figure
that
out,
but
get
you
on
that
group.
B
So
you
can
contribute
there
too
and
then,
in
terms
of
backdrop,
I
think
we
had
some
stuff
that
was
not
administrator
facing,
but
instead
front
end
facing
where
we
wanted
to
like
remove
the
gradient
from
far
tick.
There's
been
a
bunch
of
work
going
on
over
there.
I
would
love
to
see
some
improvements
on
initial
install
to
make
it
look
a
little
different,
like
I,
think
one
to
make
the
initial
color
palette
black
and
we
want
to
know
greedy,
there's
just
some
little
stuff
like
that.
B
That
would
might
also
help
separate
our
branding
a
little
from
Drupal
that
that
would
be
nice
too.
If
you
wanted
to
keep
working
on
backdrop,
but
yeah
modules,
page
stuff,
will
be
good.
I'll,
King,
Darius
again
about
designs
for
that
I
know,
he's
got
a
bunch
that
he's
working
on.
It
will
be
good
to
see
where
those
argued
so
well
thanks
anything
else.
B
All
right,
I'm
gonna
go
play
in
the
issue.
Queue.
It's
gonna
be
great
okay,
so
we
will
see
everyone
next
time
same
bat
Channel
next
week
in
the
queue
before
then.
So.
Thank
you
all
for
coming.
Super
excited
to
have
one
point:
one
out:
oh
I,
get
to
start
my
next
paid
client
project
on
backdrop
next
week,
I'm
super
excited
about
that.
What
so
everyone
else
do
the
same
yeah
start
getting
paid
for
backup
work
on
backdrop,
it'll
be
much
better,
all
right,
I!