►
From YouTube: CHAOSS.Community.August.11.2020
Description
CHAOSS.Community.August.11.2020
A
All
right,
hello,
everyone,
it
is
august
11th-
and
this
is
the
chaos
weekly
meeting-
welcome,
welcome.
I
posted
the
minutes
in
chat.
So
if
you
did
not
see
those,
let
me
know
or
let
somebody
know
and
we
can
post
it
in
there
again.
A
We
have
a
pretty
light
agenda.
There
isn't
much
on
there
today,
but
if
you
can
make
sure
to
add
your
name
to
the
attendees
list,
that
would
be
awesome
and
I
will
do
that.
A
All
right,
so
the
first
item
on
the
agenda
is
something
I've
been
super
excited.
I
can't
wait
to
see
this
yeah.
I'm
really
excited
about.
This.
Tola
is
going
to
give
us
a
demo
on
some
of
the
the
localization
stuff
that
he's
been
working
on
so
totally
I'm
gonna.
Let
you
take
over
and
share
your
screen
and
do
whatever
you
need
to
do.
C
Okay,
goody,
all.
C
The
r3g
intent
for
years,
so
my
project
is
about
localization
and.
F
C
So
I
I
did
the
purpose
of
this
project.
The
process
for.
F
C
The
second
one
was
third,
one
was
lucas
and
the
photos,
so
I'm
just
going
to
kind
of
give
a
summary
of
so
far.
The
first
one
for
crowding.
We.
C
For
crowding
there,
where
there
is
some
requirements
or
criterias
to
make
for
open
source
projects,
hijack
is
implementing
with
crime
is
actually
free
for
open
source
project,
but
some
of
the
criteria
couldn't
be
met
and
another
reason
why
we
couldn't
work
with
crowd
is
because
of
the
pricing.
For
start,
the
pricing
for
crowding
was
kind
of
very,
very
high,
so
we
had
to
switch
to
web
blitz
yeah
so
for
web
leads
and
web
bits
can
actually
be
hosted
locally
on
your
computer
using
docker.
We
did
all
of
that.
G
C
Dm
documentation
and
all
of
that,
and
also
the
rubbing
documentation,
results
easy
to
follow.
We
had
to
check
out
the
external
resources
like
medium,
google,
about
execution
and
the
rest,
and
also
for
webinars.
C
The
translation
content
is
not
it
doesn't
integrate
with
from
version
control,
the
key
digital
format
for
key
and
value,
we're
not
easily
liking
the
part
for
the
values
we're
not
easily
specified,
so
we
have
to
move
to
localize.
One
of
the
two
important
factors
that
made
us
choose.
The
best
platform
was
pricing
and
version
control
integration,
so
we
went
for
localized
and
dislocalized.
C
The
third
one
looks
very,
the
pricing
is
very
very
moderate,
starts
around
five
dollars
for
for
the
translation
context,
and
one
advantage
of
you
guys
was
that
it's
the
pricing
for
translation.
C
It's
not
powered
the
the
kind
of
groupies
per
group
of
words,
so
it's
cheaper
for
us
then
get
the
cameras
is
actually
free
for
open
source
projects
and
it's
easily
integrated
with
github
and
fashion
control
yeah.
So
so
the
two
platforms
we
went
for
finally
was
blue
guys
and
github
guys.
These
are
the
factors
that
made
us
choose
these
two
platforms
and
they
were
actually
very.
C
Very
friendly,
designed
office
is
very,
very
friendly
for
starter
goods
follow
through
actually
the
documentation
of
all
these
platforms
is
attached
to
my
reports,
so
the
how
we
integrated
a
lot
of
features.
We
worked
with
the
api,
the
command
line,
tools
and
everything.
So
this
is
the
smart
slides.
My
report
that
the
google
drive
link
is,
I
did
a
screen
record
of
the
s
platform,
so
I'm
going
to
attach
it
to
the
google
docs
too
and
yeah
so
yeah.
H
I
G
C
E
C
C
C
D
C
B
Well,
thanks
tola,
thanks
for
showing
this
and
thanks
for
kind
of
leading
this
effort,
because
I
think
translation
is
something
that
I'd
like
to
see
advanced
in
the
chaos
project.
I
guess
one
of
the
things
I
guess
do
people
have
questions
on
the
process
and
kind
of
what
this
is
about
for
tola.
A
I
have
a
quick
question.
This
is
awesome
by
the
way.
Oh,
my
gosh,
how
cool
is
this?
My
question
is:
do
we
do
we
need
to
review
the
translations
before
we
commit
them,
or
is
it
pretty
well
that
established.
C
Translation
is
pretty
accurate,
yes
yeah
you
can.
There
are
moderators
that
could
review
the
translation
on
the.
B
B
G
Okay,
I
actually
created
a
branch
for
it.
C
B
So
in
so
what
you're,
showing
here
so
there's
the
community
handbook
and
then
there's
the
es,
slash
community.
C
Community
handbook
is
the
translated
folder
like
after
we
create
the
pull
request
from
git
localize,
so
it's
automatically
generates
the
folder
called
es
or
translation
default
can
also
be
made.
It's
just
like
the
fashion
control,
question,
budget
and
fashion
control
and
execution.
So
it
generates
the
folder
for
all
the
translation
that
has
done.
G
B
B
B
B
B
This
this
route-
this
might
be
something
we
want
to
take
a
look
at
to
really
think
about
how
to
document
this
process
and
then
actually
get
it
done.
There'll
be
quite
a
bit
of
time
to
actually
get
it
done
across
all
the
repositories.
I
guess
the
other.
The
other
challenges
is
that
each
we
might
want
to
think
about
what
we
update,
because,
obviously
we're
not
translating
everything
I
feel
like
we're,
not
translating
everything
from
auger,
because
every
time
there's
a
a
change.
B
I
don't
know
we'd
have
to
think
about
things
that
are
somewhat
stable
for
translation
just
so
we
can
track
what
we're
translating
and
what
we're
not.
It's
like
the
community
handbook
would
probably
be
a
a
good
candidate,
but
we
might
want
to
think
about
specifying
some
some
world
of
things
that
need
translated.
H
Yeah
and
I
do
know
the
gate,
localized
does
offer
professional
translation.
I
think
it's
by
repo
that
they
they
can
work
with
us
on
that
kind
of
thing,
too.
Okay,.
C
A
A
Awesome
so
to
mass
point:
what
do
we
want
to
do
for
our
next
steps
on
this?
Is
there
anything
that
we
want
to
take
action
on
right
now
or
how
do
we
want
to
proceed
with
this.
A
Mean
is
this:
is
it
something
that
needs
like
its
own
little
task
force
to
to
figure
out?
Is
this
something
that
we
want
to
do
on?
These
calls.
A
Okay,
so
let's
put
a
I'm
just
going
to
suggest
we
put
an
item
on
this
agenda
and
have
people
add
their
names?
A
A
Okay,
all
right,
so,
let's
move
on
to
the
next
thing.
If
nobody
has
any
other
questions
for
tola
we'll
go
on
to
venue
is
venue
here,
yeah.
F
G
B
A
A
H
Hi,
it
seems
that
badging
is
dominating
the
meeting
today,
but
I'm
okay
with
that
personally,
so
I
just
wanted
to
mention
like
we
have
been.
Actually
the
pilot
testing
is
coming
up
next
week
on
the
second
and
final
before
we
get
ready
to
launch
the
project.
So
I
just
wanted
to.
I
actually
asked
his
email
as
the
one
to
this
time
for
contact
and
we'll
be
sending
out
a
reminder
to
anybody
that
was
interested
in
the
second
pallet
testing
on
friday
and
we're
looking
forward
to
having
that
in
place.
H
There
are.
Is
there
anything
specific
that
anyone
wants
to
mention
or
explain
for
that
processing
a
request
for
the
email.
H
Yes,
we've
got
some
things
that
are
kind
of
concretely
changing,
so
one
of
the
first
items
is
that
that
the
the
system
of
pull
requests
that
we
were
using
to
update
a
lot
of
that
has
been
a
lot
more
automated
and
that
required
switching
over
to
issues.
So
now
the
projects
and
events
are
just.
H
Events
for
now
are
set
to
issues,
and
we
are
just
doing
events
for
now,
because
we
want
to
focus
on
making
sure
that
virtual
events
can
be
included,
and
that
is
a
positive
experience
to
submit
with
we've
got
a
form
that
we've
created.
That
is
not
through
the
chaos
website
that
we
can
submit
with,
which
means
you
don't
have
to
add
a
line
item
in
the
table
on
markdown
to
submit
a
project
or
an
event,
and
I
think
those
are
the
main
parts.
H
There's
there's
been
some
changes
to
how
the
review
system
works,
it's
on
a
more
more
of
a
quantitative
basis
rather
than
qualitative,
and
it's
based
on
a
percentage
of
how
many
checks
you've
met.
Those
are
the
those
are
the
real
big
changes.
There's
there's
little
things
here
and
there
everywhere,
but
we've
been
making
a
lot
of
improvements.
I
think.
E
H
Are
going
to
happen
through
the
website
so
the
way
the
submissions
work
now
is,
instead
of
going
and
creating
the
issue
with
the
template,
you
go
on
to
the
website
and
you
fill
out
a
form
just
like
an
html
form,
and
then
you
and
then
it
will
create
a
an
issue.
That's
all
filled
out
for
you
on
github
and
you
just
have
to
create
click,
the
create
issue
button
and
it
creates
everything
pretty
much
as
as
without
the
need
to
go
into
markdown
and
dive
in
and
work
on
it
that
way.
E
H
Yes,
eight
to
10
cdt
on
thursday
is
is
it's
my
office
hours,
but
I'm
really
glad
to
invite
anybody
that
wants
to
be
part
of
that
as
well.
H
I've
created
a
pull
request
with
all
the
updates
making
it,
making
the
code
cleaner
and
all
that
stuff
and
adding
the
descriptions
and
everything.
H
And
if
there's
another
yeah,
I
I
don't
didn't
suspect
there
would
be
a
lot
of
questions
though
there
was
if
there
are
any
more
questions.
I'll
drop,
my
email
here
too,
so
we're
not
taking
up
too
much
time,
but
that's
that's
it.
For
now,.
H
Yeah,
that's
actually
we
it's
ideal
to
have
some
new
people
that
haven't
seen
the
workflow
at
all,
yet
so
we're
always
we're
also
looking
for
people
who
know
people
who
might
want
to
be
part
of
it
as
well.
A
Okay,
I
guess
not
feel
free
to
email
matt
if
you
do
think
of
something
after
we
hang
up.
So,
let's
move
on,
we
are
rolling
through
these
amazing
community
reports.
I'm
guessing
that
matt
g
put
that
on
there
yeah.
B
So
this
is
slowly
rolling
forward
and
we
had
talked
about
having
you
know:
four
visuals
a
couple
from
the
gremore
lab
cauldron,
side
of
things
and
a
couple
from
auger
side
of
things
and
the
I
think
we're
coming
to
closure
with
our
discussions
at
the
linux
foundation.
Just
in
terms
of
the
process
by
requesting.
B
I
I
So
I
I
suppose,
if
we
can
pick
areas,
I
pick
areas
where
we
already
have
stuff
that
is
working
at
scale
yeah.
But
if,
if
that
you
know,
but
I
don't
know
what
grammar
lab
would
want
to
include,
do
you
have
a
sense.
F
Would
be,
can
I
have
sharing
uh-huh.
F
I
Yeah,
I
mean
that's
kind
of
what
I
was
proposing
as
well.
I
think
that
one
one
does
cauldron.
Do
the
dashboard
of
corporate
contribution
levels,
it's
a
pie
chart
in
gremor
lab.
Does
it
have
that.
F
F
Yeah,
I
do
too
so,
since
you
want
users
and.
F
B
B
Know
what
I'm
talking
about
and
like
commits
is
just
a
single
thing
and
maybe
maybe
that's
a
totally
good
look,
but
I
was
wondering
if
there
was
something
that
was
that
you
would
want
to
bring
forward.
That's
that's
more
of
a
composite
and,
if
commits
is
what
is
what
should
be
displayed,
then
I
totally
that
there's
more
of
a
question
not
not
guiding
you
anywhere
so
yeah.
F
No,
I
I
fully
agree
so
right
now.
What
I'm,
showing
you
is
everything
that
cauldron
does
on
its
front
dashboard.
So
there
is
the
more
detail
where
you
can
go
to
kibana
and
you
can
have
your
custom
visualizations,
but
I
would
recommend
taking
one
of
the
ones
that
are
right
here
on
the
front
and
no,
they
are
all
very
basic,
elementary
visualizations
right
now,
but
I
talked
with
jesus
and
manrique
and
they
are
open
to
adding
any
new
visualizations
that
we
decide
on.
F
B
B
F
Looking
at
these,
I
would
just
recommend
the
issues
open
closed,
because
that
is
easy
to
communicate
what
that
means.
There
are
number
of
issues
that
were
opened
and
closed
on
those
days
or
in
that
time
frame.
F
B
Yeah
everything
can
change
just
so
then.
What
I
would
have
from
cauldron
would
be
commits
over
time,
issues
opened
and
closed
over
time
and
then
from
the
auger
side.
It's
it's
your
composite
visualizations
around
pr's
sean
and
your
composite
visualizations
around
new
contributors
is
that.
I
Right,
that's
right:
okay,
yeah
and
I
have
I'll
pick
through
some
and
socialize
them
with
people.
Just
okay
ones
are
the
the
best.
B
Could
totally
sounds
cool?
Could
georg
and
sean
could
do
you
have
the
captioning
that
would
go
underneath
those,
because
we
had
talked
about
providing
kind
of
rich
descriptions
of
what's
going
on
yeah
and
that's
something.
Obviously
that
can
just
be
repeated
for.
I
I
think
for
like
some
of
the
metrics
georg
was
talking
about.
If
there
aren't
captions
in
cauldron,
we
can
take
the
cauldron
image
and
just
include
the
standard
caption
for
what
those
metrics
are
like
commits
in
the
report,
and
that
can
actually
be
derived
from
the
chaos
metric
definition
for
commits.
Since
it's
one
metric,
yeah.
B
B
F
B
I
I
F
B
All
right:
well,
I
don't,
then
we
don't
even
have
to
type
the
name
of
the
repo
yeah.
We
all
know
it.
I
know
it
yeah
I've
heard
of
that
one,
okay
cool!
So
then,
maybe
it's
really
just
running
these
four
things
across
the
agar
repo,
getting
the
visualizations
and
starting
with
any
of
the
captioning
that
would
go
along
with
it
and
I'll
connect
with
youtube
guys,
just
to
kind
of
give
you
that
template
again
that
we
had
kind
of
roughed
out.
You
know
what
I'm
talking
about
the
community.
I
B
A
We
are
all
about
productivity.
I
love
it
all
right
moving
along
because
we
only
have
nine
minutes
left.
I
put
this
on
the
agenda.
The
metrics
release
announcement
just
to
let
everyone
know
that
we
did
actually
announce
them
this
morning.
So
if
you
are
curious
that
will
it's
on
our
blog,
I
believe
kevin
merged
that
in
as
this
meeting
began,
so
it's
super
fresh
and
shiny
and
new
and
we'll
be
putting
it
in
the
mailing
list
as
well
and
on
twitter
and
we'll
send
it
out
to
other
things.
A
So
you
all
can
retweet
and
spread
the
word
as
necessary.
There
is
a
really
nice
pdf
copy
of
the
release.
If
you
have
not
seen
that
it's
really
well
done,
and
I
think
kevin
was
responsible
for
that.
So
thank
you
kevin.
It's
really
great.
A
York,
sorry
awesome
job.
Georgia
really
really
good.
I
love
it.
Sorry,
that's
my
my
dog
choking
the
background.
She's,
okay,
she's,
fine,
I'm
sure
nothing
to
see
here.
It's
great
and
also
I
see
a
note
here.
It
says,
contribute
our
list
is
becoming
large.
If
you
are
left
off
the
list,
where
apologize,
let
us
know
and
we'll
add
you
so
we
would
let
kevin
know
that
is
that
right.
A
B
B
B
A
A
And
then
the
next
item-
real
quick
ruth
just
brought
up
over
here
in
the
chat,
a
potential
idea
about
measuring
burnout
from
contributors,
which
I
think
is
super
interesting.
I'm
sure
others
do
as
well
and
ruth
is
also
new
to
the
meeting
so
hi
welcome
we're
glad
we
were
wondering
what
you
all
think
about
which
working
group
that
would
fit
in,
because
I
originally
thought,
maybe
common
since
that's
where
we
kind
of
measure
contributor
activity
in
general,
but
it
also
might
speak
to
the
culture
and
inclusivity
of
a
project.
A
You
know
how
how
balanced
it
is,
and
if
people
are
aware
of
this,
you
know
burnout
problem
in
dni.
So
I'd
really
like
to
hear
everybody's
thoughts
on
that
of
where
we
should
send
ruth
to
to
pursue
this
a
little
bit
more.
B
F
I
know
burnout
has
been
a
conversation
in
general.
I
don't
think
we
have
tried
to
have
a
metric
around
it.
B
F
A
Yes,
thank
you.
My
tab
was
gone,
so
ruth
10
a.m.
Tomorrow's
is
the
diversity
inclusion
meeting
if
you're
able
to
attend
that.
That
would
be
amazing.
If
not,
you
can,
as
armstrong,
suggested,
write
up
a
proposal
and
submit
it.
Okay,
perfect!
A
If
I
was
going
to
say,
if
you
have
questions
about
how
to
do
that,
just
let
me
know
you
can
just
email
me
or
hit
me
up
sometime,
all
right,
four
minutes
and
we
made
it
all
the
way
through
the
agenda.
What
else
do
we
have
anything
any
other
ties
to
to
wrap
up
before
we.