►
From YouTube: Backdrop CMS weekly meeting 6/4
Description
Check-in on Backdrop CMS development + infrastructure tasks.
A
All
right
we
are
on
air,
it
is
thursday
june
4th
happy
summer.
Everyone
it
feels
like
summer,
we're
just
gonna.
Do
a
quick
review
on
tasks
for
currently
we're
working
on
for
backdrop,
cms
project
related
and
infrastructure
related
we've
got
a
couple
of
announcements.
We
usually
start
the
meeting
with.
We
have
php
storm
licenses.
A
Another
quick
announcement
I
just
wanted
to
mention
is
that
in
the
last
two
weeks
or
so
nate
and
I
set
up
backdrop
cms
as
a
project
on
drupal.org,
specifically
for
the
purpose
of
granting
commit
credit.
So,
while
we're
working
on
issues
that
are
getting
resulted
in
backdrop
that
have
not
yet
been
resolved
in
drupal,
you
can
mention
like
not
only
who
you
are,
that
usually
gets
commit
credit
or
issue
credit.
A
If
you're
just
adding
comments,
you
can
still
get
credit,
but
also
you
can
mention
like
which
client
you're
working
for,
and
I
think
we're
gonna
start
referencing
backdrop
when
we're
working
on
issues
that
backdrop
is
solving
and
we're
converting
back
to
the
drupal
community.
So
if
anyone
else
wanted
to
start
doing
that,
you're
definitely
welcome
to
do
that.
The
way
that
process
works
on
dribble.org
is
a
little
weird
and
they
mentioned
it
might
require
some
documentation.
A
I
don't
think
we're
planning
on
documenting
that,
so
just
because
it's
dribble.org,
I
don't
think
we
should
be
writing
documentation,
that's
a
little
weird,
but
if
you
want
to
use
it
feel
free
to
play
with
it
figured
out.
So
we
have
an
organization
there.
It's
merely
for
recording
things.
The
backdrop
is
contributing
back
to
dribble.
A
We
have
a
section
in
this
weekly
meeting
where
we
usually
do
updates
from
the
pmc
for
the
last
few
weeks,
our
like
php
storm
license
announcement
has
been
on
that
section,
but
that's
really
turned
into
kind
of
like
a
general
announcement.
We
get
every
week,
it's
not
significantly
important,
so
we
don't
have
any
serious
updates
from
the
cmc
at
this
time,
but
as
things
come
up
that
need
to
be
resolved,
we
will
use
this
time
in
the
meeting
to.
A
A
B
B
In
this
past
week,
we've
had
four
new
contributed
projects
added
to
the
github
group,
which
is
amazing.
Several
of
those
are
related
to
a
couple
of
those
are
related
to
project
browser
which
is
really
exciting,
some
new
functionality
that
we're
hoping
to
get
into
core.
Eventually,
there
are
47
current
projects
with
official
releases,
and
whenever
you
make
an
official
release
on
github,
it
will
automatically
create
a
project
node
on
back.cms.org,
and
we
don't.
B
We
have
35
total
members,
in
the
backdrop,
contributed
author
group,
but
there's
another
one,
another
application
in
the
queue,
and
somebody
sent
me
an
email
today
saying
that
they
imported
census
module
and
so
that
person
will
also
be
applying
shortly.
I
believe
so,
it's
great
still
just
you
know
real
steady
progress
in
our
community
growth.
Our
existing
members
continue
to
port
new
modules,
kind
of
on
a
weekly
basis,
which
is
fantastic
and
and
we're
getting
new
people,
so
all
really
fantastic
on
the
growth
side.
B
So
next
up
infrastructure,
we
like
to
talk
about
all
the
things
about
backup,
cms
that
we're
working
on
building
out
to
support
the
project.
The
first
item
on
this
list
is
update.
Checking
so
update
checking
makes
it
so
that,
when
a
new
version
of
a
module
comes
out,
update,
module
notify
your
site
of
the
new
version
of
that
module.
B
B
B
So
I'm
going
to
go
and
look
at
that
actually
after
the
meeting
and
check
if
check,
if
we're
accruing,
how
many
sites
are
out
there
that
are
running
each
module,
that
has
an
official
release
which
is
great
josh
for
backdrop.
I
haven't
checked
in
on
this
recently
jen.
Do
you
have
any
idea
what
the
progress
is
on
dress.
A
I
haven't
also
checked
on
anything
since
last
week,
but
I
know
that
khalid,
it's
like
his
number
one
issue
in
terms
of
things
that
are
not
yet
perfect
with
backdrop
yet
so
I
think
there
are
some
other
people
who
are
getting
involved
in
that
right
now
I
don't
know
jeff.
If
you
looked
into
that
recently
too,.
B
Okay,
so
status
of
josh,
pretty
much
the
same
as
it
has
been,
that
is
that
drush
has
been
adequately
abstracted
the
latest
version
of
josh
so
that
we
can
use
it
with
backdrop.
It's
just
that
we
need
to
write
a
backdrop
drush
class
that
makes
it
so
that
drush
can
execute
all
the
commands
using
backdrops
functions
and
methods
instead
of
drupals.
B
B
If
you
have
drush
the
latest
version
and
you
toggle
over
to
a
backdrop
site,
it
should
work
straight
up,
so
you
can
use
the
same
version
just
for
both
your
drupal
7
7
sites
and
your
backdrop
sites
pretty
great
okay.
Moving
on
our
flagship
primary
website.
Backdrop
cms.org,
as
I
mentioned
earlier,
we're
currently
working
on
building
out
the
find
a
module,
find
a
theme
and
find
the
layout
listing
pages
as
well
as
individual
module
theme.
A
B
B
Eventually,
service
providers
like
people
that
provide
hosting
or
people
that
provide
development
services
and
also
a
jobs
website.
But
all
of
those
things
are
all
kind
of
peripheral
right
now,
as
we
as
we
build
out
the
basic
infrastructure,
then
we'll
get
to
those
things
as
as
we
have
time
so.
Next
up
the
upcoming
release
timeline,
the
next
version
of
backdrop
minor
or
sorry
bug,
fixing
release
will
be
1.1.2,
the
release
of
which
is
to
be
determined
right
now.
B
We
have
four
issues.
Four
main
topics
that
we'd
like
to
build
in
the
main,
one
of
which
is
the
rich
text
editor
or
a
wysiwyg,
is
our
primary
thing
for
1.2
and
besides
those
we
also
have
adding
in
a
bunch
of
fields
that
right
now
are
in
contrib
and
we'd
like
to
move
them
into
court,
including
date
link
and
email.
B
The
most
recent
update
I
posted
to
that
issue
issue
101,
is
that
we
have
a
bunch
of
stuff
lots
of
progress,
all
of
the
functionality
of
attaching
an
editor
and
the
editor
settings
have
been
merged
into
the
filter
module,
so
the
filter
module.
When
you
configure
a
format,
you
also
configure
an
editor
which
makes
it
exactly
like
drupal
8,
except
that,
unlike
dribble
8,
it's
not
a
separate
module.
It's
all
just
directly
in
part
of
filter
module.
B
B
So
it's
a
it
reduces
our
complexity
quite
a
bit
because
in
triple
eight
we
had
to
have
editor
module
menu,
alter
and
form
alter
and
had
to
do
a
whole
bunch
of
altering
in
order
in
order
to
work
with
the
filter,
module,
and
it
just
seems
like
that's
an
unnecessary
separation
in
triple
eight
land.
We
ended
up
compromising
to
make
some
people
happy,
but
in
backdrop
blends,
we
can
just
go
directly
with
the
simple
routes
and
put
them
all
together.
B
So
filter
module
has
now
editor
capability.
Ck,
editor
version
4.4.7
is
in
the
pull
request.
It's
not
actually
in
the
poll
request,
but
it's
in
the
branch.
Let's
see,
there's
a
ck
editor
module
that
actually
exposes
the
ck
editor
library.
You
can
configure
the
toolbar
using
a
drag
and
drop
interface.
B
B
If
you
didn't
include
the
image
tag
in
the
list
of
allowed
tags,
but
you
dragged
in
the
image
button,
then,
when
you
went
and
looked
at
the
editor
on
the
front
end,
the
image
button,
sorry
yeah,
the
image
button
actually
wouldn't
show
up
at
all,
because
the
image
tag
isn't
allowed.
So
the
editor
won't
show
buttons
for
tags
that
aren't
allowed.
So
there's
an
integration
there
that
zq
editor
understands
what
the
limitations
of
the
formatting
or
filtering
system
are
and
won't.
Let
the
editor
allow
any
tags
that
aren't
specified
in
the
filter.
B
B
And,
finally,
we
need
to
make
it
so
that
when
you
update
the
toolbar
like
if
you
drag
in
the
image
button-
and
that
should
automatically
add
the
image
tag
down
below
so
basically
the
complement
to
ck
editor
understanding
the
filtering
system.
We
also
need
to
have
the
administrative
interface
for
configuring.
An
editor
have
the.
A
B
B
Anyway,
lots
of
lots
and
lots
of
issues
in
the
wysiwyg
area,
but
they're
coming
along
very
nicely:
let's
see
the
other
ones,
the
fields
date
module,
link,
module
and
email
module.
I
think
we
have
contribute
versions
of
all
three
of
those
modules
and
the
task
of
moving
them
into
core
will
be
a
matter
of
trying
to
figure
out
how
we
do
an
upgrade
path
and
if
we're
going
to
trim
any
features,
what
features
should
actually
be
trimmed
moving
them
directly
into
core
has
a
couple
of
problems
that
it
will
introduce
if
we
reduce
features.
B
So
we
need
to
evaluate
what,
if
anything,
we're
going
to
remove
okay,
so
that's
it
for
the
1.2
release,
where
we're
hoping
to
be
by
september
or
several
months
away,
so
there's
a
good
chance
that
we
may
get
all
of
that
stuff
done,
which
would
be
fantastic,
let's
see
other
things
besides.
What's
on
the
road
map,
we
always
have
the
continuous
stream
of
issues
that
are
just
kind
of
coming
in
and
we're
fixing
them
as
we
encounter
them
as
well
as
enhancements
whenever
we
can
just
to
improve
the
overall
experience
in
backdrop.
B
Let's
see
so
sprint
today
is
thursday,
sorry
about
the
becker
knife,
but
today's
thursday
and
every
thursday
is
backdrop
day.
We
usually
have
sprints
in
which
we
hang
out
in
the
irc
channel,
found
backdrop
and
we
work
back
and
forth
and
try
to
get
as
many
issues
scheduled
as
possible,
so
I'm
usually
around
on
thursday.
So
this
gen,
I'm
usually
reviewing
pull
requests
as
they
come
in
and
jen
is
usually
coordinating
people.
B
If
you're
looking
for
a
particular
issue,
you
can
give
lampton
a
ping
in
ifc
and
she
will
help
you
find
an
issue
that's
suited
to
your
talents,
upcoming
events
for
backdrop.
We
maintain
a
calendar
of
all
backdrop,
meetings
and
events
as
they
happen,
which
you
can
access
from
the
agenda
document
for
this
meeting,
but
upcoming
events
that
are
happening
in
the
very
near
future.
We
have
drupal
camp
colorado
june
20th
through
21st,
twin
cities,
dribble
camp
june,
25th
or
28th
looks
like
we're
typing
in
another
one
drupal
north
june
25th
through
28th.
B
B
A
Actually,
the
colorado
colorado
agenda
is
up,
they've
got
a
schedule
and
we're
on
it,
which
is
good,
okay
and
I'm
pretty
sure
we're
in
for
twin
cities,
though,
that
hasn't
been
posted.
Yet
they
did
send
some
follow-up
questions.
So
that's
a
good
sign,
and
just
just
about
upcoming
events
like
there's
starting
to
be
so
many
of
them
on
our
backdrop,
calendar,
which
is
amazing
that
maybe
we
should
mention
them
all
in
this
meeting
every
week,
just
because
it's
going
to
be
hard
to
keep
it
on
on
keep
it
up
to
date.
B
A
B
One
thing
I
do
want
to
mention,
because
I'm
really
excited
about
it
and
it's
not
on
this
list
yet
is
july
12,
I
believe,
or
maybe
the
13th.
We
received
an
invitation
from
an
event
that
says
basically
the
science
organizations
behind
the
national
science
foundation,
noaa
and
nasa
are
really
interested
in
using
backdrop,
as
you
may
know,
all
three
of
those
organizations
currently
use
drupal
for
their
website
and
they
are
interested
in
continuing
the
support
of
those
websites,
perhaps
by
using
backdrop
for
the
future
version.
B
B
Nothing
at
all,
nothing
at
all,
okay.
Well,
I
do
want
to
welcome.
We've
got
a
lot
of
people
in
this
meeting.
This
is
this
is
fantastic,
welcome,
janelle
and
paul
to
our
weekly
hangouts
paul.
I
know
he
interned
with
us
last
year
actually
and
he's
back
from
college
this
summer
and
is
going
to
be
working
through
the
issue
as
much
as
possible
and
it's
fantastic
to
have
him.
Have
him
back
from
school
and
yeah
yeah,
yeah,
yeah,
podca
and
that's
that's
all
I've
got
so.