►
From YouTube: Backdrop CMS weekly meeting 3/12
Description
Backdrop check-in
A
A
We
have
an
agenda
document
that
we
go
through
every
week
to
kind
of
give
us
a
status
update
on
the
overall
project,
as
well
as
all
the
peripherals
around
the
project
itself.
So
we
always
start
off
with
updates
from
the
project
management
committee
which
right
now
that
consists
of
jen
Lampton
and
myself,
just
general
project
wide
issues
or
things
that
have
been
escalated
for
conflict
resolution
and
the
one
we
have
item
way
up
from
last
week
is
that
we
still
have
three
phpstorm
licenses.
A
For
the
backdrop
contribute
so
if
you're
a
member
of
the
backdrop
contribute,
then
you
can
get
access
to
a
free
license
to
phpstorm.
So
if
you've
joined
the
group-
and
you
would
like
a
license,
then
you
can
email
its
info
and
backed
up
CMS
org
and
we
can
give
you
access
to
one
of
those
licenses.
We've
also.
B
A
Making
some
progress
around
the
backdrop
CMS
trademark,
we
put
in
an
application
like
six
months
ago
to
register
backdrop
CMS
as
a
trademark
and
we've
just
now
gotten
to
an
actual
human
who
is
helping
us
go
to
the
process
of
finalizing
that
trademark.
So
that's
actually
going
really
pretty
well.
We've
got
a
phone
call
with
the
reviewer
right
after
this.
Actually
so
we'll.
Let
you
guys
know
how
that
is
progressing
just
to
establish
backdrop.
A
Cms
has
its
own
brand
community
growth,
we've
had
a
couple
of
new
contributors
and
an
additional
seven
new
backdrop
contributes,
which
is
spent
to
see
that
continuing
to
grow
and
in
the
news
lola
bot
wrote
up
its
first
article
on
backdrop,
CMS,
which
was
fantastic
one
oliveira
r,
that's
not
correct!
Well,
one
who
wrote
up
this
amazing
article
on
Lola
become
just
a
first
impression
of
porting
modules
to
backdrop
CMS,
which
was
a
really
great
instruction.
A
C
I
had
to
change
to
a
different
google
account.
Unfortunately,
I've
got
plenty
of
those,
so
everything's,
fine,
google+
yeah,
so
things
are
working
on
the
aren't
backed
up
itself.
The
top
of
the
list
here
is
Josh.
We
have
not
really
made
any
progress
since
last
week
on
Josh.
Does
everyone
seem
to
be
pretty
busy,
but
I
think
it's
really
really
close
to
having
a
working
version,
and
not
only
is
it
close
to
having
a
working
version.
C
There's
some
instructions
on
how
you
can
hack
it
together
to
make
it
work,
and
we
also
have
a
course
of
action
for
how
we're
going
to
make
it
work
without
having
Hackett
in
the
future,
which
I
think
all
sounds
really
good.
We've
gotten
a
bunch
of
great
work
from
people
who
are
using
it
on
their
own
products,
and
we
also
have
support
from
one
of
the
current
maintainer,
so
I
think
Josh
progress
is
coming
along
well,
which
is
good.
C
We
should
be
able
to
start
using
it
pretty
soon,
so
I'll
try
and
give
that
another
poke
this
week
and
see
if
we
can
get
it
closer
to
reality,
but
I'm
really
excited
about
having
Josh
Trebek
job,
we're
also
working
on
having
the
update
status,
module
work
for
backup
CMS.
It
currently
is
enabled
in
all
core
versions,
but
we
need
to
have
a
server
app
that
will
check
the
core
version
and
any
contribs.
C
C
So
now,
if
you
are
able
to
download
a
package
version
of
a
contribute
in
it,
which
we
think
in
report
back
to
back,
drive
CM,
esta
or
check
the
version
and
tell
you
whether
you're
up
to
date
or
not-
which
I
think
is
is
super
handy
next
step
in
that
process-
is
to
create
kind
of
a
project
database
on
backrub
CMS
network.
So
we
can
track
what
the
current
version
of
each
project
should
be
and
I
know
you've
been
doing
a
ton
of
work
on
that
lately.
Do
you
want
to
give
us
an
update.
A
A
A
A
Will
the
packaging
script
will
add
the
version
information
into
a
package
and
then
upload
that
package
back
to
github
so
that
your
version
information
will
be
contained
within
it
and
that
version
information
then,
is
already
actually
being
sent
to
backdrop
CMS
Borg
on
cron
jobs
and
every
time
update
status
runs
so
back
to
fcms.
Doesn't
work
isn't
currently
capable
telling
you
whether
or
not
updates
are
available
yet
or
not
so
we're
making
progress
once
we
fix
the
packager?
That
means
that
sites.
B
A
Actually
be
able
to
tell
backdrop
CMS
out
or
what
versions
of
modules
are
actually
running,
which
is
step
one
and
then
step
two.
We
need
to
work
on
back
joke
CMS,
org,
actually
taking
those
versions
and
telling
sites
whether
or
not
they're
updates
available
so
to
further
that,
along
which
started
a
port
of
project
module
for
backdrop,
which
is
basically
like
project
module
for
Drupal
itself,
pred
for
kind
of
runs
most
of
the
infrastructure
of
drupal
org,
but
for
what
we
need
on
backdrop
CMS
or
gets
a
lot
narrower
in
scope.
A
We
don't
need
an
issue
tracker.
We
don't
need
integration
with
a
version
control
system,
but
instead
we
need
integration
with
remotely
hosted
repositories.
So
that
means
integrating
would
get
up
to
respond
to
these
web
hooks.
When
a
new
repository
is
made,
we
will
create
a
new
release
note
on
back
top
CMS
org.
So
it's
very
similar
to
to
the
way
things
work
on
drupal.org.
Only
it's
going
to
be
reversed.
Instead
of
creating
a
tag
and
then
requiring
an
ode
to
be
made
for
release
to
exist
on
backdrop,
CMS
or
get
will
be
flipped
around.
A
Then,
when
you
create
a
new
release
on
github,
the
release
notes
are
on
github
and
the
creation
of
those
release,
notes
and
the
official
release
will
in
turn,
automatically
create
a
release.
Note
on
backdrop,
CMS
org,
and
then
that
will
be
used
for
all
update
status.
Notifications
in
the
future,
so
it'll
be
pretty
similar
to
drupal.org.
Only
they'll
be
less
than
most
manual
interaction
because
most
of
the
developer
action
happens
on
github
and
then
things
will
automatically
respond
on
backed
up
CMS
dot
org,
so
we're
making
a
lot
of
progress
on
that
front.
A
C
All
right
so
a
much
lower
priority
item,
but
also
related
to
that.
Our
packaging
script
will
handle
what
happens
if
anyone
creates
a
project
in
the
contribute,
and
if
one
of
the
bonuses
of
being
part
of
Contreras
you
get
your
project
package.
Do
you
get
security
review?
We
get
a
bunch
other
good
stuff,
but
we
do
have
use
cases
where
people
will
not
be
able
to
put
their
coat
or
not
want
to
put
their
code
into
that
group
and
for
those
people
don't
need
to
manage
their
own
version
strings.
So
you
can
either.
C
You
know,
get
a
copy
of
the
packaging
script
image
that
yourself
or
just
manually
code
in
your
verging
strings
and
hope
that
you
remember
to
have
taken
when
you
create
new
releases
of
your
models.
But
there
are
people
who
may
want
to
create
the
equivalent
of
sandbox
projects,
which
is
what
we
have
on
drupal.org,
where
you
can
kind
of
put
your
code
up
somewhere,
but
in
a
kind
of
alpha
state
where
you're
like
I'm,
not
sure.
If
this
is
ever
going
to
go
anywhere,
you
don't
want
to
make
an
official
project.
B
C
Meet
that
use
case
we're
hoping
to
implement
a
github
service
so
that
you
can
create
a
project
on
github
check
a
box
and
say
this
is
a
backdrop.
Project
and
backdrop
will
be
notified
of
the
fact
that
that
project
exists
and
will
allow
people
to
find
it
if
you
have
searched
or
other
means,
but
it
won't
be
an
official
project
in
the
same
sense
as
a
sandbox
budget
country.
C
Will
that
work
isn't
an
official
project,
but
since
we
don't
have
a
lot
of
people
who
are
scratching
for
that
right
now,
that's
a
lower
priority
item
and
it
requires
more
complicated
integration
with
github
in
languages
we're
not
particularly
familiar
with.
So
it's
been
kind
of
de-escalated
in
priority.
C
Now
that
we
have
this
contribute
and
Olivia
all
the
functionality
and
we'd
like
to
deliver
to
people
in
the
country
group
will
deal
with
that
first
and
then
we'll
probably
also
start
worrying
about
people
who
have
big
contributed
projects
that
they
don't
want
in
that
group
that
they
do
want
official
releases
for
that's
also
a
higher
priority
than
the
sandbox
projects.
But
we
do
have
a
point
for
sandbox.
C
C
Now
we
don't
want
to
impact
the
usability
at
all
just
by
changing
the
theme,
so
we're
going
to
kind
of
throw
that
up
for
a
design
review
and
see
at
what
it's
like
in
the
new
theme,
and
we
may
need
to
do
a
little
redesigning
based
on
the
idea
that
the
that
the
the
site
has
a
different
purpose
and
we
want
to
make
sure
that
we're
still
able
to
serve
that
purpose.
So
Nate
was
asking
if
I
sound
like
a
robot
to
anyone
else.
C
I
have
a
okay
I
have
a
different
microphone
I
can
switch
to
if
it
sounds
too.
Funnily.
Okay,
so
maybe
it's
just
me
that
makes
me
sound
like
a
robot.
Okay,
sorry
guys,
sorry
Nate,
everyone
else
is
invited,
okay,
so
that's
the
API
site.
All
it
really
needs
is
a
new
theme
and
we
will
get
to
that
soonish
and
then
our
primary
website
backdrop
CMS
org,
obviously
I
guess
we
did
it
last
week,
but
after
the
meeting
last
week
anyway,
it's
on
bactrim
CMS,
which
is
really
exciting.
Woohoo.
C
Sorry
I
didn't
make
more
fanfare
about
earlier,
but
obviously
next
steps
are
in
designing
and
building
the
module
theme
layout
system
over
there.
So
obviously
we've
got
this
integration
with
github
going
on,
which
I
think
is
super
important,
but
we
also
need
to
build
kind
of
the
front.
End
user
facing
side
of
it.
I
want
to
go
to
backyard,
CMS,
I
work
and
search
for
a
particular
module
or
look
at
available
themes
and
drupal.org
doesn't
do
a
particularly
good
job
of
solving
those
problems.
C
So
we're
also
looking
to
other
sources
of
inspiration
like
how
WordPress
solves
this
problem
and
trying
to
figure
out
the
best
way
to
represent
these
things,
to
our
users
and
and
so
we're
going
to
kind
of
a
whole
second
round
of
design
process
for
the
specific
ends
and
needs,
and
then
we're
going
to
try
and
build
those
out
as
well.
So
while
we're
building
the
technical
stuff
on
the
backend,
we're
also
trying
to
redesign
and
think
about
the
problem
space
from
the
front
end
as
well.
C
So
that's
what's
on
our
plate
currently
for
the
new
backdrop,
CMS
org
site.
In
addition
to
rethinking
how
mobile
navigation
works,
we
have
some
designs
on
doing
mobile
navigation
for
that
site.
We
just
haven't
implemented
it
yet
and
I
used
to
say
the
excuse
was
that
we
didn't
want
to
do
it
twice,
because
we
only
want
to
it
on
backdrop,
but
now
the
sights
on
managing.
So
we
can
implement
that
whenever
we
want-
and
that
might
be
a
nice
task,
that
we
could
kind
of
dealt
dole
out
to
anyone.
B
C
B
C
Okay,
so
yeah,
it
would
be
good
to
get
that
going
to
and
then
long
term.
We
have
other
plans
for
the
flagship
site
to
they're,
not
such
high
priority.
We
want
people
who
are
building
sites
on
backdrop
now
that
we
have
sites
on
backdrop
to
be
able
to
post
them
in
kind
of
a
showcase,
just
like
the
I
Drupal
as
a
showcase
I
think
that
would
be
super
handy
and
then
we
also
want
to
be
able
to
post
things
like
service
providers.
C
We
have
a
lot
of
people
who
have
uploaded
their
logos
as
supporters
of
backdrop.
We
might
want
to
be
able
to
allow
them
to
categorize
themselves
and
advertise
their
services
as
development
companies,
your
hosting
companies
or
any
of
that
stuff.
So
people
can
find
providers
for
things
they
need
and
longer
term.
Once
we
have
people
providing
services,
those
people
are
going
to
be
needing
to
hire
people
so
we'll
put
up
a
job
section,
based,
of
course,
on
the
wonderful
drug.
Drupal
has
done
on
their
job
section
2.
C
So
we
will
eventually
get
all
these
things
short
term.
Our
priority
is
obviously
on
allowing
people
to
get
modules,
themes
and
lay
from
our
site,
but
we
do
have
plans
to
integrate
everything
else.
We
will
do
it
as
time
allows
alright.
So
back
to
back
drop
itself,
we
have
a
patch
release
coming.
Did
we
do
one
last
week
me
so.
C
We
made
the
schedule
based
on
the
calendar
and
then
we
realized
will
be
there,
but
what
we
thought
might
be
kind
of
fun
is
if
we
did
a
like
celebratory
dinner
that
night,
some
people
have
been
talking
about
doing
and
get
together,
drupalcon
alley
for
backdrop
anyway,
but
we
didn't
want
to
do
it
at
drupalcon.
So
we
thought-
let's
just
you
know,
take
everyone
to
dinner
some
night
and
buy
drinks.
C
Doug
fan
generously
offered
to
help
sponsor
that
event,
so
probably
be
a
beer
on
Doug
on
a
smaller
event
to
start
off,
which
is
great
and
I.
Think
if
we
did
that
the
night
of
releasing
1.1,
we
could
have
like
a
little
celebration
like
yeah.
Well,
no
one's
out,
everyone
be
really
excited,
so
nate
and
I'll
probably
be
holed
up
in
some
sprint
more
room
somewhere,
or
maybe
the
hotel
room
trying
to
get
one
dot
one
out.
C
But
then,
after
that,
we'll
all
go
out
and
have
drinks
and
celebrate
cuz,
we'll
be
surrounded
by
other
friendly
cool.
So
I
think
that'll
be
really
fun
so
for
one
dot
one.
We
have
four
things
on
the
agenda.
The
built-in
rich
text
editor
is
high
on
the
list
and
also
high
on
the
likelihood
of
not
being
done
in
time.
It's
obviously
a
very
important
feature,
but
we've
got
people
who
are
reporting
other
wysiwyg
modules.
C
If
there's
also
kind
of
a
lot
of
hand
waving
as
to
how
it
should
work-
and
we
need
someone
to
kind
of
architect
very
specifically-
which
pieces
go
where
and
that
I
think
it
takes
a
much
longer
amount
of
time
and
more
focused,
try
and
figure
out
like
how
it
should
work
and
I
kind
of
re-engineer
thinks
it's
like
a
wonder
for
which
is
hard
to
get
people
to
do
their
spare
time.
It's
just
there's
not
that
much
focus
available.
So
I
think
you
know.
C
Pecado
is
going
to
be
a
little
bit
more
complicated
because
we
have
to
rethink
where
these
are.
Interfaces
for
stuff
goes
where,
as
the
token,
the
only
real
interface
just
attached
anywhere
it
didn't
have
a
you
know,
looking
to
admin
page
that
needed
to
be
moved
someplace
different.
So
I
think
I
think
that
token
part
was
going
pretty
well.
Pasado
should
follow
all
I
think,
there's
there's
an
issue
open
for
each
of
them
token
is
480
and
path.
C
Auto
is
87,
and
if
anyone
wants
to
to
follow
those
there's
going
to
be
a
lot
of
posted
stuff,
like
I,
think
we're
going
to
put
it
here.
What
do
you
think
and
more
grenades
and
feedback
on
that?
So
those
issues
like
a
technique
needs
feedback.
So
we
want
to
watch
that
key.
That
would
be
really
helpful
and
then
the
other
thing
that
working
on
that
I
am
super
excited
about,
and
it
is
proceeding
at
rapid
pace-
is
getting
our
new
branded.
C
A
admin
look
and
feel
in
so
some
of
the
feedback
we've
been
getting
for
people
who
tried
backdrop
so
far,
they're,
like
wow.
It
looks
exactly
like
drupal
now
kind
of
like
to
change
that
first
impression
some
people
install
and
be
like.
Oh
it
looks
a
little
different,
you
know
doesn't
have
to
be
super
different
and
we
have
all
these
great
designs
from
Darius
with
different
ideas
on
how
we
can
make
a
big
impact
by
changing
a
little
here
and
a
little
there
in
we
have
all
that.
C
West
has
divided
up
to
a
whole
bunch
of
sub
task,
which
is
really
great.
We're
trying
to
get
all
the
design
finalized
while
cranking
out
like
things
that
are
finalized.
We've
got
pull
requests
against
a
backdrop.
They
include
these
changes
and
I.
Think
it's
going
really
well,
so
I'm
really
excited
to
see
those
changes
make
their
way
in
decor.
C
C
A
Yeah
I
think
some
of
them
they
they
end
up
with
a
weird
visual
disconnect
between,
like
the
tables
in
the
pager
I'm
not
done
at
the
same
time,
although
it
is
greater
their
separate
issues,
but
I,
don't
really
have
a
particular
reason
for
having
queued
them
up.
I
think
it's
just
if
they've
been
they
all
came
in
it
wants
to
mention,
had
a
chance
to
look
at
all
of
them,
so
I
think
that
will
get
them
merged
in
as
soon
as
possible.
C
A
A
Yeah,
that
was
it
now
that
you
in
it,
because
it
initially
we
had
things
like
the
patriot
was
done
and
the
tabs
are
done
before
the
font
was,
and
then
you
can't
actually
tell
what
the
final
looks
is
going
to
be
because
the
pots
different
I
didn't
have
that
one
came
through
I'll.
Take
a
look
at
today:
okay,.
C
I'm
not
sure,
there's
actually
pull
requests
for
it
yet,
but
I
know
that
Roni
is
working
on
it,
so
hopefully
there
will
be
one
soon
if
there's
not
already
all
right
so
other
things
we're
working
on.
We've
got
a
whole
bunch
of
issues
that
are
tagged
with
1.1.
If
you
want
to
take
a
look
at
those
and
they
get
help
cute
with
our
milestone
and
then
we
also
have
images
other
stuff,
we're
always
working
on
backdrop.
Is
improving
user
experience?
C
If
you
find
anything,
that's
a
funny
user
experience,
you
can
create
an
issue
and
tag
it
with
you
x,
+
square
brackets
in
the
title
same
thing,
with
developer
experience,
if
you're
using
it,
you
find
something
that
feels
kind
of
funny
from
a
developer
perspective,
put
that
squared
DX
in
the
brackets
and
we
can
review
those
issues
kind
of
on
a
whole.
Those
two
things
that
are
super
important
to
us
and
drupal
has
not
done
a
great
job
at
solving
those
issues
in
the
past.
C
So
if
you
won't,
if
you
want
to
create
issues-
and
let
us
know
if
you
find
stuff
like
that-
that's
good,
if
you
also
really
care
about
user
experience
or
developer
a
chance,
you
can
search
the
queue
for
those
tags
and
try
and
find
those
issues
and
work
on
those.
That's
really
good
and
anytime.
Those
get
in
we'll
look
at
what
the
issue
is
and
try
and
figure
out
how
soon
we
can
get
it
in.
C
B
C
Okay,
so
after
this
one
called
it
to
today,
Nate
and
I
have
another
call
with
our
trademark
advisor,
which
is
going
to
be
great
and
then,
after
that,
we're
going
to
be
an
IRC
sprinting
on
backdrop.
So
if
you
have
some
time
today,
you
want
to
contribute
an
hour
to
you
can
meet
us
in
IRC.
Everyone
is
in
there
talking
about
different
stuff
they're
working
on.
If
you
have
any
questions,
there's
usually
people
in
there
to
answer
which
is
really
good,
but
we
don't
have
any
other
in
person
Sprint's
scheduled
until
mid
camp.
C
Oh
wait!
That's
next
weekend
right,
yeah,
so
mid
camp
in
Chicago,
Lee
and
I
thought
it
was
like
a
month
away
still
so
is
next
weekend
and
we
have
sponsored
the
sprint
room
at
the
camp.
So
during
the
camp,
which
I
think
is
friday
and
saturday,
they've
set
up
beside
a
sprint
/
bathroom,
which
backdrop
was
able
to
give
them
some
money
for
which
makes
us
feel
warm
and
fuzzy
and
we'll
be
in
there
probably
all
weekend.
I,
don't
think
Nia
are
giving
a
talk
on
backdraft,
but
I'm
doing
a
unrelated
to
talk
on
PHP.
C
So
for
the
rest
of
the
time
will
be
available
to
hang
out
in
that
room
and
actually
work
on
factor.
So
if
anyone
is
in
the
Chicago
area
and
they're
curious
about
backdrop
for
in
Indies
case
know
a
lot
about
back
trip
already
wanna
come
chat
with
us,
that's
definitely
a
good
place
to
come
meet
and
where
we're
looking
forward
to
being
there
sunday
after
the
camp,
there
will
be
a
sprint
and
we
will
be
at
the
sprint
sprinting
arm
back
trip
as
well.
C
C
C
It's
in
a
beautiful
part
of
the
world
and
a
Happy
Camp
beautiful
time
here
so
I
definitely
recommend
Twin
Cities
triple
camp
and
if
anyone
else
has
any
other
camps
or
conferences
where
they
either
want
to
know
about
backdrop
or
want
backdrop,
people
to
attend
specifically,
let's
no
one
will
throw
that
on
to
the
backdrop
town
for
two.
So,
oh,
that's
what
that
upcoming
and
then
related
to
publicity.
C
We
also
have
the
triple
watchdog
article
coming
out
in
May
right
around
the
time
of
Triple
Crown
as
well,
so
keep
an
eye
out
for
that
all
right.
I
know
this
meeting
is
running
long
just
because
we
had
such
trouble
with
Google+
getting
it
started
today.
But
if
anyone
has
any
questions
or
anything
that
we
should
talk
about
this
week,
we'll
go
ahead
and
open
that
up
for
a
little
while.
B
C
So
if
you
just
want
to
take
a
stab
at
like
how
would
I
put
this
in
core,
you
know
go
ahead
and
start
working
on
it
if
you
want
to,
and
if
you
run
into
an
issue
you're
like
I,
don't
know
how
to
solve
this
problem
or
I
want
advice.
You
know,
throw
up
an
issue
or
ping
someone
in
IRC
and
we
can
talk
about
it,
but
yeah.
We
would
love
you
to
feel
empowered
to
do
whatever
you
want
and
you
would
probably
have
at
least
as
good
ideas
as
we
would.
So.
C
A
For
the
most
part,
it
really
is
going
to
be
renaming
things
just
to
put
it
within
the
path
module
name
space,
because
it's
not
going
to
be
a
separate
module.
It'll
just
be
part
of
past
module
so
everywhere,
where
we
currently
have
pop-out,
it
will
probably
just
become
past,
like
a
and,
if
there's
like
hooks
for
like
hooks
path,
auto
update
or
something
like
that,
you
probably
should
just
be
like
I'm,
not
really
sure
what
the
name
says
should
be,
but
maybe
it
would
be
past
underscore
auto-update.