►
From YouTube: CHAOSS.AsiaPacific.Community
Description
CHAOSS.AsiaPacific.Community
A
The
usual
request
is
for
some
set
of
organizations
on
github.
Okay,
that's
that's
typical.
Do
you
want
people?
Do
you
want
people
reaching
out
to
you
to
say?
Can
you
I
mean
I
have
the
capacity
to
do
that?
Okay,
this
time
it
worked,
I
had
to
reinstall
my
gecko
driver.
I
have
no
idea
why
okay,
but
what
go
ahead
don.
A
A
So
then
what
happens
when,
when
it
with
once
you've
installed
your
gecko
driver?
I
really
don't
know
why
I
had
to
reinstall
it.
You
get
these
png
files
that
are
output
to
the
images
directory
and
basically
it's
everything
you
see
in
the
jupiter
notebook,
but
these
I
I
do
this
really
for
my
own
purposes,
when
I
want
to
run
something
I
seldom
want
to
have
to
copy
and
paste
everything
out
of
a
jupiter
notebook.
A
A
So
if
I
go
to
this
control
cell-
and
I
do
save
files
true
and
I
run
I
run-
all
cells
it'll-
generate
the
image
files
for
the
pull
requests
as
well
and
here
here,
okay,
we're
doing
pull
requests,
we're
still
doing
auger
and
femoral.
Oh,
that
was
a
strange
sound.
Is
that
me
and
again
you
get
all
this
jupiter
labs
stuff
at
the
front,
because
you
it's
just
the
way.
Jupiter
lab
works
and
all
the
good
stuff
is
at
the
end.
I
don't
know
if
there's
like
a
jupiter
lab
god
around.
A
A
How
many
comments
are
on
each
pull
request
and
then
the
closed
pull
request
by
merge
status,
and
here
we've
separated
the
slowest
20
percent
from
so
this
list.
20
are
not
they're
part
of
this
other
set,
which
I
suppose
we
should
make
more.
I
guess
it
says
all
so
this
is
everything
in
2019
there
were
252
pull
requests
and
40
were
not
merged
and
212
are
merged.
A
A
And
then
here
we
have
the
not
merged,
mean
days
to
closed
and
the
merged
mean
days
to
close,
so
you
can
see
everything
sort
of
compressed
down
here
in
2020,
we're
pretty
fast
and
then
looks
like
we're
even
commenting
on
pull
requests
on
average
several
days
after
they're
made
merged,
and
you
can
see
this
for
any
collection
of
repos,
and
this
just
gives
you.
This
is
a
dot
for
all
closed
poll
requests
over
time.
A
So
you
can
kind
of
see
when
things
are
happening
and
how
long
the
responses
take
overall-
and
you
know
what
you
want
obviously
is
to
be
under
a
day,
and
so
you
can
see
there's
some
that
we
take
longer
on
and
then
you
can
also
see
for
the
pull
requests.
You
know
how
many
subscribers
there
are
on
average.
This
is
a
wider
graphic.
A
A
Okay,
I'm
getting
really
sorry
about
this.
My
browser
is
acting
really
weird.
It's
like
not
adjusting
the
width,
there's
some
instructions
down
here
about
this
control
cell,
so
there's
variables.
So
the
repo
set
is
the
list
of
repos,
and
you
can
say
that
repo's
not
aliased.
That
should
be
so.
You
can
like
take
the
names
out
of
competitors.
A
If
you
don't
want
to
show
them,
save
files
can
be
true
or
false,
and
your
start
and
end
dates
can
change,
depending
on
the
analysis
period
that
you're
looking
at
and
we
we
do
for
pull
requests
for
for
new
contributors,
we're
looking
at
all
new
contributors
all
time
so,
regardless
of
when
you
run
your
time
window
for
if
somebody's
made
a
contribution
prior
to
that
time
window,
we
we
don't
count
them
as
a
new
contributor
within
that
time
window.
We
just
we
see
that
they've
made
a
prior
contribution.
A
A
A
D
A
Yeah,
I've
done
it
and
I
would
I
mean
I
think
it
gives
us
a
chance
to
test
auger
against
new
data
and
okay
for
us.
That's
the
advantage
is
it
it
gives
us
like
live
data,
and
we,
you
know
you.
I
think
we've
done
enough
repositories
now
that
we're
not
encountering
new
anomalies
very
often,
but
occasionally
there'll,
be
weird
kinds
of
things.
Am
I
really
out
of
focus
for
some
reason
you
are
strangely.
C
D
A
D
D
E
D
A
D
F
A
Not
I
mean
for
me,
I
mean
especially
for
us,
we
do
it
all
the
time,
so
I
think
I
think
the
feedback
is
from
from
an
auger
perspective.
The
feedback
is
valuable
enough
that
that
offer
it
broadly,
and
so
it
becomes
a
problem.
Okay,
you
know
so
far.
The
the
requests
informally
have
not
posed
a
problem,
and
I
think
yeah
so
I'll
put
a
form
on
the
on
the
auger
labs
site
to
make
that
request.
D
Yeah,
okay,
exactly
just
because
yesterday
it
came
up
that
the
the
notebooks
are
pretty
valuable
resource
that
people
seem
to
to
like
yeah
and
there's,
obviously
a
little
bit
of
back
end
work.
That
needs
to
be
done,
and
so,
like
one
option
is
just
to
say,
we
don't
do
any
of
that
back
end
work
for
you
like
as
a
community.
We
can
just
kind
of
pass
and
say
we
don't
do
that.
D
So
if
you
want
to
use
the
jupiter
hub
notebooks
that
we
have,
you
have
to
deploy
your
own
instance
of
auger
and
collect
the
data
yourself.
We
that's
an
option.
The
other
option
is
saying
you
can
do
that
or
we
will
actually
collect
the
data
for
you
and
provide
you
read-only
access
to
a
database
for
the
repos
that
you
would
like.
Yeah.
A
A
Yeah,
I
have
a
I
have
through
the
requests
we
have
so
far.
It's
become
it's
pretty
easy.
If
someone
has
like
a
set
of
github
organizations,
I
think
I
think,
for
if
we
get
if
we
get
in
the
neighborhood
of
like
beyond
3000
repos,
I
think
sometimes
the
collection
takes
longer
than
than
people
expect,
and
that's
that's
really.
A
The
first
collection
that
takes
a
long
time
because
you're
counting
the
commits
in
every
repo
and
it
depends
on
the
it's
a
function
of
how
the
repository
has
been
maintained,
and
if
you
have
a
lot
of
repositories
that
have
been
like
fundamentally
refactored,
okay,
more
times
where
basically
every
file
changes,
then
you
get
these
gigantic
commits
and
those
those
just
take
longer
to
count
the
first
time,
okay
and
but
once
you're
through
the
first
time.
Then
it
doesn't
take
that
long
to
continuously
update
it.
A
D
Okay,
so
the
request
would
be
basically
then
like
on
the
auger
lab
site.
Somebody
could
make
a
request,
but
that
request
would
basically,
it
sounds
like
say,
like
sean
I'd
like
to
have
a
conversation
with
you,
yeah
setting
up
a
database
yeah
yeah,
because
you
could
explain
all
of
that
to
them
kind
of
in
an
out
of
band
conversation.
A
D
A
A
D
Because
I
know
I
know,
gramorlab
has
a
new
tool
that
they're
working
on
called
broomstick
and
broomstick
is
that's
right.
Just
stick
with
it
right.
Broomstick,
hang
with
us
here
for
a
second
yeah
is
a
tool
that
is
is
doing
just
this.
It's
providing
notebook
access
to
the
elasticsearch
data
on
the
back
end,
so
so
we're
going
to
have
two
tools
that
are
kind
of
providing
jupiter
hub
notebook.
D
E
D
A
D
A
Because
I
think
the
the
interesting
thing
about
that
idea,
which
had
not
occurred
to
me
before,
is
that
the
atomic
metrics
we're
defining
are
useful
to
the
community,
primarily
because
they
create
standard
definitions
of
all
the
things
that
we
spend.
But
you
know
early
in
the
project
we
spent
days
weeks
months
debating
what
a
commit
is
and
how
to
count
it,
and
I
think
those
debates
have
existed
in
the
open
source
community
for
some
time
and
we
don't
claim
to
have
the
right
answer.
A
But
we
have
a
consistent
answer
to
that
question
so
that
people
can
use
the
tools
that
that
are
part
of
the
chaos
project
and
get
consistent
results
from
them.
And
so,
similarly,
what
these
notebooks
are
doing
is
really
aggregating
a
whole
set
of
these
metrics
and
displaying
them
in
a
way
that
people
can
more
easily
consume
them.
So
on
the
new
new
contributors
is
a
measure
but
we're
showing
you
new
contributors
over
time
and
some
and
putting
some
specific
parameters
on
what
kinds
of
contributions
are
being
counted
in
these
notebooks
right.
A
So
so
yeah
I
mean
like
a
six
month
review.
I
mean
I
guess
I
I
babbled
there
for
a
bit,
but
I
guess
I
guess
my
point
was
that
these
are
these
are
comp.
These
are
consorts
and
these
are
actionable
representations
of
usually
more
than
one
metric
yep
totally
and
and
that's
what's
different
about
the
notebooks,
and
I
think
for
that
to
go
through
a
community
review
process
similar
to
the
metrics,
so
that
people
can
actually
put
eyes
on
this.
A
In
a
context
and
say
I
have
a
question
about
where
this
data
came
from,
or
this
data
doesn't
isn't
what
I
expected
and-
and
it
become
almost
kind
of
a
peer
review
that
or
according
to
the
metric,
we
don't
count
this
or
that
like.
It
could
be
a
peer
review
of
these
reports
in
a
sense
that
the
community
that
does
a
review
process
for
so,
if
that's
certainly,
if
that's
something
the
community
wants
to
make
part
of
the
larger
chaos
project
or
the
process.
D
B
The
these-
I
don't
know,
I
guess
feeling
I
feel
like
a
review
process-
would
be
overkill
for
the
jupiter
notebooks.
I
feel
like
people
who
are
using
them
can
go
ahead
and
provide
feedback
on
them,
but
it
seems
to
me
like
just
getting
them
out,
for
people
to
play
around
with
is
probably
more
important
than
putting
them
through
a
final
review
process.
B
E
D
So
do
you
think
that
the
jupiter
hub
notebook
should
be
provided
in
a
more
structured
way,
like
maybe
on
the
website
or
not
really
so
like
one
of
the
things
as
like
that
we're
always
trying
to
work
on
is
how
do
we
connect
the
metrics
with
the
tooling
to
get
it
out
in
front
of
people,
and
so
I'm
not
sure
people
track
like
the
software
releases.
So
much
you
know.
So
if
jupiter,
I'm
sorry,
if
grimorlab
has
a
release,
that's
great,
but
I
don't
know
that
that's
tracked
too
much
or
auger
has
a
new
release.
D
D
D
We
want
these
jupiter
hub
notebooks
to
be
like
a
little
bit
more
front
and
center,
something
that
we
talk
about
a
little
bit
more
broadly,
like
hey,
we
have
these
new
notebooks
that
have
been
released,
that
put
the
metrics
into
practice
or
something
like
that
kind
of
the
way
that
we
talk
about,
say
the
dna
badging
program
like
hey.
We
have
this
new
badging
program,
that's
putting
these
metrics
into
practice
and
if
we
do
it
with
the
notebooks
or
not
yeah,
so
I
don't-
I
don't
know
again,
I'm
not
making
it
stand
anywhere.
A
D
D
The
jupiter
hub
notebooks
kind
of
represent
so
when
we
do
a
release,
that's
kind
of
a
thing
and
that
we
can
talk
about
that
thing
of
the
metrics
and
that
gets
out
and
out
in
front
of
people
and
yeah
the
jupiter
have
notebooks.
I
agree
like
doing
a
formal
review
process,
probably
too
much
and
too
much
to
manage
and
but
yeah.
How
do
we
get
those
out
in
front
of
people
to
your
point?
Sean
yeah?
F
I
think
we
could
maybe
have
a
separate
section
on
the
website
for
it
and
like
when
we
do
have
a
new
one.
We
can
talk
about
it
on
twitter
or
you
know
how,
if
we,
you
know,
have
people
who
are
doing
speaking
at
conferences
and
things
like
that.
If
those
ever
come
back
or
online
conferences,
you
know
that's
something
that
we
can
talk
about
and
promote,
as
as
just
like,
you
said,
is
the
same
as
our
metrics.
I
don't
I
don't.
I
kind
of
agree
with
the.
F
We
don't
need
a
a
formal
review
process
because
it
doesn't
really
matter
like
what
version
you're
going
with
right,
like
it'll,
just
be
a
dynamic
thing
that
will
release
and
will
morph
over
time
as
we
get
feedback.
Is
that
is
that
right
or
or
is
it
like
nope?
This
is
the
version
that
you're
going
to
use
and
we
will
never
change
this.
A
A
The
things
that
one
set
of
organizations
wanted
answered
are
not
probably
uninteresting
to
many
organizations,
and
so
that's
how
the
two
jupiter
notebooks
that
we
published
came
to
be,
and
I
think
if
people
went
and
made
use
of
them
and
said
I'd
also
like
this
or
even
because
they're
jupiter
notebooks
built
additional
things
and
wanted
to
share
them
back.
I
think
that
would
be
very,
very
helpful.
F
B
E
G
G
E
Hi
everyone,
my
name
is:
I
come
from
huawei
and
I'm
now
implementing
the
university
of
huawei
and
I
always
think
unicef
is
a
way
we
want
to
use
an
open
source
like
development
in
the
interplays.
But
we
have
some
problems
about
the
in
the
source.
So
we
want
every
open
source
support
to
give
us
some
advice
and
the
first
questions
is-
and
just
just
like.
A
So
for
for
inner
source,
any
of
the
tools
on
the
github
repository
for
the
cast
organization
could
be
used,
and
you
would
just
have
to
point
them
at
so,
for
example,
depends
on
what
your
inner
source
team
uses
for
forget
repository
tracking.
If
it's
a
set
of
private
github
repositories,
then
you
can
operate
any
of
these
tools,
just
as
you
would
ordinarily.
A
As
long
as
you
have
credentials
on
the
user
that
you're
using
to
clone
the
private
repos
and
and
there's
ways
that
that
both
vermour
lab
and
auger
can
do
that
and
so,
and
if
it's
just
a
git
repository,
then
you're
only
going
to
get
commit
data.
If
you're
using
something
like
git
lab
or
github's
enterprise
platforms
for
your
intersourcing,
then
you
can
also
use
these
tools
to
gather
the
kind
of
data
like
issue
data
and
pull
request
data
that's
available
on
the
public
platforms
that
each
of
those
companies
offers.
A
So
how
much
of
the
data
is
available
for
intersourcing
is
definitely
a
function
of
what
what
technologies
you're
using
there
are.
There
are
technologies
and
gremore
labs
supports
things
that
auger
doesn't
support.
Ours
committed
to
prototyping,
get
github
and
get
lab
and
all
of
their
functions,
but
I
think
I
think
gremor
lab
also
handles
garrett
and
other
other
kinds
of
issue
tracking
sites
as
well.
E
Yeah
yeah
very
well
and
we
allow
deploy
they
get
a
label
in
the
huawei
internet
and
some
project.
We
can
set
up
the
project
in
this
system.
So
if
we
use
this
gitlab
and
we
can
get
some
metrics
from
the
universe
project
better,
but
now
we
don't
know
how
to
use
this
mexicans
and
how
to
evaluate
the
you
know,
source
project.
Does
this
community
is
health
or
not?
And
we
we
don't
know
how
to
drive
driverless
project.
B
E
A
It
sounds
like
what
you're
what
you're
asking
about
might
be
something
that
a
service
organization
that's
familiar
with
our
metrics
could
be
useful
for
I
I
don't.
I
mean
I'm
not
trying
to
plug
that,
but
it
sounds
like
there's
a
sort
of
understanding
what
your
needs
are
process
that
needs
to
take
place.
B
Oh,
I
was
just
gonna
say
I
dropped
a
link
to
to
the
patergia
inner
source
consulting
services-
page.
If
you
wanted
to
to
look
at
that,
I
do
think
it.
Probably
it
probably
wouldn't
hurt
to
get
a
little
bit
of
for
a
little
bit
of
professional
help
with
it,
whether
it's
petergia
or
or
someone
else,
but
I
think
it
might.
D
And
I
know
that-
and
I
know
that
the
inner
source
commons
that
don
had
mentioned
daniel
escuerto
who's
at
patergia
has
really
helped
and
with
the
cast
project,
has
really
helped
kind
of
tie.
Those
efforts
together
so
daniel
at
vitergia
is
also
very
skilled
in
thinking
about
metrics
that
are
applicable
from
an
inner
source
perspective.
D
A
Yeah
well
yeah,
you
need.
You
need
access
to
an
auger
instance
if
you're
not
able
to
get
to
these.
These
servers
are
located
in
europe,
so
I
don't
know
if,
if
that,
let
if
you're
like,
if
you're
ip
restricted
or
not
able
to
access
those
instances,
I
recognize
that's
been
an
issue
like,
for
example,
google
forms
on
the
asia
pacific
call
before.
A
A
H
A
Is
actively
working
on
a
git
e
plug-in
and
I'm
I'm
still
in
the
figuring
it
out
stage.
I
think
they
may
be
as
well,
but
I
just
can't
speak
for
them.
It's
a
it's
a
new
platform
for
all
of
us,
and
so
and
it's
you
know,
unlike
git,
lab
or
github,
where
many
of
us
have
used
it
before.
None
of
us
have
used
giddy
before
and
so
we're
just
trying
to
become
familiar
enough
with
it.
And
if
okay,
don't.
H
A
Oh,
I
can
point
you
to
the
auger
example
for
that,
if,
if
you
want
some
of
it,
I
think
is
reasonably
well
documented
in
our
read
the
docs
instance,
so
under
the
and
we
we
may
not
have.
Basically,
we
have
what
are
called
workers,
and
so
it's
the
the
goal.
What
you'd
have
what
you'd
have
to
do
is
write
a
worker
for
getting
to
collect
the
data.