►
From YouTube: Backdrop Weekly - February 20th 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).
B
B
B
B
B
All
right,
I'm,
Jenn,
Lampton
I'm
here,
because
I
want
to
fix
a
lot
of
things
which
is
a
problem,
but
let's
roll
into
the
meeting
agenda.
First
on
here's
updates
for
the
project
management
committee.
We
have
our
first
real
time
meeting
next
week,
which
will
be
exciting.
We
get
to
sit
down
and
chat
with
everybody.
B
I
think
the
primary
focus
is
that
meeting
is
just
to
talk
about
how
the
PMC
is
working,
but
hopefully
we'll
get
some
good
high
level
feedback
out
of
there
that
we
can
debrief
everyone
else
with
after
we're
done,
contributed
project
update.
So
in
the
last
week
we
have
one
new
contributed
project.
It's
multi-select,
that's
been
on
my
list
for
a
while,
so
looking
forward
to
using
that
one
and
then
meet
Tim,
who
wants
to
take
over
initiative
updates.
B
C
C
But
next
steps
for
us
are
drafting
a
document
on
what
initiatives
actually
are
and
that
document
would
be
kind
of
official
documentation
and
describing
the
process
for
creating
initiatives.
Some
of
those
things
are
yet
to
be
decided
upon.
Once
we
have
that
draft
document
describing
what
initiatives
actually
are
and
a
process
that
it
includes,
we
need
the
PMC
to
actually
approve
this
official
process
change.
C
Once
we
have
this
new
document,
we
then
promote
the
initiatives
process,
probably
through
a
blog
post
and
then
promote
that
blog
post
or
tweets
blog
post,
of
course,
references
the
initial,
the
official
documentation,
and
then
we
start
collecting
initiatives.
So
initiatives
get
posted
forum.
We
need
to
decide
when
things
actually
go
to
vote,
but
then
initiative
would
go
to
vote
to
the
pmc,
who
would
then
possibly
approve
the
initiative
is
being
official
that
actually
does
not
have
quotes
it's
actually
just
official,
and
so
once
the
PMC
has
approved
an
initiative.
What
does
that
actually
mean?
C
So
now
there
there
is
an
initiative.
What
does
that
actually
do?
Well,
we'd
probably
create
in
a
meta
issue,
to
track
the
initiative
or
possibly
a
project
or
tag
we're
not
actually
sure.
Quite
yet
how
we'll
keep
track
of
all
of
the
issues
that
are
underneath
the
large
the
larger
initiative
and
also
on
backdrop,
CMS
org,
we're
planning
on
creating
a
content
type
to
list
initiatives
or
page
to
lists
initiatives.
C
Initiatives
also
will
be
either
listed
or
linked
from
the
main
road
map
page,
which
we
already
have
and
what
the
initiative
actually
what
it
all
means
like.
Why
do
we
even
have
these
initiatives
in
the
first
place,
the
benefits
include
that
the
initiative
leads
get
decision-making
authority.
There's
get
you
know,
assigned
basically
the
authority
to
guide
the
overall
direction
of
what
that
initiative
will?
C
What
direction
will
will
pursue
possibly
have
an
assigned
core
committer,
that's
responsible
for
reviewing
the
work
that
is
done
within
that
initiative.
Increased
publicity
around
the
objective
of
the
initiative,
including
you
know,
being
listed
on
the
roadmap
and
having
the
initiatives
page
having
a
project
on
github.
All
of
those
things
increase
publicity
for
all
of
them
and
then
periodic
review
during
weekly
me
at
least
once
per
release
cycle.
We
would
go
through
the
initiatives
and
talk
about
the
progress
on
them.
C
H
C
A
A
A
C
H
A
C
C
In
the
backdrop,
community
can
decide
to
become
an
advocate
for
a
particular
issue
and
advocated
issues
get
priority
as
far
as
weekly
review,
like
we
mentioned
during
these
weekly
meetings,
and
that
generally
makes
it
so
that
those
issues
are
given
priority
and
attention
and
reviewing
resources
because
we're
talking
about
them
all
the
time.
So
the
advocate
system,
which
is
currently
limited
to
only
advocating
for
a
single
issue
at
a
time,
so
it's
scope
is
kind
of
by
nature,
a
little
bit
smaller
and
less
ambitious.
C
We're
going
to
continue
doing
that
and
for
the
time
being,
that's
kind
of
the
way
that
our
116
features
are
going
to
be
prioritized
until
these
initiatives
come
fully
into
their
own
I.
Think
that's
so
anyway.
That
basically
means
that
our
roadmap
for
116
at
this
point
is
the
items
that
are
advocated
for
that.
Ricketts
are
usually
here
in
these
meetings,
and
that
also
means
that
those
issues
that
are
advocated
for
some
of
the
leftover
ones
from
115.
C
E
E
A
C
C
B
So
the
only
reason
I
wanted
to
bring
this
up
in
this
meeting
is
because
this
is
a
fatal
problem,
but
it's
also
cross
sport
from
Drupal,
7
and
so
I
wanted
to
figure
out
what
our
general
priority
of
things
should
be
like.
Is
it
okay?
B
If
we
commit
one
fix
to
fix
that
you
don't
fatal
error
now
and
then
go
back
and
do
all
of
the
cross
ports
of
commits
to
Drupal
7
or
if
you
want
to
kind
of
stick
to
the
process
of
like
do
all
the
ones
that
come
first,
first
and
just
kind
of
figure
out
our
method
for
handling
stuff.
That's
getting
attention
in
Drupal,
7
and
also
in
background.
C
So
I
know
that
this
has
happened
a
lot
with
vias
already
that
when
there's
something
that's
actually
breaking
or
even
just
something
that's
affecting
someone
in
the
backdrop
community,
they
make
an
issue
just
for
that
thing
and
we
cross
port
it
because
it
they
made
the
issue
and
they
submitted
a
pull
request.
And
so
it's
ready.
So
we
put
it
in.
And
that
means
that
when
we
go
and
make
those
big
lists
of,
let's
make
sure
that
we
got
every
single
patch.
H
C
It
does
take
some
extra
legwork,
but
the
the
person
creating
that
list
or
someone
subsequently
finds
the
related
issue
and
says
we
already
applied
that
fix
or
we
had
sometimes
what
happens
is
sometimes
there's
a
backdrop,
specific
approach
that
isn't
across
port
that
makes
that
feature
or
that
patch
not
apply
or
not
be
relevant
and
so
yeah.
We
we
proceed
just.
C
G
So
I
started
working
on
it.
There
was
some
discussion
before
I
started
about
what
we
could
do
and
the
primary
thing
that
was
mentioned
was
adding
a
timer
and
so
I
did
that.
But
then
I
noticed
that
there
were
a
couple
things
that
seemed
like
they
would
be
pretty
easy
to
do
to
make
tests
faster
through
the
eye.
G
G
G
Yes,
switching
it's
not
standard,
so
I
switched
it
to
testing
for
the
default
and
then
I've
been
going
through
fixing
up
tests
that
fail.
If
they
don't
have
the
standard
profile
because
they
only
like
if
they
only
depend
on
one
module.
I
can
just
add
that
one
module
to
the
setup
function
and
then
it
works
so
yeah.
C
I
am
that's,
that's
awesome,
first
of
all,
I,
but
I
I
would
worry
that
that
change,
switching
it
from
standards
to
to
testing
by
default
could
make
it
it
could
take
a
long
time
to
fix
all
the
tests,
so
I
might
encourage
you
to
do
is
separate
that
out
into
its
own
thing
and
maybe
even
separate
it
out
into
like
multiple
issues.
If
you're,
if
you
want
to
switch
individual
tests
over
okay.
C
C
Four
hours,
that's
amazing
well,
but
but
your
new
change
so
there's
a
caching
system.
That's
there
when
you
run
the
testing
through
the
command
line
and
it
doesn't
work
when
you're
in
the
user
interface
and
it
it
sounds
like
what
you're
saying
is
that
you
made
it
so
these
your
interface
now
uses
the
same
caching
system
as
the
command
line.
Yeah
yeah,
that's
awesome!
So
that's
that's
already
in
the
pull
request
that
you've
got
created.
G
G
C
I'll
also
add
that
converting
to
my
I
Sam
is
something
that
might
not
work
forever,
like
the
new
version
of
my
sequel,
for
example,
that
my
sequel,
eight
I,
think
that
my
I
Sam
copy
or
conversion
doesn't
work
anymore.
So
it's
it's
like
that's
an
awesome
optimization
for
now,
but
it's
also
not
very
compatible.
So
I
kind
of
think,
like
let's
put
that
aside,
especially
for
the
user
interface
cuz,
that
Maya
same
conversion
with
a
variety
of
people
that
are
running
this
locally,
might
not
be
very
reliable
in
the
long
term.
Right.
C
C
E
E
G
C
G
E
H
E
C
G
E
G
F
C
That's
awesome,
that's
exactly
what
we
were
saying
there
like.
If
we
knew
how
long
each
test
took,
then
we
would
find
the
ones
that
were
exceptionally
slow
and
there
you
go
awesome.
Yeah
again,
like
that's,
that's
super
awesome,
while
the
optimization
but
like
if
you,
if
we
get
that
what
we
have
in
then
that
allows
other
people
to
possibly
optimize
the
tests
as
well,
because
they'll
also
be
able
to
have
that
increased
visibility.
C
A
C
C
Okay,
let's
go
to
116.
So
116
is
the
next
to
minor
release
rolling
on
as
usual.
Here
it
will
be
released.
May
15th
with
feature
freeze
on
May
1st,
the
advocated
issues
that
we
have
of
those
representative
here,
we'll
start
with
BW
pandas
issue
base.
Slash
sub
installed
profiles,
issue
31,
74
Peter.
Can
you
kind
of
summarize
this
and
give
us
the
current
status
yep.
H
So
we've
installed
profiles
currently
H
installed
profile
is
its
own
thing
and
if,
for
example,
you're
a
developer
that
builds
all
your
sites
a
certain
way,
you
had
a
metrical
module
here,
and
you
know
something
you
want
to
make
that
from
the
standard
profile.
You
basically
have
to
clone
your
standard
profile
and
make
your
own
profile
based
on
that
we
do
n
changes.
E
H
For
example,
I
created
the
install
profile
for
the
backdrop
challenge
puzzle
things
I
made
last
month
ago
birthday
and
because
it
is
not
available,
you
ever
had
to
clone
the
standard
install
profile
and
then
make
my
changes
that,
whereas
once
this
gets
in
there
will
just
be
a
matter
of
putting
base
profile
because
standard
in
my
profile,
and
then
it
does
all
that
stuff
and
it
inherits
all
that's
like
it.
Just
basically
runs
all
that
stuff.
C
The
issue
over
in
31
74-
this
is
actually
the
first
I've
heard
of
it,
looks
like
other
people
have
kind
of
weighed
in
on
the
value
proposition
here
and
I'm,
probably
I'm
gonna,
say
I'm
gonna
have
to
read
that
issue,
but
I
see
other
people
are
like
I'm,
not
sure
about
this,
and
then
later
there
I
go
yeah.
That
seems
like
that.
That's
legit,
so
I'm
gonna
put
myself
in
that
camp
as
well.
It's
like,
let's
take
looking
and
read
over
it.
H
Yeah
I
think
it's
like
initially
I.
Think
other
people
don't
use
install
profiles,
don't
like
install
profiles.
It
probably
isn't
matter
much
but
I
think
if
we
can
do
more
of
this
clothing
to
make
it
more
automated
and
I
think
install
profiles
could
eventually
becomes
like
a
letter.
B
waking
build
sites
more
automatically.
C
E
Think
that
so
reviled
it
so
we
had
a
lot
of
discussions
and
at
some
point
we
discussed
this
last
week
actually
and
there
was
some
confusion
around
how
people
expect
it
to
work
or
what
people
were
expecting
out
of
it,
but
I
think
it
long.
So
we
have
so
luck
with
the
conclusion.
Now
that
you
have
a
rough
idea,
how
this
should
work,
we
just
need
to
flesh
around
it.
It
means
a
lot
of
testing,
that's
looking
I
Ament
it
tested,
and
the
Creelman
has
repeatedly
requested
for
a
review.
D
B
B
That
we
haven't
ever
run
into
before,
and
everybody
had
like
different,
like
internal
names
for
it
and
then,
when
we
tried
to
like
talk
and
I,
think
that's
a
lot
of
what's
happening
in
the
issue
queue
or
it's
like.
What
do
you
mean
by
active?
What
do
you
mean
by
current?
What
do
you
mean
by
published
and
it's
all
different
for
revisions
than
it
is
for
notes,
and
so
it's
really
hard
to
have
that
conversation,
so
I
think
it'll
be
good
if
we
can
figure
out
some
way
to
do
a
new
issue.
Summary.
B
That's
like
this
is
what
we're
expecting
and
then
because
documents
like
it's
no
point
in
fixing
bugs
if
I
don't
even
know
what
I'm
building
in
the
first
place,
so
I
think
like
just
documenting
what
we're
expecting
first
will
help
anyone
who
goes
to
test
it
and
be
like
are
we
test?
Does
the
thing
or
testing
match
what
our
expectations
are
and
I
have
I
had
intended
to
write
up
that
comment
last
week
and
didn't
get
to
it?
So
I
will
try
and
do
that
today,
I
opened
the
tab.
I
was.
A
Hurt,
let
me
just
I
I
had
a
similar
thought
that
we
really
need
to
do
that.
I
was
hoping.
Somebody
else
would,
but
thinking
I
would
try
if
no
one
else
did
and
I
have
a
dead
time.
I
was
personally.
If
I
did
it.
I
was
thinking
about
opening
a
Google
Doc
and
just
like
redrafting
the
the
problem
where
our
current
status.
H
A
B
E
The
confusion
was
around
with
the
current
directive
or
whatever
we
call
it
in
from
our
discussion.
Pretty
much
sounded
that
we
sort
of,
like
all
agreed
on
certain
things
like
the
published
thing,
is
a
state
that
respects
on
the
actual
norge,
not
on
the
revisions.
So
if
you
put
that
it
sounded
at
that
time,
when
we
were
discussing
that
that,
if
we
actually
put
down
that
down
in
words,
it
would
actually
be
a
pseudo
code
of
what
we
wanted
to
work
like
so.
B
B
E
Yeah,
so
with
mint
yeah
sorry,
this
has
been
delayed
a
lot
of
time,
so
I
was
meant
to
get
it
in
a
114
and
then
115
I
think
that
the
last
update
is
that
document
just
jumped
in
and
made
a
full
request
for
it,
which
is
based
off
of
Jenn's
last
four
requests,
so
just
needs
just
needs
to
be
reviewed
and
tested,
but
the
problem
there
was
that
we
had
it
working,
but
it
broke
the
way
that
filters
work
and
ckeditor.
So
we
need
to
make
sure
that
this
doesn't
happen.
This
time.
C
B
C
B
I
think
I
was
thinking.
It
wouldn't
be
a
116
milestone
if
we
had
initiatives
instead.
But
since
it
sounds
like
we're,
not
gonna
have
initiatives
for
this
time.
I
will
continue
to
advocate
for
it
for
the
next
release
and
see
if
I
can
put
my
focus
there
and
then,
when
we
do
have
initiative,
so
I'll
probably
remove
my
focus
if
it
doesn't
get
in
the
next
release,
I'm
happy
to
let
it
go.
Okay,.
C
Great,
let's
see
my
next
up
is
my
issue
issue
1992,
which
is
digital
signatures
on
packages.
This
has
been
stuck
for
quite
a
while
I'm
I
asked
you
Jen
that
question
because
I'm
thinking
about
it
myself
for
this
and
that
we've
been
churning
a
lot
on
this
issue
and
we
have
been
making
some
progress
but
but
I
also
a
lot
of
other
irons
in
the
fire
they're
kind
of
more
interesting
and
immediate
and
issues
also
just
in
general.
C
The
Drupal
can't
rib
auda
Matic
updates,
which
apparently
works
for
Drupal
7
and
an
Drupal
8
has
an
official
release
now
as
actually
being
functional,
I,
don't
really
know
what
it
looks
like
for
for
Drupal
core.
It's
not
really
relevant
for
us,
though,
but
the
point
is
is
that
we
have
a
Drupal
7
module
and
in
an
entire
approach
that
is
working
and
out
there
and
in
production
like
systems,
and
that
it
would
be
worth
taking
a
look
at
that
and
saying
what
it
is
that
we
can
learn
from
that
implementation
over
there.
C
So
obviously
they're
working
with
the
infrastructure
that
Drupal
already
has,
or
maybe
they
made
their
own
infrastructure
that
works
better
I'm,
not
entirely
sure,
because
there
seems
like
there's
some
things
like
we're
having
to
do
on
our
infrastructure
side,
to
make
this
better
and
more
secure
and
I
kind
of
wonder
if
they've
had
to
do
something
similar
so
anyway,
that
is
all
to
say,
issue
1982,
no
updates
on
this,
but
yeah
I'd,
like
us,
I'd
like
myself
to
take
a
look
at
reconsidering.
If
that's
that's
my
priority
for
116.
C
E
C
E
E
E
E
Before
we
move
on
just
on
the
tugboat
subject,
when
we
initially
launched
the
tugboat
demos,
I
I
asked
a
couple
of
colleagues
in
the
agency:
I
worked
for
it
just
tested
and
one
of
the
senior
engineers
as
a
joke
said
was
it
has
the
Installer
you
lost
me.
So
we
had
some
discussions
about
either
removing
the
Installer
step.
E
Or
if
people
want
to
test
the
Installer
bit,
then
we
have
some
sort
of
check
box
or
a
separate
time,
but
that
does
that
and
and
as
far
as
I
know,
simply
testing
used
to
do
the
same
things.
So
you
would
run
it
and
then
you
end
up
with
something
that
was
admin
and
admin
for
password
and
that
they'll
bill
I,
don't
know
what
your
feelings
that
I
think.
C
That
would
be
great.
We
we
did
it
the
way
that
it
is
right
now,
mostly
for
maintenance
issues,
that
if
we
imported
a
database,
then
we
would
need
to
maintain
the
database
dump
like
every
release
would
need
to
make
a
new
database
dump,
which
maybe
that's
not
a
whole
lot
of
work,
but
maybe
it
is,
but
I
think
it
would
be
better
if
you
were
able
to
log
in
II,
didn't
need
to
run
through
the
Installer
yeah.
C
So
the
the
method
for
testing
this,
if,
if
you
don't,
if
you're,
not
in
the
DevOps
group,
if
you're
in
the
DevOps
group
the
password
manager,
has
access
to
talk
about
in
it,
then
you
can
actually
log
into
it.
But
you
also
need
commit
access
to
the
backdrop.
Pop's
talked
about
group
anyway,
if
you
don't
have
any
of
those
things.
C
E
But
then
Tim
mentioned
that
the
initial
one
of
the
initial
goals
was
to
allow
people
to
easily
test
contributes
without
having
to
go
through
the
project
installer
at
the
same
way
that
simply
testing
us
as
in
select
the
module.
When
you
start
and
then
do
it.
That
way
like
launch
the
the
sandbox
with
the
tugboat
sandbox,
with
the
module
installed
I'm,
not
sure
that
sounds
a
little
bit
more
complicated
to
them.
C
C
But
you
can't
actually
tell
it
like
also
install
these
modules,
and
so
what
that
means
is
that
you
need
to
have
something
beforehand
that
runs
scripting
like
and
sets
up
a
new
repository
or
sets
up
a
new
sets
up
where
the
parameters
come
from
and
now
that
I
think
about
it.
That's
that
could
be
key
that
like,
if
you
could
put
the
parameter
somewhere
and
then
type.
C
H
C
C
E
The
way
that
seems
it
gets
me
worked,
it
was,
it
would
add,
parameters
in
the
URL.
So
if
we
had
a
way
that
we
add
the
parameters
it
back
to
the
button
that
we
click
and
that
persists,
if
these
parameters
I
mean
are
passed
on
to
the
Installer
like
their
Drupal
installer,
sorry,
the
backdrop
install
it
then
maybe,
but
that
sounds
that
we
need
to
do
work
on
on.
On
the
backdrop,
the
product
itself
to
accept
parameters
and
the
installer
of
what
to
do
after
the
installation
finishes.
E
C
H
C
The
installer-
and
that
might
mean
that
we
like
install
backdrop
well
back
to
app,
has
its
installed
shell
script,
which
would
be
the
easiest
way
to
do
that,
but
longer
term.
We
could
use
the
draw
extension
and
used
rush
to
install
backup,
and
then
you
stress
it
to
download
the
modules
and
that
would
yeah
all
work
towards
the
same
goal.
E
Sounds
like
anyway,
we
have
discussed
this
about
it.
Let's,
let's
focus
I'll
get
the
link
for
that.
We
are.
The
feeder
has
filed
two
year
to
review
and
then
what
we
just
discussed
sounds
a
little
bit
more
complicated,
so
maybe
we'll
put
it
on
the
side
for
for
now,
or
maybe
we
didn't,
one
of
us
can
test
it
out
when
they
have
time
and
maybe
let's
discuss
now,
Oh
actually
were
over
time
now.
C
Okay,
well,
let's
yeah,
let's,
let's
post
on
that,
how
to
surface
initiatives
like
how
we
organize
them
is
something
that
cuz
we're
a
long
way
from
actually
proving
any
initiative
at
this
point
so
yeah.
Let's
postpone
that
table
it
and
end.