►
From YouTube: CHAOSS Weekly Community Call 08-17-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,
everyone
welcome
to
the
august
17th
edition
of
the
chaos
weekly
community
call
elizabeth,
even
though
my
name
says
chaos
community
there,
I'm
elizabeth,
I
am
the
community
manager.
I
see
some
new
names,
some
new
maybe
faces.
I
don't
know
so
welcome.
Welcome
we're
really
glad
you're
here
and
just
to
reiterate,
we
don't
care
if
you
leave
your
camera
off
totally
fine.
If
you'd
like
to
turn
it
on.
That's
fine,
too
we're
pretty
flexible
here.
A
So
if
you
would
like
to
interact,
you
can
either
use
the
raised
hand
emoji
or
you
can
put
something
in
the
chat.
We
try
to
integrate
that
pretty
well
into
the
flow
of
the
conversation,
so
don't
hesitate
to
just
drop
something
in
there
or
raise
your
hand.
I
hope
everybody's
doing
good.
It's
been
a
couple
weeks
since
I
saw
you
everyone,
I
missed
everybody,
so
I'm
glad
to
be
back.
Y'all
are
awesome
and
you
make
my
day
happy.
A
So
I'll
drop
the
minutes
in
here
one
more
time
just
in
case,
if
you
would
like
to
leave
your
name
in
the
agenda,
that
would
be
great
because
we
do
kind
of
like
to
keep
track
of.
Like
who's
coming
to
the
meetings
and
stuff,
so
that'd
be
great,
but
you
obviously
do
not
have
to
and
then,
if
you
would
like
to
tell
us
one
good
thing
in
your
life,
that
would
be
amazing
because
the
world
is
not
great
in
a
lot
of
places
right
now,
so
that
would
be
great
to
just.
A
Let
us
know
something
good!
That's
going
on.
Let's
see
here
so
we'll
go
ahead
and
get
started.
The
first
one
just
wanted
to
update
everybody
on
the
chaos
chaos
con
cfp.
We
had,
I
believe,
14
submissions
at
the
end
of
it
sophia
and
ray
were
on
the
call
today.
Do
you
all
have
anything
to
add?
I
think
you're
gonna
be
the
committee
that
picks,
if
I'm
not
mistaken,.
B
No
yeah,
so
I
started
a
google
doc
and
some
of
you
may
have
seen
it
or
google
sheet
to
for
people
in
this
election
committee
to
grade
them,
and
then
I
mean
we
can
talk
more
about
this.
I
guess
in
the
second
half
when
we
have
to
ask
on
specific
topics,
but
you
know
I
don't
know
the
rough
timeline
and
sofia
can
jump
in
here.
B
If
you
don't
agree,
but
we
can
give
people,
for
example,
in
this
on
the
committee
to
you,
know,
grade
their
greatest
submissions
by
the
end
of
the
week,
for
example,
and
we
can
have
a
quick
meeting
next
week
to
sort
of
you
know,
make
a
decision
on
based
on
grades
like
which
ones
got
accepted
and
which
one
which
one
will
not
be
so
that's
sort
of
the
thinking
right
now,
but
I
forget,
like
do
we
have
a
date
on
when
we're
supposed
to
get
back
to
people
with
decisions
or.
C
B
We
meet
by
like
early
next
week
after
the
grading.
I
guess
that
should
work.
B
No,
I
wasn't.
I
wasn't
going
to
open
that
up,
but
you
know
we
can
talk
about
that.
The
second
half
like
the.
B
I
had
was
you
know,
I
think
that
form
that
sofia
created
was
shared
with
like
five
people
like
I
don't
know
if
those
five
people
are
the
ones
that
are
part
of
this
election
committee
or
we
I
need
to
I
mean
I
was
gonna
include
everybody
on
the
the
chaos
con
channel
chaos
con
committee
channel,
like
all
13
of
them,
I
think,
but
wasn't
sure
I
need
to
include
I'm
okay
with
including
all
13
people
there
or
if
it's
just
a
subset
of
that
group,
but.
B
C
Yeah,
I
think
that
that
approach
makes
sense,
hopefully
in
the
next
it
would
be
seem
like
we
have
enough.
I
think
sort
of
the
initial
debate
was
whether
or
not
we
were
going
to
extend
the
deadline,
but
I
think
with
14
we
are
only
have
a
half
day,
so
I
think
I
think
we'll
have
enough
to
work
with.
So
I
think
that
concludes
our
cfp
process
and
we'll
have
an
update
for
the
team
in
the
next
few
weeks.
B
F
C
B
E
B
A
And
for
those
who
are
might
be
new
on
the
call
just
for
a
temporary
leading
up
to
chaos
con,
which
is
at
the
end
of
september,
this
meeting
will
be
a
little
bit
shorter
than
usual,
so
we're
gonna
end
this
meeting
at
12.
Sorry,
12,
30,
my
time,
half
past
the
hour,
wherever
you
are
so
that
the
rest
of
the
time
can
be
used
for
chaos
con
planning.
A
So
we
will
just
let
everybody
know
that's
kind
of
what
we're
talking
about
when
we
say
like
the
second
half
of
the
meeting,
that's
what
that
means.
Does
anybody
have
any
questions
for
rey
or
sophia,
or
anybody
on
the
cast
con
committee.
A
All
right
we
will
move
forward,
then.
The
next
item
is
just
a
brief
announcement
that
the
office
hours
that
we
do
on
mondays
has
been
switched
to
bi-weekly
to
make
things
a
little
bit
easier
for
the
chaos
team
to
manage.
A
So
if
you
have
questions
about
that,
I
wasn't
really
present
for
those
conversations,
so
I
can't
give
you
any
other
context
than
that,
but
if
you
would
like
to,
if
you
are
a
member
of
the
cast
community
already-
and
you
would
like
to
host
one
of
those
sessions-
they're
pretty
low
traffic,
maybe
like
one
or
two
people
max
pop
into
those,
so
there's
a
spreadsheet,
there's
a
link
to
the
spreadsheet.
A
We
have
there
where
you
can
just
drop
your
name
in,
and
I
am
working
on
a
doc
that
will
kind
of
give
you
information
about
what
what
it
is
and
how
to
do
it
and
like
how
to
use
the
zoom
tools
and
things
like
that,
if
you're
the
host
so
bear
with
me
on
that,
I'm
working
on
that
it
should
be
done
in
the
next
few
days.
A
No
okay,
all
right,
we'll
move
on
another
reminder
on
the
metrics
freeze
september.
1St
is
the
next
freeze.
So
if
you
are
in
a
working
group
that
has
some
outstanding
metrics
that
you're
working
on
just
a
reminder
just
try
to
kind
of
bring
those
in
for
a
landing
and
get
those
out
there
before
that
freeze
happens
on
september
1st
and
then
september
1st
through
the
end
of
september,
will
be
the
30-day
public
review
period
on
all
of
the
metrics
that
we
have
coming
up
in
the
next
release
in
october.
A
We
are
just
flying
through
this
agenda,
so
good
for
us,
okay,
so
the
next
one
is
about
translations.
A
Kevin
is
not
here,
but
he
asked
me
to
pass
along
some
information
to
you
and
I
do
see
that
ridiculous
are
here,
so
they
can
probably
chime
in
as
well,
but
he
just
want
to
remind
everyone
about
the
the
translation
guidelines
that
are
being
worked
on.
A
There's
a
link
to
the
doc
in
the
minutes,
and
if
you
want
to
take
a
look
at
that,
if
you're
in
a
working
group
that
has
some
metrics
that
are
going
to
be
up
for
release,
he
just
asks
that
you
double
check
to
make
sure
that
there's
a
corresponding
issue
in
the
translation
repo
and
there
should
be
some
templates
for
you
to
use,
even
though
they're
still
kind
of
being
developed.
There
is
something
there
for
you
to
use,
and
then
I
don't
know
richie
josh.
E
Josh,
if
you
have
the
the
flow,
the
workflow
the
chart
that
we
worked
on
yesterday,
if
you
would
like
to
share
your
screen
and
show
that
or
add
a
picture
in
the
minutes.
I
think
that's
a
really
nice
way
of
representing
what
that
workflow
for
translation
is
going
to
look
like.
G
H
Can
you
see
the
chart?
Yes
yeah,
yeah,
so
char?
This
flowchart
is
basically
divided
into
two
main
parts.
The
upper
one
is
for
the
metric
working
groups
and
the
lower
one
is
for
the
translation
stream.
So
initially,
let's
say
the
word
group
propose
some
change
now.
These
changes
can
be
of
two
types
either
in
the
metrics
or
in
the
focus
areas,
and
they
can
be
like
some
metric
or
focus
area
is
added,
updated,
renamed
or
removed.
H
So
after
this,
the
next
thing
would
be
to
create
an
issue
in
that
particular
working
group.
So
the
label
for
that
issue
would
be
metric
release
candidate,
and
here
we
will
be
using
an
issue
template
and
this
issue
will
stay
open
until
the
metric
release
process.
That
is
in
the
october.
I
guess
so
from
this.
H
We
will
make
a
reference
issue
and
we
will
update
this
new
metric
in
the
website
with
the
label
under
review,
and
this
issue
will
also
be
referred
in
a
new
issue
that
is
the
metric
release
node
with
the
label
of
metric
release.
Node.
Now
from
this
issue,
we
will
inform
the
translation
team
by
creating
an
issue
in
the
translation
community,
the
translation
repository
and
refer
the
metric
release
candidate
issue.
H
So
we
have
a
new
issue.
For
now
we
have
two
languages:
spanish
and
chinese,
so
we
will
add
the
language
labels.
Now
the
corresponding
translation
teams
will
resolve
the
issue
and
create
the
translation.
They
will
remove
their
labels
and
then
we
can
proceed
to
create
the
metric
release
for
that
particular
language.
A
I
have
a
question
that
first,
the
gray
box-
that's
the
process.
We
were
already
following
right
like
that.
That's
not
changing!
Is
that
correct?
Okay,
perfect!
I
just
want
to
make
sure
I
just
want
to
make
sure
this
looks
great.
This
is.
E
E
So
in
the
chat,
I
posted
the
link
to
the
current
version
of
the
checklist
for
that
central
issue.
The
metrics
release
candidate
issue
that
all
all
changes
have
to
go
through
and
there
we
have
the
process
checklist
items
and
one
of
them
is
to
create
an
issue
in
the
translation
repo,
and
so
it's
really
lightweight
on
the
working
groups.
To
start
adding
the
translation
teams
and
let
them
know
hey,
there-
are
changes
to
be
translated.
A
So
this
checklist
comes
up
when
we,
under
in
the
gray
box,
when
it
says,
create
issue
after
type
of
change,
and
it
says
create
issue.
That's
where
that
issue
is
from
okay,
perfect.
E
H
A
One
more
comment
on
this,
and
then
I
swear
I'll
stop
but
like
seeing
it
visually
like
this
is
so
great
like
because
for
the
you
know
the
first,
like
probably
six
months,
I
was
here,
it
was
still
hard
for
me
to
visualize
how
the
flow
went.
So
I
really
appreciate
you
you
all
putting
this
into
like
a
visual
form,
I'm
a
very
visual
learner.
So
for
someone
like
me,
it's
extremely
helpful
and
the
checklist
is
just
amazing
as
well
like
the
I'm.
A
very
you
know,
task
oriented
so
going
down.
A
A
Okay,
we
don't
have
anything
else
on
that.
We
will
go
ahead
and
move
forward
on
the
agenda,
so
we
have
about
nine
minutes
left
in
this
in
this
part
of
the
meeting.
Oh-
and
it
looks
like
we're
at
the
end
of
youtube,
so
oh
wait,
update
on
the
community
handbook
was:
is
that
just
adding
those
translations
in
there?
Whoever
put
that
in
oh.
A
Thank
you
guys.
Well,
we
have
nine
minutes
left.
What
do
we
want
to
talk
about
anything
exciting?
What
do
we
want
to
do
with
our
time.
C
Well,
we
had
tables
work
on
the
data
ethics
last
week.
I
don't
know
if
georgia
had
an
exercise
for
us
this
week,
but
we
have
time.
E
A
And
for
anyone
who
might
be
new
to
this
meeting,
this
is
a
statement
that
we've
been
working
on
for
a
while
in
this
meeting
and
it's
a
general
ethics
statement
on
how
people
should
be
using
the
data
that
they
collect,
based
on
our
recommendation
in
the
metrics.
So
it's
for
the
community's
use
to
when
they
start
using
a
metric.
It's
so
that
they
can
have
a
better
feel
of
like
what
do
we
do
with
this
in
a
good
way,
and
then
what
we'll
do
is
we'll,
I'm
assuming
george.
E
Well,
I
I
think
what
we
did.
If
I
remember
correctly,
we
had
one
session
with
just
a
brainstorming
of
topics
and
things,
so
that's
the
top
of
the
document,
and
then
we
had
a
second
session
where
we
were
working
on
an
outline
proposal.
So
that's
the
bottom
part
of
the
document.
E
So
the
outline
includes
some
high
level
discussion
of
why
this
document
is
important.
What
are
some
ethical
concerns
that
we
are?
We
want
to
raise
awareness
for
just
you
know,
so
everyone
has
the
same
understanding
of
what
the
issue
is,
and
then
we
go
into
a
second
part
where
we
go
through
the
stages
of
metrics
and
we
address
at
each
state
what
the
challenges
are
and
how
we
think
they
can
be
mitigated.
D
E
E
A
D
E
A
C
I
mean
I
always
have
the
like
the
former
analyst
view,
but
like
we
were
constantly
trying
to
define
things
and
then
claim
that
our
definition
was
the
best
one
so
like,
or
something
like
beyond
beyond
legal
and
regulatory
bodies,
there's
going
to
be
a
lot
of
subjectivity,
so,
instead
of
claiming
one,
we
could
also
point
to
variety
if
there
isn't
a
definitive
legal
or
government-driven
definition
of
something,
then
potentially
we
we
just
start
with,
like
I
don't
know,
collecting
a
canonical
variation
of
listening,
and
this
is
like
again
part
of
the
ambiguity.
C
Sort
of
a
general
comment
just
looking
at
this
I'm
thinking
about,
I
know
you
have
sort
of
the
like
ideas
around
outputs,
but
reading
through
the
outline.
Specifically,
the
thing
that's
really
coming
out
to
me
is
that
all
of
this
is
to
inform
your
policy
and
policies
that
you
create
around
your
project
around
data
handling
around
your
project,
and
so
at
a
certain
point.
I
do
think
we
should
at
least
state.
C
So
we'll
probably
have
to
have
something
like
that
stated
either
up
front,
or
especially
as
we're
coming
up
with
examples
and
things
like
definitions
or
considerations,
there's
potentially
a
lot
of
existing
documentation.
We
could
point
to
if
we
find
good
examples
of
how
others
have
handled
some
of
the
stickier
issues
in
this
regard,
not
that
they
want
to
be
referenced
here,
but
I
guess
for
our
drafting
purposes.
We
could
see
what
we
find
and
then
decide
how
we
want
to
surface
that
to
the
public.
E
Yeah
because
that's
what
people
come
to
chaos,
for
they
want
to
have
help
with
their
metrics
strategy,
with
their
metrics
efforts
and
so
yeah.
I
agree.
I
added
a
sentence
here.
Purpose
of
this
document
is
to
help
set
a
good
data
policy
for
your
metrics
efforts,
and
we
can
probably
fill
that
in
a
little
bit
more.
A
So,
since
we're
kind
of
at
half
past
the
hour,
do
we
want
to
have
that
as
kind
of
like
an
informal
action
item
for
everybody
to
kind
of
just
do
a
little
bit
of
research
on
some
of
these
terms
and
come
up
with
some
references?
A
E
Yeah,
I
I
agree:
let's
revisit
this
next
week,
if
someone
has
some
time
to
bring
in
references,
then
I
would
say
we
can
take
a
note
for
next
week
that
we
work
on
this
first
part
and.
E
A
Make
sense
all
right
one
last
one
last
call
for
any
questions
or
anything
that
people
might
have
before
we
officially
end
this
part
of
the
meeting.
Anybody
have
anything.
A
No
all
right,
if
you're,
not
on
the
chaos
con
planning
committee,
you
are
free
to
go
and
enjoy
the
rest
of
your
day.
If
you,
if
you
can
everybody
else,
who's
working
on
cass
kind,
if
you
would
stick
around
that'd,
be
awesome.