►
From YouTube: CHAOSS Weekly Community Call 9-14-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
Hey
everyone:
this
is
your
september
14th
edition
of
the
community
weekly
call
for
chaos.
I'm
elizabeth,
your
chaos
community
manager.
So
it's
great
to
see
everybody
here
again
today
you
have
a
thousand
other
things
going
on,
I'm
sure,
but
you
took
time
out
of
your
day
today
to
show
up.
So
thank
you.
We
appreciate
you.
I
will
drop
the
minutes
in
here.
C
A
All
right-
and
we
were
just
talking
about
chaos
khan,
a
little
bit
and
the
idea
of
that
someday
when
we're
big
enough,
we
will
share
full-size
candy
bars,
like
the
lf
does,
and
beth
hancock
has
just
said
that
we
should
use
that
as
an
icebreaker.
Oh
that's
a
good
idea.
I
like
that
a
lot,
maybe
we'll
have
to
think
about
that.
You
mean
for
the
these
meetings
beth
or
at
chaos.
Con.
D
Oh
well,
since
we're
sharing
candy,
I
thought
probably
some
place
where
we
would
actually
be
in
touch
with
each
other.
It
could
be
like
hey.
This
is
my
reese's
peanut
butter
cup
out
of
the
four
pack.
I'm
gonna
go,
find
three
other
people
and
give
them
a
reese's
peanut
butter
cup
and
get
to
know
them.
A
Okay,
so,
let's
jump
into
now
that
I'm
hungry
we're
going
to
jump
into
the
metrics
freeze
and
review
period,
which
is
currently
happening,
and
we
have
about
a
little
over
two
weeks
left
to
it'll,
be
toward
the
end
of
this
end
of
december
end
of
september.
This
is
september
until
the
freeze
is
over
and
the
metrics
will
be
released.
A
So
if
you
have
not
had
a
chance
yet
to
look
through,
there
are
16
metrics
the
list
is
we
can
provide
that
for
you
if
you
need
it,
but
you
can
also
check
the
weekly
newsletters
because
I
put
them
in
there
every
single
week.
So
go
back
and
look
at
your
weekly
newsletters
and
you
can
see
the
full
list
right
there
or
you
can
also
go
to
chaos,
dot,
community,
slash,
metrics,
and
you
will
see
the
ones
that
are
indicate
indicated
that
says
under
review.
So
please
have
a
look
at
those
offer.
A
Any
comments
or
plus
ones
thumbs
up
whatever
you
want
would
be
great.
We
would
really
appreciate
that,
and
it
makes
the
it
makes
our
metrics
better
when
we
have
more
eyes
on
them,
so
you
have
a
little
bit
over
two
weeks
to
do
that.
I
see
people
are
adding
notes
on
here.
Under
this,
we
want
to
talk
about
the
checklists
next,
the
status
of
those
checklists
and
the
enforcement
policy.
E
I
added
these
ones
here,
I'm
wondering
we
have
these
checklists
that
we're
checking
off
about
each
metric.
I'm
wondering
what
what's
going
to
happen
as
a
result
of
that
like
how
each
working
group
is
doing
and
also
how
are
we
going
to
enforce
this?
If
the
checklist
isn't
completely
checked
off
to
them,
does
the
metric
not
make
it
or
I'm
just
not
sure
how
that
works.
F
It's
the
the
working
group's
responsibility
to
make
sure
that
the
stuff
on
the
checklist
are
checked
off
the
first.
The
first
part
of
the
checklist
is
something
that
we
actually
do
during
the
release,
and
then
there
are.
The
second
part
of
the
checklist
list
is
about
kind
of
quality
and
structure.
F
So,
if
you're
reviewing
metrics
it's
it's
actually
that
the
checklist
is
actually
kind
of
nice
to
take
a
peek
at
the
second
part,
because
it
does
have
some
specific
quality
checks
for
the
for
the
metrics
themselves,
but
but
in
general,
as
far
as
enforcing
the
checklist
policy,
I
think
it's
as,
as
always
it's
up
to
the
it's
kind
of
up
to
the
working
groups,
to
tell
us
when
the
metric
is
ready
for
release
and
if
so,
if
they
tell
us
that
it's
ready
for
release,
then
we
will
take
their
word
for
it
and
assume
that
they've
gone
through
the
quality
checklist.
E
I'll
try
and
capture
that.
A
F
Common
common
renamed,
their
focus
areas.
F
We
actually
removed
a
couple
metrics
as
well,
or
they
two
metrics
of
dei
merged
into
one
metric,
so
yeah
a
lot
of
activity.
A
A
Okay,
should
we
move
on?
Are
we
good.
C
But
I
that
was
me,
it's
just
a
short
thing
just
so
you
know
we're
looking
at.
I
think
the
code
of
conduct
team
has
been
ildico,
gayorg
and
armstrong.
So
thank
you
and
I
think
it's
supposed
to
rotate
every
two
years
and
so
we're
just
kind
of
looking
in
to
the
process
of
how
that
rotation
would
occur.
A
C
Me
so
we,
as
many
of
you
know,
we've
been
working
on
our
own
chaos,
reflection
with
respect
to
dei,
so
how
the
chaos
project
can
can
just
really
work
to
better
center
dei
within
the
work
that
we
do
and
we've
updated
the
metrics
template
to
include
just
any
commentary
of
how
any
metric,
no
matter
what
working
group
it's
in
could
be
understood
in
the
context
of
dei
was
part
of
this
reflection.
C
C
A
All
right
does
anyone
have
questions
about
this
or
comments?
Wanna
talk
about
it
more.
F
Oh,
the
the
quality
checklist.
Actually,
there
is
a
check
box
for
this
particular
item
as
well.
So,
okay,
one
of
one
of
the
when
you're
doing
the
release,
one
of
the
things
that
we're
asking
is
to
reflect
on
dei
within
the
objectives
of
each
metric.
So
yeah
there
is
actually
a
check
list
item
for
that.
That
does
metric
includes
a
reflection
on
dei
cool.
A
All
right,
we
can
go
ahead
and
move
on
if
nobody
has
anything
else.
A
Okay,
making
chaos
data
available.
C
C
Possibly
making
repository
data
available
for
for
academics,
so
the
chaos
project
is
is
really
built
with
folks
from
industry
and
and
folks
from
the
academic
setting.
And
so
one
of
the
big
things
from
an
academic
perspective
is
getting
good.
Reliable
data
with
respect
to
repository
work
right,
and
so
there
was
a
project
called
gh
torrent
was
that
it
sean
yep,
gh
torrent
yep,
but
I
think,
wasn't
didn't
auger
use
that
data
for
a
while.
G
Yeah,
the
very
very
earliest
version
of
auger
used
gh
torrent
data,
and
you
know
we've
since
gone
to
gathering
all
of
our
own,
and
I
think
I
think
I
know
what
you're
going
to
talk
about
next,
so
go
for
it.
Well,
that's
that's
just.
C
There
are
a
lot
of
things
that
go
with
that,
right,
obviously,
with
respect
to
to
data
management
and
privacy
and
how
we,
you
know,
build
a
community
such
that
if
people
want
to
provide
feedback
on
how
to
improve
the
data
collection
like
there
are
a
lot
of
things
that
go
with
this.
So
this
is
a
this
note
is
a
conversation
from
yesterday,
but
I
think
it'd
be
a
real,
potentially
huge
asset
to
to
people
in
academe.
C
H
Good
morning
this
is
lucas,
hi
lucas,
good
morning
lucas.
So
I
happen
to
be
in
a
conversation
with
somebody
at
github
this
weekend
who
works
on
policy
and
privacy
implications,
and
he
told
me
there
have
been.
He
happened
to
mention
that
there
have
been
a
number
of
projects
to
spyder,
github
and
other
public
repos
and
compile
stats
on
individual
developers
and
that
they
ran
a
foul
of
state
level,
privacy
laws.
H
So
what
I
want
to
add
to
this
conversation
about
making
data
available-
which
I
think
is
a
valuable
contribution-
is
to
be
aware
of
the
difficulty
of
having
stats
on
developers
on
particular
developers
across
projects.
G
Yeah,
I
think
I
mean
just
to
address
that
I
mean
you
raise
a
very
important
point,
one
of
the
questions
that
I
have
for
the
community.
As
we
talk
about
doing
this
is,
in
my
opinion,
we
would
remove
all
individually
identifiable
information
or
hash
it
in
some
way,
so
that
the
actual
people
would
not
be
readily
identifiable
in
any
distributed
data
set.
G
However,
I
would
not
suggest
I
would
like
to
not
hash
the
names
of
the
repos
or
the
repo
specific
information,
which
does
mean
that
an
ambitious
soul
could
go
back
and,
I
suppose
reverse
engineer
the
hashes,
but
I
think
it
would
be
nominally
less
work
just
to
go
get
the
data
yourself.
If
that's
what
you
want
to
do,
but
you
know
to
what
extent
will
people
feel
protected
if
we're
hashing
the
names,
but
not
the
projects.
I
I
think
that
approach
is
also
in
line
with
what
others
have
taken
in
terms
of
removing
pii
the
people,
but
not
the
repo.
I
know
that
that's
what
we've
done
with
our
our
public
data
center
on
github
archive
on
bigquery,
there's
no
identifying
information
about
the
people,
but
we
leave
the
repo
and
or
names.
I
Yeah
exactly
so,
that's
that's
what
we
did
that,
that's
not
by
the
lawyers,
I
guess
we're
being
recorded.
So
I
don't
want
to
say
too
much
more,
but
it's
it
got
public
on
its
own
and
there
weren't
any
issues
there.
So
at
least
that's
the
approach
that
we've
taken
and
it
would
be
consistent,
I'm
assuming
others
have
also
taken
similar
approaches,
but
I'm
not
as
well
versed
in
them.
G
Okay,
I
mean,
I
think
I
think
we
should
like
just
like.
I
think
we
should
discuss
this
further
as
a
community,
get
it
adequately
socialized
and
have
our
have
some
sense
of
consensus
before.
I
I'm
also
going
to
say
there
are
different
research
approaches
that
would
require
more
information
like
I
was
thinking
about
sean
and
matt.
We
interviewed
actually
matt
you
weren't
there.
Sean
and
george
were
there
when
we
interviewing
researchers
from
berkeley
who
are
looking
at
the
incubator
projects
with
the
apache
foundation,
and
they
were
connected.
They
had
to
use
pii
because
they
were
connecting
social
networks
and
the
impact
of
social
networks
on
around
project
and
source
code
development.
I
C
Was
the
comment
here
that
there
could
be
a
case
where
developer
names
are
shared,
given
researcher
adherence
to
some
guidelines
as
to
what
they're
going
to
do
with
that
data?
Potentially.
C
Yeah,
I'm
wondering
too,
like
even
thinking
about
the
lf
data
sharing
policies
like
how
much
we
could
talk
to
folks
in
legal
at
lf
like
if
we're
going
to
share
this,
like
we'd,
have
to
have
that
discussion
anyway,
but
like
if
we're
going
to
share
a
public
data,
set,
here's
kind
of
what
would
be
in
that
data
set
and
then
would
there
be
a
path
to
share
a
data
set
that
does
include
pii
under
certain
conditions
right,
as
agreed
upon
by
researchers.
I
think
that'd
be
interesting.
Yeah.
F
C
F
That
is
the
that's
the
general
stance
that
that
platforms
like
github
and
get
lab
tape
as
well
right,
there's
no
privacy
is
not
something
that
they
are
promoting.
I
F
F
Smaller
data
sets
ensure
those
rather
than
trying
to
be
kind
of
all-encompassing.
This
is
everything.
G
You
can't
I
mean
you
can't
count
a
lot
of
things
if
you
don't
have
it
somewhere,
but
we
could.
Just
I
mean
it
depends
on
from
a
research
perspective.
If
it's
important
to
you
to
understand
the
provenance
of
your
data,
then
you
would
want
to
know
that
there's
an
actual
person
behind
each
contributor
and
how
that's
determined
by
a
particular
program
that
gathers
data,
fogger
and
vermour
lab,
do
it
differently,
and
so
we
want
to
be.
We
want
to
be
transparent
about
it,
and
that
would
be
harder
to
do.
E
E
Form
so
wouldn't
that
mean
the
obfuscation
would
be
enough
in
the
case
of
like,
if
you
wanted
to
drill
down
on
someone,
you
could
just
do
it
on
the
public
website.
E
H
But
I'm
returning
to
the
original
proposal,
I
think
it
would
be
valuable
and
I
can
imagine
the
paper
being.
You
know
read
with
interest.
C
A
Awesome,
so
this
conversation
will
be
continued,
probably
several
times
at
various
meetings
in
the
future.
So,
okay,
let's
go
ahead
and
move
on,
so
we
have
about
20
minutes
left
the
next
one
on
here
is
the
chaos
shop
and
I'm.
E
Yeah
I
put
this
in
here.
This
is
just
in
respect
to
the
branch
name
change
that
we're
working
on.
I
just
wanted
to.
We
had
some
ambiguity
in
the
dei
working
group
on
how
far
this
has
gone
in
other
working
groups,
so
I
was
just
going
to
check
in
and
see
if
anybody
had
any
thing
to
say
about
this
in
regards
to
other
working
groups,.
C
We
do
so
we
made
the
change
in
dei
and
it
broke
one
thing,
but
that
one
thing
has
been
fixed
kevin
john.
Thank
you
evan,
mostly
kevin.
Thank
you
and
then
sean
is
gonna,
be
attending
group
meetings
all
recruit
meetings
to
kind
of
talk
through
the
process
by
which
you
can
get
this
done
technically
and
then
there's
even
more
we're
gonna
write
a
blog
post
on
what
the
what
our
goals
were
with
making
this
change
and
how
it
was
done
technically
and
both
kind
of
socially
within
the
community.
C
To
this
point
like
what
needs
to
be
done
on
github
and
then
how
sean
went
to
each
working
group
so
we'll
make
a
blog
post
on
that
as
well,
and
then
there's
even
more
we're
going
to
talk
to
the
inclusive
naming
initiative
to
to
kind
of
see
if
they
have
published
processes
that
they
share
and
if
we
can
contribute
anything
to
those
published
processes
and
if
they
don't.
Maybe
we
should
think
about
putting
something
working
on
something
with
the
inclusive
naming
initiative
to
to
kind
of
make
that
more
publicly
available
for
other
communities.
F
G
I
think
you
can
plan
on.
Do
you
want,
so
I
think
you
can
plan
on
every
working
group
in
all
likelihood
doing
it.
Do
you
want
that
to
not
happen
before
the
release
of
metrics
kevin.
G
F
F
G
A
Kevin,
do
you
think
it
would
break
anything
if
we
also
applied
that
to
the
community,
a
formerly
known
as
governance,
repo
and
the
metrics
repo.
F
F
So
so
the
same
goes
there.
If
it's,
if
it
it's,
it's,
not
a
big
deal
for
me
to
go
in
and
change
it.
It's
just
if
you
don't
want
it
to
be
broken
for
a
period
of
time
reach
out
to
me,
and
let
me
know
it's
happening
and
when
it's
happening
and
I
will
coordinate
my
the
change.
A
Okay,
cool
any
questions
or
comments
about
that.
A
All
right:
well,
we
will
move
on
because
we
wanna
we
do
have
some
chaos
con
things
to
go
over,
so
we'll
move
on
quickly,
just
wanted
to
mention
that
grimore
lab
is
hosting
a
virtual
hackathon
as
part
of
the
mining
software
repositories
or
msr
conference
happening
in
2022,
and
so
georg
asked
me
to
share
that
if
you
would
like
to
participate.
If
you
have
ideas,
this
is
mostly
for
researchers.
A
Speaking
of
researchers,
you
can
register
your
interest
in
participating
in
that
hackathon
by
october
18th
and
there's
a
link
to
do
so
right
here.
It's
basically
just
opening
an
issue
in
that
repo,
with
your
name
and
some
other
information
that
they
request.
So
more
information
is
that
in
that
link
as
well,
if
you're
interested
in
doing
that,
so
that
was
very
exciting
and
really
cool
thing
to
share
any
questions
about
that.
A
I
probably
don't
have
the
answer,
but
I
can
ask
you
or
give
it
a
whirl,
okay
cool,
so
the
next
one
is
chaos
con
things,
and
I
think
this
is
for
the
planning
committee.
Is
that
right?
A
Okay,
so
do
we
do
we
have
anything
else
for
the
general
group,
the
bigger
group,
or
can
we
go
ahead
and
adjourn
this
meeting
and
do
chaos
comp
planning
for
the
rest
of
the
time?
Is
that
cool
all
right?