►
From YouTube: Backdrop Weekly - 2021/07/08
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
folks,
it's
july,
8th
2021..
This
is
the
week
weekly
backdrop
developer
meeting.
We
get
together
every
week
to
discuss
the
latest
priorities
for
backdrop,
cms
mostly
focused
on
code-related
issues.
We'll
do
some
quick
introductions
of
those
presents.
My
name
is
nate
lampton.
I
am
in
oakland
california,
and
I
am
a
core
committer
for
the
backdrop
project
robert.
Can
we
get
an
update.
D
Hi
craig,
usually
in
australia,
but
now
stuck
in
the
past
year
and
a
half
in
greece,
taking
advantage
of
the
beautiful
weather
holiday
mode
and
lots
of
catching
up
to
do
because
I
haven't
had
anything
related
to
backdrop
for
a
couple
of
weeks.
Let's
go
to
team.
E
Hi,
I'm
tim
saint
paul
tim,
I'm
in
deerwood,
minnesota
and
focused
on
our
third
backdrop,
live
which
is
happening
tomorrow.
So
please
come
join
us
events.backdropcms.org
event
step
bankruptcy
instead
of
work.
That's
it
did.
We
do
joseph
yet.
F
A
Can
right
thanks
folks
updates
from
the
pmc
this
week?
We
don't
have
any
updates
to
reports
outward
new
contributed
projects.
There
are
two
new
contributed
modules:
node
no
index
and
viewport
modules
that
have
been
published
and
have
releases
on
backdrop,
cms.org.
A
I
don't
think
that
we
have
any
updates
to
report
on
all
of
the
flagship
sites.
The
biggest
thing,
of
course,
is
the
events
website
tim
had
mentioned
that
backdrop
live
starts
tomorrow.
The
previous
meeting.
Just
before
this
one
was,
we
discussed
backdrop
live
extensively,
so
you
can
check
out
that
recording
the
event
starts
tomorrow
very
exciting,
and
many
of
us
will
be
there.
B
Can
I
mention
one
nice
thing
to
report
about
the
docs
site
that
tugboat
builds
were
broken
for
months
and
peter
has
them
working
again
so
yay.
A
That's
correct,
yeah,
bw
panda
went
through
back
in
january
and
set
up
demo
sandboxes
to
help
the
development
of
all
of
the
the
main
backdrop,
websites,
which
is
super
helpful,
that
actual
cause
of
that
breaking
was
just
that
our
tugboat
account
ran
out
of
space,
so
he
created
an
optimization
that
makes
it
so
that
all
of
the
sandboxes
share
one
set
of
files,
instead
of
all
of
them
duplicating
all
of
the
files
and
that
reduced
our
usage
from
over
100
to
like
10.
A
So
we
have
lots
of
space
to
grow
there
and
and
make
improvements
to
our
websites
now
without
running
out
of
space.
Yeah
big
kudos
again,
thank
you
for
putting
that
together,
peter.
It
really
helps
a
lot
setting
up
development
of
those
sites.
E
There
seemed
to
be
a
lot
of
activity
in
github
related
to
forums
also,
but
I
haven't
like
followed
specifically
anything
developed
there.
That's
interesting
or
the
docs
side
or
any
of
those.
No.
A
Oh,
you
mean
like
there's
new,
like
issues
and
poll
requests
regarding
like
improving
them.
E
I
get
in
my
github
notifications.
I
was
like
swamped
with
stuff
from
the
you
know:
the
internal
sites
over
the
last
couple
of
days,
yeah.
A
A
Yeah
last
week
we
discussed
a
bit
that
robert
has
been
doing
a
lot
of
enhancements
to
the
project
listings
and
the
finding
of
projects
in
the
project
pages.
That
was
a
lot
of
issues,
but
not
not
specifically
like
the
forum.
I
don't
think
there
was
also
a
big
discussion
about
using
markdown
that
we
discussed
last
week
that
we
haven't
totally
landed
on
an
on
a
solution
there
like
if,
if
we're
going
to
pursue
markdown
or
not,
but
we
are
kind
of
making
progress
in
in
the
discussion.
B
A
All
right,
let's
see,
let's
go
into
the
into
the
progress
report,
infrastructure
or
just
a
general
ongoing
issue
that
was
raised
this
week
in
the
forum
to
be
added
to
the
agenda
was
one
by
indigozella
issue.
4753
using
github
actions
for
tests.
A
Indigozala
did
some
helpful
benchmarking
checking
out
like
well.
A
First
of
all,
let's
rewind
a
little
bit
so
we've
been
using
zen
ci
for
running
our
our
unit
or
our
functional
tests
for
a
long
time,
almost
in
the
entirety
of
the
backdrop,
project
we're
having
a
lot
of
issues
with
the
tests
failing
randomly
or
the
test
results
being
unavailable
when
they
should
be,
and
just
other
maintenance
issues
and
control
issues
like
we
need
to
upgrade
like
the
php
versions
and
doing
that
right
now
we
don't
have
a
way
to
self-service
that
so
we're
looking
at
other
ci
providers
to
try
to
run
our
tests
and
so
far
other
ci
providers
have
not
been
nearly
as
fast
as
nci,
because
they're
not
optimized
specifically
for
backdrop,
but
they
have
the
promise
of
making
it
so
that
we
can
have
more
extensive
coverage.
A
That
is
on
more
different
versions
of
php.
The
most
obvious
candidate
now
that
github
has
started
providing
ci
service
directly,
is
to
use
github's
ci
service
because
primarily
it's
totally
free.
Secondarily,
it's
big
it's
tightly
integrated
with
github
and
we're
already
using
github
for
our
tools.
So
it's
an
obvious
choice.
A
It's
one
less
vendor
one
less
set
of
accounts
that
we
need
to
maintain,
so
we've
been
pursuing
using
github
actions
to
run
our
tests,
but
the
current
benchmarking
that
we've
done
shows
that
instead
of
the
tests
taking
about
six
or
seven
minutes
to
run,
they
take
about
half
an
hour
to
run.
So
it's
pretty
bad
regression
in
terms
of
like
overall
performance
of
running
the
tests.
A
Indigozala's
suggestion
is
that
we
split
up
the
tests
into
multiple
threads
and
run
one
third,
the
first
third,
the
second
third
and
the
last
third
of
tests
all
simultaneously
in
parallel
and
doing
that,
she
has
managed
to
find
that
we
could
get
php7
runtimes
down
to
about
seven
minutes
and
php
five
runtimes
down
to
about
12
minutes.
A
One
caveat
to
that
is
that
github
only
allows
20
concurrent
threads
per
project,
so
this
uses
six
threads
per
pull
request
instead
of
just
two
meaning
that
if
we
had
several
pull
requests
that
were
filed
at
the
same
time
or
the
same
one
filed
repeatedly,
we
could
really
only
run
three
pull
requests
at
a
time
worth
of
tests.
A
A
Yep
they
just
queue
up
yeah,
okay,
and
that
probably
isn't
that
bad,
because
it
just
means
that
it
would
be.
You
know,
six
to
eight
minutes
that
you'd
be
waiting
before
your
pull
request
started
getting
tested,
which
would
probably
be
just
about
the
same
as
if
there
were
only
one
pull
request.
That
was,
you
know
like
having
your
pull
request,
always
take
12
minutes
or
having
your
pull
request,
wait,
six
minutes
and
then
take
six
minutes.
A
Yeah
or
sometimes
what
happens
is
one
person
is
working
on
their
pull
request
several
times
and
it
kicks
off
one
round
of
jobs,
the
second
round
of
jobs
and
then
the
third
round
of
jobs,
because
every
time
they
add
a
commit,
it
starts
another
set
of
jobs.
Okay,
so
that's
actually
the
more
likely
scenario
that
people
would
end
up
accidentally
blocking
themselves,
then,
like
a
whole
lot
of
activity,
making
the
tests
get
too
slow.
D
A
It
finishes
the
first
one
yep
and
I
it
might
be
possible
as
a
pull
request
owner
to
stop
your
job.
I
haven't
actually
checked
that
I
know
as
an
administrator,
any
administrator
can
stop
the
jobs
if
they
see
that
they're
running
for
no
reason.
A
So
this
is
this
is
interesting.
It's
actually
an
approach
that
we,
I
think,
did
at
one
point
for
travis
ci.
We
split
up
our
things
when
our
job
started,
taking
over
45
minutes
on
travis
ci.
So
I
guess
getting
you
know.
Github
actions
down
to
this
like
six
minutes
or
seven
minutes
for
php
seven
is,
is
really
good
really.
I.
C
A
Wasn't
thrilled
about
the
separating
you
know
and
running
them
in
parallel,
but
I
don't
know
it
seems.
D
I
have
a
question:
how
do
we,
how
does
the
splitting
happen
like
from
a
technical
standpoint?
How
do
we
define
the
sets
of
tests.
A
Okay,
let's
see
we
there's
actually
oh
there's
actually
a
flag.
When
you
do
the
run
tests,
script
called
split
and
you
do
split
equals
one
quarter
or
one
third
or
whatever,
and
then
it
it.
It.
A
D
B
A
Yeah,
I
I
don't
know
it
seems,
seems
kind
of
kind
of
promising
we
could
potentially
pursue
it
and
set
it
up
in
our
repository
kind
of,
as
we
have
like
both
tugboat
and
zen
ci
sandboxes
right
now,
and
we
could
have
just
more
tests.
The
one
of
the
funny
things
is
as
long
as
we're
using
different
vendors
there's,
really
no
limit
on
the
number
of
actions
that
you
can
run
on
a
pull
request,
although
it
gets
a
little
bit
confusing
with
all
of
the
different
statuses
on
the
pull
request.
A
Like
you
know,
when
there's
like
going
this
would
make
so
there
would
be
eight
little
status
indicators
on
a
pull
request.
That
could
be
a
little
overwhelming.
But
if
this
was
successful,
then
we
could
disable
all
of
zen
ci
because
we're
using
we
can't
easily
disables
nci
right
now
for
sandboxes,
because
we're
also
using
it
for
tests
and
the
integration
right
now
is
currently
using
the
same
hooks
for
both
purposes.
So
we
can't
easily
turn
off
one
without
turning
off
the
other.
D
So
I
take
it
to
visit
a
paid
version
as
well,
which
which
allows
you
to
run
more
things
and
faster.
Possibly,
and
is
that
out
of
question
like?
Is
it
that
expensive
that
it's
sort
of
like
a
no.
A
As
far
as
I
can
see,
the
size
of
the
runner
is
the
same,
regardless
of
whether
you're,
paying
or
not
the
open
source
plan
is
effectively
actually
one
of
the
higher
tier
plans,
because
there's
no
there's
no
limit
on
the
amount
of
minutes
that
you
can
use
per
month.
So
it's
already
pretty
generous
of
github
that
we're
not
going
to
run
out
of
processing
time
per
month.
It's
just
a
matter
of
how
much
concurrency
we
can
have
the
concurrency
question.
A
I'm
I'm
sure
that
the
20
items
running
concurrently
is
a
as
a
prevention
mechanism
against
abuse
right
because
20
is
pretty
generous,
but
it's
it's
probably
intended
to
be
a
cap.
That's
so
large
that
no
one
would
normally
run
into
it.
Just
so
happens
that
our
tests
are
very
expensive
and
extensive,
so
it
would
be
worth
trying
to
ask
a
github
community
liaison
if
we
could
potentially
have
that
limit
increased,
and
I
don't
know
if
that's
an
option.
D
A
Are
you
saying
to
pay
pay
for
a
larger
plan?
Yes,.
C
A
Well,
there
are
a
couple
things
we
could
try.
We
we
could
try.
You
know,
having
the
the,
I
would
say
the
backdrop
association,
but
we
don't
have
necessarily
an
association.
We
do
have
a
fair
amount
of
funding
that
we
could
trial
to
see
if
it's
better
by
paying
not
for
long
term
purpose,
but
just
as
an
experiment.
A
Of
course
we're
also
talking
about
like
20
dollars.
So
we
also
just
anyone
could
run
that
experiment
individually,
but
I
don't
think
that
even
if
that
were
an
option,
I'm
not
sure
that
we
would
want
to
pay
for
it
like.
I
think
that
we
should
try
to
pursue
the
option
of
like
just
seeing
if
we
can
get
it
for
free
yeah.
D
A
Yeah-
and
I
think
that
we
reached
out
to
other
vendors-
I
think
travis
ci
or
circle,
and
they
also,
although
they
don't
have
like
it's
automatically
free
for
open
source.
They
also
provide
it
like
here.
You
can
have
like
20
000
minutes
for
free
per
month.
Option,
which
might
also
you
know,
be
something
that
we
should
pursue
as
as
something
to
research,
because
I
I
bet
that
the
runners
are
probably
more
efficient
or
faster
than
what
github
offers.
A
We
have
to
continue
renewing
it.
It's
not
it's
not
nearly
as
convenient
as
the
the
github
option,
where
it's
just
like
for
every
open
repository
on
github.
It's
always
free
and
github.
Also
like
github's
existence.
The
existence
of
github
actions,
I
think,
has
severely
damaged
the
future
viability
of
all
of
the
other
ci
platforms,
because
their
entire
business
was
working
with
ci
working
with
github
to
be
the
ci
provider.
Now
that
github
has
one
built
in
a
lot
of
people
are
like
us.
A
Well,
anyway,
so
I
think
we
should
continue
the
discussion
in
that
issue.
Number
4753.
A
I
think
it's
worth
a
shot,
so
maybe
we
should
at
least
enable
it.
You
know
get
fashion
a
pull
request
to
actually
enable
it
put
the
actions
directly
in
the
core
repository
and
try
it
out
for
a
little
while.
A
Okay,
let's
see
let's
go
into
the
project.
1192
is
the
next
bug
fix
release
that
we
will
be
putting
out
there's
one
big
item
to
announce
this
week,
and
that
is
that
regression
that
has
been
in
119
since
its
release,
the
php
8
compatibility
broke
the
restore
functionality
of
backup
and
migrate
issue,
5094.
A
the
workaround
to
avoid
that
problem
has
been
merged
into
core
and
that's
a
big
issue
for
a
lot
of
people,
and
so
my
objective
for
this
next
week
is
to
get
1192
out
the
door
to
include
that
fix.
A
So
if
you
have
other
features
that
you
would
like
to
get
in
as
soon
as
possible,
the
next
couple
of
days
is
a
great
window
to
try
to
get
something
in.
I
did
also
empty
out
the
rtbcq.
There
were
lots
of
great
small
fixes
again
more
terminology
fixes
a
couple
of
php
notices,
a
lot
of
documentation
updates
as
well
that
have
been
added
in
we're,
also
seeing
a
lot
of
new
faces.
A
In
the
backdrop
core
queue,
I
added
four
people
to
the
documentation
and
triage
team
that
were
new
contributors
that
were
in
that
rtbc
cue
list.
So
that's
also
really
great
to
see
new
people
coming
in
and
contributing.
A
Let's
see
so,
that's,
let's
see,
119.2
php
8
supports
we're
still.
We
still
have
full
test
coverage.
The
meta
issue
for
this
is
5076..
It
doesn't
look
like
there
are
any
updates
this
week.
A
Backdrop,
120
is
the
next
minor
version
of
backdrop
that
will
include
new
features.
Its
release
date
is
september,
15th,
2021
and
again.
We
don't
have
too
many
items
in
the
1.20
list
for
today,
but
robert's
issue
for
removing
the
direct
time
between
node
module
and
layout
module
has
been
committed,
issue,
50,
67,
very
exciting,
and
that
does
a
lot
of
things
for
the
world
of
contrib.
A
Robert
maintains
the
layout
wildcard
module
that
allows
wildcard
paths,
and
it
should
now
be
able
to
do
some
things
that
it
couldn't
do
quite
before
and
definitely
do
it
in
a
way
that
is
much
less
hacky
robert
anything
you'd
like
to
say
about
that
issue.
B
No,
I'm
I'm
I'm
very
happy
to
have
the
new
hook,
we'll
make
use
of
it
in
a
new
version
of
layout
wild
card,
and
that
will
both.
Let
us
do
some
more
fine-grained
splitting
of
the
things
layout
web
card
used
to
do
a
bunch
of
stuff,
and
we
can
split
it
out
with
individual
check
boxes
to
say.
B
Do
it
this
way,
but
not
that
way,
because
one
of
the
features
had
some
surprising
side
effects
to
users
and
we'll
be
able
to
split
that
out.
So
people
can
turn
that
on
and
then
they
have
some
other
ideas
about
how
to
how
to
deal
with
contexts
in
layout
wildcard
as
well
and
they'll
be
sort
of
floating
those
in
the
roadmap.
A
Great,
let's
see
the
other
issue
that
has
been
moving
recently
is
the
exposed
file
name
filter
for
the
media
library
dialogue
issue.
3293
laryn
is
the
advocate
for
that
this
one
recently
laren
made
a
good
amount
of
progress.
Solving
this
problem
seems
as
though
he
has
a
solution
to
fix
the
main
issue.
A
Indigozala
reviewed
it
this
past
week
and
found
that
there
were
a
couple
of
things
that
still
weren't
quite
working
after
inserting
one
image.
The
second
image
might
not
work
so
there's
still
an
a
couple
of
small
issues
with
the
implementation,
but
there's
obvious
javascript
console
errors
to
address.
So
I
think
that
you
know
the
approach
still
seems
as
though
it's
going
to
work,
it's
just
that
we
need
to
work
out
some
edge
cases,
there's
a
second
approach
to
solving
this
problem
that
has
been
put
forth
six
weeks
ago
or
so
by
el
muche.
A
That
is
a
completely
different
approach
of
using
an
iframe
instead
of
using
a
modal
form
with
the
the
view
embedded
inside
of
it.
Having
read
through
that
issue,
I
think
what
I
would
like
to
see
is
that
we
continue
to
pursue
laryn's
original
approach.
A
First,
and
because
it
seems
as
though
that
approach
is
a
much
smaller
set
of
changes,
solves
the
problem
and
pursue
that
initially
and
then
possibly
consider
the
iframe
solution
for
like
a
follow-up
or
a
future
thing,
and
I
know
that
using
iframes
could
potentially
solve
a
lot
of
dialogue
issues
in
backdrop,
but
it
requires
a
lot
of
infrastructure
kind
of
set
that
up
properly.
A
I
know
that
we
have
got
like
dozens
of
places
where
we
would
want
to
take
confirmation,
forms
and
put
them
into
modals
instead
of
taking
you
to
dedicated
pages,
and
it's
not
clear
if
using
an
iframe
would
be
the
right
way
to
do
that
or
using
an
inline
modal
would
would
be
the
right
way
to
do
that.
A
I
can't
think
of
one
that
is
obvious.
There's
some
strange
things
like
file
uploads,
sometimes
use
iframes,
but
that's
through
the
jquery
forms
library.
It's
not
something
that
we
do
directly.
So
there
are
some
uses
of
it
for
like
working
around
edge
cases
and
things
like
that.
But
we
don't
use
iframes
as
a
presentation
tool
anywhere
that
I
can
think
of.
B
A
Yeah
yeah-
and
we
already
have
some
control
over
that-
I
think
backdrop
does
set
the
content
control
policy
already
by
default,
to
prevent
cross
embedding
across
the
different
domains.
But
I
think
that,
as
long
as
we're
within
the
same
domain
that
we
would
that
we
may
already
be
set
up
for
that,
but
you're
right,
yeah
there's
different
different
problems,
which
is
why
I
think
that
we
should
pursue
not
an
iframe
solution
initially,
especially
because
it
seems
like
that
approach
is
closer
to
being
completed
and
a
much
smaller
set
of
changes.
A
That's
those
are
the
only
two
items
that
I
have
that
have
progress.
We
have
the
two
other
features
that
are
slated
for
1.20
so
far
the
advanced
caching
that
joseph
is
advocating
for,
but
I
don't
think
there's
been
anything
recently
joseph.
Do
you
want
to
say
anything
about
those.
A
I
understand
yeah,
you
sure
can,
and
that
frees
you
up
if
you
would
like
to
pursue
something
else,
no.
A
Oh
well,
that's
interesting,
an
area
that
is
highly
expensive
and
pretty
slow.
So
that's
interesting
that
sounds
great.
A
Let's
see,
and
then
jen
has
an
issue,
exposing
field
conditions
to
layout
module
issue,
4728
gen
lampton,
and
I
don't
think
that
there
are
any
updates
on
that
issue
either
so
1.20
we
have
still
this
opportunity
to
introduce
new
features
like
we
have
a
fair
amount
of
time
before
the
feature
freeze
on
august
31st,
so
we're
definitely
still
in
the
mode
of
soliciting
new
ideas
and
options
for
new
features.
A
There
are,
of
course,
some
features
that
we
have
discussed
in
our
prioritization
meetings.
From
back
at
the
beginning
of
the
release
cycle,
things
like
automatic
updates,
a
reference
module
and
and
there's
another
big
one
tim.
Can
you
help
me
out
here
with?
Can
you
recall
one
of
them?
Okay,
would
it
be.
A
Yeah,
that's
that
that's
a
I.
I
was
thinking
a
bigger
one
even
than
that.
So
there
are
a
couple
of
really
big
features
that
people
have
been
requesting.
Since
the
advent
of
backdrop
really
and
those
features
are
on
the
table.
At
the
very
least,
we
have
opportunities
to
move
them
forward.
Slightly
things
like
automatic
updates
have
a
lot
of
little
baby
steps
that
could
potentially
be
taken.
E
A
Yeah,
so
all
all
of
those
items
are
potentially
pursuable,
I'm
still
loosely
attempting
to
move
forward
automatic
updates,
as
I
have
time,
telemetry
yeah
gregory
you
mentioned-
might
not
be
something
that
is
targeted
for
1.20,
but
it
is
an
ongoing
initiative
which
we
can
touch
on
real,
quick
that
there
have
haven't
been
recent
updates
to
telemetry,
but
the
state
of
things
is
still
pretty
similar
that
we
have
the
core
module:
a
pull
request,
ready
to
put
in
a
module
named
telemetry.
A
A
As
you
know,
here's
the
module
that
provides
the
functionality
and
reports
information
to
backdrop,
cms.org,
there's
a
matching
pull
request
to
add
functionality
to
project
module
to
start
recording
the
telemetry
data.
It
needs
a
little
bit
of
work
to
only
allow
the
data
that
we
know
is.
We
expect
only
record
that
information
into
the
database
right
now.
It
will
record
a
little
bit
too
much
information
if
you
send
it
other
stuff,
so
yeah
that
that
continues
to
be
an
area
that,
like
we
have
options
we
have.
We
have
the
path
forward.
A
We
know
what
to
do
there
and
it's
just
a
matter
of
getting
the
implementation
further
along.
A
That
brings
us
to
the
end
of
the
agenda
for
today
I
guess,
since
we
do
have
a
couple
of
minutes,
there
was
another
item
that
has
been
brought
up
about
just
what
we
should
do
with
these
meetings,
and
we
have
discussed
the
format
of
these
meetings
a
couple
of
times
recently,
it's
possible
that
not
all
of
those
recordings
made
it
to
the
youtube
channel.
We
are
trying
some
changes
to
the
structure
of
these
meetings.
A
Well,
let's,
let's
kind
of
recap:
the
ideas
that
we've
pursued
so
far,
one
of
one
of
the
things
that
we
tried
is
having
these
meetings
be
more
of
a
working
session
where
people
bring
their
ideas
and
maybe
not
things
that
are
high
priority,
but
just
things
that
they're
stuck
on
and
are
looking
for
help.
A
We
did
that
for
one
meeting
and
it
was
very
productive,
but
it
did
not
make
for
very
compelling
broadcast
or
a
historical
record.
So
I
think
that
idea
of
it
just
being
a
working
session
where
people
come
together
was
great,
but
probably
not
what
we
should
do
during
this
time.
A
A
It
used
to
be
chat.
It's
still
on
the
backdrop.
Internal
project
calendar
is
something
that
could
occur,
and
I
think
that
if
we
were
to
renew
that,
if
we
had
a
leader
to
offer,
you
know
like
hey,
let's
get
together
time,
that
is
a
bigger
window.
That
would
be
a
better
use
of
that.
A
better
way
to
pursue
that
kind
of
like
hey,
let's
get
together
and
work
out
problems.
A
Yeah
look!
Is
there
anything
you
wanted
to
say
there?
Okay,
sorry,
you
just
came
back
on
and
okay,
so
that's
one
option
that
we've
done
another
thing
that
we're
doing
right
now.
That
seems
as
though
it
has
helped
a
little
bit
is
that
we've
started
posting
the
agenda
the
week
before
the
meeting.
So
at
the
end
of
this
meeting,
we'll
post
next
week's
agenda
into
the
forum
forum.backdropcms.org
as
an
event
and
then
at
any
time
through
the
entire
week,
anyone
can
see
next
week's
agenda.
A
If
they
have
access
to
the
google
drive,
they
can
actually
add
an
item
directly
to
the
agenda.
If
they
do
not
have
access
to
the
google
drive,
they
can
post
a
comment
to
the
forum
suggesting
an
additional
topic
such
as
indiegosella's
topic
this
week
for
github
actions
was
proposed.
That
way,
this
is
definitely
an
improvement.
A
So
I
think
this
is
this
is
a
big
win,
but
it's
not
quite
a
comprehensive
overhaul
of
how
our
meeting
structure
meeting
is
structured
yeah
any
do
you
guys
want
to
bring
up
any
thoughts
or
any
points
from
the
online
discussion
about
changing
the
meeting
format
that
would
be
worth
recording.
A
A
Okay,
well,
oh
oh,
and
another
idea
is
that
we
like
intermittently,
do
the
big
product
or
project
updates
like
we
did
this
week.
You
know
like
let's
look
at
119.2.
Let's
look
at
120:
let's
go
through
the
priority
issues
that
we
might
only
do
that.
Every
couple
of
meetings
instead
of
every
single
meeting
again
like
this,
is
actually
something
that
we
did
try.
I
think,
maybe
three
weeks
ago,
and
one
thing
that
we
found
has
occurred
is
that
sometimes
we
don't
have
any
topics
to
discuss
that
are
new.
A
We
get
five
people,
six
people
show
up
for
the
meeting,
and
people
are
just
there
to
hear
the
latest
updates
to
talk
about
anything
that
comes
up
that
they
might
be
interested
in,
but
they're
not
bringing
forth
necessarily
specific
topics
every
week,
and
so
one
week
we
got
together.
Our
plan
was
to
discuss
items
that
people
brought
forward,
but
no
items
were
and
in
that
situation.
A
Well,
we
just
ran
through
the
agenda
anyway
because
we
didn't
have
any
other
topics
to
discuss
in
the
first
place.
So
I
think
that
will
continue
to
kind
of
be
a
repeating
pattern
that
we
can
try
as
best
as
possible,
where,
if
there's
lots
of
items
to
discuss
that
people
have
put
forward,
then
we'll
focus
on
the
new
items
and
if
there
are
no
new
items
or
we
complete
all
of
the
new
items,
then
we'll
fall
back
to
doing
a
recap
on
the
newest
project
updates.
A
So
those
are
the
changes
that
we
have
been
pursuing
so
far.
We
have
been
trying
a
couple
of
different
things
week
after
week
and
where
we
have
settled
so
far
is
something
that's
not
very
different
from
before,
but
just
with
some
minor
changes,
we
prioritize
new
items.
The
agenda
is
posted
longer
and
we
encourage
people
to
post
items
into
the
forum
and
other
than
that
the
format
is
kind
of
the
same,
we're
still
open
to
more
changes.
A
So
we're
still
open
to
more
ideas,
though-
and
I
think
ideas
are
still
coming
and
we
love
trying
new
things.
So
if
we
have
new
actionable
things
that
we
can
try,
we
are
still
looking
to
use
this
time
as
efficiently
as
possible
and
try
out
different
things,
but
that's
it.
I
think.
That's
all
that
we
have
on
the
agenda
for
discussion.
Do
you
guys
have
any
other
things
you
guys
would
like
to
bring
up
before
we
close
back
up
live
tomorrow?
A
Yes,
again,
back
up
live
tomorrow,
events.backdropcms.org
is
the
primary
location
for
all
of
that
you
can
get
registered
view.
The
agenda
make
a
donation,
if
you
so
choose
and
yeah
it's
it's
around
the
world
continuous
event
with
time
on
and
time
off
and
yeah,
I'm
looking
forward
to
it
I'll
I'll,
be
there
as
many
people
here
will
be
okay.
Well,
let's,
let's
end
the
broadcast
today,
and
thank
you
all
for
for
being
here
and
thank.