►
From YouTube: CHAOSS.Community.Feb.25.2020
Description
CHAOSS.Community.Feb.25.2020
A
So
on
the
agenda.
We
have
one
item
right
now
and
that
is
to
continue
the
conversation
from
the
mailing
list,
about
which
platform
chaos,
reviews
for
its
repositories,
we're
on
github
right
now
and
there's
some
talk
on
the
mailing
list
about
possibly
moving
to
good
luck,
but
we
just
discussed
before
the
meeting
started
that
we
might
not
have
people
on
the
call
who
use
git
laugh
or
github
on
a
daily
basis,
so
we
will
defer
unless
someone
has
an
opinion.
They
would
like
to
add
to
the
conversation
today.
A
B
Sorry
yeah
I'll
be
checking
here.
Oh
no
I
made
a
suggestion
about
starting
to
draft
as
we
go
through
the
process,
so
so
it
was
the
idea
that
if
you
draft
the
document,
while
you
actually
prototyping
their
part
like
the
process,
is
being
driven
by
the
discussions
that
everyone
is
doing
and
so
we're
just
creating
that
talk
as
we
go,
we're
not
doing
it.
You
know,
after
the
fact,
I
believe
that
was
the
idea.
A
B
A
B
B
B
B
No,
so
so
the
idea
was
the
read
me
was
just
putting
out
the
other
thing.
Why
don't
we
start
drafting
the
read
me
based
on
that
outline
and
then
next
meeting
when
we're
talking
we're
basically
looking
at
a
dock
that
elaborates
whatever
whatever
those
points
would
actually
look
like
in
the
readme
and
if
we
refine
it
refining
the
process.
B
C
C
We
we
changed
all
of
the
focus
groups
when
we
couldn't
figure
out
which
one
to
add
it
to,
because
the
descriptions
were
so
unclear
that
we
couldn't
remember.
We
couldn't
remember
what
we
were
talking
about,
and
so
we
read
it
all
the
all
the
descriptions
so
that
we
could
add
that
metric,
but
I
think
it's
a
completed
metric
that
we
want
to
include
in
the
incremental
release.
A
B
A
B
Session
or
what
is
this
so
to
clarify
basically
like
I,
I
kind
of
like
the
idea
of
hackathons
when
I'm
doing
collaborative
work
when
we
have
enough
time
to
you
know,
focus
on
on
the
work
that
needs
to
be
done,
and
so
me
and
Matt
kind
of
share
that
style.
So
we
decided
every
other
Sunday.
We
meet
I,
guess
for
two
or
three
hours:
minimum
like
two
hours
minimum
three
hours,
maybe
more,
it
depends
on
what
we
need
and
you
just
give
it
a
push.
B
So
I
guess
it's
just
you
know
like
the
one
hour
is
good
for
GTV
by
the
book,
like
you
know,
follow
the
outline
and
action
items
and
then
go
out
and
do
them,
but
I
guess
what
we're
doing
is
we're
dwelling
more
and
we
work
and-
and
so
we
have
this
routine
slow
walk
every
other
week,
so
basically
feedback
we
get
between
those.
You
know
work
sessions,
just
basically
get
you
know,
get
get
done
at
that
point.
You
know.
So
it's
a
biweekly
sprint
that
is
done
on
one
day.
B
So
so
I
guess
swelling
is
how
we
ended
up
finding
badges
badging
as
the
ORAC
name
not
being
used,
and
you
know
by
anyone
on
github
it's
this
kind
of
thing
that
you
know
when
you're
alone,
you
might
spend
the
time
to
do
this.
But
when
you're,
when
you're
working
with
another
person,
you
you
don't
get
too
distracted
into
an
idea
that
sounds
cool
to
you
and
then,
when
you
say
to
another
person,
you're
like
okay,
that
wasn't
really
that
good.
A
A
A
Ob
hat
that's
right:
community
handbook
was
a
topic
that
was
deferred
to
this
week
and
I
am
looking
up
on
the
mailing
list.
I'd
sent
an
email
to
the
mailing
list
about
roles
and
responsibilities
in
the
chaos
project
and
I
did
this.
After
listening
to
the
keys,
the
keepers
ORS
talk
about
succession
planning.
A
A
What
the
different
roles
are,
because
it
will
help
people
coming
to
the
community
to
understand
what
we
do,
how
we
work
and
if
they
are
looking
to
take
on
responsibilities,
they
have
a
some
outline
for
what
they
could
be
doing
and
then
also,
if
one
of
us
disappears,
we
have
documentation
for
what
this
person
or
the
role
that
disappeared
was
doing.
So
we
can
find
someone
else
to
take
on
those
roles
and
we
can
also
start
in
more
clearly
defined
terms,
share
the
different
work
that
is
happening
in
the
chaos
community.
B
A
And
my
question
to
you
is:
what
are
you
doing
in
the
chaos
project
if
it's
already
represented
by
one
of
the
things
in
this
list?
Great
otherwise,
add
it
if
you
think
it's
part
of
our
role,
which
are
the
subheadings
and
add
it
underneath
that
subheading.
Otherwise,
you
can
create
a
new
role
that
we
have
and
they
can't
project.
B
B
A
B
Yeah,
whoever
is
tightening
oh
thanks,
Dirac
I
was
actually
kind
of
digging
through
my
dogs
to
try
to
find
you
know
what
I
want
to
put
under
this.
So
thank
you
all
right.
So
do
we
do
we
keep
those
markdown
files
in
a
particular
repo
about
google,
Summer
of
Code
or
crece
the
actual
proposal
documents
I've
been
just
trying
to
find
that
link
in
my
email,
I
guess
our
governance.
A
B
C
A
C
D
D
Well,
I
I
can
basically
start
with
what
I
try
to
do
at
least
as
a
minimum
activity
which
dialing
into
these
calls,
for
example,
or
at
least
following
the
the
monthly
ones,
just
to
kind
of
making
sure
that
I
as
a
board
member
and
up
to
date,
with
what's
happening
and
I,
think
that
obviously
more
involvement
than
that
would
be
desirable
for
a
board
member,
but
not
necessarily
necessary.
I.
D
D
Basically,
cut
a
little
back
on
on
conferences
in
terms
of
chaos,
but
I
I
think
that
could
also
be
something
that
I
should
look
into
as
a
board
member
I,
don't
know
giving
presentations
or
participating
some
more
activities
and
industrial
events
just
to
kind
of
make
sure
that
we
are
spreading
the
word
about
the
project
and
well
also
did
that
make
sense.
I,
don't
know
how
many
other
board
members
we
have
on
the
ball
and
what
they
think
also
I'm
with
my
Mobile's
I.
D
When
it
comes
to
my
board
members,
that's
more
of
a
higher-level
oversight
of
the
project
as
well,
so
I,
don't
think
that
it
should
be
lets
say
a
requirement
for
board
members
to
get
get
down
to
either
those
coding
level
of
involvement,
although
if
they
are
interested
and
available
to
do
it,
they
should
definitely
going
to
that.
Just
kind
of
I
was
more
brainstorming
around
the
side
of
the
middle
ground
like
what
we
can
expect
and
what
make
sense.
E
B
So
being
that
I'm,
a
new
member
I
thought,
maybe
we
need
that
header
and
I'm,
maybe
now
time
for
that
as
well
at
the
bottom.
You
know
at
least
those
bullet
points.
I
can
make
an
action
not
be
like
I'm,
getting
it
wrong
or
anything.
So
I
don't
know.
If
you
want
something
like
that
to
be
don't
great,
so
I
guess
it
is
rolled.
B
Yeah
catch
up
on
github
and
other
tools
point
if
we
have
a
moment
in
the
end,
like
a
couple
of
minutes
in
the
end,
there's
a
an
idea,
that's
that
floated
regarding
docks.
It
was
simmering
for
a
while
and
basically
finally
came
through
that.
I
just
want
to
bring
the
attention
of
folks
here.
B
So
it's
about
creating.
You
know,
101
docks
that
are
meant
to
be
more
accessible
for
github
and
other
kind
of
things
that
we'll
get
into
at
Fi.
You
know,
after
after
we're
done
with
this,
so
it
just
relates
to
the
catch
up
on
github
and
other
tools,
a
bullet
point
that
I
added
here
anyways.
If
we
have
time
in
the
end,
I
would
like
please,
you
know
a
few
minutes.
That
would
be
great.
A
F
A
B
A
B
F
B
B
B
A
B
So
worker
works
on
the
actual
metric
documents
right.
They
don't
work
on
the
software
that
allows
you
to
analyze
or
collect,
or
whatever
you
do
with
those
particular
metrics.
So
maybe
maybe
we
can
do.
We
have
a
link
for
lemme.
Let
me
just
share
mice:
I,
don't
know
if
you
guys
want
that,
but
I
can
share
this
being
an
EP.
We
can
go
to
a
work
group,
repo
versus
you
know
the
software
repo
would
that
help
demonstrate
it
I.
A
F
For
example,
is
software
maintenance
is
the
same
as
a
matrix,
walking
good
maintain,
because
no
matter
how
we
look
at
matrix,
no
matter,
even
if
it
is
at
the
level
of
still
at
the
abstract
level
that
has
not
yet
been
implemented
by
attaching
the
word
maintainer.
It's
like
you
are
to
me
both
describe
one
and
the
simple
rule.
A
C
Yes,
okay,
hi
I'm,
Lila.
F
F
C
A
B
F
A
A
A
B
But
if
you're,
someone
who
struggles
with
you
know,
visual
learning,
disability
or
you
know
Nero,
you
know
not
your
typical.
Have
you
know
in
your
divergent
kind
of
aspect,
basically
you're,
creating
all
this
stress
that
leads
you
a
sometimes
unable
to
follow
the
same
pace
as
everyone
and
and
then
you're.
You
kind
of
feel
up.
B
You
know
unable
to
stay
on
track
with
everyone
as
they
go
with
the
you
know,
more
typical
rhythm
and
the
other
problem
is
when
you
try
to
communicate
you're
kind
of
trying
to
communicate
things
in
the
more
dominant
language,
which
is
the
more
typical
Lane
would
and,
and
so
I've
been
really
struggling
for
two
years
to
try
to,
you
know,
realize
how
everybody
is
really
trying
their
best.
Everybody
is
really
trying
to
be
inclusive,
but
there
are
going
to
always
be
gaps
or
voids
between
how
everyone
looks
at
the
problem
of
communication
or
miscommunication.
B
I
basically
end
up
getting
links
to
web
development
tools
to
allow
you
to
create
accessible
content,
and
you
know
it
kind
of
felt
like
it's
an
upside
down
concept
here,
because
if
I'm
looking
for
accessibility,
it
makes
more
sense
to
make
sure
the
person
who
needs
the
accessible
Lane
actually
gets
that
Lane,
not
the
person
who
will
create
the
content.
That
would
be
searchable
when
you
use
the
word
accessibility.
So
so,
there's
there's
a
whole
missing
story
for
content
that
is
meant
to
be
consumed
by
different.
B
You
know,
users
who
have
different
capacities
and
just
trying
to
solve
that
problem
has
so
many
unknowns
like
an
expanse
of
unknowns.
That
I
think
most
people
just
freeze-
and
you
know
everyone
wants
things
to
be
more
accessible
but
like
we're,
not
gonna
do
like
everything.
But
what
is
everything?
And
then
you
know
people
start
to
really
hit
that
mental
fuzz
about
okay?
This
is
a
problem,
not
a
solution.
What
do
we
do
so
today?
I
think
the
idea
came
together.
B
A
B
A
B
B
B
B
B
It
is
related,
it
is
related
right
now,
most
MD
files
in
all
open
source
work,
most
communication
in
all
open
source
threads
are
basically
one
style
and
the
whole
idea
of
trying
to
paint
a
picture
of
this
does
not
include
many
people
was
a
very,
very
harsh
path.
Honestly
and-
and
so
this
effort
is
meant
to
basically
be,
let's
take
an
important
document
that
we
have
and
try
to
actually
create
versions
of
it
for
different
kind
of
you
know,
capacity
was.
B
Could
apply
to
everything
so
the
example
I
was
getting
to
it's
it's.
You
know
this.
This,
basically,
is
just
one
example.
So
for
them
basically
for
the
autistic
Self
Advocacy
Network,
they
basically
have
two
type
of
readers
for
their
documents.
Once
we
want
the
verbose
and
once
who
want
really
one,
that
is
more
distilled
that
can
allow
them
to
rely
on
memory
capacity.
B
B
F
Think,
like
you
asked,
this
is
not
except
like
that
you're
on
how
does
this
relate
to
chaos
project
so,
if
in
mind
like
chaos
project
once
we
are
trying
to
harmonize
the
readme
files
to
make
things
Turner,
because
our
focus
is
really
like
on
the
matrixes
and
how
people
will
use
those
matrixes.
It's
not
really
like
our
main
concern
at
this
point
actually
reduces
re
consumers.
D
B
That
is
the
ante
definition
of
inclusivity
in
what
chaos
does
in
who
uses
what
chaos
does
and
not
just
a
US
open
source
in
general.
The
problem
is
escalating
and
that's
why
I
bring
it
to
the
forefront
if
we
create
a
readme
document
that
is
only
going
to
be
accessible
to
certain
majority?
Yes,
it
is
the
majority,
it
is
not
inclusive,
it
is
actually
exclusive
of
the
rest.
You
see
what.
A
I
mean
what
I'm,
what
I'm
hearing
you
say.
Something
is
that
there
are
ideas
that
we
can
use
in
how
we
frame
documents
in
the
cares
project
and
there's
a
conversation
ongoing
right
now
in
the
diversity
and
inclusion
working
group
about
maybe
even
producing
a
metrics
toolkit
that
simplifies
the
metrics
into
more
actionable
but
I
think
some
of
the
design
choices
that
you
showed
us
like,
using
very
simple
language,
removing
all
the
extra
and
having
pictures.
Maybe
we
can
use
those
ideas
in
creating
the
metrics
toolkit
as
on
place
to
implement
your
idea
here.
Yeah.
B
B
You
know
we
can
call
them
different.
I,
don't
know
like
I,
don't
know
what
to
call
it,
but
like
different
capacities
and
and
come
up
with
simple
variations
that
you
could
you
know,
align
with
create
a
set
of
variations.
You
know
this
one
is
easy
to
read
this
one
is
a
screen
readable,
really
screen
readable,
not
just
because
you
know
it
screen
reads
in
the
same.
You
know
format
that
it's
written,
but
rather
it
actually
is
intended
to
read
right.
B
So
so
it's
just
an
idea
and
the
buy-in
to
have
baby
steps
across
more
than
one
project
is
really
going
to
make
this
evolve
into
hopefully
one
day,
something
that
everybody
can
do
and
has
an
idea
how
to
do
right
right
now,
everybody's
waiting
for
someone
to
come
in
with
an
idea.
Let's
do
it
together.
That's
all.