►
From YouTube: CHAOSS.Diversity&Inclusion.February.4.2019
Description
CHAOSS.Diversity&Inclusion.February.4.2019
C
A
B
A
A
Well,
that
the
agenda
for
today
is
what
about
the
chaos
cone.
Specifically,
chaos
come
to
toriel
previous
it
and
update
the
code
for
2019,
and
if
we
get
some
feedback
from
chaos
corner
for
stem
update
on
last
week's
action
items
that
will
we
have
some
notes
after
this.
So
I
guess
that
Georg
and
some
others,
you
you're,
really
updated
II.
So
thank
you
very
much
review
core
contributors
in
terms
of
the
list
and
basically
we
have
a
set
of
pull
requests
and
issues
that
we
typically.
If
we
have
time
for
these,
we
will
review
them.
D
E
A
A
A
B
A
So
then
it's
it's
my
site,
okay,
great,
so
well,
hello!
Everyone
thank
you
for
coming
yep,
so
the
capitulation
of
chaos
gone
and
forced
them,
I
think
I'm.
The
only
one
that
attended
both
places
so
I
will
ever
do
a
small
interaction.
So
on
Friday
we
had
the
chaos
scone.
We
had
around
58
in
this,
and
then
we
had
some
specific
topics
on
gender
and
diversity
that
we
had
the
working
group
during
the
afternoon
and
for
approximately
an
hour.
A
So
the
goal
of
that
session
was
to
split
the
people
attending
the
conference
into
four
or
five
groups
basically
filled
one
of
the
templates
that
we
are
using
for
following
all
of
the
all
of
the
discussions.
Try
as
you
are
you
hear
what
we
are
proposing
in
general
and
here
Andy
and
the
other
working
groups
is
to
follow
specific
methodology,
which
is
this
case
focus
areas.
Then
we
define
specific
questions
and
then
we
define
certain
metrics
related
to
this.
A
A
Here
in
the
chat
so
right
there,
this
is
the
repository
I'm
talking
about.
If
you
go
through,
this,
you
will
see,
like
in
admit,
meet
me
document
that
there
is
meant
to
expose
area.
So
each
of
those
focus
areas,
if
you
click
in
each
of
them,
so
you
can
go
to
event
diversity.
You
will
see
a
set
of
questions
that
were
related
to
specific
name,
so,
for
instance,
in
the
event
diversity,
we
have
things
like
speaker,
demographics,
these
demographics
diversity,
access
tickets,
code
of
conduct
at
events
or
family
friendliness
right
for
each
of
them.
A
A
What
we
did
was
basically
to
say:
okay,
so
let's
split
the
people
and
then
let's
work
on
the
specific
areas,
so
I'm
adding
here
another
example
what
I
mean
so
this
is
the
Google
dot
for
communication
in
to
see
with
Yun.
Listen,
we
in
project.
It
was
quite
interesting
because
we
got
the
people
displayed
into
groups,
so
we
had
groups
from
one
people.
There
I
remember
one
person
up
to
well
when
two
persons
up
to
six
seven
and
we
were
working
in
five
main
area,
so
we
have
as
the
example
communication
inclusivity
listening.
A
A
A
So
we
were
working
in
in
each
of
the
area
so
by
coming
back
to
discussion
before
so.
What
we
are
defining
here
is
a
description.
We
want
to
work
on
sample,
objective,
sample
strategies,
success,
metrics
and
some
resources.
If
there
are,
if
there
are
some
and
then
at
the
very
end,
what
we
did
was
we
need
to
add
ourselves
as
participants,
because
we
want
to
have
everyone
recognized
right
as
part
of
the
other
group.
A
A
Those
were
the
the
issues
that
Tom
Foster
assigned
to
herself
during
the
last
week.
So
I
think
it
was
contribution,
sentiment,
perhaps
perceived
value,
communication,
inclusivity,
listening
speaking
and
captioning.
I
think
those
were
the
five.
So
those
those
are
the
representation
that,
in
the
presentation
we
have
the
links
in
it.
So,
okay,
I'm,
looking
for
the
chaos
cone,
okay,
this
is
there
so.
A
My
perhaps
what
happen
is
that
we
asked
the
people
to
feel
elected
I
booked
a
lot,
but
they
were
working
on
some
other
document.
So
that
might
be
the
issue
here.
But
what
we
are,
but
we
are
going
to
do,
is
as
I
think
I
know
all
of
the
people
involved
in
the
five
groups.
We
will
try
to
reach
them
again
because
we
have
we
had
indeed
at
the
very
end
three
minutes
presentation
presentation,
each
of
for
each
of
the
five
groups.
So
we
have
five
presentations
at
the
end.
A
Yeah,
so
this
was
mainly
a
recapitulation
of
chaos
control
we
have
at
least
from
the
50
people.
Perhaps
I
know
30
40
of
them
well.
30
may
be
working
them
because
at
the
very
end
that
this
was
at
the
very
end
of
the
days
or
some
people
left
and
so
on,
but
yeah
okay,
so
this
is
all
from
Kaos
Khan
I
didn't.
If
you
have
some
specific
comments
about
this
okay,
then
you
reinforce
them.
I
have
to
say:
I
didn't
have
the
time
to
attend
any
of
the
talks
of
the
community
track.
B
C
A
A
A
B
A
A
A
A
C
C
A
The
only
feedback
related
to
this
group
that
I
had
to
engage
converse,
they've
done
already
proud
in
terms
of
they
are
the
IRC
channel,
but
we
had
people
that
didn't
even
know
that
we
had
an
IRC
channel.
In
some
more
cases
they
were
to
use
for
google
Summer
of
Code
student,
so
all
the
others
they
I'd,
the
general
IRC-
cares
IRC
channel.
But
this
is
including
this
group,
of
course,
but
that
was
all
thank.
B
A
A
E
E
Okay,
yeah
I
was
actually
looking
at
the
gold
with
a
fresh
eye
on,
because
I've
been
working
on
the
readme
file
and
we've
been
we've
been
wanting
to
work
across
the
workers,
the
the
growth
maturity
decline,
worker
and
the
ad
and
I
work
group
and,
and
they
see
weekly
fires.
More
consistent,
I
was
I
was
actually
just
just
looking
at
a
the
gold
document.
E
B
E
So
if
you
look
at
the
top
of
this
page
in
this
Google,
Doc
and
I
was
I
was
basically
comparing
in
outline
form
and
further
along
in
the
dog,
feel
free
that
I
grabbed
some
of
the
content,
so
I
went
into
the
repo
in
the
foot
for
the
growth,
maturity
and
decline.
Workgroup
I
said
something
along
the
lines
of
advancing
our
readme
file
and
if
you
look
at
github
for
the
growth
maturity
and
decline,
workgroup
its
current
structure,
I've
list
listed
at
the
top.
E
E
So
introduction
mailing
lists
meetings
and
so
on
and
then
right
below
that
I
have
what
my
findings
were
after
comparing
and
contrasting
to
two
readme
files.
So
there
was
a
difference
in
some
of
the
sequencing.
So
a
lot
of
the
items
were
similar
eated
work
for
the
same
in
terms
of
fun
what
they
were
in
both
readme
files.
There
was
some
difference
in
their
ordering
or
their
sequencing,
and
then
there
were
a
few
differences
in
what
the
gross
security
declined.
E
Yeah,
it
seems
like
a
nice
leader,
you
know
seems
like
a
nice
way
that
we're
handling
that
we're
we're,
I'm,
acknowledging
and
and
I
will
let
everybody
know.
I
have
not
been
back
to
been
with
any
of
these
findings.
Yet
I
wanted
to
have
this
discussion
with
our
group
first
and
but
I
was
going
to
propose
that
as
a
suggestion.
E
The
last
people
of
certain
portfolios
here
or
what
were
or
kind
of
what
was
them
include,
did
so
in
one
is
not
the
other.
So
what
is
not
currently
in
an
Arduino
file
or
in
the
D&I
readme
file,
but
is
in
the
in
the
GMD
movie
file
is
usage,
and
let
me
explain
with
one
of
the
reasons
that
I
listed
the
content
as
I
was
going
to
read
it.
It
was
helpful
to
me
and
I
was
hoping
it
would
be
helpful
to
to
others
as
well
I'm
when
they
say
usage.
E
So
the
usage
area
of
their
a
readme
file
is
essentially
how
they're
using
the
repository
itself
on
the
discussion
forum.
I
was
thinking
yeah,
they
have
a
discussion
forum,
implementations,
the
implementation
hasn't
been.
The
implementations
in
the
youth
kisses
haven't
necessarily
been
filled
out
yet
and
I
think
that
statement
is
actually
more
true
for
the
implementation
section.
So
I
wasn't
able
to
glean
too
much
from
that
yet
and
in
the
license,
I'm
included
in
our
in
in
the
DNI
readme
file,
and
not
yet
in
theirs,
was
roadmap
for
2019
software
work
and
related
works.
E
Based
on
that
and
I
will
tell
you
before
I
dive
into
the
proposed
structure
based
on
that
and
with
the
emphasis
of
inviting
others
to
join
the
DNI
workgroup
and
participate
with
us.
I
I
then
came
up
with
his
proposed
structure,
even
in
light
of
all
of
what
I
just
talked
about
it
and
then
with
the
Infosys
of
inviting
others
like
that.
Okay,
well,
introduction
and
background
made
sense,
and
then
he
focuses
made
sense
on
I
think
we
will
really.
We
already
have
that
right
and
I
was
thinking.
B
E
Honestly
need
to
dive
into
that
a
little
bit
further
to
see.
You
know
how
would
it
be
different
in
terms
of
key
focuses
on
what
I
what
I
am,
but
here's
my
just
coming
from
my
perspective,
is
that
I
I
think
we
need
to
get
folks
to
how
they
can
contribute.
You
know
to
giving
them
if
I
think
about
and
I
know.
A
lot
of
us
are
aware
of
Jonah
Bacon's
work
and
I'm
if
I
think
about
some
of
the
beacons
that
he
shares
or
best
practices
with
he
shares.
E
E
We
need
to
get
get
and
give
them
an
overview
and
get
them
given
what
they
need
to
know
and
then
get
them
there
pretty
quickly
to
some
concrete
ways
that
they
can
start
to
to
dive
in
and
contribute,
which
is
why
in
bullet
number
four,
you
see
that
I've
moved
contributing
it
up
in
the
sequence.
Then
I've
moved
it
further
up.
E
B
So
right
now,
if
I
imagine
this
new
readme,
we
have
a
short
introduction
and
then
you
reiterate
some
of
it
in
the
background
and
right
now
the
background
I
have
to
scroll
several
times
before
you
can
get
past
that
and
then
we
have
down,
focuses
and
then
how
to
contribute
I
think
maybe
we
can
shorten
the
background
or
move
the
background
into
the
background
into
further
down.
Maybe
because
I
fully
agree
with
you,
we
want
to
get
people
the
information
on
that
they
need
to
contribute
so
I
think
moving.
E
E
Provide
a
combination
of
two
and
three,
and
it
provides
you
I'm,
just
brainstorming
at
this
point,
but
provide
you
with
a
snippet
right
of
the
information
enough,
make
it
sufficient
enough
so
that
folks
Graci
information
and
get
enough
information
to
understand,
what's
going
on,
give
them
how
to
contribute
and
and
and
provide
them,
either
a
link
to
information
further
down
in
the
document
right,
so
so
kind
of
provided
in
a
nutshell,
with
learn.
More
use
me
I'll,
learn
more
so
that
if
they
wanted
more,
they
could.
A
I'm
wondering
care
or
chemical
so
as
it
seems,
there's
some
controversy
or
the
kind
of
things
we
can
have
in
the
in
the
rig
me
file.
One
of
the
things
we
can
do
if
you
want
so
would
be
to
move
the
conversation
to
offline.
So
we
try
to
have
some
discussion
through
I.
Do
not
what
do
you
prefer
issues
or
mailing
lists?
B
A
A
A
About
this,
for
for
a
few
minutes
or
a
few
more
minutes
any
case,
perhaps
regarding
to
your
question,
what
we
can
do
is
to
have
two
or
three
for
questions
that
we
want
to
ask
the
community
so
in
the
main
list
and
then
basically
try
to
have
answers,
or
or
at
least
to
have
some
discussion
there
before
before
Monday.
So,
for
instance,
it
comes
to
my
mind
time.
Perhaps
these
are
really
directed
questions
internally,
directed
in
the
meaning
of
having
a
question
that
is
trying
to
die
to
address
the
expected
answer.
A
A
Or
perhaps
we
can
have
this
Britany
file
and
split
the
readme
file
into
several
sections,
and
those
would
be
basically
the
structure
of
the
DNI
working
group,
but
it
would
try
to
ask
these
kind
of
things
and
any
we
want
to
go
to
a
specific,
let's
say
the
content
of
what
we
have.
Then
we
can
go
for
photos,
questions
set
all
of
these
I
believe
that
to
accuracy
is
something
great.
So.
B
Yeah
I
personally
prefer
a
one
pager
for
the
readme,
the
gold,
because
it
is
a
separate
document
in
itself.
I
think
we
can
separate
that
out,
but
otherwise
I
prefer
having
everything
here
and
I'm
perfectly
fine
with
having
one
week
now
to
comment
on
the
Google
Doc
and
going
back
and
forth
there
about
ordering
and
because
that's
what
you're
doing
right
now
equal
right.
The
order.
E
E
A
Okay,
so
then
I
think
we
can.
We
can
come
back
to
this
discussion
if
we
have
containment
at
the
end.
So
the
meantime
we
can
go
to
the
next
item.
We
have
thank
you
for
for
all
of
the
discussions,
so
we
have
here
so
we
have
more
notes
like
where
we
have
it
Oh.
Yet
the
disclaimer
about
PR,
perhaps
care
you.
May
you
may
want
to
say
something
here,
but
the
nippori
questions,
one
yeah.
B
So
I
already
posted
the
link
to
the
pull
request
in
the
agenda
and
the
meeting
minutes,
and
it's
a
one-line
change
that
I
made
because
we
added
some
time
ago,
the
hate
contributor
versus
unpaid,
volunteer
contributor
has
a
demographic
information
and
he
had
talked
about
how
this
information
might
be
misunderstood.
About
welcoming
a
community,
yes
and
so
I
added
this
one
line,
basically
saying
that
he.
B
A
A
A
B
C
B
C
B
A
So
we
can
send
to
the
mainland
list
first
of
people
that's
great
and
regarding
two
contributors
in
general,
PD
above
having
their
work.
Interesting
on
at
kcon
was
to
want
to
have
people
involved
and
they
have
contributed.
So
we
have
to
add
them
the
specific
area
of
the
contributors.
So,
first
we
would
need
to
look
food
to
fill
the
other
document,
so
this
is
probably
and
something
we
can
or
I
can
try
to
do
to
recover.
A
A
A
A
G
F
D
Hyper
ledger
in
general
has
a
diversity
and
inclusion
problem
and
chaos
is
a
project
that
we
want
to
work
with
to
help
advance
our
goals
and
help
advance
the
goals
of
chaos,
and
that
doesn't
sound
quite
right
to
help
advance
the
group's
goals
so
I'm
the
community,
the
one
of
the
community
architects
for
Michael
enter,
and
this
aligns
with
my
goals
as
to
you
know,
increase
our
diversity
and
inclusion
and
figure
out
how
we
can
do
better.
So
that's
why
I'm
here
I.
G
Should
say
too
that
there,
you
know
hyper
ledger,
isn't
necessarily
unique
in
this
challenge,
and
the
LF
in
general
is
hoping
that
some
of
our
projects
become
more
active
in
Cass
and
works
with
the
KSR
group
and
we're
sort
of
designating
hyper
ledger
as
like
a
pilot
for
us
to
really
try
to
integrate
with
the
work
you're
doing
here.
And
then
you
know.
G
C
C
A
B
D
D
G
You
yeah
from
thinking
about
hyper
ledger
and
other
project
system.
Lf
I
would
love
for
I,
know
some
of
the
goals
that
we
seek
use,
cases
and
examples
and
early.
You
know,
pilots
and
prototypes
and
have
projects,
use
our
tools
and
that's
my
goal
to
see
projects
like
hyper
ledger
and
others
within
that
sort
of
orbit
are
aware
of
chaos,
DNI
and
the
work
that
we're
doing
and
want
to
sort
of
volunteer
and
be
early
prototypes
and
use
case.
Examples
that
would
be
my
I
think
that'd
be
a
great
goal
Wow.
That
would
be.
E
G
E
Love
that
I
love,
that
and
and
I
for
one
just
want
to
welcome
right,
well,
welcome
you
to
the
group
and
is
excuse
me
I
recovering
from
a
cold,
obviously,
but
I'm
it's
great
to
have
you
here
and
I,
just
want
to
chime
in
with
what
Sarah
is
saying
it
would
be,
would
be
great
to
do
to
do.
Some
of
that
word
that's
be
awesome.
A
So
my
experience
from
that
analysis
was
that
it's
a
good
starting
point
understand
where
you
are
right
now
in
terms
of
well
zero
numbers
like
from
a
positive
perspective,
but
from
a
political
perspective
as
well,
in
the
sense
of
understanding
what
people
think
about
how
how
inclusivity
is
right
now
how
inclusive
the
community
right
now
in
in
per
layer.
This
is
something
we
are
still
we
what
we
still
want
to
do
in
the
penstock
case,
but
it
might
be
something
really
useful.
E
E
We
we
wanted
to
get
behind
those
numbers
and
and
to
do
it
was
going
to
take
some
some
qualitative
researcher
diving
into
some
of
the
sub
projects
on
to
figure
out
what
what
could
be
done
to
to
to
fill
those
gaps.
So,
in
fact
one
of
our
research
reports
actually
delineated.
What
was
what
we
found
as
recommendations
for
what
could
be
done
and
we
started
to
implement
on
some
of
those.
E
Request
to
the
mailing
list
for
review
of
the
proposed
structure
for
our
readme
file.
I
will
circle
back
with
them
on
the
growth,
maturity
and
decline
workgroup
to
let
him
know
where
we
are
in
the
progress
and
in
the
process
and
then
I.
My
my
hope
would
be
that
we
get
to
a
point,
hopefully
by
next
week,
where
we've
got
a
proposed
structure
and
and
can
begin
to
roll
up
some
of
the
content
into
that
proposed
structure
and
update
our
weekly
file.
E
Thank
you,
yeah
and
then
I'm
also
I
also
have
an
eye
on
the
the
open
source
leadership
from
it
in
March
I
can
see
if
we
can
get
I
we.
You
know
we
submitted
a
session
there
and
I,
don't
know
when,
when
implicit
or
when
acceptances
are
being
extended,
but
I
am
crossing
my
fingers
that
we've
got
a
session
that
we'll
be
presenting
on
there.