►
From YouTube: Backdrop Weekly Dev - 2021/09/09
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
All
right
we
are
live,
it
is
thursday
september
9th,
and
this
is
our
weekly
backdrop
developer
check-in
meeting
before
we
get
into
the
agenda.
Let's
go
around
and
do
some
quick
introductions.
If
you
want
to
share
what
your
name
is
where
you're
from
and
something
that's
not
on
the
agenda
today
to
talk
about,
you
can
definitely
do
that.
I
can
go
first.
My
name
is
jen
lampton,
I'm
joining
from
oakland
california,
and
I
am
so
excited
about
all
of
the
new
stuff
we
got
into
120..
Thank
you,
everybody
for
all
the
work.
C
Greg
hi,
I'm
greg,
I'm
joining
from
greece
very,
very
excited
about
all
the
things
that
are
coming
with
120
and
all
the
cleanup
and
the
foundation
and
consistency
that
we've
implemented
also
excited
about
this
coming
weekend.
I'm
gonna
have
some
time
to
sprint
on
fixing
and
policing
last
minute
things.
So
if
anyone
wants
to
join
just
the
usual
thing
would
be
join
on
zulip
we'll
have
a
zoom
channel
open
so
that
we
can
discuss
things
and
coordinate
and
yep
super
excited
I'll
pass
it
on
to
joseph.
D
E
C
G
Sure
I'm
tim
erickson,
I'm
in
st
paul
tim
in
deerwood,
minnesota
and
yeah
nothing
special
to
report
just
real
busy
right
now.
So
let's
go
ahead.
F
All
right
and
I'm
nate
lampton,
I'm
quick
sketch
on
the
internet,
I'm
a
core
committer
and
oh
and
I'm
in
oakland
california,
and
that's
it
for
our
introductions,
jen.
F
If
it's
okay,
I'll
just
roll
right
into
the
next
section,
which
is
kind
of
open
q,
a
general
discussion,
things
kind
of
some
announcements
that
we've
got
the
most
obvious
one
being
feature
freeze,
completed
back
on
september
1st,
so
we're
now
frozen
for
new
features,
we're
still
accepting
usability,
fixes
and
bug
fixes,
of
course,
and
the
release
of
1.20
will
be
out
a
little
less
than
a
week
from
today
on
september
15th.
F
So
that's
very
exciting.
There's
lots
of
stuff
in
1.20
that
kind
of
came
down
there
at
the
finish
line
and
we
have
the
preview
release
out
already.
It's
not
on
backdropcms.org
preview
release
is
only
on
github,
but
you
can
get
it.
It's
1.20.0
dash
preview
from
the
releases
page
on
github
and
we'll
go
over
the
things
that
are
in
1.20
here
in
a
little
bit.
F
Another
thing
that
is
a
big
announcement
type
thing
is
that
we
have
fully
switched
over
to
using
github
actions
for
all
new
poll
requests,
which
is
very
exciting
big.
Thank
you
to
indigozella
who
spearheaded
that
project.
Pretty
much
took
it
from
beginning
to
finish.
As
far
as
implementation
is
concerned,
that
is
super
exciting.
It
is
a
little
bit
funny
that
we
we
had
lots
of
problems
with
znci
that
we're
infrastructure,
specific
disappearing
results,
inability
to
access
the
results,
containers,
not
spinning
up.
F
F
They
are
a
little
bit
slower,
but
not
much.
Thanks
to
the
concurrency
running
we
haven't.
As
far
as
I've
seen
seeing
any
problems
with
running
out
of
space.
It
seems,
like
you
know.
We,
like
all
of
the
actions
actually
get
executed
every
single
time.
Reliability
seems
to
be
pretty
good,
also
kind
of
interesting.
F
A
I
had
a
question
two
questions,
so
it
looks
like
from
the
tests
that
I'd
seen
running
on
recent
pull
requests
that
they
take
about
10
minutes
the
longest
one
the
previous
ones
took
about
three.
Can
we
have
more
like
concurrency
or
I
don't
know
what
the
why
the
decision
was
arbitrarily
the
number
it
was?
Is
there
a
a
limit
on
the
github
side?
Do
you
know
anything
about
that.
F
Yeah
there
is
there's
a
limit
to
the
total
number
of
concurrent
things
that
any
one
project
can
utilize
and
so
we're
using
six
at
a
time
right
now
already-
and
I
can't
quite
remember
the
limit-
it
might
be
10
that
you're
given
per
project
so
already,
if
you
have
two
poll
requests
that
are
filed
at
the
same
time,
one
of
them
waits
on
the
other
one
to
finish
before
it
before
it
starts,
and
so
I
think
that
that's
kind
of
why
we
didn't
go
any
higher
with
that,
because
we
don't
want
to
have
it
so
that
a
single
pull
request
gets
queued
up
on
itself.
A
B
F
A
F
Yeah
yeah-
and
you
know
how
code
sprints
actually
go-
is
that
it's
like
there's
very
little
filing
of
actual
pull
requests,
it's
like
mostly
figuring
stuff
out
and
getting
a
grasp
on
issues
and
then
every
now
and
then
there's
a
ball
request,
but
but
yeah
I
get.
I
get
your
grasp.
It
is
possible
for
us
to
pursue
other
options
like.
F
If
we
wanted
to
set
up
our
own
runners,
then
we
could
increase
the
concurrency
there
and
also
we
haven't
even
tried
like
reaching
out
to
github
and
asking
you
know
hey:
can
we
get
on
a
non-free
plan?
Pro
bono?
You
know
to
increase
the
number
of
runners
that
we
get
so
there
are
other
options
available
to
us
too.
A
F
Yeah
or
or
we
could
just
upgrade
our
plan,
you
know
like
we
could
pay
for
a
github.
You
know
for
a
little
while
yeah,
although,
though
github
is
per
seat,
and
I
would
be
terrified
to
know
how
much
our
percy
cost
her
like
our
total
cost
would
be.
We
already
have
like
over
200
people,
so
that
could
be
a
problem.
F
Let's
see
anyway.
Github
actions
are
super
excited
about
that
we're
also
using
tugboat
for
sandboxes.
So
that
means
that
we're
no
longer
using
zen
ci
for
any
day-to-day
purpose.
The
hooks
have
been
disabled,
although
all
of
znci's
code
is
still
there.
The
application
is
merely
suspended
right
now.
So
if
we
want
to
restore
it,
we
still
have
that
that
option
ahead
of
us,
but
I
think,
we'll
probably
you
know,
continue
and
then
clean
up
all
of
that
that
extra
stuff
in
the
in
the
future,
let's
see.
A
A
Twice
so
yeah,
four
years
from
now
or
whatever
we
have
to
do
it
again,
we'll
be
ready.
A
C
I'm
already
I'm
already
much
less
annoyed
with
having
to
come
back
to
the
pull
requests
and
sorry,
sorry,
you
can
finish.
No,
no
and,
as
I
said,
the
the
failures
are
already
like.
We
have
issues
for
them.
They're
consistent.
I
haven't
seen
like
the
the
usual
suspects
that
were
failing
in
zen
ci,
like
they're,
taking
for
updates,
which
throws
like
failed
to
take
updates
for
x,
amount
of
modules
and
things
like
that.
C
C
D
So
if
I,
if
I
just
push
a
new,
commit
or
close
and
reopen
a
pull
request,
I've
made
already
then
it'll
run
it
on
github
actions,
and
I
don't
have
to
do
anything
else.
For
those.
F
I
meant
to
say
something
else:
there
you
need
to
rebase
or
merge
with
one.x
in
order
to
get
the
github
actions
config
file
into
your
repository,
oh
okay,
yeah,
and
if
you
just
push
a
commit
to
an
existing
one,
because
it
doesn't
have
github
actions
in
it
and
this
nci
hooks
are
disabled,
the
tests
will
fail
to
run
entirely,
so
we'll
probably
need
to
advise
a
lot
of
people
actually
as
they
go
back
and
work
on
the
several
hundred
open,
pull
requests.
F
F
G
Yeah
well.
F
All
right,
well,
we've
got
two
more
things
that
need
to
be
covered
in
depth,
and
one
of
them
is
kind
of
a
recap
of
the
things
that
got
into
1.20
and
then
the
other
thing
is
like
things
that
we
still
need
to
do
before.
1.20
is
released.
F
F
So,
let's
see
1.20,
we
had
this
flurry
of
activity
looking
for
kind
of
the
easy
wins,
if
you
will
some
of
them
not
so
easy
actually,
but
some
of
them
moved
forward
really
pretty
quickly
and
we'll
go
through
some
of
these
things
that
that
happens.
I
guess
one
before
we
do
the
new
things:
the
exposed
file,
name,
filter
for
the
media
library,
dialogue
issue,
3293,
that
one's
been
on
our
plate
for
six
months
now,
or
something
like
that.
We
finally
got
that
one
fixed-
it
was
great.
F
Laryn's
approach
was
super
close
like
it
was
a
really
good
implementation,
but
we
had
some
minor
well,
maybe
not
minor,
but
certain
edge
cases
that
that
caused.
Not
to
work,
we
took
that
implementation
and
just
tweaked
it
a
little
bit
and
we
seem
to
have
all
exposed
filters
working
in
the
media
library
dialog
now,
which
is
super
great.
There's
one
small
caveat
to
that
and
that's
the
reset
button.
F
It
doesn't
work
quite
yet.
I
think
so.
We
don't
have
the
reset
button
enabled
in
the
view
display,
but
like
that's
kind
of
a
follow-up
issue
that
still
needs
to
be
addressed
turns
out.
F
The
reset
button,
handling
and
views
exposed
filters
with
ajax
turned
on
is
really
not
very
well
done,
and
so
the
first
thing
we
should
probably
do
is
check
the
drupal
7
related
issues
to
see
if
this
sort
of
thing
has
already
been
fixed
in
drupal
7,
because
it's
just
kind
of
a
general
problem
with
the
reset
button
and
ajax
dialogs
that
it's
handling
of
like
turning
itself
on
and
off,
is
not
very
good.
C
Also
also,
there
was
the
thing
about.
If
you
have,
if
you
edit
the
filter,
the
expose
filter
to
add
auto
auto
submit,
then
it
loses
the
focus,
but
someone
mentioned.
Maybe
it
was
unh
that
this
is
a
generic
issue
and
it's
it's
pre-existing
so
yeah.
F
Yeah
yeah
in
that
particular
problem.
We
have
a
unique
backdrop,
specific
solution
to
that.
We
fixed
that
same
problem
on
the
date
format,
page
that
as
you
type,
you
would
lose
the
focus,
but
we
did
something
on
the
date
format
page
that
there's
like
a
special
option.
You
can
do
to
like
prevent
that
from
happening
from
disabling
the
field
yeah.
F
So
there's
a
couple
of
things
there
that
could
be
done
as
follow-ups,
but
the
the
big
issue
is
now
fixed
and
that's
a
huge
improvement
to
be
able
to
add
any
kind
of
filtering.
You
want
to
the
media
library
dialogue,
let's
see
so
some
of
the
new
issues
we
added
an
html5
details,
element
to
form
api
and
just
theming.
Generally
that's
issue
324,
apparently
a
pretty
old
one,
indigo
zella
headed
this
one
up.
F
A
Sure
so
we
added
a
new
form
api
element
for
details
that
works
a
lot
like
we're
currently
using
field
sets.
This
is
something
drupal
8
did
too,
and
we
made
the
same
form
api
change,
but
we
did
not
change.
All
of
our
field
sets
to
use
details
elements,
so
the
element
is
there.
If
anyone
wants
to
use
it,
but
nothing
in
core
is
using
it
right
now.
A
F
E
F
C
And
that's
why
the
the
follow-up
task
that
I
was
mentioning
with
the
toggle
is
like
you.
We
get
rid
of
two
javascript
functions,
at
least
or
maybe
entire
files,
which
basically
do
the
same
thing
for
the
modules
page.
We
get
rid
of
the
the
entire
javascript
that
runs
on
those
pages,
using
the
details,
elements
but
yeah.
A
A
F
Okay,
thank
you,
jen.
That
all
sounds
amazing.
Let's
see,
we
also
implemented
dismissible
status
messages
issue
4571
greg.
Could
you
give
us
an
overview
of
what
that
is.
C
Yeah
so
this
started
again
as
a
peter's
brainchild,
so
he
limited
the
initial
pull
request,
or
that
was
what
was
committed
any
I
think,
jen,
you
fixed
a
couple
of
things
because
peter
was
unavailable,
but
basically
we
were
contemplating
of
whether
this
should
be
a
thing
that
should
be
configurable
via
the
admin
ui.
We
we
went
with
the
solution
that
everything
every
message
should
be
dismissible
and
we
left
the
the
enabling
or
disabling
to
contribute,
if
that's
something
that
people
want
so
yep.
C
So
basically,
that's
in
that's
it
every
every
message:
whether
it's
status,
warning
or
info
or
notice
has
an
x
button
now
at
the
top
right
and
people
can
dismiss
it.
I
did
find
a
few
cases
where
it's
not
desirable
and
we
cannot
override
it,
but
that
can
be
a
follow-up.
One
of
the
cases
was
the
the
the
blue
info
message
that
we
show
when
themes
are
not
enabled
and
they
provide
color
support.
A
C
A
F
A
F
Yeah,
we
have
a
a
form.
Api
element,
just
called
help
found
type
equals
help,
but
it
doesn't
have
any
styling
on
it
whatsoever.
So
maybe
what
it
is
is
like.
Maybe
we
should
style
the
help
section
or
the
help
element,
because
there's
nothing
on
it
right
now.
It's
just
markup,
it
does
have
a
wrapper
around.
It
says,
like
div
class
equals
help
and
everything
just
yeah.
F
Well,
that's
great
yeah
lots
of
fun
things,
let's
see
and
lastly,
there's
better
taxonomy
permissions
issue:
30
382,
let's
see,
I
don't
know
anything
about
this
one,
but
let's
see
greg
jenn
or
tim.
All
of
you
had
a
hand
in
this
anyway.
F
G
Yeah
this
just
there
were
very
limited
permission
possibilities
with
taxonomy
in
terms
of,
for
example,
you
we
couldn't.
You
couldn't
assign
an
editor,
the
ability
to
like
create
new
tags,
but
not
delete
them
or
whatever.
So,
basically,
right
now,
anybody
can
you
can
assign
a
role
to
to
administer
all
taxonomies,
to
create
new
tags,
to
delete
them
or
what
would
be
the
last
one
to
edit
them.
Yeah.
C
F
Wow,
that's
awesome,
wow
so
exciting.
Well,
that's
it!
I
think,
for
the
the
really
big
items,
that's
that
we
haven't
that
that
got
in
even
reasonably
recently
there's
some
other
things
like
robert's,
layouts,
separation,
hooks
and
things
like
that
that
got
in
quite
some
time
ago.
So
overall
it
looks
like
a
nice
nice
collection
of
things
for
the
120
release.
F
We
have
a
few
more
things
that
could
be
done
yet
in
the
next
week,
I'll
just
bring
up
since
we
just
talked
about
taxonomy.
The
taxonomy
dashboard
block
has
some
issues
issue.
5198
tim
filed
the
issue
and
there's
already
a
pull
request
for
it.
Just
making
the
taxonomy
management
block
on
the
dashboard
respect
all
of
these
new
permissions
that
we
have
so
that
issue
needs
review.
F
F
I
know
craig
has
made
but
been
making
and
updating
several
issues
about,
like
the
different
data
that
we
can
possibly
collect,
and
we've
actually
had
a
tag
for
this
for
the
history
of
the
project,
almost
there's
a
needs,
usage,
metrics
tag,
and
if
you
look
at
that
tag
on
github
there's
like
20
items
in
there
of
like
things
that
we
could
potentially
collect
and
greg
has
been
going
through
and
starting
to
make
pull
requests
to
collect
those
things
greg.
Do
you
want
to
talk
further
on
that
point.
C
Yeah,
so
we
need
a
change
record.
That's
why
the
that
that
issue
is
still
it's
tagged
as
fixed
the
main
the
main
code
has
gone
in.
So,
as
you
said,
the
follow-up
things
is
created.
Change
record,
decide
what
things
we
want
to
collect
with
the
introduction
of
this
and
then
the
biggest
thing,
possibly
that
we
discussed
in
our
previous
meeting
was
that
we
now
need
to
decouple.
E
C
So
basically,
the
coupling
telemetry
from
the
not
telemetry
but
usage
statistics
of
module
from
the
installer
and
then
prompting
users
to
enable
telemetry,
so
basically
an
opt-in
for
the
installer
which
we
need
to
decide.
So
these
are
follow-ups,
I'm
not
sure
if
we
have
enough
time
to
to
make
it
for
this
release,
but
it
can
be
a
task
for
120.1.
F
Yeah,
do
we
there's
the
in
the
meta
item
issue
285?
C
C
There
must
be
another
issue,
but
maybe
we
failed
like
we
didn't
add
it
to
this
meta.
So
the
decision,
sorry,
not
the
decision,
but
the
discussion
that
we
had
last
time
late
was
that-
and
I
don't
think
it
was
during
the
dev
meeting
was
during
the
sprint-
was
that
we
we
reword
the
checkbox
that
is
in
the
settings
for
the
updater
updater,
which
basically
now
says
that
sends
project
statistics
as
well
usage
statistics.
C
So
we
enable
that
and
that's
the
only
thing
that
we
expose
and
then
the
we
need
to
decide
whether
enabling
the
telemetry
should
be
part
of
the
installer
or
it
should
be
a
message
once
the
installation
is
finished.
F
F
C
F
So
that'll
be
the
big
difference
that
right
now
update
module,
there's
no
choice.
If
you're,
if
update
module,
is
turned
on
we're
collecting
usage
information
on
you,
which
honestly
is
not
ideal
in
the
first
place
like
you,
should
totally
be
able
to
check
for
updates
without
telling
us
what
you're
running
you
know.
C
F
And
the
great
thing
about
that
is
that
also,
if
you're
not
if
we're
not
collecting
stats
on
your
site,
it's
also
more
efficient
for
us,
because
we
can
serve
up
cached
versions
of
those
xml
files
right
now,
if
you're
collecting
usage
information,
just
the
act
of
checking
also
requires
some
server-side
processing
on
our
side.
F
F
That
all
sounds
really
wonderful
and
I
I
kind
of
agree
with
you
greg
that
I
don't
even
think
that
this
necessarily
needs
to
be
1.20
type,
things
that
we
could
probably
make
these
changes
in
121.,
one
sorry
120.1,
as
just
like
incremental
additions
to
things,
it's
possible
that
maybe
telemetry
we
should
start.
We
should
make
a
policy
about
like
what
is
telemetry
data
collection.
You
know
like.
Is
that
a
feature?
Is
it
a
ux
thing?
C
One
thing
that
needs
to
be
done
before
the
release,
though,
is
we
need
to
decide
whether
telemetry
is
on
or
off,
and
I
think
that
we
are
all
leaning
towards
off
right.
It
needs
to
be
an
opt-in
thing,
correct
those
of
us
that
know
can
start
enabling
it
and
using
it
and,
and
then
the
next
big
decision
is
for
existing
sites.
How
do
we?
How
do
we?
C
Let
them
know
that
this
is
an
option?
Now
I
think
that
tim
mentioned
the
dashboard
notification
thing,
or
we
can
do
some
tweeting
about
it,
so
that
we
can
let
people
know
how
how
they
can
help
us,
but
this
there's
some
tasks
to
that.
We
need
to
create
a
either
create
a
new
policy
page
like
privacy
policy,
page
on
backdrop,
cms.org
or
update
the
existing
one,
with
what
data
will
we'll
be
collecting
for
telemetry.
F
F
C
The
other
section
for
the
telemetry
and
say
that
it's
sort
of
like
it's
opt-in
and
maybe
lists
either
list
the
things
that
we
collect
or
in
order
to
avoid
having
to
update
it
every
time.
Maybe
we
we
have
a
dedicated
page
like
we
have
the
gist
of
it
there,
that
it's
an
opt-in
and
why
it's
there,
and
then
we
have
a
dedicated
page
for
telemetry,
which
we
can
add
the
the
data
that
we
collect
like
the
charge
or
whatever
we
have
in
the
future.
F
Yeah
yeah
and
I
like
the
idea
of
just
being
able
to
link
to
backdrop
cms.org
privacy
and
then
that
link
will
live
forever
in
the
code
and
then,
if
we
need
to
make
any
changes
or
bisect
the
privacy
policy
into
multiple
pages
like
we
can
do
it
all
from
that.
One
page.
B
F
I
wonder
if
that
should
be
a
a
blocker
requirement
for
putting
it
in
the
installer.
You
know,
because
we
should
really
probably
link
to
the
privacy
policy
like
underneath
that
checkbox
that
says,
like
collect
usage,
information,
send
usage
information.
C
C
Yeah
all
right,
I
might-
I
might
work
on
that-
there's
another
two
issues
that
I
want
to
work,
but
that's
one,
at
least
at
least
the
taking
away
the
checkbox
for
the
updates
from
the
installer
and
replacing
it
with
the
telemetry,
which
basically
enables
the
telemetry
module.
C
F
Okay,
well
geez
yeah,
that's
kind
of
the
items
I
have
telemetry.
I
guess
still
has
more
a
lot
of
other
work
like
the
server
side
component
of
it.
If
we
start
even
adding
like
two
or
three
of
these
other
feature,
requests
greg
that
you've
added
for
telemetry
data
we'll
need
to
start
putting
a
lot
of
effort
into
well,
not
a
lot
of
effort,
but
we'll
need
to
start
making
the
reporting
page
for
telemetry
data
a
lot
better.
F
That's
what
I'm
getting
at,
because
we,
I
think
just
listing
every
single
one
of
them
as
a
table
is
going
to
get
overwhelming.
Really
pretty
quick
and
some
things
are
like
really
super
important,
like
the
version
of
php
that
you
have
other
things,
maybe
not
so
much.
You
know
like.
Is
this
a
multi-site?
You
know
one.
F
C
We
always
wanted
is
like
the
most
useful.
I
guess
is
the
which
core
modules
and
themes
are
enabled,
and
this
is
an
array-
it's
not
just
a
simple
volume.
So
if
we
can
work
on
that-
and
maybe
add
it
sooner
than
later-
yeah.
F
I
think
I
think
that
one
that
one
will
probably
require
some
like
whole
new
way
of
thinking
about
the
data,
because,
like
you
say
it's
an
array
so
unless,
unless
we
wanted
to
be
really
stupid,
stupid
about
it
and
just
like
collect
like
individual
items
like
is,
you
know,
is
editor
module
or
sorry.
There's
no
editor
module
is.
F
Module,
that's
a
great
example:
contact
module
turned
on
or
off
you
know.
We
just
make
a
telemetry
info
item
for
every
module
that
we
care
about.
Collecting
you
know
and
and
collect
them
individually
rather
than
blanket
like
you
know,
is,
is
node
module
turned
on
and
off?
You
know
that
sort
of
thing.
F
So
we
could
do
it
right
now
and
maybe
like
one
of
the
ways
we
can
improve.
This
is
like
if
we
started,
like
quote
categorizing
the
the
telemetry
data
on
the
server
side,
so
that
you
could
filter
by
big
batches
and
one
of
those
categories
could
be
like
core
modules
or
something
like
that,
and
then
it
wouldn't
really
matter
that
we're
collecting
it
in
such
a
you
know
rudimentary
way,
because
he
would
just
segment
out
that
whole
set
of
things
into
a
different
group.
C
F
F
F
All
right,
yeah.
C
F
There
was
a
time
that
I
remember
jen
used
project
module
at
one
of
her
previous
agencies
at
chapter
three.
They
actually
used
project
module
instead
of,
like
you
know,
asana
or
jira,
but
that
was
before
those
things
existed.
You
know
so
now,
there's
so
many
other
project
management
things
that
it
would
be
a
little
bit
silly.
I
think,
to
use
project
module
for
like
issues
issue
tracking,
for
example,
but
people
used
to
do
that
more
frequently
before
they
had
better
tools.
G
I
mean
I
could
do
a
quick
update
on
the
config
recipe
discussion
we
had
which
so
we
we
we
patched
a
bug
in
1.20
that
makes
config
recipes
possible.
We're
not
announcing.
This
is
a
big
feature,
because
there's
still
a
lot
of
questions
about
what
config
recipes
are
and
such,
but
we
have
a
couple
of
sample
config
recipes
and
the
discussion
in
the
last
meeting
was
like
in
the
interim.
G
Do
we
want
to
go
ahead
and
release
these
as
modules?
Are
we
far
enough
along
you
know?
Is
it
okay
for
me,
for
example,
to
push
my
personal
recipe
projects
into
backdrop
and
crab,
or
is
that
premature
and
I
think
the
decision
that
we're
we
we're
at
right
now
is
that
there's
no
harm
done
in
creating
and
releasing
some
recipe
modules
we're
not
providing
any
kind
of
official
support
for
them
or
anything
just
yet
jen
is
working.
G
G
Perfect,
okay,
so
basically
a
contrib
module
that
will
allow
you
to
basically
and
it's
gonna.
Is
it
gonna
use
the
package
or
is
it
gonna
use
a
custom
field
that
we're
gonna
add
to
the
dot.
G
You
manage
recipes
on
your
site
that
you
can
upload
and
then
they'll
be
available
on
backdrop.org,
and
this
will
allow
us
to
it
will
allow
people
to
easily
install
recipes
through
the
ui
by
because
they're
available
in
backdrop.org,
so
yeah-
and
you
know
I
think
we
decided-
I
was
just
asking
things
like
naming
them
should
I
include
recipe
in
the
name
or
whatever,
and
I
guess
we
decided
not
to
do
that
in
the
machine
name
for
your
modules,
because
that
might
sort
of
lock
us
into
things
in
the
future,
but
they
could
have
a
username
that
includes
recipe
in
it.
G
But
basically,
I
think
sort
them
by
package
is
the
way
right.
Now.
It's
it's
used
to
package
type
recipes
or
package
equals
recipes
so
that
they
in
the
module,
the
in
the
brow
or
the
module
browser.
They'll
all
show
it
together.
I
think
that's
the
main
thing
and
we're
gonna,
you
know
we
can
add.
I
think
we
decided
we
can
add
a
another
data
point
in
the
dot
info
file,
whether
or
not
that's
supported
right.
F
C
D
So
I
I
I
came
to
the
last
meeting
late,
so
I
kind
of
missed
half
of
this
discussion
for
jen's
module
is
the
idea
that's
going
to
be
basically
just
glue
code
around
the
existing
module
and
installer
implementations
with
like
a
simple
I'm,
a
simplified
ui.
A
Yeah,
it's
just
it's
just
like
the
module
listing
only
it's
only
gonna
list,
the
ones
with
packaged
recipes
and
then
right
now
it
doesn't
even
have
an
enable
disabled
toggle
on
it.
But
we
can
add
that
and
then
I
thought
what
would
be
really
convenient
is
if
it
had
like
a
revert
option
for
the
config
in
it.
So
that's
sort
of
my
end
goal
is
to
get
that.
A
F
Okay,
yeah
there's
lots
of
exciting
things
happening
what's
happening
between
now
and
wednesday.
Yeah
we've
got
the
telemetry
items.
Definitely
to
discuss
robert
that
one
issue
that
you
raised
it
wouldn't
be.
It
wouldn't
hurt
to
you
know,
go
ahead
and
take
a
look
at
that
issue
as
well.
I
don't
have
the
number.
F
Five,
zero,
seven
seven,
and
that
is
just
some
ui
tweaks
to
the
layout
listing
page
but
yeah.
I
think
in
the
meantime,
you
know
it's
always
good
to
keep
an
eye
on
the
the
119
milestone.
Actually,
119.4
is
the
current
one.
That's
usually
where
bug
fixes
actually
accrue
is
things
that
we
could
act
on
immediately
so
in
between
now
and
next
wednesday.
You
know
that's
a
good
list
of
things
to
do
to
find
for
for
checking
like
bug,
fixes
and
things
like
that.
C
Does
this
zen's,
the
issue
number
is
five
5149,
which
is
pretty
close.
It
just
needs
a
test
to
be
fixed
in
just
a
few
css
fixes
here
and
there,
which
is
a
big
improvement
of
how
the
flexible
template
ui
looks
like
consistency.
This
is
really
close
and
I'm
confident
that
we
can
sort
of
like
sort
it
out
over
the
weekend
or
before
wednesday.
C
Golf
thanks
and
then
I
have.
I
have
two
issues
that
I'm
working
on.
One
is
50
90,
which
is
the
toggles
for
more
or
less
and
then
I'll
need
to
find
the
one
where
I
fix
the
states
for
the
container
type.
C
F
G
C
I
think
I
think
if
there's
older
items
there,
it
would
be
beneficial
to
add
one
for
that
and
one
for
final
sprinting
over
the
weekend
or
the
days
to
come.
C
F
All
right:
well,
let's
wrap
it
for
today
then
great
great
meeting,
folks
and
great
work.
I
know
I
wasn't
here
last
week,
so
I
don't
want
to
miss
my
opportunity
to
say
thank
you
to
all
of
the
hard
work
that
happened.
The
the
code
sprint
weekend
was
wild.
Like
I
mean
it
was
just
all
all
cylinders
firing
lots
of
people
around
the
clock,
new
stuff
coming
in
yeah,
excellent
teamwork,
laryn
being
a
core
committer.
Oh
my
gosh
boy.
F
He
was
really
keeping
on
top
of
things,
and
lots
of
things
have
been
coming
in
small
bug.
Fixes
like
really
consistently
now
really
appreciating,
laryn's
new
help
merging
in
issues
but
our
other
core
committers,
bw,
panda
and
herb
dual.
Also
like
just
hopping
in
there
tag-teaming
back
and
forth,
or
to
be
saying
boy
it
was,
it
was
a
sight
to
behold.
I
really!
F
Oh,
oh,
am
I
sorry
total
tangent
here,
but
it's
time
for
a
story
that
I
was
I
was
burned
out
at
the
end
of
the
weekend,
and
I
was
like.
Oh
my
gosh.
I
don't
like
there's
these
issues
that
people
are
counting
on
me
to
review
and
I
kept
delaying
it
and
then
all
day
sunday
I
was
like
okay.
Finally,
I
got
to
sit
down
and
look
at
this
stuff.
I
sat
down
at
like
10
p.m.
F
F
All
three
of
them
had
been
fixed
and
merged
and
completed
with
everything
done,
and
I
was
like
this
is
so
great
because
yeah
like
this,
it
wasn't
dependent
on
me
and
it
didn't
need
my
review,
because
there
was
so
much
great
collaboration
happening
between
our
our
community
members
and
I
just
feel
so
thankful
and
so
grateful
that
we're
really
getting
to
that
point
where
it's
like
you
know,
every
like
every
point
in
our
project
is
not
held
up
on
any
one
person
and
yeah.
F
C
F
Obviously
yeah
it's
super
beneficial
and
I
just
yeah
putting
in
the
work
of
more
getting
more
court.
Committers
is
definitely
worth
it
because
the
return
is
is
really
great
and
I
think
that's
true
for
all
positions
actually
that
the
fewer
people
we
have
in
any
one
position,
the
the
more
important
it
is
to
get
some
more
people
added
into
that
same
role.
G
F
Okay,
all
right!
Well
now
we
really
are
out
of
time.
So
thank
you,
everybody
once
again
and
we'll
catch
you
guys
next
week
after.