►
From YouTube: Backdrop weekly 2/12
Description
Weekly check-in meeting on Backdrop CMS core development, and other relevant tasks.
A
Alright,
we
are
on
a
girl,
I've.
It
is
Thursday
februari
12
and
we're
here
to
have
a
quick
check-in
on
development
task
for
backdrop,
court
and
other
related
items
that
were
really
today
so
we're
working
on.
At
the
same
time,
we're
going
to
start
with
a
quick
update
from
the
PMC
and
Nate.
If
you
want
to
let
everyone
know
about
our
latest
security
release
and.
B
As
you
may
know,
they,
the
dribble
security
team,
has
been
really
kind
and
has
offered
to
let
us
have
access
to
all
of
the
security
issues
that
are
currently
outstanding
for
triple
seven,
and
that
way
we
can
work
together
to
coordinate
our
well
to
fix
and
to
coordinate
the
releases
for
them.
So
in
this
case
this
wasn't
actually
a
Drupal
7
buggy.
It
was
a
bug
in
views.
B
There
were
two
security
issues
and
views,
and
so
a
new
version
of
views
came
out
yesterday
and
at
the
same
time,
within
about
an
hour,
we
had
also
released
a
new
version
of
backdrop
that
included
those
same
fixes.
You
can
get
the
list
of
security
updates,
since
this
is
the
first
one.
I've
ever
had
anyone
scary,
so
you
can
get
the
lizard
security
updates
at
backdrop.
Cms
org,
slash
security,
there's
also
a
link
down
in
the
footer
for
security
information,
and
that's
where
you
can
read
about
the
issues
that
we
fixed
yesterday.
B
Besides
the
views
issue,
there
was
also
a
problem
in
layouts,
so
we
had
our
own
reason
to
make
a
release
anyway.
So
it's
just
kind
of
convenient
that
views
also
had
a
couple
issues
that
we
could
fix
it.
The
same
time.
I
also
wanted
to
say
we
got
this
awesome
dragon
sent
to
us
here,
which
I
think
is
pretty
sweet
la
la
botte
sent
it.
We
got
it
in
a
box
this
morning.
It
was
pretty
awesome.
That's.
A
B
A
Alright
well,
the
next
thing
we
want
to
talk
about
is
how
our
little
community
is
doing,
and
it's
been
let's
see
exactly
months
today,
since
we
were
released
backdrop-
one
point:
oh
so
that's
exciting.
We
have,
according
to
Nate's
latest
update
at
22.
Total
people
who
have
applied
to
be
part
of
the
backdrop
contribute,
and
we
have
a
total
of
thirty
five
projects
that
have
been
ported,
so
modules
themes
layouts
already
in
that
repository,
which
is
pretty
good
I,
know,
there's
a
bunch
of
people
working
on
other
stuff,
including
myself.
A
A
So
if
you
have
something
is
hosted
somewhere
else
or
it,
you
know
in
your
private
repository
or
company
repository
or
something
on
github,
rather
than
being
in
the
group
you'll
be
able
to
to
link
it
there
if
you
will
be
able
to
find
it
more
easily,
so
I
think
that's
pretty
good,
considering
even
around
for
a
month,
kind
of
means
were
meeting
our
goal.
Our
goal
is
for
people
at
the
port
things
quickly
and
it
looks
like
things
are
getting
far
too
quickly.
So
that's
a
good
sign.
A
We
should
talk
about
a
couple
of
things
that
aren't
back
job
here
at
the
top
of
the
meeting.
The
first
and
foremost
thing
that
we
have
been
missing.
In
the
backdrop
world
is
Josh
and
we
do
have
a
bunch
of
people
who
have
committed
to
working
on
that
Greg
Anderson
who's,
one
of
the
josh
maintain
errs,
is
doing
some
refactoring
of
drush
anyway,
and
so
we
get
to
be
his
use
case
for
that
I
guess,
which
is
kind
of
you
useful
he's
done
a
bunch
of
work
this
week
he's
got
to
poor
requests.
A
So
it's
got
some
progress
moving
on
there.
If
anyone
super
interested
in
working
on
josh
the
issues,
there's
one
in
the
backdrop-
q,
it's
issue
number
47,
which
is
how
we
make
fact
work
with
Josh
and
then
the
Josh
issue
is
issue
342
and
there's
a
whole
bunch
of
cross-linking
and
stuff
from
one
to
the
other.
If
you're
interested
in
all
of
the
work
that's
going
on
for
refactoring,
in
that
the
larger
plan
of
how
to
get
those
working.
A
Another
thing
that
we
need
to
get
going
for
backdrop,
especially
now
that
we've
had
our
first
security
release,
is
that
backdrop
itself
needs
to
be
able
to
let
you
know
when
an
update
is
available
and
in
order
for
that
to
happen,
bactrim
need
to
know
which
version
it's
running,
in
which
version
it
should
be
running,
and
so
right
now
we
have
an
update
server
that
just
returns
the
single
response
of
not
implemented
yet.
So
we
need
to
think
about
how
do
we
change
the
server
to
actually
recognize
the
version
of
backdrop?
A
How
do
we
change
backdrop
to
notify
the
server
of
what
version
it's
on
and
then
do
that
same
process
again?
Firkin
trip,
as
well
as
for
core
and
I
know,
neat,
isn't
doing
a
bunch
of
thinking
lately
on
how
we
are
actually
going
to
do
this
in
terms
of
packaging
scripts
on
github
and
all
of
that
good
stuff.
I
think
we
have
a
pretty
good
plan.
We
just
need
to
kind
of
put
it
in
action.
I
know
right
now,
Nate.
A
It
is
really
busy
with
doing
things
like
working
on
token
pasado
and
upgrading
backdrops
primary
website,
and
so
we
haven't
been
making
a
lot
of
progress
on
the
update
server.
So
if
we
had
someone
else
who
wanted
to
kind
of
help
pick
up
the
slack
in
some
of
these
other
areas,
and
that
would
help
a
little
bit
too
so
we
do
know
we
need
an
update,
sir.
We
have
a
plan
for
how
to
do
it,
we're
not
actively
working
on
it
right
now.
We
could
use
some
help
on.
You
know
the
update
server.
B
One
thing
about
the
update
server
is
that
one
of
the
reasons
why
it's
it's
kind
of
postponed
is
that
we'd
like
to
get
back
top
CMS
or
get
self
updated
to
backdrop
before
we
start
building
github
integrations
directly
into
it,
because
we're
going
to
need
is
when
a
new
release
is
great
on
github.
It
will
update
a
node
on
the
main
website
saying
you
know
what
the
current
release
is
and
things
like
that,
and
we
could
write
that
integration
against
the
site
as
it
is
right
now,
but
the
current
site
is
Drupal.
B
7
and
we'd
like
to
you
know,
get
the
site
up.
They
did
to
backdrop
first
and
then
build
out
the
github
integration,
but
I
mean
I
guess
in
reality
we
could
probably
do
them
out
of
order
if
we
wanted
to,
or
we
can
start
building
the
github
integration
against
a
generic
backdrop
site
and
then
integrate
it
into
backdrop.
Cms
org
later.
That
would
probably
be
the
best
way
to
go.
B
I
just
added
a
link
to
to
the
agenda
that
is
a
as
to
do
with
packaging
and
updating
version
strings
automatically
for
the
use
of
contribute,
as
we're.
Creating
new
releases
of
contributes
to
there's
been
a
lot
of
confusion
this
week,
because
I
tagged
final
versions
of
token
and
pasado.
But
if
you
use
the
final
releases
of
those
projects,
the
version
information
is
not
on
the
modules
page
and
that's
because
in
the
Drupal
contribute
one
ever
you
make
a
new
release.
B
The
version
information
is
automatically
added
for
you
into
the
package
information
like
into
the
dot
info
file,
setting
what
version
it
is,
and
it
reads
the
get
tag
and
then
jux
that
into
the
dot
info
files,
and
we
don't
have
that
functionality
yet,
but
we
could
and
still
host
the
files
on
github
because,
under
the
backdrop,
contribute
and
permissions
to
modify
the
archives
that
github
itself
hosts.
So
we
can
get
notified
of
a
new
release
being
made
download
the
tar
file
expand.
B
So
there's
some
that's
issue
51.
In
the
backdrop,
CMS
org
q
there's
a
whole
bunch
of
cues
that
it's
a
little
bit
messy.
But
if
you
didn't
know,
there's
besides
the
backdrop
organization
on
github,
there's
also
backdrop
can't,
which
is
where
the
controls
live
and
then
there's
also
backdrop
dash,
ops
and
backdrop.
Ops
is
where
all
of
the
things
like
the
API
website,
the
flagship
website,
the
application
process
for
applying
to
contribute
or
ease
around
the
operations
of
backdrop
are
all
in
there.
And
that's
that
includes
this
issue
and
others
about
integrating
with
github.
B
A
Related
to
that
was
this
concept.
We
had
of
creating
a
backdrop
service,
we're
on
github.
You
can
edit
a
github
project
and
you
can't
check
a
box
saying
that
this
is
a
backrub,
ok,
specific
project,
and
we
still
want
to
do
that.
We
want
anyone
who
creates
a
project.
Neighborhood
get
have
to
be
able
to
identify
it
as
a
project
for
backdrop,
but
all
that
will
do
behind
the
scenes
is
add
it
to
the
backdrop
primary
website
as
equivalent
of
a
sandbox
project.
A
So,
like
drupal
org
lets,
you
create
sandbox
project
that
are
not
actually
listed
in
the
official
module
listings
unless
you
specifically
search
for
sandwich
projects,
we're
going
to
do
the
same
thing
with
backdrop
where
to
create
an
official
project,
you're
going
to
have
a
note
on
the
back
drop
site.
That
will
say
you
know
this
is
the
project
description
here
to
screenshot
your
sort
of
documentation.
A
Let's
all
of
that
stuff,
just
like
you,
have
one
drupal.org,
but
if
you
want
to
just
create
a
get
a
project
and
take
a
box
and
say
this
is
a
sandbox
project
for
a
backdrop.
We
can
import
that
information
to
as
long
as
they
have
a
service
on
github,
so
that
involves
I,
think
creating
like
a
ruby
for
karroubi
project.
That's
already
on
there
and
filed
for
us
back
and
if
I
thought
last
week,
I
was
like,
oh
for
sure,
I
can
just
knock.
A
Do
this
really
quick,
but
it
didn't
have
the
right
environments
about
my
computer
to
test
everything
so
like
maybe
I
should
create
a
form,
that's
not
testing
it.
So
I
didn't
actually
do
it,
but
if
anyone
who
works
in
Ruby
or
wants
to
learn
how
to
I
wants
to
play
with
that,
it
should
be
pretty
easy
to
create
a
new
service.
All
you
have
to
do
is
for
kit,
and
they
even
give
you
a
good
example
of
what
your
service
should
do.
A
There
are
a
couple
of
things
that
we
could
include
that
our
servers
would
do
right
now.
We
don't
have
anything
built
so
I
think
like
we
can
add
a
checkbox,
but
it
won't
do
any
good
yet
because
we
aren't
actually
checking
for
that
checkbox
or
doing
anything.
If
a
project
has
that
box
checked
and
so
I
don't
think
that's
super
urgent!
Oh,
although
I
thought
it
would
be
quick
and
it
could
do
it
last
week,
a
determinant
was
not
for
me
anyway.
A
A
B
A
B
B
The
search
box
on
it
now
axel
a
whole
lot
like
the
search
box
for
PHP
net,
where
it
will
autocomplete
function,
names,
constants,
class
names,
etc.
But
if
you
just
type
words
in
there,
instead
of
a
function
name
and
don't
use
the
auto
complete,
it
will
act
like
a
normal
search,
so
that
can
be
kind
of
handy,
like
I
was
searching
for
a
function
the
other
day,
because
I
was
getting
functioned
not
found
in.
B
In
a
backdrop,
port
and
I
pasted
in
the
function
that
wasn't
found
and
instead
of
pulling
up
the
function
definition
because
that
function
doesn't
exist,
it
found
the
change
log
record,
which
is
super
handy
and
then
I
could
see
that
that
function
had
just
been
renamed
to
something
else.
So
it's
it's
really
nice
yeah
I'm
really
happy
with
it.
We
actually
use
the
exact
same
library
as
as
php.net
it's
salted,
which
is
Twitter
type
ahead
for
anyone.
B
Doc
Belmonts
been
doing
an
amazing
job,
writing
up
change
records
and
documentation
right
now,
everybody
need
an
account
to
create
documentation
on
the
API
website
and
right
now,
it's
exclusively
developer
documentation
if
you'd
like
to
help
with
adding
documentation,
we'd
be
more
than
happy
to
create
accounts
for
you
right
now.
It's
it's
admin
only
approval.
Until
we
open
up
backdrop,
CMS
org
itself
to
general
account
creation,
which
is
in
the
plan.
B
A
In
our
I
think
only
to
change
records
that
need
to
be
added
that
are
new
since
a
backdrop
one
came
out
and
then
anyone
who's
working
on
the
API
said.
If
you
find
anything,
we
haven't
done
a
super
thorough
review
of
what's
on
there.
So
if
you
find
anything
needs
to
be
changed,
just
let
us
know
we
can
update
it,
but
I
think
it's
a
it's
a
really
great
start.
So
yeah
we
are
working
on
the
API
site,
there's
also
some
other
stuff.
A
We
want
to
introduce
there
like
single
sign-on
with
github,
so
that
you
don't
have
to
create
new
accounts
everywhere.
If
you
don't
want
to,
but
again
they
also
need
to
single
sign-on
primary
website.
So
I
think
at
all,
that's
done
in
the
right
order,
eventually,
but
yeah
and
then
of
course,
after
we
get
the
main
site.
Ported
to
backdrop
will
be
able
to
turn
on.
Logins
will
be
able
to
allow
people
to
create
nodes,
for
their
modules
will
be
able
to
integrate
with
the
service
on
github
there's
a
whole
bunch
of
stuff.
A
That's
kind
of
like
backed
up
on
on
that
initial
port
and
I.
Think
we've
got
I
think
maybe
was
like
three
modules
left
that
need
to
be
parted,
there's
a
handful
of
a
little
once
and
then
we
need
to
just
do
the
migration
and
see
how
it
goes
or
not
the
upgrade
so
we're
we're
working
on
it.
So
other
things,
let's
see
we
started
a
new
forum
in
a
subreddit
for
backdrop.
A
Just
to
see
everyone
wanted
a
place
to
go
and
talk
about
stuff
that
wasn't
you
know
an
issue
queue
which
isn't
great
for
conversation
and
I
surprising
is
I,
think
the
separate
it's
actually
working
pretty
well
every
now
and
then
I
go
over
there
and
look
at
stuff
and
there's
a
whole
bunch
of
conversations
going
on
useful
information.
So
I
think
that's
a
pretty
good
place
for
us
to
leave
it
to
start
with
I
think
longer
term.
You
know
we'll
continue
to
evaluate
how
it's
working
mean.
A
If
there
are
things
that
we
need
to
do
that,
we
can't
do
there.
I
noticed
I
had
problems
posting
an
image
we'll
see
if
we
can
try
and
solve
those
problems
in
in
other
ways,
or
you
know,
moving
off
of
credit
if
we
have
to
so
other
things.
Let's
see,
we've
got
some.
We
did
a
security
release
this
week,
so
that
was
just
yesterday,
so
we
don't
have
any
new
bug
fixes.
A
So
we
haven't
keyed
up
a
next
date
for
an
ex
bug-fix
release,
but
I'm
sure
we
will
get
some
any
day
now
get
okay.
Let
me
look
got
plenty
folks
will
get
them
fixed,
powerful,
find
new
ones
and
fix
them
and
will
schedule
another
release,
but
we
don't
have
one
scheduled
for
now.
So
our
next
major
milestone
is
that
factor.
A
Point
1
point:
1
will
be
released
on
May
fifteenth
and
we
currently
have
a
list
of
things
queued
up
for
the
1.1
release,
including
adding
a
rich
text,
editor
decor,
which
is
something
that
is
super
important,
but
it
is
also
super
hard,
adding
token
module,
interface,
hath,
auto
and
getting
our
own
branding
to
the
administration,
look
and
feel,
and
so
as
far
as
token
pasado
names
being
a
ton
of
work
on
the
kinship
projects
for
those
which
is
the
first
step
to
moving
them.
Decor
is
getting
a
kinship
ragic
that
actually
works
a
module.
A
You
can
install
and
turn
on
and
does
what
it
does
is
important
and
then
we're
going
to
kind
of
look
at
how
the
current
contribs
work
and
say.
Is
that
how
we
want
them
to
work
in
core?
And
there
are
some
things
in
particular
that
we
will
be
changing
a
little
bit
when
they're
in
core.
They
don't
need
to
add
you
know
their
own
interfaces.
They
can
integrate
with
existing
your
faces
and
stuff
like
that.
So
I
think
we're
getting
pretty
close
on
that
and
then
the
rich
text
editor.
A
We
haven't
actually
made
any
progress
on
we've
kind
of
talked
about
how
it
should
work.
We've
talked
about
how
libraries
should
work
in
backdrop
there's
a
kind
of
a
non
consensus:
how
to
solve
all
of
these
problems.
So
the
ckeditor
integration,
I
rich
text,
editor
and
for
is
something
that
is
likely
to
not
make
that
one
point
lon
cutoff
date
unless
we
can
solve
some
of
these
other
problems
a
little
bit
faster.
B
Then
they're
working
now
they're
totally
probably
working.
We
had
to
do
a
couple
of
changes
because
backdrop
has
a
new
built-in
dialogue,
API
and
previously
token
was
using
its
own
dialogues.
Now
we're
using
the
built-in
dialogue
API
backdrop,
which
is
nice
but
other
than
that
now
yeah
they're,
just
they're
just
working
modules
there.
They
should
be
totally
functionally
an
API
equivalent
to
Drupal
7,
but
I.
Don't
know
that
entire
situation
is
a
little
bit
temporary
because
when
they
get
built
into
core
they
probably
won't
be
API
compatible.
B
Because
things
like
the
path,
auto
namespace
will
probably
go
away
and
it
will
just
be
part
of
path
module,
so
I
would
say
if
you're,
if
you're
building
a
backdrop
site
now
feel
free
to
use
token
and
path
auto,
as
they
are
right
now.
But
if
you're
contributor,
it's
probably
not
a
good
idea
to
start
integrating
with
the
path
I,
don't
token
modules
that
we
have
today,
because
they
probably
won't
be
the
same
ones.
A
Okay
and
then,
as
far
as
our
I'm
in
looking
feel
I,
believe
that
our
style
guide
is
now
done,
which
is
good.
We've
got
a
good
guideline
as
to
what
our
administration
interface
should
feel
like,
and
we've
got
two
people
brandy
Norwood
in
wes,
who
are
willing
to
start
working
on
taking
the
styles
from
our
style
guide
and
figuring
out
how
they
should
actually
be
integrated
into
core.
So
we've
got
some
things
that
we
can
put
directly
in
the
core.
A
If
it's
just
like
a
CSS
change
on
something
quick,
we
can
put
that
into
a
system
module
or
wherever
the
CSS
came
from
and
some
things
that
are
specific
to
our
current
administration
theme,
which
is
called
seven.
We
need
to
put
those
changes
in
27
or
things
that
require
markup
changes.
Four
elements
also
might
need
to
get
put
into
seven,
so
we
don't
to
be
changing
markup,
that's
kind
of
directly
out
of
core,
so
we
have
to
kind
of
look
at
it.
A
A
Themes-
stuff
like
that,
so
we
have.
We
have
a
style
guide,
which
is
the
most
important
step
and
we're
working
on
figuring
out
how
getting
those
changes
in
won't
work.
So
I
think
that's
underway
and
I
think
we're
on
track
to
get
a
new
feel
by
1.1.
So
when
people
install
backdrop,
it
won't
feel
like
they're
using
Drupal.
A
It
will
feel
like
a
different
product,
which
I
think
is
super
important
for
us
long
term,
so
two
other
stuff
that
isn't
necessarily
earmarked
for
the
1.1
milestone,
but
things
that
I
think
are
really
important
for
us
to
be
working
on
throughout
improvement
of
backdrop
and
those
two.
Those
two
major
categories
are
user
experience.
Improvements
in
developer,
experience,
improvements,
all
issues,
freezer
experience
have
a
title
that
starts
with
you
x,
at
least,
if
I've
noticed
their
user
experience
issues
and
to
aux
if
you're
creating
an
issue
that
specific
related
user
experience.
A
Please
add
that
prefix
the
beginning
of
your
title
and
then
that
way
you
can
search
the
GQ
for
all
issues
containing
UX.
If
you
care
about
you,
the
ability
and
start
working
on
improving
things
like
that
same
thing
goes
for
developer
experience.
We've
got
a
DX
in
the
front
of
the
issue,
title
and
square
brackets
to
indicate
developer
experience
issues.
We
have
to
be
careful
about
how
much
developer
experience
problem
progress.
We
can
make
in
one
point
0,
because
we
have,
or
in
the
one
point
X
branch
at
all,
because
we
can't
break
the
api's.
A
So
if
we
can
add
helper
functions
or
backwards
compatibility
wrappers,
those
kinds
of
things
are
possible,
but
in
terms
of
changing
the
way
existing
functions
work,
we
can't
do
it
without
breaking
api's.
So
we
need
to
kind
of
be
careful
with
those,
but
but
it's
good
to
document
them
so
that
we,
if
we
find
something,
that's
a
big
problem
or
something
that
people
are
struggling
with
a
lot
and
backed
up,
we
can
fix
it
in
fact,
up
to
just
to
make
sure
that
people
will
be
able
to
port
quicker
people
feel
and
understand.
A
You
know,
guess
what
things
should
be
and
be
correct
with
our
guessing.
So
maybe
is
your
code
for
just
as
important
as
we'd.
Be
easy
to
fight
together,
so
there's
links
in
the
agenda
for
today
that
linked
to
user
experience
and
developer
experience
issues,
but
you
can
also
just
search
the
queue
for
those
square
bracket
tags
than
that
that'll.
Get
you
those
same
issues
too,
all
right!
A
So
that's
what
we're
working
on
in
terms
of
backdrop
core,
there's,
obviously
a
ton
of
issues
in
the
queue
that
we
aren't
talking
about
every
week,
just
because
they
have
a
bunch
of
priorities.
Bug
fixes
obviously
we'll
be
looking
at
those
all
the
time.
Anyone
anytime
anyone,
so
that's
above
and
someone
fix
it,
we'll
try
and
get
it
into
the
next
bug-fix
release.
Again.
A
All
of
those
fixes
need
to
be
API
compatible
with
current
version,
but
that
hasn't
been
a
problem
yet
and
probably
won't
be
for
most
issues
so
that
that
will
be
good
and
then
yeah
there's
a
ton
of
issues.
If
you
fix
something,
will
either
designate
it
for
specific
upcoming
release
in
one
point
X
or
if
it's
something
that
we
don't
think
is
a
big
priority,
it
might
get
pushed
to
2x
or
if
you
have
a
future
requests,
the
same
thing
it'll.
A
If
we
know
when
we
can
fix,
it
will
tag
it
with
a
specific
milestone
milestone
if
it
doesn't
get
done
by
the
milestone
that
obviously
just
get
pushed
forward
to
the
next
one,
but
we'll
just
keep
on
plugging
it
forward
as
much
as
we
can
every
Thursday.
After
this
meeting
we
usually
have
a
little
sprint.
We
meet
in
our
IRC
channel,
which
is
compact
rep,
and
we
try
and
crank
out
a
bunch
of
stuff
on
back
job
right
now,
I'm
going
to
be
working
on
porting
modules
and
working
on
backdrop,
CMS
org.
A
If
anyone
else
wants
to
work
on
bug,
fixes
or
user
experience
or
whatever
anything
you're,
particularly
interested
in
you,
can
join
us
in
the
IRC
channel
and
pound
backdrop.
If
you're,
not
an
IRC
user,
you
can
find
us
on
twitter.
You
can
tweet
at
us
at
backdrop
CMS.
We
have
a
contact
form
on
our
website
now
which
actually
works.
So
if
you
are
not
on
Twitter
and
not
on
IRC
use,
the
contact
form
we're
in
this
meeting.
A
So,
if
you're
able
to
get
time
from
your
boss
or
yourself
or
whoever
to
work
on
backdrop,
working
with
us
on
thursday
is
good,
because
we're
usually
around
to
help
answer
questions
or
put
people
in
the
right
direction.
If
you
need
a
task
to
work
on
still
doing
that
today
in
again
next
week,
every
thursday
foreseeable
future
will
be
great.
We
do
have
some
upcoming
events
for
backtrack.
We
have
posted
two
calendars.
A
A
That's
where
we
talk
about
things
like
you
know,
redesigning
the
administration
theme
or
building
the
modules
spline
der
page
on
vector
of
CMS
org,
where
we
trying
to
talk
about
more
design
focus
thinks
that
our
designers
shouldn't
have
to
be
here
for
the
whole
developer
meeting
developers
don't
have
to
be
difficult
design,
meaning,
but
we
haven't
had
as
many
design
tasks
lately
as
developer
tests.
We've
split
that
into
a
fortnightly
meeting,
so
it
once
every
two
weeks,
but
as
things
go
forward,
we'll
try
and
see.
A
If,
if
that
schedule
continues
to
work
out
and
I
tell
people
reflect
our
actual
schedule,
the
other
calendars
for
Drupal
events,
that
are
backdrop
friendly.
So
if
you're
planning
on
attending
a
drupal
camp-
and
you
want
to
talk
about
backdrop-
there
are
some
in
particular
that
have
reached
out
to
us
and
asked
us
to
come
and
attend
and
talk
to
their
attendees
about
backdrop
to
an
hour
in
our
near
future.
A
B
A
So
if
anyone
has
had
too
much
sun
from
him
hanging
out
in
San
Diego
in
February
and
wants
a
little
bit
more
cold,
we
can
definitely
go
to
Chicago
in
March
and
we'll
be
able
to
talk
about
backdrop.
There
I,
don't
think.
We've
proposed
a
section
there
yet
and
I'm
gonna
do
a
keynote
on
PHP,
it's
just
a
little
bit
more
general
and
not
specific
to
backdrop
or
Drupal,
but
there
will
be
people
there
who
will
be
friendly
about
talking
about
backdrop
as
well,
so
we're
trying
to
be.
B
A
That
job,
so
in
general,
we
won't
propose
the
talk
at
a
camp
unless
for
specifically
asked
to
either
by
the
organizers
of
the
camp
or
people
who
are
attending
a
camp
and
saying
I
want
to
hear
about
this
at
this
camp.
So
if
you
want
to
hear
backdrop
about
backdrop
at
some
camp
that
you
are
attending,
you
need
to
reach
out
to
us
and
let
us
know,
because
we're
not
going
to
try
and
just
show
up
and
talk
about
it
without
being
specifically
asked.
A
So
that's
kind
of
where
we're
at
in
terms
of
events
Nina
will
also
be
at
drupal
con
la
we
have
not
proposed
a
backdrop
top
at
a
drupalcon,
it's
specifically
la
because
we
think
that's,
maybe
not
going
to
be
well
received.
We
were
requested
by
organizers
from
Bogota
to
propose
attack
in
Bogota,
so
we
propose
one,
but
then
we
got
in
trouble
for
it.
Oh
yes,
nothing
to
take
it
down.
A
So
there's
definitely
some
like
non
consensus,
even
in
the
organizers
of
Drupal
Constance,
whether
they
want
to
hear
backdrop
or
not
so
I
think
for
now
we're
just
going
to
keep
not
mentioning
and
are
not
talking
about
factor
up
in
official
sessions
at
triple
cron.
We
will
be
in
LA
we're
probably
going
to
do
ab
off
or
something
more
informal.
Maybe
we'll
do
a
dinner
where
anyone
who's
attending
triple
con
la
would
like
to
go
dinner
and
talk
about
it.
That's
definitely
something
we're
open
to.
A
A
We
have
a
triple
watchdog
article,
which
will
be
out
in
May
I,
think
in
time
for
Drupal
con
la
where
I
wrote
an
article
that
talks
about
very
specific
differences
between
Drupal,
7
and
backdrop
specifically
icmi
in
configuration
management,
including
code
samples
and
best
practices
and
stuff
like
that,
which
looks
should
be
pretty
interesting
and
Nate
wrote
little
faq
article
about
all
the
questions
that
we
asked.
All
the
time
from
about
backdrop,
that
kind
of
helps
answer
some
questions
about.
A
You
know
how
does
contribute
and
how
do
you
deal
with
you
know
general
problems
which
I
think
will
also
be
really
useful
to
read
your
spin
magazine.
So
hopefully
those
are
going
to
be
well
received
and
that's
the
end
of
our
announcements.
So
let's
go
ahead
and
open
up
for
a
couple
of
minutes
to
see
if
anyone
has
any
questions
or
anything
that
we
should
talk
about
in
this
weekly
meeting.
B
A
I
did
see
one
question
here
from
ken
asking:
if
WYSIWYG
module
is
going
to
be
part
of
backdrop,
we're
planning
on
putting
a
rich
text
editor
in
court,
that's
one
of
our
hit
list
items
for
the
1.1
release
that
may
not
make
it
it's
not
going
to
be
the
WYSIWYG
module,
though
the
WYSIWYG
module
provides
a
generic
API
for
integrating
with
any
WYSIWYG
editors,
and
we
want
to
specifically
integrate
with
one
and
that's
going
to
be
ck
editor.
The
same
editor
the
triple-eight
chose
to
integrate
with
and
all
of
the
implementation
and
integration.
A
For
that
specific
editor
is
going
to
be
very
deep
and
very
thorough,
rather
than
a
kind
of
a
shallow
abstract
integration
like
WYSIWYG
module
does
now,
and
our
hope
is
that
if
we
do
one
integration
really
well,
no
one
will
care
what
the
library
is
or
want
to
change
that
for
another
one.
We're
going
to
do
it
so
the
first
one
people
will
just
use
that.
A
So
that's
the
plan
we'll
see
how
far
we
can
get,
but
yeah
we've
also
kind
of
steered
away
from
using
the
word
WYSIWYG,
because
it's
not
really
what
you
see
is
what
you
get
unless
it
also
incorporates
the
position
of
fields
and
images
and
layout
and
other
stuff.
What
it
really
is
is
rich
text
and
so
we're
calling
it
a
rich
text
editor
instead
of
what
was
a
big
editor
just
to
set
the
right
precedent
for
what
it
is,
were
gonna
create.
So
it's
on
our
hit
list.
A
We
know
it's
super
important
Nate
was
actually
responsible
for
doing
Oh.
Much
of
the
work
of
those
doing
editor,
the
one
inch
tube
late.
So
we've
done
this
before
it
makes
done
this
before
anyway,
and
so
we
have
a
plan
for
how
to
do
it.
We
just
have
to
get
everything
working
nature
supposed
to
do
it
going
to
that
issue
to
and
our
issue
queue.
It's
issue
number
101
yeah.
B
I
also
wanted
to
add
that
like,
even
though
we're
going
to
be
including
seek
a
door
and
core,
because
that's
the
easiest
and
most
direct
path
forward
and
there's
a
lot
of
really
good
reasons
to
use
that
editor,
in
particular
the
functionality
of
WYSIWYG
module
that
integrates
with
the
filter
system.
That
makes
it
so
that
an
individual
text
format
is
associated
with
an
individual
WYSIWYG
editor
that
functionality
we
will
be
building
directly
into
core
as
part
of
filter
module.
B
So
it
won't
really
be
that
seek
editor
is
is
needing
to
modify
core
to
inject
itself,
like
ckeditor
module.
Does
today
instead
we'll
be
updating
the
filter,
module
to
support
wysiwyg
editors
and
then
seek
editor.
Module
will
be
leveraging
that
so
basically
kind
of
a
lot
of
the
integration
with
the
filter
system
that
wassu
Ignazio
provides
today
will
be
built
directly
into
filter
module
and
then
the
city
editor
module,
will
just
leverage
that
integration.
So
it's
kind
of
a
it's
kind
of
a
little
bit
of
a
mix.
A
A
Now
I
know
it's
gotta
watch
people,
while
working
on
link
module
same
time
too,
but
yeah.
So
there
are
some
problems
with
upgrades
if
you
guys
want
to
get
together
in
IRC
after
this,
and
we
can
kind
of
figure
out
what
problems
like
you
know,
especially
if
there's
two
ports.
If
we've
got
one
problem,
one
and
one
from
the
other
and
they're
not
we
can
kind
of
push
them
together
and
get
the
working
versions
of
both.
A
So
the
last
question
is
contact
module
I,
think
the
only
documentation
we
have
on
contact
module
is
Drupal
documentation
on
contact
module,
so
I
would
say
it
hasn't
changed
at
all
since
triple
seven.
So
if
we
can
find
something
on
drupal.org,
we
might
be
able
to
include
talks
on
that
somewhere
on
our
site
too.
I
know
our
user
guide
on
the
API
or,
on
the
primary
backdrop,
semester
or
site
right
now
is
lacking
in
concepts.
A
It's
got
some
very
specific
things
like
how
to
install
a
module
and
have
install
a
theme,
but
it
doesn't
have
a
like
what
is
a
block
or
what
is
a
layout
kind
of
a
high-level
conceptual
explanation
of
fields
or
anything
like
that,
which
I
think
would
be
super
useful
and
things
like
contact
module
could
maybe
get
listed
there
too,
like
these
are
the
building
blocks
for
your
site.
So
we
need
some
documentation
on
that
yeah.
We
should
add
some
docs
weren't,
more
docs
are
good
with
the
general.
A
B
A
Let's
go
ahead
and
stop
for
this
week.
It
was
nice
long
meeting
I
covered
a
lot
of
stuff,
which
I
think
is
good.
It's
got
a
lot
of
people
here.
Thank
you
all
for
coming
to
join
and
if
you
have
more
questions,
you
can
find
us
an
IRC
and
use
contact
form
on
the
website.
You
can
tweet
out
us
anything.
You
can
think
of
to
Tory
chess
is
fine
and
we
will
be
here
again
next
time
same
time.
Next
week.