►
From YouTube: CHAOSS Weekly Community Call 11-30-21
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello
and
welcome
to
november
30th
edition
of
the
chaos
weekly
community
chat.
We
have
all
of
these
wonderful
people
here
today.
Thank
you
so
much
for
being
here
and
there's
daniel
coming
in
right.
At
the
beginning,
there
you
go
daniel,
there's
the
minutes
yeah,
I
hope
everybody's
doing
good.
I
hope
everybody
had
a
nice
break
last
week.
We
are
back
for
a
couple
more
weeks
and
that's
actually
the
first
item
on
our
agenda.
So
let
me
just
share
this.
A
A
The
app
ecosystem
group
is
also
off
now
until
january
10th
and
then
the
dei
badging
folks
are
coming
back
a
little
bit
early
because
they
have
a
lot
to
do,
or
so
I'm
told
from
matt
cantu.
So
that's
why
they're
coming
back
a
week
early,
but
everybody
else
hi
sophia?
How
are
you
okay
good?
Can
somebody
drop
the
minutes
in
there
for
her
if
they
haven't
already?
I
don't
have
my
chat
open
here.
A
Awesome,
thank
you.
So,
yes,
so
does
anybody
have
any
questions
about
this
crazy
schedule
that
we
have.
A
Yes,
this
just
don't
show
up
for
like
a
month.
It's
fine!
I
I
personally
plan
on
just
kind
of
hanging
around
slack.
So
if
you
know
people
do
pop
in
that's
totally
fine,
if
you
happen
to
show
up
for
a
meeting
nobody's
around,
but
you
have
something
to
say
feel
free
to
drop
it
in
slack.
I
don't
know
if
a
lot
of
people
are
going
to
be
around,
but
I'll
probably
be
around.
So
if
you
do
have
questions
just
pop
them
in
there
no
worries
at
all,
or
you
can
email
me
totally
fine.
C
A
A
D
A
Unless
something
like
amazing
happens,
and
that
is
newsworthy,
then
yeah,
so,
okay
cool,
I
guess
we're
good
all
right
number,
two
new
board
member
elections-
I
don't
know
if
matt
or
sean
matt
do
you
want
to
mention
this
or
I
can't
doesn't
matter
eric.
C
I
think
it's
in
the
middle
of
the
night
in
china
right
now,
so
it
is
so.
We
will
see
him
he's
on
the
we
have
the
asia
pacific
call
tomorrow
morning,
us
central
and
then
sean
goggins
is
the
new
co-director
with
nicole.
So
congratulations
to
sean
sean.
You
now
have
to
go
to
every
single
meeting.
I
know
I
will
be
there
for
the
community.
C
C
F
C
F
C
Let's
see
our
outgoing
board
members,
let's
see
oh
hi,
salah
ray
so
rey
is
an
outgoing
board
member
ray.
Thank
you
very
much
giving
you
a
clap,
rey.
C
F
For
the
the
new
board
members,
can
I
get
a
a
picture
to
put
on
the
website.
E
Yes,
I
have
that
as
a
to-do.
What
format
I
don't
come
through
as
a
add
it
to
this
pull
request,
but
for
sharing
an
image.
If
I
don't
have
like
a
link
to
it,
I
can
just
send
it
as
an
attachment
to
an
email.
E
Think
I
know
your
voice
by
now,
but
it's
more
I'm
on
my
work
machine.
So
the
experience
of
zoom
is
not
as
ideal.
F
We
have
like
a
little
yes,
yes,
we
do
need
a.
We
do,
need
a
bio
as
well
one
to
one
to
two
paragraph
bio.
F
Yeah,
it's
it's
the
pretty
standard,
pretty
standard
bios,
I
suppose,
if
you,
if
you
would
like
to
see
what
they
look
like
you
could
you
could
go
to
the
board
member
page
on
the
website
and
see
what
other
people
have
done?
However,
there
is
some.
There
is
kind
of
there's
some
differentiation
in
the
way
people
write
them.
A
A
Okay,
I
see
number
three
says
ford
foundation,
support
and
I'm
not
do
you
put
that
on
there,
so
I
will
turn
it
over
to
him.
C
Yep,
so
that
is
so
for
those
of
you,
if
you
remember,
we
did
kind
of
a
dei
audit
for
the
chaos
project
and
there
were
a
series
of
recommendations
that
came
from
that
audit,
so
not
to
go
through
those
again.
But
the
ford
foundation
was
the
original
supporter
for
that
audit
just
kind
of
our
own
self-reflection
and
they
are
going
to
continue
support
for
us
for
the
next
two
years.
To
I
think,
yeah
do
a
couple
things
one
is.
The
hope
is:
is
the
the
members
that
we
had
to
help
us
do?
C
The
audit
would
continue
to
stay
on
with
the
project
that
we
have
and
actually
help
with
some
of
the
implementation
of
those
recommendations,
so
the
original
was
kind
of
a
shorter
term,
just
kind
of
what
what
are
people's
reflection
and
how
could
we
improve
with
no
implementation
expectation
from
that
original
work
and
over
the
next
two
years
to
start
making?
Some
of
these
implementations
we've
been
making
a
number
of
these
implementations.
So,
for
example,
things
like
office
hours
were
came
out
of
that
recommendation.
C
Translations
came
out
of
that
recommendation,
so
we're
clearly
like
doing
things,
but
I
think
there's
still
a
lot
more
to
do
and
then
over
the
course
of
the
next
two
years.
I
think
ford
would
love
to
see
not
only
us
make
these
implementations
within
the
chaos
project,
but
think
about
how
we
can
help
other
communities
who
want
to
better
center
dei
within
their
own
community
work.
C
Do
just
that.
So
we
we
have
to
think
about
how,
like
we
had
the
opportunity
to
be
supported
by
the
ford
foundation,
to
do
this
work
and
obviously
not
every
community
has
that
support,
so
how
we
think
about
the
recommendations
that
we
received
for
ourselves
and
how
those
might
be
translated
to
help
others
that
are
interested
in
doing
something
similar.
C
So
that's
the
next
two
years.
So
if
anybody
has
comments
or
thoughts
or
would
like
to
participate
in
that,
don't
hesitate
me
no
or
elizabeth
or
sean
or
whomever.
C
H
C
Just
over,
like
whatever,
during
this
break
period
or
whatever
it
could
be
short
too
right
like
here,
are
the
recommendations
that
came
out
with
just
small
small
descriptions
of
what
those
recommendations
are.
I
like
that
idea.
Do.
C
I
mean
probably
so
that
makes
sense.
Let
me
I'll
ask
michael
that's
okay,
before
we
go
ahead
and
do
that.
Okay,.
F
Currently,
on
the
main
page
of
the
website
at
the
bottom
of
the
page,
we
we
list
our
funders.
The
two
we
have
are
the
alfred,
p
sloan
foundation
and
sustain
funds,
our
podcast,
so
yeah.
If
anything
is
missing
there,
please,
let
me
know.
A
I
actually
have
a
question
matt.
We
should
maybe
also
acknowledge
the
people
who
are
on
that
team
because
I
don't
think
we've
really
done.
That
is
that
no.
A
All
right,
okay,
so
the
next
item
on
our
agenda
is
goals
for
2022.
guessing
that's
another
matt
g.
C
Yeah
that
was
me
I
just
oh
go
ahead.
Was
there
somebody
else
that
had
something
go
ahead,
so
I
mean
there
are
a
couple
things
that
I'm
really
hoping
to
accomplish
in
the
next
year.
So,
for
example,
I'd
like
to
you
know
complete
a
review.
C
Things
like
that,
right,
like
that,
would
be
great
to
kind
of
to,
if
not
finish,
in
2022
like
at
least
make
really
good
progress
in
2022.
J
C
So
the
review
is
so
a
lot
of
the
metrics
are
sometimes
maybe
two
or
three
years
old
and
just
rereading
them.
J
C
My
gosh
not
broken,
I
think
I
mentioned
this,
maybe
in
a
different
meeting,
but
we
in
in
the
dei
working
group.
We
we,
we
decided
to
review
the
code
of
conduct
for
a
project
right,
so
that's
a
metric
and
we
thought
it
would
be
like
a.
We
thought
it
was
pretty
straightforward.
We
thought,
like
the
whole
thing
was
changed.
C
I
swear
to
god.
Yeah
like
there
was
so
much
that
changed,
so
it
really
opened
my
eyes
as
to
how
much
changes
in
just
a
couple
years.
F
One
one
part
of
this
review
process
that
I
think
is
really
important
is
consistency
in
the
language
we
use
so
over
the
over
the
few
years
that
we've
we've
been
doing.
This
are
our
understanding
and
even
just
the
our
understanding
of
these
metrics
have
changed
and
even
the
way
we
talk
about
these
metrics
has
changed.
For,
for
example,
you
know,
pull
requests
have
five
or
six
different
names,
and
if
we
go
back
and
we
look,
we
look
through
all
the
the
previous
metrics
releases.
F
You'll
you'll
see
those
different
you'll
you'll
see
those
different
names
right,
so
the
preferred
term
for
us
is
change
requests.
F
So,
when
we're,
when
we're
doing
these
reviews,
we
I
think
we
we
need
to
make
sure
that
we
align
these
terms
with
our
with
our
preferred
language
and
and
additionally
link
to
the
those
terms
where
they've
been
defined.
So,
if
a
change
request
is
mentioned,
it
should
really
have
a
link
that
that
links
to
the
the
change
request
metric
things
like
that,
I
believe,
are
important.
C
K
Salah
yeah
yeah,
I
was
just
making
sure
it
was
my
turn,
so
I
think
I
think
terms
that
that
seem
to
acquire
different
flavors
fit
very
nicely
in
a
glossary
terminology.
You
know
also
known
as
and
then
you
don't
have
to
have
the
definition.
K
That's
you
know,
those
terms
can
all
mean
the
same
thing,
and
then
you
just
put
them
in
a
an
ordered
list,
an
unordered
list,
and
I
I
think,
having
that
document
means
that
even
if
somebody's
looking
at
a
legacy
version
of
any
document
that
is
not
updated
because
it
was
the
old
version,
they
would
still
be
able
to
understand
the
context
as
opposed
to
just
making
the
edits
and
and
hoping
that
nobody's
reading
the
outdated
version.
F
Thank
you,
so
I
will
say
so:
we've
we've
discussed
creating
a
glossary
before
the
problem
with
creating
a
glossary.
F
Is
that
it's
it's
another
document
that
needs
to
be
maintained,
so
our
metrics
release
is
is
kind
of
our
is
that
default.
Is
that
is
that
glossary
right?
So
those
are
the
those
are
the
terms
that
we've
defined
so
so
creating
a
separate
glossary.
That
would
include
those
terms.
Just
it
adds
a
point
of
redundancy
or
possible
failure.
K
So,
just
to
elaborate,
you
don't
have
to
redundantly
define
the
terms
think
of
it
more
as
an
as
an
index.
It
just
says
under
this
umbrella
those
terms
are
all
sometimes
meaning
the
same
thing,
so
you
use
just
the
current
term
as
the
parent
and
then
under
it.
What
other
terms
had
been
used
previously?
K
You
don't
have
to
necessarily
have
it
like
a
full
glossary
definition,
terminology
section:
you
know
it
doesn't
have
to
to
be
verbosely
redefining
the
same
meaning
just
what
other
words
may
or
may
not
have
been
used
to
refer
to
that
same
thing.
So
it's
kind
of
like
the
index
at
the
end
of
a
book
right
anyways.
K
So
so
you
know
it
would
take
maintenance
effort,
of
course,
but
it
just
also
has
the
benefit
that
if
you
do
use
those
terms
or
if
you
are
trying
to
use
the
right
term-
and
you
can
look
it
up
under
the
glossary
and
then
you
would
know
you're
using
the
right
term.
So
so
it's
not
meant
to
really
be
redundant.
K
J
Yeah
kevin,
I
I
appreciate
the
wisdom
of
your
point.
I
think
that
as
the
number
of
metrics
proliferates,
this
kind
of
maintenance
and.
L
I
was
just
gonna
say
that
I
and
the
whole
time
working
with
the
cast
project
so
far.
I
did
not
know
we
had
terms
to
find
anywhere.
I
thought
we
were
just
going
off
of
what
people
knew
so
far
about
what
the
content
of
the
metrics
were.
I'm
just.
I
think
it
would,
I
think,
maybe
in
the
handbook
just
have
it
if
it
was
even
like
10
definitions
like
best
practices,
pull
requests
things
like
that.
That
would
be
easier
to
onboard
people.
I'm
definitely.
C
Okay,
thanks
matt,
sean
or
bernard.
You
have
a
side
comment.
H
Yes,
I
have
one
comment
like
this
discussion
of
having
a
list
of
terms
or
matrix
is
coming
off
and
on
again,
so
I
was
thinking
of
one
solution,
for
this
is
like
creating
a
separate
github
page.
As
far
as
maintenance
of
that
is
concerned,
we
can
add
one
checklist
in
the
release
of
metric,
where
we
can
have
just
a
chat
list
that
we
are
adding
it
to
this
list.
H
C
So,
okay,
so
thank
you
for
these
comments.
We're
getting,
I
think,
down
into
the
details
of
how
this
might
actually
be
implemented,
which
would
be
the
goal
of
2022
so
so
this
would
so,
I
think
maybe
the
the
highest
level
thing
is
is
just
kind
of
the
this
completing
the
review
of
the
metrics
and
then
within
that
creating
consistency
around
some
of
the
terms
and
how
that
gets
sorted
out
would
be
in
the
details.
I
think
that
are
coming
up
here.
So
thank
you
for
that.
B
B
Auger
focused
tutorials
working
to
build
a
community,
and
I
think
you
know
I'm
the
first
to
talk
to
daniel
and
eorg
about
how
their
more
lab
would
would
like
this
place.
I'd
like
to
have
a
chaos
community
for
welcoming
software
developers
to
implement
metrics
and
the
tools
that
we
have.
I
think
I
think,
there's
a
an
opportunity
for
the
two
major
tools
in
the
project
to
collaborate
on
community
development
in
some
way
that
isn't
specified
yet
because
I
think
that
first
involves
a
conversation
between
us.
C
Cool
daniel
put
in
the
chat
yes,
so
so.
B
C
C
So
the
so.
The
intention
here
is
to
just
that
to
overcome
what
like
just
to
overcome,
what
may
be
a
lack
of
community
development
around
say:
auger
yeah.
C
Cool
that'd
be
great.
I
totally
agree
all
right.
I
had
put
a
couple
of
others
on
there.
Perhaps
reflection
on
the
website.
It
has,
as
you
know,
gotten
kind
of
big.
Clearly,
the
metrics
models
are
gaining
traction,
so
working
on
the
release
of
metrics
models
would
be
something
that
I
have
as
well
are
there
are
there
other
things
that
people
would
like
to
accomplish
in
2022
like
personally,
these.
G
C
K
So
I'm
I'm
like
a
very,
very
big
user
of
dark
mode,
and
I
don't
know
if
the
chaos
site
and
resources
have
yet
you
know
gotten
into
the
responding
to
the
environment
start
mode
setting
or
not,
so
I'm
just
putting
it
as
an
idea.
I
wish
I
could
do
it.
K
I
really
can't,
but
I
would
love
to
see
you
know
if
there's
a
way
to
integrate,
responsive,
dark
mode
or
you
know,
system
dependent,
dark
mode
which
is
part
of
the
css
specifications
on
the
chaos
resources.
C
I
am
not
familiar
with
this
so,
but
I
am
willing
to
learn
and
become
familiar
with
this,
so.
K
K
Color,
and
so
they
they
specify
in
the
os
as
it
you
know
they
want
dark
mode.
Then
they
go
on
a
website
that
doesn't
implement
and
that
course
that
that
shock
itself
is
is
what
gets
people
who
use
it
for
accessibility
purposes,.
K
C
K
C
Okay,
okay,
that
makes
sense.
Thank
you
all
right.
I
Yeah
a
couple
of
comments
so
plus
one
to
what
sean
mentioned
before.
Definitely
perhaps
I'll
align
with
this.
What
I'd
like
to
think
as
a
community
is
how
we
can
make
ourselves
sustainable
in
the
medium
term,
because
we
are
all
like,
let's
say
small.
I
I
There
might
be
certain
ideas
about
bringing
probably
a
large
corporation
or
so
sustaining
the
community
and
somehow
or
helping
advance,
or
you
know
this
kind
of
things,
but
I
I
would
say
this
discussion
is
good
to
have.
I
I,
for
instance,
have
had
a
couple
of
informal
conversations
with
you
ma,
for
instance,
about
this
topic,
but
that's
something
that
probably
to
have
with
all
of
us
here.
I
B
I
Mentioned
in
the
past,
I
think
that's
an
important
topic
for
2022,
but
this
this
has
been
already
mentioned.
So
that's
something
probably
to
discuss
about
or
to
move
things
for
what
I
personally,
I
personally
would
like
to
do
to
move.
I
C
I
C
Okay,
gotcha
yeah.
Thank
you
for
that,
and
hopefully
like
with,
without
assigning
like
action
items
on
this
list,
like,
hopefully,
people
are
looking
at
this
list
and
thinking
that's
something
that
I'm
interested
in
like.
I
would
like
to
be
part
of
that
conversation
whatever
it
might
be,
and
I
know
looking.
C
Myself
and
like
I
don't
think
any
of
these
things
on
the
list
are
solo
considerations.
I
think
we've
heard
these
before
so
it'd
be
great
to
just
start
kind
of
taking
these
on.
I
had
another
thought
I
really
like
the
sustainability
considerations
for
the
project.
I
think
that's
important,
of
course,
moving
forward.
So
that's
great.
C
Like
more
community
members
on
the
call
like
more
people
in
the
working
groups,
fewer
weekly
meetings
like
it
could
be
anything
totally
just
absolutely
anything
like
there's.
There's
too
much
of
this
or
too
little
of
that
you
know.
I
think
we
have
a
really
good
group
of
people
that
is
pretty
responsive
to
the
needs
of
everybody.
So
is
there
anything
that
people
have
on
their
mind.
E
It's
just
it's
only
to
get
longer
and
more
untenable,
and
so
I
know
in
the
past
we
had
talked
about
whether
or
not
that
means
reconfiguring
how
we
display
things,
how
we
group
things,
maybe
not
shipping
our
org
chart
per
se
in
terms
of
how
things
are
grouped,
maybe
trying
to
find
another
organizational
principle
that
could
be
more
aligned
to
say
someone
who's
new
to
the
project,
who
doesn't
necessarily
understand
the
nuances
and
splits
between
the
different
working
groups.
E
I
think
it's
part
of
the
metrics
model
piece
honestly,
because
I
think
that's
that's
sort
of
the
path
we
took
at
the
time
versus
saying,
like
we're
going
to
redo
how
we
organize
our
entire
website,
but
I
think
I
know
I
guess
for
me
the
goal
is
to
make
our-
I
guess
our
virtual
presence,
more
digestible
for
someone
who
would
be
a
new
newer
project
or
newer
to
a
netflix
initiative
such
that
they
could
either
either
that
might
be
through
the
maintenance
models,
but
it
might
also
be
through
some.
E
I
think
a
lot
of
these
concepts
we've
really
brought
up
today
could
could
inform
that,
like
a
glossary
or
consistent
language
across
things,
how
we
organize
how
we
present
it.
So,
I
think
that's
kind
of
a
nebulous
goal,
but
I'm
just
thinking
about
simplifying
that
experience
for
either
new
contributors
or
new
users
of
our
project.
B
B
B
C
So
to
that
to
these,
so
these
points,
one
of
the
things
that's
kind
of
interesting.
If
you
take
a
look
at
this
list,
is
like
it's
not
about
like
making
more
metrics
or
building
out
the
software.
C
You
know
what
I
mean
like.
That
seems
to
be
going
pretty
well
at
least
what
we're.
What
we're
doing
a
lot
of
these
are
about,
at
least
to
me,
like,
like
engagement
and
new
new
individuals
and
how
we
express
the
work
that
we've
done
at
least
to
me
that's
kind
of
interesting
like
it's
not
about
building
more
metrics,
which
will,
I
think,
continue
to
happen.
M
M
Gosh
hats
off
tonight
come
to
and
and
team.
You
know,
just
between
the
time
of
our
board
meeting
and
the
time
of
the
podcast
the
end
of
your
podcast.
You
know
it
just
you
know
that
initiative
has
really
seemed
to
to
take
off.
It
seems
like,
and
hopefully
I'm
not
misspeaking
here
it
seems,
like
most
of
the
badges
have
been
awarded
to
linux
foundation
events.
M
It
would
be
great
to
see
us
broaden
that
and,
as
I'm
saying
this
and
going
oh,
I
gotta
reach
out
to
this
person
and
this
person
and
this
person
and-
and
I
think
then
matt
to
bring
it
back
to
what
you
were
saying
in
terms
of
engagement.
I
think
maybe
what
that
might
also
do
is,
as
folks
start
to
see,
if
we
start
to
broaden
that
what
folks
might
also
start
to
see
is:
oh
wow.
This
event
has
a
has
a
badge
associated
with
it.
M
Oh
well,
I
wonder
what
that
is,
and
if
the
is
clickable
in
some
way
or
if
there's
right,
oh,
I
I
want
to
go
find
out
about
that.
What
is
that-
and
it
may
draw
folks
new
folks
into
the
the
project,
or
so
you
know,
and
we
may
start
to
see
other
folks
getting
involved
as
well
and
engaging.
L
Yeah,
so
plus
one
to
all
of
that,
I
I've
noticed
the
same
thing.
We've
talked
about
it
a
little
bit
in
the
badging
weekly
meetings
and
our
conclusion
was
that
when
we
first
started
and
we
were
reaching
out
to
a
bunch
of
different
event,
organizing
teams,
we
were
getting
a
pretty
diverse,
set
of
like
different
kinds
of
events
that
we're
applying
and
we've
got
that
kind
of
peppered
in
now.
L
But
a
lot
of
them
are
from
the
explanation:
yeah,
the
application's
coming
in
and
they're
at
the
point
where
they
know
what
they're
doing
with
the
applications
and
they
know
how
to
how
to
make
their
event
fit
the
best
practices
that
we
provide.
L
So
it
would
be
great
to
have
more
of
that
learning
experience
with
events
that
that
aren't
in
the
linux
foundation.
I
agree
so
that's
one
of
our
big
goals
for
the
next
release
and
also
bringing
up
the
badge
the
the
type
of
badge
that
we
provide,
we've
always
kind
of
leaned
towards.
Maybe
we
should
change
the
badge
and
make
it
something
different.
I
think
that's
going
to
be
another
focus
for
this
next
release.
M
C
Is
there
so
I
have
two
questions
on
this
for
either
nicole
or
matt,
and
one
maybe
doesn't
need
to
be
answered
now,
but
could
be
kind
of
a
consideration
for
2022.
I
actually
both
could
be
the
first
one
is
about
academic
events.
So
they're
not,
I
know
one
of
the
criteria
for
the
chaos
badge
is
that
it's
an
oss,
it's
an
open
source
event,
and
so
one
possibility
would
be
to
include
academic
events
as
well,
because
they
certainly
are
focused
on
better
centering
dei
within
their
own
events
as
well.
C
So
just
something
to
think
about,
and
then
is
there
any.
I
think
one
of
the
things
that
might
be
worth
considering
in
2022
is
how
do
projects
get
badged
if
that's
even
a
possibility,
so
we
had
talked
about
event
badging
and
project
badging
when
this
all
started,
maybe
like
a
year
and
a
half
ago,
and
we
took
the
approach
that
event.
Badging
was
probably
the
more
approachable
thing
to
look
at
first,
it
was
they
were
they
were
time
cap.
You
know
what
I
mean
like
there
was
a
there.
C
Was
this
time
component
and
you
didn't
have
to
rebadge
and
all
that
kind
of
stuff,
so
is?
Is
there
a
model
for
project
badging
and
if
so,
what
could
or
might
that
look
like,
obviously
being
sensitive
to
the
amount
of
work
that
goes
into
to
awarding
a
badge
so.
C
E
Yeah,
I
was
just
thinking
it
for
me:
that's
really
going
to
be
boundary
dependent,
so
you
mentioned
the
time
component
in
an
event
in
time.
It's
these
are
the
people
that
are
participating
in
the
event
where
participation
in
a
project
is
ebbs
and
flows.
So
it
could
be
participation
over
the
course
of
a
year
like
we'd
have
we'd
have
to
bound
it
in
some
way
and
then
it
would
also
have
to
have
an
expiration
date
on
it.
So,
and
I
mean
I
think,
it's
possible.
It's
just
like.
E
I
think
we'd
have
to
change
our
criteria
a
bit
in
terms
of
how
to
set
boundaries
that
are
applicable.
For
that
project
I
mean
it
depends.
Maybe
a
year
isn't
the
right
time
scale.
I've
been
working
with
a
project
that
has
a
release
cadence
of
18
months,
and
so
that's
a
more
appropriate
time
period
to
look
at
participation
levels,
because
some
people
are
pretty
much
only
involved
in
the
release
portion.
K
Yeah,
so
I
heard
we
were
talking
about
some
who
applied
for
badges,
have
expertise,
experience
they've
had
questions
answered,
and
so
you
know
I'm
thinking.
Okay,
somebody
who's,
meaning
to
apply
for
a
badge
can
lean
on
that
resource.
So
what?
If
we
have
a
repo
for
you
know
everyone
who's
applied
and
had
a
badge
would
be
on
this.
Repo
and
people
can
open
an
issue
they're
asking
questions
which
gives
the
ability
for
those
who
have
badges.
K
You
know
experience
with
it
and
those
in
the
project.
So
it's
more
like
a
like
a
forum
right,
but
we're
just
doing
it
the
open
source
approach,
so
that
there
would
be
that
repo
where
it's
like.
Am
I
doing
this
right
just
so
that
we
can
lean
on
the
experience
of
people
who
got
it
done
from
the
user's
experience
and
user's
experience,
as
opposed
to
from
the
project's
experience.
C
A
good
idea,
thanks,
matt
and
then
lucas.
L
Yeah,
sorry
for
the
dogs
barking
in
the
back
and
we
have
roofing
people,
but
so
we
have,
I
think,
that's
a
great
idea
saul
and
I'm
glad
I'm
glad
to
set
that
up.
I
have
some
kind
of
prototype
built
before
we
come
back
in
january.
L
I
can
take
an
action
item
to
do
that,
but
also,
I
think,
the
as
far
as
connecting
connecting
people.
We
have
a
few
people
who
are
kind
of
senior
appliers
at
this
point
and
I
think
it'd
be
great
to
reach
out
to
them
and
ask
if
they're
willing
to
to
be
part
of
that
and
and
say
like
there's,
no
reward,
there's
no
monetary
reward
or
anything
but
it'd
be
like
passing
down
what
you
know
about
how
to
apply
so
far
and
and
reach
out.
If
you
have
any
questions.
C
Cool
lucas,
your
hand
is
down.
I
don't
know
if
your
comment
went
away
here.
J
Thank
you,
but
thank
you
for
observing
that.
I
want
to
call
out
how
many
ideas
and
how
much
passion
there
is
related
to
dei,
and
I
certainly
share
that,
for
example,
I
wonder
about
expanding
the
dei
work
outside
of
open
source
entirely,
so
not
only
to
academic
applications.
This
goes
to
a
general
issue
with
chaos
or
opportunity,
with
chaos
of
applying
chaos,
metrics
to
commercial
development
outside
of
open
source
and
the
boundary
between
open
source
development
practices
and
commercial
ones.
J
C
E
I
have
one
more
goal
to
add:
yeah
yeah.
Our
list
is
getting
very
long.
I
think
it
kind
of
fits
into
the
themes
that
we
were.
I
was
talking
about
before
and
others
as
well
having
some
kind
of
feedback
or
like
user
feedback.
I
don't
know
if
that's
a
survey,
I
don't
know
like
we've.
E
We
did
do
a
survey
around
our
event,
but
that
was
pretty
limited
because
attendees
and
we
have
that
sort
of
like
the
open
office
hours
in
qa,
but
I
feel,
like
you,
haven't,
made
a
considerable
push
to
collect
feedback
from
sort
of
a
broader
user
community,
or
maybe
new
chaos,
members
or
just
like
some,
some
way
to
kind
of
gauge
what
the
experience
is
like
for
someone
who's,
not
new
to
the
project
for
both
a
user
and
a
contributor.
So
I
mean
we
could
do
a
survey.
E
C
E
Yeah
I
mean
it
could
also
just
be
like
a
state
of
metrics.
Survey
too,
doesn't
have
to
be.
Chaos
related,
like
I
think,
that's
that's
thinking
about
the
broader
question
of
just
how
how
chaos
is
supporting
these
things,
so
it
could
be
either
the
experience
of
people
coming
to
project
or
the
experience
of
people
that
are
trying
to
develop
metric
programs,
and
you
could
ask
about
the
role
of
chaos
and
potential
interest
in
that
project
as
well
as
sort
of
like.
E
C
C
In
ocean,
so
okay
cool
all
right-
that
was.
C
A
Not
if
it
would
be
helpful,
I
can
open
an
issue
in
the
community
repo
or
something
for
each
bullet
or
each
one
of
these
items.
When
you.
F
Real
quick,
I
had
a
question
about
chaos.
Con
europe,
namely
mainly
are
we
are
we
going
to
try
to
do
that?
I
think
fosdem
is
virtual,
not.
E
Chain
available
that,
given
that
we
are
not
meeting
again,
I
think
what
we
initially
talked
about.
The
last
meeting
I
was
here,
which
I
think
is
a
few
weeks
ago
at
this
point-
was
doing
some
sort
of
like
chaos
week
around
fosdem,
where
we
would
re-air
some
of
our
sessions
that
we
had
at
kscon
and
then
do
a
more
aggressive
promotion
around
the
meetings
that
we
have
that
week.
E
I
was
thinking
these
are
the
round
tables,
but
they're,
actually
just
we're
leveraging
the
existing
working
group
slots
to
have
conversations
with
people
that
might
be
new
to
the
community.
So
I'll
put
this
in
an
email
so
that
it's
more
structured
as
a
thought
versus
just
like
I'm
rambling
at
you
now,
but
we
were
thinking
the
week
after
fosdem
or
is
it
the
week
before?
That's
what
I
don't
remember.
N
The
other
conversation
that's
happening
in
the
chaos
con
channel
is
around
doing
something
around
north
eu
in
dublin
because
they
just
announced
the
dates
for
that.
N
I
mean
we
could
still
do
something
around
boston,
but
my
my
experience
is
that
the
people
who
attend
these
virtual
events
are
so
tired
of
doing
virtual
events
that
they
don't
necessarily
want
to
do
more
more
virtual
meetings
that
they
wouldn't
do
otherwise,
so
I
you
know,
I
think
that
if
we,
if
we
wanted
to
do
some
kind
of
a
promotion
of
some
of
the
other
content
that
we
have,
maybe
we
do
that
on
a
at
a
different
time.
It
doesn't
necessarily
we
could
do
it
any
time
yeah.
This
is
true.
E
I
mean
I'm
not
married
to
this
idea.
It
was
just
one
that
we
had
so
I
think,
and
we
have
free
time
to
figure
it
out
too.
So
we're
not
bakery-
and
I
also
kind
of
I'm
with
you
on
the
sort
of
the
fatigue
of
virtual
events-
and
I
I
don't
know
I
feel
like
people
are
really
excited
to
not
be
going
to
virtual
events
anymore,
and
I
know
we
all
had
the
news
over
the
weekend
that
we
don't
know
what's
happening
with
pandemic.
So.