►
From YouTube: CHAOSS.Community.November.5.2019
Description
CHAOSS.Community.November.5.2019
A
A
It's
the
first
thing
that
I'll
just
there
was
these
are
in
no
particular
order.
So
the
first
thing
is
the
the
chaos
community
reports,
and
so
the
chaos
community
reports
again
are
reports
that
we're
gonna
do
with
two
different
projects:
Zephyr
and
Jenkins
X,
and
the
idea
here
is
that
we're
going
to
provide
these
reports
for
these
communities.
A
There
are
some
details
that
need
to
be
worked
out
like
which
of
the
chaos
metrics.
The
communities
would
like
and
I
also
think,
maybe
the
timeframe
that
we
would
look
across
these
metrics
on
you
know
kind
of
how
we
represent
that
I
did
send
an
email,
as
I
was
looking
through
the
action
items
for
today
introducing
Sean
and
Georg,
who
have
decided
to
be,
or
thank
you
for
for
being
the
point
of
contact
from
Cass
with
Kate
and
Cara,
so
Kate
being
from
Zephyr
and
Cara
being
from
Jenkins
X.
So
hopefully
the
introduction
we
can.
A
A
A
A
A
A
D
B
A
Great
way
to
soar
some
excellent.
Thank
you
any
other
comments
on
that,
like
everything
moving
moving
forward.
Slowly,
but
surely
chaos
con
so
there's
the
link
to
chaos
con.
We
do
have
our
keynote,
so
it's
Deb
Mickelson
from
the
software
freedom
Conservancy
see,
which
is
great.
Does
anybody
have
thoughts
about
a
second
keynote?
We
have
done
too
in
the
past,
and
we've
also
done
one
in
the
past.
So
yeah.
E
A
E
A
Well,
let's
see,
okay,
thank
you,
sponsors
so
again,
continued.
Thank
you
to
get
lab
and
Seco
assist
and
Patricia
the
really
nice
thing
about
the
sponsorship
as
well
as
that
we're
gonna
be
able
to
provide
lunch
on-site
which
I'm
yeah
I'm
really
happy
about,
because
that
keeps
everybody
there
and
anyway
it's
just
it's
a
nice
thing.
So
pretty
happy
about
that.
Should
we
be
doing,
we
should
probably
thinking
about
some
signage.
E
A
E
D
E
F
E
E
B
A
Okay
call
for
parks,
so
call
for
proposals
call
for
proposed
talks.
The
deadline
is
the
30th
of
November.
So
honestly,
if
you're
going
and
you
have
insights
into
what
community
health
needs
to
your
organization
or
to
your
projects,
it
would
be
great
if
you
could
submit
I
know
that
we
have
a
lot
of
the
usual
suspects,
but
that's
okay,
if
we're
the
ones
that
are
talking
about
this
stuff.
You
know
like,
for
example,
Sean
like
if
you're
doing
work
with
augur.
It
would
be
silly
to
not
talk
about
augur,
but
to
me.
A
F
B
A
Okay,
so
yes,
we
submit
and
honestly,
if
you
know
folks,
I
think
we're
talking
about
ways
to
kind
of
start
reaching
out
to
people
directly
to
encourage
them
to
submit.
So
perhaps
if
they've
attended
cast
cons
in
the
past-
or
we
know
that
this
is
an
area
for
them,
but
they
haven't
submitted
prior
if
we
could
all
just
kind
of
do
our
part
and
encourage
folks
directly
to
participate.
That
would
be
great
if
you
know
somebody
who's
kind
of
working
around
this
issue.
So
there
is
a
planning
document.
B
A
A
B
B
E
E
A
E
E
A
A
So
if
people
have
an
interest
in
this,
please
reach
out
to
me,
and
at
least
the
first
thought
is
ways
that
events
could
badge
themselves
using
the
Chaos,
DNI
metrics,
so
I
think
at
the
moment,
in
the
first
release,
we
had
three
metrics.
Is
that
right:
family
friendliness,
diversity,
access
tickets
and
event,
code
of
conduct,
so
the
in
terms
of
kind
of
moving
this
badging
forward
program
we're
proposing
two
more
metrics
around
event:
diversity,
which
is
speaker,
demographics
and
attendee
demographics.
A
So
the
badging
program
that
I
actually
have
five
metrics
that
events
could
bed
to
themselves
off.
Of,
for
example,
do
you
provide
diversity,
access
tickets?
Are
you
you
know?
What
is
your
evidence
for
being
family-friendly?
Do
you
have
a
code
of
conduct
for
your
event?
Do
your
report?
Speaker?
Demographics?
Do
you
report
attendee
demographics,
just
really
these
kind
of
things,
so
it
kind
of
it's
just
more
of
a
statement
for
folks
here.
I
think
this
is
a
really
cool
idea.
A
Comments
on
this
or
has
an
interest
in
participating
or
just
I
mean
you
and
I
have
talked
about
it.
So
yeah
I
mean
I've
talked
about
in
other
weeks
here
too.
So,
if
you
do
have
an
interest
that
would
be
great
and
I,
don't
know
kind
of
what
the
timeframe
is
on
this
I
think
we
have
to
kind
of
build
a
prototype
workflow
system
by
which
this
would
occur,
and
that
would
be
something
that
I
could
bring
forward
to
folks
and
then
I
would
think.
A
We
also
have
to
consider
how
we
consider
the
metrics
so,
for
example,
if
you're
at
an
event
and
you're
looking
to
get
an
event
badge.
How
do
we
consider
things
like
attendee
demographics?
You
know
like:
what's
the
evidence
we
need
for
that
or
speaker,
demographics
or
you
know,
I
think
we
probably
as
opposed
to
just
having
everybody
kind
of
use,
their
own
judgment.
You
know
what
are
the
what's
our
evidence.
Essentially,
so
those
things
have
to
be
worked
out.
A
So
I
think
at
some
point
this
will
probably
come
to
the
the
most
likely
working
group
being
DNI.
So
we
haven't
really
had
an
in-depth
conversation
there
about
this
all
right.
So
that's
that
any
questions
on
that
all
right,
we're
just
moving
right
along
this
is
this
is
how
things
go
when
we
have
that
folks.
So
the
communication
committee
I,
was
not
at
that
meeting,
so
I
actually
don't
know.
This
is
like
one
thing:
I'm
I,
don't
actually
know
what's
going
on
so
does
anybody
have
an
update
on
this
I.
A
A
F
A
On
the
the
linking
of
software
and
metrics,
this
is
something
that
I've
brought
up
a
few
times,
and
the
idea
here
is
that
we
have
obviously
several
tools,
including
auger
and
grimore
lab
that
are
part
of
chaos,
and
then
we
have
the
metrics
that
are
also
part
of
part
of
campus
right,
and
so
the
idea
is
just
making
sure
that
that
we
kind
of
recognize
the
work
of
each
other,
and
so
Shawn
I
had
I'm
looking
at
you.
So
I
was
wondering
if
there
was
an
easier
way
to
do
this.
A
C
C
A
C
Forever
I
mean
from
a
from
a
software
perspective,
I
think
it's
super
useful
to
people.
I
mean
I,
think
that
the
value
add
isn't
necessarily
to
cath
the
caste
project.
It's
to
people
that
want
to
consume
the
software,
whether
extreme
or
ladder
auger
or
something
else.
Having
that
link
to
the
definition
is
a
value
add
for
the
software.
C
It
feeds
back
to
chaos,
I
think
as
well,
but
fundamentally
I
think
the
value
is
for
consumers
of
wherever
the
software
is
so
I
mean.
I
would
certainly
defer
to
you
because
you're
a
maintain
those
and
we
have
an
incentive
to
encourage
the
community
to
not
change
the
links
once
they
published.
Even
if
the
metric
changes,
if
you
can
keep
the
links
the
same,
but
that
will
allow
for
more
lab
and
Agra
cube
and
Bendis
with
less
labor
cost,
because
it
is
a
fairly
sizable,
leider,
kostet
offense.
A
A
C
A
C
C
A
F
C
B
D
A
A
B
Decided
to
date
during
the
callback,
we
will
add
the
text
that
you
have
here:
okay,
good
with
the
repo
readme
the
website
and
then
in
our
Engram
or
lab
itself.
We
have
an
about
panel,
oh
great,
where
we
just
can't
had
this
to
the
description
dreaming.
We
also
have
an
issue
for
linking
to
individual,
metrics
and
I,
just
added
the
comment
that
we
discussed
to
only
link
to
released
metrics,
okay,.
A
A
Are
a
few
like
little
details
but
I
think
from
a
template
perspective?
They're
all
done
so
this
morning,
I
spent
time
kind
of
going
through
each
of
the
working
groups
cross-referencing.
What
was
in
spreadsheet,
with
what
is
actually
in
the
repository,
so
I
believe
those
are
all
updated,
so
we'll
just
have
to
get
those
out
as
released
to
generally
speaking,
I.
Think
I
say
this
all
the
time
the
template
works
well,
I've
run
into
a
few
little
issues,
sometimes
around
implementation
like
where
to
put
text
in
the
level
of
detail
that
needs
to
be
provided.
A
A
A
D
A
Really
not
much
to
it,
but
it's
just
there
as
a
placeholder,
because
it's
something
that
we've
heard
before
or
somebody
has
brought
it
forward
and
so
I'm
updating
all
of
those
to
the
new
templates.
That
goes
a
little
bit
faster,
particularly
if
nothing
has
any
content
in
it.
It's
pretty
easy
to
just
just
kind
of
remove
those
and
even
like
Sean.
Some
of
them
have
like
the
old
MSR
14
database
calls
and
I
just
remember,
moving
a
lot
of
those
references
so.
A
A
Yeah
yeah
so
anyway,
those
are
all
being
updated
as
well
any
questions
or
comments
on
that
and
every
obviously
this
point
forward.
Every
new
metric
should
be
on
the
new
template
that
doesn't
seem
to
be
a
problem
at
all.
A
A
So
I
just
green
means
it's
been
released,
I
needed
another
color,
we
could
almost
get
rid
of
red,
but
purple
means
that
it's
ready
for
the
next
release.
So
I
don't
know
if
this
needs
to
be
indicated,
but
we
have
those
that
are
released
and
those
that
are
actually
ready
for
release.
So,
for
example,
common
has
a
purple
one
which
is
activity
dates
and
time.
F
A
B
A
B
A
Okay,
so
there
you
go
so
that's
that's
all
updated
should
be
all
good
I,
don't
know!
If
anybody
has
questions
on
this
tracking
spreadsheet
again.
I
do
encourage
the
working
groups
to
take
a
look
at
this
and
update
it
accordingly,
it's
you
would
have
a
lot
of
the
insight
that
maybe
sometimes
I
don't
have
in
terms
of
metric
names
or
what's
being
brought
forward,
so
I
do
in
each
of
the
working
group
meeting.
A
A
A
B
F
A
B
B
F
B
F
A
B
C
B
B
A
F
Would
say,
as
far
as
working
groups
making
changes
to
their
to
their
releases,
it
would
be.
We
gave
them
a
lot
of
time
on
this
last
release.
It
might
be.
It
might
be
a
good
idea
to
really
push
them
to
modify
the
the
release.
As
the
comments
come
in
during
the
comment
period,
mm-hmm.
A
C
Evolution
I
can
report
that
there's
a
group
of
metrics
that
were
moving
towards
that
stabilized
template,
that's
being
used
for
risk.
I
can
report
that
we
have
a
small
set
of
metrics
that
are
also
reflected
in
the
spreadsheet
that
are
being
developed
and
will
be
used.
Those
are
the
two
that
I
have
updates
for.
Okay,.
C
A
Yeah
so
there's
an
ASF
survey:
that's
going
out
with
respect
to
getting
a
better
idea
about
diversity
and
their
projects.
Correct
me,
if
I'm
getting
this
upload,
the
wrong
Georg
but
they've
been
working
with
some
folks
kind
of
across
a
variety
of
different
places
to
which
Kaos
has
some
input
in
this,
so
the
survey
is
being
released
and
I
think
that's
about
it.
Don't
get
that
am
I
right!
Yep.
A
Common
I
can
tell
you
the
common
template
or
what
the
common
repository
structure
has
been
updated
around
who?
What,
when,
where
kind
of
things
so
that's
that's
complete.
So
we
had
to
read
and
rename
some
of
the
focus
areas
and
at
the
moment
there's
a
single
metric
around
dates
and
times
that
is
being
brought
forward
in
common,
and
it's
like
I
said
maybe
earlier,
it's
largely
done,
value
will
be
Indies
on
UD
is
not
on
it.
I.
A
I
had
a
man
I,
wasn't
that
the
last
value
call.
So
it's
okay.
If
we
have
no
update
I
think
this.
This
was
the
author.
It
was
the
off
week
so.
D
C
B
C
Now,
basically,
we
have
we've
got
all
the
licenses
in
the
project
listed,
as
well
as
the
license
coverage
lots
of
license
information,
but
now
we
have
the
percent
of
the
licenses
that
are
OSI
approved
on
our
projects.
This
is
deafer.
There
are
three
files
that
have
none
OSI
through
those
and
I'm
sure,
when
Kate
sees
that
it
will
be
fixed.
B
C
A
F
C
Risk
metrics
continue
to
evolve.
There
were
also
a
number
of
installation
issues
that
emerged
from
discussions
in
the
auger
call
that
we
have
once
a
week
on
on
Wednesday
that
1:00
p.m.
Central,
Standard,
Time
and
the
installation
is
pretty
smooth
now
and
right
down
to
loading
up
your
own
repos
and
collecting
data.
So
I'm
excited
about
that.
The
whole
team's
really
excited
about
that.
C
A
A
B
So
today,
during
the
remote
lab
called,
we
decided
to
next
week
look
at
a
possible
collaboration
between
grimore
lab,
an
auger.
The
shared
problem
that
both
face
is
knowing
what
data
sources
to
look
at
and
what
projects
to
analyze-
and
there
are
different
approaches
right
now,
but
we
want
to
see
if
we
can
standardize
this
into
one
that
is
called
the
project's
Jason
right
now,
where
we
specify
hey
these
are
the
github
repos.
These
are
the
projects.
B
A
C
C
Simply
because
there's
people
who
are
not
going
to
adept
at
generating
caisson
files,
maybe
there's
some
way
that
we
can
provide
them
the
utility
that
would
take
a
CSV
and
fill
the
JSON
structure
so
that
that
could
be
the
standard
input
I
mean
that
would
be
pretty
straightforward,
so
step.
One
is
there's
no
reason
for
these
tools.
They
have
different
import
formats
first
step.
One.
Is
that
and
then
step
two
is
making
sure
that
it
remains
easy
for
the
community
manager.
That's
not
a
JSON
aficionado,
okay,.
A
C
B
One
is
a
grower
and
he
uses
it.
So
we
want
to
have
the
conversation
to
see
if
it's
feature
complete.
Maybe
auger
has
additional
ideas,
but
otherwise
it's
about
our
learning,
the
language
of
projects,
Jason
and
then
the
second
part
does
beast
cherry,
which
is
a
graphical
user
interface
for
building
the
project
station.
So
you
don't
have
to
actually
write
in
a
text.
Editor
Jason,
that's.