►
From YouTube: CHAOSS Weekly Hangout: June 26, 2018
Description
Notes:
Who is going to Portland
- OSCON?
- Community Leadership Summit?
D&I workgroup is working on resources pages (metric detail pages)
- How to engage developers who want to implement metrics? --- Maybe we want to create issues for metrics that need implementation and flag them for developers to find.
- Regular next next call would fall on the 4th of July -- workgroup will send out an email about moving or cancelling
GMD workgroup has very meta-level discussion on the mailing list about metrics and language
- the conversation will affect the entire community because it is crucial to create clarity of what we talk about.
- conversation is highly technical -- desire to use more plain english and ensure that it is useful to community managers
- Expecting a very intersting next call: This week Thursday 11am CDT -- everyone invited!
Move Monthly call out of the 4th of July by one week to July 10th. We will have a weekly hangout on July 3rd instead.
CHAOSScon preparation update:
- Working on wifi for everyone
- The coordinating committee is working on a budget to be able to approach sponsors
A
D
D
C
C
C
C
D
E
D
E
C
Product,
so
how
do
we
make
the
operationalize
the
metrics
and
the
approach
we
had
in
the
metrics
committee
so
far
is
to
have
detail
pages
that
specify
how
is
the
metric
defined?
How
is
it
calculated,
how
can
it
be
implemented
in
code,
and
we
followed
a
similar
process
in
the
diversity
and
inclusion
work
group.
C
C
C
C
C
First,
we
have
the
question
that
we
had
in
the
table.
Then
we
have
the
description
of.
Why
do
we
even
care
about
documentation?
What
benefits
does
it
have
looking
at
this
metric,
and
then
we
have
sample
objectives
for
a
community
to
look
at
okay?
Why
do
I
want
to
assess
documentation?
What
can
be
positive
outcomes
for
me?
If
I
know
how
well
we
are
doing
with
regards
to
documentation.
E
C
C
E
I
mean
when
I
had
looked
at
the
you
know
like
I,
I
I
don't.
I've
given
been
giving
a
lot
of
thought
to
the
diversity
and
inclusion,
the
way
that
that
repository
is
organized
and
if,
if
there
is
any
need
or
interest
in
distinguishing
between
metrics,
that
can
be
measured
using
trace
data
versus
metrics.
C
E
So
I
think
from
a
I
understand
the
sentiment
of
the
group
and
I'm
I'm
thinking
only
from
a
pragmatics
of
implementation
perspective
yeah.
I
think,
for
the
developers
that
we
have
who
are
interested
in
participating
in
and
advancing
the
provision
of
metrics
if
there
would
be
some
kind
of
tag
or
flag
that
the
group
could
provide
where
they
think
a
metric
could
possibly
be
done
without
like
a
survey,
for
example,
there
are,
there
are
algorithms
that
are
imperfect,
but
possibly
useful
for
discerning
gender.
E
There
are
algorithms
that
are
imperfect,
but
possibly
useful
for
in
inferring,
national
international
backgrounds
and
those
are
components
of
what
one
might
consider:
diversity,
inclusion
and
ways
of
profiling.
I
suppose
a
contributor
base
or
contrasting
contributor
bases
on
different
projects-
and
I
know
that
there
may
be
some
sensitivities
around
wanting
to
do
that
or
not
wanting
to
do
that,
and
if
the
sentiment
is
hey,
let's
not
do
that.
That's
just
a
little.
You
know
because
it's
imperfect,
we
risk
there's
lots
of
there's
a
lot
more
risk
associated
with
that
than
advantage.
C
E
E
A
D
E
From
then
on,
I
think
sunday
is
pretty
heavily
unconferenced.
If
I'm
reading
it
correctly,
although
there
are
some
prepared
present
there
is,
I
haven't
been
there
before
so
again,
nothing
to
compare
it
to
I'd,
say
it's
a
mix
of
conference
and
unconference
yeah.
At
least
it
looks
that
way
to
the
schedule.
I
don't
know
how
they'll
run
it.
Maybe
the
talk.
D
E
C
C
C
This
is
part
of
a
pull
request.
We
have
right
now,
from
our
last
conversation,
a
resource
page
where
we
outline
what
are
the
metrics.
Why
do
we
care
about
the
metrics?
How
can
we
measure
and
assess
these
metrics
and
the
understanding
of
what
the
metric
is
here
is
a
little
bit
different
than
what
we've
been
talking
about
before,
because
it's
more
high
level
and
it's
not
necessarily
something
you
can
implement.
G
E
G
C
H
E
D
C
E
Yeah,
there's
a
I
mean,
there's
a
very
big
meta
discussion.
That's
happening
on
that
list
right
now
and
I
think
it's
going
to
span
not
only
the
growth
maturity
decline,
metrics,
but
really
all
metrics
brought
about
through
trace
data,
and
I
I
think
it
the
understanding
of
it
will
be
really
important
and
the
language
that
we
choose
to
articulate.
E
E
I
need
to
look
at
what's
happening
in
some
window
of
time,
which
we
were
calling
a
filter
and
then
what
are
the
deltas
over
a
window
of
time
over
several
windows
of
time
that
I'm
calling
a
filter
and
then
what
are
the
trajectories
that
I'm
also
calling
some
kind
of
a
filter?
So
I
think
getting
super
clear
about
what
these
things
are
is
going
to
take
some
discussions
and
dialogue
and
time.
E
So
as
we
as
we
go
through
that
that
discussion
this
week,
which
hopefully
will
get
some
more
community
managers
involved
with,
then
I
think
that
we'll
have
I
mean.
I
think
I
think
that
discussion
is
going
to
be
really
important
for
all
metrics,
because
if,
if
we
don't
make
those
kinds
of
distinctions,
then
it
gets
difficult
to
say
these
are
a
metric.
This
is
a
metric
that
I
can
intelligently
compare
across
multiple
different
projects,
so
that
makes
sense.
G
E
Yeah,
I'm
hope
you
know,
one
of
two
things
will
happen.
We'll
have
a
bunch
of
you
know
right
now.
The
discussion
on
the
mailing
list
has
been
pretty
heavily
tilted
towards
computer
sciencey
people
and-
and
that's
that's
concern
that
I
have
because
I
think
that
the
decisions
about
what
we
call
these
things
and
how
we
use
them
need
to
be
influenced
more
by
non-computer
sciencey
people.
So
I
look
at
myself
as
being
at
a
deficit
and
a
lot
of
the
people
in
that
group.
E
Maybe
jesus
is
the
most
bi-modal
of
us
because,
essentially
with
grimoire
lab
he's
managed
a
community
as
well
as
built
metrics
for
it,
but-
and
I
think
that
it's
jesus
who's
come
up
with
a
lot
of
these
nuanced
ideas
and
then
I've
had
slightly
different
different
perspectives
or
words
for
what
are
very
similar
things,
and
then
I
think
daniel
german
and
others
have
brought
more
of
a
computer.
Sciencey
objective
perspective
back
to
it,
and
so
I
think
I
think,
having
like
a
singular
or
a
stronger
community
manager.
E
E
E
E
C
B
E
E
B
I
I
I
E
D
E
I
Yeah
yeah,
so
that's
why?
I
think
that,
as
we
agreed
some
millions
ago,
we
should
maybe
come
back
to
the
idea
of
discussing
the
english
description
of
the
metrics.
Don't
talk
that
much
about
how
they
are
calculated,
I
mean
I
can't
keep
on
talking
with
danielle
because
it
doesn't
doesn't
harm
but
try
to
reconnect.
I
Yeah
yeah
yeah
right,
something
like
that.
That's
convenient
too,
but
maybe
we
could
focus
on
some
of
the
specific
metrics
because,
for
instance,
during
the
last
few
weeks
we
have
been
working
with
these
metrics
about
delays,
and
how
long
does
it
take
until
the
first
reaction
until
the
ticket
is
closed
and
those
are
concepts
that
are
I
mean
the
general
idea
is
easy
to
understand
that.
How
do
you
calculate
that
and
the
difference
is
if
this
is
a
time
series
or
not
and
stuff
like
that?
I
Well,
that
doesn't
that
that's
not
that
important
for
talking
about
the
meaning
of
the
matrix.
So
maybe
we
should
be
focusing
on
saying:
let's
talk
this
week
about
this
and
this
metrics,
to
which
extent
you
find
it's
important,
to
which
extent
you
find
it
is
useful.
Can
you
provide
any
use
case
or
it's
useful,
something
like
that?
What
do
you
think.
I
I
mean
I
actually
I
have
the
intention
of
staying
working
on
the
let's
say:
how
do
you
be
part
of
the
metrics,
so
I
I'm
still
going
to
work
on
how
to
do
that,
how
to
define
it
precisely
and
so
on,
because
I
feel
that's
needed,
but
for
engaging
all
the
people
in
the
community
in
the
chaos
community.
I
think
that
we
need
to
also
focus
on
paying
this
description
and
the
value
that
the
metric
is
providing
in
the
end,
because
that's
the
reason
for
the
metric,
it's
some
abstract.
E
C
D
I
We
have
the
idea
of
trying
to
release,
let's
say
a
stable
version
of
the
graph
maturity
decline
versus
metrics
by
the
calcium.
So
in
two
months
from
now,
and
the
idea
would
be
to
discuss
on
two
sides.
One
side
could
be
on
the
value
of
the
metrics
on
use
cases
and
why
people
think
they
are
interesting
and
so
on
and
the
other
one
would
be
on
precise
description
of
the
metrics
so
that
when
you.
D
D
E
Yeah,
I
think,
no
matter
what
we'll
include
the
they'll
probably
be
a
discussion
on
the
monthly
call,
and
I
think,
as
I
was
saying,
I
think,
before
jesus
got
online,
that
the
nature
of
that
discussion
will
probably
pivot
on
the
degree
of
engagement.
We
do
or
don't
get
from
community
managers
in
the
call
this
thursday
and
because
I
think,
if
we
get
some
good
engagement,
then
the
conversations
about
how
we're
discussing
these
these
issues
like
filtering
and
how
we
express
metrics
resolution
over
time
and
and
doing
some
plain
english.
As
you
mentioned
jesus.
E
But
I
think
if
we
don't
get
a
lot
of
community
manager
discussion,
then
maybe
the
the
discussion
on
the
all
the
monthly
call
will
pivot
towards
you
know.
What
can
we
do
and
I
know
you
and
I
are
trying
to
engage
community
managers
through
contacting
them
in
a
retail
manner.
It's
kind
of
a
tough
time
here
to
do
that.
E
So
we
might
just
want
to
talk
about
our
strategy
for
increasing,
maybe
awareness
that
chaos
has
moved
from
this
metrics
and
software
duality
to
working
groups
that
integrate
those-
and
I
think
I
think,
maybe
the
risk
for
growth
maturity
decline
is
the
mailing
list
has
become
right
now.
It's
just
you
know
the
computer
science
people
are
talking
more
about
it,
because
there
are
some
nuanced
technical
questions
we
have
about
how
to
do
the
calculations
and
that
you
know,
as
jesus
mentioned
pivots
away
from
plain
english
and
disengages
non-computer
science,
people.
I
E
E
I
I
That
would
be
great.
On
the
other
hand,
if
we
have
both
options,
I
mean
they
have
it
wrong,
because
it
seems
that
the
infrastructure
is
having
any
room
for
those
of
us
who
already
have.
We
don't
need
to
use
your
rotors,
which
means
that
the
router
is
not
going
to
be
that
busy,
so
that
the
connection
is
going
to
be
better.