►
From YouTube: Backdrop CMS weekly 9/17
Description
Backdrop CMS weekly 9/17
A
All
right
we
are
on
air,
it
is
Thursday
September
17th.
We
have
a
bunch
of
exciting
things
going
on
this
week.
The
biggest
thing
is
that
backdrop
1.2
came
out
on
Tuesday
I
was
probably
around
eleven
o'clock,
I
suppose,
and
we
had
a
whole
bunch
of
things
that
went
in
at
very
last
minute.
That
made
me
personally
very
excited,
which
was
fantastic
Wes.
Your
responsive,
vertical
tabs
were
amazing
me
and
I.
Just
couldn't
we
kept
playing
with
it
more
like
it
just
makes
it
feel
so
much
more
real
to
have
like
that.
A
A
Let's
make
it
easier
to
use
it's
going
to
be
huge
everyone.
So
thank
you
to
everybody
for
working
on.
One
point
two
point:
oh,
we
definitely
had
a
ton
of
involvement
from
a
ton
of
really
great
contributor,
so
just
wanted
to
put
that
out
there
all
right.
So,
as
usual,
we
have
phpstorm
licenses
for
backdrop
containing
about
Jeff
project.
A
A
Yes,
sorry,
I
thought
I
was
actually
using
my
computer
to
microphone,
but
apparently
there's
London
I.
Had
such
awesome
apologies
for
this.
They
do
it
again.
Okay,
I'll
just
sit
really
still.
We
also
need
do
you
want
to
give
us
an
update
on
this,
because
this
is
what
you've
been
working
on,
that
browser
stack
tool.
B
Oh
yeah,
this
is
really
exciting,
so
browser
stack
has
open-source
licenses
as
well,
which
is
great
because
browser
stack
is
also
kind
of
super
expensive,
but
I
know
Wes.
You
you've
been
mentioning
a
used
browser
stack
to
find
figure
out
all
of
these
issues
and
I'm
like
I'm,
on
like
Firefox
38
on
Yosemite
on
Mac,
and
it
only
happens
on
Mac
and
only
on
this
version
of
Firefox
and
you're
like
what
the
hell.
So
this
is
really
exciting,
because
browser
stack
has
100
some
browsers
and
you
can.
A
B
Also
on
our
website
somewhere,
which
I
think
will
put
in
our
credits
page
but
will
probably
also
end
up
putting
it
references
kind
of
all
over
the
place
where
ever
we
have
like
contributing
documentation,
because
we
really
want
people
to.
We
want
to
encourage
people
to
use
that
service,
because
it
will
make
for
better,
better,
responsive
and
better
browser
compatibility
across
across
back
job.
So.
C
B
I've
been
using
it
in
Firefox,
and
even
that
I
mean
it
was
just
incredible
like
I
just
installed
it
and
then
then
it
went.
They
went
really
well
kind
of
speaking
of
which
we
kind
of
have
some
ie8
issues
since
I
pulled
that
up,
while
I
was
in
there.
That
was
like
geez.
This
needs
some.
This
need
some
love,
but
it.
C
B
So
anyway,
that's
real,
exciting
I'm,
almost
certain
that
we'll
do
that.
It's
it's
a
really
great
service
and
what
I'm
excited
about
is
I've
been
transitioning
off
of
apple
products
recently,
so
I'm
running
ubuntu
as
my
desktop
now,
and
if
you
do
that,
you
have
no
possible
way
of
testing
like
iOS
devices,
because
it
only
works
on
mac
OS.
B
So
I'm
excited
because
this
will
kind
of
liberate
us
from
needing
to
be
running
apple
products
in
order
to
test
apple
devices,
so
so
yay,
more
freedom,
that's
great,
and
thank
you
very
much
browser
stack
as
soon
as
we
get
that
hooked
up.
Will
everybody
know
how
that
works?
We're
not
sure
about
if
we
can
actually
invite
individuals,
we
may
end
up
with
like
five
accounts
or
something
crazy
like
that,
but
we'll
figure
it
out.
B
Let's
see
the
next
topic:
drupalcamp
Utah's
coming
up,
februari
26!
That's
a
long
way
away.
We
mention
it
every
week
that
they're
just
looking
for
a
speaker
on
backdrop
and
if
you
are
interested
in
visiting
Utah
februari,
26
2016
then
reach
out
to
their
organizers
there,
and
you
have
the
possibility
of
getting
a
scholarship
up
to
five
hundred
dollars
for
covering
your
travel
and
lodging
expenses
and
it's
great
time
just
no
board
out
there.
So.
B
Let's
see,
let's
see,
also
jen
stepping
up
in
the
notes
right
now.
We
also
need
speakers
for
bad
camp,
which
is
october.
Twenty
second,
on
thursday,
is
the
backdrop
summit
day
and
we'd
love
to
have
anybody.
That's
interested
in
backdrop,
orgies
back
up
to
share
their
experiences,
whether
that's
like
in
a
kind
of
a
you
know
like
a
format
that
is
more
open
and
less
formal
or,
if
you're
up
for
giving
a
presentation
any
of
those
things
we'd
love
to
have
you
speak
at
bad
camp
in
berkeley
october.
B
B
Let's
see,
community
growth
lots
more
great
community
growth
going
on
153
total
projects
for
backdrop
CMS
we
work
on
her
in
50,
which
is
nice.
We
have
five
new
projects
in
the
contribute,
since
last
week
there
around
seventy
six
total
projects
with
official
releases
on
backdrop,
CMS
org,
it
seems
like
most
of
our
contributors
have
got.
B
This
figured
out
now
the
eat,
a
new
project
with
1
dot
x,
dash,
whatever
the
version
number
of
your
module,
is
and
publish
that
tag
on
github
minute,
synchronizes,
our
with
backup,
CMS
org
and
so
our
backdrop,
CMS
org
repositories.
Looking
nice,
it's
continuing
to
build
out
there's
three
pages
of
modules,
which
is
I,
find
exciting,
50
pages,
/,
mod
or
50
modules
per
page,
let's
see
and
in
the
world
of
contribute.
This
week's
or
when
I
looked
at
39
total
contributed
module
offers,
which
is
fantastic.
B
Welcome,
Matthew!
If
you
watch
this
video
welcome
to
our
little
community,
we
made
a
module
called
WordPress
menu,
gives
you
the
menu
from
WordPress
in
Drupal
or
backdrop
he's
trying
to
maintain
it
for
everything.
So
we
love
that
kind
of
enthusiasm
and
seeing
those
kinds
of
projects
come
over
to
back
jump.
B
Let's
see
infrastructure
tests.
Every
week
we
talked
about
how
our
infrastructure
around
backdrop
CMS
is
coming
along.
Let's
see,
update,
checking
on
backdrop
CMS
org.
This
has
been
working
for
a
long
time,
but
our
analytics
aren't
collecting
properly
if
you're
interested
in
trying
to
fix
our
analytics.
It's
something
in
the
project
module
the
contributed
project
module
that
analytics
aren't
accruing
properly,
even
though
we're
getting
pinged
from
all
the
backdrop,
websites
that
are
out
there
and
they're
telling
us
what
modules
they're
running,
we're,
not
processing
that
data
correctly
we're
saving
it.
B
B
It
does
seem
like.
Actually,
we
had
one
user
that
was
trying
the
module,
installer,
the
built-in
module
installer
and
actually
using
that,
but
it
likes
1.2.
We
may
have
broken
me
in
stellar,
so
wanted
to
fix
that
as
well,
but
project
browser
will
allow
you
to
from.
In
your
backdrop,
website
download
and
install
find
download
and
install
projects
making
it.
So
you
don't
need
to
actually
leave
your
site.
You
don't
need
to
go
to
backdrop,
CMS
torg,
you
don't
need
to
go
to
github.
B
There's
some
work.
I
know
dr.
Beaumont
filed
for
request
to
fix
some
issues
that
may
be
solves
that
paging
problem
that
we've
been
itching
for
the
past
couple
weeks,
so
that
could
get
fixed
pretty
much
imminently.
Let's
see.
The
next
item
is
just
for
backdrop
and
Jen
you've
been
working
on
this
a
lot
more
than
I
have.
Could
you
give
the
update
sure.
A
A
Storing
looks
a
lot
like
you
did
in
Drupal
6,
where
it's
a
single
string
with
your
database
information
in
it,
and
rush
for
Drupal
7,
expected
an
array
and
we've
kind
of
copied
the
way
Josh
for
triple
seven
works,
and
so
josh
is
unable
to
get
our
database
connection
information
out
of
that
string.
So
I
found
the
place
in
fresh
where
it
determines
which
version
triple
you're
running
and
then
tries
to
dissect
the
information
in
the
appropriate
way,
and
we
just
need
to
somehow
tell
Josh.
Do
it
like
Drupal
6?
A
A
That's
currently
running
it,
so
we
have
a
way
to
detect
which
version
of
software
it
is,
and
so
that
needs
to
also
say:
oh
well,
if
I'm
triple
seven
I
use
the
connection
or
air
FM
triple
six
days,
the
string
or
fine
backdrop
use
the
Drupal
6
string
and
we
just
haven't.
We
don't
have
that
Association
working.
So
we
need
to
figure
that
out
too
so
yeah
this
morning,
I
was
like
what
should
they
work
on
today?
1.2
is
out
and
they
started
thinking
about
him
like
Josh.
A
Of
course,
that's
what
I
was
working
on
last
week.
It's
always
work
on
some
pink,
but
yeah
we'll
get
there
I
think
it's
it's
coming
along
and
hopefully
we'll
have
it
moving
soon,
we'll
see
so
should
I
keep
telling
nate
you're
muted.
The
next
thing
on
our
agenda
is
backdrop
CMS
to
org
our
primary
website,
something
kind
of
exciting
exciting
about
that
website.
A
Right
before
we
launched
1.2,
we
wanted
to
see
if
the
upgrade
would
work,
and
we
also
wanted
to
try
and
embed
images
in
a
post
on
backdrop
CMS
to
org
to
talk
about
inline
images
and
we're
like
oh
well.
It
would
be
great,
we'll
just
test
it
by
upgrading
our
website
first,
and
so
we
ran
the
upgrade.
It
worked
great,
which
is
fantastic,
and
then
we
were
able
to
embed
images
in
post,
so
we
even
got
backed
up
CMS
org
running
one
point
to
point
o
before
one
point
to
point
o
was
actually
out.
A
It
was
a
perfect
test
case.
It
went
really
smoothly.
Shy
thinks
fantastic.
So
now
we
have
the
latest
version
of
the
software
running
our
own
site.
We
should
probably
also
update
API
site
and
any
other
sites
were
responsible
for,
but
for
now,
I'm
just
thrilled
that
we
were
able
to
get
that
out
so
soon
so
seamlessly
also
on
our
primary
website.
We
have
integration
for
my
listings
and
layouts.
A
There
are
a
couple
of
little
pieces
left
working
on
those,
and
we
have
a
issue
queue
full
of
things
that
we'd
like
to
add
that
include
more
in
closer
integration,
with
project
module
again
having
usage
statistics
for
things
would
be
great.
We
need
to
then
once
we
get
the
user
statistics
display
them.
That
piece
isn't
built
yet
either.
A
Now
that
we
have
much
of
something
some
layouts
is
working
on
a
single
sign-on
solution
with
github,
so
that
people
who
want
to
create
a
counselor
backdrop
and
have
a
github
account,
can
push
a
button
to
do
that,
and
people
who
don't
have
a
github
account
and
still
want
to
join
vector
community
can
create
an
account
without
needing
that
joint
blinking
functionality.
And
then,
once
we
have
people
who
are
able
to
login
to
the
backdrop
website,
we
can
give
them
other
things
to
do
there
like
edit
their
projects.
A
If
they
are
a
module
theme
or
layout
maintainer,
they
can
do
things
like
post
information
about
sites
they're
building
into
our
showcase,
which
is
not
built
yet,
but
will
be
soon,
but
just
kind
of
give
people
a
little
bit
more
of
a
community
to
join
and
things
to
do
along
with
everyone
else.
So
I
think
that's
what's
next
on
our
agenda
for
the
flagship
website
longer
term.
We
also
want
to
do
things
like
provide
listings
and
service
providers.
Provide
job
listings
provide
an
event
calendar
all
the
kind
of
stuff.
A
That's
worked
really
well
from
the
Drupal
community.
We
should
probably
work
on
doing
for
backdrop
as
well
in
terms
of
backdrops
project
status
itself.
Obviously,
1.2
is
out.
We
are
really
excited
about
that.
There
are
a
handful
of
issues
that
we
have
noticed
after
the
release
like
little
tiny,
bugs
or
even
just
before,
where
we're
like.
Okay,
we've
done
find
a
problem.
We
need
to
now
fix
it.
A
Those
are
in
the
queue,
obviously
to
get
work
done
soon,
and
then
we
have
a
bunch
of
a
follow-up
issues
for
the
bigger
modules
that
we
put
in
like
date,
field
module
has
some
follow-up
rich
text.
Editor
has
a
lot
of
follow-up,
there's
just
things
that
we
couldn't
quite
get
into
the
initial
commit
that
we
also
want
to
add
project.
Those
are
all
on
our
agenda,
but
for
the
most
part
we
hit
all
of
our
major
milestones
for
1.2,
which
is
fantastic.
A
Rich
text,
editor
email
field,
Winkfield
date
field
even
ended
up
making
it
in
I
think
that
was
mostly
thanks
to
all
the
great
work
that
everyone
had
been
doing,
helping
us
with
writing
code
testing
things
providing
feedback,
so
fantastic
job,
everybody
I'm
getting
that
done.
So
for
one
point,
two
point:
one
she's,
probably
our
next
move.
B
Maybe
you
just
want
to
get
the
bug
fixes
while
you
transition
at
1.2,
although
really
the
experience
that
most
people
have
had
thus
far
has
been
really
pretty
positive,
email
link
and
date
all
upgrade
pretty
directly
ckeditor.
You
have
to
reconfigure
but
seems,
like
everyone's,
been
having
pretty
successful
upgrades.
Thus
far,
all.
A
Right
great,
so
that
means
that
our
next
item
is
going
to
be
one
point,
two
point,
one
right
and
right
now
the
only
things
we
have
scheduled
for
that
or
are
fixes
for
ck
editor,
there's
a
handful
of
little
tiny
bucks
that
we
noticed
in
actually
using
it
after
upgraded
or
the
girl.
You
know
this
could
be
better.
This
way
this
you
know
it
works.
A
If
you
do
it
this
way,
but
doesn't
work,
we
do
it
that
way
and
trying
to
make
it
consistent
for,
however,
people
are
going
to
try
and
play
with
things.
I
think
will
be
great
and
then,
of
course,
if
any
other
issues
come
out,
I
think
there's
a
couple
of
Drupal
security
issues
that
may
be
coming
out
next
week.
A
That
might
be
a
good
time
to
do
our
bug
fixes
if
we
can
get
them
all
in
by
the
time
we
have
security
issues
as
well,
go
out
together,
everyone
will
upgrade
and
bugs
will
go
away.
She's,
fantastic,
but
yeah.
Nothing
super
urgent
right
now,
just
a
lot
of
a
lot
of
little
things
and
the
other
one
are
there.
B
Was
kind
of
one
nasty
issue
with
Sookie
editor
that
if
you
turn
on
j/s
aggregation
and
seek
out
it
or
doesn't
show
up
on
your
note,
forms
which
isn't
great
but
I
mean
that
we
already
fixed
that
problem,
but
there
hasn't
been
a
release.
Yet
I,
don't
know
we
could
probably
hobble
along
for
a
week
without
another
release
with
that
that
issue
in
place,
but
it
would
be
nice
nice
to
get
fixed
as
soon
as
possible
is
JavaScript
enabled
by
default
argue
shin
mm-hmm.
B
Now
you
have
to
turn
on
JavaScript
aggregation
and
you
have
to
configure
ck
out
of
here
on
one
of
your
text
formats,
but
I.
Guess
it
I,
guess
out
of
out
of
box,
have
a
cookie
is
enabled
on
text
format
yeah,
but
and
if
you're
upgrading
seek
editors
and
turned
on,
you
have
to
turn
on
yourself.
So
so
so
it's
not
in
the
critical
path,
but
it
does
seem
like
a
lot
of
production
sites,
would
have
that
combination
of
jazz
reation
turned
on
and
using
seek
editor.
Okay.
A
So
it's
just
for
1.3
1.3
is
going
to
be
a
user
experience
release
and
we
have
a
bunch
of
really
big
items
that
we
want
to
tackle.
I'm,
not
sure
we're
going
to
be
able
to
get
like
field
you
I
rewritten,
by
1.3,
but
this
is
definitely
an
example
of
a
really
big
user
interface
that
we
want
to
kind
of
rethink.
Layouts.
You
I
think
we
can
get
done,
there's
a
bunch
of
little
teeny
tiny
changes
and
want
to
do
that'll,
improve
layouts
and
then
there's
a
bunch
of
little
things.
A
We
could
do
to
improve
views
as
well.
Some
of
the
issues
with
views
came
up
just
by
adding
our
new
administration
theme
and
having
things
to
be
inconsistent.
Some
of
them
are
just
things
that
we
think
that
we
could
tweak
a
little
bit,
make
it
better
and
then
there's
just
a
whole
bunch
of
little
teeny
tiny
things
that
I
think.
A
If
we
can
spend
some
time
focusing
on
user
experience
in
a
lot
of
different
areas,
we
can
make
a
big
difference
with
the
product
and
I
would
love
to
see
a
whole
bunch
of
those
getting
resolved
in
1.3.
Again.
This
is
the
kind
of
thing
where
we
don't
necessarily
have
to
eat
until
1.3
is
out
to
get
them
all
done,
I
think,
depending
on
the
scope
of
the
change,
we
could
just
say:
oh
it's
a
minor
improvement,
it's
a
terminology
change
and
just
push
them
out
one
at
a
time
between
now
and
1.3.
A
But
if
we
do
have
anything,
that's
you
know
big,
like
the
old
you
I.
That
would
probably
wait.
We'd
want
to
do
it
at
once.
So
it's
not
changing
the
experience
for
anyone
significantly
without
them.
Being
aware
that
that's
going
to
happen,
there's
a
couple
of
things
I
put
on
the
list
for
1.3
that
our
feature
equivalents,
tasks
for
Drupal
8,
so
Drupal
8
has
reworked
their
menu
administration.
I.
Think
we
can
use
the
same
kind
of
approach,
there's
already
a
Drupal
7
module
that
solves
the
problem.
A
And
then,
if
you
look
at
the
github
issue,
checker
for
1.3,
there's
a
ton
of
stuff,
that's
tagged
for
1.3
and
there's
either
experienced
issue
I'm,
not
sure
we'll
get
to
all
of
it,
but
I
think
having
a
list.
They're
saying
like
these
are
the
things
that
we
think
are
important.
These
are
the
ones
we're
going
to
work
on
is
good,
and
if
there
are
things
that
you
know
aren't
necessarily
type
of
1.3,
but
we
want
to
get
them
and
we
can
always
try
and
do
that
as
well.
A
I
think
the
more
improvement
the
better
so
we'll
see
how
that
goes.
We're
also,
even
though
this
is
specifically
focused
on
user
experience
release.
We
are
also
really
interested
in
developer
experience,
although
some
of
these
problems
are
harder
to
solve
without
breaking
api's.
So
if
you
are
getting
started
with
backdraft,
when
you're
writing
modules,
themes
or
layouts-
and
you
find
things
that
are
just
weird
about
working
with
the
software
we
want
to
know
about
it,
I
mean
we
know.
A
Drupal
has
a
bunch
of
weird
there's
a
little
weird
in
every
software
platform,
but
if
we
can
take
the
things
that
are
weird
and
make
them
intuitive
I
think
that's
good.
So
it's
one
of
the
things
are
weird
song,
as
you
can
figure
them
out
fairly
quickly
and
without
too
much
pain
and
suffering.
So,
if
there's
something
where
you're
like
what
would
make
so
much
more
sense,
it
was
just
this
way.
Let
us
know
what
that
is,
whether
it's
you
know
having
it
your
arguments
and
a
function
going
in
a
different
order.
A
We
can
write
a
rapper
function
for
that,
try
and
make
that
more
intuitive
or
if
it's
just
like
hooks
that
don't
work
the
way
you
expect
them
to
just
explain
what
your
anticipated,
what
you
expected,
what
actually
happened
and
if
you
have
an
idea
of
how
to
make
that
less
confusing
for
people
who
are
new
to
back
job
or
people
are
coming
to
that
trip
from
Drupal
we'd
love
to
hear
about
it.
If
we
can
fix
it
in
the
1
dot
x
version.
A
Well,
if
not
we'll
think
about
a
solution
that
might
work
for
two
dots,
so
definitely
trying
to
make
it
easier
to
warm
this
software
and
every
Thursday.
After
this
meeting
we
have
a
little
sprint
where
we
all
try
and
work
together
on
backdrop
issues
we
hang
out
in
our
IRC
channel,
which
is
come
back
up,
the
fire
see,
isn't
your
thing.
You
can
also
hang
out
with
us
on
Twitter
backdrop:
dms
is
our
hashtag.
A
We
also
have
a
reddit,
which
is
ready,
tom,
/,
r,
/
backdrop
and
hopefully,
in
the
near
future,
we'll
be
able
to
have
a
place
for
people
to
communicate
or
collaborate
on
backdrop,
CMS
network
as
well
for
now
we're
using
primarily
to
github
issue
queue
as
a
place
for
everybody
to
get
together
and
work
on
things
same
time.
So
if
you're
interested
in
working
on
backdrop
and
have
some
time
on
thursday
afternoons,
you'll
find
a
lot
of
communication
with
a
bunch
of
other
people.
A
In
the
backdrop
community,
but
a
lot
of
us
are
there
most
of
the
time
anyway.
So
if
you
only
have
time
to
work
on
backdrop
on
weekends
or
evenings
or
first
thing
in
the
morning
on
a
Tuesday,
that's
perfectly
fine.
You'll
probably
get
answers
to
your
questions
and
responses
to
to
your
work
within
a
short
amount
of
time.
Anyway,
we
do
have
a
number
of
upcoming
events.
A
If
you
are
interested
in
finding
out
what
our
meeting
schedule
is,
there
is
I
cal
feed
of
that,
but,
generally
speaking,
we
have
this
meeting
every
thursday
at
noon
and
then
every
other
week
we
have
a
design
meeting.
Just
before
that,
oh
sorry,
design
meetings
at
noon,
this
means
at
1pm
those
times
are
California
time.
A
So,
if
you
are
not
California
time,
we'll
have
to
do
that
or
you
saw
a
cow
feet
which
will
adjust
automatically,
and
we
also
have
a
couple
of
upcoming
back
upper
fence
and
we
have
ical
feed
for
that
as
well.
In
the
near
future,
we
have
the
Pacific
Northwest
Drupal
summit,
which
is
in
early
October
October
10
through
12.
We
have
the.
A
A
There's
also
sand
camp,
which
I
think
is
the
same
weekend
as
drupalcamp
Utah,
which
is
a
little
unfortunate.
You
have
to
choose
between
ski
or
sand,
but
not
not
so
rough
really
and
then,
if
you
guys,
are
attending
a
drupal
events
that
you
know
are
going
to
be
open
to
having
people
talk
about
backdrop,
let
us
know
I'll
put
them
on
this
calendar.
If
anybody
wants
to
give
a
talk
on
backdrop
at
any
upcoming
events,
let
us
know
we'll
throw
that
on
our
calendars.
A
Well,
we
definitely
want
to
try
and
keep
all
the
information
about
where
anyone
can
go
to
hear
about
backdrop
as
up-to-date
as
possible.
At
some
point
we
all
decide
being
in
our
own
batch
of
events
instead
of
using
Drupal
events,
but
I
feel
like
as
long
as
triple
seven
is
relevant
backdrop
and
Drupal.
7
are
almost
the
same
thing
and
it
would
be
good
to
keep
all
people
together
collaborate
and
share
ideas
across
both
platforms.
So
we'll
just
see
when
people
feel
like
we
need
more
backdrop
specific
stuff.
A
We
can
start
moving
that
way
too
for
now.
I
think
we're
fine
continuing
to
work
with
Drupal
events
as
long
as
the
drupal
event.
Organizers
are
happy
with
that.
So
I'm
speaking
of
drupal
events
triple
around
barcelona,
I
think,
is
next
week.
So
I'm
not
sure
if
any
of
you
are
disappearing
for
a
week
for
that
event,
but
that's
supposed
to
be
really
exciting.
Spain
is
beautiful.
This
time
of
year,
so
happy
travels,
so
anyone
who's
going
a
little
sad
we're
going,
but
next
year
we'll
go
to
Europe
it'll
be
great
all
right.
A
Let's
see,
we
still
have
a
article
on
backdrop
CMS
in
Drupal
watchdog,
although
there
is
a
new
triple
watchdog
coming
out
very
shortly,
so
you'll
have
to
be
looking
for
back
issues
after
that,
and
then
let's
see,
if
anyone
has
anything
else,
you
know
about
where
you
are:
writing
a
blog
post
about
backdrop
or
watching
a
video,
and
you
think
people
should
know
about
it.
Let
us
know
we
can
throw
that
up
here
too.
So
we
talk
about
it
every
we
can
get
more
information
out
there
for
most
people,
but
that's
it.
A
Wes
is
dog,
wanted
to
come,
say
hi,
but
all
right.
Well
again,
thank
you
to
everybody
who
put
in
so
much
hard
work
on
backdrop.
1.2
I'm
really
proud
of
it.
I
love
working
with
backdrop.
It
makes
me
really
happy
so
happiness
for
all.
Alright
I'll
see
you
all
on
IRC
and
on
github
thanks
for
turning
guys
bye.