►
From YouTube: Backdrop CMS weekly meeting 10/8
Description
Weekly check-in on tasks for Backdrop CMS
A
Alright,
we're
on
air.
It
is
thursday
october.
Eight,
it's
been
a
very
trouble-filled
internet
day.
We're
happy
to
be
here
really
quickly
we're
going
to
try
and
get
through
this
meeting
to
make
sure
that
the
internet
stays
up.
The
whole
time
should
be
fantastic,
general
announcements
first
and
most
exciting
order
of
business.
You
can
now
buy
your
backdrop,
Santa's
t-shirts
and
hoodies
on
the
backdrop
website.
If
you
go
to
backdrop,
CMS
org
slash
contribute.
There
are
designed
for
use
of
both
the
shirt
in
the
hoodie.
The
shirt
is
white
with
a
black
dragon.
A
The
hoodie
is
black,
almost
black,
this
color
eco
black
with
a
black
dragon.
It's
got
a
white
outline,
it's
adorable!
You
can
pre-order
both
shirts
and
hoodies
on
the
internet
on
that
page,
and
you
can
pick
them
up
in
person.
If
that
can,
if
you
can't
be
a
bad
camp
at
the
backdrop
summit
and
that
France
will
include
us
going
to
the
trouble
of
actually
mailing
it
to
you.
A
So
if
we
have
people
who
aren't
sending
from
it's
the
one
a
t-shirt
or
hurry,
you
can
buy
it
if
you
do
make
it
to
the
backdrop
summit
at
guide
camp
and
you
are
a
backdrop
contributor-
we're
going
to
give
away
the
t-shirts
to
those
people
for
free.
So
anyone
who
has
contributed
in
a
significant
way
being
active
in
the
issue
queue
counts.
You
don't
have
to
be
a
contributor
of
code.
Then
you'll
get
your
back
job
shirt
as
a
little.
Thank
you
gift
with
a
dragon
on
it.
Don't
feel
shy,
guys.
A
A
B
Checking
my
mom
okay,
so
community
grid.
So
every
week
we
like
to
talk
about
how
many
total
projects
they're
effective,
CMS
right
now
there
are
a
hundred
and
sixty-one
total
projects.
A
couple
of
new
themes
popped
up
in
the
last
week,
which
is
fantastic
to
see
those
coming
in
and
being
in
place,
I
think
actually
and
it
just
joined
in
as
in
law.
I
think
they
may
be.
The
creators
have
said
themes,
so
thank
you
guys
for
the
new
themes.
It's
awesome
to
see
see
this
popping
up.
B
We
have
39
total
members
of
the
backdrop,
contribute
if
you're
interested
in
porting
module
to
backdrop
CMS
or
writing
a
new
theme
or
making
some
layouts
or
basically
collaborating
with
the
broader
backdrop
community.
In
some
way,
then
please
apply
to
the
backup
contribute.
Is
a
github
com
/
backdrop
dash
ops,
/,
contribute
or
getting
new
members
into
the
community,
so
they
can
publish
to
the
backdrop
contribute,
let's
see
so,
let's
see,
updates
checking
for
backdrop
soon
as
we
go
into
infrastructure
from
here,
update
checking
has
been
working
for
a
long
time.
B
Let's
see
we're
also
trying
to
make
it
so
that
in
the
next
version
of
backdrop,
hopefully
you'll
be
able
to
find
and
install
modules
directly
from
the
user
interface
and
we're
doing
that
with
project
browser
module
project.
Browser
server
is
actually
already
up
on
backdrop:
CMS
org.
So
if
you
download
and
install
the
contribution
of
project
browser,
you
can
actually
use
it
right
now
with
backdrops
EMS
gorg,
which
is
pretty
cool.
B
B
A
I
haven't
checked
on
it
since
last
week,
and
last
week
we
had
one
person
that
said
that
they
got
it
working,
but
not
in
any
way
that
was
viable
for
Josh
or
backdrop.
So
I'll
check
in
on
that
today
and
see
if
we
can
look
at
how
we
can
get
it
working
in
a
way
that
we
can
commit
something
so
that'd
be
great.
B
Okay,
so
let's
see
our
primary
website
backdrop
cinestar
to
work
the
next
task
that
we
have
on
our
agenda.
Besides
things
like
usage,
statistics
are
making
it
so
that
everybody
can
log
into
the
website.
For
the
time
being,
we've
had
some
people
saying
that
they've
found
typos
or
something
like
that.
There's
dedicated
issue
queue
on
github
for
backdrop,
CMS
org
under
backdrop
dash
ops,
splash
backdrop,
CMS
org,
and
that
contains
the
code
for
backdrop.
Cms
daughter
work.
B
If
you
want
to
file
a
pull
request
against
backdrop,
CMS
dork,
you
can
do
that
to
solve
some
structural
problems
of
the
site,
but
if
it's
just
a
typo
or
something
like
that,
you
can
also
file
an
issue
there
and
those
who
do
have
logins
can
fix
it
in
the
meantime,
but
in
the
near
future,
we're
hoping
to
allow
more
users
to
be
a
log
in
to
work
more
collaborative
collaboratively
on
main
website
and
along
with
login.
We
do
want
to
have
some
kind
of
single
sign-on
solution.
B
For
a
couple
reasons,
we've
got
a
couple
of
different
websites
already.
The
API
website,
for
example,
is
a
separate
website
from
backdrop.
Cms
daughter
work.
So
we'd
like
to
make
it
so
that
you
can
login
across
those
different
environments
and
also
preferably
have
some
kind
of
github
integration,
since
a
lot
of
our
collaboration
happens
like
github,
it
would
be
great
if
people
could
use
their
kit
hub
logins
to
sign
into
backdrop.
B
B
We've
got
grand
plans
for
the
long
term,
goals
of
backdrop,
CMS
organ
cluding,
a
showcase
service
providers,
event,
calendar
jobs,
those
sorts
of
things,
but
those
are
all
kind
of
down
the
pike
by
the
time
being
really
getting
projects
analytics
and
sign.
Ons.
All
together
is
really
where
focuses
for
backdrop:
CMS
org.
B
Hello
all
right.
Well,
the
next
item
on
the
agenda
there's
something
else.
There
is
backdrops,
you
mess
the
project
and
talking
about
how
we're
proceeding
there.
So
the
next
version
of
next
bug-fix
release
will
be
backed
up.
One
point
two
point:
three
very
nice
little
number
and
we
don't
have
a
scheduled
release
date
for
the
next
bug-fix
release.
It's
basically
just
whenever
we
accrue
enough
fixes
that
we
will
make
that
new
release
right
now,
I,
don't
think,
there's
hardly
any
changes
to
the
code.
B
So
one
point
three
point:
0,
which
is
the
next
minor
release,
is
scheduled
for
January
15
2016,
and
this
is
what
we're
calling
the
UX
release
where,
instead
of
putting
in
giant
new
features
like
like
date
or
a
ticket
or
the
things
that
we've
put
in
the
last
release
or
pasado
and
in
token
like
we
did
the
release
before
that.
What
we're
really
focused
on
this
release
is
a
polishing
of
the
pieces
of
software
that
we
have
the
modules
that
we
have
and
making
it
so
that
things
like
the
layouts.
B
You
I
the
WYSIWYG
editor
things
like
that
are
a
lot
smoother,
so
we
have
a
number
of
issues
that
are
basically
like
master
issues
that
all
the
children
are
within.
There's
issue:
3
45
for
layouts
module,
and
that
includes
things
like
one,
adding
one
field
per
our
side:
one
block
per
field
and
potentially
relationship
handling
and
making
layouts
generally
a
lot
more
powerful,
a
a
lot
of
those
issues
actually
in
progress,
and
it
would
be
great
to
see
those
get
completed
before
the
next
release.
B
B
That
includes
things
like
fixing
up
the
filter
tips
to
make
it
so
like
filter
tips,
don't
mesh
with
the
concept
of
rich
text
editor,
because
it's
like
how
to
write.
Html
or
you
know,
paragraphs
are
automatically
break
and
those
sorts
of
things
just
aren't
relevant
when
you're
using
a
rich
text
editor
because
it
does
all
those
things
for
you.
So
we
want
to
flip
it
around
where
we
make
it.
So
the
interface
is
designed
for
rich
text,
editors
and
toolbars.
B
B
B
Actually,
some
of
the
work
that
Wes
has
been
doing
that
look
pretty
interesting,
because
it's
about
changing
the
way
that
you
add
a
field,
but
not
necessarily
the
way
you
edit
a
field.
It
seems
like
that's
actually
pretty
modest
in
terms
of
large
term
plans,
since
we've
got
as
in
law
here.
Also
like
his
sketches
of
like
dragging
in
fields
from
the
luck
and
palate,
would
probably
be
more
on
the
ambitious
side
of
things
so
not
to
say
that
we
can't
do
it
or
we
won't
do
that
eventually.
B
Let's
see,
we've
also
got
some
views
in
core.
We
want
to
make
it
so
that
we
convert
more
of
our
listings
to
views
right
now.
We've
got
about
like
two-thirds
of
them
converted,
but
there's
still
some
pages
that
could
be
totally
converted
out
to
views
and,
finally,
an
issue
for
simplifying
the
menu
you
I
just
making
it
so
that
we
have
a
couple
of
consolidated
pages
would
be
fantastic.
That's
issue
number
4,
75,.
B
Okay,
let's
see,
there's
a
whole
bunch
of
other
issues.
If
you
want
to
take
a
look
at
the
issues
that
are
tagged
for
1.3
point,
oh,
we
have
a
tag
for
that
on
github
and
you
check
that
milestone
for
things
that
we're
targeting.
For
the
one
point
three
point
over
these
I
don't
see.
We
just
haven't
added
in
here.
B
B
Let's
see,
we
have
tags
for
you
x,
+
DX,
on
the
issue,
queue
that
we
would
just
like
to
generally
make
improvements
on.
Although
the
next
release
is
supposed
to
be
the
UX
release,
where
we
fix
a
whole
bunch
of
these
small
lingering
issues,
there
are
some
ones
that
don't
get
brought
up
every
week
in
the
meetings,
but
you
can
just
search
for
UX
in
square
brackets
on
the
backdrop,
issue
queue
and
there's
a
whole
bunch
of
other
issues
in
there.
B
B
A
I
mean
the
most
exciting.
One
is
the
back
job
summit,
which
is
going
to
happen
on
october,
twenty
second
at
bad
camp.
But
before
that
there
is
a
backdrop
friendly
drupal
event
at
the
pacific
northwest
rupal
sun,
which
is
october
10
through
11.
At
the
backdrop
summit,
we
currently
have
a
bunch
of
oxidatively
scheduled
why
the
back
FML.
B
A
A
A
We
will
be
running
a
little
sail
area
there,
where
you
can
make
a
donation
to
backdrop,
and
you
will
receive
your
t-shirt
or
hoodie
like
this
second
link
and
obviously
featured
if
there's
ball
two,
and
if
you
are
a
contributor,
don't
buy
the
t-shirt
because
I
think
if
you
one
for
free,
unless
you
really
want
to
make
a
donation,
I
can't
a
backdrop
in
which
case
we'll
gladly
accept
it.
The
presentations
on
Thursday
will
be
20
minutes
long.
A
So
I'm
not
really
sure
if
you've
got
an
email
from
David
about
your
session
being
accepted
for
bad
camp,
it
could
be
that
a
backdrop
session
that
was
submitted
got
accepted
for
the
regular
sessions
which
on
Saturday
and
Sunday,
but
we
are
planning
on
just
doing
little
sessions
on
Thursday,
which
is
backed
up
to
their
20
minutes
each.
So
hopefully
that'll
be
like
a
teaser.
If
you're
doing
in
the
same
won
both
times,
you
can
say
here's
20
minutes,
I've
sponnish
leave
a
little
bit.
A
A
For
for
the
weekend,
other
events
that
are
coming
up
we
are
doing
drupalcamp.
Ohio
is
the
same
weekend
as
that
camp
that'll
just
be
on
the
twenty-third
and
twenty-fourth.
So
just
on
Friday,
Saturday
and
I
I
know
there
are
also
factor
friendly.
So
if
you
aren't
coming
to
California,
you
know
in
arson,
joy
to
Ohio,
that's
not
talk
to
people
about
back
up
there.
We
loved
your
booking
up
Utah,
as
mentioned
before
in
February
in
sand
camp
in
San
Diego
that
same
weekend,
so
yeah
I
mean
I.
A
A
I,
guess
that's
it
for
upcoming
events.
We
are
nearing
holiday
season,
which
means
things
will
slow
down
a
little
bit,
which
is
why
we've
got
kind
of
a
big
hole
from
October
until
februari
as
to
be
expected.
Oh
there's
else:
I
drupalcamp
Mexico,
just
kind
of
the
same
time
to
something
buddy
number
when
that
is
I
can
look
at
it.
Yeah
I!
Guess!
That's
it
in
terms
of
publicity
and
the
new
Drupal
watchdog
will
be
coming
out
soon.
I
think
it
might
have
even
come
out
for
a
Barcelona.
A
A
I've
also
been
getting
a
bunch
of
people
in
like
if
you
go
to
create
an
issue
on
drupal.org,
think
hey
current
maintainer,
so
you
interested
then
reporting
this
project
backdrop
I've
been
getting
a
lot
of
feedback
from
the
maintainer
that
they
are
interested
in
doing
it
themselves,
but
they
need
documentation
on
how
that
and
in
particular
how
to
maintain
both
about
Jefferson
in
person
and
so
I've
been
posting.
Those
links
to
that
article
written
by
David
Rothstein
on
how
to
maintain
your
projects
for
Jubal
and
packed
up
at
the
same
time.
A
I
think
that's
been
really
beneficial
for
a
lot
of
people,
so
anyone
else
runs
into
that
same
issue.
I
highly
recommend
those
three
articles.
It's
a
series
of
three
on
on
how
to
maintain
projects
for
both
it
seems
to
be
what
mean
tuners
relating
to
know
so
really
useful
to
have
that.
That's
all
that's
on
our
agenda.
The
internet
has
stayed
up
our
time,
which
is
fantastic,
so
really
quickly.
Does
anyone
have
anything?
We
should
talk
about
any
questions.
Anything
we
should
discuss
urgently
this
week.