►
From YouTube: CHAOSS.D&I.Jan.20.2020
Description
CHAOSS.D&I.Jan.20.2020
A
A
A
It's
in
its
early
stages,
but
you
know
early
and
early
feedback
is
good
and
then
the
outreach
chief
program,
so
we
haven't
until
sometime
in
February
to
kind
of
set
on
a
series
of
projects,
but
I
have
started
the
outreach
II
proposal
and
a
meeting
with
sage
sharp
on
Thursday
get
a
little
bit
more
insight
on
the
outreach,
II
project
and
just
kind
of
how
chaos
can
be.
You
know
better
trying
to
participate
in
that
project.
Yeah.
A
C
C
C
A
A
So
we'll
talk
about
that
all
right.
So
so,
if
you
take
a
look
at
the
minutes,
if
you
click
on
the
DNI
issues,
so
you'll
see
that
Kevin
has
thank
you,
Kevin
posted
all
of
these
issues
for
the
different
metrics
and
just
as
a
reminder.
Some
of
these
metrics
were
part
of
the
first
release,
but
we're
also
we
can
also
look
at
them
again
and
then
a
set
of
the
metrics
are
part
of
the
second
release,
so
you're.
A
What
you're
seeing
here
is
the
entirety
of
all
DNI
metrics,
as
part
of
as
part
of
the
issues
and
I
think
the
biggest
thing
is.
We
had
also
done
the
new
templates
like
for
all
the
working
groups,
so
I
my
hope
is,
is
that
we
can
just
kind
of
work
through
these
two
four
six,
eight
nine
today,
and
maybe
we
could
just
start
with
issue
two
61,
which
is
release
candidate
comments
for
sponsorship.
A
C
B
D
D
D
B
Oh
sorry,
I
interrupted,
but
I
do
think.
That
is
actually
the
important
distinction,
because
and
I
think
that's
what
makes
these
programs
less
less
formal
than
than
mentorship
programs,
because
it
really
is.
It
really
is
sort
of
an
individual
who's
established
in
the
project
going
to
bat
for
someone
who's
not,
and
so
you
can't
really.
B
You
can't
really
put
programs
around
that,
because
I
can't
be
like
I'm,
not
gonna,
take
on
some
random
person
and
put
my
reputation
on
the
line
for
somebody
that
that
I,
don't
even
know,
is
part
of
some
program,
but
you
can
help
people
encourage
them
to
do
that,
for
for
people
that
they
are
willing
to
sponsor
people
that
they're
willing
to
get
to
know
and
put
the
reputation
on
the
line
for
mm-hmm.
It
feels
it
feels
more.
C
D
C
Okay
and
then
number
four
is
the
one
that
really
relates
to
our
ambiguity
or
our
sense
of
ambiguity
about
the
you
know:
the
formality
of
sponsorships
or
the
relevance
of
them.
To
be
entirely
honest.
The
first
time
I
heard
about
sponsorships
was
in
the
meeting
where
I
ended
up
hearing
sponsorships,
so
I
always
thought
there
were
mentorships,
and
then
you
know,
I
I
never
really
heard
about
sponsorships
and
open
source.
A
This
is
the
first
that
that
is
the
first
link,
the
yeah
I'm
going
by
the
number
No.
So
a
number
of
number
four
yeah
I
need
to
stop.
Acting
like
members,
I
mean
that's
this.
That's
this
reference
right
here
so
I
mean
it
does
start
the
yeah,
so
I'm
not
outside
of
the
differentiation
between
sponsor
and
mentor
I'm,
not
hearing
a
lot
and
I.
Don't
think
that
it
sounds
like
this
has
been
a
fairly
well
thought-out
metric.
I.
A
E
A
A
C
C
C
C
A
A
C
C
A
C
A
E
E
B
A
C
Stand
alone,
I
believe
so
yeah.
The
second
part
like
it
applies
in
diversity
and
inclusion.
I
think
everything
applies
in
diversity
and
inclusion
at
some
point,
because
you
know
open
source
is
like
people
in
code.
So
if
it's
not
just
code
that,
then
it
would
have
diversity
and
inclusion
components
to
it.
Right
I
mean.
A
A
D
I
think
is
completely
fine,
but
would
it
would
it
be
helpful
to
add
a
kind
of
a
disclaimer
sentence
that
says
something
to
the
effect
of
mentorship
is
like
this
document
is
framed
as
a
diverse
as
a
diversity
inclusion
issue.
However,
mentorship
is
a
metric
that
can
be
measured
for
yeah,
common
or
sure
I.
D
C
Collaborators
or
something
like
like
any
aspect
of
a
project
that
has
to
do
with
you,
know
tracking,
for
a
collaborator
to
join,
to
be
part
to
evolve
and,
to
you
know,
move
on
I,
think
I,
don't
know.
Maybe
I'm
not
aware
of
the
particular
word
roots
enough,
but
it
seems
to
be
a
very
specific
like
it's
the
people
aspect
of
the
project.
I,
don't
know
yeah
I,
guess
we're
still
warming
up
for
2020
and.
A
D
C
B
That
it
comes
up
a
lot
actually
when
we're
defining
the
metrics
and
a
lot
of
times
to
find
ourselves
defining
a
metric
instead
of
defining.
The
diversity
includes
your
aspect
of
that
metric
and
it
does
really
kind
of
overlap
with
all
of
the
work.
So
that's
something
that
we
yeah
I
think
we
struggle
with
all
all
the
time
when
we're
defining
the
DNI
metrics.
D
D
A
C
A
C
I
mean
it's:
it's
a
good
point.
If
you're
printing
this
as
a
book
that
you
know
this
will
be
part
of
your
folio
or
like
your
header
or
footer,
the
head
or
whatever,
they
call
them
and
print
it
forget
like
when,
when
you
double-click
in
Word,
then
you
put
the
page
number
so
usually,
when
you
print
a
book,
you
put
the
chapter
and
the
section
texts
somewhere
in
your
quarters
over
here.
It's
basically
the
breadcrumbs
that
you
see
on
github.
C
They
make
it
very
clear,
you're
in
the
DNI
repo.
You
know
it's
implied,
but
I
guess
are
there
other
views
for
that
metric
on
the
website?
Maybe
you
know
that
we
want
to
make
sure
there's
a
a
bread
crumb
or
a
trail
or
a
header
or
footer
or
whatever,
that
that
kind
of
indicates
that
you
you're
in
the
DNI
part
of
this
world,
just
for
visibility,
yeah.
A
Why
don't
can
we
table
this
discussion
until
the
next
time
and
so
Kevin?
That
would
mean
that
don't
add
the
statement
yep,
so
I've
made
a
few
notes
just
kind
of
on
my
own
pad
of
paper
here,
let's
just
table
that
until
we
get
through
this
release,
so
the
next
one
is
code
of
conduct
for
a
project.
I
also
think
that
this
was
part
of
the
last
release.
Kevin.
A
C
A
A
A
A
C
D
C
A
This
is
a
small
issue
and
not
one
that
I
want
to
solve
now,
but
every
now
and
then
our
descriptive
haven't
noticed
the
descriptions.
Our
text
narrative,
the
objectives
are
often
text
narrative,
but
every
now
and
then
we
go
back
and
forth
with
bullet
points.
There's
just
a
tiny,
tiny
bit
of
inconsistency
throughout
the
metrics,
I'm,
afraid
I
can't
I,
don't
know
I'm
not
gonna
at
the
time
this
week
to
track
all
that
down
and
rewrite
these,
but
it's
just
something
we
want
I
want
to
keep
on.
This
is
probably
it's.
A
A
B
A
A
Again,
probably
day
to
Kevin's
point,
I
actually
thought
in
the
first
release,
the
DNI
working
group
was
honestly
one
of
the
most
thoughtful
groups
in
terms
of
putting
together
the
metrics,
so
I
think
that
a
lot
of
these
initial
relief
you
know
they're
released
in
version
1
are
gonna,
be
pretty
solid,
just
return
plated
where
no
text
was
lost.
All
right,
I'll
make
that
change,
family
friendliness,
adversity,
access,
tickets,
again,
small
comment
on
me:
resources
versus
references
at
the
bottom.
E
A
A
Great
so
I'll
make
those
changes
like
I,
said
I'll
just
ping
a
few
of
you
on
the
pull
request,
but
you
should
see
a
lot
of
them
are
just
kind
of
structural
issues
and
just
some
some
wording
things
here
and
there
and
that's
great
in
the
release
notes.
This
is
something
that
I'm
supposed
to
be
doing.
Do
we
have
engine?
A
D
A
A
A
A
A
Okay,
so
Matt
has
been
working,
those
of
you
they
don't
know.
One
of
the
the
big
issues
is
across
all
working
groups
is
how
do
we
develop
these
metrics,
as
you
saw
here
in
text
form,
and
then
how
do
we
get
them
to
actually
be
implemented
in
practice
or
actually
you
know
change
the
way
that
people
understand
community
health
and
certain
metrics
are
perhaps
a
little
bit
more
inclined
for
that.
A
So
the
metrics
and
evolution
may
be
a
little
bit
easier
to
deploy
because
they're
asking
things
around
issues
or
pull
requests
trace
data
that
we
can
get
oftentimes
from
from.
You
know,
Birgit
lab
different
repositories.
The
DNI
metrics
are
naturally
a
little
bit
more
challenging
because
they
don't
really
have
that
type
of
data,
so
they
require
a
little
bit
more
human
effort.
So
what
Matt
has
been
working
on
is
a
way
to
take
a
look
at
badging
around
diversity
and
inclusion.
A
Diann
eyes
a
little
bit
harder
to
do
this
with
so.
The
idea
here
is
the
the
project
is
say,
going
to
run
an
event
and
they
would
like
to
badge
their
event.
They
would
like
to
do
DNI
badging
for
their
event,
so
they
would
come
to
github.
This
would
all
be
done
out
in
the
open
completely
publicly
in
a
repository,
and
they
would
put
in
a
request
to
receive
a
DNI
badge
for
their
event.
Whatever
that
event
might
be,
the
badge
is
based
on
for
an
event
Matt.
What
what
metrics
were
you
using?
E
A
The
review
of
that
would
then
occur
publicly
so
say
salah.
You
submitted
an
event
that
said
hey.
We
would
like
to
receive
a
DNI
badge
and
we
have
an
event
code
of
conduct.
We
are
family-friendly,
we
monitor
attendee
demographics,
we
monitor
speaker
demographics
and
we
provide
diversity
access
tickets.
You
you
make
the
claim
that
you
do
all
of
these
five
things
right,
and
so
it
give
me
a
DNI
badge
for
the
event.
A
In
this
case,
we'd
have
to
have
reviewers
a
little
like
academic
papers
and
I'll.
Just
get
done
so
dawn
would
actually
be
a
reviewer
for
your
claims.
So
you
would
provide
a
link
to
the
code
of
conduct
for
the
event.
Don
would
take
a
look
at
it
and
say:
yeah,
that's
a
very
reasonable
code
of
conduct
for
an
event.
I
approve.
She
would
take
a
look
at
your
claim
of
being
family
friendly
and
she
may
say:
actually
you
you.
The
statement
that
you
provide.
A
Has
nothing
to
do
with
family
friendliness,
so
I
don't
actually
approve
that.
Why
don't
we
kind
of
work
on
something
that
could
kind
of
demonstrate
that
family
friendliness
a
little
bit
more
clearly
for
your
event
and
so
on
and
so
forth
down
the
list?
So
the
intention
here
is
to
be
as
projects
are,
applying
for
a
badge
for
their
project
themselves
or
for
an
event
that
this
is
a
very
open
and
transparent
process
by
which
you
receive
the
badge.
Does
this
make
sense.
A
E
C
E
C
A
D
E
Yeah,
just
a
second
so
I'm
going
to
go
to
a
new
issue
and
like
if
I
go
to
an
advanced
submission.
I'm
asking
these
are
just
kind
of
questions.
I
pulled
out
of
the
metric
at
this
point,
but
I'm
asking
for
more
like
does
what?
What
event
was
that
host
a
code
of
conduct
and
a
bunch
of
stuff
about
the
website
for
a
lot
of
metrics,
because
that's
publicly
available?
E
But
then
there's
some
questions
were
asked
more
demographic
based
information,
like
how
many
speakers
identify
with
each
of
the
racial
backgrounds
listed
on
your
events,
demographic
survey
and
that's
not
questions
I'm,
not
sure.
If
these
questions
would
be
relevant
as
much
as
it
is,
I
just
need
to
find
out
that
they're
measuring
the
metrics
that
we
provide.
D
A
So
Salah
the
initial
workflow
again
it's
to
do
it
out
in
the
open
right.
So
you
would
instead
of
like
event,
submission
project
submission.
It
would
be
no
be
request,
event,
badge
request,
project
edge,
and
so
you
would
get
started
on
either
one
so
just
yep,
and
so
you,
as
the
requester
of
the
badge,
would
fill
out
the
issue.
A
So
you
would
change
the
project
name
and
so
I
what
I?
What
I
kind
of
envision
happening
here
is
really
just
attending
to
the
metrics.
The
DNI
has
released
with
respect
to
events
and
projects
and
I
think
that
sometimes
Matt,
the
level
of
detail
you
have
here,
maybe
might
be
too
too
detailed,
so
I
think
sometimes
you
could
just
ask
like
what
you
know.
Can
you
provide
a
link
to
your
event?
Code
of
conduct
period?
Okay,.
E
A
E
A
You
collecting
attendee
demographics
and,
if
so,
how
and
perhaps
you
know,
do
you
report
these
numbers
I'd
something
along
these
lines?
Are
you
providing
family
friendliness
at
your
event?
If
so,
could
you
describe
the
process
and
provide
a
link
to
how
you
demonstrate
this
family
friendliness
so
that
make
sense
Sala.
A
C
C
Yeah
all
right,
yeah
cos,
because
the
template
itself,
like
I,
wish
github
issue
templates,
actually
allowed
you
to
say,
listen,
there's
no
box,
there's
like
fields
that
you
fill
out
and
we
just
you
know,
put
that
stuff
together
in
a
well-structured,
markdown
format.
You
know
this
way
I,
you
know
it
doesn't
have
to
be
exotic
forms.
Just
you
know,
just
a
name
for
everything
you
enter
and
and
whether
or
not
you
need
to
enter
it.
C
C
A
C
So
what
I've
been
thinking
about
every
now
and
then
is
well
if
you
have
a
github
repo
with
issues,
you
just
need
a
very,
very
dumb,
no
framework
web
form
that
basically
uses
the
github
API
is
to
open
the
issue
on
their
behalf
and
take
you
to
the
issue
once
it's
built
in.
You
know
it's
on
my
original
idea,
like
the
idea,
I've
seen
I
think
implemented,
at
least
with
some
JavaScript
tools.
They
give
you
you
know
in
their
in
their
demo
in
their
web
demo.
C
Oh
it
just
the
issue
and
then
from
Gera
it's
a
regular
issue.
They
go
get
a
really
tight.
Okay,
III
think
it
just
it's
it's
sugaring
as
they
call
it
in
JavaScript.
You
know
you
just
say:
okay
remove
the
manual
interaction
with
the
box,
but
you
might
as
well
just
manually
interact
with
the
box.
If
you
want
yeah,
okay,
yeah
I'd
be
willing
to
you,
know:
I
I'm,
just
trying
to
find
something.
I'm
good
at
and
I
can
contribute
with
yeah.
C
E
C
A
At
the
moment,
all
right
I'll
do
the
one
with
a
fork
I
like
that
one,
okay,
so
the
biggest
one
of
the
I
think
getting
this
working
is
going
to
be
a
process
in
itself.
The
other
real
concern
that
I
have
with
this,
and
something
just
to
think
about
is
it.
It
will
require
reviewers.
So
there's
a
human
component
in
here
that
is
necessary.
A
So
you're
I
mean
it's
a
little
like
academic
papers
and
you're,
asking
for
people's
time
to
contribute
to
the
review
of
a
project,
submission
or
an
event,
submission
I
think
the
bar
is
fairly
low
because
there's
not
a
ton
of
metrics,
you
don't
I
mean,
and
some
of
them
are
probably
pretty
straightforward.
So
it's
just
something
that
I
have
on
the
back
of
my
mind,
so
I
think
if
we
really
do
move
forward
with
this,
we're
gonna
have
to
think
well
beyond
the
chaos
project
in
terms
of
folks
who
would
be
willing
to
provide
editorial.
D
C
A
B
D
C
C
A
Is,
oh,
is
that
everybody
who
submits
for
a
badge
whether
for
their
project
or
for
their
revenge,
can
go
through
a
constructive
process
by
which
they
can.
They
can
ultimately
receive
that
badge.
But
again,
that's
that's
more
work
right.
So,
if
somebody
has
a
bad
code
of
conduct-
and
that
takes
effort
for
somebody
like
you
know,
gone
to
point
out
what
a
good
code
of
conduct
might
look
like
and
how
they
might
go
about
kind
of
integrating
that
into
their
event,
it's
just
it's
time.
So
the.
A
Process
all
along,
but
I
do
firmly
believe
that
it's
it's
things
like
this
that
are
going
to
be
needed
at
times
to
get
the
DNI
metrics
into
concrete
form
and
to
get
them
to
have
meaning
in
the
world.
So
all
right,
so
that's
that's
that
it.
This
is
the
first
look
at
this
I'm
gonna
I'll,
be
at
Kaos
Khan
I
have
my
whole
talk.
Is
on
this.
So
a
lot
of,
hopefully
there's
a
lot
of
feedback
on
the
chaos
Khan
on
this
and
few
things
to
show
ya.
A
All
right
so,
like
I
mentioned
briefly
just
in
the
last
five
minutes
here,
the
Outreach
II
program
there
I
do
have
a
couple
DNI
projects,
you
remember
Google
Summer
of
Docs.
Remember
when
we
put
together
a
couple
proposals
for
Google
Summer
of
Docs
anybody
there
were
a
few
that
came
out
of
DNI
I'll,
have
more
information,
probably
on
this
later
I.
Don't
have
a
ton
to
say
right
now,
other
than
I've
started
the
proposal,
and
then
the
other
thing
is
I
did
receive
that
some
of
the
conference
data
from
the
Linux
Foundation.
A
A
Not
just
you
know,
gender
related
issues,
so
the
nod
who's
not
on
here-
has
has
kind
of
worked
through
some
of
that
data
and
I
shared
it
back
with
with
Angela.
So
I
I'm
excited
to
share
it
with
everybody.
Here,
I'm
gonna,
just
kind
of
logistic
I'm
gonna,
wait
for
Angela
to
kind
of,
say,
okay,
but
so
that
process
is
now
occurring
and
the
other
cool
thing,
as
we
have
some
of
this
data
for
the
most
recent
conferences
and
it's
now
something
that
we
can
start
setting
timelines
against.
A
Well,
we
have
four
minutes
timing.
If
you
want,
if
we
want
to
change
the
time
of
the
meeting,
I
am
completely
more
than
happy
to
do
that.
I'm
generally
quite
available
except
Mondays,
honestly
outside
of
Kay
other
chaos,
meetings
and
Mondays
and
Wednesdays
from
10:30
to
11:45,
US
central,
basically,.
A
E
B
Might
be
worth
doing
another
doodle
poll?
Why
don't
I
do
that,
because
the
the
last
poll
that
we
did
I
think
to
move
this
meeting
I
think
part
of
the
problem?
Was
they
just
kind
of
counted
the
numbers
and
didn't
really
take
into
account
the
people
who
are
most
active,
mm-hmm
and
actually
attending
and
so
I
think
we
with
the
doodle
poll.
We
probably
need
to
prioritize
some
people
more
than
others.
Why.