►
From YouTube: Backdrop Weekly - 2021/02/18
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
Every
time,
okay,
we
are
live.
Welcome
to
the
backdrop
weekly
dev
meeting.
We
are
live
streaming,
this
on
youtube
and
recording
it.
So
if
you
don't
want
to
be
recorded,
please
turn
off
your
camera
and
or
mic,
but
we
do
welcome
people
participate
in
these
meetings,
join
us
in
zoom
and
and
engage
with
us.
So
if
that's
your
choice,
please
join
us.
I
let's
start
with
our
regular
introductions.
A
Oh
so
I
mentioned
that
we
might
have
a
my
sister
coming
today
and
she
didn't
get
the
link
in
time
and
I
did
just
send
it
to
her
and
she
was
going
to
come
and
just
kind
of
observe
our
meeting
today.
So
if
she
pops
in
and
doesn't
know,
what's
going
on,
that's
what's
happening.
A
I
don't
know
if
I
told
her
that
these
were
being
recorded,
so
I
might
remind
her
of
that
once
we
when
she
gets
here,
but
she's
gonna,
then
meet
with
us
later
and
talk
about
our
process,
maybe
a
little
bit
and
give
us
some
thoughts.
Anyways.
My
name
is
tim
erickson,
I'm
here
from
deerwood
minnesota,
the
the
turkeys
have
just
arrived
to
to
feed
outside
my
window,
and
most
of
my
focus
over
the
last
week
has
been
on.
I've
started
a
contrib
theme.
A
B
Hi,
I'm
greg
usually
in
australia
joining
from
greece.
I've
been
away
away
for
a
week
or
so
usually
when
I'm
away,
I
just
don't
attend
the
meetings,
but
I
still
follow
the
zulip
chat
and
the
issue
cue.
But
this
time
I
was
away
away,
so
I'm
trying
to
catch
up
with
everything
and
help
where
I
can
I've
went
I've
gone
through
all
the
zulu
chat
and
now
I
I'm
looking
forward
to
go
back
to
the
issue
and
my
pull
requests
over
the
weekend.
C
I'm
robert
lang
from
altadena
california
bug
folder
on
github
and
zulip,
and
I
lately
I've
been
working
on
bugs.
C
D
Hello,
I'm
jack
aponte
pronouns.
Are
they
them
I'm
getting
back
in
the
loop
on
all
things,
backdrops
so,
and
mostly
just
lurking
and
listening,
while
also
dealing
with
emergency
websites?
Well,
mostly
civ
crm
sites,
but
anyway
doing
both.
So
that's
why
my
camera
is
mostly
off
get
to
see
everyone
I'll
go
to
jen.
E
Hi,
I'm
jen
lampton,
I'm
joining
from
oakland
california,
my
parents
are
she
and
her.
I
am
very
excited
about
working
on
backdrop
projects.
I
launched
a
site
yesterday
and
I've
got
another
one
coming
up
in
a
few
weeks,
so
yeah,
hopefully
I'll,
get
some
more
time
here
soon
to
help.
With
all
the
backdrop
stuff,
I
want
to
work
on.
E
Let's
see
I
wasn't
here
in
the
beginning,
greg
have
you
gone
already?
Yes,
robert
has
tim.
B
F
G
Hey
phil
ward
out
of
wichita
kansas
kind
of
here
just
to
see
what's
going
on,
I
don't
have
anything
in
particular
to
bring
up
or
discuss.
I
think
that's
probably
it
in
it.
H
And
me
I'm
nate
lampton
from
oakland,
california
and
yeah.
Just
checking
in
on
everything
also
have
had
a
real
busy
week
and
haven't
been
able
to
get
through
the
review
cues
recently,
but
we'll
still
go
through
and
talk
about
the
progress
that
we're
making
as
a
community
jen.
Since
you
managed
to
come
back,
would
you
be
able
to
give
us
the
contributed
project
updates?
Yes,.
E
So
we've
had
four
new
contrib
modules
with
official
releases
in
the
last
week.
That
includes
civil
serum
group
nodes
jwt,
which
I
think
is
jason.
I
forget
something:
fancy
views
auto
refresh
and
translation
access.
Nate.
Did
you
just
look
that
up
for
me.
E
We
go,
I
thought
I
saw
your
cursor
move
over
and
I'm
like
he's.
Gonna
save
me,
though
jason
webb
tokens,
that's
it
for
contributing
project
updates.
I
have
seen
a
ton
of
activity
happening
in
contrib
lately,
so
I
just
wanted
to
send
another.
Thank
you
out
to
everybody,
who's,
working
on
porting
modules,
creating
modules
and
making
new
releases
of
existing
modules.
So
thanks
community
and
then
let's
turn
it
back
over.
Oh
actually,
should
we
go
into
website
related
tasks.
E
E
Then
I
don't
think
we
have
anything
pressing
happening
on
the
forum
website,
but
the
api
website
is
currently
being
updated.
We
have
changed
it
to
a
documentation
site
instead
of
just
solely
an
api
and
we're
currently
working
on
migrating.
E
The
content
from
the
primary
backup
backdropsimas.org
site
this
week,
bw
panda
very
kindly
assigned
the
ticket
to
me
that
I
said
I
would
do
so,
I'm
hoping
to
get
to
that
one
today
after
this
meeting
is
over-
and
there
was
a
great
virtual
user
group
earlier
this
week
about
multilingual
websites
and
it
sparked
a
lot
of
ideas
in
my
head
about
ways
to
improve
the
translation
website.
E
But
I
decided
not
to
immediately
start
working
on
them
because
I
have
enough
on
my
plate,
but
I'm
hoping
that
we'll
be
able
to
make
the
process
of
contributing
documentation
easier
or
for
contributing
translation
files
easier
for
people
in
the
future.
Since
I
couldn't
figure
out
how
to
do
it,
we
also
have
a
new
website
we're
working
on,
which
is
our
events,
site
and
tim,
and
I
tried
to
have
a
meeting
on
tuesday
after
the
virtual
user
group
to
discuss
the
future
of
that.
E
But
we
were
distracted
by
all
of
the
amazing
conversations
based
on
content
in
the
virtual
user
group.
So
tim,
I
don't
know
if
you
want
to
touch
base
later
today
about
that
also
to
do
there
too.
E
If
anyone
has
anything
in
particular,
you
think
we
should
be
working
on
for
any
of
those
sites.
That
is
information.
That's
also
welcome
in
this
weekly
agenda.
So
as
activity
happens
in
those
cues,
we
can
talk
about
it
here
too.
H
Sure,
let's
see
so,
we
have
a
number
of
bug
fixes
that
we're
trying
to
get
in
as
soon
as
possible.
Sorry
bug
yeah
bug
fixes
that
we're
trying
to
get
in
as
soon
as
possible
for
118.2.
That
will
be
our
next
bug
fix
version
that
will
come
out
as
soon
as
we
accrue
a
substantial
number
of
bug
fixes
that
weren't
a
release.
H
E
H
You
maximize
the
editor
and
then
close
the
max
maximize.
Then
it
doesn't
save
the
content
that
you
have
typed
into
your
editor,
which
is
a
big
issue.
So
4933
is
that
issue
there's
currently
no
pull
request
or
anything
like
that
right
now.
It's
just
a
call
for
some
help
that
that
issue
has
been
discovered
and
is
rather
prevalent,
because
the
maximize
button
is
enabled
out
of
the
box
in
new
backdrop
installations.
So
it's
something
that
can
affect
content
entry
on
all
backdrop,
websites.
H
H
This
issue
was
bumped
from
the
one,
eight
or
sorry
the
one
eighteen
point
one
release
and
is
ready
to
go
in
any
time,
but
does
require
an
update
hook
so
issue
that
issue.
We
can
merge
in
pretty
much
any
time
and
it
will
probably
be
in
there
shortly.
H
Php
8
support
has
seen
some
kind
of
interesting
things.
This
past
week
issue
47
72.
It
looks
like
from
the
reading
of
the
issue
gregory
that
now
lando
has
a
php
8
support,
and
that
makes
testing
this
a
lot
easier.
Is
that
right.
B
H
And
so
what's
what
has
been
the
outcome
of
that
testing?
Is
this
like
at
this
point?
Is
there
more
work
to
be
done?
Do
you
think
on
moving
this
forward
or
now
that
it's
easily
testable?
This
is
something
that
we
could
probably
merge
in
and
then
build
upon.
B
It's
easier
testable
for
people
that
are
used
to
use
lando
for
the
local
and
I've
tested
it
with
a
vanilla,
bankrupt
thing,
and
I
had
a
wide
screen
of
death
come
up
with
an
error,
and
when
I
tested
with
a
pull
request,
then
I
got
through
the
installer
without
any
problems,
so
the
I
marked
it
as
for
me,
I
think-
or
at
least
I
waited
for
more
input,
but
I
haven't
done
any
good
review
yet.
H
Great
excellent
that
makes
that
definitely
make
things
a
lot
easier.
Setting
up
multiple
php
versions
is,
is
a
huge
hassle.
I
think
that's
one
of
the
greatest
benefits
of
these
container
based
tools.
B
Yeah
this,
when
you
use
lanzo,
there's
still
some
errors
when
you
start
up
about
composer,
but
that
has
been
fixed
in
a
pre-release
version
of
lambda,
but
that's
not
official.
Yet
so
it's
not
in
the
brew
installer
tasking.
Yet
so
yeah
waiting
for
for
a
little
bit
of
you
know
more
fixes
on
that
and
so
that
we
can
test
easily
yeah.
H
Okay,
let's
see
next
up,
we
have
this
issue
with
internationalized
menu
links
that
the
active
trail
gets
confused
when
the
same
path
is
in
multiple
links
in
multiple
languages.
It's
kind
of
a
hard
one
to
wrap
your
head
around.
C
H
Issue
is
47.98.
The
fix
is
really
simple.
However,
it's
like
a
two-line
correction
and
it's
stuck
right
now,
because
we'd
like
to
get
test
coverage
for
it,
but
writing
the
tests.
It's
it's
a
complicated
scenario,
which
is
a
a
problematic
thing,
because
edge
case
scenarios
are
the
things
that
we
absolutely
should
be
covering
in
tests
because
they're
hard
to
reproduce
so
yeah
we're
stuck
right.
Now
that
we
have
complicated
tests
that
need
to
be
written.
H
I
I
don't
want
to
really
flex
on
that
too
much.
I
know
the
the
kind
of
request
was.
Can
we
just
not
have
tests
because
it
fixes
a
problem,
and
I
think.
E
I
came
up
with
an
idea
of
a
way
that
we
can
reproduce
the
problem
without
the
current
steps
to
reproduce,
but
it
would
involve
creating
a
custom
module
to
mimic
the
behavior
abuse
arguments
which
shouldn't
be
too
hard,
but
it
is
very
different
so
that
none
of
the
stuff
we
have
now
can
be
used
to
have
to
really
be
a
brand
new
from
scratch
solution.
But
yeah.
H
Yeah
I
kind
of
like
that
yeah
I
like
that
a
lot
actually
just
make
a
module
that
has
those
menu
entries
directly
rather
than
setting
up
a
view
to
do
the
same
thing.
That's
a
great
idea,
yep
and
we've
got
lots
of
examples
of
those
hidden
testing
modules.
There
probably
already
is
one
for
for
menus
that
we
could
just
add
additional
items
to
great
good
idea.
H
Okay,
next
up
is
a
new
issue.
The
bug
folder,
I
think,
filed
bug.
Folder
is
robert
lang,
who
is
joining
us
for
this
meeting.
I
can
give
the
short
version
that
we
at
one
point
removed
the
the
long
filter
tips.
I
I
can't
quite
remember
what
the
link
used
to
say
more
information
about
text
formats.
H
E
C
Yeah
the
so
the
specific
problem
that
arose
was
for
the
in
the
token
filter
module,
a
user
complained
with
some
justification
that
the
short
description
of
the
filter
didn't
say
what
tokens
were
allowed
and
what
could
be
used
and
that
information
is
in
the
long
description,
but
there
was
was
no
way
for
the
user
to
know
in
the
formatting
options
that
how
that
they
could
get
there,
how
how
to
find
that,
and
so
the
suggestion
before
I
knew
that
it
had
been
removed.
C
H
H
So,
while
the
solution
that
was
to
open
it
up
in
a
new
window,
but
still
it's
another
page,
that
takes
you
away
from
the
content,
editing
form
and
then
that
page
was
also
created
at
a
time
where
text
formats
were
more,
you
know
developer
oriented
where
it
was
like:
here's
how
to
type
html
and
here's
potentially
how
to
use
certain
markdown
components,
and
now
that
we
include
a
rich
text,
editor
out
of
the
box.
H
A
lot
of
that
help
text
just
isn't
relevant,
despite
the
fact
that
it's
still
there
like
here's,
how
to
type
a
bold
tag
really
doesn't
matter.
It
does
matter
if
you're
using
like
markdown
or
something
like
that,
but
yeah
still
we're
definitely
more
oriented
towards
the
rich
text
editor
than
we
are.
On
these
hand,
typed
text
formats.
C
C
For
the
token
filter
module,
even
if
someone's
using
the
rich
text
editor,
it's
it's
useful
to
the
user
for
them
to
see
what
tokens
they
can
put
into
their
rich
text
editor
one
one
idea
I
had.
I
think
I
posted
somewhere
in
the
queue,
was
as
a
possibility
to
avoid
actually
leaving
the
page
would
be
a
javascript
pop-up
overlay,
like
tooltip
style
thing.
H
Like
the
token
browser
yeah,
which
actually
in
the
case
of
this,
because
it's
actually
related
to
tokens,
that
literally
could
be
the
solution
is
using
the
existing
token
browser
filtered
to
the
tokens
that
are
available.
However,
I
don't
think
the
token
browser
can
insert
into
ck
editor
it
can.
It
can
only
insert
into
text
fields
and
text
areas.
I
think
it
does
have
some
like
javascript,
that
when
you
click
on
the
token
it
will
insert
where
your
cursor
last
was,
but
I
don't
think
that
works
with
seek
editor
yet.
H
But
if
this
is
the
solution
that
we're
moving
towards,
then
you
know
adding
that
capability
would
be
a
good
solution,
but
that
would
that
would
mean
that
we'd
end
up
with
something
that
is
specialized
for.
H
C
As
a
maybe
a
side,
question
is:
should
the
documentation
on
call
filter
tool,
tips
that
tells
you
pro
that
instructs
you
to
provide
a
short
and
a
long
version.
Should
that
somehow
be
updated
to
note
that
the
long
version
basically
is
kind
of
deprecated
or
you
know,
is
it
you
know,
people
put
it
if
we
provide
a
long
version,
there's
an
expectation
that
users
would
eventually
be
presented
with.
H
Right
right,
yeah,
I
I
think
the
way
that
we're
treating
that
page
is
that
it's
deprecated
we
just
haven't,
maybe
at
the
time
that
we
made
that
decision
we
weren't
so
clear
on
when
and
what
to
do
with
deprecated
stuff.
But
I
think
first
of
all
we
should
make
that
decision.
H
I
think
all
of
those
things
are
good
ideas
that
we
should
do.
H
Well,
I
think
in
this
issue,
because
of
the
way
that
it's
titled
and
phrased,
I
think
that
we
should
use
it
as
the
discussion
for
is
this
thing
deprecated
and
update
the
documentation,
and
then
we
should
make
a
separate
issue
for
the
token
browser
can't
enter
into
ck
editor,
and
then
we
should
make
a
contrib
issue
or
use
the
existing
contrib
issue
to
say
that
should
open
it
up
in
a
modal
instead
of
using
the
long
filter
tips
so
that
three
three-way
attack.
B
H
Yeah,
just
it
there's
a
way
that
you
can
format
the
link
that
will
automatically
make
it.
Actually,
I
think,
there's
a
theme
function
for
a
theme,
token
browser
modal
link
or
something
like
that.
That
will
make
the
link
that
will
open
the
token
browser
and
you
tell
it
what
token
types
to
allow
and
then
it
shows
it.
So
it's
really
easy
to
make
the
link
and
to
make
a
modal
pop
up
anywhere
in
backdrop,
but
yeah.
We
need
to
make
it
work
with
c
editor.
H
B
H
I'd
also
would
love
it
if
there
are
any
thoughts
about
long
filter
tips
and
if
they
are
still
useful
in
some
way.
You
know
get
some
counter
points
to
that
in
this
issue
that
we
already
opened
49.53
or
if
people
are
in
agreement
with
what
we've
done
in
the
past,
which
is
just
kind
of
quietly
sunset.
The
long
filter
tips.
H
Yeah,
and
in
this
case,
we
already
have
a
better
tool,
I
think,
and
that
we
should
just
use
that
that
better
tool
that
doesn't
take
you
off
the
page.
That
more
clearly
shows
you
what
the
tokens
are
and
and
provides
the
capability
to
insert
them
without
copying
and
pasting.
All
those
things
seem
like
they're
substantial
benefits
over
using
a
separate
page.
H
Okay,
great,
do
you
guys
have
anything
else?
You
would
like
to
bring
up
for
bug,
fixes
to
discuss.
H
H
We
have
a
number
of
issues
here
on
which
we're
moving
a
little
bit
at
a
time.
The
one
of
the
items
that
got
moved
from
the
previous
release
is
an
issue
that
lauren
is
advocating
for
the
exposed
file
name
filter
for
a
media
library
dialog
to
make
it
easier
to
find
find
items.
H
We
haven't
made
any
progress
on
this
issue
recently.
There's
a
technical
challenge
here
that
we've
got
nested
form
tags
in
the
html
that
make
it
so
that
filtering
doesn't
work
correctly
and
so
issue.
3293
need
some
technical
guidance
as
to
ways
that
we
could
solve
this
problem.
H
Let's
see
next
up,
we
have
better
support
for
cash
tax
and
cash
max
age
issue.
4127
joseph
could
give
us
the
update.
Although
I
have
a
feeling.
I
know
what
you'll
say.
H
He's
not
here,
oh
sorry,
the
well.
What
he
would
say
if
he
were
here
was
that
as
that
there's
a
pull
request
that
needs
review.
H
H
Further
next
up
is
jen
an
issue
that
you're
working
on
field
has
value
visibility,
condition
for
blocks.
It's
issue,
47
28..
I
did
not
have
an
update
on
that
one
this
week.
Okay,
that's
totally
fine,
adding
relationship,
relationship,
support
to
layout
context,
issue,
2134,
an
issue
doc
wilmont
has
been
working
on.
H
This
is
really
close.
It
needs
some
minor
renaming
of
things
and
that's
always
the
hang
upright
is
naming
things,
but
it's
in
a
really
good
place
as
far
as
being
complete
almost
got
into
118
actually,
but
I
think
we
were
nervous
about
including
such
a
major
feature
right
at
the
deadline.
So
this
issue,
I
would
really
love
it
if
we
could
get
it
completed
as
soon
as
possible,
rather
than
leaving
it
to
the
last
minute,
largely
because
if
doc
walmart
were
liberated
of
that
issue,
he
would
probably
pick
up
another
one.
B
H
B
B
H
H
I
posted
a
comment
to
that.
One
saying:
I
think
we
should
just
merge
it,
but
we
should
merge
it
and
deploy
it
all
together.
If
we
merge,
if
we
merge
code
to
backdropcms.org
repository,
I
don't
want
to
leave
it
to
a
point
later
down
the
road
to
like
actually
deploy
it,
because
then,
if
there
were
some
problem,
the
person
that
deployed
the
code
might
not
have
any
idea
that
it
was
related
to
something
that
they.
H
We
will
we
will
accept
more
work
in
exchange
for
you
doing
work,
yeah
well,
in
all
cases
and
jokes
aside.
Let's
also
just
generally
show
some
appreciation
for
doc,
wilma
and
all
of
the
work
that
he
has
been
doing
consistently
and
regularly
and
how
much
we
appreciate
it
in
all
forms.
So
thank
you
document,
okay,
next,
up,
updating
the
core
module
theme
and
layout
pages;
I'm
sorry,
the
update
pages
for
core
modules,
themes
and
layouts
into
a
single
page
for
all
updates
issue:
27
14.,
gregory
you're.
B
H
Okay
and
lastly,
changing
the
word
edit
to
configure
in
configuring
roles
is
issue.
48,
99,
bw
panda
is
the
advocate
for
this.
It's
marked
rtbc.
H
H
H
We
have
a
separate
issue
to
make
it
so
that
those
deprecated
paths
continue
working
across
the
board,
that's
2833,
but
in
the
past
we
have
not
required
all
of
the
deprecated
paths
to
continue
working.
We
get
the
main
ones
working,
but
then
the
deeply
nested
per
item
menu
links
are
not
working
from
old
versions.
So
it's
a
pretty
minor
change,
but
it
has
changed
nonetheless,
and
would
be
nice
if
we
could
get
2833
also
completed
at
the
same
time
to
keep
those
old
urls
working
across
the
board.
H
H
Docs.Backdropcms.Org
and
work
is
ongoing
there
to
consolidate
all
developer
and
end
user
documentation
onto
that
one
site.
B
I
have
I
have
a
few
questions,
so
I
know
jen
muted
itself,
but
maybe
it
is
available,
so
you
can
answer.
There
was
supposed
to
be
migration
of
content
for
the
user
guide
that
we
currently
host
on
the
main
site
onto
that
site.
The
other
day
I
was
trying
to
edit
a
a
change
record.
I
think,
on
the
api
side,
which
is
now
the
dock
size,
and
I
was
reminded
of
the
fact
that
it
doesn't
use
ck
editor.
B
So
we
might
come
into
problems
with
that
because
the
existing
content
has
been
using,
but
it
is
it
something
another
editor
and
it's
not
as
user
friendly
to
to
create
or
edit
existing
documentation
as
it
is
on
the
main
site.
So
this
is
a
problem
that
we
will
eventually
need
to
address.
H
Yeah,
I
think
that's
going
to
become
a
factor
as
we
move
that
end
user
documentation,
which
is
more
likely
to
include
imagery
and
screenshots
compared
to
change
logs,
which
are
more
developer.
Oriented
yeah.
The
the
original
api
site
is
one
of
the
oldest
sites
that
we
maintain
and
it
has
not
been
moved
forward
quite
as
frequently
as
the
flagship
site,
and
so
there's
lots
of
things
that
are
from
when
backdrop
was
much
less
capable
like
we're
not
even
using
link
fields
where
we
have
links,
for
example,
so.
B
H
A
lot
of
ux
work
to
be
done
to
kind
of
bring
it
up
to
speed
with
backdrops
current
capabilities.
B
Quick
solution
might
be
to
have
separate
to
allow
different
filter
formats
with
different
editors,
and
then
people
can
switch
to
that
when
creating
user
documentation
yes
or
start
using
it.
From
now
on.
H
Yeah,
possibly
different
pieces
of
content
using
different
formats
can
just
cause
some
confusion
because
one
person
might
go
through
and
edit
like
four
pages
and
if
some
pages
are
using
one
format
and
other
pages
are
using
another
format
with
a
different
editor.
They
probably
have
a
preference
for
one
or
the
other,
and
then
you
can
kind
of
end
up
having
like
text
format,
wars
where
people
people
are
coming
in
and
editing
the
same
piece
of
content
and
flipping
back
and
forth.
The
text
format
to
get
a
different
editor.
B
E
E
So
the
reason
we
chose
to
put
the
bu
editor
on
theirs
because
it
helps
you
write
the
code
like
it
writes
the
markup
in
the
same
way
ck
editor,
but
without
a
visual
interface
on
top
of
it,
and
so
I
think
that
might
still
be
the
better
option
for
this
site.
Maybe
we
should
do
some
user
testing.
B
B
Just
so
that
I
wrapped
my
head
around
what
you
just
said
with
regards
to
code
snippet
adding,
so
what
is
it
the
b
that
bu
editor
does
that
ck82
doesn't
do.
E
It's
the
other
way
around
ck
editor
adds
a
javascript
layer
on
the
front
end
so
that,
when
you
hit
like
bold,
it
wraps
the
text
in
both,
but
it
doesn't
actually
show
you
the
like
strong
tag.
It
shows
you,
the
text,
folder
formatted,
the!
U
editor
adds
the
strong
tag
and
shows
you
the
strong
type.
It
doesn't
have
anything
on
the
top
to
render
it
into
a
bold
text.
And
so
that's
it's.
E
B
E
H
E
D
F
F
E
I
have
to
use
all
the
time
on
like
normal
text,
but
on
because
the
normal
sequencer
doesn't
work
right,
but
when
you're
trying
to
edit
code,
if
you
switch
to
source
code-
and
then
you
switch
back
it
like
tries
to
render
your
code-
which
it
can't
usually
do
correctly.
But
if
we
can
fix
that
problem,
I
don't
know.
I
think
we
should
test
it
and
find
out
what
the
actual
problems
are
and
work
through
a
list
of
them
and
fix
them
because
there's
a
lot
of
theoretical
problems.
B
And
it
seems
that
it
would
be
great
if
in
source
code
mode
for
ck
editor,
if
you
hit
control
b,
be
the
auto
tag
thing
that
that
bu
editor
does
but
yellow.
H
E
H
A
code
editing
helper.
H
Let's
see
so
that's
it
that
for
the
oh
wait,
I'm
sorry
we're
in
the
initiative.
So
we
already
did
the
118
update.
Okay,
so
that's
it
for
the
documentation.
Update
telemetry
is
another
initiative,
tim
you're.
The
initiative
lead
on
that.
Do
we
have
any
updates.
A
No
and
I'm
gonna
jump
right
because
I
don't
see
luke
still
here
to
the
update
for
the
theme
development
initiative
and
that
we
have
a
the
update
there
is
that
we
do
have
a
meeting
scheduled
for
12
o'clock
pacific
time
next
tuesday,
and
the
goal
for
that
meeting
is
to
kind
of
one
summarize
what
we've
done
on
the
initiative
and
to
like
how
to
bring
it
to
a
close.
A
I
think
you
know
luke
would
kind
of
like
to
wrap
it
up
and
figure
out
what
what
I
don't
know
about
deliverables,
we're
close
to
that.
We
could
kind
of
use
to
finish
this
up.
I'll
just
say
it
occurs
to
me
that
when
we
were
first
talking
about
the
idea
of
initiatives,
I
think
there
was
a
sense
that
they
should
there
should
be
like
a
check-in
period
after
a
year
or
something,
and
it.
A
Been
a
year,
I
think,
since
we
did
the
initiatives,
but
it
might
be
time
for
both
the
telemetry
and
the
theme
development
that
we
kind
of
get
a
year
in
you're
in
check-in
like
what
progress
have
they
made,
and
this
is
this
process
working?
Should
it
should
the
initiatives
continue
or
so
we.
B
A
The
current
blocker
is
that
we
sort
of
got
it
the
rough
part
working
and
we
need
to
figure
out
what
the
next
steps
are.
I
think
I
mean
nate
might
have
more
of
an
id
in
his
head
exactly
what
he
needs
to
do
next,
but
I
actually
don't
know
in
my
head
what
has
to
happen
next.
I
just
need
to
go,
but
we
we
have
figured
out
where
to
store
the
data
for
now
right
that
decisions
were
made
on
that.
H
Yeah,
it
sounds
like
I
need
to
post
a
comment,
if
that's
the
case,
so
that's
the
next
action,
let's
see
so
the
issue
well,.
A
H
Yeah
my
my
memory
of
this
is
that
our
next
steps
here
involve.
H
Further
improvements
to
project
module
to
make
it
so
that
telemetry
can
be
enabled
or
disabled
on
a
per
project
basis,
because
right
now
it's
enabled
just
across
the
board
for
all
of
them.
The
only
one
that
we're
actually
collecting
any
data
for
so
far,
of
course,
is
backdrop
core
itself,
but
we
would
like
to
make
it
so
that,
from
a
privacy
standpoint
that
contrib
modules
need
to
request
a
collection
of
telemetry
data
rather
than
just
storing
any
arbitrary
data
from
all
of
our
users,
websites
onto
backdrop
cms.org's
primary
database.
H
Just
because
there's
really
no
limitation
to
the
kind
of
data
you
can
collect
and
us
storing
arbitrary
data
from
every
backdrop
site
in
the
world
could
get
us
into
various
safe
harbor
laws
and
privacy
problems,
and
things
like
that.
So
we'd
like
to
make
sure
that
we're
only
using
it
for
backdrop
core
initially
and
then
over
time.
If
we
have
contrib
product
or
contrib
modules
that
also
want
to
use
it,
we
need
to
curate
that
and
have
the
ability
to
restrict
it.
A
B
H
Yeah
and
that
portion
as
well
that
we
need
to
start
exposing
the
information
in
various
ways
like
finding
a
way
that
that's
responsible,
and
I
think
what
we
want
to
do
is
have
a
check
box
during
installer
that
says,
collect
information
and
then
it's
there
either
that
or
we
know
for
existing
sites.
We
want
to
get
all
of
the
backdrop
sites
that
are
out
there
right
now
reporting
data
if
they're
willing
to,
and
so
we
also
would
like
to
have
some
kind
of
notification.
H
After
you
update
to
a
version
of
backdrop
that
includes
telemetry
a
notification
requesting
that
you
turn
it
on
of
some
kind
to
make
it
so
that
we
can
start
getting
data
from
every
existing
site
out
there,
and
if
they
dismiss
the
request,
then
we
don't
ask
again
that
sort
of
thing
but
yeah
turning.
H
G
Topic
would
it
be
worth
coming
in
and
having
I
hate
to
do
a
granular
control
of
what
information
gets
sent
over,
but
that's
one
option.
Another
thought
is
to
create
a
telemetry
page
on
on
the
backdrop
course,
the
site
itself
right
that
is
collecting
the
information,
have
a
page
that
basically
says:
hey
here's.
What
we're
going
to
send
over
to
the
servers
that
way.
There's
transparency
and
people
can
see
what
information
is
being
sent.
H
G
H
Located,
though,
when
you
turn
on
the
telemetry
module,
it's
underneath
reports.
B
H
Yeah,
it's
fine
for
right
now
we're
only
collecting
three
pieces
of
information,
but
as
it
gets,
bigger
it'd
probably
be
more
unwieldy
and
also,
as
we
start,
collecting
more
complex
types
of
information
right
now.
It's
just
like
php
version,
what
kind
of
database
you're
using
and
the
web
server
like
apache
or
nginx,
so
it's
really
limited
and
what
we're
doing
so
far.
H
But
if
we
were
to
start
collecting
lists
of
information
like
what
are
all
the
core
modules
you
have
enabled,
or
something
like
that,
then
showing
that
in
the
report
is
one
thing
but
then
showing
it
as
useful
information
on
backdrop.
Cms.Org
is
another
thing,
so
formatting
of
this
data
definitely
is
is
a
problem
yet
to
be
solved.
B
H
E
H
Is
probably
the
most
valuable
piece
of
information
we
could
collect?
I
know
I'm
always
interested
to
see
like
what
wordpress
is
doing,
and
sometimes
we
even
use
wordpress's
numbers
as
a
basis
for
our
decisions
about
what
to
do
with
backdrop.
E
B
And
phil
phil
rightfully
said
something
about
the.
What
is
it
called
the
module
that
collects
readiness
data
from
d7
that
maybe
we
should
be
collecting
this?
It
might
be
a
all
the
new
backdrop,
sites
that
have
been
created
or
ported
people
have
moved
them
into
servers
that
have
newer
versions
of
php,
but
there
might
be
existing
sites
on
php
5.6
and
we
will
these
seven
ones.
B
I
mean
that
that
are
you
know
about
to
decide
what
to
do
and
as
deciding
to
drop
support
or
whatever
might
be
a
blocker
for
them,
then,
having
that
data
from
these
seven
sites,
if
they
decide
to
install
that
status
update,
I
think
we
call
it
or
module.
B
Yes,
yeah,
but
that
could
be
a
follow-up
thing.
It
shouldn't
block
the
the
one
you
know,
I'm
mentioning
it
just
as
a
note
on
decisions
with
regards
to
php,
but
yeah.
We
have
a
lot
of
a
lot
of
issues
depending
on
decision
either
dropping
you
know
what
anything
below
5.6
or
dropping
support
for
that
in
our
tests,
or
something
like
that.
We
still
have
a
few
inches
here
and
there
it
would
make
it
would
help
a
lot
to
have
some
data.
G
Yeah
give
some
guidance
on
that.
I'm
going
to
go
back
to
real,
quick
on
on
the
telemetry
for
core
is
to
possibly
implement
a
granular
control
of
what
can
be
sent
over.
Maybe
there's
like,
as
opposed
to
it's
either
on
or
off,
maybe
allow
people
to
enable
just
php
and
apache,
but
they
don't
want
to
send
over
a
list
of
modules
or
something
of
that
nature.
So
it's
an
idea.
I
don't
know
what
kind
of
ramifications
that
would
bring
from
the
collecting
of
data
standpoint,
but
it
might.
G
H
Yeah
yeah,
we
had
an
implementation
that
actually
did
that
and
then
we
looked
at
it
and
we're
like.
H
That
and
we
yeah
like
tim,
is
suggesting.
We
decided-
let's
figure,
that
out
later,
because
there
was
not
only
data
questions
around
it,
but
also
the
implementation
was
like
leaving
croft
around,
especially
if
modules
were
adding
and
removing
things.
So
for
now
it's
just
an
all
or
nothing
turn
it
on
or
turn
it
off.
G
H
Yeah,
well,
we
have
one
more
thing
that
we
want
to
talk
about
we're
at
the
top
of
the
hour
and
I
have
personally
have
to
drop
off.
But
if
you
would
like
to
continue
tim
and
talk
about
the
results
of
the
survey,
that
would
be.
E
A
H
A
H
Okay,
I'm
gonna
hop
off
tim.
Please
continue
with
the.
H
The
survey
thanks.
A
A
There
we
go
so
I
have
the
survey
site
for
anybody.
Listening
to
this
who
isn't
familiar,
this
was
whipped
up.
The
idea
for
this
survey
was
whipped
up
pretty
quickly
and
meant
to
be
an
experiment.
Initially,
we
hadn't,
even
we
planned
to
keep
the
participation
fairly
restricted
as
a
test.
We
ended
up
broadcasting
it
fairly
broadly
that
anyone
could
participate
and
basically
ask
people
to
prioritize
their
issues
that
they
felt
strongly
about
we're
thinking
about
how
to
use
this
in
a
future
in
the
future.
A
But
right
now
I
think
the
main
thing
is
just
looking
at
like
what
came
out
on
top
one,
getting
some
some
feedback
on
if
there
were
any
surprises
to
people.
If
anybody
has
ideas
how
we
can
use
this
data
or
this
information,
the
assumption
going
into
this
is
that
this
isn't
a
vote
like
we're.
Not
the
results
aren't
binding
in
any
way.
It's
just
to
help
us
all
inform
our
our
prioritization
of
where
we
put
our
efforts.
A
A
B
B
Tuesday,
yep
cool,
so
my
expectation
was
that
this
will
be
a
heartbeat
of
that
would
help
first
of
all
developers
if
they
had
ran
out
of
ideas
on
what
feature
to
work
on
next
or
non-developers
on
what
to
advocate,
for
they
would
come
here
and
not
necessarily
pick
the
one
that
is
at
top
of
the
list.
But
you
know
some
like
one
of
the
three
three
top
ones.
I
guess
right,
so
it
wouldn't
be
a
source
of
decision.
B
It
wouldn't
be
a
source
of
absolute
decision,
I
should
say,
and
it
it
shouldn't
become
a
source
of
complaint
as
as
in
you
know,
we
have
a
hundred
votes
on
that
why
people
are
not
working
on
it
so,
and
that
should
be
made
clear
right,
but
I
would
like
eventually
to
link
to
this
survey
from
our
roadmap
page
and
call
people
to
sort
of
like
participate
more.
I
would
I
was
expecting
this
to
work
the
same
or
in
a
similar
fashion
as
it
would
the
petitions
work
for
classic
press.
B
In
other
words,
if
something
implements
gets
implemented.
Maybe
we
allow,
as
it
is
now
you
can
vote
for
as
many
or
as
little
as
you
want.
Maybe
we
could
make
it
so
that
each
person
has
ten
votes
or
five
votes
or
something
like
that
and
once
and
once
something
is
implemented,
then
they
they
get
refunded
the
vote
and
then
they
can
cast
another
vote
to
one
another.
Maybe
that
would
be
helpful,
but
these
are
just
ideas
and
all
that
implies
that
the
survey
stays
open,
always.
A
Sure
so
quickly,
I
think
that
there's
four
people
technically
on
this
call-
and
one
of
them,
I
think
actually
left-
is
just
windows
open.
So
it's
just
a
couple
of
us,
but
I
think
we
can
go
ahead
and
talk
for
a
few
minutes
about
this,
and
I
agree
with
most
of
what
you're
saying
I
I
disagree,
I'm
just
leaving
it
open
and-
and
I
and
we
can
start
this
discussion
now
and
finish
it
with
other
people
later.
A
A
B
Yeah,
sorry,
I
missed
it
and
now
my
my
my
opinion
is
not
going
to
count
or
whatever,
but
it's
just
appealing.
This
is
not
a
you
know.
The
other
thing
is
that
in
my
head,
as
this
evolves,
we
could
automate
it
so
that
once
a
feature
here
is
implemented,
an
email
goes
out
to
the
people
that
voted
and
says
hey.
The
thing
that
you
were
waiting
for
is
now
in
core:
go
and
test
it
or
even
before
it
goes
live
we
are
working
on
it.
B
A
F
A
You
I
get
it
okay.
I
have
to
do
this,
it's
partly
it's
because
I'm
sharing
the
screen,
so
my
right,
my
options
changed
I'll.
Just
I
mean
we're
not
going
to
decide
this
definitively
today.
My
last
comment
is:
isn't
I
theoretically,
I
like
everything
that
you're
saying
about
that
practically
I'm
skeptical
that
it'll
work
that
and
it
comes
a
little
bit
from
a
background
in
like
trying
to
do
online
engagement
stuff
in
the
past.
You
know
I
find
my
experience
has
always
been
that
short
time.
A
B
Regards
with
regards
to
their
effectiveness,
would
it
work
for
you
if
we
had
a
blog,
because
you're
talking
about
announcing
that
on
social
media
and
causing
people
to
come
right?
How
about
hey
guys
over
the
next
like
on
that
specific
date?
B
The
pmc
is
going
to
convene
and
we're
going
to
decide
on
that
that
and
that,
if
you
haven't,
voted
yet
just
go
and
cast
your
vote
because
we're
going
to
take
that
into
account
so
so
locking
the
survey
shouldn't
be
the
mechanism
that
draws
people
there,
because
after
that
decisions
may
be
made
that
that
was
the
point
right.
A
Well,
that's
part
of
the
point,
but
I
also
believe
gregory
that
80
percent
of
the
people
that
fill
out
the
survey
today
are
not
going
to
come
back
six
months
later,
but
their
opinions
may
not
be
the
same.
So
I
just
believe
that
the
data
will
become
less
valuable
because
it's
less
reflective,
like
my
opinion,
nine
months
from
now
will
be
different.
A
But
if
I
don't
come
back
and
share
that,
then
the
data
just
isn't
working
and
if
a
large
percentage
of
the
people
aren't
coming
back
and
updating
their
votes,
then
I
begin
to
take
the
survey
less
seriously
because
I
know
well.
This
is
it's
got
all
kinds
of
data
from
a
year
ago,
so
why
should
I
trust
it?
A
F
How
were
how
were
the
the
things
that
people
voted
on
added
all
the
issues?
How
were
they
added
to
the
survey.
A
Well,
not,
ideally,
this
time
it
was
added
by
me.
We
we
had
some
issues
about
like
in
the
last
release
cycle.
We
asked
people
what
their
priorities
were
for
core
development
in
the
issue
form
or
yeah
in
the
the
forum.
Excuse
me
forum.backdrop,
cms,
and
so
I
went
and
I
thought
I
took
all
the
suggestions
that
had
come
through
that
channel.
Then
I
also
just
sort
of
went
into
github
and
looked
for
the
future
requests
that
had
the
most
comments
and
I
added
some
of
them.
It
was.
A
Yes,
some
people
requested
them
over
zulu
and
people
could
add
them
themselves
and
probably
about
four
or
five
issues
got
added
by
participants.
So
we
closed
we
two
weeks
ago.
I
closed
it
for
new
ideas,
because
I
thought
it
doesn't
make
sense
to
collect
new
ideas
the
day
before
you
close
voting,
because
that
idea
won't
have
had
a
chance
to
get
voted
on.
So
we
closed
knew
why
you
know
new
ideas
was
open
for
about
two
weeks.
We
closed
that
and
then
we
allowed
another
two
weeks
for
people
to
adjust
their
votes.
C
A
A
Well,
we
yeah,
but
if
we
did
this
again,
that
process
would
not
be
replicated
do
something
different.
Yes,
first
of
all,
one
of
the
biggest
flaws
I
think
in
this
current
survey,
is
that
I
just
cut
and
paste
titles
from
github
issues
and
sometimes
cut
and
pasted
descriptions
from
github
issues,
and
I
feel
like
a
lot
of
people
that
just
came
to
the
survey
and
looked
at
these
issues
wouldn't
understand
them
or
they
wouldn't
mean
anything.
So
I
would
want
either
a
better
process
of
vetting
them.
Or
you
know
I
don't
know.
A
I
we
jen
and
I
looked
at
trying
to
do
a
json
feed
from
github,
where
we
just
automatically
pulled
in
like
all
of
the
feature,
requests
or
something.
But
frankly
I
don't
think
that's
good
either,
because
if
there's
too
many
choices
that
are
poorly
defined,
then
it's
hard.
I
almost
feel
like
a
group
of
people
should
like
curate
a
list
of
30
topics
or
something
and
then
maybe
allow
other.
You
know
like
allow
people
to
suggest
things
that
are
missing.
B
I
thought
that
it
would
be
a
cool
thing
to
add
to
our
regular
newsletter,
as
in
three
new
people
registered
and
voted
here's.
The
changes
see
how
the
the
thing
that
you
were
doing
over
a
zulu
channel
could
be
a
you
know.
This.
This
issue
went
two
places
up
or
new
votes
for
that
or
downloads
for
that,
or
things
like
that,
which
could
engage
things
but
yeah.
These
are
thoughts
and
ideas
of
how
this
would
work.
B
I
think
this
is
useful,
but
we
reached
the
you
know
across
the
10
minutes
that
we
said
we're
going
to
discuss
this.
Maybe
maybe
we
should
discuss
it
again
next
time.
A
I
I
mean
I
this
was
a
good
discussion.
I
would
like
to
ask
one
more
slightly
different
discussion
question,
which
is
you've
said
that
you
were
like
you
didn't
you,
weren't
necessarily
surprised,
and
I
like
the
question
I
would
ask
both
jason
and
you
and
and
phil,
if
you're
still
there
or
anybody
else
is
what's
sort
of
most
surprising.
A
So
maybe
it's
not
super
surprising,
but-
and
I
and
I
can
give
you
some
examples,
for
example,
for
me
and
jason
would
probably
not
agree
with
me,
but
I
thought,
like
adding
backdrop
and
migrate
core
would
be
much
more
popular
than
it
was
the
fact
that
it
sort
of
turned
out
as
low
on
the
survey
as
it
did
surprised
me
a
bit.
I
think
the
recipe
project
I
didn't
that
that
was
as
popular
as
it
was
was
a
little
bit
surprising,
although
I
like
it,
they
allow
multiple
fields,
file
fields.
B
I
think
I
think
that
the
when
it
comes
to
backup
and
migrate
is,
I
think,
it's
mostly
that
title
of
the
thing
how
it's
phrased.
So
if
people
are
aware
with
through
the
the
actual
issue
and
and
see
the
reasons
why
we're
running
it
and
how
we're
writing
it's
not
just
merging
the
module.
It's
often
in
a
in
a
process
where
we
request
people
to
do
a
backup
like
when
we
do
upgrades,
there's
a
step
where
we
say
we
have
a
big
notice,
a
big
fat
notice
and
we
say:
go
away
now.
B
Do
your
backups
and
then
come
again
to
complete
this
process
and
what
we're
trying
to
do
is
like
have
a
checkbox
there
and
say:
would
you
like
us
to
backup
things
for
you
now,
so
you
don't
have
to
go
away
and
then
return.
So
it's
no
disruption,
you're
in
standing
installing
or
updating
a
module,
just
a
thick
box
there,
which
backups
the
things,
and
we
tell
you,
here's
the
backup,
here's
the
link
to
the
backup
we
saved
it.
There
just
go
on
so
it's
hard
to
sort
of
like
put
that
into
a
title.
B
So
we
said
merge
backup
to
migrate
because
that's
what
it
actually
does
right,
but
people
might
think
oh
yeah
I
can.
I
can
install
that
it's
like
a
trip
module.
I
can
install
it.
So
it's
already
there
for
me,
so
I'm
not
going
to
cast
the
vote
because
I
can
already
use
it
right
if,
if
they
knew
what
kind
of
integration
we're
planning
for
ideally
to
have,
maybe
they
would
voice
more.
I
don't
know.
A
F
A
F
C
G
I
would
I
was,
I
guess
I
wasn't
really
surprised
by
field
group
the
the
recipe
I
I
will
say
the
recipe.
One
did
kind
of
surprise
me
a
little
bit.
References
doesn't
surprise
me
honestly.
I
can't
really.
F
I
I
will
say
like,
like
I
may
ask
this
question
early
on
and
I
feel
like
a
lot
of
the
stuff
is
very
like
developer
site
builder
centric,
there's
nothing.
There
was
only
one
thing
that
I
could
find
in
there
that
was
at
all
related
to
anything
like
better,
promoting
the
site,
marketing
or
or
performance,
or
anything
like
that.
F
Right,
well,
it
wasn't
even
seo
or
something
else.
That
was
the
only
thing
I
voted
for
so
but
yeah
I
mean
like
there
is
no
there's
nothing
like,
let's
make
backdrop
better
for
the
site
owner
in
general,
for
their
site
out
in
the
world.
This
everything
was
like:
let's
make
things
better
for
us,
so
we
can,
you
know,
do
our
job
easier
or
whatever.
A
Yeah,
well,
I
guess
so.
I
both
get
your
point
and
also
sort
of
I
mean.
The
intention
of
this
was
certainly
to
focus
on
core
development.
So
right,
like
which
issues
in
the
core
issue
queue.
You
know
we
should
focus
on
and
maybe
that's
you
know.
Maybe
that
shouldn't
be
the
focus
of
the
survey,
but
I
think
that's
the
way
we
set
it
up,
and
so
I.
A
B
Not
that
this
is
a
definitive
drive,
but
field
group
has
335
000
sites,
site
installs
and
usually
that's
a
big
drive
for
things
to
get
into
core.
Like
views
hey
same
case,
so
it
didn't
surprise
me:
okay,.
E
G
G
Maybe
that's
that's
a
way
that
we
can
kind
of
look
engage
on
where
focus
needs
to
be
driven
based
on
what
people
are
voting
for.
So
as
an
example,
it's
like
okay,
this
round,
people
really
want
the
site
builder
experience
to
be
better
once
people
kind
of
get
to
a
point
where
they
feel
like
that's
better,
that
it
doesn't
need
as
much
focus.
Well
now
I
need
my
content
editors.
You
know
I
I'm
going
to
vote
on
things
where
it's
going
to
make
my
content
editors
lives
easier.
G
So
I
think
that
that's
kind
of
an
interesting
subconscious,
metric
to
kind
of
gauge
and
take
a
look,
take
a
look
at
what
the
overall
community
is
needing
within
you
know,
within
their
environments
it
kind
of
shows
the
direction
you
know
what
direction
backdrop
is
going.
Are
they
going
in
the
right
direction
for
core?
Yes?
Why?
Because
people
are
now
wanting
or
not
on
core,
but
I
mean
in
the
site
builder
side,
you
know
things
are
moving
in
the
right
direction,
because
now
people
want
content,
editor
side.
G
A
But
if
we
were
to
start
with
the
idea
that
we're
going
to
survey
members
about
priorities,
I
think
the
survey
might
be
a
little
bit
more
nuanced
than
this,
and
it
might
you
know
we
might
ask
additional
questions
other
than
just
which
issues
are
most.
You
know
which
core
issues
so
there
could
be.
You
know
like.
Where
should
the
community
be
focusing
its
effort
and
and
it
could
be
outreach
right
for
you
know
promoting
itself
better,
it
could
be
the
site
builder
experience.
A
B
A
I
mean,
I
think,
maybe
the
most
important
discussion
to
have
about
this
survey
right
now
amongst
ourselves
is,
does
how
how
do
any
of
you
feel
like
seeing
the
results
is
going
to
affect
your
participation
in
the
project
at
all
or
your
priorities,
and
if
everybody
says
no,
then
then
we
may
be
wasting
our
time
personally.
E
A
Like
it's
been
a
little
bit
helpful
to
me,
I
mean
so:
I'm
not
gonna
go
run
out
and
work
on
field
group,
because
it's
the
top
issue,
but
mostly
I
mean
I
might
if
I
thought
like,
I
had
any
idea
how
to
help
with
that
issue.
I
don't
is
I
go
down
this
list.
The
first
thing
I
get
to
that
I
feel
like
I
could
contribute
to
is
the
recipe
project
type
it's
like.
That
is
something
partly
because
the
first
step
is
just
defining
what
it
is
like.
What
is
that?
A
That's
a
really
vague
thing
that,
but
I
feel
like
that
is
something
that
I
could
actually
contribute
to,
and
the
fact
that
it
did
so
well
in
the
survey
motivates
me
to
actually
work
on
it.
So
I
feel,
like
you
know
it's
it's
something
I
was
already
interested
in
working
on,
but
I
think
the
fact
that
it's
sort
of
the
top
thing
on
the
list
that
I
might
be
able
to
help
with
is
useful
for
me
to
know
and
might
keep
me
focused
a
bit.
G
G
G
A
Of
us
that
are
contributing
want
to
know
that
our
contribution
has
an
impact
right
and
if,
if
I'm
just
working
on
an
issue,
just
because
it's
important
to
me,
that's
one
thing.
But
if
I'm
working
on
an
issue-
and
I
know
that
it's
a
priority
for
others
in
the
community-
that's
a
different
thing
right
and
I'm
more
likely.
If
there's
two
issues
out
there,
that
interest
me
and
one
of
them
has
more
support
from
other
people.
A
Then
that's
where
I'm
going
to
put
my
effort,
and
that
was
for
me
the
only
practical
outcome
of
this
is
if
doc
willmott
is
like
finishes
his
current
issue
and
he's
trying
to
decide
what
to
work
on
next
and
he's
thinking
about
doing,
make
form
button,
sticky
or
adding
field
group
decor
he's
going
to
look
at
the
survey
and
say
well,
I
guess
I'll
choose
field
group
decor,
because
that's
what
other
people
care
about.
B
Exactly
also,
I
I'll
point
out
that
phil
you
went
to
the
other
exchange.
We
said
that
this
will
not
gonna
dictate
direction.
We
didn't
say
it's
not
gonna
affect
it
or
it's
not
gonna
be
done
right.
We
never
said
it's
not
gonna
be
done
or
it's
it's
gonna.
Take
too
long
to
be
done.
We
say
we'll
take
this
into
account
when
we
make
decisions
which
means
whatever
it.
A
Means,
but
we
you
know,
I
just
don't
see
how
we
can
enforce
it
right.
We
can't
we
can't
say
to
the
community.
I
think
it
would
be
discouraging
if
we
said
okay
now,
our
top
priority
is
as
a
community
to
get
field
group
in
core.
So
does
that
mean
everybody?
Who's
working
on
other
issues
is
working
on
the
wrong
thing.
Are
we
discouraging
them
right
and
we
don't
want
to
do
that.
B
Some
of
them
are
difficult
tasks
right
and
then
they
take
long
forms
to
work
on
and
they
might
go
for
the
easiest
task.
The
you
know
low
hanging
fruits
if.
A
So
how
do
we
use
this
in
any
kind
of
binding
way,
yeah.