►
Description
Today’s development agenda: http://bit.ly/2hXvirC
A
A
A
Should
we
look
at
the
list
of
things
that
are
currently
tagged
for
16
and
see
if
there's
anything,
we
should
like
prioritize
and
work
on
in
the
next
few
days,
so
I
didn't
have
anything
you're
already
working
on
you
want
help
with
I
am
working
on
renaming
view
modes
to
display
modes,
which
I
think
is
not
super
critical,
but
I
would
love
to
do
it
just
because
we
put
that
view
modes.
You
I
on
the
manage
displays
page
I,
think
it'll
make
more
feed
more
sense
to
people
with
to
manage
this
place.
A
Page
is
managing
display
modes,
but
there
is
going
to
be
a
inconsistency
there
between
the
code
or
the
code
everywhere
says
view
underscore
mode
in
the
you
idleness
a
display
mode,
but
there's
also
a
ton
of
code
comments
in
all
the
code
everywhere.
It
refers
them
as
view
mode.
So
if
that
pull
request
gets
in
it'll
change,
like
the
ducks
will
say
like
update
the
display
mode
and
the
club
will
save
you
mode,
so
I
think
we'll
be
pretty
clear
to
developers
what
they're
working
with,
even
if
they
haven't
seen
it
before.
A
So
that's
how
I'm
working
on
today,
no
I
don't
know.
Would
you
talk
about
one
of
the
things?
Maybe
we
should
talk
about.
Is
this
issue
that
doc
Wilma
opened
this
issue
number
three,
a
22
in
the
vector
of
CMS
or
q,
and
he
brought
up
the
same
thing
that
we
talked
about
no
no
two
months
ago
or
something
about
how
to
restructure
our
weekly
meetings
to
try
and
get
the
most
out
of
it.
A
There
are
a
lot
of
people
that
commit
this
hour
on
Thursdays
to
working
on
backdrop
and
I
would
love
it
if
we
could
kind
of
make
the
most
of
this
time.
The
weekly
meetings
do
tend
to
get
a
little
repetitive,
especially
if
we
talk
about
each
thing
like
each
issue
every
week.
If
we
explain
what
they
are,
I
think
that's
not
necessary
because
most
of
the
people
who
are
in
here
and
a
lot
of
people
who
watch
the
video
have
seen
a
week
before
I
know
we're
talking
about.
So
I
would.
A
I
would
like
to
not
talk
each
bullet
point
to
death,
but
I
also
think
that
it
would
be
good
if
we
can
find
a
way
to
better
organize
what
those
low
points
are
to
make
the
best
use
of
our
time.
So
I
don't
know
what
you
guys
want
to
do
this
week.
We
have
a
milestone
for
153.
That's
like
a
handful
of
bug
fixes.
None
of
them
are
super
important,
but
if
any
of
them
to
get
in
that
would
be
great
and
we
have
a
much
another
milestone
for
16.
A
That's
just
a
bunch
of
user
experience.
Improvements
that
I
think
click
in
at
any
time
would
be
great
if
we
could
list
them
as
things
that
got
into
16.
But
if
they
don't
it's
not
that
the
world
I,
don't
know
that
it's
necessarily
worked
worth
talking
about
any
one
of
those
particular
issues
in
this
meeting,
unless
you
guys
want
to
so
I'm
open
to
the
background,
what
would
be
most
beneficial
or
here's
a
better
question?
Why
are
you
guys
here?
What
are
you
hoping
to
get
out
of
this
meeting?
C
B
A
What
audiences
are
we
hoping
to
serve
and
are
they
getting
features
they
need,
and
one
of
the
things
he
mentioned,
that
he
found
was
frustrating
as
a
developer
is
not
getting
poorer
quest
reviews
fast
enough,
and
I
think
that
there's
a
couple
of
reasons.
That
is
our
bottleneck
and
it's
because
not
very
many
people
do
them,
and
I
know
I
personally
am
guilty
of
not
doing
for
crestor
abuse,
because
I
feel
like
I'm
really
bad
at
it
like
I.
Don't
like
I
can
do
a
code
of
you
like.
A
Oh
you
forgot
a
tea
function
here
whatever,
but
that,
like
I,
don't
feel
like
that's
always
necessarily
enough.
Like
there
I,
don't
I,
don't
know,
I
just
feel
like
I'm
really
bad
at.
It
will
be
great
to
get
I,
don't
know
if
any
of
you
feel
like
you're,
have
experience
in
that
area
and
could
help
like
maybe
write
some
documentation,
some
like
how
to
write
a
valuable
review
or
if
we
could
find
something.
Maybe
there's
something
like
that
already
exists
for
Drupal.
We
could
rework
from
app
attribute.
A
Oh
poor
quest,
review,
I,
think
that
would
help,
because
right
now,
the
only
person
that
is
really
good
at
doing
for
a
question
doesn't
or
for
best
reviews
and
doesn't
malin
time
as
neat,
and
he
is
a
little
bit
of
bottleneck
because
he
does
it
at
thee.
Is
it
ready
to
merge
point
and
every
time
something
doesn't
get
reviewed
until
it's
pretty
to
merge?
A
Now
you
can
go
write
another
one
where
I
feel
like
I.
That's
that's
something
that
I
would
love
to
get
more
people
on
board
of
doing
I,
especially
think
that
if
we
can
get
some
clear
documentation
around
how
to
do
might
be
able
to
get
you
are
people
doing
it
too
or
you
don't
feel
like
you
need
to
know
all
the
systems.
A
D
A
Getting
good
at
that
about
a
week
ago,
I
also
noticed
the
clonus
was
self
assigning,
thinks
and
I'm
like
wow.
That's
so
handy
you
can
look
at
the
issue
queue
and
see
what
these,
where
I
should
do
that?
Okay,
but
yeah.
That's
also
super
useful
because
it
like,
if
there
are
six
of
us
and
we're
all
like
what
do
we
work
on,
and
we
want
to
look
at
the
issue
queue.
It
takes
something.
No
one
else
is
working
on.
A
It's
pretty
easy
to
say:
oh
clonus,
working
on
that
and
work
on
another
one
and
then
unexciting
yourself
when
you're
done
so
like
if
you're
doing
a
review,
you
take
it
a
new
review
in
and
you
untag
it
and
then
someone
else
might
give
it
another
view
or
work
on
it
or
whatever.
So
that's
a
great
idea,
assigning
I
also
think
like
one
of
the
things
that
both
claw
nose
and
Jack
Lemmon
are
having
trouble
with
this
like
when
you're
working
on
something.
That's
not
super
important.
How
do
you
give
it
attention
right?
A
Like
it's
easier
experience,
improvement?
It's
not
really
a
bug
should
it
be
assigned
to
the
153
milestone
or
not
where
it's
a
really
quick
fix,
and
if
people
are
like
yes,
this
is
good.
You
could
get
it
in,
but
if
you
nobody's
looking
at
it
because
it's
not
in
the
milestone,
you
can't
get
it
in.
So
it's
stuff
like
that
I
think
people
are
struggling
with,
but.
D
D
A
How
do
you
gauge
priority
of
things,
because
right
now,
I
think
we're
using
the
milestone
for
that,
so
that
if
the
milestone
gets
cluttered,
the
priority
gets
lost
and
I
think
that's.
Neat
has
been
doing
like
you've
been
looking
at
the
pull
request
it
q,
rather
than
the
issue
queue
and
looking
for
things
that
are
in
like
need
to
review
status
or
ready
to
be
committed,
status
and
I.
A
Think
that
that's
good,
except
for
that,
then
there
are
things
that
are
more
important,
that
maybe
aren't
getting
the
attention
they
need,
because
they're
always
in
needs
work,
but
then
they
get
overlooked
because
I
don't
know,
I,
don't
know.
If
we
have
a
good
way
of
solving
this
problem,
we
don't
really
have
great
tags
tagging
ability
a
week.
That's
a
thought
to.
D
Yeah
Brian,
you
can
filter
the
issue
queue
by
things
that
are
tagged
for
153
and
things
that
need
review
and
or
things
that
have
a
pull
request.
So
if
you
want
I
put
a
link
in
there,
that's
pre-filtered
to
153
and
needs
your
view,
so
you
can
click
on
that.
That's
a
pre
filtered
list!
If
you
lurkin
x,
yeah,
if
you
can
review
some
of
those
that
would
be
super
helpful
and.
A
Great
well
I
think
that
this
is
kind
of
the
same
problem
we
had
two
months
ago
and
we're
like
we
know
we
need
to
change
the
structure
weekly
name,
so
we
don't
know
how
to
do
it.
I
would
love
to
try
something
different
after
back
to
16
is
out
I
feel
like
it's
a
good
time
like
we
are
gonna
have
any
looming
deadlines
urgently.
A
D
A
So
I'll
create
a
draft
of
next
week's
agenda
and
I'll
put
people's
names
on
there
and
we'll
see,
and
that
way
if
people
want
to
talk
to
those
issues
so
know
ahead
of
time,
and
if
there
are
issues
we
don't
know
who
it
is
until
we
can
figure
out
who
to
do
that
meeting
and
then
they'll
happen
against
notice
for
the
next.
So
it's
a
good
idea.
A
Well
time
box
is
a
half
an
hour,
I'll
shorten
that
google
calendar
invites
to
half
an
hour
and
we'll
just
have
to
be
really
good
about
like
if,
if
we
start
having
a
good
conversation
will
say,
this
is
a
good
conversation
we're
going
to
wait
till
later,
and
then
we
can
put
that
in
the
notes.
The
bottom
of
the
agenda
like
this
is
what
we're
going
to
talk
about
after
reporting
in
sir
whatever
so
we
just
have
that
documented
to
okay.
Was
there
anything
else
you
guys
want
to
talk
about
today.
A
So
when
I
wanted
a
cool,
so
today's
focus
was
supposed
to
be
on
what
we're
doing
for
a
backdrop
16,
which
is
basically
just
a
blog
post
in
the
letter
and
I
talked
to
Tom.
Thank
you
come
into
writing
writing
my
blog
post
and
then
we're
going
to
send
that
over
to
fast
interactive,
to
send
it
out
as
our
newsletter
for
us
and
hopefully
they'll
be
able
to
manage
our
newsletters
going
forward,
which
is
fantastic
and
yeah,
there's
a
whole
bunch
of
other
stuff.
A
We
need
to
do
regarding
outreach
to,
but
we
didn't
talk
about
this
week
and
I.
Think
yeah
I,
just
trying
to
figure
out
how
to
prioritize
and
get
that
stuff
done
is
also
something
that
we're
not
very
good
at
I
would
love
it
if
we
get
more
help
in
that
area.
This
was
something
my
brain
is
really
well
and
I
know
it
I
know,
but
I
was
also
thinking
I'm,
like
that,
my
maybe
and
we'll
get
it
that's
interactive
to
help
with
two.