►
From YouTube: CHAOSS.Community.Sept.8.2020
Description
CHAOSS.Community.Sept.8.2020
B
Yeah,
I
was
just
thinking
in
terms
of
I
completely
agree
with
having
a
little
bit
more
context
around
the
form
and,
if
there's
any
sort
of
like
details
on
what
might
be
more
or
less
manual
in
the
sense
of
if
this
is
gonna,
be
faster
or
slower
for,
depending
on
the
nature
of
the
project,
just
again
to
again
set
expectations.
If
it's,
if
someone,
I'm
assuming
like
kubernetes,
isn't
going
to
show
up
and
say,
give
me
a
report,
because
that
would
drain
everything.
B
A
A
Any
other
comments,
great
thanks.
Everybody,
let's
see
in
terms
of.
C
A
D
Tell
us
what
you're
going
to
be
doing
yes,
so
the
idea
is
to
to
do
a
brief
introduction
about
inner
source,
key
concepts
and
then
a
bit
about
inner
source,
commons,
the
foundation,
the
community
and
and
finally
a
bit
of
metrics
around
inner
source
and
why
people
are
interested
in
those.
So
this
is
and
then
probably
some
open
discussion.
So
I
don't
think
more
than
20
30
minutes
some
briefing
and.
D
That
by
the
way
on
the
15th
and
16th
of
september,
so
next
week
now
spam,
the
inner
source
common
summit
is
taking
place.
9
am
11,
no
yeah
9
am
noon
30
pacific
time.
So
you
are
more
than
welcome
to
join
just
in
case.
D
Is
it
free?
We
are
charging
like
35
dollars
for
a
t-shirt,
or
so,
if
there's
anyone
who
served
an
issues
attending
our
funding
and
so
on,
we
are
happy
to
give
free
tickets.
Okay,.
D
Oh
yeah,
you
put
away
there.
Okay,
let
me
share
that
now,
so
it's
here,
you
can
share
this
in
chat
so
yeah
we
have
some
great
people
joining.
We
will.
A
A
C
A
I
know
that
you
have
a
lot
of
involvement
in
inner
source
and
I
know
that
you've
been
talking
about
it
for
a
long
time
in
the
chaos
project.
I
don't
feel
that
we've
ever
really
kind
of
given
it
the
the
view
it
could
have
in
the
chaos
project.
A
Do
you
have
thoughts
on
how
we
can
bring
these
together?
I
I
know
you've
been
thinking
about
this
or
or
not
or
if,
if
the
work
just
stays
in
our
source
commons-
and
we
just
have
a
kind
of
a
common
understanding
of
each
other
or
if
there's
something
more
explicit
to
be
done
so.
D
The
metrics
themselves
at
the
very
bottom
of
all
of
these
are
quite
the
same,
and
technology,
maybe
might
be
the
same
as
well,
so
people
can
use
pogo
or
people
can
use
remote
lab
or
credit
because
they
are
using
github
enterprise,
gitlab
atlas
and
stacks.
They
are
using
pretty
similar
infrastructure,
so
it
happens
that
the
goals
are
different.
So
from
that
perspective,
I
think
is
is
really
interesting
for
the
inner
source
commons.
D
The
way
we
are
approaching,
metrics
like
following
the
whole
question
approach
having
all
of
these
focus
areas,
working
groups
and
so
on,
because
this
is
there
are
other
goals
such
for
instance,
fostering
collaboration,
breaking
down
silos,
doing
networking
improving
the
code
review
process
if
there's
any
within
corporations,
and
some
of
them
are
metrics
that
are
already
part
even
of
chaos.
Some
of
them
are
not,
so
I
see
this
way
of
moving
into
inner
source.
D
In
that
way,
the
other
way
around
is
about
inner
source,
may
bring
other
perspectives
about
the
use
of
metrics
and
how
those
can
be
used
typically
in
corporations,
so
not
in
the
open
source
form.
So
this
may
help
to
advance
in
the
understanding
and
study
of
metrics.
That's
that's
all
all
of
these.
I
remember
from
the
very
beginning
when
we
were
writing
down
the
the
bylaws
and
all
of
these
around
chaos.
D
I
we
were
discussing
about
having
the
inner
source
topic
within
within
there,
but
what
we
focus
at
the
end
on
open
source
and
that's
all
right.
So
this
is
this
is
more
or
less
the
storyline
here.
F
Yeah
I
mean
it's
a
bit:
it's
a
bit
outside
of
the
kind
of
mission
vision
as
as
it
was
defined
for
for
chaos,
but,
like
daniel
said,
I
mean,
there's,
there's
so
much
overlap,
and
so
many
metrics
in
common.
F
D
It
is,
but
once
just
as
an
example
when
people
are
starting
with
inner
source,
they
are
defining
certain
projects
and
they
may
start
with
10
or
1000,
and
they
are
interested
in
understanding
things
as
popularity
or
newcomers
to
the
project
or
the
evolution
if
they.
If
this
is
growing
somehow
and
the
velocity
of
the
development,
these
are
metrics
that
we
are
using
in
chaos
as
well.
D
So
there
is,
there
is
certain
overlapping,
definitely
so
yeah,
and
I
agree
with
you
don
that
this
is
a
bit
out
of
topic
for
for
chaos,
but
well
so
what
I'm
doing
personally
is
I'm
bringing
chaos
experience
into
the
inner
source
commands
in
the
sense
of
how
to
define
or
how
to
use
metrics
and
so
on,
and
the
tooling
that
we
have
in
chaos,
etc
and
yeah
from
time
to
time.
I'm
talking
about
dinner
stores
here
in
chaos.
F
Yeah,
because
I
think
some
of
the
some
of
the
problems
are
a
little
bit
different
right,
I
mean
when
we
talk
about
open
source
projects,
you're
talking
about
building
community,
but
you're
you're
talking
about
pulling
that
community
from
from
externally,
whereas
intersource
these
repositories
are
private
and
it's
just
from
a
company
and
how
much
you
can
pull
resources
from
other
groups
within
your
organization
tends
to
get
a
little
bit
political.
I
mean
the
so.
F
The
discussions
around,
I
think
interpretation
are
a
lot
different
but,
like
daniel
said,
I
think
a
lot
of
the
common
metrics,
the
atomic
metrics
are
probably
are
probably
the
same,
but
I
think
that
from
a
you
know,
like
an
internal
company
standpoint,
I
think
things
are
going
to
be
certain.
Things
are
going
to
be
more
important
or
or
less
important
than
they
would
be
in
an
open
source
project.
D
In
any
case,
probably
this
is
a
matter
of
of
interest,
and
so
far
this
is
only
me
and
somehow
so
if
there
are
two
or
three
people
in
the
next
months,
the
community
about
breaching
both
is
growing.
Somehow
that's,
okay!
I
just
keep
I
I
can
keep
informing
here
and
there.
So
that's
that's!
Okay,
for
me
sounds
good.
A
G
Are
you
I'm
I'm
good,
I'm
here
to
talk
about
dni
badging
today,
among
other
things,
we're
launching
on
september
14th,
which
is
next
monday,
and
we
we
put
up
kind
of
a
request
for
reviewers
and
we
had
a
lot
of
people
really
interested
in
the
project,
which
is
really
good,
and
some
of
those
people
were
even
out
outside
of
chaos,
which
is
stellar.
G
We've
been
having
some
reviewer
kind
of
orientation
sessions
to
get
people
acquainted
with
the
program
in
the
next.
There
could
be
one
tonight
if
anybody
signs
up
for
it,
we
haven't
had
anything
we
sign
up
yet,
but
we
have
one
friday
that
a
few
people
are
interested
in.
So
there's
a
sign
up
sheet.
G
I've
added
here
and
I'm
going
to,
and
I'm
I
have,
that
includes
everything
you
would
need
to
sign
up
to
be
a
reviewer,
and
then
you
got
you
go
to
one
of
the
orientation
sessions
and
then
you'd
be
or
if
you
were
a
launch
for
the
badging
program
yeah.
So
let
me
look
at
my
calendar
here.
The
next
session
is
5
p.m.
G
Today,
cvt
and
the
next
one
is
12
so
an
hour
after
this
meeting,
but
on
friday.
So
if
you're
interested
in
attending
any
of
those
becoming
a
review
or
anything
like
that,
let
me
know
through
that
form
and
I
think
that's
that's
it
for
badging
right
now.
We're
just
so
excited
we're
not
making
any
more
changes
to
the
documentation
or
anything
like
that.
Until
we
we
work
on
the
dev
branch
after
launch.
We
have
a
lot
of
things
to
work
with.
I
think,
but
that's
it
for
that.
G
How
did
the
session
go
yesterday?
Really?
Well,
we
actually
it.
It
went
under
30
minutes,
but
we
got
everything.
I
think
I
got
everything
across
that
I
needed
to
and
we
had
good
discussion.
We
had
questions.
We
talked
about
the
two
cats
I
had
in
the
background
all
that
stuff
and
we
had
a
nice
conversation.
G
A
G
A
No,
no
for
just
like
what
people
would
see
when
they
want
to
actually
try
to
get
a
badge
for
an
event.
H
Shared
that
in
the
chat
and
I
dropped
it
in
the
google
docs
as
well
so.
A
So
this
is
what
matt
and
asta
have
been
putting
together.
So
the
idea
is
to
to
help
with
dni
at
events
and,
as
this
starts
rolling
out,
we'll
look
at
projects
as
well.
G
I
can
talk
about
this
a
little
bit
so
yeah
and
generally
the
people
that
submit
the
events
for
to
be
badged
is
they've,
got
to
be
an
organizer
or
some
person.
That's
in
the
organization
of
the
event
and
most
of
the
most
of
the
information
for
reviewing
comes
out
of
what
the
people
say
or
what
you
can
find.
All
of
it
comes
out
of
what
they
say
or
what
you
can
find
on
the
website,
but
most
of
it
comes
out
of
what
they
talk
about.
G
A
And
so,
at
this
point,
yeah,
these
criteria
that
are
on
here
are
what
the
reviewers
use
to
ensure
that
the
submitter
is
attending
to
these
things.
So
the
review
process
is
really
about
ensuring
that
the
applicant,
what
the
applicant
says
is
true
and
it's
discoverable
at
the
event,
so
I
can
scroll
down
a
little
bit
further.
G
H
Would
it
be,
would
it
be
helpful
to
link
to
the
chaos
metrics
that
are
are
being
used
in
this
form?
For
example,
diversity,
access
tickets
is
a
that
is
a
chaos
metric.
H
H
Nice,
I
think
the
code
of
conduct
for
event
is,
is
a
chaos
metric
yeah.
G
B
Yeah,
I
was
just
reading
the
documentation
around
demographics
because
that
was
gonna.
Be
my
question
too.
So
I
I
like
the
suggestion
to
link
that
in
so
they
have
a
reference
for
it.
B
I
know
I'm
a
little
bit
late
to
this
and
I
have
done
some
demographic
surveys
at
events
and
we've
been
subject
to
different
layers
of
pii
issues
in
terms
of
what
we
are
allowed
to
ask
people,
and
I'm
wondering
if
there's
any
guidance,
around
sort
of
minimum
demographic
criteria
that
you
suggest
to
go
into
this
evaluation
versus
ones
that
are
maybe
more
or
less
sensitive,
that
you're
either
encouraging
or
having
stipulations
around
acknowledging
that
this
is
slightly
more
sensitive.
B
Now
that,
like
for
an
individual,
that,
I
think
it's
slightly
different
for
data
collection.
For
me
representing
a
large
company.
There
are
very
serious
implications
for
collecting
data
like
that.
So
I'm
wondering
if
you
have
any
sort
of
guidance
around
various
levels
of
pii.
E
So
if
you
can't
ask-
because
I
don't
have
any
experience
doing
this,
is
there
specific?
Is
there
specific
pii
that
has
been
troublesome
in
the
past
from
a
perspective.
B
Yeah,
so
for
for
the
perspective
of
google,
if
I
collect
sort
of
more
sensitive
kinds
of
pii,
I'd
see
like
contact
information,
actual
locations
outside
of
just
region,
so
even
individual
company,
so
just
kind
of
the
next
layer
versus
like
general
region,
general
industry,
general
rule.
Then.
I
B
To
start,
I
have
to
create
a
process
around
how
I
will
treat
the
data
to
make
sure
that
I'm
gdpr
compliant
privacy
compliant
with
the
event
and
with
the
company.
So
that's
company-specific
policies,
but
there
are
certain
sort
of
general
gradations
of
pii
levels
that
get
you
into
more
or
less
trouble.
So
things
like
gender,
ethnicity
and
more
like
self-identifying
characteristics,
tend
to
be
more
sensitive
than
I
live
in
europe.
F
We've
talked
about
needing
some
kind
of
ethics
guidelines
for
people
around
how
to
treat
some
of
this
information,
because
you
don't
you
don't
necessarily
think
about
it
as
being
sensitive
in
the
aggregate,
but
in
a
lot
of
populations
you
might
not
have
that
many
people
of
a
certain
type
of
gender
or
certain
identity
and
and
it
becomes
identifiable
information
really
quickly,
and
you
can
figure
out
exactly
who
that
person
was,
if
you're,
not
careful
with
the
data.
F
G
Yeah,
coming
from
a
like
cyber
security
aspect
of
it
really
there's
a
lot
of
information
that
you
think
would
be
pretty
inane
and
can
trace
back
to
one
person
in
a
large
population,
even
just
from
small
details
that
you
might
not
think
would
identify
someone.
But
I,
I
think
that's
really
good
to
have
an
ethics
document
and
also
add
these
ethics
to
the
metrics
themselves.
That
might
be
something
to
get
started
here
pretty
soon,
as
we're
measuring
these
from
our
big
thing
for
badging.
G
Is
that
we're
making
sure
that
these
people
are
measuring
these
metrics
themselves
and
that
one
of
the
things
that
is
kind
of
a
a
plus
one
for
the
or
extra
plus
is
that
they,
if
they're,
displaying
anonymized
demographics
on
their
site
about
something
like
this
is
kind
of
the
people
that
came
to
our
event
and
if
it's
bad,
it
shows
bad.
If
it's
good,
it
shows
good,
but
I
think
an
ethnic.
E
Sacrament
is
yeah
a
really
good
idea,
yeah
and
maybe
even
some
quantitative
guidelines
like
if
you're
in
a
group,
that's
less
than
15
or
10
of
the
participants
that
you're
just
going
to
be
lumped
in
your
answers
will
not
be
like
recorded
as
a
percentage
with,
so
that
it
really
effectively
identifies
you
depending
on
the
size
of
the
event
yeah.
I
mean,
I
think,
that's
that
would
really
limit
the
candor
of
the
answers
that
you
would
get.
E
If
I
would
be
concerned
about
that,
and
of
course
I
wouldn't
because
a
lot
of
people
look
like
me,
but
at
these
events,
but
others
certainly
would
be.
A
So
I
have
a
thought
on
this.
I
think
this.
This
is
a
kind
of
a
big
question.
It's
because,
if,
if
we're
going
to
be
using
chaos
to
provide
a
badge
with
demographics,
whether
it's
speaker
or
attendee
demographics,
if
an
event
is,
is
capturing
those
demographics
and
they're
doing
a
really
bad
job
at
it,
but
they
are
in
fact
capturing
it
and
displaying
it.
A
H
A
An
event
you're
attending
to
the
ethics
associated
with
the
capturing
of
this
data,
like
we
it's
hard
for
us
to
define
event
by
event.
What
is
what
those
ethical.
E
Probably,
like
somebody
suggested
us
some
ethics
guidelines,
we
don't
have
to
fully
develop
it,
but
I
think
we've
identified
a
couple
of
issues
here
and,
for
example,
I
think
speaker.
Demographics
is
already
public
information
in
most
cases,
so
I
don't
think
that's
a
pii
issue.
E
It's
participant
demographics,
where
really
the
value
of
not
identifying
individuals
by
accident
needs
to
be
in
there.
I
hear
pretty
clearly
the
the
ethic
or
the
value
of
not
identifying
individuals
by
asking
them
for
too
specific
of
a
location
is
important.
E
G
The
way
I
think
about
it,
a
lot
of
the
things
we're
measuring
are
things
that
are
public
facing
as
well.
Things
that
you
can
see
when
you
go
to
the
website
are
the
kind
of
things
we're
looking
for.
So
maybe
we
I
was
thinking
we
could
add
a
check
that
is
worth
the
points
it's
worth.
G
If,
before
we
get
anything
kind
of
ethics
document
started,
I
can
add
a
kind
of
an
emergency
check
at
the
bottom
of
each
demographic
section
saying
there
is
some
kind,
something
about
respect
to
pii
and
and
the
ethical
use
of
the
demographics
I'm
thinking.
Eventually,
we
can
probably
have
some
kind
of
system,
whereas
the
ethics
aren't
being
followed,
then
they
don't
get
any
of
those
check
boxes,
but
for
now
for
the
launch,
I
think
we'd
have
to
go
with
an
extra
line
item
for
now,
but.
B
I
feel
like
something
as
simple
as
suggesting
a
data
use
blurb
like
it's
like
something
similar
to
what
lab
has
like,
there's,
always
some
sort
of
privacy.
This
is
how
your
data
is
going
to
be
used
in
the
system,
even
if
it's
really
lightweight
just
just
have
relative
intentions
and
usage,
and
maybe
a
couple
caveats
with.
If
our
sample
is
less
than
10,
we
won't
show
it.
B
But
just
I
know
I
think
that's
a
simple
suggestion
that
we
can
make
while
kind
of
have
to
say
that
there's
any
liability
here,
but
at
least
it
encourages
better
practices
up
front.
If
they're
going
to
be
collecting
any
sort
of
pii,
then
they
should
be
encouraged
to
have
some
sort
of
usage
documentation.
F
I
wonder
if
there's
already
I
mean
this,
this
obviously
is
a
problem
that
lots
of
lots
of
groups
face
anybody
that
collects
data.
Is
there
a
non-profit
out
there
somewhere?
That's
already
put
together
sort
of
a
best
practices
guide
that
we
could
just
link
to
from
a
temporary
standpoint
like
I
feel
like.
Maybe
we're
reinventing
the
wheel
here,
the
more
I
think
about
it.
F
We
have
it's,
not
that's.
That's,
I
think
that's
two
separate
things.
The
privacy
policy
is
how
we
treat
your
data,
but
that's
not
what
we're
talking
about
in
the
badging
program,
we're
talking
about
other
people,
gathering
data
and
us
wanting
to
encourage
them
to
do
it
in
an
ethical
way
using
best
practices.
Yeah.
Do
you
see
what
I
mean?
I
think.
B
F
H
Know
I
mean
when
we
start
thinking
about
you
know,
like
code
of
conduct
is
like
having
a
code
of
conduct
is
a
is
a
metric,
so
is,
is
following
ethical
data
capture.
Does
that
become
a
metric
as
well,
and
if
so,
can
we
can?
We
solve
part
of
our
problem
here
by
maybe
defining
that
metric
within
dni.
F
F
F
A
Okay,
so
can
I
ask
one
question
it's,
it
would
kind
of
be
a
procedural
question
in
the
badging.
A
Do
you
think
from
when
an
organization
is
requesting
a
badge
that
the
review
could
simply
point
them
to
a
site
that
we
don't
have
yet
about
the
ethical
considerations
of
data
and
say
you
know,
we
understand
that
you're
capturing
these
demographics.
We
encourage
you
strongly
to
take
a
look
at
this
site
that
we
don't
have
yet
or
document
that
we
don't
have
yet
or
do
we
ask
for
their
statement
of
ethical
use,
see
what
I'm
saying
one
is
asking
them
for
information
that
they've
considered
ethical
use
of
data.
G
That
make
sense
we
could
do
both.
I
mean
we
do
ask.
We
do
kind
of
have
this
conflict
of
interest
policy
with
your
viewers.
So
it's
it's
it's
something
similar
to
that.
I
think
where
they
they
could
talk
about
like
they
can.
They
will
they'll
have
to
check
a
box
that
talks
about
their
their
ethical
use,
but
they
also
have
something
that
they
talk
about.
Like
you
said,
that
sounds
like
a
good
idea.
F
I
also
think
so
I
I
obviously
have
very
strong
opinions
about
this,
but
I
also
don't
think
that
this
should
be
any
kind
of
a
gate
to
getting
getting
this
out
the
door
and
the
way
that
it
is
now
I'm
talking
about
this
more
from
a
future
improvement
standpoint.
So
I
don't
want
anybody
to
think
that
I'm
saying
we
can't
possibly
do
this
until
we
sort
out
this
big
thing
that
nobody
quite
knows
what
to
do
with.
F
I,
I
guess
I'm
just
suggesting
that
as
an
area
that
we
can,
we
can
improve,
because
I
think
we
need
the
ethical
statement.
For
other
reasons
too,
not
just
the
badging.
C
A
So
could
I
make
the
following
proposition
then,
in
an
effort
to
continue
the
badging
program,
we
do
a
search
to
try
to
find
an
ethical
use
of
data
statement,
that's
published
and
we
agree
on
and
as
part
of
the
review
process,
the
reviewer
can
simply
say
hey.
Thank
you
for
doing
this.
Demographic
work,
here's
a
link
to
a
statement.
A
If
we
have
a
metric,
as
kevin
had
pointed
out
about
the
ethical
use
of
data,
we
could
start
kind
of
expanding
that
a
little
bit
more
where
we
actually
ask
people
just
to
describe
their
ethical
use
of
the
data
that
they're
collecting
not
just
recommending
they
think
about
it,
but
actually
telling
them
to
describe
it.
Would
that
fit
with
people.
A
F
A
F
A
F
A
I
was
absolutely
blown
away
yeah,
and
so
I
was
super
happy
if
you
haven't
had
a
chance
to
to
watch
it.
It's
not
long
at
all,
and
it's
just
about
the
latest
metrics
release.
It
was
awesome,
totally
awesome.
A
We
had
talked
about
developing
or
she
had
talked
about
developing
some
other
videos,
perhaps
for
the
working
groups,
not
necessarily
the
metrics
for
the
working
group,
but
you
know
videos
describing
what's
going
on
in
the
working
groups
also
for
the
software
and
also
for
the
chaos
project
as
a
whole,
not
just
about
the
release.
I
don't
know
if
any
of
the
I
don't
know
if
people
have
thoughts
on
any
other
videos
that
might
improve
transparency
for
the
project
or
provide
insight
for
folks.
E
F
F
F
A
Cool.
Thank
you.
Oh
geez,
we're!
Okay!
So
joshua.
Do
you
wanna
give
us
an
update
on
how
the
handbook's
going
I'm
gonna.
K
Yeah
sure
so
I
basically
worked
on
the
terminology
section
inside
the
handbook,
sec
community
handbook.
So
I
worked
on
the
specific
terms.
The
general
committee
terms,
the
working
group
stamps
and
also
the
mentorship.
So
so
it
went
pretty
well,
so
I
would
be
working
on
the
terminology
usage
and
the
finally
jumping
onto
the
contribution
guidelines.
So
for
this
specific
week,
so
I
would
be
working
on.
K
I
mean
like
more
on
the
like
how
one
can
get
involved
as
a
designer
or
a
marketer
or
a
documentator
so
like
I
would
be
separating
out
all
these
things
and
good
writing
in
the
comedy
handbook,
and
other
thing
I
proposed
within
the
community
handbook
was
the
chaos
history
so
since,
like
community
handbook
is,
is
is
open
to
the
new
commerce
as
well
as
the
existing
community
members.
K
So
I
think
like
it
would
be
interesting
fact
for
everyone
who
goes
and
reads
about
the
comedy
handbook,
and
everyone
knows
about
the
history
behind
the
chaos
project.
So
I
proposed
this
idea
specifically
when
we
had
a
previous
mentors
call.
So
I
think,
like
your
met,
might
be
taking
this
overhead,
so
if
they
have
any
idea
on
this.
J
J
Here's
the
first
chaos
con.
Here's
the
first
working
group
created
a
nice
timeline,
is
a
good
idea,
so
I.
F
Personally,
I
would
I
would
find
that
particularly
useful,
because
a
lot
of
times
people
will
that
comes
up
a
lot
that
question.
So
how
did
the
chaos
project
start
and
it's
really
nice
to
be
able
if
I
had
like
one
place
where
I
could
just
grab
those
couple
of
key
dates
from?
I
think
that
would
be
really
useful.
K
I
personally
suggested
maybe
a
short
interview
with
the
core
con
for
community
members,
like
maybe
15
or
20,
minutes
interview
talking
about
how
they
got
engaged
and
how
the
chaos
project
started
and
what
was
their
contribution
like
this
way,
we
can
plan
out
things.
J
F
We
also
did
that
podcast
that
where
we
talked
a
lot
about
the
kind
of
didn't
didn't
we
talk
about
kind
of
the
history
of
chaos
on
one
of
the
one
of
the
podcasts
too.
That
might
be.
A
Too,
okay,
so
the
the
last
thing
anything
else
on
that
the
last
thing
on
the
list
was
about
chaos
attribution
and
how
much
we
want
to
talk
about
this
or
pursue
this
so
daniel.
You
had
that
link
as
well
with
community
bridge.
Was
that
right?
Could
you
share
that
real
quickly,
yeah.
A
A
D
D
Yeah
in
that
link,
you
have
a
massive
amount
of
projects
from
the
linux
foundation
or
that
are
part
of
the
linux
foundation.
So
you
can
scroll
down.
If
you
click
in
any
of
them,
go
for
maybe
10.,
maybe
they
don't
have
yeah.
Can
you
go
back
and
choose
another
one?
Maybe
you
couldn't
find
them
on
there?
Oh,
those
are
better,
probably
the
better
ones.
A
A
D
Okay
and
go
for
whatever,
so
what
they're
presenting
is
kind
of
a
dashboard
and
with
a
bunch
of
metrics
and
so
on,
which
are
well
kind
of
related
to
the
metrics
that
we
have.
But
then,
if
you
go
to
the
left
side,
you
you
see
that
there
is
a
menu
there,
where
you
see,
source
control,
pull
request,
etc.
D
What
we
see
here
is
a
dashboard
which
is
based
in
chaos.
Let
me
take
a
bit
of
charge
if
you
have
a
look
at
this.
D
I'm
sorry
now
with
you.
Basically,
this
is
remarkable
sigils
you
can
see
on
the
right
the
dashboard,
and
it's
exactly
the
same.
So
it
seems
that
the
linux
foundation
is
using
ks
technology
to
analyze
a
massive
amount
of
projects,
which
is
great,
so
they
are
reusing
our
technology,
but
I
think
it's
worth
asking
them
to
to
have
certain
attributes
here
on
somewhere
for
the
for
the
chaos
project.
D
D
Create
and
someone
else
wrote
something
maybe
in
congruent
was
this
one
yeah
cover
dot
io,
so
it's
about
asking
for
the
proper
attribution
and
as
we
are
under
the
limit
foundations
right,
I
guess
we
both
can
take
advantage
of
this.
Like
the
next
foundation
is
using
ks
technology
chaos.
Technology
is
being
used
by
the
foundation.
E
I
think
I
think
there
are
component,
and
I
think
there
are
organizations
that
are
using
chaos
metrics
within
the
project.
I
think
I
think
our
concern
would
be
people
outside
the
project
who
I
mean.
We
know
that
grimoire
lab
and
auger
reference
chaos.
We
know
that
a
lot
of
the
companies
that
are
participating
reference
that
they
use
chaos
metrics,
I
think
any
public
use
of
the
ks
organization
or
logo-
should
be
something
that
has
to
be
approved
through
some
process
beyond
the
scope
of
where
it's
currently
used.
F
F
Think
that's
totally
fair.
I
mean
I
think
I
would.
I
would
go
back
to
them
with
a
proposal
that
just
says
hey
at
the
bottom
of
each
page.
Can
you
put
something
like
you
know,
project
name
from
the
chaos?
I
don't
know
project
name
from
the
chaos
project
used
to
develop
this
metric
or
something
with
a
link
to.
D
F
F
D
D
A
A
Okay,
cool
I'll
draft-
something
maybe
for
next
week
and
think
about
how
just.
C
A
Yeah,
it
gets
to
be
a
can
we
table
this,
it's
I
we
can
pick
this
discussion
up
next
week,
we're
at
52
so
we're
a
little
bit
over
unless
somebody
hasn't
we'll.