►
From YouTube: CHAOSS Common Working Group 2/3/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
There's
the
agenda,
so
we
have
a
few
things
to
talk
about.
We
can
talk
about
the
action
items.
A
Here
we
are:
is
there
okay?
We
then
we
should
talk
about
kind
of
the
expansion
of
of
the
chaos
common
working
group
meeting.
So
I
put
that
next
on
the
agenda
before
we
do
anything
else
and
let's,
let's
just
talk
about
what
we're,
what
we're
adding
and
how
that's
how
that's
going
to
work
and
then,
if
we
have
time
we'll,
do
the
open,
prs
and
issues
we'll
look
at
the
occasional,
consistent
contributors
and
look
at
organizational
diversity,
which
is
the
other
metric
that
we're
in
review
right
now,.
A
Well,
you
know
what
I
probably
haven't
refreshed
it,
and
it's
just
well
look
at
that
completely
different
thanks
for
saying
that
you're
not
gonna
find
me
letting
me
go
on
continue
on.
We
can
start
by
adding
yourself
in
the
attendees.
That's
a
that's
a
good
thing
to
start
with.
A
Cool
I'll
just
I'll
start
cranking
on
some
of
the
things
in
the
last.
The
last
meeting.
A
C
A
I
think
this
was
different.
I
think
this
was
creating
an
actual
label
for
revisiting
metrics,
which
we
have
okay,
okay,
because
you
also
have
the
action
item
to
create
the
issue
and
the
google
doc
for
the
organizational
diversity.
B
A
Cool
and
then
it
looks
like
we
can.
I
saw
the
pull
request
for
the
converting
the
the
minutes,
so
we
can
take
a
look
at
that
in
a
bit
so
so
well
done
everyone.
We
actually
we
actually
got
all
of
our
action
items
from
the
last
meeting.
So
that's
that's!
Pretty
cool.
B
Put
that
like
on
on
hold
for
just
a
second,
if
we
it's
kind
of
a
common
issue
that
came
out
of
dei,
it's
about
how
to
think
about
labels.
A
A
Okay
cool,
so
so,
let's
talk
about
the
the
proposed
changes
to
the
the
common
working
group.
I
think
it's
just
a
common
working
group,
so
we
talked
about
a
few
things,
so
we
talked
about
adding
some
of
the
operational
things
into
into
common,
including
things
like
the
data
use,
awareness
statement
and
some
of
the
what
were
the
other
ones,
security
framework
stuff.
I'm
not
sure
what
the
consistent
project
document
distribution
is.
Does
anybody.
B
In
this
case,
say
metrics
working
group,
so
the
first
one
is
with
metrics
release
update,
so
ritik
is
on
and
he
had
done
the
work
with
the
release
process
with
kevin
who's,
also
on
and
josh,
and
myself
and
georg,
so
just
to
help
automate.
That
process
to
which
there
are
a
bunch
of
things
going
on.
This
is
also,
I
think,
includes
the
the
mars
software
as
well.
B
As
I
would
say,
it
includes
the
translation
work
as
well
so
like
how
we
think
about
making
the
metrics
available
for
translation,
and
so
that
that
would
be
that
so
like
with
this,
would
come
and
be
a
place
where
we
would
talk
about
any
updates
or
any
changes
to
the
process.
B
So
that's
the
first
one
consistent
project.
Oh
so
this
one
is,
I
we
I
came
to
learn
about
the
dot
github
repository.
Do
you
know
this
yeah?
I
I
didn't
know
about
this,
and
so
it's
a
way
to
distribute
documents
across
an
organization,
and
so,
for
example,
like
the
contributing.md
file
is
one
that
we
currently.
I
believe
we
currently
place
in
every
different
repository,
but
github
the
dot
github
repo
could
be
a
candidate
for
distributing
that
so,
like
just
kind
of
managing
that
process
by
which
documents
get
distributed
across.
B
B
You
know
just
really
recently,
but
I
think
if
you
hear
the
link,
can
you
share
any
link
for
us
to
get
familiarized
with
it
yeah
actually
don
if
you
scroll
down
just
a
little
bit
yeah,
oh,
what
go?
Throw
up
right
at
the
bottom
of
that
first
page,
so
see
that
where
it
says
example,
oh
yeah,
there's
an
example
right.
There.
A
Yeah
cause
there's
actually
a
lot
of
stuff
that
you
can
do
in
this
in
this
github
directory.
You
can
this
one
has
issue
templates,
for
example,
which
is
a
good
use
for
it
and
and
we're
yeah
we're
using
it
at
vmware
for
things
like
the
default
code
of
conduct,
contributing
and
readme
files
that
we
want
our
projects
to
use
when
they,
when
we
first
create
the
repository,
so
we
don't
have
to
don't
have
to
chase
people
down
who
forgot
to
add
whatever
document
they
forgot
to
add.
So.
D
E
Question
so
the
code
of
conduct
gets.
You
said
that
it
gets
copied
into
any
new
repos
that
get
created.
I
think
so,
okay,
how?
If
changes
are
made
to
the
code
of
conduct
in
the
dot
github
repo,
do
the
do
the
changes
automatically
get
pulled
to
the
other
repos
or
oh,
no,.
B
C
B
A
Well,
I
think,
that's
different,
because
we
copy
those
templates
every
time
we
create
a
new
metric
right,
so
this
this
would
copy
the
template
for
new
repositories
as
opposed
to
new
metrics.
B
A
Okay,
so
kind
of
eating.
You
know
all
right.
E
E
I
would
like
to
point
out
that
the
currently
the
process
or
the
structure
that
we've
defined
is
to
create
all
of
these
documents,
like
the
code
of
conduct
or
templates
in
the
community
repo
and
then
in
the
other
repos,
the
working
group
repos,
for
example,
we
create
documents
that
just
link
or
point
to
the
documents
within
the
community
repo,
so
that
that
is
the
current
structure.
The
way
we
have
it
outlined
currently.
A
I
think
we
need
to
better
understand
exactly
how
how
changes
are
are
handled
when
you
I
feel
like
we
don't
know
enough
about
the
stock
github
structure,
to
know
whether
or
not
it's
useful
for
us
yet.
E
Yeah,
I
I
agree
it.
It
could
be
useful
for
us,
but
I
don't.
I
don't
necessarily
know
that
it
would
replace
our
current
desired
structure.
A
Yeah,
I
agree,
but
the
but
the
other
thing
that
it
allows
you
to
do
so.
You
see
how
our
our
landing
page,
the
whole
chaos
org,
is
just
kind
of
the
default
landing
page
with,
like
you've,
got
pinned
things
and
you've
got
repositories,
whereas
if
you
go
to
a
repository
you
know
you
get
to
see
like
you
see
like
a
readme,
and
you
know
other
information,
what
we've
done
at
vmware
there's
a
way
to
do
this
and
it's
in
the
github
folder
you
put
a
readme
in
there
and
or
for
the
org.
A
I
forget
exactly
how
it
works,
but
you
you
can
basically
put
a
readme
at
the
top
above
your
pin
depositories,
so
we
can
put
something:
that's
like
new
contributors
go
here
so
and
so
go
here.
This
is
the
website.
We
could
do
something
kind
of
nice
with
it.
So
and
I
I
think
this
is
just
in
the
github
for
the
for
the
org
and
it's
like
the.
I
think
it's
the
readme.
C
Don
can
you
click
the
add
it
in
that
page,
see
where
it
is
taking
it
so
that
we
can
get
a
little
bit
of
idea
on
that
github,
page
or
vmware.
C
A
C
A
C
B
I
don't
know,
but
I
hear
you
but
I
don't
know
the
answer.
A
Okay,
so
I
think
I
think,
that's
probably
so
we
got
sidetracked
from
the
how
we're
gonna
run
the
common
working
group
with
the
github
discussions,
but
I
think
we've
taken
that
as
far
as
we
can
until
matt
comes
back
with
with
a
little
more
information.
A
The
question
I
had
about
you
know
bringing
these
things
into
the
common
working
group.
We
talked
a
little
bit
about
the
metrics
release.
Updates.
How
much
time
do
we
think
that
will
take
in
the
common
working
group?
Is
that
something
that
you
know
like
a
few
minutes
in
every
meeting?
Probably
a
few
more
minutes
when
we're
coming
up
to
a
release?
A
I
guess
what
I'm
asking
is
for
those
of
you
who
are
deeply
involved
in
the
release.
Will
we
have
enough
time
in
this
meeting
to
cover
the
things
that
you
need
to
cover
to
talk
about
the
release.
E
I
s,
I
suppose
when,
when
I
think
about
it,
I
still
I
kind
of
feel
like
the
work
of
the
release
and
the
work
of
mars
project
is
probably
gonna
occur
kind
of
outside
of
common,
so
I
suppose
the
release
the
release
process,
what
we
could,
what
we
could
use
would
be
kind
of
high
level,
I
suppose
high
level
design
decisions
and
high
level
coordination
decisions.
E
So
discussions
of
of
how
we
can
do
that
might
be
helpful.
Okay,.
E
However,
I
don't
have
any
specific
examples
of
that
right
now,
so
I
suppose
it
it
kind
of
comes
back
a
little
bit
to
maybe
what
I
had
mentioned
in
slack,
where
maybe
we
just
have
updates.
E
We
do
an
update
for
the
the
release
project
group
for
each
chaos
common
meeting
and
then,
if
there
is,
if
there
are
kind
of
design
decisions
around
that
process,
we
could
we
could
discuss
them
during
the
updates.
I
suppose
that's
kind
of
how
I
see
it.
I
don't.
I
don't
know
that
it
would
be
helpful
to
have
the
common
working
group
try
to
work
through
some
of
the
tasks
of
the
release
during
the
meeting.
A
Yep,
okay,
that
makes
total
sense
so
we'll
we'll
say
for
in
the
working
group
we'll
save
kind
of
the
high
level
design
decisions
any
like
big
rocks
that
you
want
to
just
like
talk
about
and
then
updates
to
the
re
release
process.
Every
every
meeting.
Just
a
quick,
quick
update
on
how
things
are
going.
E
So
mars
is
part
of
the
basically
the
release
working
group,
but
at
a
at
a
at
a
high
level.
They're,
not
two
things.
It's
just
I
would
say
the
release
working
group
is
is
how
we
would
want
to
think
about
this,
and
mars
is
part
of
that
group.
E
A
E
It's
not
really
it's
not
really
a
working
group.
It's
it's
more!
It's
just
we're
the
we're
the
four
individuals
who
have
managed
the
release
in
the
past.
So,
okay,
there
is
no
formal,
there's,
no
formal
working
group.
We
don't
have.
We
don't
really
have
a
repo
for
that.
We
don't
have
regular
meetings.
E
Okay,
so
it
would
make
sense
to
use
common
as
a
place
where
we
can
come
together
to
coordinate
those
high-level
design
decisions
about
the
process
in
the
past.
What
we
we
usually
take
those
to
the
community
meeting.
E
D
B
A
Okay,
cool
and
we
talked
about
consistent
project
document
distribution,
so
I
just
put
a
note
to
look
down
below,
because
we've
also
got
that
down
there
yeah
sophia.
Do
you
want
to
talk
about
how
you
see
the
like
the
work
that
you've
been
doing
on
the
data
use
awareness
statement
rolling
into
this.
F
So
I
don't
know,
I
think
we've
been
kind
of
tossing
it
around
because
we're
not
it
doesn't
really
have
a
good
place
or
a
good
home
for
it
like
we
initially
started
this
work
at
the
weekly
meeting
level,
given
that
it's
so
far
reaching,
but
I
think,
given
that
to
get
this
moving
and
out
the
door,
it
does
need
a
bit
more
of
a
focused
effort.
F
So
I
do
think
that
a
smaller
group
working
on
it-
and
I
know
lucas-
and
I
have
had
a
couple
conversations
in
slack
and
others
have
come
in
out
of
the
dock.
It
could
happen
here.
I
just
also
want
to
be
sensitive
of
your
own
agenda
and
what
you
typically
do
in
this
working
group
and
realizing
that
this
is
yet
a
distinct
other
thing.
F
I
think
it
meets
the
common
objective
by
impacting
the
entire
project
from
that
perspective,
but
it's
also
not
a
small
undertaking
and
the
people
that
are
showing
up
here
showed
up
for
the
common
working
group
and
not
necessarily
to
work
on
this
project,
so
if
it
ends
up
being
sort
of
like
a
special
side
team,
that's
I'm
also
fine
with
that.
I
think
for
me
personally,
I
I
have
a
pretty
tight
schedule,
so
I
can't
add
too
many
more
meetings
to
my
own
schedule.
So
I
don't
know
this
is
a
good
place
for
it.
F
I'm
also
just
kind
of
curious
to
hear
what
kind
of
things
were
covered
in
this
meeting
and
whether
or
not
at
face
value.
I
thought
it
was
appropriate
to
bring
it
into
the
space
and
then
let
the
people
that
are
already
in
the
space
opt
in
or
out
of
it
and
then,
if
people
want
to
be
a
part
of
it,
then
we
can
bring
it
in.
If
you
don't
feel
like
it's
part
of
the
mandate
that
you
expected
in
the
common
working
group,
then
I
think
we
should
take
it
out.
A
Yeah
I
mean
I
I
I
think
it
depends
a
little
bit
on
on
your
workflow
as
well.
We
could
certainly
try
it
here
and
see
see
if
it
works.
I
mean
the
so
the
way
these
meetings
are
normally
run
and
answer
to
that
question
is
we
usually,
we
usually
start
by
reviewing
the
pr's
and
open
issues
and
sometimes
the
metrics
tracking
spreadsheet,
and
then
we
pick
one
or
two
metrics
to
work
on.
So
what
we
could
do
is
if
you
want
feedback
on
some
of
the
data
use
awareness
stuff.
A
If
you've
made
some
progress
on
it
since
the
last
meeting,
we
could
pick
that
as
one
of
the
things
that
we
focus
on
in
a
particular
meeting
and
I'm
just
using
that
as
an
example.
Obviously,
some
of
the
other
stuff
that
lucas
pinned
in
the
slack
channel
we
could.
We
could
do
that
with
it
as
well,
and
so
we
could.
We
could
just
sort
of
pick
it
as
one
of
the
things
to
focus
on
or
if
you
had
specific
things
that
you
wanted
to
talk
about
related
to
any
of
these
documents.
A
A
Yeah
because
we
kind
of
we
created
the
common
working
group,
we
sort
of
called
it
the
island
of
misstep
metrics,
because
it
was
it
was
the
metrics
that
kind
of
cut
across
multiple
things
that
cut
across
multiple
working
groups,
and
so
I
do
see
things
like
the
data
use
awareness
statement
cutting
across
the
whole
project.
So
so
this
was
sort
of
designed
to
handle
the
the
metrics
and
things
like
that
that
that
cut
across.
F
Okay,
lucas,
do
you
have
anything
you
want
to
add.
F
I
will
say
it
does
seem
like
from
your
agenda
that
the
first
half
is
all
process
and
ops
versus
metrics.
So
that's
also,
I
feel,
like
part
of
the
consideration.
If
we
keep
bringing
in
non-metrics
related
work,
then
eventually
the
common
metrics
working
group
becomes
just
the
common
ops
working
group.
A
Yeah
well
to
be
fair,
like
the
operations
piece
of
the
the
meeting
is
usually
relatively
quick.
D
I
have
re-dialed
in
thank
you
for
making
all
the
space
for
me
and
I
apologize
for
being
disorganized
this
first
time,
I'm
joining.
I
think
that
I
really
appreciate
the
wisdom
of
sophia's
points
and
the
important
thing
to
me
is
making
sure
that
you
know
number
one.
The
privacy
stuff
doesn't
overload
the
other
agenda
items
for
the
common
working
group
and
then
number
two
that
the
inverse
or
the
reverse,
that
common
doesn't
make
it
harder
to
complete
the
work
of
the
privacy
of
the
privacy
goals.
B
I
have
a
couple
comments.
I
I
I
think
it
fits
here.
I
think
this
list
that
don
has
up
with
like
metrics
release,
updates
document,
distribution
and
data
awareness
statement
like
we're,
seeing
all
the
possible
things
at
once.
I
don't
think
we
would
necessarily
talk
about
all
of
these
in
one
meeting
every
time.
B
So
I
think
if
we
could
spend
part
of
the
meeting
on
one
of
these
things-
or
you
know
part
partly
two-
that's
I
think
that
would
fit,
and
then
the
thing
that
I
think
common
provides
that
the
weekly
working
group
doesn't
provide
the
weekly
call.
Is
we
don't
really
do
work
in
the
weekly
call?
It's.
We
have
a
lot
of
people
there
and
we
have
a
lot
of
newcomers
as
well,
and
it's.
D
B
About
just
kind
of
updates
and
kind
of
talking
about
the
direction
of
the
caps
project
as
a
whole,
and
so
I
think
these
working
groups
we
do
spend
time
where
we
we
stop
the
recording.
We
just
go
work
on
a
document
for
a
little
while
and
that
could
prove
really
beneficial
if
we
had
11
people
on
this
call
right
now.
If
we
just
stopped
right
now
and
took
a
look
at
the
data
use
awareness
statement,
it
would
probably
make
pretty
good
progress
pretty
fast
or
at
least
get
a
lot
of
comments
really
fast.
F
I
guess
the
last
question
I
would
have
around
that
is
just
it
seems
like
this
group
is
pretty
good
about
putting
in
the
agenda
ahead
of
the
meeting.
This
is
just
a
tricky
time
slot.
For
me,
I
will
always
reliably
have
it
free.
F
So
if
I
can
be
more
proactive
with
looking
at
the
agenda
and
seeing
what's
on
the
docket,
then
I
might
be
more
of
a
temper,
I
would
say
temporary
intermittent
itinerant
somewhere
in
there
we're
not
not
permanently
here,
but
I
will
make
an
effort
to
be
here
when
relevant
topics
are
in.
I
hope
that's,
okay,
I'll
rely
on
this
document
as
a
way
to
check
in
on
the
agenda
just
because
thursday's.
I
don't
know
why,
but
it's
like
super
popular
meeting
day.
A
D
So
to
step
away
from
that
kind
of
scheduling
and
organizational
issues,
I
always
want
to
put
some
actual
kind
of
working
items
on
the
table
and
mention
that
we're
collecting
a
list
of
relevant
regulations-
and
that
was
posted
in
slack
and
right
now
that
covers
gdpr
and
us
and
california,
and
so
on,
and
it
would
be
great
to
also
have
china,
latin
america.
D
F
Lucas,
I
know
I'd
seen
it
in
slack,
given
that
this
doc
linkedin
this
agenda
seems
to
be
our
central
place.
Do
you
want
to
add
that
link
into
that
doc,
so
it's
discoverable
all
in
the
same
place.
I
just.
B
D
I
think
that
something
we
haven't
talked
about
that
is
relevant
is
that
there
may
be
items
that
are
like
facets
of
privacy
that
are
specifically
relevant
to
the
metric.
F
Yeah,
because
I'm
wondering
then
matt,
I
feel
like
the
immediate
connection
for
me-
is
anything
in
the
dei
metric
gland,
where
you
are
collecting
more
sensitive
levels,
so
something
that
we
were
talking
about
in
slack
lucas
and
I
were
talking
about
sort
of
whether
or
not
we
want
to
provide
more
prescriptive
guidance
on
levels
of
pii.
F
Nist
gives
you
a
framework
for
doing
it,
and
so
we
can
either
like.
I
was
trying
to
borrow
as
much
as
what
has
already
been
established
in
government
bodies
likeness,
but
something
where
most
of
the
pii
that's
in.
These
metrics
is
pretty
low
level,
because
this
is
pub
like
information
that
you
volunteered
publicly.
But
once
you
start
getting
into
survey
collection,
then
you
are
collecting
things
that
aren't
necessarily
public
as
well
as
more
sensitive
in
terms
of
people
relating
their
individual
characteristics
and
affiliations.
F
So
for
that
there
might
be
like
what
had
kind
of
envisioned
is
we
have
our
general
statement
and
then
for
metrics
like
that
that
could
have
sort
of
an
extra
flag
saying
that
we've
identified
that
data
involved
in
these
sorts
of
metrics
tends
to
be
at
a
higher
level
of
risk,
because
it
includes
more
sensitive
information
about
people
or
something
like
that.
F
So
we
could
try
to
kind
of
come
up
with
a
couple
of
can
statements
that
are
just
so
you
don't
have
to
reinvent
the
wheel
every
time
just
to
kind
of
like,
in
addition
to
the
general
statement,
have
a
flag
that
explicitly
calls
out.
This
is
an
area
where
you
might
get
into
more
trouble.
F
And
I'm
just
smiling
because
I
feel
like
this
even
like.
In
the
past,
we've
been
seeing
some
pretty
interesting
rulings
in
europe
around
what.
F
Yes,
information
like
especially
like
ip
addresses
and
pulling
in
fonts
from
a
us-based
server.
I
don't
know
if
you
saw
that
one
but
like
it's
getting
pretty
wily.
F
B
A
A
I'm
just
gonna
scroll
all
the
way
down,
but
that
looks
pretty
good.
Okay.
Are
there
any
any
concerns
about
this
pr?
I
think
it's
pretty
straightforward.
A
The
only
new
one
we
have
from
the
last
time
we
talked
is
the
organizational
diversity
metric
review,
which
is
what
bernard
created.
Let's
just
have
a
quick
look
at
that
one.
We
have
google
doc
now.
Thank
you
and
looks
like
you've
copied
the
the
template
in
so
we've
got
a
nice
checklist
as
we
go
through
the
review
of
this
metric
and
revisit
it
and
make
any
changes
we
need
to
make.
A
Let
me
just
go
back
to
the
agenda,
so
we
had
so.
I
think
the
review
the
prs
and
open
issues.
I
think
that
looks
good
unless
there's
anything
anybody
else
wants
to
talk
about.
A
B
B
A
A
We
could
talk
about
occasional,
inconsistent
contributors.
We
could
talk
about
organizational
diversity
or
matt.
Did
we
talk
all
the
way
through
this
issues
in
the
working
group.
B
A
B
Yeah,
I
think
we
can
probably
take
a
look
at
it.
Okay,.
A
You
can
drive
that
discussion
and
then
vinod.
How
do
we
talk
about
episodic,
contributor
or
sorry
organizational
diversity
next
time.
B
E
Yes,
yeah
that
that
new
template
has
been
has
been
published,
so
I
believe
synonyms
goes
right
below
question.
Yeah.
E
So
synonyms
colon
and
then
the
synonyms
are
comma
delineated.
B
E
B
E
And
I
know
there
there's
a
ton
of
conversation
like
a
lot
of
conversation
about
what
the
name
of
this
metric
is
so
so
we
should
have
some
pretty
good
ideas
about
other.
E
B
Okay-
okay,
so
really
I
mean
at
this
point
it's
about
kind
of
giving
it
one
last
look
from
this
group,
because
then
the
next
step
would
be,
to
obviously
add
the
synonyms.
B
We
also
kind
of
remember
we
had
the
dev
stats
visual
in
here
and
it
was
impossible
to
read
so
that's
gone.
I
thought
it
was
just
easier
to
just
get
rid
of
it,
because
these
metrics
are
just,
as
you
know,
to
kind
of
help,
locate
people
into
what
the
metric
is
about,
and
we
don't
it
just
ended
up,
creating
confusion.
So
I'll
add
links.
B
E
That
is
me
quick
question,
so
the
name
that
most
people
use
for
this
one
is
probably
not
a
name
that
is
good
for
inclusive
naming
conventions.
B
We
could
include
it
and
say,
but
this
is
a
bad
term,
maybe
drive
by
put
it
at
the
end
too,.
E
A
C
A
B
All
right,
so
I
honestly
there's
that's
really
kind
of
the
update
don
like,
I
think,
we're
kind
of
good
on
this.
I
think
it's
ready
to
move
into
the
pr
phase
and
okay,
if
you
like,
adding
yourself
as
a
contributor,
please
do
so
down
here
at
the
bottom
and
I
just
like
I
said
I
have
just
a
few
few
little
to
do's
here.
A
All
right:
well,
it's
since
we
are
almost
out
of
time.
Is
there
anything
else
we
want
to
try
to
cover
in
our
last?
I
forget:
do
we
end
it
a
quarter
till
or
can
tell.
F
F
For
something
like
this
kind
of
metric,
there's
always
the
sort
of
the.
What
does
it
mean
in
the
long
run
of
the
project
where
it's
like?
Are
people
coming
in
and
out
or
are
they
converting
to
more
rep
like
to
provide
more
contribution
and
increase
their
contribution
levels
to
the
project
and
kind
of
looking
at
indicators
of
what
leads
someone
to
stay
engaged
say
minimally
engaged
or
engagement,
where
this
is
an
area?
F
Maybe
this
is
more
metrics
model
but,
like
in
my
head,
there's
a
very
strong
connection
between
a
metric
like
this
and
also
looking
at
your
general
engagement
levels
in
the
project
and
sort
of
other
participation,
metrics
that
this
could
follow
on
or
as
an
extension
of,
and
I
was
just
wondering
with
a
metric
like
this.
B
So
that
does
the
way
you
were
talking
about
it
sophia.
It
does
sound
like
a
metrics
model
like
how
we
think
about
a
community
contributor
attraction
and
retention,
or
something
along
those
lines
to
which
occasional
contributing
would
be
a
consideration
in
that
model.
F
Okay,
the
other
part
of
it
that
we've
been
thinking
about
a
lot.
I
guess
within
our
own
projects,
is
just
how
do
we
increase
the.
F
But
I
think
they're,
sort
of
the
second
level
of
analysis
is
where
it
gets
really
interesting
is
how
do
we,
if
we
look
at
more
programmatic
ways,
to
improve
the
effectiveness
of
occasional
contributors,
but
now
I'm
thinking
more
philosophically
about
applying
this
metric.
So
I
guess
that
means
it's
a
good
metric.
So
thank
you.
E
E
Are
there
are
a
number
of
models
that
this
one
is
going
to
be
relevant
to
a
couple
of
them
that
we
actually
already
have
in?
I
think
this
one
would
be
connected
to
the
the
the
welcoming
model
that
we're
working
on
yeah
path
to
leadership
is
another
one
that
this
one
could
be
used
for,
although
path
to
leadership
is
not
one
that
is
currently
being
advanced.
B
E
Yeah
in
the
evolution
group,
we've
actually
been
giving
some
thought
to
to
metrics
models
as
well,
so
we're
doing
a
little
bit
of
that
at
least
thinking
about
it
in
evolution.
I
don't
know
if
work
will
be
done
there,
but.
C
Yeah,
I
think
this
conversation
has
always
been
going
back
and
forth
whether
the
work
should
be
done
in
the
working
groups
or
to
the
metric
model.
So
sometimes
work
happens
in
the
group
and
moves
to
the
metric
model.
Sometimes
they
do
something
and
pass
it
to
the
working
group
so
so
far,
this
is
what
I
have
observed.