►
From YouTube: Backdrop weekly 9/8
Description
Today’s development agenda: http://bit.ly/2cj0QX7
A
Hello,
everybody
welcome
to
the
September
8
meeting
of
backdrops
CMS
we
get
together
every
week
and
talk
about
the
development
tasks
and
the
general
status
of
backdrop
of
the
projects
it's
one
week
from
today
is
the
release
of
1.5,
and
we
are
cramming
as
quickly
as
possible.
They
try
to
get
all
of
these
items
that
we
have
outstanding
wrapped
up,
but
we'll
go
through
everything,
infrastructure,
announcements,
etc,
and
then
we'll
start
talking
about
1.5
release.
A
That's
coming
up
right
around
the
corner,
general
announcements,
Calla
box,
one
point
or
RC
one
has
been
released
as
native
backdrop
supports
using
our
backdrop
container
image
and
darker,
which
is
great.
If
you're
into
that
sort
of
thing.
It
also
could
be
a
really
easy
tool
to
use
if
you're
doing
localhost
development
and
would
like
to
assemble
your
containers
through
the
command
line,
very
cool.
A
You
can
donate
to
back
top
CMS
for
thank
you,
dragon
t-shirts
and
or
hoodie.
You
can
see
find
more
information
about
that
at
backdrop,
CMS
to
org
slash
contributes
if
you
join
the
backdrop
contribute
which
we
would
love
everyone
to
do.
If
you
poured
in
a
module
to
backdrop
or
theme
or
layout
or
have
decided
to
write
one
from
scratch,
we
would
love
to
have
you
in
the
backdrop,
contribute
hub,
and
we
will
be
more
than
happy
to
send
you
a
phpstorm
license.
You
can
use
for
developments.
A
Updates
from
the
project
management
committee,
which
should
do
have
an
update
this
week,
we
took
a
votes
after
the
meeting
last
week,
where
we
discussed
this
wild
plan
to
potentially
put
a
node
reference
and
user
reference
in
1.5
because
or
sorry
into
yeah
into
1.5,
because
those
modules
were
already
done.
But
we
took
a
vote
on
it
and
basically
said
that
it
would
make
more
sense
for
us
to
do
this
right
than
to
do
it
in
a
hurry,
which
I
am
very
happy
to
see
that
that
was
the
outcome.
A
A
Infrastructure
infrastructure
things
around
the
project,
like
our
testing
frameworks
and
github,
and
the
backdrop
website
itself
items
that
we've
got
out
tuning
for
infrastructure.
We've
got
hopes
to
build
up
javascript
and
testing
right
now.
We
only
have
PHP
level
testing,
there's
an
issue
at
2097
for
making
JavaScript
based
testing
a
reality
and
backdrop
right
now.
A
All
the
time
we're
discussing
this
issue
in
concept,
but
not
you
get
encode
at
20
24
as
an
idea
and
an
option
that
would
lower
the
overall
cost
of
ownership
of
websites
so
fitting
nicely
with
our
philosophy
but
yeah
kind
of
a
challenge
from
a
technical
standpoint.
A
Next
item
backdrop:
CMS
on
Pantheon,
/,
brush
/
updates.
I
have
been
checked
on
this
because
I've
been
occupied
with
the
release
coming
up
Jeff.
Is
there
any
news
regarding
drush
and
pimp
yung?
Oh.
A
No
change:
okay,
thanks
Deb,
no
change,
basically
being
that.
There's
an
issue
right
now
that
a
pentium
and
rush
should,
in
theory
all
be
working
together,
but
we
have
some
suggestions
and
things
that
we
could
try
out
on
how
to
actually
get
those
things
working
together
in
theory
that
they
should
be
possible
to
combine.
At
this
point,
there's
also
some
updates.
Their
Pantheon
is
added
the
ability
to
add,
yellow
files
to
the
root
of
your
repository
for
configuring.
A
A
Let's
see
somebody
published
this
one
and
haven't
had
a
chance
to
look
at
it
yet
adding
added
to
the
agenda
that
github
is
improving
collaboration
options
and
they
have
a
blog
post
here,
improving
collaborations
with
forks
that
was
just
published
yesterday.
Was
it
any
of
you
guys
that
are
in
the
meeting
that
out
of
this,
the
agenda
by
chance,
then,
is
read
more
about
it
Jeff
to
hit.
Oh,
of
course,
the.
B
A
Without
a
microphone
uh-uh
anyway,
it
looks
it
looks
pretty
exciting.
There's
they've
added
a
check
box
so
that
it
looks
like
pull.
Requests
can
be
modified
by
other.
Maintain,
errs,
I
think
that
that
is
what
that
means,
which
is
really
exciting.
We
have
a
little
bit
of
an
issue.
That's
right
now.
The
backdrop
CM
esta
org
repository
is
not
is
only
writable
by
a
very
small
number
of
people,
including
Jeff,
myself,
n
doc
wellmont.
A
A
I
think
that
we
bring
this
up
during
the
design
calls
every
week
that
every
other
week
that
we
need
some
design
love
on
the
user
guide
itself,
like
especially
on
the
homepage
landing
for
the
user
guide
kind
of
splitting
that
up
instead
of
having
a
page,
that's
just
like
welcome
to
the
guy
and
then
nothing
but
navigation.
A
But
it's
great
that
that
we
filled
out
a
lot
of
great
content
and
content
is
so
frequently
the
problem
in
our
worlds
that
it's
great
to
have
all
of
that
built
out
and
looking
really
great,
and
now
we
do
the
easy
parts
of
actually
making
it
look
good
forum.
So
we
have
some
ideas
around
adding
forums
to
backdrop,
CMS
org
itself,
I.
A
A
Which
are
issues
18?
In
the
backdrop
CMS
mortgage
cube
and
250
and
I
think
that
one
of
these
is
discussion
and
the
other
one
is
implementation,
like
options
for
doing
implementation
and
the
other
one
just
discussing
where
we
should
host
it
or
what
sort
of
features
we
want
to
have
it
included
in
things
like
that.
A
A
Metric
this
is
a
design
tasker.
Oh
yeah,
cleaning
up
the
interface
for
surgery
of
design
mockups
that
have
been
around,
but
we
haven't
fully
implemented
to
make
them
look
like
mock-ups
this
issue,
95
and
service
provider
listing
follow-ups.
We
have
this
great
service
provider,
listing
that
shows
vendors
and
hosting
providers
that
can
be
used
with
backdrop
or
that
offer
backdrop
services,
and
we
have
some
follow-ups
here
for
adding
additional
segmentation
and
filtering
options
at
issue
195.
A
A
C
A
few
changes
that
happened
like
in
the
last
day
we
had
the
tags
for
the
blog's
being
just
a
single
tag
and
some
people,
because
they
needed
to
put
more
tags.
They
just
put
a
single
phrase
like
separated
by
spaces.
We've
changed
that
Jen
change,
that
to
a
multiple
tag
field
and
then
update
the
CSS
so
that
it
can
work
so
some
people
that
have
dogs
already
might
want
to
update
their
their
tags.
That's
one
and
two
seconds,
I
can't
think
of
any
other.
There
was
an
issue
with
see.
Now
we
have
the
emoji
support.
C
A
Okay,
oh
great,
also
I
call
that
during
the
outreach,
meaning
your
blog
posts,
that's
great,
really
fantastic-
to
have
that
that
person
in
helping
getting
other
people
involved.
I
love
it.
Somebody
asked
a
question
like
I,
don't
know
in
a
file
a
pull
request
and
you're
like
I
know
how
to
do
that
and
then
rope
an
article
and
then
published
it
that
was
fantastic
and
yet
all
through
the
interface
without
doing
a
clone
or
anything
in
so
that's
funny,
because
your
name
is
Chronos
a
column.
Three
close
all
right.
Sorry,
puns,
all
right!
A
A
There's
no
real
major
items
at
this
point,
but
but
we
have
a
team
that,
if
err.number
fixes
in
there,
let's
see
important
bug
fixes
we
have
a
section
here
for
major
bugs
and
backed
up
that
work
on
fixing
the
images
posted
through
ckeditor
and
then
into
blocks
that
had
their
images
being
deleted
by
cron
jobs
during
cleanup.
That
issue
is
now
fine.
We.
Finally,
we
think
under
control,
there's
a
poor
request
that
is
in
the
needs,
review
status
that
solves
this
issue.
By
doing
couple
things,
it's
marks.
A
So
deleting
is
a
risky
operation
where
we
could
inadvertently
start
deleting
content
if
it
moved.
If
blocks
are
moved
in
between
environments.
For
so
for
now,
we've
done
is
we've
made
it
so
images
become
that
are
uploaded
in
this
manner
becomes
self-referencing,
which
means
they
will
never
delete
because
they're
referencing
themselves
anyway.
The
bottom
line
is,
is
that
that
issue
is
pretty
much
wrapped
up.
Its
needs
review
on
the
implementation
there's
tests
already,
but
that
is
that
is
pretty
much
complete
at
this
point,
which
is
fantastic.
A
A
A
later
plan
is
once
we
implement
out
the
full
file
manager,
which
is
issue
1448,
that
we
would
make
it
so
that
all
files
start
becoming
kind
of
the
equivalent
of
self-referencing
that
when
you
upload
a
file,
it
becomes
an
individual
piece
of
content
that
stands
alone
from
the
content
it
is
associated
with.
And
that
means
that
this
is
the
way
we
that
WordPress
works,
that
when
you
upload
a
file
into
a
post.
And
then
if
you
delete
that
post,
the
file
is
still
there.
A
A
Adore
files
are
bound
to
content
they're
attached
to
rather
than
files
being
standalone
pieces
of
content
so
long
term,
we
may
actually
end
up
making
all
files
basically
permanent
by
default,
but
until
we
get
that
file
manager
built
up,
we've
done
it
only
in
this.
What
very
one
specific
place,
which
is
like
you
know,
a
very
common
scenario
that
people
want
to
upload
any
image
into
a
block.
So
that's
the
status
on
that
one
that
will
be
merged
here.
A
Definitely
in
the
next
week
for
the
1.5
release
and
I'll
also
be
in
the
one
point
for
the
last
version:
reform
1.4
that
goes
out
1.5.
That's
the
release.
It's
coming
up.
We
are
excited,
there's
all
kinds
of
things
that
have
been
happening.
Ira
yeah
I
was
saying
that,
after
this
release,
I
think
we
might
need
to
start
having
feature
freezes.
A
Because
everything
everything's
happening
all
at
once
and
that's
great,
that's
that
well
that
we're
going
to
have
1.5
and
it's
going
to
be
a
pretty
awesome
release.
So
let's
talk
about
the
things
that
were
working
on
seven
point:
fifty
Drupal
7
dot,
50
cross
post
their
cross
ports,
I,
don't
know
if
there's
been
much
action
on
this
one.
Yet
we've
got
about
half
of
these
half
of
the
items
that
have
seven
up
50
you
across
ported,
most.
C
A
Most
notable
of
all
of
these,
in
my
opinion,
is
the
adding
support
for
four
character,
utf-8
encoding,
which
makes
it
so
that
we
can
store
emojis
or
fancy
mathematical
symbols
into
the
database
and
that
age
two
is
pretty
much
done.
It's
it's
been
done
for
a
little
while,
but
it's
sitting
there
needs
review.
If
anybody
has
some
time
to
do
additional
testing
or
code
review,
you
can
take
a
look
at
issue
884
and
that's
the
issue
for
adding
essentially
emoji
supports
to
backdrop.
It
works
really
well.
A
In
my
testing
at
least,
we
have
a
built-in
upgrade
path
through
the
UI.
It
does
require
a
change
to
settings
settings
PHP
in
order
to
turn
on
the
functionality
and
then
run
the
updates
through
the
user
interface
and
there's.
Unfortunately,
a
lot
of
technical
reasons
why
that
ended
up
being
the
case,
but
it
does
make
it
so
that
we
have
full
backwards
compatibility.
A
We
don't
actually
need
to
try
to
modify
or
truncate
any
columns
in
order
to
accommodate
this,
but
you
do
need
to
have
a
newer
version
of
my
sequel
in
order
to
support
such
functionality.
So
if
you
have
it
back,
drop
out
of
the
box
will
use
it.
If
you
don't
have
it
back,
drop
out
box
will
not
use
it,
but
you
can
upgrade
to
it
later
if
you
switch
to
a
server
that
supports
it.
So
Mary
needs
reference
modules.
Next
item
on
here,
as
I
yeah,
I
I,
think
I
didn't
skip
this
section.
A
We
took
a
vote
from
the
PMC
on
reference
module
officially
pushed
that
to
1.6,
so
that
will
not
be
happening
for
the
1.5
release,
but
this
is
the
first
meeting
sense.
That
decision
had
been
made,
so
we're
still
going
to
be
doing
some
work
on
it's
in
the
contribute
and
alone
module
right
now,
which
is
where
most
of
the
work
is
happening
so
wanting
to
make
sure
that
1.6
includes
this
critical
functionality
and
sir
collaborating
in
the
contribute
for
the
reference
module,
and
we
won't
miss
this
again.
A
B
Crunch
time,
I
didn't
get
to
do
as
much
as
I
wanted
to
do
last
week,
but
the
big
thing
big
takeaway
from
me
was
talk
or
responding
to
some
of
grams
issues.
Implementing
the
theme
and-
and
it
also
kind
of
echoed
some
of
the
things
that
either
gen
wrote
or
Jen
reminded
me
of
gentlemen's
summer-
comments
on
drupal.org,
I'm
going
to
change
the
header
to
make
the
CSS
less
opinionated.
So
it's
easier
to
read.
B
It
might
not
be
as
cool
looking
but
it'll
be
a
lot
easier
to
work
with
and
I'm,
not
as
making
as
many
assumptions
about
number
of
items
in
the
menu
or
things
like
that.
So
and
then
yeah
I
haven't
haven't
gotten
to
a
lot
of
the
issues
that
needed
more
follow-up,
that
you
posted,
Nate
and
I
will
be
taking
a
look
again
today
and
definitely
be
putting
in
a
lot
of
time.
Switching
and
I'll
take
a
look
at
the
hero
as
well.
A
B
A
Okay,
yeah
some
some
items,
the
I'm
not
sure
if
you,
if
basis
actually
will
need
the
functionality
that
that
has
been
moved
into
court.
You
remember
or
moved
around
in
cory.
You
know
like
we
moved
the
font
detection
thing
and
get
responsive
tabs
into
central
locations.
Now
that
obviously
won't
work
in
1.4
because
they're
not
centralized
in
that
version.
So.
B
A
B
A
A
A
A
Let's
see
yeah
the
other
items
that
are
slated
for
1.5.
It
looks
like
what
1.5
is
actually
going
to
end
up
being
as
it's
going
to
significantly
change
the
out
of
box
experience
so
basis
as
the
new
default
theme,
which
is
really
exciting,
and
then
these
two
items
adding
a
new
home
page
layout,
so
that
we
have
a
new
path.
I
think
it's
at
/
home
instead
of
/.
Note
that
the
standard
profile
will
ship
with
the
layout
configuration
for
the
home
page.
A
It's
surprisingly,
a
lot
more
complicated.
It
might
sound,
especially
because
we
have
hundreds
of
tests
that
all
test
the
existing
home
page
and
when
we
talk
about
the
home
page
for
something
else,
it
started
causing
all
kinds
of
issues.
This
also
has
some
other
interesting
side
effects
like
we
previously
shipped
with
the
front
page
view,
for
example,
and
as
a
side
effect
of
this
existing
sites
that
have
that
view
will
be
unaffected,
but
new
sites
that
are
installed
will
no
longer
come
with
a
front
page
view.
A
They
will
come
with
a
front
page
layout
and
instead
of
the
view
being
a
page,
it
will
come
with
a
block
for
promoted,
and
so
the
view
will
be
called
promoted.
That
includes
all
of
the
promoted
contents
and
it
will
be
displayed
as
a
block
that
is
by
default,
placed
into
the
front
page
layout,
who,
which
actually
I
find
this
to
be
great,
like
we're
going
to
end
up
with
a
bunch
of
pre-configured
things.
The
people
are
like.
Oh,
this
is
a
listing
on
my
homepage
and
they
can
change.
A
How
the
listing
works,
which
is
which
is
fantastic
or
like
I,
want
to
remove
this
listing
from
the
homepage,
put
something
else
there
like.
They
will
start
out
with
something
that
they
can
easily
modify
run
off
the
bat.
That's
looking
really
great
I
think
that
yeah
the
tests
are
all
now
passing,
oh
and
related
to
this.
A
/
node,
essentially,
will
be
deprecated
entirely
for
the
2.0
release.
So
eventually,
when
we
release
2
point
0,
/
node
will
be
a
part
of
history
that
won't
exist
anymore.
For
now,
/
node
is
actually
moving
to
officially
into
a
deprecated
status,
which
is
fantastic
yeah.
There
are
also
a
few
additional
complexities
around
the
RSS
feeds
that
we
also
mean
RSS
feed
to
be
functionally
equivalent
to
what
we
had
previously.
The
RSS
feed
is
also
not
powered
by
views
in
that
same
promoted
view
configuration
as
I
understand
it,
a
new
hero
block.
A
This
is
doesn't
sound,
super
ambitious,
but
actually
it's
been
a
little
bit
tricky
figuring
up
from
an
implementation
standpoint
that
we're
going
to
include
a
new
functionality
right
now.
It's
part
of
layout
module,
I,
believe
for
adding
hero
blocks
and
a
hero
block
basically
is
very
similar
to
a
standard
custom
text
block
that
it
has
a
title
and
a
body
field,
but
also
has
an
image
upload
and
the
image
upload
similar
to
what
we're
doing
for
other
blocks.
A
Inline
styles,
if
you
don't
specify
a
background
image,
because
the
field
is
optional,
then
the
theme
will
provide
its
default
background
image,
which
is
where
the
background
image
that
we
see
in
the
bases
mock-ups
comes
into
play
so
basically
swimming
to
be
updated
and
as
well
bartók,
actually
to
support
this
markup
provided
by
the
homepage
hero.
That
issue
is
issue
1152.
A
It's
in
progress
is
functional
from
like
a
implementation
standpoint,
but
we're
held
up
on
deciding
what
the
default
markup
should
be
and
how
the
CSS
should
affect
it
funny
how
frequently
that
ends
up
being
the
case,
but
it's
looking
really
good.
I
think
that
there
it's
almost
certain
be
that
that
will
be
in
prior
to
1.5
being
pushed
out.
A
A
Turning
on
this
functionality,
we
have
a
checkbox
approach
where
it's
just
like
a
checkbox
board
make
drop
down,
and
then
we
have
this
menu
sales
approach
where
you
get
to
choose
and
configure
the
way
that
the
menu
would
work
on
a
per
block
basis
from
an
implementation
standpoint,
both
of
those
tie-ins
are
pretty
much
I
mean
they
could
be
functional
and
there's
it's
pretty
straightforward,
but
the
way
that
the
admin
menu
actually
integrates
into
the
menu
on
the
front
end
is
where
we
have
no
implementation.
That
is
acceptable
at
all.
A
So
we
have
to
approach
to
back
and
approaches
that
are
both
acceptable,
but
no
front
end
approaches
that
are
working
and
so
yeah
I
think
it's
unlikely
that
that
will
make
it
into
the
next
release,
especially
Wes.
If
you
have
a
limited
amount
of
time,
like
focusing
on
basis,
is
more
important
and
other
front
Enders
I
would
say
the
same
thing
to
them
that
if
it
comes
down
between
bases
and
the
drop-down
menus,
we
need
we
need
to
focus
on
paces,
but
that
doesn't
mean
that
it's
entirely
ruled
out,
but
it
makes
me
really
nervous.
A
A
Next
time,
we've
gotten
here
is
improving
the
rich
text
editor,
which
is
a
meta
issue.
This
was
one
of
the
items
that
I
was
hoping.
We
would
be
able
to
make
some
improvement
serious
improvements
in
in
this
release,
but
there
hasn't
been
a
whole
lot
of
activity
here.
I
think
the
things
that
we
will
do
Gregory
reminded
me
that
we
should
go
through
our
libraries
and
make
sure
they're
all
up
to
date,
and
so
we
updated
jquery
to
the
very
last
they're
very
latest
version.
A
A
Yeah.
One
of
the
items
in
this
meta
is
enabling
spell
check
in
the
rich
text,
editor
I'm,
pretty
sure
that
that's
almost
just
like
a
flag
like
that's,
probably
only
like
a
five
or
ten
line
fix.
If
we
can
figure
out
what
we
can
do
to
actually
disable
seek
editors
disabling
of
the
the
spell
check,
then
that
would
be
nice
one.
A
There's
a
bunch
of
other
items
in
that
meta
for
improving
the
rich
text
editor
at
1087.
A
lot
of
these
things
are
front
ends
and
either
they
work
or
they
don't
I
mean
that's
oversimplifying
things,
but
a
lot
of
them
are
front-end
fixes
that
don't
require
extensive,
integrations
anywhere
else,
and
so
there's
still
a
possibility
that
we
might
knock
one
or
two
of
these
off
if
we
have
a
volunteer
to
actually
work
on
them.
A
Alright,
that
does
it
for
the
1.5
release,
as
mentioned
it
probably
will
pretty
much
be
giving
us
a
big
bang
in
or
out
of
box
experience
between
a
friend
lay
out
the
hero
block
and
are
sorry
the
front
end
theme
the
front
page
layout
and
the
hero
block,
all
of
which
are
pretty
crates
and
I.
Think
that
that
will
really
improve
our
outer
box
experience.
A
We
still
have
time
for
a
couple
of
additional
fixes,
but
they
need
to
be
rolling
pretty
much
immediately.
We
also
updated
the
road
map
for
the
1.6
release,
as
the
reference
module
has
been
officially
pushed
to
1.6.
We
moved
that
into
the
roadmap
for
the
next
release
and
we
also
slated
the
file
management
section
for
the
1.6
release.
Although
I
don't
think
they
spent
a
lot
of
discussion
around
that.
A
Yet
I
think
we
just
wanted
to
make
the
roadmap
actually
look
like
it
had
some
more
things
going
on,
rather
than
just
the
thing
that
didn't
fit
into
this
release.
So
some
more
discussion
about
the
next
release
and
where
focus
should
be
would
be
great
to
start
having.
But
let's
do
that
next
week,
maybe
that
we
capture
that
actually.
A
After
we
get
out
of
the
1.5
release,
we
also
have
continuous
improvements
happening
in
user
experience
and
developer
experience.
These
have
been
going
in
throughout
the
release
and
a
bunch
of
1.4
items
actually
have
some
user
experience,
improvements,
adding
caltex
descriptions,
fixing
javascript
behaviors
those
sorts
of
things.
You
can
find
a
whole
list
of
UX
issues
by
searching
for
the
UX
square
brackets
on
github,
that
does
it
for
the
1.5
release,
I'm,
pretty
sure
we're
going
to
be
slamming
on
that
all
week
and
yeah,
it's
exciting.
C
C
56
total
back
the
backdrop
our
country,
Panthers,
plus
one
since
last
meeting
and
plus
one
pending
applications
bringing
them
to
1526
organization
profiles
supporting
backdrop,
not
change
their
355
total
user
accounts
plus
four.
Since
last
meeting
and
the
new
stat
there
for
the
backdrop
CMS
or
download
counties
6234,
which
is
flatlining
for
since
Leslie.
A
Awesome
yeah,
that's
super
exciting.
Welcome,
alrosa
cough
our
new
contributors.
That
is
fantastic.
Then
thanks
Gregory
for
processing
that
application
yay,
we
love
new,
a
new
contributors,
a
new
one
in
the
pending
queue
to
that
is
fantastic,
as
we've
seen
kind
of
again
and
again
with
people
that
join
the
contribute.
That's
just
a
few
people
can
make
just
a
tremendous
impact
on
our
contributory.
B
A
Official
blog
schedule
is
posted
to
the
backdrop
CMS
or
get
you
a
tissue.
158
I
looked
at
this
earlier
during
the
average
meeting.
It's
a
little
bits.
Actually
this
one
isn't
so
neglected.
We
must
have
two
issues
for
this,
but
we'd
love
to
get
some
more
blog
posts
published
out
to
backdrop.
Cms
torg
I
mentioned
last
meeting
that
criteria
published
a
great
blog
post
on
how
to
contribute
to
backdrop
or
how
to
make
pull
requests.
A
The
newsletter
for
1.4
never
went
out,
and
at
this
boy
yeah,
the
1.5
release
is
coming
out
and
week,
so
yeah
I,
don't
know
about
that.
The
way
very
well
may
be
their
next
newsletter
is
the
1.5
release,
speaking
of
which
I
mentioned
a
lot
during
the
last
meeting.
We
need
marketing
help
because
a
news
that
could
have
gone
out
any
time,
but
we
basically
just
never
got
around
to
it.
It's
even
actually
written
in
everything,
so
so
next
newsletter
will
be
coming
out.
A
A
A
A
It's
a
lot
like
slack,
basically
but
integrated
with
github.
It's
a
fantastic
tool
and
we
are
going
to
be
there
today
and
probably
all
weekends
working
live
with
each
other
to
to
make
the
next
release
a
backdrop.
Amazing.
We
also
use
github
as
a
primary
means
of
official
documentation
and
recording
of
activity.
He
find
that
at
github.com
/
backdrop
upcoming
events,
you
can
get
a
list
of
upcoming
events
that
feature
backdrop
or
which
backdrop
presentations
will
be
given
or
community
members
will
be
present
at
facto
semesta
org
slash
events.
A
There
is
also
an
ical
feed
if
you're
interested
in
getting
a
list
of
all
backed
up
related
activity,
books
that
are
available
for
backdrop,
backdrop
CMS,
so
I'm,
beginning
the
backdrop
CMS.
The
first
comprehensive
guide
to
backdrop
has
been
published
and
is
out
so
you
can
grab
it
from
a
press
or
on
amazon.
I
know
our
copy
is
on
the
mail
there
in
the
mail,
so
I'm
really
excited
to
get
my
hands
on
that.
A
B
A
C
A
C
A
All
of
you
guys
in
the
issue
queue
sends
this
time
next
week.
We'll
probably
have
our
last
minutes
I'm,
not
sure
what
we'll
do
the
meeting
the
day
of
a
release,
but
we'll
find
out
as
a
as
that
date
approaches
some
and
I
can't
respond,
fuzzy
all
right.
Well,
that's
then
assign
for
the
end
of
meaning
all
right.
Thank
you
guys
all
for
for
coming
and
thank
you
for
watching
we'll
catch
you
next
week.
Bye
bye,.