►
From YouTube: Backdrop Weekly 04/27
Description
Today’s development agenda: http://bit.ly/2p0N2Gv
A
A
So
first
item
on
the
agenda.
We
have
some
big,
exciting
news
at
PNC
it
has
been
working
on
an
agreement
with
the
software
freedom
Conservancy
to
be
our
fiscal
and
legal
sponsor,
and
we
don't
have
the
complete
details
of
that
arrangement
ironed
out
yet.
But
we
did
will
not
to
announce
that
we
are
working
on
that
and
if
you
have
any
comments
or
concerns
or
feedback,
you
can
send
us
an
email
info
at
back
drug
CMS
at
work.
But
I
would
encourage
anyone
who's
curious
about
this
to
check
out
the
conservancies
website.
A
It
they're
an
organization
that
is
particularly
useful
for
open
source
projects
where
we're
really
good
at
knitting
code,
but
not
so
much
at
managing
nonprofits.
So
they're
going
to
take
care
of
all
of
the
details
for
us,
which
is
fantastic
and
they're,
also
have
a
lot
of
experience
with
the
GPL
in
particular,
so
more
more
information
on
that
front
as
it
happens,
but
we
are
still
working
out
what
exactly
they're
going
to
be
providing
for
us.
B
So
we've
only
got
a
little
bit
more
time
to
complete
a
lot
of
functionality,
but
before
we
get
into
1.7
cover
1.6
real
briefly
one
point:
6.4
is
the
next
bug
fix
release,
there's
a
actually
more
transliteration
bug
than
a
translation
bug
at
26:37
that
ole
often
Jeff
are
working
on
a
solution
to
Jeff.
Do
you
have
any
update
that
you
would
like
that?
I
had
a
look
at
this
issue,
yeah.
C
B
Awesome:
okay,
well,
looking
forward
to
that
one
and
item
that
we
had
from
last
week,
which
is
there's
an
issue
with
the
autocomplete.
That
is
some
styling
issues
that
make
it
so
that
we
can't
use
autocomplete
within
a
dialogue,
and
this
came
up
during
one
point:
seven
issue
that
autocomplete
style
bug
has
been
fixed
now
in
one
dot:
X.
B
We're
saying
that
we
haven't
put
this
back
into
1.6
and
I.
Guess
that
is
kind
of
a
point
that
is
open
for
discussion
like
the
issue
only
comes
up
with
autocomplete
is
in
a
dialogue.
We
don't
have
anything
autocomplete
succour
in
dialogues
in
1.6.
So
is
this
something
that
needs
to
actually
be
back
ported
or
not
so.
A
B
Tabs
I
guess
some
like
I,
don't
think
there's
any
substantial
risk
involved
like
we
did
change
the
way
that
the
autocomplete
dial
are
completely
pop-up
is
positioned.
It's
positioned,
fixed
instead
of
absurd
instead
of
relative
now,
but
I.
Don't
think
that
that
it's
a
hard-coded,
it's
JavaScript
layer,
I,
don't
think
that
something
can
really
be
affected
by
themes.
So
I,
don't
think,
there's
ancient
pad
ability
issue
there.
So
I
would
say
sure
that's
that's
back
port,
then
Jeff
you
merged
it
into
into
one
Dex.
Do
you
think
you
could
get
back
to
1.6?
B
Ok,
the
github
issue
tracker
for
1.64
includes
a
bunch
of
other
issues,
they're
actually
starting
to
really
pile
up
in
there
as
where
you've
been
fixing
and
enhancing
things
in
1
dot.
X
we've
been
back
porting
a
substantial
number
of
them
to
1.6
as
well,
however,
with
1.7
only
being
a
couple
weeks
away,
I
think
that
it's
really
likely
that
we'll
just
see
one
six.
For
the
same
time
as
we
see
the
one
one,
seven
o
release
come
out.
B
Some
of
these.
Actually
there
might
be
room
for
fuzzing,
because
we
allow
bug,
fixes
and
UX
enhancements
all
the
way
up
until
the
release
date.
So
some
of
these
ones,
like
the
redesign
of
the
status
report
that
have
a
very
almost
impossible
to
actually
break
other
things
besides
the
status
report
itself
impact,
but
they
not
need
to
be
completed
by
code,
freeze
or
side
by
feature
freeze,
so
so,
let's
run
through
them
here.
B
Links
to
local
has
this
makes
it
so
that,
if
the
link
dialog
and
seek
editor,
when
you
want
to
linked
to
a
piece
of
contents
or
or
link
anywhere,
you
can
now
type
in
the
URL
or
you
can
also
type
in
like
the
name
of
a
node
or
term
or
lay
out
a
review,
and
it
will
autocomplete
and
expand
that
out
that
functionality
is
now
complete.
It's
been
merged
in
grey.
B
B
B
B
This
pull
request
just
got
updated
a
ago
day
or
two
ago,
and
it
needs
some
more
review
again,
like
kind
of
just
design
feedback,
how
we
think
that
it
looks
and
then
a
CSS
review,
no
code
changes
it
all
going
on
here.
Well,
code
is
in
CSS
all
name
changes
so
more
things
that
could
use
a
designer's
hand
there
Emily,
like
it,
looks
so
much
better
than
what
I
had
been
previously.
B
B
I
think
we've
got
a
couple
more
people
that
have
posted
some
feedback,
including
a
Gregory
and
Olaf,
basically
posting
that
the
functionality
itself
works
great,
but
they
have
some
concerns
around
the
user
experience
that
we
probably
won't
be
able
to
change
the
way
it
works,
but
we
can
at
least
do
a
little
bit
work
to
explain
how
things
work
a
little
bit
better
and
so
I.
Think,
like
my
review
of
it,
is
that
from
a
code
perspective,
it's
done.
B
I,
think
that,
just
as
additions
to
descriptions
and
summaries
that
help
explain
how
those
blocks
actually
work
is
the
only
issue
that
I
know
of
that
needs
to
be
addressed
on
those
are
on
that
pull
request
so
anyway.
That
that
feature
is
enormous,
ly
powerful
and
would
be
fantastic
or
will
be
fantastic
and
go
ahead
and
say
that
already
there's
that
one's
a
shoe-in
at
this
point
for
the
release,
it's
just
a
matter
of
how
much
polishing
we
want
to
do
before
you
do
the
merge.
In
my
opinion,.
B
Looking
great
layout
relationships
is
issued,
21:34
personally,
I
haven't
had
a
chance
to
review
this
one,
but
we
did
have
a
reviewer
come
and
trying
to
assemble
some
functionality
of
the
relationships,
but
ended
up
getting
a
PHP
error
with
certain
set
of
circumstances.
So
thank
you.
I'll
Rose
called
for
for
doing
that
review
so
that
one
needs
a
little
bit
more
work,
but
relationships
would
be
super
awesome
and
amazing
to
get
that
one
completed
as
well
looks
like
okay,
the
hair
relationship
PR
was
never
meant
for
inclusion
in
1.7.
Its
way
alpha.
B
B
B
B
B
B
This
capability
makes
it
so
that
you
could
override
views.
Settings
unlock
a
placement
so
as
your
place
of
view
that
contains
a
place,
a
block,
the
content
view
you
could
change
settings
on
that
view.
Every
single
time
you
place
the
block,
this
functionality
I
started
working
out
the
end
of
last
release
and
I.
Don't
think
that
it's
seen
a
lot
of
activity,
it's
pretty
far
from
being
complete
at
this
point.
It's
not
functional
even
like
it
doesn't
actually
work.
So
I'd
probably
say
this.
One
is
also
highly
at
risk.
B
I
think
I've
been
preoccupied
with
reviewing
poor
requests.
I
think
that
reviewing
the
code
that
is
in
progress
is
more
of
a
priority.
To
me
at
least
then
completing
this
one
that
is
not
yet
even
functional,
so
I
think
for
this
one
to
be
to
even
stand
a
chance
of
being
in
the
next
release
will
need
a
champion
to
come
in
and
pick
that
up.
B
B
B
So
that
one's
pretty
much
done,
that's
all
the
items
that
we
have
for
the
main
features
that
are
slated
for
1.7.
There
are
a
number
of
other
issues
that
are
also
in
1.7.
Some
of
them
have
been
fixed
and
merged.
Already
you
can
check
out
the
entire
list
in
the
github
issue.
Tracker
there's
also,
probably
good.
B
There's
gosh
I,
don't
probably
on
the
order
of
about
60
or
70,
a
poll
requests
that
are
in
a
needs,
review,
State
and
I've
been
doing
my
best
to
go
through
those
as
much
as
I
can
I've
been
taken
today
and
tomorrow
off
to
kind
of
help
clear
out
some
of
the
the
code
that
needs
review
but
again,
like
a
call
out
for
help.
If
we
can
get
peer
reviews
going
on
to
actually
review
each
other's
work,
that's
happening
in
the
needs,
review
queue
and
moving
those
towards
our
TBC.
B
B
That's
it
for
the
one
point:
seven
status,
update,
I'm
still
I'm
optimistic
I
think
that
we've
got
great
functionality
lined
up
for
the
1.7
release,
and
most
of
these
are
are
so
close
that
they're
certain
they
will
be
completed.
The
ones
that
won't
are
the
ones
that
are
less
likely
and
already
mentioned
those
but
yeah,
I'm,
really
stoked
I,
think
it
we've
got
some
great
functionality
lined
up.
B
Go
team
we've
got
some
work
to
do
actually,
but
compared
to
other
releases.
I
feel
like
this.
One
is
probably
the
most
in
hand
like
as
far
as
like
we
have
a
pretty
realistic
set
of
features
and
functionality.
Some
of
them
have
been
completed,
we're
looking
really
solid.
We
did,
of
course,
as
we've
done,
every
single
release
kind
of
have
this
giant
like
hurrah
of
excitement
right
at
the
tail
end
of
code
freeze,
but
that's
the
way
acceptor.
B
B
B
I
start
naming
our
releases
after
contributors-
okay,
oh
there's,
some
banter
going
on
in
the
chat
in
here
weather
I,
don't
think
it's
of
consequence,
I
think
that
we're
all
complete
for
this
meeting.
Thank
you,
everybody
for
watching.
Thank
you
guys
for
joining
we'll
see
you
guys
in
the
issue
queue
all
right.
Thanks
guys.