►
From YouTube: CHAOSS.Common.February.21.2019
Description
CHAOSS.Common.February.21.2019
B
C
B
B
Okay,
so
the
orga
filiation,
so
I've
included
in
the
minutes,
there's
a
link
to
the
issue
that
Toby
put
together
and
a
link
to
the
the
document,
so
the
the
issue
frankly
just
links
off
to
the
document.
So
there's
not
really
much
interesting
in
that
bit.
Right
now
did
anybody?
Did
anybody
contribute
to
this?
This
document
that
wants
to
to
talk
about
it.
D
C
C
They
get
dams
to
work.
That
is,
there
already
has
a
notion
of
time
windows
associated
with
the
organizations
and
standardizing
on
some
of
that
type
of
how
we
track
organization
affiliation
and
time
bounded
I
think,
is
something
we
should
be
looking
at
being
able
to
capture
people.
Don't
just
look
at
metrics
at
a
point
in
time.
They
also
tend
to
look
at
trends
in
historical
mm-hm.
B
A
C
B
Would
say,
though,
Matt
instead
of
adding
it
to
the
list
right
now,
let's,
let's
work
in
this
in
the
stock
sure
just
to
keep
things
in
one
place
so
that
we're
not
working
on
them
and
in
both
places,
so
I
added
it
to
their
related.
Oh
yeah,
I'm
just
create
a
new
category.
I
created
a
new
category
at
the
bottom
called
missing.
Metrics
yeah.
A
E
C
E
A
E
B
C
B
D
C
C
C
F
We've
done
I
guess
in
Sochi.
C
C
Best
practices
and
copyright
statements
there's
some
evolving
thoughts
going
on
there,
and
certain
projects
will
basically
put
a
copyright
statement
on
each
file
saying
copyright
contributors
to
this
project.
You
know
project
X
and
then
inside
project
X.
There
is
a
file
called
contributors
and
everyone,
you
know
as
they
start
contributing
they
get
at
it
by
their
peers.
Something
like
that.
C
D
C
What
they
may
want
themselves
to
be
formally
affiliated
with
the
project
rather
than
the
companies
are
coming
in
from
because
we're
doing
this
as
community
work
or
something
like
that,
but
you
know
Kay
brace
them
back
through
their
gmail
and
they
have
another
account
somewhere
else.
We
know
they're
active.
We
might
affiliate
them
with
a
company
where
they
personally
want
to
be
affiliated
with.
As
you
know,
Daniel
says
like
FSF,
as
opposed
to
mature
Chia.
Okay,.
F
It
seems
like
it
seems
like
there
are
like
three
axes
of
control
for
this
information
when
one
might
be.
The
standard
that
we
want
to
stay
is
how
we
decide
where
people
are
doing.
The
work
for
the
other
might
be
the
developers,
preference
and
a
third
might
be
how
a
community
manager
wants
to
interpret
affiliation,
because
I
think
I,
understood
in
conversations
different
people
see
these
affiliation
things
very
differently
like
how
I
would
affiliation.
E
E
Asking
for
certain
services-
or
they
are
not
aligned
with
whatever.
Basically
they
don't
want
them
to
be
part
of
the
affiliation,
so
it's
kind
of,
let's
say
a
service,
maybe
from
from
the
people
paying
for
for
dashboard.
Just
perhaps
a
fourth
case
that
maybe
someone
the
the
one
producing
the
matrix
itself,
but
I
didn't
even
make
sense.
You.
E
So
not
exactly
said
that
the
specific
case
was,
if
you
are
not
paying
for
the
services
that
we
are
offering.
You
will
not
be
listed
as
organization
here,
so
you
know,
but
this
is.
This
is
basically
a
way
of
proceeding
by
the
one
producing
the
dashboard
right
or
controlling
the
dashboard.
So
I
mean
from
a
pure
metrics
perspective.
Maybe
it
doesn't
make
sense.
F
B
So
what
I've
done
is
I've
created
a
section
in
the
organizational
affiliation
metric
stock
called
missing,
metrics
and
I've
just
been
listing
listing
all
the
ones
that
we've
talked
about
so
I
think
what
we
have
to
do
first
is
probably
make
sure
that
we
have
all
of
the
or
as
many
of
the
metrics
we
can
possibly
think
of,
and
then
I
think
it'll
actually
be
kind
of
a
bigger
exercise
to
look
at
some.
Some
focus
areas
related
to
organizational
affiliation
and
put
these
into
logical
groupings.
B
B
C
Definitely
should
make
sure
we
stress
that
it's
an
organization
rather
than
a
company
yeah
and
because
I
think
organizations
play
our
the
role
here
that
wanna
capture
companies
are
just
a
subset.
Companies
have
multiple
sub
branches,
and
things
like
that
too.
So
I
don't
know
to
what
extent
you
want
to
know
wholly
owned
subsidiaries
and
secondary
subsidiaries,
and
that
type
of
thing
that's.
A
A
So
does
anybody
care-
and
this
is
that
whole
shepherding
yeah,
but
you
can
have
an
organization
kind
of
a
Peter
as
a
large
contributor
over
a
brief
period
of
time,
but
they're
not
really
a
committed
member
to
a
project
right,
so
you
could
have
a
lot
of
code
being
dumped
in
a
short
period
of
time,
so
the
number
of
commits
might
be
high,
but
they
really
might
just
be
a
peripheral
organization
that
made
a
a
temporary
entry
into
the
core
right.
So
do
we
care
it?
Does
anybody
care
about
this?
F
I've
written
a
lot
of
papers
using
that
analysis
and
I
think
I
think
it's
a
question
of
so
the
challenge
is
in
open
source
has
been
what
you're
gonna
count
as
core
carry
and
if
you
want
to
show
that
without
vetting
it
first,
because
the
core
is
usually
determined
by
communication
acts,
so
the
people
who
are
most
engaged
in
specific
acts
of
communication
often
end
up
defined
as
being
in
the
core
and
usually
that's
right.
Sometimes
you
get
it.
It's
not
quite
right,
there's,
obviously
thresholds
that
have
to
be
on
a
project-by-project
basis.
F
D
F
B
F
A
F
D
I
I
think
I've
got
it
in
my
head
now.
Does
that
apply
in
this
situation,
because
we
kind
of
call
those
I
mean
so
like
if
I
wrong
in
thinking
that
this
is
similar
to
what
we
would
call
a
drive-by
contribution.
D
A
D
A
D
D
Just
yeah
and
I
could
see
this
being
useful
because
first
I'm
sort
of
like
why?
Why,
because
like?
If
we're
talking
about
like
private
organizations
like
a
company,
the
dividing
line
is
pretty
easy.
Either
you
get
a
paycheck
or
you
don't
mm-hmm,
so
that
that
definitions
pretty
easy,
but
I
could
also
see
an
intra
organizational
analysis
are
most
of
the
people
contributing
to
this
project
from
a
certain
team
or
they're
people
from
the
outside
who
have
been
chipping
in
as
well.
So
you
know,
I
can
see
where
I
could
lay
both
ways.
Okay,
thank
you.
D
E
In
the
same
way
that
we
have
these,
so
you
remember
these
onion
analysis
of
different
source
communities
or
we
have
most
of
the
people.
No
small
amount
of
the
people
are
doing
most
work,
so
we
can
basically
characterize
organizations
in
the
same
way.
So
probably
small
amount
of
the
various
nations
are
doing
a
big
amount
of
the
work.
So
we
can
have
this
core
really
similar
to
this,
but
just
characterize
in
organizations
right
activity
in
the
several
data
sources-
and
this
is
another
thing,
so
we
are
talking.
Oh
well,
I've
only
seen
and
sorry.
E
This
is
my
first
meeting,
so
we
have
two
already
discussed
about
this,
but
we
are
talking
about
commits
around
the
document,
but
there
are,
of
course,
any
a
lot
of
data
sources
and
different
data
sources.
So
on
top
of
this,
I
have
a
couple
of
extra
here's,
a
pie,
I,
don't
know
if
they
apply
here
so.
E
It
is
okay,
but
you
say
so.
This
is
the
use
case.
Is
this
one?
Are
organizations
being
fair
in
the
code
review,
so
is
the
code
review
for,
of
course,
they've
several
organizations,
because
there
are
organizations
that
are
probably
leaving
this
and
they
are?
They
are
the
ones
that
have
maintained
errs
or
code
reviewers
and
the
code
reviewers
are
the
ones
that
are
adding
the
functionality
at
the
very
end.
So
what
do
you
think
is
something
that
we
can
have
here?
You.
A
B
Towards
the
top,
because
I
think
in
some
of
these
I
think
we
maybe
need
to
better
neat,
we
need
to
figure
out
how
we
want
to
distinguish
between
metrics
that
are
describing
organizational
affiliation
and
metrics
that
are
using
that
to
do
something
else.
You
know
what
I
mean,
because
I
think
Daniel
is
like
your
your
example
is
not
really
a
centrally
an
organizational
affiliation
metric
you're,
taking
the
organizational
affiliation
metrics
and
doing
some
analysis
on
them.
B
B
Yeah,
that's
good
point.
I
think
it
does
fit
into
kind
of
that
same
category.
So
I
summarized
this
as
which
metrics
are
directly
related
to
organizational
affiliation
versus
other
metrics
that
use
organizational
affiliation
for
additional
analysis.
Then
we
need
to
decide
where
we
put
these
and
how
we
characterize
them.
B
B
A
So
though,
as
you
well
know,
I,
just
the
focus
areas
it
would
sound
like
would
be
a
slightly
bit
different
here,
just
in
the
sense
that
obviously
BNI
is
the
highest
level
working
group
with
say
six
or
seven
focus
areas
in
there
and
then
obvious
are
the
goals
and
the
questions
in
there.
So
what
would
common
be
the
highest
level
here
and
then
a
focus
area
is
called
organizational
affiliate
or
organizational
things
whatever
the
proper
name.
B
A
B
A
D
A
A
B
A
B
A
D
All
of
these
concerns
for
determining
affiliations,
there's
work.
That
seems
to
be
worried
about
what,
if
affiliation
changes,
because
it
gets
merged,
quiet
or
people
move
jobs,
but
I'm
gonna
and
the
other
is
what,
if
people
have
more
than
one
affiliation
and
want
to
be
affiliated
with
a
specific
project,
work,
company
or
organization.
A
D
D
B
B
D
B
C
C
C
C
The
problem
or
the
interesting
issue,
I'm
seeing
and
I'm
seeing
a
lot
of
contributors
from
Australia
but
I,
know
they're
coming
in
from
China
they're
tumbling
in
and
being
able
to
track
them
more
than
just
the
server
their
prime
court
actually
track.
Where
they're
really
affiliated
with
is
the
interesting
case.
I've
been
seeing.
D
B
D
B
B
D
B
B
B
B
B
D
B
B
B
A
E
The
following
I
mean
I've,
seen
at
the
very
beginning
that
there
is
a
link
to
the,
but
she
maturity
model
yeah,
but
you
material
model
guidelines,
processing
the
maturity
of
a
brilliant
I'd
like
we,
we
tried
to
make
kind
of
list
of
existing
models
cuz.
There
are
several
of
them,
I,
don't
know
if
it
even
makes
sense
here
in
this
discussion,
because
at
least
I'm
aware
of
so
polar
seas,
maturity
model
which
is
part
of
the
Eclipse
Foundation.
E
E
D
E
F
The
Apache
maturity
model,
I
I,
think
it
should
should
czar
judgment
I
think
it's
something
that
naturally
would
fit
in
that
category.
I
think
if
it's
yeah
I
mean
I
think
naturally
would
fit
in
that
category.
I
think
you
could
also
make
the
argument
that
maturity
might
encompass
things
other
than
the
growth
maturity
in
decline,
metrics
and
so
I'd
have
to
actually
look
at
what
the
what
the
Apache
model
includes,
which
I
have
not
done.
Okay,.
F
D
F
I
can
just
I
just
pulled
it
up
and
there
are
parts
of
the
maturity
model
that
fit
in
literally
every
working
group
there's
a
license
and
copyright
model
that
would
probably
fit
in
risk.
There's
a
community
model
that
I
think
is
likely
to
fall
partly
in
diversity
and
inclusion,
at
least
consensus-building
models
kind
of
a
cultural
metric.
So
there
are
the
Apache
maturity.
Model
is
more
than
worth
maturity
and
decline,
but
it
does
include
growth,
maturity
and
decline.
F
B
B
I
also
tend
to
think
that
we
should
probably
discussions
about
things
like
like
maturity
models,
and
things
like
that
are
probably
a
little
bit
outside
of
the
scope
of
this
group
and
maybe
something
we
should
be
doing
kind
of
on
the
on
the
project
as
a
whole,
but
I
also
I'll
I'll,
be
honest,
like
with
my
practical
practitioner
hat
on
I'm,
not
sure
that
out
of
this
list
of
things
that
we
have
here,
that
figuring
out
which
models
things
fit
in
is
maybe
I
wouldn't
say
its
highest
priority.
No,
no.
F
F
E
F
E
A
E
A
E
Rated
to
community,
so
you
can
build
whatever
you
want
to
these
yeah.
It
was
more
I
wanted
to
open
these
works
with
the
with
the
goal
of
saying.
Well,
all
of
these
exist
if
there
is
a
stay
or
a
really
massive
state
of
the
art
in
quality
models
and
so
on
in
open-source
and
software
engineering.
The
point
is
first:
if
we
want
to
go
into
them,
I
think
the
answer
is,
we
prefer
not
to
enter
them
and
then
at
least
what
we
can
do
is
to
learn
from
them
several
metrics.
A
Maybe
the
next
thing
would
be
to
curate
this
list
and
kind
of
ask
out
loud
whether
things
like
maturity
models
are
actually
a
metric
right
and
then
kind
of
cleaning
up
the
repeats.
That's
on
my
to-do
list.
What
if
we
considered
maturity
models
at
them
in?
My
second
point,
is
what
if
we
considered
maturity
models
at
though
the
Tuesday
weekly
call,
not
necessarily
within
a
particular
at
this
point
that
makes
sense.
B
D
B
A
B
A
A
B
B
F
B
D
B
So
I
think
there
are
ones
that
are
probably
common
across
most
of
the
working
groups,
but
I
don't
see
any
links
to
anything.
So
I
don't
see
anybody.
It's
been
kind
of
kind
of
working
on
that,
then
I
think
the
first
step
would
be
to
you
know,
identify
which
of
these
metrics
is
like
bug,
age,
I,
don't
know.
If
that's
the
same
as
like
resolution
time,
I,
don't
know
how
we
would
how
he
would
decide
that,
but
that's
another
one
I
see
as
a
possible
thing
for
something
too.
F
E
B
E
E
B
B
E
A
A
B
B
But
I
think
the
the
first
step
is
to
at
least
to
even
figure
out
which
of
the
metrics
in
this
big
list
here
fall
into
that
kind
of
response
time,
because
there
are
like
oh
here's,
another
one,
percentile
distribution,
the
first
response
time.
So
there
are
a
bunch
of
them
in
here
that
relate
to
that
that
we
need
to
at
least
figure
out
what
the
scope
of
it
is
and
for
the
that
Daniels
already
has
some
definition
on.
We
can
start
with
that
and
then
fit
that
into
the
template
later.
D
B
Would
say
I
mean
if
there
are
any
metrics
in
this
list
that
haven't
been
haven't
been
defined,
that
somebody
wants
to
pick
up
or
if
they
want
to
collaborate
with
us
on
some
of
the
organizational
diversity
stuff
or
once
Daniel
gets
the
pull
request
and
or
not
the
pull
request
issue
and
the
the
dock.
People
can
start
collaborating
on
that
as
well.
I.
B
Mean
at
this
point
we're
just
sort
of
getting
organized,
so
it's
there
aren't
any
things
that
are
like
super
tangible,
like
someone
could
go
off
and
do
this
I
think
we'll
have
those
soon.
So
once
we
once
we
get
a
little
bit
organized
around
the
organizational
diversity,
I
think
we
can
start
sort
of
farming.
Those
out
like
we
have
with
the
DNI
working
group
and
sort
of
just
give
those
to
people
to
start
defining.
Once
we
have
the
template
and
everything.