►
From YouTube: CHAOSS Weekly Community Call 7-27-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
Hello,
welcome
to
the
july
27th
edition
of
the
chaos
weekly
community
call.
I
am
elizabeth.
The
chaos
community
manager,
I'm
really
happy
to
see
everyone
here.
We
do
have
a
light
group
today.
Totally
awesome,
fine,
it'll
work,
we'll
make
it
work
and
again
you
can
always
feel
free
to
keep
your
cameras
off.
We
don't
really
mind
here
just
chat
or
you
can
use
the
also
the
raised
hand
emoji.
That
also
works.
A
If
you
have
something
to
say-
or
you
can
just
bust
in,
that's
totally
fine
too
dropped
the
minutes
in
the
in
the
chat.
But
I
see
we
have
a
couple
of
people
filtering
in
so
we'll
just
do
that,
one
more
time
and
yeah.
We
have
a
pretty
light
agenda
too,
so
it
actually
works
out
great,
we'll
just
jump
right
in
to
it.
A
A
Okay,
no
worries
we'll
just
kind
of
wait
on
that
then,
and
we'll
talk
about
that
again
next
week.
C
You
guys
want
to
maybe
use
this
moment
to
book
a
kickoff
or
how
should
we?
What
are
your
thoughts,
man.
A
Matt's,
actually
not
on
the
call
so
well
maybe
wait.
He
said
he
wanted
to
lead
or
he
volunteered
to
lead
so.
A
You,
oh
no
you're,
fine,
you're,
totally
fine!
I
was
just
looking
to
see
who
else
was
on
the
committee.
It
was
you
and
kevin
and
maxie,
sean
and
nod,
and
almost
maxie
and
matt
g
aren't
here,
but
the
rest
of
you
are.
If
you
wanted
to
settle
on
a
d
or
something
like
that
or
a
plan
of
action
totally
fine.
We
can
just
let
matt
g
know.
A
No
worries
so
so.
Last
week
we
talked
about
different
ways
to
bring
metrics
together
and
we
decided
just
to
take
a
step
back.
The
asia
pacific
committee
had
put
together
a
very
nice
kind
of
presentation
on
this
idea
of
a
metrics
model
of
of
bringing
you
know
different
metrics
together
in
one
place
for
different
reasons,
and
we
linked
to
the
doc.
A
You
might
have
to
go
back
a
couple
of
weeks
to
find
that,
but
it
was
really
awesome
and
we
we
brought
it
up
again
last
week,
we're
talking
about
how
to
you
know
kind
of
bring
these
metrics
together
in
a
digestible
way,
so
that
people
can
use
them
in
the
context
that
makes
the
most
sense
for
them,
and
so
there
were
a
few
of
us
we
decided.
A
Maybe
we
should
just
have
like
an
ad
hoc
committee
to
kind
of
sort
this
out
and
figure
out
how
we
want
to
display
these
on
the
website
and
really
talk
about
them
moving
forward,
because
that
seems
to
be
kind
of
the
next
phase
of
the
metrics
you
know
is
taking
them
from
those
atomic
metrics
and
putting
it
together.
So
we
had
a
committee
that
just
kind
of
volunteered
hey
who's
interested
in
working
on
this
problem
or
this
issue
of
how
we're
going
to
visualize
these
on
the
website
and
other
places
for
people.
A
So
if
you're
interested,
you
are
again
being
a
part
of
that
feel
free
to,
I
don't
know
if
matt
g
has
really
had
a
time
to
reach
out
to
everybody,
to
kind
of
solidify
anything,
but
either
reach
out
to
him-
or
you
know,
indicate
your
name
down
below
or
up
here
somewhere
just
to
indicate
that
you're
interested.
If
you
are
just
didn't
talk
about
that.
B
A
B
This
is
related
to
the
some
of
the
use
case
work
and
it's
also
related
to
the
data
visualization
categorization
google
summer
of
code
project
that
we
had
kind
of
put
forward
that
we
that
we
didn't
do
so.
A
F
Yeah,
I
think
I
think
we
should
decide
to
meet.
I
think
it
would
be
given
the
nature
of
summer.
Maybe
a
couple
of
weeks
from
now.
F
So
maybe
meet
maybe
right
after
this
meeting
or
at
the
conclusion
of
this
meeting
not
next
week
but
the
following
week.
C
3Rd
at.
F
C
C
Okay,
so
august
10th
at
10,
pacific.
C
H
B
I
I
won't
be
able
to
make.
F
B
Day
so
feel
free
feel
free
to
meet
without
me,.
F
B
F
A
All
right,
then,
we
can
move
on.
The
next
item
was
another
carryover
from
last
week,
and
that
was
to
talk
about
our
data
ethics
statement
that
we
worked
on.
I
wasn't
sure
if
people
had
had
a
chance
to
kind
of
think
about
it.
I
know
that
we
worked
on
it
in
the
in
the
meeting.
We
took
time
to
actually
work
in
the
dock,
so
I
didn't
know
if
that
was
something
that
we
would
be
interested
in
continuing
or
do
we
have
did
have
we
had
enough
time
to
digest?
A
A
Again,
I
hear
no
objection
so
we'll
take
that
as
a
yes,
okay,
so
sean
I
don't
know
if
you
want
to
pause
or
if
you
want
to
just
keep
the
recording
going.
Sometimes
conversation
doesn't.
H
A
Okay,
so
for
anyone
who
was
not
here
last
week,
georg
has
posted
a
link
to
this
doc
that
we've
been
working
on
hi
tola.
We
haven't
seen
you
in
a
while
we're
glad
to
see
you
back.
A
We
are
working
on
this
similar
to
what
we
do
in
the
working
groups,
where
we'll
just
take
some
time
and
actually
work
in
the
doc
and
we'll
collaborate
together,
and
we
do
recommend
that
you
add,
or
you
change
your
status
to
suggesting
instead
of
editing
and
that
way
we
can
kind
of
talk
about
the
changes
that
you're
proposing.
So
if
everyone
wants
to
go
into
that
doc,
we'll
just
take
five
minutes
and
and
actually
work
on
it,
and
if
anybody
has
questions
just
just
yell
them
out
totally.
D
G
D
G
So
maybe
the
second
point
in
this
document
is
a
statement
of
ethics
for
chaos,
community
as
a
whole,
since
we
are
separating
it
out,
I
think
we
can
extract
the
values
which
are
useful
rather
than
focusing
it
as
a.
B
As
a
reminder
from
last
week-
and
I
think
sophia
may
have
brought
this
up
and
I
believe
matt
german
prey
bought,
it
brought
it
up
as
well.
There
are
kind
of
two
different
things
going
on
here,
so
this
document
is
not
about
chaos,
data
ethics.
So
it's
not
the
way
we
use
data.
This
is
about
recommendations
for
data
ethics
in
the
use
of
metrics.
Is
that
correct
sofia?
B
So
I
I
think
I
think
we
were
getting
confused
on
in
in
a
couple
places
on
this
document,
so
chaos,
data
use.
Ethics
is
a
that
is
a
different
conversation
and
we
have.
We
have
documents
for
that.
C
Elsewhere,
I'd
like
to
ask
for
feedback
on
an
idea
related
to
data
ethics,
and
that
is
boundaries
and
delineations
between.
C
For
example,
corporate
projects
will
have
a
private
repo
and
a
public
website,
and
then
often
there
will
be
things
that
are
on
both
sides
and
there's
an
ethical
issue
related
to
allowing
information
to
leak
from
the
private
to
the
public
sphere.
C
I
I
If
this
data
is
being
collected
and
stored
inside
a
large
vendor
like
google,
that
we
are
now
assuming
proprietary
accountability
over
it
and
that
changes
the
display
and
usage
of
the
data
as
well
as
how
we
would
handle
that
as
a
vendor,
but
not
necessarily,
we
can't
impart
recommendations
once
we
get
into
the
corporate
landscape
because
that's
going
to
be
defined
per
company
policy
and
they
have
their
own
lawyers.
So
it's
more
just
the
acknowledgement
that
this
is
really
only
addressing
the
parts
that
are
in
control
and
managed
by
the
community.
I
So
I
maybe
I
would
sort
of
extend
that
explicitly
knowing
that
once
that,
once
there
is
collection,
management
and
usage
on
the
behalf
of
a
corporation
that
we
assume
the
corporation
will
will
be,
I
know,
will
be
in
control
of
their
own
policies,
usage
and
accountability
around
it,
but
just
again
making
it
focus
more
on
the
community.
So
I
think
it's
a
valid
point
that
we'll
need
to
be
addressed,
but
I
would
propose
we
focus
on
the
community
side.
D
D
So
we
can
start
to
have,
I
don't
know,
maybe
we
can
turn
these
into
headings
or
something
that
we
can
then
describe
in
more
detail
and
put
the
right
considerations
in
my
thought.
Is
we
start
at
the
top
with?
Why
do
we
even
have
this
document?
What
are
the
high
level
concerns?
What
do
we
mean
with
privacy?
D
D
So,
as
someone
who
is
planning
to
collect
data,
what
are
the
things
you
should
be
thinking
about
up
front
when
you
get
into
data
collection?
What
are
the
things
that
you'll
be
dealing
with
data
handling,
storing
it
reporting?
Maybe
you
want
to
make
raw
data
available?
What
are
things
to
think
about
and
yeah?
I
I
think
we
can.
D
I
D
D
A
A
A
A
A
A
A
A
So
if
everyone
wants
to
kind
of
just
think
about
this
for
another
week
and
look
over
this
outline,
you
know
in
the
days
to
come.
That
would
be
great
and
then
we'll
revisit
it
next
week
and
see
where
we
go
from
here,
just
build
it
out.
Slowly,
but
surely
so
thanks
everybody
appreciate
you
and
your
efforts.
A
Okay,
so
let's
move
on
the
next
item
we
had
on.
There
was
the
metrics
quality
checklist
and
I'm
not
sure
who
put
this
on.
But
if
you
would
like
to
talk
about
that,
that'd
be
great.
D
Creating
metrics
is
having
more
and
more
dependencies
and
there
are
other
things
that
are
being
triggered
and
we
have
more
and
more
requirements
for
the
right
format
and
the
right
naming
convention,
and
we,
the
chaos
project,
is
growing
to
the
point
where
it's
not
enough
to
live
in
the
heads
of
a
few.
We
need
to
formalize
it
not
just
in
the
handbook,
but
maybe
this
is.
The
idea
of
the
checklist
is
when
we
create
a
new
metric.
That
we
have.
D
A
checklist
of
here
are
all
the
things
that
a
working
group
needs
to
to
do
before
it
can
go,
live
on
the
website
or
before
it
can
be
included
in
the
release,
and
that
checklist
can
include
things
like.
We
filled
out
a
question,
you
know
very
simple:
we
used
active
language
versus
passive
language
if
that's
a
style
choice
that
we
want
to
make
one
requirement
we
have
is
we
do
not
use
tables
because
that
messes
up
our
pdf
generation
images
have
a
certain
naming
convention.
D
Did
we
comply
with
that?
You
know
just
as
a
checklist
to
make
sure.
Yes,
we
we
did
that
as
a
reminder
before
we
move
forward
institutionalizing
those
those
things
and
then
also
a
checklist
for
we
created
an
issue
for
feedback.
We
created
we
added
that
new
metric
in
the
release
notes
issue.
D
We
have
alerted
the
translation
community
that
it's
ready
for
translation.
So
so
there
are
a
lot
of
things
that
that
need
to
happen,
and
it's
becoming
more
and
more,
and
the
idea
is
to
have
a
quality
checklist
so
that
when
we
create
new
metrics,
we
can
just
go
through.
Click.
Click
click
click.
Yes,
we
did
all
that.
B
I
would
I
would
like
to
point
out
that
a
lot
of
this
stuff
has
been
informally
done
by
the
organ
myself
during
the
release
process,
so
that
what
we're
really
talking
about
here
is
offloading
some
of
this
work
to
the
working
groups
to
make
sure
that
they
are
giving
us
these
metrics
in
a
form,
that's
usable
for
the
release
and
also
it
in
a
process
that
is
structured.
The
same
for
all
of
the
working
groups.
B
G
I
would
highly
endorse
for
the
checklist,
because
recently
I've
made
three
releases
and
I
was
facing
all
these
issues.
While
I
was
compiling
them,
I
have
to
add
it
to
three
different
pages.
I
have
to
check
the
formatting
of
the
images
and
all
these
things,
so
I
would
highly
endorse
for
the
checklist.
This
is
really
helpful.
Yeah.
B
I
think
this
checklist
would
actually
would
naturally
fit.
I
know
I
know
one
of
those
checklist
items
is
that
the
issue
for
the
metric
has
been
created,
but
I
think
this
checklist
would
actually
naturally
fit
into
that
issue
for
the
for
the
metric.
So
I
think
that
that's
the
perfect
place
for
it.
So
the
the
first
thing
you
do
when
you
release
a
metric.
Is
you
create
that
issue
and
then
you
go
down
through
the
checklist.
C
I
think
that
there
would
be
benefits
for
project
management
just
to
help
the
working
group
keep
track
of
where
they
are.
F
B
D
D
G
D
That's
that's
awesome
yeah,
so
it
sounds
like
we
note.
If
you
can,
if
you
can
add
to
this
issue,
add
the
other
tasks
that
need
to
go
in
and
then
when,
when
we
are
done
with
that.
Well,
we'll
also
ask
you
tick
and
rush
to
make
sure
we
have
all
the
requirements
in
here
review
this
a
few
times
and
then
because
when
we
are
ready,
would
definitely
like
your
help,
create
the
issue
template
for
all
the
working
groups
yep.
How
should
we
do
that?
Follow-Up
work?
Sorry,
vinod.
B
So
I
would
say
that
georg-
and
I
are
probably
the
product
owners
on
this
so
for
final
review.
I
think
I'd
probably
probably
need
to
tag
george
and
myself
yeah
and
I'm
happy
to
I'm
happy
to
make
edits
and
comment
as
well.
So
I'm
I'm
fairly
familiar
with
the
process.
A
F
I
have
a
I
know.
We
have
student
updates
and
a
few
items
there's
a
couple
things
at
the
end,
with
translation,
review
and
choosing
swag
for
chaos
con.
F
F
All
right
we
can,
and
then
yes,
I,
I
think,
maybe
just
we're
looking
for
people
are
people
aligned
with
the
translation
guidelines
as
they're
presently
to
find,
and
maybe
you
want
to
review
quick
foreign.
E
I
think
we
haven't
discussed
this
in
the
weekly
community
called
the
major
discussion
has
taken
place
in
the
asia
pacific
one
so
I'll.
Just
give
a
quick
summary
that
translations
team
currently
is.
You
know,
looking
at
the
working
group
repositories,
looking
at
the
changes
that
have
been
done
to
metrics,
so
they
are
having
a
hard
time
finding
out
where
the
changes
have
been
made
like,
for
example,
if
we
change
just
a
single
word,
so
we
want
to
make
sure
that
the
translated
metrics
are
updated
with
the
original
english
metrics.
E
So
we
are
trying
to
create
a
process
for
that,
and
there
have
been
a
lot
of
questions
revolving
around
the
release
of
translated
metrics.
So
the
translations
team
has
been
very
helpful
in
that
they
have
added
their
comments
as
well,
and
hopefully
we'll
get
the
talk
analyzed
tomorrow
and
we
can
ask
for
a
final
community
review.
A
E
So
the
mars
for
the
english
release
of
metrics
is
ready.
We
are
currently
working
on
the
automation
of
the
translated
metrics.
It's
a
little
different
since
the
structure
of
the
organization
of
translated
metrics
is
different.
We
have
a
just
one
repository,
so
things
are
little
different,
but
since
half
of
the
process
has
already
been
done
before,
we
expect
to
get
this.
A
A
Anything
all
right,
then
we
will
move
ahead.
Thank
you,
josh
see
what
you
get
for
coming
to
the
meetings
you
have
to
update
everyone,
but
we
appreciate
it.
Thank
you,
okay.
So
the
next
thing
is
new
metrics
released
for
review.
We
do
have
some
that
are
open
right
now
for
a
review
for
our
continuous
release
process.
We
just
want
to-
or
I
just
listed
them
here,
just
to
make
sure
people
knew
that
they
were
out
there.
A
Some
of
them
are
new,
so
the
first
one
is
time,
inclusion
for
virtual
events-
and
that
is
part
of
the
dei
working
group
and
that's
basically
making
sure
that
the
time
of
an
event
is
inclusive
globally
as
as
inclusive
as
possible.
So
what
measures
are
being
taken
to
to
make
sure
that
that
happens?
A
A
The
next
one
is
programming,
language
distribution
and
that
one
was
from
common
and
that's
pretty
self-explanatory.
I
think
the
next
one
is
collaboration
platform
activity
and
that's
also
from
common
and
that's
just
again
pretty
pretty
self-explanatory.
Just
measuring
the
activity
that's
happening
on
each
collaboration
platform,
contribution
attribution,
that
is
from
evolution,
and
that
is,
I
think,
we've
talked
about
that
before
here,
but
it's
just
making
sure
that
non-code
contributions
are
given
some
credit
and
and
really
attract
somewhere.
A
If
I
recall
that's
what
that's
about
someone
stopped
me
if
that's
wrong,
and
also,
I
think
it
has
something
to
do
with
if
work
is
sponsored
versus
volunteer.
I
believe
correct.
B
A
And
then
the
last
one
is
from
value
and
that's
academic,
open
source
project
impact
and
that
one
kind
of
revolves
around
the
value
to
someone
trying
to
get
tenure,
because
there
are
some
pretty
specific
requirements
for
that,
and
so
part
of
that
metric
is
trying
to
kind
of
enumerate
those
and
put
them
into
metric
form.
A
B
B
And
a
dish
and
I'd
like
to
also
remind
the
working
groups
to
use
the
use,
the
full
metric
name
in
in
all
of
their
their
naming
conventions,
so
the
the
language
distribution
one.
It
was
an
example
of
it
was.
It
was
language
distribution.
In
some
places
it
was
programming,
language,
distribution
and
other
places,
so
just
like
consistently
always
use
the
full
name
in
naming
the
files
and
then
mentioning
the
metrics
we'll
put
that
on
the
checklist.
A
A
A
B
G
G
G
I
just
need
the
chairs
over
the
chairs
rest
of
the
information
I
can
grab
from
the
repository.