►
From YouTube: CHAOSS Weekly Hangout: April 24, 2018
Description
CHAOSS Weekly Hangout: April 24, 2018
A
B
A
A
D
A
I'd
like
to
talk
a
little
bit
about
the
work
groups
and
I
can
give
an
example.
Lillico
is
not
gonna
be
in
an
Coover
I
had
reached
out
to
her
to
see
if
she
would
like
to
participate
as
well,
but
she
and
I
will
just
talk.
Out-Of-Band
and
I
think
kind
of
get
an
update
on
what's
going
on
with
the
work
group
at
the
time,
specifically
with
OpenStack
Danielle,
but
then
I
think
the
focus
is
to
really
hone
in
on
the
growth,
maturity
and
decline.
E
F
Yeah
I
mean
I
one
of
the
things
that
I
remember,
because
I
mean
this
is
gonna,
be
part
of
the
I
mean
they
change
the
name
like
a
community
track
right.
Community
related
track
that
John,
oh
Bacon's
running
I
mean
if
they.
If,
if
the
pattern
repeats
itself
I
think
last
year
there
were
like
what
Jonna
was
saying
was
that
there
would
like
record
number
of
submissions.
Okay,.
B
F
Have
to
turn
a
lot
of
things
away,
I
mean
so
I
think
one
of
the
things
that
I'm
finding
is
that
because,
rather
than
just
because
it
starts
off,
the
abstract
starts
off
with
you
know
the
current
status
and
overview,
because
that
makes
it
I
think
less
interesting.
I
think
that
needs
to
be
there
in
the
presentation,
but
I
think
if
it
can
be
more
you
can.
You
can
provide
more
detail
on
what
we're
going
to
cover
in
growth,
maturity
and
decline,
or
whatever
the
other
working
groups
right,
I.
F
B
E
E
A
A
A
A
F
A
F
F
A
Addition
to
the
presentation
all
right-
and
you
know
we
did-
that
birds
of
a
feather
kind
of
for
unconference
session
in
Sonoma,
which
I
thought
was
pretty
nice
in
that
tiny
little
route.
Remember:
hey
SUSE!
You
had
presented
kind
of
the
state
of
affairs
with
grimore
lab
stuff
and
Shawn.
You
had
presented
kind
of
the
state
of
affairs
with
PHP
that
at
the
time
are
now
well.
A
We
could
do
something
similar
for
that,
and
you
know
we
just
kind
of
showed
the
software
is
part
of
the
birds
of
a
feather
and
then
kind
of
open
it
up
for
how
people
would
like
to
connector
things.
They
would
like
to
see
software
side
or
metric
side
birds
of
a
feather,
they're,
pretty
informal,
I
think
the
tube
you
could
kind
of
leave
that
that
would
be
cool.
C
A
A
B
A
B
C
B
In
any
case,
we
have
the
cow
stone
the
day
before
and
if
you
remember
the
format,
we
still
have
to
decide
on
it,
but
the
idea
was
to
in
the
afternoon
writing
up
some
tutorials
and
those
could
be
on
software
and
was
my
own
on
matrix,
and
my
impression
is
that
support
for
the
Venus
conditions
are
going
to
be
much
more
busier
during
the
OSS
itself
they
under
day
before
so.
Maybe
we
could
try
to
have
tutorials
the
day
before
invite
people
from
definition
to
what
they
want
to
come.
Who
do
you
think
this.
A
I
like
that
idea
and
then
for
open
source
North
America,
we
submit
a
presentation
which
is
around
growth,
mature
in
decline.
You
submit
of
birds
of
a
feather.
It
is
really
about
community
building,
but
we
can
kind
of
hone
in
on
the
the
two
of
you,
leaving
that
from
the
softer
side
of
things
and
I
think
that's
it
for
open
source,
Clement,
North
America.
We
submit
the
presentation.
A
B
F
B
Was
great,
so
the
idea
is
that
where
we
intend
to
improve
very
much
the
support
for
code
review
in
curate
in
remote
lab
and
apply
it
among
other
projects
to
open
a
fee,
so
the
submission
would
be
like
a
mixture
of
what
can
be
analyzed
it
in
code
review
and
how
that
applies
to
open
a
fee.
And
maybe
you
can
do
it
with
the
second
part,
and
that
will
also
give
us
the
opportunity
to
discuss
you
in
this
month
on
what
lessons
can
be
learned
and
understand.
A
A
D
D
F
B
A
F
F
A
B
A
B
A
A
F
F
F
B
F
F
A
B
With
respect
to
cows
come
the
day
before.
Finally,
the
committee
is
established,
you'll
probably
saw
them
in
the
message
in
the
Middle
East.
So
my
idea
is
to
start
working
tomorrow
so
tomorrow
when
to
send
a
message
to
all
of
those
who
volunteered
and
the
first
team
by
the
way
scene
is
to
try
to
arrange
for
the
place.
So
since
you
had
the
contact
in
the
university.
B
B
B
B
A
All
right
cool
any
other
on
that
kind
of
August
period
up
in
Vancouver,
I'll
call
it
that
everybody
good
all
right
cool,
maybe
I'll
jump
down
to
google
Summer
of
Code.
Congratulations,
everybody!
We
have
no
new
students
who
are
gonna,
be
joining
I.
Think
introductions
have
gone
out
on
the
mail
list
and
they've
both
responded.
So
no,
no
we're.
A
B
G
B
E
C
A
I
do
know
that
I've
done
google
Summer
of
Code
in
the
past
I
know
that
the
reports
that
are
due
to
Google
are
pretty
important
over
the
course
of
the
summer.
We're
just
gonna
keep
that
on
your
radar
and
obviously
I
can
help
in
preparing
any
of
those.
But
those
are
that's
a
pretty
important
milestone
that
needs
to
be
hit
administrative
perspective.
So.
B
A
A
The
meetings
are,
are
really
interesting,
and
so
just
great
discussions
going
on
there
and
I
know
that
Sean
you're,
starting
out
the
growth,
maturity
and
decline
worker
starting
May
3rd,
you
know,
is
the
first
kind
of
meeting
on
that
which
is
awesome,
but
now
I
think
at
least
from
my
perspective,
it's
to
set
sights
on
value
and
risk
they're
kind
of
the
first
two
are
getting
out
of
the
door
and
now
I
think
it's
ISS
I'ts
on
either
value
or
risk.
I
think
my
inclination
is
towards
risk.
G
A
G
E
Kind
of
well
I
mean
my
experience.
They
are
definitely
related
and
they
almost
reflect
two
different
perspectives
on
how
to
look
at
open-source
software
right
I
mean,
like
lawyers
typically
view
it
from
the
perspective
of
risk
product
developers.
Product
managers
view
that
as
an
opportunity
or
value
proposition
as
an
overgeneralization,
but
I
would.
G
A
G
Like
basically
someone
who
owns
the
product
portfolio,
what
organizations
are
the
projects?
Will
you
want
to
prevent
that
will
be
decisions
on
things,
I
broke,
maturity,
decline,
nut
job,
but
I
think
risk
in
terms
of
if
they
use
it
cat
that
they
put
people
on
it?
Can
they
actually
use
it
at
the
end
of
the
day
is
what
they
look
at
from
the
discussions
I've
had
in
the
past.
A
G
A
G
A
A
G
I've
got
you
know:
I've
got
a
really
interesting
one.
That's
crossing
my
desk
right
now
in
some
discussions
with
the
GCC
community,
and
that
is
really
touching
on
some
interesting
issues.
It's
regards
to
some
of
what
we're
setting
up
and,
to
some
extent,
I
almost
like
to
use
them
as
a
touch
point
across
check,
what's
happening
on
the
girls
mature
Klein,
what's
potentially
happening
on
the
risk
and
so
forth,
because
I'm
seeing
a
lot
of
problems
that
I've
seen
people
tackling
in
other
spaces,
but
that
community
not
quite
tracking
it.
G
B
Think
so
I
don't
think
so,
but
we
could
consider
that
so
I
think
that
they
move
to
get
some
time
ago
if
they
were
using
something
else,
and
maybe
we
could
produce
something
in
any
case,
when
you
talk
about
DCC
and
other
problems
pre,
it's
like
that.
My
impression
is
that
the
pundit,
when
they
talk
about
value
they
talk
about
grade
vo,
fell
from
the
venture,
capitalist
venture.
D
B
D
G
For
what
the
numbers
actually
show
would
be
interesting
value
of
it
to
all
the
projects
have
a
dependency
on
it.
Mm-Hmm
it's
got
a
much
larger
reach,
especially
when
you
start
bringing
the
libraries.
So
just
a
new
project
to
me
is
you
know
that
GCC,
the
GFC
gdb
binutils,
which
everyone
has
a
dependency
on,
and
everyone
sort
of
takes
for
granted
right
now,
but
they've
got
a
very
it's
a
30
year
old
project
they've
got
very
crafty
infrastructure,
it's
very
hard
for
people
to
onboard
into
it,
it's
a
great
community,
etc.
G
B
We
didn't
allow
it
litchi
like
ten
years
ago,
and
at
that
time
it
was
like
five
people
maintained
in
the
library
I
mean
most
of
the
world.
Water
were
stolen
back,
like
five
people,
and
you
know,
every
single
project
in
Linux
requires
lips.
Ii
thought
that
that's
a
cane
of
a
staff
which
is
quite
important
to
highlight.
G
So
much
of
the
ecosystem
take
it
for
granted
today
work.
But
you
know
it's
not
shiny,
shiny,
it's
maintenance
there's
that
factor,
then
that
makes
it
hard
for
them
to
attract
people.
It's
also
a
function
of
their
community.
As
elements
of
you
know,
their
steering
committee
doesn't
is
technical
folk,
it's
not
focused
on
a
community
and
they
have
really
paid
attention
to
the
community
and
I
haven't
seen
the
FSF
really
support
them
that
much
either.
B
F
Right,
yeah
I
think
we
had
this
discussion
before
I
think
we
need
to
be
I,
mean
I,
think
more
specific
or
suggesting
value,
because
I
mean
like
hey
Zeus
was
saying
it's
it's
overloaded,
I
mean
it
doesn't
mean
like
usage
by
other
community.
That's
one
thing
is
it.
You
know
there
are
dependencies
on
on
certain
libraries
or
certain
communities
by
other
community,
I
I
think
I
almost
want
to
maybe
undervalue.
We
break
it
down
right,
so
I
mean
that
would
be.
That
might
be
the
way
to
do
it.
F
G
You
know
the
RPM,
you
can
pretty
much
get
a
bit
of
a
mapping
as
to
who
has
who's
calling
this
to
bring
them
in,
and
so
it's
scope
of
impact
effectively
on
depth
trees
to
out
who's
using
it.
So
some
of
that's
actually
calculate
able,
in
terms
of
you,
know,
who's
using
it.
The
other
factor
is
I
think
the
CII
project
has
been
looking
at.
You
know
core
infrastructure
initiative.
G
You
know
that's
some
of
the
metrics
that
they've
been
using
for
their
survey
historically,
should
probably
filter
into
the
risk
here
to
I.
Think
and
say
should
be
looked
at
as
part
of
the
sole
risk
and
value
story.
Instead,
let's
see
just
what
other
people
already
done
and
see
to
what
extent
we
can
incorporate
it
in
to
this.
G
You
know
security
is
something
everyone's
gonna
care
about.
Where
does
security
fall?
You
know
how
actively
are
right,
procedures
and
processes
being
followed,
and
so
like
the
CII
badging
does
do
that
measurement
already,
so
we've
got
some
interesting
pieces.
We
could
take
and
exploit
for
building
up
the
risk
value
story.
G
A
I'm,
all
behind
that
I
was
wondering
just
kind
of
as
an
out-of-band
thing
if
we
could
actually
calculate
the
B
index
or
the
GCC
community.
But
this
is
we've
been
developing:
hey
soos
we've
been
developing
an
index
which
is
basically
a
an
H
index
for
projects,
so
you're
familiar
with
the
academic
agent.
That.
A
B
A
B
G
E
G
A
B
Meant
with
respect
to
this
proposal,
decade
of
starting
with
risk
and
value
I'm
interested
in
it.
But
I
would
like
to
push
the
growth
mobility
decline.
Workbook
with
her
seen
before,
because
I
think
that,
in
addition
to
the
varsity
and
in
question,
who
need
another
workbook,
working
and
performing
and
producing
software
and
matrix,
oh
yeah,.
A
B
Would
like
to
put
that
at
much
as
possible,
but
maybe
the
time
in
the
documented
Kate
this
would
harass,
because
around
a
host
we
should.
We
have
everything
in
rails
with
respect
to
the
google
Summer
of
Code
who
are
going
to
work
in
the
semester
and
maybe
in
when
we
can
basically
have
this.
At
least
you
know
on
Rails,
and
maybe
some
other
people
can
come
later
and
flow
on,
and
maybe
we
can
do
that
I
don't
know,
but
we
can
maybe
evaluate
in
July
if
nobody
else
cams.
E
I
think
there
is,
you
know
getting
the
word
mean,
there's
we're
getting
the
working
groups
going
and
that's
important
and
and
the
there
is
relationship
between
them,
as
Kate
pointed
out
with
between
value
and
and
risk,
but
there's
also
a
relationship
between
growth,
maturity
and
decline,
metrics
and
diversity.
Inclusion,
because
their
growth,
including
decline
metrics,
are
usually
the
stick.
That's
used
to
prevent
diversity
and
inclusion
from
occurring.
F
E
B
E
And
that's
really
all
it
is,
but
right
and
it
doesn't
and
I
think
there
is
like
these
benefits,
I.
Think
for
us
being
involved
in
multiple
discussions
as
folks
coordinating
I
mean
I.
You
know,
frankly,
with
all
the
things
going
on
an
email,
I
lost
the
tractor
when
the
diversity
inclusion
meetings
are
and
I
can't
actually
find
Ono
where
that
is
listed.
Maybe
is
it
on
a
website.
D
A
So
yeah
couple
notes
on
this,
so
one
I
think
I
agree
the
categories
necessarily
kind
of
right,
actually
I
think
from
a
rhetorical
perspective.
It's
just
important
that
we
keep
them
somewhat
separated
so
that
we
can
talk
about
them
independently.
As
many
as
opposed
to
just
saying
we
have
one
giant
category
and
I
know
you
weren't
saying
that
Shawn,
but
no.
C
A
Good
point,
though,
though,
and
then
I
will
say
you
know
part
of
part
of
my
lake
would've,
it's
made.
My
ulterior
motive
in
all
of
this
is
to
only
get
the
work
groups
off
the
ground.
So
I
think
you
know
it's.
It's
dancing
pretty
awesomely
and
building
on
the
work
that
had
been
done
with
Virgie
and
OpenStack
in
the
past,
and
that's
just
awesome,
and
now
growth,
maturity
and
decline
is
having
its
first
meet.
A
Third,
and
so
now
that's
slowly
going
and
if
we
can
start
getting
risk
or
risk
/
value
whenever
we
end
up
calling
it
off
of
the
ground
just
kind
of
much.
My
motive
is
not
to
necessarily
have
everybody
be
part
of
these,
but
then
just
slowly
move
them
all
forward,
and
then
I'll
kind
of
just
be
doing
and
I
can
assist
it
anyway,
so
kind
of
the
overall
chaos
project.
A
These
different
work
I
think,
are
getting
off
the
ground,
and
if
we
can
get
this
third
slash
forth
off
the
ground,
that
would
be
really
great
forward.
Momentum
for
the
project
and
whether
or
not
I'm
in
the
work
groups
is
I.
Don't
you
know
we'll
see
so,
but
I
can
at
least
how
can
to
the
best
of
my
ability
off
the
ground.
So
I
have
an
interesting
risk
to
Kate,
so
that
might
be.
A
A
F
F
A
B
A
Everybody's
good,
just
as
a
reminder,
I've
been
recording
these
sessions.
I
do
like
to
get
them
up
on
YouTube.
If
you
have
any
thoughts
or
things
that
you
would
like
me
to
not
post
I
do
try
to
respect
people
who
attend
these
meetings.
I
also
like
to
record
and
get
these
things
out
before.
We
can't
attend
I,
get
an
overview
of
just
what
we
talked
about
in
the
hopes
of
transparency
and
openness
and
all
that
kind
of
stuff.
So
yeah
I
have.