►
From YouTube: Backdrop Weekly Dev Meeting July 16th 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
C
A
E
A
D
A
Alright
next
is
me:
I
am
Joe
Lampton
I'm
in
Oakland,
California
and
I
am
feeling
very
invigorated
from
our
last
meeting.
So,
let's
move
on
this
week,
we
have
one
new
maintainer
application
for
contribute
code.
Early
Berg
has
ported
the
search
api
pages
module
and
there's
a
couple
of
other
things.
There
are
poor
requests
associated
with
other
modules,
like
entity,
plus
I,
think
in
a
couple
of
personal
marshals
that
are
also
getting
ready
to
get
moved
over,
so
early
bird
gets
through
busy,
which
is
great.
Thank
you.
D
All
right
so
116
3
is
a
current,
but
fixed
release
up
the
issues
that
we
normally
bring
up
there
happen
hasn't
been
updates
on
most
of
them.
Let's
see
the
visual
regression
text.
Format
order
still
remains
the
same
note.
No
port
request,
yet
views
pager
by
dates,
still
news
review
and
we
haven't
had
an
update
on
PHP
CSS,
automated
code
Jackson.
So
those
three
issues
no
updates
on
them.
Jen
you
added
a
new
issue
for
a
big
tub.
Php
throws
an
error
on
there's
an
error,
that's
related
to
installation
when
you're
running
update
dot
PHP.
A
Quite
a
while
ago,
and
was
really
alarmed
by
it,
so
of
course,
I
immediately
filed
the
pull
request
and
then
forgot
about
it,
but
I
ran
into
it
again
this
week
on
it's
like
a
16-1
site
or
something
where
I
went
to
run,
updates
on
it,
and
the
error
message
tells
you
to
delete
all
your
configuration
files,
which
seemed
really
dangerous,
that
we
are
instructing
people
to
delete,
something
that
possibly
could
be
an
unrecoverable
mistake.
So
I
just
wanted
to
surface
that
issue
again
and
get
you
eyes
on
it.
A
Where
there
was
just
an
if
check
in
there,
I
think
was
checking
a
little
too
generally
what
it
should
have
been
checking
in
now.
It
specifically
checks
updates
versus
installations
separately.
Hopefully
we
won't
throw
the
wrong
error
and
the
round
circumstances
and
should
be
safer
for
people.
So
we
know.
D
All
right
yeah,
so
we
don't
have
a
whole
lot
of
things
to
mention
on
the
116
3
and
had
I
had
time.
I
would
have
looked
through
the
the
list
of
issues
generally
in
116
3
to
see
if
there
was
anything
else
that
was
worth
bringing
up,
but
I
don't
have
anything
at
this
time.
So
I
think
we'll
probably
just
move
on
to
117
and
talk
about
those
issues.
So.
D
A
F
A
By
turning
on
this
setting,
they
will
inadvertently
be
releasing
that
information
to
everyone
in
the
world,
and
so
there
are
a
couple
of
recommended
solutions
in
the
poll
requests,
including
adding
entirely
new
layout.
That
would
be
just
for
the
administrator
or
just
for
these,
like
log
in
register
password
reset
pages.
In
order
to
get
that
layout
to
trigger.
A
So
if
we
wanted
to
modify
any
layout
to
automatically
add
this
condition,
we
could
protect
that
data
from
leaking
I
also
had
recommended
that
if
we
were
going
to
add
a
visibility
condition
to
blocks,
we
might
want
to
automatically
add
that
condition
to
every
block
that
was
added
to
the
default
admin
layout,
just
so
that
people
won't
after
the
fact,
okay
I've
got
this
setting
turn
on
I
forgot
about
it
now.
I'm
gonna,
add
this
potentially
sensitive
information
to
my
admin
layout,
not
realizing
it.
A
That
would
also
show
up
for
anonymous
users,
so
I
think
there
is
some
rethinking.
We
need
to
do
about
how
to
handle
this
particular
scenario,
because
we
don't
want
to
leak
anything
that
should
be
private
to
the
public,
but
there's
also
a
little
balancing
act.
That
needs
to
be
done
because
I
think
the
use
case
for
people
adding
blocks
to
the
default
admin
layout
is
almost
zero.
A
I
think
the
use
case
for
having
a
separate
Lea
or
your
login
page
is
almost
zero
and
so
the
amount
of
features
we
want
to
add
into
a
course
to
support
these
alternate
use.
Cases
might
like
there's
a
kind
of
a
balancing
act.
They
were
like.
We
really
don't
want
to
do
anything
that
could
be
a
potential
security
issue.
We
also
don't
want
to
add
a
ton
of
features
to
core
that
and
no
one's
going
to
use
so
trying
to
figure
out
where
the
happy
medium
there
I
think
is
going
to
be
important.
D
All
right,
yeah,
you
guys,
are
up
having
a
small
conversation
about
it.
Do
you
think
just
increased
messaging?
Have
you
guys
considered
that
is,
like
you
know,
just
providing
more
notification
that
does
block
your
adding
is
going
to
be
visible
to
everybody,
because
you
have
it
enabled
on
the
login
form
so.
A
A
B
Just
that
I
think
that
adding
this
is
this
was
this
is
an
awesome
feature
and
I
wanted
it
to
go
in
one
second
theme,
but
adding
scary
messages
here
and
there
by
enabling
it
I,
don't
think
it's
the
best
user
experience
I
understand
the
pushback
with
regards
to
adding
another
layout.
But
it's
the
safest
option
in
my
head.
B
I
know
that
it
might
be
a
adding
too
much
noise
in
the
layouts
panes,
because
there's
too
many
layouts,
but
it's
the
safest
people
know
and
by
calling
it
something
like
login
layout
people
just
get
it
straight
away.
That
is
just
for
that.
It's
safe,
there's,
no
risk
to
add
any
module
any
blocks
there.
That
will
be.
F
A
How
many
people
are
gonna
use
it
if
nobody's
gonna
use
it
like
nobody
like
nobody
being
less
than
20%
yeah?
It
seems
like
that,
might
not
be
a
good
solution.
I
understand
it's
clear
in
terms
of
like
you
look
at
the
paging,
like
oh
I,
definitely
know
this
layout.
It's
gonna
behave
differently
than
the
other
ones,
but
I'm
not
sure
that
I
mean
I.
Don't
know,
I'm
really
interested
know
what
other
people
think
about
that,
but
I'm
not
sure
that
that
clarity
is
worth
the
overhead
in
terms
of
having
it
so
I.
Just
I.
B
D
A
A
A
A
A
A
B
A
D
D
Yeah,
that's
not
ideal,
but
it
probably
is
pretty
low
impact
because
you're
you,
unless
you
can
log
in
first
of
all
yes
I
mean
yeah
yeah.
It
just
doesn't
make
any
sense,
although
I
think
it
does
affect
the
way
for
three
pages
are
displayed.
Doesn't
it?
If
you
go
to
slash
admin,
you
get
a
4-3
page,
it's
either
the
admin
theme
or
the
front-end
thing.
Depending
on
whether
or
not
anonymous
users
have
the
view.
Admin
theme,
permission,
yeah.
D
B
D
B
D
D
I
mean
if
we
took
the
permissions
problem
out
of
it.
You
know
we
still
have
other
problems,
you
know,
and
so
so
I,
don't
think
the
permission
is
the
limiting
factor
here.
It's
it's.
It
sounds
like
the
the
layout
like
placing
blocks
in
the
page.
I
can
showing
those
to
anonymous
users.
That's
the
thing
that
needs
to
be
a
hashed
out
and.
A
Know
which
way
we're
gonna
land
on
this
one
so
yeah
it's
getting
some
work
feedback
on
what
would
make
the
most
sense
so
and
I
think
also
trying
to
keep
in
mind
like
the
point
of
this
change
is
important
to
or
like
was
to
make
it
so
that
everybody
who
has
a
back
drop
site
doesn't
either
forget
to
theme
the
login
page,
which
also
then
gives
anyone
new
to
back
up
sort
of
that
first
impression
about
there's
a
login
system
looks
terrible
or
have
to
put
in
the
work
to
beam
this
page
for
every
site,
even
if
the
only
people
who
are
locking
in
are
a
high
level
administrator
or
two,
and
so
it's
sort
of
like
a
first
impression
and
intent
change
and
a
decrease
in
work
for
website
ownership,
change
and
I
feel
like
the
amount
of
change
we'd
originally
made.
A
But
the
first
for
us
was
very
small
and
it
made
sense
for
those
two
things,
but
the
amount
of
change
that
we
might
be
end
up
making
might
outweigh
the
benefit
that
those
two
things
offer
so
just
trying
to
keep
those
things
in
inline.
It's
also
important
to
like:
do
we
really
want
to
do
all
this
reimagining,
just
like
save
a
little.
D
D
It's
well
the
combination
of
like
yeah
their
front
end
pages,
but
you
know
it's
weird
cuz
they're,
going
to
the
back
end
the
the
combination
of
it
having
so
many
other
considerations
and
needing
to
be
at
multiple
pads,
because
we
don't
have
the
ability
add
a
layout
on
the
multiple
pads.
Currently,
if
we,
if,
if
we
did
support
this,
it
ended
up
kind
of
being
another
default
layout
like
down
at
the
very
bottom
of
the
list.
D
A
Something
that
increases
the
overhead
for
like
looking
at
the
backdrop,
so
you
must
at
work
site.
We
have
three
layouts
for
modules,
themes
and
layouts,
and
that
should
be
one,
and
so
maybe
we
should
say,
let's
backburner
this
issue
and
solve
some
of
these
other
issues
like
the
ability
to
put
a
layout
on
multiple
paths.
This
theme
system
and
work
on
all
of
the
little
blockers
in
117
and
push
this
to
118
and
say,
like
let's
reimagine
this
with
some
of
these
other
way.
A
A
Very
clean
gives
you
a
sort
of
a
polished
impression
where
a
lot
of
times,
people
like
style
their
front,
end
theme
and
not
realize
it
affects
the
login
page.
And
then
you
end
up
with
like
the
login
box
on
the
left
and
everything
else
is
centered,
and
it's
just
like
something.
No
one
ever
looked
at,
so
it
just
gets
messy.
F
A
So
this
this
patch
also
include
it's
theming
for
the
login
pages.
In
seven
we
could
also
add
improved,
aiming
for
the
login
pages
in
basis,
I'm,
not
sure
how
much
of
what
we
would
want
to
add
to
like
system.
But
we
could
look
at
that
and
see
if
it's
worth
like
shrinking
those
forms
or
something
that
might
be
a
good
first
step.
I
guess.
C
B
Thing
is
that,
by
definition,
this
this
issue
calls
for
the
removal
of
the
permission,
my
definition,
having
a
permission
that
says,
allow
people
to
view
the
admin
thing
does
not
make
sense
anymore,
because
that
would
be
the
admin
command.
You
want
anonymous
users
to
be
able
to
access
it,
so,
by
definition
that
that
we
need
to
defecate
that,
for
me.
A
C
D
If
it's
okay,
we
can
pivot
to
the
layout.
The
next
item
is
a
layout
discussion
item
anyway,
and
so
the
next
year's
3750,
which
is
support
for
custom
contexts.
It's
an
issue
that
dark
woman
has
been
working
on
and
they
think
artificially
saying
he's
advocated
for
it
so
custom
contexts
conceptually
makes
it
so
that,
when
you're,
adding
a
new
layout,
instead
of
needing
to
specify
like
a
node
specific
path
like
node,
/
%,
which
affects
all
nodes,
it
makes
it.
D
So
you
can
specify
any
path
you
want,
and
then
pole,
an
arbitrary
node
or
an
arbitrary
user
or
any
any
kind
of
thing
and
add
it
as
a
context,
and
that
makes
it
so
that
you
could
like
have
your
home
page
layout,
but
also
place
a
bunch
of
blocks
about
your
fields
from
like
node
one,
for
example.
So
you
could
just
decide
to
pull
in
arbitrary
notes
and
place
their
arbitrary
fields
into
any
region
you
wanted.
D
So
it's
pretty
neat
work
and
it's
something
that
panels
had
interval
seven
and
backdrop
in
its
core
code
as
like
slots
for
it's
like
when
contexts
are
supported.
They
go
here
and
so
3750
is
kind
of
restoring
the
functionality
from
triple7
panels
that
was
lost
in
the
porting
and
it's
bringing
it
into
backdrop
proper.
So
it's
very
exciting
seems
like
the
current
functionality
is
is
functioning.
D
D
B
D
D
We
have
a
special
context
right
now
for
dashboard,
for
example,
that
on
slash
dashboard,
there's
a
special
context
that
shows
up
automatically
that
allows
you
place
blocks
that
only
exist
within
the
dashboard.
We
could
make
it
so
there
could
be
all
kinds
of
different
sets
of
blocks
that
are
categorized
only.
C
I
guess
I'm
not
seeing
how
that
is
impossible
now
or
is
it?
Does
it
just
make
it
easier
like?
Even
when
you
talk
about
like
certain
fields
for
a
certain
node,
we
can
already
define
the
visibility
condition
to
only
show
up
on
a
you
know,
on
a
blog
post
content
type,
and
once
we
do
that,
we
have
field
level
blocks.
A
Adding
additional
blocks
like
on
a
node
context
needs
talking
about
we're
moving
them
so
like,
rather
than
being
like
here's
5,000
blocks
for
you
to
choose
from
when
you
present
it
to
your
editor
would
be
like
here
are
the
ten
blocks
that
are
safe
for
you
to
put
on
this
page.
So
it's
panels
had
a
little
bit
of
this
too.
In
the
panel
settings
you
could
control
what
blocks
and
what
layouts
your
editors
had
access
to.
You.
F
A
C
Okay,
so
what
you're
saying
is
that
I
could
create
a
layout,
give
an
editor
the
ability
to
to
reorganize
the
blocks
and,
using
this
context,
I
could
define
which
blocks
are
available,
not
implemented
so
which
ones
are
available,
got
it?
Okay,
I,
don't
I,
don't
know
that
I've
had
a
use
case
for
that
it
sounds
cool
like
a
fun
thing
to
able
to
do,
but
maybe
I
haven't
done
it
just
because
I
haven't
at
the
ability.
F
A
Of
their
admins
to
be
so
architects,
but
they
needed
a
little
more
control.
It
was
a
better
fit
there.
So
I
think
this
might
be
a
tool
for
like
a
slightly
larger
audience
than
most
of
us
are
dealing
with
with
our
backdrop
sites
right
now,
but
the
fact
that
we
have
it
means
that
backdrop
has
now
better
fit
for
that
audience
as
well.
So
it's
a
growth,
I
think.
C
D
D
What
context
is
that
one,
so
the
whole
context
that
you
would
whole
context.
Settings
area
only
appears
right
now,
if
you
put
a
wild
card
in
your
URL,
what
this
does
is.
It
makes
the
context
setting
always
show
up
and
as
a
link
just
like
visibility
conditions.
It
says
add
context,
and
so,
if
you
want
to,
you
can
additionally
add
a
context,
but
just
like
visibility,
conditions,
they're
completely
optional
and
you
can
just
kind
of
scroll
past
it,
and
it's
really.
The
the
visual
weight
of
this
entire
feature
is
like
one
length.
B
Since
we
don't
have
any
other
items,
there's
a
related
issue
that
I
worked
on
I
didn't
make
a
comment
that
just
updated
the
poor,
oppressed
I'll
I'll
make
a
comment:
I
just
need
to
fix
the
piston,
that's
only
three
or
six,
which
is
display
all
available
blocks,
so
Jen
started
work
on
that
from
dock
Wilmots
initial
PR
and
then
I
picked
up
on
those
that
yeah
with
those
Network
already
and
and
I've
started
fixing
a
few
things
and
your
feedbacks
problem.
The
review
that
you've
done
so
I
have
one
question
in
the
PR.
B
D
Yeah
this
is
yeah.
This
is
interesting,
and
this
this
is
kind
of
related
to
this
issue,
and
that,
like,
if
you
wanted
to
add
a
field
like
an
image
like
hey
I,
want
to
add
an
image
field.
To
this,
then
right
now,
there's
just
a
way
to
do
that,
like
you
can't
add
an
image
field
to
the
home
page
because
it
doesn't
know
where
to
get
the
data
from,
and
this
adds
the
ability
to
get
the
data
from
somewhere
yeah.
C
D
This
makes
it
so
that
it
could
possibly
I'm
not
sure
how
they
would
relate
to
each
other
yet
but
yeah
you
could
somehow
make
that
possible.
You
can
maybe
potentially
place
the
block
anyway,
even
though
it's
not
going
to
show
anything
but
then
later
after
you've
added
a
context,
go
back
to
the
block
and
say
now
associated
with
that
node
10
I
want
to
pull
the
image
from
that
node
yeah
and.
D
D
D
E
Last
night
or
this
morning,
depending
what
content
you're
in
pieces
of
kind
of
the
the
the
idea,
the
deliverables
and
it
was
it
that
a
lot
of
sort
of
division
that
I'd
outlined
is
already
baked
into
backdrop
just
just
in
pieces.
They
weren't
so
obvious.
So
I
I
kind
of
had
like
a
Wizard
of
Oz
moment
where
it
turns
out
that
the
path
was
there
all
the
time
and
I
just
didn't
didn't
realize
it
was
there
in
that.
E
Like
the
theme
settings,
you
know
speeding
up
three
it
through
kind
of
you
know
what
was
a
longer
tail.
The
the
theme
settings
screen
is
actually
this
interface
did
I
didn't
realize.
Was
this
feature
complete
as
it
was
that
that
has
a
lot
of
that?
The
effect
of
allowing
you
know
novice
users
to
to
click
on
things
and
see
an
immediate
result
without
without
having
to
do
a
very
complicated?
E
You
know
technical
dance
in
order
to
achieve
those
things,
and
if
you
choose
in
that
in
the
theme
settings
window
from
one
of
the
preset
color
color
palettes,
it
can
even
change
a
whole
bunch
of
different
elements.
On
the
on
on
the
page
to
to
good
effect,
so
that
this
is
the
backlog,
increasing
items
like
we
realize
that
that
the
the
luxurious
end
result
is
an
interface
that
combined
somehow
theme,
selection,
layout
selection
and
color
setting
selections
in
a
you
know,
presentation.
E
E
We
had
a
good
commercial
first
and
then,
when
we
come
back
from
commercial
now,
basically
choosing
a
few
themes
which
which
we
might
already
have
available
to
us,
because
because
actually
there's
less
fit,
that's
involved
in
the
theme
piece
and
realize
and
and
the
other
the
other
side
that
was
like
staring
us
in
face.
The
whole
time
is
is
a
demo.
Is
you
know
it
in
the?
E
If
you
go
to
you
know,
obviously
the
the
backdrops
you
mask
that
org
site
and
click
the
launch
demo,
you
you
get,
you
get
a
sample
site,
but
it's
empty.
It
comes
from
from
the
core,
and
if
we
enhance
that
just
with
a
relatively
simple,
we
hope
change
of
or
option
to
have
that
have
content
to
have
it
be
a
content
display.
What
we
can
do
is
pop
up
a.
E
A
C
D
D
E
I
was
thinking
that
it's
a
tugboat
thing
and,
and
so
the
the
question,
the
question
is:
none
of
us
in
the
previous
meeting.
We're
sure
is
how
hard
is
it
to
configure
talk
about,
to
have
a
have
sample
content
and
have
a
sure
it
might
be
helpful
to
just
straight
forward?
Is
it
hard
or
like
I,
wouldn't
expect
it
to
be
hard
I.
A
E
Mvp
to
to
understand
the
space
of
people
grasping
the
ways
to
affect
the
appearance
of
a
site.
Now
now
this
may
lead
to
interface
changes
in
core,
but
there's
no
there's
no
heard.
You
know
that's
in
that's
in
backlog,
that's
when,
after
we've,
you
know,
proved
the
market
readiness
of
these
ideas
through
the
through
it,
the
demo
site
and
yeah.
The
proposal
is,
you
know,
demo
backdrops,
you
messed
at
work.
There
is
there's
a
github
repository
already
created,
waiting
to
be
populated.
D
Yeah
I,
don't
think
any
type
of
we
have
as
a
resource
and
we
can
use
it
for
a
lot
of
purposes
and
creating
sample
contents.
It
shouldn't
be
too
terribly
difficult,
they
say,
probably
maybe
boy
this
gets
into
another
thing.
You
couldn't
make
a
profile
that
includes
the
sample,
content,
yeah
I,
know
and
then
and
then
have
that
be
installed
that
doesn't
that
profile
is.
B
C
D
I
mean
because
boat
has
I
mean
it's
a
container
that
you
can
do
whatever
you
want
in
it,
so
you
can
pull
from
multiple
locations.
It
doesn't
have
to
all
be
in
core
by
definition,
we're
gonna
be
pulling
from
a
contributing
and
adding
core
already.
So
if
we
want
to
add
another
thing
up
like
get
the
sample
content,
you
know
we
could
like
that
as
well.
Well,.
C
Yeah
my
point
was
that
that
we've
already
kind
of
moved
away
from
using
the
install
problem
profile
might
be
good
whatever.
Let's
avoid
that
discussion,
I
think
what
we,
what
we
haven't
quite
settled,
maybe
or
maybe
we
have
is
like-
we
would
still
need
the
ability
for
somebody
to
spin
up
a
default
playing
backdrop
site
so
I
get
the
feel
that
we
were
leaning
towards
changing
the
demo
button
to
you
to
actually
spin
up
this
demo
site
with
content
but
provide
somewhere
along
the
way
and
that
I
don't
it's
clear.
C
D
C
The
first
step
is
just
being
able
to
do
to
do
either
this
demo
site
with
multiple
themes
and
the
what
we
currently
milla.
So
once
we
have
those
two
options,
we
can
sort
of
figure
out
where
and
how
to
trigger
either
one.
But
we
need
to
know
we
can
get
both
of
those
working
simultaneously
and
like
what.
What
do
you
need
from
us
and
or
you
know
who
needs
to
do
that?
Yeah.
B
E
Can
be
a
second
button
while,
while
we're
you
know
seeing
how
comfortable
the
whole
thing,
but
but
the
reason
I'm
excited
with
it
is,
is
it
allows
us
to
to
sort
of
understand
this
whole
school
of
problems
of
kind
of
you
know?
If,
once
we
have
this,
we
can
kind
of
market
test
it
with
people
we
can
see
where
people
go,
we
can,
we
can
try.
It
gives
a
platform
to
try
like
interface
ideas.
It
enables
you
know
things
that
that
may
at
some
point
be
included
in
core
could
be
could
be
you
know.
E
E
You
know,
themes
which
are
big,
you
know
complicated
beasts
and
and
layouts
and
color
selections
and
content,
and
all
these
things
that
are
there's
too
many
pieces
to
to
get
the
vision
in
in
your
mind.
But
you
know
this
gives
us
a
path
to
get
it
out
of
out
of
theory
and
and
into
something
you,
click
on
and
I,
think
I
think
once
we
have
that
once
we
have
that
that
prototype
that
MVP
further
refinements
are
relatively
straightforward
in
more
obvious,
so
the.
B
Decision
in
the
previous
meeting
that
was
not
clear
was
that
first,
we
get
a
demo
dossier,
miss
sorry
doc,
bankruptcy,
mister
or
domain,
and
we
did
separately
note
where
I'm
built
and
we
have
the
people
that
design
already
created
and
then
we
need
a
playground
so
that
we
can
set
up
the
demo
database.
Sorry,
the
demo
content
and
then
we
spin
off
instances
of
that
so
yeah.
E
And
there
and
I
I
think
these
pieces
already
in
motion.
You
know
the
the
technical
consideration
of
a
building,
the
tugboat
interface
I
think
is,
is
a
straightforward
site
building
configuration
problem
that
I'm
actually
even
comfortable
to
take
a
shout
out,
but
but
I
I've
I've
already
got
a
sandbox
that
they
work
in
torch
to
be
the
thing
that
would
be
demoed
now
they
have
a
better
understand
of
what
it
is.
E
I
can
continue
to
refine
that
we've
be
the
call
for
better
themes,
has
kind
of
gone
out
and,
as
I
forgot,
who
pointed
out
earlier,
like
what
people
seem
to
be
working
on
their
themes.
You
know
like
there's
some
renewed
interest
in
that,
which
I
think
is
a
good
and
positive
thing,
and
we
can
you
know
that'll
that'll
up
the
up.
The
bar
raise
the
level
for
things
and-
and
I
I
I
think
I
think
we're
not
very
many
iterations
away
from
from
having
a
satisfying
first-timer
experience.
D
D
Yeah
right
now,
all
of
the
the
entire
demo
on
bankruptcy
master
award
is
driven
by
the
tugboat
contribute
had
been
custom
code
and
now
it's
no
longer
custom.
It's
like
just
literally
running
the
tugboat
module
on
backdrop,
CMS
org,
and
so
what
this
might
end
up
doing
is
that
right
now,
it's
just
driven
to
just
have
one
single
repository
for
tugboat,
and
this
might
change
the
way
that
that
works
quite
a
bit.
D
But
that
does
mean
that
if
you
want
to
work
independently
of
what's
on
backdrop,
see
when
I
start
argue
up,
so
that
we
can
and
just
install
the
talk
about
module
and
I
sign
up
for
a
free,
tugboat
account
and
then
go
to
town.
You
know
make
all
changes
as
necessary
and
then,
when
it
comes
to
integrate
that
into
backdrop
CMS
org,
then
you
know
I,
depending
on
the
rock
take
in
it.
D
Used
when
he
was
doing
all
of
the
bankruptcy
messed
org
stuff,
he
was
just
he
just
built
a
nun,
a
normal
backdrop
website
and
then
eventually
like
we,
we
added
him
as
an
administrator
to
back
trip,
CMS
toad
org,
but
now
what
we
do
every
time
we
have
two
demos
is
we
make
a
new
release
of
the
tugboat
module
and
then
we
just
update
the
module
on
back
from
CMS
George
yeah.
There's
almost
nothing
custom
on
work
at
this
point
so.
D
C
D
Really,
okay,
you!
There
is
one
other
thing,
and
that
is
that
you
have
to
add
a
repository
to
your
tugboat
account
from
which
you
want
to
base
your
previews
and
so
right.
Now
there
is
the
backdrop:
ops,
slash
backdrop:
tugboat
repository
you
don't.
If
you
don't
have
permission
to
that,
then
you
can
fork
it
and
then
link
to
your
fork.
Man.
Yes,
then
you
can,
then
you
can
spin
up
as
many
backdrop
to
us
as
you
as
you
want
I
mean
within
the
limits
you
have.
Your
free
account
sounds.
D
B
D
Yeah
yeah,
so
the
reason
why
it
used
to
be
super
fast,
and
now
it's
not
is
because
previously
we
were
taking
a
demo
that
was
fully
built
and
just
empty
empty
of
all
content
and
we
were
just
making
a
copy
of
it,
and
so
it
was
exactly
the
same
as
before.
Now
it's
it
actually
runs
the
installer.
It
makes
a
copy
and
then
it
runs
the
installer,
and
so
the
additional
waiting
time
is
while
it's
running
the
Installer
and
it
needs
to
run
the
installer
so
that
right,
right
now
it
runs
the
Installer.
B
Because,
before
we
were
forcing
every
user
to
just
go
through
the
installer
themselves,
they
had
to
go
through
the
process
of
specifying
a
site,
name
and
so
on
and
so
forth,
and
what
we
wanted
to
avoid
is
what
we
wanted
to
achieve,
rather
was
to
get
them
straight
by
clicking
one
button
into
a
ready
environment
without
having
to
install
assuming
that
they're
the
people
that
will
be
demoing,
it
would
be
less
technical
about
it.
They
didn't
want
to
go
through
the
installation.
D
D
B
Just
really
really
quick
created
an
issue
about
moving
the
license,
txt
file
out
of
core
into
the
main
directory
and
the
only
the
only
reason
for
that
I'm
happy
to
like
Adam
I'm,
not
very
hard
on
it.
It's
just
that
it
automatically
pulls
that
if
it's
in
the
root
directory
and
puts
it
in
the
project
summary
on
the
side
burns
on
the
project-
and
it
shows
that
we're
GPL
but
yeah.