►
From YouTube: CHAOSS Weekly Hangout: May 22, 2018
Description
CHAOSS Weekly Hangout - May 22, 2018
A
A
And
so
part
of
what
there's
also
another
tool
out,
there
called
auger,
which
is
what
Derek,
who
just
joined
and
Keano
or
working
on
and
that's
out
of
the
University
of
Missouri,
and
so
there
are
a
number
of
pieces
of
software
there's
another
one
called
credit
as
well,
which
is
tool.
The
Daniel
German
is
working
on
we've
different
pieces
of
software
that
we
also
support
in
this
community
that
we
can
use
to
actually
implement
the
metrics.
A
So
if
there
are
metrics
that
we're
trying
to
understand
with
respect
to
the
risk
category,
the
question
becomes,
can
we
actually
implement
this
metric?
Technically?
Is
that
even
possible?
So
just
because
we
have
a
wish
for
something
doesn't
mean
that
we
can
do
it
technically
and
obviously
we
have
found
that
some
of
the
metrics
we
can
gather
from
online
trace
data,
say
from
like
the
github
API
or
from
a
mail
list,
but
other
metrics
are
quite
difficult
to
capture
with
respect
to
that
kind
of
data,
so,
for
example,
understanding
diversity
of
speakers
at
your
conference.
A
Different
metrics
require
different
ways
of
collection.
Some
are
more
real-time.
Some
are
a
little
bit
longer.
So
on
one
hand
we
have
the
metrics
that
are
implementation,
agnostic.
On
the
other
hand,
we
have
the
the
pieces
of
software
which
are
helping
us
implement
and
think
about
these
metrics
as
they're
implemented
in
practice
all
right.
So
we
have
two
different
kind
of
kind
of
groups
working
on
this
right
now
one
is
the
girl,
more
live
group,
and
one
is
the
augur
group
then
kind
of
in
between
in
between
software
and
in
between
metrics.
A
We
have
working
groups
that
are
actually
honing
in
on
the
growth,
maturity
and
decline,
category
or
honing
in
on
the
diversity
and
inclusion
category,
so
they're
kind
of
the
bridge
serving
as
the
I
don't
know
the
impractical
or
in
the
metrics.
So
that's
that's
kind
of
just
not
kind
of
that
is
the
structure
of
the
chaos
project
right
and
so
Georg
posted
a
link
to
the
grimore
lab
right.
A
Then
the
questions
would
kind
of
go
back
to
you
and
you
don't
have
to
answer
them
now.
One
of
the
things
that
alfresco
would
want
to
see
I
mean
what
what
do
you
care
about
when
it
comes
to
understanding
the
projects
that
you're
about
ready
to
engage
in
or
what
do
you
fear
about
the
projects
that
you
want
to
support?
A
D
If
we
talk
about,
of
course,
user
prospect
or
stuff
like
that,
we
are
interested
more
on
the
on
the
technical
personas.
Let
me
say
so
how
many
of
them
are
using
the
software
in
which
way
how
many
of
them
are
contributing.
For
example,
raising
question
answering
questions
supporting
the
other
people
in
the
community,
how
many
they
are
contributing
to
the
source,
call
how
many
of
them,
but
I
mean
it's
not
only
how
many
of
them,
but
which
is
the
real
behavior
behind
these
so
and
yeah.
D
D
Why
they're
they're
staying
nesting
because
they
are
find
they're
finding
supportive
community
because
we
have
a
great
product
or
an
awful
product,
although
they
go
away
what
they
would
like
to
and
to
have
more
less
differently
and
stuff
like
that,
so
let
me
say
we
would
like
and
of
course
all
these
pictures
of
the
of
the
current
community
is
something
we
would
like
to
see
changing
in
time.
So
all
that
what
you
were
saying
are
we
growing?
Are
we
there
or
are
we
declining
terms
of
of
we
out
of
time
passing
and
yeah?
D
So
one
of
the
challenge
we
have
is
that
definitely
we
have
a
variety
of
technology
that
we
are
using,
because
we
have
docker
staff,
kubernetes
staff,
angular
staff,
back-end,
Java
staff,
geetam
projects,
dete
lab
projects
and
lots
of
lots
of
sources.
I
have
a
background
also
in
business
intelligence.
That
I
usually
call
these
all
these
sources
a
variety
of
different
stuff.
So
did
you.
B
D
Ticket
the
the
the
community
portal
we
have,
but
is
a
giant
portal,
its
collaboration
place
quite
known,
heat
up
of
course,
and
stuff
like
that.
So
I
mean,
let
me
say:
if
I
can
summarize
everything
I
would
like
to
say
that
as
I
as
I
saw
in
the
project,
the
LV
of
our
community
and,
of
course,
the
LT
of
the
communities
connected,
of
course
to
the
product
to
so
it's
not
it's,
not
the
LT
of
the
community,
because
is
the
ability
of
the
people
that
has
attained
about
it's
the
ability
of
the
company
to
so.
D
In
few
words,
this
is
what
what
I'm
working
on
and
I
would
lie.
Yeah
I
I
already
have
some
metrics
and
something
that
I
use
internally,
but
when
I
saw
your
project,
say
hey
guys,
but
they
are
working
on
something
you
know
shared
and
something
more
yeah
share.
It
I
think
it's
an
open
source
I
say
also
so
I
would
like
to
yeah
understand
more
about
that
and
again,
my
goal
is
to
clarify
better
the
earth
of
our
community,
because
we
are
talking
about
there's
a
thousand
of
people
around
our
services.
D
A
Is
great
so
it
sounds
like
at
alfresco.
You
have
your
own
projects
that
you
are
supporting
the
projects
that
are
that
are
core
to
your
organization,
but
then,
of
course,
you
are
pulling
projects
in
that
contribute
to
the
to
the
as
part
of
the
whole
project
ecosystem.
So
you
care
about
the
health
of
your
own
and
then
you
care
about
the
health
of
external
projects.
A
B
A
E
A
You
see
this
is
kind
of
what
has
come
of
things
over
time,
that
people
have
these
have
kind
of
bubbled
to
the
top
as
being
relevant
to
organizations.
Now
this
is
kind
of
a
first
step
in
just
identifying
what
those
metrics
are.
The
people
seem
to
care
about,
I
think,
probably
down
the
road.
We
have
to
start
asking
questions
of
as
we
see
these
change.
What
do
we
do?
A
D
This
is
for
very
committed
and
active
people
inside
our
community.
So
we
have
lots
of
people
that
most
shy
more
probably
beginners
or
newbies,
and
they
start
working
with
our
technology
without
really
contributing
back
to
the
to
the
to
the
project
and
and
yeah
I
mean
so
we
as
an
organization
would
like
to
understand
more
also
about
them,
because
it
is
part
of
our
community.
Take.
A
D
A
E
A
A
D
Think
I
think
that
I
mean,
of
course,
before
any
any
pull
request.
I
would
prefer
to
be
more.
Let
me
say:
I
mean
it's
a
no.
No,
it's
it's
a
matter
also
to
be
aligned
with
the
team,
and
the
group
I
mean
before
every
pull
across
I
would
like
to
be
or
expert
and
scale
on
the
content.
Because
again,
this
is
not
easy,
so
there
are
lots
of
by
a
variety
of
things
around
there.
D
So
I
was
so
one
of
the
question
I
had
in
mind
before
joining
the
meeting
is
to
understand
how
to
move
the
first
step,
so
I
mean
I
had
the
chance
also
to
went
through
project
main
on
the
technological
part,
less
on
the
on
the
on
the
kpi's
here,
and
thank
you
for
sharing,
because
I
will
study
that
content.
You
yes.
B
D
But
I
was
I
was
thinking
also
to
to
try
to
understand
how
to
start
using
the
things
that
you
already
have
and
because,
probably
if
I
start
you
use
these
in
my
environment,
I
can
better
see
the
gaps.
If
some
gets
gaps
there
are,
of
course,
and
and
try
to
understand
back
there.
Also
the
project.
Do
you
think
it's
a
good
approach?
Do
you
suggest
another
approach?
I
mean.
A
My
I
guess
probably
might
my
next
suggestion
would
be
after
checking
out
these
metrics
is
to
to
do
an
install
of
grimore
lab
and
do
an
install
of
augur
as
well.
There
are
two
different
tools
but
they're
kind
of
accomplishing
the
same
thing
with
respect
to
trying
to
help
us
deploy
these
metrics.
So
Derek.
You
want
to
talk
a
little
bit
about
fire,
so
Derek's,
one
of
the
lead
developers
on
auger
here,
yeah.
B
So
we've
we've
really
built
auger
like
in
line
with
the
metrics
Committee.
In
terms
of
like
we,
we
really
want
to
build
a
platform
that
enables
us
to
prototype
and
like
visualize,
new
metrics,
really
really
quickly,
and
so
auger
is
a
Python
on
the
back
end.
So
he
can.
He
use
pandas
and
everything
that
pandas
gives
us,
and
then
it's
JavaScript
at
UJS
on
the
front
end.
B
So
we
could
build
visualizations
with
d3
and
so
there's
a
lot
of
flexibility
in
what
we
can
do
right
now,
we're
using
the
github
API
NGH
torrent,
primarily
which
I've
both
focused
on
github
repositories,
but
I'm
currently
working
on
adding
support
to
things
like
it
and
some
other
data
collectors
for
like
mailing
lists
and
so
I.
Think
that
you
know
we're
like
augur,
is
really
gonna.
Be
able
to
shine
this
when
we
have
like
a
metric
that
you
know,
for
instance,
just
risk
that
might
be
more
difficult
to
do.
B
B
A
B
That
do
people
have
access
to
that.
So
we
have
a
version
that
I'm
you're
welcome
to
reach
out
to
us,
and
we
can
give
you
access
to
that,
like
for
people
who
are
doing
chaos
stuff,
that
we're
happy
to
share
access
to
our
database
and
then
it's
also
MGH
tornado
org.
They
have
instructions
on
how
to
download
it
and
install
it
as
well.
A
D
D
A
B
D
Because
one
of
my
niche,
a
question
where
exactly
about
the
collection
so
harvesting
those
data
from
where
the
data
are
so
now,
because
my
first
understanding
is
that,
probably
you
know
I
so
me
as
a
as
a
potential,
let
me
say,
user
of
this
kind
of
stuff
I
can
I
should
develop
something
by
myself
to
to
extract
the
data,
but
I
understand
from
what
you
say
that
this
is
not
the
case.
I
mean
there
are
some
connections
and
the
connection
are
there
yep.
A
And
I
think
at
least
my
my
long-term
goal
is
to
have
kind
of
a
single
large
scale
aggregator
that
people
can
connect
to
with
a
variety
of
different,
whether
it's
elastic
elastic
indices
with
Cabana
front
end
or
if
it's
just
connecting
the
standard
statements
and
then
putting
it
into
JavaScript.
I
would
hope
to
have
some
shared
large
data
aggregator
that
can
be
connect
and
I.
Think
Derrick,
you're,
even
talking
or
maybe
Keanu,
was
looking
at
this
too,
with
first
of
all,
as
an
aggregator
for
augur.
B
Yes,
so
we're
already
in
the
process,
because
we're
moving
from
looking
at
just
get
hub
repository
to
everything,
and
in
that
we
had
to
talk
a
lot
about
how
we're
going
to
persist
our
data
and
so
we're
just
guessing
the
use
of
different
graph
databases
and
everything
but
and
part
of
these
discussions.
We've
we've
been
working
with
Keanu
des
potentially
integrate
personal
into
augurs
data
collection.
B
So
we
might
build
a
database
that
women
see
things
from
what
is
already
out
there
and
auger
and
then
also
try
to
entry
things
from
like
libraries
I/o,
which
provides
dependency
data
and
also
try
to
include
things
from
github.
You
know,
so
we
don't
lose.
We
don't
go
back
at
all,
you
know
and
so
yeah.
B
We
would
really
like,
in
some
day
to
have
like
just
kind
of
this
unified
database
that
would
have
you
know,
information
from
everything
everywhere
about
open-source
projects,
but
the
big
challenge
there
is
trying
to
automate
that
process
and
like
Oh,
pointing
at
a
repository
automatically
finding
which
mailing
lists
to
use
like
that's
a
really
hard
challenge,
and
so
a
lot
of
the
discussions
we're
having
kind
of
internally
are
about,
like
which
of
those
challenges,
are
really
needed
to
be
solved.
And
where
are
we
looking
to
do?
That
sounds.
D
My
experience
with
you
I'd
be
great
yeah,
I,
think
I
will
and
because
also
in
my
organization,
I
had
the
chance
to
talk
about
your
project
to
some
a
couple
of
other
evangelists
they're
here
and
yeah.
So
let
me
see:
I
can
transform
these
first
meeting
something
visible
for
for
us
internally
and
and
share
the
experience
to
you.
I
think
it
could
be
positive.
A
A
A
A
A
C
A
A
What's
it
yes,
what's
well,
Shawn
got
the
rooms,
so
we're
all
set
at
University
of
British
Columbia
I
think
is
where
we're
at
UBC
yeah,
so
we're
all
set
we're
all
set
there.
So
I
don't
think,
there's
many
more
local
arrangements
that
need
to
be
made,
but
I
really
honestly,
don't
have
any
updates
with
respect
to
submissions
or
anything
like
that,
because
I
don't
see
those
things.
I
can.
A
C
C
A
Well,
I
mean
honestly,
part
of
me
is
like
if
we
get
no
submissions,
or
very
few
I
mean
that's
fine,
because
I've
been
part
of
the
whole
I.
Think
goal
is
to
have
some
working
sessions
at
Kaos,
con
yeah,
and
so,
if
I
mean,
if
we
have,
if
it's
free
to
attend,
which
is
what
we're
going
with
it's
the
day
before
opens
for
summit
North
America,
it's
like
28
28,
so.
C
A
C
A
C
E
A
C
A
Then
they
have
a
like
the
name
of
the
metric
and
a
question.
It's
the
questions
the
the
metric
is
intending
to
address.
So
that's
this.
That's
the
structure.
It's
called
gold
question
gold
question
metric,
so
that's
the
structure
that
you
see
in
there
has
Garak
is
anybody
wrists?
Are
those
two
outstanding
or
the
outstanding
pull
requests
to
get
risk
and
value
in
that
method
or
those
still
open,
I,
don't
work
lately,
yeah.