►
From YouTube: Backdrop Weekly Dev - 2021/10/21
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
it's
october
21st
2021,
and
this
is
the
backdrop
weekly
development
call.
We
get
together
every
week
to
talk
about
priorities
for
backdrop,
core
development,
we'll
start
with
some
introductions.
My
name
is
nate
lampton,
I'm
quick
sketch
on
the
internet,
calling
in
from
oakland
california.
C
I'm
luke
mccormick,
I'm
actually
now
a
technical
account
manager
from
san
ramon.
California
going
to
be
doing
a
lot
more
programming
with
my
my
new
gig,
so
I
I
may
show
up
more.
Although
timing
gets
me
tricky,
let
me
go
over.
Tim
looks
busy,
so
let's
say
panda.
D
Maybe
not
maybe
tim
sure,
peter
if
you're
available
later.
Let
us
know
this
is
tim.
I'm
st
paul
tiem,
I'm
in
deerwood,
minnesota
and
yeah
very
focused
on
backdrop,
live
right
now
joseph
already
went.
Didn't
you
yeah,
it's
just
ten.
Just
gentlemen.
E
Hi
I'm
jen
lambton
and
I'm
joining
from
oakland
california.
I
can
do
the
community
update
section.
If
you
can
give
me
a
link
to
the
agenda.
A
A
All
right,
great,
well
welcome
everyone,
so
this
week
we're
going
to
be
continuing,
doing
kind
of
like
a
priority
planning
for
the
next
release
of
backdrop
back
to
1.21.
A
We
started
this
kind
of
planning
session
two
weeks
ago,
taking
the
results
of
a
survey
that
was
done
a
couple
like
18
months
ago.
A
I
think,
and
going
through
that
list
of
survey
results
and
sizing
them
talking
about
the
status
and
where
they
currently
are,
and
then
today,
we're
probably
going
to
go
through
that
same
list
a
second
time
and
start
sizing
them
for
impact,
so
kind
of
impact
in
a
way
kind
of
equates
to
priority
like
how
how
big
of
a
a
splash
it
would
make,
but
not
necessarily,
you
know,
because
a
lot
of
times
we'll
choose
things
that
are
easy
or
fit
people's
needs.
You
know
over
the
the
impact
that
it
has
on
the
entire
project.
A
Okay,
okay!
Well,
let's
get,
let's
maybe
maybe
skip
over-
that
we
can
just
dive
right
into
the
road
mapping.
I'm
gonna
share
my
screen.
A
Okay,
so
here's
the
list
of
of
features
these
again
are
pulled
from
survey.backdropcms.org.
A
A
Moving
the
title
display
settings
form
advanced
caching,
removing
the
tabs
from
the
login
register
and
password
reset
pages.
Better.
Google
page
speed
out
of
the
box,
save
draft
module
core,
add
a
site
architecture
report
and
accordion
blocks
yeah.
I'm
sorry.
A
I
said
that
we're
going
to
start
sizing
this,
but
I
forgot
to
mention
something
else
and
that's
before
we
get
into
that
we'd
like
to
also
kind
of
amend
this
list
with
just
items
that
have
momentum
right
now,
because
those
are
things
that
are
likely
to
continue
and
get
pushed
into
121
as
well.
So
we
don't
have
an
official
list
of
these
things.
A
I
think
that
we're
hoping
to
solicit
the
the
knowledge
of
the
people
present
to
see
what
issues
they've
seen
that
has
momentum
that
we
would
likely
be
continuing
work
on
in
the
in
the
near
future.
A
I
think
well,
joseph
mentioned
right
off
the
bat.
There
was
php8
upgrade
or
compatibility,
and
this
isn't
necessarily
something
that's
a
121
issue.
It's
something
that's
happening
continuously,
but
that's
definitely
moving
forward
really
pretty
quickly
tim
or
jen
or
or
peter
or
joseph.
Do
you
guys
have
other
items
that
you
had
in
mind.
A
And
so
this
is
so,
we
already
have
something
akin
to
rabbit
hole
in
core,
and
this
is
the
idea
that
we
would
include
a
content
type
out
of
the
box
that
utilized
it
right.
D
Yes,
but
more
than
that
that
we
would,
if
you
look
at
the
issue,
there's
some
screenshots
and
it
would
not
just
include
that
in
core,
but
also
sort
of
showcase
it
on
the
front
page,
which
is
the
so.
The
the
scope
of
this
issue
is
a
little
broader
than
implied
by
the
title,
and
actually
I'm
trying
to
think
it
might
be
that
we
have
a
separated.
A
Interesting
so
it
looks
kind
of
like
yeah.
I
can
see
card
being,
possibly
one
of
the
candidates
for
the
the
name
of
the
thing
that
we
had
yeah.
D
D
So,
for
example,
you
know
there's
been
some
back
and
forth
about
whether
or
not
to
actually
display
this.
I
think
one
of
the
technical
issues
which
I'm
not
sure
if
I
understand
why
it
is
a
technique.
Jen-
has
raised
the
issue
about
how
do
we,
if
we
have
actual
images
like
how
do
we
include
those
in
core
which
I'd
it's
not
clear
to
me
why
that
would
be
difficult,
but
maybe
I'm
not
understanding
the
issue.
E
Just
because
we
don't
have
any
files
in
the
files
directory,
so
a
cop
like
an
image,
that's
content
that
someone
could
like
upload.
It
gets
complicated.
So
if
we
wanted
to
do
it
in
a
theme
like
the
way,
we
did
the
basis
well,
the
welcome
area,
the
hero
block
that
doesn't
actually
have
an
image
on
it.
It's
just
added
as
css.
In
the
background.
We
could
do
that
and
give
somebody
an
option
to
override
it.
E
But
just
we
need
to
make
a
decision
about
how
we
want
to
do
that
and
if
we
want
to
like
always
do
that
going
forward
or
if
we
want
to
try
and
add
a
file
during
installation
and
then
where
do
we
get
that
file
from?
Does
it
live
in
in
a
module
somewhere?
So
just
some
again,
not
technically
hard,
but
decisions
that
need
to
be
made.
A
F
D
A
Okay,
very
cool:
let's
see
we
can
go
ahead
and
size
this
too.
So
what
have
we
got
here?
This
is
votes.
We
don't
have
votes
on
this
one,
but
size.
D
D
D
A
Yeah,
it
might
might
yeah
it
might
be
a
medium
but
yeah
so
impact.
Let's
see
stats
status.
Okay,
so
naming
decisions.
D
I
would
say
that
the
two
things
that
we're
struggling
with
a
bit
or
when
naming
decisions
and
two
just
how
to
display
you
know
what
you
saw
was
one
proposal
for
sort
of
how
to
to
show
this
on
the
front
page
and
then,
as
soon
as
we
start
doing
things
to
the
front
page,
then
other
issues
sort
of
pop
up.
Although
I
think
we're
trying
to
limit
it
to
this,
you
know
to
just
adding
this
one
like
region
and.
A
Yeah
big
issue
here
too,
I
imagine
this
has
been
discussed
in
the
extensive
comments
here.
Is
that
as
soon
as
we
add
another,
especially
a
content,
type
like
this
that,
where
there's
like
some
styling
applied
here,
you
know
we
also
need
to
theme
it
essentially,
so
that
you
know
that
also
gets
into
the
design
aspect.
A
little
bit.
F
A
D
Well,
yeah,
and
I
think,
and
I
don't
know
I
don't
remember
if
this
is
an
issue
or
if
it's
going
to
cause
problems,
but
I
want
to
say
that,
like
you
know
what
this
is
is
largely
like,
I
don't
think
we
added
any.
I
don't
know
if
we
had
to
add
any
css,
but
we
did
add
like
a
view
with
some
classes,
in
the
view
to
sort
of
get
it
to
display
this
way.
D
B
Last
week,
greg
said
that
he
was
really
interested
in
working
on
the
that's
right:
the
field
creating
new
fields,
ui.
D
A
Be
this
one
yeah:
this
is
a
couple
of
weeks
ago,
yeah.
This
is
reworking
the
ad
field
process
substantially
and
apparently
there's
a
contributed
module
in
the
world
of
drupal
called
dream
fields
that
implements
a
new
way
of
adding
fields.
A
Yeah
definitely
an
interesting
option
here.
Yeah,
I
think
we've
and
there's
a
much
bigger
issue
here.
This
meta
field,
ui
redesign,
it
seems
like
this-
is
a
a
more
explicit
direction.
Where
he's
saying
here's
one
option
that
is
in
front
of
us
that
we
could
potentially
adopt
it's
not
necessarily
like
this
issue.
Isn't
so
much
like,
let's
discuss
options
so
much
as
it
is,
let's
discuss
this
option.
D
A
Interesting,
he
pulled
this
in
nine
days
ago.
A
Okay,
well,
we
can
add
it
to
the
milestone,
we'll
see
how
this
shapes
up.
A
Well
so
this
issue
like
or
this
feature
exists
within
drupal
8,
and
it
honestly
has
never
really
worked
right,
and
I
think
that
by
itself
like
presents
exactly
how
difficult
it
is
that
it's
it's
a
lot
more
challenging
than
it
than
it
seems
so
on
a
lot
of
sites.
We
it's
on
by
default,
I
think,
even
in
in
new
drupal
sites,
but
on
a
lot
of
sites.
A
I
ended
up
turning
it
off
because
it
it
very
frequently
like
suppresses,
like
the
error
message,
doesn't
show,
and
so
what
ends
up
happening
is
that
the
page
reloads,
but
the
field
that
contains
the
error
is
somehow
hidden
or
not
shown,
and
so
the
page
reloads
and
there's
just
nothing.
It's
just
like
the
save
just
doesn't
work
and
it's
really
hard
to
tell
exactly
what
failed.
A
Sometimes
it
has
a
little
message
up
at
the
top
that
says,
like
you,
know,
check
the
fields
below
for
errors
and
correct
them,
but
then
it's
like,
but
it
doesn't
tell
you
which
fields.
So
it's
just
like
you're,
just
completely
helpless
like
trying
to
find
which
field
failed.
The
validation
you
have
to
click
through
the
whole
node
form
trying
to
find
it.
D
A
Okay
well
interesting.
Sorry,
I
have
to
keep
muting.
I
have
allergies
that
are
bothering
me
so
all
right,
let's
see
so
yeah
I
I
would.
I
would
call
this
a
large
but
sounds
like
the
impact
that
or
the
approach
that
gregory's
thinking
makes
him
think
that
it's
easier
than
that.
So
maybe
we'll
compromise
and
put
it.
B
B
A
Yeah,
let's,
let's
do
impacts
on
these
these
couple
of
items
before
we
go
back
up
to
the
top,
just
while
we're
here
so
hidden
content
type
in
core.
What
do
we
think
we
haven't
defined
our
impact
levels?
Yet
maybe
that's
what
needs
to
happen?
First
right.
A
So,
let's
see,
I
would
probably
say:
okay,
so
I'm
just
gonna
start
throwing
out
ideas
here
so
effects
out
of
box
experience.
It's
like
a
medium
item.
D
C
D
You
know
from
for
me,
high
impact
might
be
something
that
would
get
a
lot
of
attention
like
if
we
tweeted
about
it,
which
might
be
completely
contrary
to
somebody
else's
definition
of
high
impact.
Something
could
be,
could
have
high
pr
value
and
really
low
user
impact
right,
like
that's
possible.
Hopefully
it's
not
the
case,
but
I
and
I-
and
I
think
these
are
two
both
legitimate
ways
of
thinking
about
impact.
D
You
know
we
offer
caching
or
cash
tax.
I
think
we've
often
discussed
is,
is
like
having
a
bigger
pr
value
than
maybe
actual
value.
Just
because
a
lot
of
people
ask
for
it
and
compare
us
to
drupal
8.
Yet,
as
joseph's
pointed
out,
you
know
it
might
not
actually
affect
users
all
that
much.
C
All
right,
let
me
throw
out
sort
of
what
I
had
in
in
mind
with
this
and
it
it
has.
Let's
do
sort
of
the
nature
and
the
type
of
the
impact
itself,
but
more
the
the
audience
so
so
kind
of
the.
Let
me
throw
out
like
sort
of
three
possible
levels
that
I
would
think,
whereas,
like
the
the
smallest
one
would
be,
people
who
are
experiencing
this
issue
directly
themselves
would
understand
and
appreciate
this
change.
C
The
medium
size
would
be
people
who
are
familiar
with
backdrop
in
general,
but
not
maybe
not
that
particular
issue,
but
just
if
they're
in
the
backdrop
world
and
understand
that
they
would
appreciate
why
this
is
a
good
thing
and
the
largest
impact
is
people
who
don't
know.
Backdrop
would
still
appreciate
that
this
is
a
a
good
thing.
So.
C
D
I
think
that's
pretty
useful
luke
and
it's
the
direction
I
was
going
and
an
example
of
this
would
be
the
the
pageless
no
or
the
pathless
nodes,
not
the
pathless
nodes
themselves,
but
are
displaying
them
on
the
front
page.
D
To
me
it
would
have
a
large
impact
because
it
it
refreshes
the
look
of
a
backdrop
on
the
front
end
and
makes
it
look
much
more
like
a
website
and
so
to
me
it
would
be
like
high
impact,
because
you
wouldn't
need
to
know
anything
about
backdrop
to
to
appreciate
the
fact
that
backdrop
looks
a
lot
better.
Yeah.
A
Non-Users
yeah
somebody.
A
D
A
Great
okay!
Well,
I
like
this
I'll,
get
rid
of
this
option.
Well,
I
guess
optional
modules
kind
of
actually
applies
but
yeah.
So
this
looks
pretty
good,
so
low,
optional
modules,
beneficial
mostly
to
power
users,
medium
effects
out
of
box
experience
beneficial
to
most
we're
all
backed
up.
Users
and
hai
is
major
new
features,
modules,
tweetable,
noticeable
or
marketable
to
potential
users.
Yeah.
C
I
I
think
we
want
to
use
the
word
impact
as
a
placeholder
like
I
don't
replace
with
anything,
because
I
don't
want
to
replace
it
with
something
else.
That's
also
not
describing
it,
but
but
if
there's
a
word
that
describes
sort
of
marketability
and
visibility-
and
you
know
pr
value.
A
Okay,
are
we
good
enough
to
roll
with
this?
Do
you
think.
D
A
C
A
A
A
Okay,
okay,
add
a
hidden
content
type
in
core
yeah.
I
what
do
you
guys
think
on
this
one?
D
I'm
going
to
make
a
an
argument
for
large
because
of
the
way
we're
implementing
it
that
the
re,
because
it's
coming
with
a
redesign
of
the
front
page,
which
I
think
just
makes
backdrop
to
everybody,
look
much
more
appealing
and
that's
why
the
the
the
content
type
itself.
I
would
call
a
medium
impact,
but
putting
it
on
the
front
page
to
me
gives
it
a
large
impact.
A
I
would
have
said
medium
but
sure,
okay,
I'm
not
sure
field
ui
actually
got
in
this
list.
I
think
we
were
thinking
about
it
because
gregory
had
mentioned
that
recently,
but
I'm
not
sure
this
actually
is
in
the
in
the
list.
A
Okay,
inline
form
errors
so
size,
medium
impact.
B
A
Users
fill
out
forms
right,
but
I'm
not.
C
Yeah,
I
I
it
shouldn't,
really
be
important
so
much
like
he
can
it's
more
just
what
who
you're
explaining
it
to
that
actually
sounds
like
a
broad
audience.
I
mean
people.
C
B
C
A
Yeah,
okay,
so
it
sounds
like
we're,
definitely
a
medium,
but
I'm
not
really
sure
about,
like
you
know
that
this
would
matter
to
people
outside
of
backdrop.
You
know:
okay,
okay,
good,
so
we're
pretty
solid
there.
A
Okay,
let's
start
back
up
from
the
top,
so
add
field
group
functionality
to
core
our
most
popular
item
from
the
survey
impact
rating
here.
A
I'm
looks
like
a
medium
to
me.
What
do
you
guys
think.
C
A
Multiple
files,
image
uploads-
this
isn't
exactly
like
a
earth
shattering
thing
at
this
point.
This
is
like
catching
up
honestly,
so
I
don't
think
this
is
really
like
something
that
would
be
like
a
key
feature.
It
wouldn't
wouldn't
be
large,
but
it
does
affect.
Like
absolutely
everybody,
I
would
think.
C
A
A
Reference
module
to
core-
I
think
I
think
this
one
is
is
a
high
impact
and
I
know
it
might
not
be
like
just
said:
multiple
uploads
isn't
impressive,
but
references
in
the
general
scheme
of
cmss
is
a
really
substantial
feature,
because
wordpress
doesn't
have
anything
like
references,
a
lot
of
other
cmss,
don't
either
it's
kind
of
like
this.
C
A
Great
okay
recipe
project
type,
this
one
could.
C
A
Okay,
add
an
icon,
font,
decor
or
just
icons
in
general,
because
it's
this
kind
of
taken,
a
new
turn
sorry
and
it
we
already
have
icons
in
core.
This
is
actually
more
about
vector
icons
in
core,
whether
it's
an
icon,
font
or
svg,
driven
font.
A
Right
and
I
would
even
say
that,
even
if
it
were
available
to
all
contrib
modules,
I
guess
that
it
might
affect
end
users
eventually,
if
modules
start
using
them
more
regularly.
But
I
don't
know
I
I'm
saying
this
is
like
a
this
is
like
useful
to
developers
and
and
power
users,
because
it's
like
the
big
difference
between
the
convenience
of
having
an
icon.
That's
already
there
versus
going
out
getting
font
awesome
and
then
converting
the
icon
to
a
png
or
an
svg
like
that's
like
a
convenience.
E
So
there's
like,
I
think
that
there's
two
different
with
this
particular
issue
that
should
maybe
be
like
rephrased,
so
that
we
can
adequately
size
it,
because
it's
currently
solving
like
two
problems
and
the
current
solution
mentioned.
There
is
not
solving
two
problems.
It's
only
one
and
it
would
be
small.
C
So
so,
but
wait
wait,
wait.
I
I'm
not
sure
if
I
understand
I'm
I'm
feeling
inflationary
here,
because
this
one
seems
big
to
me
too,
hey
what
what
does
this
like,
like
nate,
just
the
way
he
described
it?
C
E
E
Different
approaches
to
this
one
of
them
is
we're
going
to
provide
like
a
library
of
infinite
icon
options
for
anyone
to
use
and
the
other
one
is
we're
just
going
to
replace
the
16
icons.
We're
using
in
core
and
replacing
the
16.
We're
using
in
core
doesn't
really
benefit
anyone
other
than
the
core
development
team,
or
maybe
kintrib
if
they
happen
to
use
the
same
icon,
which
would
probably
be
a
bad
idea
anyway.
E
But
if
we
provided
a
utility
for
anyone
to
easily
add
in
like
individual
one
of
hundreds
of
icons,
then
it's
big,
but
I
think
that
that
particular
issue,
it
says,
add
an
icon
font
to
core
which
describes
the
big
solution,
but
the
technical
implementation
that
we're
working
on
that
issue
just
replaces
course
icons
which
is
small.
So
I
think
we
need
to
rephrase
the
issue
title,
at
least
in
this
spreadsheet,
if
not
an
issue
itself
to
indicate.
This
is
not
the
feature
that
everyone
wants,
that
it's
the
thing
that'll
only
help
core.
B
E
D
C
E
A
And
things
have
been
done
a
bit
at
some
of
these:
let's,
let's
keep
chugging
along
here
that
one's
yeah
definitely
yeah.
It
needs
more
clarification,
automatic
updates.
C
A
Yeah
everybody
uses
backdrop
and
everybody
that's
considering
a
cms.
I
think,
because
this
lowers
maintenance
cost
potentially,
depending
on
your
you
know,
your
setup,
okay,
exposed
fields
to
layout
visibility,
conditions.
A
E
A
C
Anyone
anyone
who's
like
actively
building
backdrop
sites
would
be
like
oh
yeah,
I'll
use
that
I
mean
no
one's
not
going
to
use
it
if
it's
available-
and
you
know
much
more
so
if
it's
built
in
than,
if
you
have
to
find
it
and
contribute
like
like
moving
that
into
core,
is
a
giant.
You
know
visceral
change
to
the
accessibility
of
that
particular
feature.
A
E
A
Views
book
operations
allow
for
updating
entity
values.
Well,
this
based
on
the
previous
conversation
previous
lineup
seems
like.
It
is
also
the
same
thing.
Don't
you
think
so
right?
I.
A
C
E
Wouldn't
care
these
bulk
operations
is
now
on,
like
the
content
listing,
so
everyone's
uses
it
whether
they
know
they're
using
it
or
not.
It's
just
it's
there
and
I,
I
think
yeah,
I
don't
know
I'm
also
leaning
towards
small,
even
though
I
feel
like
these
bulk
operations
is
there,
I
feel
like
the
amount
of
times
I
want
to
change
the
values
of
all
of
my
fields.
F
A
C
E
I
don't
know
how
many
current
drupal
7
site
owners
would
attempt
an
upgrade
this
way,
and
maybe
her
point
is
that
if
we
make
it
easy
enough,
they
will
try
even
if
you're
a
developer.
If
it
takes
you
five
seconds
to
throw
at
any
base,
and
you
would
do.
A
A
Yeah
and
and
so
irena,
just
going
some
context
here
is
one
of
the
backdrop
user
who's
currently
undertaking
an
upgrade.
She
works
at
stanford
and
yeah.
There's
some
active
issues
right
now,
where
she's
struggling
to
like
get
past
like
step,
one
kind
of
of
like
import,
the
database
so
yeah.
I
think
she
would
probably
say
yes,
because
then
at
least
she
would
have
a
backdrop
site
that
was
working
and
she
would
try
to
be
trying
to
pull
stuff
into
it
rather
than
just
seeing
php
errors.
A
C
I
I
mean
my
migration
issues
in
general,
I
mean
I,
I
think
I
think
that
is
of
giant
importance
to
our
community
and
and
and
that
that
is,
that
is
a
big
gatekeeper
to
the
rest
of
the
world.
That's
not
using
backdrop.
So
so
I
I
think
almost
anything
that
might
make
migration
easier
is
large
market.
Now
now,
if
they
don't
work,
you
know,
then
you
know
that's
a
different
issue,
but
like
right,
anything
that
might
make
it
easier
is
is
broadly
happenable.
A
Yeah,
okay,
I
I
agree.
I
think
I
think
this
would
be
a
high
impact
thing,
even
even
if
it
wasn't
like
it's,
not
something.
People
are
going
to
be
using
all
the
time,
but
it's
would
be
pretty
critical
to
getting
new
users
into
backdrop
and
if
we
say
affects
new
users
or
affects
potential
users,
then
that
makes
a
high
impact.
D
A
Okay,
see
you've
got
a
couple.
Minutes
left,
select
all
items
on
all
pages
in
vbo.
A
D
A
A
A
A
Marked
as
l,
so
you
might
want
to
fix
that
yeah.
So
that's
exactly
what
happened:
hi,
okay,
yeah
boy!
I
just
got
this
yeah.
I
made
this
really
messy
low.
Okay,.
A
Okay:
okay,
move
the
title
display
settings
to
the
manage
form
display,
manage
display,
form.
A
Yeah,
I
would
be
inclined
to
say
that
this
is
low
impact.
A
I
mean
it
is
kind
of
a
long-standing
inconvenience,
but
it's
also,
you
know
like
because
you
tend
to
land
on
the
content,
type
settings
form
first
and
that's
where
the
settings
are
are
located
already
and
then
and
then
you
add
fields
afterwards,
like
workflow
wise,
it
seems
like
I
don't
run
into
this
problem
very
frequently,
because
I'm
kind
of
introduced
to
where
the
settings
are
before
I
get
to
adding
individual
fields.
C
Like
think
about
impact,
maybe
this
will
sort
of
get
across
like
if,
if,
if
somebody's
asking
their
their
boss
for
permission
to
like
move
their
site
to
backdrop,
high
impact
is
something
where
the
boss
might
say:
we're
not
doing
it.
Unless
it
does
this,
and-
and
this
wouldn't
be
that
kind
of
thing
this
would
be
like
boss-
doesn't
care
whoever's
doing
it's
happy
to
to
have
their
life
a
little
better.
A
Okay,
all
right
we're
going
to
run
out
of
time.
Actually,
I
think
we've
already
kind
of
run
out
of
time.
A
We
did
really
well,
I
mean
we
added
three
additional
items
and
there's
only
one
two,
three
four
five,
six
six
items
remaining
so
yeah
we
did.
We
did
really
really
well
going
through
and
slicing
on
impact.
C
A
Okay,
well,
I
guess
the
next
step
here
is,
you
know
we
have
do
we
have
a
session?
Actually,
I
should.
A
We
potentially
will
have
a
section
section
session
on
this
during
backdrop,
live
which
starts
tomorrow
and
runs
through
part
of
saturday,
so
I
guess
the
next
step
here.
You
know:
we've
got
events.backdropcms.org
backdrop
live
starting
tomorrow
and
the
day
afterwards,
so
yeah.
This
is
probably
the
next
place,
we'll
see
this,
and
if
we
don't
discuss
it
during
backdrop,
live
you
know,
then
we'll
pick
it
up
again
next
week
during
weekly
meetings.
A
A
Well
thanks
everybody
for
participating
in
this
discussion,
it
was
fun
and
interesting,
as
always
to
like
kind
of
go
through
these
things
and
start
sliding
them
out,
and
the
whole
point
of
this
exercise,
of
course,
is
to
give
people
direction
and
priorities.
You
know
to
like
look
at
this
list
and
say:
oh
I
want
to
do
something.
Of
course
everybody
would
love
to
have
a
high
impact
thing.
That
is
easy
to
do
right
so,
but
other
people
could
be
looking
for
challenges
or
maybe,
if
they're
looking
at
things
saying.
A
So
thanks
again
for
participating
in
this
discussion,
we
will
catch
up
again
tomorrow
during
backdrop
live
or
next
week,.