►
From YouTube: CHAOSS.Community.June.4.2019
Description
CHAOSS.Community.June.4.2019
A
A
So,
since
today
is
the
monthly
called,
we
have
an
agenda
to
get
up
updates
from
the
working
groups
update
from
software
google
Summer
of
Code
update.
We
have
an
upcoming
release,
so
we
talked
about
the
metrics
and
the
release
schedule.
We
have
our
Kaos
Khan
and
the
CFP
is
still
open.
And
finally,
there
was
a
request
to
talk
about
code
of
conduct
and
repositories
and
we'll
talk
about
that.
I
just
received
requests
to
do
some
introductions
for
anyone
who.
A
D
D
Well,
first
of
all,
just
introduce
myself
as
a
say
and
the
show's
working
from
this
area
and
university
I
reckon
Carlos
a
man
involved,
maybe
in
the
revolution
working
group
and
in
the
model
of
one
of
the
social
choices.
With
respect
to
the
revolution
working
group,
we
have
been
working
in
defining
some
of
metrics
related
to
issues.
We
are
still
working
on
that
and
in
the
last
week's
I,
think
that
the
most
important
focus
and
helping
our
our
google
Summer
of
Code
students
that
are
working
with
reference
implementations
of
the
metrics.
D
E
Can
give
a
common
metrics
working
group
update?
This
is
dawn
foster,
so
we
have
been.
We've
been
mostly
working
on
figuring
out
what
metrics
we
want
to
clean
up
and
have
ready
for
the
release,
so
we're
actually
meeting
weekly
now,
at
least
for
for
the
rest
of
this
month
and
possibly
a
couple
of
weeks
into
July,
so
that
we
can
get
some
metrics
ready
for
the
ready
for
the
release.
Since
we're
a
relatively
new
working
group,
we
have
a
lot
of
work
left
to
do
so.
E
That's
one
of
the
things
that
probably
probably
the
biggest
thing
that
we're
we're
working
on
the
other
recent
change
that
we've
made
with
the
metrics
working
group.
I,
can't
remember
if
we
discussed
in
the
last
big
monthly
meeting,
but
we
are
now
working
out
of
a
separate
repository,
so
we
were
working
out
of
the
main
metrics
repository
which
was
becoming
confusing.
So
that's
where
all
of
the
metrics
are
and
we
needed
to
create
some
focus
areas
and
things.
So
we
know
of
a
separate
repository
for
the
common
metrics
working
group.
E
A
A
F
G
Been
developing
a
set
of
metrics
focused
on
understanding,
licensing
and
also
understanding
of
software
building
materials,
so
you've
been
to
a
minute
for
the
type
software
building
materials
for
the
depository
scanning,
these
gee
socks
and
auger,
and
we're
putting
out
we're
gonna
be
putting
that
into
these
are
facing
front
end
piece
of
auger
here
in
the
next
couple
of
weeks,
and
the
metrics
that
we
have
proposed
are
on
a
list
inside
of
our
repository,
but
we're
going
to
add
that
to
the
list
on
Matt's
central
command.
Shortly,
that's
my
responsibility!
So
it's
behind.
G
G
G
The
idea
that
what
is
basically
knowing
what
is
the
list
of
pieces
of
software
libraries
and
other
projects
that
are
incorporated
in
something
that's
deployed
inside
of
the
corporate
environment.
So
it's
thinking
about
the
consumptions,
what
I
call
the
consumption
side
of
open
source
software
I
think
think.
A
lot
of
us
produce
open
source
software.
F
H
So
I've
got
five
things
to
share.
First
is
we
are
in
the
process
of
putting
together
an
email
survey,
that's
going
to
go
out
to
a
great
number
hundreds
of
the
folks
in
open-source
program
offices-
that's
being
done
by
the
node
second
is
hopefully
in
the
next
week
or
two
we'll
have
an
augur
instance
that
we
can
use
to
to
start
to
actually
assemble
value.
Metrics
for
forget
this,
an.
G
H
We
also
are
going
to
putting
together
a
series
of
interviews
where
we're
going
to
go
out
and
talk
with
with
folks
in
program,
open
source
program
offices,
maybe
like
half
a
dozen,
and
that
is
in
preparation
for
talks
that
we
will
do
in
August.
We
are
accepted
to
speak
at
open
source,
a
summit
in
North
America
and
we've
put
in
a
proposal
for
Kaos
Khan.
So
hopefully
that
gets
accepted
and
the
final
thing
is
over
the
next
week
or
two
we
will
put
together
also
value
metrics.
H
H
There's
kind
of
to
two
broad
categories
of
metrics
that
we
have
been
discussing:
one
relates
to
project
managers,
so
open
source
value
for
repo
maintainer
Xand
project
managers
and
and
those
metrics
relate
to
economic
value
that
the
cost
of
the
the
labor
cost
of
creating
a
repo,
the
labor
cost
of
fixing
a
bug.
The
the
innovation
speed
things
of
that
nature.
H
The
other
type
of
value
metrics
that
we
have
been
discussing
relate
not
to
project
maintainer
x',
but
project
contributors
and
we've
probably
sort
of
classed
that.
As
you
know,
how
can
we
help
project
contributors
make
a
living
wage
in
open
source,
and
so
for
that
we
look
at
metrics
like
you
know,
which,
which
open
source
repos
are
most
valuable,
which
open
source
repos
are
being
used
by
large
organizations.
You
know
where
are
there
the
opportunities
to
go
in
and
make
consulting
fees
or
perhaps
get
paid
bug
bounties?
F
Ring
some
more
context
today
you
people
in
the
call
is
that,
as
you
can
see,
said,
working
groups,
each
of
the
working
groups
as
a
specific
focus,
has
value
or
restore
precision
or
diversity
inclusion.
Then
there
is
a
common
set
of
metrics
that
are
part
of
everything.
Are
they
working
group
and
then
this
is
the
more
the
most
theoretical
approach
to
define
metrics,
but
then
you
there
are
some
piece
of
software
that
ferments
in
a
small
board.
F
Marla
or
Greg
or
perspectives,
there
are
two
main
legs,
the
same
chaos
that,
by
the
way,
the
acronym
is
community
health
analytics
for
open
source
software.
So
we
have
metrics
team
with
the
several
working
groups
and
then
the
software
part
where
we
are
developing
trying
to
bring
all
of
this
knowledge
from
the
more
through
the
collective
view
into
practice.
A
G
Can
go
first,
so
we
have
two
google
Summer
of
Code
students
who
are
working
actively
on
risk
and
risk
and
value
metrics
right
now,
implementing
API
endpoints
off
of
the
new
schema
that
we've
implemented,
which
integrates
data
from
github
libraries.
Do
other
authors
on
the
side
base
depository,
minor
and
bunch
of
other
things
that
we're
pulling
in
so
they've
been
really
actively
developing
those
out
and
that
going
pretty
fast
with
it.
Actually,
we
also
have
our
new
worker
collection
architecture
working
with
github
right
now
and
also
the
Linux
badging
API.
So
that's
exciting!
D
So,
with
respect
in
my
lab,
I
was
just
taking
notes,
so
we
had
some
results
in
the
sorting
hat.
They
didn't
person
management
component.
We
also
have
Google
or
some
of
the
students
working
with
with
the
owl
in
improving
wasting
mr.
Malla.
Remember
that
vial
is
a
fool
that
can
run
a
fictional
specific
files
from
a
new
version
of
the
specific
files
or
in
a
git
repository.
This
integration
is
basically
to
turn
your
dashboards
with
information,
waited
on
running,
license,
analysis
or
complexity,
analysis
or
things
like
that.
So
the
tank
is.
J
A
A
D
A
D
Answered?
Yes,
yes,
of
course,
so
that
the
one
involved
in
remote
lab
is
working
with
ground
of
them
in
Canada
a
moment
ago.
Well,
it's
a
big
tool
for
running
metrics
on
every
release
of
every
file
and
what
it
does
is
run
external
goals
and
inject
that
information
into
the
useful
to
Muslim
stream
of
data,
and
this
one
student
is
now
working
in
integrating
that
with
the
database
with
elasticsearch
so
that
we
can
have
hopefully
at
the
end
of
the
of
the
universal
soul
theory.
We
have
that
work
with
that
information.
D
D
One
building
on
the
Refresh
implementation,
because
area
is
to
make
them
in
a
way
that
can
be
easily
understood,
and
for
that
we
are
using
fashion
model,
but
we
are
now
responding
them
into
classes
so
that
the
common
code
is
clearly
separated
in
one
plane
and
the
code
specifically
dependent
for
the
network
is
in
another
place,
and
this
person
is
also
of
this.
This
new
structure
is
also
going
to
know
having
testing
on
the
Refresh
implementation.
It
seems
to
be
good
for
avoidance
generation,
small
things.
G
A
Yes
and
I
do
want
to
encourage
everyone
here
in
the
community
to
read
the
blog
post
they're
being
sent
to
the
Megan
list,
so
you
should
all
have
received
them
and
I
think
the
students
are
doing
an
amazing
job.
That's
really
identifying
the
tasks
that
they
work
on,
that
describing
the
challenges
that
they're
overcoming
and
how
they're,
overcoming
in
so
there's
they're,
really
helping
us
to
see
how
they
learn
so.
A
A
A
A
A
Moving
on
to
the
chaos
Kok
North
America
on
August
20,
we
still
have
the
call
for
participation
out.
We
extended
it
by
one
week.
So
please
everyone
who
is
coming
or
who
can
potentially
come.
Please
do
submit
what
you
would
like
to
talk
about.
We
are
also
thinking
about
having
open
workshop
discussions
and
having
unconference
working
discussions
specific
to
the
working
groups,
but
we
really
want
to
make
this
task
on
for
the
community
by
the
community
and
we
need
to
know
what
it
is
that
you
want
to
talk
about.
A
E
E
A
A
Why
do
we
do
that
because
clearly
shows
that
there's
a
code
of
conduct,
it's
the
right
place
to
show
that
we
have
it
in
every
repository
and
also
github
has
some
internal
algorithms
as
far
as
I
know
we're
not
having
a
code
of
conduct
actually
Doc's
the
ranking
in
their
search.
So
could've
come
back
as
the
right
thing
to
do
and
it
helps
us
having
it
having
the
full
code
of
conduct
copy,
duplicates
information
and
we
were
looking
for
a
better
way
to
do
it
in
the
common
working
group.
A
And
if
you
click
on
the
link
in
the
minutes,
you
can
see
how
the
working
the
common
working
group
is
trying
to
solve
the
duplication
of
information.
Simply
by
saying
we
do
have
a
code
of
conduct
in
this
code
of
conduct
markdown
file
and
then
linking
to
one
truth
of
source
source
of
truth
in
the
government
repository
or
the
website,
which
one
is
written
to
governments,
yeah
and.
E
E
Yeah
I
tend
to
think
we
should
be
consistent
across
all
of
our
repositories
and
use
I
think
we
should
use
some
points
this
across
all
of
our
repositories,
as
opposed
to
having
something
copied
and
pasted
where
we
could
end
up
with
different
information.
If
we
ever
decide
to
change
the
code
of
conduct.
J
A
A
A
Don't
see
anyone
raising
a
hand
or
unmuting
themselves,
which
hopefully
link
you're
all
eager
to
get
back
to
finishing
metrics
working
on
the
good
work
that
you're
doing.
Thank
everyone
very
much
for
participating
today
and
our
call,
and
throughout
the
weeks
and
months
putting
everything
together.
I
was
just
looking
at
our
minutes.
We
have
almost
three
pages
of
meeting
minutes,
but
just
updates
of
what's
happening
in
the
community
and
I
think
the
amount
of
activity
that
we
have
is
it's
just
amazing,
reflecting
that
and
I'm
super
happy
with
everyone
here.
I
thought
working
again.