►
From YouTube: CHAOSS.Common.August.8.2019
Description
CHAOSS.Common.August.8.2019
B
A
B
So
how
are
we
seeing
this
in
more
lab
or
augur
or
somewhere
else
and
I
said
it's
not
something
that
has
to
be
solved
right
now.
One
of
my
goals,
like
kind
of
more
broadly
overall,
is
to
bring
software
a
little
bit
more
to
the
forefront
this
year.
Now
that
we
have
the
version,
release
and
I
mean
I,
there's
been
a
lot
of
great
work
being
done
on
the
software,
but
really
starting
to
stitch
these
things
together.
A
B
So
that's
maybe
more
of
an
action
like
a
long-term
action
item
and
it
might
involve
in
trying
to
include
folks
from
augur
in
these
meetings
like
I,
can
reach
out
to
Sean
and
Georg
I.
Don't
know
if
you're
the
person
to
talk
to
with
respect
to
grimore
lab,
you
know
like
Danny,
should
Danny's
here
a
lot.
But
yes.
A
B
D
A
E
They've
been
developing
this
idea
to
have
a
weekly
community
meeting
the
hour
before
our
weekly
chaos
calls
so
we're
going
to
use
the
same
zoo,
channel
work
on
the
metrics,
how
they're
implemented
in
more.
Let's
talk
about
how
to
use
it
if
we
need
to
anyway,
that's
what
we
want
to
do
across
all
working
groups
and
just
have
one
dedicated
hour
every
week
to
connect
the
software
with
the
metrics.
A
B
A
B
A
Wondering
if
we
need
to
do
a
bit
of
not
really
reverse
engineering
but
really
having
a
close
look
at
some
of
the
metrics
that
are
being
manifested
in
the
tools
and
defining
them,
and
so
so
you
know
in
a
lot
of
cases,
we
can
probably
just
define
them
the
way
the
tool
uses
them.
Unless
we
have
some
kind
of
compelling
reason
to.
A
B
B
A
Organizational
affiliation
is
a
great
great
example,
but
the
problem
is
I,
think
tools
implement
it
differently
and
there's
a
lot
of
stuff
to
think
about,
so
that
one's
really
complicated
I
suspect
there
are
some
easier
ones
than
org
affiliation
that
have
already
been
implemented,
that
we
can
sort
of
dovetail
on
some
of
those
okay.
B
No
I
agree,
maybe
that's
trying
to
think
if
that
would
be
in
the
session
that
Gary
was
talking
about,
or
is
that
inviting
those
folks
here
again
like
what's
the
most
efficient
way
to
do
that?
I
agree
like
surveying
the
tools
would
be
handy
and
trying
to
mark
what's
being
done,
but
it's
not
what's
not
currently
captured
in
the
metrics
I.
Think
that's
what
you're
talking
about
yeah.
A
E
Yeah
I
mean
I'll,
go
high-pitch,
Eric
I.
Think
one
thing
we
need
to
do
for
this
is
to
identify
what
those
metrics
are.
That's
something
we
have.
The
working
group
need
to
do
and
then
we
can
go
to
the
tools
and
for
the
experts
who
develop
those
tools
to
figure
out
how
they
have
implemented
it
once
we
know.
B
E
B
A
Thinking
that
we
could
use
some
of
that
to
drive,
drive
some
decisions
around
which
metrics
we
define
for
the
next
release,
because
it
would
be
nice
to
be
a
little
more
deliberate
about
defining
some
of
the
metrics
that
we're
already
using
and
making
sure
that
we
have
common
definitions.
So
so,
if
we
look
at
how
grimmer
Labs
is
doing
something
and
how
augur
is
doing
something,
are
they?
Is
it
the
same
so
different?
How
do
we
define
it,
but
we
might
be
able
to
you
know,
and
we
could
do
the
same
thing
with
Sean.
E
B
A
Yeah
I
feel
like
in
some
cases,
I'm
worried
that
sometimes
we
sort
of
start
over
I
mean
I.
Think
we
needed
to
do
that
with
organizational
affiliation
cuz
that
one's
just
really
complex
mm-hmm,
but
I,
don't
want
to
do
that
for
all
of
them
I.
If
we
already
have
some
implementations
and
some
some
use
in
the
tooling,
you
might
as
well
start
with
those
definitions.
I
would.
B
Actually
think
that
that
was
probably
the
approach
I
don't
know
if
it
was
quite
this
explicit,
but
the
approach
to
say
it.
The
evolution
working
group
took
because
those
are
like
you're
talking
about
our
kind
of
a
straightforward
metrics.
There
are
things
about
pull
requests.
There
are
things
about
commits
there.
Things
about
reviews
and
I
know
that
grimore
labs
and
I
were
already
doing
these
things,
who
they
were
the
activity
metrics
that
were
pretty
approachable.
B
E
Just
from
an
organizational
affiliation,
implementation
in
Ramallah
on
the
horizon
is
a
new
feature
to
be
developed,
probably
soon,
because
Georgia
has
a
potential
customer
that
meets
it,
where
it's
a
large
organization
that
has
multiple
business
units,
so
more
fine-grained.
Analysis
for
employees
and
associations
with
business
units
and
being
able
to
aggregate
on
both
levels,
the
business
unit
level
and
then
the
group
level
and
the
business
level.
Oh.
B
So
I'm
going
to
share
something
that
I
shared
yesterday
in
the
weekly
call
gehrig.
You
saw
this
already.
No,
can
you
see
that
so
one
of
the
things
that
I'm
putting
together
is
just
this
like
a
table
of
the
based
on
the
version,
one
release
which
is
say
coming
out
of
the
Rizk
working
group?
They
have
metrics
one
and
two
and
then
trying
to
understand
where
these
are
deployed.
This
is
just
a
total
mock-up.
This
is
not
where
it
was.
There
called
metric
one.
So
there's
that
should
give
you
an
indicator.
B
B
A
E
I've
been
thinking
about
that
table
as
well
yeah
one
one
point
that
I
keep
coming
back
to
is
having
this
table
is
great
for
figuring
out.
Okay,
what
tools
support
it,
but
then
I
would
also
like
to
provide
the
next
step
on
where
to
actually
find
this
metric
and
how
do
I
get
this
metric
in
auger
and
collabs,
similar
to
what
we
have
in
the
metric
definitions,
where
we
have
step-by-step
on
how
to
find
this
metric,
and
maybe
we
can
link
to
those
known
implementation,
sections
or
maybe
need
new
documentation.
E
B
A
C
A
No
worries
the
only
other
thing
I
would
like
to
do
is
build
the
agenda
for
next
time.
So
I
wanted
to
talk
a
little
bit
about
that,
but
so
to
catch
you
up,
Sean.
We
just
talked
about
how
metrics
are
being
manifested
and
tooling
and
how
we
can
do
a
better
job
of
making
those
connections.
We
didn't
really
design
anything.
We
just
talked
about
a
lot
of
stuff,
which
is
in
the
notes
anything
else.
Anybody
wants
to
talk
about
in
this
meeting
other
agenda
items.
Oh.
D
A
B
We
should
it
for
my
agenda.
We
have
responsiveness
and
geography.
It
would
be
great
to
put
maybe
not
closure
to
those
but
like
80%
of
the
way
towards
closure.
Uh-Huh,
so
I'd
really
like
to
get
those
if
we
just
focus
on
one
or
two,
but
whether
it's
me
I
think
I'm
doing
this
part
this
metric
and
then
Danny's
doing
geography
so
put
pressure
on
either
me
or
Danny
to
really
talk
side.
E
A
So
maybe
we
focus
on
on
the
agenda
for
September
5th,
make
progress
on
geography
metrics?
Yes,.
B
E
A
B
B
A
I
was
wondering
Sean
if
you
wanted
to
bring
in
a
discussion
for
next
time
about
some
some
common
metrics
things
that
you
think
would
fit
within
common
metrics
that
are
probably
already
being
implemented
with
an
auger,
but
that
we
have
but
that
no
one's
taking
the
time
to
yeah
actually
define
because
what
we
talked
about.
You
probably
read
it.
There's.
C
C
Yeah
I
would
be
happy
to
do
that
and
I
think
that
whatever
my
brain
was
going
was
inaugurated,
I
docks,
which
I
shouldn't
even
make
a
bigger
deal
about
where
there
is
a
chaos
metric
to
find
each
to
it,
and
you
know
and
where
there's
not.
You
know
obviously
but
yeah
I'd
be
happy.
That
would
be
kind
of
a
fun
thing
for
me
to
perform
actually
cool.
Oh.
A
Anything
else
we
want
to
add
to
the
agenda
for
September
5th,
that's
probably
a
pretty
good
agenda.
To
be
honest,
those.
C
A
The
other
thing
that
we
sometimes
doing
this
meeting
that
maybe
we
should
just
do,
is
have
a
look
at
the
issues
and
any
I
don't
think
we
have
any
pull
requests
open.
Sorry,
let
me
just
find
the
chaos.
A
B
A
B
F
B
A
Yeah
I
do
I,
do
actually
like
I,
like
your
suggestion,
new
organizations
that
contribute
to
the
project
so
the
first
time
we
see
an
organization
versus
organizations
that
a
new
contributor
belongs
to
so
the
first
time
we
see
a
contributor.
What
organization
do
they
belong
to
and
I
think
it's
worth
making
that
distinction?
It's.
A
F
A
C
C
B
E
E
B
D
A
A
C
So
the
that
is
really
the
question
so,
for
example,
an
organization
implementing
water
can
maintain
a
list
as
long
as
it's
not
public
of
their
people
and
gather
it.
Yeah
I,
don't
think
that's
against
any
GPR
rules.
It's
the
public
availability
of
it.
There
is
a
question
and
I
think
that
was
just
that.
I
was
posing
the
question
because
it's
I
don't
know
if
we
need
to
have
a
stance
on
it.
A
C
I,
don't
I,
don't
know
that
we
can
I
would
like
to
think
that
we
should
I
think
we
should
have
some
kind
of
discussion
policy
under
the
policy
or
a
white
paper
or
a
statement
of
how
we
approach
that
question
or
how
we
recommend
organizations
approach
that
question
or
maybe
even
if
we
don't
make
a
recommendation
to
sort
of
have
someplace
that
we
can
refer
people
to
as
part
of
the
content,
maybe
even
on
the
cat's
website.
That
represents
how
we're
thinking
about
it.
C
B
Think
a
lot
of
metrics-
probably
not
just
this
one
alone,
but
carry
some
sort
of
caveat
like
this
mm-hmm
and
so
I
I,
had
thought
more
broadly
about
on
the
templates,
including
some
header
that
was
like
known
concerns
or
no
yeah.
I
didn't
want
to
do
it
in
this
first
version,
just
because
the
goal
was
to
get
all
the
visa,
even
in
the
first
place
in
the
line,
and
then
it
was
everything
is
now
well
yeah
and
I.
Don't
oh,
we
wanted
on
every
single
metric
order.
This
comes
up
pretty
often
on
all
metric.
B
C
C
A
Think
I
see
where
you're
going
with
this.
The
problem
is
that
organizational
affiliation
is
so
incredibly
complex
that
it
comes
that
a
whole
bunch
of
different
metrics
are
affected
by
this
one
caveat
one
one
caveat.
So
if
we
had
sort
of
a
paper
that
described
like
how
to
use
email
addresses,
how
do
you
determine
organizational
affiliation?
What
are
some
of
the
things
you
need
to
think
about,
because
it
is
super
super
tricky
and
super
complex
and
there
you
might
want
to
do
it
different
ways,
depending
on
what
you're
trying
to
get
out
of
it.
C
A
D
A
A
Explicitly
prohibits
you
from
using
the
information
that
you
gain
on
LinkedIn
for
basically
any
purpose
whatsoever.
I
think
that
that
that
clause
in
their
Terms
of
Service
would
never,
in
a
million
years
hold
up
in
court,
but
I'm
not
about
to
take
it
to
court.
So
I'm,
just
gonna
live
within
their
terms,
service.
B
A
Was
a
discussion
that
I
actually
had
with
Gregorio
Robles
in
Madrid,
because
I
was
talking
about
how
I
used
LinkedIn
for
all
of
this
and
he
was
like
and
we
sat
there
and
looked
at
the
Terms
of
Service
and
I
was
like?
Oh
that's.
A
A
Assuming
they
haven't
changed,
it
I
kept
looking
to
see
if
they
had
changed
it.
While
I
was
working
on
my
PhD
and
they
didn't
but
but
anyway
sorry,
that's
a
total
total
digression,
but
but
yeah.
My
point
is
that
that
this
there's
a
set
of
issues,
they're
gonna,
affect
a
whole
set
of
metrics
and
so
okay.
B
A
Yeah
I
do
think
I,
think
Shawn,
I,
think
you're
I
think
you're
right
that
maybe
we
just
need
like
some
sort
of
I,
don't
know
if
it's
like
a
position
paper
or
white
paper
things
to
think
about
paper
documents
somewhere
that
and
we
could
link
to
that.
As
the
caveat
for
you
know
this
set
of
metrics
that
deals
with
organizations
I.
F
A
F
A
The
metrics
that
we
have
open
are
all
things
that
we
need
to
kind
of
work
on
the
qualitative
measures
we
should
be
able
to.
We
can
just
close
that
one
after
somebody
does
the
pull
request
to
change
that
since
we've
already
defined
that
and
then
we
don't
have
any
open,
pull
requests
right
now.
So
that's
looking
good
cool
anything
else.
You
want
to
talk
about
before
we
before
we
call
it
a
meeting
I.