►
From YouTube: Backdrop Weekly - Aug 16th
Description
Today’s development agenda: http://bit.ly/2w0sFee
B
B
Although
we
lost
Jen,
hopefully
she'll
be
back
to
run
things
here
shortly.
Well,
in
the
meantime,
I'll
start
going
through
the
agenda
that
we
have
sorry
we're
starting
a
bit
late.
We
had
a
really
excellent
conversation
about
documenting
some
authorities
and
teams
regarding
different
groups,
and
we
might
recap
that
here
in
a
minute,
but
first
of
all
contribute
to
projects
Hey,
oh
god,
Jen
you're,
back
apparently
there's
no.
Why
fighting
this
thing?
Yeah
go
ahead
and
start
on
contributed
projects
all.
C
Right
so
under
contributed
projects
we
have
two
new
ones
highlight:
Jas,
has
integration
with
our
rich
text
editor
and
GDP,
our
cookies,
which
is
a
module
but
sets
up
here
at
compliance
for
a
year,
keen
desserts,
we
both
been
ported
in
the
last
week.
So
thank
you
to
all
of
our
contributors.
We
made
those
happen
in
addition
to
new
projects.
There
are
a
bunch
of
fantastic
new
ideas
emerging
in
the
contribute
hue,
and
so
I
wanted
to
kind
of
highlight
it
healed.
Those
because
I
think
that
I
know
who's
not
watching
the
contribute.
C
Queue
probably
should
take
a
look
at
these
there
once
that
needed
to
do
some
feedback
on
so
the
first
one
is
about
licensing
policies
that
is
recommending
that
we
follow
board
presses,
can
shrimp
licensing
which
is
GPL
and
GPL
three.
So
there's
an
issue
number
294
in
the
contribu
about
that,
and
also.
C
Recommendation
to
add,
like
licensing
information,
I
think
into
the
readme
files,
so
that
github
would
identify
a
project
as
being
under
a
certain
license
if
you're
looking
for
something,
that's
GPL
licensed
back
drive,
Ana
deaconship
projects
to
would
come
up
with
that
license.
So
that's
just
something
to
think
about.
If
we're
gonna
set
standards
for
our
licensing
licensing,
we
should
probably
also
have
people
document
that
that
is
come
on
I'm,
not
sure
if
you're
still
here
but
I,
think
that
was
your
idea
of
being
that
issue.
Yeah.
D
I
mean
you
don't
have
to
with
the
backdrop
project
itself.
You
don't
have
to
put
the
license
text
in
there.
You
can
define
the
license
through
the
github
UI,
but
yeah
right
now
there
is
no
license
for
it.
So
if
you
search
for
PHP
prod
CMS
projects
that
are
GPL
license,
you
don't
find
github.
You
find
grove
and
october
and
some.
D
B
D
B
B
Backpacking
trip
because
properly
identify
all
of
our
projects
or
should
identify
all
of
our
projects
is
GPL
2,
because
that's
part
of
our
porting
that
you
include
the
license
dot
txt
file
in
all
pretty
much.
It
actually
looks
like
I'm
saying
it's
not
consistent,
but
most
of
them
have
it.
It's
supposed
to
be
a
requirement
of
any
control
that
you
include
the
license
to
a
txt
file
and
it
looks
like
that's,
been
Hazzard
lis
implemented,
although
it
is
their
own
on
most
of
them.
I'm,
seeing
like
9
out
of
10,
probably.
D
Part
of
that
was
the
question
as
to
whether
or
not
GPL
3
is
allowed
for
backdrops
can
trim,
and
so
in
that
issue
you
know,
I
talked
about
that.
The
weird
line
Drupal's
are
always
tried
to
walk
with
that,
having
its
cake
and
eating
it
too,
and
it's
just
unclear
whether
or
not
that's
the
way
backdrop
wants
to
be
structured
with
with
can
trim
the
core
project
or
whether
it's
ok
to
to
follow
WordPress's
example
and
allow
individual
contributors,
and
that
include
apache,
2
or
GPL
3
only
licensed
libraries.
B
B
B
We
haven't
discussed
it
before.
I
know
that
we
we
had
a
long
discussion
over
core
and
the
way
that
we
should
treat
core
4.
Now
we're
basically
saying
you
know
that
the
end
result
of
that
Louis
we're
going
to
leave
it
as
being
GPL
with
the
option
that
you
can
upgrade
to
GPL
3
when
you
distribute
it,
because
that
is
your
right
under
the
GPL
anyway.
B
So
defining
whether
or
not
contributes
can
be
GPL
3.
You
know
officially
just
like
from
the
outset
without
saying
they're
GPL,
because
you
have
to
be
cheap
Hilter
in
order
to
include
an
apache
library
is
useful.
So
let's
yeah
continue
chatting
back
and
forth
on
that
one
I!
Don't
think
that
we
should
use
up
the
meeting
to
discuss
licensing
but
yeah.
Let's,
let's
continue
an
issue.
C
So
other
suggestions
in
the
queue
clerkship
are
changing
our
backdrop,
concurrent
agreement
to
use
a
service,
and
it's
something
that
we
looked
at
back
in
the
beginning.
We
decided
not
to
do
for
a
bunch
of
various
reasons.
It
might
be
good
to
document
those
here
and
see
if
they
all
still
apply.
So
just
there
are
standard
ways
and
github
to
have
people
agree
to
various
licenses.
C
There's
also
a
recommendation
to
add
to
include
a
contributing
the
MD
file
for
every
cancer
project
so
that
we
can
leverage
more
of
github
skills
in
tools
around
managing
contributors.
That
would
might
be
something
that
would
be
really
familiar
to
people
on
github
and
helpful
to
people
who
are
new
to
backdrop.
There's
also
recommendation
to
add,
perhaps
paragraph
of
text
to
every
projects
readme
file
that
mentions
how
security
issues
should
be
reported.
So
if
all
security
issues
need
to
go
to
the
backdrop
security,
cubics
private,
we
should
probably
put
a
link
to
that.
C
In
every
concerned
project
so
that
anyone
who
has
a
pension
project
is
identified,
an
issue
also
has
the
information
about
how
to
report
that
issue
safely
and
then
there's
also
an
issue
here
to
try
and
better
leather
to
get
home
security
scans
by
including
an
adjacent
file
that
references,
a
version
of
a
particular
library
if
they're
going
to
be
bundling
a
library
with
their
module.
That
way.
If
that
library
has
known
security
problem,
the
module
we
get
flag
does
need
an
update.
C
So
I
think
all
these
are
great
ideas.
I
would
love
to
have
feedback
from
other
people
on
which
ones
we
should
move
on
right
away
in
the
points
1934
their
plot
or
discussion,
and
these
are
all
in
the
kinship
queue.
If
you
don't
have
access
to
me,
I
think
everyone
should
have
access
to
comment,
but
if
you
need
additional
access
to
it,
asking
do
you.
D
C
Well
rates,
that
is
the
end
of
updates
for
contributed
projects
this
week,
Wow
does
look
like
there's
a
lot
of
activity
and
again
have
conserve
queue
with
people
who
are
questing.
Some
people
are
working
on
modules
and
people
are
talking
about
modules
and
themes
such
let's
say
a
quick.
Thank
you
to
all
people
who
are
super
involved
in
making
kimchi
cotton
tobacco.
C
C
It's
going
to
redundant
configuration,
reform
and
localized
stuff
like
it's
enough
support,
so
we
should
think
a
lot
and
Robert
for
all
of
their
work
on
getting
new
translations,
so
there
and
the
forum
site
it
looks
like
it
might
be
time
to
assign
official
forum
moderator
so
I'm
here,
timer
interest
and
keeping
an
eye
upon
questions
coming
up
in
the
website.
It
might
be
good
to
have
someone
you
know,
spend
an
hour
a
week
addressing
those
questions
and
making
sure
they
have
answers.
C
That's
kind
of
thing
that
I
find
really
rewarding
to
do
if
you
only
have
half
an
hour
and
you
need
it
something
to
do
while
you're
changing
context,
visiting
the
farm
site
and
seeing
what
people
are
up
to
is
really
interesting,
but
it
is
something
that
I
think
would
be
much
better
for
new
people.
There
was
that
it
may
seem
like
for
moderators.
That
might
also
do
another.
C
In
modern
spin,
so
we
have
a
way
that
anyone
can
apply
the
comment
or
post
as
being
spam,
but
we
don't
have
an
automatic
unpublish
er
yet
so
I
think
that
could
be
something
we
could
automate
pretty
easily
like
if
two
or
three
people
marcus
in
Harmonists
fam
that
automatically
gets
unpublished
or
sending
a
post.
But
it
would
also
be
good
to
have
more
moderators
in
power
to
do
markets
on,
say
all
right,
infrastructure
wise.
I
think
this
is
what
just
talked
about
right
before
the
meeting.
C
So,
let's
see
to
summarize,
we
need
to
document
who
can
do
what
and
in
some
cases
to
find
points
of
contact,
and
this
might
not
be.
People
is
going
to
want
to
talk
so
much
as
locations
where
you
can
find
people
depending
on
what
the
thing
is
that
you're
trying
to
do
so.
A
page
or
series
of
pages
on
dr.
sinister
org
begins
descriptions
of
the
different
cues
issue,
queues
in
particular
in
working
groups
or
teams,
and
what
their
responsibilities
are.
C
Also,
it
would
be
good
to
have
a
list
of
what
servers
and
sites
were
running
and
who
has
responsibility
for
managing
what,
and
so,
if
you
are
interested
in
working
with
someone
and
you
need
access
to
a
sanitized
database,
backup
or
perform.
Who
do
you
ask
for
that?
Who
knows
where
those
are?
You
can
hook
you
up,
so
that
would
be
really
great
too
I,
don't
know
if
we
need
to
have
that
discussion
again,
but
there
is
an
issue
in
the
report.
C
It's
67
for
those
who
weren't
here
or
weren't,
watching
before
we
started
recording
where
we
are
going
to
continue
discussion
about
how
to
make
that
happen.
That's
is
you
know,
therefore,
for
67
in
the
backdrop,
CMS
or
QED,
so
just
trying
to
figure
out
what
are
all
the
things
that
we
don't
have
documented.
How
do
we
document
them
in
a
way
that
makes
sense,
is
transparent
and
is
helpful
to
everybody
who
needs
anything.
B
Okay,
alright,
so
product
updates,
we've
got
a
boatload
of
things,
progress
on
most
fronts
here,
so,
first
of
all,
let's
talk
about
one
but
10.2,
which
is
the
next
bug
fix
release.
We
still
have
that
same
outstanding
issue
around
the
database
credentials.
That's
been
bugging
us
since
1.9
2904.
Still
no
progress
on
that
front
still
has
the
workaround
but
needs
some
flushed
out
implementation.
There
I'm
not
gonna,
recap
that
again
this
meeting
also
kind
of
interesting.
We
are
accumulating
a
lot
of
fixes
in
the
1.10
branch.
B
There's
two
issues
regarding
JavaScript
behaviors
issued
32,
10
and
32
12
that
were
implemented
a
few
weeks
ago
and
got
reviewed
and
I've
merged
them
this
past
week
and
those
fix
this
long-standing
problem
that
users
of
backdrop
had
probably
noticed
that
when
they
upload
a
file,
sometimes
there's
too
progress.
There
are
proper
that
show
up
or
sometimes
multiple
progress
starters.
The
combination
of
either
one
of
those
or
both
of
them
combined
solves
that
problem.
B
So
it's
nice
to
have
that
regular
kind
of
annoyance
assault
and
that
could
actually
cause
larger
problems
on
a
more
complex
backdrop
website.
So
anyway,
that
is
to
say,
we're
accumulating
enough
bugs
in
the
one
but
10
release
that
making
a
a
bug
fix
release
would
probably
be
advisable
at
this
point
like
there's
enough
fixes
in
place.
That's
don't
be
valuable
to
have
those
pushed
out
as
a
release.
B
B
B
Okay,
all
right:
well,
let's
talk
about
1.11,
then
1.11.
It's
coming
right
up
today
is
august
16th
and
the
release
of
1.11
will
be
september
15,
so
we
now
effectively
have
one
month.
It's
actually
30
days
until
the
release
of
1.11.
We
have
a
bunch
of
issues
that
are
in
progress,
though
feature
freeze
will
happen.
B
It's
usually
said
the
first
of
the
month
prior
to
release
we've
mentioned
last
week.
I
think
that
our
tentative
plan
for
feature
freeze
will
actually
be
the
end
of
September
2nd,
which
is
Sunday
night.
Essentially
so
you'll
have
the
weekends
for
all
of
our
volunteers
out
there
the
weekend
to
do
last-minute,
merging
and
feature
review
and
get
in
all
of
the
last-minute
functionality
for
the
1.11
release,
so
feature
freeze
normally
on
the
1st
of
the
month,
because
that
falls
on
a
weekend.
B
B
I
think
the
code
review
that
was
put
in
place
a
couple
weeks
ago
still
has
some
that
had
the
changes
addressed
quite
yet
and
there's
some
other
meta,
Munder
Neath
that
meta
as
well.
Although
those
two
are
the
ones
that
currently
seem
to
be
in
progress,
next
up
is
color
module
improvements
which
there
is
metaphor
at
19:05,
although
that
medic
can
get
a
little
bit
confusing
at
times
we
have
in
the
1.11
release
already
made
it
so
that
the
basis
theme
is
now
colorize
Abul.
B
So
you
can
change
the
appearance
of
basis
from
its
default
blue
to
another
color
scheme.
We
do
still
need
to
make
it
so
that
we
would
like
to
include
default
color
schemes
out
of
the
box
or
basis
that
hasn't
been
completed
yet,
and
a
new
color
UI
that
provides
a
live
preview
is
also
in
progress
and
that
one
is
at
31
86
joseph
has
been
doing
taking
the
lead
on
31
86
for
the
new
color
UI
I
posted
a
code
review
just
day
before
yesterday.
B
That
code,
wise,
it
looks
fantastic,
actually
I,
think
I,
don't
even
think
I
had
any
complaints
about
the
implementation
at
all
so
code,
wise,
it's
good
to
go.
We
also
separated
out
that
question
of
like
what
to
do
with
the
new
external
or
new
color
picker
library
called
spectrum
that
we're
just
punting
on
that,
not
including
spectrum
for
internet
explorer
compatibility
and
making
that
a
sub
issue.
B
If
we
decide
to
add
support
later,
then
we
can
do
that
just
as
ladies
up
item,
but
there
are
a
couple
of
functional
problems
with
that
poll
request
right
now.
The
background
for
some
reason
always
defaults
to
being
black,
which
is
about
what
it
should
default
to
being.
It
should
default
to
being
white
and
the
preview
doesn't
seem
to
work
in
Firefox.
B
Next
up
is
node
preview,
which
is
issue
30
62.
This
issue,
primarily
Bowman,
has
been
taking
the
lead
on
to
make
it
so
that
the
preview
button
comes
back
to
the
node
forum
and
it
makes
it
so
that
you
can
see
a
node
on
the
front
end
of
the
site
with
all
of
the
theming
in
place
during
preview
mode
and
the
holdups
in
that
issue
have
all
all
been
resolved.
B
It
seems
like
now
we're
just
back
to
doing
the
nitty
gritty
of
polishing
thanks
herb,
dual
Gregory
Olaf
and
others
who
have
all
been
doing
a
excellent
amount
of
feedback
there
and
making
it
so
that
there's
been
a
lot
of
feedback
loops
there
happening
with
with
iterations
on
the
implementation,
so
that
one
continues
to
move
in
towards
completion.
It
still
needs
more
review.
Another
code
review
would
be
appreciated
and
then
there's
more
feedback
regarding
the
CSS
and
the
appearance
of
things
that
is
currently
in
progress
right
now.
Thank
you.
B
B
Next
up
is
core
updates
or
automatic
updates,
and
this
is
issue
200,
sorry
2018.
This
is
a
meta
that
just
covers
like
our
overall
goals
for
making
it,
so
the
core
can
be
updated
automatically,
eventually
for
1.10
or
1.11.
We're
not
trying
to
be
so
ambitious
is
to
actually
achieve
automatic
updates
at
this
point,
but
we
are
trying
to
make
it
so
that
core
itself
can
be
updated
via
the
user
interface
and
potentially
put
in
some
groundwork
for
adding
automatic
updates
at
a
point
in
the
future.
B
B
If
anybody
has
any
bright
ideas
on
how
to
add
any
kind
of
automated
testing,
that
would
be
really
helpful,
but
considering
the
complexity
of
core
replacing
itself,
we
don't
have
any
tools
that
are
suitable
for
testing
that
functionality,
which
means
manual
testing
at
this
point,
is
important
to
us,
an
automated
testing.
If
we
can
figure
out
a
way
to
make
that
happen,
that
would
be
a
really
nice
improvement
to
making
sure
that
that
that
functionality
keeps
working
into
the
future.
B
Signing
I
think
we're
still
kind
of
waiting
to
see
the
implementation
on
that,
but
it
does
look
like
what
he's
suggesting
may
end
up
being
I'm,
not
quite
sure
if
it's
actually
more
complex,
but
it's
more
complicated
for
the
implementation
that
we
ourselves
would
have
to
maintain,
and
so
there's
a
good
chance
that
we
will
probably
continue
with
the
sodium
based
signing
implementation,
but
we'll
see
like
if
he
comes
back
with
more
suggestions
on
the
OpenSSL
implementation.
That
is
the
possibility.
Still.
C
B
If
you
have
or
have
not
used
authorized
PHP
or
have
any
experience
using
the
user
interface
updates
within
backdrop
or
Drupal,
please
chime
in
to
issue
3208,
where
we're
discussing
the
removal
of
authorized
dot
PHP
entirely
conceptually
the
way
that
this
would
actually
look,
though,
wouldn't
be
an
outright
removal,
but
probably
deprecation
of
everything
related
to
authorize,
dot,
PHP
and
then
just
removing
our
use
of
authorize,
dot
PHP
from
the
mechanisms
and
backdrop
that
currently
use
it,
which
right
now
includes
the
manual
module,
installer
and
module
updates.
So
we
probably
just
remove
those
small.
B
B
But
this
is
kind
of
the
prerequisite
work
is
adding
it
to
core
itself
and
then
having
a
minor
feature
improvement
just
that
those
tags
are
also
utilized
on
the
modules
page
so
still
need
some
more
work
on
that
particular
one.
There
there's
two
implementations
to
choose
from
the
more
recent
one
that
kind
of
went
a
little
bit
too
far
in
ambition
and
an
older
one
that
was
really
close
to
being
complete,
but
just
didn't
get
polished
up
before
1.9
or
before
one
point
10
was
pushed
out.
B
Let's
see
okay
next
up,
let's
see
one
minor
feature
and
the
grand
scheme
of
things
issue
28
87,
making
it
so
that
images
automatically
rotate
based
on
the
exif
data
when
they're
uploaded.
This
one
is
really
really
close.
It
just
needs
some
really
minor
work
and
test
coverage.
There's
already
similar
tests
in
place
for
resizing
images,
so
I
think
that
we
can
base
our
tests
off
of
that
and
it
will
be
very
similar,
but
once
we
get
test
coverage
out,
if
that
one
is,
should
be
complete
and
issue
31
34.
B
Also
really
two
images
makes
it
so
that
you
can
keep
saying
which
text
file
if
it's
actually
the
image
browser
that
31:34
adds
an
image
browser
to
the
image
dialog
making
it
so
that
you
can
reuse
images
that
have
previously
been
uploaded.
We
had
both
a
code
review
and
a
reroll
this
past
week,
gram
72.
Thank
you
again
for
your
continued
efforts
there.
B
F
We
teamed
up
with
after
Western
Mass
this
past
week
and
we
moved
several
of
the
issues
forward.
So
that's
great
and
some
of
the
team
there's
going
to
continue
to
work
on
some
of
the
issues
they
picked
up.
That's
fantastic
collaboration,
we're
glad
to
move
that
forward
and
looking
forward
to
designs
and
starting
on
that
fact
as
well
and
was
interested
to
check
out
the
issue
queue.
If
you
want
to
I
thought
it
would
put
some
great
backdrop,
developers
and
people.
B
C
Yeah
I
was
just
checking
the
foreign
posts
to
see
what
people
said.
It
looks
like
Tim
out
of
comment.
He
said
last
year
there
was
one
day
of
training
and
what
they've
something
so
that's
the
same
agreement
same
thing
this
year,
so
this
doesn't
be
more
advanced
or
an
opportunity
for
community
members
to
talk
about
participation
and
contribution,
for
maybe
both
I
think
contribution
is
a
good
topic
like
we're.
E
E
C
It
might
be
good
to
try
and
get
a
feel
for
who's.
Gonna
be
there.
Obviously,
Mike,
Nate
and
I
are
local,
so
it's
a
little
easier
for
us
to
get
there
than
some
other
people.
You
might
need
to
travel,
but
we
are
sort
of
balancing
this
like.
What
is
the
point
of
the
backdrop
summit
question
where
it's
like?
Is
this
something
that's
supposed
to
serve
our
community,
or
is
this
something
that's
supposed
to
grow
our
community,
because
if
we
have
a
whole
bunch
of
people
who
are
there
to
figure
out?
C
What
is
backdrop
like
talking
about
like
how
we
make
contributions?
Better,
isn't
gonna
benefit
them.
They
really
need
to
like
show
me
a
showcase
of
something
backed
up
or
tell
me
why
this
is
gonna.
Save
me
money
in
the
long
run
and
that's
sort
of
different
content,
then
the
kinds
of
things
that
our
community
means
and
they
think
one
year
when
we
know
who's
last
year,
you
might
have
been
here
before
we
did
sort
of
both
things
like
the
morning
was
like
a
this
backdrop.
C
C
It
was
much
harder
just
because
it's
like
there
were
people
in
the
room
who
are
like
I,
don't
understand
why
we're
talking
about
this
so
I,
don't
know
like
like
if
we
have
more
people
in
there
in
who
would
benefit
from
that,
it's
going
to
be
better,
but
if
even
one
more
people
it's
hard
to
know
who's
gonna
be
there,
and
especially
even
if
we
get
a
list.
How
do
we
know
it?
Are
you
already
infected
or
not?
We
can
send
out
a
survey.
A
C
I
definitely
think
we
can
do
art
like
mini
presentation
in
the
morning,
regardless
we
probably
should
even
for
people
who
are
the
only
respect
up
just
to
see
like
what's
changed
in
the
last
year,
but
yeah
I
feel
like
one
of
the
things
that
I
thought
went.
The
best
in
the
last
two
years
was
the
showcase
section
and
having
people
who
have
adopted
back
draft
talking
about.
Why
and
how
and
what
it's
doing
for
them.
So
I
wouldn't
want
to
lose
that
entirely.
A
C
A
Don't
think
we
should
be
here
to
save
every
single
time
like
what
is
backdrop
I
mean
if
we
want
to
do
that,
we
can
have
a
session
about
what
is
backdrop
that
might
be
a
more
appropriate
place
to
do
it
yeah,
who
haven't
heard
of
us,
but
if
someone's
gonna
actually
come
to
our
summit
like
they
should
know
what
the
project
is.
Yeah.
C
I'm,
just
not
sure
what
that's
like
actually
who's
gonna,
be
there.
Let's
see
make
that
website
says
you
might
want
to
update
our
thing
if
it's
like,
if
you
don't
I'll
back
up,
is
don't
fountain
like
we
can
kind
of
make
that
more
clear
in
the
description
of
what
it's
you
know
once
you
know
what
it's
gonna
be
about
right,
what
it's
gonna
be
about,
and
that
will
help.
Let's
see.
B
And
that's
that's
what
I
was
just
thinking
like.
We
could
do
I'm,
not
sure
I
can
into
this,
but
basically
kind
of
like
a
conference
within
a
conference.
You
know
that's
not
where
I
used
to
do
yeah
that
we
could
actually
even
like
to
say
you
know
a
if
you
would
like
to
submit
a
session
proposal
and
then
actually
make
a
schedule
yeah
exactly
and
I
yeah.
E
A
Maybe
the
most
important
thing
to
talk
about
is
maybe
upgrading
from
Drupal
7
have
a
session
on
how
to
upgrade
a
site
from
Drupal
7
to
backdrop
and
just
go
over
some,
maybe
a
couple
example
sites
and
what
it
takes
to
do
it
just
because
you
know
we
are
starting
to
talk
about
the
end
of
life
of
Drupal
7
and
that's
supposed
to
be
sort
of
our
big
time
when
people
are
trying
to
figure
out.
What's
do
with
your
site's,
they
come
to.
They
come
to
backdrop
instead.
A
E
C
Year
we
have
proposed
three
sessions
on
backdrop
for
the
normal
bad
camp
session
area.
Nate
and
I
took
part
like
one
an
hour
talk
and
it
split
it
into
two.
So
there's
sort
of
one
hour
about
philosophy
and
one
hour:
that's
a
demo
and
I
think
it
works
better
in
that
format,
I'm
not
sure
both
the
sessions
will
be
accepted
and
then
there's
another
session
that
Nate
recommended
it
was
like
hunting
one.
You
go
the
improvements
and
back
at
CMS,
which
you
would
need
to
write
if
it
works.
C
C
But
what
I
don't
want
to
have
happen
is
have
people
like
show
up
if
you
summit
like
curious
to
do
like
I
really
want
to
dig
in
the
backdrop
and
find
out,
if
it's
for
me
and
then
we'll
be
like
I'm
sorry,
you
need
to
go
to
the
session
and
drive
them
away,
but
I
do
think
that
we
could
do
like
we're.
Gonna
give
this
little
thing
now.
C
We
can
kind
of
set
that
up
a
lot
of
home
that
you
can
avoid
the
discontent
so
I,
don't
know
how
well
we
can
put
that
on
them,
though
right
on
the
homepage
looks
like
this
is
our
actual
schedule,
and
this
is
what
we're
going
to
do
and
then
at
least
there's
no
shock
when
they
get
there.
So
yeah
I
think
I.
C
C
I
think
it
would
be
good
to
get
people
who
made
the
decision
to
use
backdrop
an
upgrade
from
Drupal
7
there
to
talk
about
it.
I
think,
last
year,
year
before
year,
before
we
had
Brian
there
and
he
chose
stuff
different
ripple,
six
I
have
a
couple
of
other
people,
who've
chosen
to
creep
in
Drupal
seven
this
year,
I
can
reach
out
to
them
and
see
if
they
can
speak
to
it
a
little
bit.
Even
though
I've
done
a
lot
of
upgrades,
I
feel
like
it.
C
A
If
we
can't,
if
we
can't
adequately
express
that
why
people
should
upgrade
from
Drupal
7
backdrop
instead
of
Drupal
8,
like
yeah,
we
can
get
some
people
to
say.
Oh
yeah
works
for
my
business
or
something
like
that.
But,
like
you
know,
I
think
that
we
need
also
be
able
to
make
the
argument
ourselves
work.
Yeah.
C
A
A
C
Well,
maybe
I
don't
really
work
on
a
survey
that
we
can
send
to
our
people
ahead
of
time,
and
if
we
get
a
bunch
of
developers,
then
that's
totally
what
we
should
do
and
if
we
get
a
bunch
of
people
that
are
like
I
have
a
website
and
thinking
about
backdrop.
We
can
do
the
same,
but
in
the
last
technical
way.
C
So,
rather
than
having
like
a
live
demo
of
an
update,
we
could
be
like
here's
a
bullet
list
of
things
that
you
should
look
at
to
decide
whether
you're
ready
to
have
great
or
not.
That
might
be
easier
for
non
developers
to
start
but
I
think
like
the
same
content,
it's
like
how
to
update
is
valid,
regardless
of
how
are
we
threatening.
C
Yeah
be
great,
so
I'm
gonna
be
at
the
session
selection
meeting
for
a
bad
camp.
I,
don't
know
whether
I'm
gonna
be
selecting
sessions
or
not,
but
I'm
happy
to
say
like
hey.
If
you
guys
want
to
choose
other
people
to
go
sign
on
backdrop,
we
are
more
than
happy
to
back
out
so
I'll
be
at
least
a
voice,
sick,
letting
them
know
that
when
you
screw
everything
into
it
doesn't
have
to
be
ours.
E
A
C
C
C
C
Out
of
time,
one
thing
I
don't
know:
if
anyone
has
the
agenda
open,
I
tried
to
Ida
Mize
all
of
the
teams
under
the
infrastructure
bullet
list
item,
there's
probably
other
ones
that
I'm
missing
feel
free
to
add
them
in
there
I'm
gonna,
try
and
use.
This
is
my
topic
for
going
these
honestly
website
today,
all
even
unpublished
and
posting
link
and
get
her
so
I
need
some
feedback
on
it
before
it
goes
up.