►
From YouTube: Backdrop Outreach - Jan 7th, 2021
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
Okay,
okay,
so
I'm
confused,
because
I
don't
have
my
zoom
and
naturally
there
we
go.
Give
me
just
a
second
here:
we
go
welcome
everyone.
We
are
now
officially
live
with
the
week,
their
bi-weekly
outreach
meeting
for
january
7th.
A
We
are
recording
this.
So
if
you
have
any
reservations,
turn
off
your
camera
or
mute
yourself
anyways,
unless
you
were
talking,
we
there
will
be
yeah.
I
guess
that
doesn't
matter,
let's
go
ahead
and
introduce
ourselves.
First,
I'm
tim
erickson
we're
st
paul
tim
up
in
deerwood
minnesota
and
have
been
kind
of
frantically
busy
with
too
many
different
things
lately
to
have
come
into
this
meeting
within
the
agenda
other
than
to
talk
about
outreach
and
what
needs
to
happen.
Luke
introduce
yourself.
C
I
am
luke
mccormick
living
in
san
ramon,
california,
I
do
web
product
management
or
project
management
and
all
sorts
of
things.
I
do
all
sorts
of
things,
so
my
challenge
is
always
to
figure
out
what
to
focus
on
at
any
given
time
and
finish
before.
I
start
any
other
things,
but
at
the
moment
I'm
focused
largely
on
backdrops
usability
and
learnability
phil.
D
B
All
right
introduce
myself,
I'm
jen
lampton,
I'm
joining
from
oakland
california.
I
have
a
pack
job
website,
that's
doing
a
lot
of
work
today,
so
I'm
on
call
for
them
as
they
need
things.
So
that's
why
I'm
only
lurking
I'm
very
excited
about
it.
Thank
you
back
up,
let's
see,
has
everyone
else
introduced.
A
It's
just
the
four
of
us
so
what
I
think
we're
to
do
to
start
out.
We
talked
about
what
we
wanted
to
talk
about
in
the
meeting
today
we
have
a
regular
agenda,
which
includes
reviewing
some
things,
like
blog
posts
and
and
things
before.
The
meeting
phil
mentioned
wanting
to
talk
about
the
upgrade
module
was
that
right.
D
A
But
what
I
was
going
to
say
is:
we
might
spend
a
little
time
today
or
we
could
wait
until
after
the
release,
but
last
year
we
waited
until
after
the
release
of
the
the
before
we
did,
it
sort
of
our
end
of
the
year
review
or
new
year
preview,
and
we
have
a
release
of
backdrop
1.18
coming
out
like
in
nine
days
and
certainly
for,
like
the
dev
group,
it's
better
to
wait
before
we
do
any
big
reflection
until
after
that-
and
I
think,
with
the
dev
group
last
year
we
or
the
the
the
outreach
group
what
we
did
last
year
is
we've
tried
to
schedule
this
big
year-end
review
or
or
goal
setting
for
the
next
year.
A
I
think
we
focus
more
on
goal
setting
for
the
next
year
and
we
scheduled
that
we
tried
to
schedule
out
a
couple
of
weeks
so
that
people
that
don't
normally
attend
would
be
able
to
sort
of
show
up
for
that
and
participate
in
that,
and
I
think
it
went.
It
went
fairly
well
in
terms
of
we
had
good
meetings.
We
had
some
attendance,
you
know
some
people
show
up
that
weren't,
usually
there
and
we
had
lots
of
good
discussion
where
I
think
the
follow-up
as
usual.
It's
like
okay.
A
Now,
what
do
we
do
with
all
this
information
and
great
ideas
that
we've
got
so
this
year?
I'd
kind
of
like
to
look
back
at
what
we
did
do
last
year
in
terms
of
process
and
think
a
little
bit
about
more
of
them
about
how
to
how
to
process
that?
What
luke?
What
did
you
have
involved?
You
talked
about
breaking
down.
Barriers
of
entry.
Was
that.
C
Yeah
yeah
well,
I've
I've
got
two
things
now
see.
I
told
you
just
just
to
to
complete
the
the
question
there.
What
I,
what
I
propose
would
be
listing
and
and
treating
as
an
ongoing
goal,
understanding
what
the
barriers
to
entry
for
people
coming
into
backdrop
are
and
and
looking
for
ways
to
to
reduce
those
barriers
of
entry.
Okay.
C
However,
I
I
want
to
throw
a
new
agenda
item
that
I
didn't
think
of
before,
but
but
but
that
might
might
warm
the
cockles
of
your
heart.
Is
you
you
you're
talking
about
1.18
comes
out
in
nine
days
now
this
meeting
happens
every
14
days.
So
this
is
the
last
outreach
meeting
before
the
release
comes
out.
C
So
maybe
this
would
be
a
good
time
to
sort
of
mention
the
checklist
things
that
we
should
do
upon
a
new
release
and
and
just
tick
them
off,
so
that
so
that
if
there's,
if
there's
available
horsepower,
we
can
apply
it
to
to
complementing
and
and
maximizing
the
effect
from
the
release.
A
I
think
that's
a
good
idea,
I
mean
so
first
of
all
to
review,
you
know
what
it
is.
We
do
do
before
each
release
or
around
each
release
and
talk
about
how
that
effective.
That's
been,
I
mean
we,
I
think.
A
The
sort
of
the
quick
answer
to
that
is
that
we
do
have
a
checklist
that
includes
some
sort
of
outreachy
stuff,
certainly
like
the
blog
post,
for
example.
I
think
we're
pretty
good
at
getting
out
a
blog
post
around
each
release,
but
we
also
have
things
like
getting
a
video,
a
video
out,
highlighting
new
features
even
or
a
newsletter
post
that
we
are
not
so
good
at
that.
It's
on
our
checklist.
It's
on
our
to-do
list
for
every
release,
but
oftentimes
doesn't
happen.
A
One
of
my
concerns
about
a
lot
of
these
meetings
is
that
we
love
to
come
up
with
new
ideas
for
things
we
should
do
while
not
implementing
the
long
list
of
ideas
that
we've
already
got
and
I
like,
and
this
this
is
sort
of
a
good
in
between,
because
we
can
talk
about
how
to
you
know
I
mean
to
me
it's
like.
A
If
you
have
a
long
list
of
things
to
do
and
you're
not
doing
some
of
them
on
a
regular
basis,
then
you
either
need
to
redo
your
list
like
because
you
don't
have
the
resources
and
or
or
motivation
to
do
them
or
you
need
to
figure
out
why
you're
not
getting
them
done
and
come
up
with
a
plan.
A
So
that
seems
like
go
ahead.
Oh
I
was
just
going
to
say
it
seems
like
a
smart
thing
to
talk
about
right
now.
C
No
well
like
within
the
agile
world.
That's
that's
something
that
I
I
come
from.
I'm
actually
studying
for
agile
tests
at
the
moment,
okay
certification,
but
so
so
so
the
list
of
things
you
want
to
do
in
in
scrum
is
called
the
the
backlog
sure
and
there's
a
role
within
scrum
to
do
exactly
what
you
just
said
to
to
look
at
the
backlog
and
pick
what
to
do
next
and
instagram.
A
Sure
and
there's
two
different
kinds
of
lists
that
we're
talking
about
right
now,
I
the
sort
of
the
backlog
the
backlog
I
take.
It
would
apply
more
to
the
issues
that
we've
created
in
github
and
haven't
really
started
to
work
on.
The
other
list
that
I
was
bringing
up
is
the
checklist
that
we've
created
sort
of
for
each
release.
A
That
has
things
like
a
newsletter
post
or
release
a
newsletter
on
it,
but
that
we
have
not
very
but
not
very
regular
about
getting
to
that.
So,
if
we've
already
moved
that
from
the
backlog
we've,
you
know,
we've
done
it
in
the
past.
It's
just
we're
not
doing
it
regularly
and
so
to
me.
The
action
item
on
that
is
to
either
figure
out
is.
Is
that
something
we
can
do
on
a
regular
basis?
And
if
not,
why
not
or
you
know,
or
to
figure
out
why
it's
not
happening
right
and
like
what
can
we
better?
A
C
Well
I'll
do
a
soft
shoe
shuffle
here?
Well,
oh
yeah!
No,
I
I,
I
think
I
think
I
think
that's
not
in
inconsistent.
C
I
I
think
I
mean
agile,
is:
is
people
normally
think
software
development,
but
but
there's
a
growing
movement
within
marketing
to
to
treat
you
know
marketing
tasks
the
same
way
which
is
kind
of
what
we're
talking
about
here
and
you
know
if,
if
you
think
of
each
release
as
being
a
product,
then
then
you
end
up
in
in
similar
territory
of
you
still
do
the
same
things
you
have
to
you
know
you
have
to
look
at
a
list,
that's
too
big
for
to
accomplish
everything
all
the
same
time
and
and
break
it
up,
and
you
know
pick
somehow
which
what
are
you
going
to
do
things
then.
A
A
So
we
have
update
the
pr
okay
post
release
tasks
looks
like
it's
mostly
technical
yeah,
so
the
post,
the
publicity
tests
are,
would
be
the
outreach
and
we're
getting
a
tweet
out
is
something
that
I
think
we
do
pretty
good
about
getting
a
blog
post
out
we're
pretty
good
at
maybe
not
perfect,
getting
the
newsletter
out.
I
would
give
us
a
d
to
an
f
on.
We
have
not
been.
It's
been
very
erratic,
updating
the
wikipedia.
A
A
A
B
Yeah,
it's
it's
either
on
the
preview
checklist
or
on
the
actual
release
checklist.
But
I
don't
remember.
A
Well,
I
would
consider
that
a
little
bit
of
an
outreach
thing,
although
maybe
less
so,
that's
also
a
development
thing
so
yeah.
So
I
I
think,
there's
two
questions
about
this
list
that
I
just
read
off
one.
What
is
what's
is
there
anything
missing
from
that
that
we
could
or
should
be
doing
and
two?
How
do
we
do
better
at
it?
C
Do
I
mean
in
commercial
software
when
you
release
a
new
version,
sort
of
the
the
the
the
fundamental
thing
that
happens?
Publicity-Wise
is
a
press
release
gets
released
and
and
that
that
goes
out
to
a
bunch
of
places
right,
and
I
don't
think
I'm
seeing
that
kind
of
thing
here,
but
it
could
cause
that
I
mean
sort
of
like
the
newsletter.
Is
I
mean
that's
a
press
release.
A
Right
yeah,
my
gut
reaction
was
going
to
be
the
closest
I
think
we
have
to
that
is
is
the
newsletter,
but
but
I
don't
think
those
things
are
the
same.
The
idea
of
a
press
release
has
come
up
to
me
before,
but
I've
been
reluctant
to
bring
it
up
just
because
we're
having
a
hard
time
doing
the
things
we're
doing
already
and
I'm
not
I'm
not
real,
confident
that
we'd
get
a
lot
of
value
from
it,
but
we
might.
C
No,
no
but
but
I
I
don't
actually
mean
so
much
as
a
specific,
like
actually
being
published
in
right
places,
although
that
that
can
be
happened,
but
but
just
as
an
organizing
principle,
one
of
what
one
of
the
the
brilliant
things
I
think
that
I
learned
about
amazon
is
is
one
of
the
things
they
do
is
is
when
a
new
project
is
proposed.
C
The
very
first
thing
they
do.
The
first
thing
they
do
is
they
write
a
press
release
as
if
it
was
finished,
as
if
you're
announcing
the
thing
that's
completed
and
and
half
the
parts
get
killed
because
of
press
release,
because
the
idea
is
that
they
don't
start
something
unless,
like
once,
it's
finished,
it's
it's
worth
bragging
about.
So
I
I
I
think
the
the
discipline
of
creating
a
press
release
is
helpful.
It
gives
you
momentum,
you
know,
and
it's
useful
to
to
kind
of.
Have
it
in
mind.
I'm
I
mean
we're
related.
C
I
I
guess
I
can
look
at
the
roadmap
and
and
one
of
the
questions
I
had
is
there
there's
the
the
five
things
that
happened
right,
the
the
five
new
features?
I'm
I'm
sorry,
I'm
looking
at
something.
No
one
else
is
like
I'm.
Looking
at
the
roadmap
on
the
site
features
planned
for
version,
1.18.
A
Right,
so
my
understanding
is
that
I
think
gregory
often
updates
this,
although
I'm
sure
jen
or
other
people
might
as
well,
but
I
think
that
I've
never
updated
the
roadmap.
My
understanding
is
that
we
have
been
largely
updating
it
based
on
the
milestones
and
the
milestones
are
generated
by
our
advocates
so
that
to
get
something
on
the
you
know
like
we'll
be
announcing
one
or
adding
a
1.19
features
planned
for,
and
that
will
largely
depend
on
on.
You
know,
who's
advocating
for
what
we're
going
to
be
in
an
interesting
state.
A
We
have
a
two
like
two
big
issues:
advanced
caching
being
one
and
and
then
the
one
doc
willmon's
working
on
that
are
almo.
We're
almost
ready
for
1.18,
so
they'll
sort
of
be
easy
to
get
on
the
roadmap
for
1.19,
but
other
than
that.
It'll.
A
lot
depend
on
what
people
get
behind
and
advocate
for.
A
Right
and
some
of
those
things
won't
be
decided
for
several
weeks.
I
mean
one
of
the
things
we
struggle
with.
I
think,
as
a
an
open
source
community
and
the
backdrop
community
is
like
is-
is
setting
these
kinds
of
goals
because
we're
all
motivated
as
we're
all
volunteers
and
working
on
what
motivates
us.
So
as
a
community,
you
know,
we've
tried
to
sit
down
and
say
like
what
should
our
goals
as
a
community
be
for
1.19?
A
A
D
Do
you
do
you
think
in
in
regards
to
this
that
maybe
we
can
introduce
into
that
planning
phase
the
time
frame
phase
and
so,
for
example,
we
sit
down
and
figure
out.
What
do
we
want
to
see
put
into
one
1.19,
okay,
we're
going
to
spend
the
next
two
weeks.
Look
into
the
thing
that
you
want
to
look
into
and
figure
out
and
get
a
ballpark
idea
how
much
time
it's
gonna
take,
and
then
we
come
back
and
okay.
I
think
this
is
probably
gonna
end
up
taking.
D
You
know
up
front
it
sounded
like
it
would
have
been
a
really
easy
fix
and
then,
once
you
guys
kind
of
started
to
dig
into
it,
you
found
out
no
there's
more.
It's
a
lot
deeper
than
just
changing
the
the
the
front
end
name:
we've
got
to
change
the
back-end
name
and
that
deals
with
existing
modules
and
it's
going
to
take
a
lot
longer.
D
C
Oh
yeah
well
well
from
from
from
sprint
from
a
scrum
world
again
that
that
particular
task
is
the
the
sprint
planning
piece
of
the
equation
and
and
and
it
wrestles
with
I
mean
the
idea
of
estimating
effort
is,
is
just
you
know,
universal
within
software
just
considered
incredibly
hard.
C
You
know
almost
almost
nobody
does
it
well,
you
know
along
the
board,
and
and
so
so
the
approach
that
the
the
scrum
world
uses
is
to
get
a
bunch
of
people
and
to
measure
story
points
and
and
to
not
really
not
really
try
to
absolutely
measure
the
size
of
any
one
thing,
but
compare
them
like
you've
got
five
things
and
you're
like
okay.
C
I
don't
know
how
long
either
of
these
are
going
to
take,
but
like
b,
is
going
to
take
twice
as
long
as
a
right
and
and
so
so,
like
that's
one
approach
and
then
that's
combined
with
like
a
bunch
of
people
all
kind
of
looking
at
it,
and
if
everybody
says
that
then
you're
feeling
pretty
good
you're
like
yeah,
that's
probably
right,
and
if
it
varies,
if
it's
different,
then
then
you
know
you
have
a
discussion
like
wait.
Why
why
does
this
seem
hard
to
you
but
easy
to
me?
A
First
of
all,
I'm
assuming-
and
you
can
tell
me
if
I'm
wrong-
look
that
in
the
common
scenario
you're
talking
about
is
that
you
know
you
come
up
with
sort
of
a
unified
set
of
goals
or
tasks
that
you're
thinking
about
working
on,
and
then
you,
you
know,
do
what
you're
talking
about
figure
out
what
the
effort
or
timeline
would
be,
and
it's
just
hard.
You
know
again.
We
have
difficulty
with
that
process.
It's
like.
A
A
But
what's
the
point,
if
nobody's
going
to
step
up
to
do
them
now,
where
I
thought
the
idea
that's
coming
to
me
from
what
you're
saying
is
that
sometimes
nobody
steps
up
to
do
them,
because
sometimes
it's
not
clear
what
how
much
work
is
involved
in
them?
So
there
would
there
might
be
some
value
in
like.
A
I
don't
know
that
we
can.
You
know
that
we
can
just
sort
of
at
one
moment
sit
down
and
decide
here.
Are
the
goals
for
next,
but
what
we
might
be
able
to
do
is
you
know,
brainstorm
some
ideas
of
things
that
our
people
are
interested
to
doing
and
go
a
step
further,
which
is
to
outline
like,
what's
involved
in
each
of
these
tasks,
because
that
might
make
it
easier
for
people
to
step
up
or
or
for
us
to
as
a
sort
of
a
community
to
set
something
aside
and
say.
A
And
that
might
affect
my
decision
about
whether
or
not
to
take
that
on
and
or
more
importantly,
somebody
with
the
skills
to
help
implement
it
to
just
for
them
to
decide
if
they're
interested
and
for
us
to
collaborate.
So.
C
C
Your
releases,
so
so
that
that
gives
that
gives
us
like,
is
a
four
month
cycle
and,
and
so
so
it
sounds
to
me
like,
like
there's
at
least
a
a
feeling
like
it
might
be
good
to
have
within
there
some
events
where,
where
possibilities
are,
are
examined
and
prioritized
and
talked
about,
and
you
know
as
as
we're
doing
like
you
have
to
walk
on
this
gently,
because
because
there's
you
know,
this
is
not
the
circumstance
for
any
kind
of
heavy-handed
things,
but
nevertheless,
I
you
know
there's
that
there's
probably
advantages
to
just
being.
C
A
I
mean,
I
think
I
don't
know
if
we
could
do
it
on
a
release
by
release
basis,
but
I
don't
know
if
it
would
be
unreasonable
to
come
up
with
sort
of
five
features
for
20
20
21,
that,
like
we
as
a
community,
are
behind
and
and
we
you
know,
we
really
want
to
find
the
resources
and
get
people
working
on
them.
Even
though
we
can't
commit
to
that
that
that's
something
that'll
have
to
organically
happen.
A
C
You
know
I
I
I
can.
I
can
give
you
an
analogy
that
that
we'll
all
immediately
understand,
I
think,
to
give
everything
it's
what
dress
does
with
the
dress
note
right
like
so
so
we
kind
of
somehow
within
our
world.
I
think,
could
use
a
little
bit
of
that
guidance
that
that
kind
of
you
know
try
chase
this
particular
rainbow.
At
the
moment
we
did
some
that,
with
backdrop
live
right,
I
mean
there.
It
seemed
like
like
at
that
time
there
was
some
of
that
crystallized.
D
B
That
would
be
a
better
choice
than
someone
like
nate
or
myself,
or
tim
or
greg,
who
are
always
around
right.
I
think
that
would
be
good.
C
And
in
particular
I
I
don't
think
I
mean
the
the
part
of
the
the
dress-
note
that
that
I'm
referring
to
here
isn't
isn't
like
dresses,
song
and
dance
thing.
I
mean
that's
fine,
but
but
that's
not
really.
The
core
thing
like
like
really
to
me,
the
most
important
30
seconds
of
the
driest
note
is
at
one
point,
there's
a
bulleted
list
of
you
know
hey
this
time.
This
is
these
are
the
five
things
and,
and
so
so
I
think
it's
like
a
single
powerpoint
slide
once
a
year
is,
is
what
I'm
looking
for.
A
A
It
could
be
a
project
management
committee
thing,
although
I
don't
even
know
if
it
would
have
to
be
that
formal,
but
like
a
blog
post,
might
be
the
output
as
opposed
to
a
speech
that
just
sort
of
says,
we've
we've.
This
is
the
process
we
followed.
These
people
have
discussed
it
and
here's
what
we
think.
Here's
what
we'd
really
like
to
see
happen
this
year,
something.
B
A
And
I
mean
I,
I
think
that
was
implicit
in
in
what
we
were
trying
to
do
last
year,
but
we
never
got
to
the
like.
We
never
go.
You
know
what
we
we
did,
the
brainstorming
phase
of
that
and
we
talked
you
know
and
we
did
the
discussion
phase
of
it,
but
we
never
got
to
the
winnowing
down
the
ideas
and
and
like
doing
a
blog
post.
D
Yeah
I
do
like
that
idea.
You.
B
D
What
direction
so
dres
kind
of
typically
would
do
that
from
a
release
to
a
release
like,
for
example,
here's
drupal
six,
here's
what
we
want
to
do
in
drupal,
7.,
here's
drupal
7.,
here's
what
we
want
to
do
in
drupal
8..
I
I
like
the
idea
of
doing
that
on
a
yearly.
B
D
And
coming
out
saying
hey:
this
is
this
is
what
we
want
to
accomplish
this
year
and
something
that
I've
learned
in
life
is
something
I'm
still
working
on,
because
I
was
not
taught
this,
but
being
intentional
about
doing
something
and
then
focusing
on
it.
D
Obviously
there
could
be
little
things
that
get
shoved
in
there
as
well,
but
it's
kind
of
like
I'm
throwing
this
out
as
a
total,
just
a
total
brain
fart
idea.
But
it's
like
hey.
We
want
to
make
the
front
end
a
java,
javascript
framework
front
end
top
to
bottom.
That
is
what
we're
going
to
work
on
this
year,
because
we
feel
like
that's
the
direction
that
the
web
is
moving
and
we
feel
like
it's
really
going
to
benefit
everybody
involved.
D
You
know
that
type
of
that
type
of
a
deal
I
can
remember
going
to
group
con
in
denver
and
he
was
kind
of
talking
about
the
mobile
and
the
rest
apis
and
services,
and
you
know
mobile,
is
the
future
and
we
really
want
to
make
drupal
sing
with
with
mobile
and,
and
so
he
kind
of
was,
was
creating
kind
of
a
game
plan
of
what
what
they
wanted
to
do
moving
forward
in
the
future.
So
no,
I
think
that
is
good
idea.
D
A
Let
me
just
invite
you
phil,
because
we
don't
even
need
to
talk
about
that.
That
has
been
a
goal
of
ours
for
as
long
as
I've
been
involved
in
background
is
to
do
a
monthly
newsletter,
or
at
least
at
least,
I
think,
for
sure.
Every
release
has
been
a
goal
to
do
a
newsletter,
but
we've
also
talked
about
doing
it
monthly
and
the
problem
isn't
setting
the
goal.
The
problem
is
implementing
it
so
to
be
helpful
in
that
discussion.
What
you
need
to
tell
us
is:
how
do
we
make
it
happen?.
D
A
B
A
B
What
worked
best
with
the
newsletter
is
when
we
had
the
folks
at
fafsa
interactive
and
we
could
be
like
the
blog
posted
up-
here's
the
blog
post
and
they
would
send
us
here's
a
google
doc
of
the
newsletter.
Is
this
the
right
content
and
they
would?
They
would
adapt
the
blog
post?
And
we
would
say
yes
and
then
they
would
also
take
that
content
and
throw
it
into.
I
think
at
the
time
was
like
mailchimp
and
hit
send.
B
The
fact
that,
on
our
end,
there
wasn't
it
wasn't
like
another
person
who
had
already
done
all
of
the
work
for
the
release
that
also
had
to
do.
The
work
on
the
newsletter
was
really
helpful
and
we
do
have
a
little
bit
of
a
technical
challenge
now,
because
we
have
like
reimport
all
of
the
email
addresses
we
got
since
the
last
time.
But
I
think
that's
less
less
of
an
issue
than
just
getting
somebody
to
write
the
newsletter
put
it
into
the
system
and
hit
go.
B
Yeah,
I
mean
it's
a
release,
schedule
right,
so
every
time
there's
a
release,
that's
the
blog
post.
They
will
copy
and
put
in
there.
They
did
also
draft
a
bunch
of
additional
content
for
us
that
we
have
in
like
a
google
drive
somewhere,
but
it
never.
B
We
didn't
ever
like
prioritize
like
well.
Okay,
if
it's
not
a
release,
what
do
we
tell
people
like?
We
don't
have
any
news.
I
mean
it's
all
the
same
stuff,
so
that
I
think
was
was
another
problem,
so
yeah
the
schedule
was
determined
by
our
releases
and
those
those
ones
went
out
regularly
and
additional
ones.
It
would
only
be
like.
Oh,
we
should
tell
everybody
about
bad
camp
when
we
have
a
backdrop
summer
or
something
like
there
would
have
to
be
an
event
at
a
particular
time.
A
Ultimate
yeah,
but
ultimately
I
think
the
problem
is
that
we
have
too
few
people
trying
to
do
too
many
things
like
it's
like
I
feel
like
doing.
A
regular
newsletter
is
something
I
could
do,
but
I'm
also
trying
to
spearhead
a
an
initiative.
I
also
had
an
issue
I
was
advocating,
for
I
also
have
a
you
know,
six
other
things
that
I
really
want
to
do
in
backdrop,
and
so
it's
like
I'm
always
juggling
those
things
and
it's
hard
to
to
regularly
focus
on
the
newsletter
and
not
let
those
other
things
slide.
D
You
know
just
something
that
just
gets
in
front
of
people
and
lets
people
know
that
things
are
moving
forward.
So
the
the
newsletter
idea
for
me
kind
of
ties
in
I
should
say
kind
of
it.
Does
it
ties
in
with
the
backdrop
upgrade
status
and
trying
to
get?
You
know
drupal
7
folks,
to
take
a
look
at
backdrop
just
getting
in
front
of
them
on
a
monthly
basis
and
saying
hey.
You
know
this
is
what
we
did
on
backdrop
come
check
it
out.
D
You
know
something
where
they
can,
they
can
come
in
and
they
can
subscribe
to
it.
It's
kind
of
like
hey
I'll,
just
kind
of
subscribe
to
this
newsletter
and
when,
when
they
when
I
feel
like
they
have
moved
forward
enough
that
it
makes
sense
for
me
to
take
it
serious,
then
I'll
start
looking
at
it
and
just
kind
of
being
in
front
of
a
lot
of
those
drupal
7
folks,
I
I
think
a
newsletter
for
existing
backdrop.
D
C
B
A
Well,
right
I
mean,
I
don't
think
the
template
is
is
the
problem.
The
problem
is
having
somebody
regularly
focus
on
it,
and
it's
like
every
time.
This
comes
up.
I
want
to
say
I'll,
do
that,
but
I've
said
that
before
and
then
fallen
down
on
it
so
yeah,
it's
not
that
we
don't
have
people
who
want
to
do
it
or
that
think
it's
important.
It's
just
that
those
people
have
other
things
that
they
think
are
important
as
well
right.
A
So
it's
like
how
do
we
focus
the
resources
on
it,
and
so
I
mean
I
I
want
to
look
at
the
and
I
don't
want
to
jinx
them,
but
the
the
module
monday
folks
in
germany
that,
for
at
least
a
couple
of
months
here,
have
been
really
disciplined
about
getting
something
out
on
a
weekly
basis
and
how
do
we?
A
B
A
C
I
just
want
to
finish
my
my
thought
as
to
why
I
I
heard
jen
was
like
no,
no,
you
don't
want
to
increase
the
frequency,
but
let
me
let
me
actually
sell
the
idea
of
why
I
think
that
might
make
it
easier.
So
so,
currently
the
the
schedule
is
to
do
it
for
for
each
release,
basically
and
and
the
reason
I
was
proposing,
let
me
get
the
sentence
out
and
then
you
can
shoot
it
down.
C
The
reason
I
was
proposing
more
than
that
is,
is
to
have
a
rhythm
of
a
newsletter,
that's
kind
of
about
the
release
and
then
one
that's
just
knock
so
that
so
that
the
so
it's
not
not
such
a
huge
bear
like
oh,
my
god.
This
is
like
rare
and
important,
and
it's
got
to
be
perfect.
A
Well,
I
mean
I
don't
disagree
with
luke,
but
I'm
I'm
just
still
at
the
point
where
that's
not
the
problem,
because
I
set
a
goal
to
do
it
every
month.
Right,
it's
like
doing
it
more
frequently
to
me,
isn't
necessarily
a
huge
hurdle,
but
unless
we
have
somebody
we
can
set
all
the
schedules
we
want.
It's
like
it's
like
man
saying
well.
What
we
need
to
do
is
pick
the
five
features
we
want
in
1.19.
A
D
Can
some
of
it
be
automated
and
where
I'm
going
with
this
is
to
maybe
pick
the
the
top
five
issues
in
the
queue
that
were
over
the
last
month
that
were
popular
issues,
maybe
somehow
pull
out
some
automated
stuff
out
of
github
that
just
kind
of
creates
that
content
for
us-
and
I
don't
know
it
probably
wouldn't
be
very
pretty
to
do
that,
but
somehow
creating
an
automated
way
of
of
just
getting
some
information
out
there
and
kind
of
yeah
it
just
kind
of
goes
on
autopilot.
D
D
A
I
mean
I,
I
I
think
it's
a
it's
a
good,
the
easier
we
can
make
it
the
more
like
like
for
me
like
I've,
said
I'm
willing
to
step
up
and
do
it,
but
I
haven't
had
a
good
tractor
well,
the
easier
it
is
for
me
to
do
it
the
more
likely.
Maybe
I
would
I.
I
have
set
a
pretty
low
threshold
myself
for
what
needs
to
go
into
the
newsletter.
So
I
don't
think
that
that
simply
automating
it
is
going
to
solve
that
problem,
but
it
could
help.
C
I'll
think
about
content.
I
I'm
going
to
I'm
going
to
like
brutally
throw
it
over
to
sebastian
here,
who's
who's
here
and
like
say,
hey,
so
austria.
What
do
you
think
about
writing
newsletter
articles
you're
you're,
writing
a
book
on
backdrop?
Can
can
you
can
you
drop
your
latest
chapter
into
a
mail
program
and
send
it
out.
F
I
don't
know
how
to
do
it,
and
so
it
would
be
really
great
if
we
could
have
some
sort
of
way
for
people
to
learn
by
doing
learn
by
copying,
and
so,
if
somebody
has
a
website
that
they've
done
and
they
think
it's
maybe
a
little
bit
instructive
and
not
too
difficult,
then
they
could
talk
through
exactly
how
they
did
it
step
by
step.
What
was
their
thinking,
how
they
did
it,
how
they
picked
the
modules
that
they
wanted
to
use
and
how
they
went
about
it
step
by
step.
F
F
F
F
I
have
not
been
successful.
I've
been
looking
at
the
little
thing
that
tim
did
for
me
starting
website,
and
I
couldn't
figure
out
how
he
got
where
he
got
it.
Wasn't
it
wasn't
easy
to
figure
out
going
through
okay?
Well,
I
know
it
has
to
do
with
feels,
and
I
know
it
has
to
do
with
with
layouts.
I
know
it
has
to
do
with
this
and
the
other,
and
then
I
would
try
to
go
and
dig
it
out,
and
I
couldn't
do
it.
C
A
Sorry,
I'm
going
to
indulge
myself
in
a
final,
quick
comment,
which
is,
I
think
we
need
to
figure
out
like
for
me.
I
could
be
more
effective
at
these
things
if
there
were
some
sort
of
a
an
accountability
process
in
the
like
some
way
of
a
better
way
of
of
sort
of
like
setting
deadlines
or
or
setting
aside
time
like
having
work
sessions
where
we,
where
we
actually
get
together
and
sort
of
help,
each
other
work
on
things,
as
opposed
to
have
broad
philosophical
discussions.
F
I
think
that's
a
really
a
really
great
idea.
Sometimes
it's
good
not
for
one
person
just
work
on
something,
but
for
two
people
to
work
on
it
and
they
keep
each
other.
He
said:
you're
gonna
do
this.
Now,
I'm
here
I'm
trying
to
get
you
to
do
it.
You
know,
and
they
remind
the
person
and
they
help
out
some
whatever
they
can
do,
and
back
and
forth
at
least
two
people.
But
if
you
can
do
three,
that's
even
better.
F
Okay,
so
it's
gotta
be
like
two
or
three:
it's
something
simple
and
easy
where
they
remind
each
other
they're
your
buddy,
you
know,
and
so
you
have
a
buddy
system
and
the
buddy
reminds
you
where
you
said
you're
going
to
do
this
and
we
got
it
scheduled.
So
let's
do
it
that
that
works,
so
everybody
picks
a
buddy
or
something.
A
I
think
so
so
luke
gave
me
the
opportunity
to
hold
myself
accountable
to
end
this
meeting
and
I
failed
so
let's
end
this
meeting,
I'm
going
to
go
ahead
and
cancel
or
stop
the
recording
and.