►
From YouTube: Backdrop Weekly - July 25th
Description
Today’s development agenda: http://bit.ly/2YZ6XEL
A
All
right
we're
on
air
today
is
Thursday
July
25th,
and
this
meeting
is
to
check
in
on
active
development
tasks
for
doctype
CMS,
first
and
most
exciting
announcement.
Is
that
backdrop
past
1000
live
reporting
backdrop
sites
I'm,
not
sure
when
it
was
looks
like
July
13th
I
want
to
put
this
screenshot
at
the
top
of
the
agenda
because
it's
exciting.
A
So
that's
great,
it
looks
like
we're
1020
right
now.
Oh
yeah,
you
are
you
thinking,
it's
great
I'm,
also
very
exciting.
In
our
community
we
have
new
contributors.
There
are
three
people
who
have
applications
there
since
last
time,
I
looked
I,
don't
know
rigor.
If
you
guys
covered
some
of
these
in
the
last
meeting,
but
yeah.
B
A
That's
great
and
then
there's
two
other
people
with
maintain
an
application
supported
over
Drupal
modules
that
are
also
waiting,
so
I
find
that
very
exciting
I
mean
Drupal
people
porting
their
own
stuff.
That's
also
really
great
in
the
creation
of
new
projects.
These
are
lots
of
official
releases.
This
week
we
have
three
black
background
color,
which
is
the
one
that
Nitesh
worked
on:
texana
meatiest
CSV
import,
export,
something
I've
actually
used
a
lot
in
Drupal
and
charts,
which
I
think
me.
It's
a
module
that
you
made
initially.
C
D
C
Oh
yeah,
it's
been
what,
like
three
weeks
a
month,
I,
don't
know
it's
been
a
long
time
since
I've
been
on
a
meeting.
I've
been
traveling
a
lot,
so
apologize
for
things
that
I
might
be
repeating
or
covering
in
the
past
couple
of
meetings.
So,
let's
see
one
thirteen
point.
Three
will
be
the
next
bug
fix
release.
We
don't
have
any
expected
release
date
on
it.
C
B
B
So
we
changed
the
operation
from
edit
to
update
oops
and
we
did
have
a
wrapper
that
was
normalizing
that
thing,
but
for
some
reason
it
didn't
kick
in
and
we
can
follow
that
up.
While
it
didn't
happen
and
there's
also
a
block
comment
that
says,
the
way
that
comments
are
meant
to
be
working
is
that
if
someone
replies
to
a
comment,
then
you
cannot
edit
it.
B
But
that's
that's
what
the
doc
block
says,
and
maybe
it's
inherited
from
like
d6
or
previous
versions
of
Drupal,
but
people
that
have
tested
it
say
that
it
doesn't
work
that
way.
Nevertheless,
that's
not
the
scope
of
the
issue
we
just
mentioned,
so
it
can
be
a
follow
up.
The
immediate
problem
is
fixed
by
a
single
line
thing.
Oh,
that's.
C
B
So
it's
issue
three
nine
four,
eight
missing
edit
link
from
for
comments.
C
B
C
C
We
have
two
different
pull
requests,
one
from
back
home
latin
one
from
jen
has
tests,
but
one
of
the
tests
is
not
testing
everything
quite
appropriately,
but
it's
passing
and
the
other
one
tests
everything
appropriately,
but
it
has
three
exceptions
and
so
still
working
on
getting
the
tests
sorted
out
on
that
issue.
Although
the
functionality
it
seems
like
everybody's,
agreed
that
what
we
have
this
is
working.
C
Let's
see
it
looks
like
this
issue.
37
sixty
two
currently
meets
review.
Gregory
thanks
for
your
work
on
this
and
herb
dual
working
on
tag-teaming
back
and
forth,
to
figure
that
one
out,
let's
see,
we
have
a
number
of
issues
as
the
views
module
both
in
Drupal,
7
and
Drupal.
8
has
been
receiving
fixes,
but
in
particular
keeping
up
with
the
Drupal
7
module
is
a
much
more
attainable
thing
for
us
and
so
Gregory.
You
opened
up
issue
36
85,
that
is
keeping
on
track
with
changes
to
the
triple
17
triple
looks
like
so.
B
This
has
become,
it
has
become
a
meta
issues
of
a
thing.
I've
done
the
first
two
steps
like
37,
19
and
37
20,
and
not
all
of
the
requests,
the
sorry
the
commits,
maybe
like
ninety
nine
ninety-five
percent
of
them.
It's
just
I
gotten
to
a
point
where,
if
I
take
a
boil,
I
will
have
conflicts
with
the
rest
of
that
for
requests
so
I.
Some.
Some
of
these
need
to
be
most
so.
C
A
B
C
B
C
C
B
C
C
Okay,
so,
let's
see,
we've
got
the
different
issues,
as
we've
been
doing
the
advocates
for
each
issue
we'll
talk
about
their
issue.
If
they
have
anything
any
updates
that
have
been
happening,
the
one
that
I've
been
covering
is
digital
signatures
on
packages.
Probably
automatic
updates
initiative
is
shooting
1992
I
I
wish
I
had
more
status
updates
on
this,
but
I
don't
have
anything.
We're
currently
still
working
I'm
working
on
getting
updates
into
project
module
to
make
it
so
that
the
project
XML
feeds
start
having
signatures
in
them.
A
C
C
Take
a
look
in
the
now
if
the
court
issue
queue,
but
the
project
module
issue
queue
where
there's
pending
work,
that
John
Franklin
has
been
filing
merge
requests
like
pull,
requests
everything
and
that's
where
we're
trying
working,
let's
see
before
I,
give
up
the
microphone
there's
been
from
the
Gator
chat.
Log
dark
moment
also
wants
to
mention
that
the
flexible
layouts
functionality
that
he's
been
working
on
also
could
use.
Oh
it
sounded
they're.
C
B
B
Worries
no
worries:
thanks,
I'll
get
the
trusted
host
patterns
out
of
the
way,
because
it's
a
smaller
one.
So
that's
issue
2568.
It's
been
waiting
for
code
review
and
testing
for
some
time,
but
unfortunately
the
testing
cannot
be
done
in
the
pr
unboxers,
because
people
need
to
add
those
things
in
their
settings
PHP
file,
so
it
has
to
be
done
under
local
I've
tested
it
on.
B
My
local
I
think
that
I've
covered
most
of
the
cases
and
the
way
that
it's
implemented
is
that
we
do
not
stop
the
Installer
and
we
do
not
throw
a
white
screen
at
people
if
they
haven't
said
it.
So
it's
an
opt-in
thing.
People
can
use
it
if
they
want
we'll
just
ignore
the
warning
and
we
don't
throw
an
error.
We
throw
a
warning
instead.
B
E
B
E
B
She
doesn't
explain
it
in
words,
but
if
you
see
the
code
setting
speeds
because
whatever
you
need
so
there's
a
there's,
a
documentation
in
added
in
the
settings
block,
P,
symbol,
ads
I'll,
add
some
comments
so
that
it
we
can
test
it
more
easily.
Okay,
yeah
all
right
cool.
So
next
issue
is
37:55,
the
one
that
dr.
Lamott
has
been
working
on
and
he's
brought.
B
His
will
request
him
to
a
status
where
we've
tested
it
and
we
all
like
it
and
we're
all
excited
about
it,
but
he
needs
technical
sort
of
like
guidance
and
safety
implementation
that
his
father
is
correct
and
so
yeah.
I
think
that
this
is
a
job
from
for
one
of
the
core
committers
nate
or
curve
the
war
death.
Perhaps
so
that's
what
we
stack
at
this
point.
C
Yeah
I
mean
sounds
like
it
is.
What
it
is
you
know
like.
We
need
somebody
do
the
reviewing,
whether
that's
a
cork
emitter
or
somebody
else
like
yeah
I'd
like
to
say,
oh
I'll,
think
look
at
that
right
away,
but
I
don't
want
to
add
too
much.
You
know
commitment
that
I
will
fail
to
follow
through
on
so
time.
I.
Look
at
it.
I.
A
B
E
We
did
I'm
unmuted
nothing's
happened
since
last
week.
Basically,
there's
some
we're
waiting
on
getting
the
JSON
feed
configured
on
back
rapid
org
and
some
decisions
have
to
be
made.
I
just
posted
the
link
to
where
Jeff
has
asked
some
questions,
I
think
it's
really
a
matter
of
making
some
decisions
about
my
kind
of
nickname.
Some
things
like
I
have
to
go
back
and
review
it.
It's
been
over
a
week
since
I
looked
at
it.
E
I
was,
after
the
last
meeting,
just
going
to
do
some
more
research,
because
I
don't
have
strong
opinions
on
this,
but
to
see
what,
if
I
could
do
some
research
and
see
what
other
people
are
doing,
but
but
really
it's
just
a
matter
of
making
some
decisions.
So
those
were
the
opinions
on
this
need
to
weigh
in
it's
like
on
how
to
name
me,
the
the
URLs
and
stuff
like
she
can
use,
slash
api
or
slash
json,
or
things
like
that,
and
once
we
make
those
decisions,
I
think
we
can
wrap
this
up.
E
A
A
And
it
looks
like
that's
the
end
of
the
things
that
are
tagged
for
one
14-0,
but
there
is
one
ongoing
item
we
want
to
keep
our
eye
on
and
that
is
updating
seek
editor
to
the
next
version
it
looks
like
there
is.
The
next
minor
version
has
very
few
changes
between
what
we
have
now,
and
so,
if
we
can
get
our
working
or
request
up
for
that,
it
could
go
into
114
yep.
B
C
B
B
C
A
A
Just
think
it
would
be
good
to
figure
out
what
the
current
pain
points
are
for
people
who
want
to
be
maintained
errs.
Then
people
want
to
know
what
those
are.
We
can
point
to
some
idea
of
what
better
process
might
be.
I
think
one
thing
we
should
do
that'll
definitely
help
with
getting
those
templates
up,
because
once
we
have
the
templates
up,
it'll
prevent
people
from
creating
issues
that
are
incomplete,
where
you
need
to
follow
up
and
ask
them
for
additional
things,
but
yeah
beyond
that.
B
E
E
Okay,
the
other
advantage
in
this.
We,
a
distinction
or
thing
with
with
a
webform-
is
that
we
could
ask
like
contact
information,
other
things
that
we
wouldn't
necessarily
just
put
in
to
get
it
github,
which
I
don't
know
if
we
want
to
or
need
to,
but
right
now
we
don't
have
anything
to
do
with
that.
But
if
we
got
the
right.
A
A
Now
panicky,
we
can't
just
ask
them
for
a
name
and
they
still
have
to
want
their
code
on
getting
it
just
because
we
have
their
user
name,
doesn't
prevent
them
from
meaning
to
use
github
like
that's
where
the
code
lives.
They
have
to
put
the
code
there
for
a
code
review.
We
have
to
maintain
the
module
there.
No.
E
That's
the
issue
to
me
that,
though,
there's
one
steps,
step
of
creating
an
issue
in
github
to
say:
hey
I,
want
to
become
a
maintainer,
that's
kind
of
you
and
you're
saying
we're
gonna,
replace
that
with
a
template.
So
a
better
template
would
definitely
help
that
it
might
reduce
the
need.
We
don't
have
that
template
today
so
compared
to
our
process
today,
a
web
form
would
be
better
because
it
I
know
what
I
need
to
fill
out.
That's
right!
No.
E
That's
not
the
part
that
I'm
complaining
but
I
understand.
You'd
have
to
do
that.
I
understand.
York
I
have
to
do
that,
no
matter
what
but
there's
another
part
right
which
we're
trying
to
fix.
Then
the
other
part
is
the
part
where
I
just
post
a
message.
In
this
backdrop,
contribute
saying:
hey
I
want
to
become
a
maintainer.
A
E
C
A
C
Process,
you
know,
even
even
if
they
have
to
do
something
on
github,
and
that
is
part
of
web
form
that
they
fill
out
like
saying
you
know,
check
the
box,
I
have
created
an
issue
or
I
have
pushed
stuff
up
to
github,
and
so
that
way
like
it
provides
a
path
for
people
to
follow,
even
though
it
might
not
actually
provide
any
new
data.
You
know
it
would
just
be
like
a
step
for
them
to
like
it
would
be
a
guide,
essentially
yeah.
C
A
E
A
B
C
B
A
Yeah,
the
part
of
the
part
of
the
whole
isn't
like
you
wanna
beyond
get
harvest,
because
people
don't
need
to
have
anything
to
do
with
blackjack
semester,
art
you
know
in
teenage
their
code,
so
I
think
it
should
be
a
requirement.
I
mean
I.
Think
if
we
I
think
it
would
be
good
to
take
everybody
who
wants
to
have
an
account
and
manage
them
through
seduce
around
in
the
same
way,
but
I.
Don't
think
that
should
be
a
blocker.
Maybe.
B
C
E
B
A
C
A
So
what
our
next
steps
with
this?
Well,
someone
in
that
issue
write
down
like
problems
with
all
the
problems
people
face
so
that
we
can
address
them.
I
totally
agree:
the
readme
file
needs
to
be
cleaned
up,
I
think
we
put
over
the
checklist.
That
would
be
great
anything
else.
We
run
into
issues,
would
pain,
points,
sticking
points,
let's
write
them
down,
so
we
can
try
and
figure
out
yeah
I.
B
A
Already
have
an
issue
that
includes
like
three
possible
templates:
I
mean
they're,
not
written,
it
just
says
like
we
have
one
who's,
a
maintainer
application
one.
It
was
our
request,
one
that
looks
like
a
notification
thing.
Oh
look
at
that
I.
Don't
remember,
I
think
there
was
an
issue
but
I,
like
your
shirt.
C
C
C
A
Like
just
because
people
want
to
know
how
this
is
computed,
sending
them
to
a
file
full
of
code
and
telling
them
to
figure
out
isn't
super
helpful.
I
was
just
wondering
if
there
was
like
a
document.
I
don't
have
anything
like,
maybe
in
project
modules.
Readme
that
says
like
we
track
X
sites
when
this
happens,
counting
IP
addresses,
but
only
I,
don't
know
if
it's
like
in
human
words
rather
than
in
code
I.
Don't.
C
C
So
in
the
effort
of
like
answering
this
question,
like
just
herbally
I
know,
it'd
be
better
to
have
it,
but
no
wait.
There's
a
riparian
project
release.
Oh
this
project
released
out,
not
usage
yeah!
Oh
oh
I'm,
getting
things
mixed
up,
so
I
project
release
sort
of
history.
This
is
actually
the
file
that
doesn't
I
believe.
C
C
C
This
is
like
your
kind
of
unique
identifier,
but
then
the
fact
that
you've
checks
for
updates
gets
put
into
this
table,
project
usage,
raw
and
then
on
cron
jobs,
cross
project
usage
runs
this
PHP
file
and
this
pull
stuff
out
of
project
usage
raw
that
table
and
then
puts
into
the
final
project
usage
tables,
including
the
daily
chair
at
the
day
table
and
the
weekly
table
and
the
yeah
I
guess
this
is
daily
okay.
So
the
question.
A
Is
how
is
it
counted
right
like
and
I
think
I
heard
you
say
this
before
Nate,
where
it
was
like.
It
only
counts
a
site
if
it
reports
two
weeks
in
a
row
and
it
won't
count
multiple
copies
of
the
same
site.
Key.
C
C
C
C
A
C
A
E
A
We
have
to
find
it
yes
and
be
like
I
think
it
just
fits
and
I
know
does
this
and
it
might
do
this,
so
it
would
be
good
to
have
somebody
like
we're
doing
right
now,
read
through
the
file
and
see,
if
you
see
anything
specific,
that's
notable
and
then
put
it
into
like
either
the
readme
file
in
the
project
mother,
to
make
a
good
blog
post
and
especially
like
how
this
is
different
from
how
Drupal
counts.
Perfect
usage
might
also
be
interesting.
Well,.
E
I
agree:
I
mean
it
came
up
this
week
because
we
crossed
over
a
thousand
and
people
are
curious.
What
that
means?
Also
there's
always
this
volatility
right,
which
I
understand
that
there's
going
to
be
some
volatility
but
sort
of
it's
a
lot,
just
curiosity
understanding
how
that
works.
You
know
somebody
made
a
joke
or
maybe
they
weren't
about
like.
C
B
A
Something
different
like
Drupal
Tech
counts
all
of
the
sites
that
are
running
tests
so
like
when
you
where,
in
the
test
suite
you
like,
install
a
bunch
of
different
times
backdrop
doesn't
like
we
change
the
way
our
test
thing
work,
so
that
it
doesn't
actually
ping
our
outside
server
for
any
test
instance.
So,
I
I,
don't
know
how
that
like
translates
into
direct
number
differences,
but
I
would
imagine
it's
fairly
substantial.