►
From YouTube: YUI Open Roundtable July 25, 2013
Description
YUI Open Roundtable for July 25, 2013
A
Alright,
hello,
everybody
welcome
to
this
week's
yui
open
round
table
for
july
25th,
so
13.
So,
as
you
can
see,
andrew
is
not
joining
us
today.
So
we
decided
to
mix
things
up
and
try
something
a
little
bit
different
and
kind
of
spread
around
and
see
if
it
works
better,
to
get
more,
essentially
more
cameras
going
as
opposed
to
everybody
all
cramming
into
one
conference
room
so
yeah.
A
B
B
Yes
see
in
the
documentation,
screen,
yeah,
ok,
so
it's
broken
down
into
two
components:
that's
paginator
core,
which
has
the
base
functionality
of
paginator
in
it
and
patching
under
URL,
which
has
URL
components.
So
if
you
have
a
URL
that
you're
wanting
to
have
pet
agitated
out
and
provide
links
to
it,
then
it
it
takes
the
URL,
that's
as
its
formatted
and
provides
the
page
number
in
the
euro.
Just
so
you
don't
have
to
keep
compiling
it.
For
you,
the
pageantry
core
is
typically
what
I
would
say.
B
B
Oh,
it's
a
gaucho,
it
doesn't
have
the
information
there,
so
I'll
need
to
get
that
corrected,
I'm,
not
certain.
Why
that's
going
on
alright!
So
there's
a
couple
of
attributes
that
are
there.
We
have
the
page
number
that
you're
on
the
total
number
of
pages,
the
items
per
page
and
the
tow
lines
actually
yeah.
Okay,
so
that's
that's
here
and
then
there's
four
methods
you
have
you
have
the
do.
We
have
a
next
page.
B
B
All
that
does
is
update
the
internal
page
number
and
has
previous
page
and
has
the
next
page
have
caps
on
them
so
that
they
don't
go
look
below
the
minimum
range,
which
is
page
one
and
above
the
maximum
range,
which
is
the
total
number
of
pages
in
total
number
of
pages,
is
actually
is
calculated
based
off
of
the
total
number
of
items
that
are
set.
So
if
you
have
ten
items
per
page
and
you
have
100
total
items,
then
you'll
have
10
total
pages.
B
B
Then
you
can
click
on
icon
that
you
want
and
go
to
that
slide
and
then,
whenever
we
mouse
over,
it
says
its
paws
when
everyone
else
out
it
regimes
the
slideshow
just
circles
around
now,
I
said
earlier.
That
next
page
has
a
cap
that
it
doesn't
go
past
the
max
number.
So
this
example
shows
you
how
to
do
with
continuous
slide
slide
show,
and
that
is
taken
care
of
with
the.
B
With
this,
so
whenever
the
timer
fires-
and
this
is
using
the
gallery-
module
from
why
timer
whenever
the
tower
fires,
the
town
or
event,
if
we
have
a
next
page,
we
go
to
the
next
page.
Otherwise
we
get
a
page
one.
So
that
gives
you
the
simulation
that
you're
just
continuously
leaping
around
and
around
the
room
and.
B
B
B
Obviously
this
is
done
for
you
if
you
use
data
table
with
paginator.
But
if
you
wanted
to
do
your
own
implementation
of
it,
then
you
could
get
here
copy
and
paste
and
it's
ready
to
go
or
something
that's
a
little
bit
more
robust
I
like
to
try
to
do
the
examples
in
three
different
stages.
So
this
right
here
would
be
the
more
advanced
one
where
we're
using
JSONP
and
it
actually
uses
the
model
view
from
the
app
framework
to
construct
this.
A
Knows:
okay,
so
one
question
I
guess:
I
do
have
with
paginator.
So
when
most
people
think
of
agitators,
it's
like
they
think
of
the
visual
aspect
of
a
janitor,
so
sin
thinking
or
what
you
have
at
the
bottom.
But
why
not
paginator
isn't
isn't
a
visual
widget,
it's
just
in
my
pregnancy
and
it's
just
going
to
be
underlying
all
of
the
implementation
logic
that
kinda
helps
build
these
interfaces.
Yeah.
B
That's
that's
exactly
what
it
is.
It's
just
the
implementation
logic
because,
as
you
can
see
with
these
three
different
examples,
there
three
completely
different
views
for
what
a
paginator
could
could
be,
and
you
can
even
take
a
paginator
and
make
it
into
a
tab
view
itself
and
have
create
multiple
tabs
with
different
content
on
the
pages
based
on
the
total
number
of
items
that
you
have
so
because
there
are
so
many
different
views,
it
would
have
been
crazy
and
so
from
different
files
to
ship
with
paginator.
B
And
then
you
would
end
up
overriding
it
your
to
make
whatever
kind
of
agitator
interface
you
wanted
whenever
it
was
also
done
anyways
so
to
keep
it
streamline
the
packaged
up,
the
reusable
components
which
is
the
core
and
the
URL
and
the
URL
is
even
separated
from
the
core,
because
not
every
one
of
them
uses
a
URL
paginator
and
then,
if
you
just
include
paginator
itself,
you'll
get
a
base
component
with
pageant
or
core
mixed
into.
So.
C
B
A
Yeah
so
we've
talked
about
it
in
the
past
and
I
just
haven't
had
a
chance
to
actually
dig
in
and
see
what
see
what
parts
of
paginator
could
actually
replace
the
scroll
p
paginator,
but
from
looking
at
it
it
definitely
looks
like
that
that
it
can
help
out
there.
Yeah
it'll
just
take
a
look,
a
bit
of
work
to
actually
hop
in
and
do
it
so
hopefully
at
some
point
that
would
happen.
A
B
Well,
there's
there's
a
lot
of
different
other
components
that
I
can
see
benefitting
paginator.
For
instance,
you
you
could
take
the
dial
widget
and
have
that
control
a
paginator
under
the
hood
and
I.
Think
that
would
be
really
interesting
to
have
a
dial
switch
through
pages
and
the
same
thing
at
you
with
a
slide
the
slider.
You
could
have
a
slider.
Tell
you
what
page
that
you
want
to
go.
Basically
anything
that
has
anything
to
do
at
all
with
number
increments
or
a
number
state
could
be
wired
up
to
go
towards
the
paginator.
B
As
I
said
before
the
tab,
you
could
be
something
that
is
built
using
a
paginator
under
the
hood,
where
each
tab
is
represents
a
different
page
yeah.
So
there's
there's
a
lot
of
really
interesting
ideas
that
I
have
of
what
could
use
paginator
under
the
hood.
As
far
as
the
visual
aspect,
but
I
haven't
really
seen
other
components
other
than
scroll
view
and
data
table
work
with
a
paginator
and
inside
the
component
itself.
D
C
Was
wondering
if
this
was
flexible
enough
to
handle
the
use
case
of
like
like,
for
example,
if
you
have
a
responsible
eight
that
might
you
know
the
layout
might
change?
If
the
user
changes
the
size
of
the
window,
then
you
know
you
have
to
maybe
have
to
dynamically
change
the
number
of
items
per
page
or
maybe
yeah.
E
C
B
You'd
easily
be
able
to
do
that.
There's
a.m.
there's
an
attribute
in
here
for
the
items
per
page
and
all
you
would
have
to
do
is
update
the
items
per
page
and
then,
as
whenever
the
items
per
page
changes
just
listen
for
that
and
tell
it
to
go,
go
to
the
first
page
or
grab
the
index
that
you're
on
do
a
calculation
to
find
out
what
page
you
should
be
on
and
then
go
to
that
page.
Okay,.
C
B
Right
so
there's
have
a
a
test
up
or
got
a
table
running
in
paginator
or
with
a
pageant
here,
but
I
don't
have
a
live
example
yet
so
we
have
to
turn
it
on,
and
this
is
what
the
table
would
look
like
without
a
paginator
in
it.
This
is
what
the
table
looks
like
with
the
paginator
in
it,
and
this
is
the
actual
you
I
that
shipped
with
the
CSS
and
everything
you
can
go
to
it.
B
B
B
So
that
full
example,
we
have
two
different
data
sets
that
we're
putting
in
and
there's
after
three
seconds
it
loads.
The
second
data
set
just
there
again,
it's
four
different
mechanics
that
are
going
on
with
paginator
and
testing
out
different
parts
of
the
functionality
and
so
I'm
loading
it
into
the
header
and
the
footer.
B
At
the
same
time,
I
set
the
rows
per
page
to
null,
but
whenever
we
first
turn
it
on,
I
said
the
rows
per
page
210
and
then,
whenever
the
the
other
thing
that
I
was
doing
with
this
is
that
whenever
we
go
from
page
to
page,
it's
under
the
hood
paginator
is
setting
up
the
each
function.
It
odd
metacognition
and
to
just
take
a
slice
of
the
data
for
wanting
to
display
at
one
time
and
that.
B
Is
right
here
so
that
each
function
will
actually
just
get
a
slice
of
the
based
off
the
index
and
the
link
that
we're
going
to,
and
so
that's
it
was
really
convenient
to
be
able
to
do
that
and
then
it
ends
up
the
whole
paginator
itself.
Unless
you
have
some
funky
UI
stuff,
that's
going
on.
It's
literally
just
including
data
table
paginator
in
the
youth
statement
and
then
setting
up
this.
A
Well,
that's
really
cool
just
seems
very
simple
and
pretty
straight
forward
to
actually
get
it
up
and
running
inside
the
paginator.
So
it's
nice
to
get
yeah
I
can
just
imagine
I,
guess
from
from
your
perspective
of
creating
paginator
and
then
using
data
table
is
kind
of
the
use
case
for
guiding
some
of
the
implementation
as
we
built
in
paginator
yeah.
B
A
I
remember
talking
with
Luke
mono
almost
two
years
ago.
It
is
when
I
was
working
on
some
scurvy
stuff
and
they
were
saying
that
he
wanted
to
get
a
paginator
built
for
data
table.
It
could
also
be
used
for
scrollview,
and
just
from
that,
quick
conversation,
I
didn't
quite
make
sense.
How
data
table
and
scroll
view
could
sure
is
similar
paginator
because
they're
so
completely
different.
But
then,
when
I
look
at
it
from
not
being
an
actual
widget,
but
the
underlying
implementation
of
imaginator
yeah.
B
B
And
the
other
thing
is
like
the
way
the
patch
intercourse
set
up.
If
you
are
using
a
model
of
you,
you
can
just
mix
pageant
your
core
into
a
model
and
it's
ready
to
get.
You
don't
have
to
do
anything
else.
It
will
already
give
you
all
the
data
information
for
the
page,
number
being
updated,
the
items
per
page
being
being
updated
and
the
total
number
of
pages
being
updated.
So
you
get
all
that
out
of
the
box
just
by
mixing
it
in
you,
don't
have
to
do
any
extent,
extending
Emma
data.
Oh.
A
A
A
That
includes
all
of
the
changes
necessary
for
updating
the
pull
request
to
essentially
to
do
for
that.
So
in
this
pull
request
that
kind
of
outline
what
it
is,
we're
trying
to
do,
some
of
the
problems
with
recurrent
tasks
that
you
have
and
a
couple
different
ideas
on
how
we
can
address
these
so
the
way
the
current
of
the
way
the
performance
tests
are
in
this
or
the
state
that
they're
in
in
this
poor
request
is
actually
in
this.
It's
a
kind
of
a
configuration.
A
It's
not
straight
I
can't
say
that
it
is
actually
JavaScript
because
it
doesn't,
you
have
to
actually
wrap
it
in
boy.
You
enough
took
your
pen
like
I.
Don't
know
bar
data
equals
been
this
object
here
but
anyway,
so
it's
a
configuration
object
that
can
easily
be
eval
din,
whatever
JavaScript
environment,
Iran,
and
then
turn
this
string
into
an
object.
So.
A
Structuring
the
performance
tests
like
this
makes
it
really
really
simple
and
pretty
straightforward
when
you
actually
both
need
to
parse
it
as
well
as
we
divide
in
the
task
to
it,
because
there's
a
very
little
confusion
in
terms
of
the
scoping
and
what
actually
is
going
on
here.
So
the
alternative,
at
least
that
I
came
up
with,
was
something
that
looks
very
similar
to
like
finish
much
chaos
as
well
as
what
we
currently
have
an
unit
testing
in
it
all
day
with
blood
tests.
A
So
basically
you
create
like
a
performance
test
suite
and
then
the
other
sweet
object.
Then
you
start
adding
test
center.
Now
we
could
go
with
this
approach
as
well,
but
I
think
there
are
a
few
downsides
here
in
that
it
is,
it
does
require
a
little
bit
more
work.
In
my
opinion,
it
is
from
my
perspective
for
the
developer
to
kind
of
memorize.
A
new
API
and
they're
also
can
be
some
some
issues
in
terms
of
what
happens.
A
If
you
put
code,
create
some
variables
or
something
outside
of
where
you're
adding
text
are
those
included
in
the
same
scope?
Is
your
best
or
not,
so
that
would
have
to
be
something
that
we're
kind
of
discussing,
and
there
are
some
some
issues
that
could
arise
from
that
to
just
terms
of
deconstructing
your
test
file
and
then
reconstructing
it
into
an
executable,
whether
it's
an
HTML
file
or
something
that's
fed
into
a
nodejs
process
to
execute
all
this
code
and
draw
the
results.
A
Basically,
if
you
are
going
to
go
to
route
deconstructing
in
the
truck
in
every
part
of
the
task
has
to
be
wrapped
in
some
type
of
some
with
an
object,
and
you
can't
have
things
just
kind
of
hanging
out
like
so
for
good
arm,
one
of
the
performance
tests,
that's
currently
in
either
that
so,
if
we're
going
to
test
and
then
performance
so
inside
of
the
node
test,
for
example
yeah.
So
here
this
is
the
node
attributes
test.
A
So
the
HTML
file
is
basically
just
includes
all
the
boilerplate
code
to
include.
Why
do
I
include
benchmark
OS
and
include
your
Yui
modules,
but
it
doesn't
actually
handle
any
parts
are
constructing
the
test.
Well,
one
of
the
problems
is
that
up
here
is
test
code,
but
that
isn't
inside
of
the
JavaScript
fry.
So
if
you
want
to
in
its
current
state,
if
you
wanted
to
consume
this
performance
testing
parts
it
in
some
way,
you
would
have
to
know
when
you
go
in
through
the
HTML
like
okay.
This
is
just
boilerplate
up
here.
A
Then
this
is
test
code
and
then
here's
some
more
boiler
tripod
and
if
there's
no
there's
no
really
easier
good
way
to
parse
it
at
this
point,
so
that's
kind
of
where
we're
we're
going
at
least
rebuilding
our
performance.
So
it
would
be
good
to
kinda
get
some
some
additional
feedback.
Some
people
have
already
chimed
in
on
it
and
but
yeah.
If
anybody
else
has
any
thoughts,
thoughts
on
that
I
don't
do
here
and
we're
getting
pretty
close
to
to
the
point
of
releasing
some
of
these
tools.
A
A
That's
okay:
we
got
something:
T
Lowe
did
actually
chime
in
on
some
comments
on
the
pro
request
and
then
hack
had
a
pretty
as
well.
So
oh
yeah,
I
know,
is
it
still
open
for
still
good
for
feedback
on
discussions?
So
if
anybody
hasn't
it,
that's
definitely
love
to
do
them
aside
from
stuff
to
screen
share
here.
A
Let's
see
the
first
deadline.
Whether
it
is
tag
is
honest
about
it.
That's
the
code
for
use
for
best
I've
had
so
there's
any
new
features
that
you
would
like
to
include
in
this
in
the
next
release
of
the
library.
That's
at
least
the
first
time
to
get
a
man,
but
beyond
that
anything
else
that
will
be
included
or
strictly
bug,
fixes
documentation,
updates
testing,
essentially
nothing
that
works
backwards.
Compatibility
so
we'll
round
up
some
time
right
around
the
11th
and
figure
out.
A
E
E
E
E
I
can
drop
elements
within
the
browser
with
the
nadaam
itself,
such
as
tables
buttons
forms
and
also
being
able
to
upload
images
using
the
file
uploader
API,
the
new
JavaScript,
and
also
possibly,
and
also
saving
state
saving
state
using
the
model
modules
in
Yui
library.
If
I
change,
different
views
and
a
download
link
where
you
can
download
the
theme
itself
so
yeah.
So
this
is
what
I've
got
so
far
and
I.
E
E
F
Be
cool
to
just
get
just
as
you're
working
on
it's
a
to
host
it
up
somewhere
you
soon,
people
can
start
using
it
and
because
the
features
you're
thinking
about
adding
seems
feeling
like
incremental
features.
So
it
doesn't
stop
some
from
starting
to
use
it
today,
apart
from
the
fact
of
I,
would
say
if
you,
if
you
get
that,
if
you
get
the
ability
to
download
the
HTML
CSS
in
somehow
or
just
like
link
to
a
place
which
shows
that
then
everything
else
can
be
incremental
after
you've
kind
of
launched
it
somewhere.
Some.
E
A
E
Serving
layer,
yeah
wow,
what
I
wanted
also
to
make
my
layout
generate
a
different
was
as
you
edit,
the
themes
you
know
typical
generators.
They
push
very
obtrusive,
styling,
CSS,
inline
style,
so
I
needed
a
back-end
to
be
able
to
access
this
file
system.
So
I
can
create
separate
external
style
sheets
and
be
able
to
write
to
those
style
sheets
and
so
any
edits.
That's
me.
I
can
push
that
to
those
external
style
sheets.
E
A
A
E
Currently
not
say,
but
right
now,
everything
that
the
show
was
all
done
is
out
in
front
side
with
basic
Dom
manipulation
and
some
of
the
why
you
got
models
but
front
side
as
far
as
style
sheets
I
know,
I
haven't
looked
too
much
into
it,
but
there's
a
stylesheet
module
within
Yui
I.
Don't
know
if
that
creates
external
style
sheets.
Thank
you
have
fun
gonna
do
external
file,
she
I,
don't
know
how
it
works,
but.
F
For
a
grid
builder
and
I
just
use
the
wild
y
dot
stylesheet
module
to
do
everything,
client
side
and
not
have
a
server-side
back
in
and
the
reason
I
do.
That
is
because
I
remember
where
you
are
hosting
anywhere
just
you.
It
just
works
off
github
pages
directly
but
like
I,
don't
fine
if
you're
like
right
now,
I
think
or
your
Express
app
is
pretty
much
so
so.
Firstly,
if
you
used
wideout
stylesheet,
I
think
it
would
simplify
your
code
a
little
bit.
E
F
E
E
E
F
Yeah
yeah,
that's
also
another
good
idea.
You
could
also.
You
could
also
do
that,
but
what
the
problem
of
doing
that
is,
someone
downloads
their
stuff
and
they
want
something
changes
to
it.
Just
more
Croft
to
look
to
like
that,
bae
since
64
thing,
yet
just
like
just
moorcroft
looking
and
looking
through
like
a
path.
So
that's
why
I
was
adjusting
if
path
exists
somewhere
in
the
internet,
you
can
just
link
off
that
path.
E
E
E
E
F
E
F
F
E
Definitely
yeah.
Definitely,
I
agree.
That's
exactly
what
I
want
to
do.
I
didn't
want
to
manage
people's
images
and
everything
else,
so
yeah
yeah
definitely
yeah,
but
definitely
yeah,
but
that's.
That's
all
I
worked
on
for
this
week.
Crew
now
look
forward
to
pushing
out
new
features,
at
least
once
a
week
later
on
and
possibly
trying
to
get.
This
thing
live
as
soon
as
possible
as
well.
Yeah
I.
A
A
A
E
A
A
A
It's
been
a
big
debate,
so
no,
no,
it's
probably
worth
actually
discussing.
It
is
not
me
email
a
little
bit
too
I,
don't
know
its
own.
It
was
young
I
hope
you
have
the
ability
to
specify
the
default
branch
that
you
want
on.
So
when
people
go
to
your
repository
right
now,
it's
set
to
master,
but
it
can
be
set
to
any
type
of
grant
you
one.
All
of
our
development
right
now
is
done
off
with
dev
master.
A
So
we've
been
discussing
whether
we
should
actually
update
that
default
branch
to
dev
master
instead
of
masters,
so
I
don't
know,
I've
I
don't
have
a
ton
of
thoughts
about
it.
It's
kind
of
like
there's
so
many
different
ways.
You
could
do
it
there,
alright
settling
on
kind
of
one
we're
trying
to
find
absolute
right
and
wrong
with
it
is
I.
Don't
know
that
that's
quite
possible,
but
I
don't
know
I
mean
I'd
like
to
see
us
just
get
rid
of
the
dead
branches.
All
together,
I,
don't
think
they're
there
to
necessary,
but
I.
F
A
F
A
F
One
of
the
one
of
the
one
of
the
issues
is
like
github
says
that
the
default
branch
should
be
the
branch
that
poll
requests
should
be
sent
to.
But
so
that's
the
official
word
right,
but
there
is
also
this
notion.
Like
I
mean
I.
Have
this
notion,
which
is
that
whatever
the
default
branches
is
kind
of
like
the
main
branch,
you
know
like
it's
like
what
I
should
clone
awful
like?
What's
gonna
get
close
and
what's
pretty
much
I'm
gonna
come
on
it
like
check
out
my
branches
from
that
branch,
sort
of
thing
right.
D
F
D
F
On
the
type
of
bug
I'm
trying
to
I'm
trying
to
solve
right
but
yeah,
so
it
depends
so
like
for
me
as
a
Yui
developer.
I
would
I
would
clone
either.
I
would
sorry
I
would
check
out
like
fork
from
either
dev
3x
or
deafness
and
thought,
let's
suppose,
you're
I,
don't
know
if
you're
using
Yui
and
you're
someone
else
out
there.
F
D
A
use
case
might
be
that
they
want
like
this
version
works,
so
I'm
gonna
take
the
stable
branch
and
then,
if
I
can
few
tweaks
that
I
want,
but
I
don't
necessarily
want
to
put
it
back
into
the
core,
because
it's
not
exactly
the
line.
Leaders
thing
right
so
with
that
use
case,
having
a
master
branch
default
would
make
sense.
D
D
D
A
F
F
A
A
F
A
F
My
problem
with
that
is
like
right,
I
think
it's
important
for
a
project
to
have
sort
of
a
stable
development
workflow
because,
like
not,
everyone
is
contrary
to
the
product
as
much
as
we
are
right.
So
once
someone
understands
that
okay,
dev
master
and
even
for
us,
like,
we
had
a
bunch
of
emails
that
Dave
said
and
other
people
said
to
remind
us,
like
oh
you're,
making
this
change
and
go
into
a
master
making
that
change
and
go
into
have
3x.
F
So
once
people
got
their
heads
around
that,
unless
we
have
a
very
good
reason
and
which
greatly
simplifies
something
I
feel
we
should
stick
to
that.
The
current
workflow
we
have,
unless
we
can
be
great,
it
can
be
greatly
improved
somehow
because
see
once
like,
I
think
that
there's
the
documentation
issue
once
we
change
it
and
it
becomes
something
new
that
it's
a
matter
of
people,
understanding
that
okay,
what
I
was
doing
initially
those
branches
no
longer
just
now,
I
have
to
go
to
this
other
bridge.
A
And
I
guess
to
counter
that,
I
would
say
unless
we
are
workflow
right
now,
I
feel,
like
at
least,
is
pretty
non-standard,
where
we
just
have
all
of
these
branches
that
we
we
kind
of.
Do
a
circular
flow
with
it,
so
branch
for
master
into
our
dev
one
and
then
develop
and
commit,
and
then
that
gets
pushed
up
in
the
CI.
And
then
it's
just
a
circle.
Players
I
really
feel
like.
A
It
should
be
much
more
linear
where
everybody's
just
you
do
your
development
and
then,
when
you're,
confident
that
your
code
is
what
you
would
consider
stable,
then
you
push
it
into
master.
But
then
that
just
goes
on
the
assembly
line
through
all
the
testing
processes,
and
then
it
eventually
learns
into
master.
F
F
E
A
Branches
names
two
different
things
on
in
one
fork:
vs
2,
similarly
named
branches
on
two
different
folks,
so
in
reality
I
mean
it's
really
just
kind
of
the
whatever
flow
you
kind
of
want
to
go
and
I.
Think
so
I,
don't
it
doesn't
matter
a
time,
I
think
we'll
kind
of
adapt
to
whatever
it
is.
We
have
but
oh
yeah
what
I
was
going
to
say
at
least
was
before
to
counter
your
opinion
that
we
should
stick
with
what
we
have
unless
it's.
A
Unless
we
come
up
with
a
pretty
good
reason
to
to
shift,
I
would
say,
because
we
have
a
pretty
non
standard
workflow.
It's
like
we
should
go
with
what
something
a
little
bit
more
standard
unless
we
actually
have
a
really
good
reason
why
you
can't
do
why
we
can't
move
at
the
standard
fashion,
so
I,
don't
know
I
mean
we
do
have.
We
do
offer
reasons.
I.
Think
I
think
we
could
do
some
to
tweak
that.
But
in
reality
it's
not
that
big
of
a
deal
on
exactly.
A
A
F
F
A
It
is
so
in
terms
of
what
exactly
happens
with
the
default
branch
on
github
I.
Don't
know
we
might
just
leave
it
as
is
to
not
open
up
at
that
can
of
worms,
but
I,
don't
know
we'll
see
in
the
meantime,
if
anybody
has
any
thoughts
on
or
experiences
with
changing
default
branches
for
large
contributor
and
projects.
Certainly,
let
us
know
with
yours
well
I
believe
andrew
did
all
of
the
scalpel
request,
reviews
and
reached
out
to
the
owners.
Okay,
so
you
can
skip
that
for
this
week.