►
From YouTube: Backdrop Outreach - 2021/09/16
Description
Most of this meeting is about our plans to use CiviCRM to help manage our community.
A
Hello,
everyone-
this
is
september
16th.
This
is
the
backdrop
outreach
meeting,
as
is
our
practice.
We
will
go
around
and
do
brief
introductions
of
everyone.
I'm
robert
lang
bug
folder
on
the
internet,
I'm
interested
in
layouts
and
documentation,
sort
of
odds
and
ends,
and
that's
what
I'm
working
on
very
happy
to
see.
1.20
come
out
and
I
will
pass
it
over
to
luke.
C
Hi,
my
name
is
greg.
I'm
joining
from
greece,
I'm
at
the
same
time
doing
some
of
the
work,
but
I'm
super
excited
about
the
release
that
came
up
yesterday
and
interesting
to
hear
the
progress
with
cv
crn,
because
I
have
not
been
part
of
this
at
all.
I
know
what
it
is.
I
know
where
what
the
goal
is,
but
I
have
had
no
update
so
yeah
passing
on
to
jack.
D
G
Hi,
I'm
tim
sorry
about
background
noise.
I'm
tim
erickson,
st
paul
tim,
I'm
in
deerwood
minnesota
this.
It's
been
an
exciting
couple
of
weeks.
I
got
after
kind
of
missing
the
last
released
into
the
getting
really
active
in
this
this
most
recent
release,
so
it
was
fun
being
a
part
of
a
number
of
pull
requests
that
got
into
the
new
release
and
just
being
really
involved.
G
So
that's
it.
Did
we
get
everybody?
I
think
we
got
everybody
didn't
we
anybody
not
introduce
himself
okay
yeah,
so
we
have
a
couple
of
things
on
our
agenda
today.
I
think
again,
we
put
there's
been
some
work
going
on
on
cbcrm
for
use
by
the
backdrop
community,
and
today
we
put
on
the
schedule
a
chance
to
sort
of
report
back
and
get
input.
I
think
is
that
a
good
way
to
characterize
that
check
from
from
this
group,
and
so
that's
one
thing:
that's
on
the
agenda.
G
We
also
probably
would
like
to
talk
a
little
bit
about
promoting
the
new
release,
and
maybe
I
don't
know
luke
if
you
have
any
need
any
help
with
that
or
like
would
like
some
input
on
that
or
not
we
could.
If
so,
today,
would
be
a
great
time
to
give
you
that
and
if
there's
time
something
I
thought
would
be
fun
to
do
in
the
outreach
committee
is,
is
in
my
experiments
with
sarvashri.
G
G
D
Sure
yeah,
so
today
I
think
basically
we
just
wanted
to
update
folks
who
come
to
outreach
meetings
about
the
work
we've
been
doing
to
get
civ
crm
ready
to
use
as
the
crm
or
constituent
relationship
manager.
For
the
backdrop
community,
so
you
know
it.
Outreach
meeting
is
a
good
place
to
bring
it,
because
what
we're
trying
to
do
here
is
have
one
place
where
folks
were
involved
in
outreach
and
like
volunteer
management,
doing
events,
handling
donations
etc.
D
Can
centralize
all
of
that
information
for
more
effective,
like
efforts
on
all
of
those
things,
the
outreach
side
of
things,
fundraising,
volunteer
management,
etc.
So
folks
have
been
talking
about
this
for
a
while.
In
the
backdrop,
community
and
civic
crm
rose
up
as
a
natural
choice,
so
to
be
our
crm
of
choice,
it's
you
can
find
it
at
civis,
civi
crm.org.
D
If
folks
don't
know
about
it
already,
it's
a
long-standing
open
source,
constituent
relationship
management
system
that,
for
I
think
it
started
out
in
drupal
and
was
early
on
ported
over
to
to
backdrop,
because
that's
relatively
easy
to
do
from
drupal.
So
it's
been
out
for
backdrop
for
a
while.
Now
it's
actually
not
even
in
full
release
for
like
drupal,
8,
9
or
10
yet,
but
it's
full
release
for
up
and
very
well
integrated,
so
makes
a
lot
of
sense
for
us
to
use
it
for
all
sorts
of
reasons.
D
D
So
that's
the
link.
I
just
dropped
in
the
chat
here
and
you
can
see
the
different
slowly
moving
pieces
in
this
process.
There
are
a
few
things
in
progress
right
now,
there's
a
kind
of
the
larger
conversation
that
was
opened
up
by
laryn
actually
a
while
ago
about
setting
up
city
for
the
backdrop
community,
that's
issue
number
782
in
github
and
that's
where
we
started
talking
about
all
of
this.
D
You
can
see
lots
of
kind
of
like
the
the
what's
and
whys
of
it
there,
and
then
we
organized
a
few
meetings
and
came
up
with
two
different
kind
of
veins
of
work.
So
some
folks
are
working
on
the
technical
side
of
things
and
you
can
see
the
work
on
that
in
issue
789
in
github
and
I'll
drop,
a
link
to
that
in
the
chat.
So,
on
the
technical
side
of
things
update,
there
is
basically
things
have
stalled
for
a
little
bit
just
because
of
capacity
on
folks
on
different.
D
My
co-worker
morgan
has
been
working
for
a
while,
along
with
justin,
to
get
a
pull
request
together
and
to
start
testing
backdrop
cms.org
with
civi
installed,
so
that
is
in
progress
and
we
actually
are
about
to
get
that
updated
and
tested
on
a
test
site
before
we
get
it
installed
on
the
live
site.
Obviously
we
want
to
make
sure
that
civi,
installing
civic
crm,
doing
a
very
basic
installation
doesn't
break
anything
on
our
main
backdrop
website,
so
tim
and
I'll.
D
Configured
set
up
properly
to
do
what
we
want
to
do,
so
that's
all
been
on
the
tech
side
of
things
and
that's
captured
in
that
issue
there
and
then
there's
been
the
other
side
of
things,
which
is
like
more
the
end
user
planning
for
civ
crm
and
I'll
drop
that
into
the
chat
as
well.
That's
github
issue
790.
D
So
so
far,
that's
mostly
been
me
and
tim
and
jen
talking
together
about
how
exactly
we're
going
to
use
civic
crm
in
this
community,
and
that
brings
up
a
whole
lot
of
things
like
what
are
our
policies
for
what
information
we
do
or
do
not
collect
in
the
database?
What
are
our
policies
about
permissions?
You
know
who?
How
are
we
going
to
do
work
on
this?
Who
can
shade
configuration?
D
Who
can
add
data
in
etc?
So
we've
been
discussing
all
of
that
stuff
talking
about
probably
starting
a
working
group
that
kind
of
focuses
on
this,
like
community
management
type
of
stuff,
where
people
can
go
to
get
access
to
the
crm
and
learn
how
we're
like
structuring
this
whole
process
and
get
involved
in
all
these
efforts.
So
there's
a
lot
of
meeting
notes:
we've
had
a
couple
of
end
user
meetings
so
far
and
there's
meeting
notes
that
are
in
that
last
issue
that
I
dropped
in
there.
D
So
folks
get
all
caught
up
on
what
we've
discussed
before
we're
having
another
end
user
meeting.
Let's
see
when
is
it
next
friday?
Let's
see
if
the
info
is
it's
4
p.m:
pm,
pacific
and
there's
a
world
world
time
clock
thing
link
in
there,
so
folks
can
get
it
translated
to
wherever
you
are
and
next
time
around
we're
going
to
keep
on
having
a
policy
discussion
kind
of
about.
D
The
last
thing
I'll
say
before
I
stop
just
talking
that
young
giving
you
the
update,
is,
I
should
have
said
this
earlier,
so
the
things
we
are
planning
to
use
sevi
for
at
the
start,
it's
in
some
notes
that
I
have
let's
see
well,
I
could
probably
just
remember
it
actually,
so
the
primary
things.
I
think
that
we're
using
city
for
to
start
are
volunteer
management,
we're
hoping
to
get
donations
in
there.
D
First,
we're
starting
off
with
just
basic
contact
management
of
like
you
know,
who
is
in
our
community,
who
has
expressed
interest
in
doing
this
and
that
stuff
like
that.
We're
also
using
it
for
donations,
we're
working
out
with
the
software
freedom
conservancy,
hopefully
getting
donations
right
into
our
account
through
civic
crm,
so
we
can
streamline
the
donation
process
and
also
keep
track
of
who
are
our
donors.
So
we
can
reach
out
and
say,
hey,
thank
you,
please
donate
again
and
finally,
event
management.
D
So
you
all
know
that
we've
had
a
different,
a
few
different
websites,
different
ways
that
we've
had
people
registering
for
events
by
consolidating
all
of
this
into
one
place.
It'll
give
us
a
much
better
understanding
of
like
who's
involved
in
our
communities
in
all
these
different
ways
and
make
it
a
lot
easier
to
reach
out
to
folks.
D
We
want
to
let
folks
know
what
we're
doing
on
this,
get
any
input
or
thoughts
from
folks
on
this,
but
also
encourage
folks
to
come
to
the
meetings
that
we're
having
for
this
to
get
more
involved
and
to
yeah
to
actually
work
on
it
if
you're
interested
so
I'll
kind
of
stop
there
see
first,
if
tim,
if
there's
anything
that
I
left
out,
but
then
open
it
up.
Questions
discussion.
G
Well
I'll
just
I
thank
you,
jack
for
keeping
this
process
moving
jack
has
really
kept
kept.
This
going,
we've
had
now
a
couple
of
meetings
and
stretched
out
over
you
know.
I
think
this
most
recent
initiative
has
been
going
on
for
a
couple
of
months
with
just
a
few
meetings,
but
yeah
I
mean
I
for
personally
I'm
really
interested
in
in
using
it
for
volunteer
management,
so
kind
of
the
way
you
describe
starting
light,
we're
working
building
our
way
up,
but
yeah.
G
We
do,
I
think,
we're
trying
to
figure
out
we're
making
some
decisions
about
sort
of
how
how
it's
going
to
be
managed
and
how
that
will
fit
in
say,
for
example,
with
the
outreach
group
that
was
part
of
the
reason
to
come
here
today.
If
you
really
want
to
get
involved
and
be
a
part
of
managing
and
having
input
yeah
that
meeting
next
week
would
be
great.
So
I
don't
think
I
have
anything
else
really
bad,
I'm
curious
to
see.
If
you
know
anybody
has
any
questions
or
any
thoughts.
C
D
D
In
the
the
backdrop,
repo
the
backdrop
cms.org
repo,
so
there's
already
been
pull,
requests
and
stuff
like
that
to
start
getting
it
in
there,
even
though
it's
not
actually
installed
and
morgan
and
justin
have
been
working
really
quickly
on
that.
So
that's
how
that's
going
to
work
from
a
technical
perspective
in
terms
of
where
it
goes
and.
C
I
would
like
to
have
a
page
with
you
know:
go
to
people
at
least
who's
managing
who's,
approving
things
how
like
what
is
the
process
for
someone
to
be
awarded
and
because
there's
privacy
there's
this
personal
data
as
well?
So
there's
a
lot
of
things.
So
I
was
wondering
about
the
plans
and
what
has
already
been
discussed
with
regards
to
that.
D
Yeah,
we've
actually
spoken
a
lot
about
that,
because
so
right
now
on
backdropcms.org
folks
probably
know
how
many
folks
on
this
call
have
a
have
a
user
with
editor
or
admin
access.
There's
lots
of
us
so
right
now
it's
it's
a
bit.
We
don't
have
a
very
solid
structure
around
what
happens
on
the
website
in
terms
of
like
how
do
we
agree
to
make
changes?
Add
content
do
things
like
that
right?
So
when
it
comes
to
that,
that's
one
thing
for
the
website.
D
When
it
comes
to
the
civ
crm,
it
feels
like
an
even
more
sensitive
thing
because
of
what
greg
said
there
is
private
information.
There's
contact
information,
there's
stuff
like
that
people
send
the
mailing
out
if
they
wanted
to.
We
certainly
don't
want
folks,
just
like
kind
of
of
their
own
accord,
deciding
to
send
a
mailing
without
consulting
other
folks
right.
So
we
want
to
have
some
two
things.
D
If
we
want
we'll
probably
start
with
the
former
and
folks
will
get
the
role
that
gives
access
to
the
crm
if
you're
part
of
the
working
group
that
we've
started
talking
about
so
at
the
our
most
recent
meeting,
I
think
that
the
august
27th
meeting,
let
me
see
yeah
we
started
talking
about
these
policy
decisions.
We
need
to
make
who's
using
civi
who
can
access?
What
who
paid
these
things?
D
D
Maybe
a
community
management
committee
is
what
we
came
up
with
first
like
so
we
have
these
outreach
meetings
and
the
outreach
teams
are
great
because,
like
all
of
us
can
come
to
it,
talk
about
outreach,
hear
about
outreach,
give
input
stuff
like
that,
but
there
also
has
to
be
a
space
for
kind
of
like
more
focused
working
on
particular
things,
including
civ,
crm,
stuff
and
the
things
we're
doing
with
civi
like
sending
mailings
and
organizing
events
and
stuff
like
that.
So
we're
looking
at
this.
D
Probably
this
community
management
committee,
a
new
committee
within
the
backdrop
community
that
we'd
like
to
also
pitch
to
folks
as
a
place
where
these
decisions
are
made
and
where
this
access
is
granted
in
terms
of
how
we
make
decisions.
We
talked
a
bit
about
that
there
and
it's
like
a
kind
of
a
top-down
thing
where
there's
like
a
like.
Let's
say
a
core
person
who
like
makes
the
decisions
on
what
to
do
with
civvy.
D
So
that's
kind
of
like
a
brief
kind
of
I
don't
know.
I
don't
know
how
brief
that
was,
but
that's
an
overview
of
what
we've
discussed
so
far.
All
these
big
questions
that
come
up
when
we're
using
a
crm
and
giving
false
access
to
it
through
the
website
we
already
have
yeah,
I
saw
I
see
robert
with
a
hand.
I
also
see
luke
off
of
mute,
so
luke.
If
you
want
to
get
in
the
stack.
Let
us
know.
D
A
A
So
I
have
one
a
question
and
a
comment.
The
question
relates
to
one
of
the
things
city
is
really
good.
At
is
events,
you
know,
registrations
and
all
that
sort
of
thing
and
if
city's
on
backdrop
that
cms
thus
far
our
events
have
been
on
event
style
and
the
user
user
accounts
are
distinct.
So
have
you
talked?
Can
you
talk
a
little
bit
about
what
your
thinking
is
on
sort
of
how
to
integrate
civi
across
our
sites?
If
it's
on,
if
it's
at
all
possible.
G
G
We
did
talk
about
whether
or
not
we
should
set
up
a
completely
separate
installation
of
backdrop
to
manage
civvy
crm,
but
I
think
the
thought
was
that
there's
too
much
data
already
in
backdrop.org
and
it
just
kind
of
made
sense
to
do
it
there.
So
we
we,
we
think
we
should
just
start
with
backdrop
or
cms.org
integrate
it.
There
primarily
use
it
within
that
site,
not
really
addressing
the
whole
like
single
sign-on
between
sites
at
this
stage.
These
are
things
we
will
have
to
address.
G
My
like
jack
mentioned
earlier
that
one
of
the
uses
for
it
would
be
managing
events.
My
understanding
is
that
we
don't
have
immediate
plans
to
like
we.
We
don't
have
an
integration
right
now
between
events.backdrop.org
and
the
regular
background
cms.org,
and
we
don't
plan
to
just
sort
of
shut
down
and
move
all
the
event
stuff
we
are
doing.
You
know,
there's
there's
a
lot
of
content
around
events
that
I
I'm
not
sure
we're
comfortable
like
bringing
that
all
into
backdrop.org.
G
Yet
so
for
the
the
short
term,
I
think
we'll
be
using
cvs
crm
in
parallel
with
events.backdropcms.org,
not
as
fully
integrated
as
they
could
be,
but
looking
for
opportunities
to
integrate
them
and
sort
of
figuring
out
what
the
path
is
down
the
road
so,
but
I
think,
like
the
next
backdrop,
live
even
if
we
got
cvcrm
going
next
week,
we'll
still
run
backdrop.
The
next
backdrop
live
on
the
event
site
and
they
won't
be
directly
connected.
However,
we
might
start
looking
for
ways
to
get
at
least
some
of
the
information
into
cbcrm.
G
D
Yeah,
I
think
that's
a
great
point
like
so
when
the
user
accounts
are
created,
we're
going
to
have
some
civic
crm
integration
right
off
the
bat
because
backdrop,
user
accounts
can
be
connected
to
the
civ
crm
record,
so
something
will
be
created
for
accounts,
we'll
have
to
weed
out
the
ones
that
are
spammy
but
yeah.
I
think
robert
you're
right
like
if
we
we
can
ask
for
more
information
that
goes
directly
into
civic
crm
on
the
user
registration
form
and
we
can
think
about
what
to
ask
for
and
how
to
use
that
in
spam.
D
Defense
for
sure
yeah,
just
adding
to
what
tim
said
before
so
yeah
events
is
the
last
thing
we're
planning
to
do.
I
think
we
put
in
order
of
priority.
First,
we
want
to
start
out
tracking
donations
because,
right
now
we
only
track
any
donations
or
event
registration
donations
through
like
there's,
barely
any
tracking.
It's
really
mostly
done
through
paypal.
D
We
don't
have
ways
to
reach
out
to
people
again
things
like
that,
so
we're
gonna
start
with
donations,
then
mailings
through
it.
So
we
can
get
off
a
mailchimp
because
there's
limitations
there
anyway,
then
after
that,
after
that,
but
we
could
kind
of
be
doing
it
at
the
same
time,
community
member
info
just
like
interest.
How
folks
want
to
be
involved
with
stuff?
You
know
so
that
we
can
do
things
like
reach
out
to
everyone
who
said
they
want
to
help
out
on
front
end
stuff
or
help
out.
You
know
whatever.
D
It
is,
then
event
registration.
Luckily,
because
we
are
doing
everything
in
backdrop
for
event
registration,
we
can
easily
export
stuff
and
bring
it
into
the
backdrop
city
site
on
backdropcms.org.
If
we
need
to
so
at
the
very
least,
we
can
export
and
import
stuff,
but
we're
going
to
think
through
more
together
of
like
how
to
get
them
integrated
or
how
to
move
the
event
stuff
like
what
to
move
into
backdrop
cms.org
what
to
keep
separate.
G
B
B
Made
that
fit
with
our
use
case
yet
have
we
reduced
the
number
of
fields
do
do
we
understand?
I
mean
I
assume
you
understand
them.
I
I'm
curious
how
how
we're
going
to
get
past
like
the
thing
that
actually
stopped
me
like
I
went.
I
was
like
I'll
figure
this
out,
like
I
open
it
up
and
like
suddenly
there's
like
a
million
controls.
I'm
like,
I
really
don't
know
how
this
works.
So
I'm
curious
how
we,
how
we
get
over
that.
D
I
could
speak
to
that
a
little
so
on
one
side
of
things.
I
think
it's
super
helpful
that
we
have
folks
like
morgan,
already
working
on
it
and
also
like
eric
and
laren
and
other
kind
of
civ
crm
heads
right
who
are
going
to
help
us
with
getting
the
configuration
in
place
so
that
that
side
of
things
is
not
so
daunting.
D
It's
also
good
because
folks,
who
are
experienced
with
civil,
know
kind
of
what
needs
to
get
turned
on
and
what
can
be
ignored
in
order
to
do
the
things
you
want
to
do
so
they'll
be
able
to
help
us
kind
of
we
don't
have
to
look
at
but
get
the
stuff.
We
need
to
do
the
stuff
we
want
configured
properly
right.
So
I
think
on
one
side
of
things,
it's
like
having
that
ongoing
support
too
from
folks
folks
have
expressed
interest
in
continuing
to
help
us
use
civi.
D
Well,
so
there's
that
then
there's
also
like.
So
when
you
open
up
civvy
and
look
at
a
contact
record.
There
are
a
ton
of
fields
that
can
be
filled
out
for
a
given
contact
and
then,
if
you
get
into
events
and
activities
and
things
like
that,
each
of
these
has
a
lot
of
fields.
That
can
be
quite
daunting,
but
I
think
the
the
key
for
us
will
be
figuring
out,
which
is
part
of
a
big
thing,
we're
going
to
talk
about
next
time.
What
is
it
that
we
do
want
to
collect
about
our
contacts?
D
Much
more
simple
forms
to
give
us
their
info.
Civic
crm
has
something
called
profiles
where,
basically,
you
choose
exactly
what
fields
you
want
someone
to
fill
out.
It
could
be
fields
that
go
into
all
sorts
of
different
places
in
civvie,
but
to
the
user.
It
just
looks
like
one
very
simple
form
so
like
we're,
never
gonna
confront
anyone
who
we
want
in
our
contact
database
with
all
of
those
fields
and
options.
The
city
gives
we're
always
going
to
pare
it
down.
D
B
I'm
I'm
aware,
with
with
this
kind
of
thing,
that
that
that
it's
one
of
those
things
that
that
makes
adoption
difficult
because
because
you
you're
you're
picking
on
you,
know
a
system
that
has
lots
of
capabilities
and-
and
it's
clear
to
me
that
the
crm
is
inherently
complicated
in
this
sense.
Like
I,
I
had
a
a
salesforce
developer
account
for
a
while
and
mucked
around
with
that,
and
it
looks
just
like
cbcrm.
It's
the
same
thing.
B
You
you
open
it
up
and
you've
got
like
95
fields
with
similar
sounding
names
to
it,
and
you
know,
and
and
you're
like
all
right.
I'm
sure
this
must
be
useful
but
like
like
until
you've
got.
Actually
you
know
a
user
like
a
critical
mass
of
data,
I'm
sure
it's
hard
to
figure
out
like
which
pieces
are
there
and-
and
it's
tempting
you
know,
because
they're
configurable
systems
to
think
like
okay,
well,
we'll
simplify
the
form
so
that
it
doesn't
look
good.
But
I
know
that
you
know
that's.
B
G
Anybody
else
I'll
just
add
to
that.
I
don't
know
if
this
is
exactly
the
point
you're
making
luke,
but
just
some
blog
posts
about
our
process,
you
know,
would
be
an
artwork.
You
know
this
is
the
outreach
meeting,
we're
always
looking
for
content
for
our
website
and
some
sort
of.
If
we
could,
I
think
you
were
talking
more
about
documenting
some
of
the
real
technical
things
for
other
users
that
need
it,
but
also,
I
think,
on
just
a
high
level
like
what
our
process
has
been
to
make
this
decision
and
integrate.
G
B
B
D
Yeah,
I
think
for
folks
who
you
know
obviously
again
for
folks
who
are
not
like
admins
in
civvy
and
going
in
there.
None
of
like
that
won't
be
a
worry
like
the
the
forums
we
present
to
the
general
public
are
gonna.
We're
gonna
have
to
like
there's,
there's
nothing.
We
can
show
them.
That's
not
cleaned
up
like
we're.
Gonna
have
to
like
design
them,
so
that'll
be
good
and
yeah.
D
I
think
it's
important
and
that's
what
we're
trying
to
do
in
the
meetings
and
in
the
meeting,
notes
and
stuff
is
document
these
decisions
about
like
what
do
we
want
to
collect?
What's
important
for
us
to
have?
What
do
we
want
to
use
this
for
and
then
have
real
clear
guidance
for
all
of
us
working
on
it
like
on
that
stuff?
Like
read
me,
maybe
level
guidance
like
simple
straight
up
guidance
like
you're,
suggesting
documentation
of
how
we're
using
the
system,
because
it
is
a
really
complex
system.
D
B
I
think
that's
a
good
thing
to
keep
in
mind.
In
general,
I
mean
within
within
the
overall
backdrop
project
and
even
you
know
related
to
drupal.
That's
like
an
ongoing
thing
is,
is
you
know
almost
all
the
drupal
sites
they
that
I've
I've
worked
on
over
the
years
like
no
one
ever
bothers
to
simplify
the
admin
interface
and,
and
so
so
you,
you
have
the
the
the
poor
content
editors
who
end
up
having
to
do
to
work
on
things.
B
You
know,
there's
these,
you
know
endless
menu
items
any
one
of
which
they
could
click
and
destroy
the
system
and
they
have
to
like
desperately
try
not
to
click
on
the
wrong
thing.
So
yeah,
it's
one
of
those
things
that
wordpress
gets
right.
You
know
you
open
a
wordpress,
there's
this
nice
administration
interface,
where
you
can
basically
not
get
into
trouble,
and-
and
you
know
we
should-
we
should
have
that
in
our
dna.
G
Okay,
so
we're
two
thirds
or
three
quarters
of
the
way
through
this
meeting
and
the
intent
wasn't
to
take
up
the
whole
meeting
with
cbcrm.
So
is
there
anything
else
urgent
on
this,
or
should
we
can
we
move
on
and
talk
about
a
few
other
topics?
I
I'd
like
to
stress.
I'm
also
a
little
sensitive
about
the
fact
that
some
people
are
really
disappointed.
G
They
couldn't
be
here
so
I'd
like
to
you
know
not
cover
everything
in
this
meeting,
but
save
some
for
the
next
one,
where
maybe
some
other
people
can
attend
and
maybe
make
the
final
point
that
it
is
exactly
this
pro.
We
know
there
are
people
out
there
that
are
interested
in
this
topic
and
might
be
feeling
a
little
bit
left
out,
and
that's
why
we
need
to
be
crm
is
because
we
don't
have
good
ways
of
sort
of
track.
G
You
know
we,
we
we
we
all
sort
of
know
in
our
heads
who
the
people
are
who've
expressed.
An
interest
in
cv.
Crm
jack
has
made
an
attempt
to
sort
of
tag,
people
I
think
in
some
posts
to
draw
their
attention
to
it.
I
did
the
same
today
in
zulu,
but
we
don't
have
an
easy
way
to
just
sort
of
say:
hey,
let's
notify
all
the
cvcrm
people
about
this
next
upcoming
meeting
and
hopefully
cvcrm
will
give
us
that
so.
G
B
C
It
was
a
big
relief
to
like
I
mean
we
did
get
very,
very
few
random
failures,
but
it
was
just
a
matter
of
you
know,
restarting
the
tests,
and
then
it
was
a
relief
to
actually
know
that
when
you
run
the
tests,
you're
gonna
get
useful
results
and
you're
not
gonna
result
in
spending
all
your
day.
Restarting
them.
You
know
and
not
getting
consistency.
C
C
Instead
of
making
assumptions
of
how
how
useful
or
or
how
popular
a
thing
is,
we
now
will
have
some
metrics
eventually
we'll
have
some
metrics
to
back
that
up,
and
it's
a
big
thing
for
me
and
of
course
recipes
but
I'll
not
not
recipes
is
not
a
new
thing,
but
we
made
progress
but
I'll.
Let
team
talk
about
that.
G
A
G
A
No,
it's
it!
It
allows
it.
It
makes
it
easier
for
a
contribute
module
which
there
is
one
which
is
layout
wide
and
but
it
also,
it
also
makes
it
easy
again.
If
you're
going
to
write
code,
it
makes
it
easy
for
you
to
write
your
own
code.
If
you
want
to
do
things
with
layouts
that
are
not
easily
supported
in
chord,
and
I
think
ultimately,
it
will
make
it
easy
to
migrate
some
of
that
functionality
from
the
contrib
module
in
the
core,
which
is
kind
of
kind
of
what
I'm
looking
at
now.
C
Did
not
make
it
unfortunately,
so
this
was
another
thing
which
was
not
a
single
thing
that
that
excited
me
about
these
releases
was
that
we
had
so
many
improvements
that
regarded
user
experience
and
getting
consistency
among
different
parts
of
the
user
interface.
We
got
so
many
things
in,
but
still
certain
things
were
left
out.
C
So
there's
plenty
to
do,
but
the
thing
that
I
was
excited
about
was
that,
because
everyone
has
got
their
own
daily
routines
their
lives,
their
work
is
the
the
way
that
the
community
coordinated-
and
there
was
you
know
when
people
couldn't
complete
their
pull
requests.
Other
people
might
jump
in
and
you
know,
base
a
new
pull
request
off
of
the
previous
person
and
you
know
drive
things
to
an
end
to
the
finish
line
and
that's
yeah.
That
was
really
exciting
as
well.
It
was
really
great
to
see
in
action.
C
G
So
unfortunately,
luke
for
for
pr
purposes,
some
of
the
things
I'm
most
excited
about
aren't
the
best
things
in
a
press
release,
and
one
of
them
is
like
what
luke
or
greg
just
talked
about
was
to
me.
Part
of
the
excitement
of
this
release
was
just
that.
I
got
really
involved,
and
so
I
helped
out
with
some
obscure
bug,
fixes
that
really
aren't
pr
worthy,
but
but
it
was
fun
to
be
a
part
of
getting
these
things
fixed
that
have
been
there
for
four
or
five
years
languishing.
B
G
Wouldn't
it
be
cool
if
we
could
do
x,
oh,
we
should
be
able
to
do
that,
but
there's
this
bug.
Okay,
we
fixed
that.
So
it's
it's
like
it's
not
really
a
new
feature,
but
the
other
problem
with
with
promoting
this
is
that
really
we
haven't
made
decisions
like
what
is
the
config
recipe?
How
do
we
want
to
manage
them
so
to
make
big
announcements?
I
I
have
been
not
shy
about
like
tweeting
about
this,
but
I
think
as
a
project
we
might
want
to
be
careful
about
like
what
is
it.
G
B
B
B
Endlessly
obscure
like
like
now
now
when
you
do
this,
so
unlike
that
it
doesn't
do
this,
I'm
like!
Oh
okay,
I'm
glad
somebody
fixed
that
thing,
I'm
never
gonna.
So
so
I
mean
that
that's
that's
part
of
packaging
stuff
is,
is
making
sure
you're
addressing
it
to
like
okay,
you
might
not
be
the
audience
that
cares
about
this,
but
there
are
audiences
and
here's
what
you
need
to
know
to
to
get
a
sense
for
the
overall
flow.
G
I
think
what
I
would
package
the
config
recipes
as
a
step
forward
and
not
like
as
a
final
thing,
because
there
just
aren't
decisions
like
on
how
we're
going
to
handle
them.
What
exactly
we
consider
them
and
also
there's
competing
ideas
right
now,
still
about
how
we
should
manage
them.
So
I
don't.
I
don't
want
to
send
out
the
message
that
we've
like
decided
this,
that
this
has
all
been
decided
much
more.
G
B
C
Yeah,
so
so,
if
one
looks
at
the
changelog
for
120,
which
is
the
minor
release
that
was
released,
it
doesn't
do
enough
credit
to
it
because
at
the
same
time
we
released
the
119
for
bug,
fix,
release
and
in
backdrop,
we
have
this
in-between
thing,
which
is
not
a
bug.
It's
not
a
feature,
but
it's
it's
a
task
and
usually
user
experience.
Improvements
fall
into
that
category.
C
So
if
one
wants
to
see
the
the
amount
of
the
full
amount
of
work
that
has
gone
into
this
release
should
also
compare
the
changelog
for
119.4,
because
this
there's
there's
things
there.
That
are
not
mentioned
in
the
120,
of
course,
because
it
was
in
the
previous
release
that
are
amazing,
like
consistency
in
the
ui,
as
I
mentioned
earlier,
which
is
really
great
one
of
my
favorites
when
it
comes
to
that
is
another
child
of
peter
bw,
panda,
the
the
consistency
with
the
machine
names
and
labels
for
things
in
the
tables.
B
G
G
Well,
I
I
think
ideas
for
luke
is
one
thing.
Another
thing
would
be
anything
else
we
should
be
doing
so
we
have
a
new
other
things
on
the
outreach
front
that
we
do
to
promote.
Our
new
releases
is
there's.
Usually
we
wait
about
two
weeks
before
we
do
a
newsletter
which
is
about
the
time
our
newsletter
would
normally
come
out,
so
the
next
newsletter
will
probably
have
some
good
coverage.
G
G
G
Okay,
yeah:
well,
I'm
inclined
we're
almost
at
the
at
the
hour,
my
little
thing
about
showing
them
the
name,
cheap,
softaculous
interface.
Probably
we
don't
have
time
for
so,
although
we'll
see,
if
there's
a
dead
spot
in
the
next
meeting,
maybe
I
whip
it
out
because
I've
got
it
ready
and
cued
up
to
go
otherwise,
we'll
bring
it
up
at
a
future
meeting.
B
Can
you
can
I
throw
out
something
actually
when
you
said
that
I
was
sort
of
inspired,
not
not
necessarily
by
by
that
I'm
interested
in
that
particular
topic,
but
but
I
think,
on
a
more
meta
level
planning
like
many
presentations
in
our
meetings,
I
think,
might
be
a
really
kind
of
solid
thing.
I
I'd
love
to
see
that.
E
F
G
B
G
G
On
the
outreach
and
softaculous
front,
let
me
mention
that
softaculous
tweeted
this
morning
that
they
have
updated
to
backdrop
1.20,
and
I
find
that
pretty
amazing
and
impressive
that
that
you
know
that
they're.
I
don't
know
how
they've
systematized
this
or,
if
how
much
it's
automated,
but
they've
already
pulled
in
our
upgrade
and
tweeted
about
it.
And
it's
like
how
can
we,
how
can
we
get
more
people
doing
that
right,
yeah.