►
From YouTube: Backdrop Weekly - Jan 21st, 2021
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
All
right
today
is
thursday
january
21st
2021,
and
this
is
our
weekly
developer
check-in
meeting.
We
have
a
couple
of
items
on
the
agenda
today
before
we
get
to
that.
Let's
go
through
and
start
updates
or
sorry
introductions.
A
B
C
Hi,
I'm
joseph
I'm
from
las
vegas
nevada
and
I
don't
know
I
haven't
really
done
much
the
last
two
weeks,
but
hopefully
this
week
I
can
finish
the
stuff
yeah.
D
Hi,
I'm
luke
mccormick
san
ramon,
california,
I
dived
in
and
did
a
bunch
of
things
right
at
the
end
related
to
118,
and
it
was
a
interesting
experience.
I'm
enthusiastic
to
to
kind
of
pick
up
the
momentum
and
do
things
like
that
into
the
future.
E
E
Hi
peter
from
australia,
I've
been
doing
lots
of
stuff
in
backdrop
lately
all
different
things,
but
particularly
interested
in
talking
about
some
documentation.
Proposals
later
so
yeah.
F
If
I
can
get
unmuted
here,
hey
phil,
ward
out
of
wichita
kansas,
I
don't
have
anything
specific
to
bring
up,
but
maybe
when
we
get
down
to
the
the
olympia
area,
then
I've
got
some
thoughts
on
that.
So
let's
go
have
you
gone
yet
jen.
G
I
haven't
yet
so
I'm
nate
lampton,
I'm
from
oakland,
california
and
yeah,
excited
about
the
118
release,
that's
out
and
in
the
wild
now
very
exciting
lots
of
sites
have
already
been
moving
on
to
it.
Let's
see
and
yeah,
I'm
excited
about
the
possibilities
for
the
next
version
right,
it's
time
for
blue
sky.
We
always
love
this
part
of
this
part
of
the
release,
planning
and
yeah.
I'm
happy
to
get
into
that
later,
and
I
think
last
up
is
justin.
B
A
Okay,
so
I
unmuted
and
muted
opposite
sorry.
Everyone
last
week
we
had
four
new
contributed
modules
provided,
link,
checker
web
form,
localization
slider
field
and
grid
field.
Formatter
grid
field
formatter
was
released
on
the
14th.
So
I
don't
remember
if
we
talked
about
that
during
our
last
week
or
not,
but
thank
you
everybody
for
working
on
kinship.
It's
exciting.
A
I'm
gonna
turn
over
to
nate.
To
talk
about
backdrop,
118.
G
Yeah
so
backdrop,
2018
came
out
six
days
ago
on
friday
of
last
week
january,
15th,
so
kind
of,
as
always
like
on
time
release.
We
again
had
no
problems
with
getting
the
release
out
as
scheduled,
I
might
say
this,
every
single
release,
but
I
love
our
release.
Cadence,
like
the
regularly
scheduledness
of
it,
the
predictability
of
it,
and
we.
C
G
To
it
once
again
here
for
this
release,
latest
release,
feature
freeze,
went
really
well
with
things
the
things
that
got
into
the
things
didn't,
but
we
had
a
very
minimal
number
of
changes
between
feature
freeze
and
the
actual
release.
So
far
from
what
I've
seen
in
issue
queue,
we
also
haven't
seen
any
regressions
with
the
new
features
that
were
introduced
so
yeah
we're
looking
really
good.
There
is
an
excellent
blog
post
on
backdrop.
Cms.Org
the
backdrop
118
released
is
the
title
of
it.
G
You
can
just
google
it
or
see
it
on
the
backdrop
homepage
and
thanks
again
to
luke,
who
is
here
in
this
meeting
for
authoring
that
post
and
tim
for
taking
several
of
the
screenshots
the
whole
blog
post
is
super
great
and
comprehensive
of
all.
C
G
Functionality
that
got
added
to
118.,
so
I
don't
have
more
to
say
about
118
other
than
maybe
let's
take
a
second
and
be
happy
about
that
so
yay.
Thank
you.
We
made
118
it's
out
there.
Thank
you
to
all
of
our
contributors
who
continue
to
make
backdrop
an
excellent
piece
of
software
and
all
of
those
here
who
have
been
critical
in
the
release
and
most
every
release
of
backdrop
to
date.
G
So,
let's
see
118
1
is
the
next
bug
fix
version
of
118
that
will
be
coming
out.
We
posted
a
security
announcement
earlier
today
about
118.1,
saying
that
its
release
is
going
to
be
happening
very
soon.
It's
not
this
week
but
wednesday,
the
27th
of
january.
G
We
are
scheduling
the
release
of
118.1,
which
is
roughly
in
line
with
our
pattern
of
making
a
new
minor
version
and
then
waiting
two
weeks
and
then
releasing
a
bug,
fix
version
that
addresses
any
regressions
or
anything
that
we
found
over
that
like
after
the
release.
G
The
reason
for
the
scheduling,
though,
and
the
reason
why
it's
a
security
release
is
because
the
pair
archive
tar
library,
which
is
a
library
that
backdrop
core
bundles,
had
a
security
release
earlier
this
week
and
drupal
also
released
a
security
release
yesterday
and
so
we're
intentionally
postponing
the
security
release
slightly
to
make
it
line
up
with
our
normal
cadence
of
waiting
two
weeks
after
a
minor
version.
G
Also
releasing
a
security
update
right
after
a
new
minor
version
comes
out,
can
cause
people
to
panic
because
they're
like
oh,
I
don't
have
time
to
test
things
and
the
security
risk
of
our
assessment
of
the
security
risk
is
fairly
low.
G
G
Just
the
user
interface
for
uploading,
because,
ironically,
maybe
not
ironically,
but
backdrop
core,
like
our
distribution
system-
is
entirely
built
upon
zip
files,
not
tar,
gz
files,
and
so
our
use
of
the
entire
tar
gz
library
is
much
less
than
that
of
drupal,
so
yeah.
In
a
way.
I
kind
of
wish
that
we
could
just
say
you
know,
let's
turn
that
library
off,
because
it's
now
caused
us.
G
What
like
two
three
security
issues
over
the
life
of
backdrop,
two
of
which
have
been
in
the
last
like
four
months
like
yeah,
so
the
targe
z
files
just
have
a
lot
more
complexity
than
zip
files
do
in
the
end
because
they
manage
things
like
sim
links
and
permissions
and
zip
files
just
don't
deal
with
those
things,
and
so
zip
files
are
also
handled
by
php.
G
Okay,
do
you
guys
have
any
questions
or
comments
on
118
one
or
the
security
release,
or
anything
like
that?.
A
I
do
so
there
are
seven
rtbc
issues
I
didn't
know
if
those
should
go
into
118.1
with
a
security
release
next
week
or
if
you
wanted
to
hold
off
of
those
until
whatever
release
comes
after
that,
so
I
left
them
in
the
118
milestone.
But
I
probably
should
kick
that
to
core
committers
to
make
that
decision.
G
Yeah,
in
most
cases,
we
don't
hold
off
on
fixes
for
security
releases,
like
our
none
of
our
security
releases
intentionally
have
been
security
only
because
frequently
we'll
have
a
whole
queue
of
fixes,
and
then
a
security
release
needs
to
happen
imminently
because
of
some
reason
or
another,
and
so
the
whole
queue
gets
pushed
out
all
at
the
same
time
with
the
security
release.
So
we
have
never
had
a
policy
of
making
security
releases
that
only
include
the
security
fix
solely
so
these
other
items
here.
G
Is
that
all
clear,
okay,
okay,
118.2
118.2,
which
I
know
is
a
little
bit
silly-
that
we're
now
talking
about
the
next
bug
fix
release?
But
these
are
the
issues
that
basically
got
carried
over
from
the
117
5
release.
I
think
it
was,
and
these
are
issues
that
are
not
imminently
ready
to
to
be
merged
in,
but
are
ones
that
we'd
like
to
bring
up
as
to
put
a
focus
on
them.
G
So
the
site,
getting
stuck
in
maintenance
mode,
has
been
a
bit
of
an
issue
for
a
while,
if
you
use
the
installer
module
or
sorry
if
you
use
the
update
functionality,
which
is
from
installer
module,
the
site
gets
stuck
in
maintenance
mode,
while
updating
modules,
and
you
need
to
turn
it
back
off
manually.
There
is
an
issue
there
that
is
in
needs.
Review.
Gregory
has
volunteered
to
review
it.
It's
been
a
while,
though,
that
this
issue
has
been
open
and
it
just
needs
some
eyeballs
reviewing
to
make
sure
that
works
as
expected.
G
Let's
see
next
up
php
notices
when
installing
modules
that
have
sub
modules,
I
haven't
had
an
opportunity
to
look
at
this
one.
Yet
so
the
issue
number
is
4640..
G
Oh
this
one
got
fixed,
so
we'll
take
this
one
off
the
list,
that's
in
117.5,
oh.
I
should
also
make
a
quick
note
saying
that
117.5
also
came
out
at
the
same
time
as
118,
0
and
118.
0
obviously
includes
all
of
the
fixes
from
117.5,
but
it
had
a
huge
number
of
fixes
in
it.
Jen.
Do
you
remember
how
many
items
there
were
in
117.5?
G
G
Okay,
next
up
is
this
issue
setting
throwing
a
warning
if
the
max
input,
vars
variable
php
variable
is
not
set
high
enough
issue.
38
24,
currently
still
not
getting
a
whole
lot
of
updates.
Here
recently,
oh
looks
like.
G
G
A
Sorry,
so
I
think
that
issue
is
fine
as
it
is,
but
right
now
on
the
like,
after,
for
example,
on
the
permissions
page
after
you
submit
the
form,
it
throws
multiple
errors,
because
the
error
gets
generated
on
the
process,
part
of
the
form
and
in
the
process,
part
of
the
form,
there's
no
actual
element
that
we
can
use
to
determine
whether
the
form
has
been
submitted
yet
or
not.
A
So
the
only
way
to
like
remove
messages
from
messages
is
to
pull
them
all
and
like
search
for
specific
strings,
and
so
I
got
a
little
bit
nervous
about
how
to
alter
the
messages
in
that
case.
So
I
don't
know,
I
would
like
core
committer
review
on
that.
To
make
sure
the
process
of
altering
messages
and
back
to
upset
messages
is
kosher.
In
that
scenario,.
G
G
Let's
see
and
then
last
up
on
the
list
that
we
have
on
the
agenda
is
language
names
not
translated
into
their
native
names
issue.
45
11
and
this
one
is,
has
a
pull
request
that
needs
review
real
sim.
Well,
relatively
simple
change
in
that
one
as
well
from
the
end
user
perspective
quite
simple,
but
those
are
all
the
items
that
we
have
pulled
out
for
118.2,
largely
because
we've
been
clearing
out
so
many
that
had
been
the
117.5
list
previously.
G
I
think
it
would
be
a
good
opportunity-
maybe
in
this
next
week,
for
us
to
go
through
these
ones
that
we
have
remaining,
because
some
of
these
we've
been
mentioning
for
months,
pull
in
some
new
ones
that
we
think
are
of
high
priority.
G
I
notice
like
one
of
the
ones
that
I'm
looking
through
the
list
here
that
are
tagged
once
sorry,
118,
two
and
joseph
has
an
issue
like
making
sure
backdrop
works
in
php
eight,
which
will
be
important
in
the
near
future,
any
other
items
that
we
think
we
should
start
bringing
up
on
or
giving
some
attention
to.
We
should
move
into
our
agenda
for
weekly
discussion.
G
Yeah,
so
preferably
it's
something
that's
been
milestone
already,
so
something
it's
in
the
118-2
milestone,
so
the
normal
process,
for
that
is
someone
tags
it
with
milestone
candidate
and
then
a
second
person
says
that
they
agree
and
then
then
they
add
the
milestone
to
the
issue,
and
anybody
can
actually
any
anybody
that
has
as
membership
to
the
backdrop
issues
repository,
which
is
we
try
to
be
inclusive
of
absolutely
everybody.
That
contributes
add
them
to
that
group.
G
Anybody
can
add
the
milestone,
but
the
process
of
following
the
tag
and
then
getting
getting
a
second
on.
It
is
the
process
that
we
usually
use
to
get
in
that
list.
Right.
Yeah.
Sorry,
that's
not
for
you.
I
know
you
know
that,
but
then
these
other
ones.
G
What
I
would
say
to
to
bring
them
up
is
that
you
can
either
post
in
zulip
before
the
meetings
like
in
the
weekly
meetings
channel
like
if
you
want
to
have
something
added
to
the
agenda
or
if
you
have
permission
to
view
the
agendas
or
edit.
The
agendas
then
add
it
to
the
bottom
of
the
agenda,
or
even
just
like
right
in
the
section.
If
it's
something
that's
of
interest
to
you,
okay,.
G
Yep
we
also
have
in
the
agendas
folder
that's
on
google
drive,
we
have
a
template
that
is
used,
so
not
sometimes
there
isn't
a
agenda
yet
for
the
next
week,
but
you
can
put
it
into
the
agenda
and
we
copy
the
agenda
before
each
meeting
to
make
the
next
meeting
notes
so
putting
in
the
template
is
also
completely
acceptable.
G
A
That
we
weren't
sure
if
it
was
going
to
be
able
to
get
in
as
a
bug
fix
or
not.
Is
it
the
remove.
G
All
right
we'll
move
on
okay,
so
119
119,
wow,
we're
really
moving
up
in
the
numbers,
so
119
will
be.
May
15
2021
with
feature
freeze
on
may
1st
subjects
change
as
we
approach
that
date,
but
the
only
items
that
we
have
in
the
119
milestone
right
now
are
items
that
got
carried
over
from
118,
and
so
that
includes
the
exposed
file
name
filter
for
the
media
library,
dialog
issue,
3293
lauren,
is
the
advocate
for
this.
G
I
don't
think
that
there's
been
progress
other
than
we
were
trying
to
see
if
we
could
get
it
in
for
118,
but
there
was
just
some
technical
challenges
that
we
have
yet
to
sort
out
that
there's
some
there's
some
real
problems
like
that.
We
need
to
figure
out
that
are
that
are
kind
of
hard
in
that
issue.
So
issue
3293
currently
still
needs
work.
G
Let's
see
advanced
caching
support
for
cash
tax
and
the
cash
max
age.
Header
issue
4127.
joseph
you
mentioned
at
the
beginning
of
the
meeting
that
you
hadn't
been
working
much
over
the
past
couple
weeks.
But
can
you
give
us
the
status
update
on
just
where
that
is
sitting
sure.
C
I
think
it's
mostly
done.
I
do
have
a
pull
request
up
on
that
issue.
If
people
want
to
go
look
at
the
changes
so
far,
there
are
some
issues
I've
been
dealing
with
some
bugs
involving
how
it
determines
if
something
should
be
cached
or
not.
Cached,
based
on
the
tags
that
I
haven't,
I
just
haven't
had
time
to
work
through
those
yet,
but
they
should
be
minor.
G
I'll,
well,
that's
great
thanks
for
filing
the
pull
request.
I
didn't
realize
that
there
was.
There
was
code
up
there
now
that'll
provide
an
opportunity
to
get
some
initial
feedback
on
on
the
overall
approach
right,
so
yeah.
C
G
C
Are
currently
failing
because
of
those
issues,
and
once
once
I
get
it
so
that
it's
actually
like
has
the
correct
settings,
because
the
the
class
itself
actually
has
quite
a
lot
of
settings
that
it
uses
to
handle
different
things
so
yeah,
just
once
I
get
those
fixed
it'll.
It
should
be
working
great.
G
And
next
up
jen,
you
have
this
issue.
4728
a
field
field
has
value
visibility,
condition
for
blocks.
G
Okay-
and
I
see
tim
putting
in
this,
this
issue,
which
was
super
close
for
one
night
for
118-
add
support
for
relationships
to
layout
contexts.
What's
the
issue
number
on
that
one
tim.
B
I'm
just
adding
it
2134.
and
that
doc
wilmot
has
is
advocating
for
it,
so
it
should
have
been
on
the
list.
G
Yeah
so,
let's
see
last,
we
checked
on
this
before
release.
It
was
on
feature
freeze
day,
actually
that
we
we're
trying
to
get
the
last
items
finished.
The
functionality
works
completely.
It
seems
to
be
doing
exactly
what
we
expect.
I
think
probably
the
the
the
biggest
hold
up
that
I
had
here
last
time
I
did
a
code
code
review.
Was
that
the
terminology?
G
Of
course
it's
terminology
right
on
things
needed
to
be
improved
slightly,
that
it
was
saying
things
like
user
from
node
and
that's
really
ambiguous
that
what
it's
really
talking
about
is
the
author
of
the
node
and
so
just
coming
up
with
terminology
there
for
those
labels
and
the
associated
class
name
as
well
should
should
be
aligned.
That
was
the
only
feedback
that
I
had
on
that
one.
G
Now
that
we
have
more
time,
I
also
have
a
feeling
that
we
might
raise
some
questions
about,
like
just
the
general
user
interface
like
now,
there's
a
lot
of
additional
items
when
you
add
a
context
that
there's
a
new
link
that
says,
add,
contextual
or
add
context
relationship
which
is
a
bit
wordy.
G
But
I
shouldn't
complain:
it's
totally
awesome
that
it's
there,
but
I
don't
know
it's
it's
a
it's
starting
to
bring
in
a
lot
of
the
power
and
flexibility
from
panels
into
layouts
and,
if
you
recall
the
ui
of
panels,
so
it's
always
catastrophic,
and
so
with
complexity
and
flexibility
comes
well
complicated.
F
And
throw
in
there
real
quick
on
that
with
the
contextual
filters,
that's
something
that
or
I'm
sorry
the
relationships.
I
always
saw
that
I
kind
of
understood
them.
I
watched
videos
on
them
and
I
never
really
needed
them
from
for
my
sides.
I'd
always
figure
out
workarounds,
because,
to
be
honest
with
you,
it
was
almost
so
over
the
top
that
I
was
scared
to
death
of
it,
and
so
whatever
we
can
do
in
that
fashion,
to
make
it
less
scary
would
be
highly
recommended.
F
A
Yeah,
this
is
one
of
those
things
that
I've
used
a
lot
in
panels
drupal
land,
but
it
was
on
very
complicated
sites
and
it
is
sort
of
more
advanced
feature
in
any
way
we
can
find
to
make
it
not
daunting
for
those
who
don't
need
it.
I
would
definitely
be
in
favor
of
but
yeah.
This
is
something
that
drupal
8
doesn't
have
like.
A
There's
no
way
to
do
any
of
this
in
drupal
8,
so
I
think
it'll
put
us
vastly
ahead
in
terms
of
like
feature
completeness,
if
you
would,
if
you
use
this
in
drupal,
7.
F
I
may
be,
I
actually
may
be
speaking
about
the
wrong
thing.
There
was
one
piece
that
I
would
use
the
snot
out
of,
and
it
may
be
relationships
of
what
we're
talking
about.
There
was
another
piece
where
you
had
to
put
in
a
node
of
like
an
existing
piece
of
content.
That's
the
one
that
I'm
talking
about
that.
Always
scared
me,
because
it's
like.
F
G
Yeah,
that's
kind
of
interesting
that
adding
a
context
like
for
a
fixed
node
is
something
something
that
we
already
have.
Am
I
making
that
up,
but
adding
adding
a
fixed
context
is
also
unusual,
but
that
feature
is
already
there,
but
adding
a
relationship
equally
unusual.
G
So
we
now
have
two
options
to
like
add
a
context
that
perhaps
both
of
them
are
kind
of.
Like
you
know,
maybe
we
should
hide
both
of
those
links
somewhere
in
the
user
interface
under
advanced
or
or
something
because
now,
there's
not
just
one
confusing
option.
There's
two
that
in
nine
out
of
10
situations
you
won't
be
using
in
the
first
place,
so
yeah.
F
F
G
Yeah
and
the
initial
pull
request
only
adds
one
out-of-box
relationship
and
that's
the
the
author
from
node,
which
is
probably
the
most
common
relationship.
But
because
we
don't
have.
A
A
So
I
would
recommend
us
doing
that
as
the
second
one,
not
right
now
after
we
get
this
in,
but
all
of
the
other
ones
are
dependent
on
other
relationships
that
aren't
in
core
yet
like
reference
fields
and
stuff,
and
those
can
come
either
as
part
of
the
contrib
module
that
maybe
eventually
goes
into
core
or
whenever
we
start
to
support
those
in
core
yep.
G
The
normal
process
for
119
items
is
that
you
have
something
that's
in
the
119
milestone
and
we
need
a
volunteer
to
say
that
they
will
be
an
advocate
for
a
particular
issue,
and
that
is
as
simple
as
editing.
The
issue
summary
putting
advocate
colon
your
handle
in
the
issue
summary,
and
that
makes
it
an
issue
that
has
an
advocate
and
then
we'll
start
talking
about
it
during
these
weekly
meetings.
G
G
Four
months
from
now,
and
usually
we
allocate
a
meeting
or
two
a
couple
weeks
after
the
release,
so
that
could
be
as
soon
as
next
week,
but
we
might
want
to
say,
like
february,
4th
as
being
the
first
meeting
where
we
start
throwing
out
ideas
and
we'll
kind
of
not
have
the
normal
meeting
and
we'll
just
talk
about
the
things
that
we're
excited
to
see
or
possibly
interested
in
in
developing
for
the
next
release
tim.
Do
you
have
some
suggestions?
I
know
you
you've
kind
of
been
our
event
organizer.
B
Yeah,
we
talked
a
little
bit
about
this
last
week
in
the
I
think
when
you
weren't
there
in
the
other
meeting
nate
or
in
the
last
couple
weeks
about
that
whole
planning
process
and
also
last
year
about
this
time
we
did
sort
of
a
year-end
or
your
goal
setting
for
the
year
meeting.
B
So
I
think
if
we
did
sort
of
a
brainstorming
of
new
features
for
1.18
or
9,
we
maybe
think
about
it
slightly
broader
and
brainstorm
like
what
would
we
like
to
see
over
the
course
of
the
next
year,
of
course,
some
of
which
could
be
1.19
I'd?
My
feeling
was
that
last
year
we
had
some
really
productive
meetings
and
sort
of
brainstorming.
B
I
mean
part
of
those
meetings
last
year,
weren't
just
features
they
were
just
like
process.
You
know
what
did
we
do
right
last
year?
What
do
we
want
to
do
better
this
year?
I
feel
like
we
had
some
really
good
discussions.
I
think
we
didn't
do
a
great
job
at
documenting,
like
what
the
next
steps
were
on
a
lot
of
it.
So
if
we
want
to
do
something
like
that
this
year,
I
would
say
we
try
to
like
have
some
sort
of
blog
post
or
final
report.
B
Does
anybody
else
remember
those
meetings
and
and
have
any
thoughts
on
what
whether
they
were
helpful.
A
A
As
project
as
a
whole,
I
like
the
idea
of
having
a
list
of
issues
for
the
pmc
to
review
before
we
have
that
meeting,
so
that
we're
not
just
pulling
things
out
of
thin
air.
We
have
something
concrete
to
look
at
and
then,
if
we
feel
like
there's
something
missing
from
that
list,
I
think
it
feels
like
an
easier
starting
point
than
like
what
do
we
want
for
backtrack,
which
is
sometimes
never
ending
right.
B
I
am
a
little
bit
hesitant
to
to
bring
this
up
right
now,
but
I
might
if
it's
okay,
so
I
have
I
mean
what
we
tend
to
do
is
brainstorm
lists
of
possible
future
ideas,
and
I
know
we've
talked
about
before
like
doing
some
kind
of
a
survey
to
see
like
actually
how
popular
the
different
ideas
are,
and
I
I
don't
know
that
there's
opposition
to
the
idea
of
doing
that
survey
and
it's
more
just
like
how
would
we
do
it
implement
it
and
can
I
share
my
screen.
B
Where
I
set
up
a
temporary
website
for
my
thought,
was
it'd
just
be
sort
of
a
temporary
thing.
B
It
would
require
that
to
people
to
participate
that
they
log
in
I'm
using
the
flag
module
so
that
everybody
can
just
sort
of
flag
the
ones
they
think
are
most
popular
and
I
feel
like
I
don't
know
it
might
be
an
interesting
one-time
experiment
to
just
sort
of
see
what
and-
and
you
know,
even
if
we
only
had,
in
my
view,
10
or
15
or
20
people-
maybe
some
of
the
core
members
of
the
the
most
active
people
in
the
community.
B
F
I
think
it's
a
great
idea.
I've
been
thinking
over
the
last
week
or
two
that
having
some
type
of
a
poll
on
backdrop,
the
the
backdrop
cms.org
of
being
able
to
get
in
front
of
the
people
who
are
not
on
the
back
end
channels,
they're
not
in
front
of
it
they're
not
in
front
of
sula
for
the
meetings,
but
you
know
they
are
active
on
the
website,
a
place
where
people
can
kind
of
know
that
hey.
F
B
I
think
this,
the
idea
of
surveying
users
comes
up
from
time
to
time,
and
I
think
it's
just
an
implementation
like
how
do
you
do
that
on
an
ongoing
basis?
That's
meaningful,
and
this
idea
is
limited
to
like
a
one-time,
two-week
thing
where
you
know
we
either.
You
know
you
know,
I
don't
know
how
broadly
we
promote
it,
but
the
idea
is
that
we
just
get
a
snapshot
of
like
during
the
next
two
weeks.
Give
us
as
much
input
on
what
the
most
popular
issues
are.
F
I
think
I
I
think,
as
opposed
to
go
ahead,
jen.
A
B
Yeah,
so
right
now,
I'm
not
so
great
at
like
apis,
so
I
manually
created
nodes
for
about
20
issues
that
have
been
brought.
I
basically
went
to.
We
did
an
issue
about
two
or
three
releases
ago.
We
did
a
what
new
issues
do
you
want
to
see
in
backdrop
cms,
and
we
had
a
bunch
of
people
post
their
favorite
issues,
and
I
mostly
took
these
from
that.
I
also
added
a
few
more.
Basically
anybody
could
there
is
a
submit,
a
feature
idea,
and
you
know
you
just
add
the
issue
number.
B
B
F
I
can
see
where
we
could
have
kind
of
an
ongoing
feature
request
type
of
deal,
but
then
you
know
maybe
one
that
deals
with
the
overall
for
the
year.
Another
one
that's
going
to
deal
with
the
next
milestone,
and
I
could
see
us
integrating
this
with
the
newsletter
where
you
know
right
now,
we're
talking
about
119
and
so
for
a
short
period
of
time.
Hey,
here's,
the
issues
that
we're
discussing
for
119
vote
on
them.
F
If
you
have
some
ideas
for
119
adam,
you
know,
and
then
the
voting
process
for
119
is
going
to
close
on
this
date,
but
send
that
out
as
a
newsletter.
You
know
before
each
one
of
those
milestones
just
get
in
front
of
the
people
that
aren't
normally
coming
in
to
check
this
stuff
out.
It's
kind
of
like
oh
hey.
Let's
go
see
what
they're
thinking
about
adding
and
oh
yeah.
I
want
to
vote
on
that
and
then
go
go
about
their
day
anyway.
Integrating
in
with
newsletter,
I
think,
would
be
beneficial.
B
B
A
G
Thanks
tim
yeah
before
we
close,
let's
also
go
over
initiative
updates.
So
telemetry
is
one
initiative
that
we're
moving
forward
on
tim
you're,
the
advocate
or
the
lead.
Excuse
me
for.
B
The
initiative
yep
and
the
there's
really
no
new
information
on
this
particular
initiative.
The
last
couple
weeks,
once
we
decided
it
wasn't
going
to
go
into
the
last
release.
I've
focused
on
other
things,
but
we'll
now
go
back
to
further
testing
and
updating
the
next
steps
to
get
this
in
the
next
release.
For
sure
I
think
we're
I
mean
I
think
we're
close
enough.
We
should
be
able
to.
G
Okay
and
yeah,
we'll
just
keep
cruising
along
here
theme
development
should
not
be
necessary
to
use
backdrop
or
they're
ready
to
wear
initiative.
Luke.
Can
you
give
us
an
update.
D
Sure
sure
we're
actually
in
in
in
the
final
stretches
as,
as
I
said,
said
last
week,
I've
I've
I've
got
a
terrible,
looking
but
functional
site
put
together
that
that
kind
of
does
does
the
the
intent
of
of
giving
away
to
test
themes
and
content
and
touch
on
on
some
other
interface
issues
together.
D
I'm
I'm
working
with,
with
tim,
to
kind
of
put
it
into
sort
of
a
a
place
where,
where
people
can
poke
at
it,
and
it's
almost
it
it's
kind
of
ready
to
be
poked,
I
I
I'm
going
to
be
looking
for
design
guidance
actually,
just
because
I
I
can
kind
of
you
know
realize
the
things
that
that
I
can
do,
but
I
probably
shouldn't
do
them
in
terms
of
interface.
C
D
D
D
Yeah
there
there's
an
initiatives
section
and,
and
within
that
area
it's
one
of
the
approved
initiatives
and
they'll
be
able
to
read
about
it.
There.
G
Thank
you,
okay,
yeah
and
last
up.
We
have
documentation
which
peter
has
been
working
on
this
past
weekend
proposed
an
issue
over.
In
the
backdrop
cms.org
issue,
issue
747,
but
yeah.
I
haven't
had
a
whole
lot
of
time
to
look
into
this,
but
I'd
love
to
hear
what
you're
thinking
is
peter
and
kind
of
where
you're
heading.
E
Yeah,
so
it
came
about
a
while
ago.
E
I
just
made
a
comment
in
an
issue
about
maybe
we
should
put
all
documentation
into
one
place,
which
is
effectively
a
docs.cms.org
site,
and
this
is
similar
to
how
other
websites
do
it
like
lando
github
tugboats,
such
as
the
logo,
like
docs
dot,
their
domain
like
a
separate
sub
domain
for
their
documentation
site,
and
the
reason
I
thought
of
that
is
because
currently
we
have
all
documentation
like
spread
out
between
two
sites,
the
api
site
and
the
backdrop
see
mr.log
site
and
even
on
the
backdrops
in
my
org
site,
it's
like
separated
between
the
developer
section
and
the
user
guide
and
like
different
places
even
in
the
menu.
E
So
it's
all
like
all
over
the
place,
and
I
thought
just
putting
it
all
into
one
place
where
it's
easy
to
find
everything.
It's
all
searchable.
It's
all.
You
can
see
it
in
one
place,
which
means
you
can
see
where
there
might
be
gaps,
sort
of
update
documentation
and
also
just
for
someone
to
be
able
to
go
to
one
place
and
just
sort
of
step
through,
like
a
book.
Page
type,
just
click
next.
Next:
here's
the
requirements
to
install
backdrop:
here's
how
you
install
it!
E
Here's
how
you
update
it's,
how
you
use
the
different
parts
of
backdrop,
all
that
sort
of
thing:
here's
how
to
contribute
all
the
stuff
in
one
place.
So
the
reason
I
brought
up
today
is
mainly
because
of
two
questions.
One
is:
can
this
just
be
an
issue
that
it's
in
the
I
think
like
drops?
He
has
to
look
to
you,
or
I
know
where
I
put
the
issue,
but
it's
in
one
of
the
cues.
Is
it
just
a
normal
issue
that
we
can
just
work
on
or
does
this
have
to
be
an
official?
E
What
do
you
call
it
initiative
where
the
pnc
has
to
vote
on
it?
We
have
to
wait
till
the
approved
time
to
start
working
on
it
all
that
sort
of
thing
and
then
secondly,
the
issue
of
the
domain
change,
because
we're
thinking
that
it
would
be
easiest
to
re-purpose
the
api
site
rather
than
set
up
a
whole
brand
new
website,
so
because,
if
api
site's
already
got
lots
of
documentation
on
there
and
that
can
just
change
from
api
dot
backdrop
to
docs.backdrop
a
few
urls
redirections
would
need
to
happen.
E
That
sort
of
thing,
but
that's
probably
the
whole
thing
that
would
just
need
the
pnc's
approval
before
we
go
ahead
with
that.
G
But
I
don't
think
that
anything
needs
to
be
necessarily
an
initiative
to
move
forward
on
things.
I
think,
just
as
long
as
we
know
which
direction
we're
going,
it
can
be
done.
But
that
said
that
documentation
is
already
an
initiative
that
we've
been
looking
for.
C
G
Some
momentum
around
that
we're
just
like
we
want
to
improve
documentation
generally,
is
already
an
initiative,
but
we
actually
haven't
been
really
sure
about
which
way
we
want
to
move
forward
on
it.
So
this
brainstorming,
even
putting
together
and
suggestion,
is
super
highly
appreciated
and
looks
like
it's
already
garnered
a
lot
of
feedback
from
various
people.
A
He
was
the
gonna,
be
the
documentation,
initiative,
lead
and
just
make
sure
he
wants
to
be
involved.
He
would
have
the
chance
to
be
because
I
don't
think
he's
seen
this
yet,
but
he.
A
F
Only
right
yeah
is
this,
for
the
presentation.
Is
this
something
that's
gonna
be
an
open
edit
kind
of
like
the
way,
I
think
drupal.
It
seems
like
they
kind
of
went
backwards
and
closed
a
lot
of
that
documentation.
E
Well,
this
so
my
this
is
why
I
think
it
doesn't
need
to
be
initiative,
or
does
it
be
just
an
initial
issue,
because
my
initial
idea
was
just
set
up.
The
documentation
website
in
this
case
convert
api
to
docs,
move
our
existing
documentation
from
backdrop
cms.org
to
the
new
docs
dot
backdrop
website,
and
then
that's
this
my
idea
effectively
done
once
that
happens
once
that's
done.
We
can
then
use
the
new
docs
repository
to
have
an
issue
here
where
people
can
ask
for
new
documentation,
fix
documentation,
maybe
make
feature
requests
for
all.
E
Let's
make
it
more
of
a
moderated
status
where
you
can
just
create
documentation
and
it
goes
into
a
queue
where
people
approve
it.
Then
it
gets
published.
So
anyone
can
do
it
and
we
can
discuss
all
that
stuff
there.
Once
this
we
have
a
dedicated
website
for
it,
but
it's.
My
initial
thing
was
like:
let's
just
sell
the
website
and
do
more
documentation
there
and
then,
after
that
we
can
work
out
what
we
want
to
have
with
that,
rather
than
trying
to
figure
that
all
out
now,
basically.
G
B
Okay,
okay,
okay,
so
if
we
want
to
talk
about
this
a
few
more
minutes,
we
can.
A
Yeah,
please
do
and
see
what
you
guys
think
and
if
you
can
write
a
summary,
an
issue
that'd
be
great.
A
B
Bye
hi
I'll
just
say
peter.
I
appreciate
the
work
you're
doing
I
just
to
me.
It's
such
a
big
issue
in
terms
of
like
what
what
which
direction
we
should
go
in
terms
of
where
to
how
is
it
and
what
the
workflow
is,
and
there
seem
to
be
a
lot
of
opinions
out
there
that
you
know
I'm
equally
convinced
either
way
makes
sense.
So
I'm
just
right
now
kind
of
listening
and
love
to
see
these.
B
These
questions
answered,
but
I
you
know
like
I,
I'm
not
ready
to
take
a
position
on
whether
or
not
combining
all
the
documents
on
one
side
is
a
good
idea
or
not.
I
just
sounds
like
a
good
idea,
but
then
you
know
jen
comes
back
and
says
you
know
that
that
they
deliberately
made
the
decision
not
to
do
that
before
and
I'm
like.
Oh
okay.
Well,
what
does.
E
Yeah
to
summarize
that
point
in
the
so
there
is
an
issue
for
this.
If
you
want
to
look
it
up,
it's
in
the
backdrop
cms.org
repo,
it
issues,
seven,
four,
seven
in
there
I've
put
in
the
proposal.
I've
I've
basically
gone
through
and
listed
all
the
documentation,
the
title
of
each
page
of
documentation
that
we
have
on
backdrop
cms.org
and
on
the
api
website.
I'll
put
it
all
in
there
and
then
I've
in
a
separate
comment.
E
Re-Listed
it
in
a
new
proposed
re-emerged
fashion,
and
I
was
my
initial
thought
was
to
put
everything
in
one
place
and
I
still
believe
that's
the
best
idea,
but
yeah
jen
did
bring
up
the
point
that
apparently
there
was
a
reason
that
they
separated
the
user
guide.
So
here's
how
to
use
the
admin
bar
he's,
how
to
create
a
node
or
something
that's
the
user
guide,
and
that
was
specifically
kept
separate
from
the
documentation
and
she
believes
that
that
would
be
best
kept
separate
from
everything
else.
E
So
there
is
that
debate
whether
we
put
the
user
guide
and
everything
else
on
the
one
side
or
whether
we
keep
the
user
guide
on
laptopscenis.org
and
everything
else
on
the
new
documentation
site.
If
it
does
get
it
pushed
through,
I'm
happy
to
leave
the
music
about
where
it
is,
and
then
we
can
revisit
that
later,
once
you've
seen
how
the
new
website
works,
but
yeah
still
believe.
E
So
that
that's
one
thing
that
needs
to
be
decided
but,
as
I
said,
we
can
remember
before
we
just
leave
it,
as
is
like
with
the
user
card
separate,
but
but
yeah
that
issue
seven.
Four,
seven
on
the
backdrops
you
messed
a
lot
of
repo,
has
all
the
thoughts
and
suggestions
and
and
stuff
where
people
can
make
comments
or
we'll
see,
what's
being
proposed
exactly
and
stuff
like
that.
E
B
So
yeah
to
nate's
point
about
the
pmc
involvement
like
it
probably
doesn't
need
to
be
involved
to
move
forward,
but
I
feel
like
you're
looking
for
that
because-
and
I
would
be
too
because
unless
there's
real
clear,
you
know
shared
direction.
You
don't
want
to
spend
time
a
lot
of
time
on
a
specific
idea.
If
the
community's
not
going
to
buy
into
it
and
like
having
the
pmc.
Take
a
position
would
give
you
some
clarity
about
like
yes,
it's
okay
to
move
in
this
direction
and.
E
Yeah,
it's
also
because
like
if
we
do
go
ahead
with
it,
I
mean
I'm
not
sure
how
best
to
do
it.
Yet,
whether
I
cloned
the
api
site
put
all
the
documentation
there
and
then
just
talk
with
justin
about
getting
that
updated
database
onto
the
server
or
whatever,
but
yeah.
If
there
is
stuff
about
updating
the
server
changing
domain
names
et
cetera,
and
I
thought
we
just
can't.
E
E
E
I
don't
know
how
it's
going
to
be
doing
like
an
automatic
migration
or
something,
but
if
I
take
a
copy
of
the
api
site
and
then
on
my
local
or
something
just
in
updating
its
database
with
all
the
new
stuff
and
getting
it
ready
to
push
live.
How
do
we
then
manage
the
existing
api
site?
Getting
updates
in
the
meantime,
with
this
one
happening
and
all
that
sort
of
things
I'm
not
sure
on
the
best
approach?
B
C
B
B
H
So
for
issue:
oh,
I
had
commented
a
little
while
ago
it's
in
a
different
queue.
H
B
H
And
now
I
put
it
into
so:
it's
for
the
7.4
upgrade
on
the
production
for
php
sure,
so
it
looks
like
it's.
It
was
depending
on
you
know,
issue
for
777,
which
has
been
resolved,
so
I
should
have
the
green
light
to
move
forward
on
it.
But
I
was
just
wondering
if
there
were
any
concerns
about
that
with
anybody
that
has
special
software
running
on
the
server.
H
B
Okay,
I
mean
I
doubt
I
have
any
objection,
I'm
looking
at
it
now
upgrade
ph
okay,
so
the
upgrade
php
the
7.4
x
on
the
production
house
and
you're
just
looking
to
see,
if
there's
any
objections
to
that
or
any
concerns
right,
yep,
okay,
peter
you
would
probably
of
the
people
here
the
most
likely
to
know.
If
that's
a
problem.
E
H
Well,
I've
been
testing,
you
know
backdrop
cms.org
on
my
workstation
and
it
looks
fine,
but
you
know
there's
other
code
that
I'm
not
aware
of
that
runs
right
certain
jobs
and
things.
So
I
was
kind
of
looking
to
feedback
to
see
if
anyone's
tested,
that
against
7-4
or
if
there's
any
you
know,
concerns
about
it
before
I
just
go
for.
B
E
B
E
Yeah,
I'm
not
sure
what
else
is
on
there
or
how
it
all
works,
and
whatever
you
probably
need
or
jeff
would
be
more
knowledgeable
about
that.
B
B
E
F
H
F
F
Okay,
so
have
you
looked
into,
I
know
like
with
cpanel
they've
got
ways
of
being
able
to
choose
different
versions
of
php
based
on
the
website
itself.
F
That
might
be,
I
don't
know
if
you've
got
that
ability
on
that
server,
but
that
might
be
something
to
look
into
and
then
that
way
you
could
come
in
and
say:
hey
backdrop.org,
you
know
or
backdrop
cms.org,
that's
fine.
We
can
go
ahead
and
upgrade
that
one,
but
the
api
site
yeah.
H
F
A
link
it's
on
digitalocean
and
honestly.
Most
of
this
is
pretty
much
over
my
head,
but
I
think
it
might
point
you
in
the
right
direction
of
what
I'm
thinking
on
this.
It
might
be
something
worth
looking
into,
and
I
don't
know
for
me
looking
at
it
it's
way
over
my
head
too
complicated.
I
wouldn't
mess
with
it,
but
somebody
that
knows
more
about
linux.
They
could
probably
look
at
and
go.
Oh
yeah.
H
B
Back
but
I
think,
if
you're,
if
you're
relatively
confident,
I
would
give
you
I
would
endorse
just
going
ahead.
But
if
you
want,
if
you
want
a
more
official
endorsement
from
nate
and
jen,
I
get
that.
H
E
You've
tested
and
that's
mostly
working
I'd,
say
just
do
it
and
then,
if
there
is
just
a
little
job
and
that's
the
only
problem,
everything
else
works
fine.
I
don't
think
it's
worth
reverting
just
for
that.
I
think
we'll
just
try
and
fix
it
there,
and
then
I
mean
yes,
it's
nice
to
get
nate
and
jen's
approval,
but
on
the
other
hand,
they're
not
the
backdrop
community.