►
From YouTube: 2022/05/12 Backdrop Outreach 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-
this
is
the
backdrop
bi-weekly
outreach
meeting
today
is
thursday
may
12th
in
most
of
the
world
13th
in
some
parts,
as
is
our
practice,
we
will
go
around
the
room.
Everyone
will
brief
introduction
and
pick
the
next
person
to
introduce
I'm
robert
line
button
folder
on
the
internet,
coming
to
you
from
out
in
california,
pass
the
baton
over
to
martin.
D
E
Sorry
got
something
in
my
throat,
I'm
tim
erickson,
I'm
st
paul
tiam,
I'm
in
deerwood,
minnesota
and
being
really
sort
of
busy
and
distracted
lately
and
yeah.
We
have
a
our
next
1.22
release
coming
out
on
sunday,
so
that
has
been
taking
up
some
of
my
backdrop
time
so
yeah,
I
guess
we
did.
Did
we
get
joe
and
stuff
yeah?
We
did.
I
heard
joseph
okay.
E
This
is
again
our
weekly
outreach
meeting,
jan
is
jen
and
nate
are
out
of
town
this
week,
so
they
won't
be
at
either
meeting.
E
Irena
tried
to
get
to
this
meeting
and
I'll
just
really
quickly
pass
along.
I
think
she
just
wanted
to
kind
of
congratulate
us
on
a
couple
of
good
months,
outreach-wise
in
terms
of
some
really
good
blog
posts
out
there.
In
the
last
two
months,
we've
gotten
the
atten.
What
the
company
has
done,
some
nice
blog
posts
about
their
upgrade
a
backdrop
or
two
of
drupal
seven
site
to
backdrop
for
stanford
irena
has
written
two
blog
posts
that
include
backdrop
on
the
pantheon
website.
E
She
mentioned
talk
at
drupalcon
about
backdrop,
but
I
was
not
there
and
she
didn't
have
time
to
elaborate
on
that.
So
I'd
be
curious
to
hear
what
I
haven't
really
heard
much
about
what
if
any
talk
there
was
at
drupalcon
about
backdrop
I
mean
I'm
sure
it
came
up,
but
I'd
love
to
hear
more.
If
anybody
knows
any
rumors,
let
us
know
some
some
others
were
there.
Did
you
anything
else
that
irena
mentioned
martin?
Do
you
remember.
B
No,
I
don't
remember
anything
else.
I.
E
There
have
been
some
interesting
discussions
in
twitter
there's
one
guy
in
particular,
who
was
in
a
couple
of
occasions
said
he
really
wished
that
backdrop
and
drupal
would
collaborate
to
create
some
kind
of
drupal
classic,
and
I
have
some
of
you
probably
noticed
the
topic
I
opened
up
in
zulu.
E
Basically,
I
I
actually
wrote
a
blog
post,
didn't
I
no
a
forum
post?
I
don't
know
that
it's
gotten
much
of
a
response.
I
wrote
a
forum
topic
where
I
talked
about
what
that
collaboration
might
look
like
specifying
that
I
don't
think
we're
in
the
backdrop,
is
interested
in
being
absorbed
back
into
drupal,
but
if
it
serves
the
need
of
the
community,
I
think
that
there
are
opportunities
for
backdrop
and
drupal
to
work
together
to
make
the
upgrade
process
easier
in
order
to
provide
confidence
in
to
drupal
7
site
owners.
E
That
backdrop
is
a
viable
option
that
to
me
that
that
seems
at
least
worth
exploring
whether
or
not
the
drupal
community
will
be
receptive
to
that
and
I
and
when
I
say
the
drupal
community,
I
mean
the
leadership.
E
I
know
that
some
members
of
the
community
are
open
to
that
idea,
but
whether
or
not
the
leadership
would
be.
Is
the
question
so
but
anyways
that
there's
been
a
little
bit
of
public
discussion
on
twitter,
about
all
of
that,
which
I
think
is
interesting
and
yeah
and
good
for
our
outreach.
B
We
got
a
few
mentions
on
linkedin
with
regards
to
the.
B
E
B
E
Well,
I'm
going
to
jump
in
here.
Sarvashri
shared
the
link
to
drupalcam
asheville,
and
since
our
last
outreach
reading,
it
has
been
confirmed
that
we
are
doing
a
training.
E
Justin
submitted
a
training
proposal
to
drupal
camp
bashfield
and
they
have
accepted
that
they
have
also
encouraged
us
to
submit
backdrop
session
topics
for
drupal
camp
asheville.
We
have
one
of
the
key
organizers
for
triple
camp.
Well,
I
shouldn't,
I
should
say
more
than
one
of
them
more
than
one
of
them
are
have
been
very
supportive
of.
If
you
look
at
the
list
of
organizers
for
for
drupal
camp
asheville,
several
of
them
have
been
to
backdrop,
live
events
and
been
very
supportive
of
us
in
the
past.
E
One
in
particular
has
actually
you
know,
written
modules
or
reported
modules
for
from
drupal
to
backdrop.
E
So
I
think,
there's
a
lot
of
support
for
us
at
drupal
camp
nashville
and
it
is
an
opportunity
for
us
to
promote
you
know,
sort
of
the
first
chance
for
people
to
go
to
an
event
in
two
years
with
backdrops
or
the
present
and
there'll
at
least
be
a
training,
if
not
more
than
that,
I
don't
know
other
than
justin
justin's.
The
only
one
that's
committed,
I
know
sarvashri
is
not
too
far
away
and
who
knows?
E
Maybe
if
some
other
of
us
go,
that
will
lure
him
to
triple
camp
we'll
asheville,
but
I
have
it
on
my
list
of
things
that
I
would
really
like
to
do
this
summer,
but
I'm
just
not
sure
I
can
swing
it.
Yet.
E
We
also
have
drupal
camp
colorado
on
our
on
our
calendar
list.
I
think
that
jen
might
have
agreed
to
do
a
training
or
something
in
colorado,
but
this
is
unofficial,
but
not
I
think
she.
If
anybody
was
at
the
meeting
last
week,
didn't
she
mention
something
about
that.
Anybody,
remember
no
okay.
We
do
have
a
number
of
supporters
in
colorado,
so
that's
a
good
place
for
us
to
go.
E
Okay,
martin,
I
know
you
said
you
might
have
to
cut
out
in
a
little
while,
but
you
wanted
to
talk
about
promoting
the
next
release.
So
backdrop,
1.22
comes.
B
B
So
I
think
that
the
cards
one
is
a
good,
is
a
good
one
to
hook
on,
which
is
why
I
was
asking
I'm
not
sure
that
there's
a
lot
of
the
others
are
quite
kind
of
small
and
not
really
kind
of
headline
grabbing
type
things
I
mean
it.
B
It
all
sort
of
adds
up
to
constant
improvement,
which
is
a
good
story
in
itself,
but
unless
anyone
thinks
that
there's
anything
else
that
that's
what
I'm
kind
of
going
to
go
with,
it
would
be
really
good
if
we
had
a
if
we
had
a
recipe
that
we
could
say
and
if
you've
already
got
a
backdrop
site,
here's
what
you
can
do,
but
I
don't
know
if
you'll
it
might
be
a
bit
too
much
to
have
for
you
to
have
time.
For
that.
E
Just
to
elaborate
make
sure
everybody
understands
martin's
been
asking
about
whether
or
not
we
could
have
a
recipe
for
that
feature.
The
cards
feature.
I
assume
the
recipe
would
involve
a
front
page
view,
so
that
somebody
on
an
existing
backdrop
site
could
just
sort
of
install
the
recipe
in
half,
because
because
this
new
cards
feature
which
we're
going
to
have
in
the
next
backdrop,
is
only
for
new
installations,
it
will
not
affect
existing
sites.
E
My
you
know,
my
gut
reaction
to
this
idea
is
that
existing
sites
have
already
you
know,
aren't
necessarily
likely
to
want
like
a
new
feature
like
this,
because
it's
so
specific
right,
but
that
could
be
wrong
and
the
more
I
think
about
it.
I
think
there
could
be
some
pr
value
in
it,
even
if
it
isn't
that
useful,
practically,
even
if
most
sites,
you
know,
wouldn't
really
want
to
add
this
as
a
recipe
it.
E
E
How
big
a
deal
is
this
I
I
I
mean
I
would
love
like
if
let's
say
we
to
me
the
fact
that
drupal,
the
backdrop
is
gonna,
look
different
out
of
the
box
in
a
noticeable
way
is
a
big
deal
and
I'm,
but
I
mean
it
like
if
we
had
an
entirely
new
front-end
theme,
that
would
be
a
much
bigger
deal,
but
this
is
still,
I
think,
kind
of
a
big
deal,
but
I
don't
know
if
it's
a
big
deal
like
promotable.
E
I
mean,
I
think
it's
a
big
deal
in
the
sense
that,
like
people
looking
at
backdrop,
are
going
to
just
have
a
more
pleasant
experience
when
they
arrive
at
it,
but
is
it
a
big
deal
that
we
could
promote?
Like
I
mean
for
sure,
we're
gonna
mention
it.
I
just
don't
know,
I'm
I'm
looking
for
feedback
on
how
big
of
a
deal
people
think
and
and
like
whether
you
know
what
the
pr
value
is.
B
I
think
it
I
think
it
is
because
it's
I
I
think,
the
one
of
the
best
things
for
cards.
I
guess
is
it's
a
way
to
kind
of
showcase
particular
products,
services
or
achievements,
or
things
like
that,
so
it's
got
kind
of
broad
range
of
use,
cases
that
I
think
it
either,
even
if
it's
even
if
people
think
well.
I
wouldn't
do
it
quite
like
that,
but
I
can
see
a
way
to
do
it.
It
it
fires
the
imagination
beyond
just
the
the
kind
of
it's
a
content
management
system.
B
E
So
that
question
is
an
interesting
sarvashri
in
that
to
me.
There's
actually
two
completely
different
things
aspects
to
this
new
feature
that
in
some
ways
are
unrelated
and
and
some
people
are
really
excited
about,
for
example,
the
changes
to
the
front
page
and-
and
I
think
those
changes
you
know
in
ways
are
independent
of
the
new
card
content
type.
E
We
used
the
introduction
that
the
cards
themselves
is
a
new
content
type
which
is
not
just
about
the
front
page
at
all.
The
the
new
card
content
type
is
a
feature.
That's
that's
just
sort
of
a
built-in
to
backdrop
which
can
help
you
independent
or
on
the
front
page
either
way.
E
D
E
It's
not
using
recipes
at
all
what,
but,
but
we're
using
recipes
to
make
it
backward.
E
Basically,
what
recipes
are
are
just
modules
that,
let
you
add,
features
like
the
two
module
recipes
we
currently
have
are
frequently
asked
questions
or
testimonials
right
and
they're,
basically,
just
modules
that
add
content,
types
and
views
to
your
website,
and
these
are
something
that
really
have
been
possible
in
backdrop
for
a
long
time,
but
they
became
much
easier
about
six
months
ago
or
nine
months
ago,
but
but
nobody's
really
using
them.
E
Yet,
and
the
point
was
we:
could
there
there's
this
new
content
type
in
that's
in
news
sites
for
backdrop,
and
some
people
might
be
saying
well
I'd
like
that
new
content
up
on
my
old
backdrop
site?
Well,
they
could
just
build
it
themselves,
but
this
is
a
chance
for
us
to
say.
D
Websites
with
a
focus-
I
guess:
what
do
you
call
those
when
you
have
a
ready
to
go
website
drupal
had
a
name
for
it.
Distribution
distribution
so
could
could
recipes,
create
distributions.
C
I'm
talking
too
much
to
somebody
else
want
to
answer.
I
think
I
think
the
correct
answer
is
sort
of
it,
so
enabling
a
module
allows
you
to
do
all
the
same
things
that
you
could
do
in
an
installation
profile,
so
you
could
have
a
module
or
a
recipe
that
is
basically
exactly
the
same
features
as
your
distribution
and
just
enable
the
module
in
order
to
get
that
set
up.
B
D
D
D
C
A
big
problem
that
people
ran
into
in
the
past
with
distributions
is
that
they
sort
of
lock
you
in
and
you're,
essentially
dependent
on
the
distribution
maintainer
for
when
you
get
updates
to
back
drupal
or
your
modules
right.
So
a
lot
of
distributions
actually
ended
up
being
really
bad
for
beginners.
Because
of
this
lock-in
effect.
D
C
D
C
D
C
D
A
E
Because
when
you
say
things
like
that,
a
lot
of
people
would
want
the
problem
is
that
I
don't
know
that
they're,
we
don't
know
what
a
lot
of
people
would
want.
Right
and
people
want
very
different
things,
and-
and
that's
one
of
the
reasons
why,
if,
if
there
were
something
that,
like
a
majority
of
people,
wanted
that
you
know,
we
might
just
put
it
into
core
the
problem.
Is
people
use
backdrop
for
so
many
different
purposes?
E
That
I
mean
even
you
take
a
massage
therapist
right
and
you
say
well
that
that's
a
use
case,
but
it's
still
kind
of
a
narrow
use
case
compared
to
the
overall
usage
of
backdrop
so
figuring
out
what
it
is.
People
want
it's
a
challenge
in
itself
and
even
then
people
really
what
they
want
is
the
ability
to
customize
those
things
and
the
problem
is
in
using
a
recipe
I
mean.
If
you
build
it
yourself,
you
better
understand
how
it
was
that's.
E
One
of
the
problems
I
had
with
distributions
is
that
if
I
start
with
a
distribution,
I
push
a
button
and
it
implements
a
whole
bunch
of
features,
and
I
didn't
know
as
a
beginner,
I
didn't
know
how
those
features
got
there,
so
it
was
hard
for
me
to
change
them.
Whereas
if
I
went
back
and
sort
of
tried
to
rebuild
those
features,
then
I
would
sort
of
learn
about
them
as
I
built
them,
and
it
was
easier
for
me
to
modify
them.
E
So
I
you
know,
I
don't
know
that
recipes
or
distributions
are
great
learning
tools,
if
anything
may
be
the
opposite,
but
they
are
helpful
if,
if
you
can,
if
they,
if
they
meet
your
exact
use
case
right,
if
if
the
recipe
is
perfect,
it
gives
you
exactly
what
you
want.
Then
they're
really
helpful,
because
now
you
just
install
it,
you
don't
worry
about
it.
D
D
E
It's
like
I'm
trying
to
provide
websites
for
beginners
in
a
way
that
where
recipes
could
be
really
helpful
and
that's
why
I've
spent
time
on
that,
and
I
think
joseph
has
a
similar
use
case,
which
is
why
he's
been
somewhat
interested
in
that,
but
most
developers
don't
have
that
use
case
and
like
that
they
would
be
developing
something,
that's
not
at
all
useful
to
them
and
they
maybe
don't
even
fully
appreciate
the
benefits
of
because
they
don't
use
them
so
but
anyways.
I
think
we
need
to
talk
about
that
at
a
different
time.
E
Right
have
another
I'll
have
another
angle.
Next
time
we,
where
we
left
off,
was
talking
about
this
upcoming
release
and
how
to
promote,
promote
it
and
if
there's
anything
else
that
that
we
can
do,
I
mean
either
new
venues,
but
I'm
I'm
interested
in
this
idea
of
the
angle
robert.
Can
you
say
something
from
your
perspective
about
what
what
you
think
the
impact
would
be
of
the
the
new
card
content
type?
A
I
think
it
it
just
takes
us
a
step
closer
to
providing
a
useful
good-looking
website
after
that,
first
click.
That's
the
main
thing,
so
I
I
I
kind
of
don't
think
the
recipe
the
recipe
would
be
a
big
deal
right.
The
adding
cards
and
the
new
front
page,
I
think,
is
a
pretty
good
thing,
because
now
someone,
you
know
they
clicked
and
their
site
looks
good
and,
as
you
said,
it
also
provides
an
entree
into
how
to
customize
it,
and
I
think
that
shouldn't
be
overlooked.
A
That,
especially
now
that
we've
added
links,
I
think,
we've
added
links
back
to
the
documentation.
So
it's
easier
for
people
to
get
from
that.
First
click
and
the
site
is
installed
too.
Now
I
want
it
different
from
what
that
clip
provided,
but
it's
that
we've
lowered
that
barrier
a
little
bit,
and
so
I
think
that's
a
good
thing.
E
You
know
useful
information
and
examples
to
help
people
get
started,
so
I
feel
like
landing
if
I
open
up
a
new
backdrop
site
right
now
today
as
a
beginner,
it
just
feels
much
more
inviting
to
me.
It
feels
much
more
like
a
website
and
there
are
just
sort
of
hints
and
clues
what
to
do
next,
that
I
just
don't
think
were
there
before.
E
E
If,
if
I
I
did
last
night,
if
robert
and
joseph
in
particular,
if
you
haven't
seen
this
before
jen
and
I
were
at
a
a
code-
sprint
a
hackathon
about
a
year
and
a
half
ago
and
a
first-time
backdrop,
user
was
trying
to
install
and
do
something
with
backdrop.
She
was
trying
to
like
reproduce
an
issue
and
we
used
it
a
little
bit
like
a
usability
study.
E
E
She
went
back
and
forth
looking
and
she
never.
It
never
occurred
to
her
to
go
to
the
dashboard
and
jen
immediately
opened
up
a
ticket
saying.
Maybe
we
should
redirect
new
users
directly
to
the
dashboard
which
didn't
go
over
really
well,
but
there
was
a
suggestion
which
again,
if
you
saw
the
issue
that
maybe
we
just
have
a
link
for
new
sites
direct.
E
You
know
letting
them
know
about
the
dashboard
and
to
me
the
the
that
it's
like
the
the
links
to
the
documentation,
on
the
one
hand,
they're
kind
of
specific
links
and
like
whether
people
are
going
to
need
those
specific
links
immediately
or
not,
is
questionable.
But
what's
most
important
to
me
is
that
we're
just
introducing
them
to
that
documentation,
we're
sort
of
inviting
them
to
say
hey
this
documentation
is
out
there
use
it.
E
From
the
cards
themselves,
they
have
three
links.
So
if
you,
if
you
spin
up
a
site,
it
has
three
cards
and
each
each
of
the
cards
linked
to
a
different
part
of
the
documentation.
I
think
one
of
them
links
to
content
so
not
within
drupal.
They
don't
link
or
but
within
backdrop,
they
don't.
We
at
one
point.
We
had
like
links
that,
like
here's,
where
you
go
edit
your
content
types,
but
for
a
few
reasons
those
ideas
were
rejected
and
what
we
ended
up
with
was
links
to
the
the
docs
site.
A
Go
ahead,
you
just
made
me
think
of
something.
You
know
that
that
home
page
also
shows
your
first
post,
which
says
this
is
your
first
post
you
may
edit
or
delete
it.
So
obviously
that
has
to
change.
It
seems
like
that
first
post
would
be
a
great
place
to
put
tips
like
administrators
check
out
the
dashboard
and
because
because
users
are
going
to
change
that
anyhow,
so
it's
it's
okay
to
put
stuff
there.
That
won't
be
on
a
real
website.
E
A
E
I
think
that
it
wouldn't
have
been
shot
down
if
it
was
done
consistently
at
the
end.
The
problem
was
that
idea
came
up
too
early
in
the
process
and
early
in
the
process.
It
confused
things,
and
so
people
didn't
like
it.
I
think
if
people
looked
at
the
website
now-
and
you
know
it
would
make
sense
to
modify
that
text,
and
I
don't
know
that
there
would
be
objections
to
it.
E
So
I
actually
think
we
could
certainly
that
you
know
that
wouldn't
need
a
major
release
to
change
that
content
and
we
could
try
to
get
something
in
before
sunday,
but
more
likely,
maybe
in
the
next
bud,
fix
release
right
that
could
go
into
the
the
first
bug
fix
release
of
the
next
thing,
which
would
be
to
update
that
content
to
make
it
sort
of
consistent
and,
to
maybe
add
one
more
link
right
into
the,
but
there
was
resistance
you
know
prior
to
this
pr.
E
The
idea
was
to
keep
the
front
page
as
simple
and
have
as
little
content
on
it
as
possible
and
like
starting
to
add
educational
content.
There
was
resistance
to,
but
now
we've
done
that
already
right.
That
that's
no
long!
We
can't
say
that
that
we
don't
want
to
do
that,
because
we've
done
it,
and
so
I
think,
adding
a
little
bit
as
long
as
it's
it's
not
anything
too
crazy
right
if
we
keep
it
short
and
keep
it
kind
of
consistent
in
the
same
tone
as
the
cards,
it
makes.
E
A
I
didn't
really
just
realize
one
problem
with
that,
as
we
that
page
is
visible
to
non-logged
in
users
and
if
we
say
go
to
the
dashboard
and
then
it
leads
to
right.
You
are
not
that
would
that
would
be
bad
well.
E
The
the
some
of
the
original
texts
for
the
cards
linked
to
administrative
features,
but
right
away.
There
were
objections
to
that.
That
said,
no,
we
can't
do
that
because
so
that's
why
all
of
the
links
currently
go
to
the
documentation
page,
because
that
is
something
anybody
has
access
to
right.
So
if
we
added
any
links,
they
would
probably
have
to
do
that.
Yeah,
like
the
same
go
ahead.
Joseph.
E
E
C
E
I
love
it
that
idea
has
come
up
before
I
don't
know.
I
mean
I
think
this
is
an
accept,
a
good
topic
for
outreach,
because
this
isn't
this
would
be
an
outreach
thing
really.
Wouldn't
it
yet.
I
love
the
idea.
I
mean
the
the
the
question
would
be.
We
I
think
the
biggest
pushback
to
that
is
that
we,
a
deliberate
choice,
was
made
to
not
have
multiple
install
profiles
early
on
right.
E
We
have
two
install
profiles
in
backdrop
right
now
right,
but
one
of
them
is
deliberately
hidden
and
all
you
have
to
do
is
unhide
it
and
it
shows
up.
So
if
we
created
a
learning
profile,
we
could
easily
just
have
it
show
up.
E
C
E
Well,
here's
the
way,
I
think
this
happens,
and
this
would
be
something
I
would
get
excited
about,
and
I
know
sarvashri
would
as
well
is
to
just
build
out
a
distribution
like
that
is
a
contrib
project
first
with
the
idea,
but
but
make
it
clear
up
front
that
it's
a
candidate
for
core
right
that
we're
building
it
out
to
for
inclusion
and
core,
possibly
but
we'd
have
to
like
show
people
how
it
works
first
before
so
that
way,
people
would
know
what
our
intent
is,
but
they
wouldn't
be
able
to
like
say
no
until
until
it
actually
got
flushed
out
enough
that
they
could
try
it
and
then
once
it's
flushed
out
and
it
actually
works,
then
we
could
introduce
the
idea
of
bringing
it
into
core
or
not
introduced.
E
D
E
You,
the
code,
would
sit
there
on
your
in
your
install
basis.
You
wouldn't
you'd,
only
actually
use
it
during
just
like
the
standard
install
profile.
We
have
a
standard,
install
profile
right
now,
which
runs
the
first
time
you
spin
up
your
drupal
site
and
then
it
never
runs
again
and
that's
it's
there.
It's
in
your
code.
It
doesn't
hurt
anything,
it
doesn't
slow
your
site
down,
it's
just
a
bunch
of
files.
It's
not
even
a
bunch.
It's
a
couple
of
files.
B
E
Take
that
much
space
and
this
this
new
thing,
probably
wouldn't
either
depending
on
how
elaborate
we
made
it,
but
I
think
that
would
be
a
really
good
idea.
I
would
love
to
work
on
it.
E
Well,
and
the
thing
is,
we
don't
have
any
contributed
distributions
right
now
and
it
would
be
nice
to
just
have
one
as
an
example
to
prove
that
you
know.
I
know
that
the
people
there
are
people
in
our
community,
including
possibly
you
guys
do
you
guys,
have
a
distribution
that
you
use
internally.
Joseph.
C
B
E
And
I
used
to
do
that.
I
had
my
own
install
profile
that
I
would
use
when
spinning
up
new
sites
that
just
added
and
enabled
modules
that
that
I
always
used.
But
then,
when
I
started
working
on
simplo,
I
went
with
a
different
approach,
which
was
instead
of
using
an
install
profile.
I
just
import
database
so
right,
which
is
different,
but
also
for
my
this
case.
E
E
It's
debated
whether
or
not
it
should
go
into
core,
and
I,
if,
if
you
it
could
be
well,
the
problem
while
this
is
where
recipes
come
in,
is
that
right
now
you
can't
install
an
install
profile
after
the
site
is,
is
spun
up
so
you
we
can't
include
an
install
profile
in
the
in
app
like
browser,
because
it
wouldn't
make
any
sense
to
to
install
it
later,
but
an
elaborate,
an
elaborate
recipe
could
be.
E
You
know
there
could
be
then,
because
the
the
the
problem
right
now
with
the
contrib
install
profile
is
that
you'd
have
to
download
it
manually.
You
know
put
it
in
your
folder
structure,
which
for
a
lot
of
users,
no
problem,
but
for
some
of
the
people
that
would
like
to
use
this.
That
might
be
too
much
for
them.
It
would
like,
whereas
a
a
recipe
is
something
they
could
just
install
the
website.
You
know
use
a
one-click
installer
at
godaddy.
E
They
could
go
to
the
project
browser.
They
could
find
the
module
which
says
beginner
starting
kit,
download
that
module
run
it
and
it
would
upload
a
bunch
of
features
and
have
their
site
look.
You
know,
look
like
so
so
it
I
don't
know.
D
E
E
C
E
I
know
greg
has
brought
it
up
a
number
of
times
and
I
only
sort
of
scoff
at
that
a
bit
very
politely,
because
I
have
no
idea
how
that
would
work
right
to
me,
an
install
profile
is
an
install
profile,
so
when
you
say
like
okay,
if
if
if
you're
saying
you
can
add
it
later
well,
then
it's
really
just
a
module
right.
E
That
is
true
and
in
a
way
well,
you
could
certainly
uninstall
it.
The
average
user
is
probably
just
going
to
leave
it
on
their
server,
which
is
again
it
doesn't
really
hurt
anything.
It
doesn't
take
up
much
space
and
the
code
would
never
be
touched
again.
If
you
want
to
install
it.
So
that's
probably
what
most
people
would
do
is
you
could
tell
them?
You
know,
install
the
module.
You
know.
E
E
E
C
How
would
you
do
that
you
could
have.
C
Yes,
you
could,
you
could,
have
it
be
removable?
What
you
would
need
to
do
is
you
would
need
it
sorry,
one
moment:
okay,
my
dad's,
watching
it
on
youtube
and
talking
to
me
about
what.
D
E
C
Oh
okay,
you
could
use
an
uninstall
hook
to
remove
all
the
stuff
when
you
disable
the
recipe.
If
you
had
a
user
interface
for
actually
making
the
recipes,
then
we
could
automate
all
of
that
stuff.
E
Completely
different
idea,
which
is
one
that
I've
also
played
with,
but
we
we're
out
of
time.
This
discussion
wondered
a
bit.
It's
a
interesting
topic,
though,.
E
I
think
this
this
meeting
has
been
a
little
bit
helpful
to
me
in
terms
of
like
I'll,
probably
write
the
blog
post
about
this
release
and
like
what
to
emphasize
I'm,
hopefully
going
to
do
a
video,
but
I
keep
promising
to
do
those
every
so
don't
get
around
so
we'll
see.
But
if
anybody
wanted
to
do
a
release,
video
that
would
be
helpful.
C
E
Yeah,
well,
you
can
just
go
to
the
milestone
and
click
if
you
go
to
the
issue
queue
and
you
go
to
the
milestone
and
you
look
at
the
1.22
milestone.
You'll
see
all
of
the
closed
issues
and
those
are
all
the
ones
that
got
it.
Okay,
I
think
that's
the
easiest
way.
Does
that
sound
right
robert
to
to
get
a
list,
I
mean
there
will
be
well
actually
we
might
have.
E
I
think
we
have
release
notes
for
the
preview
release
and
those
release
notes
now
would
also
be
a
good
source
that
wasn't
available
until
the
preview
release.
E
The
other
thing
to
look
at
well,
of
course,
is
we
can't
forget
to
look
at
the
bug
fixes
because
there
are
some
bug
fixes
that
are
significant.
I
think
you
know
stuff,
like
robert's
the
rewording
of
the
layouts,
the
the
stuff
you
added
to
the
layout
page.
That
makes
that
easier
to
use
to
me.
That's
like
a
new
feature,
but
it's
not
technically
in
the
1.22
release,
because
it
was
a
bug,
fix
release.
E
Yeah,
I
we
haven't
talked
about
that,
but
I
I
think
that
might
be
the
second
most
marketable,
although
to
it
like
different
audience.
Right
there's
like
a
first
time
backdrop
user
might
not
care
so
much
about
that
feature,
but
for
drupal,
7
users
or
existing
users.
That's
like
a
big
one
that
people
have
been
asking
for,
and
I
think
they're
going
to
be
really
happy
and
it's
also
backwards,
unlike
the
cards
content
type
that
one
will
affect
existing
sites.
So
that's
right.
C
I
think
a
lot
of
the
other
I'm
just
scanning
through
here.
I
think
a
lot
of
it's
like
that
in
the
cards
and
then
a
lot
of
the
other
things
are
really
just
administrative
things
or
like
the
upgrade.
The
upgrading,
the
fixing
the
problem
with
entity
plus
during
upgrades
is
like
a
big
thing,
but
it's
not
really
an
easy
thing
to
market.
E
Right
yeah,
I
mean
actually
that's
a
good
one
to
talk
about
right
now,
quickly,
robert,
because
you
were
involved
in
it
and
you
obviously
felt
strongly
about
it.
But
how
do
I
I
mean?
Is
it?
Is
it
something
that
we
can
promote?
Well,
like
I,
I
it's
primarily
going
to
affect
people
who
are
upgrading
triple
seven
sites,
but
it
is.
Is
it
a
problem?
Is
it
something
we
can
tell
people
about
and
they're
going
to
appreciate,
or
will
nobody
appreciate
it
unless
they've
actually
had
the
problem
already.
A
E
E
A
Sorry,
what
are
you
going
to
say?
You
know
just
because
I
mean
it's:
it's
smoother
upgrades
for
people
who
use
certain
modules,
that's
really
what
it
boils
down
to
you're,
not
going
to
get
bad
surprises.
If
you
upgrade
those
modules.
E
You
know
the
other
one,
although
it's
just
such
a
narrow
market,
is
that
there
are
some
good
ui
improvement.
I
think
the
book
module
works
a
lot
better
now
with
the
this.
The
thing
we
inserted,
but
I
don't
know
that
anybody
cares
because
so
few
people
use
the
book
modules
and
also,
unless
you
sort
of
used
it
before
it.
It
just
makes
it's
a
little
bit
like
robert's
point:
it's
like
promoting,
it
would
be
to
say
using
the
book
module
will
be
less
frustrating
than
it
was
before
it's
it's
not
like.
E
It
adds
new
features.
It
just
makes
it
a
much.
It
makes
it
a
less
frustrating
process,
and
that's
not
it's
hard
to
promote
that.
Oh,
the
the
date
format.
That's,
I
think,
that's
actually
a
promotable
feature.
The
additional
date
feature
the
fact
that
it
sort
of
automatically
configures
for
european
a
european
format.
E
So
sarvajri
for
your
information,
if
you
haven't
picked
up
on
this,
the
the
date
format,
one
is
the
you
know:
the
eur
europeans
and
well
everywhere
in
the
world,
except
the
us
puts
the
day
before
the
month
in
their
dates
and
backdrop
has
always
used
the
u.s
format
it's
month
day
year,
starting
starting
with
this
1.22,
any
new
site
will
automatically
you
if
you're,
if
you're
outside
the
us,
it
will
give
you
day
month
year,
it's
automatic,
you
don't
have
to
try
to
you.
E
E
On
the
other
hand,
it's
it's
not
as
significant
of
a
change
as
it
sounds
because
well,
everybody
in
the
world
uses
it
different
than
the
us.
They
all
have
their
own
little
takes
on
it
anyways,
so
they're
most
people
are
probably
going
to
end
up
having
to
edit
their
time
zone.
Anyways
or
maybe
not-
I
don't
know
we'll
see,
but
I
think
that's
a
significant
nice
improvement.
E
Let's
wrap
up
this
meeting.
The
dev
meeting
is
supposed
to
start,
given
that
neither
nate
or
jen
are
coming.
E
I
had,
I
don't
know
what
what
we're
going
to
do
for
this
meeting,
if
any,
but
I'd
love
for
someone
else
to
facilitate
it.
If
anybody
wants
to
otherwise
I'm
willing
to
facilitate
it.
Let's
end
the
youtube:
we're
still
got
the
youtube
running
by
jason.