►
From YouTube: Backdrop Weekly - June 18, 2020
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
Day
is
Thursday,
June,
18th
and
necessarily
in
meeting
director
of
CMS.
Before
we
get
to
the
agenda,
let's
have
everybody
go
around
with
some
instructions?
What's
your
name?
Where
are
you
from
and
if
you
have
something
fun
you
want
to
share
with
us
30
seconds
or
less,
that's
not
on
the
agenda
feel
free
to
go
ahead
and
do
that
Nate
you're
in
my
top
left.
Would
you
like
to
introduce
yourself
first
sure.
B
B
A
D
E
F
A
F
A
F
A
Okay
related
to
the
website,
I'm
not
really
excited
yesterday
about
replacing
all
of
our
master
branches
with
main
branches
and
I
deleted
the
master
branch
on
backdrop
CMS
to
orc,
which
accidentally
closed
everybody's
floor
requests,
so
I
wanted
to
publicly
apologize
for
doing
that.
I
have
reopened
all
the
florists
and
assign
them
to
the
new
main
branch
and
in
doing
so,
I
also
reviewed
most
of
them
and
merged
many
of
them.
So
apologies
to
everybody.
A
B
Okay,
well,
as
many
of
you
may
have
noticed,
there
was
a
release.
Yesterday,
116
two
came
out
a
coordinated
with
Drupal
as
a
security
release
to
button
down
a
cross-site
request,
forgery
issue
and
forms
API
that
affected
backdrop
and
every
version
of
Drupal,
so
that
came
out
just
yesterday.
It
did
also
include
a
dozen
other
small
fixes
and
yeah.
So
it's
nice
having
me
release
out
there.
The
up
streams
for
most
things
are
updated,
Pantheon
and
tugboats
and
I
know
Jeff
did
Oh
composer
as
well,
so
updates
getting
pushed
out
all
over
the
place.
B
C
B
Sorry
I
took
a
quick
look
at
it
too,
and
I
also
couldn't
immediately
figure
out
why
it
caused
the
problems
that
it
did,
but
it
clearly
caused
some
so
that
issue
38
79
is
just
reverted,
so
it
got
put
back
nice
work,
yep,
so
116
3.
We
still
have
a
pretty
healthy
queue
of
our
TBC
issues
that
we
won't
bring
kappa
gangster
the
same
as
last
week's,
but
we
cannot
remove
blocks
from
searching
layouts
issue.
44
20,
Sarika
BC,
making
views
strings
translatable.
Shield
4382
is
our
TBC.
B
Let's
see
I
say
there
are
others
but
they're,
not
all
nice.
This
list,
we
have
an
issue
that
is
rather
important
that
we
get
figured
out
that
there's
a
visual
regression
in
the
list
of
text
formats.
It's
issued
44,
oh
seven,
and
that's
just
that
when
you
look
at
the
list
of
text
formats
as
of
116
they're
not
displayed
in
the
right
weight
border,
they
are
saved
in
the
right
wait
order
and
their
use
is
the
right
way
order.
B
B
B
That's
in
there
goes
Ella
I
think
put
together
a
pull
request
that
fixes
the
pager
so
that
you
can
have
previous
page
index
page
lists
and
views
based
on
dates,
which
is
necessary
for
calendaring.
So
2766
is
the
pull
request,
they've
put
together
and
it
currently
needs
review,
and
then
it
goes
all
I
know
that
there
also
are
no
tests
currently
and
so
test
coverage.
There
is
also
needed.
B
Your
entire
code
base
and
the
idea
is
that
we
would
have
it
automatically
run
on
the
code
that
is
being
changed
and
so
issue.
32
13
is
a
long
open
issue
for
discussing
how
we
can
make
it
so
that
becomes
automated
to
happen
on
poor
requests.
So,
let's
see
is
this:
o
is
just
Jeffers
this
you
Jen,
that's
saying
you
started
looking
at
github
actions,
gab.
B
A
B
A
B
B
4441
remove
all
instance
of
blacklist
and
white
lists
from
core,
so
this
is
derived
or
related
to
or
spurred
on
by
black
lives
matter.
That's
happening
kind
of
globally
and
kind
of
related
to
Jen's
earlier
comment
about
removing
master
branches
and
renaming
them
to
Maine,
which
we
did
for
backdrop
schemas
org
I
was
just
trying
to
remove
all
like
racially
driven
or
historically
racially
driven
phrasing
and
technology
turn
take
terminology
from
our
code
base.
Jen.
Can
you
give
us
any
more
information
about
the
status
of
this
issue?
I.
A
B
B
A
B
It
also
wouldn't
hurt
to
proceed
with
this
a
little
bit
more
incrementally
like
there's
some
places
where
it
might
just
be
code
comments.
You
know,
I
know
other
places
where
it's
the
names
of
functions
and
so
and
and
even
worse,
there's
some
places
where
it's
configuration,
because
kind
of
easiest
functions
are
fairly
easy
to
wrap
and
then
configuration
starts
getting
a
little
complicated,
yeah.
A
B
Okay,
that's
a
great
issue
thanks
for
calling
that
I
see
that
the
discussion
in
there
is
also
great
that
it's
covering
other
terminology
and
other
places
as
well.
So,
if
you're
looking
for
an
interesting
discussion
and
Clearinghouse
on
racial
terms
used
in
various
ways
in
our
code
and
in
our
branch
names
and
such
that's
a
great
place
to
read
up
on
it,.
C
B
C
A
minor
thing
I
reopened,
2805
because
it
would
be
ed
mentioned
that
we
need
documentation,
so
I've
started
by
creating
a
change
record
for
it,
and
it's
currently
sitting
in
draft
I
hope
to
trick
that
a
beta,
a
quick
tour
a
little
bit
more
so
yeah.
If
you're
happy
with
it,
you
can
publish
it
and
then
maybe
we'll
follow
up
with
some
advanced
inspiration.
B
C
So
the
documentation
that
we
have
in
but
rope
chain
has
default.
The
main
side
is
not
fitting
in
my
opinion,
for
that,
because
it's
a
bit
develop
e
subject,
so
it
should
be
in
API
but
I'm,
not
sure
if
just
the
change
record
is
enough
or
if
we
should
have
something
more
elaborate.
It's
quite
nice
yeah.
B
It
looks
like
so
the
tweet
referred
to
you,
the
blog
post,
that
Jeff
wrote.
That
was
just
the
the
backdrop
CMS
one
sec,
medical
release,
Diana
so
yeah.
The
change
record
sounds
like
a
great
idea,
because
we
need
something
that
is
canonical.
You
know,
like
here's
the
place
to
talk
about
this
one
thing
and
I
think
the
change
record
would
be
a
great
place
to
include
that
you
tried.
C
B
B
A
C
B
B
B
Ux
things
that
happen
with
overridden
configuration
as
well
that
if
you're
looking
at
a
form,
it
shows
you
the
overridden
config.
You
know
what
it
is
that's
actually
reading,
but
when
you
save
it,
it
doesn't
actually
update.
What's
in
the
config
file,
it
leaves
what's
there
previously
and
so
yeah.
That's
a
definitely
deviation
from
the
way
the
Drupal
7
worked
with
variable
overrides
that
yeah.
A
B
B
Okay,
so
117
we
can
move
on
to
the
feature
releases.
117
will
be
the
next
minor
version
of
backdrop,
that'll
be
coming
out,
September
and
15th
with
feature
freeze
on
the
1st
of
September,
and
we
don't
have
a
whole
lot
of
items
queued
up
for
the
117
release.
Currently
we
still
have
Jen's
unofficial
issue
using
the
admin
theme,
login
pages
issue,
44:10.
B
A
A
C
Yeah
I
I
would
like
that.
So
don't
worry
about
just
I
haven't
I
haven't
been
around
the
queue
lately.
So
that's
why
it's
not
what
I
wanted
to
mention
that,
since
we
don't
have
a
lot
of
items
as
low-hanging
fruits,
I
would
like
to
get
those
out
of
the
way,
even
if
it
means
that
now
early
on
it's
just
like
pages.
B
A
A
B
A
B
Okay,
all
right
other
issues.
We
have
the
initiatives
that
are
currently
proceeding.
Jeff
Saren
deputy
is
the
leader
of
the
telemetry
telemetry
initiative.
He
posted
into
the
agenda
that
there's
no
progress
this
week,
thanks
Jeffrey
for
checking
in
there.
We
also
have
the
ready-to-wear
initiative
theme.
Development
should
not
be
necessary
to
use
backdrop
Luke.
Is
the
initiative
lead
on
that
which
I
think
you
guys
just
had
a
huge
brainstorming
call
just
before
this
one,
but
there's
anything
else.
You
guys
would
like
to
cover
today.
B
F
Yeah,
you
can
hear
me
I'm
successfully
unmuted.
Yes,
yes,
all
right,
good,
good!
All
right!
Well,
there's
definitely
process
issues
with
it.
I
I
thought
we
had
been
experimenting
with
different
places
to
to
sort
of
post
about
updates
and
get
discussions,
and
things
like
that.
Most
of
the
action
has
been
happening
in
Zulu,
but
but
there's
there's
feeling
bouncing
around
and
including
me.
I
agree
with
this
that
maybe
more
of
it
should
happen
on
on
github
or
the
forums
or
elsewhere.
So
I
I
wanted.
F
This
is
the
group
where
we
have
you
know
4400
github
issues.
So
that's
a
lot
of
experience
with
github,
oh
I'd
like
to
address
that
should
should
we
spin-off
should
I
spend
off,
should
it
be
spun
off
issues
for
each
like
piece
of
the
initiative
as
we
knock
off
things,
or
should
that
to
be
a
checkbox
within
a
big
issue?
Should
we
do
meta
issues
I'm
looking
for
for
github
help
here.
A
A
Or
just
some
documentation,
page
somewhere,
that
has
all
the
links
and
then,
when
we
figure
out
like
you
know
what
maybe
other
initiatives
are
doing,
we
might
end
up
with
a
better
process
where
we
can
manage
it.
But
since
all
of
the
initiative
stuff
is
currently
in
the
forum,
that's
where
I
would
start
all.
F
A
F
B
I'm
all
right.
Well,
no
look
on
the
flip
side
of
that.
Luke
I
think
that
a
meta
issue
that
bullet
lists
and
links
to
all
of
the
sub
issues
once
you
get
to
that
point,
would
also
be
useful
for
a
like
Clearing
House.
If
it
turns
into
a
you
know
it's
a
spider
of
several
issues
where
you
have
to
you
know:
go
through
these
seven
pull
requests
to
get
your
objective,
then
it
would
be
good
to
split
those
that
in
two
separate
issues
and
they
have
a
method
to
track
them
all.
F
Okay,
yeah
I
I.
Don't
think
it's
really
issues
so
much
as
steps
in
the
process
that
we're
we're
we're.
Looking
at
this
point,
but
I
I
think
it's
relatively
sequentially
method,
a
certain
parallelism
they
get
snare
of
of
you
can
do
things
figure
out
something
enough
to
like
move
to
the
next
step
without
having
it.
You
know
without
cabling,
discussion
on
that
thing,
so
I'm
thinking
a
certain
amount
of
threading.
F
A
B
This
happens
pretty
regularly
with
issues
that
affect
backdrop,
CMS
org
or
like
the
project
browser,
for
example,
like
the
project
browser
unfortunately
frequently
requires,
like
updates
to
core
to
project
module
and
to
backdrop
CMS
org,
so
it's
across
three
repos,
but
generally
speaking,
people
put
it.
In
the
main
backdrop,
issues
repository
that
the
meta
or
even
even
the
feature
request,
because
from
an
end
user
perspective,
they
don't
know
which
repositories
are
what
like,
like
you
say
like
finding
it.
So
any
meta
should
be
in
the
main
repository
so
that,
because
that's
kind
of
like.
F
F
F
There
there's
definitely
activity
there.
I
guess
see
the
others
start,
and
we
might
just
answer
this,
but,
but
others
are
having
is
how
do
we
make
sure
that
everybody
that
wants
to
be
involved
is
involved?
How
do
we?
How
do
we
get
things
and
I
think
the
answer
we
just
came
up
with
is
everyone
goes
to
the
forum
to
the
thing
and
if
they're
anywhere
else
will
direct
them
to
the
forum
to
make
sure
that
that
that's
the
source
of
truth,
at
least
for
the
moment,
all
right
do
I
interpret
that
correctly.
F
Yes,
thank
you
that
was,
it
was
definitely
something
that
came
up
and
ended
that
the
thought
was
all
right.
So
so
one
of
one
of
the
things
that
came
up
in
in
serve
as
we're
mucking
around
looking
for
solutions
is,
is
we
found
theme
collections
that
are
seemingly
kind
of
public,
but
we're
worried
about
the
license.
What
was
what
was
life?
Is
it
that
the
things
you
were
looking
at
or
under
beta.
F
B
Yeah
I'm
trying
to
find
there.
There
are
some
tools
out
there
that
are
licensed
compatibility
calculators
but,
let's
say
like:
if
something
is
this,
then
it
can
also
be
that,
for
example,
like
MIT
and
be
made
GPL
yeah
yeah,
but
it
gets
a
little
crazy
with
when
you
start
getting.
The
themes
like
because
like
Creative
Commons
is
about
like
attribution
like
it's,
not
really,
it's
not
like
a
legal
framework.
B
So
much
it's
not
it's
like
I,
don't
know
and
I
might
I
think
what
I'm
saying
is
that
themes
and
imagery
and
assets
have
a
different
fundamental
licensing
scheme
than
software
does
and
so
figuring
out
compatibility
between
those
two.
It
gets
a
little
trickier
so
but
I'm
sure
that
we're
not
the
first
people
to
encounter
this,
so
I
would
say:
let's
just
start
doing
some
homework
on
it.
B
C
And,
as
I
said,
I'm
not
sure
he's
joined
her
lip,
it's
not
the
last
time
that
we
had
a
discussion.
It
seems
like
at
least
that's
that's
what
I
recall
that
Kevin
was
sort
of
like
an
expert
on
this
matter
like
so
at
the
end
of
the
day,
we
can
just
think
him
and
say
I
so
like
what
are
your
thoughts
on
these
specific
license?
Oh
whatever,
if
it's
compatible,
if
you
can
spare
two
minutes.
E
F
F
Yeah
they're,
definitely
not
locked
out
and
proprietary,
so
we
can
use
them
for
inspiration
and
sort
of
discussion
and
then
when
it
gets
to
the
point,
if
we
want
to
actually
include
it
in
our
product
and
we
have
to
worry
about
compatible
licenses,
then
we
cross
that
bridge
at
that
point
and
and
figure
out.
If,
if
we
can
move
ahead
with
that
component
or
if
we
need
to
find
a
substitute
how's
that
done
yep.
B
B
B
So
that
raises
some
interesting
questions
because
we
still
distribute
under
GPL
version,
2
and
so
I
think
we
have
some
caveats
in
our
contributor
long
process.
That
say
you
can
have
a
GPL
version,
3
module,
so
you
can
choose
whether
to
be
a
2
or
3
when
you
make
a
module,
but
core
itself
is
still
2
and
so
I
don't
know
what
that
really
means
still.
B
C
Well,
just
a
bit
of
a
guidance
as
to
what
should
be
acceptable
as
an
MVP
for
3624,
the
dedicated
security
section
that
I
mentioned
so
there's
a
lot
of
thoughts
on
what
could
be
included
in
that
hides.
But
I
would
like
to
just
add
a
couple
of
things
and
get
something
done,
and
then
eventually
we
we
keep
adding
things
the
same
day
way
that
we've
done
with
the
dashboard
I.
C
C
That
one
at
least
was
been
like
that
as
d8,
so
much
comparability
as
in
parity,
whatever
we
call
it
so
yes,
the
whole
idea
is
that
we
have
a
dedicated
section,
especially
if
you
look
at
last
comment
that
I
have
there
there's
a
security
review
so
like
module,
which
sort
of
like
outlines
in
a
report
the
status
of
your
site,
so
that
the
system
administrators
can
say
I've
ticked.
All
these
ten
boxes
already
I
have
a
couple
of
things.
C
C
It
could
be
a
home
for
the
trusted
post
button
thingy
exposed
the
UI
as
well
as
all
the
things
in
the
future.
But
my
point
is
that
if
we
try
to
make
it
perfect
and
wait
for
all
these
things
to
be
ahead,
it's
gonna
take
forever.
So
I
was
thinking
of
just
getting
two
or
three
of
things
that
are
most
simple:
to
implement,
just
put
it
there
and
then
gradually
would
that
be
acceptable.
I.
C
B
B
B
That
maybe
we
don't
have
on
the
status
report
is
the
ability
to
skip
certain
things,
because
it
is
possible
in
some
situations
that
the
recommendations
that
are
provided
don't
apply
or
they're
not
even
possible
to
implement.
You
know
like
maybe,
if
you're
saying
change
the
permissions
on
stuff
and
feel
like
I
can't
do
that.
You
know
that
allowing
them
to
say
you
know,
suppress
or
ignore
or
whatever
to
like,
maybe
just
downgrade
it
from.
You
know,
warning
to
disable
there
so.
B
Because
if
we
have
a
comprehensive
set
of
all
of
the
best
practices
that
can
be
implemented,
not
all
best
practices
are
possible
in
all
situations,
and
so
I
think
security
review
probably
includes
some
things
that
are
best
practices,
but
not
required.
You
know
and
I
don't
think
that
we
need
to
be
throwing
you
know
we
don't
need
to
be
alarming
people
if
there's
things
that
they
could
be
doing
even
if
they're
not
required.
You
know
yeah.
C
Exactly
so
trusted
host
patterns,
for
example,
could
go
away
from
this
night
of
spades
and
into
that,
because
we
do
not
enforce
it.
The
way
that
it's
being
enforced
and
true
it's
just
that
we
didn't
have
any
other
place
at
the
point
where
we
introduced
that
setting.
We
just
had
this
not
Spence,
and
that's
why
we
put
yeah
so
yeah
do
not
unnecessarily
bother
people
with
warnings
in
the
status
report
when
there's
nothing
that
they
should
solve.
Like
specifically,
do.
B
B
But
it
would
also
be
nice
that
github
now
provides
the
ability
for
people
to
so
it
and
make
pull
requests
that
are
private
for
security
purposes.
And
this
is
kind
of
an
issue
that
we've
been
running
into
that
when
we
make
a
pull
request
against
court
or
when
we
have
a
security
related
pull
request.
We
have
to
run
it
against
core
publicly.
The
last
time
before
we
do
the
merge
to
make
sure
that
all
the
tests
pass
and
honestly
we
could
do
that
separately.
But
we
still
have
to
wait
for
the
tests
to
pass.
C
B
B
C
Sure
that
github
would
offer
that
but
I
get
told
at
least
there's
restrictions
around
merging
requests
like
it
requires
at
least
one
review
and
maybe
from
specific
people
as
well,
so
the
CIA
fails
or
if
the
CIA
fails
or
things
like
that,
like
you,
you
can
block
merging
cautious
about.
We
can
still
give
access
to
people,
but
the
mage
requests.