►
From YouTube: YUI Open RoundTable April 18 2013
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
everybody
to
the
latest
yui
open
round
table
for
april
the
18th
we
have
with
us
several
members
of
our
team,
derek
jenny,
jeff
and
tony,
and
we
kick
things
off
with
looking
at
the
roundtable
topics.
We've
got
a
number
of
items
for
discussion
and
then
we
also
can
go
over
our
pull
request
and
unassigned
bugs
in
terms
of
the
order
we
can
go
into
whatever
order.
I
know
jenna,
you
have
two
items
that
you.
C
Sure
all
right,
so
we
ran
into
something
in
our
contributor
model
that
I
just
wanted
to
throw
up
for
discussion,
and
then
we
can
finalize
on
the
contrib
mailing
list
after
our
discussion
here.
So
in
the
contributor
model,
we
specify
that
there's
like
a
72-hour
window.
After
a
pull
request
comes
in
and
if
it's
from
a
committer
after
72
hours
passes,
it
will
just
be
auto
merge.
This
is
the
lazy
consensus
model.
C
So
the
idea
is
that
an
objection
can
block
the
submission,
but
if
no
one
objects
that
it
should
just
be
allowed
to
be
part
of
the
code
base,
which
is
great
and
that's
that's
what
we
want.
The
point
of
clarification,
however,
is
if
a
reviewer
gives
a
thumbs
up.
Does
that
indicate
a
shortcut
to
merging
right
away,
or
do
we
want
to
leave
that
72
hour
window
open
and
the
last
time
we
talked
about
it?
C
I
forget
if
it
was
during
a
hangout
or
just
at
the
water
cooler
or
something,
but
the
last
time
we
talked
about
it.
We
thought
that
72
hour
window
is
great
to
leave
open
because
it
allows
for
people
in
different
time
zones
or
people
who
are
working
on
other
things
gives
them
a
bigger
window
to
look
at
the
submission
and
provide
an
objection.
C
If,
if
that's
you
know
what
they
would
like
to
do,
so
we
decided
that
you
know
in
the
contributor
model.
It
says
specifically
if
a
reviewer
gives
a
thumbs
up,
that
could
shortcut
the
72-hour
window
at
the
reviewer's
discretion,
which
kind
of
is
vague
but
implies
the
reviewer
needs
to
say
thumbs
up,
feel
free
to
merge
it
in
right
away.
C
Now
this
actually
came
up
in
a
practical
way
earlier
this
week,
where
we're
kind
of
in
a
shortened
timeline
where
we
want
to
get
to
the
end
of
the
cycle
to
release,
and
we
do
want
to
merge
things
in
right
away
if
there
is
really
no
objection
to
it,
and
so
you
know
in
practicality,
it
felt
like.
Oh,
this
got
a
thumbs
up
from
dave.
I
think
what
that's
implying
is
that
it's
good
to
merge
right
away,
but
you
know
do
that.
C
Is
in
essence
the
same
thing
as
giving
a
thumbs
up
and
forcing
that
72-hour
window
to
remain
open,
so
in
the
in
reality,
what
it
comes
down
to
is,
if
a
reviewer
objects
to
something
they
should
just
outright
object,
and
then
it
won't
get
merged
in
further
discussion
will
ensue
if
a
reviewer
gives
a
thumbs
up.
It
should
just
mean
that
you
know
someone
at
the
reviewer
status
likes
what
they
see.
C
All
they
can
review
and
then
neither
thumbs
up
nor
object,
that's
the
same
thing
as
not
objecting
and
leaving
the
72-hour
window
open.
So
I
don't
know
how
clear
that
was.
Hopefully
I
can
summarize
with
the
degree
of
clarity
in
the
email
I'd
like
to
follow
up
with,
but
I
just
didn't.
I
wanted
to
throw
that
out
there
for
discussion.
A
C
A
pulse
check
see
if
other
people
agree
that
that
sounds
reasonable
and
then
make
that
amendment
to
the
contributor
model
so
that
a
thumbs
up
means
shortcut
to
merge,
looks
good
to
me
from
the
reviewer
level
and
then
objection
means
objection
need
to
discuss.
Does
anyone
have
any
thoughts
either
way.
A
D
A
So,
just
to
play
devil's
advocate
what
matt
was
saying
when
we
had
this
discussion.
Was
he
felt
like
that
short
circuiting?
The
72
hour
window
should
be
a
exception,
as
opposed
to
the
rule,
so
it
sounds
more
like
he's,
I
think
he
would
be
in
compliance
with
your
alter
alteration
of
this,
where
a
thumbs
up
would
still
be
a
short
circuit,
but
no
response
would
just
be
keep
thinking
I'll,
follow.
B
C
C
C
Yet
I
want
to
leave
this
before
requested
and
get
a
little
more
feedback.
So
for
that
reason
the
person
who
issued
the
request
is
the
best
person
to
merge
it
in
after
a
thumbs
up.
So
I
would
just
like
to
clarify
that
that
that's
the
expected
practice
that
for
committer
after
you
get
the
thumbs
up,
it's
at
your
discretion
when
you
merge
it
in,
but
you
can
merge
it
in
right
away
as
soon.
C
F
B
So
what
I've
seen
is
generally
a
reviewer
will
will
give
a
thumbs
up
or
you
know,
have
a
problem
and
ask
for
clarification
or
fixes
or
something,
but
sometimes
a
committer
like
dave,
will
give
a
thumbs
up
but
not
merge
it.
Yet
because
he'll
wait
around
to
see
if
anybody
else
wants
to
comment-
and
I
think.
D
B
A
C
C
B
A
Okay,
so
the
second.
A
Was
exploring
different
open
source
platform
services.
C
So
one
of
the
things
that
we're
exploring
right
now,
which
has
been
on
our
plate
for
a
while
but
is
in
sharp
focus
right
now,
is
we
currently
maintain
our
own
open
source
services
for
community
platforms
like
our
bug,
tracker
and
forums.
Specifically,
this
is
quite
a
bit
of
overhead
for
the
team
to
you,
know,
maintain
and
run
operations
on
and
there
are
totally
viable.
You
know,
platforms
that
are
externally
hosted
that
other
open
source
projects
use,
so
I'm
pretty
seriously
invested
in
exploring
those
and
moving
to
those.
C
So
I
wanted
to
give
everyone
a
heads
up
and
open
the
discussion
for
see
how
people
thought
about
that.
There
are
a
number
of
different
options,
but
I
mean
at
the
point
where
I
am
in
my
research:
I'm
really
converging
on
well.
So,
let's
just
let's
have
a
two-part
discussion.
One
is
our
existing
services,
which
are
forums
and
bug
tracker.
I
I
I
don't
know
if
you
know
other
people
can
give
input,
but
you
guys
can't
really
see
the
cost
of
what
it
takes
to
run
these
things
internally.
C
So
I'm
letting
everyone
in
the
community
know
that
the
burden
has
now
become
too
high,
and
so
I
think
it's
in
the
best
interest
of
the
product
project
to
move
to
something
else
where
we
don't
really
have
to
deal
with
the
overhead
of
that.
So
that's
part
one
and
then
part
two
is
what
do
we
move
to
so
for
forums
the
leader
right
now
that
I'm
looking
at
is
google
groups
a
lot
of
other
open
source
projects?
C
You
know
have
their
forums
and
mailing
lists
on
that
it
provides
a
lot
of
the
same
features
that
our
current
forums
does
in
terms
of
email,
capability
and
and
online
access
and
categorization
as
in
sub
forums.
The
one
drawback
is
that
it's
a
different
system,
so
everyone
needs
a
google
account
to
post
to
that.
But
anyone
can
view
so
you
don't
need
an
account
for
that.
C
B
C
Very
interesting,
okay,
great!
That's
that's
even
better,
then
so
so
that's
that's
the
the
forum's
alternative
that
I'm
looking
at
it
and
it's
free.
If
there's
something
else
that
you
know
is,
is
just
as
good
or
better.
I'm
certainly
open
to
hearing
those
suggestions
or
if
everyone
who
uses
google
groups
today
loves
it
and
thinks
we
should
move
to
that.
C
I'd
love
to
hear
that
feedback
as
well
and
then
so,
while
I'm
talking
about
the
forums
the
the
plan,
there
would
be
that
we
don't
migrate
everything
to
a
google
group,
the
plan
there
would
be
that
we
start
our
forums
over
there
and
that
we
all
move
there
and
that
we
would
preserve
the
the
legacy.
C
C
This
to
sort
of
move
before
and
it
as
far
as
I
know,.
G
C
Yeah
well,
the
the
thing
about.
What
we
would
do
here
is
that
you
could
go
to
your
library.com
forums
and
you
wouldn't
be
able
to
do
anything,
so
it
would
be
much
more
obvious.
G
C
The
group
had
moved
whereas
the
other
one,
I
don't
think
we
could
do
that.
I
think
we
just
kind
of
laughed.
So
I
think
you
mean
sort.
A
C
Was
one
of
those
of
that
move
that
we
wouldn't
have
with
this
move,
so
that's
forums
and
then
for
bug
tracker?
Actually
I
am
a
little
more
conflicted
about
that.
There
is
no
clear
winner.
There
are
obviously
in
an
ideal
world.
I
would
love
to
just
move
to
github
issues
and
call
it
a
day,
but
the
workflow
isn't
quite
there
yet.
But
the
good
news
is
it's
being
improved
like
every
quarter,
it
seems
like
you're
adding
features,
but
you
can't
do
certain
things
that
you
need
like
a
robust
project
like
ours
to
do.
C
I
don't
know
if
it's
worth
the
short-term
pain
of
of
just
fighting
that
bullet
and
having
those
features
land
when
they
land
and
taking
advantage
of
them
later.
So
that's
something
I'm
a
little
more
involved
about
in
the
interest
of
again
not
having
to
host
our
own
infrastructure,
I'm
kind
of
willing
to
be
aggressive
and
take
that
risk.
C
One
thing
that
we've
been
using
a
lot
lately
internally
here
for
project
management
is
trello,
so
I'm
looking
at
github
issues
and
trello
integration,
that's
something
that
I
think
we're
better
off
building
ourselves
and
then
we
could
have
like
a
pretty
nice
workflow
to
get
to
where
we
need
to
be
in
terms
of
tracking
and
having
people
understand
like
what
their
current
commitments
are
and
being
able
to
do,
burn
downs
and
everything.
C
So
that's
certainly
something
that
I
would
appreciate
a
little
more
discussion
around,
because
I
have
more
questions
around
if
you
know
if
that
would
provide
everything
that
I'm
looking
for
or
if
there
are
other
projects
that
are
using
something
to
greater
effect,
I've
definitely
been
enticed
by
jira
and
they
have
an
open
source
license.
C
So
that's
something
that
you
know
is
in
the
back
of
my
head,
that
that
might
actually
be
the
thing
that
I'm
looking
for,
but
it's
not
as
easy
to
use
and
delightful
to
use
as
the
trello
interface
that
we've
kind
of
grown
to
love
over
the
past
couple
months,
they
do
have
a
certain
level
of
gift.
Github
integration
too,
though,
so
that's
nice.
C
So
I'd
love
to
hear
community
thoughts
and
if
you
have
experience
with
anything
in
the
bug
tracking
realm,
any
github
integrations
specifically.
That
might
be
useful
to
us,
and
here
are
other
thoughts,
including
objections
on
the
topic.
So.
C
Off
the
top
of
my
head,
there's
no
easy
way
to
filter
bugs
for
unassigned
tickets.
So
that's
something
that
is
in
my
common
workflow
that
I'd
be
missing.
You
can
assign
people
to
things,
but
you
can't
just
filter
for
tickets
that
are
unassigned.
C
All
right,
that's
true,
but
when
a
new
ticket
gets
created,
can
you
auto
assign
the
unassigned
tag.
F
C
G
Crosslink
on
the
whatever
other
ticket
there
is
yeah.
B
That's
that's
one
really,
nice
thing
about
the
the
cross
linking
via
comments
is
really
nice
about
github
issues.
So
if
you
want
to
mark
something
as
a
duplicate
or
you
want
to
say,
this
thing
depends
on
this
other
thing.
You
just
mention
it
in
a
comment
or
even
a
pull
request
or
a
commit,
and
it
all
gets
cross-linked.
A
So
I
wanted
to
point
to
an
open
source
project.
That's
using
github
issues
and
trello
together,
it's
brackets.io.
They
have
an
open
development
roadmap
that
points
to
their
current
issues
as
an
open,
trello
board.
For
anyone
to
look
at,
I
think
it's
a
really
nice
sort
of
interface
for
how
they're
they're
trying
to
keep
their
development
open,
and
it's
just
it
just
stands
out
as
a
great
example
of
how
an
open
source
project
is
trying
to
get
a
community
involved
using
trello
as
a
way
to
so.
A
A
Oh
yeah,
on
brackets.io.
A
If
you
scroll
to
the
development
roadmap,
go
under
contribute,
okay,
the
other
thing
that's
really
nice
about
their
issues
list-
and
I've
mentioned
this
before-
is
they
have
a
really
great
use
of
labels?
So
they
have
things
like
fix
in
progress.
Community
bug
code
mirror
code,
cleanup
things
like
that,
so
they
have
they're
they're
using
labels
in
the
great
effect.
So
if
you're
a
new
developer
for
this,
you
can
just
go.
Look
at
the
you
know
new
user
bugs
list
and
be
able
to
pick
up
about
quickly
there.
G
A
C
A
A
C
That's
the
missing
piece
that
I'm
looking
for
is
some
mechanism
for
doing
that
integration
and
it
looks
like,
as
of
today,
we
kind
of
need
to
build
our
own.
It
doesn't
look
super
complicated
and
and
fairly
customizable,
because
trello
has
an
api
you
can
have
isn't
it
has
api,
so
that's
not
necessarily
a
blocker,
but
it
would
certainly
be
easier
if
there
was
something
like.
C
That
some
other
project
has
used
that
we
could
like
build
off
of
so
that's
my
request
to
the
community.
If
you
know
any
trello
github
integrations
like
there
are
companies
that
you
that
offer
the
services
for
a
fee.
So
aside
from
that,
if
you
know
of
anything
that
I
should
be
looking
at,
please
send
it
my
way.
B
So
a
couple
of
things
because
you've
sort
of
covered
a
lot
of
stuff
and
asked
for
feedback
on
a
lot
of
stuff.
Google
groups,
I
think,
is
a
great
idea.
I
think
it's
been
working
really
well
for
the
contributor
list
and
I
think
it's
good
for
people
who,
like
you
know,
email
lists
or
forums
they
can
sort
of
choose
which
one
they
want
to
use
github
issues.
B
I
agree
on
the
lack
of
some
organizational
stuff,
but
I
think
it's
actually
been
working
fairly
well
in
terms
of,
I
think
the
community
likes
it
for
reporting
issues,
because
it's
really
easy.
It's
really
convenient
it's
it's
directly
linked
to
source
and
to
pull
requests
and
all
that
stuff,
and
I
like
it
as
an
external
contributor,
because
I
get
an
email
when
a
new
issue
comes
in
and
I
can
easily
you
know
triage
my
own
issues
and
and
that
sort
of
thing.
A
I
think
you
bring
up
a
good
point
about
that,
where
people
are
working
on
other
projects,
other
open
source
projects,
the
migration
to
going
to
yui
may
be
less
right
exactly.
E
E
H
E
B
E
Are
talking
about
if
github
issues
is
missing,
as
you
said,
some
of
the
visualization
stuff
like
I
want
to
know
what
bugs
are
on
the
side.
I
want
to
see
this
group
of
bugs
that
are
tagged.
This
way
we
could
easily
write
stuff
that
has
that
will
communicate
with
the
api
and
yeah
just
host
it
on
a
github
page
like
on
yui.github.com
issues,
so.
C
Let
me
be
a
little
more
specific.
The
big
things
that
I'm
interested
in
are
sprint
level
line
item
ordering
of
tasks
and
burn
down
metrics,
and
those
are
things
that
trello
gives
us
today.
Okay,.
D
C
If
we
could
have
a
github,
trello
integration
piece
that
I
think
gets
us
like
90
there
or
maybe
even
95,.
A
C
It's
just
a
couple
things
like
that.
Like
I
said,
I
think
these
are
known
things
I
think,
there's
nothing
off
the
shelf
that
I
see
that's
free.
That
is,
gives
us
everything
that
we
need,
but
I
see
all
the
pieces
out
there
like
people
have
done
it
in
the
past,
so
I
I
feel
like
maybe
a
couple
weeks
of
effort,
maybe
an
intern
or
something
like
that
could
potentially
get
us
that
integration
piece,
but
even
better.
If
someone
knows
something,
that's
already
been
done
or.
F
C
A
It
looks
like
there's
a
lot
of
like
you
know:
skunk
works
projects.
C
E
Then,
going
back
to,
I
guess,
continuing
some
some
more
feedback
on
google
groups.
I
think
I've
always
been
an
advocate
of
mailing
lists,
so
I
think
getting
the
the
forums
to
much
more
of
a
mailing
list
approach,
but
also
having
that
foreign
capability
there.
I
think,
that's
just
so
much
better
for
the
community
and
for
the
active
contributors
to
kind
of
get
it
get
a
sense
of
what
people
are
working
on
a
little
bit
more.
The
forums
are
a
little
bit
too
easy
to
do
out
of
sight.
E
E
D
A
Not
in
your
flow
of
you
know,
messages
yeah
well,
one.
A
D
A
A
A
D
E
C
I
love
that
alerts.
A
D
Yeah
there's
a
pull
request
in
or
66
yeah
that
one
had
the
link
up
there,
so
I
didn't
have
to
remember.
D
D
Should
the
paginator
core
methods
be
in
a
file
by
themselves
so
that
they
that
paginator
core
can
just
be
used
on
its
own,
which
would
leave
y.paginator
empty
and
then,
if
you
wanted
to,
if
you
wanted
to
use
paginator
or
paginator
url,
that
would
be
mixed
together,
or
is
it
okay
to
keep
paginator
core
in
the
same
file
as
the
what
as
wide.paginator
as
it
is
now
as
paginator.js?
D
So,
basically,
should
it
be
two
files
or
three
where
paginator.js
would
simply
use
paternator
core
and
mix
it
into
y
dot,
paginator.
B
So
I
I
think
the
three
file
thing
makes
sense.
I
mean
it.
It
makes
sense
to
have
the
core
module
separate
from
the
other
stuff,
so
that
people
can
mix
it
into
their
own
things
as
an
extension,
or
you
can
also
provide
the
everything
baked
in
you
know,
paginator
that
they
can
use
if
they
don't
want
to
just
use
the
core
module.
D
All
right
and
that's
that's
what
I
was
thinking
would
be
the
best
way
to
do
it
and
then
so,
aside
from
that,
I'm
wanting
to
get
any
additional
feedback
for
any.
If
anyone
sees
anything
missing
and
derek.
I
know
that
you
have
the
paginator
inside
scroll
view,
and
I
would
be
interested
in
your
thoughts
of
being
able
to
integrate
paginator
core
to
replace
your
overhead
for
maintaining
paginate
pagination
functions.
Functionality
in
the
scroll
view,
paginator.
E
Yeah
I'd
have
to
take
a
look
and
see
where,
if
there's
any,
if
there's
any
overlap
there,
because
I
guess
I
wonder,
do
or
do
they
really
there's
not
really
much
similar,
they
just
share
a
similar
name
but
yeah.
I
could
certainly
take
a
look
page
so
paginator.
E
It
might
make
sense.
As
like
cares,
I
don't
know
yeah.
I
I'm
thinking
about
you
I'll,
take
a
look
at
it
more.
Thank
you.
Feedback
yeah.
D
I
think
a
lot
of
the
core
functionality
as
far
as
like
keeping
the
current
page
that
you're
on
taking
the
number
of
items
and
the
number
of
items
that
you
displayed
at
a
time
to
create
a
total
of
number
of
pages
and
then
next
and
previous
options
and
then
going
to
a
specific
page.
That's
really
what
pageantry
core
takes
care
of.
E
Yeah
it
sounds
like
paginators
grovy,
paginators
api,
so
yeah
interesting.
D
And
then,
as
soon
as
soon
as
I
can
get
sign
off
on
the
functionality
of
that,
I'm
wanting
to
roll
out
an
actual
view
of
paginator
to
be
included
with
a
data
table
and
go
ahead
and
get
that
in
the
next
release.
That
comes
up
so.
G
D
No
it'll
be
a
view
the
for
the
something
similar
to
how
the
head
works
right
now,
it'll
be
a
view
that
gets
loaded
into
the
footer
of
data
table
and
or
gets
loaded
in
as
a
view
alongside
of
data
tables.
A
few
too
okay.
D
A
Is
there
a
branch
that
the
community
can
try
things
out
already
with
or.
D
No,
I
don't
have
any.
I
had
examples,
and
none
of
that
none
of
that
has
really
changed
as
far
as
I've
just
basically
stripped
out
the
number
of
files
that
I
have,
but
I
had
working
examples
that
I'll
have
to
rebuild
outside
of
it
being
auto
included.
D
Yeah,
if
anybody
has
any
any
thoughts
as
to
if
there's
anything
missing
from
paginator
core,
which
I
can't
see
and
I
believe
ryan,
he
read
through
the
code
probably
a
couple
of
times
and
he
hasn't
really
indicated
anything's
missing,
but
has
actually
indicated
that
some
stuff
needs
to
be
removed
and
I've
taken
taken
that
stuff
out
and
so
if
anything's,
missing
or
could
be
improved
upon.
I'd
be
happy
to
hear
that.
D
I
D
C
So
just
I
think
the
documentation
outstanding
needs
to
be
included
with
the
poll
with
the
pull
request
and
then
actually
matt
started
a
new
thing
in
like
half
an
hour
ago.
So
I
think
there's
a
little
bit
of
ongoing
commerce.
B
Yeah
I
just
I
just
responded
to
matt
he's
actually
contradicting
the
advice
that
I
gave
to
tony
earlier.
Okay,.
C
B
No,
I
think
I
would
give
this
a
thumb
a
thumbs
up
if
there
were
docs
okay-
and
I
think
the
great
thing
about
just
not
quite
being
sure
if
it
has
everything
it
needs,
is
that
if
you
find
out
it's
missing
something
you
can
add
that
later
it's
not
gonna
break
anything.
Okay,.
E
A
Great
awesome,
so
we
look
forward
to
that.
You
think
you'll
have
some
demos
next.
D
A
The
latest
okay,
we'll
move
her
along.
We
have
two
other
items:
the
stale
pull
request
review
and
the
unassigned
bugs
review.
I
want
to
make
one
comment
that
ryan
has
been
kicking:
butt
on
all
the
pull
requests
like
everyone
that
I
saw
that
was
stale
before
he's
gone
in
and
updated
or
moved
things
forward,
so
we
have
a
whole
fresh
list
of
stale
4
requests,
and
a
number
of
these
are
if
we're
looking
at
the
query.
A
B
So
some
of
these,
when
I
went
through
earlier
today,
I
there
were
some
of
them
that
have
already
been
given
a
thumbs
up
and
are
just
waiting
for
code
freeze
to
lift
so
I've
marked
those
as
ship
it.
Okay,
so
once
once
we're
not
in
code
freeze,
we
can
just
go
through
and
merge
all
of
those.
G
And
just
to
clarify,
though,
with
the
release
being
pushed
till
next
tuesday
doc
live
docs
updates
are
still
frozen
until
that
tree
is
thawed
or
we
can.
We
can
just
stick
those
in
there.
They
are
if
they're.
B
C
C
So
I
would
just
ask
for
a
little
bit
of
patience
right
now
and
not
commit
anything
of
any
kind
until
we
get
to
the
release
milestone
which
we're
targeting
for
tuesday
under
normal
circumstances,
the
process
means
that
that
time
frame
is
from
friday
to
tuesday.
So
just
a
handful
of
days.
But
in
this
case,
because
of
the
split
it's
been
like
a
week,
so
there's
going
to
be
pent
up
check-ins
as
soon
as
we
release
and
that
freeze
can
be
lifted.
F
A
So,
moving
down
to
the
first
one
that
looks
like
a
candidate,
it
would
be
from
illion,
I
believe,
and
it's
pull
request.
519.
A
It
says,
restore
form
attributes
after
successful
upload
in
the
I
o
upload
frame
fixes
bug
two
five,
three,
two,
eight
nine
nine
and
it
looks
like
he's
fixed
the
issue
with
id
that
I
think
someone
else
had
an
issue
that
we're
about.
D
D
C
Is
that,
during
a
time
of
known
instability,
let
me
look
at
the
traps.
A
B
A
So
one
question
ahead
is:
I
know
we
wanted
the
list
in
these
pull
requests
the
browsers
that
they
then
the
platforms
they
tested
on.
Is
that
something
we
want
to
start
asking
of
these
requests
as
well?
A
B
I
think
that
is
kind
of
a
burden,
and-
and
also
I
don't
know
it
seems
like
that's-
that's
the
responsibility
of
of
whoever's
signing
off
on
it.
So
I
would
say,
that's
probably
the
reviewer's
responsibility
to
say
yeah
I've
at
least
given
this
a
sanity
check,
and
it
looks
fine.
C
A
B
Yeah
definitely,
but
you
know
it
could
also
be
that
the
way
they
test
is
less
thorough
or
it's
not.
You
know
the
way
it.
C
Yeah-
and
I
don't
see
any
like
systematic
way
of
having
that
communication
in
there-
it's
not
like
a
checkbox,
we
can
add
to
the
chloroplast
workflow.
J
C
C
B
H
A
So
with
regards
to
this
one,
do
we
just
what
else
is
needed
for
it
to
move
forward.
C
It
looks
ready
to
merge,
given
a
little
due
diligence
by
the
merger.
H
A
A
A
G
The
data
binding
the
work
that
needs
to
be
done
on
that
is
is
postponed
by
other
work
that
I'm
doing
right
now
anyway.
So
I
think
it
actually
makes
sense
because
of
how
long
it's
at
there
that
I
can
close
it
and
issue
a
new
one
based
on
updated
code
against
the
latest
in
the
tree.
Okay,.
B
I
think
we
should
err
on
the
side
of
closing
things,
rather
than
keeping
them
open,
because
they'll
always
be
there
even
if
they're
closed.
If
we
want
to
go
back
and
refer
to
them
right.
A
Yeah,
I
agree.
Okay,
next
up
tony
you've
got
one,
that's
548
and
that's
13
days
ago.
D
That's
one
that
it's
got
a
regex
with
a
etf8
character
in
it
to
keep
an
open
space
on
hex
parsing
to
allow
for
an
alpha
channel
to
automatically
be
added
in,
and
there
hasn't
been
really
any
any
solid
feedback
as
to
keep
that
in
there
or
an
alternative
to
that
right.
Now,
rgba,
hsl
and
hsv
a
all
provide
an
alpha
channel
because
it's
looking
for
an
optional
parameter
at
the
end
of
the
color
value
string,
but
hex
and
hex
three
do
not
look
for
an
optional
color
value.
D
D
I
understand
that
having
a
utf8
character
in
there
is
a
little
odd,
but
if
anyone
else
has
any
suggestions
as
to
what
what
to
do
to
make
sure
that
only
modifying
the
regex
would
provide
that
alpha
channel,
because
the
what
I'm
trying
to
do
is
I'm
trying
to
prevent
the
two
array
method
from
having
to
be
overwritten.
If
someone
adds
a
new
color
package
to
it.
D
If
we
can
just
modify
the
hex
and
hex
three
regex
strings
to
provide
the
space
for
the
alpha
channel,
that
would
be
the
easiest,
the
most
flexible
way
to
go
about
doing
that.
B
D
D
D
D
Right
because
I
was
just
using
a
ut,
any
utf-8
character
that
would
most
likely
never
be
entered
in
a
string
so
that
the
value
would
never
be
found.
It
would
never
come
out.
B
Yeah
yeah,
okay,
what
I
would
recommend
is
actually
so
you
want
this
thing,
never
to
match
I'll
I'll
leave
a
comment
about
this,
but
there's
actually
a
utf-8
character.
That's
backslash!
U
fffe!
Okay!
That
is
guaranteed,
never
to
be
in
a
valid
utf-8
string,
but
it
is
a
valid
utf-8
character,
so
you
can
put
it
you
can
like
you
can
test
for
it.
Okay
and
you
can
use
that
as
a
as
a
you
know,
never
match
this
character.
A
B
A
B
A
A
A
A
A
Oh,
it's
a
link
on
the.
If
you
go
to
roundtable
topics
underneath
the
discussion,
there's
a
stale
pull
request
review
and
that's
a
canned
query
that
sorts
on
updated.
F
A
C
There's
so
he's
adding
parsing
with
config
feature.
F
I
C
That
we
need
to
be
aligning
with
for
number
parsing
for
internationalization.
G
No,
the
well
the
only
date
specification,
that's
sort
of
standardized
inside
of
like
what's
ecmas
back,
has
to
do
with
iso
9601
for
jason,
but
that
is
represented
by
two
iso
string,
but
since
there's
no
actual
parse
process
for
dates
in
json,
oh.
G
Right,
that's
my.
The
the
thing
that
stood
out
to
me
was
the
number
of
regexes
that
are
being
created
on
parse
and
if
this
is
going
to
be
called
enough,
a
lot
of
times
on
records,
for
example,
in
a
data
source
parser,
or
something
like
that,
then
then
so
you're
thinking.
If
it's
going
to.
G
D
A
It
goes
back
to
satyan's,
you
know
code
for
the
the
optimal
case
not
make
everyone
else,
pay
the
cost
for
the
edge
case.
G
I
can
see
something
like
this
being
useful
for
receiving
input
from
forms.
People
are
going
to
be
typing
in
commas
into
their
numbers,
that
sort
of
things
they'll
be
formatting
in
a
particular
way.
That's
localized
to
that
area,
and
so
this
would
be
a
convenience
to
take
whatever
various
forms
of
those
inputs
and
turn
it
into
a
real
number.
So
I
think
the
use
case
exists
right.
G
Well,
the
performance
bottleneck
would
be.
I
think
the
performance
bottleneck
is
avoided
by
the
language
object.
Config,
which
can
be
dealt
with
by
saying,
is
the
config
even
specified,
or
something
like
that.
So
yeah.
D
G
C
Yeah,
I'm
just
concerned
that
I
I
would
I
would
want
to
know
I
would
want
the
people
who
would
want
to
use
this
feature
to
be
weighing
in
because
I
kind
of
don't
care
either
way.
This
is
not
like
something
that
I
would
find
useful
in
in
my
code,
but
there
are
plenty
of
customers
who
would
so?
I
would
want
to
make
sure
that
they
got
a
chance
to
weigh
in
as
well.
E
A
I
list
four
more
to
go
one
more.
This
one
is
pull
request:
541,
it's
from
maxim:
meredi
fix,
async
q,
bugs.
A
B
So
I
took
a
quick
look
at
this.
I
don't
know
that
much
about
async
cue,
but
this
looks
I
mean
it
looks
decent
and
it's
got
tests,
so
I
think
it
would
just
need
somebody
who
knows
something
about
async
queue
to
say
that
this
is
not
insane.
J
A
Next,
one
is
from
gray
rest
mouse.
Events
do
not
participate
in
gestures
on
touch
enabled
devices.
This
is
request.
471.
B
A
A
Is
big
one
from
dave,
so
we
it's
marked
as
work
in
progress.
So
if
we
skip
this
one,
it's
the
new
c
poc,
so
just
merge
it.
A
So
the
last
one
that
falls
into
our
our
bucket
today
is
566
from
satyam,
improved
parser.
B
This
is
another
one
that
for
me
like,
I
wouldn't
use
it
and
I'm
not
sure
who
does
or
who's
the
expert
who
should
be
commenting
on
this.
B
B
C
I
mean
it
looks
like
actually.
Okudu
has
something
that
dovetails
with
what
satyam
is
working
on.
A
Yeah
when
we
saying
that
he
was
running
the
tests
and
one
of
these
failed
because
and
I'm
saying
it's
not
his
test
from
the
previous
code.
A
So
my
question
is
back
to
sort
of
where:
where
did
we
go
from
here?
Do
we
need
does
need
additional
comments,
more
tests?
Do
we
need
overview
well.
B
My
big
question
is,
I
mean
there,
it
doesn't
seem
like
there
are
any
reviewers
who
can
own
this
or
who
can
be
an
expert
on
it.
So
it's
it's
guaranteed
to
be
something
that
sachin
will
own.
B
C
Yeah,
no,
I
don't
think
that's
the
issue.
It's
just
there's
no
real
subject
matter
expert
at
the
reviewer
or
even
like
the
committer
level.
That
gives
like
a
true
blessing,
and
so
if
this
was
a
committer,
it
would
just
be
merged
in
after
72
hours.
But
we
need
someone
to
step
up
and
sponsor
it,
because
it's
not
coming
from
a
committer
and
there's
just
not
a
real.
C
C
So
I
mean
if
we
were
to
air
on
one
side
or
another,
is
it
just
like
merging
in
with
the
with
the
understanding
that
satyam
is
like
passionate
about
this
and
seems
to
have
done
all
the
right
things?
But
we
don't
really
know
I'm
just
er
on
the
side
of
someone
will
find
it
useful
or
are
on
the
side
of
we
don't
know.
So,
let's
just
put
it
in
a
gallery
or
pause,
and
until
we
can
get
more
consensus.
Well,.
E
It's
like
what
the
what's
the
scale
of
the
public
api
change
on
this
digging
through
here
to
see.
H
G
So
it
actually
seems
to
revisit
the
larger
question
of
breaking
out
core
versus
widgets
and
the
whole
larger
product
discussion.
B
G
I
do
think
that
in
this
specific
case
it
it's
probably
fine
to
merge
in
you
know
with
with
some
review,
but
this.
H
B
A
So
what
I'll
do
is
seek
out
an
owner
for
this
or
someone
who
can
pull
it
in
so
move
it
forward.
In
that
respect,.
C
I
think
maybe
also
just
take
this
state
pressing
and
the
number
parsing
to
the
contrib
mailing
list
and
just.
D
C
A
So
this
is
a
report:
146
yeah,
it's
not
in
github
issues
right
now,
it's
still
in
the
yui
library.com
site.
If
you
go
to
the.
E
Round
table
wiki
on
github
you'll
see
a
link
there.
B
So
I
have
to
tell
you
from
my
perspective,
anything
that's
in
track
doesn't
exist
as
far
as
I'm
concerned,
just
because
it's
so
hard
for
me
to
deal
with
externally.
It's
just.
A
Goes
back
to
jenny's
point
that
how
would
you
write
this
query
right.
B
Well,
I
mean,
for
it
sort
of
depends
on
some
due
diligence
on
each
on
each
committer's
part
like
I
get
emails
about
new
issues
that
are
filed
as
they
come
in,
and
I,
if
it's
something
that
applies
to
something
I
care
about,
then
I'll,
look
at
it
and
maybe
assign
it
to
myself,
but
it
sort
of
depends
on
everybody
to
do
that.
A
It's
just
they're
they're
a
thing
that
exists
that
people
can
go
take
a
look
at.
Maybe
we
need
to
start
migrating
this
over
to
github
issues
as
well,
but,
right
now
this
is
people
are
online,
watching
this
feel
free
to
go.
Look
at
the
roundtable
topics
and
click
on
the
I'm
assigned
bugs
and
pick
up
a
bug.
A
So
that
concludes
things
that
we
had
scheduled.
Does
anyone
have
anything
unscheduled?
They
want
to
talk
about,
or
are
we
good
to
go?