►
From YouTube: Backdrop CMS weekly meeting 10/15
Description
Weekly check-in on Backdrop CMS
A
Right
we're
on
air.
It
is
Thursday
October
15th.
This
is
our
last
backdrop
status
meeting
before
bad
camp
and
the
backup
set,
which
is
next
Thursday,
so
pretty
get
very
excited
about
that
really
quickly
to
go
through
our
standard
general
announcements.
The
first
and
most
exciting
is
that
dragon
t-shirts
and
hoodies
are
now
available.
If
you
go
to
backdrops
a
mass
to
org,
slash
contribute,
you
can
see
examples
mock-ups
of
what
each
will
look
like
they're
being
printed
as
we
speak,
and
we
should
be
able
to
go
and
pick
them
up
any
day.
A
Now,
if
you
want
to
pick
yours
up
in
person,
that's
totally
fine.
T-Shirts
are
going
to
be
given
away
for
free
to
contributors.
Hoodies
were
expecting
a
fifty
dollar
donation
to
cover
our
printing
costs
of
all
the
supplies
and
then
there's
a
little
bit
in
there.
That
gets
kicked
back
to
backdrop
as
well.
If
you
aren't
going
to
be
a
bad
camp
and
you
still
want
a
t-shirt
or
hoodie,
you
can
make
a
donation
in
that
cost
will
include
your
shipping
costs.
A
A
If
somebody
house
would
be
willing
to
do
a
show-and-tell
differences
between
drupal,
7
and
backdrop,
we
would
love
it
if
anyone
has
any
sites
they
built
and
want
to
do
a
show
and
tell
on
what
they
particularly
loved
about
backdrop
or
just
walk
through
the
site.
What
it
does
features
they
were
able
to
get
implemented.
Anyone
who
is
upgraded
from
Drupal
7,
we
would
love
to
hear
about
we're.
Just
going
to
kind
of
the
whole
thing
will
be
very
loose
in
terms
of
format.
A
A
We
also
had
a
request
from
the
organizer
of
drupalcamp
Utah
in
February
to
find
a
speaker
who
will
talk
about
back
dress.
So
if
anyone
wants
to
go
to
Utah
in
February
and
get
some
excellent
skiing
in,
let
us
know
we
can
put
you
in
touch
with
the
organizer
of
that
camp.
Send
an
email
to
info
backdrop,
CMS
technician
also.
We
still
have
free
phpstorm
licenses
for
backdrop,
contributed
developers.
B
B
Cms
org,
I
also
and
e
sincera
wanted
to
give
you
a
shout
out
whether
or
not
you
were
going
to
be
here
not
but
the
issue
in
which
a
claw
nose
just
called
out
and
said
I
don't
know-
maybe
maybe
Andy
will
come
over
and
porch
responsive
favicon
for
us
and
then
the
next
comment
was
here's
the
response
of
favicons
module.
But
it
is
pretty
awesome.
B
So
thanks
for
doing
that,
we
really
don't
expect
you
to
port
every
module,
but
but
it's
still
pretty
awesome
on
when
that
sort
of
thing
happens.
So
it's
also
great
to
see
the
speed
at
which
you
can
port
stuff
is
just
really
pretty
phenomenal.
So
thanks
again
for
doing
all
that
work,
let's
see
so
we
have
39
total
contributed.
B
Authors
Gore
has
applied,
as
of
today,
of
course
been
participating
with
us
in
the
cork
you
for
a
while,
but
he
has
ported
bootstrap
to
Drupal,
which
I
think
is
the
theme
I'm,
not
really
sure,
but
with
the
way
themes
and
layouts
go
it's
a
little
bit
interesting.
The
way
things
work
so
we're
working
on
some
things
he's
also
really
interested
in
making
it
so
that
layouts
can
have
classes
on
them
which
would
really
facilitate
the
use
of
bootstrap,
because
bootstrapped
is
entirely
all
class-based.
B
A
The
kid
with
the
maintainer
of
the
bootstrap
module
mark
Carver
in
the
Drupal
or
kiss
you
Q
about
some
of
these
same
things
and
I
think
he
has
a
pretty
strong
idea
of
how
to
get
that
working
and
is
interested
in
doing
the
backdrop
port,
so
I'm,
not
sure,
of
course,
working
with
Mark
or
not
already
addressed
most
of
these
issues,
so
we
might
be
having
it
multiple
issue
queue.
Our
first,
which
is
kind
of
exciting
for
people
working
on
stuff,
is
definitely
better
than
less
but
a
multiple
issue.
B
Yeah
I'll
bring
that
up
in
his
application
because
he's
he
started
he's
already
ported
the
module
and
has
put
it
up
somewhere
and
is
asking
for
review.
But
there's
a
couple
of
issues
already
like
it
didn't
didn't,
make
an
enjoyable,
seven
history,
things
like
that
which,
if
mark
decides
to
participate
over
in
the
backdrop
linked
to
I'm
sure
he
would
appreciate
having
all
these
attributions
all
in
place,
and
it
also
makes
merging
between
the
drupal
project
and
the
backdrop
project
lot
easier
if
that
history
stuff
so
yeah,
okay,
I'll
bring
that
up
in
that
issue.
B
Let's
see
so
there
are
39
total
contributed
authors
if
you'd
like
to
join
the
backdrop,
contribute
to
make
it
so
that
you
can
get
your
ported
or
new
modules
and
themes
up
on
backdrop.
Cms
org,
then
visits
github.com,
/
backdrop
dash
off
/
contributory
that
we
use
mostly
just
for
an
issue
cute
to
go
through
the
process
of
reviewing
the
application
for
a
module
and
then
once
you're.
In
the
backdrop,
contributor
of
you
can
create
modules
and
themes
and
layouts
willy-nilly,
but
so
it's
a
one-time
approval
process
which
isn't
very
strict
at
all.
B
Ok
on
to
infrastructure,
desks
so
infrastructure
desks.
Let's
see,
we've
had
this
update,
checking
on
backdrop,
CMS
daughter
work
for
a
long
time,
but
we
keep
talking
about
it
every
week
because
we're
not
accruing
usage
statistics
correctly
right
now.
I
realized
somebody.
Somebody
I
should
actually
say
it.
As
her
home
goal,
I
filed
a
ticket
against
project
module,
saying
may
mention
that
the
number-crunching
script
was
broken,
but
I
can't
find
an
issue
and
I
felt
kind
of
bad
that
we've
been
talking
about
this
for
weeks
and
I
hadn't
actually
made
an
issue
anymore.
B
That
problem
is
a
really
gnarly
one
to
solve,
because
you
have
to
have
usage
data
in
order
to
test
that
it
crunches
correctly,
and
so,
if
you're
interested
in
working
on
that
project,
send
an
email
to
info
at
Mac
drop.
Cms
organ
will
get
you
a
dump
of
the
database
of
backdrop
CMS
to
work
before
we
ran
the
number-crunching
script,
the
first
time,
because
now
it's
it's
getting
truncated
all
the
time,
but
we
have
a
bunch
of
usage
numbers
that
we
can
test
on,
need
to
get
that
problem
fixed.
B
So
that
would
be
great
to
have
a
volunteer
for
that.
But
it's
it's
not
terrible,
but
it
would
be
nice.
It
would
make
it
so
that
we
could
sort
projects
by
the
amount
of
times
that
they're
installed
the
usage
rather
than
just
sorting
them
by
I.
Think
it
was
the
time
that
were
created
as
the
current
sort
order
right
now,
which
isn't
isn't
ideal.
B
Let's
see
a
project
browser
we're
hoping
possibly
in
the
next
release
that
you
will
be
able
to
find,
as
well
as
install
modules
directly
from
within
backdrop,
without
needing
to
visit
backdrop,
CMS
org
and
that's
called
project
browser
and
project
browser
server
project
browser
server
is
actually
up
and
running
on
backdrop,
CMS
org
and
you
can
download
the
control
a
project
browser
from
github
and
try
it
out.
It
actually
works
really
pretty
well
there's
some
issues
with
the
way
project.
B
Browser
server
is
set
up,
not
the
module
button
in
bankruptcy,
messed
up,
orgs
implementation
of
project
browser
server
and
again
like
if
we
had
usage
statistics
that
could
make
a
return
results
more
useful
by
storing
them,
in
the
order
of
which
you
know
most
popular
modules.
First,
let's
see
Usher
backdrop,
man.
This
is
one
of
our
oldest
longest
issues.
B
We
really
love
to
have
drush
work
on
backdrop
to
make
you
said
you
could
do
you
know
address.
She
see
all
address,
install
backdrop,
drush
dl,
all
of
those
things
that
were
used
to
using
brush
for
we've
kind
of
been
slumming
it
for
over
a
year
now,
without
any
command
line
tool
for
doing
those
things
we
have
a.
B
We
know
we
have
some
scripts
like
we
have
the
ability
to
install
backup
from
scripts,
there's
installed
on
SH
and
run
tests,
Sh
a
couple
other
ones,
but
those
alucard
scripts
now
forming
people
are
familiar
with
them
in
the
first
place
and
they're,
just
not
very
versatile.
So
there's
been
some
work
on
getting
that
extra.
A
lot
of
work
getting
dressed
working
for
backdrop,
but
it's
still
not
quite
functional
genet.
You
know
the
the
latest
I
yeah.
A
Think
that
what
he's
got
going
on
is
that
the
Josh
he's
running
is
falling
back
to
a
Drupal
site,
and
so
he
thinks
it's
working,
because
all
the
commands
are
returning
the
right
responses,
but
I
don't
think
it
is
actually
working
because
I
followed
his
exact
setup
instructions
and
it
does
not
work
for
me.
I've
asked
him
specifically
about
a
couple
of
the
issues
that
I've
run
to
run
into
and
he's
kind
of
ignored
the
questions.
So
I
don't
know
if
it's
just
that.
A
A
If
you
could
take
a
look
at
his
recommended
solution
and
see
if
you
can
get
that
working,
I
shredded
doesn't
work
for
me
I,
but
I
do
have
time
set
aside
to
work
with
Greg
Anderson
this
week,
this
coming
week
at
bad
camp
to
sit
down
next
to
each
other
and
figure
out,
like
some
of
the
things
that
he
has
committed
to.
The
latest
version
of
Josh
should
be
working
and
I
haven't
been
able
to
get
those
working
either.
A
So
there
could
be
an
issue
with
my
setup
as
well,
so
I
think
having
more
people
try.
This
thing
out
would
be
really
valuable,
so
the
issue
we're
at
right
now
is
that
we
use
a
database
connection
string
like
Drupal
6.
If
we
tell
Josh
that
backrub
is
your
bull
seven,
it
will
look
for
a
database
array
and
it
won't
find
one.
So
we
basically
need
to
use
the
database
connection
style
of
Drupal
6,
plus
all
the
other
things
of
Drupal,
7
and
so
short
term.
A
But
what
we
want
to
do
long
term
is
going
to
abstract
it
out
into
a
backdrop
thing
where
it'll
say
hey
if
its
back
trap,
then
you
use
this
style
of
day
of
these
connections
storing
in
this
title
of
other
stuff,
but
we
need
to
kind
of
figure
out
what
the
right
processes
for
doing
the
tricking
into
making
think
at
making
Josh
think
the
backdrop
is
Drupal
7
and
then
also
into
doing
the
overrides
once
a
thing
since
seven.
How
do
we
then
over?
A
A
Comment
number
Oh
me
just
throw
this
issue
in
the
queue
is
triple
I
from
commercial
in
the
chat.
But
this
is
this
one:
child
a
1
comment
where
he
said
he
just
added
the
string
version,
which
I
don't
think,
is
a
good
idea,
because
we
don't
want
gerbil
modules,
fun
and
that's
joining
and
thinking
that
it's
running
Drupal
7.
A
But
if
we
can
confirm
that
adding
that
gets
Josh
working,
then
I
think
that
we
can
add
it
not
in
backdrop,
but
in
our
rush
class
for
backdrop
and
then
that
way
that
would
only
exist
when
you're
running
Josh
commands
and
loading
system
backdrop
itself.
So
we
just
need
to
figure
out
if
that
actually
works
and
if
so,
where
to
put
it
I
have
Mabley
good.
So
everybody.
A
So
we
latest
change
to
the
website
was
adding
the
addition
of
the
modules
and
themes
and
layouts
pages.
We
have
some
follow-up
issues
on
those
two
just
involve
some
more
development
tasks,
so
that
we
can
have
tools
to
implement
the
rest
of
our
design,
and
that
includes
things
like
making
sure
that
our
update
update
data.
A
What's
that
called
update
status
data,
is
aggregated
and
counted
correctly,
so
that
we
can
do
things
like
display
that
information
on
the
page.
We
need
to
get
the
information
correct,
but
then
we
also
need
to
build
integration
with
views
or
solar
or
whatever
it
is
we're
going
to
use
sort
render
those
pages.
So
there
are
some
development
tasks
there
as
well.
The
next
step
will
be
allowing
people
to
login
to
the
backdrop
website,
we're
hoping
to
give
people
kind
of
a
way
to
join
the
community.
A
A
So
we
will
eventually
figure
that
out
that's
kind
of
next
next
on
our
radar,
and
then
we
also
like
would
also
like
to
set
up
a
showcase
site
so
that
anyone
who
can
log
into
the
website
can
post
sites
that
they've
built
they
should
be
able
to
post
themselves
as
a
service
provider.
So
people
can
find
service
providers
we'd
like
to
include
our
events
calendar.
Even
though
Google
cow
feeds
are
fun,
we
would
a
central
location
where
anyone
can
add
any
event
to
the
calendar.
A
Job
listings,
all
the
stuff-
that's
worked
really
well
for
the
Drupal
community
should
be
duplicated
in
backdrop
lanes
as
well,
so
well
we'll
get
to
those
all
right
back
drop
the
product.
Our
next
release
is
one
point,
two
point:
three
just
kind
of
an
exciting
number:
oh,
don't
have
anything
urgent
that
is
demanding
a
release
date
for
that
release,
but
as
we
get
bug
fixes
we'll
put
them
in
and
then
when
they're
ready,
we
will
kind
of
release.
A
We
have
a
new
version
of
Drupal
out,
so
we
need
to
backport
the
fixes
that
got
into
gerbils
for
7.40
to
make
sure
that
those
get
into
the
next
version
of
as
well.
It
looks
like
we
don't
have
an
issue
yet
for
that
on
metro,
but
we
can
create
one
today
and
get
like
going.
That's
a
great
thing
to
you
know
we
just
got
a
couple
of
Raymond,
it's
time,
porting
over
some
patches
from
triple
decker.
Oh
this
is
nice,
quick,
easy,
generally
painless
task,
yeah.
B
I
also
wanted
to
interject
here
that
it's
exciting
7
dot
40,
which
is
also
just
kind
of
an
incredibly
high
number
that
there
been
40,
might
be
releases
of
Drupal
7.
But
it's
a
relatively
minor
release
like
there's,
nothing
really
serious
in
there
and
I
think
actually,
there's
only
like
well
I
guess
actually,
there's
like
20
25
issues
in
there,
which
is
pretty
small
as
far
as
Drupal
really
Cisco,
but
one
of
our
patches
that
we
started.
In
the
backdrop,
q
actually
made
it
into
that
version
of
Drupal,
which
is
kind
of
exciting.
B
There
are
a
lot
of
people,
but
not
quite
in
the
same
way
that
we're
looking
at
it,
because
we're
changing
a
lot
more
things
than
Drupal
7.
So
we
kind
of
how
we
approach
things
with
a
little
bit
more
Liberty
and
in
Drupal
8
land,
not
a
lot
of
people
are
using
people
ate,
and
so
we
run
into
all
of
these
triple
8
feature
problems
with
this
particular
they
would
seek
a
editor
that
we
r
cross
violent
back
to
cheerful.
B
So
we
are
getting
a
lot
of
collaboration
that
way
and
it's
actually
been
nice
to
get
because
the
Drupal's
larger
community,
we
get
validation
faster
over
there
to
make
it
so
that
we
feel,
like
it's
good
for
backdrop,
to
go
ahead
and
implement
it
in
there
and
then.
Finally,
like
the
review
process,
takes
long
and
drupal
what
we're
seeing
some
of
those
get
back
in
the
triple
now,
which
is
exciting.
B
A
B
A
B
A
So
backed
up
1.3
is
so
to
come
out
on
january
fifteenth,
and
this
is
our
first
usability
release,
we're
focusing
mostly
on
cleaning
up
all
the
fancy
new
features
they
have
added
recently
and
doing
some
other
significant
improvements
just
to
make
the
product
more
powerful.
I
think
one
of
the
things
that
were
dressed
is
really
well
as
its
focus
on
user
experience
and
having
a
whole
entire
release
devoted
to
it.
I
think
it's
going
to
help
as
kind
of
clean
up
some
of
our
dirty
edges
a
little
bit
and
make
them
more
polished
product.
A
So
I'm
really
excited
about
it.
A
couple
of
things
we
have
scheduled
for
that.
Our
follow-up
issues
related
to
layouts,
which
we
kind
of
created
a
Minimum,
Viable
Product
and
put
it
right
in
we
know.
There's
a
bunch
of
boats
will
get
to
those
will
get
them
cleaned
up
to
be
great.
We've
got
a
same
thing
for
rich
text
editor.
We
got
a
new
feature.
We
got
it
in,
there's,
definitely
a
bunch
of
polish.
We
can
add
there,
so
we've
got
follow
ups
as
well.
A
We
have
a
bunch
of
leftover
issues
and
that
were
modules.
Like
that
moved
into
Drupal
8
that
we
also
needed
to
evaluate
moving
into
back
Jeff,
we
got
someone
half
done
things
like
getting.
All
of
our
administration
listings
changed
into
views.
We've
got
one
left.
The
comment
list
needs
to
be
converted
to
a
backdrop
of
you
and
backdrop
as
well.
We've
got
some
really
really
hard
tasks
like
let's
evaluate
the
field
UI
and
see.
A
A
I
think
what
we
should
do
is,
as
we
find
these
issues
will
tag
a
handful
of
them
1.3
and
well.
We
can
just
depending
on
the
craziness
of
the
of
the
issue.
If
those
get
done
before
1.3,
they
can
go
in
any
of
our
bug
fixed
releases.
If
it's
something
as
crazy,
it's
like
rewrite
field.
You
I,
that's,
obviously
going
to
need
to
wait
for
1.3
release,
but
we
have
so
many
little
tiny
things
that
we
can
improve
on
the
way.
I.
A
Don't
think
they
all
need
to
wait
for
1.3,
but
I
think
that
the
thought
should
be
our
focus
is
use
your
experience
until
1.3,
so
hopefully
by
1.3.
Well,
I'm
a
fantastic
better
to
use
product.
So
I'm
really
looking
forward
to
focusing
on
some
of
the
little
things
for
a
while,
since
1.3
is
a
user
experience,
improvement
release,
we've
started
also
thinking
about
features
that
we
want
to
add
in
1.4,
so
this
will
be
in
May
of
25
2016
and
currently
the
first
thing
on
that
list
is
getting
references.
A
A
The
reference
to
feel
different
governments
so
I
think
well,
we'll
try
and
figure
out
how
to
get
there
and
I
think
giving
us
until
May
is
a
great
plenty
of
time
to
do
it.
So
just
definitely
you
guys,
as
you're
building
sites
in
backdrop,
keep
in
mind
the
features
you
find
yourself
using
over
and
over
again,
if
you
think
you're
installing
one
module
on
every
single
site,
it
starts
to
feel
like
eighty
percent
use
case,
not
as
candidate
forming
into
core
I,
have
until
May
to
get
those
done.
A
So
what
we
need
to
start
thinking
about
what
ones
on
that
list
so
I
think
thinking
gadson,
let
us
know
other
things,
we're
always
working
on
our
developer
experience
issues.
So
if
you're
working
on
yeah
redirect
would
be
great
actually
redirect
so
sorry
Jeff
just
mentioned
reader
apps,
we
have
I,
don't
I,
don't
know
this
too,
probably
even
get
into
1.3.
A
We
have
a
plan
for
how
to
make
global
redirects
happen
all
the
time
like
it's
a
small
improvement,
it's
not
necessarily
a
feature
edition,
but
something
as
crazy
as
redirect
module
that
has
its
own
interface
and
its
own.
You
know
integration
into
node
forms
that
might
need
to
be
a
1.4
soil
thing.
We
can,
let's
evaluate
that's
a
good
candidate,
though
it's
a
good
idea.
Okay,
developer
experience
issues
as
you're
working
on
building
sites.
A
If
you
find
something
is
not
intuitive
or
hopefully
hard
too
time-consuming
create
an
issue
we're
trying
to
make
the
experience
of
developing
code
for
backdrop
easier.
We
need
to
identify
the
pain
points
and
try
to
figure
out
how
to
solve
them.
Not
all
of
these
things
can
be
solved
in
the
one
dot
actually
cycle,
but
as
they
move
our
API
changes
that
it
would
be
good
to
note
them
so
that
when
we
start
thinking
about
we're
going
to
do
a
20
x,
we
can
think
about
what
are
the
most
important
things
for
changing.
A
So
keep
those
tag
them
on
github
with
square
brackets
DX
and
we'll
pull
them
every
Thursday.
We
usually
do
a
little
sprinting.
We
meet
together
an
IRC
channel,
found
backdrop
we're
chatting
in
add
the
github
issue
queue
as
well.
That's
where
most
activity
is.
We
also
have
a
reddit.
So
if
you're
not
into
IRC
and
you're,
not
on
github,
you
can
chat
people
on
reddit
as
well.
We
are
eventually
going
to
open
up
the
backdrop
website
if
you
subs
another
place
to
try
and
figure
out
how
to
facilitate
communication
a
little
bit
more
easily.
A
So
hopefully
we'll
have
more
avenues
for
communication
and
collaboration
here
in
the
future.
Thursday
afternoons
are
great
day
to
work
on
backdrop,
because
there
are
a
bunch
of
other
people
working
on
backdrop,
but
if
you
can't
work
on
backed
up
on
Thursday
and
can
on
any
other
day
of
the
week,
that
is
just
fine,
we'll
take
what
we
can
get
upcoming
events,
I'm,
not
sure
if
anyone
here
attended
the
Pacific
Northwest
gerbil
summit,
but
I
heard
that
it
ended
up
being
on
canadian
thanksgiving
just
a
little
bit
unfortunate,
probably
affected
their
turnout.
A
So
not
not
so
great
I
heard
the
people
that
were
there,
I
had
a
really
good
time.
I
talked
to
a
couple
that
heard
a
lot
of
great
sessions
and
a
lot
of
fun
people
which
is
what's
important
but
haven't
gotten
any
other
more
specific
feedback
on
it.
Bad
camp
is
next
week
we
talked
about
that
a
little
bit
already.
Drupalcamp
Ohio
is
the
same
weekend
as
bad
camp.
There
efecto
friendly
event
triple
camp
Mexico
is
November
fifth
through
seventh.
A
B
A
And
then
drupalcamp
utah
is
the
same
weekend.
Is
stand
camp
in
February
2016.
So
if
anyone
else
has
any
events,
they
are
planning
on
attending
or
want
to
be
added
to
the
backdrop.
Events,
calendar,
email
them
to
info
5dr,
see
mr.
burgundy,
we
added
or
you
can
+
in
the
IRC
or
similar,
we'll
figure
it
out
publicity.
The
new
version
of
Drupal
watchdog
is
out.
A
I've
got
500
copies
here
since
when
he
wouldn't
want
one,
let
me
know,
but
that
means
that
the
backdrop
article
featured
story
is
no
longer
than
the
latest
version
after
wash.
I
get
is
in
the
previous
version
of
triple
watchdog,
so
I
took
that
off
of
our
publicity
list
here.
Most
important
thing,
I
think
for
us
right
now
is
to
harp
about
how
awesome
our
dragon,
hoodies
and
t-shirts
are
going
to
be
so
definitely
try
and
find
yourself
for
this
all
right.
Is
there
anything
else?
B
Mentioned
this
in
the
in
the
design
call,
and
they
need
to
mention
it
again
that,
because
literally
one
week
from
today
is
the
backdrop
summit
at
fat
camp
in
berkeley
lot
of
bees,
we
won't
be
having
a
weekly
status
meeting
next
week.
So,
if
you're
in
berkeley,
we
would
love
to
see
you,
we
will
be
there
in
person
chatting
all
day
long,
a
day-long
meeting
of
backdrop
and
where
we
located
in
we're.
A
That's
the
same
place
as
the
non
summit,
so
I
figured
that
would
be
a
great
kind
of
overlap
of
audiences,
we're
actually
going
to
be
in
the
bar
area,
they're,
going
to
turn
into
classroom
style
seating
for
us,
so
they'll
have
a
little
projector,
so
we
can
do
a
bunch
of
little
talks,
but
the
bar
opens
at
four
thirty
and
all
of
the
nonprofit
people
will
start
flooding
in
shortly
after
that.
So
we
can
go
to
chat
and
tell
them
about
how
amazing
the
backdrop
some
it
was
and
yeah
make
friends
bro.
So.