►
From YouTube: Backdrop CMS weekly meeting 9/3
Description
Weekly check-in on progress for the Backdrop CMS project.
A
All
right,
we
are
on
air,
happy,
September
everybody.
It
is
September
third
Thursday
back
draft
day
and
we're
just
going
to
do.
A
quick
review
of
items
need
to
be
covered
for
backdrop
for
community
and
backed
up
the
project.
Knee
is
feeling
a
little
under
the
weather
today,
so
we
won't
be
joining
us,
but
hopefully
he
doesn't
have
measles
or
some
horrible
I
have
to
Rick
related
illness.
I.
Think
I'm
gonna
know
what
it
is.
He'll
be
fine,
alright,
so
a
general
announcements.
As
usual,
we
have
phpstorm
licenses
for
backdrop
contributors.
A
So
if
you
are
working
on
backdrop,
contributed
projects
send
an
email
to
envelop
backdrop,
CMS
org,
and
we
can
send
you
a
license.
Those
are
good
until
februari
I'm
thinking
about
reaching
out
to
the
phpstorm
folks
and
seeing
if
we
can
get
a
batch
of
new
ones
that
are
good
for
a
year
again,
instead
of
just
a
few
months
now
that
we're
running
out
of
year
here,
so
those
will
be
a
little
more
useful
to
people.
A
We
also
have
been
contacted
by
the
organ
errs
organizers
of
drupal
camp
Utah,
which
is
in
February
2016,
and
they
don't
have
anybody
in
their
small
community
who's
working
with
backdrop
yet,
but
they
want
someone
to
speak
on
backdrop
at
their
camp,
so
they've
reached
out
to
us
and
said:
please
make
announcements
and
let
anyone
know
that
we
do
have
scholarships
available.
We
can
fund
up
to
five
hundred
dollars
towards
your
travel
and,
if
you're
sent
by
a
company,
they're
happy
to
be
tell
us,
your
company
is
a
sponsor
on
their
camp
website.
A
They
also
wanted
everybody
to
know
that
Utah
has
the
world's
best
skiing
and
they're
here.
If
you
wanted
to
do
a
little
trip
in
Florida
or
Florida
in
February
and
get
some
skiing
in
that
might
be
really
fun
things
to
come
by,
but
the
drupalcamp.
So
what
you're
thinking
hats
on
to
what
you
want
to
be
doing
next
februari
and
if
you
think,
you're
going
to
need
a
little
break?
That
might
be
a
fun
thing
to
do.
We
have
no
updates
from
the
pmc.
A
This
week
seems
two
things
seem
to
be
business
as
usual,
but
in
the
community
growth
area,
we've
had
a
ton
of
activity.
In
the
last
week
we
have
146
total
projects
for
backdrop.
Those
are
there's
five.
Anyone
since
last
last
week,
which
is
pretty
exciting
and
we
have
71
projects
on
backdrop,
CMS
org
and
there
are
nine
new
ones
since
last
week.
So
I
think
it's
a
combination
of
a
couple
things
I
know:
Andy
you've
been
pouring
like
crazy,
which
is
fantastic.
A
I
started
a
client
project,
ripe
importing
a
bunch
of
modules
as
well,
but
I
think.
The
biggest
thing
is
that
that
we
got
the
modules,
themes
and
layouts
pages
up
on
backdrop,
CMS
org
and
so
people
who
had
projects
wanted
to
start
creating
official
releases
so
that
they
would
appear
there
so
I
think
that's
why
we
have
nine
new
releases,
all
of
a
sudden
which
I
think
is
very
exciting,
so
good
job
thanks
for
helping
get
those
done.
A
A
I
did
find
a
couple
of
little
issues
and
I
think
we
should
sort
those
out
before
we
make
an
official
release,
but
we
basically
cleaned
up
two
or
three
problems
with
layouts
and
two
or
three
problems
with
the
theme
and
I
think
so
far
it's
looking
fantastic,
so
that
should
be
imminent.
Getting
getting
those
up
there,
sometime
too
soon
too
so
I'm
very
excited
about
that.
A
We
still
have
38
backdrop,
pinch
of
authors,
but
I,
know
we've
gotten
a
couple
of
new
people
in
the
last
week,
because
people
have
been
emailing
via
our
website
asking
about
where
to
find
documentation
and
how
to
port
modules
and
stuff,
like
that,
so
I'm
hopeful
that
we
will
have
a
couple
of
new
applications
here
in
the
near
future.
So
thank
you.
A
Everybody
for
giving
back
drop
a
shot,
and
until
we
have
all
the
processes
clearly
outlined
using
the
contact
form
is
great
because
that'll
help
us
figure
out
where
we
need
to
add
more
documentation.
Yeah
I
contacted
Arshad,
asking
him
to
create
official
release
and
he's
like
do
you
have
any
documentation
on
how
to
do
that
and
I
was
like.
A
Actually
we
don't
that
could
be
used
while
we
talk
about
in
this
meeting
every
week,
but
if
you
miss
Anita
you're
out
of
luck,
so
I
added
a
new
page
on
the
API
site
that
talks
about
how
to
make
official
release
for
your
project
since
I
tried
to
do
at
night
at
it
wrong
like
that's,
definitely
something
we
need
to
get
out
there
publicly
available.
Hopefully,
that'll
help
people,
okay,
infrastructure
tasks,
so
we
have
update,
checking
working
for
vector
of
CMS
and
there's
a
couple
of
follow-up
tests.
A
If
we
end
up
shipping
with
a
bunch
of
these
fields,
modules
enabled
it
would
be
nice
to
know
if
people
are
using
them
or
not,
and
that'll
help
us
inform
decisions
in
the
future
about
whether
things
should
be
added
or
removed
from
core
cuz
we're
trying
to
meet
the
majority
use
case.
So
we
need
some
numbers
to
know
what
our
majorities
are.
I
went
ahead
and
created
a
couple
of
new
issues
this
week.
A
On
the
backdrop,
CMS
org
issue
queue
for
all
of
the
remaining
items
that
we've
been
talking
about
in
this
weekly
meeting,
so
that
if
anyone
wants
to
kind
of
jump
in
on
practicing
musta
org
stuff,
there's
a
nice
list
for
that,
we
don't
have
to
rely
on
these
Google,
Docs
and
so
special
feature.
Checking
for
project
usage
is
issue
number
99
over
there.
I
also
added
issue
number
98,
which
is
something
up
charting
and
that's
something
it's
not
going
to
be
super
useful,
but
I
really
really
like
the
charting
that
they
have
on
drupal.org.
A
That'll,
show
you
project
usage
over
time
as
well
as
charts
on
issues.
So
you
can
say
how
many
issues
are
active
and
how
many
issues
are
closed
and
don't
give
you
an
idea
of
how
much
work
is
getting
done
on
the
module
and
how
often
so
I
think
you
know,
as
as
we
start
collecting,
that
data
will
start
to
have
something
that
it
will
be
more
interesting
to
model
and
chart
in
overtime.
I
would
love
to
get
that
charts
solution
integrated
so
that
we
can
see
that
in
backdrop
as
well?
A
Actually
it's
a
week
in
half
I
would
love
to
get
that
in
these
or
experience
release.
I.
Think
it's
going
to
make
a
bit
were
a
really
big
difference
for
back
job
and
I
also
wanted
to
mention
that
I
think
this
is
probably
a
good
move
for
us
long
term.
If
we
can
adopt
a
pattern
of
doing
to
future
releases
and
then
a
user
experience
release
and
that
way
we
can
kind
of
all
always
stay
on
top
of
making
sure.
A
As
many
user
experience
issues
get
attention
as
new
features
because
some
of
the
times
the
new
features
are
adding,
are
really
big
and
really
hard,
and
that
means
that
all
of
our
focus
goes
into
something
like
getting
rich
text
editing
in
core
and
we
miss
up
the
little
things
and
I
think
if
we
can
have
a
couple
of
releases
where
we
focus
on
the
big
things
and
then
one
where
we
focus
on
all
the
little
things.
It'll
help
make
sure
that
we
kind
of
create
a
better
product
long
term.
So
I've
been.
A
A
We
just
forgot
about
it
because
we're
busy
working,
not
a
text,
editing
and
I-
know
that
there's
a
lot
of
stuff
like
that
in
Interpol,
into
where
there's
just
so
much
going
on
it's
hard
to
keep
track
of
everything,
so
I
think
having
specific
user
experience
releases
is
going
to
be
huge
for
us.
Okay,
so
little
little
divergence
there
at
back
to
things
we're
working
on
for
infrastructure.
Jesh
is
something
that
I
took
over
a
couple
weeks
ago.
A
I
got
it
half
working
I
got
a
kind
of
working
to
the
point
where
I
figured
out
why
it
wasn't
working.
So
it
does
some
things.
It's
able
the
bootstrap
backdrop,
but
I
can't
get
it
to
run
any
of
its
commands
like
glaring
caches
or
anything.
So
I'm
gonna
spend
a
little
bit
more
time
on
that.
I
have
now
that
I'm
building
sites
with
backup
I
am
experiencing
the
pain
of
not
having
to
rush,
and
so
I'm
definitely
looking
forward
to
getting
that
working
today.
A
So
I
can
get
back
to
using
it
tomorrow,
so
that
should
be
fun
and
or
have
a
plan.
I
just
need
to
actually
cut
to
it.
Our
flagship
website
backdrop
CMS
org
currently
has
modules,
themes
and
layout,
so
people
can
find
them
there,
which
I
think
is
great.
We
have
a
couple
of
follow-up
issues
based
on
adding
those
in
the
last
few
weeks.
One
of
them
is
trying
to
clean
up
our
top
level
navigation.
We've
gotten
feedback
from
a
couple
of
different
people
that
it's
a
little
bit
weird,
to
have.
A
A
top-level
item
like
handbook,
followed
by
a
top-level
item,
called
modules
and
there's
not
a
lot
of
explanation
as
to
what
modules
is
and
why
it's
top-level
item.
So
what
we're
thinking
about
doing
is
adding
a
drawer
just
like
the
handbook
hazard
or
where
you
can
click
on
something
like
extend
backdrop
and
that'll
slide
out
and
then
in
there
you
can
see
all
of
the
categories
where
we
can
extend
backdrop
like
module,
seems
layouts
and
potentially
in
the
future.
We
could
have
distributions
for
libraries
or
whatever
other
things,
end
up.
A
People,
people
end
up
creating
for
backdrop
and
I
hope
kind
of
organized
the
site
in
a
way
where,
yes,
modules
are
really
important,
but
having
them
in
some
kind
of
context
might
be
useful.
So
I
think
we
even
have
an
issue
are
patching
the
queue
no
chair,
digipak
there's,
definitely
an
issue
in
the
queue
and
there's
some
screenshots
about
how
it
should
look
and
work
in
some
discussion
going
on
over
there
and
I
think
that's
going
to
be
a
good
improvement.
I'm
not
sure
we'll
get
that
done
by
the
time.
A
1.2
comes
out,
but
we'll
see,
I
think
it'll
be
nice
because
we'll
have
a
flurry
of
activity
of
people
watching
at
one
point
to
it.
When
it
comes
out,
it'll
be
great
to
get
that
primary
navigation
and
play
back
by
then
two
other
plans.
We
have,
for
the
backdrop
website
include
setting
up
a
showcase,
so
people
can
show
off
the
sites
are
building
with
backdrop
adding
a
services
listing,
so
you
can
find
companies
or
people
who
are
building
you,
websites
or
modules
or
whatever
it
is.
A
You
need
for
backdrop,
designs,
information,
architecture,
training,
what
everything
Drupal
has
fractured
beloved
Julie
also
need,
and
we
need
a
place
where
people
can
say
that
they're
interested
in
doing
those
things.
So
we
should
set
that
up.
We
also
would
like
to
do
a
jobs
system.
Much
like
drupal
has
a
job
somewhere.
If
you
have
a
Drupal
job
or
you're.
Looking
for
someone
to
hire
other
way
around
looking
for
a
job,
we
could
post
them
all
in
a
central
location,
I
think
initially,
we
won't
be
charging
for
that.
Like
jiggle,
that
work
does.
A
It
was
just
kind
of
make
it
a
little
more
crystal
style,
but
still
having
providing
that
service.
I
think
would
be
really
useful
to
people
and
also
events
calendar
so
that,
rather
than
having
to
subscribe
to
a
knife
alfie
to
find
out
what
events
you
can
go
to
to
learn
more
about
backdrop.
We
can
just
list
all
of
those
events
directly
on
our
site
and
in
order
to
get
people
to
do
things
like
post
their
websites,
post
their
jobs
and
post
events
they
might
be
hosting.
A
We
need
to
also
let
people
log
in
to
the
primary
backdrop
website
so
before
we
get
to
any
of
that,
we're
also
going
to
add
single
sign-on
with
github,
and
then
people
will
be
able
to
use
the
accounts
that
are
teasing,
forget
hub
click,
a
button
on
the
back
drop
site
and
get
in
really
easily.
But
if
you
aren't
a
developer
and
you
don't
have
a
github
account,
you
can
also
create
an
account
like
you
would
normally
do
on
a
triple
network
or
anywhere
else,
and
that
way
it'll
least
feel
like
people
are
joining
something.
A
So
you
we
can
start
to
kind
of
create
the
sense
of
community
by
joining
our
official
website,
which
I
think
is,
is
not
to
be
overlooked
in
terms
of
getting
our
community
going
to
so
more
fun
stuff
coming
for
our
website
in
the
future.
A
A
I
think
we
should
try
and
get
those
fixes
there's
another
another
issue
here:
queued
up
for
the
next
release,
which
is
a
bug
in
backdrop,
set
message
being
missing
from
admin
pages
and
that's
because
we
removed
the
system
settings
form
that
used
to
do
that.
For
us
and
but
I
think
we're.
You
know
nothing
here
is
so
horrible.
We
need
to
do
it
today
and
get
it
out
there
any
security
releases
anyway.
A
This
is
this
should
all
be
in
line
for,
let's
get
all
these
in
and
get
them
done
before
1.2
and
then
include
all
those
in
1.2
and
there's
nothing
super
horrible,
that's
hard
to
fix
everything
anything
here.
It
even
has
a
pull
request,
so
that's
fantastic
and
then
we
have
for
1.2.
The
built-in
rich
text
editor
is
in
the
follow
up.
Issues
for
inline
images
is
also
in
so
we
are
looking
really
good
for
inline
image
handling
in
rich
text,
editing,
which
is
really
exciting,
I've
been
using
on
this
I.
A
I
know
they're
a
bunch
of
low
follow-up
issues
on
user
experience,
like
don't
tell
people
to
enter
HTML
tags
at
the
HTML
tags,
they're
going
to
be
entering
are
going
to
be
escaped
and
printed
as
HTML,
instead
of
as
though
text
they
want
to
see,
but
I
think
those
are
all
pretty
minor.
Any
of
those
could
go
in
after
1.2
great
we
get
the
men
before,
but
it's
not
a
blocker
in
any
way.
The
email
field
module
is
also
looking
really
good.
A
We
have
a
final
full
request
that
several
of
us
have
reviewed
and
it
looks
fantastic
I
think
it's
ready
to
be
committed
and
can
go
in
anytime.
The
link
field
module
slightly
more
complicated
than
email
field,
I
think
it's
also
looking
really
good
and
a
couple
people
tested.
It
also
seems
to
be
working
as
expected.
I
have
both
of
those
modules
in
use
also
getting
turned
over
to
content
creators
next
week.
A
This
is
a
bunch
of
little
tiny,
minor
things
that
need
to
be
updated.
In
addition
to
ripping
out
all
of
the
stuff
we're
not
supporting
like
there's
some
date
repeat
stuff
built
right
into
date
that
we
don't
need.
If
we
don't
update,
repeat
and
then
once
we've
got
all
of
that
ready,
I
think
we're
going
to
need
some
more
extensive
testing
on
dates
for,
for
so
that
is
looking
a
little
iffy
for
1.2,
but
it's
pretty
close,
so
I
think
you
know
with
everything
else
being
kind
of
done
already.
A
A
However,
if
date
does
not
make
1.2,
we
can
definitely
push
that
to
1.3,
even
though
it's
supposed
to
be
user
experience,
release
I
think
getting
date
in
there,
because
it's
already
almost
done
is
not
going
to
be
a
lot
of
work.
I
think
it'll
be
fairly
straight
forward
to
just
say:
okay,
any
more
review,
or
we
need
to
fix
this
problem
where
we
need
to
fix
the
texts
or
whatever
it
is
and
get
it
scheduled.
A
There's
a
couple
of
other
little
things
that
are
currently
slated
for
1.2,
that
are
minor
user
experience,
things
that
I
think
will
be
great
if
we
could
get
in
there
stuff
like
adding
transliteration
to
core.
If
we
don't
get
them
and
it's
not
gonna
be
the
end
of
the
world.
I
would
much
rather
put
our
effort
into
getting
date
in
and
we
could
add
things
like
transliteration
and
redirect
module
functionality
and
stuff
like
that,
could
go
in
1.3
as
well,
so
there's
stuff
that's
currently
earmarked
for
that
milestone
that
we
may
not
get
to.
A
But
it's
not
mission-critical.
So
if
you
really
are
passionate
about
redirect
functionality,
you
can
do
that
and
they'll
get
in.
If
not
that's
fine,
okay,
so
issues
for
1.3-
and
these
are
just
what
we
currently
have
on
the
list
and
there's
a
whole
handful
of
layout
follow-ups
that
include
clean
the
user
experience
adding
some
features
that
were
not
included
in
the
initial
for
of
layouts,
making
sure
that
we
get
stuff
like
a
field
block
that
would
represent
any
fields
on
any
entity
type
that
we
could
drop
into
any
region.
That
would
be
great.
A
There's
a
workaround
right
now,
I'm
using
vuze
right.
You
can
build
a
view,
the
pulls
out
of
field
and
drop
it
in
that's
totally
fine,
but
I
think
if
we
could
provide
that
utility
without
making
people
build
that
view,
that
would
be
huge.
So
that's
also
kind
of
user
experience
related,
so
we'll
get
all
of
those
in
then
we
also
have
our
rich
text,
editor
follow-up.
So
anything
we
don't
get
to
for
1.2,
we'll,
try
and
get
in
in
1.3
and
then
there's
a
handful
of
little
modules.
A
The
triple-a
didn't
had
included
in
core
that
I
think
back.
Jeff
also
wants
to
get
in
things
like
cleaning
up
the
menu
administration.
You
I
things
like
making
sure
all
of
our
admin
pages
are
using
views,
and
these
are
things
that
we've
all
kind
of
started
on
in
backdrop.
I
think
will
be
nice,
just
kind
of
wrap
them
up
and
get
them
done.
Also,
things
like
adding
transliteration
module
decor
would
fit
in
really
nicely
with
that
too.
A
If
we
don't
get
it
in
in
1.2,
I've
also
added
a
couple
of
things
to
the
1.3
milestone
that
have
been
bothering
me
as
a
site
builder
and
I
would
recommend
if
anyone
else
is
going
through
the
same
thing
as
you're
building
websites
and
you're.
Finding
things
were
like,
oh
you
know,
that's
always
bothered
me
in
Drupal
I'd
like
to
see
that
cleaned
up
in
backdrop
and
add
a
comment
in
the
issue,
queue
saying
you
want
it
to
be
added
to
the
UX
milestone
and
we
can
put
them
all
in
there.
A
I
think
it'll
be
good
to
have
everything
in
the
milestone
and
then
kind
of
evaluate
like
okay,
which
of
these
are
most
important
and
then
definitely
prioritize
those
work
through
those
once
we
start
getting
to
1.3
and
then
have
all
the
other
ones
be.
You
know
nice
to
haves,
and
if
we
get
done
with
what
with
the
top
of
the
list,
we
can
move
through,
the
bottom
so
definitely
open
to
feedback
on
those
as
well
so
user
experience
issues.
A
We
should
document
figure
out
why
it's
weird,
how
to
make
it
less
weird
and
if
any
of
those
changes
can
be
included
for
the
current
version
of
backdrop
without
API
change,
I
think
we
should
prioritize
those
as
well.
You
know,
Wes,
you
created
a
whole
long
list
of
things
that
are
really
weird
when
creating
themes,
sometimes
they're
just
bugs
operation
fix
them.
Sometimes
there's
just
weird
things.
A
In
our
theme
system,
I
noticed
that
too
I
was
working
on
trying
to
get
a
pre
process
function
for
a
theme
hook,
suggestion
to
run
without
a
template
for
the
theme
of
suggestion.
Then
that
made
me
really
grumpy,
because
I
didn't
need
a
different
template
file,
but
in
order
to
get
the
reprocess
function
to
run
you
needed
it.
That
was
one
of
my
fixes
for
radix
and
I
was
like.
Why
isn't
it
working
and
I
just
realized
that
that
was
just
a
weird
thing
about
how
a
backdrop
works.
A
That
might
be
something
that
we
could
fix
now,
just
by
inserting
a
function
call
in
a
different
place
to
say
hey,
you
know
if
the
theme
of
suggestion
is
available
run
the
process
function,
even
if
there's
no
template
file
but
we'll
see,
there's
also
a
performance
implications.
Doing
stuff
like
that,
so
may
need
some
benchmarking,
but
I.
Think
noting,
where
those
things
are
annoying
is
very
important,
because
everybody
who's
new
to
backdrop
is
going
to
run
into
them
to
everybody
who's
coming
back
from
from
Drupal
has
this.
A
You
know
idea
of
tools
that
they
use
and
if
the
tools
don't
work
right,
I
mean
even
if
they
didn't
work
right,
drupal,
that's
something
we
can
improve
and
I
think
we
should.
We
should
focus
on
getting
that
as
good
as
we
can,
at
least
in
the
Bois
de
X
version
zipping
right
through
this.
We
also
have
sprints,
if
you're
interested
in
working
on
any
of
the
issues
we
talked
about
today
or
other
issues
that
are
bother
you
more
than
the
things
we
talked
about
today.
We
did
a
little
sprint
every
Thursday
afternoon.
A
After
this
meeting,
we
also
are
going
to
be
doing
some
sprints
at
some
upcoming
events.
There
is
the
nerd
summit,
which
is
coming
up,
we're
going
to
try
and
stick
around
lots
for
a
day
and
get
people
working
on
back
up
there
as
well.
Anyone
doing
any
other
Sprint's
want
us
to
know
about
it.
Let
us
know
we
can
throw
it
in
this
meeting
agenda
and
talked
about
it
in
the
future
too,
but
Thursday
afternoons
in
general.
A
If
you
join
us
an
IRC
in
our
Channel
pound
back
trap,
we're
often
they're
chatting
about
working
on
different
things
in
Bactra.
We
also
have
a
read
it
if
I
or
C
isn't
your
thing,
and
hopefully
in
the
future,
we'll
get
people
communicating
on
dr.
TMS
org
in
one
way
or
another,
not
sure,
yet
how
that's
going
to
work,
whether
it's
forums
or
something
else,
but
we'll,
try
and
make
it
easier
for
people
who
aren't
uber,
nerds
hangout
chat
with
us
as
well.
Speaking
of
upcoming
events
at
drupalcamp
LA
was
last
weekend.
A
I
was
really
sad.
We
weren't
able
to
make
it
there,
but
it
was
success.
Looked
like
at
least
from
Twitter
like
there
are
a
lot
of
people,
a
lot
of
great
talks,
I'm
looking
forward
to
looking
at
some
of
them
on
video
and
they
get
posted.
We
have
the
Pacific
Northwest
Drupal
summit,
which
is
coming
up
in
just
over
a
month.
A
We
have
bad
camp,
which
is
two
weeks
after
that,
with
our
first
backdrop,
summit,
just
going
on
october,
twenty
second,
if
you're
interested
in
giving
a
talk,
let
us
know
we
are
currently
working
on
getting
some
cool
backdrop
schwag
together
for
that.
So
if
you
weren't
planning
on
coming,
you
might
change
your
mind
when
you
see
our
adorable
dragon
stuff,
so
that'll
be
really
fun.
We've
got
drupalcamp.
Ohio
is
also
that
same
week.
I'm
not
sure.
A
If
there's
a
way
we
could
work
together
with
the
backdrop
some
it's
tough,
but
I
know
we're
going
to
try
and
get
some
collaboration
between
drupalcamp
ohio
in
fact
camp
in
other
ways.
So
if
they're
doing
anything
on
thursday,
that
might
be
fun
set
up
a
hangout
or
something
in
work
with
ibis,
all
alright
I
think
that's
it
for
today.
Unless
anyone
has
any
other
questions
or
comments.
A
Sorry
Nate
couldn't
be
here.
I
think
I
said
he
wasn't
feeling
super
well,
but
we
are
totally
on
track
for
the
upcoming
release
and
very
excited
about
telling
everyone
about
1.2
with
rich
texting
core.
So
I'm
gonna
go
ahead
and
drop
off
a
call
then
and
I
guess
you
can
see
you
guys
and
I
are
seat
thanks
everyone
for
joining
today
and
for
those
of
you
watching
at
home,
and
for
this
we
watch
later
so
happy
Thursday
hi
everyone.