►
From YouTube: D&I.Hangout.November.26.2018
Description
D&I.Hangout.November.26.2018
A
C
A
D
B
C
C
So
initially
you
told
me
we
are
the
monster.
If
there
are
seven
adults
I
can
we
can
actually
doing
at
them
later
and
then
I
got
into
the
Python
there
from
I.
Don't
know
you
were
not
that
in
the
mood
for
having
this
so
I
didn't,
say:
I
didn't
send
anything
at
the
very
end,
but
I
think
we
are
still
in
time.
C
B
No
I
thought
we
should
submit
it
because
I
think
it
would
be
a
great
talk.
I
just
don't
want
to
I.
Don't
want
to
over
commit
myself,
because
with
helping
with
helping
organized
chaos
con
and
submitting
proposals
to
chaos
con
and
then
submitting
proposals
to
the
community
deaf
room,
it
just
seemed
like
it
seemed
like
a
lot,
but
I
I
definitely
want
you
to
submit
it.
If
it's
not
too
late,
you.
C
B
B
B
A
B
Honestly,
no
no
worries
you're.
Just
talking
about
the
positive
proposals.
I
I
did
submit
the
one
to
the
community
Deborah
map.
Annele
I
also
submitted
one
of
my
own
on
coming
up
with
a
metric
strategy.
So
not
not
Addie
and
I
talked
at
all,
but
just
like
in
general,
matching
your
metrics
up
to
your
up
to
your
strategy.
So
I
submitted
I
submitted
both
of
those
and
then
we
were
just
talking
about
Daniel's
proposal
for
the
Python
dev
room
and
we
were
trying
to
remember.
E
C
C
Okay,
let
me
let
me
think,
I'm
they
and
then
I
wouldn't
reach
you
right
by
email,
okay,.
B
E
E
B
D
A
A
E
Don't
I,
don't
know,
what's
useful
for
now
the
way,
the
way
that
I
broke
this
out,
just
it's
kind
of
how
I
start
building
objectives
and
and
cares
I,
don't
know
how
you
all
would
in
the
first
is
like
the
problem
statement
that-
and
you
know
a
lot
of
this
is
like
for
me
talking
about
like
the
work
well
I
arrived
here,
so
it
might
be
quite
right
for
the
group
and
I'm
not
sure
how
to
other
than
to
present
you
with
like
what
I'm
thinking
and
have
you
do
kind
of
proposed
another
way
to
do
it,
and
so
that
was
that
open
source
has
less
diversity
in
tech.
E
Overall,
there's
no
standard
best
practices
for
measuring
success
of
our
interventions
so
basically
like.
Even
if
we
do
things
we
don't
know,
we
might
have
an
idea.
Short
term
like
like
la
didn't,
enjoy
the
project
but
long
term.
We
stopped
tracking
again.
So
there's
never
that
attraction.
That's
that's
my
occurs.
It's
mainly
footnote
without
additional
standards
and
guidance
for
data
metrics
and
ethics.
E
So
that's
where
some
of
those
numbers
came
from
I
think
before
you
get
to
those
ten
partners
might
be
like.
Oh
that's
where
the
kr
is
coming
and
I
didn't
write
any
cares
out
yet
so
I
wanted
to
get
people's
feedback.
Firstly,
if
the
group
agrees
that's
the
right
objective,
then
you
start
writing
the
care
which,
like,
for
example,
might
be.
You
know
we
have
an
agreed
set
criteria.
E
E
So
this
might
be
like
the
open
source.
Architects,
if
you
remember
like
you,
might
want
to
have
a
small
project,
it
might
be
like
you
know,
someone
massive
like
Microsoft
and
they're.
You
know
like
just
happy
to
hear
and
then
you
would
agree
on
the
set
of
criteria
for
the
partnership
and
then
you
would
reach
out
to
them,
and
then
you
know
that
would
all
kind
of
make
the
objective
successfully.
E
It's
like
the
steps
that
you
would
take
to
make
the
objective
happen
you
wouldn't
just
jump
to
like
who
are
those
partners
gonna
be
like
by
the
time
you
you
could
answer
that
question
at
the
end
of
those
keys,
which
would
be
like
based
on
like
who
you
want
to
work
with,
based
on
the
criteria
for
who
they
have
to
be.
Maybe
it's
like
that
they
have
to
commit
to
some
sort
of
ethics
thing
and
that
you've
reached
out,
and
that's
our
thing.
E
A
B
D
B
A
A
B
B
E
C
A
C
C
A
A
A
What
are
we
going
to
do
about
those
ideas
that
I
post
like
issue
101,
no
issue
7
for
maintainability,
clean
and
clear
code
or
issue
a
67,
but
still
test
where
I
just
dropped
in
ideas
for
metrics,
and
we
had
a
conversation
on
them,
but
it's
really
counterintuitive
to
leave
it
open
until
we
decide
to
do
something,
because
once
we
close
it,
it's
like
out
of
sight
out
of
mind,
but
some
of
those
ideas,
I,
don't
think
we
are
ready
to
actually
incorporate
as
a
metric.
Yet.
A
What
was
your
question
there
in
the
issue?
Tracker
I,
sometimes
posted
ideas
for
new
metrics
like
the
maintainability,
clean
and
clear
coat
or
the
pigtailed
test
and
I
just
wanted
to
know
if
we
should
leave
those
issues
open
or
close
them,
because
there's
no
discussion
going
on
keeping
clear
issue
tracker
and
not
losing
ideas.
That's
the
balance.
I
wanted
to
see
what
our
thoughts
are.
C
I'd
say
that
having
open
issue
sees
it's
not
a
big
deal,
so
basically,
if
you
you're
the
owner
of
one
of
those
other
things,
you
have
to
do
it's
a
key
date.
So
hey
I
opened
this.
So
what
do
you
think
remember,
but
we
can
work
on,
is
to
produce
in
a
procedure
to
say:
hey.
There
is
a
new
metric
or
metric
potion
that
is
scientific
to
solve
this
problem.
It's
on
the
table,
so
you
let's
say
we
all
agree
or
there's
some
discussion.
Then
we
can
say
this
seems
to
be
related
to
governance
Princeton.
C
So
we
go
there
and
open
this
there
and
then
perhaps
we
ask
for
more
feedback
in
this
case.
So
let's
say
that
you
are
interested
in
understanding
a
bit
more
about
the
metric
a
and
we
say
hey.
We
believe
that
this
is
part
of
the
governance
thing,
so
we
move
everything
to
do.
The
metric
to
the
whole
focus
area
course
the
matrix
approach
and
say
it
should
be
there.
So
then
we
open
some
discussion
with
you
perhaps
and
say
so.
E
E
Honor
get
some
alignment,
questions
concerns
I'm
what
I've
identified
as
a
problem
statement,
opportunity,
goal
and
risks
and
then
ask
that
if
you
have
time
to
review
it
objectives,
one
into
you
do
during
the
week,
but
then
next
week,
I'll
do
objectives
one
and
two
we'll
talk
through
those
three
and
four
and
then
somehow
leave
room
for
objectives
that
I've
missed,
which
you
might
want
to
propose,
but
that
can
be
a
good
way
forward
and
I
can
tax
it
to
ten
minutes
here.
Just
do
I.
E
What
I'm
trying
to
do
is
drive
this
as
a
set
of
goals
for
2019
right
so
that
you
know
January
2019.
You
look
fly
just
ready
to
start
the
year
and
like
oh,
what
are
our
goals?
Oh
look.
We
have
all
our
goals
outlined
for
the
year,
at
least
like
what
we
think
they
are
now
they
might
change,
and
we
have
some
like
for
each
of
those
goals.
We've
identify
the
steps
we
need
to
take.
E
So
do
we
just
need
to
open
some
issues
like
and
work
on
them,
and
you
know
there's
kind
of
that
and
then
also
so
that's
like
the
the
process
piece,
but
then
it's
also
late.
If
something
else
comes
up
during
the
year
or
during
any
quarter
in
here,
and
somebody
wants
to
work
on
it,
you
can
say
well
what
how
does
this
align
with
our
current
goals?
So
it
also
helps
helps
keep
you
from
straying
too
far
or
working
on
things
that
are
like
many
layers
away
from
the
goal.
E
You're
trying
to
make
like
it's
sort
of
is
a
way
to
focus
as
well.
So
that's
that's.
What
I
propose
I
deal
with
kind
of
like
the
time,
not
that
I'm
forever
going
away,
but
I
will
be
on
these
calls
anymore.
Is
this
something
I
thought
I
could
contribute?
Having
thought
a
lot
about
this?
It's
the
reason
that,
like
you
know,
I
push
for
a
working
group,
and
chaos
like
like
this
is.
A
B
F
Yeah
I
would
agree
with
that
too,
and
I
really
really
like
the
the
whole
notion
of
having
you
know
in
2019.
Here
is
what
we
hope
to
accomplish
right
and
and
and
have
some
real
some
some
focused
areas
where
we're
working
and
and
moving
things
forward.
I'm
one
of
the
things
that
the
Nell
and
I
talked
about
in
Berlin
and
OpenStack
summit
was.
F
E
E
So
it's
also
like
I'm
completely
comfortable
with
it,
but
if
others
have
other
ways
than
that-
and
you
know
it's
just
to
talk
about
that-
hi
like
the
vision
and
then
the
key
results
of
like
reaching
that
that's
objective,
so
an
objective
when
I
sort
of
built
out
a
little
bit
how
it
would
be,
but
I
I
won't
build
out
the
key
results
for
the
objectives
until
I've
got
more
feedback
from
all
of
you,
as
as
part
of
that
so
I'm.
Looking
at
the
time,
maybe
just
ask
I'll
start
with
a
prop
I'm
gonna.
E
Do
the
problem
statement,
opportunity
goal
and
risk,
and
maybe
I'll
just
ask
you
to
alter,
read
those
four
headings
and
what's
underneath
them
and
then
to
go
ahead
and
add
some
like
comments
and
then
then,
after
about
five
minutes,
I'm
gonna
ask
people
to
like
verbalize
their
comments.
Does
that
sound
like
a
good
way
to
go
about?
It
is
instead
of
it
just
being
discussion.
E
A
E
E
E
Well,
I
was
suggesting
that
you
all
read
the
problem
statement,
opportunity,
goals
and
risks
first,
and
but,
if
you
so
and
then
what
then,
the
objectives
just
are
coming
from
those
so
okay,
but
if
you
did
both
that's
fine,
okay,
I
would
just
try
not
to
take
up
too
much.
Time
was
the
reason
I
was
trying
to
like
okay,
like
not
the
objectives,
but
before
that
in
the
rest,
schools,
opportunity
or
promising.
What
does
anyone
have
any
thing
they
like
to
verbalize
that
they've
written
here
otherwise
later
I?
Think.
B
D
B
It's
gonna
be
hard
for
us
to
make
sure
that
this
work
fits
in
with
the
goals
of
the
project.
I
mean
getting
aid,
some
of
your
risks
down
there
yeah,
but
I
do
think
we
should
we
we've
kind
of
mentioned
it
a
few
times
and
never
actually
quite
teed
it
up
for
a
discussion
and
the
like.
The
formal
chaos
meeting,
but
I
think
we
need
to
have
a
little
more
something
about
the
overall
goals
of
the
project
and
make
sure
that
those
are
clearly
stated
because
I
don't
feel
like
they
are
I
feel
like
I'll.
G
Chime
in
on
that,
yes,
please
yeah
so
I
mean
and
that
this
is
a
it's
a
totally
fair
point
and
it's
something
we
can
bring
up
for
the
board
meeting
and
I
think
it's
definitely
worth
bringing
up.
But
you
know
I
think
when
the
Charter
was
put
together
ash
a
while
ago,
but
maybe
we
didn't
quite
know
what
the
goals
were.
We
kind
of
knew
this
vague
our
sense
of
community
health,
and
maybe
we
want
to
kind
of
take
a
look
at
this
and
move
it
forward.
G
B
It's
perfectly
natural
that
we'd
be
in
this
state,
given
when
the
project
was
formed
and
how
the
working
groups
formed
and
kind
of
everything
you
just
said.
So
it's
not
it's
not
a
criticism
of
the
project
at
all.
It's
just
that
we're
now
at
a
state
where
we
have
multiple
working
groups
that
are
really
active,
and
we
probably
should
clarify
the
goals
of
the
overall
project,
just
to
make
sure
that
everyone
is
working
in
the
same
direction.
Yeah.
E
E
E
A
E
B
B
E
G
F
E
G
I'll
do
that
it's
not
a
problem.
It's
a
very
sensible
approach
to
me,
irrespective
of
how
people
feel
about
things
yeah.
This
is
the
we
have
we
have
to
as
a
project
as
the
cash
project
recognize
the
work
that's
being
done
and
if
we-
and
if
we
fail
to
do
that,
then
we're
really
not
a
project
that
is
recognizing
the
work,
that's
being
done
project,
so
it
doesn't
make
any
sense
to
me.
I
think.
E
F
Mm-Hmm
I
need
to
I
need
to
walk
that
thing
to
school,
but
I
wanted
to
to
a
note
here.
I
figured
a
help
that
some
of
the
comments
I
was
making
it's
because
I
got
labels
under
open
source
birthday,
and
that's
me
just
on
them,
and
it's
only
because
my
account
is
linked
to
a
blog
and
podcast
theory
and
so
apparently,
I
was
signed
in,
but
not
to
the
ride
account
anyway.
No
I
know
yeah
I've
noted
where
that
happened.
I've
noted
my
name
next
to
it.
F
A
F
E
C
The
first
of
them
that
I
was
not
sure
if
there
was
a
real
risk
about
the
couch
board,
not
recognizing
the
work
we
are
doing,
but
it
seems
that
the
feeling
of
us
is
basically
that
this
might
be
a
risk.
So
comment
stir
so
I
resolve
my
own
comment,
and
everyone
knows
about
using
the
the
world
silos
that
I
really
like
in
the
problem
statement.
C
So
I'm
kind
of
reinforcing
this
in
front
of
the
true
the
problem
here
is
how
to
be
transparent
in
the
sense
that
we
do
have
all
of
this,
but
at
the
same
time
not
to
harm
people.
So
basically
I'm
saying
again
the
same
so
I
basically
agree
with
all
of
the
writers
to
distress.
Might
to
my
two
comments.
A
Thank
you.
So
one
of
the
observations
I
have
is
the
problem
statements
especially
focused
on
work
done
in
communities
and
to
see
if
they
are
being
effective
and
with
a
chaos
project
as
a
whole.
I
sometimes
get
the
sense.
It's
also
a
lot
about
taking
a
look
at
a
project
as
an
outsider
and
understanding
the
health.
E
E
B
E
E
A
E
Because
I
have
down
here
this
whole
thing
about,
like
we,
we've
worked
with
10
open
source
projects.
You
know
apply
this
metrics,
but
yeah.
That's
a
good
point.
I'll
I'll
include
that,
because
right
now
you
know
I
mean
the
stories
help,
but
people
don't
understand
how
to
use
it
out
of
the
gate
like
there's
those
use
cases.
Ok,
so
I
I'm,
just
gonna
stop
this
year.
So
please
do
like
add
in
your
comments.
E
A
C
B
C
C
C
F
A
B
C
B
A
G
So
the
third
discussion
today
about
Emma's
email
from
whatever
Friday
or
with
the
24
contributions,
all
right
but
I,
think
that's
a
huge
deal.
So
I
I
mean
from
my
perspective,
it
starts
putting
this
work
into
practice,
which
is
it
I
think
it
appears
to
be
one
of
the
hard
parts
of
the
chaos
project.
It
appears
to
be
a
hard
part
for
any
of
these
types
of
projects
that
are
trying
to
specify
the
ways
we
understand
data
so,
for
example,
the
SPD
X
project
I
think
this
was
a
challenge.
G
It
was
easy
to
talk
about
how
they
understood
licensing
and
copyright,
but
to
have
other
groups
put
those
efforts
into
practice.
That's
a
whole
nother
request,
so
I
think
that
the
24
contribution
stuff
is
a
huge
potential
minute
to
actually
see
some
of
this
work
from
the
DNI
work
group
captured
by
another
project.
G
I'm
actually
having
a
discussion
with
some
folks
from
Red
Hat
here
in
the
week
and
I
would
love
to
propose
something
like
this
for
their
groups
as
well
or
the
communities
that
they
work
with,
but
I'm,
not
quite
sure
where
I
would
point
them
or
what
mm.
Oh,
you
had
suggested,
like
maybe
five
fairly
simple
things
to
capture.
Maybe
you
didn't
say
5,
but.
E
E
E
You
know
he
wanted
to
find
a
way
to
capture
non-technical
contribution.
So
I
asked
him
to
put
on
like
basically
put
on
the
website
this
checklist,
and
he
said
he
would
I,
don't
know
that
he
was
putting
it
out,
but
what
he
he
asked
or
I
haven't
seen
his
he's
the
copy
of
what
he's
doing
it
so
I,
actually
don't
I,
don't
know
how
he's
even
envisioning
that
checklist
where
it's
gonna
go.
I
know
what
I'm
envisioning,
maybe
a
lineup.
Okay,.
G
E
E
That's
totally
what
sorry,
if
that
sounded
different
yeah,
that
we're
encouraging
it's
like
hey,
sumo
who's,
our
support
people
who
have
helped
people
on
Twitter
record
your
contributions,
and
this
this
thing
and
then
you
know
they
might
get
highlighted.
That's
part
of
like
duty
contributions,
not
as.
G
Duty,
so
how
does
a
work
from
the
DNI
from
the
work
group
here?
Are
there
perhaps
a
couple
different
contributions
from
those
focus
areas
that
you
might
want
to
put
forward
because
any
of
you
put
forward
I
think
this
was
your
point.
If
you
put
forward
all
six
focus
areas
and
say
here
capture
all
these
things
in
a
gun
hub
repository,
they're
gonna,
be
like
ya,
know:
ya,.
E
Know
what
I
was
going
to
do
was
I
have
to
actually
finish
writing
this
text.
Maybe
I'll
send
it
all
to
you
all
mm-hmm
afterwards,
I
was
the
check.
I
was
gonna,
propose
like
five
things,
because
we
just
talked
about
it
being
short,
because
I
showed
you
a
checklist
that
I
have
that's
longer.
It's
just
like
you
know.
E
Does
the
code
of
conduct
have
a
way
to
report
like
as
a
as
an
inclusive,
any
bug
contribution
those
can
come
from
each
of
the
focus
areas
like
maybe
there's
one
for
events,
one
for
governance,
one
for
communication,
I
can
maybe
I'll
just
share
a
document
with
you
all,
but
I
do
have
to
turn
get
invited.
A
I
think
there's
a
song
even
if.
E
G
B
G
Love
that
and
doing
it,
like
you
said,
is
a
green
square
and
I
I.
Think
one
of
the
things
are
that
raises
is
we're
gonna
have
to
think
about
how
we
captured
this
work
in
relation
to
the
current
projects.
Yeah
we're
not
gonna
change
that
workflow
and
github
is
just
a
structure.
They
define
a
lot
of
the
workflow
yeah.