►
From YouTube: Backdrop Weekly - September 24th
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
Today
is
thursday
september
24th,
and
this
is
our
weekly
developer
check-in
meeting
and
before
we
get
started,
we're
gonna
go
around
and
do
introductions,
but
I
just
wanted
to
say
that
we
know
nate's
not
here
and
he
will
be
joining
us
a
little
later,
so
we're
after
that
gonna
go
to
the
bottom
of
the
agenda
and
start
with
the
q,
a
discussion
section
until
nate
gets
back
so
tim.
Let's
start
with
introductions.
B
Sorry,
my
name
is
tim
saint
paul
team
on
the
internet.
I
am
coming
from
deerwood
minnesota.
B
The
only
thing
I
think
I'm
gonna
say
in
introductions
is
that
I'm
recovering
from
backdrop
live
last
weekend
and
starting
to
get
ready
for
open
source
day
next
week,
when
we're
gonna,
hopefully
have
some
new
folks
in
our
hoq,
helping
us
out
for
at
least
a
day,
and
maybe
we
can
convince
a
few
of
them
to
come
back.
B
That's
it
gregory.
C
A
And
I
am
jen
lampton
calling
from
oakland
california
and
yeah
I'm
looking
forward
to
talking
about
the
future.
A
So
before
we
move
on
to
discussion,
I
just
want
to
say
a
couple
of
things:
we
have
two
new
contributors
in
the
application
queue
with
a
port
of
the
rules
once
per
day
module
and
a
port
of
the
zerb
2020
theme.
So
I
wanted
to
do
a
quick
thank
you
to
bug
folder
and
cheese.
A
Dj
this
is
the
work
I
believe
for
working
on
those
projects
and
hopefully,
we'll
get
both
of
those
projects
reviewed
by
the
end
of
the
day.
I
did
one
of
them
this
morning,
other
ones
half
done
with
and
then.
A
Sorry
about
that
all
right
contributed
projects
this
week,
there's
a
new,
a
new
module,
the
civic
serum
kron
module
was
released.
A
I
also
wanted
to
say
a
quick
thank
you
to
bw
panda,
who
has
been
working
tirelessly
for
like
the
last
two
years
on
the
forum,
api
page
on
the
backdrop
api
site
when
he
first
mentioned
him
like
this
is
crazy.
This
is
way
too
much
work.
Nobody
would
ever
want
to
do
this
and
he's
been
plowing
forward
with
it
for
forever
and
he's
really
close
he's
got
to
the
point
where
they're
just
ready
to
enter
content,
so
yeah
a
huge
thanks
for
the
continued
commitment
to
getting
that
done.
B
Yeah,
I
just
wanted
to
quickly
bring
up
meta
issues
and
how
we're
using
them
and
I'll
just
quickly.
My
intro
is
right.
I
think
of
a
meta
issue
is
usually
a
high
level
issue
with
a
lot
of
sub
issues,
and
we
were
talking
about
gregory
before
he
got
online,
because
I
just
ran
into
a
couple
of
metal
issues
that
you've
created
that
really
aren't
just
sort
of
high-level
discussions
of
an
issue
which
is
appropriate
but
don't
have
any
like
child
links
in
them.
B
Yet
and,
like
I
came
to
one
of
those
I
think
related
to
the
date
stuff,
and
you
had
this
meta
issue
with
like
20
screenshots
in
it
and
I'm
like
I'm,
not
sure
if
this
is
where
I
should
like,
if
I
should
create
a
new
medi,
I
want
a
meta
issue
for
these
sub
issues
and
I
don't
you
yeah.
I
don't,
and
also
I
just
want
to
ask.
I
have
you
in
the
last
probably
two
months
spent
time.
B
C
Yeah,
so
meta
issues
can
come
to
life
in
various
ways.
Either
you
have
a
plan,
you
have
a
discussion
and
then
you
know
that
there's
some
tasks,
so
you
create
a
parent
issue
so
to
speak,
to
sort
of
coordinate
the
rest
of
the
issues
or
you
start
off
an
issue
without
it
being
a
meta.
But
the
discussion
moves
so
far
along
and
so
there's
so
many
ideas,
or
things
mentioned,
that
you
convert
that
into
a
meta
and
then
split
off
of
separate
tasks.
C
So
where,
where
you
know
manageable
tasks
can
be
discussed
and
separate,
pull
requests
can
be
made
for
different
sections,
and
I
guess
I
guess
maybe
sometimes
the
initiatives
if
they
have
an
issue,
they
might
need
to
be
meta
issues.
C
Sorry,
the
other
way
that
this
can
be
born
is
that
if
you
have
like
different
people,
raising
issues
about
a
similar
subject,
but
different
different
things
like
improving
a
singular
aspect
of
backdrop
or
a
similar
or
the
same
page,
then
in
order
to
have
a
sense
of
how
sort
of
like
to
coordinate
those
things,
you
create
a
meta
and
you
link
those
tickets
off,
so
a
person
might
come,
create
a
ticket
and
then,
after
a
few
months,
another
person
and
then
over
the
years,
a
lot
of
issues
about
the
same
thing
get
covered.
C
I
guess
into
so
that's
that's
my
understanding
of
how
things
work.
A
How
how
those
issues
come
about
can
be
any
possible
format
like
it
could
have
started
as
one
issue,
and
then
we
realized
it's
actually
10
or
it
could
just
be
one
that
turns
into
two
like
it
doesn't
have
to
have
any
given
like
amount
of
child
issues.
It's
just
like
if
there's
one
thing
where
you
want
a
whole
bunch
of
different
things
done,
and
it's
really
hard
to
do
them
all
in
one
issue,
it's
much
easier
to
make
smaller
issues,
but
you
want
to
keep
them
all
kind
of
grouped
together.
A
That's
the
general
idea
and
I
think
yeah.
If
you
find
one
that
doesn't
have
child
issues
in
the
issue,
it
could
be
that
those
child
issues
are
mentioned
in
the
comments,
and
we
just
need
a
little
like
clean
up
to
make
it
clear
why
it's
a
meta
or
it
could
have
been
something
that
started
as
a
meta
and
eventually
morphed
into
not
a
meta,
and
maybe
just
meta
was
never
removed
from
the
title.
C
Or
a
third
or
a
third
thing
could
be
that
we
knew
what
tasks
needed
to
be
sort
of
like
some
issues
needed
to
be
created,
but
we
didn't
get
to
creating
them.
We
have
the
bullet
points,
but
no
issues
for
them,
which
is
that's
another
case
yeah.
B
Yeah
well,
let's
look
at
a
specific
specific
example:
2653
it's
making
basis
work
better
as
an
admin
theme,
it's
defined
as
a
meta
issue,
but
really
it
seems
more
like
a
broad
discussion
about
like
how
to
do
this.
There
are
no
child
issues
and
basically,
I
wanted
to
add
a
child
issue
to
it,
but
it
feels
like
it's
not
the
right
place
to
do
it.
So
I'm
just
wondering:
can
you
please
repeat
the
number
two
six
five,
three,
two
six
five
three.
C
Yeah
sure
so
what
we
can
do
is
when
you
I
put
the
screenshots
there,
but
we
can
remove
the
screenshots
if
you
create
separate
tickets,
for
them
so
feel
free
to
just
create
tickets
in
place
of
the
screenshots
and
move
the
screenshots.
To
that
other
issue
that
you
create.
Okay,
that's
that's
one
suggestion
but
feel
free
to.
A
A
So
yeah
like
this
reads
right
now,
like
a
thought
like
an
experience
and
that's
useful
from
the
I
don't
know,
understanding
perspective,
but
from
the
solutions
perspective
it's
hard,
so
yeah
feel
free
to
rework.
However,
you
think
works.
Yes,
okay,.
B
Any
other
comments
just
on
like
because
there
are
some
of
our
meta
issues
that
are
pretty
far
out
of
date
and-
and
I
mean
that's
okay,
but
I
just
want
to
make
sure
that,
like
people
still
like
meta
issues
and
they
want
to
keep
them
up
to
date,
so
I'm
not
wasting
wasting
my
time
when
I
do
update
them.
A
No,
I
think,
they're
really
helpful
to
help
just
in
terms
of
organization.
We
don't
have
any
other
way
to
really
represent
hierarchy,
and
so
I
think
you
know
whatever
people
feel
helps
them
stay
organized
in
a
meta
is
allowed.
So
there's
no
real,
strict
rules.
So
much
as
like
it
that
that
tag
is
supposed
to
indicate
this
there's
a
bunch
of
stuff
going
on
here
and
there
should
be
links
to
other
things
inside
and
that's
kind
of
it.
B
Like
the
recently
I
did
about
the
blocks
blocks
blocks
meta,
you
know
I
I
knew
that
there
was
about
eight
ten
issues
that
weren't
linked
to
it.
So
I
just
spent
a
half
an
hour
linking
you
know,
adding
a
bunch
of
sub
issues
to
that
yeah.
C
There's
sometimes
there's
sometimes
that
we
miss
people
are
not
aware
of
the
existence
of
the
meta
issues,
so
they
create
tickets.
So
it's
left
to
some
of
us
to
go
and
link
it
at
some
point,
since
you
mentioned,
if
we
need
to
add
a
comment
at
some
point,
we
discussed
about
using
github
projects.
Are
you
aware
of
what
that
is?
Yep,
yep,
okay,
but
some
matters
are
not
as
big
to
sort
of
qualify
for
projects
and
that's
what
I
wanted
to
say.
C
G
You,
okay,
yeah
I'll,
add
that
I
also
really
appreciate
meta
issues
just
the
way
that
we
aggregate
and
use
them
yeah,
even
though
it's
somewhat
tedious
to
collect
the
things
inside
of
them.
If
you're
interested
in
a
particular
topic,
it's
a
really
great
way
to
see
like
here's
everything
related
to
layouts,
for
example,
yeah
yeah.
I
really
like
them,
because
the
alternative
would
be
like
we
use
tags
or
or
projects
and
projects,
I
think,
has
kind
of
been
a
bust
like
our
use
of
them.
Github
projects
is
like
it's
like
a
trello
board.
G
C
Another
thing
that
might
help
tim
is
that
metas
start
as
a
sort
of
like
way
to
organize
or
improve
a
specific
section,
and
if
we
that
is
in
a
bad
shape-
and
if
we
get
that
in
a
good
shape,
then
it
may
not
any
longer
make
sense
to
keep
the
meta
open.
We
just
close
the
mirror.
We
say
we've
done
most
of
these
things
and
then
we
don't
need
to
keep.
You
know
adding
things
to
that.
C
Then
we
can
file
separate
issues,
so
you
can
identify
that
if
you
see
within
a
short
period
of
time,
people
raising
issues
about
the
same
aspect
like
a
new
feature
that
was
introduced
and
they
have
follow-up
issues.
Things
like
that
so
yeah,
I
think
it
it
organically
sort
of
like
evolves
to
a
helpful
tool.
B
G
All
right,
so,
if
you're
saying
that
we
started
from
the
bottom
up,
some.
G
Okay,
got
it,
have
you
done
the.
G
G
Well,
let's
start
going
over
that
then
I
yeah
it's
kind
of
tradition
that
I
read
through
this
section
I'll
preface
this
a
little
bit
did
we
already
celebrate
backdrop
live
because
I
think
we
should
take
a
minute
to
do
that
then
so
yay
we
had
our
first
online
conference
event
our
first
exclusive
backdrop
event,
probably
ever
it
wasn't
associated
with
any
other
camp
or
conference
or
tim
anything
you
want
to
say
any
of
the
words
in
particular.
B
Well,
nope,
except
two
48
hours
of
virtual
goodness,
65
participants
or
65
registrations.
Not
everyone
showed
up,
but
we
raised
like
thirteen
hundred
dollars
in
in
fees
or
in
donations,
yeah
and
a
lot
of
good
discussions.
G
Yeah,
I
think
it
was
a
smash.
It
was
so
great.
We
I
mean
we
brought
in
a
lot
of
people
that
we
don't
see
regularly
or
that
we've
never
seen
at
all
like.
I
think
we
expanded
our
community
reach
quite
a
bit.
We
generated
a
lot
of
buzz
on
social
media.
We
generated
a
lot
of
new
content
that
got
published
to
our
youtube
channel.
G
Most
of
the
recordings
or
most
of
the
sessions
were
not
recorded
because
they
were
in
a
discussion,
format
that
allowed
free
conversation
to
occur
without
a
penalty,
but
the
ones
that
were
presentations
are
recorded
and
posted
to
our
youtube
channel
and
yeah.
It
was,
it
was
just
great,
oh
and
it
was
really
excellent
for
the
people
that
do
we
do
frequently
see
just
to
get
together
and
hash
out
some
very
specific
problems.
G
So
these
weekly
meetings
can
be
a
little
wrote,
sometimes
and
there's
not
enough
time
to
really
deep
dive.
Anything.
G
Like
10
things
and
backdrop
live,
gave
us
those
opportunities
to
really
look
at
individual
topics
as
a
team
and
have
people
come
in
and
really
have
an
extended
conversation
about
those
things.
Yeah.
G
Constraints
yep,
so
talk
about
a
hit
backdrop.
Live
was
super
awesome.
So
so
so
we
had
backdrop
live
this
past
weekend
and
then
a
week
before
that
we
had
or
in
the
week
days
before
backdrop
live.
We
also
had
the
release
of
backdrop
117.
G
So
it's
been
action-packed
the
past
couple
of
weeks
with
getting
releases
getting
the
bug.
Final
bug,
fixes
out
conference
planning
and
then
actually
executing
the
conference
so
yeah.
I
think
all
of
that
is
to
say
that
the
updates
in
the
core
land
actually
aren't
really
like
where
the
effort
has
been,
but
we
can
go
over.
Those
updates.
Nonetheless,
so
1
17
is
our
current
version
of
backdrop
and
the
next
bug
fix
release
will
be
117.1.
G
Oh
man,
there's
just
so
much
activity
that
happened.
We
also
released
a
public
service
announcement
to
the
security
page
of
backdropcms.org
that
notified
that
there
was
a
security
release
of
drupal
on
september
16th
and
we
intentionally
did
not
release
a
corresponding
version
of
backdrop.
Even
though
a
new
version
of
drupal
7
came
out
almost
always
we
coordinate,
we
actually
did
coordinate,
but
we
release
simultaneously,
within
the
same
day
at
least
a
version
of
backdrop
for
every
version
of
drupal.
G
As
a
security
update,
we
intentionally
did
not
make
a
backdrop
release
because
it
was
the
day
after
1.17
came
out
and
forcing
a
security
update
or
an
alarming
notification.
On
every
backdrop
website
saying
you
have
to
update
right
after
117
came
out
would
be
putting
a
lot
of
pressure
on
our
users
that
we
didn't
want
them
to
feel
like
they
should
upgrade
to
117
right
away
when
at
the
same
time
we
just
released
it
and
we
weren't
100
certain
that
there
weren't
unknown
upgrade
issues.
G
So
the
public
service
announcement
says
that
we'll
be
doing
the
117.1
release
on
september
30th,
which
is
great
because
that's
within
the
two-week
window,
you
know
that
we
usually
fix
any
issues
that
have
happened
in
the
current
release
and
then
we
make
a
bug
fix
release
with
those
addressed.
G
B
G
Yeah
and
we
as
I'm
actually
not
sure
if
it's
policy,
but
almost
all
security
releases,
also
have
bug
fixes.
In
the
main
backdrop,
it's
only
if,
by
pure
coincidence,
that
we've
had
a
bug
fix
release,
nothing
else
has
been
committed
and
then
we
make
a
security
release.
That's
the
only
time
that
an
issue
or
a
release
only
has
security
issues.
Then
it's
pure
coincidence.
G
In
the
world
of
drupal
briefly,
where
they
released
two
versions
every
time
a
security
update
came
out,
but
they
stopped
doing
that
because
it
was
too
confusing
like.
Why
are
two
new
versions
of
drupal
coming
out
on
on
wednesdays,
that
it
was
just
a
it
was
strange,
got
it
so
117
one
is
the
next
version
of
backdrop,
it'll
be
coming
out
september
30th,
and
we
have
these
issues
that
we
could
potentially
pursue
in
that
time
frame.
So
first
one
up
is
transliteration,
does
not
respect
the
site
default
language.
G
It's
issue
2637.
It
currently
needs
code
review,
but
has
been
marked
works
for
me
and
has
test
coverage
and
looks
like
it's
in
really
good
shape.
Andy
gozella
posted
three
days
ago,
politely
saying
the
pull
request
has
been
updated
and
it's
ready
for
another
review,
so
that
one
is
in
good
shape.
G
We
added
a
new
feature
in
117
that
allows
you
to
put
descriptions
and
titles
on
the
administrative
interface.
When
you
place
a
block,
you
can
customize
what
is
shown
on
the
administrative
interface
to
represent
that
block
and
issue.
4
600
is
an
issue
that
just
cleans
up
the
labels
and
descriptions
on
the
fields
for
labels
and
descriptions.
G
So
it's
just
like
terminology
tweaking
and
help
text
changes
to
make
that
more
clear.
It
currently
needs
review
and
testing,
but
it's
really
just
string
changes.
Let's
see
the
site
gets
stuck
in
maintenance
mode,
sometimes
when
updating
modules
using
the
ui.
This
issue
is
39.56
currently
has
needed
review
for
quite
some
time.
Three
weeks
now
currently
still
needs
that
aids
review
and
testing.
G
G
Let's
see
a
usability
improvement
is
the
next
one,
removing
the
block
title
for
the
search
box
that
if
you
place
a
search
block
on
the
page,
it
currently
has
a
label
on
the
field,
and
it
has
a
title
on
the
block
and
it
has
a
button,
all
of
which
say
search.
So
the
search
block
currently
says
search,
search,
search
and
the
enhancement
is
that
we'll
remove
the
label
from
the
field
and
from
the
block
title
and
leave
it
on
the
button
it's
issued.
3476..
G
Yeah
these
next
four,
I
don't
think,
have
any
updates.
So
I'm
going
to
just
read
their
summaries
as
a
reminder
that
we're
working
on
them.
G
There's
an
issue
with
the
views
or
behavior
that
doesn't
work
quite
as
expected.
That's
issue
3415.,
removing
the
words
blacklist
and
whitelist
from
core
issue.
4441
we
haven't
had
any
updates
on
that
issue
and
the
similar
issue.
Removal
mastering
slave
terminology
from
core
44
51..
G
Both
of
those
issues
have
had
a
couple
of
caveats
that
have
made
that
a
little
bit
more
difficult
than
we
expected
it's
possible
that
we
might
start
splitting
them
out
into
like
the
easy
part
and
the
hard
part
just
to
make
it
so
that
we
can
move
forward
with
the
changes
that
are
easy
easily
made
next
up
30
to
13,
adding
automated
code
checks
using
phpcs.
G
G
But
some
modest
progress
is
coming
along
in
that
area
as
well,
though
it's
not
in
the
issue,
so
I
don't
actually
have
a
lot
to
convey
verbally
last
up
is
using
tugboat
qa
for
pull
request
sandboxes
this
one
most,
interestingly,
is
marked
fixed,
but
I
haven't
seen
a
pull
request.
That's
used
it
yet
gregory.
Have
you
noted
any
change
in
the
sandbox
behavior.
C
I've,
no,
I
haven't
we're
still
using
zen
ci.
I
think
there's
something
neat
that
needs
to
be
done
on
your
blast.
I
recall,
I
think
you
need
to.
We
need
to
decide
whether
we're
going
to
set
up
a
separate
account
for
the
prs
or
require
talk
to
the
tag
board
team
to
give
us
more
space
if
needed.
I
can't
remember
exactly
what
it
was,
but
I
remember
that
it
was
waiting
on
something
for
me.
G
Okay,
yeah,
I
see
hang
on
there's
a
follow-up
issue.
Oh
no,
there's
an
additional
comment,
so
the
code
is
merged
into
core,
like
you
say,
but
we
haven't
done
the
corresponding
setup
on
tugboat
side.
I
did
notice
that
when
I
updated
the
backdrop,
demos
117
that
we
actually
had
a
conflict
because
now
there
was
a
tugboat
directory
in
core
itself
and
the
tugboat
demos
directory
demo
site
also
has
a
tugboat
directory,
and
so
we
had
a
merge
conflict.
G
But
for
the
time
being,
I
just
removed
that
from
the
tugboat
demos
repository
it's
still.
In
the
actual
backdrop,
core
repository,
but
yeah
there's
some
additional
work
that
needs
to
be
done
there,
but
it's
exciting.
I
think
that
bw
panda
did
all
of
the
work
on
his
own
site
with
his
own
tugboat
account
and
had
it
all
fully
working.
So
it's
it's.
The
core
changes
are
made
and
we
just
need
to
like
finalize
the
connection.
I
bet
we
have
to
set
up
the
github
hook
too
yeah
like
fire
off
the
tugboat.
C
Peter
also
provided
instructions
on
how
people
could
test
it
on
their
own
fork
of
backdrop,
so
they
can
do
it
with
their
own
tagboard
account.
And
one
thing
to
note
is
that
we
need
this.
We
need
a
separate
account
or
the
separate
repo.
I
guess,
because
the
tagboard
account
that
we
use
on
the
main
site
is
configured
so
that
tag
both
sandboxes
are
being
destroyed
after
24
hours,
but
we
don't
need
that
for
prs
more
system.
G
Yeah
I'll
I'll
post
a
comment
first
of
all,
but
I'll
also
reach
out
to
tugboat
and
see
if
we
can
get
us
either
a
second
comp
account
or
if
our
current
account
can
be
increased
because
right
now
we
cap
out
at
40
gigabytes,
and
we
have
exceeded
that
at
times
when
we
have
more
than
200
sandboxes.
G
That
was
mostly
an
error
in
which
sandboxes
had
not
been
getting
cleaned
up
properly.
Now
that
they're
getting
cleaned
up
properly,
so
we're
well
with
under
that
40
gigabyte
limit,
but
with
sandboxes
of
which
we
have
hundreds
of
sandboxes.
G
I
have
a
feeling
that
we
may
legitimately
start
consuming
kind
of
a
large
volume
of
space,
so
okay,
well
I'll
reach
out
to
talkboat
and
I'll.
Also
take
a
look
at
this
issue
to
see
what
integration
we
need
on
on
the
backdrop
site
and
on
the
tugboat
side.
I
think
that
once
we
get
this
working,
what
that'll
mean
is
that
for
a
while,
we
may
have
two
sandboxes
on
every
pull
request,
which
I
think
is
fine.
While
we're
getting
that
worked
out.
C
I
have
a
related
question
question
because
I
recently
in
the
past,
they
have
discovered
a
few
issues
that
creeped
up.
We
fixed
an
issue,
a
long-standing
issue,
where,
when
you
selected
a
module
to
be
installed
via
the
project
installer
the
step
where
it
allows
you
to
enable
it
would
only
show,
with
only
this,
the
main
module
and
not
its
modules.
So
we
fixed
that
and
if
you
have
errors,
said
to
be
shown,
there's
a
few
notices.
C
It
doesn't
break
anything
but
there's
a
few
php
notices
that
are
thrown,
so
the
idea
was,
should
we
enable
like.
First
of
all,
let
me
ask
the
question:
it's
my
impression
that
for
the
pr
sandboxes
we
are
using
a
sort
of
like
a
fixed
like
pre-built
database.
Is
that
correct
to
speed
things
up
or
does
it
get
built
from
scratch?.
B
G
C
G
Yeah,
well
that
I
think
that's
fine,
because
our
sandboxes
are
not
the
same
as
our
testing
infrastructure
that
we
can
have
php
errors
and
notices
like
turned
on
in
the
sandboxes,
but
not
turned
on
on
tests
infrastructure,
and
that's
that's
no
problem,
but
that's
a
good
point
that
conceivably
if
we
had
something
that
needed
to
be
tested
that
could
cause
some
confusion
like
in
the
manual
testing
related
to
error
messages,
but
I
think
overall,
that's
kind
of
a
minor
like
edge
case
for
something
it's
not
even
automated.
G
It's
for,
like
the
human
testing,
we
could
just
put
a
note
in
there
and
say:
hey
other
humans
notes
areas
are
going
to
be
turned
on
yeah
yeah.
We
could
either,
like
you
say,
like
run
an
additional
task
like
on
it,
or
we
have
to
set
up
a
settings.php
file
specifically
for
tugboat
to
use
or
the
sandbox
to
use.
We
now
that
we
have
config
overrides,
we
could
just
always
turn
them
on
in
settings.php
yeah.
That
was
method
yeah.
I
think
that
settings.php
approach
is
the
most
obvious
and
straightforward
way.
A
C
So
do
we
have
a
separate
repo
for
such
things,
so
I
can
open
an
issue
about
it.
Is
it
the
main
government
so.
G
For
it'll
it'll
be,
in
the
main
backdrop,
issues
repo
or
issue
right
now,
because
the
back
the
tugboat
integration
for
backdrop
for
the
sandboxes
is
in
core
right.
Now,
it's
literally
a
directory
in
core.
C
G
All
right,
that's
all
of
the
updates
for
117.1.
G
Some
of
these-
I
don't
know
like
they'll,
take
more
work
than
we'll
be
able
to
do
in
the
next
week,
but
a
good
chunk
of
those
early
ones
will
probably
get
completed
and,
of
course,
there's
always
the
117
one
milestone
in
github,
which
has
64
issues
in
it.
Currently,
so
there's
lots
of
items
to
be
prioritizing
for
the
release
that
comes
out
next
week.
G
G
We
will
probably
use
this
meeting
next
week
to
specifically
discuss
118
items
and
that's
kind
of
an
open
discussion
format
where
we
all
come
in
with
crazy
ideas
and
talk
about
which
ones
we
should
prioritize.
But
the
mechanism
that
we
use
for
deciding
118
features
is
still
the
same
that
you
can't
just
come
into
the
meeting
and
say
I
think
we
should
do
that
and
then
we'll
focus
our
attention
on
it.
We
still
need
issue
advocates
to
be
prioritizing
minor
issues
or
minor
release
features.
G
So
the
discussion
is
great
and
you
might
encourage
someone
to
be
an
advocate
or
decide
to
be
an
advocate
during
that
issue,
but
things
for
118
still
require
advocates.
Just
someone
to
take
that
issue
and
and
move
it
forward.
Just
keep
keep
an
eye
on
it
and
encourage
other
people
to
work
on
it,
be
a
person
ready
to
test
and
review
changes
as
they
come
through.
G
So
the
only
items
that
we
have
for
118.
So
far
are
this:
first
one
mysql
8
support
4238
this
issue.
Actually
there's
been
some
discussion
about
putting
it
into
a
bug
fix
release.
G
So
there's
been
some
muttering
about
putting
it
into
a
bug,
fix
release
rather
than
a
minor
version,
primarily
because
the
current
version
of
red
hat
centos
and
if
you
install
my
sequel
on
ubuntu
or
debian,
ubuntu
and
debian,
use
mariadb
by
default,
and
they
don't
have
the
same
incompatibility.
G
But
if
you
do
install
mysql
on
this
latest
version
of
pretty
much
any
linux
operating
system,
my
sql
8
is
now
the
default
and
backdrop
does
not
work
with
it
and
that's
a
bad
look.
So
we
might
not
want
to
wait
a
whole
a
full
four
months
before
we
add
my
sql
eight
compatibility
just
because
this
is
kind
of
a
critical
issue.
Yeah,
it
is
marked
as
a
bug,
but
it's
also
like
has
the
potential
to
break
things
so.
C
G
I
think
it
would
be
unwise
of
us
to
rush
it
into
the
security
update.
That's
coming
out
a
week
from
now,
but
there's
a
good
chance
that
we
may
reach
a
decision
that
it's
safe
enough
to
put
into
1.
17.2
is.
B
B
Who
might
not
know
how,
to
I
mean
really,
all
you
need
to
do
is
clone
that
branch
right,
yeah.
C
G
Also
indigozala
provided
some
instructions
to
domain
good
in
that
issue
and
used
a
trick.
I
didn't
know
existed,
which
is
you
can
go
to
the
pull
request
and
then
add
zip
to
the
end
of
it,
and
it
will
download
an
archive
of
that
branch
instead
of
needing
to
use
git
at
all.
You
can
actually
just
download
all
archive
which
I've
never
seen
before.
B
Path
thing
right,
but
I'm
right
and
I'm
thinking
it's
one
thing
to
like
spin
up
a
new
site
using
backdrop
or
using
that
patch
and
a
new
database,
but
I'm
thinking
to
make
it
easy
for
somebody
to
add
to
an
existing
site
and
test
it
because
I
have
a
few
sites.
I
could
do
that
for
and
I'm
sure
I
can
figure
out
how
to
do
that
testing.
D
It
would
also
be
good
to
test
on
non-mysql
eight
databases
to
make
sure
it
doesn't
break
existing
existing
seven
or
whatever
else.
C
C
E
G
Okay,
let's
see,
we've
got
a
couple
more
issues
still,
but
we're
bumping
up
against
time
so
ad
web
p
support
is
issue.
4509
webp
is
a
new
image
format.
That
is
an
alternative
to
jpegs
and
I've
not
seen
this
issue
prior
to
today,
but
it
looks
like
lauren
is
heading
up
this
particular
initiative.
It
has
a
pull
request
and
it
currently
is
marked
as
needs
code,
review
and
testing
looks
like
ander
goes,
l
added
tests
and
you
need
to
sign
up
from
core
committers
so
yeah.
G
G
C
Yes,
I
I
would
like
actually
to
advocate
for
that,
because
there's
a
few
tickets
that
recently
came
up
like
the
dashboard
blog
that
available
updates,
so
there's
confusion
all
over
the
place.
The
links
linked
to
like
say,
there's
an
update
for
a
module,
but
when
you
click
it
it
lists
everything.
So
we
need
to
picture.
There's
been
a
confusion
for
like
many
versions.
Now,
let's
just
get
it
done.
G
C
Yeah,
so
that's
a
discussion
that
we're
currently
having
so
we
should
keep
the
reports
page
as
our
reports
page
and
the
reports
available,
updates
and
then
we're
thinking
about
moving
the
the
actual
updating
enter
somewhere
like
configuration
system
updates
or
something
which
is
where
you
you
can
actually
perform
the
action
of
updating,
rather
than
getting
a
report
of
what
or
what
needs,
updating
or
has
available
updates
and
the
other,
the
other
sort
of
like
argument
there
is
like.
Why
have
two
pages?
C
G
Yep,
I
think
it's
great
I
I
would
love
to
see
that
because,
like
updates,
first
of
all,
updating
just
your
like
just
one
but
not
the
other
is
really
strange
like,
and
it's
also
strange
that
update
modules
also
happens
to
mean
update
core
right
and
so
there's
a
lot
of
weird
consistencies.
That
inconsistencies
that
happen.
C
You
can
still
select
which
ones
to
update,
because
we
have
the
checkboxes.
The
confusion
is
that
we
are
listing
all
all
types
of
projects
within
each
one
of
those
pages
which
is
supposed
to
be
explicit
to
each
one
of
those
project
types
which
is
like
the
whole
confusion
like
we
say,
update,
update
modules,
that
we
include
core
and
themes
and
layouts,
and
we
do
that
same
same
thing
in
the
other
places,
it's
just
confusing
user
experience.
G
Yep
all
right
looks
like
jen
also
put
into
the
agenda
helpful
list
for
discussion.
G
Week
possibly
jen
apparently
is
interested
in
advocating
15
different
issues,
so
perhaps
we
can
start
with
one
and
then,
as
as
as
we
complete
one
then
she'll
be
able
to
take
on.
Another
she'll
also
probably
want
to
use
the
this
list
for
discussion
for
next
week
to
solicit
volunteers
to
see
if
we
can
parallelize
any
of
this
work
and
get
advocates
on
any
of
these
other
issues
right,
but
I
won't
go
over
all
of
them
today,
since
I
would
just
read
them
so
we'll
do
that
next
week,
yep.
G
That's
it
for
the
118
update.
We
have
a
section
in
here
we're
running
over
time,
but
I'll
say
we
have
a
section
here
for
initiative.
Updates
luke
is
not
around
to
give
us
an
update
on
the
ready
to
wear
initiative.
However
telemetry
I
think
it's
worth
noting
that
tim
has
some
things
to
say
on
telemetry.
B
Sure
I'll
be
really
fast
to
just
say,
still
confirming
this
with
jeff,
but
I'm
under
the
impression
that
he
this
doesn't
have
time
right
at
the
moment,
so
I'm
hopefully
going
to
step
in
and
help
move
this
forward.
Nate
and
I
and
gregory
I
think,
was
there
for
we
did
during
backdrop,
live
we
had
a
nice
discussion
and
got
a
bunch
of
a
brain
dump
from
nate
in
terms
of
things
that
we
could
use
to
move
forward,
and
my
next
step
is
to
sort
of
update
the
issue.
B
G
And
that's
that's
great
news.
The
entire
last
release
we
unfortunately
didn't
have
progress
on
telemetry.
So
I
really
appreciate
the
passing
of
the
torch
to
get
that
moving
along.
A
G
It
still
is
like
the
initiative
that
has
been
voted
upon
and
approved.
It's
like
saying.
Yes,
this
is
super
important
for
us
as
a
community,
and
it's
great
to
have
some
new
leadership
pushing
that
forward.
G
All
right,
that's
it
for
the
entirety
of
the
product
updates
and
you
guys.
B
Yeah,
I'd
like
as
many
people
as
possible
to
be
aware
that
this
open
source
day
is
a
week
from
today
from
the
grace
hopper
conference,
and
I
we've
got
three
mentors
assigned
to
work
with
us
and
then
we
will
supposedly
be
getting
a
bunch
of
volunteers
from
that
conference
that
will
be
sort
of
sprinting
or
contributing
in
our
issue
queue
again
a
week
from
today.
A
couple
of
the
mentors
are
already
in
the
issue:
queue
writing
some
test,
pull
requests.
B
They
started
coming
in
yesterday,
so
one
I
want
people
to
be
aware
of
that.
Be
friendly
and
helpful
to
these
new
folks
who
are
showing
up
in
the
issue
queue
I've.
B
I've
asked
them
to
sort
of
identify
themselves
when
they,
you
know,
do
their
first
post
and
just
to
let
us
know
that
they're
there,
but
also
we're
pointing
them
at
the
good
first
issue
tags
to
help
them
find
issues
to
work
on
and
I'd,
love
help
triaging
those
jen
and
I
have
spent
some
time
going
through
some
of
the
existing
ones
and
either
you
know
untagging
them
if
they're
no
longer
good,
first
issues
or
updating
them
with
additional
information.
B
I
mean
if
you
see
a
good
first
issue,
you
got
to
keep
in
mind
that
these
are
also
like
it's
one
thing
for
a
good
first
issue
for
somebody.
That's
like
used
backdrop
and
never
contributed.
These
are
folks
that
are
completely
new
to
our
community
and
haven't
used
backdrop
before
so.
Sometimes
a
little
extra
information
might
be
helpful
to
them.
B
So
I
think
one
of
the
things
jen
and
I
have
done-
is
added
some
screenshots
to
a
couple
of
the
the
issues
that
might
not
normally
be
required,
but
we
thought
would
be
helpful
for
these
folks.
So
those
are
the
kinds
of
things
you
could
do
to
help
or
just
if
you
come
across
an
issue
without
that
tag,
but
that
would
be
a
good
first
issue.
Please
help
us
tag
that,
because
I
don't
know
I
mean
there's
several.
I
I
want
to
say
this
conference
has
like
30
000
participants.
B
I
don't
know
how
many
of
them
are
participating
in
this
sprint
day,
but
they
have
been
very
actively
tweeting
about
it
and
trying
to
recruit
people
to
work
specifically
on
backdrop.
And
so
it's
again
I
don't
I'm
making
up
numbers,
but
it
could
be
that
they
show
up
with
20
volunteers
to
write,
bull
requests
and
we
need
to
have
things
for
them
to
work
on
and
also,
if
you're
available
that
day,
just
to
pay
attention
to
the
issue.
Queue,
jen
and
nate,
and
I
and
gregory
are-
and
I
are
all
designated
reps.
B
So
we
will
be
like
in
slack
with
these
folks,
helping
them
out
and
answering
questions,
but.
B
They've
actually
set
up
a
special
slack
channel
just
for
their
their
event,
so
I
think
that's
where
they
want
people
to
be.
We
may
direct
them
to
zulu
up
as
well.
I
don't
know,
but
certainly
you
know,
it
would
be
great
if
people
were
available
like
to
review
their
work
quickly
that
day
in
the
issue
queue
because,
as
I
said,
you
know
my
goal,
I'm
hopeful
that
it
would
be
great
if
we
could
get
one
or
two
of
them
that
it's
it's
not.
For
me.
It's
not
so
much
about
the
work.
B
That's
going
to
get
done
that
day,
but
the
possibility
of
maybe
somebody
enjoying
working
with
us
and
coming
back
and
helping
us
in
the
future
and
that's
more
likely
if
they
have
a
good
experience
next
thursday.
So
to
the
extent
that
we
can
like
respond
to
their
questions
and-
and
you
know,
review
their
work
and
give
them
feedback
quickly.
I
think
we'll
say
a
lot
about
their
likelihood
of
coming
back
and
helping
us
in
the
future
yeah.
G
Yep,
okay
sounds
great
anything
else.
D
C
C
So
that
explains
why
I'm
so
prompt
so
anyways
I'll
have
a
slack
and
zulu
open
while
we're
doing
that,
but
our
meetings
are
going
to
be
one
or
two
hours
right.
This
whole
thing
is
an
event
that
is
happening
throughout
the
day,
so
we
might
go.
G
B
Yeah
that
might
work
the
problem
is,
I
just
have
no
idea
how
this
day
is
going
to
go,
and
I
have
mentored
at
at
large
sprints
before
at
drupalcon,
and
I'm
I'm
envisioning
a
situation
where
it
could
be
gregory
that
we
are
like
deep
in
helping
them
with
issues,
and
we
can't
say:
oh
we're,
going
to
go
away
for
a
meeting.
So
we
should
not
even
for
an.
C
B
G
Yeah
I,
if
it
comes
down
to
teaching
new
contributors,
are
having
their
discussion
about
118
features.
I
would
take
the
contributors,
and
so,
if
we're
in
a
zoom.
A
G
B
Yeah,
so
I
think
that's
fair,
that
that
would
be
fair
to
go
ahead
and
do
it
next
week
and
then,
if
some
of
us
aren't
there
to
either
just
follow
that
up
later
or
something
and
yeah
yeah
and
to
be
honest,
I'm
gonna
have
plenty
of
opportunities
to
give
my
input.
Even
if
I'm
not
there
so
I'll,
find
ways.