►
From YouTube: 2022/03/03 - Weekly Dev Meeting
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's
march
3rd
2022-
and
this
is
the
weekly
backdrop
developer
call
we
get
together
every
week
to
talk
about
priorities
and
things
that
are
happening
in
the
world
of
backdrop.
Development
before
we
get
started
we'll
do
some
introductions
of
the
people
that
are
present
here
in
this
meeting.
My
name
is
nate
lampton,
I'm
quick
sketch
on
the
internet,
I'm
a
court
committer
for
backdrop,
and
I
am
coming
to
you
from
oakland,
california,
we'll
go
to
greg
and
then
tim.
B
Hi,
I'm
greg
I'm
joining
from
greece
generally
interested
to
help
in
any
way
that
I
can,
with
anything
related
to
the
backdrops,
nothing
new
or
exciting,
to
report.
A
Great
tim
and
then
joseph.
C
Him
erickson,
I'm
st
called
tim
and
deerwood
minnesota
and
just
real
busy,
promoting
and
organizing
drop.
A
Thanks
justin
and
then
finally,
wilbur.
G
Minneapolis
minnesota
and
I
run
the
weekly
backdrop
office
hours.
A
Thanks
robert
all
right,
that's
everyone.
Before
we
get
started
into
the
backdrop
core
recap:
we
like
to
do
a
rundown
on
new
contrib
projects
in
the
world
of
contrib
jen.
Do
you
have
the
the
new
modules
list.
F
Yep,
so
there's
a
lot
of
activity
this
last
week
as
well.
We
have
a
new
release
for
full
calendar
views
and
g
ng
usually
stands
for
next
generation.
So,
if
anyone's
interested
in
better
use,
support
for
full
calendar
there's
a
new
project
for
that
which
looks
pretty
great.
We
also
have
a
contrib
project
called
role
delegation,
one
chart
css
framework
and
the
full
calendar
library
module
which
probably
just
loads
the
full
calendar.
H
F
So
for
new
projects
this
week,
thank
you.
Everybody
who's,
contributing
to
work
on
continuing
to
contribute
on
contributed
projects.
A
All
right,
let's
see
so
for
today,
we
don't
have
a
lot
of
specific
topics.
So
the
one
item
that
was
raised-
oh
let's,
first
first,
the
big
news-
is
that
a
new
release
of
backdrop
came
out
yesterday.
There
was
a
security
release
that
includes
backdrop
122.3
and
one
21.6,
I
think
and
yeah
that
was
a
pretty
minor
release.
As
far
as
changes
are
concerned,
there's
only
two
commits
to
the
whole
release
versus
the
the
previous
version.
One
of
them
was
a
very
minor
fix.
A
As
just
a
note
about
our
processes,
when
we
make
releases,
we
have
a
big
to-do
checklist.
Every
time
we
make
a
release,
we
make
a
new
issue.
That
is
the
release
checklist
and
we
assign
out
obligations
for
like
who's
going
to
do
what,
after
the
release,
because
it's
not
just
making
the
release
that
we
need
to
decide
who's
going
to
be
doing
the
cutting
of
the
tag
and
making
the
release
notes.
A
We
also
need
to
do
things
like
update
the
home
page
and
update
all
of
the
backdrop
cms.org
sites
and
then
update
all
of
our
up
streams
like
pantheon
platform,
trying
to
think
of
other
ones.
There's
there's
lots
of
different
ones
that
we
need.
We
ourselves
need
to
manually
update
and
one
of
those
that
we've
kind
of
been
struggling
to
maintain
properly
is
the
docker
image
and
wilbur
raised
the
volunteered
or
asked
about
like
if
he
was
interested
in
volunteering?
How
would
he
maintain
that
and
let's
see
so
yeah,
I
think
jen.
A
F
That
is
example
of
what
our
checklist
would
look
like
for
security
release,
and
so
every
time
we
have
one
we
copy
this
template
into
an
issue
and
there's
a
whole
bunch
of
items
on
that
list
that
require
their
own
documentation
for
how
to
update
things
like
the
pantheon
upstream
or
the
docker
upstream
are
great
examples,
and
so
inside
that
same
directory,
where
we
track
the
issue
template,
we
also
have
the
documentation
on
how
to
make
all
of
those
updates,
and
so
I've
also
dropped
a
link
into
both
the
zoom
chat
and
the
zulub
chat
on
the
current
status
of
the
docker
documentation
and
wilbur.
F
You
might
find
in
the
docker
repository
different
documentation,
and
we
should
just
make
sure
that
whatever
is
the
most
accurate
appears
in
both
places
or
if
you
want
to
update
one
to
point
to
the
other
one.
So
we
don't
have
it
in
two
places.
That's
also
fine.
It
doesn't
matter
which
ones
which,
whichever
one
you
prefer
to
be
the
master,
is
fine
and
then
we'll
just
point
the
other
one
at
it.
F
But
yeah,
so
I
think
the
the
documentation
in
the
public
issue
queue
repository
is
probably
documentation
that
I
wrote
when
I
was
working
on
the
docker
image
a
very
long
time
ago,
and
it
could
be
that
the
documentation
in
the
docker
repository
in
backdrop,
ops,
is
more
up
to
date
and
feel
free
to
replace
mine
with
the
other.
If
you
need.
A
F
I
don't
know,
I
think
we
might
have
to
notify
the
docker
folks
that
he
is
an
authorized
maintainer
of
the
project
in
order
for
his
pull
requests
against
their
project
to
get
merged
reasonably
quickly.
We'll
have
to
check,
I
don't
know
also,
I
think,
on
our
repository.
He
needs
probably
to
be
given
commit
access.
If
that's
in
ops
and
not
in
contrib,
we
can
check.
A
Yeah
I'm
looking
over
the
readme
file
here.
It
looks
like
it's
merely
a
repository
in
backdrop.
Ops.
A
Interesting,
okay,
let's
see
wilbur,
do
you
think
you
need
any
more
information
on
that.
G
A
All
right,
let's
see
other
things,
let's
see
I'd
like
to
go
over
the
items
that
we
have
for
122..
That's
the
next
release
of
backdrop
that
will
be
coming
out.
A
May
15
2022,
there's
only
two
issues
that
we
have
any
status
updates
on,
first
of
which
is
the
add,
a
new
hidden
path,
content
type
decor,
which
also
modifies
the
home
page
of
backdrop
sites
quite
a
bit
with
the
display
of
some
new
card
content
on
the
home
page.
A
C
Oh
okay,
yeah,
so
the
we've
been
waiting
for
me
to
update
the
pr,
which
I
finally
did
a
few
days
ago
on
this
this
issue,
and
basically
I
mean
we
do
need
another
round
of
feedback
that
we've
added
some
icons
at
olaf's
suggestion,
based
on
the
feedback
in
the
in
the
issue
form
and
right
now,
I
want
to
be
clear:
olaf
is
doing
a
lot
of
the
work
in
terms
of
the
content
of
this
vr
and
I've
just
been
implementing
it.
C
He
also
revised
the
text
which
I
think
he
did
a
good
job
of,
but
we
could
use
some
other
eyes
on
the
text
to
see
what
people
think
of
it.
So
this
we're
just
using
views
now.
I
think
we
decided
we
had
to
do
that
at
least
for
the
time
being,
but
we
could
really
use
some
eyes
on
how
we've
configured
this.
I
there
was
a
bit
of
a
discussion
about
adding
a
an
image
style
for
this,
and
I
did
so.
C
I
also,
I
guess
I
have
some
questions
and
we
don't
have
to
answer
them
right
now
about
things
like
adding
an
image
style.
If
I
just
do
that,
if
it's
okay
to
just
do
that
has
been
fake.
I
know
in
the
past
nate
some
of
my
other
pull
requests.
C
C
C
Some
of
them
are
a
bit
tricky.
I
don't
know
that
I'm
going
to
be
able
to
fix
them,
so
I
could
use
help
there
in
particular
the
ones
that
are
troubling
me
right
now
in
terms
of
not
knowing
what
to
do
are
related
to
files,
and
I
think
that
the
tests
are
assuming
that
there
are
no
files
in
backdrop
when
it
launches,
and
we
in
this
pull
request,
we
actually
install
three
files
and
I
think
that
might
be
causing
some
problems.
C
So,
if
somebody
feels
like
they
could
help
me
figure
out
and
fix
those
tests.
A
Okay,
thanks
tim,
so
a
combination
of
general
code
review
checking
the
way
things
are
implemented
and.
A
Yeah
and
specifically
checking
the
install
profile
to
see
like
if
the
that's
the
best
approach,
great
okay,
let's
see
the
other
issue
that
we
have
that
is
trucking
along
is
issue
3992,
which
is
dropping
support
for
php
or
versions
prior
to
php.
5.6.
A
A
In
doing
that,
I
removed
all
up
all
things
that
referenced
versions
like
php,
5.4
or
5.3,
but
in
because
I'll
point
out
some
things
that,
like
possibly,
we
might
still
have
some
code.
That
is
specific
to
those
versions
that
we
could
potentially
remove
some
workarounds
that
we
have
there
so
that
that
still
kind
of
needs.
Review
plus
also
needs
a
little
bit
of
work
to
address
the
feedback
that
indicazeal
has
provided
already.
A
All
right:
well,
those
are
the
two
issues
that
we
have.
We
also
have
a
one
other
issue,
that's
in
the
122
milestone,
but
we
don't
have
any
updates
on
it,
so
I
won't
bring
it
back
up,
let's
see
other
than
well.
I
guess,
before
we
move
on
from
122,
I
guess
it
would
be
good
to
put
a
call
out
there
that
our
feature
list
for
122
is
still
really
quite
slim.
A
There's
only
three
open
issues
right
now
in
the
122
milestone
and
then
there's
one,
that's
already
been
fixed.
A
Robert
worked
to
add
this
feature,
for
if
there
are
multiple
copies
of
the
same
module,
then
the
status
report
now
tells
you
about
those
those
different
copies,
which
is
super
helpful,
but
yeah
just
putting
it
out
there
that
it
would
be
helpful
for
anyone,
that's
interested
in
trying
to
get
some
more
eyes
on
their
work
if
they
would
be
interested
in
marking
themselves
as
an
advocate
for
issues
and
getting
items
added
to
the
122
milestone.
A
The
process,
for
that
is
any
issue
that
you're
interested
in
edit,
the
summary
of
it
and
then
simply
put
advocate
colon
and
then
your
handle
at
the
bottom
of
the
issue
summary
and
then
tag
it
with
milestone
candidate
minor
and
then
someone
else
will
come
in
and
if
they
agree
that
that's
a
good
feature,
then
it
can
get
moved
into
the
122
milestone.
A
It
would
just
be
great
to
have
a
couple
more
things
in
there
and
we
don't
you
don't
even
need
to
commit
to
really
finishing
it
at
that
time.
It's
really
just
a
an
aspirational
like.
I
would
like
this
to
be
done
in
the
near
future
sort
of
thing,
and
you
don't
necessarily
need
to
be
a
developer
to
be
an
advocate
for
an
issue.
It's
merely
just
a
way
of
showing
that
something
is
important
to
someone,
and
that
makes
it
a
priority
for
the
rest
of
the
community.
A
Oh
they're,
all
my
that's
funny,
so
there's
lots
of
issues
that
are
marked
as
candidates,
but
don't
have
an
advocate,
yeah
great
great
suggestion,
peter
yeah,
let's
see
speaking
of
things
that
are
ready,
so
we
also
can
take
a
look
at
things
that
are
already
marked
in
the
bug
fix
milestone.
A
So
the
next
bug
fix
is
121.4,
since
we
just
came
out
with
124
121.3
yesterday,
there
are
no
issues
that
are
currently
closed
in
that
milestone,
however,
we
are
down
to
only
30
open
issues
in
that
milestone,
which
is
excellent
and
of
those
taking
a
quick
look
every
well
there's
only
one
of
them
that
doesn't
have
a
pull
request.
A
So
there's
29
issues
that
have
pull
requests
and
of
those
almost
all
of
them
are
in
a
state
of
needs
review.
So
so
we're
really
on
top
of
the
the
bug,
fix
queue,
and
that's
that's
really
excellent.
That
just
means
that
our
our
hang
up
as
usual
is
on
the
on
the
review
process,
but
not
to
knock
the
reviews
that
we've
been
getting
recently,
because
we've
we've
actually
just
been
doing
really
good
with
cleaning
up
and
like
getting
these
things.
A
Let's
see
and
that's
kind
of
all
we've
got
for
today,
because
we
didn't
have
any
topics
that
were
brought
up
through
the
forum
post
and
we
didn't
have
anything
else
that
was
specifically
raised.
We
don't
really
have
a
lot
of
topics
today,
tim
go
ahead.
C
C
I
I
Like
the
sorry,
the
release
notes
for
the
update,
but
I
think
that's
the
proper
way
to
do
it
is
to
create
a
separate
issue
for
that
library
itself
and
just
have
everyone
else
depend
on
it,
yeah,
which.
F
F
That's
that's
definitely
one
way
to
do
it.
I
think,
in
a
perfect
world
we
shouldn't
ever
have
any
modules
that
don't
do
anything
like
if
all
it
does
is
lump
in
a
library-
that's
not
ideal
now,
so
if
there
could
be
some
base
functionality
that
would
like
attach
it
as
a
view
display
or
something
like.
I
don't
know.
I
just
made
that
up,
but
something
that
that
module
does.
That
provides
the
library.
F
Then
we
could
have
that
be
like
this
is
the
module
that
adds
that
functionality
to
x
and
then,
if
you
have
other
modules
that
depend
on
that
module,
that
would
be
fine,
that's
not
always
the
case.
Sometimes
libraries
are
generic
enough
that
you
don't
want
the
base
feature,
and
you
only
want
the
sub
feature,
and
you
know
that's
the
world
we're
living
in.
F
I
think,
in
that
case
it's
totally
fine
to
have
a
module
that
doesn't
do
anything
other
than
include
a
library,
but
in
a
perfect
world
there
will
be
one
main
module
that
does
most
of
the
things
people
need,
plus
the
library
and
then
all
the
other
ones
would
just
extend
it
to
make
use
of
that
library.
E
Go
ahead,
robert!
Having
done
exactly
what
you
just
said
that
we
don't
do,
I'm
wondering
we
should
probably
document
that
somewhere
or
point
out
where,
if
it's
already
documented,
because
because
that's
what
I
thought
was
the
best
way
to
handle
a
library
that
might
be
used
by
multiple
places
and.
D
F
F
What
how
developers
feel
and
that's
how
drupal
sort
of
ended
up
in
the
state
that
it
was
in,
but
it's
a
less
than
ideal
experience
for
people
who
are
building
websites
but
like
oh,
I
wanna
whatever,
and
then
they
install
the
module
and
they're
like
it
doesn't
do
anything.
I
can't
see
what
it
do.
Where
do?
F
I
turn
it
on
where's,
the
page,
and
so,
if
we
can
have
it
provide
some
functionality
out
of
the
box,
it
would
at
least
be
clear
to
people
that
that
module
does
something-
and
I
I
know
there
are
instances
where
you
there
isn't
a
sensible
base
default
for
what
a
library
does
and
I
feel
like.
That's,
because
the
libraries
are.
D
F
And
I
think
you
know
in
many
cases
it's
totally
fine,
that's
just
the
world
we
live
in
and
we're
going
to
have
a
separate
one.
But
if
you,
if
there
is
a
scenario
where
you
feel
like
80
of
the
time,
people
who
use
this
library
are
going
to
want.
This
thing
bundle
it
into
a
module.
That
does
the
thing
and
then
every
other
module
can
depend
on
that.
F
F
You
wouldn't
have
to
install
two
modules
to
get
the
same
features
that
80
of
people
need.
You'd
only
need
it
in
one.
That's
not
always
going
to
happen,
sometimes
to
figuring
out
where
that
80
line
is,
is
arbitrary
and
so
joseph.
If
you
want
a
separate
module
for
everything,
it's
totally
fine,
you
can
do
that,
whatever
your
preference
is
as
a
developer.
Building
the
thing
is
better
than
not
building
a
thing,
but
in
general,
just
I
like
to
think
about
it
from
the
experience
of.
F
What's
it,
gonna
be
like
for
someone
who's
building
a
site.
Even
you
know
someone
like
me
who's
a
developer.
I'm
like!
Oh,
I
read
about
this
great
library
online
and
there's
a
module
for
backdrop
that
does
it
I'm
going
to
install
the
module
and
see
what
it
does
and
if
it
does
nothing,
it's
a
disappointing
experience.
D
D
F
D
B
I
like
it
as
well
and
the
the
thing
that
is
one
of
the
missing
links
there
is
that
dot
info
files
need
to
support,
and
we
do
have
an
issue
for
that,
specifically
the
recommends
or
enhances
which
actually
so
that
would
bridge
the
gap
of
yeah.
I
downloaded
the
library,
it
doesn't
do
anything,
and
I
know
that
the
readme
says.
Oh,
you
need
other
modules,
but
if
it
was
exposed
in
the
ui
somehow-
and
it
was
saying
yes,
you
need
one
of
these
modules
select
something
then
yeah.
F
Our
dependencies
go
the
other
way
like
a
module,
wouldn't
be
able
to
say
these
are
the
18
000
things
that
might
depend
on
me.
But
if
you
were
to
figure
out
that,
like
you,
don't
need
the
stripe
module,
you
need
the
stripe
web
4
module
in
order
to
get
stripe
on
your
web
form,
which
many
people
won't
get
there.
If
you
installed
stripe
web
form
and
you're
missing
stripe,
it
would
tell
you
hey
by
the
way
you
need
stripe,
but
most
people
are
like.
I
just
want
stripe.
F
Why
isn't
it
on
my
web
form?
And
so,
if
you
can
put
those
together
at
least
make
it
a
sub
module?
It's
a
lot
easier
for
people
to
deal
with
going
forward.
D
Could
we
have
some
kind
of
info
file
flag
for
like
api
and
then.
H
A
Sometimes,
the
way
in
which
the
library
can
be
used
is
just
there's
too
many
ways
to
actually
provide
a
lot
of
useful
functionality
in
the
base,
module
and
then
there's
other
ones
that
are
like
super
specific
where
it's
like.
You
might
have
stripe
web
form,
but
you
might
as
well
have
like
stripe,
uber,
cart
or
stripe.
Commerce,
and
you
don't
want
all
three
of
those
modules
to
be
in
one
package,
because
the
person
that
might
be
maintaining
the
stripe
module
might
only
use
one
of
those
three
and
not
be
an
adequate
maintainer
for
the
other.
A
D
A
D
F
F
D
Yeah,
so
we
could
have
a
flag
in
the
info
file
for
api
and,
if
you
we
can
put
something
if
that
exists,
we
can
put
something
in
the
ui,
because
we
already
have
a
module
that
downloads
lists
of
other
modules.
With
the
project
browser,
you
could
just
click
a
button
and
it
would
take
you
to
the
project
browser
and
show
you
all
the
things
that
depend
on
that
other
module,
because
we
already
have
all
the
data
for
this.
A
Oh,
that's
interesting
so
so
like
gregory
or
greg
had
mentioned,
like
a
recommends
flag
on
the
lower
level
module
but
you're
right
that
we
don't
actually
even
need
that,
because
we
can
automatically
generate
a
list
of
all
projects
that
depend
upon
another
project
because
we
already
have
all
of
the
other
ones
that
we
could
actually
make
a
list
automatically
of
other
projects
that
depend
on
one.
Only.
F
A
For
a
project
browser
right,
if
you
were,
if
you
looked
at
stripe
module
and
it's
like
here's-
you
know
54
other
modules.
I
don't
know
why.
I'm
thinking
that
there's
going
to
be
54
other
modules
that
depend
on
stripe,
but
you
know,
and
then
you
could
show
those
in
like
a
collapsed
field
set
or
something
like
that.
That
was
just
like
all
of
the
other
projects
that
depend
on
that
one.
It.
B
Doesn't
have
to
be
a
field
set,
even
you
can
you
can
use
the
project
browser
and
have
the
search
limit.
The
results
of
the
project
browser
on
what
modules
actually
depend
on
stripe.
So
it's
basically
click
this
link
here
to
show
you
a
list
in
the
project
browser
of
everything
that
can
be
used
with
this
module,
and
then
you
can
just
click
yep
install
this
this
and
that
follow
the
the
process
that
we
do
with
the
project
installer
and
actually
go.
A
A
Yeah
that
it
would
be
interesting,
I
I'm
a
little
hesitant
at
the
same
time,
the
it's.
It's
funny
that
the
more
capable
our
dependency
management
become.
The
more
dependencies
are
created,
it's
kind
of
like
adding
more
lanes
to
the
highway.
You
know
like
if
there's
more
infrastructure
people
will
use
it.
It's
not
that
bad.
A
It
can
be
because
in
a
way
jen
it
makes
it
so
that,
as
your
dependencies
become
more
complex,
they
also
become
more
granular
or
sorry,
as
as
your
infrastructure
becomes
more
sophisticated,
the
modules
become
more
granular
and
the
dependencies
start
becoming
smaller
and
smaller,
and
then
you
end.
A
Yeah
exactly,
and
so
so
literally
the.
I
think
this
is
a
key
thing.
Why?
One
of
the
reasons
why
wordpress
plugins
are
so
massive
and
comprehensive
and
drupal
modules
are
so
granular,
especially
these
days
where
it's
like
now,
it's
you
also
have
the
ability
to
have
not
just
modules,
but
you
know
php
library
dependencies.
You
end
up
with
this
massive
vendor
folder,
it's
just
it's
just
a
matter
of
like
wordpress,
doesn't
even
have
the
concept
of
a
dependency.
You
can't
specify
a
plug-in
depends
on
another
one.
A
I
mean
you
can,
but
only
in
a
readme
file,
there's
no
enforcement
of
it
at
all
in
the
user
interface
of
like
dependencies,
and
that's
that
the
lack
of
dependency
management
makes
it.
So
you
get
these
more
monolithic
modules
or
plugins
and
we're
kind
of
like
walking
a
line
here
where
the
more
capabilities
we
add
we'll
end
up
doing
the
same
thing,
where
we'll
get
more
more
granular
things
for
better
or
worse.
F
Okay,
so
let
me
guess
where
we
land
is:
we
should
have
some
documentation
somewhere
on
how
libraries
are
handled
in
backdrop,
regardless
of
what
that
is,
I
don't
think
we
have
that
specified.
F
From
how
it
would
be
in
drupal,
and
then
we
revisit
the
issue
about
support
for
more
stuff
in
info
files
and
then
later
on,
we
decide
if
we
want
to
include
that
in
project
browser,
but
with
reservation.
A
F
Just
to
make
sure
that
this
that
we
include
the
dependencies
lines
in
the
information
that
comes
in
the
feed
from
backup
cms.org-
it's
not
there
now,
but
it
would
need
to
be
there.
And
then
we
would
need
that
data
to
get
searched
on
when
you
put
in
the
search
term
on
the
installer
page,
so
that
it
would
find
like
everything
that
web
form
has
a
dependency
of
or
something.
A
A
It's
like
it
would
actually
be
like
recommended
projects
on
backdrop
cms.org,
but
the
packager
would
automatically
check
for
dependencies
and
if
it
had
one,
it
would
find
the
associated
project
and
then
add
itself
to
the
node
type
thing
right
now
we
don't
have
a
lot
of
manual
editing
on
the
nodes
that
are
on
backdrop
cms.org,
but
it
is
possible
for
administrators.
A
A
Yeah
yeah
there's
also
yeah,
there's
also
that
I
mean
yeah,
there's
no
scanning
of
dependencies
at
all
right
now,
yeah,
I
guess
actually
before
we
add,
recommends
it.
We
should
probably
handle
dependencies
first
right.
A
Right
yeah:
what
happens
right
now,
if
you
download
a
module
that
has
a
dependency
you,
you
download
it
in
project
browser,
and
then
you
just
can't
turn
it
on.
Is
that
what
ends
up
happening?
It
says.
F
B
Yes,
so
you
select
a
module
and
then
it
has
another
step:
it
downloads
the
module,
it
reads
the
info
file
and
then
it
says:
here's
a
list
of
other
dependencies
that
need
to
be
enabled
first
and
it
does
that
and
that
until
and
you
might
do
it
in
a
series
of
times
until
you
have
all
the
dependencies
required
for
that
specific
module
that
you
initially
sort
of
like
selected,
excellent.
A
Okay,
that
that's
perfect
and
I
actually
appreciate
the
download
one
at
a
time,
find
the
dependencies
there
and
then
ask
you
again,
because
it
really
makes
it
clear
exactly
how
much
stuff
you're
turning
on
and
also
because
that
a
module
can
include
like
sub
modules
or
a
project
can
include
sub
modules,
depending
on
which
ones
you
turn
on
the
list
of
dependencies
changes.
Yeah
yeah.
B
One
thing
that
happened
that
doesn't
happen,
and
I
think
it's
a
good
thing
that
it
doesn't
happen
is
that
the
the
dependencies
that
are
being
downloaded
is
for
the
initial
selection
of
modules
that
you
made.
So
if
there's
sub
modules
that
require
other
things,
the
final
list
of
modules
and
sub
modules
that
you
get
might
have
some
modules
that
do
not
have
any
met
dependencies.
B
In
this
case,
the
checkboxes
are
going
to
be
disabled
and
then
you're
going
to
have
to
sense
for
them
and
manually
install
them.
Otherwise
we
would
get
into
endless
loops
of
downloading
things
that
people
don't
actually
need.
A
All
right,
well,
that's
great!
A
Well,
if,
if
people
are
interested
in
this
level
of
functionality,
the
place
to
put
it
initially
is
probably
in
I
mean
we
can
have
a
tracking
issue
in
the
core
queue,
but
the
work
first
has
to
be
done
on
backdrop.
Cms.Org,
so
there'll
need
to
be
a
corresponding
issue
over
there
to
update
the
project,
to
update
the
packager
and
to
update
the
fields
on
the
project
nodes
and
then
once
those
are
in
place,
then
we
can
update
the
corresponding
project
browser.
B
Just
quickly,
I'm
not
sure
because
I
phased
down
at
some
point
I
needed
to
work
during
the
meeting
has
the
issue
that
is
being
discussed
about
the
updater,
failing
to
fetch,
updates
and
throwing
errors,
which
is
an
issue
that
comes
up
every
now
and
then
has
it
been
brought
up.
It's
issue
5455.
B
And
rd
piano
has
done
a
sort
of
like
an
initial
or
a
summary
in
the
zulu
chat,
and
also
mentioned
that
the
update
updates,
updates.backupcms.org
release
history
backdrop:
one
dot
x,
gives
a
404
there's
a
thread
in
zulu.
B
A
Yeah,
that's
that's
very
interesting
yeah.
This
is
a
great
great
thing.
I
think
this
probably
needs
to
just
have
more
discussion
in
the
issue.
There's
certain
it's
kind
of
funny,
because
it's
like
http
is
in
a
way
like
on
its
way
out.
You
know
like
it
probably
will
never
really
go
away,
but
I
think
that
a
lot
of
systems
will
make
it
harder
and
harder
to
use
as
time
goes
on,
but
yeah.
A
It's
kind
of
interesting
that
that
we
should
provide
this
kind
of
fallback,
because
it's
a
it's
like
a
server
misconfiguration
that
it's
unable
to
do
it.
I
wonder
if
we
could
just
have
it
ignore
the
certificate.
Maybe
I
don't
know.
A
B
D
A
Yeah,
my
my
guess
is
that
this
is
by
design
that
it
really
wanted
to
make
sure
that
absolutely
everybody
used
https,
because
when
we
first
built
it,
we
had
the
opportunity
to
set
what
our
update
path
was
going
to
be
at
that
time.
I
think
at
that
time
we
decided
only
https,
because
why
bother
with
http,
but
now
this
looks
like
there's
some
justification
for
why
we
should
have
http.
B
Well,
I'm
not
sure
if
I
recall
the
the
discussion
precisely
is
that
in
such
cases
where
people
do
actually
hit
this
problem,
where
they
can't
update
or
it
doesn't
function
that
there
is
a
checkbox
that
says,
I
understand
the
risk.
Yes,
please
allow
me
to
proceed
as
it
is,
and
if
they
do
that,
then
it
works,
but
it's
not
on
by
default
and
it's
maybe
a
settings
dot.
Php
thing.
I
A
All
right
well,
we'll
think
about
this
one.
We
are
now
all
out
of
time,
so
much
for
the
meaning
that
where
we
didn't
have
agenda
items
you
get
into
one
topic
and
then
suddenly
time
is
gone.
So
thanks
everybody
for
the
riveting
conversation
about
dependency
management
and
thanks,
as
always
for
all
of
the
work
that
happens
in
the
contrib
issue,
queue
one
last
call
out
for
backdrop
live
which
is
upcoming.
A
A
And
anything
else,
tim,
no,
okay,
all
right!
Well,
thanks
everybody
for
joining
the
meeting
and
we'll
catch
you
all
next
week.