►
From YouTube: Backdrop Weekly - October 29th, 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
All
right
we're
live
today
is
october
29th.
This
is
our
weekly
developer
check-in
meeting
and
before
we
start
I'm
going
to
do
something
I
forgot
in
the
last
meeting.
We
should
go
around
and
do
some
introductions.
I
will
start
and
pop
coronet
over
to
greg
next.
My
name
is
jen
lampton.
I
am
joining
from
oakland,
california,
I'm
very
excited
about
all
the
exciting
stuff
that's
happening
in
the
world
of
backdrop,
even
though
I
am
not
doing
my
part,
so
I
will
try
to
fix
that
greg.
Let's
go
to
you.
B
I
am
greg,
usually
in
australia,
about
now
just
joining
from
greece.
I
haven't
been
that
active
in
the
issue
for
the
past
two
or
three
weeks,
so
I'm
very
eager
to
go
back
and
keep
up
with,
what's
been
happening
lately
and
start
doing.
Some
work
for
the
next
release,
pass
it
on
to
luke.
C
I'm
luke
mccormick
coming
to
you
live
from
san
ramon,
california,
I
I
do
marketing
and
various
other
things
associated
with
the
project.
When
I
can
mathis.
D
Sure
I'm
a
test
from
switzerland
and
actually
I'm
not
a
developer.
Article
is
just
to
have
an
overview
of
overview
of
what
has
been
going
on
in
the
past
few
weeks
in
the
project.
D
E
Hello,
I'm
nate
lampton,
also
in
oakland,
california,
I'm
core
committer
and
yeah
this
week.
I'm
excited
to
go
over
our
regular
status
updates
on
things.
There's
a
lot
of
activity
in
the
issue,
queue
on
issues
that
we
don't
normally
talk
about,
so
yeah
excited
to
see
things
moving
along,
as
always
to
tim,.
F
Hi,
I'm
tim
erickson,
st
paul
tim
coming
to
you
from
deerwood
minnesota.
My
big
backdrop
thing
right
now
is
starting
a
discussion
about
backdrop,
event
tools.
We
have
a
project
called
backdrop,
underscore
events
where
we're
looking
at
maybe
a
distribution
or
at
the
very
minimum,
some
contrib
modules
to
help
with
events
all
right.
Joseph.
G
A
Sure
so
we
have
been
on
fire
and
by
we
I
mean
everybody
else.
Since
the
last
meeting
we've
had
a
ton
of
new
contributed
projects,
web
form
structured
text,
web
form,
layout
web
from
telephone
web
from
countdown
web
from
autocomplete,
private
files,
download
permission
and
ajax
markup.
So
thank
you.
Everybody!
That's
continuing
to
work
on
porting
modules
from
drupal.
E
Sure
so
117
117
is
our
current
release.
117.1
is
the
current
miner
or
bugfix
version
and
117.2
will
be
the
next
release
that
we
create
since
our
release
on
september
15th.
If
I
look
at
the
ready
to
be
committed
lists
or
sorry,
the
the
closed
list
from
117
there
are.
E
Sorry
one
second
one,
seventeen
two
fifteen
closed
issues
right
now,
slotted
in
the
117
two
list
and
68
currently
open
ones.
So
we
have
a
huge
bucket
of
minor
fixes
that
could
be
fixed
in
117
too.
E
A
new
issue
that
I'd
like
to
bring
up
this
week
is
something
that
needs
additional
feedback
is
issue.
2398
2398
is
a
question
about
when
putting
a
block
onto
a
layout
that
uses
fields
from
the
user
from
the
user,
account
that
if
you
use
the
current
user
and
try
to
pull
out
a
field,
that's
on
that
user's
account.
E
Then
it
throws
an
error
because
the
in
internally
the
block
when
it
gets
past
the
user
account
it's
passed,
the
global
user
account
which
doesn't
have
fields
attached
to
it
and
so
2398.
E
The
solution
is
currently
in
place
makes
it
so
that
well,
the
user
account
that
gets
passed
in
is
now
a
fully
loaded
user
object,
but
the
difference
that
that
or
a
consequence
of
that
change
is
that
it
makes
it
so
that
the
current
user's
account
gets
loaded
from
the
database
on
every
single
page
request,
because
every
page
is
delivered
by
a
layout
and
every
layout
would
need
to
have
the
context
of
the
current
user
with
all
of
the
fields
loaded.
E
And
so
the
question
is
there:
can
we
implement
this
in
a
way
that
we're
not
loading
the
user
object
fully,
all
the
time
or
potentially,
maybe
we
should
be
loading
the
user's
fields
into
into
either
the
user
account
that's
passed
into
layouts
or
even
possibly,
into
the
global
user,
account
that's
available
as
a
global
across
the
entire
system.
E
E
Next
up
is
tugboats
for
pull,
request,
sandboxes
issue
4351
we
have
a
tugboat.
First
of
all,
tugboat
is
the
service
that
we
use
for
making
sand
boxes.
When
you
visit
the
home
page
of
backdrop,
cms.org,
there's
a
try
demo
button
and
that
spins
up
a
sandbox
on
tugboat,
which
is
a
containerized
service
that
we
can
customize
to
do
various
things.
E
The
primary
function
of
tugboat
that
they
advertise
is
their
business
model.
Is
that
it's
for
sandbox
creation
when
you
create
a
pull
request,
create
a
pull
request.
E
It
makes
a
working
sandbox
and
we
have
a
service
that
does
that
already
called
zen
ci,
but
we've
been
having
some
issues
with
the
sandboxes,
not
spinning
up
properly
and
sometimes
not
working
correctly,
and
so
we're
evaluating
using
tugboat
as
an
alternative
to
that,
and
the
current
status
of
that
is
that
we
have
the
configuration
merged
into
the
backdrop
core
repository
so
we're
configured
as
far
as
the
core
repository
and
now
we
need
to
hook
it
up
to
a
tugboat.
E
The
problem
is,
is
that
we
would
need
to
spend
up
so
many
tugboat
sandboxes
that
we
would
expend
the
current
account
that
we're
using
right
now,
and
so
we
have
a
meeting
set
up
to
discuss
what
kind
of
collaboration
we
can
have
in
between
backdrop
and
the
tugboat
product
with
the
owners
of
tugboats
tomorrow
and
gregory,
and
I
are
going
to
be
meeting
with
that
group,
then
so
we'll
have
some
more
information
about.
E
You
know
how
we'll
be
able
to
proceed
after
we
talk
to
them
tomorrow.
E
E
Okay,
well,
118.
110
is
the
next
version
of
backed
up
that
will
be
coming
out
january,
15th
with
feature
freeze
on
january
1st.
That
will
be
in
2021,
which
is
just
exciting
to
think
about
the
end
of
this
year.
E
So
the
first
item
that
we've
got
here
is
my
sql
eight
support.
The
issue
is
43
or
sorry
42.38,
and
this
feature
we
have
merged
into
the
one.x
branch.
So
it's
already
in
the
next
version
of
backdrop.
E
However,
the
tic,
the
issue
is
still
open
in
a
state
of
needs
testing
because
we're
considering
backboarding
into
117
sooner
than
january
15th.
So
my
sequel
8
is
the
current
version
of
my
sequel
that
gets
installed
on
pretty
much
every
linux
distribution.
If
you
do
an
install
of
my
sequel
backdrop
works
fine
with
the
latest
release
of
mariadb,
it's
only
the
mysql
variant
that
is
having
this
particular
problem
that
there's
new
additional
keywords
that
need
to
be
escaped
so
we're
considering
putting
that
back
in.
It
seems
to
be
really
stable.
E
E
E
E
Okay,
all
right
we'll
just
move
on
along
next
up
is
the
media
library
dialog
we'd
like
to
add
a
file
name
filter
to
that
dialog.
It's
issued
32.
E
Lauren
is
the
advocate
for
this
one.
It's
currently
marked,
as
it
needs
help,
there's
no
pull
request.
We
know
that
this
would
be
a
highly
desirable
feature
and
it's
a
great
candidate
for
the
next
release
of
backdrop,
but
there's
no
code
backed
up
here,
yet
I
think
that
we've
been
having
some
problems
with
the
way
that
the
ajax
system
works.
I
think
I
I
don't
have
a
real,
clear
understanding
of
this
issue,
but
there's
an
open
call
for
help
on
this
particular
issue.
A
I
think
it
has
something
to
do
with
how
modal
forms
load
ajax
calls
like
they're
like
detached
and
reattached,
in
a
way
that,
because
it's
a
ck,
editor
model
that
makes
it
so
that
you
can't
just
like
form,
multiform
and
expect
expose
filters
to
work
the
same
way.
So
I
think
there
was
some
javascript
confusion
in
there
and
it
would
be
good
to
have
someone
who
knows
how
those
models
work,
help
sort
that
out.
E
Next
up
is
adding
a
setting
to
the
menu
block
for
changing
or
for
setting
a
breakpoint.
E
So
right
now
backdrop
has
a
hard
coded
location
when
you
resize
the
window,
the
built-in
navigation
switches
to
a
hamburger
menu
at
a
certain
point
and
there's
a
question
of
how
can
we
handle
that
to
make
it
so
that
that
location
of
where
it
changes
can
be
changed?
E
The
latest
on
this
that
that
I
know
of
jen
you're
updating
the
agenda
right
now,
but
the
latest
I
know
of
is
that
we
have
a
configuration
that
just
simply
makes
it
be
specific
to
menu
blocks,
in
particular
that
you
can
configure
the
break
point
for
the
menu
block.
Currently
there's
a
pull
request
that
is
out
there.
That
seems
to
work,
but
it's
marked
needs
some
work
yeah.
If
it.
A
Were
to
get
merchant
decor,
all
existing
sites
would
break
because
it
removes
the
core
style
sheet
that
handles
breakpoints
and
adds
a
whole
bunch
of
additional
ones.
So
any
site
that
has
styled
their
drop
down
menu
would
lose
the
styling
and
would
get
back
all
of
the
core
styling
that
they'd
previously
overwritten.
A
So
I
linked
it
to
the
other
issue
where
we
have
this
ongoing
problem
of
like
how
to
add
css
to
core
and
without
breaking
existing
sites,
and
so
I
think
we
need
to
figure
that
out
before
we
can
start
adding
emerging
things
that
haven't
like
that
change,
css
and
core,
and
so
I
think
we
need
to
figure
out
what
our
policy
is
like.
If
we
want
to
do
things
conditionally
or
if
we
want
to
just
say
anyone
running
an
existing
site
should
expect
their
site
to
break
with
every
update.
A
F
Thanks
for
bringing
it
up
jen,
I
was
I've
kind
of
backed
off
it.
I
made
a
big
deal
about
this
issue
last
week,
release
cycle
and
I
feel,
like
it
kind
of
gets
stuck
with
everybody
not
liking
the
proposed
solutions,
but
not
providing
like
one
that
they
like,
and
so
we're
sort
of
stuck
on
like
a
solution
that
there's
any
consensus
behind.
F
So
that's
kind
of
where
I
feel
like
we're
at,
and
I
I
kind
of
just
sort
of
put
this
on
the
back
burner
and
moved
my
attention
to
other
issues,
but
it's
holding
things
up.
There's
you
know
it's
just
like
there's
a
number
of
issues
that
I've
just
written
off
my
agenda
because
they
can't
be
addressed
until
we
know
what's
going
on
here.
E
Yeah
this
particular
approach,
it's
literally
creating
all
new
css
files
that
yeah.
I
could
see
some
issues
with
that.
Well
I
mean.
F
Although
to
be
fair,
I
I
haven't
looked
exactly
at
your
concern,
john,
I
wasn't,
and
I
was
wondering
if
this,
if
this
didn't
give
us
another
option,
maybe
in
our
css
thing
this
thing
with
the
the
break
point
for
the
block,
I
mean
this
seems
different
than
anything
we
proposed
for
other
things,
because,
yes,
it
changes
the
css,
but
it
only
does
so.
If
you.
A
Oh,
it
does
so
for
everything
whether
you
touch
that
setting
or
not
it
throws
out
the
old
css
and
writes
new
ones.
So,
in
my
last
comment,
I
proposed
like
okay,
we
could
leave
the
existing
css
and
just
duplicate
it
all
over
the
place,
but
we
need
to
decide
that
duplicating
css
in
multiple
places
is
okay,
because
that
means
that
in
the
future,
if
we
wanted
to
make
any
changes
to
anything,
we'd
have
to
do
it
multiple
places,
which
is
fine.
A
As
long
as
we
decide
that's
our
process,
but
you
know
we
do
need
to
just
keep
that
in
mind.
B
One
of
the
things
so
I
haven't-
I
haven't
reviewed
the
issue
in
a
few
weeks
now,
but
are
we
adding
a
generic
breakpoint
sort
of
like
api
ish?
No,
it's
just
for
the
menu
block
yeah
I
would.
I
would
find
more
value.
I
know
that
it
would
be
more
complicated
that
I
would
find
more
value
if
there
was
a
generic
breakpoint
api
added
to
core
that
other
things
can
use
it,
but.
A
So
we're
not
rolling
that
out,
but
but
it's
really
hard
to
provide
a
generic
api
breakpoint
in
core,
because
right
now
we're
using
the
bootstrap
grid
system
and
it
only
supports
certain
points.
I
think
it
would
be
smarter
to
like
very
slowly
introduce
things
that
we
know
are
going
to
work
rather
than
providing
a
new
feature.
That
has
you
know
four
settings
that
work,
but
anything
else
you
enter,
isn't
going
to
work,
sort
of
thing.
B
Yeah
yeah,
so
I.
A
Think
like
this,
this
is
sort
of
a
good
first
step
to
figuring
out
like
how
we're
going
to
solve
breakpoints.
Once
we
solve
this,
we
might
be
able
to
introduce
additional
settings
and
then
maybe
come
up
with
some
kind
of
an
api.
But
I
think
that
we
can't
start
there,
because
our
core
already
has
a
bunch
of.
B
A
So
you
right
now
that
there's
one
library
that's
attached,
and
so
you
could
just
remove
the
parent
library
and
add
a
different
one,
but
usually
if
you
want
to
use
css
grade,
you
probably
also
want
to
have
different
classes
that
trigger
it.
A
different,
so
you'd
probably
want
to
override
your
templates
anyway.
So
it's
up
to
you,
which
way
you
want
to
go.
You
could
also
drop
in
another
set
of
layouts
that
use
it
css
grid,
okay,
but
yeah.
It's
not
hard.
It's
all
just
easily
attached
to
the
library.
A
A
Well,
so
layouts
are
interesting
because
we
already
done
this
once
where
we
threw
out
all
of
the
layouts
we
provided
in
core
and
we
just
put
them
into
like
a
legacy
section
where,
if
you
were
using
them,
they
were
enabled.
But
if
you
weren't
using
them,
you
wouldn't
see
them.
So
we
still
ship
core
with
the
original
four
layouts
that
we
had
that
were
all
customed
on.
So
we
have
a
precedent
for
doing
this
and
we
could
do
it
again.
A
B
Yeah
or
have
an
option
to
use
either
bootstrap
or
the
new
thing
similar
to
what
so
when
we
set
up.
I
know
we
rely
on
contrib
for
that,
but
when
we
set
up
text
formats
you
give
the
option
to
select
the
text
editor
right.
We
can
equally
select
which
library
to
load
right
or
not,.
A
I
mean
you
can,
but
you
probably
wouldn't
want
to
use
two
completing
grid
systems
on
the
same
site.
G
A
Yeah
well
so
this
isn't
related
to
the
grid
system.
The
grid
system
is
only
attached
to
layouts
and
this
is
attached
to
menus.
So
this
isn't
related.
B
Yeah
just
throwing
it
out
there.
I
don't
want
to
derail
this
a
lot
since
we
have
the
option
to
just
install
things.
B
We
have
previously
removed
things
in
the
early
days
that
were
in
d7
core
and
we
moved
them
to
country,
and
since
we
have
the
option
to
automatically
install
things,
we
could
during
an
upgrade
say
we're
not
switching
this
library
until
that,
like
we,
we
do
this
once
again
like
if
we
ever
decide
to
replace
bootstrap,
we
move
it
to
contrib
and
then
for
existing
sites.
We
make
sure
that
it
automatically
installs
the
contrib
module.
Something
like
that.
I
don't
know,
that's
that's
an
option
because
we
do
it
automatically.
E
E
How
do
we
change
css
and
core
safely,
or
we
need
to
come
up
with
some
approach
that
changes
the
css
less
tracks
drastically?
That
would
somehow
be
compatible
with
existing
sites,
which
I
guess
is
a
big
generic
problem,
but
I'm
saying
there
might
also
be
a
specific
way
that
might
be
safe
in
this
situation,
but
I
don't
know
what
that
is.
B
Just
as
a
general
advice
team,
if
you
can,
if
you
can
add
that
4663
to
the
list
of
issues
that
are
being
blocked
by
4167,
maybe
once
we
have
enough
issues,
there's
also
enough
drive
to
just
push
for
a
decision.
I
guess
more
solution.
E
All
right
next
issue
is
simple
in
concept,
and
that
is
that
the
full
html
text
format.
We
have
the
intention
to
rename
that
to
raw
html.
The
issue
is
44.99
tim
you're.
The
advocate
for
this
any
updates.
E
B
So
that's
99
percent
there
it's
a
marked
rtbc,
it
has
a
type
4
needs
more
feedback,
I'm
probably
going
to
remove
that
tag.
So
the
the
only
remaining
task
there
is
to
replace
the
mentions
of
login
name
with
username
and
I
think
we're
good
to
go
so
I
can
then
jump
to
the
my
next
favorite
one,
which
is
merging
the
all
the
updates
pages.
B
E
A
much
more
ambitious
undertaking:
okay,
great,
let's
see
advanced
caching,
adding
up
tags
and
max
age,
headers
issue:
41
27.
joseph!
Do
you
have
any
updates
this
week.
G
I
do
I
did,
however,
discover
that
a
bunch
of
the
features
of
the
drupal
7
module
that
is
like
the
back
part
of
that
feature
depend
on
core
patches.
So
I
think
I'm
actually
going
to
have
to
hunt
down
a
bunch
of
core
patches
from
drupal
7
and
include
those
into
the
issue
which
is
probably
going
to
cause
feature
creep.
E
Okay,
well,
that's
the
status
for
advocated
issues
for
118.
We
also
have
initiatives.
E
F
Not
really,
I
think
my
next
step
is
to
to
do
some
testing
of
it
myself.
If
I
recall
we
had
a
good
discussion
about
it
last
week,
I
think
I
even
posted
a
link,
I'm
not
sure
in
the
issue,
to
the
to
the
discussion,
but
it
was.
I
don't
remember
there
being
any
immediate
next
steps
other
than
getting
some
more
testing
on
it.
Is
that
right?
Does
that
sound
familiar.
E
Yeah
more
testing,
I
think,
is
issue
number
one,
and
there
are
a
couple
of
obvious
things
that
we
have,
that
we
need
to
enhance.
E
The
reporting
of
the
data
is
one
that
we
need
to
get
into
a
better
format
and
we
need
the
ability
to
suppress
the
retainment
of
data
that
is
sent
to
us.
So
if
a
contrib
module
tries
to
send
us
data
that
we
specifically
haven't
allowed,
then
we
should
be
discarding
it,
so
we
need
to
make
it
so
that
backdrop.
Servers
cannot
collect
inadvertent
data,
basically.
F
E
B
Thanks
are
we
doing
the
decoupling
from
the
installer
thingy
the
steps
in
the
check
boxes
in
that
vr
or
that's
separate?
We
left
that.
F
E
Yeah,
I
think,
maybe
gregory.
We
should
separate
out
that
problem
we
might
put
telemetry
in
in
core.
Have
it
be
a
disabled
module
because
we
can't
turn
it
on
by
default?
Unless
we
ask
people
about
it
and
then
separately
have
an
issue
for
like
redo
the
installer
check
boxes,
because
that
also
affects
the
way
the
update
module
works
yeah.
I.
B
E
Okay,
unless
there's
anything
else,
I
think
that's
probably
good
for
telemetry
next
up
is
the
ready
to
wear
initiative.
Luke,
do
you
have
updates
on
ready
to
wear.
C
C
I
I
I
I
do
have
sort
of
a
question
that
I'm
finding
so
I'll
just
throw
out
to
this
knowledgeable
crowd
here,
which
has
to
with
with
dark
mode
things
in
particular,
what
I
was
hoping
to
discover
was
like
a
dark
mode,
color
setting
and
this
this
feels
like
something's,
been
gone
over
so
so
before
I
try
to
reinvent
the
wheel
and
I've
read
stuff
people
have
talked
about
it
and
seen
things.
C
B
Yeah,
so
this
is
an
issue
for
dark
mode
version
of
seven,
because
I
don't
think
that
people
want
dark
mode
of
their
front-end
theme.
I
think
it's
usually
used
for
content,
editors
and
people
in
the
back
end.
I
could
be
wrong
about
it,
but
this
issue
3990,
which
aims
to
add
color
support
for
seven
for
the
seventh
in
and
then
provide
a
preset
which
turns
it
into
a
dark
mode
thing,
because
that's
something
that
people
have
requested.
G
Would
we
want
this
to
be
configurable
per
user
or
global
across
the
whole
site,
global
across
the
global
crossover
site,
so
the
color
module?
Currently
can't
do
that
or
I
mean
sorry,
the
color
module
currently
can't
support
a
per
user
setting,
so
global
across
the
whole
site
would
probably
not
be
that
hard
yeah.
C
B
So,
for
the
front
end,
I
think
browser
extensions
that
do
that
for
front
end
themes.
So
no
one,
that's
that's.
Building
a
site
for
general
consumption
might
have
thought
of
that,
and
the
request,
even
in
the
drupal
land,
is
for
dark
modes
for
back-end
things
like
for
the
admin
theme.
C
F
C
Having
a
dark
color
scheme
white
on
black
or
you
know
the
equivalent
so
so,
for
example,
in
in
in
the
boots
watch
choices
which
honestly
the
boots
watch
homepage
is,
is
as
I,
as
I
mentioned
january
before,
it
was
awfully
close
to
kind
of
what
I
had
in
mind,
just
like
choices
of
things
and
of
their
21
options.
Three
of
them
are
are
light
on
dark
and,
and
that
seems
actually
I
I
think
I
think
this
might
be
one
of
these,
like
professional
versus
small
scale.
C
F
And
just
looking
for
like
a
color
palette
that
leans
towards
the
darker,
I
think
that's
not
technically
a
problem
which
it
just
involves
a
designer
coming
up
with
a
good
combination,
and
I
also
think
it's
it's
a
per
theme
thing
though
right
so
like
we
could
add
one
to
basis,
but
each
team
would
kind
of
treat
that
differently.
So
each
theme
sort
of
sets
its
own
predefined
color
sets.
F
C
G
B
F
B
C
B
I
provided
a
link
in
the
chat
for
the
the
issues
specific
to
seven.
Maybe
you
can
create
a
respective
issue
basis.
B
E
Great
thanks,
luke,
let's
see
tim,
you
have
an
additional
thing
that
you've
slotted
in
the
open
q,
a
that's
where
we
are
now
is
just
general
discussion.
You
have
an
idea
about
profile.
Selector
seems
like
we
do
have
time.
Well.
Kind
of
we've
got
four
minutes
until
the
top
of
the
hour.
Would
you
prefer
to
do
that
after
the
meeting
or
do
it
do
it
now.
F
Either
way
I
could
describe
the
idea
really
quick.
It's
just
an
idea
that
came
up
you
back
home.
I
think
it's
interesting
having
on
the
tape
might
not
hurt,
but
we
could
hold
the
discussion
off.
It's
there's
nothing
urgent
about
it,
but
it
so
this
backdrop,
event,
distribution
project
that
I
started.
F
Part
of
the
goal
is
I've
heard
a
few
people
actually
bring
up
distributions
recently
for
backdrop,
and
we
don't
have
any
official
distributions.
I
know
individual
developers
have
created
them
and
used
them.
I
use
one
and
I'm
interested
in
exploring
that
idea
a
little
further-
and
I
was
talking
to
my
friend
wilbur
yesterday
about
this
and
he
asked
would
it
be
possible
and
I
think
it
would.
F
I
just
I'm
not
saying
it's
a
good
idea
yet,
but
if
we
that,
rather
than
having
distributions,
if
we
used
install
profiles
and
and
right
now,
when
you
get
to
the
install
profile
page
and
during
installation,
I
think
by
default,
you
don't
have
actually
have
a
choice.
Do
you
unless
you,
unless
you've
added
your
own
install
profile,
it
just
assumes
the
standard
profile.
Is
that
right?
B
So
people
that
know
how
to
use
this
feature
and
enable
it
there's
not
enough
there's
not
enough
things
required
that
have
been
bootstrapped
by
by
that
point,
to
take
advantage
of
the
project
browser.
But
there
is
an
issue
and
that's
what
I'm
trying
to
find
with.
I
remember
sorry,
you
might
be
ahead
of
me,
then
maybe
you're.
Maybe
there
is
an
issue
for
this
already
there's
an
issue
that
says:
allow
installation
profiles
to
run
after
the
installation
of
backup.
Oh
okay,.
F
Well,
my
idea
was
during
during
installation
when
you
get
to
that
page,
that
it
give
you
a
project
browser.
So
you
could
pick
from
existing
installation
profiles
and
then
during
installation
at.
B
E
Yeah
it
I
mean
that
sort
of
thing.
I
think
you
would
need
to
run
the
installer
to
get
you
know
the
database
initiated
and
then
after
you
had
it
basically
installed,
then
you
would
possibly
then
kick
them
into
the
project
browser.
If
you
wanted
to
then
run
additional
things,
but
then
you
got
into
the
question
of
gregory
like
if
you
were
pre-bundling
things.
It
wouldn't
be
an
install
profile
anymore,
because
the
installer
has
already
run,
and
so
it
would
be
something
that
was
like.
B
The
issue
is
pretty
one
of
the
old
ones,
not
three
videos
once,
but
it's
one,
five,
nine
one
which
is
titled
allowing
store
profiles
to
run
after
site
creation,
okay
or
it's
it's
a
similar
as
to
allow
people
to
switch
installation
profiles.
I
guess.
F
Well,
I
think,
there's
a
whole
nother,
there's
one
the
technical
discussion
too,
the
is
it
even
a
desirable
idea.
I
just
wanted
to
quickly
see
if
what
the
technical
issues
were-
and
I
think
you've
already
answered
that
this
has
been
helpful.
So
it's
just
something
I'm
floating
around
and
I
thought
it
would
be
easier
to
talk
about
it
quick
than
to
try
and
do
it
in
the
issue
queue.
Thank
you.
B
But
yeah
this
ties
to
the
discussion
of
the
tugboat
demos
as
well.
So
if
we
do
have
a
an
installation
profile
or
a
distribution
like
the
umami
thing,
I
think
that
simply
test
me
already
allows
you
has
a
one
click
button
that
says
install
instead
of
installing
drupal
install
umami
right.
So
we
would
like
to
ideally
get
to
the
place
where
we
allow
people
to
install
those
things
so
that
they
can
try
real
sites
like
sites
with
actual
content,
to
get
better
ideas,
but
yeah
this.
B
E
Okay,
anything
else
that
anybody
would
like
to
bring
up.
B
Just
a
question
is
the
documentation
thing,
an
initiative.
We
didn't
decide
anything
officially
yet,
but
it's
sort
of
like
a
proposed
initiative
or
to
be
proposing
right.
We.
A
Were
gonna
wait
until
there
was
time
to
work
on
it
in
december.
E
A
Also,
I
just
want
to
throw
out
there.
We
are
looking
for
new
volunteers
to
help
us
manage
the
backdrop
group.
We're
getting
a
lot
of
applications
now
and
it'll
be
great
if
we
get
other
have
other
more
people
who
are
empowered
to
review
those
applications
and
admit
people
to
the
group.
So,
if
anyone's
interested
in
doing
that,
reach
out
to
myself
greg
or
tim-
and
we
can
let
you
in.
B
I
just
remembered
one
final
thing:
backdrop
for
good
came
up
and
so
the
I
think
that
the
domain
has
expired
and
maybe
jeff
was
the
one
that
registered
it.
So
we
do
have
the
we
do.
Have
the
what
you
call
the
github
repo.
B
B
So
just
as
a
one
of
the
to
do
things
in
the
backlog
maybe
revive
that.
But
in
order
to
do
that,
we
would
need
to
know
where
was
it
hosted
was?
Was
it
hosted
in
one
of
the
backdrop
owned
the
nodes,
or
was
it
somewhere
else
and
then
make
a
decision?
If
we
want
to
purchase
that
domain
or
transfer
it,
it
doesn't
have
to
be
decided
now,
just
for
next
for
next
meeting.