►
From YouTube: Backdrop Weekly 2/16
Description
Today’s development agenda: http://bit.ly/2k9a1Jm
A
A
How
will
he
handle
sponsorships,
which
you
don't
yet
have,
but
particularly
in
exchange
for
pro
bono
work-
and
this
is
a
particularly
contentious
issue-
that's
come
up
several
times
in
Drupal
community
and
we
wanted
to
make
sure
that
we
had
a
policy
right
from
the
outset,
so
that
if
we
do
have
people
who
are
trying
to
do
in
kind
of
traits,
we
know
how
do
you
feel
about
that?
How
it's
going
to
work,
and
so
it
looks
like
we
have
a
consensus
on
that.
A
A
Let
us
know
we
have
them
feel
if
you
were
waiting
to
to
pick
them
up,
so
the
websites
been
updated
with
the
new
sizes.
Son
wants
to
buy
them
from
the
website
can,
and
we
are
also
traveling
to
sand
camp
this
weekend
in.
If
anyone
wants
to
try
on
a
nice
warm
soft,
fluffy
hoodie
in
person,
san
Diego's
place
to
do
it.
A
B
A
A
That'd
be
great
already,
okay,
so
we're
also
working
on
a
bunch
of
subdomains.
For
the
backdrop
community
at
large,
the
forum
is
something
that
we've
been
waiting
for
for
two
years
now
and
I'm
really
excited
that
we're
finally
working
on
it.
I
had
a
test
last
week
to
figure
out
bakery
module
and
I
am
working
on
that
I'm.
Working
on
that
this
morning,
I
think
we're
kind
of
close.
A
It's
not
working
and
I'm
trying
to
figure
out
exactly
why
and
fix
it,
but
it
looks
like
it
should
work,
so
I
feel
like
which
should
be
pretty
close
on
that
one.
But
we
do
need
to
make
some
decisions
about
architecture
on
the
actual
forum
site
eliminate
the
stuff
we
don't
want
and
move
forward
with
the
stuff
we
do
want.
I
haven't
checked
that
issue
since
last
week
on
the
architecture
decision,
but
I'll
do
that
after
this
call
and
we
can
move
forward,
Daniel
I
know
you
had
some
thoughts
on
forum.
A
C
C
C
My
I
would
like
to
have
to
do
something
that
this
kind
of
circular,
something
that
would
not
only
solve
the
the
need
to
get
the
forum
up
and
running
for
the
internal
discussion,
but
something
that
at
least
even
if
we're
not
finishing
and
any
of
it,
we
can
write,
write
it
down
as
a
perspective,
so
that
we
can
start
tempting
people
to
come
in
here
with
something
cool.
I
would
like
to
discuss
how
we
can
actually
solve
some
of
the
things
that
everybody
is
struggling
with,
no
matter
which
solution
they
are
using.
C
Not
just
with
just
the
features
thing
but
may,
for
example,
from
the
perspective
of
information
overload.
A
CMS
is
a
content
management
tool,
tool
kit
and
now
everybody
is
getting
more
and
more
information.
More
and
more
things
to
read.
We
cannot
when
I
go
to
websites
and
I,
see
a
very
large
post.
I,
don't
have
time
two
three
even
read
it:
I
have
to
browse
through
sometimes
I.
C
C
Multi-Layer
is
a
GUI
so
that
first
you
get
a
summary,
then
you
get
click
and
you
get
something
more
and
even
with
a
premium
community.
You
could.
If
you
have
this
in
that
role,
you
can
drill
down
five
layers
and-
and
if
you
look
at
the
media
today,
I
maybe
I
said
trying
to
sell
trying
to
convince
people
that
you
should.
You
should
not
have
all
the
news
for
free,
but
what
they're
doing
is
that
they
are
they're
doing
it.
In
my
opinion,
an
exact
opposite
way
of
what
they
should
be
doing.
C
Those
kind
of
solution
doesn't
necessarily
need
to
be
in
court,
but
it
would
be
nice
if
core
can
make
some
description
about
what
the
kind
of
things
that
the
core
will
enable
to
build.
Yes
and
just
point
to
contribute
use
but
I.
These
kind
of
short
small
statements
give
people
perspective
and
to
tell
people
that
these
are
the
things
that
actually
they
can
come
here
and
discuss
with
us,
because
there
are
people
in
our
community
here
that
actually
are
working
on
these
things
to
solve
them.
C
E
So
I
didn't
catch
you.
Do
you
have
a
github
account
hi
I
think
that
this
list
should
go
in
an
issue
there,
because
most
of
us
monitor
that
at
least
they're
in
on
github
and
see
how
these
bits
that
you
have
there
related
to
look
so
so
that
we
can
reply
to
each
one
of
them
and
discuss
what
for
it's.
One
of
them.
I
think
that
the
best
thing
is
now
that
you
put
the
thing
together.
Perhaps
you
start
an
issue
in
the
queue
and
then
describe
what
it
all
is
about,
and
you.
C
This
one
with
I
just
posted
the
link
in
the
chapter-
that's
what
I
did
last
week,
I
present
in
the
cuckoo.
Okay.
Yes,
okay,
I
don't
know
if
that's
enough,
or
that
is
the
right
place,
because
I
didn't
get
any
feedback,
so
I
was
starting
to
wonder.
Where
should
I
put
it?
You
know,
but
I
also
realized
there
are
not
a
lot
of
people,
so
there
is
not
a
lot
we
need
to.
Actually,
mostly,
this
is
now
kind
of
a
developer
community
right,
so
I'm
kind
of
fun
to
fight
talking
more
about
it.
C
E
C
E
E
What
I
meant
is
not
to
post
a
comment
about
this
but
start
and
a
new
issue
with
all
these
bullets,
and
then
I
haven't
been
personally
around
their
forum
yeah
up
to
you,
but
it's
not
a
new
issue
and
the
claret
I'll
guide.
You
I'll
guide
you
through
how
to
do
that
after
the
meeting
is
personally
what
I
can.
C
A
All
right,
oh
I,
will
go
and
take
a
look
at
that
forum.
Q
later
stay
just
wanted
to
get
bakery
worked
out
because
that's
issue
number
1,
I'd
like
to
get
them
ourselves
and
I'll
see
what
else
is
going
on
I'll.
Take
a
look
at
your
well
it's
daniel
and
see
what
of
that
we've
already
considered
and
what
maybe
needs
to
be
added
to
one
of
our
to-do
lists.
A
C
D
A
D
C
A
F
It's
a
yep,
it's
a
website
and
it's
ready
for
some
initial
prodding
by
probably
Gregory
and
Olaf
kubinski,
and
flesh
out
some
issues
and
start
writing
them
in
the
there's.
A
github
issue
queue
in
backdrops
for
localization.
So
if
you
find
those
issues
put
them
there
and
we'll
start
solving
those
hey.
G
G
So
if
you
spun
up
a
Pantheon
website
based
on
backdrop
with
their
upstream,
that's
now
updated,
Jeff
updated
the
docker
images
and
yeah
we're
in
a
great
spot
with
161
the
next
bug-fix
release
is
162
and
the
16
to
release.
We
don't
have
any
critical
items
stacked
up
yet
that
would
initiate
our
demand.
Another
bug-fix
release.
However,
there
are
a
bunch
of
items
that
are
already
slated
for
162
and
you
can
get
the
full
list
of
them
by
checking
out
the
get
up,
issue
queue,
a
backdrop
issues
and
then
the
162
milestone.
G
E
G
Page
element
blocks,
which
is
issue
1704
and
layout
relationships
which
is
issued
2134.
There
hasn't
been
any
activity
on
those
issues,
though
so
I'm
just
going
to
say,
go
to
those
issues,
review
them
and
provide
some
feedback.
The
page
element
blocks,
one
is,
is
looking
really
good.
The
layout
relationships,
one
needs
in-depth
reviews,
both
in
functionality
and
encode
reference.
Module
is
the
other
item
that
is
slated
for
1.7,
oh
and
work
on
the
reference
module
is
currently
happening
in
the
contribute,
contribute.
G
G
G
G
Yeah
actually
add
to
the
newsletter,
was
great
I
I
didn't
even
realize
it
came
through
because
it
got
filed
away
in
my
social
tab
on
gmail,
but
once
what
I
actually
looked
at
it
I
was
like.
Oh,
this
looks
amazing
hahahahaha
our
best
newsletter
to
date,
I
think
well
tonight
Carl
as
far
as
structure
and
content.
So
it
looks
great,
not
a
problem.