►
From YouTube: Backdrop Weekly - May 16th
Description
Today’s development agenda: http://bit.ly/2vQ05wI
A
B
Of
course,
yeah,
the
most
obvious.
An
exciting
thing
is
that
backdrop
113
came
out
yesterday
and
so
our
final
release
of
backdrop
that
included
the
dashboard
was
the
the
big
headline
feature
there
and
we
gotten
the
blogpost
on
yet.
No,
so
we've
only
got
the
release
notes.
Yeah.
We
need
to
make
the
eye
expansions
around
the
field.
Api,
let's
see
dashboard,
let's
see,
there's
some
other
things.
We
started
working
through
translatable
strings
in
config.
We.
B
What
was
that
link
attributes
for
the
rich
text?
Editor?
Oh
yeah.
Now,
when
you
insert
a
link,
there's
a
lot
more
properties
that
you
can
put
on
a
link.
Self
updates
are
turned
on
by
default.
Now
sorry
manual
self
updates,
so
you
can.
The
option
is
no
longer
well,
it's
no
longer
hidden
or
and
and
it's
on
by
default,
so
the
same
way
that
you
can
update
a
module,
a
contributor,
you
know,
upgrade
back
to
our
core
itself
out
of
the
box
without
changing
any
options
so.
C
B
B
In
addition
to
113
112,
seven,
the
last
well,
the
last
bug
fix
release
of
the
112
branch.
Besides
security
fixes
that
will
continue
to
come
out
until
114
comes
out,
I
was
also
released
and
that
included
26
additional
fake
fixes,
which
I
was
excited
to
see
a
lot
of
these
getting
wrapped
up
a
lot
of
the
things
that
we've
been
mentioning
every
week
for
the
past
several
weeks,
including
like
she
catered
our
icons
being
broken
in
the
RTL.
Oh
yeah,.
B
So
that
that's
that's
very
exciting,
let's
see
we
did
move.
Let's
see
we
merge
views
into
their
respective
modules,
including,
like
taxonomy
views
and
the
front
page
got
moved
in
node
module
when
we
did
not
get
comments
converted
into
a
view.
Yep
issue
549-
and
there
was
also
this
issue
about
exposing
a
filename
filter
from
the
media
library,
dialog
issue,
32
93-
it
also
did
not
make
it
any,
but
I
mean
we
went
through
it
like
a
little.
It
was
a
little
bit
of
a
flurry
storm
yesterday.
B
Getting
all
of
these
items
that
had
been
reviewed
extensively
mark
Garrity
receive
quite
a
while
in
for
the
113
and
112
seven
releases,
so
113
1
the
next
minor,
our
next
bug-fix
release.
We
don't
have
anything
slated
in
here
yet,
of
course,
things
that
were
mark
2007
didn't
get
in,
got
all
bumped
into
113,
but
I
don't
think
we
have
anything
really
of
notes
to
bring
up
for
this
meeting.
B
We've
got
the
big
discussion
item
for
this
week.
Is
you
know
114?
Like
that's
the
next
version?
We've
got
some
things
queued
up
the
items
that
have
been
bumped.
Of
course
I.
Think
that
includes
things
like
the
check
sums
on
packages
and
hang
on.
Let
me
pull
up
the
milestone.
There's
some
other
things,
I'm
sure
somebody
has.
It
pulled
up
already.
B
A
A
Maybe
we'll
add
that
to
the
list
too,
so
it
wouldn't
be
so
much
the
PMC
setting
the
direction
of
the
project,
but
the
PMC,
like
approving
the
direction
of
the
project,
to
make
sure
that
we're
not
doing
anything
crazy,
but
that
still
means
that
it
leaves
the
decision
of
what
those
six
to
ten
issues
should
be
in
the
hands
of
the
community,
which
is
right
now
us
and
we
need
to
figure
out
how
we're
gonna
do
that.
We
have
an
issue
in
the
queue
for
anyone
that
has
an
issue.
A
What
is
this
30
per
page
60
of
them
and
turn
that
maybe
40
ish
turn
that
into
10,
yet
the
most,
and
so
last
week
we
talked
about
a
couple
of
things
that
might
be
good
ways
to
room.
You
know
remove
things
from
our
possible
list
if
the
issue
doesn't
have
a
clear
person
who
is
an
advocate
for
making
it
happen,
advocate
doesn't
have
to
be
a
person,
writes
the
code,
but
it
has
to
be
someone
who's
going
to
check
on
it
weekly
and
find
out
like.
If
there
is
someone,
that's
writing
the
code.
A
Do
they
need
any
help?
Are
there
any
blockers?
They
may
want
to
test
it,
just
someone
who
kind
of
keep
moving
it
forward.
If
there's
no
one
who's
really
passionate
about
moving
that
issue
forward
every
week,
maybe
it
shouldn't
be
a
priority
for
community
and
then
something
that
had
been
a
month
on
a
previous
milestone
might
get
added
wait
so
something
that
we
previously
thought
was
a
priority.
Maybe
it's
still
a
priority
and
haven't
gotten
to
it,
because
it's
hard,
maybe
it's
not
a
priority
and
it
shouldn't
be
on
the
list.
A
But
that
is
something
we
need
to
consider
carefully.
There
are
a
couple
of
things
that
I
think
would
make.
You
know
backdrop
a
lot
better,
that
we
just
haven't,
haven't
gotten
finished
and
maybe
they're
really
close.
Maybe
they
just
need
a
user
experience,
review
or
code
cleanup
or
something
little
that
might
make
it
really
easy
to
have
a
big
difference.
So
I,
don't
know,
I,
don't
have
an
answer.
D
A
We
have
to
be
a
little
bit
careful
with
the
Sinese,
because
that
is
kind
of
a
signal
to
other
people
not
to
work
on
that
issue.
Like
Oh.
Someone
else
has
this
I
won't
touch
it,
and
so
we
want
to
make
sure
I
mean
if
we
can
decide
to
do
that,
but
we
should
also
somehow
clearly
indicate
like
whether
you
want
other
people
to
work
on
it
or
not.
If
it's
like
I'm
writing
the
code,
I'm
gonna
file
a
pull
request.
D
A
So
last
week,
in
this
weekly
meeting,
we
made
a
list
of
a
handful
of
the
issues
that
were
typed
with
milestone
candidate
and
we
started
to
kind
of
go
through
them
and
see
like
if
it.
If
the
issue
had
an
advocate
or
not,
there's
also
some
notes
into
here
as
to
like
whether
we
thought
it
was
going
to
be
easy
or
not
or
questions
we
had,
but
I'm,
not
sure
going
through.
Issues
like
that
is
necessarily
gonna.
Get
us
closer
to
the
list
that
we
want
in
the
end.
D
A
And
we
did
go
back
through
a
handful
of
issues
last
week
and
find
ones
that
were
that
we
least
once
we
were
thinking
about
like
we
didn't
get
all
of
them.
I'm
andrey
add
the
milestone
candidate
label,
so
I
went
found
like
feel
double
files
and
layout
relationships
and
a
bunch
of
stuff
that
we've
gotten
really
close
and
added
that
label
back
onto
them.
So
they
should
be
in
this
list.
There
might
be
other
stuff
relationships.
We
got
back
on
there
too.
There
might
be
some
stuff
that
existed.
A
You
know
before
we
had
this
label
that
we
haven't
remembered
and
hasn't
gone
back
on,
but
I
would
also
like
to
mention
that
it
could
be
that
something
that
we
thought
was
a
priority
before
isn't
actually
a
priority,
and
maybe
it
doesn't
need
that
label.
So
I
would
say
if
there's
something
that
we
do,
you
think
we've
forgotten.
You
can
definitely
add
a
label
it'll
be
there,
but
there
might
be
other
stuff
with
it.
You
know
we
added
a
milestone.
It
didn't
begin.
It
wasn't
really
that
point
currently.
B
A
E
A
B
A
Did
that
okay?
Try
that
approach,
but
the
problems
they're
all
like
tied
together,
like
the
interface
for
adding
a
file
is
like
depends
on
whether
you
have
bundles
or
not
so
there
I
tried,
like
I'm,
just
gonna,
do
a
look
just
a
little
piece
of
it
and
then
I
was
like.
Oh,
this
is
silly
cuz,
it's
all
tied
together.
So.
B
Yeah
I
still
think
oh
good
possible
candidate,
though
I
mean
the
fact
that
all
this
card
exists
and
it
all
works,
and
it
provides
all
the
functionality
like
it's
like
it's
not
quite
as
contentious
as
the
text
format
UI,
where
we
don't
even
know
what
you
look
like,
although
we
are
coming
up
on
the
same
concept
that
we
have
a
aux
problem
here
or
you
know
or
terminology
problem,
or
you
know,
we've
got
some
conflicts
and
the
way
that
I
think
to
us
creates
interfaces
conflict
with
other
ones.
Okay,.
D
Going
I'm
going
to
just
ask
this
because
I
don't
see
it
in
any
of
the
lists
like
in
the
current
milestone
world
the
candidates.
What
is
going
on
with
the
references
thing
like
it
started
early
on
it
had
some
momentum
and
then
we
stopped
like
what
other
book
is
for
that.
One,
because
I
think
it's
an
important
one,
but
I
don't
see
it
in
the
list,
not
in.
A
The
list
in
the
in
the
in
the
issue
queue
it's
issue.
1301
I,
think
that
where
we
decided
with
that
is
that
we
needed
to
have
a
usable
contribs,
we
still
don't
have
a
release
of
a
conversion,
so
I'm
going
to
the
deaf
person
and
a
bunch
of
sites
in
it
like
it's
good.
It's
fine,
like
all
my
sites,
are
working,
but
it's
definitely
not
feature
complete
in
the
same
sense
that
either
of
the
previous
ones
work
and
circle.
A
We
have
a
bit
of
an
issue
with,
like
you
know,
a
bunch
of
there's
a
ton
of
issues
in
the
queue
there.
Some
of
them
are
really
stuck
or
some
of
them
aren't.
There
are
some
core
release
blockers
with
not
being
complete
enough
and
I
think
that
just
trying
to
do
all
of
it
at
once
that
came
too
much,
but
now
it
hasn't
been
getting
a
lot
of
attention
in
control.
So.
D
A
B
That
seems
like
pretty
fair
such
when,
including
that
reference
module
doesn't
have
anything
like
because
it
stands
by
itself
like
it
could
be
matured
and
can
trim,
but
that
hasn't
been
happening
either,
but,
like
it's
really
like.
If,
if
there's
one
module
that
we
could
probably
do
outside
of
everything
else,
its
reference,
you
know
and
just
have
that
be
done
and
contribute
into
court
when
it's
ready
rather
than
saying.
A
That
already
in
Drupal,
like
so
yeah
my
my
goal
for
reference
and
there's
an
Apache,
the
key
I
think
includes
an
upgrade
path
book
from
node
reference
and
form
entity.
Reference
I
had
a
site
that
was
using
both
of
them
and
they
moved
them
both
into
reference.
But
when
you're
trying
to
include
like
all
of
the
features
from
all
the
projects
they,
it
gets
to
be
a
lot
so
yeah
I
mean
also
like
the
entity.
A
A
So
then,
there's
like
kinship
projects
that,
like
add
back
the
parts
that
are
missing
and
it
it
I
think
like
the
way
that
we
wanted
to
do
it
with
our
reference
module
was
to
use
our
API
solidia
were
intended
to
be
used,
so
we
wouldn't
need
all
these
weird
Drupal
7
workarounds,
but
it's
tough,
because
we
have
all
these
people
coming
from
triples
that
are
earned
using
the
weird
workarounds
and
so
trying
to
get
them
to
like
not
look
for
entity.
Api
module
is
really
hard,
I,
don't
know
if
that's
a
battle
worth
fighting
anymore.
D
So
my
understanding
now
is
no
I
understand
gender.
You
would
really
like
to
get
a
list
and
have
it
approved
by
PMC
that
this
will
most
likely
evolve.
Organically
I
think
that
having
the
current
list
as
it
is
with
the
8
issues
is
a
good
sort
of
like
controllable
number
of
issues,
and
then
we
have
this
pool
of
30
issues
and
at
some
point,
if
anyone
wants
to
work
on
any
of
these
can
come
on
Gator
and
say:
look
I
have
some
capacity
I
want
to
grab
one
of
the
issues,
I
don't
know
which
one?
A
Not
sure
they're
real
either,
though
okay,
just
like
we
remove
tabs
from
user
to
log
in
register,
saying
like
there's
the
there's
stuff
here
that
hasn't
gone
through
the
process
of
like
being
a
candidate
and
being
approved.
It's
just
in
like
and
there's
things
that
have
been
like
bumped
and
bumped
in
bump,
so
I
think
maybe
aren't
aren't
there
are
these
I
don't
know
I.
C
A
A
A
But
the
problem
is
like
so
before:
when
it
organically
happened,
we
ended
up
with
so
much
stuff
in
the
milestone
that
we
didn't
actually
have
a
priority
anymore.
It's
just
like.
Oh
there's,
another
100
issues
here
whatever
so
we
can
anyone
add
whatever
they
want
to
the
milestone.
Okay.
Well,
let's
let
anyone
add
whatever
they
want
with
this
label,
you
can
use
the
label,
it
adjusts.
It's
in
the
mountain.
E
E
D
Like
all
those
ideas,
but
I
would
love
so
like
two,
because
we
seem
to
be
stuck
try
to
understand
what
is
the
problem
that
we're
trying
to
solve,
and
my
understanding
was
that
the
problem
was
that
people
that
wanted
to
contribute
came
to
the
issue
queue
and
they
didn't
know
which
ticket
to
grab.
Was
that
bless?
You
is
that
the
issue
that
we're
trying
to
show
that
no.
A
Are
we
gonna
tell
people
what's
in
that
release
ahead
of
time,
and
then
are
we
gonna
work
to
make
those
things
happen
like
do
we
have
a
direction
or
are
we
just
like?
Well
we'll
see
what
we
have
in
four
months,
and
so
we've
been
trying
to
have
a
direction
and
it
changes
a
lot
which
I
think
is
fine,
but
I
think
it
is
I,
don't
know.
Maybe
it's
not
helpful,
but
I
think
it's
also
feel
like.
G
It's
a
little
bit
about
just
having
some
focus
on
some
issues
that
we
think
will
have
the
most
impact.
We
obviously
can't
tell
people
what
they're
gonna
work
on
a
knob
right.
We
can't
shake
it
completely,
but
I
think
we've
run
into
the
situation
right
or
we
say
hey.
This
would
be
really
cool.
We
should
all
work
on
this
and
then
a
week
later,
somebody
starts
home.
Let's
work
on
X
and
the
detention
G
shifts
right
because
it's
just
so
fluid
and
the
thing
that
a
couple
weeks
ago
was
a
priority.
G
Or
no
I
mean
I
sort
of
agree
with
you,
but
I
think
there
are
things
we
could
do
to
moderate.
That
right,
like
one
of
the
ideas,
is
if
this
whole
idea
of
having
an
advocate
was
right.
If
we
identify
six
or
eight
things
and
we
assign
somebody
to
sort
of
hey,
your
job
is
to
kind
of
keep
some
attention
on
this
issue.
I
think
that
could
counteract
you
know
if
we
can't
prevent
the
sudden
shift,
but
we
can
put
some
things
on
right.
D
G
I
think
that,
similar
to
what
I
got
in
my
graduate
was
that
yeah
it
was
that
sort
of
like
each
person
person
helped
something
that
they
kind
of
advocate
for
so
you
have
40.
You
have
40
issues,
this
big
one
but
I
mean
sure,
but
I'd
like
for
me,
I'd,
be
willing
to
advocate
for
an
issue,
but
I
I
would
love
input
on
which
one
you
guys
think
I
should
advocate
for
it
right.
A
And
I
think
we
can
also
like
kick
that
to
the
pmc
and
be
like
hey.
We've
got
these
five
people
working
on
these
issues
that
they're
super
passionate
about.
Is
this
cool
with
you
and
long
as
they
don't
say?
No,
then
that's
fine,
but
that
way
there
isn't
someone
who's
like
I'm
gonna
push
really
hard
on
want
issue
that
I
believe
it's
important
that
we
don't
think
is
a
match
for
our
audience
and.
D
C
C
G
D
A
D
E
D
E
E
D
G
Right
I
think
we
all
have
the
ability
to
like
just
pick
up
an
issue
right
now.
Right
part
of
the
goal
is,
is
to
have
some
group
influence
on
what
those
issues
are
that
we're
advocating
for
without
you
know,
hoisting
it
on
anybody
right,
it's
the
ability
for
us
as
a
group
to
say
hey.
We
would
really
like
somebody
to
step
up
and
advocate
for
this,
and-
and
we
haven't
solved
that
right,
it's
like
I'm,
not
actually
gonna
work
on
an
issue.
G
I'm
gonna
advocate
for
one
and
I'm
gonna
try
and
get
other
people
involved
and
make
sure
it
gets
done,
but
I
really
that
sort
of
the
goal
here.
I
could
just
pick
one
sure,
but
my
goal
was
like
I
want
to
know
what
what
where
I'm
put
it
most
best
using
my
time
and
I
want
your
input
for
that.
So
how
do
I
get
that
input?
How
do
how
do
you
guys
help
me
decide
which
ones
I
should
advocate?
Is
that
sort
of
what
you
were
getting
at?
That.
B
B
A
F
D
D
D
A
D
A
D
Like
we
know
that
what
the
status
of
it's
sort
of
a
complicated
issue
is
at
each
point,
sort
of
like
a
meta
issue,
there
is
a
milestone
and
underneath
it
we
have
the
tasks
which
is
the
priorities.
Then
people
can
comment
on
that
dish
and
say:
look
I
need
I,
think
that
this
should
be
added
in
the
priorities
or
bit
should
be
removed
either
because
I'm
working
on
it
or
because
I
was
assigned
and
I
look
at
it
now.
D
A
So
I
think
I
think,
like
the
weather
and
issues
actively
being
worked
out
or
not
should
determine
what,
whether
it's
in
the
114
milestone
or
the
next
milestone
or
not.
And
so,
if
you
were
an
advocate
for
an
issue
and
it
didn't
get
done
and
you're
still
two
months
out
from
release.
But
you
know
that
you're
not
gonna
have
time
to
work
on
it
in
the
next
two
months.
You
should
remove
the
milestone
and
add
a
comment
saying
it.
I'm
not
gonna,
be
able
to
advocate
for
this
thing,
where
I'm
moving
to
Moscow.
D
G
If
I
understand,
where
we're
at
right
now,
it
sounds
to
me
like
there's
a
general
consensus.
This
idea
of
having
an
advocate
for
issues
still
sort
of
make
sense.
Yeah
yeah
is
the
idea
right
now
that,
in
order
to
be
a
milestone
or
no
a
milestone
issue
that
it
means
an
advocate,
so
we
basically
have.
However,
many
issues
on
the
milestone,
as
we
have
advocates,
is
that
kind
of
where
we're
at
yeah.
E
D
D
Issue
I
would
still
like
issues
not
to
be
removed
from
the
or
the
tides
better,
the
milestone
candidates
not
to
be
removed,
but
if
these
are
to
be
prioritized,
then
we
should
like
the
idea
of
having
an
advocate
sounds
good
to
me.
So
we
need
to
denote
which
issues
have
advocates
and
which
do
not.
But
we
do
not
necessarily
need
to
tie
that
to
the
milestone
candidate.
No,
but
if
an.
A
Here's
here's
what
I've
been
doing
and
this
might
solve
the
problem
was
like
any
time,
I
remove
anything
from
a
milestone.
I've
been
adding
the
milestone
candidate
label,
so
it's
still
in
a
list
of
like
these
are
things
that
are
high
priority.
But
my
learner's
like
these
are
the
issues
that
are
gonna
be
closed
before
the
next
release.
So
no
Precure
an
issue
is
not
going
to
get
closed
for
the
next
release.
A
It
should
come
out
of
that
list,
but
being
in
the
mouths
of
candidates,
list
still
puts
it
in
a
pool
of
stuff
where
it's
like.
Hey.
Are
you
looking
for
something
to
be
an
advocate
for
here's?
Our
issues
that
you
know
our
community
generally
thinks
are
high
enough
priority
that
they
should
have
this
label.
We
already
have
a
process
for
that
I'm
completely
against
the
has
advocate
label,
but
I
feel
like
this
yourself.
Trying
to
solve,
isn't
really
a
problem.
I
just
want
to
get
to
the
bottom
like
what
the
real
problem
is.
The
original.
D
B
So
maybe
even
narrow,
maybe
would
be
more
like
the
like.
If
we
said
like
on
the
roadmap
that
we
were
going
to
have
like
layout,
enhancements
or
self
updates,
or
media
management
improvements,
yeah
I
think
it
would
be
at
that
level,
not
at
d
like
it
was
or
I
don't
know,
because,
because
some
of
these
things
are
really
probably
media
management
like
that,
then
the
Advocate
might
not
be
interested
in
like
feel
double
files,
but
they
might
be
interested
in
improving
the
file
browser
or
something
I
thought
already
image.
B
Browser
I,
don't
yeah,
not
an
easy
entry
like
each
individual
issue.
Some
of
these
issues
are
too
granular,
though,
like
if
you
said
that
advocate
could
only
have
one
issue
per
milestone.
You
know
I
could
pick
with
big
meaty
key
and
pick
emitter,
yeah
yeah,
it's
what
yeah.
That's
not
a
theme,
it's
more
like
at
the
metal
level
that
we're
talking
about.
A
D
A
B
G
What
can
you
do?
Yeah
I
like
where
this
is
going
but
I
think
it's
a
different
issue
or
it's
a
whole
different
concept,
right,
yeah,
the
advocating
for
a
specific
issue
in
advocating
for
a
meta
like
topic,
yeah,
really
different
things
and
I'm
afraid
we've
just
shifted.
The
topic
too
far
like
I,
would
propose
that
we
not
abandon
that
idea,
but
maybe
we
try
an
advocate
for
an
individual
issue
for
one
release
and
revisit
it
like
at
the
next
release
and
say:
was
this
too
narrow
and
should
we
expand
it?
Yeah
I'm.
E
E
Just
don't
think
we
have
enough
people
adding
more
labels
to
the
people
that
we
have
here
so
you're
going
to
develop
a
PMC
chair,
The,
Advocate,
personalized
blogs,
I
mean
all
of
us.
Have
lots
of
things
already
add
another
label
I,
don't
think
it
helps
it's
a
good
idea,
but
I
just
don't
think
it
helps
in
our
situation.
It
just
adds
another
level
of
another
layer
complexity.
D
So
the
Advocate,
the
idea
is
that
the
Advocate
would
not
be
a
blocker.
It
would
be
a
person
that
has
more
time
available,
but
not
necessarily
the
skills
to
do
the
work
so
he's
there
to
help
the
person
who's
actually
working
on
the
issue.
If
they
happen
to
be
the
same
person,
yeah
okay,
then,
but
usually
would
be.
For
example,
team
wants
to
push
for
a
specific
issue,
and
then
you
are
working
on
it
and
then
you're
blocked.
D
G
Can
see
that
Wilma,
where
it
might
not
affect
you
so
much?
You
might
feel
like
this
doesn't
really
change
anything
because
you
are
already
bet
deep
in
an
issue
for
me.
It
feels
like
that
gives
me
a
place
to
hook
the
end
of
the
process.
More
so
I
think
it's
more
helpful
for
me.
I
could
also
see
if
we
have
concerns
about
this
sort
of
testing
this
with
just
a
couple
of
advocates
this.
You
know
you
know
just
trying
a
couple
of
it.
You
know
like
it.
We
don't
have
to
all
be
advocates.
G
D
G
G
G
Things
tied
together
is
that,
like,
for
example,
you
might
have
something
that
you
think
is
a
priority
or
that
you're
gonna
work
on
anyways
right
and
you
might
not
care
whether
you're
an
advocate
or
not.
The
only
reason
that
naming
you
the
advocate
would
be
helpful
to
the
rest
of
us
is
then
I
know
I
can
focus
on
something
else,
so
it
might
be
fairly
meaningless
to
you.
But
if
you
said,
hey,
I'm
working
on
X
anyway,
so
I'll
just
call
myself
the
Advocate.
G
A
Also
feel
like,
if
we
end
up
choosing
three
issues
any
that
you've
already
like
put
a
lot
of
time
in
then
you
might
accidentally
being
anything
that
you
give
all
three
of
them,
but
like
I,
don't
have
one
that's
assigned
to
me
right
now,
so
maybe
I'll
be
like
okay.
Well,
you
know,
would
you
rather
work
on
the
flexible
layout
builder
or
the
field
whole
file,
entity,
bundles?
And
if
you're
like
flexible,
a
builder
he'll
be
like
okay,
then
I'll
go
work
on
final
editing,
bundles,
so
something
like
that
could
be
helpful.
G
Anyways
right
so,
if
I
were
to
pick,
one
I
would
want
some
impact
like
what
is
where
can
I
put
my
effort,
so
it's
gonna
have
the
most
impact.
Where
are
you
not?
You
know?
Where
are
other
people
not
working?
You
know,
I
have
I
think.
If
we
just
looked
at
the
list
right
I
would
look
at
things
that
I
know
because
I
feel
like.
If
I
am
damn
them,
you
know
getting
back
up
and
migrated
into
core
I.
Don't
know
how
complicated
that
is.
G
G
D
Now,
with
the
implementation
of
by
default,
you
know
allowing
core
updates
I,
think
that
we
have
consensus
will
be
on
the
merge
all
the
update
core
module
thin-layer,
the
issue
2714.
Would
that
be
something
that
you
understand
anything
then
I'm?
Sorry
I
didn't
quite
get
that
to
the
core
updates.
Say
it
again,
so
we
now
with
this
release,
we
have.
D
We
enable
a
core
updates
by
default
and
we
agreed
that
now
it
gets
more
confusing
the
fact
that
we
have
a
separate
update
pages
for
modules
for
things
and
for
layouts
and
we
decide-
and
now
we
have
core
listed
on
all
of
these,
so
we
have
decided
to
move
all
these
things
and
consolidate
them
in
a
single
page,
single,
updated
page.
If
you
would
like
okay.
G
D
It
also
includes
modules
that
you
can
update
and
now
core
as
well
yeah,
and
then
you
see
the
same
page
if
you
go
to
functionality,
update
modules
and
if
you
go
to
layouts
update
layouts,
you
also
see
the
same
thing
so
they're
supposed
to
be
separate
could
pages
for
separate
things,
but
they
display
the
same
thing.
So
we
decided
to
move
it
to
a
single
place,
consolidate
it
and
have
a
single
page
where
everyone
in
the
update
sort,
when
when
someone
can
update
everything
right,
I.
G
Think
one
of
the
tricks
in
picking
out
these
issues
is
to
pick
something
that,
like
I
kind
of
want
to
get
excited
about
an
issue.
That's
like
something
we
can
sell
like
bringing
backup
and
migrate
into
core
I'm,
just
not
much
paper.
It's
not
necessarily
my
favorite,
but
it's
like
something
really
solid
and
I
could
say:
wow
I
accomplished
that
and
an
issue,
that's
just
sort
of
fixing
something
that
we've
already
done
might
be
important
and
if
so
then
I'm
happy
to
do
it.
But,
okay,
no
it's!
G
A
That's
not
necessarily
worry
about.
You
know.
Choosing
these
right
now,
Tim
will
give
you
a
chance
to
read
over
that
issue
and
see
if
it's
something
excites
you
or
not,
and
if
not
it's
fine,
if
you
don't
advocate
for
it
all
right,
but
there
are
two
things
and
I
saw.
Another
thing
is
like
I,
don't
know
how,
like
the
two
things
that
I'm
most
excited
about
issues
that
put
a
ton
of
time
into
so
that
how
do
we
decide
like
do
we
fight
over?
Who
gets
to
be
an
advocate
or
something
I,
don't
know.
D
Team
just
to
make
your
life
a
bit
easier.
If
you
want
to
choose
issues,
it's
like,
if
you
go
to
the
milestones,
yeah
and
then
also
that
month,
milestone
candidate,
you,
you
can
feel
there
by
the
ones
that
also
have
the
tag
feature
request
please
these,
because
these
are
things
that
are
new
and
exciting
right.
The
other
ones
that
are
tagged
as
documentation
or
tasks
is
clean
up
things
yeah.
So
maybe
that's
another
way
for
you
to
filter.
G
A
Guys
we're
gonna
pending
out
of
time,
can
I
recap
what
I
think
we've
decided
just
to
make
sure.
So
what
we're
gonna
try
and
do
is
make
sure
that
all
the
issues
that
are
in
the
114
milestone
have
an
advocate,
and
if
you
find
an
issue
that
you're
really
passionate
about-
and
you
want
to
advocate
for
it,
you're
gonna
like
add
a
comment
on
the
issue.
If
you
like
I,
want
to
advocate
for
this
issue,
make
sure
nobody
else
wants
it
more
than
you
and
then
you
can
add
them.
A
It
has
to
be
already
tagged
with
a
milestone
candidate
label,
but
then
you
can
move
it
into
the
114
your
milestone.
If
you're
its
advocate
okay,
we
should
document
that
just
that
part,
we
finally
figured
out
I'll
write
that
up
and
how
to
use
the
issue
queue
section
of
the
website
and
then
let's
try
this
for
a
while.
A
We
can
get
that
that
milestone
in
an
issue
for
the
PMC
and
just
say
like
this
is
what
we're
doing
stop
us
if
it's
wrong
and
then,
if
there's
anything,
they
want
us
to
focus
on
well
have
them.
Let
us
know
what
it
could
be,
something
meta
like
upgrading
from
Drupal,
7
or
media
or
whatever,
but
well
is
to
give
them
a
chance
to
weigh
in
on
it.
D
A
G
C
E
We
leave
it
to
all
of
us
nothing
going
to
be
priority.
This
is
why
I
knew
it
might
be
useful.
If
we
we
have
a
leadership
team
BMC
we're
not
asking
them
to
decide.
This
is
what
we're
going
to
do
and
that's
it.
It's
not.
You
know
it's
not
the
operator
for
coz.
You
will
be
useful
if
from
their
knowledge
as
the
senior
developers
and
people
who
have
experience
in
these
things,
if
you
look
through
all
the
issues
are
not
necessarily
the
issues,
but
the
topics
are
getting
the
groups
of
things.
E
E
Do
that
then
maybe
the
advocacy
plan
might
be
more
helpful.
Then
we
can
say
okay,
we
can
get
an
advocate
for
this
one
thing,
because
the
PNC
has
said
it's
important
to
us.
Yes,
otherwise,
everyone
is
still
going
to
take
one
of
the
thousands
of
issues
to
be
an
advocate
for
which
may
not
necessarily
be
a
priority
and
the
end
with
the
end
up
of
thousands
of
mast
on
candidates.
A
Another
important
separate
thing
that
we
need
to
go
to
the
PMC
and
say:
hey:
we
just
did
a
release.
What
do
you
think
our
priority
should
be
mm-hmm
lord,
give
us
a
list
and
one
that's
somewhere,
so
that
when
people
are
trying
to
decide
which
is
used
to
be
an
advocate
for
they
can
compare
to
that
list
and
say
PMC
says
mean
we
work
on
media,
so
I'm
gonna
pick
a
media
issue,
something
like
that.
All.
D
D
B
D
B
D
Can
I
propose
the
final
thing,
then
we
ask
each
member,
although
it
might
seem
a
little
bit
oligarchy.
We
are
state
member
of
the
PMC
to
pick
up
an
initial,
so
we
have
only
six
members
of
the
PMC
right
now
or
eight.
How
many
are
we
six
and
six
so
we'll
have
six
issues
there
are
priorities.
Is
that
fair
enough
do.
D
G
D
E
Maybe
I
don't
I,
don't
think
it
needs
to
be
one
issue
for
PMC
member
per
se,
I
think
if
the
PMC
sits
down
and
decides
that
listen
based
on
our
research
on
WordPress
drupal.
You
know
this
particular
issue,
or
these
three
should
be
focused
on
for
the
next
four
months
in
order
to
make
backdrop
competitive,
and
that
would
not
be
a
useful
guidance
for
us.
It
doesn't
have
to
be
six
if
all
six
of
them
agree
that
this
one
thing
or
these
two
things,
that's
what
we
should
be
focused
on.
D
A
F
A
C
A
D
B
D
A
D
A
D
All
right,
so
this
is
the
last
thing
that
I
want
ask
for
the
day
and
ask
for
any
ideas.
So
the
back
book
that
saw
it
across
sports
try
a
cross
watch
from
various
modules
like
views.
We
are
quite
behind,
so
I've
done
some
work.
We
have
the
list.
This
is
a
problem
with
which
I
need
helpful
ideas,
which
we
have
a
list
of
the
commits,
and
then
we
have
them
as
check
boxes
and
usually
in
the
mirror.
D
Issues
that
set
box
means
that
it
has
been
merged
because
I
don't
want
a
file
like
might
be
twenty
or
thirty
five
commits
we
don't
have
one
a
file
separate
issues
for
those.
How
can
we
sort
of
like
have
a
way
to
also
have
a
second
tick
box
against
each
one
of
these?
That
people
can
come
and
say,
I
reviewed
those.
A
So
the
way
that
we
did
this
in
the
past
was
you:
can
you
don't
have
to
have
a
separate
pull
request
for
each
issue?
I
mean
if
you
want
to
do
that.
That's
fine,
but
I
used
to
do
like
ten
at
a
time
and
then
that
one
issue
would
get
like
reviewed
reverted
with
you,
Bergen
and
until
all
of
the
problems
in
that
one
poor
request
for
results.
So
there
could
be
problems
with
three
of
the
patches
I
applied,
but
I
would
it
would
just
all
be
one
for
West
when.
A
A
D
B
I
don't
know
yeah
it's
alright,
it's
been
working,
okay,
it's
just
a
comment.
Saying
I
root
like
herb
dual
comes
in
and
says
are
DBC
and
then
he's
the
pole
request
number
or
you
know,
and
and
then
the
is
the
overall
issue
that
contains
all
of
the
all
of
the
port
links.
All
of
those
links
to
the
pr.
The
overall
issue
stays
at
the
highest
level
of
its
pole
requests.
So
if
there's
a
rate
RIT
our
TBC
pull
request,
the
whole
thing
is
our
TBC
and
then
they'll
get
moved
back
down
to
needs
review.
D
B
D
D
D
Just
just
to
sort
of
like
give
some
sort
of
confidence,
most
of
them
are
like
straight
ports,
just
the
functions
that
changed
on
our
end
and
and
some
of
them
have
been
committed
to
use
for
like
years
yeah
yeah
I
saw
it
there
tested
once
we
reach
the
most
recent
ones.
Maybe
then
we'll
be
sort
of
like
that's
untested,
and
the
reason
why
I
break
this
up
is
that
it's
not
just
the
views
mojo.
If
there's
other
things
that
we
brought
to
coresight,
we
need
to
get
done
with
that.
D
So
we
keep
it
to
a
sort
of
like
a
level
of
control
that
there's
less
sort
of
like
less
less
backlog,
Yamit
and
then
the
view
specifically
has
caused
there's
other
issues.
That
sort
of
like
the
pent
like
we're
wondering
is
that
because
we
don't
have
priority
like
is
it
happening
on
view
7?
Why
it's
not
happening
there
and
it's
happening
with
us?
No
yeah
I
mean
speaking
of
focusing
direction.
I
know
that
we
are
excited
about
new
features,
but
this
is
something
that
needs
to
happen.
Yeah.