►
From YouTube: CHAOSS.Common.May.2.2019
Description
CHAOSS.Common.May.2.2019
B
B
Cool
we'll
run
through
previous
action
items,
I
also
published.
So
we
just
started
working
in
the
new
repository
where
I
published
a
readme,
but
I
think
we
need
to
just
run
through
it
and
see
if
we
have
the
right
things
and
update
the
list
of
contributors
and
maintain
errs
and
then
we'll
also
discuss
the
release
spreadsheet,
similar
to
what
Dee
and
I
did
but
different,
because
we
don't
have
a
lot
of
our
metrics
defined.
B
C
C
Then
we
had
decided
to
use
the
metrics
repository
and
you
weren't
on
the
call,
and
nobody
was
willing
to
answer
questions
and
I
was
not
sure
where
to
put
it,
because
if
I
put
it
in
the
metrics
repo,
then
it
would
have
been
like
obviously
I
felt
I
was
like
how
do
I
do
that
because
that'll
be
confusing,
but
now
I
think
we
decided
we're.
Gonna
have
our
own
weekly
working
group,
repo
for
just
stuff,
like
that
yep.
B
C
B
B
C
B
B
B
Not
complaining
I,
so
my
folks
have
been
in
town
and
they're
there
at
Edinboro
for
a
couple
of
days,
but
but
it's
just
great
all
kinds
of
chaos
like
I,
can't
get
anything
done.
I
thought
you
know,
sort
of
like
on
the
weekends
further
on
before
they're
out
of
bed.
I
could
get
a
few
things
I'm,
not
getting
anything
done
and
there's
three
weeks
they're
here,
but
yeah.
B
C
B
B
Okay,
so
the
next
one
Daniel
was
gonna
open,
an
issue
about
responsiveness,
metrics
I,
seen
those
no
update
on
that
one
Matt
who
is
mushroom
hunting
instead
of
on
the
call,
has
the
next
two
action
items
open
a
PR
to
include
metrics
from
the
geographic
metrics
discussion.
I
haven't
seen
a
PR,
no
I,
think
about
it.
I
think
I
forgot
to
track
this
repository,
I
think
I'm,
probably
not
even
getting
notification
about
it
and
he
was
gonna,
send
an
email
to
Calais
to
get
consensus
on
which
repositories
to
pin.
B
C
A
B
B
B
A
B
The
clones
I'm
not
gonna,
create
something
new.
If
I
can
just
steal
something
that
someone
else
has
already
done
exactly
so,
it
has
a
link
to
the
mailing
list.
The
weekly
calls
the
just
kind
of
a
general
background
which
I
think
it's
the
same
as
what
we
had
on
the
participate
page
and
then
the
only
other
section
we
really
have,
as
contributors.
B
B
C
A
A
A
C
Think
I
mean
I
think
it
would
be
helpful
because
I'm
kind
of
a
I
guess
I'd
consider
myself
an
overlap
with
the
evolution
group
and,
and
so
in
that
way,
the
things
that
overlap
with
evolution,
risk
value,
which
are
the
other
Carl's
I'm
in
a
lot
I.
Think
I.
Can
it
would
be
nice
to
have
that
visibility
to
the
pull
request?
So
the
responsibility
gives
me
visibility
that
might
help
keep
us
in
it
together
or
okay
may.
A
C
B
Generally
happy
to
have
more
maintain,
errs.
Okay,
so
I
will
add
you
as
a
maintainer
and
then
as
a
reminder
that
to
be
a
core
contributor,
you
basically
participate
kind
of,
at
least
at
least
one
once
a
month
in
some
way,
so
whether
it's
in
okay
dawn
to
correct
typos,
about
the
DNI
meetings,
which
I
copied
and
pasted
that
heart
from.
B
So
that's
the
criteria
for
becoming
a
core
contributor
is
basically
participation
in
some
way,
at
least
once
a
month
over
a
period
of
three
months.
So
the
way
I'm
reading
this
since
the
we
really
kind
of
just
started
this
working
group,
it
probably
hasn't
even
I,
don't
think
it's
been
around
quite
three
months.
B
D
D
D
E
B
E
B
A
B
Yeah
because
one
of
the
things
we
noted
in
particular
with
with
D&I,
but
it's
also
happening
in
this
working
group
as
well
as
we
do
a
lot
of
the
work
and
there
should
work
and
kind
of
documents
and
things,
and
so
you
know
the
fear
was
that
you
know
we
do
all
this
work
in
documents.
It
tends
to
be
like
me,
you're,
gay
or
gramma,
like
kind
of
a
couple
of
people
who
always
tend
to
pull
those
together
into
a
pull
request,
and
we
don't
want
all
the
credit
to
go
to.
B
Anything
else
is
there
anything
that
you
see,
that's
do
have
any
glaring
omissions
and
readme
I
kept
it
relatively
short.
We
still
need
to
add
like
the
focus
areas
and
things
mainly
because
we
have
it
I
think.
Once
we
get
the
template
created
and
then
we
can
get
the
we
need
to
create
a
focus
area
section.
A
So
one
activity
that
we
did
in
the
value
group
to
get
started
on
the
focus
areas
as
we
created
a
Google
Doc.
We
just
took
the
table
that
would
later
become
the
focus
areas
to
formulate
out
the
goals
that
we
have
for
each
of
those
focus
areas.
So
that's
one
step
we
can
take
to
formalize
the
focus
areas,
although
it
feel
like
we
already
have
the
focus
areas
pretty
much
so
just
a
matter
of
formalizing.
The
wording
yeah.
B
C
B
A
B
B
B
B
C
A
C
Like
I
think
so,
for
example,
I
think
we
could
release
a
metric
on
what
some
of
these
things
we've
defined
like
organ
like
the
interest
area
of
organizational
affiliations.
So
that
would
be
we
can
release
the
metric,
but
actually
producing
data
in
a
useful
way.
I
think
is
the
more
of
the
challenge,
and
that
I
mean
so.
B
We
see
similar
I
think
a
similar
issue
with
the
DNI
metrics
and
that
a
lot
of
them
aren't
they're,
not
things
that
are
built
into
tools,
they're
they're
things
that
you
know
are.
You
know,
measuring
the
diversity
of
speakers
at
a
conference,
for
example
right.
It's
not
not
something
you
put
in
a
tool
and
can
just
generate
so
the
actual
so
will
define
the
measurements,
and
some
of
them
will
likely
be
things
that
can
be
easily.
C
B
Less
so,
but
I
think
it'll
it'll
depend
and
some
of
them
like
geography,
people
have
lots
of
ideas
about
how
we
should
measure
geography,
the
the
catch.
Is
that
a
lot
of
open
source
projects?
You
don't
have
the
data
that
people
want,
so
it
would
be
nice
to
know.
Like
the
you
know,
the
basically
lat/long
kind
of
characteristics
for
someone
you're.
F
B
Where
there's
you
know
where
everybody's
on,
like
a
forum
or
slack
or
something
and
people
put
their
location
and
some
communities
might
have
that
they
might
have
that
data
and
be
able
to
use
it
so
I
think
I
think
we
need
to
be
careful
not
to
define
the
metrics
as
we
traditionally
think
that
they
can
be
the
data
go
third,
but
more
about
how
people
might
want
to
use
them.
Knowing
that
not
everyone
has
that.
A
A
C
Well,
I
think
so,
and
then
I
guess
going
back
to
the
ionized.
Similarities
like
it
is
actually
like.
Auger
has
a
way
for
you
to
map
10
emails
to
one
user
and
say
when
a
user
work
at
different
organizations
and
then
count
that
in
the
metrics.
But
everybody
is
responsible
for
populating
that
with
their
own
organization,
because
maintaining
a
central
central
directory
is
just
not
a
problem
that
is
solved,
but
hyper
ledger
is
trying
to
solve
it
and
software
which,
where
you'd
have
like
a
double
anonymous
ledger
or
whatever
they
call
it.
B
Important
point
or
not
yeah,
and
then
there
are
things
like
you
know,
like
the
the
Linux
Foundation
like
Corbett
and
Greg
cage,
do
a
pretty
good
job
of
manually
tracking
everyone
down
so
that
they
can
put
people
in
organizational
affiliation
categories
for
the
date
that
they
do
that
the
CNC
F
is
also
super
proactive
about
that
for,
for
at
least
for
kubernetes.
I
only
know
that
one,
that's
the
project,
I
work
on.
B
B
Back
to
what
Garrick
said,
I
think
we've
probably
gone
as
far
on
the
spreadsheet,
as
we
can
right
now
and
we
start
to
define
the
focus
areas
and
figure
out
what
what
metrics
we
have
and
what
our
goals
are.
And
then
we
can
populate
this
with
all
of
the
metrics
that
we
have
under
each
of
those
areas
and
then
give
each
of
them.
You
know
kind
of
yes,
no,
maybe.
B
A
B
D
B
C
Although
we
I
want
one
thing
that
Brian
prophet
mentioned
and
I,
don't
think
I'm
saying
anything
that
you
wouldn't
want
to
share
is
they're
gonna
start
to
look
at
the
time
of
day
of
commits
according
to
UTC
and
that
when
the
actual
work
is
taking
place
could
be
a
signal
of
where
someone
is
approximately
now.
It
could
also
be
a
signal
that
you're
me
and
got
an
idea
to
do
something
in
the
middle
of
the
night
and
did
it
so
I,
look
like
I'm
in
Europe,
but
I'm,
not
if
you
use
that
method.
B
B
A
A
G
B
A
B
B
G
B
D
D
Firefox
has
a
steady
growth
with
small
contributions
on
a
daily
basis,
while
the
WebKit,
which
is
at
the
heart
of
chromium
and
Safari,
has
big
ink
ups
or
suddenly
big
steps
in
the
world,
and
this
is
when
Apple
or
Google
suddenly
contribute
a
big
bunch
of
code.
So
you
really
see
a
difference
in
in
the
behavior
of
a
project
and
to
me
that
is
a
sign
whether
it's
a
community
written
or
corporate
driven
project.
A
B
B
A
Of
the
one
thing
I
shared
in
the
chat
is
a
paper
that
was
released
a
week
or
two
ago,
with
a
method
for
analyzing
stakeholders
influence
on
an
open
source,
ecosystems
requirements,
engineering
process,
that's
the
title:
I
I
just
came
across
it
because
I
talked
to
the
first
author
on
this
paper
and
I
was
like
that
sounds
like
something
this
workgroup
liked.
The
interest
of
it
cool.
B
B
B
A
G
C
A
A
B
Was
looking
back
at
everything
I
see
about
the
responsiveness
metrics?
Is
that
it's
not?
He
hasn't
created
that
doc
or
that
issue
yet
okay,
but
he
did
at
one
point.
There
is
sort
of
a
laundry
list
of
things
here
things
like
time
to
merge
time
waiting
for
a
reviewer
action.
He
says
he
see
that
these
are
specific
to
Garrett
time
waiting
for
a
submitter
action
time.
/
cycles
to
review
time
to
merge
time
for
approval
time
for
first
response,
so
I
think
what
we
have
kind
of
captures,
the
spirit
of
that
and.
B
A
B
A
Our
question
metric
approach.
Once
we
have
the
questions
we
want
to
answer,
you
would
create
detailed
pages
where
we
say
this
metric
can
answer
this
question,
and
this
is
what
to
consider
in
answering
this
question
more.
So
that's
the
activity.
We
did
last
time
where
we
wrote
down
a
whole
list
for
questions
now.
A
The
activity
that
I
can
suggest
for
the
next
10-15
minutes
for
us
is
to
go
through
this
list
of
questions
see.
If
there
is
anything
we
want
to
add
to
it,
there
also
may
be
some
duplicates
or
we
can
merge
them
together
and
then
the
final
ideal
outcome
would
be
a
table
where
we
have
a
name,
a
metric
me
and
the
question
next
to
it,
which
then
we
can
again
create
a
pull
request
and
move
over
into
the
repository
I'm
going
to
stop.
This
is
what
I'm
proposing
to
do.
A
Example,
so
if
we
wanted
to
advance
those
other
two
focus
areas,
I
think
a
similar
document
would
be
helpful
just
as
a
way
to
brainstorm
ideas
yeah.
What
I'm
proposing
right
now
is
to
take
the
order.
P
nation
metrics
focus
on
this
focus
area
and
formulate
out
what
are
the
metrics
and
questions
that
we
have
in
this
focus
area.
Okay,.
A
A
The
issue
with
that
approaches
me
sometimes,
then
wonder:
okay,
what
can
we
actually
say
about
our
projects
know
that
we
have
these
measurements.
The
other
way
is,
we
think
about
what
does
it
mean
to
know?
What
are
the
questions
we
have,
and
this
is
what
this
highlighted
questions
in
yellow
are
about,
and
then
we
figure
out
okay,
what
data
to
be
actually
need
to
answer
those
questions,
so
we
have
a
top-down
approach.
D
B
Yeah
that
seems
reasonable
to
me
because
especially
I
know
when
we
talked
last
last
time
about
the
stock.
The
impact
of
the
job
changes,
organizational
affiliation
changes,
something
I'm,
particularly
interested
in
so
I
added,
a
bunch
of
like
sub
questions
underneath
that,
and
so
that's
an
example
of
one
that
and
I
mean
these
two.
One
of
these
is
probably
a
subset
of
the
other
fiscal
motivations
and
buying
contributions.
B
A
B
B
G
A
B
B
Well,
Garak.
That
was
a
great
way
to
spend
the
last
10
or
15
minutes
of
the
meeting
I
feel
like
we
made
a
ton
of
progress
on
that
feels
feels
more
organized
if
nothing
else.
It
feels
because
that
massive
laundry
list
of
stuff
was
a
little
overwhelming
and
I
feel
like
we've
got
something
that
we
can
sort
of
take
and
put
into
focus
areas
now.
A
G
G
G
B
That's
different,
I
I
would
agree
with
the
way
the
words
are
listed
now
by
the
names,
but
I.
Don't
think
that
captures
the
spirit
of
what's
in
the
sub-questions,
because
the
so
the
spirit
of
this
sub
question
I,
remember
when
we
talked
about
how
do
organizational
partnerships
and
collaborations
impact
the
project,
and
so
that
was
things
like.
If
you
look
at
the
Linux
kernel,
a
bunch
of
the
big
hardware,
companies
have
people
on
loan
to
Lennar
o,
for
example.
B
So
Lennar
is
this
big
nonprofit
organization,
you
know
people,
and
so
people
are
sort
of
on
loan
to
Lonardo,
so
they
might
be
contributing
from
Allen
ro
email
address,
and
then
you
also
get
things
like
if
you
look
at
kubernetes,
so
VMware
and
pivotal
are
both
owned
by
Dell
and
a
lot
of
our
work
on
kubernetes
we
do
jointly
with
with
vmware,
and
so
how
does
that?
How
do
those
partnerships
impact
the
work,
that's
happening
in
the
open
source
projects,
which
I
feel
is
very
different,
actually
feel
has
nothing
to
do
with
I.
D
A
D
It's
it's
a
it's,
not
just
borrowing
an
email
address
as
a
as
an
ecosystem.
Just
you
were
mentioning
the
partners
for
how
they're
then
caldera
gives
an
email
addressed.
In
this
specific
case,
the
members
provide
of
Manara
provide
to
us
an
annual
fee
that
we
use
to
hire
engineers,
and
they
also
provide
engineers
that
are
part
of
our
team
and
they
work
very
very
closely
as
as
as
a
single
team.
So.
G
D
Yes,
it's
really
a
part
of
the
membership
agreements,
companies
joining
the
now
Rene
Pinnell
fee.
They
provide
engineers
and,
as
part
of
the
agreements,
there's
a
contribution
agreement
and
copyright
assignment,
because
these
engineers
are
as
if
the
company
paid
more
and
enero
higher
wage
years.
So.
H
F
F
G
F
G
B
But
it
does,
it
does
create
this
sort
of
dual
organizational
affiliation
that
you
know.
Ultimately,
as
the
person
doing
whatever
research
you're
doing,
you
need
to
decide.
Do
I
count
that
TI
person
on
loan
to
Lennar,
o
aslan
ro
affiliation,
or
do
I
count
them
as
Texas
Instruments
affiliation,
yes,
and
that
decision
depends
on
what
what
you're
trying
to
achieve
I
suppose
it.