►
From YouTube: CHAOSS.D&I.April.22.2019
Description
CHAOSS.D&I.April.22.2019
B
Welcome
to
the
chaos
diversity,
inclusion,
working
group
meeting
on
April,
22nd,
Eastern
Monday.
The
agenda
right
now
is
pretty
light.
We
didn't
know
who
else
would
be
here
because
we
have
Easter
holiday
in
some
areas.
So,
right
now
we
have
review
action
items
and
then
determine
next
week's
facilitator.
Note-Taker
I
think
we
can
also
talk
about
the.
B
A
B
B
A
Check
in
with
Nicole
to
just
to
you
know,
since
we're
getting
close,
we
might
want
to
have
a
touch
base.
Call
you
know
months,
maybe
Danielle
myself
and
Nicole,
and
we
can
talk
about
any
research
we've
done
or
any
people
we've
talked
to
and
just
move.
You
know,
make
sure
we're
all
prepared
for
that.
Mm-Hmm
yeah
sounds
good,
did
Nicole
reach
up
to
you
know
so.
I
can
I'll
make
sure
to
connect
with
her.
C
D
B
A
A
A
A
Okay,
oh
no!
Actually
you
were
on
the
email
thread,
though
okay
Matt,
so
you
mustn't,
miss,
asked.
A
So
I
guess
the
next
step
is
just
officially
submitting
it
right
and
you
release
okay
and
did
we
I
think
I
picked
either
next
fall
is
when
we
would
try
to
get
this
activated.
You.
B
A
E
D
So
kind
of
two
things
on
that
on
my
end,
I
had
sort
of
the
community
bridge
I
do
have
a
request
out
to
who
is
it
I,
don't
know,
okay
put
me
in
touch
with
somebody
who
does
the
dollars
at
the
ELA,
because
we
have
some
money
from
google
Summer
of
Code
last
year,
and
so
the
hope
was
is
that
we
could
just
move
those
dollars
to
the
community
bridge.
E
A
D
D
B
Okay,
the
next
action
item
was
to
send
out
double
of
completeness
exercise
results
to
the
general
cast
meaningless
and
what
we
have
decided
as
the
working
group
to
focus
on
to
reach
consensus
there
and
I've
done
that
feedback
was
really
good
and
other
working
groups
have
expressed
interest
in
copying
our
approach
or
tweaking
it
a
little
bit.
So.
D
D
It
was
just
to
add
tabs
for
the
other
working
groups
that
just
follow
the
same
model,
so
that
was
so
point
being.
Thank
you
very
much
for
putting
that
together.
It's
gonna
serve
as
a
nice
template
for
the
other
working
groups
to
identify
metrics
as
part
of
the
release.
One
and
number
two.
It's
gonna
make
my
life
a
lot
easier,
because
there's
going
to
be
a
central
place,
that
identified
metrics
for
release
will
be
located
as
opposed
to
across
all
working
groups.
Mm-Hmm.
A
B
B
A
So
the
editor
is
reviewing
it
and
it's
gonna
just
make
some.
They
want
it
to
be
a
little
bit
shorter,
so
I
think
they're
going
to
do
a
slight
edit
and
tweak
that,
but
then
share
it
with
you,
for
you
know
before
it
goes
to
final
publication,
and
then
the
editors
also
are
interested
in
having
people
on
the
podcast
to
help
promote
the
article,
and
we
kind
of
like
the
idea
of
trying
about
the
article,
as
well
as
the
upcoming
coupon,
talk
on
that
because
believe
it's
a
20-minute
segment
on
the
podcast.
A
E
E
A
B
A
A
C
A
A
D
D
So,
okay,
so
the
basically
the
premise
for
the
day
is
to
give
the
participants
an
opportunity
to
work
on
some
development
skills
and
contribute
to
a
project,
so
chaos
being
the
project.
So
the
thought
was:
is
there
anything
from
the
grimore
lab
side
or
from
the
augur
side
that
is
related
to
DNI,
that
we
could
ask
the
students
to
work
on
during
that
day?
You
know
like
like
a
panel
or
an
interface
component
or
a
data
component.
F
C
D
D
Put
maybe
we
could
just
do
it
right
now
in
the
minutes,
can
you
just
drop
a
sentence
or
two
on
what
those
things
might
be?
I
just
I
need
them,
because
there's
a
Google
Form
application
that
I
have
to
submit
we're
Grace,
Hopper
and
again
it's
just
kind
of
an
orienting
and
if
I
need
more
information,
I'll
reach
out
to
both
of
you
directly,
but
what
that
might
look
like
not
in
the
chat,
if
you
could
just
put
it
in
the
minutes.
F
D
C
C
D
C
D
C
B
C
C
C
F
F
D
F
D
For
the
hug
right
is
I,
have
the
grimore
live
ideas?
What
a
Grace
Hopper
thing
like
I
said:
I
got
it
I
got
but
I'll
get
these
in
and
then
I
know
that
they
had
said.
If
we
could
just
get
these
ideas
roughly
in
to
the
system.
Now
we
can
modify
them
of
course,
over
the
course
of
summer
to
be
a
little
bit
more
fine-tuned
to
the.
D
A
B
This
is
one
of
the
metrics
we
had
identified
during
our
level
of
completeness
exercise
as
one
that
we
want
to
advance
and
add
to
the
repository
for
our
release,
but
we
don't
have
it
right
now.
We
have
some
ideas
here
in
this
document,
and
so
the
proposal
is
that
we
review
the
proposal
right
now
and
Sarah
I
see
that
you
made
some
comments.
Maybe
we
can
talk
about
them.
A
Yeah,
let
me
pull
it
up
here,
like
one
of
all
is
definitely
around
the
fact
that
you
know
that
these
organized
google
Summer
of
Code
Zoar
mentorship
programs
tend
to
have
some
formal
sort
of
marketing
and
promotion
or
awareness
around
them,
but
sponsorship
can
often
be
kind
of
under
it,
not
purposely,
but
it's
not
always
as
noticeable
or
obvious
or
formalized.
So
I
think
when
it
is
happening,
though,
it's
great
to
try
to
capture
that,
and
you
know,
talk
about
the
ways
in
which
sponsorship
is
happening
and
is
helpful
and
is
beneficial.
A
A
That
was
one
thing
and
then
the
other
idea
I
had
that
I
thought
could
be
really
interesting.
To
add
to
sponsorship
was
around
as
a
metric
on
objective.
You
sort
of
capture
that
obviously,
or
one
of
the
things
we
hope
happens
with
sponsorship-
is
that
people
stay
engaged
in
a
project
and
take
on
bigger
leadership,
roles
or
new
leadership
roles
and
grow
in
within
the
project.
So
should
that
be
a
sample
objective,
but
maybe
that's
too
specific,
but
that
was
one
idea.
I
had
is
something
to
consider.
A
A
B
A
Know
two
projects,
you
know
I
mean,
maybe
you
do
it
out
of
obviously
a
lot
of
times
people
volunteer
not
for
to
receive
accolades
and
get
recognition,
but
it
is
taking
someone
under
your
wing
is,
it
can
be.
You
know,
takes
time
effort,
energy.
Maybe
it
goes
on
more
under
the
radar
and
unrecognized,
but
I
didn't
know.
If
there's,
we
would
want
to
promote
the
idea
of
sponsorship
and
who's
engaged
in
that
who
you
know
who's,
doing
it
really
effectively
and
actively
I
think
that
would
be
good
yeah.
B
B
B
B
F
C
Yeah
so
babe
I've
been
reading
about
the
difference
between
a
sponge
for
some
mentors,
I
think
I'm
more
or
less
understand
the
difference,
but
in
the
same
way
that
we
have
mentors
in
a
community
and,
for
instance,
network
some
of
code
and
so
on.
There
are
people
in
charge
of
helping
other
people
to
be
promoted
and
understand
and
participate
in
the
community,
and
because
these
they
are,
for
instance,
reviewing
those
people
called
I.
Guess
sponsors
may
have
a
similar
role
when
we
are
talking
about
specifically
contributions
right.
C
B
I'm
not
an
expert
on
this.
My
understanding
is
that
sponsors
are
less
involved
in
the
technical
aspects
of
contributing
they're,
more
involved
in
providing
opportunities
and
saying
hey.
We
have
this
task
on
coming
up
and
mice.
Prodigy
could
take
on
some
roles
in
helping
along
and
to
open
up
opportunities
in
the
community.
I,
don't
know
if.
B
A
Guess
some
I
didn't
necessarily
differentiate
between
it.
Had
the
nature
of
the
help
or
the
you
know,
the
coaching
or
the
guidance
would
be
technical
or
non-technical,
but
that
it
it
would
in
my
mind
it
would
be
less
formalized
and
they
said
you
know
sponsored
in
the
Protege
didn't
necessarily
formally
go
through
like
a
google
Summer
of
Code
or
a
community
bridge
or
any
typical.
You
know
University
internship
program,
but
that
it
was
happening
a
little
bit
more
organically.
But
maybe,
but
maybe
there
is
a
differentiation
between
the
technical
and
non-technical
too.
A
B
A
C
G
We
decided
to
stay
away
from
when
we
were
writing
the
diversity
reports
for
OpenStack.
We
decided
to
stay
away
from
the
technical
versus
non-technical
language,
because,
just
because
you
may
not
be
contributing
code
or
writing
lines
of
code
doesn't
necessarily
mean
that
your
not
technical,
so
yeah
and
there's
been
some
discussion
in
the
community
too
around
that.
So
we
decided
to
be
a
little
more
specific
in
calling
it
code
contributions
versus
non
code
contributions
right
that.
B
The
the
mentor
can
be
anyone
even
from
outside
the
community
who
shares
skills
in
formal,
unwritten
rules
and
make
suggestions
for
the
mentee
where's.
The
sponsor
gives
the
Protege
access
to
their
own
network
and
basically
pulls
them.
Maybe
we
can
think
of
it
as
a
push
install
where's
the
mentor
pushes
the
mentee
choose.
B
A
A
And
maybe
it's
something
that
we
all
take,
isn't
it
if
she's
written
or
spoken
about
it
and
we
can
find
the
talks,
maybe
a
few
of
you
know.
Anyone
actually
on
the
working
group
could
try
to
take
the
time
to
familiarize
themselves
with
it
a
little
bit
and
then
we
might
be
able
to
have
a
more
coherent
discussion
around
it.
You
know
I
need
to
decide.
A
B
A
A
C
C
Then
it
happens
that
during
the
last
comment,
there
is
a
lot
of
discussion
around
cultural
change
and
communities,
marketplaces
and
and
tooling
and
processes,
and
so
on,
but
there's
little
discussion
about
specifically
diversity
and
inclusion
DNA.
So
it's
it's
a
topic.
I
would
like
to
bring
to
the
today
no
short
comment,
but
as
a
first
try,
we
are
having
this
small
meta
inner
source
pain,
which
is
taking
place
co-located
with
in
with
kid
complicated
during
the
same
days
in
keep
control.
I
know
that
Nicole
she
mentioned
that
she
will
Joan.
C
Sarah
would
be
great
if
you're
around,
if
you
think
this
is
interesting,
I
would
love
to
hear
it
from
you
to
be
part
of
perhaps
more
presentation
around
how
to
be
internal
communities
and
then
the
good
hand,
perhaps
point
of
view
from
Intel
in
this
case
like
well.
We
have
this
and
this
is
our
attention
and
then
your
roller
perspectives
are
in
terms
of
well
the
Linux
foundations.
We
are
working
in
this
areas,
which
is
core
it's
not
a
company
or
internally
at
the
company,
but
you
are
bringing
different
source.
A
C
That's
the
URL
so
far
we
we
have
I
was
looking
for
a
couple
of
yours
cases,
but
I
think
it's
a
good
opportunity
for
DNI
the
work
we
are
doing
to
say:
hey.
We
are
doing
this
and
we
think
this
is
very
important
for
building
communities
either
they
are
in
open
source
or
internally
after
annotations
and
I
would
say
that
through
our
expertise,
specifically,
your
expertise
are
in
Nicole
might
be
useful.
So
I
know
think
about
this.
Absolutely.