►
From YouTube: Backdrop CMS weekly 4/3
Description
Status Weekly progress meeting for Backdrop CMS.
A
We
need
to
make
sure
that
they
have
a
low-cost
solution,
also,
so
we're
working
on
that
we
are
going
to
be,
including
all
of
the
bug
fixes
that
have
currently
gone
into
Drupal
7,
as
well
as
a
lot
of
the
bug
fixes
that
have
gone
into
Drupal
8.
They
won't
necessarily
be
the
same
solutions
because
Drupal
8
and
backdrop
have
different
principles
to
guide
us
so
where
drupal
8
might
have
chosen
one
particular
solution,
we
might
choose
a
different
one,
but
that
means
we
still
need
to
solve
the
bug.
A
So
there
are
some
things
in
Drupal
7
that
are
really
hard
and
confusing
for
new
end-users,
for
new
developers,
for
new
site
builders
to
be
able
to
grasp,
and
so
we're
going
to
try
and
take
these
things
and
make
them
easier
to
use
easier
to
understand,
but
in
making
that
transition.
We
also
need
to
make
sure
that
it
is
easy
for
existing
Drupal
7
modules
to
be
ported
or
existing
Drupal
sites
to
be
updated
to
get
to
backdrops.
A
We
can
get
some
new
stuff
in,
but
we're
not
going
to
get
too
much
new
stuff
in
the
requires
changing
too
much,
because
that
again
would
put
a
strain
on
the
community.
What,
instead,
we
want
to
do
is
put
in
some
things
that
change
things
a
little
bit
and
then
say
that's
enough
change
and
then
all
the
rest
of
our
new
features
will
have
to
leverage
the
existing
api's
and
we
know
there's
a
lot
of
potential
there,
because
Drupal
7
has
a
ton
of
really
great
contributed
modules.
A
We're
going
to
look
at
that
kind
of
pool
of
what
you
can
already
do
with
the
API,
so
they're
already
there
and
try
and
move
those
in
24
as
needed
only
if
it
benefits
the
majority
of
sites
that
are
using
what
will
be
backdrop,
so
we're
going
to
not
get
change
very
much
in
terms
of
ApS,
but
we're
going
to
make
a
tool
that
has
a
comparable
set
of
features
to
Drupal
8.
When
backdrop
one
point
0
point
0
comes
out,
it
might
not
be
feature
comparable
with
your
blade.
A
A
We
can
start
working
on
contribs
made
to
be
included
or
what
other
features
need
to
be
added,
and
so,
hopefully
that
by
the
time
drew
blade
comes
out,
we
will
be
comparable,
but
we
want
to
make
sure
that
we
have
a
stable
product
that
is
ready
to
release
as
soon
as
possible.
So
we're
going
to
try
and
get
it
out
this
summer,
which
should
be
exciting.
B
A
The
bar
be
made
to
Drupal,
so
since
last
week
we
made
a
ton
of
progress
on
Drupal
7
crafts
ports.
So
this
is
looking
at
bug,
fixes
and
minor
changes
that
have
been
committed
to
the
latest
stable
version
of
Drupal
7
or
even
the
latest
drupal
7,
and
seeing
if
these
changes
also
applied
a
backdrop
as
they
don't
apply
cleanly
trying
to
figure
out.
Why
and
if
they
do
just
point
them
in
making
sure
that
we
get
all
of
the
same
improvements
at
triple.
7
has
and
we've
closed
the
first
issue
we
had.
A
If
yes,
we'll
do
that,
because
we
want
the
same
kind
of
improvements,
but
if
no,
we
can
either
rethink
the
problem
or
just
leave
it
out
entirely.
So
if
you
look
at
the
Drupal,
8
meta
issues-
and
we
just
have
four-
we
now
have
three:
that's
because
we've
kind
of
reorganized
the
issues
a
little
bit,
we
will
have
4,
I'm
gonna
go
through
make
another
one.
Hopefully,
today.
A
A
whole
bunch
more
there's
a
lot
of
changes
going
on
at
your
plate,
but
we've
also
reorganized
the
ones
that
are
there.
So
I
pulled
out
all
of
the
CSS
reorganization
in
JavaScript
reorganization,
and
this
is
mainly
like
selector,
changing
like
changing
the
way
that
we
add
classes,
two
divs
to
match:
Drupal,
eights,
new
style
for
adding
classes
and
then
changing
the
way
that
we
identify
these
things
in
JavaScript.
There's
a
whole
bunch
of
conversion.
A
Issues
of
those
and
I
think
that
we
should
just
kind
of
take
a
holistic
approach
and
look
at
what
your
plates
doing
and
say.
Is
that
what
we
want
for
backdrop?
And
if
it
is,
we
can
go
ahead
and
apply
those
patches
and
if
it's
not
like
I,
think
that
personally,
the
class
naming
they
using
interpolate
is
a
little
funny
and
there
was
a
whole
bunch
of
conversations
going
on
in
Drupal
8
about
that
class.
A
Naming
we
maybe
should
look
at
those
conversations
and
see,
and
if
reading
through
all
those
issues,
we
don't
end
up
in
the
same
place,
they
did.
But
it
would
be
good
to
make
that
decision
again,
specifically
with
back
Jeff.
In
mind
what
our
goal,
who
are
you,
sir
Sir
yeah
and
bike
last
names
you
mean
CSS,.
A
Css
classes
in
IDs
and
I
think
there's
definitely
some
cleanup.
We
need
to
do
regardless
of
whether
we
use
those
patches
or
not.
So
if
we
don't
use
their
approach,
we
should
decide
on
our
own
approach
and
then
just
kind
of
holistically.
Look
at
backdrop
and
say
how
do
our
classes
work?
Can
we
do
it
consistently?
Just
so
that
makes
sense
to
people
and
same
thing
with
JavaScript,
and
so
we've
got
to
meta
issues
for
CSS
and
JavaScript.
A
B
A
So
we
need
to
look
at
these
conversion
issues
and
say:
is
there
anything
in
the
issues
that
are
the
patches
that
went
into
drupal
8?
That
is
not
in
our
list
of
major
conversions
or
fixes
to
the
system
that
we
haven't
encountered
so
I
also
pulled
out
all
of
the
cmi
related
issues
from
Hydra
plate.
Listen
put
those
into
the
sea
mi
meta
issue,
just
for
a
review
and
I
think
Nate.
It
would
be
good
since
you
worked
on
cmi
and
backdrop.
A
A
And
so
there's
a
big
chunk
of
those
and
I.
Imagine
that,
as
we
continue
working
on
creating
these
droid
metas,
there
will
be
more
of
them,
probably
less
as
time
goes
forward,
but
the
part
of
history
looking
at
right
now
and
those
get
logs
might
still
have
a
lot
of
them.
So
my
goal
for
today
go
to
blows
for
today.
First
one
is
to
finish
these.
These
Drupal
8
Meadows
I
want
to
get
at
least
a
back
to
having
four
of
them.
A
Wish
I
really
want
to
do
not
let
myself
do
that
till
I
finish
the
ecchi
step,
so
that
that's
pretty
fun
I
think
we're
making
a
lot
of
progress
in
terms
of
making
sure
that
we're
staying
up
to
date
with
everything
that's
going
on
with
Drupal,
which
I
think
is
great,
and
we
also
have
a
medalist
for
security
updates,
and
this
is
in
the
same
status.
It
was
last
week
where
there
are
seven
of
them.
Six
of
them
are
solved
in
backdrop.
A
The
last
one
is
one
that
just
needs
a
little
careful
consideration,
because
the
solution
that
went
into
Drupal
7
and
upset
a
lot
of
Kim
trip.
It
broke
a
lot
of
kinship
modules.
Enough
said
a
lot
of
current
site
owners,
and
so
I
wanted
to
see.
If
there
was
a
more
clever
way,
we
could
solve
that
problem,
maybe
less
elegant,
but
something
that
was
less
damaging
would
be
good.
A
Okay,
we're
working
on
a
couple
of
new,
exciting
things
for
Mac
job
most
exciting,
at
least
to
me-
is
getting
our
blocks
and
layout
system,
and
this
is
a
system
that
will
set
us
apart
from
Drupal
7
and
your
blade
it's
something
that
your
plate
really
wanted
to
work
on,
but
they
had
so
much
other
stuff.
They
were
changing
that
they
never
actually
were
able
to
deliver
our
new
blocks
and
layout
system.
A
B
So
I,
finally,
finally,
as
promised
updated
that
issue
issue
86
with
my
status
of
how
things
are
coming
along
right
now,
it's
it's
pretty
minimal
the
functionality
that
I've
got
in
place.
It's
basically
like
basic
crud
operations,
but
I
solved
a
whole
bunch
of
problems
this
week
around
how
to
deal
with
menu
items
versus
layouts
on
those
menu
items
like
what
we're.
B
What
we're
basically
doing
is
porting
panels,
but
panels
obviously
depends
on
both
see
tools
and
page
manager,
and
so
the
approach
that
we're
using
is
is
kind
of
a
combination
of
both
page
manager
and
panels
together
being
merged
together.
So
it
took
me
a
little
while
to
figure
out
how
page
manager
was
going
to
fit
into
this
entire
business.
So
now
in
layout
land,
when
you
create
a
new
layout,
you
get
to
type
in
whatever
path
you
want
and
it
can
be
an
existing
path
or
it
can
be
a
new
path.
B
And
if
it's
an
existing
path
like
node,
/
/
sense,
then
it
identifies
the
contexts
automatically.
For
you
and
says:
oh
I
know
what
node
/
%
is
or
anything
under
node
/
%.
I
know
what
that
is
as
well,
but
if
you
want
to
type
in
something
completely
arbitrary,
like
you
know
my
new
path,
it
will
create
those
new
pads
on
the
fly
too.
B
So
it's
kind
of
like
it's
kind
of
like
a
combination
of
what
panels
ships
without
our
page
manager,
ships
with
out
of
the
box
where
it's
like
these
are
the
predefined
system
pads,
and
these
are
the
ones
that
you
can
create
manually.
Only
the
the
user
interface
and
the
process
for
creating
those
things
is
is
much
more
streamlined,
instead
of
going
through
all
of
like
the
the
seed
tools
wizard.
So
like
four
steps.
Long
before
you
actually
get
to
something
useful,
it
is
a
single
form.
You
fill
out
type
in
the
path
you
want.
B
It
identifies
the
contacts
automatically
and
then
it
plops
you
into
layouts.
Supposedly
we
haven't
gotten
to
the
layout
screen
yet,
but
buttons
making
some
progress.
So
in
that
issue,
issue
86
I
linked
through
my
branch
over
in
my
fork
of
backdrop
in
the
quick
sketch
repository,
and
so
you
can
download
and
try
it
out.
But
it's
really
just
like
it's.
It's
a
whole
big.
B
Like
it
works
it's
safe
stuff
in
the
config
system
and
you
can
clone
things
and
create
new
layouts
and
things
like
that,
but
it
doesn't
actually
really
function
right
now
and
there's
a
whole
bunch
of
code
right
now
that
is
pulled
both
from
panels
and
a
page
manager
that
is
just
kind
of
strewn
about
that
needs
to
be
cleaned
up.
So
it's
coming
along,
but
I
feel
like
pretty
soon
we're
going
to
need
to
probably
connect
with
Bowie
on
I
know.
B
Boy
Owen
is
really
interested
in
this
layout
stuff,
whether
it
happens
in
backdrop
or
Drupal
or
whatever
he
just
wants
to
see.
It
makes
him
forward.
Movement
and
I
want
to
talk
with
him
because,
as
I'm
going
forward,
I
was
trying
to
emulate
what
he
did
in
his
wireframes.
He
has
a
nice
video
demo
of
how
he
imagined
layouts
would
work,
but
as
I'm
implementing
it
I'm
finding
that
I'm,
accidentally
or
unintentionally,
moving
more
and
more
towards
like
the
existing
panels.
B
Ui
and
that's
not
because
yeah
well
I'm,
it's
still
something
fide
down
quite
a
lot,
but
the
concepts
of
panels
just
end
up
sort
of
affecting
the
UI.
So
we
are
ending
up
with
things
in
the
UI
that
are
awfully
similar
to
panels,
because
the
architecture
is
similar
to
panels
and
I'm,
not
sure
that,
like
going
ons
wireframes
took
into
account
all
of
those
things
so
anyway
we're
making
some
progress,
and
if
anybody
wants
to
look
at
it,
it's
an
issue.
86
and
I
would
appreciate
any
help.
So
that's
it
for
me,
tada
great.
A
Some
other
stuff
that
we're
working
on,
we
obviously
have
views
in
core
and
we've
got
a
bunch
of
stuff
that
needs
to
be
converted
and
we
have
cmin
score.
We've
watched
stuff
that
needs
to
be
converted.
We
talked
about
that
a
little
bit
with
all
these.
Your
blade
patches
that
also
includes
cmi
convergence.
Ours
are
obviously
different,
so
they
have
their
own
issues,
but
we
could
use
some
help
on
both
of
those
funny.
A
We're
not
going
to
call
the
WYSIWYG,
because
it's
not
going
to
be
WYSIWYG
is
going
to
be
a
rich
text,
editors
for
colored
or
text
editor,
and
we
need
to
get
one
of
those
in
court.
We
have
some
ideas,
obviously,
based
on
all
the
work
native
interpolates.
We
also
have
some
thoughts
about
how
we
maybe
can
do
things
in
a
way
that
would
be
a
little
less
confusing
to
an
end
user,
and
we
have
some
features.
We
want
to
add
it's
all
still
kind
of
up.
A
In
the
air,
we've
got
a
great
starting
point,
but
we
haven't
determined
our
end
point,
so
we
definitely
want
to
get
that
in
before
the
first
release
and
some
of
this
other
stuff
I
might
be
pushed
back
to
later.
A
dialogue
system
is
going
to
be
super
important
for
views
in
the
rich
text.
Editors.
We
want
to
get
that
in
first
updating
the
administration
theme
is
going
to
be
super
important
for
setting
our
brand
apart
from
Drupal.
A
That's
definitely
something
that
applies
to
eighty
percent
of
websites,
but
we
haven't
figured
out
a
good
plan
to
move
that
forward
and
it's
not
as
much
of
a
priority
as,
for
example,
a
block
to
layout
system.
So
if
we
have
someone
who
was
really
passionate
about
JavaScript
or
drop
down
menus
and
wants
to
work
on
that,
there's
definitely
some
so
place
for
us
there,
but
it's
it's
something
that
will
worry
about
later.
A
There's
also
some
termini
terminology
updates
I
want
to
do
in
terms
of
user
experience
that
have
created
a
meta
issue
for
that
the
lists
kind
of
big
picture
changes
and
where
I
want
to
go
with
that,
it's
totally
open
for
a
feedback.
These
are
all
issues
that
have
been
bike
sheds
on
drupal
org,
fixed
affecting
there's
a
lot
of
opinionated
people
feeling
on
both
sides
of
each
issue,
whether
they
want
them
changed
or
not,
so
I
put
them
all
out
there
just
for
discussion.
A
Obviously
this
thing
aren't
thinks
we're
getting
changed
tomorrow,
but
it
is
something
that
I
think
our
general
user
experience
and
interfaces
in
backdrop.
We're
gonna
need
a
lot
of
help.
User
interfaces
and
Drupal
have
always
needed
a
lot
of
help
and
inserting
talk
about
these
things
now
I
think
will
maybe
hopefully
get
us
to
a
conclusion
before
we
need
to
actually
make
the
changes
which
puffs
Lee
is
right
before
we
ship
but
we'll
see,
and
so
those
issues
are
up
there.
If
you
want
to
review
them.
A
The
big
picture
is
that
we
want
to
make
it
easier
for
people
to
use
back
trip,
but
we
don't
want
to
hurt
people
who
already
know
how
to
use
Drupal,
so
those
two
groups
are
going
to
be
at
at
war
right
like
we
don't
wanna
change
the
name
block,
because
everybody
who
knows
how
to
build
your
bowl
knows
how
to
deal
with
blocks,
but
at
the
same
time
nobody
outside
of
Drupal
knows
what
a
block
is.
So
how
do
we
balance
that,
like?
A
These
are
parallels
to
issues
that
we've
been
working
on
on
Drupal
8,
consolidating
template
files
using
loops
and
places
where
we
should
be
using
loops
cleaning
up
mark
up
changing
variables.
So
we
don't
have
any
objects
in
the
template,
layer
and
just
kind
of
stuff
that
makes
sense
and
I
think
that
there's
not
too
many
of
those
issues
for
backdrop,
because
in
Drupal
8
most
of
the
issues
we
were
working
on,
where
conversions
from
one
sister
to
another,
backed
up.
We
don't
have
those
conversions.
A
We
just
have
the
underlying
architecture
changes
and
then
some
cleanup
in
the
template
file
so
I
think
that's
definitely
something
we
can
get
done
before.
We
ship
I
also
think
don't
think.
There's
too
much
change
involved.
It'll,
be
you
know,
instead
of
using
two
templates
for
search
and
search
results,
search,
results
and
search
results.
You'll
use,
one
I
think
that
that's
not
going
to
be
too
painful
for
contributes
to
make
that
update.
A
So
hopefully
we
can
keep
that
the
facts
on
can
trip
minimal
and
still
improve
the
experience
for
people
working
in
the
theme
system
in
the
future.
So
we
can
start
on
those
now,
there's.
Definitely
a
bunch
of
Drupal
7
cross
sports,
we're
still
working
on
we'll,
probably
merge
the
Drupal
7
stuff.
First,
take
it
take
care
of
those
pull
requests
before
we
merge
the
pull
request
on
beam
system,
but
I
had
a
bunch
of
people
specifically
asking
me
about.
A
A
So
moving
on
big
news
this
week,
the
backdrop
CMS
org
website
is
up.
We
actually
launched
it
last
Friday
a
little
soft
launched
out
telling
anyone
and
because
we
wanted
to
send
an
email
out
to
all
of
our
donors
and
give
them
the
chance
to
opt
out
of
having
their
name
listed
on
our
thank
you
page.
We
know
some
people
donated
money
to
backdrop
and
they
want
to
do
it
kind
of
on
a
personal
level,
and
so
we
wanted
to
make
sure
we
only
list
people
who
wanted
to
be
listed.
A
So
I've
got
a
list
of
people
who
are
going
to
put
on
that
Thank
You
page
tomorrow,
but
I
wanted
to
give
everybody
a
chance
to
kind
of
not
ever
appear
on
that
page
they
didn't
want
to.
So
it
is
that
for
lunch
last
week
we
contact
our
donors
and
really
thank
you
very
much.
We're
launching
the
website.
Can
we
put
your
name
on
it
and
we
had
a
couple.
A
People
say:
oh,
please,
yes
and
a
couple
people
say:
maybe
not
so
we're
gonna
take
their
responses
and
then
post
the
full
list
tomorrow
and
then
right
now.
Our
website
doesn't
really
do
much.
It
just
basically
says
hey
we're
legit
and
here's
our
handbook,
but
we
do
have
new
pages
in
the
works.
We're
obviously
going
to
need
to
have
like
a
modulus
section
at
themes,
section
all
that
kind
of
stuff
in
the
future.
We've
got
plans
for
all
of
those.
A
We
want
to
put
up
a
showcase:
I've
got
a
bunch
of
cool
stuff
in
the
works,
but
since
it
wasn't
done
yet
get
this
initial
launch,
the
website
is
basically
just
like.
This
is
our
own
page,
and
this
is
our
handbook
and
that's
kind
of
it
so
longer
term,
there's
more
stuff
in
the
works,
we're
also
working
on
a
more
responsive
version.
It
is
responsive
now,
it's
just
not
very
usable
when
it's
on
phone,
so
we've
got.
A
B
We
should
also
talk
a
little
bit
about
the
branding
and
styling
on
it
right
now,
yeah
right
now,
it's
darius
Garcia
did
this.
What
the
design
for
us,
which
is
basically
kind
of
a
lack
of
design
actually-
and
we
did
that
intentionally
just
to
make
it
so
that
we
could
launch
the
site
I
mean
we
did
it
in
like
two
weeks
so
so
that
got
us
some
progress
just
to
it,
having
a
website
up
and
then
over
time,
we're
going
to
work
on
developing
a
new
design,
a
new
style
and
I
think
there
is.
B
This
is
cool
with
moving
forward
to
that,
but
we
just
wanted
to
make
it
as
easy
as
possible
for
him
to
give
us
something.
It
looked
good
which
it
does
look
good.
It
just
doesn't
look
like
a
just,
doesn't
have
a
lot
of
branding
to
it
at
this
point,
so
we're
moving
forward
with
like
designing
a
logo
and
working
on
overall
branding,
but
for
now
we
just
wanted
to
get
the
actual
information
up
at
our
primary
website.
A
So
that
is
up,
we
definitely
could
use
some
help
on
the
handbook
pages.
So
if
anyone
wants
to
kind
of
I
know,
Michael
originally
offered
to
kind
of
read
through
our
pages
right
now,
it's
very
developer.
Refocused
I
took
a
couple
of
stops
at
creating
a
couple
of
pages
that
we
need
to
copy
from
tripled
at
work,
but
they're
a
little
light
on
content
in
some
places.
A
All
of
that
stuff,
so
that's
pretty
exciting,
I
think
at
least
it
gets
the
the
instant
need
of.
We
need
a
real
website
out
of
the
way
and
vices
some
time
to
do
some
of
the
other
stuff
that
we
can
work
on
just
good
next
on
our
list
is
the
API
site.
I.
Think
you
set
up,
there's
a
site
there
for
us
to
work
on
already
that.
B
A
That's
fine,
as
long
as
we
can
put
a
Drupal
there,
drupal
7
for
now,
I
think
we
should
turn
that
site
over
to
Luke
who's
volunteered
to
do
some
site
building
for
us
and
we're
gonna
wish
to
set
up
a
call
with
him
and
get
him
going
on
that
we're
going
to
need
a
place
just
to
put
all
of
our
change
requests,
short
term
and
the
longer
term.
We
want
to
make
that
actually
read
our
source
code
and
BB.
B
A
Site
but
I
can
put
a
Drupal
site
up
there
and
turn
that
over
to
Luke,
and
he
can
start
going
to
town
on
giving
us
a
place
to
put
our
poll
requests.
So
that's
probably
the
next
thing
that
we
should
be
working
on.
It's
not
backdrop
itself
and
a
couple
other
things
we
should
be
working
on.
That
are
not
backdrop
itself
are
the
update
server
and
we
need
to
build
one
of
those.
If
anyone
wants
to
work
on
that
a
lot
of
snow
in
a
github
service,
we
need
to
work
on
that
as
well.
A
So,
let's
see
every
Thursday
after
this
meeting,
we
are
gonna
have
a
little
sprint.
We've
also
got
a
couple
of
official
spreads
coming
up
this
summer
and
main
are
going
to
be
doing
a
keynote
at
the
Drupal
corn
camp
in
Iowa
and
backdrop.
Cms
is
going
to
be
sponsoring
this
print
day
at
the
end
of
that
event.
So
that's
a
sprint
for
anything.
Anyone
wants
to
work
on
back.
Jeff
obviously
will
be
there.
We
would
like
you
to
work
on
back
Jeff,
but
if
you
want
to
our
country
Blake,
that's
also
fine.
A
We're
going
to
buy
you
coffee
and
lunch
and
make
sure
everyone
there
gets
the
opportunity
to
do
whatever
work
they
want
to
do
and
we
are
interested
in
sponsoring
other
sprints.
If
anyone
has
an
event
coming
up
and
they
need
sprint,
sponsors
love,
snow,
I
think
we
need
to
spread
a
little
goodwill
around
the
triple
world
as
well
as
the
backdrop
world
as
well
as
you
know
everywhere
else,
and
if
we
can
help
developers
do
what
they
do
best
I
think
that's
going
to
be
good
for
everyone.
So
yeah!
A
A
So
we
have
this
project
management
committee,
which
will
be
responsible
for
issues
that
get
escalated
out
of
the
github
q,
things
that
might
be
becoming
bike
sheds
or
need
discussion
at
a
higher
level
to
get
you
know,
committers
unblocked
and
any
of
those
discussions
that
we
have
won't
want
to
publicly
announce
what
the
resolution
was.
We
might
even
want
to
have
a
public
discussion
about
the
issue
and
so
I
added
a
section
to
this
meeting,
specifically
about
an
essence,
the
PMC's
that
we
can
say
hey.
We
had
this
problem,
we
talked
about
it.
A
We
decided
this
at
least
short
term
and
then
once
we
start
getting
more
pmc
members
and
need
to
have
the
kind
of
discussions
there
should
be
a
place
where
we
can
do
that
every
week.
So,
right
now,
we
have
no
updates.
No
I
didn't
want
to
just
announce
that
that
was
in
here.
So
if
anyone
has
an
issue
they
want
to
weigh
in
on,
they
want
to
talk
to
the
PMC
raised
there.
You
know
point
of
view
stressed
their
case.
We
have
a
place
for
that
communication
to
happen.
A
So
what
you
want
in
the
issue
queue
will
escalate.
As
the
PM
CPMC
we'll
talk
about
it.
There
will
be
a
discussion
either
here
or
an
announcement
here
and
give
other
people
kind
of
a
chance
to
interact
with
the
fantasy,
so
I
think
that's
important
long-term,
just
to
kind
of
keep
our
goals
in
our
goals
publicly
stated
in
our
process
open
for
the
world
to
see,
and
then
yeah
we've
got
other
stuff
going
on.
A
You
well
maybe
not
easier
because
we
tried
to
go
to
the
Sonoma
County
user
group
both
last
week
and
this
week
and
the
PDF
was
canceled
twice
so
we've
been
just
Noah
County
a
bunch
but
didn't
actually
get
stacked
with
the
triple
people.
We're
gonna,
maybe
try
and
reschedule
that
later
we
do
have
a
couple
of
other
meetups
scheduled
clustered
at
home,
where
we
can
do
downloads
of
backdrop
once
we
have
a
product
which
should
be
pretty
fun.
So
that's
all
I
have
for
this
meeting.
I
didn't
know.
A
A
C
B
C
A
C
A
Yeah,
okay,
I
I
still
want
to
go,
and
it's
right
here
in
Berkeley,
there's
no
sense
and
not
going
if
you
guys
are
going
to
be
in
town
I
think
it
would
be
great
to
connect
and
strategize.
Do
you
think
you
want
to
come
to
I
feel
like
on
a
technical
level?
You
might
be
better
for
them
to
talk
to
you
about
what
it's
reported.
Yeah.
B
A
A
A
What
she
was
thinking
about,
Stanford
being
a
week
before,
okay,
so
you're
gonna
be
in
Mexico.
So
we
leave
this
20.
The
23rd
is
a
training
day,
so
we're
going
to
be
leaving
the
23rd.
Maybe
we
can
leave
I
was
planning
on
leaving
in
the
morning,
but
we
could
leave
wait
on
the
twenty-third
and
what
time
are
you
guys
getting
in
town.
C
I
think
we
didn't
I'm
getting
in
a
ten
marks
coming
from
Portland,
so
I
don't
know
what
time
he's
getting
in,
but
we're
also
going
to
be
there
after
the
sprints
in
tahoe.
Don't
start
12
in
quo,
so
there's
two
days
of
kind
of
muffin,
this
they're
on
the
temp
and
a
love
and
lots
of
the
pendulum.
Sorry
29th
and
30th
yeah,
okay,.
A
C
C
B
C
C
Don't
know
they
just
announced
the
dates
for
that,
but
that's
it
series
a
little
more
predictable,
it's
berkeley
in
London
every
year,
so
you
can
plan
on
those,
but
the
only
other
question
I
had
is
with
the
certificate
of
service.
Are
you?
Is
there
an
existing
project
that
has
a
service
that
you
you're
looking
at
as
being
done
well
or
something
you
want
to
emulate?
We.
C
B
Yeah,
the
the
corresponding
website
for
jQuery
is
is
plugins
jquery
calm,
and
these
plugins
that
are
listed
on
this
website
is
fed
from
github
on
any
github
repository.
You
can
edit
settings
and
then
toggle
on
the
settings
saying
this
is
a
jquery
plugin
and
when
you
do
that
this
is
what
happens.
Is
it
gets
listed
on
plugins,
jquery
com,
okay,.
A
C
B
I'm
not
sure
that
we're
sure
yet,
but
I
mean
we
do
have.
We
do
have
the
website
actually
up
and
I.
Think
if
we
can
manage
to
build
the
integration,
maybe
the
fact
that
I
mean
it's
on
the
internet
and
it's
its
production
in
the
value.
That's
when
you
register
a
project
it
should
show
up
somewhere,
but
yeah
I
mean
it's
definitely
pre-release
it
point,
but
I
mean
we
have
to
start
building
it
out
before
we
actually
have
it
finished.
B
B
With
what
we
were
planning
on
doing,
this
is
relevant
to
actually
what
what
we
were
planning
on
doing
was
having
it
so
that,
if
you
toggled
that
option
in
github,
that
just
said
this
is
a
backdrop
module.
Then
that
would
list
it
automatically
on
backdrop,
CMS
torg,
very
similar
to
how
plugins
jQuery
com
works.
No.
B
Right
right,
but
what
about
migrant
of
segments,
the
ones
that
are
automatically
listed
like
just
these,
the
the
the
modules
that
were
pulling
directly
from
github
vs?
These
are
the
ones
that
are
registered
github,
and
on
top
of
that,
if
the
maintainer
has
logged
into
backdrop
CMS
dot
org,
then
they
can
sort
of
put
peripheral
information
around
it.
Creating.
C
C
A
A
B
You
know
that's
interesting,
it
obviously
doesn't
show
Forks,
but
at
the
same
time
it
also
seems
to
limit
it
so
that,
like
any
one
of
these
plugins,
they
claim
a
namespace
already
and
I
think
that
they
claim
they're
namespace.
The
way
they
work
is
I
think
the
banquet
a
JSON
file
in
the
plug-in
repository
that
specifies
what
they
want,
their
short
name
to
be
so
in
jquery
land,
there's
no
logging
into
plugins
jquery
com.
C
So
so
I'm
just
curious
is
the
approach
using
github
as
the
reef.
Oh,
you
have
her
the
host
repository
to
recognize
those
repository.
You
have
the
option
of
differentiation,
train
yeah,
differentiating
yourself
and
Drupal
by
embracing
forking
and
I.
Wasn't
sure
if
you
guys
are
talked
about
that.
If
that
would
please
you
to
backyard
in.
B
Yeah
so
we've
already
thought
of
some
issues
that
are
going
to
cause
us
problems.
So
so,
obviously,
whenever
you
do
any
kind
of
collaboration
on
github
you
for
comprar
ject
and
then
you
submit
pull
requests
and
that's
that's
the
new
patch
workflow,
so
I
mean
there's
already
100
forks
of
backdrop
or
something
like
that,
which
is
great.
So,
yes,
absolutely
like
the
forking
workflow
is
the
way
that
you
submit
submit
back
to
the
original
project,
but
forking
like
in
github
land
Forks
do
weird
things
like.
B
B
B
C
B
What
we
would
do
is
we
would
change
what
the
canonical
like,
let's
say,
on
an
all:
it's
a
flag
module
needed
to
be
forked.
M5
module
was
originally
with
one
person,
but
then
they
abandoned
the
module
in
theory.
What
we
would
do
is
we
would
fork
it
and
then
point
the
canonical
like
what
is
the
flag
project
from
backdrop,
CMS
org
to
the
new
github
repository
so
allow
like
if
something
dies,
then
we'll
pointed
at
a
new
github
repository,
but
the
problem
with
that
is
that
it
doesn't
move
all
of
the
issues.
B
So
if
you
had
an
issue
queue
that
was
on
github
and
you
forked
and
then
put
it
into
a
new
repository,
all
of
the
issues
would
be
lost.
So
when
we
haven't
figured
out
the
solution
to
that,
yet
if
a
project
is
abandoned,
how
do
we
maintain
or
or
or
keep
all
of
the
issues
we
don't
want
to
lose
all
of
them,
so
we've
got
some
working
out
to
do
and
I
think
we'll
need
to
communicate
with
github
around
how
we
could
handle
such
a
situation.
It's.
A
B
C
A
So
I
think
having
like
you
know,
if
you
have
a
major
change
in
maintaining
you're,
probably
also
going
to
be
having
some
major
changes
in
the
way
project
is
maintained,
whether
it's
changes
in
code
or
changes
in
approach
and
some
of
those
old
issues
might
not
applied
a
new
project
anyway.
So
if
we
did
some
kind
of
thing
where
it
was
like,
if
you're
having
problems
with
this
issue,
go
see
this
issue
over
here
or
go
open
and
show
over
here,
I
mean
I,
don't
know
how
painful
we
want
to
make.
B
B
Potentially
that
would
work,
but
you
know
over
time
small
projects
become
large
projects.
So
it's
kind
of
hard
to
know.
You
know
that's
a
sorry.
We're
gonna
have
to
act
as
an
honor.
No,
whatever
whatever
path
is
that
it
is
forever
at
that
path.
I
mean
you
can
always
move
the
repository,
but
you
can't
move
issue
queue
right,
yeah,
so.
B
A
Also
might
be
running
into
a
little
issue
with
the
people
who
claim
the
modules
first
rate.
So
if
you
have
a
new
module
and
you
just
create
one
I
github
and
you
register
with
backdrop
your
friend,
but
if
you
are
trying
to
fork
flag
module
who
owns
flag
module
comes
kind
of
an
issue
too,
because
maybe
the
flag
maintained
errs,
who
are
maintaining
it
on
drupal.org,
also
want
to
maintain
it
and
github.
A
But
there's
somebody
else
who
worked
it
first
and
so,
like
we've
got
to
have
some
kind
of
process
in
place
for
like
just
because
you
created
the
fourth
kind
github.
Does
that
make
you
the
de
facto
maintainer?
So
there
were
people
like
stealing
stuff,
especially
when
you
know,
if
you
have
someone
who's
already
been
working
on,
this
project
is
really
familiar
with.
The
end
is
willing
to
maintain
it
for
backdrop.
We
want
to
make
sure
that
they
have
that
they're
empowered
to
do
that
as
well.
A
So
this
is
another
issue
we
were
thinking
about
like
is
there
a
way
that
we
can?
You
know,
offer
the
project
first
to
the
Drupal
maintainer,
or
do
we
let
them
work
that
out
on
their
own?
What
happens
we
have
people
fighting
over
grab
the
genigans.
That's
probably
a
really
good
position
to
be
a
no
people
are
fighting
over
maintaining
projects.
A
Oh
and
then,
if
there
is
some
kind
of
a
disagreement
where
someone
has
it
and
someone
else
wants
it
like
how
do
we
do
we
have
a
process
for
you
know,
do
we
have
policies
around?
Can
we
remove
something
from
someone
and
give
it
to
someone
else
or
not?
Is
that's
just
something
that's
like
well,
you
know
they
got
there.
First,
that's
how
it
is.
Then.
C
C
A
That
might
create
more
trouble
than
it's
worth
just
from
I
mean
I,
don't
know
we
can't.
We
can
talk
about
it,
but
just
from
the
reaction
from
the
Drupal
community
or
it's
like
we're
using
your
tool
to
distribute
our
thing
long
term
backdrop
Interpol
can
be
very
different
things
right
like
when
it's
true
boolean,
triple
nine
that
are
out
at
the
same
time
is
backdrop.
You
know.
None
of
those
triple
seven
modules
on
drupal.org
are
going
to
be
supported
anymore
and
the
two
projects
going
to
be
so
different.
A
It's
not
going
to
be
worth
distributing
it
in
the
same
place
and
I.
Think
that
that
you
know,
when
you
kind
of
keep
that
that
long-term
approach
in
mind,
it
doesn't
make
any
sense
to
move
it
there,
even
though
short
term
like
everybody,
does
want
to
get
all
their
stuff
from
football
to
org,
because
that's
where
eligible
seven
modules
are
and
that's
what
they
want
to
use
and
right
now,
that's
the
same
mr.
bolt.
That's
it
same
kind
of
thing
is
backdrop,
but
longer
term
I
think
it's
not
going
to
be
the
right.
A
A
B
No
ok!
Well,
let's,
let's
call
it
a
meeting,
then
thanks
everybody
for
joining
and
yeah.
We'll
see
you
guys
next
weekend,
as
usual,
will
be
an
IRC
pound
backdrop
on
freenode
sprinting
sprinting
away.
Today,
Jen's
going
to
be
working
on
cross
and
backports
I'm
going
to
be
working
on
layouts
and
we'll
see
you
guys
online.
These.