►
From YouTube: Backdrop Outreach April 15, 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
Least
there
we
go
that's
taken
care
of
so
welcome
everybody
to
our
week.
Our
bi-weekly
is
that
right,
our
bi-weekly
outreach
meeting
we
are
in
the
midst
of
for
those
watching
at
home.
We
are
in
the
midst
of.
We
recently
changed
our
meeting
schedule,
which
may
be
affecting
a
participation
a
little
bit,
but
I
also
just
think
that
a
lot
of
people
are
overwhelmed
right
now
with
a
lot
of
stuff.
So
but
we're
going
to
go
ahead
and
do
our
meeting
as
regular.
A
So,
let's
just
jump
in
with
the
three
of
us
and
do
our
weekly
introductions
just
ask
people
to
identify
who
they
are
where
they're
from
and
just
any
tidbit
they
want
to
share
about
either
what
they're
doing
with
backdrop
or
or
life
in
general.
I
suppose
I
am
tim
erickson,
I'm
coming
to
you
from
deerwood
minnesota
about
two
hours,
north
of
the
twin
cities,
saint
paul
and
minneapolis,
and
I
will
just
share
that
I've
been
really
overwhelmed
with
life
and
work
lately.
A
So
backdrop
hasn't
been
getting
a
lot
of
attention,
but
we
did
have
a
nice
meeting
about
civvie
crm
stuff
for
backdrop
dot
org
earlier
this
week,
and
maybe
we
can
talk
briefly
about
that
later.
C
C
I
should
say
a
extraordinary
beginner's
guide
to
backdrop
ultimate
beginner's
guide,
I
might
say,
to
try
to
get
people
up
to
speed
so
that
they
can
use
it
if
they're
not
already
developers.
A
lot
of
the
users
on
the
backdrop
are
former
drupal
developers.
They
take
to
it
right
away,
but
we
need
people
who
who
have
no
skills
to
be
able
to
use
backdrop.
C
So
people
can
see
you
and
get
to
know
you
and,
and
you
look
good
so
those
two
things
are
worth
looking
at
those
aren't
available
to
the
public.
I
don't
think
or
are
they?
Oh?
If
you
posted
them
on
github,
they
are
okay,
so
somewhere
we'll
post
how
you
can
get
to
those
to
look
at
those
if
you're
interested
in
doing
video
tutorials
for
anything,
but
especially
for
backdrop,
because
we
want
some
great
backdrop
tutorial
videos.
B
So
great
hi,
my
name
is
greg,
I'm
usually
in
australia,
but
for
the
past
year
stuck
in
greece
yeah,
we
skipped
the
or
at
least
I
didn't
join
the
previous
meeting.
So
I'm
trying
to
catch
up
with
things
instead
of
because
of
the
time
changes,
the
previous
week's
meetings
were
sort
of
like
unofficial
discussions,
so
I'm
gonna
bring
certain
things
up
later
in
the
agenda,
but
yeah.
A
Going
good,
so
I'm
going
to
try
a
couple
of
things
this
week
to
sort
of
move
us
through
and
maybe
be
a
little
more
action-oriented
this
week,
and
one
of
the
things
that
I
started
two
weeks
ago
is
experimenting
a
little
bit
with
so
two
things
that
we're
gonna
try
experimenting
with
using
miro
a
little
bit
more
to
which
I'll
show
you
in
a
second
I'll
share
my
screen,
but
also
we're
going
to
try
and
use
a
portion
of
these
meetings
just
to
get
working
on.
A
Backdrop
live
each
every
meeting
and-
and
we
also
have
other
topics
every
week.
So
I'd
like
to
try
and
break
the
meeting
into
like
three
15-minute
segments
so
that
we
know
it
won't
be
precise.
We're
not
going
to
you
know,
stop
exactly
at
15
minutes,
but
the
point
is
so
we
know
if
we're
falling
behind
and
can
try
to
move
on
and
make
sure
we
got
time
to
at
least
address
all
the
topics.
A
And
I
think
if
there
are
some
topics
that
are
just
too
big
to
fit
into
this,
then
we
need
to
talk
about
another
meaning
yep.
So
the
I'm
going
to
start
out
with
I'm
going
to
go
ahead
and
share
my
screen
briefly,
and
I
I
know
some
people
prefer
that
we
not
do
that
the
whole
meeting
so
I'll
just
do
it
for
a
little
bit
for
this
first
section
in
particular,
what
I'd
like
to
do.
A
I've
created
this
mural
board,
which,
for
me
at
least,
is
helpful
to
sort
of
visualize
some
of
the
weekly
ongoing
stuff.
We
have
to
do,
and
hopefully
move
through
it
and
basically
to
keep
things
going
in.
Our
blog.
I'd
like
to
you
know,
break
keep
this
list
full
of
ideas
and
also
get
some
stuff
scheduled
and
really
try
harder
to
meet.
You
know
to
get
something
out
at
least
every
week.
A
I
think
that
we
can
do
that,
especially
maybe,
if
we
loosen
our
standards
a
little
bit
and
just
you
know,
write
sort
of
short,
even
short
announcement
blog
posts
that
just
let
the
community
know
what's
going
on,
there's
a
lot
of
things
that
do
happen
in
backdrop
that
really
don't
get
out
to
the
public.
Very
well,
for
example,
this
time
switch
that
we
we
did
this
time
switch,
and
we
never
really
did
a
blog
post
until
today,
and
we
made
this
decision
like
three
weeks
ago.
A
The
other
thing
is
I,
for
one,
do
a
lot
of
tweeting
and
I
would
love
to
actually
use
a
little
bit
of
time
in
this
meeting
to
just
sort
of
brainstorm
and
keep
a
a
list
of
ideas
here
that
that
we
can
refer
to
when
tweeting,
also,
the
virtual
user
group.
I
think
if
we
make
a
point
to
try
and
have
at
least
two
virtual
user
groups
scheduled,
I
think,
with
our
with
what
we're
learning
with
backdrop
live,
we
can
have
really
productive
sessions
that
aren't
heavily
scheduled
and
prepared.
A
So
I
think,
there's
no
reason
we
can't
like
every
two
weeks,
just
have
a
topical
discussion.
Have
somebody
prepared
to
lead
it
and
somebody
prepared
to
host
it?
Two
weeks
ago,
sarvashri
specifically
asked
said
he'd
like
to
see
a
virtual
user
group
on
creative
custom
views,
so
anyways
I'd
like
to
just
for
this.
This
segment
of
this
meeting
fill
in
some
of
these
things,
and
it
occurred
to
me
if
we
could
come
up
with
at
least
one
more.
A
So
we
we
have
we're
a
little
bit
limited
in
participants
today,
but
I'd
love
to
come
up
with
another
virtual
user
group.
I
think
for
this
this
upcoming
one
creating
custom
views.
A
A
It
could
start
with
just
somebody
walking
through
the
views
interface
and,
for
you
know,
try
and
explaining
it
to
a
beginner
would
be
a
way
to
handle
that
and
then
to
just
sort
of
open
it
up
to
discussion
and
questions
and
have
people
share
interesting
things.
They've
done
with
views
or
or
you
know,
bring
their
own
questions.
A
So
if
anybody
is
willing
to
facilitate
that
or
you
know
to
be
the
presenter,
let
me
know
can
we
come
up
with
at
least
one
more
topic
like
that
that
we
could
get
on
the
schedule
and
recruit
a
volunteer
for.
C
We
could
just
copy
what
they've
done.
Oh
also,
olaf
had
a
nice
presentation
on
on
the
web
for
creating
a
website.
A
So
what
we're
looking
for
right
here
sarvashri
are
specific
ideas
that
we
can
do
in
a
virtual
user
group.
So
this
would
be
a
live
discussion
that
we
could
have
and
we
need
a
topic
idea.
Olaf's.
The
thing
that
you
really
like
that
olaf
did
was
about
layouts.
Wasn't
it
or
was
it
more
than
that
yeah?
It
was.
A
Sure
so
one
way
to
think
about
this
is
we
could
sort
of
walk
through.
A
This
would
be
a
way
of
generating
some
video
content
with
that
kind
of
an
outline
sarvashri.
But
I
want
to
be
clear
that
the
idea
for
the
virtual
user
groups
is
that
they're,
interactive
and
so
inherently
less
prepared,
they're
not
going
to
be
like
a
professional
tutorial
video,
but
they
they
might
be
better
than
nothing.
So
we
could.
You
know
we
could
take
a
lot
of
those
topics
like
layouts,
creating
custom
views
and
make
them
into
user
groups.
Yeah.
C
We
can
start
out
like
everything
that
you
do
when
you're
writing.
You
start
it
with
a
scratch
pad.
You
know,
and
this
is
like
a
scratch
pad.
You
know
if
you
get
people
together,
you
talk
about
stuff,
you
figure
out
what
you
want
to
cover
and
it's
all
sort
of
chaotic
but
everybody's
introducing
their
ideas.
C
Then
you
go
back
and
look
at
that
and
you
structure
it
and
create
the
tutorials
from
that.
A
Okay
sure,
so
these
these
virtual
use,
some
of
these
at
least,
could
be
sort
of
dry,
runs
or
or
like
note
taking
for
that,
let's
I'm
going
to
take
as
an
idea
the
the
blog
post
that
olaf
did
and
see.
If
we
can't
turn
that
into
a
user
group
meeting
and
then
that
blog
post
could
serve
as
background
materials
and
then
we
could
basically
have
a
discussion
kind
of
walk
through
some
of
what
was
covered
there
and
give
people
a
chance
to
ask
questions
yeah
yeah.
A
A
So
I'm
gonna
put
this
down
as
a
tentative
idea
for
the
second
one
and
we
don't
have
to
plan
out
any
further.
If
anybody
has
another
specific
idea
for
now,
I
I'm
going
to
look
at
the
blog
post
and
see.
I
think
it
was
primarily
about
using
layouts,
but
it
might
have
been
a
little
bit
more
generic
than
that
and
either
way
it
was
in
two
parts.
Yeah.
B
Yeah,
okay,
by
the
way
dan
and
phil,
have
joined
the
group.
I
don't
know
if
they
have
okay,
hello,.
A
Hello,
hello
right
again,
so
we're
just
trying
to
brainstorm
we're
going
to
spend
about
another
five
minutes
and
then
move
on
to
some
other
topics.
Just
virtual
user
group
ideas.
I
think
we've
got
two
ideas
out
there,
the
other
thing,
our
blog
post
articles
or
twitter
posts
things.
A
These
could
also
go
into
a
dashboard
notifications.
Is
there
anything
going
on
right
now
that
we
should
be
talking
about
and
I'll?
I
can
start
this
out
with
a
few
things
I
listed.
We've
come
up
with
some
possible
virtual
user
groups,
so
these
are
things
we
want
to
talk
about.
We
are
coming
up
on
the
code
phrase
sort
of
reminding
people
via
social
media
by
coming
up,
while
it's
two
weeks
away
right.
B
Yeah
so
around
may
1st
there's
going
to
be
a
call.
Freeze,
I'm
going
to
take
the
dates.
May
1st
is
actually
a
saturday,
so
we
may
decide
to
give
us
that
weekend
and
do
the
content
freeze
on
on
the
third,
which
is
a
monday
as
we
usually
do,
or
maybe
we'll
do
the
content
freeze
on
friday.
I
don't
know
okay,
but
it
will
be
around.
May
1st
yeah
so
yep,
okay.
So
that's
a
topic,
the
sorry
and
we
should
it's,
not
a
cod
freeze,
it's
a
feature
freeze.
Yes,
that's
a
good
point.
A
A
It
occurred
to
me
there
was
some
talk
on
twitter
yesterday
about
drupal
talking
about
the
project
browser.
I
think
luke
posted
something
in
tulip
about
this.
B
Yeah
I
actually
watched
the
dress,
not,
and
I
actually
made
a
comment
on
on
the
slack
channel
at
the
company
that
I
worked
for,
saying
that
this
was
a
a
dress
knot
that
I
enjoyed,
which
hasn't
happened
for
many
many
years
now,
and
it
was
less
upsetting
and
they're
actually
they're.
Actually,
there
was
a
section
about
the
forgotten
user
or
site
builder,
which
was
exciting,
and
my
hope
is
that
they're
probably
going
to
start
doing.
At
least
they
acknowledge
that
they
overcomplicated
things
for
certain
people.
B
A
B
Yeah
theresa
at
some
point
showed
a
screenshot
of
four
project
browsers
by
four
competitors,
and
I
said,
oh
backdrop
should
be
there
as
well.
C
It,
what
is
this
project
browser
thing.
B
Oh
yeah,
so
that
it
basically
intro
for
as
it
is
now
in
drupal,
7
and
8
and
9.
If
you
want
to
install
additional
modules
that
are
not
included
with
core,
you
have
to
go
to
drupal.org.
B
First
of
all,
if
you're
a
new
user
as
presented,
it's
like
first,
you
have
to
figure
out
what
modules
are
and
how
they
add
functionality
to
drupal.
And
then,
once
you
understand
what
modules
are
you
need
to
know
where
to
look
for
them?
Find
them
download
them
put
them
on
your
server,
then
install
them.
So
this
is
a
process
that
is
tedious,
but
I'm
I'm
taking
it
that
thing,
you're,
gonna
fire
and
it's
just
so
that
we
can
show
it
live
so
good.
B
So
a
project
browser
is
something
that
we've
been
enjoying
for
many
years
now
and
it's
something
that
wordpress
also
has,
and
I
think
that's
where
we
borrowed
the
idea
from
so
we
we
still
have
the
traditional
way
to
allow
people
to
install
modules,
the
way
that
they
used
to
with
drupal
by
manually,
downloading
and
exporting
the
code
or
pasting
a
url
to
a
zip
file
from
the
user
interface.
But
we
also
have
a
visual
project,
selector
downloader
and
installer,
which
is
what
team
is
going
to
show
you.
A
C
A
B
A
What
else
is
going
on
when
we
have
well?
These
things
overlap
a
bit.
We
also
have
some
blog
post
ideas.
Any
of
these
blog
posts
could
turn
into
tweets,
of
course,
but
once
we
get
them
done
and
so
oops
we
got
the
pmc
update
twice
some
of
the
topics
we
have
in
mind.
We
just
need
somebody
to
write.
Why
did
I
do
that?
Is
a
pmc
update
there?
We
had
a
meeting
earlier
this
week
about
cvcrm
and
we'd
like
it's.
A
I
think
we
might
be
at
a
stage
where
somebody
could
post
an
update
about
sort
of
what
that
project
is
doing
and
what
our
plans
are
an
update
on
our
code
of
conduct
sarvashri.
If
you
wanted
to
do
like
a
in
fact,
I
would
encourage
you
to
do
a
blog
post
that
talks
about
what
your
goals
are
for
your
videos
and
what
you're
looking
for
people
to
do,
and
that
might
be
a
way
to
find
some
people.
Other
people
who
are
interested.
C
B
And
I
would
like
to
subjects
I
don't
know
where
they
fit,
whether
they're,
feeding
the
tweeting
or
blogging
or
doing
a
user
group
about
it,
but
easy
entry
to
start
contributing
in
any
way
be
it
code,
be
documentation
and
then
also
mentioning
some
things
that
certain
things
that
a
few
members
of
the
community
expressed
that
we
should
sort
of
like
develop
a
mentality
and
a
an
environment
where
we
don't
even
unknowingly
sort
of
like
imply
that
contribution
is
required
or
expected
from
people
so
that
we
don't
put
that
burden.
B
A
Well
sure
I
mean
the
thing
that
you
said
that
was
specific
to
me
was
sort
of
talking
about
expectations.
That
seems
like
a
really
specific
topic
in
terms
of
contributing
in
general,
there's
so
much
that
we
could
do
that.
I
right
what
I'd
be
looking
for
is
more
specific
ideas.
A
I'm
going
to
say
one
quick
thing
about
that,
and
then
maybe
we
should
move
on
to
another
topic,
which
is
that
I
I
like
that
idea
on
the
one
hand.
But
what
concerns
me
is
the
comment
that
rob
feature
made
a
few
weeks
ago
about
all
of
our
channels
being
focused
on
getting
people
to
contribute
and
not
just
users,
and
I
feel
like
it
might
be,
that
the
virtual
user
group
is
a
place
where
yeah
fair
enough.
Now.
A
Just
using
backdrop
and
not
turn
it
into
that
doesn't
mean
we
don't
talk
about
contribution.
Obviously
it's
going
to
come
up
and
it
can
be
a
part
of
the
discussion,
but
but
maybe
we
keep
the
user
group
focused
on.
How
do
you
use
backdrop?
That's
just
a
thought
right,
I
don't
know.
Have
we.
A
We
actually
did
just
recently
that
that
was
like
one
of
our
last
two
or
three
topics
cool.
So
you
can
check
the
video
on
that.
It
was
a
kind
of
a
loose
discussion
about
it.
Matias
helped
talk
about
some
showed
a
site
that
he
was
working
on.
B
A
Okay,
great
I'm
gonna,
stop
sharing
and
I
think
move
on
to
what
we
talked
about.
Jen
and
phil
before
you
got
here,
was
sort
of
three
dividing
the
meeting
into
three
agendas:
the
first
three
parts
about
15
minutes
each
the
intro
part
that
we
just
did
and
now
spend
about
15
minutes
talking
about
backdrop,
live
just
getting
that
discussion
going
and
then
leaving
15
minutes
to
talk
about
whatever
else.
A
So
the
the
the
next
backdrop
live
is
scheduled
for
july
shortly
after
the
4th,
like
the
10th
or
something
it
has
been
suggested,
that
we
try
to
use
at
least
some
time
in
these
meetings
to
get
that
process
going
earlier.
We've
already
waited
a
while
it's
so
we're
april,
it's
april
15th.
So
it's
made
well
we're
three
months
out,
so
we
still
have
quite
a
bit
of
time,
but
I
thought
what
might
be
a
useful
outcome
for
the
meeting
today
would
be
identified.
What
are
the
first
things
that
need
to
happen?
B
I
have
a
few
questions
yep,
so
I
know
questions
observations
as
well.
So
we've
we've
tried
to
ease
things
with
like
by
creating
a
dedicated
events
website
and
a
github
repository
where
we
can
discuss
things,
and
I
guess
now
we
have
templates
for
sort
of
like
recreating
the
the
these
recurring
events.
B
Are
there
any
tasks
that
we
sort
of?
Like
I'm
sure
there
are
a
lot,
but
I
mean
major
tasks
that
we
need
to
do
with
regards
to
sort
of
like
you
know,
preparing
something
that
can
be
reused
which
can
be
paired
with
the
recent
sort
of
like
cvc
or
anything,
and
you
know
reaching
out
to
people
that
are
going
to
join.
B
Yes,
so
how
to
use,
for
example,
cvcrm,
so
that
we
can
gather
information
about
people
that
have
already
attended
or
people
that
express
interest,
and
then
you
know
communicating
things
to
them,
but
also
the
various
tools
that
we've
already
built,
and
you
know,
we've
identified
tasks
that
need
to
happen.
It's
time,
maybe
maybe
sort
of
like
deciding
early.
Who
has
time
for
what
and
things
like
that.
B
B
Sense
to
me
and
what
helps
us,
for
example,
with
releases
when
we
do
releases,
we
have
a
really
release
template
which
we
reuse
and
actually
it
each
task
in
on
the
template
has
a
candidate
people
that
it
can
be
assigned
to.
It
doesn't
mean
that
it's
going
to
be
assigned
to
that
person,
but
it's
sort
of
like
that
person
has
offered
to
do.
That
is
knowledgeable
enough
to
do
that
specific
task
and
usually
we
assign
it.
B
If
they
can't
do
it,
they
can
remove
themselves,
of
course,
but
I
was
proposing
to
sort
of
like
break
down
the
the
tasks
that
we
do:
repetitively
identify
which
people
usually
volunteer
or
know
how
to
do
them,
and
then
you
know
preparing,
and
by
asking
these
people,
are
you
going
to
be
able
to
do
it
in
the
next
one.
A
Sure
so,
I'm
not
sure
that
that
wouldn't
be
a
good
use
of
our
time.
Right
now
would
be
to
sort
of
break
down
the
big,
the
big
tasks
while
doing
that
identify
which
ones
are
most
important
but
and
also
try
start
trying
to
assign
names
but
doing
it
in
a
way
that
is,
reproducible,
like
you,
said
it's
kind
of
a
template.
B
Sense
yeah:
I
understand
that
this
cannot
be
done
in
one
go
like
this.
This
is
this
feels
like
a
documentation.
Sort
of
like
thing
that
will
improve
will
be
a
live
thing,
ongoing
thing
that
will
be
improving
as
we
go
it's
time
that
we
do
things
and
learn
from
from
that,
but
it
would
be
great
to
sort
of
like
documenting
things
as
we
do
and
keeping
record
actually
of
who
does
what
and
what
needs
to
be
done.
C
Is
it
software
to
help
this,
like?
I
use
outline
processors
a
lot,
so
I
have
a
sequence
beginning
to
end
and
there
are
headings
and
subheadings
within
that
sequence.
Outlines
are
great
for
any
kind
of
organization.
B
Yeah
so
so
summaries
at
the
top
of
issues
like
in
any
comment
that
you
add,
you
can
add
a
dashbase
brackety
thing
and
it
converts
that
into
a
checkbox.
So
you
can
put
a
series
of
such
things
and
you
can
have
multiple
checkboxes
of
tasks
that
need
to
be
done
and
then,
when
they're
done,
we
take
them
off,
and
this
is
what
we
actually
use
for
our
releases.
B
So
I
was
thinking
that
maybe
we
can
produce
such
a
thing.
It
could
be
rough,
like
only
only
whatever
comes
to
mind
now
rough
things
like
you
know,
change
the
the
the
the
update
the
events
side
to
mention
the
next
date
of
the
live
archive,
the
previous
one
and-
and
you
know
maybe
links
to
any
recordings
or
things
so
repetitive,
things
that
need
to
happen.
C
Just
a
task
list
is
what
it
is
in
outline
processor.
You
can
drag
and
move
things
up
and
down
easily.
A
A
Yeah
we've
got:
we've
got
10
minutes
to
work
on
this
right
now,
so.
B
B
So
yeah
is,
it
is
the
event.
Sorry,
my
computer
is
always
getting
really
slow
when
zoom
is
on.
So
have
we
updated
the
events
side
to
mention
the
next
date,
even
if
it's
identity.
A
There
is
it's
on
the
list
of
it's
on
the
list
of
events
as
a
tentative
date,
but
that's
as
far
as
we've
gotten.
If
you
go
to
the
website
and
you
go
to
events,
you'll
see
tentative
date
for
the
next
backdrop,
live.
A
Getting
the
registration
form
set
up,
coordinating
with
with
sfo
software
freedom,
conservative
or
sfc.
A
D
No,
I
I
re
poked
them
recently
and
haven't
heard
anything
I
can
do
it
again.
A
B
A
B
A
B
A
That's
cool
great,
the
I'll
quickly
say
this
about
civi
crm,
because
it's
it's
relevant
here.
It's
been
raised
like
how
we
could
use
cvcrm
to
better
manage
events
at
the
nextbackdrop.org.
We
had
a
meeting
on
tuesday
of
that
was
just
this
week.
Wasn't
it
yep
about
integrating
using
civvy
crm
better
as
an
organization
in
general,
and
I
think
what
we
decided
in
that
meeting
was
that
getting
events
going
on
cbcrm
may
not
be
our
first
priority,
but
it
is.
It
is
a
long-term
goal.
A
A
We
just
want
one
instance
of
cvcrm,
so
I
don't
think
we
should
count
on
having
like
being
able
to
use
civic
crm
for
the
next
backdrop,
live,
although
it
could
happen,
but
but
in
the
meantime
I
think
we
should
just
go
ahead
and
get
the
current
events
website
going
for
that.
What
are
other
things?
We
could
be
working
on
well,
any
tasks
that
need
to
happen.
It's
like.
B
D
So,
usually,
with
a
camp
we
have
like
a
like
an
old
old-school
in-person
camp.
D
There
was
like
a
whole
bunch
of
dates
that
were
established
ahead
of
time
and
it
was
like
okay
well,
we
know
that
we're
gonna,
open
registration
on
x
date
and
then
on
y
date,
we're
going
to
open
session
submissions
and,
on
z,
day
we're
going
to
select
the
sessions
and
then
on
you
know
a
date
we're
going
to
shut
everything
down
and
lock
it
lock
it
down
when
we're
out
of
tickets
or
whatever
it
is,
and
we
haven't
done
that
yet
for
backdrop,
we've
just
been
like
oh
back,
to
live
this
and
do
all
the
things.
D
I
don't
know
that
that's
something
is,
you
know
necessary
for
an
online
event,
but
I
think
it
would
really
help
in
terms
of
publicity,
if
we
have
those
milestones
just
to
motivate
us
to
be
like.
Oh,
let's
tell
people
about
it
again,
let's
tell
people
out
again
and
then
more
people
might
sign
up
ahead
of
time.
D
So,
since
we
know
the
approximate
dates
of
all
these
upcoming
events,
we
might
even
be
able
to
like
set
up
a
pattern
where,
like
we
know
for
sure
it's
always
a
month
backwards,
and
then
we
would
have
the
dates
for
the
rest
of
the
year.
We
could
set
up
the
nodes
on
backdrop
cms.org.
We
could
even
use
scheduler
to
like
automatically
publish
them
and
have
these
things
go
out
to
the
home
page
on
time.
D
It's
something
we
haven't
thought
about
before,
but
now
that
you
bring
an
upgrade.
I
think
it
could
be
easy
to
do
that
using
the
system
that
we
have
in
place
now.
A
Yeah,
yes,
I
think
so
and
like
so,
I
added
a
third
category
of
sort
of
things
to
list
right
now
which
tasks,
roles
and
sort
of
dates
or
deadlines
and
by
dates
or
deadlines.
I'm
not
looking
for
the
date
but
more
the
the.
What
are
the
things
that
we
should
go
on
that
schedule.
B
Jen
was
mentioning
announcing
the
dates
where,
where
the
registration
is
open
and
announcing
it
ahead
of
time
that
that
registration
is
going
to
open
for,
but
I
think
that
registration
is
allowed
up
the
last
minute,
even
right,
so
yeah
that
doesn't
apply
much
to
us,
but
sessions
also
until
last
minute.
B
A
B
I
would
actually
be
more
specific:
it's
open
force,
submission
proposal
for
sessions
or
not
for
sessions
exactly
because
it's
not
the
actual
session
yeah
and
then
on
the
roles.
We
also
have
the
security
sort
of
like.
I
don't
know
what
you
call
it:
the
guard
whatever
for
the
the
main
room,
the
person.
What
are
we
calling.
A
Exactly
I'm
just
going
to
call
them
greeters,
but
or
we
also
had
like
a
safety
committee
or
something
idea,
I'm
going
to
put
both
of
those.
A
Other
discussions,
so,
if
we're
going
to
try
this
is
this
has
got
us
going
and
I
think
building
out
this
agenda,
putting
names
to
this,
I
would
like
to
figure
out.
I
think
the
most
for
me,
the
most
and
two
important
things
for
us
to
do
quickly
is
one
figure
out
the
whole
registration
problem
with
the
civi
with
sfc
and
possibly
even
get
them
working
because
they,
basically
they
have
to
set
up
something
for
us
to
accept
payments
through
their
system
and
they
need
enough
notice
and
so
like.
A
Let's
get
out
ahead
of
that
this
time
and
make
that,
like
one
of
the
priorities
to
me,
the
other
priority
is
that
we're
getting
a
lot
of
feedback
that
they
love.
People
love
this
idea
of
an
international
schedule,
but
I
just
don't
foresee
it
working
well
unless
we
have
folks
in
europe
and
that
are
designated
as
point
people
that
can
sort
of
be
the
contact
for
making
sure
we
have
volunteers
making
sure
that
we're
getting
session
submissions
at
those
times.
B
Maybe
until
we
sort
of
like
because
it's
my
understanding
that
cv
does
that
it's
soliciting
help
from
people
like
they
it
lets
you
allow
it
lets.
People
say
that
they
are
willing
to
help
with
certain
tasks
and
which
times
of
the
year
they're
available.
But
now
we
can
do
it
manually.
We
can
ask.
We
can
actually
solicit
volunteers
for
lives,
so
ask
them
if
they
will
be
available
during
those
dates
and
what
they're
willing
to
help
with.
A
Yeah,
but
what
I'm
looking
for
right
now
is
more
than
just
a
volunteer
on
the
day,
I'm
looking
for
somebody,
that's
sort
of
willing
to
be
the
point
person
for
you
to
like
represent
europe
during
this
process.
Right
because
I
think
that's
thinking
about
the
the
the
issues.
That's
also
like
encouraging
people
from
the
you
know.
I
think
one
of
the
problems
we
get
in
is
that
we're
not
getting
like
session
ideas
from
europe
early.
So
we
don't
get
anything
on
the
schedule.
A
A
B
B
A
A
I
we
could
tweet
that
could
be
a
good
tweet.
I'm
gonna
put
it
on
the
tweet
on
my
tweet
schedule
for
something
to
remember.
A
I
feel
like
we've
got
to
start
here.
People
can
add
to
this
this
list
of
tasks
and
I
think,
certainly
general.
I
could
probably
either
of
us,
dump
a
bunch
of
ideas
in
here
just
off
of
our
head
later
where's,
that
going
to
be
so
it's
in
the
agenda
for
this
week,
but
I
think
jen
has
also
made
a
ticket
where,
in
which
repo.
D
A
D
But
for
releases
I
don't
think
we
actually
have
a
template
in
the
queue
because
we
don't
want
it
to
bother
everybody
else,
who's
creating
issues.
It's
only
like
it's
in
our
github
repository
as
a
flat
file,
but
I
think
in
this
case
it
might
be
useful
to
have
it
in
the
public
queue,
because
my
vision,
long
term
is
this
event.
Site
can
be
used
by
anyone
in
any
location
to
host
any
backdrop
event
and
so
having
something
for
them.
It
would
be
like
this
is
what
you
should
do
to
make.
D
Your
event
could
be
really
helpful,
so
I
don't
know
maybe
thinking
too
long
term,
but.
B
A
B
How
the
the
the
the
templates
evolved
with
with
the
releases
is
like
on
the
current
currently
released.
We
said:
oh,
we
need
a
task
for
this
and
then
we
would
update
that.
So
we
can
do
the
same
thing
it's
worth
for
us,
so
yeah.
A
A
Just
to
reiterate
that
getting
that
registration
stuff
going
with
sfc
and
getting
our
sort
of
our
geographic
coordinators
maybe
a
way
to
phrase
that
would
be
identifying
a
group
of
people
that
that
included
geographic
coordinators.
So
having
sort
of
a
steering
committee
for
this
event
would
be
good
that
some
specific
names
as
opposed
to
whoever
shows
up
in
any
given
week.
A
So,
let's
think
about
that
for
the
next
meeting
and
then
I'm
going
to
suggest
we
move
on
and
we
talk
about
so
move
on
to
the
other
portions
of
our
of
our
topic.
A
For
a
couple
of
seconds,
the
two
things
that
we've
identified
so
far
are
this
community
talk?
I
actually
I
don't
know
if
sarvajri
has
anything
new,
but
we've
been
talking
a
lot
about
video
tutorials
and
if
we
have
time
for
that,
we
can
but
I'd
like
to
start
with
phil's
issue
and
or
this
the
the
community
talk
one
which
may
be
the
same.
Go
ahead.
Phil.
E
Yeah
community
talk,
I'm
assuming
it's
the
same
thing.
Basically
formal
location
for
community
discussion
is
that
kind
of
what
you're
thinking.
E
Okay,
so
greg,
and
I
we
kind
of
talked
last
week
I
mean
for
for
anybody-
I
guess
that's
watching
or
listening
on
the
back
end,
there's
kind
of
two
schools
of
thought
as
far
as
where
this
should
be,
how
the
main,
I
think,
what
we'll
probably
go
ahead
and
do
for
a
short-term
solution
is
put
it
into
github.
In
the
backdrop,
dash
ops
organization
and
just.
E
To
house
this
discussion
right
now,
all
of
this
discussion
is
sitting
in
backdrop,
cms.org
repository,
which
really
just
needs
to
be
relegated
for
tasks
and
changes
that
need
to
be
made
to
the
backdrop
cms.org
website.
So
we
need
to
pull
all
that
discussion
out
of
that
repo
and
put
it
into
its
own
repo,
so
that
you
know
anything
that
is
about
the
organization
about
backdrop
that
has
nothing
to
do
with
code.
It
has
to
do
with
moving
things
forward.
We
need
kind
of
a
formal
place
and
that's
what
this
overall
discussion
is
about.
E
So
I
think
I
think,
really
what
we
need
to
probably
go
ahead
and
do
set
up
that
single
repository
need
to
decide
on
a
name,
there's
a
couple
floating
out
there
I'll
get
to
that
in
a
minute,
but
go
ahead
and
just
create
a
place
that
general
general
discussion
can
take
place
long
term.
If
it's
decided
that
we
need
to
break
that
out
into
another
place.
You
know,
for
example,
into
forums
on
the
backdrop
website
or
into
a
different
github
organization.
E
You
know
just
kind
of,
depending
on
the
scale
of
of
that
thing
and
logistics.
We
can
kind
of
discuss
moving
it
moving
things
around
or
reorganizing
where
that
discussion
takes
place
at
a
later
time,
so
the
the
immediate
issue
is
get
it
off
of
that
backdrop,
cms.org
repo
and
into
its
own
repo,
and
that
really
needs
to
take
precedence.
E
So
as
far
as
names
go.
For
that
repo
backdrop,
dash
community
has
been
one
thought
me
personally.
I
like
the
idea
of
doing
the
backdrop
dash
talk
and
kind
of
doing
a
branding
around
backdrop
talk,
meaning
anytime.
You
see
anything
from
that
kind
of
a
brand
standpoint
of
backdrop.
Talk
get
it
to
a
point
where
people
understand
hey.
This
is
discussion
about
the
community.
E
This
is
discussion
about
moving
things
forward
and
ideas
about
how
we
can
grow
as
a
community,
as
opposed
to
you
know,
code
related
talk,
so
thoughts
on
names,
thoughts
on
the
overall
discussion.
D
E
A
A
B
Not
necessarily
everything
else,
but
things
like,
for
example,
funding
or
monetizing
as
it
was
called.
This
has
nothing
to
do
or
very
there
might
be
sub
tasks
that
will
need
to
sort
of
like
be
communicated
or
advertised
or
whatever.
You
want
to
call
it
on
the
main
site,
but
it
has
nothing
to
do
with
the
website
itself.
So
we
need
a.
This.
Is
a
community
discussion,
so
basically
things
like
that
matters
like
that
and
one
crucial
thing
that
should
be
discussed
as
well:
it's
not
whether
it's
going
to
be
a
github,
repo
or
a
forum.
B
It
could
be
actually
both,
because
what
we
discussed
with
phil
is
the
end
result
will
be
a
policy
and
a
document
or
multiple
policies
and
documents,
and
that
needs
github
repo,
so
we'll
have
the
ripple,
but
for
discussions,
maybe
github
is
not
the
perfect
tool.
So
maybe
we
need
a
also
a
matching
category
on
our
forum,
where
people
that
don't
have
github
accounts.
B
Sorry
github
accounts
you
can
just
jump
into
discuss
and
then
maybe,
if
there's
enough
people
chiming
in
on
a
certain
subject
and
there's
a
sort
of
like
general
consensus,
formulated
that
this
needs
to
be
taken
to
github.
You
know
and
then
form
a
document
that
that's
the
process.
D
Yeah,
so
I
was
asking
primarily
for
figuring
out
what
to
name
things,
and
there
are
a
lot
of
issues
in
the
backdrop,
queue
that
are
related
to
like
publicity
tasks
and
stuff
that
you're
exactly
right
needed
to
do
list
somewhere,
which
doesn't
necessarily
fit
in
the
forum,
but
we
didn't
have
anywhere
else
to
put
it.
D
D
So
I
I
like
fill
your
idea
about
branding
it
that
way
and
having
something
that
could
have
that
terminology
consistent
between
the
forum
and
the
repository,
I
think,
is
good,
I'm
just
not
sure.
That's
the
right
name,
just
because
I
want
people
who
are
looking
for
those
things
to
be
able
to
find
them
now.
That
said,
I
don't
know
that
you
would
be
able
to
find
it
in
backdrop
community
either.
D
But
at
least
that
seems
like
a
place
where
people
would
poke
around
like
if
they
didn't
know
what
that
was
where
with
talk,
you
might
just
immediately
dismiss
it
as
being
like.
Oh,
like
maybe
that's
a
chat
platform
or
something
I'm
not
even
gonna.
Look
at
that
so
yeah,
that's
my
only
thought.
I
also
don't
have
strong
feelings.
If
everyone
likes
talk,
I'm
fine.
Let's
talk.
B
Yeah
I
I
kind
of
like
the
word
talk
like
phil
said,
but,
as
I
said,
I'm
not
married
to
any
idea
the
only
the
what
I
did
last
time
when
we
sort
of
like
unofficially
discussed
this
with
phil
nate,
and
I
think
justin
was
on
the
call
at
some
point
and
jason.
B
The
decision
that
we
made
was
that
we
will
bring
it
up
during
this
meeting
and
the
the
reason
why
we're
doing
that
is
a
that
more
people
need
to
participate
and
decide
on
the
name.
This
is
what
we're
doing
now
and
we
understand
that
phil
and
myself.
B
B
D
Yeah,
I
think
the
learning
curve
is
the
only
real
cost
there
to
changing
the
name.
It's
pretty
easy
to
change
a
github
repository
name
and
keep
all
of
its
issues,
and
if
we
have
to
change
the
form
topic
to
match,
that's
also,
you
know
editing
a
node
or
a
term
or
something
yeah
yeah.
B
And
for
the
record
and
for
the
record
being,
this
is
being
recorded
and
it
brings
up
naming
and
separation
of
things.
This
discussion
started
with
the
suggestion
that
it
should
be
a
different
organization
actually,
but
there
was
resistance
there.
I
see
you
then
nodding
as
a
yes.
Yes,
it
could
be
so
why
we
decided
we'll
start
off
with
a
repo.
B
Is
that
you
can
easily
transfer
issues
between
repositories
within
the
same
organization
and
but
you
cannot
do
that
across
organizations
with
github
currently,
but
once
we've
got
the
issues
transferred
to
a
separate
repo,
we
can
transfer
repositories
the
ownership
of
repositories
to
a
separate
organization
which
could
be
community
or
whatever.
Okay.
So
let's
go.
Let's
go
with
the
low-hanging
fruit,
which
is
a
separate
repo.
We
sort
of
like
separate
the
issues
out.
Maybe
we
also
create
a
matching
category
for
the
forum
and
then
just
get
things
started.
Baby
steps
film.
E
Yeah,
no,
I
I
think,
that's
good.
I
think
kind
of
I
think
kind
of
what
my
my
thought
on
this
is
to
have
a
place
where
the
discussion
can
take
place
where
anybody
can
join
in
on
the
discussion,
but
then
have
a
place
like
on
github,
where
the
official
issues
and
tasks
related
around
that
discussion
take
place.
I
don't
feel
like
everybody
needs
to
be
involved
in
having
access
for
those
issues
and
tasks
and
things
of
that
nature.
E
But
so
that's
why
I'm
kind
of
saying
you
know
I'm
not
opposed
to
having
a
separate
platform
for
the
discussions
themselves,
but
I
do
think
that
github
is
a
really
good
place
to
keep
track
of.
You
know:
code
of
conduct.
It's
like
okay.
Here
is
the
code
of
conduct.
Well
now
we've
talked
about
it
in
discussion
and
we've
decided
to
change
the
code
of
conduct,
and
now
we
can
see
within
the
repo
who
made
the
changes
and
why
they
made
changes
and
when
and
and
all
of
that
stuff
that
way
documents
policies.
E
E
It's
open
to
everybody
to
be
able
to
see
how
those
types
of
very
important
discussions
were
able
to
evolve
and
have
gotten
the
point
of
where
they
are
so.
I'm
kind
of
looking
at
the
big
picture
on
this
that
if
we
want
to
bring
in
business
if
we
want
to
bring
in
organizations-
and
we
want
to
present
ourselves
as
being
a
professional
community,
those
types
of
entities
are
going
to
kind
of
pick
through
some
of
this
stuff
and
go
yeah.
No,
these
guys
have
their
ducks
in
a
row.
You
know
I
can.
E
B
Yeah,
I
think
that
phil
mentioned
that
in
the
previous
discussions
that
we
had
and
it
sort
of
like
resembled
something
that
we
have
privately
now
the
pmc
discussion
thing
which
is
not
open
to
everybody.
So
this
will
be
a
respective
thing
for
the
community
until
maybe
some
of
the
issues
there
might
need
to
be
brought
up
with
the
pmc
yeah.
A
Okay,
let's
so
we're
just
about
out
of
time
I'll,
just
quickly
say
my
overall,
I'm
fine
with
what
what's
being
said,
I
think
like
jen,
the
word
talk
in
a
github
repeat:
suppository
seems
like
dissonance
to
me.
It
just
doesn't
makes
I
don't
think
about
github
as
a
chat.
A
E
E
But
I
would
right
I
would
say
at
this
point
I
mean
I
like
the
branding
idea
of
talk,
keeping
it
all
seamless.
If
we
do
a
forum-
or
you
know
some
other
area
for
that,
and
then
it
it
all
funnels
down.
But
I
mean
I'm
not
going
to
sit
here
and
fight
the
name.
What
we
do
need
for
sure
is
the
repo
created.
Do
we
need
to
go
ahead
and
create
an
issue
for
getting
that
repo
created
and
getting
a
list
of
labels
that
can
be
created
for
that
or,
I
think
greg.
D
Think
you
do,
I
think
I
tried
to
make
you
have
everything
I
had.
I
can
find
out
real
quick.
E
C
I
was
thinking
you
know,
community
discussion
forum
already
exists
or
not
on
the
forums.
B
Yes,
but
the
forum
has
categories
for
reporting
issues
or
asking
questions
about
how
to
do
things
with
the
product,
we're
talking
about
processes
now
and
discussions
and
decisions
about
the
community.
But
I.
A
E
I'm
not
opposed
to
that
me
personally.
I
would
like
to
see
a
separate
forum
that
is
nothing
but
discussion
about
the
community
just
to
separate
out
from
people
that
are
asking
questions
and
things
of
that
nature,
but
that's
just
kind
of
how
my
brain
works.
E
I'm
not
going
to
sit
here
and
fight
it
and
again
it's
you
know.
These
are
things
that
we
can.
We
can
create
temporary
locations
for
this
stuff
and
if
we
need
to
move
them,
break
them
out
into
more
structured
places
later,
then
we
can
always
do
that.
I
I
just
sometimes
I
kind
of
look
at
that.
It's
like
if
there
is
a
possibility
of
breaking
it
out
later.
E
Well,
let's
just
go
ahead
and
do
the
work
to
do
that
now
that
way,
it's
less
work
later,
so
that's
just
kind
of
how
I
think
about
that,
but.
A
Well,
I
think
we're
not
going
to
be
able
to
make
a
decision
on
any
further
steps.
Today
we
just
don't
have
time,
but
we
could.
I
think
we
have
enough
consensus
to
move
forward
on
the
github
repo
today
and
then
and
then
we
can
start
talking
about
next
steps
and
I'm
not
saying
it
has
to
take.
You
know
they
could
happen
quickly
like
yeah,
I
don't
even
want
to
let's
say.
E
That
we
you're
right
next
meeting.
We
don't
need
a
plan
for
that
right
now.
It's
just
yeah,
just
some
ideas
being
thrown
out
and
that
I
think.
D
E
You
know
a
two
two
three
four
year
plan,
it's
kind
of
like
well,
let's
be
moving
towards
this
direction,
so
now
I'm
perfectly
happy
with
getting
repo
going
that
way.
We
at
least
have
that
that
dedicated
location
for
discussions
exactly
like
this.
This
is
about
the
community.
You
know
it
has
nothing
to
do
with
the
code.
Just
having
that
repo
out
there
is
going
to
be
really
good.
So.
C
A
E
Yeah
go
to
conduct
philosophy,
things
of
that
nature,
branding
copyright
information.
A
D
It
exists,
I
post
a
link.
I
made
the
pmc
admins,
so
anyone
should
be
able
to
change
the
name
later
as
needed.
Okay,.
B
And
feel
if
you
don't
have
access
to
transfer
topics,
sorry
issues
from
the
current
dot,
org
that
the
bid.org
people
just
post,
maybe
maybe
slap
a
dedicated
topic
on
zulip
and
say.
I
think
that
this
should
be
moved
to
the
community
repo
and
then
one
of
us
will
action
it
if
they
agree
actually,
maybe
we'll
let
people
give
a
few
thumbs
up
and
if
everyone
agrees
we
move
it.
E
A
D
So
nate's
weekly
meetings
changed
a
lot.
He
has
like
three
meetings
in
it.
There
was
one
point
where
they
were
all
scheduled
at
the
same
time
and
he
was
like
screwed,
I'm
not
doing
any
of
them.
I'm
gonna
do
backdrop
and
then
they
separated
so
one
of
them
started
half
an
hour
ago
and
one
of
them
starts
in
half
an
hour
and
he's
like
well
now,
I'd
have
to
miss
like
two
work
meetings.