►
From YouTube: Backdrop CMS weekly 6/22
Description
Backdrop CMS weekly check-in on development tasks
A
Happy
Thursday
everybody,
it
is
June
eleventh,
and
we
were
here
to
have
a
quick
little
development
task
check-in
for
backdrop,
CMS
general
and
announcements.
As
usual.
We
have
phpstorm
licenses
for
backdraft
developers.
So
if
you
have
a
project
in
the
backdrop,
contribute
and
would
like
a
PHP
spawn
license,
go
ahead
and
send
an
email
to
info
@
backdrop,
CMS
org,
and
we
can
get
you
hooked
up
if
you
are
not
yet
a
contributor
for
a
backdrop
CMS
and
want
to
be.
We
can
also
help
you
through
that
process.
A
Basically,
if
you
have
worked
on
our
supporting
or
are
porting
or
writing
an
email,
module
seams
or
layouts
for
backdrop,
put
them
in
and
contribute
when
we
can
get
you
guys
the
license,
we
have
a
section
in
this
weekly
meeting
for
updates
from
the
PMC.
We
don't
have
any
know.
If
there's
really
big
news
happens
for
backup
we
tend
to
make
a
little
announcement
here
or
thursday.
It
needs
to
be
discussed
for
a
larger
audience.
B
So
a
backdrop
community
continuing
to
grow
at
a
nice,
steady
clip,
we
had
three
new
applicants
that
were
approved
to
the
backdrop
contribs
pastic
to
see
new
blood
coming
in.
We
have
had
five
new
projects
added
to
the
backdrop,
contribute
hub
group
in
the
last
week.
I
think
one
of
those
was
the
theme
and
the
other
40
modules,
and
there
are
now
49
total
projects
with
official
releases
on
backup,
CMS
org,
which
is
two
more
than
last
week.
B
But
for
the
time
being,
it's
great
to
make
official
releases
because
update
status
is
our
update.
Status
checking
requires
those.
So
when
you
make
a
an
official
release,
it
will
notify
sites
that
there
are
updates
that
need
to
be
done
as
long
as
they've
turned
on
update
module,
so
update
module,
communicated
back
drop,
CMS,
org
and
github
communicates
with
backdrop
CMS
org,
and
when
it
all
comes
together,
you
get
updates
as
checking
which
is
great.
B
B
Yeah,
the
next
section
we
always
like
to
cover
its
infrastructure,
which
is
how
our
pieces
are
coming
together
around
the
software
project,
not
the
backdrop
project
itself,
but
all
of
the
websites
and
infrastructure
and
things
that
we
need
in
order
to
sustain
the
project.
So
the
one
item
that
I
just
mentioned
this
update,
says
checking
now
update,
are
now
active
and
running.
So
whenever
we
make
a
new
release
of
backup,
CMS
itself
or
any
module,
those
updates
are
communicated
back
to
the
sites
that
need
them.
B
As
long
as
you,
you're
running
actually
official
releases,
there's
a
couple
of
bugs
that
we've
been
running
into
like
apparently
some
projects.
They
end
up
getting
bound
to
the
wrong
the
wrong
parent
project.
So
when
one
module
is
updated,
another
module
thinks
they
did
as
an
update,
we're
working
out
the
bugs
in
that,
though,
there's
a
an
issue.
B
Yes,
there's
an
issue
for
that
issue:
70
in
the
backdrop,
CMS
org
issue
queue,
I
think
I
mean
that's,
probably
just
a
minor
like
a
sequel,
query
problem
that
we
have,
but
it
would
be
great
to
get
all
of
that
fixed.
Let's
see
we
are
collecting
project
usage
data
already.
I
have
not
actually
looked
at
the
total
numbers
of
project
usage,
but
I
think
it's
been
up
now
for
three
weeks,
so
we
should
have
three
weeks
worth
of
project
usage
data.
B
B
Excellent,
so
things
are
kind
of
just
kind
of
rolling
along
there.
I'm
sure
Jeff
would
appreciate
more
eyes
and
more
help
on
that
issue,
and
it's
really
important
due
to
erotic.
So
if
anybody
has
some
spare
cycles
and
familiar
or
even
not
familiar
with
with
brush,
then
it
would
be
great
to
have
some
more
eyeballs
on
that
issue.
B
Okay,
continuing
infrastructure
asks
backdrop
CMS
org,
we're
coming
along
soon
with
actually
having
a
project
listing
directory
of
all
of
the
themes
and
all
the
modules
and
all
the
layouts
that
are
available
for
download.
All
of
those
notes
are
actually
all
created
on
backdrop:
CMS
org,
as
people
make
releases,
it
automatically
creates
nodes
on
boxing
orgs,
but
we
don't
have
views
yet
to
display
the
listings
of
those
modules
and
I
think
that
that's
going
to
be
coming
fairly
soon.
B
We're
hoping
it's
basically
metod
as
soon
as
we
can
build
out
those
views,
but
we
also
have
a
design
task,
which
we
mentioned
the
last
meeting
that
we're
working
on
building
out
what
those
module
and
theme
pages
look
like
when
you're
browsing
them.
So
you
know
what
the
download
button
looks
like
the
descrip,
the
project
description
and
things
like
that.
So
that's
coming
along
I
think
general
is
the
date
that
we
tried
to
set
or
that
we
have
set
for
the
tie
on
next
module.
We.
B
Ok,
so
it's
coming
coming
soon
coming
later,
we
also
want
to
expand
backdrop.
Cms
org
out
a
little
bit
more
extensively
to
include
like
a
showcase
of
sites
built
using
backdrop,
service
providers
that
provide
hosting
or
other
services
for
backdrop,
jobs,
a
job
search
and
posting
board
and
an
event
calendar,
but
all
of
those
things
are
much
lower
priority
than
either.
You
know
the
tests
that
working
on
and
backdrop
itself
for
things
like
the
project
listing
pages,
which
is,
is
the
highest
priority
for
our
own
website.
A
So
next
in
our
agenda
is
getting
back
to
the
work
that
we're
actually
doing
on
backrub
CMS
the
project
itself.
We've
got
a
couple
of
issues
earmarked
for
the
next
minor
release
and
which
is
going
to
be
one
dot,
one
dot
X.
We
don't
have
a
date
scheduled
for
that,
because
we
have
nothing
super
urgent
that
needs
to
get
into
that
version,
but
should
a
security
issue
or
something
come
up
in
the
next
few
days.
We
can
go
ahead
and
schedule
that,
but
for
now
all
we
have
and
left
for
that.
A
One
is
getting
all
of
the
changes
that
are
in
the
latest
versions
of
Drupal
7
into
the
latest
version
of
backdrop.
We
have
a
giant
meta.
We
have
a
ton
of
four
requests
that
are
all
just
waiting
to
get
reviewed
and
merged
in
and
on
that
note
we
do
have
a
backdrop
intern
this
summer.
Who
is
helping
us
review
all
of
the
poor
requests,
so
we
should
hopefully
get
through
that
bottleneck
a
little
bit
faster
in
terms
of
getting
new
stuff
in
the
core.
A
So
that
is
looking
really
good
and
as
soon
as
we
get,
those
PRS
merged
will
probably
go
ahead
and
issue
the
one
dot
one
release
and
then,
or
so
one
1
dot
x,
release
and
then
we'll
start
a
new
branch
for
any
other
changes
that
need
to
come
along
after
that
bug
fixes
or
what
have
you
for
1.2,
which
is
the
most
exciting
things
we're
working
on
right
now,
we've
got
earmarked
a
ton
of
major
features
we
want
to
get
in
the
first
biggest
and
most
important
of
those
is
a
rich
text
editor.
A
This
is
something
that
word
precise,
did
something
that
your
blade
has
something
that
is
a
horrible,
painful
disgusting
process
to
try
and
set
up
in
Drupal
7
right
now,
I've
been
doing
nothing
but
fighting
with
Drupal
7
with
you
again
udders
for
the
last
two
weeks
and
I
really
hate
it.
Oh
my
really
want
to
get
back
up
to
a
point
where
it
ships
with
a
deterrent
court
that
has
great
integration
both
with
the
system
itself
with
backdrop
and
with
the
editor,
so
neat
has
been
working
for
an
equally
way
on
that.
B
B
B
Yeah,
I
love
being
unfrozen,
ok,
so
issue
101
is
where
we're
tracking
work
on
this,
and
we
have
decided
that
for
all
large
projects
like
this,
similar
to
what
we
did
with
the
style
guide,
where
it's
a
large
set
of
changes
that
touches
on
a
lot
of
things.
What
we
would
like
to
do
is
make
a
feature
branch
in
the
core
story.
B
Of
course,
it
shouldn't
be
too
surprising
because
I
think
this
is
the
third
time
I've
done
a
WYSIWYG
in
like
this
many
years,
basically
I
mean
for
core
work
because
it
we
did
a
whole
bunch
of
work
on
Drupal,
8
and
then
way
back
forward
a
bunch
of
stuff
into
Drupal
7
in
the
WYSIWYG
editor
module,
and
now
it's
that
WYSIWYG
ckeditor
module
actually
was
the
basis
for
the
working
backdrop.
And
so
now
it's
being
moved
back.
B
In
the
backdrop
and
thanks
for
coming
along
very
nicely,
we
have
the
ability
to
attach
an
associate
text,
editors
and
text
formats.
Together,
you
can
configure
the
toolbar
using
the
drag-and-drop
interface,
the
synchronization,
between
the
configuration
of
the
toolbar
and
the
configuration
of
the
filters
is
working
now,
that's
new
since
in
plastic.
B
Dialog
handling
the
current
thing
that
I'm
working
on
that
isn't
yet
in
that
issue,
but
should
be
there
probably
before
next
meeting.
Is
the
link,
handling
and
image
handling.
So
when
you
insert
an
image,
we
should
be
using
a
backdrop
dialogue
rather
than
2k
editors
dialogue,
to
make
it
so
that
you
can
do
things
like
upload,
a
file
into
that
or
potentially
used
like
a
view
to
browse
recently
uploaded
files,
and
things
like
that.
So
the
initial
integration
will
basically
just
be
making
it
so
that
links
and
images
will
use
a
backdrop.
B
Dialogue
and
first
starter,
so
probably
be
just
a
text
field
that
you
paste
in
URLs
to
which
isn't
ideal.
But
it's
a
good
starting
point
and
then
later
we'll
work
on
fling
out
the
upload
functionality.
But
yeah
things
have
been
rolling
along
really
quickly
there
and
with
our
next
release,
not
until
September
I'm,
feeling
really
confident
that
we're
going
to
have
some
amazing
functionality
and
by
the
1.2
relief
I
love.
Additional
eyeballs
I've
heard
that
there's
some
JavaScript
errors
and
things
like
that
in
the
current
branch.
A
I'm
super
excited
to
get
that
moving.
You
can't
wait
to
to
play
with
it.
Other
things
we've
got
going
on
for
backed
up
1.2
is
we
want
to
start
moving
in
field
type
modules,
so
this
is
also
coming
from
a
list
of
all
of
the
modules
that
exist
in
Drupal
7
that
are
moved
into
Drupal
8
4.
We
have
on
that
issue
of
life.
A
A
We
want
to
move
them
into
floor
and
backdrop
well
so
on
our
list
for
1.2
our
date
field,
lingfield
an
email
field,
and
hopefully
this
will
be
quick
and
easy
things
to
move
in,
because
the
other
thing
on
our
place,
a
rich
text
editor
which
we
are
not
calling
was
he
like,
is
a
it
is
going
to
be
tricky,
so
I
think
it
would
be
great
if
anyone
wanted
to
start
working
on
that.
We
have
contribs
on
all
of
the
issues
for
movie
nose
into
four
and
I.
A
Didn't
see
any
comments
that
anyone
was
working
on
it
already,
but
I
think
there
are
people
working
on
it
already
I.
Just
don't
think
the
status
has
been
updated
in
those
issues.
So
if
you're
one
of
those
people
who's
working
on
one
of
those
modules
and
you
want
to
share
any
of
what
you've
done
or
get
feedback
or
what
have
you
go
ahead
and
just
add
a
comment,
and
you
know
maybe
post
a
link
to
what
you're
working
on
or
if
you
have
a
github
branch
or
whatever.
Just
so.
A
We
know
but
yeah
I,
think
I.
Think
yeah
for
the
most
part,
it'll
be
as
simple
as
like.
Oh
it
just
kind
of
works
and
then
we'll
just
have
to
hit
we'll
have
to
yeah.
If
it
just
works,
I
think
that's
good.
I
think
we'll
need
to
kind
of
take
a
look
at
all
of
the
features
that
are
currently
included
in
each
of
these
modules
and
try
and
figure.
D
A
They
are
all
worth
moving
to
core
and
then
I
have
adequate
testing
and
then
also
our
you
know.
Is
it
if
there
are
a
bunch
of
silly
features
that
are
going
to
be
hard
to
support
that
don't
benefit
the
eighty
percent.
Maybe
we
don't
need
to
have
them
I
think.
For
the
most
part,
these
modules
are
kind
of
tried
and
true
and
proven
and
don't
need
a
lot
of
cleanup
and
but
it
is
worth
kind
of
thinking
about,
since
we
have
the
opportunity
to
do
that
and
other
stuff.
We
have
a
github
milestone.
A
For
one
point,
two
point:
oh
there's
the
link
in
our
agenda.
If
you
wanted
to
look
at
anything
else,
it's
slotted
for
the
1.2
release.
Generally
speaking,
there
won't
be
a
lot
of
things,
but
there
are
our
few
that
will
decide
as
we're
working
on
them.
Oh,
this
is
really
important.
I'd
love
to
get
it
into
the
next
version
will
add
the
milestone
generally.
If
we
get
to
the
1.2
release-
and
we
don't
finish
all
the
issues
that
were
slotted
for
that
milestone-
we
removed
the
milestone
unless
it's
something
like
the
rich
text.
A
Editor
in
this
case
was
slotted
for
1.1,
and
it
was
important
enough
that
got
bumped
to
1.2.
If
it's
a
more
minor
issue
and
it
doesn't
make
the
cut
that
we
originally
established,
we
just
remove
the
milestone
entirely
and
then
that
module
would
need
to
get
finished
enough.
If
that
was
something
or
moving
into
court,
that
it
would
get
the
issue
tagged
again
when
we
get
closer
to
to
the
next
choice.
So
we
have
an
issue
a
milestone
right
now.
A
We
do
have
on
the
backdrop
primary
website,
the
road
map
page.
The
kind
of
outlines
are
big
picture
goals
for
the
next
few
releases
again,
what's
in
the
far
distant
future,
is
kind
of
in
flux
based
on
what
our
users
want.
So
that
might
change
you
know
as
we
get
1.2
out.
What's
in
1.3
will
be
established,
but
what's
in
1.4
might
still
be
changing,
so
keep
an
eye
on
that
and
if
you
have
any
feelings,
so
what's
super
important,
obviously
what
they
end.
A
Let
us
know
I
post
things
in
the
issue
queue
and-
and
we
can
reprioritized
as
we're
working
on
various
changes
for
chop
one.
There
are
two
specific
categories
that
we
are
super
interested
in
working
on,
mostly
because
right
now
backdrop
is
really
really
similar
to
drupal
long-term
we're
going
to
be
trying
moving
it
down
market.
So
it's
going
to
be
competing
with
tools
like
wordpress
wordpress
is
really
good
at
user
experience,
drupal
is
historically
not
so
good
user
experience.
We
want
to
identify
issues
in
backdrop
where
user
experience
can
be
improved
and
improve
them.
A
Similarly,
we
want
to
identify
issues
and
developer
experience
and
improve
those
issues
as
well.
So
we
have
two
tags
that
we're
doing
an
issue
queue
just
by
prefixing,
an
issue
with
square
brackets
and
for
user
experience
for
putting
you
x
and
the
square
brackets
and
for
developer
experience
we're
putting
a
DX
in
the
square
brackets.
If
you
find
an
issue
that
really
see
either
of
those
things
tag
it,
it's
definitely
something
that
we're
focused
on
working
on
in
back
trip.
So
happy
knows
clearly
identified,
is
super
helpful
at
every
Thursday.
A
We
have
a
little
sprint
on
backdrop
in
the
IRC
channel.
So
if
IRC
is
your
theme,
you
can
join
us
in
pound
factor
up.
If
I
is
not
your
thing,
you
can
also
jump
on
reddit.
You
can
always
join
in
this
meeting.
This
is
a
great
place
to
come
in
and
hang
out
with
the
backdrop
crew.
You
can
just
post
issues
in
the
issue
cute
whatever
it
is,
that
works
for
you,
Thursday
you'll
find
the
most
activity
happening,
a
backdrop,
the
most
feedback,
the
most
other
people
to
bounce
ideas.
A
Off
of
so,
if
you
can
get
an
hour
or
two
from
your
work
every
week
to
work
on
backdrop,
Thursday's
is
the
ideal
day
to
do
it.
If
you
can't
get
it
on
Thursdays,
we'll
take
it
whenever
you
can
get
it
thursday
nights
or
thursday
afternoons
are
ideal,
but
you
know,
sundays
at
midnight
are
also
just
as
good.
A
So
if
you
don't
know
where
to
get
start,
go
ahead
and
ask
to
tell
us
what
you
like
working
on
and
what
you're
most
passionate
about,
and
we
can
hopefully
find
an
area
where
you
will
excel.
We
have
every
Thursday
this
weekly
meeting
every
other
Thursday.
We
have
a
design
focus
meeting.
Those
are
both
happen
on
Google,
Hangouts
and
I
are
posted
on
YouTube
later.
So,
if
you
ever
miss
one,
you
want
to
watch
something
that
happened.
You're
welcome
to
do
that,
they're
open
to
everyone,
I!
Think!
A
For
now,
we
haven't
really
had
any
issues
with
our
being
too
many
people,
but
if
they're
do
start
to
be
too
many
people,
you
can
force
always
watch
the
live,
broadcast
and
participate
in
IRC
with
chatting
if
you
want.
Instead,
we
are
also
having
meetings
for
PMC
members
as
necessary.
Those
are
not
public
meetings,
but
we
do
publicly
talk
about
the
meetings
in
this
meeting
when
necessary
this
week.
Obviously
we
said
there's
no
updates,
because
they
haven't
had
anything
urgent
to
talk
about
lately,
but
also
in
events.
A
There
are
a
ton
of
Drupal
events
this
year
that
have
decided
if
they
are
backdrop
friendly,
one
way
or
another,
either
by
back
droppers
wanting
to
participate
and
reaching
out
to
the
people,
organizing
dribble
events
and
operating
to
give
a
session
or
four
people
whom
the
Drupal
community
be
reaching
out
to
people.
In
the
backdrop,
community
and
saying
hey
come
talk
to
our
people
about
backdrop,
which
I
think
is
really
good.
It's
showing
that
our
communities
are
still
one
in
the
same,
acting
together
hanging
out
together
or
solving
problems
together.
A
We
can
totally
do
this
as
one
community
at
least
until
Drupal
7
is
no
longer
a
thing
at
that
point.
They're
probably
actually
fork
right.
That's
why
we're
doing
this?
The
way
we're
doing
this
but
I
think
for
now.
It's
really
great
that
we're
still
working
together
and
we
have
a
list
of
upcoming
Drupal
events
that
our
backdrop
frensley.
On
the
backdrop
google
calendar,
which
has
an
ical
feed,
you
can
find
out
ical
feed
on
back
top
CMS
org
on
the
contribute
page.
You
can
find
it
on
our
subreddit.
A
You
can
find
it
on
our
weekly
agendas.
Anyone
who
wants
to
see
what
those
events
are
can
go
ahead
and
just
take
a
look
at
that
calendar.
If
you
are
a
backdrop,
community,
member
and
you're,
giving
a
talk
somewhere
at
a
backdrop,
family
event-
and
you
don't
see
it
on
our
calendar-
go
ahead
and
send
an
email
to
info
a
backdrop
CMS
network,
and
we
can
definitely
add
that
to
the
calendar
to
go
so
there's
too
many
to
list,
but
there's
a
lot
coming
up,
which
is
really
great.
A
A
Okay,
other
things
we
have
the
latest
version
of
Drupal
watchdog
has
a
seven
page
feature
story
on
back
job.
You
haven't
seen
it
go
ahead
and
take
a
look
at
it.
It's
a
pretty
exhaustive
explanation
of
the
significant
differences
between
backdrop
and
Drupal
7
talking
about
our
three
favorite
new
features:
cmi
layouts
and
using
four.
So
just
a
if
you
want
to
see
what
it's
going
to
be
like
difference
between
Drupal
7
and
backed
up.
That's
a
good
articles,
a
good
read!
A
We
had
one
question
earlier
amber
wanted
to
know
what
the
process
was
for
was
for
becoming
a
contributor
when
we
were
talking
about
our
new
contributors
this
week.
Basically,
if
you
have
a
module
that
you
either
refer
Drupal,
you
want
to
be
in
backdrop
or
have
ported
from
Triple
DES
backdrop.
The
process
is
to
post
that
module
in
a
github
repository
belonging
to
you
and
then
file
an
issue.
A
In
the
backdrop
ops,
contribs
dating
that
you
would
like
to
be
a
contributor,
and
then
we
will
review
the
project
that
you've
ported
and
there
are
a
few
requirements.
You
need
to
maintain
the
get
history
from
Drupal
so
that
if
you
have
contributors,
they
still
end
up
getting
their
credit
from
having
worked
on
that
project,
other
contributors
other
than
yourself,
and
then
we
also
want
to
make
sure
you
have
a
readme
file
that
states
to
the
current
backdrop.
A
Maintainer
will
be
because
that
is
not
something
that
we're
able
to
get
from
github,
and
then
we
also
have
some.
You
know
just
like
be
nice
guidelines.
We
want
you
to
follow
so
basically
agreeing
not
to
make
pushes
into
anyone
else's
repository
without
being
added
as
a
maintainer
and
that
sort
of
thing.
So
as
long
as
you
do
those
two
things
in
terms
of
following
the
rules
and
then
agree
to
our
contributed
author
agreement,
we
will
then
grant
you
to
be
a
committer.
A
In
the
backdrop,
contribute-
and
at
that
point
you
can
then
move
your
project
from
your
private
github
repository
or
public
personal
repository
into
the
public
github
group
for
backdrop
contributors.
So
it's
not
a
terribly
complicated
process.
It
takes
any
no
matter
of
minutes
for
people
who
are
interested
in
in
getting
involved
and
if
you
have
not
boarded
a
project
or
don't
have
a
project
of
your
own
that
you
want
to
move.
We
also
have
plenty
of
projects
that
need
maintain
errs.
A
If
you
want
to
take
a
look
at
those
if
you're
using
them,
if
you're
interested
in
maintaining
them,
we
definitely
need
help
in
lots
of
different
ways.
So,
if
you
know
go
ahead
and
open
an
issue
and
they
contribute
stating
your
case
as
to
why
you
want
to
be
contributing
taner,
what
your
causes
are
and
we'll
definitely
review
those
on
the
case
by
case
basis.
B
We
accidentally
skipped
over
it
in
the
agenda.
I
think
wait.
Maybe
we
should
move
that
into
a
infrastructure
and
talk
about
it
there.
Instead
of
user
experience,
improvement.
Okay,
it
would
make
a
lot
more
sense
there,
but
project
browser
so
doc.
Boma
has
been
doing
some
amazing
work
on
project
browser
and
project
browser
is
functionality
that
will
allow
you
to
find
like
discover,
modules
and
themes
from
within
your
own
backdrop
website,
without
needing
to
go
anywhere
else.
B
We
already
have
the
ability,
through
update,
module,
two
to
install
projects
and
themes,
modules
and
themes
through
the
user
interface,
but
it's
really
clunky,
because
you
have
to
go
and
find
the
URL
to
a
zip
file
copy
and
paste
it
and
then
hit
hit
the
button,
and
then
it
will
actually
download
that
that
project
onto
your
site.
But
the
big
problem
is
that
you
can't
actually
find
those
links
to
the
zip
files,
especially
right
now,
since
we
don't
have
the
project
listings
upon
backdrop,
CMS
org.
B
Yet,
but
while
we're
working
on
project
listings
as
views
in
the
user
interface
for
just
people,
browsing
vector,
CMS,
org
doc,
Lamont
has
also
been
working
on
making
it
so
that
this
project
browser
module
would
work
making
it.
So
you
don't
have
to
leave
your
website
at
all
in
order
to
find
and
install
new
modules
and
themes
and
that
work
is
coming
along
really
well.
B
We
put
it
on
the
server,
but
we
haven't
yet
turned
it
on.
So
he's
got
a
deb
site
that
he's
turned
it
on,
and
the
plan
is
is
that
we
should
be
turning
it
on
pretty
much
any
day
now
so
we'll
have
the
server
side
part
in
place
and
then
we'll
only
need
to
finish
up
the
project
browser
support
for
the
project.
B
Therefore,
the
the
client-side
module,
whether
or
not
we'll
move
that
into
core
we'll
see,
but
it
seems
like
if
everything
comes
together
that
could
end
up
being
one
point
to
feature
which
would
be
really
pretty
exciting
and
cool.
So
very
neat
Wes
asks
ie8
support.
There's
been
a
number
of
issues
that
people
have
been
asking
about,
our
like
whether
or
not
to
drop
I
a
tissue
had
some
chatter
in
it.
Our
current
policy
right
now
is
that
backdrop
supports
ie8
in
the
1x
branch.
B
So
that's
basically
the
current
version
that
we
have
and
I
think
that
our
policy
towards
backwards
compatibility
basically
states
that
we're
kind
of
stuck
supporting
ie8
for
the
lifecycle
of
1x.
However,
as
other
people
have
noted,
RIAA
support
is
kind
of
only
superficial,
like
we
say
that
we
support
IE
8
and
where
specifically
doing
things
like
we're
using
a
version
of
jQuery
that
is
ie
8
compatible
and
some
other
things
that
we're
trying
to
make
it
accommodating
towards
ie8.
But
we
also
have
some
other
issues
like
we're.
B
Using
media
queries
all
over
the
place
and
ie8
doesn't
support
media
queries,
so
our
support
fry.
It
is
a
little
bit
superficial
right
now
that
it
doesn't
actually
work
great
on
I-8,
but
at
least
we're
not
making
it
impossible
to
support
IE
8,
so
we'd
like
to
continue
building
up
better
I
ate
support,
if,
like
a
there's,
some
a
breakpoint
thing
for
javascript.
That
makes
it
so
I
ate
supports
media
queries
that
we
haven't
put
in.
That
would
be
great
to
include
but
yeah.
Our
general
policy
is
support.
B
Ie
eight
until
two
decks
as
best
we
can,
but
you
know
the
priority
for
that
is
really
just
kind
of
you
know.
Middling.
You
know
it's
not
like
we're
going
to
bend
over
backwards
or
hold
up
a
release
of
backdrop,
/,
a
lack
of
ie8
support
for
a
particular
function,
but
we'd
really
like
to
try
to
support
IE
8
as
much
as
possible.
At
this
point.
D
Yes,
I
have
a
question
I'm,
going
to
a
mentoring
like
this
weekly
developer,
mentoring
event
that
happens
every
week
on
Saturday
and
there
are
a
lot
of
junior
developers
or
people
with
programming
experience,
but
not
necessarily
Drupal
experience.
Is
there
a
way
to
then
that's?
Why
I
asked
about
the
contributing
tasks
policy,
but
is
there
a
way
to
for
for
developers
who
are
maybe
porting
their
modules
to
like
tag
things
that
might
be
good
for
novice
PHP
developers
and
you
know
I
think
this
is
a
great
project.
D
You
know
it's
still
young
and
it's
a
great
way
for
people
to
learn
like
how
an
open
source
project
works,
and
you
know
I
think
it's
just
a
great
learning
opportunity
for
people,
and
so
I
was
just
wondering
if-
and
maybe
this
is
just
something
I
can
work
on
in
the
issue
queue,
but
is
there
a
way
to
label
tasks
that
might
be
good
for
for
for
young?
You
know
more
less
experienced
developers
who
are
learning
PHP,
or
maybe
they
have
some
skills,
but
they
just
don't
they're
not
familiar
with
triple
or
backdrop
so.
A
We
do
in
the
cork
you
we
do
have
a
novice
tag.
So
if
you
are
a
novice
developer
and
you're
looking
for
issues
that
are
supposed
to
be
a
little
bit
easier,
using
a
novice
tag
in
the
cork,
you
would
find
you
novice
core
issues,
but
I
think
what
you're
asking
about
is
about
contributes
which
aren't
using
the
core
issue
queue
and
it's
up
to
every
pin
trimming
taner
to
decide
what
issues
they
want
or
what
text
they
want
on
their
issues.
A
So
I
think
it'll
be
good
to
say
you
know
as
a
general
rule,
if
you
want
to
steal
our
tags,
that's
fine!
If
not,
if
you
just
want
to
add
not
a
sec,
that's
fine!
But
it's
hard
for
us
to
enforce
that.
Just
because,
because
the
tags
are
all
per
project
well,.
A
D
I'll
start
there
I
think
I
was
looking
in
the
wrong
cue.
I
was
only
saying,
contribute
your
things
cool
well
I'll,
see
what
I
can
do
to
to
kind
of
help.
Point
people
that
direction.
Okay,.
A
I'm
fair
warning
like
some
of
those
issues,
I'll
create
them
and
I'll
say:
oh,
this
sounds
easy
and
I'll
add
a
novice
keg
and
then
Nate
will
look
at
it
like
three
days
later
and
be
like
this
is
not
a
novice
now
and
I'll
remove
it.
So
I
would
say
like
if
you
are
a
novice
and
you
grab
one
of
those
issues
and
you
start
thinking.
This
issue
does
not
seem
novice.
It
might
not
be
a
novice
issue
and
just
move
on
to
the
next
one
like
don't
spend
any
time.
A
Thinking
that
it's
you,
it's
probably
me
so
I'll
definitely
take
another
look
at
the
at
the
novice
q
today
and
see
if
there's
anything
in
there
or
it
shouldn't
be
nervous,
but.
A
Alright,
any
other
issues,
questions
comments,
okay,
well,
then,
I
think
we
should
jump
off
and
go
into
sprint
mode.
You
can
meet
us
in
IRC
in
the
pound
backdrop
channel.
If
you
have
anything
interesting
going
on
with
backdrop,
you
can
tweet
using
the
hashtag
backdrop.
Cms
backdrop
is
also
at
factor
of
CMS
on
twitter.
A
So
if
it's
not
a
thursday
and
you
have
urgent
questions,
that's
all
sometimes
a
good
way
to
get
other
people
who
are
working
on
backed
up
to
respond,
which
is
good,
there's
always
the
reddit,
and
if
anyone
has
anything
interesting
in
terms
of
blog
posts
or
anything
like
that,
it
will
be
great
to
tag
it
with
vector,
FCMs
or
tweet
at
backdrop
CMS,
so
that
we
can
all
learn
about
them.
So
I
guess
that's
it
for
me
anything
else.
You
want
to
add
neat
nope.