►
From YouTube: 2016-12-20 Build WG Meeting
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
Well,
a
warm
welcome
to
the
last
build
the
working
group
meeting
the
node.js
build
working
with
meaning
of
2016
with
me
today.
I
have
Joelle
and
that's
about
it
we're
only
two
today,
but
you
know
we
obviously
are
the
most
important
guys
in
the
bill
group.
So
that's
what
it
is
anyway,
I
guess
we
should
just
start
in
a
normal
fashion,
with
stand
up
and
I
just
want
to
notice
as
well
that
we
actually
haven't
had
a
meeting
in
a
while.
A
A
B
A
I
know
you've
been
doing
some
work
on
this
general
see
I
as
well.
Okay,
anyway,
I
think
the
biggest
items
have
been
doing
is
we.
We
were
running
out
of
space
on
the
backup
hosts
I.
I
randomly
logged
in
no,
why
I
kind
of
look
around,
even
on
than
we
were
at,
like
ninety-five
percent
allocated
and
the
main
reason
for
the
quicker
growth,
because
when
I,
when
I
initially
george,
I
had
media
had
roughly
a
year
in
the
current
growth.
A
A
I
also
did
some
work
with
regards
to
the
downtown
we
had
a
week
and
a
half
ago,
so
the
node.js
main
host
a
biblical
ocean
was
experiencing
network
related
issues
and
I
was
working
pretty
closer
together
with
the
digital
ocean
support.
In
order
to
resolve
it,
we
had
roughly
four
to
five
hours
of
have
some
downtime,
but
like
very
intermittent
issues
and
for
most
users
they
couldn't
be
Gamelyn.
This
has
had
pretty
severe
ramifications
because
you
know
you
have
no
gip,
which
downloads
headers
or
a
tarball.
You
have
Travis.
A
You
have
all
kinds
of
infrastructure
that
rely
on
downloading
nodejs
as
part
of
their
work
clothes.
So
it
was
really
getting
pretty
heated
at
the
end
of
the
run,
but
yeah
we
managed
to
get
back
to
normal
pretty
quickly.
There
was
no
loss
of
daughter.
There
was
no
issues
with
that.
It
was
purely
network
related.
A
A
We
should
also
look
at
improving
our
resiliency,
so
we
should,
for
instance,
use
the
unencrypted
host,
which
mirrors
you
know,
gets
host
as
another
mirror
and
try
to
redirect
traffic
from
club
drug
if
our
main
mirror
goes
down,
I've
been
doing
some
minor
work
and
the
refactor,
as
always
I'm
gonna,
have
more
time
on
Christmas.
The
idea
is
to
try
to
get
it
into
a
real
shape
done
and
I've.
Also,
more
importantly,
been
work
continues.
Booing
continues,
work
on
the
tab,
2
j
unit,
python
script,
which
aims
to
help
us
with
growing
pains
of
jenkins.
A
Since
we
upgrade
again
means
to
yankees
two
we've
had
a
much
better
quality
of
life,
I
would
say,
but
there's
still
a
lot
of
50
for
25
or
30
into
a
specific
job
like
arm
fan
or
windows,
where
you
have
a
lot
of
build
history.
So
getting
this
into
production,
it's
a
really
high
priority
of
mine
and
will
hopefully
solve
all
the
problems.
We
have
a
Jenkins,
not
okay,
not
all,
but
a
few
and
the
reason.
A
It's
not
really
out
this
because
I'm
just
trying
to
finish
full
debian
seven
support
in
our
ansible
scripting,
which
yeah
I
have
to
roll
to
the
init
script.
So
if
anyone
likes
working
with
wn7
init
scripts,
which
is
like
some
old
flavor
of
suspended,
feel
free
to
ping,
me
finally
I've
been
doing
some
work
on
like
Jenkins
jobs.
A
We
have
in
terms
of
before
to
the
get
out,
but
like
it's
very
error-prone,
because
there's
so
many
scenarios
where
you
have
the
matrix
jobs,
you
have
the
fan
jobs
and
you
have
the
multi
jobs
and
all
of
them
have
like
different
branching.
So
getting
that
to
work
flawlessly
is
yeah,
it's
kind
of
a
constant
work
in
progress.
B
Joint,
oh,
he
did
yeah,
but
is.
C
C
I
think:
well,
it's
been
a
minute
since
we've
had
any
meetings.
Since
then,
we
now
have
a
team
of
about
five
different
people
on
canary
the
gold
mine.
Now
it's
been
moving
forward,
pretty
pretty
quickly.
C
A
C
There
was
a
meeting
it
interactive
with
a
group
of
people
talking
about
like
alternatives
for
the
installer
and
solutions
moving
forward.
I
think
it
would
kind
of
it
was
a
conflation,
and
I
mean
that
in
a
good
way,
even
though
that's
a
negatively
charged
word,
but
between
the
installer
and
the
version
management,
stuff
and
nvm.
So
if
you
go
and
take
a
look
on
that
version
management
repo,
there
was
a
lot
of
discussion
that
came
around
to
like
what
we're
trying
to
accomplish.
C
Why
we're
trying
to
do
it
and
I
was
of
the
impression
number
other
people
agreed
that
you
know
we
have
this
kind
of
installer
story
problem.
You
know
we
have
all
this
really
bespoke
tooling
in
there
and
it's
just
super
fragile.
So
we
started
looking
into
like
you
know
like
what
could
potentially
be
standardized
as
far
as
like
what
the
installer
and
these
various
version
management
tools
share
and
then
also
a
bit
of
a
look
into
like
what
other
tools
we
could
be
using
an
electron
was
kind
of.
C
A
C
Know
I
think
it
kind
of
falls
under
the
build
group
in
my
own
opinion.
As
far
as
you
know,
the
installer
is
concerned
and
even
the
version
management
story,
because
that's
all
kind
of
you
know
part
of
tooling
the
other
one
that's
probably
worth
bringing
up
is
the
gnu
debugger
repple
are
the
two
been
following
that
issue:
yeah
cool
because,
like
there's
some
interesting
discussion
right
now
about
how
it
should
be
embedded,
whether
or
not
it
should
be
done
like
NPM
or
whether
or
not
is
done
slightly
differently.
That's
again,
something
that
would
affect
build.
A
I
think
I
mean
both
of
those
are
pretty
active
in
terms
of
you
know,
deciding
on
what
to
do
so.
I
think
you
know
once
the
path
has
been
choice
in
shoot
chosen.
We
should
kind
of
open
an
issue
at
our
at
our
place
and
see
what
you
know
how
it
affects
us
and
what
we
need
to
be
doing.
Okay,
but
yeah
I'm,
actively
monitoring
the
one
and
I
know:
there's
been
a
discussion
of
an
electron
I
haven't
really
engaged
yet
so
yeah
yeah,
okay,
pretty.
A
A
A
A
A
A
The
next
issue
is
number
48,
for
which
is
a
draft
text
for
HST
s
communication.
So
this
is
coupled
with
our
encrypted
unencrypted
server,
as
well
as
making
no
j.
Sh
t
is
only
Michael
wrote
a
proposed
text
which
we
kind
of
accepted,
but
in
here
I
need
to
be
adding
a
bit
of
information
about
the
arcing
situation,
because
if
we
enforce
this
some
people,
we
also
need
to
give
them
an
alternative
in
terms
of
how
they
can
access
downloads
of
node.js
and
this
without
necessarily
having
SSL
or
modern
ssl.
A
A
A
So
the
quick
back
story
is
that
the
tap
plug
Lane
is
pretty
much
one
of
the
main
reasons
why
our
Jenkins
is
excruciatingly,
Lee
slow.
It
is
faster
since
we
upgraded
to
Jenkins
to,
but
there
are
still
a
lot
of
50
fours
if
I
check
the
logs,
which
is
not
good
and
50
trees,
which
means
that
Jenkins
did.
A
The
gist
is
essentially
that
every
time
you
open
a
job
page,
he
also
jokin
open,
20
or
30
jobs,
and
for
each
job
you
might
have
five
or
six
workers
and
for
each
worker
you
have
a
tap
file,
which
then
is
parsed
every
time
it's
open,
and
if
this
just
runs
out
of
memory,
which
it
does
a
lot
or
it
just
gets
GC
doubt
you're
going
to
look
into
a
timeout.
So
the
solution
is
to
walk
away
from
top
and
the
way
we
do
this
is
instead
of
walking
away
from
it.
A
A
The
reason
we
chose
part
python
is
that,
because
it's
a
main
requirement
for
ansible,
which
we
use
or
orchestration
the
tool
is
done,
it's
it's
very
rudimentary,
but
what
remains
to
be
done
is
just
making
sure
it's
on
all
our
workers
and
the
reason
it's
not
on
all
our
work
is
just
yet
it's
because
some
of
the
inference
is
wn7.
Santo
is
five:
they
don't
even
have
set
up
tools
and
set
up
tools
or
dis.
A
You
do
is
nowadays
not
even
released
for
those
platforms,
so
I
had
to
jump
through
some
hoops
to
get
back
going,
but
we're
almost
there.
You
haven't
already
on
most
of
the
workers,
so
there's
just
a
few
that
needs
to
be
completed.
So
that's
also
one
thing:
I
really
want
to
focus
on
over
this
holiday,
so
I
guess
I'll.
Just
I.
Don't
note
that
I'll
do
that
as
well.
A
A
While
we
had
no
issues
with
no
jstor
org,
because
people
were
asking
for
a
mirror
and
the
problem
was
that
we
recently
changed
our
triple
dub
host
and
the
keys
changed,
which
means
that
the
the
house,
when
it
tried
to
do
the
are
sinking,
didn't
really
updates,
so
I
had
to
fix
that,
but
now
its
back
and
its
same
thing,
every
15
minutes.
So
the
endpoint
that
unencrypted
dog
no
gesture
or
should
be
working
just
fine
both
to
http
and
through
or
sink
I.
A
C
A
So
me
and
you
all,
we
just
had
a
quick
chat
before
we
went,
live
and
I
think
you
know
you
and
you
and
me
talked
about
it.
We
can
have
a
go.
The
idea
is
that
we
first
of
all
want
to
use
cloud
fire
to
shield
our
downloads
to
have
them
just
serve
it,
so
we
don't
have
to
and
what's
holding
us
up,
there
is
pretty
much
that
we
need
to
fetch
the
logs
from
culture
in
order
to
keep
our
scripts
that
generates
download
statistics
going.
A
A
The
second
thing
we
want
to
do
is
set
up
a
mirror.
We
already
have
the
mirror
at
unencrypted,
no
no
Jay
sword,
so
my
thought
was
that
we
could
add
it
to
cloud
player
and
then
I'm
not
sure
what
kind
of
traffic
routing
you
have
available
at
their
place
when
it
comes
to
business
or
enterprise
accounts,
but
my
idea
was
to
have
them
redirect
traffic
to
their
if
it
if
it
falls
so
and
I'm.
A
Third
and
lastly,
we
are
also
exploring
ways
of
setting
up
a
a
mirror
of
the
image
or
of
the
machine
even
at
digital
ocean,
so
we
can
distribute
traffic
between
those
two.
We
haven't
really
resorted
or
resolved,
how
we
do
it
yet,
but
it's
a
work
in
progress,
and
that
is
currently
between
me
and
rod
quite
cool,
but
I
think
you
know
getting
cloud
for
it
to
serve
it.
A
Okay,
so
the
last
issue
is
issued
for
95,
which
is
looking
for
issues
for
a
good
first
contribution
and
I.
A
A
How
do
we
have
anything
else
we
want
to
add
to
it
or
to
this
issue
I
know.
I
know
we
have
I'm
just
trying
to
find
his
name
Haley
from
Italy
that
Michelle
yeah
yeah.
So
it's
a
good
example
of
someone
that
you
know
started
contributing
through
this.
So
it's
great
to
see.
I
know
he
filed
the
PR
just
today
about
improving
the
windows
deployment
around
school,
so
you
know
keep
it
coming.
Micheline
Michaela,
perhaps
sorry.
A
So
that's
the
agenda:
do
we
have
anything
else?
You
need
to
discuss,
I,
guess
one
thing
which
I
just
want
to
bring
up
its
that
we
are
working
on
a
post-mortem
on
what
happened.
We
can
have
a
go
with
no
Jace
organ
and
I
feel
like
it's
important
that
we
communicate
this
to
our
community,
because
it's
pretty
obvious
that
if
nodejs
or
it
goes
down
a
lot
of
third-party
Services
also
does,
and
we
need
to
make
sure
that
we
maintain
a
certain
amount
of
quality
for
the
service.
A
C
A
Okay,
anything
else
besides
me
talking
all
the
time
as.