►
From YouTube: Backdrop Weekly 9/22
Description
Today’s development agenda: http://bit.ly/2cdmBIh
A
Okay,
all
right,
happy,
Thursday
everybody.
It
has
been
a
week
to
release
packed
up
1.5,
which
is
super
exciting,
so
I
have
started
upgrading
some
of
my
sites
to
it.
I
love
it.
It's
just
like
backdrop,
only
better,
all
right,
so
general
announcements.
Ok
before
I
start
with
anything
in
the
agenda,
we
had
started
an
issue
in
the
PM
CQ.
I
don't
think
it
needs
to
be
public
or
I
don't
think
it
needs
to
be
private,
but
I
moved
it
in
there
just
because
I
want
to
have
somewhere.
A
We
could
talk
about
it,
but
we're
trying
to
figure
out
how
to
manage
releases
of
the
software
and
Wes
made
some
great
recommendations
about
how
these
meetings
could
be,
maybe
made
more
efficient
and
we're
trying
to
figure
out
exactly
what
that
should
be.
But
if
we
know
that
the
meetings
not
working
the
way
they
are
I
figured,
we
tried
start
trying
to
size,
try
something
so
we're
a
little
bit
different
see
if
we
can
get
to
a
meeting.
That
is
the
most
efficient
use
of
everyone's
time,
and
so
for
today
is
a
meeting.
A
I
removed
some
of
the
stuff
that
we
talk
about
every
week.
That
doesn't
necessarily
add
some
value
stuff
like
this
Prince
I
think
it
would
be
great
if
we
have
like
an
actual
in
persons
friends
to
encourage
people
to
do
that.
We
don't
necessarily
have
to
mention
every
week
that
we're
going
to
be
hanging
out
in
Gator
after
the
meeting
I
removed
some
of
the
meta
issues
around
like
JavaScript
testing
that
haven't
been
getting
any
feedback.
So
hopefully
this
is
just
kind
of
a
pared-down
version
of
the
agenda.
A
One
of
the
things
West
recommended
is
if
we
could
come
up
with
a
way
to
kind
of
focus,
our
talk
on
what's
longline
and
back
drop
in,
what's
actually
going
on
back
drop,
whether
it's
you
know.
What
are
we
going
to
talk
about
next
week,
where
we
talking
about
this
week,
just
kind
of
figure
out
like
some
way
to
set
a
focus?
A
So
we'll
see
how
it
goes
and
then
the
other
thing
we
just
had
an
outreach
meeting
and
we
spent
a
bunch
of
time
talking
about
the
website
in
the
upper
for
each
meeting
so
I
took
a
couple
took
a
couple:
did
I
change
this
I?
Don't
know?
Oh
yeah
I
took
a
couple
of
items
off
of
the
website
section
of
this
meeting's
agenda
so
that
it's
narrowed
down
to
the
most
important
things
to
discuss.
A
We
haven't
quite
figured
out
how
we're
going
to
handle
that
long-term
and
whether
it's
we
should
just
talk
about
one
thing,
and
we
should
just
talk
about
the
things
have
been
changed
or
whatever
and
I
know
that
Gregor
you're
concerned
about
not
being
able
to
attend
both
weekly
meetings.
What
I
figured
we
would
do
this
week
is
because
we
had
the
outreach
meeting
this
morning.
We'll
do
a
modified
version
of
website
this
week,
but
we'll
put
the
whole
thing
back
on
for
next
week.
A
B
A
Figure
out
over
time
how
to
make
sure
that
everybody
can
stay
up
to
date
on
what's
going
on,
but
there
were
also
not
like
repeating
ourselves
a
lot
from
week
to
week
so
that
we
can
kind
of
make
the
best
use
of
things.
So
as
we
go
through
this,
please
give
us
feedback.
If
these
changes
aren't
working,
we
will
try
something
else.
We.
B
A
B
A
Oh
also,
if
anybody
would
like
to
become
backdrops
project
manager
and
run
these
meetings,
that
would
also
be
awesome
so
yeah,
okay,
so
Jeff
asked
what
we
did
yesterday.
Oh
part.
A
No
I'm
not
gonna.
Ask
that
okay,
you
can.
You
can
Brad
to
the
manage
you
like,
okay,
anyway,
alright,
so
let's
go
ahead
and
get
started
at
the
top
of
the
meeting.
We
usually
have
a
section
for
general
announcements.
This
week,
backdrop
to
or
Calla
box
2
point
0
is
out.
There's
another
issue.
We
have
a
little
lower
down
to
talk
about
calabarzon
backdrop
together,
but
we'll
get
to
that
later.
If
you
would
like
to
make
a
donation
to
vector
of
CMS,
you
can
do
that
on
the
contribute
page.
A
We
have
t-shirts,
we're
getting
some
new
ones
just
in
time
for
bad
camp.
We
have
some
hoodies
of
various
sizes
we're
getting,
hopefully
a
small
run
of
the
missing
sizes
in
time
for
bad
cam,
so
that
should
all
be
coming
together
soon
ish
but
yeah
we're
gonna
have
more
stuff
for
people
three
phpstorm
licenses.
If
you're
a
contributor
of
the
backdrop
kinship
group,
we
can
get
you
a
phpstorm
license
and
an
info
email
back
from
CMS
to
orc.
A
Also,
if
you
guys
think
it's
not
valuable
for
me
to
say
this
stuff
every
week
we
can
take
this
off
the
agenda.
Follow-Up
appreciate
it
on
that
updates
for
the
PMC.
We
don't
have
any
updates
this
week,
because
there's
still
a
bunch
of
stuff
that
we're
talking
about,
but
we
are,
we
mentioned
it
last
week-
we're
thinking
about
imposing
a
two-week
feature
freeze
before
every
major
release,
and
there
was
a
bunch
of
confusion
about
what
a
future
freeze
actually
is.
A
A
Means
so
I
just
wanted
to
talk
about
that
really
quickly
in
this
meeting,
and
then
we
can
talk
about
if
we
decide
to
do
it
or
not.
In
next
week's
meeting,
once
everyone's
have
attacked
by
chance
to
kind
of
way
in
and
vote
on
that
issue,
but
the
proposal
is
that
we're
gonna
have
an
issue
queue
it's
going
to
be
tied
with
a
bunch
of
issues.
A
Some
of
them
are
going
to
be
labeled,
feature
requests
and
some
of
those
features
requests
are
going
to
be
big
things
like
installing
references
module
or
getting
some
kind
of
media
equivalent
or
in
the
last
few
releases
we
had
a
new
core
theme
going.
These
are
huge
chunks
of
work
and
trying
to
figure
out
like
how
to
manage
those
work
and
pieces
of
work
and
where
to
manage
them
in
a
process.
That's
going
to
work,
we're
also
working
out
how
to
make
that
easier.
A
But
it's
it
makes
me
really
nervous
to
take
one
of
these
huge
pieces
of
work
and
commit
it
like
the
night
before
we
release
the
software,
and
a
lot
of
that
is
because,
like
even
though
the
piece
may
be
working
perfectly
on
its
own,
like
as
a
contributor
when
you
stick
it
in
core
there's
a
bunch
of
stuff
that
comes
together,
that
you
might
not
have
noticed
when
it
was
in
contributing
to
nur,
so
that
number
one
we
can
get
more
eyes
on
it.
A
Number
two
as
we're
working
on
the
rest
of
core
will
start
to
notice
places,
or
maybe
there
was
an
issue
before
there
is
now
because
of
the
future,
whether
it's
just
an
aesthetic
thing
like,
oh
you
know,
there's
a
new
tab
here
whatever
or
it's
a
functional
thing
like
oh
I
can't
push
the
button
anymore.
It
would
be
great
to
be
able
to
find
those
things
earlier
so
that
we
had
some
time
to
fix
them
as
it
is
now.
A
We
kind
of
push
everything
in
the
last
minute
and
then
we
do
a
bug-fix
release
later
right,
and
then
we
tell
everyone
after
we
do
the
bug-fix
release
I
think
when
you
just
push
that
entire
process
like
forward
two
weeks.
That
would
be
good
and
especially
now
that
we
have
more
and
more
people
using
back.
Dropping
this
off
are
they're
running
stable
is
going
to
be
more
important
over
time.
So
what
that's
going
to
look
like
is
in
the
issue.
Queue
if
you
have
something
that's
tagged,
feature
release.
A
It
needs
to
actually
be
committed
to
the
project
more
than
two
weeks
before
the
software
comes
up,
so
in
the
next
version.
On
what
we're
looking
at
for
a
real
example,
is
references
module
references,
module
will
need
to
be
committed
to
core
before
january.
First,
if
it's
not
committed
before
january
first,
it
gets
bumped
to
17,
instead
of
being
added
in
16.
A
What
I'm,
hoping
this
will
mean
is
that
we
can
commit
references
before
it's
completely
finished
right
like
if
it
works
and
it
does
what
it
wants,
but
these
are
interfaces
a
little
clunky
or
needs
a
little
design
or
refresh
like
we
don't
have
to
keep
kicking
that
issue
back
to
needs
work.
We
can
say:
okay,
this
is
a
minimal
Viable
Product
put
it
in
and
then
we'll
have
another
issue.
That's
like
clean
up
these,
your
interface
and
I'll.
A
Is
also
an
excellent
idea,
I
think
that's
great
thing
to
end
your
release
candidate
tag
in
conjunction
with
the
future
phrases
perfect,
it's
it's
yeah,
excellent
suggestions,
and
so
what
that
would
mean
is
that
if
you
have
with
it,
we
actually
ended
up
doing
this
with
the
what
was
it
the
we
added
a
feature
in
15?
That
was
the
ability
to
embed
a
node
as
a
block.
So
we
have
a
new
block
type
that
you
can
reference.
An
existing
piece
of
content
and
Deborah
made
this
poor
across.
A
A
These
are
in
her
face
and
we
should
you
know,
change
the
names
of
thing
and
it
was
a
great
example
of
like
just
get
it
in
if
it
works
and
then
come
back
later
and
clean
it
up,
and
we
did
that
a
little
bit
with
basis,
but
we
didn't
really
have
very
much
time
so
we've
had
okay
to
put
it
in
and
then
we
have
like
500
issues
show
up
or
like
okay.
We
could
change
this.
We
should
push
this
and
we
can
change
this
thing
here.
A
Maybe
that
and
I
think
it
would
be
great
if
we
could
also
manage
like
for
these
large
features.
There
are
going
to
be
a
lot
of
those
issues,
especially
if
we
put
things
in
earlier
before
they're
quite
is
finished.
We
can
even
handle
that
with
a
specific
milestone.
That's
like
16
references
and
all
of
the
issues
that
come
up
early.
A
Two
references
go
into
the
16
references
milestone,
so
you
can
have
16,
which
includes
references
which
is
now
closed
and
the
up
16
references
which
are
all
the
follow-ups
you
need
to
work
on
the
next
two
weeks
and
I
think
there's
a
way
that
we
can
kind
of
manage
that
sanely
over
time.
So
feature
freeze
just
means
new
features,
don't
get
in
after
the
last
few
weeks.
A
Hopefully,
it'll
fill
make
things
a
little
easier
on.
All
of
us.
It'll
help
give
us
a
little
little
extra
focus
in
the
last
two
weeks.
We're
not
like
oh
I
found
this
issue
in
the
issue:
queue
the
guts
gifts
in
the
last
version.
What
I
really
want
it
now
and
I
can
squeeze
it
in
because
no
that's
too
close,
we
have
done
that
in
the
boss.
We
love
doing
that,
but
it's
getting
to
the
point
now
where
you
feel
careful.
So
so.
A
Yes,
there's
also
some
top
we
haven't
figured
out
yet
what
whether
we
want
to
do,
how
we
want
to
manage
feature
branches,
I.
Think
it's
an
excellent
to
create
a
committed
I
like
take
a
fall
requesting
commit
on
a
specific
feature,
branch
and
work.
There
I
think
we
also
need
milestones
for
each
feature
branch
we're
going
to
do
that,
just
so
that
we
can
keep
the
issues
for
the
branch
in
a
sensible
place.
They
don't
just
go
directly
into
the
cork
you
with
all
the
other
core
issues.
A
Having
ways
to
keep
keep
our
you
know,
we
don't
miss
one.
We
don't
want
to
yeah
just
to
figure
out
a
way
to
keep
organized
around.
That
is
good,
but
yeah,
so
we're
trying
to
figure
out
like
at
the
PMC
level.
How
do
we
manage
this
in
a
way
that
makes
sense?
We've
had
several
tries
of
doing
it.
The
way
we've
been
doing
it
that
have
maybe
made
us
think
that
it's
not
the
best
way
to
do
it.
So
we're
going
to
figure
out
for
1.6
something
else
to
drive.
A
A
E
Filed
that,
if
everybody
can
take
a
look
at
that
filed
an
issue
I've
seen
that
in
other
projects,
what
they
do
is
they
say
they
file
an
issue
and
they
say
release
version
X
and
they
have
a
public
place
from
a
template.
This
is
just
drafted
random
things
that
are
out
there,
but
I
think
that
we
should
do
that
with
its
release
and
have
specific
people
assigned
to
tasks
so
that
we
can
get
the
load
off
of
you,
nice
and
who
ever
else.
Oh.
E
This
is
a
good
thing
to
solve,
like
tick
the
boxes
and
then,
when
we
are
done
with
the
pre-release
tasks,
we
do
the
release
and
then
everybody
jumps
to
the
post
release
tasks
and
we
do
those
as
well
as
well.
We
don't
forget
to
send
the
newsletter
or
update
the
docker
image
or
anything
I.
Think
that's
a
really
good
thing.
Yeah.
B
E
E
A
Yeah
I
think
this
looks
great.
I
love
this
idea.
What
there
are
starting
to
be
a
lot
of
things
that
we
need
to
do
for
each
release,
including
not
only
the
software
we're
managing,
but
now
there's
a
pantheon
repository
got
to
fetch
two
and
there's
docker
thing
that
we
need
to
update
and
just
keeping
track
of
all
the
things
we
have
to
manage
and
who
has
to
do
them
and
when
they
need
to
get
done
is
an
excellent
idea.
A
A
Just
to
see
that
we
have
a
process
in
place
and
we've
done.
I
know
15
come
out
a
week
ago,
but
we
could
definitely
do
at
least
the
like
release
and
post
release
tests
and
then
get
set
up
and
ready
for
to
do
it
again
in
164
I,
don't
know
we're
gonna
do
this
for
bug
fix
releases
to
maybe
we
would
have
a
different
list
for
both
like
the
bug
fix,
really
shall
probably
them
won't
need
a
a
newsletter,
but
I
will
need
like
to
get
pushed
a
pantheon.
A
So
having
a
modified
version
for
41
would
be
great.
Fantastic
I'll.
Add
a
comment
on
these
later,
but
I
think
that
looks
like
a
good
idea.
Does
anyone
have
any
reason
we
shouldn't
do
it?
No
everyone
loved
it.
Okay,
oh.
A
Alrighty
so
under
infrastructure
tasks-
I
Gregory
just
mentioned
this,
but
we
did
have
this
issue
with
the
doctor
imaging
to
get
updated.
A
D
A
Does
that
also
include
moving
backdrop
into
a
subdirectory
or
so
no.
A
I
want
to
look
at
that,
so
many
things
I
would
do.
I
want
to
look
at
that
because
I
wanna
I
wanna.
I
also
want
to
get
it
thrush
working
on
campeon
so
that
we
can
get
backdrop
to
be
installed
by
anyone
who
has
a
Pantheon
account
without
needing
to
know
where
our
site
is,
but
also
because
I
would
love
to
be
able
to
figure
out
our
get
file
deploy,
workflow,
which
I
think
we
could
also
solve
with
some
of
the
new
tools.
A
So
we're
going
to
be
using
that
issue
and
what
this
get
done.
First.
So
I'll
look
at
that
today,
I
keep
saying
that
I'll.
Definitely
look
at
that
today
and
we'll
try
and
move
forward
on
that.
A
Okay,
so
dr.
up
CMS
org,
the
there
are
two
important
things
that
I
wanted
to
talk
about
today.
The
first
one
is
the
showcase
of
sites
built
with
backdrop.
This
is
something
that
keeps
coming
up
as
everybody
comes
to
our
website
and
their
first
question
is:
do
you
have
a
showcase,
or
do
you
have
a
place
that
I
can
see
sites
they're
built
with
backdrop,
and
the
answer
is
kinda?
We're
working
on
one:
it's
not
there,
yet
you
can
put
your
sites
in,
but
you
can't
see
them.
I
would
love
to
get
that
finished.
A
So
if
anyone
has
any
free
time
and
that's
very
funny
but
wants
to
help
work
on
building
things,
we
need
a
layout
for
the
showcase
site
which
should
be
might
be
a
little
complicated
because
it'll
be
dependent
on
the
data
that
we
get
in
should
have
some
data
in
there.
We
can
use
as
a
test
point
so
I've
been
allowing
people
to
put
their
stuff
in.
We
also
need
some
theming
on
it.
So
I
know
everyone
is
really
busy
right
now
because
we're
all
working
so
hard
backdrop
for
the
last
few
weeks.
A
We
have
other
work
that
he's
intending
to,
but
that
is
kind
of,
first
and
foremost
in
our
priorities
for
backdrops
and
stork.
So
if
anyone
has
any
pre
cycles,
let's
work
on
that.
That
would
be
great.
Second,
most
important
thing
is
the
documentation
section.
Only
reason
I
put
this
up
here
as
being
super
important,
because
I
think
it's
pretty
much
done.
We
know
that
it
needs
screenshots,
I,
think
that's
fine.
We
can
publish
it
before
it
has
screenshots
in
there,
and
people
can
still
use
it.
A
A
I've
only
gone
through
like
two
or
three
pages
and
then
realized
I
had
other
things
that
are
more
important
to
do.
So
if
anyone
loves
reading
technical
documentation,
this
is
a
great
place
backdrops
to
invest
at
work.
/
user
dash
guide
a
great
place
to
spend
some
time
do
some
heavy
light
reading
and
we
would
definitely
love
any
feedback
you
have
on
there.
We
have
revisions
turned
on
on
the
content,
so
we
can
make
you
an
editor
and
you
can
just
go
in
and
make
changes
and
we
don't
like
them
again
revert
them.
A
We
do
like
them,
it
will
get
better.
So
that's
a
good
place
for
people
to
jump
in
and
help
alright.
So
the
backdrop
the
product
I
haven't
gone
through
the
issue
queue
since
we
released,
but
I
have
been
kind
of
keeping
track
of
issues
as
they
come
in.
We
do
need
to
issue
1.5
bug-fix
release.
There
are
a
couple
of
bugs
that
are
fairly
urgent
and
there
are
a
lot
of
them
that
are
completely
not
that
important
gets
them.
We
get
to
them.
A
I
would
love
it
if
we
could
get
that
feature
back
now
that
it's
not
as
broken
for
people
and
I
think
that,
especially
for
existing
people
who
have
relied
on
their
images
and
their
existing
sites,
that
is
kind
of
broken
for
them.
So
I'd
love
to
get
that
resolved
before
the
151
release,
and
we
do
have
a
github
issue
milestone
for
151,
but
it
has
a
ton
of
stuff
in
it.
A
I,
don't
think
all
of
that
stuff
is
going
to
get
done
for
151,
but
anyone
who
wants
to
grab
a
bug
and
work
on
it
there's
a
good,
a
good
list
there,
as
many
of
them
as
we
can
fix,
get
fixed
before
we
release
would
be
great,
I,
don't
know
Jeff
if
you've
seen
anything
else
come
through.
That
you
think
is
important
enough
that
it
should
be
on
our
important
bug
fix
list.
He
is
not
feeling
well
today,
unfortunately,
so
we'll
get
his
feedback
later,
maybe
well.
E
I'm
Jenny
I,
don't
think
well,
I,
don't
know
if
it's
that
critical,
but
it
seems
like
a
usability
issue.
Today's
that
that
the
with
a
new
home
page
layout,
the
primary
navigation
I,
have
created
an
issue
for
it.
The
primary
navigation
block
menu
vlog
is
not
set
to
drop
down,
whereas
the
rest
of
that
site,
which
is
the
default
layout,
is
set
as
a
drop-down
and
yeah
when
I
try
to
create
that's,
not
what
I
fact
that
that
I
feel
is
like.
E
B
A
E
A
The
damn
sure
that
was
an
oversight,
I
think
I,
don't
know
what
went
in
first,
the
front
page
layout
or
the
home
page
level,
but
it's
probably
a
conflict
of
like
two
features
going
in
and
somehow
this
eye
thing
didn't,
guess
that
where
it
should
have
concept,
but
that
definitely
I
agree.
That
sounds
important.
It's
going
to
be
very
weird
for
new
people
who
are
installing
this
backdrop
to
run
into
that.
So
yeah
I
would
say
that
definitely
goes
on
an
important
call.
E
A
Yeah
we'll
get
that
next.
That
seems
important
and
ok
and
then
16.
So
this
is
the
next
major
release
currently
scheduled
for
january
first
possible
or
sorry
train.
Your
fifteenth
possible
bug
fix
on
january
first
or
feature
agreed
on
january
first
and
look
like
about
next
week,
but
features
we
know
are
going
to
be
in
it
are
at
entity
reference
which
is
one
that
got
bumped
from
this
last
release,
and
one
of
the
things
that
came
up
when
we
were
talking
about
this
solution
to
the
image
is
getting
deleted
when
they
were
inserting.
A
The
box
is
the
fact
that
both
wordpress
and
drupal
8
now
have
some
sort
of
central
media
management
system
included.
We
have
a
module
in
Drupal
7
qualified
entity
that
gives
us
a
kind
of
a
strange
interface
for
managing
files.
That
works
a
lot
like
our
interface
for
managing
content.
Gordon
press
has
something
similar,
but
is
very
different
in
how
it
handles
images
and
hazel
arrest
of
content.
I
would
love
if
we
could
figure
out
some
way
to
set
up
a
asset
manager,
tool
and
I.
A
Don't
know
whether
it's
going
to
be
something
more
like
file.
Energy
or
something
more
like
media,
or
something
more
like
what
WordPress
has,
but
there's
a
bunch
of
places
that
I
think
this
is
going
to
solve
some
problems
for
us
right
now.
We
have
some
pretty
serious
core
books
where,
if
you
place
an
image
somewhere,
for
example,
into
a
block,
and
then
you
delete
the
block
that
image
will
never
get
deleted.
A
So
if
you
accidentally
upload
something
that
could
be
super
bad
news
to
your
site
and
then
you're
like
oh
I,
need
to
take
that
off
my
site.
It's
super
bad
news
and
you
delete
the
block.
You
can't
actually
delete
the
image,
there's
no
user
interface
anywhere.
That
will
let
you
get
to
that
image
that
was
previously
uploaded
and
delete
it.
So
if
you
have
database
access,
you
can
of
course
go
into
the
database
tables
and
delete
them.
A
You
can
go
on
to
disk
until
eight
to
file,
but
I
think
we
need
a
user
interface
to
manage
this
stuff
too,
and
so
trying
to
figure
out
what
that
user
interface
looks
like
and
how
to
integrate
it.
The
rusted
backdrop
is
going
to
be
a
huge
undertaking,
and
so,
but
it's
also
something
that's
really
important
right
like
media
management.
Media
is
one
of
the
top
modules
for
Drupal.
Media
management
is
something
that's
makes
wordpress
a
killer
tool.
A
It
would
be
great
if
we
could
start
thinking
about
how
to
solve
our
media
problem
in
backdrop
as
well
and
create
something
that's
super
well
integrated
with
all
of
the
bits
and
pieces,
like
the
rich
text,
editor
on
the
article
creation
interface
like
all
the
stuff
that
we
need
to
manage
at
any
file
upload
field,
and
so
I
put
it
on
the
list
here
to
talk
about
prioritizing
for
16,
because
I
thought
that
one
of
the
solutions
we
were
approaching
for
the
previous
image
is
saluted
by
garbage
collection
issue
was
going
to
be
dependent
on.
A
A
Maybe
what
would
be
better
is
if
we
schedule
that
for
17
and
focus
all
of
our
effort
for
16
on
references,
because
that's
not
missed
two
releases
that
we
can
get
reference
is
done
in
16,
then
we
can
kind
of
change
gears
and
focus
on
media
for
17
I,
wanted
to
throw
it
out
there
and
see
what
you
guys
thought
about
doing
a
media
solution
in
backdrop.
A
A
Is
one
somewhere
in
the
key
ellipse
one
one
of
the
old
ones
that
I
dug
up
during
the
15
released
when
we're
working
on
that
bug
fix
for
images
automatically
deleted
in
court?
It
was
something
like
I
can
find
it
in
yeah.
D
A
And
it
had
like
all
the
different
places
it
needs
to
integrate
and
how
like,
if
we're
gonna,
be
putting
in
something
that's
going
to
have
api's
we've
got
to
make
sure
that
you
know
we
get
it
right,
because
we
aren't
gonna
be
able
to
change
those
until
backup
do
so.
D
A
Then
it
could
be
that
some
of
the
sub
issues
get
slated
for
16,
but
the
major
feature
gets
added
later
and
that
would
give
us
some
time
to
for
you
know
if
we,
if
we
can't
get
them
main
issue
in
until
we
get
these
other
problems
solved,
we
could
have
a
recourse
for
that.
Okay
sounds
good.
A
A
Okay,
we
also
moved.
We
have
this
meta
issue
for
improving
the
rich
text
editor,
and
we
got
a
couple
of
fixes
in
for
that
in
at
the
last
minute
before
15,
which
is
good,
there's
a
bunch
more
that
we
need
to
work
on
and
so
that
meta
got
pushed
to
16.
I
think
this
is
the
kind
of
thing
where
we're
always
going
to
be
improving
and
iterating
on
that
rich
text
editor,
because
everybody
is
always
going
to
use
it.
So
it's
good
that
we
have
an
issue
we
can
continue
to
kind
of
push
along.
A
I
would
love
to
see
that
get
a
little
more
attention.
So
if
anyone
is
pretty
feel
interested
in
working
on
ckeditor
plugins,
that
could
be
a
good
place
to
work.
It's
issue
number
at
1087.
In
the
backdrop,
q,
all
right
it,
we
do
have
a
road
map
on
dr.
CMS,
org
I,
updated
it
a
couple
weeks
before
the
1.5
release,
so
that
we
could
see
what
the
1.5
atleast
would
look
like
without
references
in
it,
and
but
it
is
what
we're
going
to
do
for
once.
A
16
is
still
kind
of
up
near
so
yeah
I
would
say
this.
Let's
see
what
we
think
like
right
now
we
only
have
one
major
feature
slated,
and
that
is
references
module
which
is
going
to
be
big,
but
it
will
be
great
if
we
could
figure
out
what
other
features
can
wanted
to
see
in
16.
So
we
can
get
a
little
priority
for
what
we
should
be
working
on
the
next
few
months.
E
B
E
Right
these
are,
ladies
for
the
two
past
weeks,
since
we
skip
that
section.
On
the
previous
step
meeting,
we
have
313
total
project
on
backdrop,
CMS
the
dog
nursery
kidnap,
that's
plus
four,
since
last
meeting
229
projects
with
official
releases
on
backdrop,
CMS
dog,
that's
plus
five.
Since
last
meeting
367
releases,
that's
project
releases,
a
does,
plus
12
56
total
backcountry
bar
thurs.
A
A
We
have
bad
camp
coming
up
soon.
We've
got
a
bunch
of
good
things
going
on
in
bad
camp.
We
have
a
backdrop
summit
which
will
be
happening
on
thursday.
We've
got
a
bunch
of
speakers
lined
up
I'll,
probably
update
that
age
on
the
bad
campsite.
We
have
a
back
from
training
which
will
be
all
day
on
friday.
We
have
a
session
which
will
either
be
saturday
or
sunday,
and
I
just
wanted
to
throw
it
out
to
anyone.
We
lost
Luke
use
earlier.
A
Anyone
who's
going
to
be
a
bad
camp
who
wants
to
dissipate
in
any
of
these
events,
I
think
will
be
great
to
get
as
many
people
as
possible
representing
backdrop.
I
don't
want
it
to
be
Nate
and
I,
giving
another
top
on
backdrop
at
band
camp
I
want
it
to
be
the
backdrop
community
talking
about
backdrop
at
that
camp,
and
so
we
talked
a
little
bit
about
it.
A
little
bit
in
the
outreach
meeting,
we're
going
to
have
Wesson
Jack
participate
in
the
summit.
A
A
jackal
help
with
the
training
West
Jekyll
both
be
in
the
talk.
I'll
also
want
to
reach
out
to
Jim
birch
he's
going
to
be
there
the
see
if
he
wants
to
get
involved.
People
who
aren't
necessarily
can
see
members
but
who
are
involved
in
backdrop
should
also
feel
comfortable
talking
about
it
at
that
camp.
So
just
anywhere
we
can
get
people
involved.
They
think
it's
going
to
be
good,
just
kind
of
show.
A
You
know
it's
been
a
couple
years
but
like
there
is
a
community
behind
this
thing,
and
these
are
the
faces
that
are
representing
it
not
necessarily
like
same
people.
You've
heard
from
before
so
I,
don't
know
Jeff
if
you're
going
to
be
here
for
bad
camp,
probably
not
you're,
pretty
far
away
yeah,
but
anyone
who
is
interested
watching
this
video
later
you
want
to
be
a
part
of
these
things.
Let
us
know
all
right.
A
If
you're
interested
in
buying
a
book,
there
are
two
books,
beginning
backdrop
and
migrating
from
triple
left
vailable
in
a
press
and
Amazon
I'm
feeling
like
we
can
probably
remove
that
item
from
this
weekly
agenda,
because
we
talked
about
all
time
there
on
the
website.
They've
been
up
for
a
while
that
okay
general
discussion,
Oh
amazing,
who
is
our
designated
note-taker
this
week?
A
Thank
us
so
one
of
the
things
we
also
talked
about
and
trying
to
make
these
meetings
more
effective
is
to
have
somebody
take
notes
during
the
meeting
and
create
a
list
of
follow-ups
that
we
should
do
and
that
way
we
can
plus
this
information.
I,
don't
know
where
we're
going
to
post
it
long
term,
but
for
now
I'll
post
it
in
get
ur.
A
C
Issues
of
faces
I'm
going
I'm
trying
to
go
through
and
do
a
tutorial
of
how
someone
could
something
the
basis,
and
so
I'm
actually
doing
it
myself
and
running
into
like
little
dumb
issues
that
a
few
of
them
are
hard
to
fix.
They
are
hurting
my
brain.
So
if
anyone
wants
to
check
that
out,
I
will
put
it
in
the
follow-ups
and
a
link
to
the
project
that
I
cooked
up
I.
C
E
Document
has
created
the
the
hero
versions
of
the
layouts,
which
are
actually
they
have
a
container.
That's
that's
a
big
help.
I,
don't
know
how
what
what
we
plan
to
do
with
the
actual
poor
to
allow
them
to
have
full
width,
but
this
is
a
good
workaround
for
people
that
want
to
get
it
down
now,
sort
of
so.
E
A
When
we
originally
put
in
layouts
it
was
in
14
and
it
went
in
again
like
the
night
before
release
and
we're
like.
Oh
that's,
good
push
right
and
then
here
we
are
in
15
/
like
let's
add
the
hero
thing
and
we're
like
oh
wait.
This
doesn't
work
because
we
made
a
mistake
back
in
14,
and
now
we
have
this
problem.
We're
changing
the
markup
and
core
is
hard
right.
A
That's
kind
of
an
API
change,
because
anyone
who's
over
in
those
templates
aren't
going
to
get
the
changes
that
you
push
to
the
core
versions
and
anyone
who's,
depending
on
the
mark
up
being
in
the
format
of
the
core
version
for
their
CSS,
might
have
their
CSS
break,
and
so
we're
stuck
in
this
like.
How
do
we
change
the
mark-up
of
the
layouts?
Now
that
oops
we
got
it
wrong,
it's
fine!
A
How
do
we
fix
it,
and
so
we
decided
to
do
short
term
and
talk
Lamont
made
this
counter
project
called
hero
that
adds
an
extra
enter,
the
Elias,
the
hero
region
to
being
cool
with,
but
it
does
override
all
10
bar
layouts.
So
we
were
talking
a
little
bit
about
it
in
basis
for
were
like,
should
we
just
override
the
court
layouts
and
bassist
theme,
so
you
can
see
how
these
work
I
think
that
might
be
a
good
option
for
getting
these
in
decor
I.
A
Don't
think
we
can
just
change
the
ones
in
core
because
the
ones
in
core
that
might
break
people's
sites,
but
we
should
also
slate
this
for
12
or
backdrop
to
wear
what
one
of
the
things
we
need
to
fix
is
the.
B
A
In
the
core
layouts,
so
that
we
don't
have
this
kind
of
cascading,
where
we
put
the
big
solution
so
I
don't
know
Wes.
If
you
want
to
take
a
look
at
that
project
and
see
what
you
think
of
that,
markup
yeah
would
be
a
good
candidate
for
basis.
I
know,
/,
adding
10
layouts
is
not
ideal.
It
makes
it
messy
for
like
having
a
nice
clean
starting
point,
but
if
it
fixes
this
problem
that
might
be
worth
the
mess
good.
C
A
Yeah
I
think
I,
don't
really
I
could
do
it
too.
The
people
yeah
with
a
special
like
hero
region
right.
C
A
C
Basically
be
like
a
version
of
the
existing
home
page
layout
and
just
call
it
like
you
know,
whatever
it
is
underscore
hero
or
something
I
don't
know,
but
yeah,
including
my
basis,
would
also
work
just
typed
it,
but
it
does
bring
it
the
problems
of
if
somebody
makes
a
basis
site
now.
Does
that
mess
them
up,
because
if
they
sub
teamed
off
of
it
they're
going
to
inherit
things
yeah.
A
B
A
Then,
of
course,
when
it's
waiting
increases
the
risk
of
people
using
it
yeah,
it's
definitely
messy,
but
I
knew
I
liked
the
idea
of
doing
a
new
layout.
But
again
that's
the
kind
of
thing
where,
if
we
can
get
it
in
151,
we
can
switch
the
home
page
to
use
the
new
home
page
layout.
But
if
we
wait
very
long,
we're
gonna
have
two
sure.
E
C
C
One
thing
of
the
basis
can
trib
a
theme
but
I
I
changed
the
theme
name
and
still
there
so
now
its
basis
under
stork,
contribs
I
put
in
the
readme
like
this,
is
you
know
a
version
of
the
core
theme
but
to
work
on
experimental
features
and
maybe
add
features
in
here
that
we're
not
going
to
add
two
core.
So
that's
around
nothing's
new
in
it
right
now,
it's
exactly
the
same
as
the
core
version,
with
like
a
few
additional
files
that
I
took
out
four
chord
that
don't
really
affect
anything.
C
Okay,
a
point
does.
C
A
C
A
Ok
well,
thank
you,
wes
for
being
our
designated
note-taker
excellent
job.
Also,
let
us
know
what
you
think
about
like
the
format
of
these
meetings.
This
one
is
kind
of
halfway
between
what
we
had
and
what
we
might
eventually
get
to,
but
I
think
it
kind
of
worked
I'm
not
lets
the
keep
an
eye
on
and
going
forward,
though,
and
see
if
we
think
it's
helping
or
hurting
or
what.
If
what
else
we
should
drive,
it
is
I.