►
From YouTube: Backdrop Weekly Dec 28th
Description
Today’s development agenda: http://bit.ly/2p81WfD
A
Hey
we're
on
here
I
mean
everybody
happy
Thursday,
December
28th.
This
is
a
meeting
to
talk
about
vector
of
CMS
development
tasks.
In
the
past
week,
we've
had
three
releases
for
contributes
image,
URL
formatter,
there's
a
little
discussion
about
whether
that
should
go
and
core
or
not
but
exists
and
contribute
for
people
who
need
it
now.
It's
now
available
meta
tag
had
a
new
release
that
included
some
fixes
to
the
Facebook
Open
Graph
tags
and
the
Twitter
card
stuff,
so
that
should
work
a
little
better
and
there's
gonna
be
another
release.
A
A
Know
like
nope
I
can't
find
out
real
quick
anyway.
There's
some
entre
contacts
you
can
check
out.
I
know
what
it
does.
It
needs
a
better
formatted
readme
before
it.
Well,
no,
but
yeah
it's
great
that
even
during
the
holidays,
people
are
busy
making
backdrop
stuff.
So
thank
you,
everybody
for
making
backdrop
stuff
for
the
website.
There
was
a
bunch
of
activity
going
on
a
doctor
of
CMS
org.
As
we
mentioned
last
week,
there's
new
footer
and
a
new
drop-down
menu.
A
The
try
backdrop
page
Jeff
is
made
for
us
I'm
going
to
test
it
out
again
today.
I
think
I
did
it
last
week,
but
it
didn't
get
merged.
So
I,
don't
remember
why
and
we're
also
working
on
adding
some
of
the
other
missing
design
elements
from
our
header
back
in
there.
I
just
stumbled
across
one
of
those
issues
today
too
and
I'll
take
another
look
at
that
and
see.
If
we
can't
get
a
little
closer,
the
forum
site
was
announced
via
a
newsletter
this
week.
A
You
guys
probably
all
got
that
and
there
seems
to
be
a
flurry
of
activity
going
on
there,
which
is
pretty
exciting.
We've
got
a
bunch
of
new
people
who
don't
usually
contribute
in
the
issue,
queue
or
participating
the
forum,
which
is
exactly
what
we
wanted,
because
these
are
people
who
might
not
github
accounts
but
still
have
questions
or
comments
about
backdraft.
A
There's
also
a
couple
of
questions
in
there
that
are
markets
frequently
asked
questions
which
is
great,
I'd
love
to
see
more
of
that.
So
if
anyone
else
is
in
there
as
a
logged
in
as
a
moderator,
if
you
see
something
that
you
think
is
a
common
question
that
you've
heard
a
bunch
of
time.
So
maybe
it's
the
first
time
in
the
forum,
it's
okay
to
talk
that
one
is
frequently
asked
question
I,
also
added
a
flag
called
archive.
A
A
B
B
See
here
so
backdrop,
one
point
eight
point:
one:
we
continue
to
have
a
set
of
cross
ports
that
are
pending
just
some
tiny
little
work
to
get
a
backdrop
up
to
date
with
bug
fixes
coming
into
Drupal
as
well.
Those
are
issues
2013
and
then
27,
74,
75
and
76.
So
all
of
those
still
just
a
couple
of
lingering
items
there
we'll
see
about
I'd
like
to
get
this
kind
of
knocked
out
so
that
we
could
release
one
point:
8.1
we're
not
actually
held
up
in
any
way
there,
but
still
gonna
put
that
out.
B
Let's
see,
there's
a
couple
of
other
items
that
we've
seen
some
recent
activity
on
and
some
requests
from
people
issued
28:45
that
you
cannot
delete
the
cloned
default
view.
So
if
you
copy
a
view
and
then
try
to
delete
the
copy,
it
doesn't
let
you
do
that
the
code
is
great,
but
the
tests
need
to
be
updated.
It
looks
like
so
issue.
2845
is
back
in
needs
a
little
bit
of
work.
B
Let's
see
deleting
a
node
should
not
validate
the
form.
This
is
like
one
of
those
things.
That's
kind
of
been
around
forever
that
when
you
delete
a
node
or
if
you
edit,
a
node
and
then
click
the
delete
button
it
there
is
validation
errors.
If
you
have
a
blank
title
or
something
like
that,
that's
issue
45
their
site.
2594
looks
like
this
has
been
reviewed
by
others,
which
is
great
I'll.
B
B
Those
are
the
items
for
one
point,
eight
point:
one
I
think
that
I'm
not
quite
sure
whether
or
not
we're
gonna
see
one
point,
eight
point,
one
before
the
release
of
one
point:
nine
or
not,
I've
been
thinking
about
cutting
one
January
first,
along
with
the
preview
release
for
one
point,
nine.
But
at
this
point
now
one
point:
nine
is
pretty
modest
in
its
future
outside
feature
set,
I,
don't
know,
I
probably
wouldn't
hurt
to
cut
one
anyway.
B
So
that's
it.
For
one
point,
eight
point,
one
one
point:
nine
we're
coming
right
up
on
future
freeze,
which
is
in
just
one
two
three
four
days:
January
first
and
I
know
you
know
it's
right
in
the
middle
of
the
holiday
season
and
I
had
some
optimism
going
into
holiday.
So
I
was
like.
Oh
this
be
great.
Everybody's
gonna
have
all
this
free
time.
Nope
turns
out,
we
went
on
holiday
and
that
is
just
a
okay.
That
is
what
all
it.
D
B
So
I
hope
everybody's
been
having
it
just
as
an
enjoyable
holiday
as
as
I
have,
which
has
been
really
pretty
great.
Let's
see
so,
let's
talk
about
one
point:
nine
items.
You
know
we
can
still
knock
out
some
of
these,
the
guys
in
particular
27
96,
the
ability
to
edit
an
existing
file.
This
one's
just
been
chilling
out
lacking
a
minor
terminology
change
and
an
upgrade
hook,
update
hook
to
edit
of
you
totally
manageable,
41.9
stove.
B
Let's
see
follow-ups
on
top
of
that
one.
The
ability
to
edit
our
site
upload
a
file
manually,
separate
about
any
Content
issue,
26:33
that
one
hasn't
seen
any
activity
recently
but
I,
don't
know
that
one
that
one
can
get
a
little
bit
involved.
We
might
be
able
to
knock
out
something
simple
and
elaborate
on
it
later,
possibly,
but
you
know
that
one
is
in
a
state
that
needs
some
work
and
then
field
about
files
is
issued.
B
26:32
again
a
has
a
very
promising
pull
request
there,
but
something
like
I,
don't
know
it's
pretty
unlikely
that
that
would
get
finished
in
the
next
couple
of
days.
We
also
have
the
possibility
here
of
getting
into
basic
functionality
and
then
making
sure
you
know
that
it's
completely
clean
over
the
first
two
weeks
of
January
but
I,
don't
like
to
you
know
completely
Russian
things
that
are.
B
Let's
see,
hang
on
there's
more
items,
yet
the
ability
to
show
and
hide
translated
note
links
is
issued.
2910
that
pull
request
has
been
reviewed
by
elders.
I
think
it
needs
review
by
a
committer,
but
that
one
seems
like
it
is
ready
to
go
for
the
most
part.
Let's
just
get
a
committee
review
on
that,
whether
it's
myself
or
Jeff
in
the
next
couple
of
days.
D
D
B
B
Okay,
yeah
I,
don't
think,
there's
any
updates
on
that,
but
it
is
great
that
we
that
we
have
a
start
on
a
polar
question.
We
have
an
outline
of
a
plan
in
the
issue
so
that
that
looks
like
it'll,
be
a
great
foundation
for
building
up
that
functionality
that
one,
even
once
we
decide
on
the
plan
and
actually
begin
to
execute
it.
B
It'll
take
a
fair
amount
of
effort
to
update
the
implementations,
they're,
not
core
of
strings
that
use
strings
that
are
in
configuration
that
use
T
right
now,
the
T
function
and
we'll
switch
them
over
to
the
new
method
that
we
build
out,
so
that
one
will
probably
need
to
yeah
start
early
on
in
a
release
cycle
and
then
try
to
get
through
all
the
conversions
during
that
cycle,
so
that
one's
got.
You
have
some
great
promise,
but
yeah
it
will
be
targeting
for
one
point.
Ten.
B
D
That's
basically,
the
purpose
is
a
lightweight
rabbit,
hole
for
nodes,
only
type
of
deal,
it's
pretty
simple
and
it
works,
and
my
main
motivation
for
it
is
it's
gonna
solve
the
issues
that
are
mentioned
in
the
issue.
Queue
such
that
we
can
use
content
like
interviews
like
for
a
slider
that
won't,
you
won't,
have
to
drill
down
to
a
page,
but
you
still
want
to
use
that
content
and
a
few
slider
or
in
a
block,
but
my
main
motivator
was.
B
E
A
A
If
the
problem
is
with
backdrop,
access
tonight
and
backdrop
not
found
if
those
functions
need
to
include
the
call
to
backdrops
the
title
instead
or
there's
some
reason
that
the
current
calls
to
set
the
title
aren't
working
because
of
our
menu
callback
functions
or
something,
but
it
would
be
less
than
five
minutes
to
get
the
kinship
module
working.
So
I
think
we
should
definitely
do
that
and
then
that
way
we
have
a
solution
for
anyone
in
control
who
needs
page
list
notes
and
it'll
give
us
a
little
more
time
to
review
the
pour
request.
A
D
A
This
is
probably
not
the
best
way
to
solve
this
problem.
Let's
figure
out
like
where
in
the
menu
system
we
need,
we
should
be
interrupting
instead
of
what
we
are
doing,
but
at
least
if
we
could
get
a
working
solution
of
that
module
out.
I
think
that
might
unblock
a
bunch
of
people,
so
I
would
still
start
there.
Okay,.
B
Great
yeah
I
feel
like
we
can
just
talk
ourselves
in
circles
on
on
this
item.
The
underlying,
maybe
not
underlying,
but
one
of
the
goals
that
Olaf
has
been
stressing,
is
that
core
itself
should
be
able
to
have
be
have
full
translation
functionality
or
internationalization
functionality
without
any
controls,
which,
I
think
is
a
an
admirable
goal
and
I
think
that's
how
this
got
brought
back
in
and
especially
under
the
translation
category.
B
B
Okay,
that's
it
for
the
1.9
summary
update.
We've
only
got
a
couple
of
days
left
in
2017,
thank
goodness
and
yeah
we're
gonna
head
right
into
the
new
year
with
the
1.9
release,
big
or
small.
It's
always
great
to
get
a
new
release
out
of
backdrop
and
so
yeah
2017.
It's
been
a
little
bit
of
a
rough
and
tumble
year,
but
backdrop
has
been
growing
throughout
it
and
so
okay,
congratulations
on
the
good
year
and
that's
it
for
the
status
updates
on
the
project
for
2017.
B
D
Excuse
me
this
yeah,
so
recently
I've
been
using
this
for
math
of
commit
messages
when
you
have
an
issue
queues,
it's
in
one
repo
in
law
and
the
commits
are
going
against
another
repo.
So
if
you
just
format
them
in
this
backdrop,
slash
backdrop
issues
issue
number,
then
it
will
link
up
the
the
PR
to
the
to
the
issue,
queue
where
the
issues
being
discussed.
So
for
okay
with
having
that
format
as
our
commit
message,
we'll
get
the
advantage
of
them
being
referenced
in
the
issue.
B
B
So
I
kind
of
think
for
that
reason
pursuing
this
might
be
a
good
idea.
I
think
my
only
hesitations
are
in
the
fact
that
it's
so
verbose,
you
know,
and
it's
a
change,
so
we
have
to
either
train
people
or
or
as
part
of
our
merge
process.
You
know
we
normally
squash
and
merge,
and
that
gives
us
the
opportunity
to
rewrite
the
commit
message
so
I
mean
we
could
do
it
at
that
layer
that
you
know
we're
already
usually
rewriting
the
commit
messages
for
brevity
or
clarity.
B
B
In
as
a
note
on
the
on
the
commit,
which
I
mean
it's
an
annoying
behavior,
because
if
I
want
a
long,
commit
message,
I
want
a
long,
commit
message
and
I
don't
care
what
did
have
really
wants.
But
it
has
this
functionality
in
place.
That
kind
of
really
pushes
people
to
use
an
18
character,
commit
message
limit.
E
E
B
E
Doing
okay,
here's
another
question:
do
we
need
the
backdrop
slash
or
what
what
happens?
If
you
just
put
backdrop,
issues
of
hash,
100,
I,
think
I
think
github
knows
to
look
because
you're
in
both
are,
in
the
backdrop,
organizations
I
think
if
you
reference
just
to
be
just
put
backdrop,
issues
100.
That
should
be
enough
without
adding
the
the
organization
name
in
front
of
it.
You.
B
B
E
E
Well,
this,
you
can
do
a
short.
We
could
do
a
shortened
version
to
prevent
the
cross
posting.
So
if
we
just
put
bi
hash
100
that
would
at
least
that
would
at
least
solve
the
cross
posting
into
the
wrong
issue
on,
in
the
backdrop
repository,
it
wouldn't
create
the
right
issues.
You
know
without
a
space
without
a
face,
yeah.
B
D
E
E
B
I
kind
of
recall
this
conversation
previously
as
well
then
I
at
the
time
I
felt
like
I,
didn't
want
to
have
the
permanent
history
of
our
project
using
github,
specific
syntax,
but,
on
the
other
hand,
I'm
also
kind
of
like
well.
You
know
we're
already
in
many
ways
tied
permanently
into
github,
based
on
our
issue
numbers
so
yeah.
B
Although
I've
actually
found
that
smoking
takes
a
few
migrate
into
gitlab,
it
actually
maintains
issue
numbers
as
long
as
you
start
with
a
fresh
repository
but
I'm
not
sure
that
I
don't
know
if
I
shouldn't
even
be
thinking
about
such
things,
but.
B
E
This
might
be
a
good
issue
for
the
product
management
project
management
committee
to
just
just
to
go
through
that,
since
it
is
really
a
meta
meta
issue,.
B
E
D
C
D
B
Yeah,
okay:
well,
let's,
let's
see,
there's
one
more
item:
translation
in
internationalization,
I,
don't
think,
there's
not
actually
any
update
in
this
issue.
Issue
number
one
in
the
ight:
this
is
something
that
is
new
this
week.
Er
is
just
left
over
from
last
week's
meeting
left
over
I.
Think,
okay,
all
right,
let's
not
rehash
that
then,
and
let's
call
it
a
meeting.
So
thank
you,
everybody
for
joining,
and-
and
thank
you,
everybody
any
last
words.
Jen.