►
From YouTube: Backdrop Weekly Meeting 7/31
Description
Come join or watch our weekly status update for Backdrop CMS.
A
Hey
good
afternoon,
everyone,
it's
a
July
thirty-first,
and
this
is
the
weekly
backdrop
meetup,
where
we
just
talked
about
backdrop
and
give
a
status
update
on
how
the
project
is
going
and
where
we
are
on
things
and
answer
any
questions
that
anybody
might
have
out
there.
So
we've
got
a
weekly
agenda
that
we
always
post
before
the
call
that
is,
that
is
on
Twitter
and
we're
going
to
go
through
the
agenda
and
just
see
where
we
are
on
each
of
the
major
initiatives
within
the
backdrop
project.
A
We
expect
that
one.
Second,
we
expect
that
we'll
be
having
our
release
around
fall,
2014.
So
in
the
next
couple
of
months,
we're
hoping
to
get
this
initial
release
a
backdrop
one
to
point
out
and
then
we're
going
to
have
regular
iterations
on
our
releases
sort
of
similar
to
like
drupal
8.
They
recently
adopted
semantic
versioning
as
well,
and
we're
going
to
be
rolling
out
releases
every
three
to
four
months
or
so
with
minor
updates
so
onto
our
progress
reports.
We've
got
three
major
initiatives
that
we
need
to
finish
before.
A
We
would
make
one
point
0
release.
The
first
of
these
is
blocks
and
layouts
there's
a
github
issue.
That
summarizes
where
we
are
with
blocks
and
layouts
issue
86
under
github.com
/
backdrop,
/
backdrop
issues,
and
so
the
blocks
in
that
system
is
actually
coming
on
really
nicely.
This
past
week,
Jen
was
going
through
and
porting
a
bunch
more
of
the
panel's
integrations
into
blocks
and
layouts
things
like
content
type
selection
and
bundle,
selection,
taxonomy
term
selection
and
those
sorts
of
things.
A
So
I
think
that
she
has
made
progress
on
that
front
to
get
some
some
of
those
more
conditions
and
access
rules
all
set
up
the
biggest
piece.
That's
missing
in
the
blocks
and
layout
system
is
primarily
we
still
have
the
old
region
based
system
right
now.
So
when
you
install
layout
module
it
just
layers
on
top
of
the
existing
Regent
system
and
that's
not
what
we
want
so
I
think
it's
actually
like
architectural
II
like
a
pretty
simple
thing
to
implement,
but
we'll
have
pretty
far-reaching
consequences.
A
So
that's
probably
our
biggest
item
in
blocks
and
layouts
land.
That
needs
needs
to
be
done.
Views
in
core
is
our
next
major
initiative.
It's
looking
really
good.
We've
had
views
for
like
nine
months
now,
quite
a
long
time.
We
still
have
major
listings
that
need
to
be
converted.
That's
if
you
won
51
in
the
github
issue,
queue
and
things
like
the
administrative
listings,
the
list
of
users
and
the
list
of
nodes
still
needs
converting
and
I.
Think
both
of
those
issues
are
are
up
for
grabs.
A
We
had
John
red
dike,
do
some
work
at
Drupal
corn
on
them,
but
I
think
he
mostly
was
focusing
on
the
action
system
rather
than
getting
these
views.
Converted
I
think
I'll
try
to
reach
out
to
him
this
week
and
see
if
he
has
time
to
work
more
on
it
or
it
may
have
also
just
been
something
that
he
was
doing
during
the
camp,
which
was
awesome
for
him
to
help.
But
we'll
see
if
thanks
michael
michael
says,
he's
out
this
week,
so
I
guess
he
probably
won't
be
doing
it
this
week.
A
Well,
that's
all
right.
You
did
a
bunch
of
work
during
the
camp
and
he
left
us
in
a
good
place
where
we
can
pick
up.
So
those
issues
are
probably
up
for
grabs
for
anyone
interested
in
doing
some
version.
2
views.
So,
lastly,
of
the
three
major
initiatives
were
trying
to
hit
out
for
the
one
point
0
release,
the
last
one
is
configuration
management
we
have.
The
major
meta
issue
is
issue
1
69.
A
In
the
backdrop,
issue
queue
and
we've
had
the
base
system
in
place
for
a
long
long
time
now,
and
some
major
systems
like
views
and
image,
styles
and
contact
module
are
all
really
fully
converted
and
Paul
hello.
Mr.
Kent,
here
in
the
issue,
Cuban
on
the
Hangout,
has
been
doing
tons
of
work
on
converting
all
of
the
variables
all
of
the
configuration
forms
and
we're
probably
like
three
quarters
of
the
way
through
converting
variables.
At
this
point,
there's
very
few
of
them
left,
especially
for
things
like
configuration,
forms
like
settings
forms
for
various
modules.
A
Almost
all
of
us
are
converted
so
now
the
items
that
are
really
left
are
like
the
big
major
ones,
things
like
fields,
content
types,
menus,
those
sorts
of
things
that
are
kind
of
major
subsystems
that
that
still
need
to
be
converted,
so
I'm
feeling
really
good
about
where
we
are.
Overall
just
we
need
to
probably
shift
our
attention
to
work
on
those
major
systems
that
haven't
yet
been
converted,
even
though
there's
only
a
couple
of
them,
they're
really
central
to
the
functionality
of
backdrop.
So,
let's
see
I
now.
Paul
also
has
a
great
poll
request.
A
A
A
So
we've
got
a
number
of
issues
for
maintaining
cross
ports.
We
went
through
like
600
some
issues
for
Drupal
6
and
all
of
those
three
medicines
are
now
complete,
but
we've
got
two
issues
for
tracking,
basically
changes
from
like
724
onwards,
issue
222
and
262,
and
each
one
of
those
fans
about
three
versions
of
Drupal,
minor
versions
of
Drupal
7
that
that
we
have
to
do
a
little
bit
more
work
on
catching
up.
A
A
We
also
got
a
number
dribble,
eight
backboards,
there's
some
a
gerbil
issues
that
were,
for
the
most
part,
taking
these
ala
carte,
but
we've
got
a
couple
of
sub
sub
issues
for
html5,
CSS
and
JavaScript,
just
back
porting
a
lot
of
the
major
front-end
changes,
and
each
of
those
issues
is
also
in
the
agenda
doc,
which
should
be
shared.
With
this.
This
video,
let's
see,
we've
got
a
number
of
minor
projects
that
we're
trying
to
complete
as
well.
A
Here
are
stickers,
it's
pretty
exciting,
so
we've
got
stickers
printed,
so
I
guess
it's
real
because
its
physical
now,
but
we
got
a
whole
bunch
of
more
stickers
getting
printed
and
we'll
be
at
triple
camp
Minneapolis
distributing
Twin
Cities
triple
camp
for
anybody
interested
in
picking
them
up,
but
we're
working
on
doing
a
lot
more
than
that
throughout
the
entire
project.
There's
a
poor
request
right
now
that
jen
has
been
working
on
to
rebrand
the
installer,
which
also
was
sort
of
a
continuation
of
the
work
that
came
out
of
drupal
corn.
A
Oh
yeah
Anna
did
some
design
work
on
the
installer
which
we're
now
implementing
and
the
pull
request
is
is
ready.
Well,
it
needs
a
little
bit
of
work
code,
styling
things
but
other
than
that.
It's
ready.
We
also
want
to
rebrand
the
administration
theme
and
right
now
we
have
a
designer
working
on
this,
but
it
hasn't
written
a
lot
of
progress.
Recently
I
think
Jen's
going
to
contact
the
designer
to
see
if
she's
still
working
on
it.
A
Otherwise
we
might
need
to
reallocate
rebranding
the
administration
theme
to
someone
else,
I
think
to
keep
them
moving
forward.
Let's
see,
we've
got
a
number
of
areas
that
we're
looking
to
improve
the
user
experience.
One
of
them
is
we
really
need
to
get
a
rich
text
editor
in
core,
which
will
probably
be
ckeditor
right
now.
A
Let's
see
and
we're
also
doing
some
terminology
updates
just
to
clean
up
the
structure
in
the
way
that
things
are
referenced
in
impact
drop
issue.
127
is
a
meta
of
all
the
terminology.
Changes
that
we're
looking
at
doing
some
of
them.
We've
already
done
because
we
needed
to
make
like
the
administration
menu.
A
So
let's
see
man,
we've
also
got
one
last
thing
theme
system
cleanup
and
Drupal
8.
They
had
their
converting
everything
to
twig,
but
we're
worried
during
the
impact
droplets
we're
cleaning
up
the
theme
system
by
consolidating
templates
and
theme
functions,
but
we're
not
actually
converting
twig
we're
basically
doing
the
cleanup
portion,
but
not
the
conversion
portion
and
jen's
been
playing
away
on
that
issue.
125.
You
can
get
the
full
information
on
that.
So
we
have
a
section
in
the
agenda
every
week
to
do
updates
from
the
p.m.
A
We've
got
a
bunch
of
peripheral
sections,
peripheral
work
that
needs
to
happen
around
the
project
that
isn't
the
software
itself
and
most
of
those
things
include
like
websites
and
web
services
around
the
software.
We've
had
a
lot
of
progress
on
this
first
item,
which
is
the
API
website.
Api
backdrop
CMS
org.
Actually,
if
you
go
there,
it's
actually
up
and
functioning
at
this
point,
which
is
exciting
because
that
hasn't
been
there
prior
to
this
week.
A
Basically,
all
of
the
developer
documents
are
all
going
to
be
consolidated
into
the
API
documentation
and
it's
nice
that
we've
got
that
rolling
forward.
Now,
let's
see
all
right
next
item,
we
need
an
update
service
for
backdrop.
When
you
install
backdrop
right
now,
it
still
connects
to
drupal.org
and
immediately
says
that
your
software
needs
to
be
updated
and
we
need
to
make
it
so
that
it
connects
to
backdrop
CMS
org,
probably
via
you
know,
project
module
that
keeps
track
of
the
update
statuses
of
each
module.
A
So
that
backdrop,
can,
you
know,
notify
people
when
they
need
to
update
the
modules
or
the
base
system
itself?
Also
related
to
that
is
our
solution
for
handling
can't
rip.
We
need
to
make
a
official
github
service
for
backdrop,
CMS.
That
makes
it
so
that,
when
a
contributed
module
is
hosted
on
github,
they
should
be
able
to
go
to
the
settings
for
the
project
and
toggle
on
the
backdrop
CMS
service.
That
makes
it
so
that
that
module
gets
registered
with
backdrop,
CMS
org
as
an
official
project.
A
So
all
the
code
and
packaging
all
happens
on
github,
but
the
official
listing
and
Status
checking
of
modules
happens
in
a
central
location
at
backdrop
CMS
org.
So,
in
order
to
do
that,
someone
who
is
familiar
with
the
github
api's
and
probably
know
jay
s,
because
it's
the
sort
of
favorite
api
of
github
to
integrate
with
the
web
hooks
and
make
it
so
that
people
can
do
that
so
that
we
can
get
a
contributed
module
repository
up
and
functioning.
A
Okay.
Last
thing
is
a
backdrop:
CMS
org
are
our
primary
website
itself.
It
just
needs
some
more
love.
It's
looking
really
good
like
in
terms
of
its
content
and
its
structure,
but
at
some
point
we're
going
to
need
to
give
it
like
an
official
redesign
to
make
it
actually,
you
know,
match
the
project
branding
and
implements
or
logo,
and
everything
like
that.
A
B
B
A
Exxon
so
we'll
be
at
once,
eh
drupalcamp
will
be
at
the
code
sprint.
You
want
to
work
on
backdrop
or
gets
a
bootstrapped
on
the
project.
We'd
be
happy
to
help
you
there,
the
only
other
camp
that
we've
really
gotten
the
agendas
bad
camp,
which
is
in
November,
I'm,
sure
it'll
be
more
camps
between
now
and
then,
but
for
now,
that's
what's
on
the
schedule,
let's
see!
Oh.
A
Well,
I'm
not
sure
we're
obviously
not
there,
but
I
think
we
might
have
people
there
may
be
spreading.
The
word
about
backdrop.
Tones
a
triple
can,
of
course,
it's
next
weekend
and
dribble
come
on.
Amsterdam
is
at
the
end
of
sep
tember
Oh
John
also
wants
me
to
mention
that
this
is
I,
guess
as
to
do
with
publicity,
but
I
also
to
do
with
branding
we've
been
on
the
hunt
for
a
mascot
for
the
project.
A
If
you
got
it,
get
when
im
mean
so
or
looking
we're
currently
reaching
out
yeah
we're
currently
reaching
out
to
illustrators
right
now
to
take
some
plays
on
the
ideas.
We're
not
really
sure.
If
it's
going
to
be
like
highly
geometric,
like
the
logo,
we
want
to
potentially
do
something
with
fractals
or
if
we're
gonna,
make
it
something
like
more
playful,
like
a
like
a
rag
doll
or
something
like
that.
A
We
don't
really
know
yet
so
we're
up
and
reaching
around
trying
to
put
out
feelers
for
for
developing
a
mascot
for
the
project,
something
that's
a
little
bit
more
playful
than
their
logo
itself.
So
why
don't
we
just
end
with
that?
That's
all
I
got
I,
don't
think.
Let's
see,
we
got
a
lot
of
feedback
in
the
chat
here,
but
I
don't
think
we
have
any
questions
if
we
do
speak
now,
okay!