►
From YouTube: CHAOSS.Community.September.17.2019
Description
CHAOSS.Community.September.17.2019
A
A
A
We
got
zero
as
well.
Valerio
and
I
were
on
the
slack
channel
that
the
hackathon
provided
and
there
was,
in
general,
zero
questions
from
students
for
any
project.
So
we
are
not
the
only
one
that
didn't
miss
a
question
and
I
have
not
heard
from
any
of
the
projects
what
they
do
so
I
don't
actually
know
if
they
use
chaos
in
their
work
or
not.
Okay,.
C
B
B
D
A
C
A
B
A
A
A
B
A
A
A
B
B
F
A
B
E
A
Ni,
we
were
talking
on
behalf
of
meeting
tomorrow
with
Angela
to
talk
about
how
to
apply
the
DNI
metrics
for
events
to
the
Linux
Foundation
events.
Everyone
who
is
interested
in
joining
is
welcome
to
join
us.
The
we're
talking
at
the
same
time
as
this
meeting
this,
but
tomorrow
on
the
same
zoom
channel,
so
everyone
is
invited
to
join.
If
you
want
a
calendar,
invite
let
me
know
and
then
the
second
thing
we
are
helping
with
collaborating
on
the
Apache
survey
foundation.
B
I
reached
out
to
Kate-
and
she
said
a
lot
of
projects
have
an
interest
and
it's
kind
of
thing
and
the
hope
is
Matt.
Snell
had
shared
a
link
about
the
Linux
Foundation
running
surveys
in
the
past,
and
the
hope
would
be
that
something
similar
could
be
promoted
and
up
at
the
top
level.
Linux
Foundation
for
projects
with
an
interest.
B
A
D
Yep
I
can
do
that.
I
was
just
pulling
up
the
agenda,
so
we
as
a
reminder.
We
do
have
a
common
working
group
meeting
on
Thursday,
September
19th.
So
great.
If
you
look
at
at
end,
we
have
been
talking
a
little
bit
about
geography
metrics,
so
we've
been
kind
of
working
on
those
collaboratively,
Matt's
been
Matt's,
been
driving
that
the
other
thing
that
we've
been
talking
about
with
with
Sean
our
metrics
that
have
already
been
implemented
in
augur
that
are
common
metrics,
that
we
should
probably
write
down
the
definition
for
so
I.
C
C
F
F
So
basically
we
were
discussing
about
the
matrix
updates
and
all
the
metrics
that
probably
worst
support
reported
in
angry,
more
lab
so
basically
was
setting
up
a
document
and
they
start
discussing
all
the
metrics
around
there.
There
was
a
nice
discussion
about
if
we
want
to
go
deeply
metric
by
metric
all
the
column
matrix
implemented
by
the
tools
and
discuss
all
of
that
or
go
the
other
way
around
and
look
for
use
cases
and
then
put
that
into
valuable
matrix
for
for
the
people.
Yeah
I,
don't
know
if
enough.
C
C
For
the
risk
working
group,
the
biggest
discussions
we've
had
are
around
supper
bill
of
materials
and
I've
reached
out
to
a
couple
people.
We
want
feedback
from
there's
a
few
metrics
that
we
have
nearly
ready
for
release
that
we
will
release,
and
then
there
are
a
bunch
of
risk
metrics
that
Matt
Snell
has
actually
put
together
in
augur
that
we're
going
to
be
releasing
in
the
risk
working
group
as
well.
So
I
see
as
a
risk
working
group
being
quite
active
in
the
next
release.
I.
B
B
F
F
One
tool
that
one
of
our
people
in
the
company
has
a
site
as
a
side
project,
so
starting
to
do
the
same
infrastructure
we
were
using
to
analyze,
commits
and
contributions
of
other
lies
in
just
specific
things:
by
licensing
or
code
complexity,
I'll
start
more
ready
with
the
quality
of
the
code
of
integer,
okay
and
I.
Think
that
was
wrong.
Thank
you,
girl
for
posting
the
link
into
the
tag,
so
you
have
more
information
there.
So,
basically
it's
just
release.
I
didn't
finish
yet
even
on
part
of
the
bitter
genetics
offerings,
but
this
powerfully
into.
E
F
B
B
B
F
A
C
F
B
F
C
F
E
H
Yes,
let's
see,
first
of
all,
the
value
group
is
no
meeting
once
every
other
week,
not
every
week
we
met
last
Friday
and
we
have
a
wonderful
new
metric
that
is
going
to
be
part
of
the
next
release.
The
new
metric
relates
to
number
of
job
offers
and
salaries
associated
with
the
job
offers
for
open
source
projects,
so
we'll
be
working
on
that
in
the
coming
weeks.
H
C
D
C
D
You're,
theoretically,
you're,
not
even
supposed
to
look
someone
up
on
LinkedIn,
see
that
they
work
for
Google.
Use
that
in
your
data
point
because
you're,
especially
if
you're
a
logged
in
user
I,
don't
know
you
should
read
the
Terms
of
Service
I
had
to
read
it.
When
I
was
going
through
my
PhD,
because
I
was
now.
C
B
Okay,
I
think
in
in
the
case
of
all
the
metrics
right,
it's
to
provide
any
improvement
in
transparency.
So
any
of
these
metrics
aren't
gonna
solve
this
issue
to
the
fullest
degree
or
to
the
hundreds
to
the
nth
degree,
but
if
they
can
improve
transparency
and
actionability
in
any
way,
I
think
that's
a
very
positive
thing.
I.
A
H
H
Their
focus
is
his
focus,
is
somewhat
related,
but
slightly
different
to
to
chaos.
He's
focused
a
little
bit
more
high-level
than
chaos
is,
but,
but
we
have
been
talking
about
potentially
joining
forces
and
we've
been
strategizing
about
how
to
get
to
you
know
different
constituencies,
like
you
know,
possibly
like
a
CFO
or
or
CIO
or
or
you
know,
people
who
who
do
operate
at
a
very
high
level
that
he
might
have
relationships
with
in
Linux
Foundation.
So
it's
just
it's
just
discussions
right
now.
H
A
C
B
B
B
A
B
So
in
terms
of
the
metrics
released,
I
guess
I
wanted
to
get
feedback
from
people
here,
so
I
I
think
there's
kind
of
been
implicitly.
This
idea
that
we
would
release
near
FOSDEM,
right
chaos,
Scott
I
I
think
that's
always
been
kind
of
the
kind
of
the
cadence.
So
I
just
want
to
make
sure
we're
still
on
that
on
that
cadence
that
that's
what
we
want.
C
B
Are
we
are?
We
still
are
the
you
know
we
do
have
representation
from
the
working
groups
here.
Is
this
still
a
reasonable
thing?
Even
if
it's
just
a
single
metric
or
two
metrics
I
mean
it
doesn't
have
to
be
a
long
list?
I
just
I,
don't
want
to
put
four
I'd
love
to
do
a
release,
but
at
the
same
time
I
don't
want
to
kind
of
suggest
a
cycle
that
might
not
be
a
cycle.
That's
worth
keeping
I,
don't
know.
There's.
B
A
B
C
I,
don't
think
less
than
five,
but
that's
largely
because
we
have
a
set
of
things
that,
for
example,
the
badge
of
the
Linux
badging
metric
that
are
pretty
ready
to
go.
We
just
didn't
release
them
because
we
hadn't
talked
to
David
wheeler
and
then
the
stock
or
Bill
of
Materials
is
a
single
metric
right
now,
but
I
think
that
it
actually
needs
to
be
subdivided
into
a
set
of
metrics,
because
it's
so
like
we
could
keep
the
whole
ass
bomb.
C
I
think
there's
a
need
to
subdivide
some
of
the
things
that
are
in
the
giant
software
Bill
of
Materials
universe
and
the
multiple
metrics.
So
it's
it's
sort
of
like
cheating
to
up
our
metrics
score,
so
we're
kind
of
gaming
metrics
we're
building
on
tricks,
but
but
a
so
no
I'm,
not
I.
Don't
it's
not!
So
it's
not
that
we're
extraordinarily
productive
or
large.
It's
that
the
sense
of
what
a
software
build
materials
is
is
causing
us
to
generate
multiple,
separate
metrics,
I.
Think,
okay!
C
F
G
D
E
C
D
B
C
B
C
B
C
A
B
A
B
A
B
D
F
A
B
B
Nobody
would
know
so
then
that's
fine
and
then
on
the
the
evolution
of
metrics
right.
So,
as
Matt
had
pointed
out
and
as
Shawn
had
pointed
out,
that
some
of
the
metrics
require
a
little
bit
of
tweaking
because
the
they
just
need
to
be
refined
just
a
little
bit.
Do
we
is
that
easy
enough
to
handle
in
the
workflow
that
we
have
the.
C
B
C
Well,
so
it's
it's
yeah
it's
and
these
are
there's
like
no
fundamental
change
to
what
the
metric
measures,
but
there
are
two
different
ways
to
read
what
a
concert
I
believe
is:
there's
a
way
to
read
it
that
it's
commits
and
there's
a
key.
Remember
the
metric
and
there's
a
way
to
read
it
that
it's
lines
of
code
and
mine
is.
This
is
more
of
a
question
of
white
workflow.
C
So
if
your
workflow
I
think
it's
a
pull
request
against
the
metric
and
and
maybe
there's
something
we
oughta
do
to
tag,
a
metric
is
published
like
creative
release,
so
that
when
we're
working
on
it,
there's
an
awareness
that
we're
changing
it
public
metric,
so
that
the
discussion
about
not
fundamentally
changing
the
public
metric
is
it
takes
place.
In
other
words,
the
change
I
propose
is
one
of
making
it
more
clear
what
the
metric
is,
so
that
developers
don't
become
confused
if
I
had
proposed
a
change
of
metrics
or
commits
that
fundamentally
changed.
C
B
B
A
B
A
Idea
that
came
from
this
discussion
is
to
keep
a
version:
history,
insights
and
metric.
So
at
the
bottom
we
can
have
version
history,
initial
release
with
20
1908,
updated
in
2020
or
one
with
these
changes
and
then
the
description
of
the
changes
and
that
right
we
have
the
history
of
how
the
metric
evolved
and
if
anyone
looks
up
the
metric,
they
can
see.
Oh
okay,
there's
changes.
I
need
to
make
right.