►
From YouTube: npmCamp 2016 - Lightning Talk - Asynchronous wombats: developing OSS globally by Daijiro Wachi
Description
Lightning Talk - Asynchronous wombats: developing OSS globally by Daijiro Wachi
A
Yeah
I'm
kind
of
nervous
right
now,
because
I'm
so
excited
to
join
this
camp
and
meet
you.
Finally,
I
have
been
a
contributor
to
am
PM
for
a
couple
years
now
and
I
have
seen
a
lot
of
great
things
happening
in
this
community
and
on
github,
but
since
I'm
from
Japan,
it's
sometimes
hard
to
during
the
interesting
discussions
on
pull,
request
or
issue
report.
So
today,
I'm
here
to
talk
to
you
about
some
of
the
communication
issues
from
our
differences
face
on
github
on
the
daily
basis.
A
To
start,
let's
see,
em
p.m.
Who
am
I
and
present
there's
a
long
option.
My
name
is
digital
at
watch
it
on
github
I'm,
one
of
the
implement
a
greater
responsible
for
the
free
version
and
post
version
hooks
and
have
cultivated
other
bits
and
pieces
to
over
40
patches,
I'm,
always
looking
to
join
open
communities
related
to
knowledge
is
like
a
interworking
globe
in
nodejs
or
no
to
school
or
yes,
something
like
that
and
the
other
side.
A
Recently
I
joined
the
team.
Mystic
yeah
I'll
be
in
Pokemon,
go
not
that
it
matters,
but
it
matters
and
I
have
always
been
interested
in
driving
into
new
and
different
culture.
I
used
to
mainly
do
this
by
getting
involving
always
as
development
projects
on
github,
but
last
October
I
took
a
big
jump
and
relocated
from
Tokyo
to
Amsterdam,
and
today
Here
I
am
in
Auckland
Freddie's
camp.
It
seems
like
almost
around
the
world
trip
recipe.
A
So
it's
true,
no
Jay!
Yes,
we'll
take
you
around
the
world.
If
you're
a
dedicated
server,
/
well,
yeah
I
think
most
of
you
here,
its
knowledge
is
diverted,
so
you
have
probably
been
asking
something
related
to
knowledge
es
by
your
friends
or
colleagues
months
ago,
my
colleagues
sitting
next
to
me
got
confused
like
this
cat
and
asked
I
get
around
when
their
own
MPM
install.
Oh,
you
are
reportedly,
but
she
didn't
get.
Give
me
much
detail.
So
I
asked
ok,
show
me
your
empty
empty
backlog.
Please
and
she
gave
me
the
five.
A
A
Think
it's
a
quite
general
conversation
and
in
this
case
it
takes
only
10
minutes,
but
in
a
global
OSS
project
it
can
take
a
week
to
result
because
of
some
gaps.
One
of
those
gaps
is
time
difference.
If
the
issue
reporter
lives
in
Tokyo
and
mpm
divert
all
lives
in
New
York.
There
are
30
hour
due
time
difference
between
the
two.
For
example,
the
reporter
asked
the
same
question
at
ten
a.m.
in
tokyo.
A
I
get
a
era
when
I
wrong
npm
install
10
am
in
total,
but
it's
9pm
in
New
York
the
day
before,
and
the
burper
might
be
doing
something
really
into
town
important
things
like
drinking
a
beer.
So
maybe
he
or
a
she
doesn't
get
the
question
until
the
next
day
their
time,
so
they
don't
actually
look
at
it
until
King
a.m.
the
next
morning,
and
eventually
she
said,
show
me
your
MP
md
backlog.
A
Now
it's
10
a.m.
in
new
york,
but
Alabam
p.m.
in
tokyo
and
after
the
30
hour
delay
the
issue
reporter
finally
gets
a
response.
Now
we
know
japan's
developer
a
very
hard-working
so,
of
course,
reporter
immediately
replies
at
eleven
at
night
and
in
this
case
a
single
conversational
ball
spent
thirty
our
queen
are
going
around
the
world.
So
imagine
there
is
another
30
/
delay
for
the
new
york
developer
to
send
the
box
final
asset
to
our
I
developer
in
Japan.
A
A
Oops
and
another
major
gap
is
a
language
difference.
Well,
the
case
I
just
talked
about
is
fixing
a
tiny
bug,
but
questions
on
github
can
be
a
lot
more
complex
and
the
more
complex
the
question,
the
harder
it
can
be
to
upgrade.
Clearly
in
OSS
we
are
working
with
a
global
community
of
people.
Food
first
language
isn't
always
English.
Sometimes
it
can
be
so
hard
to
explain
an
issue
to
other
people
depending
on
what
language
we
speak.
Sometimes
the
result
just
doesn't
make
sense
and
it
creates
work
back
and
forth
to
try
and
reach
understanding.
A
But
beyond
the
questions
and
issues,
there
are
feature
requests
which
much
more
complicated
conversations,
because
it
usually
becomes
a
deep,
interesting
discussions,
plus
many
people
jumping
on
the
flat.
So
it's
not
just
one.
No
one
anymore.
Now
we
are
going
beyond
time
and
language
differences
and
adding
the
new
dimension
number
of
people
involved.
It
sounds
like
a
network
sighs.
A
The
cost
of
the
conversation
is
in
proportion
to
number
of
participants.
It
can
be
reckoned
up
by
Metcalfe's
law,
like
n
times
n
times,
n
minus
1,
/
2,
and
in
this
equation
the
more
participants.
The
more
time
is
spent
communicating
and
let
stores
a
line
on
the
world
map.
Actually
it
was
so
hard
to
add
all
of
us
a
line
manually
but
yeah.
This
is
what
exactly
we
are
doing
on
the
future
regret.
A
Then
this
question
determines
the
complexity
of
the
discussion
in
global
OSS
development
complexity.
Equal
distance
means,
like
a
time
difference
x,
language,
differences,
x,
network,
sighs,
it's
like
a
number
of
people
involved
like
I,
say,
and
we
can
separate
a
question
into
a
communication
issue
and
an
organization
issue.
A
Since
our
communication
is
like
an
sync
process,
we
can
use
the
same
solution
as
for
having
the
sync
process
in
jab
coding
and
in
JavaScript.
Vanya
Jes
has
promised
all
to
affect
weight,
handle
I,
think
processing,
but
in
vanilla
English
we
don't
have
a
method
to
do
it
for
us,
so
we
have
to
do
it
ourselves
by
increasing
the
details
and
clarity
of
our
questions.
A
Reporters
game
enough
detail,
the
information
and
those
answering
should
try
writing
clear
answer
easier
said
than
done.
I
know.
So
here
are
some
solutions
or
tools
to
handle
them
for
reporters
documentation.
Work
can
be
helpful
before
they
ask
as
a
pre
process.
You
know
recently
issued
template
is
added
by
interim
Emma
and
rid
o
me,
which
and
the
contributing
market
and
are
also
useful.
So
let's
increase
the
detail
and
the
clarity
of
our
documentation
and
for
it
does
answering
it's
really
important
that
imagine
the
actual
issue
reporters
are
having
even
they
are
missing
any
information.
A
An
easy
way
to
understand
your
problem
is
reproduce
so
use
the
same
version
of
the
knowledge.
A
yes
with
nvm
use,
the
same
version
of
an
MP
with
MP
and
blue
I,
build
it
and
use
the
same
always
with
another
laptop,
and
if
you
don't
have
it
go
amazoncom
right
now,
honesty.
This
is
what
I
have
been
doing
for
an
accomplice
in
mpm,
also
there's
a
good
way
to
handle
the
language
and
time
differences.
It's
good.
Having
a
localization
community
here
is
an
example.
A
I
did
I
try
to
open
the
issue
tab
on
my
vocal
repository
and
the
burb
burb
report
issue
immediately
related
to
mulch
bite
collectors.
Then
I
equated
the
patch
and
next
week
it
was
merged.
So
it's
an
effective
way
to
supporting
localization
community
with
the
focuses
on
an
active
contributor,
and
next
is
the
organization
actually
which
not
about
this
problem
entirely
in
global
development
and
I.
Think
the
discussion
is
ongoing
about
this
challenge.
A
The
only
thing
we
can
do
is
keep
having
fun
and
working
together
to
try
and
shrink
the
gaps
whenever
we
can
putting
our
brains
to
work
on
the
issue
constantly.
We
are
the
upper
hand
wheel
of
efficiency,
but
we
don't
have
to
always
have
a
technical
solution.
Some
of
these
problems
can
be
solved
so
charity
right
and
last
but
not
least,
I
never
could
have
made
it
this
far
over
the
years.