►
From YouTube: Backdrop Weekly - Nov 21, 2019
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).
B
A
B
B
These
are
all
rather
old
at
this
point,
but
there
are
lots
of
new
Mazal
ports
in
progress.
I've
been
working
on
a
couple
of
sites
this
past
week,
I
notice,
there's
a
bunch
of
other
people
creating
a
bunch
of
new
stuff,
so
I
just
want
to
say
thank
you.
All
people
are
doing
all
of
the
work
and
contribute.
We
don't
have
any
new
releases
this
week,
but
there's
a
bunch
of
work
happening
nonetheless,
for
our
web
sites
backed
up
CMS
org,
the
forum
and
the
API
site.
B
We
have
been
sprinting
this
week
on
solving
a
bunch
of
issues
on
those
sites
around
visual
things.
Functionality,
changes,
features
that
we're
missing
it
or
intended,
but
never
got
implemented
and
there's
been
a
whole
bunch
of
work
happening
there.
So
I
want
to
thank
everybody.
That's
working
on
the
websites.
Also,
we
had
a
kickoff
sprint.
Last
Sunday
we're
gonna
have
another
kick-off
sprint
there.
Another
wrap-ups
I,
don't
know,
maybe
keep
going
sprint.
B
This
Sunday
and
there's
been
a
bunch
of
work
happening
between
those
two
events,
so
thank
you,
Tim
for
organizing
this
I
think
it's
definitely
something
that
it
has
been
needed
for
a
while
and
it's
great
to
see
a
lot
of
these
issues.
Getting
attention
you
want
to
join
in
everybody
is
welcome
to
pitch
in.
There
are
issue
queues
and
under
the
organization
backdrops
that
have
all
the
stuff
for
all
the
sites,
and
if
you
wanted
to
priority
what
to
work
on
top
and
get
her
chat
with
people,
I
would
say
it's
repetitious.
B
Alright.
Moving
on
to
backdrop,
the
product
meat
is
usually
here
for
this
weekly
meaning
it
can
run
through
the
issues
in
core
that
are
getting
worked
on.
I,
don't
know
where
he
yesterday
so
I'm
gonna.
Do
it,
but
I
have
not
looked
at
the
status
of
all
these
issues.
Apologize
I'm,
not
necessarily
up
to
speed
on
where
they
all
are.
So,
let's
start
with
B
114
to
release.
B
C
B
We
also
have
the
flexible
templates
follow-up
issues,
there's
a
meta
for
0
for
6.
A
lot
of
those
are
getting
attention,
I
think
one
of
them
we
just
talked
about
in
our
user
experience
meeting.
We
finally
got
consensus
on
language
to
use
for
the
options
for
how
your
rows
should
behave,
so
that
will
get
a
little
bump
forward,
but
there's
a
bunch
of
circle
o
hanging
fruit
in
there
that
I
think
we
could
probably
get
started
out
by
1/15.
B
B
A
lot
of
them
are
bugs
that
have
pull
requests,
because
any
bug
that
has
a
forward
press
can
be
slotted
for
the
next
milestone
and
I
would
love
it
if
we
could
make
an
effort
to
go
through
and
do
a
bunch
of
reviewing
hat,
we
mostly
meaning
myself,
I'm,
not
great
at
doing
reviewing
the
elaborating
code
and
not
reading
it,
but
this
time
I
want
to
go
through.
It
spend
some
time
doing
a
bunch
of
testing
on
all
the
quests
that
are
already
in
there.
B
B
Adjusted
so
that
they
can
be
committed
and
get
the
get,
those
bug
fixes
for
assault,
more
exciting
insight
fixes.
We
have
a
bunch
of
new
features
scheduled
for
the
115
release,
and
a
lot
of
these
have
been
getting
attention
since
our
weekly
meetings
highlight
them.
We
now
have
advocates
letting
us
know
how
it's
going,
each
of
them
tap
on
here,
adding
an
image
library,
modal
for
image
fields,
number
32
97.
B
That
issue
I
think
has
some
progress
this
week
from
Graham
worked
on
getting
a
search
box
edits
the
modal,
so
you
can
type
in
like
the
name
of
your
file
and
try
and
find
it
that
way,
but
there's
a
problem
with
the
way
the
JavaScript
is
acting
on
the
page
there
that
we
need
to
get
resolved
there's
also.
Some
feedback
in
the
issue
was
originally
developed
without
using
modal's,
and
so
there's
some
feedback
there
to
make
it
use
modal's
and
that's
a
little
tricky.
B
B
The
next
issue
Auto
menu
settings-
this
is
number
16
10-
is
had
an
update.
Today
there
was
a
pull
request
that
I
filed
recently
that
had
some
commits
from
some
other
issue.
I
was
working
on
in
it,
so
I
made
kind
of
a
mess
of
things
and
VW
panda
went
and
cleaned
up
after
me.
So
thank
you.
Peter
fixing
my
poll
request
and
so
now
there's
new
pour
request
there
that
needs
review.
B
So
if
someone
wants
to
go
test
that
sandbox
I
think
this
poll
request
in
particular
it's
very
close
to
being
done,
it's
pretty
straightforward
and
simple,
and
if
we
can
get
in
a
little
free
up
computer
to
focus
on
other
core
issues,
if
you
would
like
to
dedicate
this
next
is
adding
a
recent
news
box
to
the
dashboard.
This
is
number
thirty.
Five,
sixty
six
I'm,
not
sure
if
you've
looked
at
this
recent
LinkedIn,
but
last
I
remember,
is
that
we
needed
an
update
to
the
news.
Jason
module.
Is
that
still
the
case?
A
B
C
Same
abate
as
before,
so
we
got
it
pretty
close,
it
was
breaking
other
things.
So
what
has
proposed
a
solution
that
seems
less
intrusive
and
it
will
that's
less
things,
so
it's
less
likely
to
break
things.
We
just
need
to
revise
the
pull
request.
It's
just
that
I've
been
focusing
on
bug
fixes,
but
since
the
December
is
upon
us
and
close
to
the
115
release,
I
will
start
working
on
that
as
well.
I
I
believe
the
first
week
of
December
I
should
be
able
to
start
working
on
it.
B
B
Nate,
isn't
around
this
week
to
give
us
an
update
on
that
one,
but
I
know
that
he
did
a
bunch
of
work
on
it
last
week.
So
I
would
assume
that
you
can
watch
last
night's
video
for
that.
Update
and
I.
Don't
know
anything
happen
this
week,
but
we
can
check
issue
1982,
I,
not
believe
it
yep
all
right.
Next
up
is
entity
cash
in
core
issue,
number
74,
Joseph
I,
don't
know
if
you're
here
anymore,
I.
B
Haven't
checked
on
that
one
recently,
I
don't
know.
What's
going
on,
but
I'm
pretty
sure
we
ran
into
some
problem
with
meeting
like
some
kind
of
an
entity
create
hook,
because
there
was
an
action
they
needed
to
fire
every
time
an
entity
was
created
and
I
believe
we
decided
to
support
all
the
core
entities
out
of
the
box
and
allow
can't
rip
entities
to
add
that
support
for
that
at
the
time.
But
I'm
not
sure
if
we
have
a
new
poll
request
for
that,
yes
or
not,
we
can
check
yeah.
C
B
The
next
issue
number
14
75,
and
this
is
about
changing
the
way
our
workflow
states
work,
sort
of
behind
the
scenes,
change
that
will
change.
These
are
interface
very
little,
but
that
will
make
the
system
make
a
little
bit
more
sense
so
that
in
the
future,
King
trip
can
have
useful
workflow
states.
So
things
like
having
an
unpublished
revision,
that's
in
draft
state
is
something
that's
really
hard
to
do
right
now,
either
the
note
is
published
or
not,
and
there
is
either
a
revision
or
not,
but
their
revisions
themselves
are
not
published.
B
C
B
Okay,
so
that
other
issue,
the
step
enemies
issue,
was
affixed
that
has
been
committed
to
115
branch
already.
I
ran
into
some
other
problems
that
also
needed
that
fix
this
week.
So
perfect
30
fix
that's
great,
so
that's
fantastic
that
that
makes
workflow
states
work
better
too
I
was
wondering
how
chuckle
not
arrived
at
that
one
great,
the
whole
history
of
it,
but
that's
great
so
I
wanted
to
say
that
that
purpose
probably
needs
updating,
but
thank
you
stuff,
Wilmont
for
doing
all
of
the
amazing
work
on
fixing
the
hard
problems
in
backdraft.
C
B
C
B
I
looked
in,
my
watch,
I
was
working
on
and
it
did
look
like
I
could
call
entity
create
directly
instead
of
creating
a
stuff
entity,
you
can
create
a
whole
entity,
but
I
didn't
know
if
that
was
gonna,
have
any
implications
that
we
didn't
want.
I,
don't
know
if
creating
an
entity
and
not
saving,
it
might
actually
end
up
saving
something
I,
don't
know,
but
it
would
be
interesting
to
see
what
the
recommended
alternative
is
about.
B
The
proposal
is
to
mark
that
function
is
deprecated,
which
means
that
kinship
shouldn't
use
it
anymore,
and
even
though
right
now
there
isn't
much
of
a
core
that
uses
it.
It's
used
pretty
heavily
in
contribs,
so
trying
to
figure
out
what
a
control
should
do.
Instead,
I
think
it's
very
important,
Mike
and
Tripp
module
use
it
in
two
different
places.
One
of
them
was
to
create
a
node
entity
which
is
fine,
because
I
can
entity
create
a
node,
but
another
one
was
to
create
a
fake
entity
and
it
didn't
actually
need
an
entity.
B
It
just
needed
an
object
to
manipulate,
and
so
in
that
case
my
module
wouldn't
work
at
all,
because
there
is
no
class
for
it
to
instantiate
when
it
creates
the
thing.
So
I
ended
up
having
to
create
a
fake
class.
So
there's
now
a
class
in
my
module
called
pseudo
entity,
it
is
actually
an
entity
that
I
now
have
to
instantiate
instead
of
using
that
function.
So
it
just
seemed
a
little
weird
that,
like
maybe
every
control
would
have
to
provide
a
pseudo
class,
and
do
we
really
want
every
like?
B
Do
you
really
want
800
different
pseudo
classes?
If
the
only
purpose
is
just
to
be
a
placeholder
for
something
so
I,
don't
know
if
I'm
misunderstanding,
the
alternative
to
what
that
function
should
do
or
not
so
yeah,
maybe
give
you
a
deeper
dive
into
what
the
what
we
should
be
doing
instead
in
kinship
would
be
good,
maybe
with
some
example.
So
maybe
I'll
I'll
keep
an
eye
out
for
that
on
any
of
the
other
projects.
I'm
working
on
and
see
what's
necessary,
but
it
seems
complicated.
B
Ok,
so
that
is
it
for
the
115
queue.
I
was
just
thinking
today
that
it's
probably
time
to
open
a
new
PMC
issue
and
just
get
know.
We
have
a
ton
of
stuff
in
this
115
queue.
Originally,
there
were
like
four
items,
just
be
like
hey.
This
is
we're
going
for
115
any
objections.
Yes,
no,
our
normal
I
can't
see
project
vision
and
oversight
thing
and
make
sure
that
we
are
doing
everything
we're
supposed
to
be
doing
and
nothing
we're
not
moving.
So
we'll
do
that
too,
but
that's
it
can.
A
A
B
In
it's
in
the
PNC's
responsibilities
to
be
able
to
guide
the
direction
of
the
project,
and
so
we
wanted
to
make
sure
that
we're
focusing
on
things
that
are
important
for
backdrop
as
a
whole,
rather
than
things
that
may
be
important
to
one
of
us
for
one
or
take
another
reason,
and
so
just
having
a
ton
of
people
look
at
the
list
of
the
changes
we're
going
in
and
go
yeah.
Those
are
all
fine,
I
think
is
good
precaution.
B
B
A
C
A
David,
what
I
explained
to
them
was
that
you
that
you
were
looking
for
a
database
credentials
to
facilitate
just
import
process
into
the
Heroku
app.
What
I
heard
from
them
was
that
unless
you
have
access
to
the
server
that
doesn't
do
you
any
good,
that's
I,
don't
quite
a
camera!
There's
all
that
yeah.
B
I
also
not
entirely
sure
how
Roku
works
or
even
how
that
whatever
database
system
were
using
Redis
or
something
I,
don't
know
for
for
this
tool
works
like
maybe
it
is
intended
to
only
ever
be
accessed
from
a
different
server
and
has
some
connection
process,
but
I'm
pretty
sure
that
our
current
database
is
not
set
up
that
way
because
it
was
accessed
from
the
student
server
on
which
the
code
was
running,
and
so
we
probably
don't
have
any
ports
open.
That
would
allow
that,
so
there
isn't
any
way
that
anything.
B
A
B
B
A
B
C
C
A
C
Point
was
that
all
the
databases
are
currently
set
up
to
be
accessed
only
locally,
so
lieutenant.
For
example,
we
remotely
access
the
database
from
different
work
right,
so
when
I
would
go,
how
I
would
go
about
it
is
I
would
get
the
rest
to
be
done.
Would
it
temporarily
excuse
me,
could
it
temporarily
somewhere,
where
it's
publicly
accessible
accessible,
then
point
Orrico
to
it
that
it
the
data
and
then
the.
C
B
A
B
A
Gonna,
just
throw
out
I
mean
once
we
get
this
working.
There
are
issues
like
with
dinner,
using
maybe
more
than
one
channel
I,
don't
know
if
it's
been
a
successful
experiment
this
week,
but
one
thing
that
would
help
it
is
if
the
bot
work
the
board
one
channel
like
right
now
the
bot
doesn't
work
in
both
so
but
once
you've
got
this
move,
we
can
at
least
explore
that
as
an
option
and
also
one
I
mean
I.
A
Think
the
main
things
that
are
in
the
database
is
is
our
current
karma
and
I
would
like
to
open
a
discussion
about
maybe
like
resetting
the
karma
every
once
in
a
while.
So
I
don't
know,
I,
don't
know
how
much
we
want
to
talk
about
this
depart.
There's
a
part
of
me
that
it's
like
you
know
that
karma
after
a
while.
You
know
that
somebody
new
it's
like
it's
meaningless,
because
my.
C
B
D
B
B
C
Started
I
started
writing
a
pull
request
and
he
got
myself
into
a
rabbit
hole,
because
what
I
saw
was
that
so
my
intention
was
to
start
doing
what
people
think
it's
correct
as
in
they
do
it
indeed
work
as
well.
They
file
a
pull
request
with
a
test
that
fails
first
intentionally
and
then
they
fix
so
they
have
a
failing
test.
I
started
fixing
I
started
with
a
pull
request
that
is
pitching
there
with
me.
C
B
This
is
actually
in
core,
so
rather
than
putting
like
a
DP
m
or
DSN
or
whatever,
where
you
want
to
see
the
message
he's
debug
instead
and
it'll,
basically
give
you
the
same
output
instead
I'll,
but
it's
not
like
collapsed
into
a
beautiful
click
through
like
expand
ething
it
just
like
blah
dumps
all
of
its
stuff
out
on
the
page,
but
it's
really
helpful.
I
use
it
all
the
time.
Fantastic.
C
B
B
C
Right:
okay,
cool
yeah:
it's
just
that
some
are
a
das
that
I
will
create
once
I
fix
this
bit
the
consistency
in
the
tests,
then
I'll
I'll
just
make
sure
that
I
create
this.
The
tests
all
three
types
of
numbers
and
make
sure
that
they
fail
because
that's
what
they
do
like
leaving
the
field
NP
and
then
try
to
fix
it
and
I
have
an
idea.
How.
B
C
So
I
found
out
this
was
fine
is
one.
This
is
why
I
say
I
have
a
feeling
how
it
would
be
fixed.
So
the
specific
cook
implementation
for
number
four
number
is
empty,
or
something
like
that,
whatever
it's
called
was
the
same
as
cookies,
empty
yeah,
so
I
started
thinking.
Why,
but
maybe
didn't
make
sense,
maybe
we're
missing
a
use
case
there.
This
is
probably
happening,
yeah
yeah
and
it's
drupal.org,
and
they
don't
have
any
such
issues.
Fault
on
a
different
test
with
Drupal
actually
verifies.
B
We
had
this
number
field
in
Drupal,
7
and
I.
Don't
think
it
was
a
problem.
I
think
it
only
became
a
problem
change
to
the
html5
development,
so
that
might
be
a
Drupal
8
thing,
I'm,
not
sure.
If
it's
an
issue
there
or
not-
but
if
it
is,
it
probably
won't
have
a
comparable
fix
just
because
the
field
system
is
so
different.
Yes,.