►
From YouTube: Backdrop Weekly Meeting 11/21
Description
Backdrop Weekly Meeting 11/21
B
Okay,
obviously,
we
have
a
really
horrible
delay,
but
that's
better
than
everything
else.
B
Okay,
so
I
guess
really
quickly:
we
should
go
back
over
the
goals
for
backdrop,
and
the
big
picture
is
basically
that
we
just
don't
want
to
change
the
apis
very
much
from
drupal
7..
There
are
four
things
that
we're
going
to
be
able
to
work
on
number
one.
We
want
to
take
all
of
the
new
features
that
we
have
in
drupal
8
and
basically
back
port
them
to
drupal
7.
B
number.
Two.
We
want
to
simplify
existing
systems
whenever
we
can,
we
obviously
want
to
fix
bugs.
So
that's
all
of
the
bug
fixes
that
are
in
drupal
8,
as
well
as
any
other
sensible
changes
that
we
can
work
on
at
the
same
time
and
then
also
add
new
features
within
reason
for
our
time
frame,
we're
hoping
to
have
backdrop
1.0
out
sometime
before
triple
h.
B
So
we
have
a
list
of
things
we
really
want
to
get
done
and
as
soon
as
we
get
those
things
done,
we
can
release
basically
any
time-
and
I
think
the
sooner
the
better,
but
we
do
need
to
make
sure
that
we
at
least
make
significant
progress
away
from
triple
seven
and
into
our
own
landscape.
B
So
in
terms
of
what
we
need
to
be
making
progress
on
the
big
issue
is:
we've
got
a
lot
of
commits
that
have
been
made
to
dribble
eight
and
we
need
to
make
all
those
same
changes
or
at
least
solve
problems
in
in
similar
ways
to
backdrop.
So
we
want
to
go
through
the
entire
get
commit
history
of
drupal
8.
Look
at
all
the
stuff.
B
B
I
think
the
biggest
thing
we
need
to
work
on
is
is,
first
of
all,
making
that
list
of
things
that
we
need
to
work
on
by
comparing
the
drupal
8,
commit
history
to
to
our
goals
and
then
working
through
those
issues,
and
so
I
think
first
and
foremost
is
we
need
a
volunteer
to
start
working
through
that
list
of
issues.
I
know
nate
and
I
have
both
talked
about
doing
it
over
the
past
two
few
weeks.
Neither
one
of
us
had
ended
up
having
time
to
do
it.
B
So
if
there's
someone
on
this
call
or
someone
who
watches
this
video
later,
who
is
really
interested
in
going
through
that
list
of
commits
and
figuring
out
how
to
get
those
into
a
meta
issue
for
us
to
work
on?
That
would
be
something
that
we
would
really
love
help
with.
A
Yeah,
so
the
work
that's
involved,
there
is
looking
at
the
drupal
8
history
like
through
the
git
history.
A
A
visual
tool
really
helps
with
that,
like
I've
been
using
sourcetree
and
going
through
and
actually
looking
at
every
individual
commit
that
is
in
the
drupal
8
history
since,
since
the
the
branch
point
and
evaluating
is,
is
this
a
change
that
we
need
to
make
in
backdrop
as
well?
A
lot
of
them
are
really
simple.
A
lot
of
them
are
bug
fixes,
so
many
things,
like
literally
hundreds
of
commits,
are
just
like
reapply,
the
patch
from
from
triple
h
to
backdrop,
but
a
lot
of
them.
A
C
A
Like
we
yeah,
we
don't
have
any
immediate
volunteers.
That
seems
to
be
the
this
seems
to
be
the
situation.
B
C
I'm
going
to
take
a
stab
at
it.
I
think
that
I
I
mean,
I
think
my
hesitation
about
volunteering
is
that
I
really
don't
know
core
very
well
and
so
evaluating
what
should
go
in
and
what
should
not
feels
like
it's
a
little,
but
I'm
certainly
wouldn't
take
a
stab
at
just.
You
know:
pasting
in
the
the
hits
or
history
making
looking
and
see
whether
maybe
or
not,
and
getting
some
help
on
the
evaluation,
but.
B
Yeah,
I
think
that
that
would
actually
be
really
helpful
and
even
if
you
don't
like
you,
don't
feel
comfortable
making.
The
decision,
I
would
say
just
include
whenever
you
don't
know,
include
something
and
you
can
ask
us
about
it
and
we
can
just
say:
oh
no,
that's,
okay!
We
don't
need
to
do
that
because
of
whatever
and
then
you'll
know
for
next
time,
so
just
kind
of
err
on
the
side
of
including
more
and
then
we
can.
We
can
help
walk
you
through
those
decisions,
too.
Okay,
okay,
great.
B
All
right,
so
we
also
have
a
list
of
major
projects
or
tasks
that
are
large
enough.
That
they're
not
just
going
to
be
a
single
issue
in
our
cube,
but
they're,
probably
going
to
be
a
series
of
them
and
and
the
the
first
one.
The
big
thing
we
need
to
get
done
for
backdrop
is
to
get
cmi
moved
over
and.
C
B
That
we've
talked
about
doing
this
a
couple
of
different
ways
in
the
issue
queue,
but
we
need
someone
to
kind
of
own
it
and
and
take
charge
of
making
whatever
changes
are
necessary
in
order
to
get
cmi
working,
probably
based
on
the
current
version
of
cnn
cmi,
as
opposed
to
the
version
that
we
currently
had
in
in
backdrop
before
so
nate.
I
don't
know
if
you
want
to
talk
a
little
bit
more
about
that.
A
Yeah
so
yeah
it's
it's
a
it's
a
little
bit
of
a
tough
one
to
actually
analyze
the
entire
situation.
So
what
we
have
or
what
is
most
readily
accessible
to
us,
is
that
our
forking
point
in
backdrop
february
29th
2012,
was
just
before
the
initial
version
of
cmi
was
committed
to
the
repository.
So
we
have
available
to
us
like
a
traditional
procedural
drupal
based
module
that
drupal
7-ish
module
for
configuration
that
we
could
start
with
and
merge
that
into
backdrop
and
then
and
then
start
from
there.
A
A
What
we're
familiar
with
some
downsides,
though,
is
that
well
for
the
most
part,
it
doesn't
doesn't
really
quite
work,
it's
and
it's
all
in
xml,
rather
than
drupal
8,
moved
towards
yaml,
and
I
think
we're
likely
to
move
towards
json
for
storing
our
configuration
files.
A
The
the
other
option
is
starting
with
what
drupal
8
has
and
back
porting
it
into
into
backdrop,
but
I'm
worried
about
that
approach
as
well,
because
there's
so
many
subsystems
in
drupal
8
that
just
have
no
equivalent
anymore
in
in
triple
seven
or
in
backdrop,
and
so
if
we
try
to
backboard
things,
we're
going
to
find
that
most
of
the
code
because
of
the
level
of
complexity
in
triple
eight
most
of
the
code,
isn't
exactly
directly
portable
at
all.
A
So
I'm
a
little,
I
don't
know
I'm
worried
about
both
approaches.
I'm
not
really
sure
which
way
is
better
drupal
8
is
overly
complicated
and
the
cmi
version
that
we
have
that
we
can
merge
in
is
is
not
mature
enough.
A
So,
whichever
approach
we
take,
I
think
that
we're
looking
at
a
lot
of
work,
so
I'm
not
really
sure
which
way
to
go,
maybe
maybe
a
mix
of
both
of
starting
with
what
we
have
in
the
the
cmi
branch
already
and
then
trying
to
back
port
the
drupal
8
changes
into
that
module
might
be
the
best
approach
where
it
starts
us
with
something
that
we
can
then
work
on
as
opposed
to.
A
So
either
either
way
could
work,
but
both
are
going
to
be
a
lot
of
work.
B
Okay,
so
I
guess
the
the
first
question
is:
do
we
have
any
volunteers
on
the
call
we
want
to
take
her
on
owning
the
cmi
project
and
then,
if
not,
if
anyone
watches
this
on
the
video
later,
let
us
know
this
is
something
you're
really
passionate
about
working
on.
B
B
The
next
thing
that
we
need
to
work
on
is
moving
views
into
core,
and
I
think
you
have
some
ideas
about
how
we
can
do
this
as
well.
That
differs
from
how
drupal
8
did
it.
A
Yeah
I
I
can
only
imagine
that
tim
plunkett
is
going
to
watch
this
video
and
laugh
at
me
when
I
say
these
next
couple
of
things,
but
so
be
it.
A
A
But
I
think
that
for
the
most
part,
what
we're
hoping
to
do
for
backdrop
isn't
do
a
whole
lot
of
rewriting,
which
has
a
couple
of
benefits
that
makes
it
so
that
porting
is
more
direct
from
drupal
7
to
backdrop.
A
If
we
try
to
well
kind
of
like
everything
in
backdrop,
changes
as
little
as
possible
and
move
move
the
the
pieces
of
software
that
we
want
to
move
into
core
like
directly
in
with
with
little
or
no
changes
whatsoever.
A
So
the
re
like
the
re-architecting
or
improvement
of
all
of
the
the
handlers
that
went
into
dribble
eight,
probably
isn't
something
that
we
want
to
start
off
with
immediately.
A
Instead,
we
want
to
basically
take
the
parts
of
c
tools
that
views
depends
on
which
include
like
the
temporary
data
store
and
the
exportable
system
and
take
those
and
make
them
part
of
backdrop
directly
and
then
other
than
that
just
throw
in
views
entirely
into
core,
as
is
so
oh
plus,
distribute
all
the
plugins
throughout
all
of
the
different
throughout
all
the
different
core
modules.
Of
course,
so
node
module
would
own
its
own
own
handlers
and
things
like
that.
B
No
okay!
Well
again,
if
anyone
watches
this
video
later
and
wants
to
help
on
this,
let
us
know
we
need
someone
to
kind
of
own
these
things
and
and
and
start
getting
them
moving.
So
we
are
open
to
any
of
that
at
any
point
not
necessary
to
volunteer
today
and
then.
The
next
thing
we
want
to
work
on
is
some
equivalent
of
blocks
and
layouts,
but
we
also
had
some
ideas
on
how
that
would
be
different
than
what
we
were
thinking
was
going
on
in
interplay.
A
A
Okay,
so
blocks
and
layouts.
So
I
think
there's
been
a
couple
of
stabs
of
this
actually
through
the
triple
eight
cycle
that
actually
were
really
pretty
good
starts.
I
remember
gabor
put
together
a
module
called
the
page
module
at
one
point,
which
actually
was
a
pretty
good
starting
point
and
bojan
has
put
together
multiple
different
efforts,
describing
how
he
thinks
that
the
blocks
and
layouts
should
work.
A
The
basic
concept
is
isn't
too
difficult
to
grasp.
A
What
we're
thinking
about
doing
is
implementing
something
that
is,
I
mean
if
you
were,
if
you
were
to
take
a
look
at
analogs
in
drupal
7
it
it's
analogous
to
the
panels
module,
but
the
panels
module
is
ridiculously
kind
of
heavy
like
it's
it's
complicated
and
it's
got
a
lot
of
things
going
on,
but
the
basic
concepts
are
there
that
that
we
want
to
borrow,
and
that's
basic
things
like
the
layout
is-
is
separated
from
the
theme
in
panama's
module
when
you're
using
something
like
panels
everywhere.
A
You
no
longer
have
theme
regions.
You
instead
only
have
regions
provided
by
by
your
layout.
I
guess
in
in
panels
land
I'm
not
really
sure
what
what
are
they
called
in
panels
where
they
have
that
they're
equivalent
of
regions
they're
still
called
regions?
Okay,
so
so
imagine
that
we
ship
with
something
like
a
layout
module
and
a
layout
module,
accepts
the
responsibility
of
providing
regions
to
the
site.
A
So,
instead
of
themes
having
regions,
the
layout
module
provides
like
say,
four
to
six
regions
out
of
the
box
with
backdrop
and
all
themes
simply
style
those
regions.
So
if
you
had
a
really
comprehensive
theme
that
that
was
intended
to
be
used
with
backdrop,
you
would
include
styling
for
the
like
the
four
to
six
layouts
that
come
with
that
come
with
core,
and
this
makes
it
so
that
you
can
switch
between
themes
like
at
any
time
and
still
maintain
all
of
your
layouts.
A
This
whole,
like
every
theme,
has
its
own
different
set
of
regions,
makes
for
a
lot
of
craziness.
It
makes
say
you
can't
rebuild
your
theme
or
you
can't
switch
between
themes.
Themes
are
responsible
for
a
ridiculous
amount
of
layout
and
if,
if
instead
layout
module
was
providing
all
of
the
layouts
for
the
entire
site,
then
every
theme
would
sort
of
naturally
be
responsive
because
the
layouts
themselves,
the
core
comes
with,
would
all
be
responsive,
thereby
making
all
themes
responsive.
A
Of
course
I
mean
there's
the
things
inside
of
the
the
layouts
that
still
need
to
be
responsive
as
well,
but
for
the
most
part,
if
the
layout
is
responsive,
that
the
theme
kind
of
is
naturally
responsive
because
it
it's
just
styling
on
top
of
the
layout
as
far
as
page
layouts
go.
What
I
was
thinking
of
is
that
probably
out
of
the
box,
you
probably
only
use
two
layouts
you'd
have
like
a
home
page
layout
that
was
different
and
then
like
everything
else
layout.
So
let's
say
your
everything
else.
A
But
if
you
had
other
pages
on
the
site
that
you
wanted
to
give
them
custom
layouts,
then
you
would
have
an
interface
that
said.
Okay,
this
is
the
list
of
all
pages
on
the
site
site
that
are
using
layouts
currently
and
by
default
it
would
only
be
the
home
page
has
a
different
layout
and
then
everything
else
would
fall
back
to
the
default
layout.
A
But
if
you
had
another
path
that
you
wanted
to
layout
at
say
you
had
like
a
a
heading
page
like
a
I
don't
know
like
a
main
section.
Let's
say
you
had
a
podcast
page
and
the
podcast
page
is
at
slash
podcast,
and
it
has
some
different
appearance
that
has
like
header
images
and
a
a
couple
of
different
views,
and
things
like
that,
then
you
could
say
I
want
to
add
a
new
page
and
start
with
the
layout.
A
So,
basically,
exactly
like
panels
or
page
manager,
where
you
say,
add
a
new
page
at
slash,
podcast
and
give
it
this
layout
and
then
inside
of
when
you're
editing
the
layout
then
drag
in
the
individual
blocks
and
views,
and
things
like
that
that
you
want
to
actually
place
in
that
layout
and
besides
creating
new
pages,
you
should
also
be
able
to
take
any
existing
url
and
say
I
want
to
take
this
page,
which
currently
is
just
returning
a
piece
of
content
and
wrap
it
in
a
layout.
A
So
if
you
had
a
piece
of
node
content,
for
example-
and
let's
say
at
node
10
or
something
like
that-
and
you
wanted
to
give
that
node
an
individual
layout,
then
on
your
list
of
layouts,
you
would
say
I
want
to
add
a
new
page
at
node
10
and
it
would
allow
you
to
wrap
the
existing
content
of
node
slash
10
in
a
layout.
So
you
could
take
the
content
area
and
place
it
in
the
sidebar
or
down
below
and
and
put
a
header
image
up
at
the
top
or
something
like
that.
A
I'm
probably
I
don't
know
I'm
it
feels
like.
I'm
super.
Simplifying
this,
but
basically
what
what
I'm
seeing
is
is
a
a
strip
down
version
of
panels
plus
page
manager.
A
That
makes
it
so
that
all
layouts
are
controlled
by
the
this
individual
module
and
we
we
get
rid
of
the
idea
of
regions
and
layout
being
owned
by
the
theme,
and
it
all
becomes
owned
by
modules
that
provide
these
layouts.
So
basically,
a
very
panels-esque
way
of
approaching
things,
but
with
hopefully
a
little
less
complication
than
panels
itself
has.
A
B
It's
probably
enough
explanation
for
now:
we've
got
a
couple
of
issues
too,
that
that
talk
about
building
a
drag
and
drop
interface
and
for
replacing
stuff
and
and
other
ideas
about
how
to
make
that
work.
So
the
big
thing
for
for
this
call
is
if,
if
that
sounds
really
exciting
to
anyone,
if
we
have
anyone
who
wants
to
kind
of
own
getting
that
going,
it's
kind
of
the
one
feature
that
we
would
like
to
add.
B
On
top
of
what
drupal
8
is
doing
to
try
and
set
ourselves
apart
a
little
bit,
it's
something
that
you
know
they
they've
been
working
on
in
drupal
8
for
a
long
time
didn't
actually
happen.
So
if
we
could
make
that
happen,
it
would
look
really
cool
again.
It's
not
it's
not
make
or
break
it
for
us,
but
it
would
be
really
nice
to
have
that
problem
solved
once
and
for
all,
and
then,
if
we
don't
have
any
volunteers
now,
that's
also
fine.
B
But
if
anyone
watches
this
later
and
really
wants
to
work
on
that,
let
us
know
we
could
certainly
use
your
help.
A
Yeah
I'd
like
to
do
the
work
on
on
the
layout
system,
just
because
I've
built
a
couple
systems
in
the
past
that
are
really
similar
and
I
feel
like
I've
got
a
I
mean.
I
have
a
good
grasp
on
what
I
think
I
I
want
it
to
be,
of
course,
but
we'll
see
if
it
met
if
it
jives
with
everybody
else.
But
I
I
think
that
there's
just
so
much
stuff
that
needs
to
be
done.
A
That
is
kind
of
it's
not
prerequisites
but
like
the
priorities
of
things
are
probably
cmi,
is
number
one
and
then
followed
closely
by
views
that
I'll
probably
be
pushing
my
efforts
towards
those
two
goals.
First,
at
least
until
we
get
someone
who
who
volunteers
to
become
a
lead
on
those
those
items
and
then
address
blocks
and
layouts
later.
But
if
somebody
else
comes
in
and
steps
up
to
do,
cmi
and
views,
then
blocks
and
layouts
is
really
where
I
want
to
be.
B
Okay,
so
next
up
on
our
kind
of
big
issues
that
we
want
to
work
on
is
the
theme
system
cleanup.
There
is
an
issue,
in
the
backdrop
queue
for
adding
twig
to
backdrop.
That
is
probably
not
going
to
happen
for
backdrop
1.0,
but
there
is
a
bunch
of
other
stuff
that
we
need
to
do
to
the
theme
system
to
make
it
make
more
sense.
B
The
drupal
7
theme
system,
as
we
all
know,
is
kind
of
a
bit
of
a
mess
and
there's
a
lot
of
work
that
we
can
do
to
improve
that
it
isn't
quite
such
a
drastic
change
as
replacing
the
entire
theme
engine
from
php
template
to
twig,
and
so
I
would
like
to
head
up
that
kind
of
project
to
to
get
things
sorted
out
and
figure
out
how
much
we
can
do
in
terms
of
cleanup
with
the
what
we
have
without
having
to
break
too
many
apis.
B
But
I
would
love
some
help.
So,
if
there's
anyone
who's
kind
of
a
friend
of
ninja,
I'm
I'm
not
very
frightened.
In
spite
of
my
work
on
jupiter,
I
would
love
some
some
help
in
that
area
too.
So,
if
there's
any,
who
wants
to
work
on
front-end
stuff,
let
me
know
and
I'd
love
to
get
you
involved
on
kind
of
what
I
think
we
should
do,
based
on
what
I've
done
for
drupal
8
and
see
if
that
can
kind
of
fit
in
nicely
with
backdrop
as
well.
B
There's
a
bunch
of
other
littler
things
that
we
are
planning
on
working
on
in
backdrop
of
before
the
release,
but
those
are
kind
of
the
big
major
projects
that
we
need
to
have
people
in
charge
of
moving
them
forward
from
now
until
we
get
done
with
it.
So,
if
there's
anyone
who
has
anything
else
that
they
want
to
work
on,
that's
not
in
that
list
feel
free
to
continue
working
on
it,
but
just
know
that
our
priorities
are
kind
of
in
in
those
main
areas,
at
least
for
the
short
term.
B
In
terms
of
the
the
rest
of
this
agenda.
The
next
item
is
sprints.
We
probably
will
schedule
some
in-person,
sprints
or
longer
periods
sprints
at
some
point,
but
right
now
we're
planning
on
doing
is
just
meeting
on
irc
and
continuing
to
work
on
thursdays
after
this
phone
call.
B
I
know
some
of
you
may
not
be
located
in
the
u.s
and,
if
you're
in
europe,
it's
probably
very
late
at
night-
and
you
don't
want
to
work
after
this
phone
call,
so
we
could
probably
be
talked
into
working
thursday
mornings
as
well
before
this
phone
call,
but
for
now
we'll
probably
meet
all
on
irc
and
continue
to
work
on
backdrop,
thursday
afternoons.
B
So
if
you
want
to
get
together
and
work
on
stuff,
then
that's
a
good
time
to
find
us
there's
a
couple
of
other
things
that
we
need
to
work
on.
That
aren't
actually
backdrop
itself.
We
obviously
need
a
website.
B
We
were
thinking
that
we
could
build
one
out
of
drupal
7
for
now
and
then
one
backdrop
was
ready.
We
could
upgrade
from
seven
to
backdrop,
and
that
would
also
be
a
really
good
test
case
of
our
ability
to
you
know,
move
any
client
projects
or
any
website
in
the
world
from
7
to
backdrop.
So
that
would
be
a
good
test
case
for
that,
but
in
terms
of
our
own
website,
we're
gonna
need
design.
B
We're
gonna
need
a
designer,
we're
probably
gonna
need
a
new
logo,
and
so
we're
gonna
need
to
to
put
some
put
aside
some
time
and
effort
to
get
that
going
and
then
we're
also
going
to
need
some
content.
We
obviously
have
right
now
a
manifesto
and
we
have
the
start
of
a
handbook,
but
we
don't
really
have
content.
We
don't
have
any
content
strategy
underway
for
our
actual
website.
So
if
we
have
anyone
who's
really
good
at
content,
copywriting
or
content
strategy,
we
could
use
help
in
those
areas
as
well.
B
I
know
we've
had
a
couple
of
people
have
expressed
interest
in
that
before,
but
it
might
be
time
to
get
going
on
those
now,
so
he
gives
help
in
those
areas
as
well.
Our
indiegogo
campaign
has
ended,
that's
something
that
nate
mentioned
the
beginning
of
the
call,
but
we
are
going
to
work
on
alternate
ways
to
take
funding
for
people.
Who've
had
a
couple
people
reach
out
to
us
and
say:
oh
no.
B
I
want
to
give
you
monday,
but
your
campaign's
over,
so
we're
going
to
come
up
with
some
kind
of
paypal
donation
form
or
something
else
that
we'll
put
on
the
website
to
try
and
still
take
people's
money.
A
At
least
at
least
with
some
other
progress
there,
we
did
set
up
a
bank
account
specifically
for
for
backdrop.
That
is,
is
right
now,
just
a
checking
account.
So
basically,
we
have
a
separate
location
to
actually
keep
track
of
all
the
money
that
comes
in
and
all
the
money
goes
out.
Fortunately,
right
now,
don't
it's
only
money
coming
in,
but
but
as
as
as
things
go
out
at
least
we'll
have
a
way
of
keeping
track
of
accounting
and
figuring
out
what
we're
spending
money
on.
B
And
then
I
guess
I
just
wanted
to
ask
if
there's
anything
else,
that
we
should
be
adding
to
this
weekly
meeting
for
everyone
who's
here.
If
there's
anything
in
particular,
you
came
from
that.
You
wanted
us
to
talk
about
that.
We
should
talk
about
weekly
or
anything.
You
want
to
talk
about
now
and
just
kind
of
open
up
the
floor
to
anyone
who's
joined.
B
You
you've
all
kind
of
dropped
out
in
terms
of
video.
I
don't
know
if
you're
actually
still
listening
or
not,
but
if
there's
anything
in
particular
you're
hoping
to
get
out
of
this
meeting.
We
are
here
for
you,
so
let
us
know:
okay,
nate
did
you
have
something
you
want
to
add.
A
No,
I
I
wanted
to
hear
from
michelle,
and
I
know
that
she
wrote
up
this
most
excellent
blog
post.
That
basically
was
probably
the
most
accurate
representation
of
where
we
were
hoping
to
go
with
backdrop,
and
I'm
hoping
that
well,
I
was
wondering
if
there
was
anything
michelle.
That's
that
you're,
particularly
interested
in
or
it
sounds
sounds
like
yeah.
I
saw
you
also
to
to
be
a
maintainer,
so
I
was
excited.
I
just
want
to
hear
from
you.
C
C
And
also
I
like
I
like
contributing
to
projects,
and
this
feels
like
a
very
nice
community
beginning
and
it
felt
like
a
nice
place
to
be
so
and
I'm
happy
that
we're
having
these
calls.
It
sounds
good,
so
yeah,
I'm
just
gonna
keep
you
know,
checking
away
and
as
I
said
I
mean
I'm,
not
I'm
not
I've
most
of
the
work,
I've
actually
all
the
work
I've
done
on
drupal
has
been
on
contrib,
so
I
haven't
really
so
I
really
haven't
touched
course.
I
don't
really
know
core
at
all.
B
C
A
Yeah,
I
think
you'll
find
that
the
core
is
surprisingly
not
not
anything
special.
B
C
A
So
right,
hopefully
I
mean
it'd,
be
even
it'd
be
better
if
we
can
actually
make
it
so
that
the
things
that
you
don't
understand
are
probably
things
that
are
too
complicated
to
begin
with,
at
least
that
that's
my
general
opinion
on
things
is
like
it's
like.
If
I,
if
I
don't
understand
this,
how
can
I
expect
other
people
to
use
it
right,
yeah,
so
we're
hoping
hoping
to
make
the
things
that
are
difficult
to
understand,
easier,
cool,
cool.
B
Okay,
okay!
Well,
I
guess
that's
probably
all
we
need
to
cover
in
our
first
meeting.
Hopefully,
people
watch
the
video
and
we'll
get
some
volunteers
for
people
who
want
to
work
on
cmi
views
blocks
and
layouts
and
if
not,
we'll
just
meet
again
this
time
next
week-
and
hopefully
we'll
have
made
some
progress
on
on
those
issues
by
then
and
be
able
to
bring
you
some
updates.
A
Yeah,
okay,
kevin
just
asked
a
question
that
that
we
could
answer
real
quick,
but
it's
yeah,
it's
kind
of
long
term.
It's
basically
asking
about
contrib
like
what
should
we
do
for
for
contributed
modules,
which
I
don't
know,
I'm
not
sure
if
we've
actually
expressed
this
on
recordings
yet
so
so
I
can
elaborate
on
that
real,
quick
yeah.
So
the
the
question
that
kevin
asked
is,
with
the
recent
pain
of
project
releases
on
drupal.org
after
the
drupal
7
upgrade.
Are
there
plans
for
a
more
reliable
github
based
structure
for
backdrop?
A
Can
trip?
So
we
have
an
issue
for
this.
I
I
think
it's
the
reason
it's
long
term
is
because
we
need
to
have
backdrop
cms.org
built
out
to
begin
with
and
then
we'll
work
on
managing
contributed
repositories
on
top
of
it.
Let's
see
so,
besides
the
backdrop
issue
queue,
there's
also
a
backdrop:
cms.org
issue
queue
that
is
on
github
and
there's
a
one
in
there
for
contrib.
B
A
But
the
ideas
that
we
have
focus
around
continuing
to
use
github
for
for
contributed
modules
like
marcus,
took
over
xml
rpc
module
and
turned
it
into
a
quote:
contrib
module
for
backdrop
by
making
a
separate
github
repository
for
it,
and
we
haven't
quite
figured
out
how
we're
going
to
centralize
it
quite
yet.
A
But
the
model
that
I
think
is
is
probably
easiest
to
implement
is
adopting
the
same
thing
that
jquery
did
for
their
plugin
repository,
where
their
plugin
repository
is
nothing
but
github
repositories
and
then
in
the
settings
for
each
github
repository
they
set
up
a
web
hook
in
github.
That
makes
it
so
that
you
can
say
this
repository
contains
a
jquery
plugin
and
it
automatically
registers
it
with
plugins.jquery.com.
A
That
allows
you
to
like
search
and
find
and
categorize
all
the
various
jquery
plugins,
and
it
also
makes
it
so
that
you
can
prevent
namespace
conflicts.
So
you
can
only
have
like
one
module.
That
has
a
particular
name,
for
example,
and
that
way
there
could
be
like
a
canonical.
A
I
don't
know
path,
auto
module
or
something
like
that,
even
though
there
might
be
hundreds
of
forks
or
maybe
that's
exaggerating,
dozens
of
forks
on
github
of
people
that
have
made
copies
of
path
auto
or
have
done
their
own
thing
with
path
auto.
Only
one
of
them
is
considered
to
be
like
the
canonical
source
of
path
auto
and
that
that
is
held,
like
whichever
repository
is
registered
at
backdropcms.org.
A
So
basically
we
would
keep
the
distribution
of
issue
management
repositories
and
packaging.
We
would
probably
keep
that
distributed
or
utilize
github's
infrastructure
for
it,
but
we
would
still
have
a
central
module
repository
that
all
of
the
so-called
official
modules
were
were
associated
with.
A
Yeah
so
kevin's
feedback
is
jquery
is
a
great
example,
since
they
started
with
drupal
project
module,
which
is
totally
true.
Had
it
had
an
epic
fail,
was
offline
for
one
year
and
then
returned
with
the
new
system
yeah,
although
that
was
kind
of
hilarious,
because
what
their
epic
fail
was.
A
They
literally
dropped
the
database
that
held
all
of
drupal
and
so
and
then
they
got
mad
at
drupal
for
being
so
for
being
so
dumb
that
when
they
dropped
their
database,
that
there
wasn't
some
kind
of
backup
or
something
like
that,
so
yeah
total
total
epic
fail
but
yeah
it's
the
same
sort
of
thing
where,
like
yeah,
with
the
amount
of
infrastructure
we
have
and
after
drupal
7's
upgrade,
and
I
mean
I've,
I've
been
using
triple
seven
or
dribble.org
since
the
upgrade
and
man.
A
It
is
it's
rough,
it's
rough
and
I
mean
you
could
just
yeah.
I
mean
I
mean
when
we
have
the
option
of
using
existing
tools
that
are
out
there
and
not
to
mention
like
I
don't
think
we
could
convince
people
to
sign
up
for
backdrop,
cms.org
accounts
to
file
bug
reports
and
issues
or
or
file
patches
like
trying
to
start
a
new
infrastructure.
Today,
where
people
need
to
sign
up
for
a
new
account
and
a
new
developer
community,
I
don't
think
it
would
work.
A
So
I
mean
we
have
this
problem
already,
where
we
can't
even
keep
people
on
drupal.org
using
drupal.org
tools,
even
though
they've
been
using
them
for
years,
and
I
think
that
trying
to
compete
against
github
in
this
area
is,
is
just
a
losing
battle,
so
yeah,
plus
it's
easier
and
it's
more
direct.
A
So
that's
probably
where,
where
we're
going
to
be
headed,
but
that's
all
it's
all
kind
of
down
the
road,
because
the
first
things
we
need
to
do
is
is
get
let's
get
this
core
project
done
as
well
as
build
our
main
website
and
then
then
we'll
work
on
contribute.
After
that
point,.
A
Okay,
well,
let's,
let's
call
it
a
wrap
up
and,
like
jen
said
we're
going
to
be
sprint
sprinting
today.
So
if
you
guys
are
in
the
issue,
queue
we'll
be
in
there
too
trying
to
make
some
progress
on
things.
And
if
you
have
any
other
questions,
we'll
of
course
be
in
the
rc.