►
From YouTube: CHAOSS.Community.December.3.2019
Description
CHAOSS.Community.December.3.2019
A
A
B
Let's
see
Dean
I,
we
were
working
on
some
new
metrics
and
then
we
have
the
all
of
the
metrics
we
wanted
to
do,
or
the
events
focused
area.
Okay,
all
of
those
are
ready
for
release.
Okay,
I,
don't
know
if
any
other
working
group
has
one
in
time
for
this
area,
but
in
I
have
okay
and
then
we've
been
working
on
some
more
metrics
and
other
purposes:
okay
and
discussing
about
well.
Thank
you.
This
technique
was
accessible
to
you.
C
B
C
D
E
A
C
A
C
I
I
suppose
I
could
mention
briefly.
Then
we
do
have
that.
I
can't
remember
if
we
discussed
this
before,
but
there
is
now
an
enumeration
of
every
license
in
every
file
that
you
can
get
a
list
of
in
auger,
which
is
sort
of
a
risk
related
item,
and
also
that
we
are
now
classifying
the
percentage
of
any
project
that
is
covered
by
an
OSI
approve
license.
A
B
A
So
I
don't
know
if
everybody
got
that
so
basically
in
auger
right
now
and
then
subsequently,
through
the
risk
working
group
they're
doing
license
scans
based
on
the
information,
that's
in
the
project
in
a
repository
and
making
sure
license
coverage
they're
using
pathology
tools
that
are
in
pathology
and
they
can
show
licensed
coverage
and
percent
of
that
coverage
that
is
OSI
compliant
or
OSI
covered
mat.
I,
don't
know
if
you
want
to
add
anything
to
that,
because
I
know
you've
been
working
on
this.
A
B
Georg,
so,
yes,
we
have
been
meeting
in
the
value
group,
the
newest
metric,
that
we
added
was
the
social
currency
metric
system,
okay,
which
we've
discussed
here
on
this
call
two
months
ago,
three
months
ago,
so
remember
yeah.
Now
we
distilled
it
down
into
metric.
Is
that
ready
for
release?
Has
it
gone
through
the
whole
process?
Yes,
it's
ready
for
release.
Okay,
so
they've
been
working
on
this
for
for
the
last
couple
weeks.
Okay,.
A
A
A
Okay,
all
right
I
have
not
I'll,
take
a
look
at
those
but
I,
just
I
guess
during
the
public
comment
here,
I
haven't
seen
him
all
right.
A
It
was
good
thank
you.
Everybody
Don,
with
common.
G
We
haven't
had
a
meeting
in
a
while
and
I
missed
the
last
meeting,
but
I
think
in
this
next
meeting,
which
is
next
week,
which
I
think
is
the
12th
I
think
we're
going
to
talk
about
what
we're
gonna
do
for
the
release
and
talk
about
some
of
the
overlap
with
diversity
and
inclusion
on
one
of
the
metrics
which
I'm
forgetting
which
one
it
was
right
now.
G
A
I
think
one
of
the
things
that's
kind
of
interesting
is:
it
does
appear
that
a
number
of
the
different
working
groups
are
kind
of
coming
up
with
metrics
that
they
thought
fit
in
their
working
group
originally,
but
actually
end
up
kind
of
going
up
to
common
and
so
yeah
right,
it's
cool.
So
you
might
be
inheriting
kind
of
kind
of
a
different
form
of
of
how
you
collect
metrics
that
they
might
just
be
coming
from
other
working
groups
as
well.
Yeah.
A
B
A
Anything
else
kind
of
working
group:
why
is
it
I
think
everybody's
kind
of
focusing
on
the
development
of
metrics
for
the
next
release?
That
seems
to
be
the
the
general
tenor
at
the
moment.
I
think
maybe
well
I'll
just
leave
it
at
that
and
what
I,
maybe
I,
won't
one
of
the
things
that
I'm
always
thinking
about.
A
Is
that
right,
as
we
put
these
metrics
forward,
that
we
are
also
really
legitimately
thinking
about
ways
that
they
can
be
deployed
so
I
know
that
there's
always
the
strategies,
I
kind
of
forget
what
that
category
is
called
like
deployment
strategies,
but
trying
to
find
you
know,
organizations
to
work
with
that
could
put
these
metrics
into
practice
or
trying
to
find
ways
to
get
them
into
tooling,
whether
it's
grimore
lab
or
auger
I.
Think
really,
you
know,
maybe,
after
the
release
kind
of
reflecting
on
how
these
metrics
are
actually
being
deployed.
A
There's
always
something
that's
very
interesting
to
me
like
keeping
those
two
things
connected.
That's
all
because
I
never
want
to
have
a
metric
that
just
kind
of
elam,
then
just
kind
of
sits
there
free
kind
of
just
floating
around
so
so
anyway.
Those
are
my
thoughts
but
they're,
certainly
not
something
that
needs
to
be
addressed
at
the
moment
and
I.
Think
we've
done
a
really
good
job
on
that.
So
that
was
my
comment
that
I
wasn't
going
to
say:
software
updates,
arrogant
things
forum
or
lab.
B
So
since
this
is
the
monthly
meeting
yeah
things
that
happened
during
the
last
month,
we
have
during
the
weekly
calls,
they
were
addressing
a
specific
question
that
we
were
asked
by
the
Jenkins
yep
manager,
and
we
have
just
been
done
and
modeling
how
we
could
answer
the
question.
Okay
I
know,
what's
part
of
the
weekly
chaos
newsletter,
so,
okay.
A
B
Yeah
cauldron
is
a
big
development
just
using
the
grimoire
Lab
tools,
different
composition.
Okay,
work
is
also
being
done
on
some
of
the
back
end.
Things
still
ongoing
to
make
it
more
reliable,
have
better
and
logging
be
able
to
find
it
she's
in
the
platform
more
easily.
Well,
those
are
focuses
right
now.
Okay,.
H
C
Contributors
with
multiple
email
addresses
with
I
think
increasing
effectiveness.
That's
that's
been
a
big
focus.
We've
also
added
a
good
deal
of
support
for
pull,
request
information,
that's
giving
us
insight
into-
and
this
is
just
in
the
development
stage,
but
we
plan
to
release
it
by
the
end
of
the
year.
Insight
into
how
how
active
various
different
Forks
are
to
try
to
paint
a
more
complete
picture
of
the
contributor
community
activity.
H
F
A
Sounds
good,
so
one
of
the
things
that
I
had
for
both
grimore
lab
and
auger
is
how?
How
can
we
continue
to
encourage
developers
who
are
not
necessarily
part
of
that
core
team
to
engage
like
how
have
things
been
post,
google
Summer
of
Code?
Have
those
developers
stayed
involved
and
if
not
you
know,
what
can
we
do
to
help
retain
that
engagement
and
then
obviously
be
on
google
Summer
of
Code?
C
A
B
A
C
Had
we've
had
part
one
of
one
so
I
mean
I,
guess
one
of
our
two
developers
has
I
mean
I,
would
say
extremely
engaged
and
continues
to
develop
the
code
base
that
he
started
for
us
or
different
pieces
of
code
workers
really
that
we've
had
our
other
Google
Summer
of
Code
person
was
super
active
at
the
beginning
of
the
year
like
September
and
early
October,
but
I
think
he's
finishing
graduate
school
and
has
has
moved
on
to
other
things.
Okay,.
H
C
A
Okay,
yeah
I
do
know
both
of
you
were
more
lab
and
both
of
the
projects
for
more
eleven
Hardware
have
focused
a
lot
of
the
ease
of
deployment.
That's
been
a
big
push,
which
has
been
great
Sean
I
know
that
you
were
involved
in
Grace
Hopper
with
auger
yeah,
so
I
mean
it's
just.
It
seems
like
these
continued
activities.
A
C
This
is
actually
that
was
great.
We
have
almost
I
mean
it's
not
necessarily
something
we
sought,
but
we
have
a
piece
of
work
started
at
Grace
Hopper
on
getting
it
to
install
easily
on
Windows
that
one
of
my
students
at
Missouri
is
finishing
up
now,
so
we
may
actually
have
a
way
to
install
it
on
Windows
somebody's
worked
through
all
of
the
idiosyncratic
things
that
exist
there.
Okay,.
A
Does
anybody
have
thoughts
on
things
that
that
I
can
do
or
that
we
can
do
as
a
community
to
just
encourage
I'm,
not
asking
okay
I,
don't
suspect
that
we're
gonna,
like
all
the
sudden,
get
20
developers
into
these
projects?
That's
certainly
not
the
goal,
but
it's
how
to
retain
the
ones
that
are
that
are
there
that
aren't
necessarily
part
of
that
core,
or
even
identifying
ones
and
twos
here
and
there
beyond
what
we're
doing
at
the
moment.
A
B
B
B
A
A
B
A
Okay,
if
I
move
on
to
the
community
bullet
point
again,
I'll
share
the
the
minutes
here
in
the
Chad.
If
I
move
on
to
the
community
bullet
point
kind
of
a
variety
of
things
here,
so
one
is
the
tracking
spreadsheet,
so
I
think
a
lot
of
you
have
seen
this
is
for
metrics
tracking
I.
Think
Sal
is
on
right
now,
so
Salah
had
done
some
work
on
creating
a
consistent
tracking,
spreadsheet,
I
think
all
of
the
tabs
and
sort
of,
if
all
down
to
the
road.
A
So
thanks
to
Saul
offer
kind
of
rating
that
in
and
in
enabling
a
more
consistent
message
across
the
spreadsheet,
Kevin
I
do
think
it's
have
you
I,
don't
know
if
you've
had
a
chance
to
take
a
look
at
the
work
that
Saleh
has
done,
because
I
know
that
you
kind
of
look
at
the
spreadsheet.
From
our
release
perspective,
it
was
probably
some
you
should
take
a
look
at
and
if
something's
not
clear
to
you,
hey.
E
A
H
A
A
Not
at
the
moment
no
okay
community
reports,
its
we're
now
into
December
kind
of
looking
at
Garrigan
and
Shawn
I
know
that
we,
we
have
obviously
made
connections
with
Zephyr
and
Jenkins
X
and
there's
a
lot
of
interest
in
these
reports
that
we
can
does
anybody
have
progress
and
is
gehrig
mentioned.
We're
more
lab
is
kind
of
working
on
some
of
the
the
metrics
that
have
been
expressed
as
interesting
from
Jenkins
X.
Are
there
updates
on
these
again
just
kind
of
curious.
A
A
A
C
The
Zephyr
side
of
things
we've
started
producing
metrics,
but
we
haven't
come
down
to
a
report.
Yet
we're
just
getting
going
on
that
and
our
notes
are
academic
year
is,
but
my
students
are
getting.
This
is
their
last
week
of
class,
so
I'm
kind
of
taking
this
on
and
kind
of
working
on
chipping
away
at
it.
Okay
probably
have
progress
report
next
week.
Okay,.
D
A
E
E
E
E
A
Right
cool.
Thank
you.
The
last
thing
that
I'd
like
to
bring
up
just
in
terms
of
community
is
the
mentorship
program.
So,
okay,
so
you
all
know
that
we
have
the
community
bridge.
The
glue
link
is
on
there
and
so
part
of
the
dollars
that
are
in
community
bridge
are
kind
of
assigned
to
mentorship,
which
is
not
google
Summer
of
Code.
It's
where
we
would
actually
pay
a
mentee
to
be
part
of
the
project.
A
If
you
recall,
we
had
talked
about
using
outreach
e
as
a
way
to
identify
who
those
mentees
could
be
and
outreach
e
is
a
it's
a
six,
sixty
five
hundred
dollar
expense
for
the
project
that
goes
to
the
outreach
program.
Fifty
five
hundred
dollars
of
that
$6,500
is
to
pay
the
mentee.
Five
hundred
of
those
dollars
are
for
travel
for
the
mentee,
and
five
hundred
dollars
are
for
administrative
costs
to
the
software
freedom
Conservancy.
That
runs
the
outreach
e
program.
A
So
I
put
it
there's
a
timeline
in
here
so
currently
today,
December
3rd
is
when
the
new
mentor
mentee
program
starts
at
the
outreach
e
at
outreach
e
meaning
this
is
you
know
when
the
the
mentees
are
doing
their
work,
so
the
work
has
actually
started
today.
So,
but
it
does
look
like
what
I
could
understand
late
January
early
February
is
when
we
as
chaos
could
apply
to
our
Ricci
to
be
an
organization
and
then
maybe,
like
a
month
later,.
A
Individuals
identify
the
projects
that
they
want
to
work
on
and
subsequently
from
there,
a
new
kind
of
period.
Mentorship
period
begins.
So
we
had
talked
about
this
in
the
past.
What
are
people's
feelings
on
using
out
Ricci
as
a
way
to
identify
the
mentor,
mentee
relationship
or
tied
down
to
to
kind
of
move
mentorship
forward?.
A
I'm
done
talking,
people
can
chime
in
or,
if
you
don't
like
it,
that's
fine
too
I
mean
if
we
can
but
I
think
it's
something
we
should
move
forward
with,
because
we
do
have
the
dollars
in
community
bridge.
They
have
been
assigned
to
the
mentor
mentor
them
to
these
mentor
relationships.
I
think
it's
it's
a
good
way
to
keep
people
involved
in
the
project.
I.
B
A
Other
thoughts
on
this
I'm
not
too
concerned
with
an
overlap
with
google
Summer
of
Code
I
think
we
could
probably
do
it
because
I'm
guessing
if
I'm
looking
at
the
date,
I
didn't
put
all
this.
My
guess
is
it
would
go
almost
right
up
to
the
google
Summer
of
Code
period.
It
looks
like
I
think
the
relationship
starts
in
February,
so
it
probably
March
April
May
Julie,
not
a
super
long
period.
I
mean.
B
D
A
When
people
be
okay,
if
I
start
kind
of
pursuing
this,
just
in
this
january/february,
okay,
so
I'm
getting
some
yeses,
so
I'll
I'll
start
doing
the
organizational
application.
It's
not
even
open
yet,
but
I'll
do
that
in
January
and
we'll
just
a
and
step
by
step.
I
don't
know,
for
example,
like
you
know
how
in
google
Summer
of
Code
how
we
have
to
identify
projects
to
a
pretty
pretty
finite
level,
I'm,
not
sure
what
the
level
of
granularity
is
in
outreach
e.
Has
anybody
done
this?
A
A
B
A
A
Alright,
from
an
outreach
perspective,
I
did
just
send
an
email
to
Angela
at
the
Linux
Foundation.
You
know
how
we're
talking
about
helping
them
with
their
events.
Stuff.
All
right,
Matt
see
you
later
and
she's
she's
been.
Apparently
there
was
this
large
conference
called
coop
con
I
think
ate
a
lot
of
time
for
a
lot
of
people
and
anyway,
we're
gonna
we'll
be
connecting
here
shortly.
So
that's
kind
of
the
update
on
that.
A
B
B
A
And
I
would
say
that
I
think
both
of
these
on
the
left
side
of
the
ass
up
side.
These
are
both
largely
related
to
the
efforts
out
of
the
DNI
working
group,
so
this
is
kind
of
back
to
that
earlier
point
of
metrics,
finding
a
home
and
and
being
put
into
practice.
So
that's
really
awesome
to
see
am
I
missing
anything
on
our
reach
Georg.
Sometimes
you
have
some
insight
on
that.
Well,.
A
G
Alright
I
was
muted
and
I.
Don't
know
how
to
work.
My
mouse
yeah
I
mean
what
I
would
say
is
that
we're
in
the
process
of
selecting
the
talks?
So
we
got
a
lot
of
really
great
submissions
and
we
have
a
meeting
later
this
week
to
sit
down
as
an
organizing
team
and
pick
some
of
those
talks.
So
we
should
be
on
schedule
to
notify
people
not
this
week,
but
the
the
following
week,
so
things
are
looking
looking
pretty
good
for
for
chaos
gone.
A
And
I'm
gonna
wait
to
buy
the
speaker
gifts
until
we
know
how
many
speakers
there
are
because
apparently
I
have
to
buy
them
for
speakers
and
for
coordinators
next,
a
a
square
number
at
that
point.
They
don't
take
that
line
to
ride
so
we'll
be
all
good
there.
Anything
else.
Chaos
con
wise,
just
I,
think
kind
of
waiting
till
next
week.
I
did
you
know
with
Deb.
Should
I
I
was
gonna
wait
until
we
had
I
haven't
announced
Deb
as
the
speaker.