►
From YouTube: CHAOSS Weekly Community Call 10-19-21
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Let's
go
hey
everyone!
Welcome
to
the
october
19th
edition
of
the
community
call
for
chaos.
I'm
elizabeth,
the
community
manager
quickly.
Just
a
reminder.
No
cameras
are
fine,
feel
free
to
chat
in
the
chat
on
the
side
of
the
zoom
call.
If
you
want
to
chat
with
us,
you
don't
want
your
your
voice
or
your
face
on
the
recording
there.
So
totally
totally
fine
and.
B
A
If
you
have
anything,
you
want
to
bring
up
feel
free
to
add
it
to
the
agenda,
which
I
will
post
one
more
time.
Just
in
case
just
add
that
on
there
not
a
big
deal
at
all,
and
I
will
go
ahead
and
share.
A
Okay,
all
right,
so
if
you
have
not
added
your
name,
please
do
so
if
you
feel
like
doing
that,
so
we
do
kind
of
take
a
look
at
that.
So
it'd
be
great.
If
you
want
to
indicate
that
you
were
here
today,
we
had
a
couple
of
items
from
last
week.
These
two
things-
and
I
don't
think
max
c-
is
on
the
call
because
I
believe
he's
at
all
things
open.
I
don't
see
him
on
here
and
I
don't
know
what
this
means.
A
D
That
may
be
a
reference
to
the
the
chaos
swag.
D
C
D
The
the
plan
is
to
the
plan
was
to
create
a
portal
on
the
website,
basically,
an
e-commerce
store
where
we
could
basically
collect
addresses
and
do
all
the
shipping,
but
we're
running
into
a
a
bit
of
a
stopping
point,
because
we
to
collect
money
over
the
internet
we
need
to.
We
need
to
have
some
information
and
chaos
isn't
technically
a
a
entity
that,
from
from
a
government
standpoint,
chaos
isn't
an
entity
that
can
collect
money
in
that
way.
D
So
we,
I
think
we
collect
money
through
the
linux
foundation,
so
we're
waiting
for,
I
think,
word
from
them
on
how
we
can
how
we
can
do
that
so
alternately
I
could
use.
We
could
use
a
member
of
the
organization
as
the
entity
to
collect
money,
but
that
creates
all
sorts
of
other
issues.
So.
D
Oh
yeah,
the
other
there.
Actually
there
are
a
ton
of
e-commerce
platforms
that
just
plug
right
into
wordpress
and
the
the
idea
right
now
is
to
just
use
one
of
them,
but
the
problem
is
collecting
money
online.
It
has
to
it
has
to
go
to
a
bank
account
and
there's
credit
card
processing
and
that
money
collection
is
then
connected
to
that
person's
bank
account
or
the
organization's
bank
account
right.
So
chaos
does
not
have
a
bank
account.
Technically,
chaos
is
not
a.
D
We
don't
have
a
like
a
business
id
we're,
not
officially
a
non-profit,
we're
we're
part
of
the
linux
foundation.
So
if
we
were
to
collect
if
we
were
to
take
money
even
if
we're
not
not
for
profit,
even
if
we're
just
taking
it
so
that
we
can
do
shipping,
we
have
to
have
that
kind
of
organization.
You
know
it
has
to
be
connected
to
a
person
in
in
all
of
those
e-commerce
platforms.
D
E
D
I'll
take
a
peek,
I'm
open
to.
You
know
we're
open
to
many
different
many
different
avenues
here,
so
even
even
not
using
even
not
using
one
of
these
ecommerce
platforms.
If
it's
it's
easier
to
not
use
one
of
these
e-commerce
platforms,
then
we
can
certainly
do
that.
Yeah,
the
shipping,
the
shipping
application
that
comes
with
these
e-commerce
platforms
is,
is
really
what
we
want
to
take
advantage
of.
D
D
Even
if
we
create
we've
talked
about
just
creating
like
coupon
codes,
so
that
people
don't
have
to
pay
for
it
right,
you
still
have
to
it
still
cost
money
to
ship
things,
and
we
still
have
to
account
for
that
in
the
process.
So
so
using
using
an
e-commerce
platform,
just
out
of
the
box
is
gonna
require.
D
It
requires
some
information
that
we
don't
necessarily
have
right
now,
so
so
from
that
standpoint,
we're
waiting
on
the
linux
foundation
for
some
answers,
and
then,
alternatively,
if
anyone
has
a
better
way
of
doing
it,
certainly
open
to
open
to
listening
to.
C
You
well,
I
think,
open
collective
is
designed
to
address
this
problem,
in
particular
that
cooking
course,
projects
are
not
businesses
and
being
a
business.
It's
you
know
something.
That's
capable
of
accepting
and
spending
money
is
the
wrong
way
for
open
source
projects
to
invest
their
time.
D
So,
just
to
reiterate
that
I
guess
so,
the
the
collecting
money
isn't
the
issue,
it's
the
it's
the
credit
card
processing
that
may
be
required
or
the
and
the
the
shipping,
the
shipping
information.
D
So
I
know
one
of
the
things
that
matt
was
looking
at
is,
if,
rather
than
rather
than
connecting
to
a
bank
account
if
we
could
connect
the
e-commerce
platform
to
open
collective.
So
I
know
he
is
looking
at
that.
D
Yeah,
that's
completely
fine,
I'm
we're
we're
not
exactly
sure
what
the
best
way
to
do
it
right
now
is
so
so
any
input
that
you
have
is
is
is
great,
and
I'm
not,
I
don't
know,
has,
has
anyone
heard
of
anyone
else
doing
this.
F
D
Very
specifically
we're
talking
about.
We
want
to
create
a
online
portal
that
would
allow
our
contributors
to
put
in
their
information
so
that
we
can
send
them
swag.
E
I
mean
a
couple
of
lf
projects,
they
did
this,
but
I
don't
think
they
actually
collected
payment.
They
would
give
like
coupon
codes.
Like
you
said,
kevin.
Let's
say
there
are.
I
mean
contributors
that
you
want
to
send
swags
to
and
then
in
lieu
of
credit
card
information
you
enter
this
code,
then
the
the
price
will
basically
zero
out
so
yeah.
There
are
a
few
few
projects
in
lf.
Did
that?
Let
me
the
lf
networking
project
did
it
because
I
I
got
a
free
hoodie,
there's
a
recognition.
E
D
Okay,
yeah.
That
sounds
exactly
like
like
what
we
want
to
do
right
so
yeah.
Our
goal
is
not
to
collect
money.
We
would
prefer
to
just.
We
would
prefer
to
to
do
the
cucum
coupon
code
to
zero.
It
out
right
right.
E
Yeah
I
mean
they
did
something
like
funny.
They
would
like
a
list,
a
hoodie,
a
thousand
dollars,
so
nobody
would
pay
for
it
and
then,
but
you
know,
like
the
people,
you
want
to
recognize
there
get
a
coupon
code,
so
you
get
minus
thousand
and
then
you
get
a
hoodie.
D
Yeah,
that's
that's
so
when
we
started
going
through
the
logistics
of
how
we
would
do
that,
that's
actually
that's
exactly
how
we
talk
about
it
and
since
we
put
a
crazy
price
on
the
item
and
then
we
just
give
them
a
coupon
code,
all
right.
D
E
A
Awesome
thanks
you
guys,
okay,
so
let's
move
on
the
next
item
from
last
week
was
to
talk
about
the
brand
kit,
and
I
know
this
is
something
that
nicole
really
wanted
to
to
talk
about
and
george
as
well.
So,
but
I
don't
see
either
one
of
them.
I
think
george
ato
and
I
don't
see
nicole
in
the
call
either,
so
we
might
defer
that
until
she
comes
back
because
I
know
that's
something
she
wants
to
talk
about.
A
Right
and
then
the
next
one
is
our
wonderful
metrics
release,
so
hooray,
hooray
to
everyone
who
took
part
in
that
all
the
people
who
worked
on
this,
like
that's,
it's
so
much
work
to
put
this
together
and
if
you
have
not
seen
this
pdf,
oh
my
gosh,
you
have
to
go
well
here,
we'll
just
do
it
right
now
gigantic
it
is
so
beautiful,
like
it
makes
my
heart
happy
to
look
at
it
like
look
at
this.
A
So
good
so
big,
huge
huge
thank
you
to
ritik
and
josh
and
kevin
and
georg,
who
made
this
happen,
and
it
is
absolutely
amazing,
like
I
just
love
it,
I
just
want
to
keep
looking
at
it
all
day
long.
So
so,
if
nothing
gets
done,
that's
because
I'm
just
staring
at
this
wonderful
pdf
that
we
have
now.
So.
Thank
you
guys
and
also
with
this
latest
release.
We
had
16
new,
slash,
revised
metrics
and
six
new
and
revised
focus
groups
in
our
focus
areas
in
our
working
groups.
A
So
that
brings
our
metrics
to
70..
We
have
70
metrics
now
of
different
ways.
People
can
measure
their
community
health.
So
it's
really
good
that
we're
also
thinking
about
metrics
models
like
lucas
up
here,
because
that's
a
lot,
that's
a
it's
a
for
people
to
digest
and
to
figure
out
so
hopefully
those
metrics
models
will
help
people
make
sense
of
how
to
package
these
metrics
together
in
meaningful
and
impactful
ways.
A
D
We
are
tentatively,
we
have
we've
given
it
about
a
week
to
release
the
chinese
translation
of
these
metrics.
However,
the
translation
team
just
informed
me
that
they
are
they're
good,
so
I
have
a.
I
have
already
created
the
pdf
for
the
chinese
translation
and
I
sent
it
to
them
for
approval.
D
C
Kevin
I'm
going
to
be
working
on
the
the
metrics
model,
shared
document
that
we
were
looking
at
last
week
today
and
just
so
just
a
heads
up
that
I'm
going
to
do
that
and
it's
kind
of
sprawling.
So
I'm
going
to
try
to
do
something.
Much
smaller
sounds
good
I'll
I'll,
take
a
peek
as
well,
but
I'll.
Let
you
take
the
lead.
C
C
Indeed,
one
thing
I
wanted
to
just
put
out
there
kind
of
socially,
and
that
is
that
I
think
the
privacy
conversation
is
still
kind
of
lurking,
and
I
just
want
to
put
it
on
people's
attention
and
I
think
the
task
there
is
to
think
about
pii
in
metrics
and
and
come
up
with
a
kind
of
come
up
with
consensus
on
what
to
do.
B
Before
the
summit,
so
it's
been
a
while-
and
I
know
garrick
is
leading
some
of
that.
So
I
didn't
know
if
we
want
to
keep
those
conversations
in
the
weekly
meeting
or
if
we
wanted
to
officially
spin
out
a
working
group
by
the
way
we
did
think
that
maybe
because
it
touched
on
all
metrics
that
should
be
kept
within
this,
but
I
like
to
make
time
for
it.
I
suppose.
B
That
we
had
been
working
on,
we
have
a
privacy
document.
I
think
this.
What
lucas
was
referring
to
is
guidance
around
how
to
enumerate
suggestions
around
how
to
deal
with
pii
and
privacy
and
metrics.
Okay,
knowing
some
data
required
to
generate
the
metric
is
going
to
be
more
or
less
sensitive,
agreed.
A
Okay,
so
what
do
we
want
to
do
for
our
action
item
because
I
feel
like
we
can
talk
about
this
all
day
but
like
we
need
to
you
know
kind
of
move
it
forward.
So
do
we
want
to
like
just
start
a
doc
again
and
have
like
some
some
verbage
that
we
collaborate
on
to
someone
lucas?
Maybe
you
want
to
take
the
initiative
and
draft
something
that
we
can
look
at
and
approve
or
or
comment
on.
C
C
Yeah
right,
like
I
think
you
to
sofia's
point,
I
wonder
about
what
group
that
will
belong
in
or
like.
Where
should
I
do
that
and.
B
C
Just
say,
I
think
what
needs
to
be
done
is
form
a
definite
policy
which
is
going
to
be
like
three
lines,
which
is
probably
going
to
be
examine.
Whether
there
is
any
pii
revealed
in
the
likely
course
of
your
metric
and
flag
it
in
the
document
and
then
there's
part
one
and
then
part
two
is
to
actually
review
old
metrics.
Maybe
it
could
be
a
lot
of
work,
but
so
where
would
that
be
natural
home
for
that
work?
D
Maybe
the
maybe
the
community,
the
community
work
group
right,
the.
B
Yeah,
I
know
there
had
been
an
argument
for
keeping
it
in
the
community
call.
I
think
the
challenge,
though,
is
that
we
may
have
other
agenda
items
that
we
need
to
address
keeps
getting
kicked
down
the
road
a
bit.
So
I
think,
if
it's
a
bit
more
scheduled,
maybe
like
every
other
community
call,
we
could
dedicate
time
to
it
similar
to
a
working
group.
That's
never
a
week.
B
It's
every
other
week,
but
they'd
be
every
other
community
meeting
and
said
we
dedicate
a
certain
amount
of
time
to
moving
this
forward
until
we've
moved
it
forward.
B
A
Okay,
so
let's
do
this,
let's
open,
I
can
open
an
issue
in
the
community
repo,
that's
kind
of
like
a
placeholder.
That's
a
reminder
that
so
it
doesn't
get
lost
in
the
shuffle
of
everything
else.
A
A
C
I
was
imagining
kind
of
three
things:
first
of
all,
a
policy
somewhere
like
guidance
for
metrics
groups
and,
secondly,
maybe
review
of
earlier
metrics
of
existing
metrics
and
then.
Thirdly,
maybe
a
checklist
item
in
the
checklist,
so
guidance
guidance
on
what,
like
a
suggestion
to
metrics
teams
about
how
they
should
think
about
privacy.
C
C
It's
like
do
your
metrics
likely
touch
on
the
publication
of
personally
identifiable
information.
A
A
A
All
right,
okay,
we
only
have
two
more
items
on
the
agenda,
so
I
guess
if
we
do
have
time,
we
could
maybe
even
start
that,
but
anyway,
just
a
reminder.
No
dei
badging
tomorrow,
because
of
ato
matt
c
is
out.
Obviously,
so
if
you
were
planning
on
attending,
don't
do
that
you'll,
be
by
yourself,
the
second
or
the
last
one
is
the
kscon
feedback,
and
that
was
added
by
sophia.
B
Yeah,
mostly
just
saying
so,
we
had
put
out
a
survey.
We've
had
nine
respondents
so
far,
most
of
them
are
from
the
in
person,
but
if
we
can
plug
it
again,
it
says
if
we
want
to-
or
we
can.
I
was
thinking
we
could
wondering
where
and
how
we
want
to
share
that
information
back.
So
I'm
assuming
we
want
to
share
it
with
the
chaos
committee
planning
group,
but
it's
also,
I
can
make
it
into
a
format
where
we
feel
comfortable,
sharing
it
with
the
entire
community.
B
B
So
I
just
wanted
to
basically
float
it
as
when,
when
should
we
schedule
that
it
doesn't
have
to
be
now,
given
that
I
take
we're
pretty
low
attendance
feeding,
so
I
probably
want
to
bump
it
to
next
week
when
we
have
more
books
like
than
join
the
conversation,
but
that
makes
sense
I'll
put
I'll
put
in
the
link
again.
If
there's
anyone
else
hasn't
pulled
out.
The
form
I
feel
like
it's
probably
because
how
tiny
our
meeting
is
today,
but
just
I
was
putting
it
out
there
to
say,
can
I
can.
A
All
right:
well,
that's
the
end
of
the
agenda,
so
we
have
about
20
minutes
left.
We
can
do
one
of
two
things
we
can
end
the
meeting
or
we
can
work
on
the
privacy
statement
that
lucas
has
brought
up.
So
what
would
the
group
like
to
do.
D
A
I
don't
know
what
you
would
call
it
guidance.
F
F
D
B
Everyone,
because
it
depends
on
the
company-
I
mean
I
work
for
master
organizations
where
we
do
have
various
layers
and
levels
of
information
protection
where
clearly,
there's
more
information,
that's
more
sensitive,
say
we're
a
custom
like
customer
behavior
versus
employee
data
and
those
things
are
treated
differently.
But
if
you're
collecting
something
like
open
source
contribution
data,
it
can
be
a
little
bit
of
both
and
then
also
depending
on
how
much
additional
information
you
bring
into
your
data
set.
B
If
you
are
working
internally
today,
we
like
to
use
alongside
what
we
know
about
our
employees
to
better
understand
who,
in
the
company
is
doing
what
and
what
their
roles
are.
So
do
we
know.
Do
we
have
the
right
tool
in
here
to
write
documentation,
which
means
that
we've
just
added
more
sensitivity
to
the
data
set?
It's
not
just
public
data
anymore.
B
We've
now
married
it
with
private
data,
and
so
essentially,
the
recommendation
that
I
have
is
developing
your
own
custom-built
classification
system,
for
how
you
want
to
treat
this
information
and
what
parts
of
it
are
more
or
less
enough
to
do
with
the
general
recognition
that
things
that
include
pii
and
the
parts
that
include
pii
are
treated
on
a
more
sensitive
end,
but
you
can
keep
adding
to
that.
B
You
can
always
make
it
more
sensitive,
and
so
I
know
we
had
talked
about
originally
if
we
want
to
share,
say
something
like
data
from
the
chaos
project
as
part
of
a
research
asset
that
by
we
would
reduce
our
own
liability
by
removing
pii
making
an
anonymizer
at
default.
So
I
don't
know,
I
guess
I'm
rambling
a
bit,
but
the
guidance
that
I
have
for
something
like
this.
What
we're
trying
to
do
general
purpose
statement
is
to
flag
within
a
metric.
What
data
do
you
need
to
actually
create
the
metric
and
then
flagging?
B
What
pieces
of
information
can
make
your
sensitivity
level
of
your
data
set
increase?
So
if
it's
just
a
name
and
an
email,
that's
one
level.
If
it's
a
name
and
an
email
and
an
affiliation
and
a
demographic,
that's
sort
of
level
two,
if
we're
starting
to
keep
adding
more
personal
information,
and
the
thing
is
like
within
a
company,
each
company
defines
their
own
risk
levels.
What
levels
should
be
applied
to
various
types
of
information
so,
depending
on
the
collecting
entity,
whether
or
not
it's
a
project
or
a
company?
B
It's
kind
of
it's
up
to
them,
how
they
want
to
define
those
parameters.
It's
more
just
in
terms
of
how
we
can
support
that
as
the
metrics
describer
is
to
flag.
These
are
all
the
things
that
potentially
could
fit
into
sensitive
information,
buckets
and
just
kind
of
flag
it,
and
then
I
get
some
sort
of
tag
with.
We
recommend,
if
you
are
collecting
this,
that
you
have
some
sort
of
privacy
documentation
that
you
have
some
sort
of
data
classification
and
protection
system
put
in
place
because
now
you're
collecting
more
than
just
public
information.
D
So
I
I
do
worry.
I
worry
about
the
scoping
of
this
work
and
I,
if
we
can,
I
think
we
should
avoid,
including
the
bulk
of
this
work
in
the
metrics
documents
themselves.
D
I
think
we
would
be
better
off
providing
guidance
outside
of
the
metrics
documents
and
perhaps
providing
some
way
to
link
from
the
document
to
this
guidance
right.
So,
if
there's,
if
there's
a
specific
class
of
metric,
that
is
basically
a
flag
for
this
document
or
the
for
this,
this
general
guidance,
maybe
we
can
maybe
create
a
way
to
flag
it
within
the
metrics
document
and
point
people
to
that.
D
B
I
I'm
inclined
to
agree
with
you
kevin.
I
think
that
that's
kind
of
what
I
was
envisioning
as
well,
so
the
only
thing
that
would
be
included
in
the
metric
is
just
some
kind
of
flag
that
says:
hey,
there's,
potentially
sensitive
information,
that's
going
to
be
collected
as
part
of
the
session.
We
recommend
that
you
go
to
x,
page
x,
document
for
more
for
more
suggestions
on
how
to
treat
this
or
how
to
deal
with
this
or
something
like
that.
C
Think
that
this
is
a
nice
way
of
it's
kind
of
a
parsimonious
way
of
approaching
the
task,
although
I
I
think
that
it
makes
a
question
of
metrics
specific
flags.
C
So
the
way
I
envision
this
playing
out
is
that
in
each
metric
there's
a
link
to
the
general
privacy
guidance
and
and
there's
also
specifics
about
known
privacy
issues
within
the
metric.
So,
for
example,
in
the
attribution
metric
there
probably
would
need
to
be.
I
guess
I
would
just
ask
for
little
thoughts
on
that.
Like
would
the
discussion
of
privacy
issues
specific
to
attribution,
be
in
the
attribution
metric
or
would
it
be
in
the
generic
document
that
is
linked
from
all
the
all
directions.
D
Are
the
so?
Are
we
going
to
start
seeing
so
in
contribution
attribution
the
specific
privacy
issue
is
that
you're
collecting
personal
information
about
about
your
contributors,
right,
yeah
and
publishing
and
publishing
it.
So
I
think
that
that
particular
that
particular
issue
would
be.
I
don't
think
I
don't
think
we
would
need
to
duplicate
that
particular
issue
in
every
document
where
we're
collecting
personal
information
right.
D
C
So
would
there
be
a
definite
determination,
for
example,
in
the
attribution
metric
that
says
this
metric
definitely
includes
stuff
that
you
know
suggests
you
need
to
think
about
privacy
and
here's
where
to
go
to
get
that
information.
Where
is
it
I
mean
like?
Is
there
a
link
in
every
single
metric
that
says
here's
where
to
go
to
think
about
privacy?
Was
there
a
specific
link
in
metrics,
where
it's
known
that
there
are
privacy
issues.
A
Personally,
I
feel
like
when
we
know
we
should
we
should
identify
that
and
it's
in
a
certain
way.
You
know,
because
I
mean
people,
I
don't
think
people
will
necessarily
go
look
at
that
privacy
statement
if
they're,
if
they
just
like
glance
at
the
metric
and
they're
like
nah.
It's
fine,
I'm
not
gonna,
but
if
they
may
not
realize
like
that,
there's
something
in
there.
So
I
feel
like
it's.
If
we
know
that
there
is,
we
should
say
that
that's
my
feeling.
A
Okay,
so
I
did
start
a
doc
in
case
you
didn't
see
that
in
the
chat
I
just
started
jotting
down
goals
as
we
were
chatting,
so
we
can
just
kind
of
use
that
I'll
put
it
in
the
minutes
as
well
as
a
starting
place.
A
C
I
also
I
I
like
the
idea
of
being
specific
about
sensitivity,
levels
and
risks
in
the
guidance
document.
A
A
D
I
think
we
could
so
I
do
like
it
on
the
checklist,
although
I
think
we
need
to
be
specific
about
what
that
is,
that
that
we
want
the
working
groups
to
consider
so
it'd
be
similar
to
the.
Currently.
We
have
a
there's,
a
there's,
an
item
on
the
checklist
that
asks
the
working
groups
to
consider
possible
use
cases
dei
use
cases
for
each
metric
that
we
can,
that
we
add,
so
that
would
be
in
the
in
the
objective
section
if
it
was
on
the
checklist.
D
This
would
probably
it
would
be
so
ask
the
working
groups
to
consider
what
possible
data
ethics
issues
there
are
with
the
metric
and
I'm
not
sure
if
that
would
be
in
the
would
that
belong
in
the
description
or
would
that
belong
in
the
objectives
section
or
would
it
be
just
like
a
separate
disclaimer
at
the
bottom
of
the
page.
B
I
think
implementation
makes
sense,
but
I
kind
of
like
that
it
would
be
its
own
flag
so
that
we
don't
dictate
exactly
how
you
have
to
write
the
implementation
section,
because
I
seen
a
fair
amount
of
variability
across
metrics
groups.
But
if
it's
just
kind
of
within
the
implementation
section,
it's
either
flagged
or
not
flagged
as
a
potential
potential.
Sensitive
data
collection
like
it
could
just
like
I'm
not
always
envisioning
as
a
check
box,
but
like
something
that
says
like
it's
just
like
a
flag.
D
We
could
have
that,
as
we
could
have
that
as
text
at
the
top
of
the
implementation
section,
we
could
add
it
to
the
metrics
template
and
put
an
optional.
The
optional
header
tag
on
it
there,
so
that
it'll
always
be
on
the
metrics
template.
So
when
they're,
when,
when
the
working
groups
are
creating
the
metric,
they
will
always
have
to
make
the
choice
of
deleting
that
text
or
or
deleting
the
optional
bit
right.
D
And
then
that
text
would
include
a
link
out
to
the
the
the
central
document
that
we're
talking
about
creating.
D
Yeah,
I
think
it
could
exist
in
both
so
the
the
metrics,
the
the
checklist
item,
is
really
kind
of
a
helpful
tool
for
the
reviewer.
D
D
Then
I
think,
as
part
of
the
review
process
that
could
be.
That
can
be
something
that
can
come
up
so.
A
And
lucas
to
your
point
earlier
about
going
back
and
reviewing
the
old
metrics
we've
already
released,
I
know
that
that's
something
that
is
a
goal
for
the
next
metrics
release
anyway,
is
to
just
review
the
old
and
just
see
if
they're
stale,
if
they
need
to
be
rewarded,
and
things
like
that.
So
there's
an
issue
for
that
in
the
community
repo.
We
can
I'll
just
put
a
comment
in
there
that
that's
something
that
we
want
to
also
include
as
we're
going
back
and
auditing.
Some
of
these
old
metrics
is
that
okay.
C
So
I
will
add
to
the
checklist.
This
question:
are
there
ethics
issues,
data
ethics
issues
that
have
not
been
flagged
in
the
metric.
D
C
C
D
C
D
So
I
think
the
I
think
the
operations
group
is
going
to
it's
going
to
start
looking
at
the.
I
think
the
majority
of
their
work
is
going
to
exist
in
the
community
working
group
and-
and
it's
also,
I
think,
they're
also
concerned
with
the
any
of
the
shared
workspaces
that
the
work
that
the
working
groups
use.
D
So,
however,
that
group
is
tentative.
We
have
not
had
any
sort
of
meetings,
yet
I
think
manche
is
going
to
put
that
together
and
if
you're
wanting
to
be
part
of
that
group,
I
think
that's,
I
think,
that's
open
membership.
Yes,
please
please
come.
C
I
will
happily
participate
and
until
the
operations
group
creates
that
document,
which
I
think
I
think
that
creating
that
document
goes
to
the
operations
group.
If
I'm
wrong,
while
do
writing
on
the
specific
guidance
in
the
issue
that
elizabeth
is
slated
to
create.
D
I
don't
I
don't
know
if
I
don't
know
if
creating
the
document
falls
to
the
the
operations
group,
I
think
that
I
think
that
would
fall
to
us
here.
Okay,.
C
Hopefully
I'll
create
a
document
and
flag
it
I'll
I'll
make
it
in
the
community
group.
I
will
flag
it
in
the
issue
and
put
some
kind
of
placeholder
text
in
there.
A
All
right
we're
almost
out
of
time
anything
else.
We
have
two
minutes
left.