►
From YouTube: Backdrop Weekly May 23
Description
Today’s development agenda: http://bit.ly/2WQIhx8
A
A
So,
on
our
philosophy
page,
we
have
a
section
for
principles,
I'm
going
to
throw
a
link
in
the
meeting,
chat
and
indicator,
and
we
decided
to
have
sort
of
an
open
discussion
about
the
wording
around
security,
so
I
thought
I
would
create
an
issue
and
the
backdrop
semester,
org
cube
where
we
can
sort
of
revise
and
refine
that.
But
since
there's
a
bunch
of
people
here
at
once,
I
just
wanted
to
see.
If
we
had
any
preferences
on
like
we're
in
the
list,
it
should
go.
A
B
A
B
A
B
A
C
C
A
C
A
Like
it
and
then
we
have
sort
of
a
one
or
two
sentence:
explanation
right
now
about
each
principle,
and
what
do
we
want
to
say
about
security,
and
is
this
worth
talking
about
now
or
should
we
just
start
writing
some
drafts
in
an
issue
and
review
there?
Okay,
let's
create
an
issue
on
backdrop,
semester
org,
and
we
can't
figure
it
out.
A
Okay,
that
was
exciting.
Thank
you.
Pmc
website.
We
talked
a
little
bit
about
the
website
in
the
design
and
usability
meeting
in
the
last
hour.
But
when
we
talked
about
the
demo
button,
we
said
it
wasn't
working
and
we
have
news
apparently
Nate
thinking
up
a
button
in
the
last
hours
so
fix
now,
which
is
great,
and
we
can
then
move
forward
about
replacing
Pantheon
button.
A
That's
currently
on
the
home
page
with
the
demo
button,
but
as
just
pointed
out
in
the
last
meeting
that
button,
the
Pantheon
button
is
the
only
way
to
currently
install
a
doctor
up
on
Pantheon.
So
we
need
to
make
sure
we
get
the
secondary
page
up
at
the
same
time
as
we
remove
the
bottom.
The
camera
button
right
away
so
I
think
we
have
a
secondary
page.
A
It's
a
view
somewhere,
I'm,
not
sure
I,
think
it's
accesses
and
turned
on
or
I
don't
know,
but
all
the
content
should
be
there
and
we
just
need
to
kind
of
do
it
like
once
over
it
for
design.
It's
been
a
long
time
since
the
design
make
sure
it's
okay
and
then
first
about
so
should
we
create
a
straight
board
theory:
okay,.
A
A
C
That's
a
really
good
thing
to
cover
so
I
see
it
need
to
pull
up
that
issue.
We
had
an
issue
earlier
today
actually
filed
a
couple
of
days
ago.
That's
we
had
a
problem
with
the
changes
to
the
entity,
API
that
we
added
a
consistent
way
of
working
with
entities
or
access
control
and
as
part
of
that
changes
change,
we
had.
C
Don't
change
anything
and
so
we're
just
going
to
remove
the
static
declaration
and
basically
under
the
API
change,
because
I
had
a
lot
larger
impact
than
we
had
expected.
So
because
that's
a
really
big
problem,
let's
say
this:
the
issue
number
on
this
is
38:
oh
nine,
three,
eight
or
nine
and
that's
already
been
merged
and
pushed
into
the
113
dot,
X
branch
and
I.
C
Today,
yeah
I
was
I
was
thinking
maybe
after
this
meeting.
If
that
would
be
okay,
there's
only
there's
only
five
issues
so
far
they've
been
merged
into
the
113
branch,
so
I
think
there's
gonna
be
really
trivial,
but
it
is
important,
so
we
should
get
out
there
quickly
if
you,
okay,
that's
kind
of
it.
For
the
113
update
then
looks
like
in
the
agenda.
We
also
hadn't
removed.
C
C
C
C
A
C
A
C
C
A
C
A
Sure
so
I
also
posted
a
link
to
this
page
in
the
agenda.
I'll
post
it
again
in
the
Gator
chat
into
sidebar,
but
I
wrote
up
a
documentation
page
after
our
last
meeting.
Since
it
sounds
like
we
finally
figured
out
a
sensible
way
to
manage
milestones,
I
wanted
to
write
it
down
so
that
everybody
who
is
coming
to
work
in
the
issue
queue
could
figure
it
out.
A
So
I
put
a
section
for
bug,
fix
milestone,
so
it's
just
sort
of
what
we
have
been
doing
or
basically
you
can't
have
anything
in
the
bug
fix
milestone
unless
it
has
a
pull
request,
unless
it
has
been
deemed
by
a
cork
emitter
to
be
a
super
high
priority
issue,
and
those
would
like
folks
something
like
this.
If
we
didn't
have
a
fix
for
it,
but
we
know
it
was
important,
so
they're
quiet
Rancheria
are.
A
It
must
have
first
been
tagged
with
a
minus
one
candidate
like
one
person,
it
must
have
had
the
milestone
candidate
added
by
a
second
person.
It
must
have
a
recent
poor
question
to
put
near
ready
states.
That
would
mean
something
that
got
a
pull
request
like
two
years
ago
and
doesn't
apply
anymore
could
be
bumped
and
it
must
be
suitable
for
a
bug-fix
release.
A
So
something
that's
not
a
new
feature
and
I
tried
to
outline
that
saying
it's
either
going
to
be
tagged
with
the
label,
bug
report
type
task
or
have
user
experience
tag
in
the
title
or
a
cork
emitter
must
have
said.
Yes,
this
is
appropriate
for
bug
fix
release,
so
we
have
some
things
are
like
kind
of.
A
We
have
one
issue
right
now:
I
think
that
what
was
it
converting
comments
to
views
like
could
maybe
be
a
bug
fix,
but
I
think
it
might
be
better
as
a
mind
as
a
minor
release
in
a
new
feature
issue
so
stuff
like
that,
where
I
think
we
need
to
get
core
committers
sign-off
and
whether
that's
allowed
and
then
minor
releases,
which
is
the
thing
that's
new
here,
is
how
do
we
figure
out
what
goes
into
our
next
milestone,
so
the
requirements
there
are
that
it
has
to
be
tagged
with
the
milestone
candidate,
minor
label.
A
It
must
have
an
advocate
and
that
doesn't
have
to
be
a
person,
who's
gonna
work
on
the
issue,
but
it
is
a
person.
Who's
gonna
push
the
issue
forward,
and
then
we
also
explained
what
an
advocate
is
in
detail
on
this
page,
where
we
said
the
Advocate
would
ideally
be
able
to
attend
most
of
our
weekly
meetings
to
report
on
the
status
of
the
issue.
That's
not
possible,
then
you
can
put
an
update
or
summary
of
issue
into
the
issue
queue
and
that
way
or
into
the
top
post
and
the
issue
in
queue.
A
A
So,
in
the
same
way
that
if
you
have
a
bug
fix
with
a
pull
request,
it
can
get
added
to
the
bug
fix
release
if
you
have
a
feature
request
with
an
RVT
sequel
request,
I
can
get
into
the
minor
release
so
that
way,
if
you
are
working
on
something
that
hasn't
been
a
priority,
but
you
get
it
all
the
way
to
done
we're,
not
gonna
prevent
that
from
going
in,
like
that's
good
work,
it's
ready,
but
we
do
want
to
have
a
list
that
will
help
us
prioritize.
Let's
laughs,.
C
There's
some
note
in
here
saying:
I,
think
that
make
sense
for,
like
our
TVC
state
means
that
it
can
be
moved
into
the
next
milestone
like
right
away,
yeah,
but
there's
a
comment
here
saying
that
the
advocate
for
this
issue
can
cannot
also
be
the
advocate
for
another
open
issue
in
this
milestone,
unless,
of
course,
the
other
issue
has
a
pull
request
in
the
near
ready
state
yeah.
Are
you
saying
that
if
you
were
an
advocate,
there's
this
documentation
been
saying?
A
So
we
don't
want
to
make
sure
that
you
only
commit
one
thing
in
three
months
like
if
you're
super
motivated
to
work
around,
like
eight
things
at
a
time
or
eight
things
in
a
cycle.
That's
fine,
but
we
don't
want
you
to
have
any
things
at
a
time
we
want
to
have
in
succession,
but
there
might
be
a
period
of
time
where
your
pearl
request
is
marked
our
TBC
and
it's
not
getting
reviewed.
It's
not
getting
merged.
We
don't
want
you
sitting
around
doing
nothing.
A
So
at
that
point
you
can
adopt
another
one,
and
even
if
your
art
to
BC
issue
gets
bumped
back
to
like
needs
work
that
doesn't
mean
you'll
have
to
remove
your
other
issue
from
the
milestone.
You
can
go
back
and
forth
between
the
two
of
them,
but
one
of
them
has
to
be
close
enough
that
it
you're
not
confused
about
which
one
to
work
on
okay.
C
A
B
And
yet
the
the
the
notes
on
the
definition
of
the
issue
you
had
forget
where,
like
the
last
one,
was
the
initial
version
of
it
said
that
you
had
to
solve
like
attend
the
meetings,
and
that
was
very
limiting,
because
some
people
don't
have
the
time
there
aren't
favorite
time
zone.
That's
why
we
adapted
it
to
sort
of
like.
If
you
cannot
make
it
then
here's
alternatives.
The
point
is
that
try
to
get
an
update
to
someone
that
can
get
it
during
the
meetings.
A
So
following
our
new
rules,
I
have
adopted
one
issue
or
114,
and
that
is
core
field
of
all
file
entity.
Bundles
and
that's
because
right
now,
I
feel
like
that.
Jeff's
priority
should
be
on
feature
compatibility
with
Drupal
in
particular,
Drupal
7,
so
that
people
are
updated
for
some
don't
have
to
use.
A
A
Resolved
I
also
feel
like
it's
pretty
close,
because
doc
Lamont
did
a
ton
of
amazing
work
on
it
and
what
prevented
it
from
going
in
the
last
time
it
was
almost
ready,
was
usability
stuff,
and
so
that's
why
I'm
motivated
to
take
it
over,
because
I've
always
felt
that
file
enemies
in
Drupal,
7,
contributed
a
nightmare
and
I
would
love
to
try
to
solve,
resolve
that
problem
or
improve
it
slightly.
That's
all
I
can
do
so
that
we
can
get
it.
A
B
Yeah
and
we
decided
that
we
should
at
some
point
have
a
dedicated
security
section,
like
maybe
configuration
security
or
something
like
that,
the
product
itself.
So
this
is
a
stat.
This
is
a
good
candidate,
so
where
this
issue
is
left
at
it's
the
implementation
impact
rope
is
a
bit
more
less
intruding.
Does
it
say
so?
It
doesn't
prevent
you
from
installing
bat-rope
and
it's
not
a
an
error.
It's
rather
a
warning
and
the
that
the
goal
is
to
have
it
be
configurable
via
the
user
interface
and
via
the
settings.
B
A
And
then
the
other
one
I
left
here,
digital
signatures
on
project
packages-
that's
assigned
to
you
currently
I-
think
cuz.
It's
still
like
90%
reviewed,
but
not
all
the
way,
and
so
I
put
you
down
as
an
advocate
for
that
one.
But
Jeff
Franklin
could
be
the
advocate
for
it
if
he
wanted
so
I,
don't
know
but
you're
both
working
on
that
one.
So
we'll
just
leave
it
there
and
let
you
guys
fight
over
who
gets
down
it.
Cool.
C
So
this
is
interesting,
so
that
means
that
the
three
issues
that
we've
got
listed
in
the
114
minor
version
right
now,
at
least
that
we've
gotten
this
agenda.
One
person
present
is
the
advocate
for
each
one
of
them.
So
does
that
mean
that
we're
going
to
start
having
the
Advocate
be
present
to
talk
about
their
issue
and
the
meetings
we.
A
C
Great
okay,
I'll
should
I
go
ahead
and
start
on
signatures
on
packages.
Sure,
okay,
all
right
so
issue.
1992
is
our
digital
signatures
on
packages
that
John
Franklin
has
been
leading
the
charge
on
we're
working
through
kind
of
the
necessary
infrastructure
to
support
it.
Currently,
we
did
make
an
update
to
project
module
a
couple
weeks
back.
That
makes
it
so
that
it
can
now
be
XML.
A
That's
I
think
for
all
114
issues
that
we
know
about,
but
there
are
a
bunch
of
people
who
do
a
bunch
of
great
work
on
course
up
who
maybe
not
aware
of
this
new
policy
or
process
ocean
yeah
and
so
I
would
encourage
anyone
who
wants
to
work
on
something
and
hasn't
anything
the
priority
to
continue
to
bring
it
up
and
get
her
and
the
issue
queue.
However,
and
we'll
try
and
spread.
This
information
is
not
just
making.
B
A
A
So
it
was
a
little
hard
to
figure
out
exactly
where
that
came
from.
So,
if
I
can
help
with
that
on
any
of
the
other
issues,
let
me
know
or
any
of
the
modules
I
think
you
should
definitely
be
our
priority.
So
there's
been
a
lot
going
on
and
you
slightly
and
there's
been
not
a
lot
going
on
a
lot
of
those
other
Drupal
7
can
trim
projects
but
I'm
definitely
happy
to
help
set
up
those
metas,
if
that
makes
it
easier
for
other
people
to
do
the
cross.
Porting
yeah.
B
A
B
One
problem
that
I
noticed
is
that
some
of
the
links
do
not
work
because
it
wasn't
pointing
to
right
the
lane
or
something,
but
it's
an
easy
sell
to
search
and
replace
so
I've
been
fixing
those
okay,
but
I
can't
remember
who
was
the
links
to
the
commits
or
the
links
to
their
respective
issue?
There's.
B
D
B
A
Also
need
for
today's
really
speaking
of
use
being
integral.
We
committed
something
recently
that
broke
filters
like
a
filter
operator
and
in
the
drupal
issue
queue
they
had
a
fix
that
didn't
actually
fix
the
problem,
but
they
had
an
earlier
commitment
did,
and
I
was
recommending
that
we
commit
the
fix
that
actually
fixes
the
problem
and
then,
when
Drupal
7
lands
on
a
solution
that
fixes
it
in
a
way
that
they
like
better.
A
E
A
A
A
A
E
A
A
That
we
don't
have
that
hooked
up,
so
I
think
I
was
like
what
we
could
move
sanitized
back,
but
really
I'd.
Much
rather
move
back
top
CMS
I
worked
forward
to
you,
so
the
only
problem
just
says
that
Nate
and
I
are
gonna,
be
out
of
town
until
Monday
I
mean
it's
a
long
weekend
and
not
sure
I
won't
ask
anyone
to
work
this
weekend
anyway.
Well,
maybe
we
can
schedule
a
day
next
week
to
do
a
car
over
yeah.
A
A
C
A
C
A
B
A
Is
that
for
every
control
that
we
put
in
back
to
our
core,
we
can
have
it
running
on
a
Drupal,
7
site
and
then
anytime,
there's
an
due
to
the
module.
The
triple7
site
will
email
someone
to
go:
hey,
there's
a
new
update
up
for
links
and
that'll
help
us
know
when
we
need
to
create
a
meta
to
include
all
the
crosswords
for
those
yeah.
B
E
A
E
A
A
B
B
A
I
also
recently
set
up
some
better
group
handling
on
github
for
our
control
projects.
So
there's
a
group
for
every
site.
So
if
you
won't
commit
access
to
individual
site,
you
can
do
that,
but
there's
also
a
like
web
team
that
has
access
to
all
of
the
sites.
So
I
think
where
you
might
already
be
on
the
web
team
but
I'll
check
and
make
sure
that
if
not,
you
have
at
least
commit
access
to
that
one.
A
B
B
E
C
C
A
B
A
B
A
B
A
A
F
C
C
A
A
F
A
And
then
Nate,
you
are
in
the
design
meeting,
but
the
problem
space
we're
facing
right
now
is
that
if
we
made
a
change
to
the
way
that
team
colors
work,
we
might
want
to
regenerate
all
of
the
color
modulized
versions
of
that
scene,
which
generates
CSS
files
and
right
now.
The
only
way
those
files
are
regenerated
by
hitting
save
on
the
game
settings
form
and
we
wanted
to
be
able
to
do
it
in
an
update
hook.
A
F
A
F
F
F
C
C
A
F
A
A
C
I,
don't
know
like
I,
really
don't
like
things
that
aren't
like
you
know,
listening
all
the
time
you
know
like
did
something
change.
Yes,
then
then
do
something
invisibly
like
on
the
first
time.
The
page
is
loaded
like
I
feel
like
any
kind
of
update
like
if
you
update
a
module
or
theme
like
the
process
to
actually
apply
that
update.
You
know
should
be
explicit.
C
C
A
A
So
the
color
module
could
define
something
like
regenerate
new
themes,
files,
true/false
right
and
you
put
in
your
theme-
be
like
okay,
it's
time
to
do
it
set
to
true
and
then
color
module
would
be
like.
Oh
okay,
this
is
it
such
a
true
regenerate
file.
I
mean
something
you
don't
like
me,
because
it
would
needed
a
moment
that
check.