►
From YouTube: Backdrop Outreach - 2021/08/05
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).
C
A
A
To
get
it
live,
it's
it!
It's
cerveza,
I
don't
know
if
you
figure
got
it
yet
it
starts
recording,
but
then
it
turns
on
my
computer
like
10
seconds
later,
and
I
have
to
wait
until
it's
come
on
on
my
computer
and
I
muted
it
with
that
lag.
Otherwise,
we
get
weird
feedback.
So
welcome
everybody
to
the
weekly
outreach
meeting
for
august
5th
2021.
A
We
are
streaming,
live
on
youtube
and
let's
just
jump
in
and
do
a
quick
round
of
introductions.
I
am
tim
erickson
or
st
paul
tim,
I'm
in
deerwood,
minnesota
and
yeah
just
been
really
really
busy
lately.
So
continue
to
be
just
not
having
enough
time
for
backdrop.
So
let's
see
what
we
can
do
about
that
luke.
Do
you
want
to
go
next
sure.
B
C
Yeah,
I'm
sarveshri
and
I'm
in
walnut
cove
north
carolina
and
I'm
working
on
a
beginner's
guide
for
backdrop.
D
I'm
here
I
am
mentally
checked
out,
but
otherwise
I'm
hoping
to
be
back
soon
joining
from
oakland
california
yeah.
That's
it.
Let's
see.
Does
everyone
else
introduce
themselves
way
back
to
tim,
okay,.
A
A
I
we
have
an
agenda
here.
I
really
think
I
that
we
just
have
an
open
discussion
today,
as
we
have
been
it's,
it
doesn't
make
you
well
like
I
say:
let's
find
things
for
luke
to
do
and
keep
look
busy
because,
like
I
don't
need
new
things
to
do
right
now,
so
I
don't.
I
don't
want
to
create
a
longer
to-do
list
of
things
that
aren't
getting
done
for
myself,
but
if
we
can
pass
them
off
to
luke
or
luke.
B
I
want
to
make
some
intro
videos,
I'm
I'm
showing
off
the
the
green
screen
here,
which
is
why
I've
got
the
the
the
van
gogh
stuff
and.
A
Well,
luke,
if
you
have
time,
maybe
what
we
should
do
so
my
big
backdrop
thing:
it's
been
collaborating
with
sarvashri,
which
he
alluded
to
already.
A
We
have
been
for,
like
eight
or
nine
weeks
now,
we've
met
every
week
and
have
just
been
walking
through
the
steps
of
building
a
website
and
viewing
it
in
mind,
and
I
think
what
savagery's
been
doing
is
collecting
information
for
himself,
but
also
for
his
beginner's
guide,
to
backdrop
which
he's
writing
and
I
have
been
viewing
it
as
kind
of
a
dry
run
that
I
could
use
to
make
sort
of
an
outline
and
or
start
to
create
some
more
public
materials.
A
So
what
what
sarvajri
and
I
have
been
doing
has
been
very
specific
and
very
impromptu,
so
it's
pretty
crude.
We've
recorded
it
for
our
own
sake,
but
it's
nothing
that
I
would
share
with
the
public,
but
I
feel
like
it's
sort
of
a
practice
run
that
we're
kind
of
getting
to
the
stage.
A
Now,
where
I'd
like
to
to
go
back
and
say,
okay,
how
you
know,
how
did
this
go
and
you
use
it
to
sort
of
create
an
outline
for
a
second
pass,
where
we
maybe
do
some
more
structured
and
shorter
videos
that
are
more
to
the
point
and
combine
that
with
some
written
text
and
just
links
and
and
sort
of
create
a
beginner's
guide.
So
anyway.
So
that's
all
kind
of
abstract,
but.
C
A
C
C
C
So
that's
where
we
are
we
don't
we.
We
looked
at
trying
to
do
big
videos
but
videos
if
they're
any
length
at
all
soon
become
outdated
yeah.
C
So
we
didn't
want
to
create
videos
that
would
be
outdated,
so
we're
looking
at
link
snippets
if
it's
something
that
really
needs
video
in
order
to
understand
it,
then
we
should
have
a
video
for
it.
If
it's
something
that
can
be
learned
easily
with
just
text
and
screenshot,
then
that's
good
enough
for
many
things.
B
C
And
we
have
some
short
snippets
of
video
and
we
have
my
beginner's
guide,
which
is
a
summary
of
everything
that
we
want
to
put
in
it.
But
not
yet
everything
is
complete.
So
far,
so
we
we
don't.
I
don't
have
layouts
written
up.
I
don't
have
styling
written
up,
there's
a
few
things
towards
the
end
that
I
want
to
complete.
A
Can
I
interject
from
from
my
perspective
so
the
google
doc
and
the
videos
that
we
have
have
all
been
sort
of
just
internal
notes,
right
luke,
so
they
weren't
they're,
not
really
like
anything
that
could
be
useful
to
anybody
in
public
right
now.
We
we're
happy
to
share
them
with
you.
If
you
wanted
to
collaborate
with
us
on
this,
but
it's
this
has
really
been
improvised,
so
we've
gotten
together
each
week
sarvashri
and
I
and
just
sort
of
started,
recording
and
said:
hey.
A
Let's
add
some
views
to
our
website
and
it's
been
totally
improvised
and
unstructured
and
wandered
around
and
we've
hit
dead
ends
and
found
bugs
and
spent
30
minutes
trying
to
debug
something.
So
I
would
not
want
to
like
publicize
these
videos
for
anybody,
but
if
we
need
to
go
back
and
and
reference
them
we
can
so
we
started.
C
Off
we
started
off
following
the
drupal
pattern:
they
had
documentation
up
on
creating
a
website
with
drupal
for
a
farmers
market,
but
they
never
completed
it
as
far
as
we
can
tell.
A
Right,
the
the
drupal
8
user's
guide
talks
about
building
a
farmers
market
website,
but
I
don't
know
we
couldn't
find
any
like
finished
product
that
you
could
look
at
and
say.
Oh,
this
is
what
we're
trying
to
build,
and
so
our
goal
was
hopefully
to
to
to
walk
through
this
at
the
end.
To
have
that
finished
product
that
we
could
then
rebuild
in
a
sense
in
some
videos
and
and
but
but
have
you
know,
have
a
model
that
we
could
work
from.
C
And
then
we
could
also
share
the
website
with
new
users.
They
wanted
to
dig
into
it.
They
could
load
it
up
on
their
system
and
see
how
it
was
put
together.
Look
at
all
the
different
aspects
of
it,
so
they
have
something
a
working
model
that
they
could
use
as
a
pattern
for
creating
their
own
website.
A
So
I'm
thinking
luke
that,
if
you're
interested
and
then
creating
some
videos
that
maybe
you
could
we
could
meet,
maybe
we
could
bring
you
into
this
process.
I'm
ready
to
be
drafted
and
decide.
We,
you
know,
like
we've,
we've
sort
of
been
through
a
lot
of
the
things.
Sarvashri
still
has,
I
think
a
few
things
he'd
like
us
to
cover,
but
we've
been
through
and
done
a
lot
of
the
things
and
I'd
like
to
start
stepping
back
and
seeing.
A
So
that's
where
that's
at
what
do
you
think
sarvashri.
C
Luke.
You
have,
you
have
my
guide
and
we
can
point
you
to
the
google
doc
that
we're
working
with
and
we
can
send
you
copies
of
our
websites.
I
have
a
website
that
I'm
following
along
with,
but
tim,
he
has
a
farmer's
website
and
I
have
a
farmer's
website
and
we've
done
some
different
things
with
them.
C
A
C
A
Get
some
better
images,
make
it
a
little
bit
better
of
a
demo
site
and
the
other
thing
again
we've
talked
about
this
before
is
we
could
sort
of
a
little
very
roughly
used
the
drupal
8
user's
guide,
maybe
as
a
model
in
that
it
has
a
nice
outline
here
and
my
thought
was:
maybe
we
start
with
this
outline
but
then
thin
out
all
the
stuff
that
we
don't
need
clean
it
up,
maybe
add
a
few
sections
that
are
specific
to
backdrop
and
and
have
the
the
farmers
market
site
is
an
end
product
that
people
can
kind
of
look
at
and
say:
oh,
okay,
here's
how
I
build
each
piece
of
that
site,
but
we
welcome
input
or
ideas
on
that.
A
A
A
Yeah
I
do
and
it's
kind
of
a
complicated
tool.
I
tried
to
spin
it
up.
A
Yes,
they
they
use,
they
used
a
complicated
tool
for
for
developers
so
that
they
could
do
revisions
to
give
them
a
lot
of
power
to
do
revisions
and
to
have
multiple
people
different
submit
commits,
and
I
tried
to
get
it
working
locally
and
I
couldn't
get
the
tool
to
work.
So
it's
it's
in
the
footer
actually
of
every
page
of
the
guide.
It
says
this
page
is
generated
with
they
use
this
open
source
library
called
ascii
doc,
and
then
they
had
a
git
repo.
A
A
C
A
Well,
they
have
a
full
html
version,
so
if
we
want
to
link
to
it,
I
would
just
link
to
their
to
the
the
website
right
and
anybody
can
download
it
there.
So.
A
A
I
have,
as
is
as
a
so
the
social
media,
one
of
the
social
media
people
been
totally
off
base.
I
think
our
our
social
media
accounts
have
been
pretty
quiet
lately,
so
we'll
try
to
get
back
up
on
that
as
we
get
time.
A
If
anybody
has
time
to
write
blog
posts.
Obviously
we
have
a
whole
list
of
ideas,
but
just
have
been
lacking
the
people
with
time
to
do
them-
videos
luke.
That
would
be
great
if
you
had
some
time
to
do
some
videos
and
if
you
want
to
talk,
you
know
more
now
about
if
you
want
to
just
wrap
that
into
what
we're
doing
or
if
you
just
have
some
ideas
of
things
you
wanted
to
do.
B
Is
the
list
of
ideas
in
in
github?
Is
there
like
an
issue
for
them?
There
is
something
like
that.
There.
A
Is
an
issue
for
that
has
ideas
my
mirror
board?
Might
I
don't
think.
C
A
Specifically
has
video
ideas
that
has
blog
posts
and
and
social
media
stuff,
but
I
in
in
github
and
I'm
not
we
haven't
looked
at
this
again.
I
would
probably
have
some
new
ideas
in
the.
In
the
backdrop,
dot
org
issue
queue.
A
A
Some
of
these
this
this
use-
I
don't
I
mean,
there's
some
ideas
here
that
are
totally
useful,
but
this
is
way
out
of
date
and
you
know
we've.
We.
I
think
there
are
some
good
videos
about
layouts
out
now
here.
Let
me
put
the
link
in
soon
yeah,
if
anybody's
not
looking
at
it.
A
Why
don't
we
talk
right
now
about
some
ideas?
Well,
sarvashri.
Are
there
some
just
in
general
or
more
specific?
Are
there
some
other
video?
I
mean
view
modes.
I
think,
is
a
great
idea
for
a
video.
C
B
To
pull
the
trigger
on
having
to
do
with
development
and
deployment
like
not
so
much
once
you're
inside
the
platform,
but
you
know
the
development
in
a
local
environment.
I
was
gonna,
pick
lando
and
deployment
to
a
an
end
user
environment.
I
was
going
to
pick
pantheon
as
an
initial
thing,
but
but
would
eventually
try
to
look
for
a
more
generic
lamppost
and
then
in
particular.
B
B
B
C
C
B
Yeah,
I
I
I
find
the
away
we
go
pieces
is
sometimes
pretty
involved
so
so,
which
is
why
the
videos
there
like,
like
I,
I
feel
like
like
in
order
to
to
have
people
who
are
not
familiar
with
it,
find
their
way
through.
You
need
both
written
and
video
stuff.
You
need
the
written
material
to
be
able
to
get
a
a
overall
picture
of
it,
but
but
sometimes
you'll
read
something
and
and
then
try
it
and-
and
it
just
doesn't
look
the
way
you
know
it.
B
C
A
Yeah,
I
think,
to
do
a
video
for
one
of
the.
The
hosts
that
have
a
one-click
installer
might
also
be
helpful.
I
think
these
are
good
things
though
luke
that
aren't
you
know,
we've
been
making
some
how
to
use
backdrop,
videos
but
stuff
on
like
setting
it
up
on
the
server.
B
B
Six
or
seven
years
into
it,
I'm
still
kind
of
baffled
by
them,
like
I
it's
time
for
me
to
learn
I'm
confused
by
them
in
drupal
8
too,
but,
like
I,
I
find
myself,
you
know
wishing
for
the
the
days
of
drupal
7
and
features
back
when,
yes,
you
want
to
hated
it
at
least
understood
what
I
hated.
A
Yeah,
either
aaa
or
backdrop
I
I
have
yet
to
really
feel
like
config
management
is
making
my
life
easier.
I
have
kind
of
gotten
to
the
point
where
I
think
it
doesn't:
I'm
not
I'm
fighting
it
less.
B
Well,
well,
I
I'd
like
to
pull
the
pull
the
pieces
together.
You
know
document.
What's
there
and
in
the
process
you
know
perhaps
perhaps
nudge
the
implementation.
If,
if
there's,
if
there's
things
that
can
be
simplified,
you
know
make
the
case
for
for
how
and
and
why
that
should
happen.
D
The
beginning,
I
got
excited
when
tim
said
he
wasn't
excited
and
I
was
like
well,
someone
should
be
excited
so
yeah.
This
I
feel
like
this
is
a
really
common
part.
When
I
did
drupal
training,
it
was
like
at
the
end.
People
were
like
okay.
D
Well
now,
I
know
how
to
do
the
thing
but
like
how
do
I
take
care
of
it
long
term,
and
I
think
when
you
first
start
like
everything
is
all
it's
one
glob
and
then
once
you
deploy
it,
you
like
take
the
glove
and
you
deploy
it,
but
then,
after
that,
you're
going
to
be
making
changes
to
the
different
pieces
and
understanding
how
they
fit
together
and
how
they
should
move
back
and
forth.
That's
where
it
gets
really
messy.
D
If
you
do
it
wrong,
and
I
always
had
like
a
half
an
hour
at
the
very
end
of
the
training
session,
where
we
would
go
through
like
a
best
practices
environment
where
you'd
have
like
three
copies
like
on
pantheon
or
something
like
that
and
then
we'd
have
like
the
alternate
realities
where
it's
like.
Not
everybody
has
that,
and
how
do
you
do
it
when
you
only
have
two
copies
and
how
do
you
do
it
when
you
only
have
one
copy
and
trying
to
figure
out
how
how
to
make
like
how?
D
When
do
you
move
the
files
and
when
to
sync
configuration
in
which
direction?
And
how
do
you
not
overwrite
things?
Other
people
are
working
on
and
I
feel
like
every
one
of
those
questions
could
benefit
from
like
a
video
explanation,
like
real
world
scenario
of
when
you
might
need
to
use
something
like
that,
because
I
feel
like
talking
about
it
like
in
a
situation
like
this.
D
It's
really
easy
to
just
be
like
you
do
this
and
when
this
happens,
but
without
a
specific
example
of
what
that
is,
it's
really
hard
to
then
apply
that
to
your
own
scenario.
So
I
love
configuration
management
because
it
means
I
never
have
to
deal
with
like
features
and
features
in
drupal.
7
were
one
of
the
things
that,
like
always
got
kind
of
corrupted
in
a
way
that,
like
you,
couldn't
get
everything
back
the
way
you
wanted
it
in
backdrop.
D
It
is
easy
to
change
something
and
then
change
it
back,
because
you
aren't
dealing
with
that
painful
practice
of
getting
it
to
change
in
the
first
place.
So
it's
easy
to
accidentally
revert
stuff.
I
run
into
that
all
the
time
on
triple
and
drupal
nine
two,
where,
like
someone
changes
something
and
someone
else,
changes
something
and
accidentally
unchanges
the
first
thing-
and
that
is
I
it
is
you
know
when
you
make
something
too
easy:
you're
gonna
change
everything
all
over
the
place,
but
I'd
rather
have
that
than
have
this.
D
Like
frustrating
experience
like
I
just
can't
get
my
sight
to
do
what
I
wanted
to
do,
which
is
where
I
felt
like
we
were
before.
D
I
also
feel
like
moving
a
database
around
is
something
that's
pretty
dangerous
and
there's
was
like
an
alternative
to
that,
like
you,
don't
have
to
like
freeze
the
site
and
move
database
move
it
back,
and
I
feel
like
being
able
to
do
all
of
my
deploys
with
that,
like
the
configuration
in
code
also
makes
it
really
easy
to
like
deliver
a
new
feature
where
it's
like:
here's
the
content,
type
and
the
view
and
the
page,
it
appears
on
like
in
one
piece
where
you
don't
have
to
be
like:
okay.
D
B
C
D
That
so
I've
got
to
deploy
half
of
it
and
then
make
the
content
and
then
work
on
the
view
and
then
deploy
the
view,
and
that
was
always
really
hard
too.
Where
I
feel
like
invector
can
be
like
here's
the
whole
thing,
and
then
I
can
do
it
all
once
I
know
it's
done,
which
makes
it
a
little
bit
easier
too.
D
So
I
feel
like
without
use
cases
where
these
things
are
valuable,
like
if
you
build
a
site
and
you
deliver
it
and
then
you're
like
done
like
there's
no
benefit
to
having
configuration
management,
because
you
could
have
just
done
that
originally
or
if
you
have
a
site
where,
like
nobody's
working
on
it,
except
for
you,
like
you,
create
the
content
you
don't
have
to
worry
about.
D
That,
like
database
is
out
of
sync
on
your
local
site
versus
live
site
problem
and
you
can
copy
it
down
and
do
whatever
you
want
copy
it
back
up
like
wordpress
people
do
all
the
time
and
it's
not
an
issue.
So
I
think
that
yeah,
it's
a
feature
that
only
benefits
those
of
us
who
use
that
workflow,
but
if,
once
you
figure
it
out
and
like
learn
to
lean
on
it
like
I
have,
it
starts
to
become
really
valuable
to
you
like.
D
Oh,
I
can
do
this
all
the
time
and,
like
I
just
fill
this
thing
and
config
and
deploy
and
sync-
and
it's
done-
and
I
can
do
that
like
eight
times
in
a
day
for
eight
different
sites,
and
it
just
makes
everything
much
faster.
So
it's
the
kind
of
thing
where
I'm
hoping
that
people
who
are
new
to
it,
don't
necessarily
need
to
understand
all
of
it,
because
you
don't
have
that
use
case.
D
Where
you
need
it
and,
like
tim
said,
you
learn
to
work
around
it
and
you're
fine,
but
like
maybe
you
don't
love
it
and
then
one
day
tim
will
end
up
with
some
like
huge
horrible
monstrous
sight
that
he
has
to
maintain
and
he's
like.
Okay,
I'm
gonna
figure
this
out.
I'm
gonna
set
this
up
and
it's
gonna
be
way
less
painful
and
then,
like
six
months
and
he'll,
be
like
hey.
I've
been
spending.
D
Half
as
much
time
fighting
with
my
configuration
deploys
as
usual
and
then
it'll
get
better
so
yeah
I
feel
like
I
have
a
couple
of
big
sites
that
really
benefit
from
them,
but
most
of
my
sites,
it's
just
like
because
I
benefit
from
it
personally,
like
it
takes
less
time.
For
me,
that's
the
reason.
D
B
Well,
like
cmi
cmi
feels
like
like
a
lot
of
things
in
drupal
have
always
felt
to
me.
It
feels
like
it's
90
percent,
finished,
really
useful
solution
and,
and
that,
like
that,
what
feels
like
the
last
10
it
isn't
done,
and
I'm
aware
from
just
you
know,
one
of
the
common
tropes
of
software
development
is
that
is
that
that
last
ten
percent
is
you
know
ninety
percent
of
the
work.
B
So
so
it
can
feel
like
it's
almost
done
where
it's
not
in
fact,
actually
almost
done
yeah
but
but
but
I
I
think,
I
think,
sort
of
recognizing
you
know
trying
to
figure
out
what
the
what
the
80
80
20
options
are
for
that
that
last
bit
of
pain
well
I'll
throw
an
example
like
when
I,
when
I
do
cmi
things
these
days,
it
either
works
or
it
doesn't
and
sort
of
it
doesn't
is
the
one
that
really
gets
to
me
because
I'll
I'll
do
something
and
it'll
just
fail,
and
I
forget
what
the
error
messages
are,
but
it
just
stops
and
I'm
thinking
like
come
on
computer
you're
even
telling
me
that
you
did
like
you,
know,
53
out
of
the
55
things.
D
Yeah,
the
problem
is
that,
like
we
don't
know,
if
those
two
are
going
to
cause
fatal
errors
or
not
so
it's
safer
to
be
like
your
site's
working
right
now,
let's
just
leave
it
in
a
working
state
rather
than
being
like
okay,
we
did
53
everything's,
broken
good
luck
and,
like
you,
don't
have
a
user
interface
to
like
choose
for
them.
They're
fine
they're,
just
view
configuration
changes,
nothing's
different,
but
because
we
can't
tell.
C
D
C
D
Should
be
an
error
message
that
tells
you
exactly
what's
wrong
and
since
we
launched
we
have
made
a
lot
of
improvements
to
those
error.
Messages
they're
still
not
always
great,
but
we
have.
I
have
that's
been
one
of
the
things
where
you
know.
If
I
get
an
error
message
now,
I
don't
know.
What's
going
on,
I
got
really
mad.
D
Like
this
is
completely
useful,
unuseful
yeah,
but
I
do
think
that
that's
something
that
we
we
should
keep
working
on
like
every
time.
Someone
comes
into
an
error
message
where
it
doesn't
give
you
like
this
is
what's
wrong,
and
this
is
how
to
fix
it.
That's
a
big
problem
and
then
I
think
that
the
big
piece,
that's
missing
from
making
configuration
management
a
100
feature
tool
is
the
piece
that
tim
has
been
rallying
for
for
a
really
long
time,
which
would
be
like
a
partial
import
so
that
you
don't
have.
C
D
Like
re-import
all
of
your
configuration
every
time-
and
we
know
that-
and
that
is
90
of
the
work,
but
we
have
been
making
baby
steps
toward
it.
Like
we've
got
this
core
issue,
that's,
like
you
know,.
B
B
Yeah,
well
I
mean
I
mean
one
one
thing
that
didn't
occur
to
me:
I've
actually
I've
actually
seen
and
been
part
of
of
workflow
environments
that
use
backup
and
migrate
as
as
the
sole
migration
tool
and
just
like
move
the
database
back
and
forth,
and-
and
I
was
thinking
with
in
terms
of
a
backdrop
which
has
back-to-back
migraine-
where
I
do-
I
use
the
you
know-
I'm
one
of
the
few
people
that
ever
tries
to
do
the
the
internal
gui
configuration
backup
and
migrate.
Well,
no,
no
for
for
for
cmi
for
configuration
management.
B
F
D
F
D
D
B
D
Place
like
so
I
I've
been
getting
him
to
help
me
with
a
lot
of
my
stuff
lately,
because
I've
been
a
little
underwater,
and
so
I
have
an
issue
specifically
like
me
and
justin
and
I'll
like
drop
a
link
to
the
drupal
or
the
backdrop,
issue
queue
and
be
like.
Can
you
please
fix
this
and
then
he
goes
and
fixes
my
problems?
D
D
You
can
do
from
your
backdrop
site
and
it's
like,
but
it
really
needs
to
do
all
the
things
I
think
he's
he's
got
some
of
my
sites
working
with
backup
and
migrate
without
the
issue
resolved
because
he
figured
out
how
to
define
like
a
files
directory
that
was
outside
of
your
doc
root
and
so
backup.
My
great
treats
are
like
files,
so
he's
got
like
a
work
around
in
there
yeah.
I
really
want
it
to
show
up
in
the
user
interface
as
being
like
database
files.
D
D
I
agree
that
there
are
pieces
like
that,
where
you
know
we've
got
stuff
from
drupal
where
we
didn't
have
cmi
and
we
don't
have
nice
integration
with
all
of
the
cmi
stuff,
and
I
feel
like
that's,
also
going
to
take
some
time
to
come.
Like
I
don't
know,
I
was
like
node
queues
or
there
was
something
that
like.
I
would
expect
to
be
configuration
and
backdrop,
and
it
wasn't-
and
I
was
like
oh
no
to
self.
I
should
come
back
and
fix
this
later,
but
it's
been
like
a
year.
It.
B
Happened
well
like,
like
I
find
myself.
I
was
in
a
triangle
this
week
where,
where
I've
I
I've
decided
to
to
put
css
injector
into
area
into
the
flow,
and-
and
so
so
I
I
forget,
where
you
know,
I've
got
a
thing.
I've
got
a
local
landlord
thing,
I'm
like
okay,
so
there's
actually
three
things
that
have
to
go
up
in
in
some
sense
of
order.
I
mean
the
code
changes
right.
B
B
I
could
see
that
as
being
sort
of
a
separate
step,
but
but
then
they're
trying
to
figure
out
like
which,
how
the
how
the
configuration
that
was
that
was
in
code
in
in
you
know
in
cmi
versus
pieces
that
seem
configurationy
that
are
actually
data
and
yeah,
and
that
seems
to
be
like
an
ongoing
thing.
It's
like
it's
like
okay
is.
Is
this
thing
that
I'm
interested
in
right
now
like
like,
which
which
of
the
classes.
C
D
Yeah-
and
this
is
a
notorious
problem
because
we
came
from
drupal
where
it
didn't
matter
like
it
was
all
treated
the
same
way.
So
people
didn't
distinguish
like.
Is
this
configuration
or
is
this
data?
And
so
you
have
systems
like
taxonomy,
which
are
systems
for
categorization,
and
it's
like
well.
D
Sometimes
that
categorization
is
configuration
for
the
rest
of
your
content,
but
sometimes
it's
just
more
content
and
it's
like
meh,
I
don't
know,
and
so,
when
we
became
backed
up
with
configuration
management,
we
had
to
sort
of
draw
a
line
and
be
like
your
vocabulary
is
configuration,
but
your
terms
are
content
and
when
we
make
that
distinction
as
like
a
module
developer,
the
way
we're
supposed
to
convey
that
to
you
is
by
changing
the
label
button.
So
if.
D
Configure
it's
going
in
configuration
if
you
click
about-
and
this
is
edit
it's
going
in
your
database,
but
because
we
came
from
drupal
where
all
of
the
button
labels
were
all
mixed
up
if
you're
porting
a
module
that
had
a
button
that
said
configure
and
that
content's
going
in
the
database
and
had
a
button.
That
said
edit
and
the
content
is
going
into
configuration.
C
D
But
this
is
a
great
example
of
like
is
that
css
code
that
you're
writing?
Is
it
configuration
or
is
it
content
because
in
reality,
it's
code
and
that's
not
where
you're
storing
it
right?
So
the
person.
D
Has
to
make
a
distinction
and
be
like:
where
does
this
go
and
you're
you're,
absolutely
right
that
if
you
spend
a
lot
of
time
working
on
that
on
your
local
site
and
want
to
deploy
it
you're,
not
like
what
which
piece
is
it
in
and
if
they
didn't
do
a
good
job
in
the
interface
of
telling
you
where
it
is?
The
only
way
you
would
know
is
to
open
the
code
and
read
it
and
say
like:
where
is
this
saved
and
that's.
E
D
Yeah
yeah
yeah,
and
so
the
safe
thing
to
do-
and
this
is
what
I
do
sometimes
is
just
install
the
module
on
your
local
site-
make
sure
it
doesn't
break
anything.
D
Add
the
code
for
the
module,
deploy
the
code
and
then
build
everything
on
your
production
site
turn
it
on
create
the
stuff
save
it.
Because
now
you
know
it's
all
there.
The
problem
is,
though,
you
don't
want
to
write
css
code
on
your
production
site
without
knowing,
if
it's
going
to
work
or
not
right.
So
what
I
might
do
is
like
write
the
code
on
my
local
site,
save
it
make
sure
it
works
and
then
copy
and
paste
from
that
field
to
the
live
site.
D
And
then,
if
you
do
like
configuration
export,
you
could
compare
and
be
like.
Is
there
any
difference
between
the
files
that
are
there
before
and
the
files
that
are.
D
Are
you
know
that
the
configuration
is
where
that
stuff
is
saved
and
if
they
aren't,
then
it's
in
the
database
somewhere
but
yeah?
That's
we
need
to
do
a
better
job
of
conveying
to
people
where
that
is.
Information
is
triggered.
B
Yeah,
but
so
so
try
trying
to
figure
out.
You
know
an
actionable
path
to
make
things
better
without
without
insisting
that
you
boil
the
ocean,
and
you
know,
fix
everything
all
at
once.
I
I
think
maybe
ferreting
out
error
messages
that
they
don't
tell
you
precisely
enough.
What
happened
is
it's
perfect
because
one
of
the
things
I
I
mean
I'll
give
credit
to.
I
guess
it's.
You
know
in
my
my
little
triage
trio
thing
here
when
I
I
think
I
did
configuration
first
and
it
told
me
like
there's
not
a
module
for
this
yeah.
D
B
F
D
Don't
do
the
way
that
you
would
tell
it
don't
do
this
one,
it's
really
easy
if
you're
on
the
command
line
or
have
an
ftp
tool
open.
So
I
do
just
delete
the
file,
but
if
you
don't
have
those
tools
like
there's
no
user
interface,
for
that
there's,
no,
you
know
because
our
configuration
step
is
just
a
sync.
It
doesn't
have
a
like.
D
Should
I
copy
these
files?
Yes,
no
option
into
it.
That
could
be
something
we
could
add.
That
could
also
be
something
that
could
be
like
a
standalone,
contrib
module
that
could
clean
up
that
interface
a
little
bit
because
I
don't
know
like
in
a
perfect
world
you'd
never
get
into
that
scenario
in
the
first
place,
but
I
do
agree
that
it
happens
to
all
of
us,
but
yeah.
D
It's
usually
because
there's
something
I
forgot
to
do
earlier,
like
oh,
I
forgot
to
synchronize
my
house
before
I
started
or
something
like
that,
and
that
might
be
another
thing
that
we
should.
You
know,
make
sure
people
could
do
more
easily
like
check
that
through
some
kind
of
error
somewhere.
If
it's
not.
B
Or
one
thing
you
know
rather
than
deal
with
with
all
the
all
the
permutations
of
the
way
people
might
approach
this.
If
we're
willing
to
to
be
opinionated
about
it
and
say
you
know,
when
you
do
this,
like
do
them
in
this
order,
do
the
code
first,
do
the
configuration
do
the
data
and
and
and
that
way
at
least
at
least
a
I
I
don't
know,
I'm
I'm
picturing.
B
You
know
each
step
kind
of
knowing
what
the
step
before
it
was
and
said
like
have
you
done
this
before
you
know,
dude
don't
do
this
until,
but
but
again
that
that's
actually
opening
up.
I
even
as
I'm
trying
to
describe
it,
I
can.
I
can
hear
I'm
saying
well
what,
if
what
if,
if
then,
if,
then,
if
then.
D
Yes,
and
I
think
that's
something
we
had-
we
had
taken
into
consideration
with
our
configuration
like
some.
Some
of
them
have
dependencies
right
but,
like
your
fields,
depend
on
the
content,
types
that
they're
attached
to
stuff
like
that,
but
there
are
it's
sort
of
like
an
infinite
world
and
contrib
of
how
things
relate
to
each
other
because,
like
if
you
have
a
reference
field
right,
not
only
does
that
depend
on
the
content
type
it's
on,
but
it
depends
on
the
content,
type
of
thing
it's
referencing
and
so
then
you're
like
okay.
Well,
what?
D
If
you
I
don't
know
I'm
just
making
stuff
up
now,
but
that
you
can
get
into
the
point
where
things
get
really
complicated
and
we
might
that
might
work
it
might
not.
I
don't
know
that
we
have
that
or
that's
been
tested,
but
trying
to
build
that
dependency
tree
is
hard
all
right.
I
I
do
think
that,
like
what
I've
been
talking
about,
this
whole
time
is
like
only
configuration
and
what
you
just
added
is
like.
D
D
You
can
do
configuration
without
so
yeah.
I
mean
so
like
this
thing.
You
just
talked
about
with
having
a
module
not
exist
right.
If
you
have
a
configuration
file
that
contains
data
for
a
module
that
doesn't
exist,
we
know
it's
safe
to
ignore
that
configuration
file
because
there's
nothing
on
the
site.
That's
going
to
run
it
right.
That
could
be
something
where
our.
What
did
you
call
it?
Opinionated
decision?
D
Is
that
we're
just
gonna
throw
that
away
we're
gonna,
throw
an
error
and
say
we
didn't
import
this
because,
but
we
can
just
throw
it
away
and
keep
going
so
there
could
be
some
stuff
like
that,
where
you
know
we
can
make
opinionated
decisions
and
carry
on
rather
than
being
like
hold
on
a
minute.
Did
you
mean
to
do
that?
D
A
Well,
the
other
problem
with
that
error
is
that
it
stops
the
process
for
one
module
and
then
you
fix
that
and
then
it
stops
it
for
another.
You
know
if
you've
got
five
modules
that
aren't
there.
You
have
to
go
through
the
process
five
times
before.
So
that's
one
of
the
reasons
that
that
error
is
so
frustrating
is.
A
D
D
Think
so
I
think
tim
or
luke
just
made
me
have
the
idea
about
being
opinionated.
One
thought,
though,
is
that
oh
no,
you
just
talked
about
this
tim
like
if
there.
If
there
are
a
bunch,
we
just
thought
all
the
messages
and
at
the
end
be
like
we
didn't
do
this
and
then
you
can
go
back
and
do.
C
D
Thing
I
was
thinking
is
like
we
wouldn't
want
to
like
lose
lose
the
files
right
so
rather
than
deleting
them
from
the
sync
directory.
We
just
skip
it
and
then
that
way,
if
you
just
push
the
button
again,
it'll
still
be
there.
Originally,
I
was
thinking
you
could
just
throw
the
whole
file
away,
but,
and
that
doesn't
make
any
sense.
So,
okay,.
B
Yeah,
I
mean,
I
think,
having
errors
show
up,
I
mean
that's
just
part
of
life
like
like
half
half.
You
know
95
percent
of
the
drupal
sites
out
there.
If,
if
you
go
to
to
the
the
the
report,
it'll
be
like
this
is
wrong.
This
is
wrong.
This
is
like
10,
things
are
wrong,
like
yeah,
it
works
and-
and
you
know,
you've
got
the
option
to
clean
them
up,
but
you
know
you
also
have
the
option
to
not
clean
them
up.
A
And
if
it
let
me
first,
let
me
the
time
is
up
for
this
meeting,
and
this
is
all
part
of
our
live
meeting.
Let's
just
wrap
this
up
and
maybe
tie
it
back
to
outreach
just
in
this
that
we
got
off
on
a
discussion
about
sort
of
just
config
management
in
general.
I
think
the
outreach
aspect
of
this
is
where
we
started
luke,
which
is
the
value
of
of
more
documentation
and
videos,
and
and
if
we
can
get
more
people
using
config
management
and
feeling
comfortable
with
it.
A
I
think
one
of
the
reasons
that
it
doesn't
get
a
lot
of
attention
right
now
in
terms
of
making
it
better
is
a
lot
of
people
are
just
kind
of
working
around
it
because
they
haven't
become
masturbate.
I
I
you
know.
I
want
to
qualify
my
earlier
lack
of
enthusiasm,
not
as
like
that
I
don't
like
it.
It's
like.
A
B
Help
me
go
ahead
kind
of
kind
of
what
I
was
suggesting
in
you
know
when
I
was
kind
of
volunteering
to
document
stuff
is
it
is
it's
sort
of
the
a
usable
step
in
terms
of
solving
the
overall
problem
like
like,
rather
than
like
sit
down
and
cry
like?
I
wish
it
was
like
this.
B
A
Okay,
well,
let's
end
this
meeting,
it's
exactly
on
the
hour
time
for
the
next
meeting
to
start
and
then
we
can
keep
chatting
if
we
want
so
but
officially
signing
off
from
the
outreach
meeting.
Hi
everybody
bye
internet.