►
From YouTube: Backdrop Weekly - June 24, 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
Hello,
it
is
june
24th
2021,
and
this
is
the
weekly
backdrop
developer
meeting.
We
get
together
every
week
to
talk
about
development
priorities
and
active
issues
and
blockers
that
are
happening
in
the
backdrop
issue
queue
we'll
go
ahead
and
do
introductions
as
we
normally
do.
I'm
nate
lampton,
I'm
a
core
committer
in
oakland
california,
robert.
Would
you
introduce
yourself.
B
I'm
robert
lange
folder
on
the
internet
in
altadena,
california,
and
working
on
various
things
lightly,
documentation
in
the
main
site,
entire
passive
adjustment.
C
I'm
justin
christopherson
in
denver,
colorado
and
I
am
help
out
with
infrastructure
tasks
as
needed
and
I'll
pass
it
to
tim.
D
I
am
tim
erickson.
I
am
here
in
dearwood
minnesota
and
I
well.
I
wish
I
were
saying
we're
putting
a
lot
of
time
in
backdrop
live
right
now,
but
I'm
not
doing
as
much
as
I
should
anyways
that's.
My
main
focus
for
the
next
two
weeks
is
back,
wrap,
live
coming
up
on
july,
9th
and
10th
whoever's
left.
A
There
is
no
one
left,
that's
it
for
for
us
presents
today.
Let's
see
we
have
a
couple
of
new
contributed
projects.
It's
been
a
couple
weeks
since
we've
had
this
meeting
posted
publicly,
so
there's
kind
of
a
longer
list.
There's
new
contrib
modules
include
image
link
to
file
multiple
email
addresses
session,
api,
mass
password,
reset
and
simple
timeline
modules.
There
may
be
one
more,
I'm
not
quite
sure,
depending
on
when
we
cut
this
off,
but
thank
you
for
the
new
contrib
modules.
A
It's
really
exciting
to
see
them
coming
in
also
acknowledge
that
we
have
an
open
session
application
for
joel
steedle,
really
excited
to
see
your
work
coming
in
for
the
new
sendgrid
port.
Thank
you
very
much
as
that
all
comes
together.
A
It
was
noted
that
we
didn't
have
a
recording
last
week,
we're
trying
out
some
adjustments
to
the
way
that
we
use
these
meetings
to
make
them
a
little
less
repetitive,
where
we
want
to
have
like
new
and
engaging
things
that
we
talk
about
every
week
rather
than
going
over
the
same
like
bullet
list
of
issues
every
week.
A
But
one
of
the
problems
that
we've
run
into
is
that
we
don't
really
know
what
it
is
that
we're
going
to
discuss
prior
to
the
meeting
beginning
if
it's
different
every
week,
and
so
we
have
a
little
bit
of
a
a
tooling
problem
that
we
don't
have
the
a
way
to
collect
like
what's
going
to
be
on
the
agenda,
make
that
publicly
available
and
allow
people
to
add
stuff
to
it.
A
We
we
keep
our
agendas
right
now
in
a
google
drive
that
a
lot
of
people
have
access
to,
but
not
everyone
and
the
the
process
of
adding
something
to
the
agenda
is
just
going
to
the
document
and
and
writing
it
in
there,
and
I
think
that
that
process
isn't
well.
First
of
all,
it's
not
documented
anywhere
how
you
add
stuff
to
the
agenda
and
even
if
it
were
documented,
it's
still
kind
of
a
gated
place.
So
well.
A
Robert
was
making
the
suggestion
that
in
any
case,
we
need
to
have
the
agendas
available
beforehand.
How
to
actually
do
that.
We're
not
quite
sure.
Yet.
We
need
the
ability
for
people
to
be
able
to
add
things
to
the
agenda
and
then
for
everyone
to
be
able
to
look
at
what
those
agendas
are
beforehand,
and
it's
hard
to
disagree,
that
having
agendas
that
are
regularly
updated
and
available
before
the
meetings
would
be
more
helpful
to
make
it.
A
We
spent
a
lot
of
the
meeting
like
heads
down
like
trying
to
understand
what
the
problems
were
during
the
entire
course
of
the
meeting
it
didn't
make
for
a
very
interesting
like
video
recording,
because
it
was
basically
everybody
just
looking
at
the
issues,
reading
them
and
every
now
and
then,
like
every
five
minutes.
Somebody
would
say
something
or
announce
something
saying
hey.
I
understand
what
this
issue
is,
or
this
is
the
status
of
this.
A
So
as
a
working
session,
it
was
very
productive,
but
as
a
recording
and
communication
device
from,
like
you
know,
community
leaders
to
to
people
that
are
just
interested
in
checking
in
on
backdrop
status,
it
wasn't
wasn't
the
best
use
of
the
time
so
for
now
we're
not
really
sure
where
we're
going
to
head
with
this.
For
today
we're
kind
of
falling
back
to
the
status
update
approach.
A
I
think
if
we
want
to
discuss
more
about
the
format
of
the
meetings
now,
you
know
acknowledge
some
of
the
things
that
people
have
been
saying
on
zulip,
there's
a
big
conversation
about
how
the
meetings
are
run
and
how
recordings
are
useful
versus
how
we
can
use
the
meetings
so
yeah,
I
think
tim
or
robert
justin,
if
you
guys
have
any
thoughts
or
anything
that
I
haven't
mentioned,
yeah
I'd
love
to
get
your
guys's
feedback
as
well.
D
D
A
Yeah
we,
we
also
did
some
slight
brainstorming
on
tooling
that
we
could
possibly
use
using
a
github
issue.
Q
was
thrown
out.
There
is
like
one
option
that
would
be
kind
of
consistent
with
some
of
our
other
tooling
or
using
a
backdrop.
Driven
solution
like
a
web
form
submission
or
even
like
some
kind
of
issue,
queue
or
forum,
or
something
like
that.
You
know
that
we
can
also
do
that's
kind
of
kind
of
interesting.
I
wonder
like
using
the
forum
itself
as
agendas.
A
We
haven't
discussed
that
as
a
as
a
thing
like
if
there
was
just
a
one
of
the
categories
in
the
forum,
was
weekly
meetings
and
each
agenda
was
like,
like
a
node,
basically
where
we
would
say
like
this
is
the
agenda
and
then
people
wouldn't
be
able
to
necessarily
edit
it,
but
they
could
post
comments
on
it
prior
to
the
meeting
beginning
and
then
that
that
would
be
a
publicly
accessible
way
to
see.
A
The
agendas
also
would
be
good
for
historical
reference,
because
similar
to
like
putting
stuff
into
the
google
drive
once
it's
there.
A
lot
of
people
don't
know
how
to
find
or
access
the
the
past
agendas,
but
the
downside
being
that
the
and
the
reason
we
use
google
docs
in
the
first
place
is
because
it's
a
you
know
asynchronous
as
you
type
you
know,
everybody
can
see
the
changes
happening.
A
So
it's
beneficial
in
that
way,
but
in
reality
we
usually
only
have
like
you
know
two
people,
maybe
three
actually
actively
typing
into
the
agenda
at
any
given
time,
so
we're
not
actually
overly
dependent
upon
that
live
as
you
type
functionality
yeah,
I
don't
know
or
or
maybe
we
could
even
just
cross-link
them.
You
know
have
have
have
a
google
document
and
a
forum
post.
I
guess
that's
almost
what
we
do
right
now
for,
but
we
use
zoolip
as
a
place
of
kind
of
discussion
of
where
things
are
happening.
A
I
don't
know
there
are
definitely
some
things.
Some
options
out
there
as
with
most
things,
the
approach
that
we
normally
do
is
we
give
it
a
shot.
You
know
we
like
try
and
see
if
it
works
so
yeah.
If
you
guys
have
ideas
about
what
it
is
that
we
should
try.
Yeah
I'd
like
I'd
like
to
know,
and
then
we
can,
we
can
just
give
it
a
shot.
A
Robert
you
saw,
I
saw
that
you
had
a
slight
look
of
agreement,
possibly
or
like.
Oh
maybe
that
would
work
for
the
forum
post
is.
Is
that
am
I
reading
that
correctly?.
B
The
forum
post,
actually,
what
I
was
thinking,
was
how
to
make
if
there's
discussion
of
agenda
topics,
how
to
maintain
how
to
collapse.
A
lot
of
discussion
into
a
smaller
agenda.
B
Actually,
a
challenge,
I
guess,
since
we're
recording,
I
will
throw
out
another
idea
that
perhaps
you
could
use
a
module
like
a
ticketing
system
which
makes
it
frictionless
for
people
to
put
in
an
item
to
include
some
description
of
what
it's
all
about.
But
that
also
makes
it
easy
to
see
a
summary
view
of
all
of
the
submitted
items.
B
So
something
like
that
might
also
be
a
core
of
the
way
of
implementing
it.
But
I
think
it
probably
requires
going
off
and
doing
some
research
to
see
to
see
and
try
something
out.
B
One
aspect
of
the
agenda
that
sort
of
couples
to
the
use
of
the
google
doc
is,
if
it's
possible,
to
not
only
submit
agenda
items
and
see
what
the
agenda
items
are,
but
during
the
meeting
to
enter
in
the
resolutions
or
what
actions
are
taken
so
that
the
agenda
even
becomes
as
as
the
google
doc
is
a
record
of
what
went
on
what
was
this
decided?
That
would
also
be
pretty
helpful.
A
Yeah
interesting
that
makes
me
think
that
possibly
doing
the
cross-linking
might
be
the
the
lowest
friction
option,
because
it
it
won't
change
the
way
that
we
use
our
tool
right
now,
it'll
just
surface
the
agendas
into
a
new
location
as
being
like.
Hey
here's,
the
the
new
location,
but
tim
mentioned
before
the
meeting
that
the
the
trouble
there
is
that
that
means
that
we
need
to
actually
put
in
the
work
that
after
meeting
ends.
A
A
Require
additional
work
to
do
that,
and
maybe
what
that
should
be,
then,
is
that,
instead
of
ending
at
three
o'clock,
sorry
that
specific
time
where
I
live,
ending
at
the
top
of
the
hour,
where
we
kind
of
run
right
up
until
the
hour,
and
then
we
say:
okay,
we
have
to
drop
dead
end.
This
call
because
a
lot
of
people
have
other
meetings
and
hard
stops.
A
We
could
do
it
like
five
minutes
beforehand
and
say:
okay,
here's
the
hard
stop
at
five
minutes
before
and
then
leave
that
five-minute
space
to
do
the
agenda
set
up
for
the
next
week,
possibly
okay.
Well,
I
like
I,
I
like
that
we
continue
to
have
these
discussions
about
how
to
most
effectively
use
our
time.
I
am
pleased
that
everybody
seems
to
think
that
having
a
once
a
week,
check-in
of
some
kind
is
a
great
idea.
A
A
Okay?
Well,
let's,
let's
move
on
from
that
topic
and
we'll
kind
of
go
into
the
status
update,
that's
okay
with
everyone
before
we!
Oh,
there
is
a
note
here
about
the
events
section
tim
you
already
mentioned
backdrop
live
is
upcoming.
Do
you
want
to
say
anything
further
about
that?
What
are
the
dates
again.
D
The
dates
are
july,
9th
and
10th
registration
is
live,
it's
20
suggested
donation,
but
we
really
want
everybody
to
participate
without
a
donation.
We
recognize
that
this
is
a
prime
vacation
time,
so
a
lot
of
people
aren't
available.
But
if
you
are
available,
please
join
us
for
some.
D
You
know
to
today
a
little
over
24
hours
of
structured
or
semi-structured
discussions
and
about
the
backdrop
related
topics.
So
in
the
previous
recruit
I
sort
of
showed
the
schedule
how
it
looks
so
far
in
the
previous
recording
for
our
outreach
meeting.
Although
the
outreach
meeting
isn't
properly
titled,
so
I
need
to
change
the
name
of
that,
so
that
you'll
find
it,
but
it's
only
a
short
10-minute
video.
So
if
you
want
to
look
at
that,
you'll
get
some
more
updates
on
backdrop.
Live.
A
Okay,
that's
it
great
and
that
registration
website
is
events.backdropcms.org.
D
Yes
and
I'm
gonna
on
camera,
nate
tell
you
that
I
just
penciled
you
in
for
the
same
things
you
did
at
the
last
backdrop,
live,
and
it's
up
to
you
to
change
that
rather
than
wait
till
the
last
minute
and
try
and
sort
it
out.
So
if
you
have
any
objections
to
what
we've
penciled
you
in
for,
let
me
know
and
we'll
we
can
adjust
it,
but
it's
basically
the
same
thing
as
a
a
discussion
about
an
update
on
cork.
D
You
know
core
and
in
the
opening
session,
where
the
two
things
you
kind
of
mainly
did
last
time.
Anybody.
C
D
D
A
A
Yep,
very
nice
registration,
a
very
nice
event,
site
yeah.
The
next
steps
very
exciting
suggest,
a
discussion
topic,
very
cool,
very
cool.
Okay,
let's
see
so
status
update,
so
119.2
119.2
will
be.
The
next
bug
fix
release
that
we
don't
have
a
particularly
scheduled
timeline
for.
However,
I
think
that
it
will
probably
be
in
the
very
very
near
future.
A
We've
had
a
big
issue
that
has
been
causing
a
lot
of
people,
some
problems
with
backup
and
migrate
that
our
php
8
support
efforts
have
made
it.
So
the
backup
and
migrate
cannot
restore
backups
that
have
been
created
and
the
issue
that
we
have
for
that
is
5094
and
the
solution
that
we
have
in
place.
A
There's
a
pull
request
that
is
marked
rtbc
that
has
been
tested
and
shown
successful
by
several
different
people
simply
adds
a
wrapper
around
the
old
method
that
used
to
be
there
and
then
calls
the
child
class.
That
pdo
class
has
basically
been
wrapped
inside
of
the
abstraction
layer
in
a
way
that
no
longer
makes
it
accessible,
and
the
fix
is
simply
that
we
add
a
wrapper
method
from
the
parent
class
down
to
the
child
class.
A
For
the
prepare
method
that
allows
backup
and
migrate
to
do
the
database
table
substitutions
specifically
without
doing
anything
else
that
the
abstraction
layer
normally
does
so
that
fix
seems
like
it's
been
approved.
There's
this
follow-up
issue
to
talk
about
whether
or
not
we
need
to
surface
any
other
api
functions.
Low
level,
pdo
functions
to
the
database,
abstraction
layer,
but
as
this
is
the
only
major
regression
and
this
fix
the
fixes,
the
problem,
we're
thinking
that
we'll
probably
merge
that
one
in
as
is
and
then
then
do
follow-ups
for
any
other
concerns.
A
So
that's
exciting,
and
once
that
gets
in,
I
think
that
we
should
probably
make
the
119.2
release
pretty
quickly
afterwards,
because
that
that
has
been
a
first
of
all.
We
don't
like
regressions
in
the
first
place,
and
it
goes
counter
to
literally
our
number
one
philosophical
goal
of
backwards.
Compatibility
is
important,
and
so
we
want
to
get
that
fixed
as
quickly
as
possible.
A
Let's
see
also
in
the
119
two
milestone,
if
I
just
take
a
look
in
github,
I'm
sorry
not
in
the
119.2,
but
the
rtbc
queue
has
several
items
that
are
all
ready
to
go.
I
can
find
the
label
here.
We
go.
Let's
see
the
php
8,
backup
and
migrate
issue.
A
There's
one
of
those
small
label
adjustments
on
a
button
for
the
cancel
canceling
an
account
feature
we're
just
going
to
change
the
label
on
that
some
semantic
structure
in
the
markup
on
the
dashboard
automatically
clearing
caches
when
you
change
a
an
account
settings,
so
all
very
minor
issues
that
are
all
ready
to
be
committed
and
there's
also
a
1.20
issue,
bug
folders
issue.
Actually
the
separating
the
the
layout
hooks
is
ready
to
go
into
1.20
so
very
exciting.
A
Our
tbcq
is
where
I
live,
and
so
I'm
sorry
that
I
like
to
talk
about
those
items
because
that's
usually
where
I
fit
into
the
process
to
actually
do
the
the
final
review
and
merging.
So
all
of
those
look
like
they're
really
set
to
go,
so
I'm
excited
to
get
those
items
in.
A
Let's
see,
I
don't
have
anything
else
really
for
119.2.
We
do
have
full
php
8
support
issue
5076
that
is
still
open.
Although
backdrop
will
run
on
php
8,
it
won't
pass
all
current
tests
and
so
issue.
50
76
is
the
meta
issue
for
follow-ups
to
continue
building
up
full
php
8
support.
A
There
are
a
couple
of
drupal
7
patches
that
we
have
yet
to
be
ported
that
fix
some
issues
and
then
there's
just
other
ones.
That
are
backdrop
specific.
That
getting
complete
test
coverage
is
what
it
will
take
to
get
that
issue
closed.
A
1.20
is
the
next
minor
release
of
backdrop,
it'll
be
coming
out
september.
15Th
2021..
We
already
talked
about
bug,
folders
fixing
of
the
layout
module
code.
That
issue
is
5067,
currently
is
rtbc
and
should
be
going
in
pretty
quickly
robert.
Do
you
have
anything
you
want
to
add
about
that
or
any
plans
that
you
can
fill
us
in
on
once
that
issue
is
resolved?
Do
you
have
any
other
thoughts
for
where
you're
going
to
take
things
from
here.
B
Yeah,
so
that
should
that
should
just
fix
the
preview
issue.
I
mean
in
terms
of
how
an
existing
installation
works.
It'll
fix
the
previous
issue,
hopefully
there's
no
way
of
hidden
breaking
it,
but
it's
kind
of
a
gating
item
for
further
improvements
in
layout
wildcard,
which
is
contrib
module
and
there's
one
of
the
things
to
do
upgrades
to
layout
wildcard.
B
I
want
to
do
them
based
on
that
foundation,
because
it's
a
much
more
robust
foundation.
We
can
throw
away
a
lot
of
duplicated
code
and
then
we
can
also
plan
to
use
that
to
maybe
try
out
some
some
broadening
of
the
ways
you
can
use
wild
cards
to
use
the
same
layout
in
multiple
places,
and
we
can
kind
of
use
the
contrib
module
as
a
testbed
to
see
if
people
like
it
and
then
maybe
consider
some
of
the
aspects
that
you
like
can
migrate
into
core
and
things
that
seem
special
purpose.
A
Excellent
yeah,
it
sounds
like
a
great
great
plan.
Is
that
likely
to
be
like
a
2.0
version
of
the
module.
A
Yeah
cool,
very
cool:
let's
see!
Let's
move
on
to
the
next
item,
which
is
the
exposing
the
file
name
filter
for
the
media
library
dialog
issue
number
is
3293..
Laran
is
the
advocate
for
this
issue.
A
Laryn
recently
overcame
the
technical
hurdle
of
this
issue
of
finding
out
why
views
exposed
filters,
weren't
working
inside
of
the
media,
library,
dialogue
and
he's
filed
a
pull
request
that
fixes
this
issue
in
3293,
and
I
think
several
people
have
tested
it
out
seems
like
it
mostly
works
looks
like
indigo
zella
did
a
little
bit
of
testing
and
found
that
there
were
some
small
issues
yet,
but
there's
also
just
a
whole
separate
discussion
where
another
approach
was
suggested
by
el
muche
that
uses
an
iframe
instead
of
using
instead
of
loading
the
content
directly
into
the
modal
dialog.
A
So
I
think
that,
with
that
in
a
way
kind
of
put
us
into
a
position
where
it's
like
now
now
we
have
two
different
things
to
test.
The
troubling
thing
about
el
muche's
suggestions
thus
far,
is
that,
although
he's
written
up
extensively
how
to
how
to
set
up
the
system,
we
don't
have
a
pull
request
that
demonstrates
it
and
with
a
pull
request,
they
would
make
it
so
that
we
could
get
a
sandbox
and
then
easily
test
it.
A
So
I
think
the
testing
is
is
trending
towards
the
solution
that
laryn
has
created
just
because
there's
a
pull
request
for
it.
People
can
test
it
out
in
the
sandbox
and
technically
it's
not
very
different
from
what
we
were
doing
already.
So
I'm
not
totally
sure
what
to
do
about
this
one.
I
think
maybe
posting
an
issue
saying
that
you
know
we
should
use
the
solution
that
we
already
have
and
then
maybe
separate
out
the
iframe
alternative
to
to
a
second
issue.
It
seems
like
it
would
be
a
good
idea
this
on
it.
A
The
inability
to
put
a
view
inside
of
the
media
dialogue
is
kind
of
a
limiting
issue,
with
the
way
that
you
interact
with
images
in
backdrop,
and
this
opens
the
door
not
just
to
adding
the
file
name,
but
adding
any
filtering
that
you
want
making
it
so
that
all
of
views
exposed
filters
work
inside
of
the
media
library
dialog.
A
So
it
seems
like
you
know,
this
is
actually
a
bug
that
needs
to
be
fixed
and
we
should
get
in
a
fix
to
that
and
then,
if
we
want
to
change
the
way
that
it
works
to
allow
for
additional
flexibility,
I'm
not
even
sure
what
that
would
be
using
the
iframe
approach.
Then
we
can
separate
that
out.
A
Do
you
guys
have
any
other
thoughts
or
feedback
on
that
issue?
I'm
not
sure
if
you
guys
are
tracking
that
anymore
closely.
A
No
okay,
all
right
and
then
1.20,
I'm
looking
at
the
the
milestone
over
on
github
other
items
that
are
in
here
include
the
advanced
caching.
That's
cache
tags
and
cache
max
age
header
that
pull
request
that
needs
review.
Joseph
is
the
advocate
for
this
one.
Although
last
I
heard
him
talk
about
it,
he
expressed
that
he
quote
does
not
like
this
pull
request
or
does
not
like
this
issue,
and
I
think
it's
probably
because
of
the
complexity
of
it
that
you
might
have
concerns
about
maintaining
this.
A
This
approach
in
the
future,
which,
if
you've
done
any
triple
eight
or
nine
work,
you'll,
know
that
cash
tags
is
a
double-edged
sword,
because
it
adds
some
nice
capabilities
to
make
it.
So
you
can
clear
your
caches,
but
good
gravy
does
it
cause
issues
like
with
just
like
cash
is
not
getting
invalidated
when
they're
supposed
to
and
having
so
many
layers
of
caching,
you
can
never
really
tell
where
things
are
coming
from.
I'm
sorry,
I'm
actively
fighting
that
problem
like
today,
so
it's
it's
top
of
my
mind.
A
Let's
see,
but
we
don't
have
any
updates
on
that
issue.
It's
issue
4127.
A
This
pull
request
is
hasn't
been
worked
on
recently,
but
it
does
have
something
that
is,
that
is
underway
to
make
it
so
you
could
use
all
kinds
of
conditions
and
capabilities
of
fields
to
determine
when
blocks
should
or
should
not
show
up
inside
of
a
layout.
A
So
those
are
the
only
issues
that
we
have
slighted
for
1.20,
we're
definitely
still
in
the
you
know.
Anything
could
happen.
Phase
of
the
development
cycle
where
any
issue
to
be
prioritized
for
1.20
simply
needs
an
advocate,
someone
that
is
going
to
basically
like
champion
for
a
particular
issue.
It's
not
hard
to
be
an
advocate.
You
edit
the
issue
and
then
put
yourself
as
an
advocate,
like
literally
you
type
into
the
summary
of
the
issue,
and
then
that
basically
gives
you
the
permission.
A
If
you
will
to
mark
something
into
the
1.20
milestone
and
that's
all
I've
got
for
the
1.20
updates.
Let's
see,
we
also
have
the
initiatives.
The
long-running
initiative
right
now
is
telemetry.
Tim
is
the
lead
on
that,
and
I
know
tim
you've
been
busy
with
backdrop
live
and
also
just
life
and
work.
I'm
not
sure
if
we
have
any
updates
on
telemetry,
no
okay.
A
Great
all
right,
yeah
I'll,
join
in
with
my
own,
like
long-running
thing.
Telemetry
is
one
of
the
things
that
I've
been
working
on
long-running
as
well,
and
I
think
that
during
the
planning
meetings
for
1.20
earlier
this
month,
I
reiterated
my
commitment
to
automatic
updates
as
being
something
that
I
I
strongly
want
to
continue
proceeding
work
on.
So
it's
it's
my
priority
other
than
the
normal
committer
tasks,
automatic
updates
or
issues
that
I'm
I'm.
A
Definitely
if
I'm
gonna
work
on
something
it's
gonna,
it's
going
to
be
that
area,
so
yeah
excited
to
to
move
forward
that
it's
possible,
that
I'll
start
picking
up
particular
issues
to
say
I'm
an
advocate
for
so
that
we
can
actually
talk
about
them.
Specifically.
A
Well,
that's
go!
That
is
the
complete
agenda
for
today
we
did
start
a
bit
late,
so
we
don't
have
time
for
to
discuss
much
else.
We
can
go
ahead
and
wrap
up
early
unless
there's
anything
else.
You
guys
want
to
discuss
and
I'm
going
to
use
that
time
to
make
a
forum
post
and
then
cross-link
next
week's
agenda
and
we'll
see
how
that
works
out.
So
it's
it's
something
that
we
can
try.
I
guess
tim.
We
don't
actually
have
a
category
for
agendas
yet.
A
On
the
forum
yeah,
let's
see
so
where
would
be
the
best
place
to
do
it?
Meetups
and
events
does
that
seem
fair.
A
Okay,
well,
let's
just
put
it
into
meetups
and
events
for
the
time
being,
and
if
this
proves
to
be
successful,
then
possibly
we
can
split
it
out
to
a
dedicated
topic.
Sure,
okay!
Well,
thanks!
Everybody
really
appreciate
it
and
yeah
we'll
catch
you
all.
Next.