►
From YouTube: YUI Open RoundTable 01/24/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
B
All
this
is
documented
our
contributor,
the
developer,
workflow
and
other
mechanism
that
posted,
and
so
what
that
means
is
at
the
end
of
every
sprint
we
we
will
have
hope,
lift
at
a
PR
and
when
we're
ready
to
cut
the
release,
we
do
like
a
pulse
check
on
our
confidence
level
of
the
quality
and
in
the
case
where
we
feel
like
we
need
more
time
to
fully
baked
something
or
get
more
feedback
where
we.
B
We
haven't
had
time
to
work
right
back.
We
will
pause
on
releasing
from
the
32
X
friend.
I
put
them
on
these
off
with
a
master
branch
which
allows
us
a
great
deal
of
confidence
and
the
quality
of
the
release,
and
so
that
happened
for
the
first
time
this
past
spread.
We
had
a
regression
in
the
3x.
We
wanted
a
little
bit
of
time
to
fix
that
we
went
ahead
and
released
a
master
381
instead
of
a
390,
and
that
was
the
first
thing
that
happened.
I
wanted
to
put
this
on
the
table
for
discussion.
B
What
do
we
do
now?
So
it's
a
good
time
to
talk
about
what
we
think
the
best
process
is
moving
forward.
I
think
if
we
can
come
to
a
decision
today,
we
can
revisit
it
in
the
future.
If
you
don't
feel
like
it's
working
out,
but
the
big
question
on
the
table
is:
when
do
we
cut
for
you?
I
know
we
have
a
couple
different
options
and
since
we
have
the
scope
kind
of
well-defined
for
free,
no,
no,
we
have
the
regression
that
we
wanted
to
address
and
that's
about
it
fixed.
B
B
Release
that
is
as
soon
as
possible,
alchemist
milestone
and
then
the
other
option
is
we
keep
rolling
along
into
our
next
sprint
and
we
target
for
you
now
know
for
the
end
of
this
coming
sprint.
The
the
advantage
of
that
is
that
we
don't
have
this
one
off
release,
but
the
disadvantages
we.
D
I
guess
my
thought
would
be
that
the
default
thing
we
would
do
it
would
be
to
wait
and
for
the
spring
and
but
but
I
like
the
idea
of
being
able
to
adjust
our
our
process
when
coming
up
with
these
new
you're
running
into
these
new
situations,
I
was
curious.
How
many
open
pull
requests
we
have
on
against
the
dev
3x
branch
I
know
I,
see
to
that
look
like
they
were
bug
fixes
from
trip
that
are
still
open
against
that
branch.
Now.
B
So
I
think
I
think
yeah
I
think
we
need
to
make
that
decision
independent
of
what
those
to
pull
requests
happen
to
be
because
otherwise
we're
always
going
to
be
doing
on
a
case-by-case
basis
of
well.
What's
in
the
queue
should
be,
those
are
not
I
would
rather
come
up
with
a
process
that
is,
you
know,
makes
sense.
Independent
of
all
these
other
moving
factors
is.
A
B
I
guess
in
general,
I
am
reluctant
to
make
all
everything
that's
in
with
me
da
NEX
French
wait
for
a
whole
other
sprint,
but
I
understand
that
there's
a
cost
to
having
a
one-off
release.
So
that's
the
real
question
is
this:
that
trade-off
worth
it.
I
feel
like
I
would
prefer
us
to
in
the
in
the
future
when
this
happens,
and
we
don't
ship
off
30
X
to
get
to
equip
making
off
of
us
as
soon
as
possible
and
do
what
one-off
release
so.
D
B
D
B
B
This
time,
but
the
process
that
I'm
proposing
what
I'm
leaning
towards
is
we
get
to
Friday.
We
say
code
freeze,
we're
getting
ready
to
ship
off
of
food
on
X
we
go
in
and
look
and
we
see
a
few
decks
doesn't
feel
ready.
So
we
do
ship
off
of
three
off
of
master
and
get
that
out
the
door,
and
then
we
go
back
and
address
whatever
we
feel
like
was
preventing
us
from
releasing
and
just
close
that
gap
and
then
cut
a
really
release,
aquafina
x
and
then.
E
My
only
opinion
on
it
would
be
that
we
would
we
would
Murr.
We
would
stabilize
three
decks
by
pulling
in
any
of
the
problems.
We
can
also
address
any
pull
requests
that
were
late,
breaking
that
people
kind
of
forgot
to
merge
in
because
they
didn't
know
they
could
because
I
believe
there's
a
couple
of
them
sitting
there
from
Tony
that
didn't
make
it
in
because
he
just
didn't
realize
that
he
actually
could
I
don't.
E
But
but
my
thing
is:
I:
don't
want
to
release
two
releases
back
to
back
because
I
think
that's
poor
judgment
on
us.
What
we
should
do
is
clean
up
3x
issue,
another
PR
off
of
that,
so
we
at
least
get
a
release
of
some
kind
out,
but
not
an
official
and
we
and
then
we
have
our
wait
time
that
we
normally
would
and
then
release
it.
Maybe
you
know
the
week
after.
What's
for
better
once
we
got
the
pr
out
one.
E
We
could
do
that
to
I
mean,
but
my
main
thing
is
I.
Don't
think
that
we
should
just
immediately
issued
the
39
release
if
we
can
issue
the
the
PR
for
it
that
still
gets
it
up
on
the
CDN
that
still
gets
it
an
NPM
people
can
use
it,
they
can
validate
off
of
it
and
just
as
if
we
had
done
a
39,
but
then
we
still
get
the
time
to
fix
anything
else
in
between
and
we're
not
out
anything
right.
You.
B
All
right,
here's
my
modified
proposal,
so
we
get
to
code
freeze
and
we
realize
we're
not
ready
to
cut
off
of
three
dot
X.
So
we
go
ahead
and
cut
off
a
master
and
then
master
becomes
unfrozen.
We
bridge
the
gap
and
fix
whatever
we
felt
like
was
laughing
if
you
don
and
in
any
kind
of
PR.
After
that,
and
then
redirects
becomes
unfrozen
for
ongoing
development
and
then
at
the
end
of
the
next
spread,
we
do
a
phone
call
Belize
off
of
three
times
yeah.
B
F
B
A
D
B
With
this,
with
the
latest
proposal
that
I
lied,
Master
stays
frozen
for
the
Schwartzman.
A
lot
of
time
possible,
so
from
Friday
to
Tuesday
will
be
cut
the
release,
and
then
it
becomes
unfrozen
and
3x
from
a
friday
until
whenever
the
PR
can
get
cut
only
murders
in
the
Delta
between
what
was
wrong
that
prevented
it
from
getting
released
in
the
first
place
and
right
after
that,
PR
can
get
cut.
Then
we
do
emerge
from
master
right
after
that.
Okay.
D
Yeah
cuz,
if
master,
doesn't
stay
frozen
in
that
process,
then
I
don't
think
we
should
do
that,
because
our
whole
thing
is,
we
always
want
to.
We
always
cut
the
release
off
a
master
right
like
that's
how
we've
been
doing
it
and
what
we
do
is
we
merged
3x
into
master?
Let
make
sure
the
build
is
good
and
then
cut
the
release.
Well,.
D
A
B
D
A
B
D
Yeah
I
feel
like
we
need.
You
know.
We
need
to
do
something,
because
if
we
didn't
have
a
some
type
of
process
around
this,
we
could
get
in
a
state
where
we
never
release
anything
off
of
3x,
because
it's
it's
unstable
many
times
in
a
row.
So
I
I
agree
that
there's
there'd
be
a
problem.
If
that
was
our
process,
that
we
don't
have
any
exception
for
for
doing
a
release
soon
after
you
know,
outside
of
the
normal
cycle
or
whatever,
no.
D
D
A
Today
and
ask
a
question
about
sort
of
a
little
bit
about
what
happened,
so
that
would
I
think
I
thought,
because
if
we
want
to
avoid
this
thing
for
the
part
of
the
thing
that
got
me
was,
then
we
were
getting
around
after
friday
and
was
kind
of
ad
hoc
like
Oh.
Are
we
even
tested
for
this,
or
is
it
good
to
go?
We
have
you
know,
sign
off,
or
maybe
I
just
wasn't
in
the
I
saw
a
finally
I'd
read
about
this
invention
and
I
go
or
maybe
this.
A
B
G
B
Right
so
I'm
going
to
wrap
this
up
and
send
it
to
the
contributor
mailing
list
before
posting
it
on
the
leaf
eater.
Do
it
in
parallel
and
get
have
some
time
for
some
white
or
feedback,
but
I
think
this
is
a
good
place
to
start.
So
thank
you.
I
have.
A
One
more
on
this
we
know
are.
We
now
are
n
state
where
this
TR
could
have
other
things
other
issues
right,
because
we'd
open
the
door.
This
has
been
merged
master.
So
how
do
you
feel
that
you
just
cross
that
bridge
when
you
do
it
take
that
issues?
Sheila's
master
has
been
merged
into
30,
desks,
esco
degrees.
So
the
scenario
that
we
mentioned
amount
of
oil
was
well.
B
A
B
D
G
B
B
Overall,
long-term
I
want
to
get
to
having
two
weeks.
Friends
I
want
to
really
start
exploring
the
idea,
or
at
least
you
know,
be
able
to
release
every
two
weeks
which
would
help
alleviate
this.
You
know
wait
a
month
and
see
if
we
can
only
talk
for
30
x,
I
think
it
fits
every
two
weeks.
We
would
just
feel
like.
We
have
more
opportunities
to
cut
overly
safavieh
x.
A
This
kind
of
makes
a
question
I've
seen
those
projects
and
you
like,
browsers
and
stuff
that,
instead
of
releasing
a
monolithic,
they
released
like
modules
module
basis,
so
offensive
go
to
bring
up
in
the
future.
Some
point
where
you
know
core
stays
relatively
stable,
Illinois
reduces
our
path
time
and
then
certain
modules
are.
F
A
E
Yeah
so
I
released
the
blog
post
a
little
while
ago
and
actually
just
tweeted
about
it.
Yui
compressor
has
a
new
owner
and
that
owner
is
an
external
contributor
who
has
gained
committer
access
on
the
compressor
project.
Joey
Smith
has
been
running
a
fork
of
Yui
compressor,
where
he's
keeping,
where
he's
been
keeping
up
to
date
and
patches
and
fixes,
and
things
like
that,
because
he
has
a
vested
interest
in
it
and
he's
expressed
the
the
want
to
be
able
to
take
it
over
fully
and
actually
maintain
the
code
from
now
on.
A
A
E
D
E
So
I
created
a
team
on
there
and
gave
him
committer
access
to
it.
So
he
has
read
and
write
access
to
the
repository.
We've
redirected
the
developer
de
yahoo
com
site
over
to
the
github
pages
for
compressor.
So
he
has
full
access
to
update
the
compressor
pages.
One
of
the
things
we're
going
to
be
working
on
it's
getting
downloads
back,
because
downloads
are
missing
from
github
now
so.
D
E
D
E
E
Exactly
I
mean
the
the
st.
we
would
do
the
same
thing
for
PHP
loader.
If
somebody
came
up
and
decided
that
they
wanted
to
to
manage
the
PHP
loader,
we
would
do
the
same
process
with
them
builder.
If
somebody
wanted
to
maintain
that,
because
the
fact
that
you
know
you've
got
compressor,
people
are
using
builder
not
only
just
to
build
while
you
I
stuff,
but
to
build
like
their
projects.
So
someone
might
want
to
be
able
to
control
over
that.
You
know
any
any
of
our
products
like
that
I
mean
even
even
our
normal
ones.
E
E
Yeah,
you
know
we
would
look
at
the
same
thing
for
yo
shifter,
Yui
doc,
Yeti
any
of
those
that
if
some
community
member
gets
involved
and
starts
modifying
code
and
wants
to
to
help
maintain
it,
we
r
you
know
fully
capable
of
giving
them
committer
access.
Just
like
we
do
on,
though
you
know
the
j
s
part
of
our
library.
All
these
other
tools
have
the
same
problems.
A
E
Actually,
he
came
looking
for
us.
He
commented
on
the
blog
post
for
why
uglify,
where
we
said
that
we
were
deprecating,
yui
compressor,
so
him
and
I
started
talking
after
that
about
their
vested
interest
in
using
it,
and
that
he'd
been
maintaining
a
fork
with
all
the
patches
and
fixes
and
keeping
things
up
to
date.
So
we
just
moved
from
their
school.
A
Okay
from
here,
if
no
one
else
does
any
more
comments
back
to
presser,
we
have
the
standing
items
about
step
for
requests
and
unsigned
bugs,
but
how
I
just
are
open
things
up
quickly
before
that
I
don't
know,
tio
had
something,
but
you
can
make
it
today.
So
is
there
any
other
issues
that
you
had
before
moving
into
the
stable
request.
D
D
D
B
E
D
If
you
go
to
the
issues
tab,
you
are,
the
pull
request,
show
up
as
issues
with
a
little
code
attached
tag
or
whatever
you
want
to
call
it
on
it,
and
then
we
can
apply
issues
there
and
then.
D
D
A
A
B
B
C
D
A
Ironically,
this
will
make
the
malt
remote
I.
Can
someone
make
them
drop
off?
Is
it
title
change
one
thing
now,
the
second,
the
next
one
on
the
list.
This
you
sure
this
actually
is
the
criteria
for
this
is
two
weeks.
Is
that
correction
or
maybe
shorter
than
the
next
one
is,
as
skinned
word,
other
enhancements
its
number
for
Crescent
165?
That's.