►
From YouTube: Backdrop Weekly Meeting - March 25, 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
Hello:
everyone:
it
is
march
25th
2021,
and
this
is
the
weekly
backdrop
developer
meeting.
We
get
together
every
week
to
talk
about
the
backdrop,
project
and
development
tasks
that
are
before
us.
We
kick
things
off
with
little
introductions.
Every
week,
I'm
nate
lampton,
I'm
core
committer
in
oakland,
california.
Let's
go
to
tim.
B
C
Greg
I'm
greg
usually
in
australia,
but
now
I'm
joining
from
grace.
I
haven't
joined
the
last
one
or
two
weekly
meetings
so
trying
to
catch
up.
I've
been
through
all
the
discussions
in
zulip,
but
still
trying
to
catch
up
with
pull
requests
and
issues
in
the
queue
excited
about
the
release
that
we
just
had
and
passing
on
to
jen.
D
I
am
dan
lampton
joining
from
oakland
california,
where
I
am
uncomfortably
cold
today,
in
spite
of
it
looking
beautiful
outside,
and
I
am
excited
about
all
the
backdrop
work
I
have
going
on,
even
though
it's
making
my
eye
twitch
justin,.
E
A
Thanks
I'll
go
ahead
and
do
the
contributed
project
updates,
we
have
three
new
contrib
projects
that
were
released
this
past
week,
background
images,
formatter
utf-8
mb
for
helper
and
restricted
restrict
abusive
words,
so
those
are
three
new
conjured
projects
that
have
come
up
in
the
last
week.
A
A
So
that's
very
exciting.
118.2
included
a
large
number
of
bug
fixes
the
release,
notes,
detail
everything
that
was
in
there
some
exciting
things
that
we've
been
focusing
on.
As
of
late,
include,
accessibility,
improvements
and
118.2
includes
two
accessibility
improvements.
One
is
that
the
layouts
user
interface
is
now
navigateable
and
you
can
move
blocks
around
using
the
keyboard,
which
is
pretty
cool.
A
So
if
you
give
elements
focus
within
the
block
interface,
you
can
use
the
arrow
keys
to
move
blocks
up
and
down
within
a
region
or
left
and
right
to
move
them
across
regions,
and
it
works
really.
Well.
We
also
added
a
new
api
for
making
announcements
to
screen
readers.
So
four,
nine
eight
five
is
that
issue
and
that
has
also
been
merged
in
his
m118
two.
That
makes
it
so
that
anywhere,
you
have
an
event
that
occurs
that
you
would
like
to
inform
a
screen
reader.
A
What
it
is
that
has
just
happened,
such
as
the
blocks
user
interface,
that
having
that
keyboard
support.
We
now
have
this
api
available.
To
do
that,
however,
we
have
not
actually
implemented
those
two
features
together,
yet
so
there's
a
follow-up
issue
to
to
actually
make
it
so
that
the
blocks
ui,
which
is
now
navigateable
with
the
keyboard,
actually
announces
to
the
screen
reader.
A
That
a
change
has
occurred
because,
right
now,
when
you
move
a
block
around,
it
works
via
the
keyboard
and
we
have
the
api
available
to
announce
it,
but
we're
not
actually
announcing
anything.
Yet
we
went
ahead
and
proceeded
with
the
two
pieces
in
118.2
and
left
that
other
issue
as
follow-up.
Probably
we
will
need
to
have
a,
I
hope,
not
so
long
discussion
about
what
it
is
that
we
should
actually
be
saying
when
those
things
occur
right.
We
need
to
determine
the
terminology
of
those
announcements.
A
Also
in
118.2
we
fixed
one
of
the
major
bugs
that
we've
been
bringing
up
in
these
meetings
every
week,
which
is
an
issue
with
ck
editor
the
maximize
button.
Once
you
clicked
it,
it
would
disable
the
save
button
on
the
form
which
could
cause
content
loss
so
that
issue
4933
has
been
fixed
in
118.2.
A
A
That's
it
for
118.2
having
just
made
that
release
the
next
bug
fix
for
the
release
will
be
118.3.
So
all
issues
that
were
in
the
118.2
milestone
got
bumped
into
1183
and
some
issues
that
we're
still
working
through
include
php
eight
support
issue.
Four
seven
seven
two
this
continues
to
need
review
is
where
this
has
has
been
sitting
for
a
little
while
now
and
this
issue
regarding
menu
links
that
have
been
translated
issue.
Four
seven,
nine
eight
is
an
issue
that
currently
still
needs
tests.
A
C
I
would
like
to
mention
two
related
issues.
One
is
5007,
which
is
about
the
description
field
in
taxonomy
terms,
which
does
not
did
not
allow
images
to
be
uploaded.
C
You
can
only
select
from
the
library,
so
we
have
a
working
pr
there
and
then
a
an
issue
that
was
sort
of
like
is
a
follow-up
and
related
to
that
is
5016,
so
5016,
which
we
discovered
that
when
you
add
images
to
the
description
fields
in
taxonomy
terms
and
the
block
content
field
in
custom
blocks,
these
images
do
not
get
added
in
the
managed
files
sort
of
like
view,
and
they
don't
get
a
usage
count.
C
A
C
A
Something
about
that
that
that
I
thought
that
we
started
adding
file
usage.
I
thought
that's
what
we
did,
but
I
guess
I
guess
that's
still
an
issue,
so
I
think.
C
A
Yeah,
I
think
that
we
had
a
thing
with
custom
blocks,
so
usage
count
has
to
be
for
a
piece
of
content
and
so
with
blocks.
It
was
tricky
because
blocks
aren't
content
their
configuration,
and
so
we
don't
really
have
the
api
available
to
register
usage
for
a
block
right
now
we
do
have
the
api
available
to
register
usage
for
a
taxonomy
term,
though
so
that's
an
that's
an
oversight
but
blocks
yeah.
We
have
a
larger
problem
that
we
we
can't
even
register
a
usage
with
a
block
at
all,
because
it's
not
content.
C
So
indiegogo
suggested
that
we
should
split
those
issues
then,
should
I
make
it
through
separate
things,
one
for
descriptions
and
part
one
for
content
blocks,
because
it's
the
same
issue,
but
it
could
be
different
underlying
causes.
A
Yeah,
I
would,
I
would
actually
be
in
favor
of
using
5007
the
one
that
the
insert
image
dialogue
does
not
work
because
right
now
there
isn't
a
problem
with
text.
I
mean
taxonomy
terms,
don't
allow
you
to
insert
an
image
currently,
but
if
we
did
enable
that
it
would
have
the
temporary
problem
that
the
file
will
get
deleted
after
six
hours.
A
A
C
And
the
pull
request
is
just
one
line:
actually
adding
a
property
to
the
that
that
text
field
editor
uploads,
true
and
it
fixes
the
issue
so
that
that
itself
adds
a
tab
in
the
upload
dialog.
Sorry
in
the
image
insert
dialog
to
be
able
to
upload
images,
so
I
wouldn't,
if
that
is
an
actual
fix
and
it
doesn't
suffer
from
the
the
file
deletion.
Like
the
data
loss,
I
wouldn't
want
to
delay
it
in
order
to
fix
the
other
thing.
D
A
Yeah,
because
we
have
the
fix
that
we
have
in
blocks
it
where
we
would
normally
register
a
file
usage.
We
just
mark
the
file
permanent
because
we
don't
have
the
ability
to
configure
a
usage
for
a
block,
so
we've
already
addressed
it,
but
specifically
for
blocks
that
the
files
are
marked
permanent.
C
The
only
field
that
is
added
is,
I
think,
a
signature
field
and
what
you
call
it
user
images,
which
is
a
special
case.
It's
not
a
an
actual
field.
I
think.
C
We
have
them,
but
we
disable
them.
We
have
them
and
sorry
we
made
we
had
images
on
by
default
and
we
made
it
off
by
default,
so
it
both
of
these
settings
are
added
in
the
there's
two
check
boxes,
which
do
this
thing
in
the
user
profile.
The
same
the
same
place.
A
All
right,
yeah,
so
there's
lots
of
other
issues
in
183.
Do
you
guys
have
any
other
ones
that
you'd
like
to
bring
up.
A
Okay,
all
right.
Well,
that
brings
us
to
119.
119
will
be
the
next
minor
version
of
backdrop.
It
will
come
out.
May
15
2021
here
is
where,
as
we
approach
the
end
of
march,
we're
getting
into
that
period
of
time,
where
we'll
try
really
hard
to
complete
the
items
that
we
have
started.
A
A
A
Let's
see
next
up
is
advanced
caching,
adding
support
for
cash
tags
and
cash
maxage
issue
four
one:
two
seven
joseph
flatt
is
the
advocate
for
this
issue.
Herbduel
gave
it
a
code
review
and
provided
some
feedback
there,
but
we
still
get
to
actually
do
testing
on.
D
A
This
is,
I
mean
other
people
doing
doing
testing
out,
so
this
is
still
pending,
both
more
code
reviews
and
more
user
testing
on
issue.
Four
one
two
seven
next
up
is
ad
field,
has
value
visibility,
condition
issue
four
seven
two
eight
jen
lampton
is
the
advocate
for
this
one.
I
don't
believe
there
are
any
updates
this
week
from
the
queue
okay,
adding
support
for
relationships
to
layout
contexts,
issue
2134,
doc.
Wilmont
is
the
advocate
for
this
one.
He
re
re-rolled.
A
This
pull
request
about
10
days
ago,
and
it's
looking
great.
All
tests
are
passing.
He
made
changes
as
suggested
he
did
some
cleaning
up
here
and
there
and
now
this
issue
needs
review.
A
So
that's
great
moving
along
there
merging
the
different
update
pages
into
a
single
page,
listing
all
updates
for
modules,
themes
and
layouts
issue.
2714
gregory
is
the
advocate
for
this
issue.
C
We
still
have
no
updates,
although
indie
gazelle
has
been
chasing
me
for
weeks
now
to
just
get
back
on
the
issue.
I
keep
promising
that,
but
yeah
work
and
real
life
have
gotten
in
the
way
I
promise
to
get
it
right,
I'm
very
confident
that
it
will
get
in
for
the
next
119
release,
but
yeah
no
updates.
A
Awesome:
okay,
let's
see,
is
there
there
there's
a
pull
request
for
that
one
right.
C
Yes,
there
is
so
the
the
the
actual
bit
of
changing
the
merging
the
parts,
and
the
pages
is
solved.
The
only
problem
that
we
have
now
is
that
that
we
get
an
error
with
the
dashboard
block
and
the
the
reason
why
I
said
I'm
confident
is
because,
at
the
end
of
the
day,
if
I
don't
manage
to
sort
that
out
very
soon,
I
might
split
it
out
into
a
separate
issue.
A
That's
right,
I
remember
that
now
yeah,
okay,
well,
something
that
might
affect
your
work
there,
since
you're,
probably
moving
many
paths
around.
Is
this
next
issue,
which
is
add,
support
for
wild
cards
and
deprecated
path?
Redirects
issue
2833.
A
A
2833
fixes
that,
however,
that
means
that
everywhere
that
we
have
had
deprecated
redirects,
there's
now
a
new
way
of
doing
deprecated
redirects
the
old
way
still
works,
but
for
consistency,
there's
a
new
way
available
that
also
handles
wildcards
and
issue
2833
documents
that
old
and
new
approach-
and
there
is
already
a
change
log
record-
that's
published
to
the
docs
site
that
shows
what
the
old
and
what
the
new
looks
like
there.
A
Of
the
old
one,
but
it's
real
simple:
it
works
exactly
the
same
as
the
old
approach.
It's
just
that
now
it
handles
wild
cards.
It's
it's!
The
new
approach
is
wrapper
around
the
old
approach,
so
it
ultimately
is
pretty
much
the
same
thing.
A
Okay,
let's
see
and
prevent
urls
or
email
addresses
from
turning
into
links
issue
1926
this
one
was
also
merged.
Bw
panda
was
advocate
for
this
one,
and
there
is
now
just
a
real
simple
capability.
C
A
There
is
not
any
default
ui
for
doing
that.
However,
if
you
wanted
to,
you
could
add
a
seek
editor
style
for
no
link
and
then
like
select
a
section
of
text
and
then
say
no
link
on
it
and
it
would.
It
would
accomplish
that,
but
yeah
there's,
no
there's
no
user
interface
for
it.
However,
it
does
say
in
the
filter
tips
if
you
have
automatic
linking
turned
on
it
has
a
little
note
there
saying
if
you
add
no
no
link
to
a
class
wrapper
or
to
a
wrapper,
it
will
disable
that
file.
C
B
A
I
can
see
that
being
confusing
like
on
the
unlink
button
and
seek
editor,
possibly
disabling
automatic
links
yeah.
I
can't
even
recall
exactly
what
the
setup
is
out
of
the
box,
but
I've
had
a
slight
preference
for
disabling
auto
linking
everywhere
on
on
my
sites,
because
if
you
have
ck
editor,
it
auto
links
stuff
as
you
type
it.
So
if
it's
linked
in
seek
editor,
then
it's
it's
linked
in
the
output,
because
it's
literally
typed
or
generated
a
link
tag
on
the.
C
C
My
point
was
that
if
someone
just
gets
succeeded,
all
you
know
undesirable
links
and
then
they
edit
the
node
again
they
could
have
this
button
where
they
select
the
link.
Click
that
button
that
button
adds
the
no
link
tags
so
that
it
never
gets
added
as
a
link.
Again,
that's
where
I
was
getting
at
them.
A
Yeah
yeah,
and
it
could
also
be
confusing
that
the
use
of
that
filter
with
seek
editor
is
also
just
a
little
strange
because
yeah,
you
don't
see
a
link
on
the
input,
but
then
one
shows
up
on
the
output.
It's
a
little
confusing.
A
Okay,
so
that's
a
just
a
minor
bit
of
functionality
that
is
completed.
That
now
means
the
bw
panda
has
completed
two
issues
in
one
minor
release,
which
I
think
is
the
first
time.
That's
ever
happened
that
an
advocate
has
completed
multiple
issues
in
a
single
release
and
yeah.
A
Yeah
he's
primed
for
another
one,
and
we
don't
know
what
which
one
that
will
be.
Maybe
something
really
great
would
happen,
and
he
would
pick
up
one
of
the
other
ones
that
we've
already
started
all
right,
that's
it
for
the
119
update.
Do
you
guys
have
anything
else?
You
guys
would
like
to
mention
around
119
or
any
progress
in
the
queue?
A
Okay.
Well,
then,
next
up
we've
got
initiatives.
We
give
little
updates
every
week
on
larger
scale,
projects
that
might
span
multiple
releases,
two
issues
or
two
initiatives
that
are
going
on
right
now.
Our
documentation,
which
bw
panda
is
the
lead
on
documentation
mostly
has
to
do
with
improving
the
new
docs
website.
Docs.Backdrop
cms.org.
A
We
did
just
have
a
engaging
conversation
right
before
this
meeting
that
was
not
broadcast.
Unfortunately,
regarding
other
ways
that
documentation
could
be
improved
largely
through
video
content
tim
is
there
anything
that
kind
of
came
out
of
that
discussion
that
it
would
be
worth
repeating.
B
Sure
so
I'll
just
mention
that
sarvashri,
who
regularly
attends
our
outreach
meetings
and
has
been
advocating
for
a
long
time
for
more
videos,
instructional
videos
and
is
really
looking
for
developers
to
help
make
those.
So
if
you're
interested
in
a
developer,
that
knows
backdrop
and
interested
in
making
videos
reach
out
to
us.
But
I
I
think
sarajevo
and
I
are
going
to
go
ahead
and
try
to
start
doing
some
stuff
to
get
the
ball
rolling
and
then
maybe
do
some
more
outreach
later.
B
But
we
we
talked
today
about
just
in
case
anybody
has
feedback
on
this
about
using
the
leveraging
the
drupal
user
guide
for
drupal
8
as
a
as
a
model,
rather
than
recreating
something
completely
from
scratch,
and
so
people
have
feedback
on
whether
that's
a
good
or
a
bad
idea.
Let
us
know
basically,
starting
with
that:
it's
a
template
and
modifying
it
and
then
adding
some
videos.
C
Yeah
and
I
have
a
question-
I
think
that
that
what
I'm
about
to
ask,
I
think
that
last
time
it
was
sitting
with
jen.
So
when
we
moved
or
when
we,
we
wanted
to
merge
the
documentation
that
we
have
on
the
main
site
like
into
that
new
site.
But
there
was
an
issue
where
ck
editor
was
not
being
used
by
default
of
the
content
types
that
are
existing
in
the
api
side,
which
is
now
the
doc
site.
And
so
I
was
wondering
where
we
are
with
that.
If
there's
any
update.
C
A
Yeah,
I
know
that
the
doc
site,
since
I
just
wrote
a
change
log
on
it.
It
has
both
both
there's
two
text
formats
now,
one
that
has
seek
editor
on
it
and
one
that
does
not,
and
my
only
take
on
that
is
that
you
should
use
the
one
that
is
most
appropriate
for
the
content
that
you're
writing.
D
The
content's
all
there
bw
piano,
was
working
on
reorganizing
it
I
think,
via
book
or
menu,
or
something
to
make
it
match.
His
new
outline.
D
I
don't
know
you'll
have
to
ask
bwp
on
it
right
now.
Content
from
the
main
website
gets
pulled
over
every
12
hours,
so
if
anything
is
added
or
updated
on,
the
live
site
it'll
end
up
over
there,
but
that
also
means
that
any
changes
he's
making
like
if
he
changes
the
title
of
a
page.
It'll
get
overwritten
12
hours
later,
so
at
some
point,
we're
going
to
want
to
turn
that
off
because
he
wants
to
be
able
to
improve
things
as
well
as
just
move
them
around.
A
All
right
next
up
is
the
telemetry
initiative
collecting
information
about
the
way
backdrop
sites
are
actually
being
used
and
then
reporting
that
back
to
backdrop,
cms.org
tim
is
the
initiative.
Lead
no
update
this
week
is
what
is
in
the
agenda.
Thanks
tim.
C
B
This
a
few
weeks
ago,
I
haven't
looked
at
it
for
long
enough
that
I
need
to
just
kind
of
go
back
and
go
through.
I
mean
anybody
could
step
in
there
and
try
to
figure
out
what
the
next
steps
are.
I
believe
we
have
some
decisions
to
make
about
opt-in
opt-out,
but
until
somebody
defines
exactly
what
those
decisions
are,
we
can't
make
them
also,
there
is
some
more
code
work
that
has
to
be
done,
but
again
I
think
I
think,
having
somebody
and
I
keep
intending
to
do
it
and
not
get
into
it.
B
A
Yeah,
I
think
the
well.
This
is
actually
a
little
bit
confusing,
because
the
issue
that
we
have
right
now
it
looks
to
off
to
the
forum
from
the
agenda
yeah.
The
meta
issue
is
issue:
285.
A
wow,
that's
an
old
one,
but
that
that
gives
a
pretty
good
summary
of
exactly
where
we
are
right
now
and
it's
available
for
testing.
But
you
have
to
set
up
both
a
a
client
and
a
server
currently,
but
there
are
full
instructions
on
how
to
test
it.
In
that.
B
D
A
D
A
Time
changes
and
scheduled
meetings.
I
created
an
issue
779
in
the
backdrop
cms.org
issued
to
you,
which
is
kind
of
where
we
put
a
lot
of
things
that
maybe
aren't
exactly
related
to
the
website,
but
we've
been
having
a
problem
as
of
late
that
the
united
states
changed
its
daylight
savings
time
clocks,
but
the
rest
of
the
world
did
not,
and
that
resulted
in
some
confusion
there.
A
B
I'm
happy
to
to
do
it
sure.
So
the
the
problem
is
is
a
couple
fold
for
some
people
in
the
northern
hemisphere.
Their
clocks,
don't
change
at
the
same
time
that
others
do
in
the
us.
So
for
those
of
us
in
the
us.
It's
pretty
easy
to
know
when
the
next
meeting
is
even
after
the
clock
change.
If
you're
say
in
europe
where
the
clocks
change
at
a
different
point.
B
This
affects
you
differently,
like
first
of
all,
the
meetings
change
twice.
First,
they
change
an
hour
off
and
then
they
change
an
hour
back.
But
if
you
live
in
the
southern
hemisphere,
it's
even
worse
because
it
changes
twice,
but
it
changes
twice
in
the
same
direction.
So
for
peter.
The
meetings
will
eventually
shift
by
two
meet
two
hours
from
our
time
so
for
which,
for
him
is
pretty
dramatic.
B
And
so
the
proposal
is
to
have
a
universal
time,
which
would
be,
for
example,
utc
instead
of
basing
the
meeting
times
off
of
u.s
time
to
base
them
off
utc
and
then
they're
always
the
same
time
all
year
in
utc
and
for
places
that
don't
have
daylight
savings
time,
they'll,
never
check.
You
know
they'll,
always
stay
the
same
for
places
that
do
have
daylight
savings
time.
They
won't
sweat.
B
Right
it
will
the
point
at
which
it
changes
for
them
will
be
the
chain
time
that
everything
else
changes
right
now.
It
changes
in
u.s
daylight
savings
time.
Well,
if
you
live
in
germany
or
australia,
where
they
didn't
switch
the
clocks,
they
have
no
clue
that
daylight
savings
time
happened
in
the
us,
so
yeah
yeah
anyways.
This.
B
I
don't
nobody
has
disagreed
with
this.
So
far,
it's
just
a
question
of
how
to
make
this
decision,
and
I
don't
know
if
we
just
sort
of
assume
that
there's
enough
unanimity
and
make
it
because
we
could
do
this
and-
and
there
is
a
proposal
for
exactly
what
uct
time
we
use,
which
I
don't
know
if
it
measures
with
the
current
meeting,
I
think
it
actually
would
push
this
meeting
back
an
hour
for
us.
B
It
would
make
it
an
hour
later,
I
think,
is
the
current
proposal,
but
I'm
not
sure
somebody
please
fact
check
me.
B
B
And
there's
a
link
where
you
can
just
click
on
the
link
and
it'll
show
you
what
time
the
meeting
would
be
in
your
time
zone.
So.
B
I'm
totally
like
confused
right
now,
so
I'm
trying
to
get
to
there,
but
it
might
take
a
minute
if
somebody
beats
me
to
speak
up.
D
Yeah,
so
it
looks
like
it
for
california
time
anyway.
It
would
push
everything
one
hour
later
for
arizona
time.
It
would
probably
be
the
same.
B
D
B
D
B
So
I
think
that
he
probably
optimized
his
proposal
for
what
would
help
him,
which
I
think
is
totally
legit
given
right.
So
that's
why
I
would
sort
of
just
go
with
his
idea,
but
you
know
one
could
equally
argue
that
we
should
stick
with
our
current
time
and
then
shift.
D
E
B
A
B
Okay,
so
in
theory
we
we
changed
the
time
in
two
weeks,
but
we're
gonna
get
a
confirmation
from
peter
first
as
soon
as
possible,
and
if
anybody
else
has
any
strong
opinions
speak
now,
because
otherwise
we're
gonna
make
them
look
right.
C
Well,
that
time
affects
me
when
I'm
in
australia,
but
it
hasn't
due
to
cover
it
hasn't
been
done.
It's
not
going
to
be
done
for
another
six
months
at
least,
but
the
question
would
be:
would
that
make
peter
be
able
to
attend
the
meetings,
because,
even
if,
after
the
time
change,
he
still
cannot
attend,
then.
B
I
think
from
my
understanding,
first
of
all,
he
again
suggested
the
time
and
I
don't
think
by
any
means
it's
ideal
for
him,
but
I
think
that
starting
an
hour
later
would
be
better
for
him.
He
pretty
much
said
that
that
you
know
for
the
next
six
months.
He
won't
participate
at
all
if
we
stay
at
the
current
time,
and
so
I
think,
pushing
an
hour
later
would
be
helpful
to
him,
because.
C
Even
from
where
I
am,
I
work
aussie
nine
to
five
aussie,
prime
right
at
least
melbourne
and
sydney
time
previously
like
before
the
hour
change.
I
would
go,
do
the
two
meetings
and
then
straight
stop
work.
Now
I
do
the
two
meetings,
this
one
hour
gap
and
then
I
start
work
which
I
understand.
Why
peter
mentioned
that,
because
then
he
would
have
to
wake
up
really
early
in
the
morning
and
then
have
a
gap
right,
yeah.
A
Okay,
well,
I
think,
that's
all
that
we
have
for
the
agenda
today,
there's
a
little
aftertalk
discussion
as
well,
but
do
you
guys
have
anything
else
you'd
like
to
wrap
up
before
we
end
the
broadcast.
B
I
I
don't
want
to
talk
about
it
now,
but
because
I
mean
just
mention
it
so
people
are
aware
this
discussion
is
happening
if
they're
not
nate.
You
just
made
a
comment
about
how
issues
like
this
end
up.
In
the
backdrop,
dot
org
issue
queue,
and
we
do
have
an
active
discussion
about
that
right
now.
There
is
a
proposal
to
find
a
better
place
to
put
discussions
like
this
and
again
I
don't
want
to
debate
this
right
now.
At
the
moment.
B
It's
actually
there
are
multiple
different
proposals
out
there
and
it
is
a
an
opinionated
discussion,
but
we
should
at
least
let
people
know
what's
happening
and
it
looks
like
it
is
issue
number
which
is
at
778
in
the
backdrop.org
issue
queue.
So
if
you
have
opinions
on
that.
C
The
basic
discussion
is
either
a
different
repo
or
sorry,
certainly
a
different,
a
different
repo
that
doesn't
relate
to
the
site
tasks,
but
whether
that
repo
lives
in
the
same
group,
gitlab
group
or
a
separate
gitlab
group.
That's
the
main
sort
of
like
debate
that
we're
having
now
but
we're.
B
I
think
so
it's
the
difference
between
having
a
back
dot
dash,
ops,
slash,
community
and
community
is
just
an
example.
I
don't
know
exactly
what
it
would
be
called
or
there's
another
proposal,
which
was
we
open
up
a
whole
new
group
of
of
issue
cues,
which
would
be
like
backdrop
dash
community
instead
of
and
then
have
multiple
repos
there
yeah.
E
C
I'm
conscious
of
your
time
nate,
but
I've
added
a
point
there
about
the
ck
editor
for
thing,
and
I
think
that
you
are
the
most
appropriate
person
to
sort
of
like
timing.
C
With
regards
to
that,
I
don't
expect
us
to
have
a
solution
or
come
to
an
agreement
now,
but
maybe
we
can
bring
it
up
next
next
minute.
If
we
don't
have
it.
A
Yeah,
that
would
be
a
fun
discussion
to
have,
because
it
is
something
that
we
need
to
get
started
on
on
pretty
soon,
actually
considering
the
end
of
life.
A
seek
editor
for
is
going
to
be
an
issue
for
us
at
some
point.
C
Yeah,
the
demo
that
the
drupal
guys
organized
was
a
discussion
between
the
legs
of
the
initiative
on
the
drupal
end,
and
then
there
was
a
person
from
ck
editor.
I
watched
that
discussion
there
and
they
seem
to
be
accommodating
as
always
working
side
by
side
with
google.
So
there's
a
working
contrib
module
at
the
module
at
the
moment.
Sorry-
and
I
was
wondering
how
easy
that
would
be
to
be
backported
into
you-
know
backfill,
but
yeah.
A
Yeah
yeah-
I
don't
have
time
right
now
because
we're
at
the
top
of
the
hour
but
would
be
fun.
So
thanks
for
the
heads
up
and
we'll
add
it
to
the
agenda
for
next
week
and
yeah
in
the
meantime,
there's
an
issue
for
that.
Do
we
have
do
you
have
the
number
handy
by
chance
I'll.
C
C
A
Four
one:
two,
two
yep:
okay,
all
right!
Well,
I
think
that's
it
for
today.
Thank
you
for
joining
folks
today
and
everyone
that
listens
and
watches
these
broadcasts
afterwards,
thanks
for
sticking
with
us,
while
we
talk
about
scheduling
and
looking
up
issue
numbers,
so
all
right
thanks,
everybody.