►
From YouTube: CHAOSS Weekly Hangout.November.20.2018
Description
CHAOSS Weekly Hangout
A
B
I
wonder
if
we
should
talk
a
bit
about
the
decision
model
and
this
thing
that
has
raced
in
the
Middle
East
with
respect
to
the
communication
methods
for
the
best
innovation
working
group
or
whether
we
should
below
discuss
it
into
the
mailing
list,
just
avoid
having
a
you
know
a
site
discussion
here.
What
do
you
think
I.
A
It
could
feel
like
it's
set
in
stone
once
it
gets
posted
as
a
summary
to
the
mailing
list,
and
so
I
don't
know
how
to
make
sure
that
everyone
on
the
mailing
list
knows
that
hey
this
conversation
is
still
ongoing
and
you're
also
welcome
to
participate
in
join
in
this
and
decision
making
process.
So
that's
that's
one
thing
I
see
as
an
issue.
B
So
I
think
that
up
to
now,
I've
been
working
basically
on
consensus,
and
that
could
be
a
good
good
thing
to
keep
my
person
is
that
usually
the
meetings
like
this
called
are
for
talking
and
based
on
this
talking,
some
proposals
came
out
and
in
some
cases
some
idea
of
we
have
a
consensus
on
this.
Maybe
the
only
trouble
is
to
consider
that
people
not
joining
the
conversation
in
the
cold,
for
any
reason,
agree
with
that.
B
So
my
personal
said:
if
we
frame
the
results
of
discussions
in
this
called
as
proposals
for
the
rest
of
the
people,
we
can
just
see
whether
in
the
mailing
list
people
agree
or
not,
if
they
don't
say
anything
at
all,
while
they
agree,
that's
fine.
We
have
a
consensus.
Always
we
can
go
on
with
the
discussion
either
in
the
main
list,
or
even
in
a
specific
color,
or
something
like
that.
B
C
Everyone
can
attend
the
meetings,
not
over
ones
present
every
single
every
single
day
on
the
mailing
list,
and
so
we
do
need
to
get
people
time
to
kind
of
turn
through
things
and
and
get
feedback
and
make
make
decisions.
And
it's
yeah.
It's
easy
to
fall
into
the
trap
of.
Oh.
We
decided
that
just
because
a
group
of
us
did.
D
D
A
C
E
E
E
The
use
of
discourse
are,
we:
are
we
talking
about
work
groups
being
able
to
use
it,
or
are
we
talking
about
moving
the
entire
community
to
the
discourse?
If
we're
talking
about
work
groups
being
able
to
use
it,
then
I
think
just
at
the
works
groups
decide
individually.
I
think
there
needs
to
be
some
clarification.
There,
though,.
B
So
one
of
the
things
that
I
think
we
need
to
decide
is
whether
every
working
group
can
decide
everything
they
want,
or
there
is
some
common
rules
for
the
who
Kallstrom
it
up
to
now.
Honestly,
I,
don't
think
we
never
discussed
that,
and
groups
have
had
a
lot
of
autonomy
and
every
good
attitude.
Basically,
they
said
oh
we're
going
to
do
this
and
that's
it
so
nobody
object.
B
Maybe
this
is
the
first
time
that
we
are
trying
to
raise
the
discussion
to
the
whole
Kev's
community,
some
extent
and
honestly,
I,
don't
know
this
balance
between
autonomy
and
having
some
kind
of
common
rules.
It's
almost
difficult
in
communities
and
I,
don't
know
so
I
would
like.
I
would
like
to
have
some
kennels
where
I
know.
I
can
be
informed
of
everything
that
happens
because
in
many
cases
I
can
not
participate
in
the
discussions,
but
I
like
to
know
what's
happening.
C
B
D
It
almost
sounds
like
we
need
some
sort
of
platform
where
we
and
any
sort
of
decision
that
comes
up
in
discussions
with
the
community
can
just
be
posted.
You
know
one
like
say
just
going
back,
sorry
I'm,
sorry
to
bring
this
up
again,
but
to
go
back
to
the
discourse.
We
could
have
some
sort
of
thing
that
is
posted.
That
says
the
community
wants
to
move
to
discourse,
do
you
agree
and
people
can
like
upvote
or
downvote,
and
and
that
would
give
you
consensus
on
items.
B
In
general,
it
will
start
to
do
something
similar
to
voting.
We
need
to
discuss
who
has
to
write
the
boat
and
that
ends
in
in
a
difficult
decision.
So
that's
why,
in
general,
I
prefer
consensus
is
the
for
acceptance.
In
some
cases
you
can
not
reach
consensus,
and
apparently
for
that
we
have
the
board.
B
C
A
B
But
maybe
in
the
Middle
East
we
can
have
two
separate
discussions.
First,
try
to
clarify
this
idea
or
for
whether
everybody
agrees
on
train
consensus
as
much
as
possible
and
considering
the
decisions
made
in
the
course
and
so
on,
assess
proposals
for
bases
that
people
in
the
Middle
East
can
also
say:
I,
don't
like
that
or
whatever,
and
try
to
find
out
whether
we
really
have
to
consensus
and
stick
into
the
board
as
the
last
resort
foreboding
if
needed.
B
If
at
some
point
that
doesn't
work,
we
can
try
to
find
out
as
as
been
suggested,
other
ways
of
holding
by
having
some
people
with
voting
rights
and
stuff
like
them
and
I.
Don't
know,
maybe
that's
something
that
we
could
even
devote
some
time
to
discuss
in
the
next
count,
so
that
we
can
have
a
more
open
discussion
of
a
base.
But
for
now.
C
A
B
A
If
we
do
it
in
a
separate
tool,
then
we
don't
have
the
history,
but
there
are
some
cases
where
anonymous
boating
is
needed,
and
then
we
can
revert
to
other
tools.
No
yeah
I,
like
the
proposal
to
make
everything
we
discussed
on
these
calls
a
proposal
and
make
that
clear
in
our
submarines
that
this
is
only
a
proposal
and
also
the
way
we
talk
about
it
on
the
calls
that
we
keep
in
mind
hey.
This
is
not
the
whole
community
deciding
right
now.
B
In
any
case,
there
was
one
proposal
and
I
think
we
didn't
implement.
That
was
having
something
like
the
first
meeting.
Every
month
is,
let's
say
the
formal
meeting
so
that
we
may
have
an
agenda
and
items
to
talk
about
and
so
on,
and
even
when
the
decisions
are
not
made,
people
mean
well.
This
item
is
going
to
be
talked
about.
B
I
can
say
before
that
in
the
million
days
opinion,
if
I
can
not
you're
in
the
cold
or
after
I
can
contribute,
with
my
opinion,
vulgar,
but
people
may
know
that
of
all
the
meetings
every
month.
The
first
one
is
mostly
for
talking
about
anything
that
could
need
a
decision
when
the
others
are
most
for
sharing,
and
that
could
also
make
a
difference,
because
if
you
need
to
really
talk
about
that,
maybe
you
can
do
an
important
join
the
meeting.
If
that's
important
for
you,
and
maybe
that
way,
we
can
get
more
involved.
A
Those
first
first
Tuesday
of
the
month
meetings,
those
are
always
well
attended
and
I.
Think
you
have
a
good
point
there,
that
by
having
the
agenda
and
letting
him
want
to
know,
know
in
advance
that
we
want
to
come
to
consensus
on
a
topic
and
that
if
they
cannot
attend,
please
talk
about
it
on
the
mailing
list.
A
B
B
Okay,
I
wanted
to
serve
with
you
what
we
are
doing
in
the
gym,
the
working
group.
Yes,
will
you
to
know
very
quickly?
The
most
interesting
thing
that
I
think
that
we
are
doing
is
collecting
the
use
cases,
so
those
are
pull
requests
and
issues
in
the
in
the
repository
for
the
working
group.
It
would
be
great
if
you
can
have
a
look
at
them.
B
Have
a
look
at
the
procedure.
The
procedure
is
in
the
directory
use
cases
of
the
repository,
and,
if
you
look
at
the
procedure
is
basically
starting
with
an
issue
or
we
should
be
collecting
commands
based
on
a
description
of
the
use
case
and
everybody
having
any
interest
in
using
metrics
or
an
experience
in
using
metrics
in
using
metrics
can
submit
a
use
case.
Use
cases
are
specific;
they
don't
need
to
be
generic,
or
something
like
that.
B
B
The
idea
is
that
the
group
tries
to
find
out
the
metrics
that
would
help
with
that
and
that's
the
way
of
completing
the
use
case
and
then
with
those
matrixes
what
or
what
we
are
going
to
use
for
the
rest
of
the
working
group
activity
in
all
of
the
focus
areas.
So
if
you
have
any
area
of
a
use
case,
that
could
be
interesting.
B
Just
came
a
not
in
an
issue,
even
if
it
is
just
a
test
that
people
I
and
other
people
are
going
to
help
you
to
convert
that
into
you
and
to
our
use
case.
And
second,
we
are
starting
to
visit
all
the
focus
areas,
starting
with
code
development.
So
if
you
have
any
stake,
hold
on
that
and
you
want
to
contribute
somehow
with
ideas
or
something
else,
just
cam
and
again,
we
have
an
issue
for
discussion
cam
and
doing
the
discus
and
that's
all
I.
A
Think
the
approach
makes
perfect
sense
to
me
and
in
doing
the
DNI,
a
call
yesterday
paper
also
briefly
think
about
use
cases
or
user
reports
or
something
that
that
sounds
very
similar
to
what
you're
doing
and
the
chain
from
developing
from
the
use
cases
down
to
the
metrics
and
through
the
questions.
And
that
just
makes
sense
to
me.
So
yeah
I've
been
following
that
and
I
like
what
you're
doing.
B
A
A
So
after
the
conferences,
we
have
been
a
little
slow
and
continuing
our
work,
but
we
still
have
more
resource
pages
to
complete
they're.
All
they
all
exist,
as
is
using
our
github
right
now
and
as
Google
Docs
to
start
working
on
it.
The
main
conversation
we
have
right
now
is:
what
is
it
that
we
want
to
do?
What
are
our
next
steps?
One
of
the
reasons
is
that
emma
is
reducing
her
involvement
next
year,
and
so
we
want
to
figure
out
how
be
as
a
group
are
going
to
move
forward.
C
Only
other
thing
we
talked
about
was
we
worked
on
finalizing
some
proposals
for
DNI,
for
Kaos
Khan
and
for
the
FOSDEM
community.
Deaf
room
and
I
think
I
think
we're
also
gonna
submit
Daniel
has
a
talk
for
the
Python
community,
deaf
room
about
diversity
and
inclusion
in
the
Python
community.
It's
a
redo
of
a
talk
that
he
did.
It
I
think
something
more
more
local.
So
it
looks
like
those
are
things
we're
gonna
submit
around
paws
down
for
for
D&I.
A
One
of
the
one
thing
that
I
shared
yesterday
during
our
DNI
meeting
is
that
I'm
conducting
interviews
with
people
from
the
open
source
ecosystem
about
DNI
metrics
and
that
those
interviews
are
producing
some
really
interesting
insights
that
we
haven't
thought
about
before.
One
of
them
is
sponsorship
in
open
source
project
and
I'm,
not
talking
about
sponsorship
in
terms
of
money,
but
people
sponsoring
other
people
similar
to
mentorship.
But
this
mentorship,
you
only
provide
guidance.
You
show
where
resources
are.
You
help
push
through
problems
with
sponsorship.
A
The
sponsor
actually
puts
their
reputation
on
the
line
and
helps
promote
their
sponsee
and
brings
them
up
in
conversations
and
tries
to
give
them
more
responsibilities
within
the
community
because
they
want
to
advance
them
and
help
them
move
along
in
the
community.
So
that
is
something
that
came
out
of
my
interviews.