►
From YouTube: Backdrop Outreach - 2021/01/21
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,
today
is
thursday
january
20,
21
21st
of
january
2021,
it's
kind
of
exciting.
I
guess-
and
this
is
our
fortnightly
community
outreach
meeting.
We
have
a
couple
of
items
on
the
agenda,
but
before
we
get
to
that,
let's
go
around
and
do
some
quick
introductions.
I
will
start
and
jen
lampton
joining
from
oakland
california.
I
apologize
in
advance.
I
have
two
cats
in
here
both
meowing
for
some
reason.
So
I
don't
know
what
that's
all
about,
but
apologize
in
advance
all
right.
Let's
go
to
luke.
B
I
am
luke
mccormick
in
san
ramon,
california,
I
I
do
web
product
and
project
management,
occasional
coding,
various
other
random
things.
I
am
interested
in
in
getting
the
word
about
backdrop
out
to
the
out
to
the
world
and
I
think
we're
at
a
particularly
exciting
point
with
that.
So
so
I'm
looking
forward
to
this
meeting,
let
me
throw
it
over
to
matthias.
C
I'm
attached
for
living
in
switzerland
to
marketing
for
small
business
customers
and
working
in
the
small
german
community
of
bankruptcy.
Ms
and
as
I
wrote
in
in
zulip,
we
will
have
a
discussion
tomorrow
about
how
to
move
forward
with
the
with
the
with
the
backdrop
german
side.
We
have
a
lot
of
ideas,
but
there
was
a
pretty
long
christmas
break
and
not
that
much
into
backdrop
right
now.
But
let's
change
that.
D
Phil,
I
am
phil
ward
out
of
wichita
kansas
if
we
could
squeeze
in
some
backdrop,
upgrade
status
today.
That'd
be
great,
if
not
no
worries
but
for
the
most
part,
just
kind
of
here
to
see
how
I
can
help
get
the
backdrop
out
there
in
front
of
more
people
who
we've
got
left
here
so
varsity.
E
A
All
right,
I
think,
that's
everyone
so
for
the
list
of
things
that
are
well
relevant
right
now,
backed
up
118
came
out
last
week,
which
is
pretty
exciting,
we're
hoping
to
have
another
release
next
wednesday.
This
would
be
our
normal
follow-up
bug
fix
release
where
we
would
usually
rush
to
fix
anything
that
we
found
that
was
horribly
broken.
A
We
haven't
found
anything
horribly
broken,
which
is
good,
but
there
was
a
security
release
for
drupal
this
week
and
so
we're
going
to
release
next
wednesday
with
the
security
release
that
went
out
today
for
drupal,
and
there
is
a
security
advisory
on
our
website
explaining
the
situation
and
that
it
will
be
out
next
wednesday.
E
A
Yeah
then,
you
won't
have
to
do
one
this
week
and
one
next
week,
bw
panda
has
been
working
on
our
newsletter,
which
is
fantastic.
A
He
has
a
ton
of
experience,
doing
newsletters,
and
so
I'm
super
excited
that
he's
offered
to
pick
up
ours,
because
that
seems
to
be
a
sticky
point
for
us
after
releases
and
luke
did
our
blog
post
on
118.
So
thank
you,
luke
for
spending
the
time
and
energy
on
that.
Let's
talk
about
your
thoughts
on
that
now,
just
to
make
sure
that
we
get
those
covered
sure.
B
Well,
it
it
was
harder
than
anticipated,
which
which
led
me
to
realize
the
the
pieces
that
that
I
didn't
understand
that
I
want
to
understand
that
I
want
the
world
to
understand,
and
so
so
hopefully
I
can
capture
sort
of
my
conduit
of
of
the
things
that
I
didn't
know
and
and
put
a
a
path
to
sort
of
turning
that
into
a
pipeline,
so
so
30.
B
Second,
recount
of
of
what
I
need
to
do
to
to
write
the
the
the
blog
post
I
didn't
know,
I
was
reading
the
blog
post
until
you
assigned
it
to
me,
and
I
was
like
oh
okay,
really.
I
I.
A
B
B
Because
that
wasn't
really
that
obvious
to
me
and-
and
I
found
the
the
released
issues
and
found
basically
a
thread
in
github
about
each
one
and
and
what
I
needed
to
do
was
was
coalesce
okay,
what
are
these
and-
and
I
discovered
a
process
and-
and
let
me
know
if
this
is
for
any
reason
like
not
the
usual
process
or
if
what
I
experienced
this
time
is
different
than
what
typically
happens,
but
for
each
of
these
threads
they
started
off
with
somebody
kind
of
proposing
something
they
saw
as
a
problem.
B
Here,
here's
a
here's,
a
problem.
Here's
something,
I
think
is
wrong.
Here's
a
solution
that
I
think
we
can
do
and
and
then
I'd
read
through
the
thread
and
see
various
back
and
forth
about
which
pieces
of
it
and
it
always
ended
up
with
some
bit
of
code
being
approved
and
included
into
into
the
release.
B
But
what
I
noticed
is
that
there
often
wasn't
a
description
of
what
was
finally
delivered
like
the
description
in
the
beginning
of
what
of
what
was
needed
and
then
there's
code,
so
so
so
for
each
of
these,
I
had
to
go
through
and
actually
find
the
code
and
then
kind
of
compare
it
to
to
what
was
suggested
and
and
try
to
try
to,
like
reverse
engineer,
what
the,
what
the
feature
really
was
and
and
how
it
how
it
changed
things.
So
this
you
know
I
I
wasn't
feeling
all
that
much.
B
You
know
pity
on
on
my
process
of
doing
like
this
little
piece
of
it,
but
but
it
seemed
to
suggest
a
process
that
might
make
the
whole
thing
more
effective
to
the
outside.
So
as
I
it,
it
struck
me
that
the
part
of
that,
if,
as
part
of
that
release
process,
whoever
had
proposed
the
thing
in
the
beginning
or
or
somebody
else,
you
know,
but
somebody
should
sort
of
when
it
gets
included
right.
B
It
doesn't
have
to
be
like
like
marketing
language,
but
just
bullet
points
of
what
it
is.
You
know
we're
we're
taking
this
feature
that
used
to
work
like
this,
and
the
use
of
work
could
be
nothing.
You
know
if
it's
created
from
scratch,
it
could
be
entire
thing
but
like
if
it's
changing
something
or
creating
something
it
should
say.
If
there
was
something
existing,
they
should
say
what
it
was,
but
I
guess
you
just
say-
and
this
is
what
it
is
now
this
is.
This
is
how
the
new
thing
works.
B
That's
different
than
what
the
previous
release
did.
Here's
you
know
you
didn't
have
this
in
the
previous
weeks,
and
now
you
have
this
for
for
better
words,
so
so
there,
because
there
there's
a
couple
pieces
that
that
straighten
about
that
one,
one
is
sort
of
the
press
release
aspect,
the
the
newsletter,
the
blog
post,
the
the
announcements
saying.
B
Here's
this
new
thing
as
as
part
of
that
same
process,
it
seems
since
there's
a
new
thing:
there's
a
new
bit
of
functionality
that
that
seems
implicitly
to
be
new
documentation,
so
so
part
of
that
is
whatever
gets
written
should
slide
into
the
documentation
either
as
is
or
as
it's
a
due
item,
because
if
it's
changed-
and
it
wasn't
like
that
before
then-
it's
not
documented
that
the
documentation
has
to
be
updated
with
this
new
thing
somewhere.
B
Somehow
you
know
a
feature
of
a
programming
environment
doesn't
doesn't
do
any
good
if
nobody
knows
about
it,
and
the
documentation
theoretically
should
be
how
people
can
can
know
about
it.
So
so
there
there
that's
kind
of
so
that's
two
things
so
far
and
there's
gonna,
be,
I
think,
three
all
together
with
my
sort
of
like
brain
dump.
B
All
of
all
of
the
new
features
strike
me
as
being
at
least
implicitly
part
of
of
the
general
roadmap
of
backdrop
becoming
what
it's
going
to
be
you're
going
from
its
you
know,
initial
state
into
into
something
else,
something
that
that's
good,
something
that's
desirable
and,
and
there
there
are.
There
are
road
map
elements
that
are
that
are
written
down
and
that
are
understood
and,
and
the
release
process
seems
to.
B
It
seems
to
roughly
coincide
with
that,
like
the
the
roadmap
kind
of
documents,
things
that
that
that
are
desired
to
be,
and
then
the
release
process
shows
what
actually
happens,
those
those
should,
at
some
level
be
the
same
thing.
B
So
so,
if,
if
things
that
are
road
mapped
become
releases,
they
they
can
be
checked
off
the
roadmap
if
things
that
weren't
on
the
roadmap
become
releases
that
that
needs
to
be
incorporated
into
into
the
roadmap.
And
you
know
I
I
don't
know-
I
don't
know
how
much
love
the
road
map
in
general
gets
as
part
of
the
whole
process,
but
but
it
it's
important
in
sort
of
the
product
management
world
that
I
essentially
come
from,
so
so
that
that's.
Why
I'm
kind
of
paying
attention
to
it?
B
So
summing
up
that
those
are
sort
of
the
three
things
that
jumped
out
at
me
for
this
whole
process,
that
that
would
help
to
get
the
development
team
to
state
the
functionality
that
the
documentation
that
functionality
should
be
captured
permanently,
rather
than
just
ephemerally
with
release
things,
and
that
all
this
stuff
should
be
viewed
as
part
of
the
overall
lifetime
possession
of
backdrop.
D
So
I'm
gonna
throw
in
my
thoughts
my
my
just
off
the
top
my
head
thoughts
on
this
all
of
them.
I'm
done
what?
What?
If
on?
What?
If
on
git,
we
create
two
more
tags.
One
tag
is
a
conclusion,
needs
conclusion
as
a
tag
and
another
one
is
needs
documentation,
and
so
if,
for
example,
an
api
or
something
changes
and
it
needs
to
be
updated
or
you
know
the
way
something
works
within
the
system
needs
documentation,
then
you
need
to
add.
D
You
know
somebody
would
add
in
that
needs
documentation
tag,
but
before
an
issue
could
be
closed,
if
those
two
tags
are
on
there,
then
it's
kind
of
like
okay.
Somebody
needs
to
come
in
here
and
create
this
conclusion
or
the
conclusion,
and
then
also
somebody
needs
to
come
in
and
do
documentation,
which
I
would
personally
prefer
that
the
conclusion
is
the
very
last
thing
to
be
added
to
the
issue,
but
that's
that's
one
way
that
we
might
be
able
to
approach
what
you're
talking
about.
A
Yeah,
so
we
already
have
the
documentation
label
and
I
think
we
probably
just
need
to
do
a
better
job
of
using
it
when
we
have
something
that
needs
it.
And
another
thing
is
that,
like
we,
like
backdrop,
probably
contains
a
million
features
and
we
don't
have
documentation
on
all
of
them,
so
it's
also
kind
of
like
arbitrary.
When
we
decide
a
new
feature
needs
documentation,
I
would
say:
if
we
already
have
documentation
on
it
needs
to
be
updated.
A
A
I
don't
know
so
yeah
and
then
like
if
we
had
documentation
on
the
media
dialogue
and
we
added
a
new
filter
to
it,
does
that
need
to
be
included
in
the
documentation
or
would
it
be
self-explanatory
so
that
I
think,
like
every
decision
needs
to
be
a
little
bit
arbitrary
as
to
whether
it
needs
the
documentation
or
not?
But
I
think
we
do
need
to
have
that
thought
process
which
we
don't
always
have
right
now
we're
just
like
yeah.
A
If
you
join
in
and
then
it
gets
closed,
the
summary
thing
making
sure
that
issue
summary
is
up
to
date
with
like
a
conclusion
on
it.
That's
something
like
drupal
has
been
suffering
with
forever.
It's
something
that
we
suffer
with,
even
through
the
lifetime
of
an
issue
when
the
first
person
requests
it.
A
It's
usually
like
hey,
I
want
thing
x
and
then
it
goes
to
100
iterations
and
what
you
get
is
thing
z,
but
the
issue
might
still
say
I
want
thing
x
and
then
it
gets
committed
and
it
says
thing
x
but
like
what
was
committed
was
being
z
and
that's
something
that
I
think
like.
If
you
don't
look
at
the
issue
for
a
long
time,
you
come
back
to
it.
You
realize
that
there's
a
big
disconnect
and
you're
like
whoa
whoa.
A
I
just
read
the
issue,
and
this
thing
is
nothing
like
what
the
issue
requested,
but
it's
really
hard
to
stay.
On
top
of
that,
and
especially
when,
like
we
get
a
lot
of
activity
on
something,
it
means
everyone's
really
excited
about
it.
But
that
means
that
everybody
is
aware
of.
What's
going
on
and
nobody's
looking
at
it
with
that,
like
fresh
perspective
of
like
oh
wait
hold
on,
this
is
really
different
from
what
we
originally
envisioned.
A
I
think
having
a
tag
for
that
might
also
not
be
necessary,
because
we
already
have
a
list
of
all
of
these
things
that
are
committed
right,
and
so
I
think
what
we
could
do
is
use
this
milestone
label.
Here's
an
example
of
one,
so
we
have
everything
that
went
into
this
issue.
We
know
all
of
these.
A
Things
should
have
some
kind
of
summary
on
them,
and
I
know
that
one
of
the
things
that
I
do
when
I
create
release
notes
for
these
things
is
I
go
through
and
like
update
the
issue
titles,
so
that
like
if
the
thing
has
changed
a
lot
since
we
created
the
issue
and
the
title
doesn't
even
match
I'll
fix
the
title,
but
I
don't
ever
read
the
top
issue.
I'm
just
working
on
the
release,
notes
and
the
release
is
just
a
bold
list
of
titles.
A
So
that's
all
I
focus
on,
but
this
would
be
a
really
good
place
where
we
could
involve
anyone.
Who's
been
involved
in
these
issues
to
say,
like
hey,
could
you
go
through
and
like
write,
an
update
on
this
issue,
and
it
could
be
something
that
would
happen
like
immediately
when
the
code
is
merged
that
adds
it
or
it
could
be
something
that
could
happen
like
sort
of
on
your
own
time
until
you
make
sure
each
one
of
these
has
one,
and
I
think
that
it
could
be
pretty
straightforward
to
do
it.
A
You
know
how
we
have
like
in
the
top
issue
we
used
to
have
the
format
of
like
okay.
We
have
an
issue,
it
has
an
advocate,
there's
like
a
section
for
advocate.
If
it
has
a
pull
request,
there's
a
section
before
request.
We
can
do
the
same
thing
at
the
top
with
a
section
for
conclusion,
and
so,
if
you're
looking
through
the
issues
to
see
which
one
has
a
conclusion,
if
it
says
conclusion
and
then
there's
like
a
paragraph,
you
know
that
that's
done
and
you
can
move
on
to
the
next
one.
A
We
don't
usually
have
that,
I'm
going
to
say
this
hesitantly.
We
don't
usually
have
that
many
issues
in
each
release,
although
velocity
does
tend
to
change
from
really
sometimes
we
get
a
ton
of
stuff,
but
I
think
in
general,
it's
sort
of
manageable
to
do
this
between
the
preview
release
when
we
like
cut
cut
off.
This
is
all
the
end
of
stuff
that
go
in
and
two
weeks
later,
when
the
blog
post
needs
to
go
out
and
the
newsletter
needs
to
go
out.
A
We
just
need
to
have
a
process
for
making
sure
that
someone
goes
through
and
reviews
them
all
and
sorry
luke
that
fell
on
you
this
time,
because
you're
in
there.
A
Is
there
a
reason
the
process
is
when
a
program
comes
out
or
an
issue
gets
created?
That's
the
checklist
of
all
the
stuff,
and
your
name
goes
on
that
list.
But
for
this
particular
release
the
checklist
was
never
created
until
the
day
of
the
actual
release,
and
so
I
created
it,
then
to
make
sure
we
didn't
forget
any
of
the
stuff
that
should
have
been
on
the
checklist
two
weeks
before.
So
I
think
that
was
just
like
a
timing
issue
with
118,
but
for
every
other
release.
B
So
so
one
of
the
things
that
I'm
wondering
is
that
it
is,
would
it
be
an
applicable
thing
there
there's
a
process
that
I
know
amazon
does
that
I've
always
just
loved
which,
which
is
that,
when
they
start
a
project
at
amazon,
the
very
first
thing
they
do.
B
Where,
where
you
can
imagine
you
know,
somebody's
excited
like
I
want
to
change
backdrop
to
do
this,
and,
and
as
part
of
that
just
say,
okay,
you
know
what
is
it?
What
is
it
when
this
is
all
done
that
you,
you
think
you'll
end
up
with
and
just
kind
of
state
as
like
a
paragraph
like
okay
after
after
this,
you
know,
every
time
somebody
publishes
a
thing:
it'll
feed
the
dog
you
know
like
whatever
it
is
just
like,
like
something
that
you
think
will
be
the
outcome
of
of
this
work
that
you
do.
E
B
You
know
we
said
we're
going
to
do
this
if
it
has
changed
a
lot,
though
update
and
be
like
well,
we
started
there,
but
we
ended
here
and
and
just
have
like
a
description
of
so
so.
What
is
it
that
you
actually
did
so
so
that
so
the
process
of
of
doing
these
things
would
basically
go
to
each
thread
and
go
to
the
last
message,
and
you
know
copy
that
text
and
you
know,
relate.
A
It
to
the
rest
of
the
world,
we
have,
I
posted
a
link
into
the
chat
here.
We
have
an
issue
template
for
a
feature
request,
which
I
think
might
be
a
great
place
to
put
this
desire,
for
I
don't
know
if
you
might
call
it
a
press
release
but
like
a
new
summary
feature
report
or
whatever
we
end
up
calling
it,
but
it
could
be
added
into
there
so
like
right
now.
I
think
this
is
loosely
copied
from
what
they
do
on
drupal,
where
it's
like.
A
You
describe
the
problem,
you
recommend
a
solution,
you
list
any
additional
alternatives
and
then,
if
there's
anything
else
that
you
think
is
relevant,
we
can
add
an
entirely
new
section
here.
A
That's
like
summarize
the
end
res
the
end
result
as
you
see
it,
or
something
like
that,
so
that
we
could
use
that
as
a
comparison
and
if,
if
the
original
request
turns
out
to
be
exactly
what
we
get
which
happens
sometimes,
then
we
can
just
change
the
heading
on
that
to
like
conclusion,
when
we
sign
off
on
it
and
be
like
okay,
we're
done
but
a
lot
of
times.
A
It
does
change,
and
I
think,
having
that
moment
at
the
end,
where
we
go
back
and
say,
is
this
what
we
originally
stated
we
wanted
as
helpful.
The
only
downside
to
this
is
that
a
lot
of
the
things
we're
working
around
predate
this
issue
template
right
so
like
if
we
change
it
now
everything
that's
on
the
list
for
like
119,
probably
isn't
gonna
get
that
section.
So
we
still
need
to
have
a
process.
I
think
for
adding
it
to
pre-existing
issues,
and
maybe
that's
just
something
we
do.
A
We
could
add
it
to
the
one
that
the
preview
release
checklist,
so
it
would
be
like
review
all
new
features
and
make
sure
each
one
has
the
conclusion,
and
then
that
will
come
before
draft
blog
post
so
that
we
can
sort
of
have
the
opportunity
to
make
sure
we
know
what's
going
to
get
written
up
in
the
blog
post
before.
E
So
we
should
have
a
list
of
websites
that
we
can
go
to,
and
somebody
can
take
you
through
the
website
how
it
was
created,
what
their
thinking
was,
what
tools
they
decided
they
needed
needed
to
use
for
that
website,
etc.
Basically,
how
they
thought
it
through
and
built
it
out,
and
then
the
person
going
through
could
could
then
build
that
website
on
their
own.
E
As
a
practice
of
how
you
develop
backdrop,
websites
and
that
kind
of
learning
process,
I
think,
is
very
much
needed
because
I've
gone
through
the
user
guide,
pretty
much
everything
there
and
it
tells
you
how
to
do
this.
You
have
to
do
this
and
you
use
this.
You
know
this
tool
whatever,
but
doesn't
give
you
any
of
the
context
by
which
you
want
to
use
those
kinds
of
things
right.
E
You
know
the
thought
process
by
which
you
develop
websites
with
backdrop
and
it's
a
huge
gap
for
me,
because
I'm
not
making
much
progress
at
this
point
on
on
developing
the
things
that
I
want
to
develop,
because
I
don't
really
know
how
to
tie
everything
together
and
I'm
too
much
of
a
neophyte
to
to
get
that
done
and
just
going
to
the
user
guide
is
not
complete
enough
for
me.
So
where
would
I
put
that
or
or
would
you
put
it
or
where
does
that
go?
E
You
know,
in
these
backdrop,
outreach
ideas
where
we're
developing
ideas
for
outreach.
I
think
making
backdrop
really
fun
to
develop
with
and
easy
to
develop
with
and
to
learn
to
develop
with
would
be
a
very
high
mark
for
backdrop,
and
so
that
should
go
into
some
some
place
as
a
project.
B
Yeah,
I
I
mean
that
that
ties
into
what
I
was
saying-
I
I
I
don't
when
I
hijack
it-
I
hopefully
I'm
not,
but
but
but
the
the
idea
of
sort
of
the
documentation
piece
of
it
and
the
roadmap
piece
of
it
seems
like
something
can
come
after
the
release
so
like.
B
If,
if
we
change
the
process
to
make
the
the
release
notes
like
that,
like
like
knowing
knowing
that
these
pieces
of
description
of
functionality
are,
are
going
to
have
a
lifespan
like
like
after
the
after
the
issue
concludes
they're
going
to
go
into
the
announcement
and
and
then
and
then
at
like
a
time
like
this,
you
know
post
release.
That
would
be
like.
Oh
look
at
look
at
the
you
know
we
had
to
play
with
the
children
that
we
birthed
before
right.
We've
got,
we've
got
these.
B
You
know
five
or
six
little
things
and
all
right.
You
know,
let's,
let's
document
them,
let's
get
them
into
tutorials,
let's,
let's
figure
out
how
they
fit
in
the
road
map.
Let's
you
know,
revise
the
road
map
so
that
so
that
you
know
it
it.
It
gives
us
an
opportunity
and
and
a
an
excuse
and
incentive
to
like
look
at
these
kind
of
passive
things.
It's
like
okay,
now's,
a
good
time
to
to
take
a
look
at
that
and
make
sure
it's
all
still.
In
fact,.
E
Essentially,
it's
like
a
map
right,
you
you,
you
get
to
this
stage
and
you
do
this.
You
get
this
station
do
this,
so
you
have
a
sequence
of
things
that
you
do
when
you
finish
a
new
iteration
of
backdrop.
Now
we
have
to
do
documentation,
we
want
to
put
it
into
tutorials
whatever
it
is.
It
should
be
a
list
steps,
a
sequence
of
things
that
we
do
to
complete
the
completion.
B
It
means
all
the
ways
that
people
learn
how
to
do
things
so
so,
for
example,
something
comes
up
in
in
backdrop
like
a
lot
is
that
is
it
we
have
something
that
that
we've
inherited
from
drupal
and
we're
like
okay,
let's
finally
stop
doing
this,
the
stupid
drupal
way
and
do
something
better
right
like
that,
that
periodically
comes
up
and
and
so
the
so
that
that
actually
should
trigger
kind
of
two
documentation
changes
in
that
in
that,
hopefully,
if
it's
better,
it's
it's
easier
to
learn,
so
so
people
that
aren't
familiar
with
drupal
should
be
like.
B
B
So
if
you
knew
this
old
thing,
you
know
be
alert
that
that
it's
not
going
to
work
the
way
it
did
before
it
has
these
changes,
and
I
I
think,
if
that's
if
those
are,
if
those
are
factored
out,
if
those
are,
if
there's
a
list
of
them,
it
becomes,
it
becomes
less
of
a
stumbling
block.
It
you
know
that
you
will
go.
Oh
okay,
sure
it's
fine!
I
never
liked
that
thing
anyway.
Yeah.
C
This
is
also
a
point
we
will
discuss
tomorrow
at
tomorrow's
meeting,
there's
in,
in
my
opinion,
there's
an
approach
of
coming
from
the
module
from
this
from
the
solution.
Let's
say
the
the
the
media
filter,
which
I'm
very
happy
with
when
this
is
available.
But
this
is
a
problem
a
beginner
does
not
see,
doesn't
have,
and
our
idea
is
to
have
some
very
basic
websites
created
and
then
tell
people
how
to
do
this.
Tell
people
how
to
create
relations,
which
is
very
a
very
powerful
feature
in
backdrop
and
drupal,
but
for
us
it's
it's.
C
E
C
C
A
C
E
C
E
Without
without
modules,
if
you
think
about
the
way,
you've
learned
anything
whether
learning
to
write
or
learning,
to
paint
learning
to
draw
learning
to
do
anything,
you
always
started
copying
something
simple,
first
and
then
gradually
building
your
skill
looking
at
who
would
evolve
their
art,
you
know
before,
and
then
you
would.
You
would
be
begin
to
to
become
a
master
by
copying
masters.
E
That's
that's
the
way
we
always
learn,
even
as
children,
we
learn
by
copying
our
parents,
so
we
learn
by
copying
and
if
we
can
do
more
of
that,
have
those
kinds
of
simple
tutorials
available
to
build
simple
websites.
Friends
that
would
encourage
a
lot
more
people
to
pick
up
backdrop
instead
of
wordpress,
because
wordpress
they're
going
to
run
into
limitations
and
they're
going
to
then
try
to
figure
out
well.
E
E
So
that's
that's
why
I'd
like
to
see
people
start
with
something.
That's
more
powerful,
just
use
the
simple
elements
of
it
first
and
then
later
as
they
realize
that
they
want
to
go
further.
Those
tools
become
available
and
then
they
can
dig
in
and
create
a
more
more
complete
vision
of
their
website
that
they
want.
B
A
A
I
updated
the
checklist
for
the
preview
release
to
include
a
section
on
reviewing
the
issues
that
got
merged
in.
I
had
three
bullet
points
there.
One
of
them
is
to
add
the
documentation
label
if
it
needs
to
be
added.
One
of
them
is
to
update
the
summary
to
including
conclusion,
and
one
of
them
is
to
update
the
title,
which
is
something
I
do
all
the
time
anyway.
I
also
updated
the
template
for
creating
a
new
feature
request.
So
there's
now
a
section
at
the
bottom
that
says
draft
a
feature,
description
for
press
release.
A
So
if
anyone
does
create
a
new
one,
they
will
at
least
have
the
ability
to
add
that
from
now
on,
I
do
think
that,
hopefully,
the
checklist
for
the
feature
list
will
catch
all
the
ones
that
don't
have
this
in
the
template
for
the
past,
but
luke.
Thank
you
for
the
wonderful
recommendations
on
how
to
make
this
easier
for
everyone
going
forward
and
I'm
really
excited
about
hopefully,
next
time,
this
being
much
easier.
B
A
Let's
check
the
agenda,
I
think
so,
let's
see
blog
post
stuff,
I
didn't
want
to
mention.
We
have
one
draft
blog
post
that
was
written
by
a
community
member
on
security
that
now
that
118
is
out.
I
think
we
should
schedule
for
maybe
not
next
week,
but
the
week
after,
if
everyone's
okay,
with
that,
we
talked
a
little
bit
about
learning.
A
I
really
like
your
idea,
so
if
I
actually
about
having
like
a
beginner
and
an
expert
sit
down
together
and
talk
about
how
to
solve
a
problem,
because
I
totally
agree
that
when
you
have
to
explain
something
to
someone
else,
you
say
things
that
you
would
never
think
of
writing
down
yourself.
If
you
were
by
yourself.
One
thing
that
I
also
find
really
attractive
about
that
is
that,
like
every
backdrop,
developer
might
do
things
differently?
A
So
I
would
love
to
figure
out
how
to
make
this
happen,
whether
it's
like
a
podcast
series
or
just
a
quick
like
audio
or
video,
or
something
like
how
do
we
get
these
people
together?
To
have
this
conversation?
I
don't
know.
E
A
Yeah,
I
love
it.
Suggestion
tim,
I'm
not
sure
how
much
of
this
you've
heard,
but
this
also
could
be
something
that
could
be
useful
for
a
backdrop
user
group
meeting.
It
could
be
something
that
might
fit
well
there
too.
G
Yeah,
I
like
the
idea,
like
you
thinking
about
the
format
and
how
to
vote
most
impossible
and
like
does
it
require
a
screen
share
or
is
it
just
a
conversation.
A
Yeah
well
an
interesting
idea:
let's
see
we're
going
to
talk
a
little
bit
more
about
documentation
in
the
developer.
Meeting
bdb
amanda
has
some
great
recommendations.
He
wants
us
to
talk
about
so
we'll
do
that
again.
There
move
this
item
to
the
next
meeting
backdrop
upgrade
status
fill
in.
You
said
you
wanted
to
talk
about
that
today.
I
don't
know
if
you
have
anything
pressing,
you
need
help
with,
or
conclusions
on
or
justin.
D
I'm
pretty
much
in
a
holding
pattern.
I
can't
do
any
of
the
code
stuff,
the
back-end
code
stuff,
so
I'm
pretty
much
just
waiting
for
somebody
to
step
up
and
say:
hey
yeah,
let's
collaborate
on
this.
Let's
get
this
thing
hammered
out
as
of
right.
Now
it's
in
a
broken
status.
You
can
only
run
back
up.
You
can
only
run
that
module
one
time
and
then
it
breaks.
D
So
it's
got
a
very
glaring
bug
that
needs
to
be
addressed,
but
outside
of
that
we
need
to
get
the
basically
the
telemetry
stuff
implemented
into
it,
and
those
are
pieces
that
I
myself
cannot
do,
but
I
just
need
somebody
to
say
yeah,
let's,
let's
hammer
this
out
and
get
it
done
so.
D
There
is,
and
the
title
is
a
very,
very
bad
title,
but
I
don't
know
what's
actually
going
on
under
the
hood
to
be
able
to
rename
the
title
it's
something
to
do
with
headers
or
something
I
I
think
it
might
be.
A
Okay,
I'm
if
I'm
gonna
send
you
this
link,
if
you
can
tell
me
which
issue
it
is
I'll,
have
a
look
at
that,
because
I'm
about
to
use
this
on
the
site
anyway,
so
I
might
as
well
work
on
it.
A
A
Okay
and
then
other
things
on
today's
agenda.
Backdrop
live
that's
coming
up
in
a
month
and
maybe
a
bit.
So
I
don't
know
when
is
that
march
ish
15
ish.
A
G
Yeah
yeah
you
scheduled.
B
G
A
I
think
we
could
also
to
maybe
I'll
check
with
you
offline
about
that,
but
I
think
we
could
set
up
a
website
with
registration
pretty
quickly
and
then
post
on
the
rest
until
later,
so
sure,
I'm
starting
to
have
some
more
breathing
room
in
my
life
again.
So
maybe
we
can
chat
about
yeah.
A
All
right,
I
think,
that's
it
for
today's
agenda
for
outreach,
so
I'm
gonna
go
ahead
and
turn
off
the
video.
You
guys
can
stay
here
and
we
will
kick
off
dev
meeting
in
a
minute.
So
thanks
everybody
for
watching
outreach.