►
From YouTube: Backdrop CMS weekly meeting 7/23
Description
Check in on Backdrop CMS progress.
A
We
are
going
live,
it
is
Thursday
july,
twenty
third
and
we're
doing
a
quick
check
in
on
backdrop,
CMS
and
all
the
awesome
stuff
that
we're
working
on
as
usual.
We
still
have
three
phpstorm
licenses
for
backdrop,
contributed
developers.
So
if
you
are
working
on
porting,
a
module
or
army
interested
in
maintaining
a
module
or
a
theme
or
lay
up
and
want
to
try
phpstorm,
we
have
licenses
that
are
good.
I
think
until
next
March,
so
I'll
definitely
give
you
a
little
jumpstart
on
those
licenses
or
the
software.
B
It's
been
a
little
bit
of
a
quiet
week.
We've
had
one
new
module
added
to
the
contributory,
no
new
contribute
at
this
point.
But
if
you
are
interested
in
watching
these
hangouts
regularly
and
you
haven't
taken
the
time
to
to
submit
a
contributed
module
application,
I
would
highly
encourage
anybody.
That's
interested
to
make
a
post
to
backdrop.
Ops,
/
contribs
go
for
if
you
ordered
a
module
and
you
would
like
to
move
into
the
official
github
group
repository-
let's
see
but
totals
wise.
B
We
do
have
a
lot
of
great
integrations
already
so
that
when
you
publish
a
new
project
on
github,
it
synchronizes
with
backdrop
CMS
org
and
when
you
make
new
releases
that
checks
in
with
the
mothership
of
backdrop,
CMS
org,
to
notify
all
existing
backdrop
installations,
that
new
version
of
your
module
is
out
or
a
new
version
of
backdrop.
Cms
itself
is
out
so
that
stuff
is
all
coming
along
I.
That
means
all
it's
all
there
and
it's
all
works
really
well.
B
A
project
browser
is
some
functionality
that
we're
working
on
to
make
it
so
that
you
can
find
and
install
modules
directly
from
within
your
backdrop
website,
without
needing
to
go
to
backdrop,
CMS
org,
to
find
a
list
of
modules
or
themes
or
anything,
and
that
project
is
looking
really
good.
Client-Side
server
side,
where
we're
just
hung
up
a
little
bit
on
doing
a
little
bit
of
server
administration
work
to
make
that
so
that
it's
on
its
own
sub
domain,
so
that
we
can
federated
and
put
it
on
CDN
in
the
future,
if
needed.
So
I.
B
B
B
B
A
A
A
A
We
also
want
to
create
a
service
provider
listing,
so
people
can
find
developers
or
designers
or
web
hosts
for
back
job
and
we're
going
to
want
to
create
a
job
listing,
so
companies
can
post
jobs
and
developers
can
find
gems
designers
can
find
jobs
all
that
good
stuff
kind
of
around
the
backdrop
ecosystem.
Just
like
we
have
or
Drupal
we
wanted
to
do.
Those
and
another
thing
that
we
thought
might
be
a
good
idea,
is
to
create
a
backdrop,
events
calendar
so
in
the
Drupal
world.
A
There's
this
thing
called
droopy
cow
which
can
aggregate
all
of
the
events
and
put
them
on
a
calendar.
So
you
can
see
what's
coming
up
right
now
we
have
a
google
calendar
that
we're
manually,
adding
stuff
to
I
think
long
term.
It
would
be
great
if
we
could
have
a
place
for
anyone
to
be
able
to
post
their
own
events
on
the
primary
backup
website
and
have
them
show
up
in
a
place
where
everyone
can
see
them.
So
that's
long
term
on
our
radar
as
well.
A
So
that's
what
we
have
for
infrastructure
task
this
week
and
we
wanted
to
do
a
quick
update
on
the
project.
Again,
there
hasn't
been
a
whole
bunch
of
activity
in
the
last
week,
but
we'll
just
kind
of
go
over
upcoming
releases.
The
next
minor
release,
one
dot,
one
dot
3
is
not
yet
scheduled.
We
do
have
a
handful
of
tiny
issues.
We've
been
working
on
emerging
as
they
get
done,
but
we
don't
have
any
security
really
releases
that
would
force
that
to
be
released
soon.
A
We
don't
have
any
bug
fixes
that
we
consider
a
big
enough.
It
would
force
a
really
soon,
so
we'll
just
continue
merging
in
tiny
bug
fixes
until
we
get
something.
That
seems
like
it's
a
good
stopping
point
and
then
we'll
cut
back
up.
One
point:
one
point:
three
of
the
things
we're
working
on.
We
are
have
a
layouts
Qi
meta
issue.
Where
we've
been
getting
a
ton
of
activity
on
improving
it
and
also
much
of
feedback
on
things.
A
We
maybe
should
consider
that
weren't
already
in
that,
so
that's
great,
and
then
we
also
have
some
responsiveness,
responsiveness
issues
can't
seem
to
talk
today.
We're
back
to
out
of
the
box
is
responsive,
but
there's
a
lot
of
stuff.
That's
left
over
from
Drupal
that
wasn't
responsive
before
we
made
the
layouts
responsive
that
we
need
to
account
for
in
our
new
responsive
backdrop
world.
A
Stuff
to
our
next
major,
our
sorry,
our
next
minor
release
is
one
point,
two
point
zero
and
that
is
currently
stabbed
up
for
sep
tember
15th.
So
far,
we
are
on
track
to
include
a
handful
of
new
features,
including
my
favorite,
the
built-in
rich
text
editor.
We
haven't
been
making
kind
of
progress
as
it
was,
and
I
would
say,
probably
three
or
four
weeks
ago,
where
we
have
a
integration
with
ckeditor
included.
We
have
modal
support.
A
We
have
a
bunch
of
new
things
like
floating
images
with
captions,
which
is
something
that
WordPress
has
had
for
a
really
long
time,
the
great
if
we
could
at
least
get
prom
parable
with
that,
but
there
are
a
bunch
of
little
teeny-tiny
pieces
that
we
can
work
on
later.
So
I
think
we've
got
it
to
a
point
where
it's
a
shippable
product
and
we
can
add
integration
with
stuff
like
image
upload
in
an
iterative
pass.
A
So
I
think
we
should
merge
what
we
have
as
long
as
we
can
assume
all
tests
or
passing
and
all
the
human
related
tests
go
well
as
well.
We
should
get
that
in
soon
and
then
we
can
go
ahead
and
start
on
follow-up
tests,
like
uploading
images
and
associating
images
to
nodes
in
the
files
table
similar
things
like
that.
A
Other
things
were
working.
We've
got
ish
modules
related
to
fields
that
we
would
like
to
include
in
court
on
our
hit
list
for
backdrop.
1.2
includes
date,
fields,
simple
link
field
and
simple
email
field
and
the
date
module
as
it
is
in
contribute
a
whole
bunch
of
stuff.
We
don't
necessarily
need
to
put
in
core,
and
so
we
have
an
issue
on
which
things
should
be
included
in
which
things
shouldn't
be
included
and
started,
creating
a
poor
module
that
will
have
this
of
the
one
included
and
contribute
the
stuff.
A
We
don't
want
included,
in
course,
so
that
we
can
still
kind
of
put
the
two
together
and
get
the
comprehensive
date
module
that
we
have
today,
but
not
everybody's
going
to
need
recurring
dates
or
date,
formats
that
are
unusual
or
all
of
the
kind
of
edge
Casey
stuff.
So
we're
going
to
put
that
into
a
kind
of
a
deep,
extended
module
or
know
what
we're
going
to
call
it.
Some
other
date
module
link
field.
We
have
a
pull
request,
form
I
haven't
looked
at
it
yet,
but
that
makes
me
exciting.
A
An
email
field
is
also
fairly
straightforward
and
we
should
get
that
going
soon
as
well,
so
I
think
we're
on
track
to
get
all
of
those
things
done
in
backdrop
1.2,
and
we
should
also
start
looking
at
our
list
for
what
we
want
in
backdrop
1.3
as
well.
So
right
now,
I'm
just
going
to
take
a
look.
Oh,
it
says
I
to
be
determined,
so
we
should
start
thinking
about
if
we
want
to
add
more
field
modules.
A
This
might
be
a
good
time
to
do
it
if
we
want
to
add
more
functionality
to
the
WYSIWYG
editor,
and
that
also
might
be
a
good
time
to
add
those
in
any
other
major
features.
People
feel
are
missing
from
backdrop.
We
could
look
at
the
top
50
contributed
modules
and
see,
if
there's
anything
kind
of
a
no-brainer
for
inclusion
in
core
and
and
just
kind
of
make
sure
that
we
get
everything
that
we
need
to
be
a
suitable
alternative
to
Drupal
8,
ready
the
cast
your
plate,
but
be
out
soon.
A
Alright
other
things
we're
working
on,
and
these
are
not
necessarily
scheduled
with
things
that
we
do
all
the
time.
Our
user
experience,
improvements
and
developer
experience
improvements,
and
this
is
something
that
you
know
right
now,
our
target
audience.
Our
people
were
coming
from
Drupal
and
they're,
going
to
be
used
to
a
tool-
that's
very
similar
to
triple,
but
once
people
have
made
the
decision
to
go
to
Drupal
8
to
go
to
backdrop
to
go
to
some
other
platform,
to
throw
it
all
out
and
go
without
a
website.
A
Whatever
decision
they're
going
to
make
people
are
currently
on
Drupal
7,
once
they've
made
that
decision,
our
target
audience
needs
to
change
because
right
now
our
target
audience
is
them,
but
once
they're
gone,
we
need
to
start
trying
to
move
this
product
a
little
bit
downstream.
We're
not
going
for
the
enterprise,
that's
not
our
market.
We
are
definitely
for
the
small/medium
business.
So
we
need
to
look
at
the
other
tools
that
they're
using
see
the
kind
of
things
that
they
do
really
well
and
make
sure
that
we
do
those
things
really
well
as
well.
A
User
experience
is
something
that
WordPress
has
gotten
right
and
it's
something
that
Drupal
has
not
been
particularly
attended
to
for
a
very
long
time.
So,
there's
a
whole
bunch
of
stuff
that
we
can
improve
in
user
experience,
land
there's
a
whole
bunch
of
stuff.
We
can
also
prove
in
developer
experience
land.
One
of
the
reasons
people
used
to
come
to
Drupal
back
in
the
trip
for
56
days
is
that
it
was
lightweight
simple
and
made
sense
and
dribbles
moved
away
from
that
sort
of
mod
model.
C
A
We're
left
with
a
Drupal
7
that
was
already
not
lightweight,
simple
or
made
sense,
and
that's
our
starting
point.
So
we
need
to
kind
of
look
at
what
it
feels
like
to
be
a
new
developer.
In
the
backdrop
world
and
say
how
can
we
make
this
experience
better
for
those
people?
What
does
it
like
to
write
code
for
a
backup?
Are
there
things
that
just
seemed
really
unusual?
A
A
Issues
are
tagged
in
the
github
queue
with
you
x,
and
if
you
find
other
issues
that
you
think
are
all
related
to
a
theme
go
ahead
and
I
noticed,
people
have
already
been
doing
this
already
put
low
square
brackets
around
it,
and
then
that
way
you
can
search
for.
You
know
forgiveness
and
find
all
the
issues
with
that
tag.
Eventually,
I
think
we'll
come
up
with
some
kind
of
documentation
as
to
what
those
are.
So
it's
not
just
those
who
are
super
familiar
with
issue
kunis,
how
it
works,
but
I
think
for
now.
A
A
Note,
there's
five
hours
have
a
whole
bunch
be
working
on
backed
up
at
the
same
time,
which
is
fantastic
if
you
can
get
hours
from
your
job
to
contribute
to
working
on
backdrop.
This
is
a
great
time
to
do
it
any
other
time.
Oh
okay,
very
we
take
evenings
weekends.
Whatever
anyone
wants
to
work
on
anything,
but
you
will
get
the
most
feedback,
the
soonest
on
the
Thursdays.
A
Let's
also
have
design
meetings
that
happen,
fortnightly
so
every
other
week
and
the
next
resign
wouldn't
will
be
next
week
and
and
a
robot
eNOS
of
my
voice.
I,
don't
know
if
that's
an
Internet
and
issuer
of
my
computer's
processing
speed
issue,
but
we
are
nearing
the
end.
So
sorry
about
that
everyone.
A
We
have
a
bunch
of
upcoming
events,
let's
see
so
83rd.
Next
up
we
have
Drupal
corn,
which
is
July
thirtieth
through
august.
First,
we
have
the
drupal
camp
in
Pennsylvania,
which
is
august
1st
through
second,
we
have
drupalcamp
LA,
which
is
August
29
30th
and
drupalcamp
Costa
Rica,
which
is
july
29
through
31st.
So
that's
now.
A
Okay,
so
quest
regas
is
first
and
then
to
perform,
and
then
all
of
these
other
things,
if
you
want
to
see
a
complete
doc
drop
a
friendly
triple
thanks,
we
do
have
I
cow
feed
of
them.
You
can
find
that
I
cow
feed
on
the
backdrop
CMS
network
contribute
page.
You
can
find
it
in
our
reddit,
which
is
reddit
com,
/
r,
/
backdrop,
and
that
sometimes
will
help
you
know
what's
coming
up.
A
You
can
also
email
info,
I
factor
of
CMS
or
can
we'll
add
that
to
account,
even
if
you're
not
sure
if
it's
been
accepted
yet
go
ahead.
Let
us
know
we'll
throw
it
on
calendar.
I
guess
that's!
It
is
there
anything
that
we
should
talk
about
this
week
or
anything
that
wish
to
talk
about
weekly
in
the
future.
Thank.
B
You
I
made
a
short
note
there
at
the
top
of
the
events
section
in
the
agenda
that
we
have
been
working
on
some
reusable
slides.
Some
generic,
reusable
slides
that
has
been
adapted
from
the
toxic
Jen
and
I,
normally
give
unless
I
saw
you've
already
taken
a
look
at
that
and
that's
that's
great
I
could
come
in
and
handy
for
your
upcoming
talk
in
Pennsylvania
or
do
you
think
they'll
make
something
of
your
own
yeah.
C
C
A
lot
of
the
core
stuff,
yeah
and
I,
don't
know
if
we
want
to
just
keep
adding
to
that.
If
people
find
that
you
know
I
think
my
my
deck
is
pretty
general,
like
maybe
somebody
does
a
theming
for
backdrop,
specific
presentation
and
they
toss
it
in
there.
So
I
architected
the
repo
so
that
having
a
bunch
of
decks
in
there
would
make
sense
and
then.