►
From YouTube: CHAOSS Weekly Community Call 10-26-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
the
october
26th
edition
of
the
weekly
community
call
for
chaos.
I
am
elizabeth
barron,
your
community
manager
so
happy
to
see
everybody
here.
So
thanks
for
joining
us
really
appreciate
you
being
here
and
attending
and
giving
us
your
attention,
or
you
know
just
giving
you
a
place
to
check
your
email.
While
you
listen
in
that's
totally
fine
too,
I
will
drop
some
minutes
here,
one
last
time.
If
you
would
like
to
add
your
name
to
the
agenda
that
would
be
great
or
to
the
list
of
attendees.
A
There
we
go
okay,
so
we
had
some
items
from
last
time
that
we
pushed
to
this
time.
So
let's
go
through
those
really
quick.
The
first
one
was
there
was
a
note
about
matt
c.
If
we
go
down
here,
it
said
maxie
is
the
center
of
things,
so
that
kind
of
kicked
off
a
little
discussion
about
the
e-commerce
and
chaos
swag
topic.
So
kevin
was
going
to
look
to
see
if
there
was
a
way
that
we
could
connect
open
collective
to
our
e-commerce
platform
so
kevin.
B
Yeah
and
ray
had
mentioned
that
the
linux
foundation
has
done
this
before
and
he
was
going
to
give
me
a
contact
person
to
figure
out
how
they
were
doing
it,
because
it
sounds
like
the
way
that
they
were
doing
it.
It's
very
similar
to
the
way
that
we
had
contemplated
doing
it
and
it
looks
like
he
has
given
me
the
the
person
here,
it's
brandon
wick,
so
I
will
reach
out
to
that
person.
However,
I
I
had
not
reached
out
to
that,
yet
I
don't.
B
I
don't
think
he
gave
me
that
name
in
the
meeting.
I
think
he
must
have
put
that
in
after
the
fact.
D
A
C
I
am
ordering
on
this
while
we're
talking
about
flag.
I
have
ordered
I'm
ordering
more
t-shirts,
so
I'm
gonna
order
a
lighter
color
t-shirt
with
the
black
logo.
You
know
how
the
last
one
was.
The
white
logo
and
I'm
gonna
do
a
slightly
thicker
t-shirt
and
then
I'm
also
getting
coasters
chaos
coasters.
Some.
E
C
F
E
A
Okay,
I
know
she
is
passionate
about
this
building
out
the
brand
kit,
so
we're
consistent
with
you
know
the
way
things
look
on
twitter
versus
linkedin
versus
all
the
other
places.
I
don't.
I
know
she
has
thoughts
about
this,
so
I
don't
want
to
presume
to
know
what
those
thoughts
are.
So
we
can
just
defer
this
until
next
time,
when
nicole
is
able
to
join.
A
All
right,
so,
let's
move
on
to
number
three,
which
is
the
privacy
statement
in
metrics
lucas
this
lucas
on
here
you
don't
see
him
either
okay.
Well,
I
can
share
that.
Here's
the
issue
where
we're
kind
of
collecting
thoughts
and
lucas
was
if
we
could
look
down
here.
Lucas
was
going
to
start
a
draft
and
I
believe
that
he
did
that.
A
So
we
can
click
on
that
issue
and
look.
Y'all
will
see
my
payment
thing
again
because
I
have
not
updated
my
credit
card
and
give
up
so
you're
gonna
see
this
little
thing
here,
someday
I'll.
Do
that
not
today
but
yeah.
So
here's
the
issue.
If
you
would
like
to
comment
on
what
lucas
has
written
here,
feel
free
to
do
so.
C
A
I
think
it's
going
to
be
the
well
there's
two
things.
There's
one:
it's
going
to
be
like
a
central
document
that
will
have
like
more
details
about
levels
of
pii
and
things
like
that
to
give
people
a
little
bit
more
guidance.
A
B
G
B
Then
for
the
metrics
template
itself,
we
would
add
a
checklist
item.
That
would
say
basically
is
this
metric.
Does
this
metric
have
privacy
guide
privacy,
guidance
issues,
and
then
we
would
have
just
a
bit
of
text
that
we
would
add
to
the
template,
which
would
be
optional.
B
That
would
basically
say
hey.
This
metric
has
some
privacy
issues.
Please
see
this
central
document
we've
created
and
it
would
link
to
that.
G
H
C
B
Add
it
to
the
checklist,
and
then
we
also
add
it
to
the
metrics
template
as
an
optional
yeah,
an
optional
message
that
would
be
under
implementation.
That
was
my
third
thing:
yep,
okay,
so
it
does.
It
does
create
this
situation
where
every
time
you're
defining
a
metric,
you
have
to
make
the
decision
on
whether
or
not
does
this
does
this
metric
have
privacy
concerns
okay,
and
then
you
either
remove
the
optional
tag
or
don't
include
the
statement.
C
Okay,
great,
could
we
just
break
this
up
into
four
extra
four
three
action
items
then
so
one
ai
is
the
actual
pii
text
document.
G
C
I'll
take
the
metrics
template
to
include
optional
statement.
A
Well,
matt's
typing:
we
did
talk
about
the
community
operations
team
being
involved
in
this,
but
we
were
not
sure
where
that
stood.
So
if
that
is
not
a
thing
yet,
then
we
can
just
like
share
the
work
across
the
community
to
do
these
three
things.
But
if
the
operations
team
was
in
place,
then
we
thought
that
might
be
good,
something
good
for
them
to
work
on.
A
G
J
All
right
there
were
three
things
happening
all
at
once.
I
heard
someone
else
talking.
They
should
go
first,
because
mine
wasn't
going
to
be
a
side
turn.
I
C
K
Hello,
hi
yeah
thanks,
so
I
I
have
a
question
so
I
you
know
I
sat
in
on
on
a
couple
of
your
meetings
and
such
and
I
hope
to
be
at
the
meeting
tonight
and
then
also
with
some
of
the
other
pieces.
I
was
wondering
if
there's
anywhere,
where
we've
like
outlined
kind
of
where
these
processes
are
because
I
was
like
kind
of
following
along
and
kind
of
seeing.
K
Oh
this
went
here
and
then
this
one
over
here
and
then
this
one
here,
but
is
there
anywhere
where
we've
like
kind
of
written
out
where
each
of
these
things
are
or
anything
along
those
lines
that
I
could
read
up
on,
so
that
I
can
be
more
knowledgeable
when
we're
going
over
things
like
the
privacy
statements
and
the
metrics
and
some
of
those
different
pieces,
because,
like
y'all
done
such
a
good
job,
writing
up
all
of
these
details-
and
it's
like-
where
does
this
other
part
exist,
so
that
I
can
be
a
little
bit
less
confused.
C
Yeah,
let
me
so,
would
it
help,
even
just
under
these,
like
the
b
c
and
d
that
we
have
here
like
put
links
to
what
these
actual
things
are.
K
Noticed
I
was
uncharacteristically
quiet
and
that's
because
I'm
like
what
I
don't:
okay,
I'm
gonna
just
sit
back
and
watch.
I'm
gonna
do.
J
We
did
some
of
that
in
our
own
privacy
statement,
so
that
we
wrote
around
the
chaos
community
and
our
privacy
statement
around
how
we
handle
documentation
or
sorry
to
handle
data
collection.
So
I
would
say
that
we
should
either
start
there
or
make
sure
that
we
update
them
in
tangent
or
that
this
crash
reference.
J
I
would
hate
to
have
two
different
classifications
of
pii
coming
from
the
same
community,
just
in
terms
of
us
following
our
own
descriptions,
because
we
did
build
on
say
what
say
how
nist
classifies
various
levels
of
pii
those
tend
to
be
very
corporate
centric.
J
So
I
think
it's
kind
of
the
open
space
here
to
define
is
how
to
provide
risk
categorization
outside
of
a
corporate
revenue
regulatory
structure
and
that
we're
kind
of
self-forming
without
any
of
those
pre-existing
things.
So
I
mostly
just
wanted
to
bring
it
up
to
make
sure
that
we're
referencing
and
building
on
and
updating
and
tangent
versus,
creating
something
that's
completely
separate
and
somehow
might
may
or
may
not
align
with
what
we've
already
published.
C
They
don't
have
a
meeting,
so
this
was
this
kind
of
came
out
of
a
different
discussion
with
respect
to
the
dei
efforts
so
like
there
was
the
dei
reflection
team
and
the
operations
that
reflection
team
doesn't
necessarily
have
to
do
the
implementation,
and
so
the
operations
team
would
be
the
team
that
would
help
think
through
how
we
would
implement
some
of
those
recommendations
and
that
kind
of
led
to
this
whole
idea
of
an
operations
team
to
kind
of
help
with
things
that
really
occur
across
the
entire
project.
So
no
meeting.
A
J
J
J
A
Use
that
to
start
with,
whoever
wants
to
work
on
this
looks
like
it's
missing
some
things.
This
is
obviously
just
a
draft.
J
A
J
J
B
J
A
A
C
A
A
A
A
G
E
C
B
B
Why?
Because
the
the
metrics
models
group
is
the
is
the
group
that's
kind
of
talking
about
the
the
implications
for
metrics
in
use.
B
Either
either
way
works.
I
I
community
is
fine
too,
but
the
discussion
could
be
had
in
in
the
metrics
models
as
well.
So
when
you,
when
you
start
talking
about
metrics,
that
have
privacy
considerations,
that
could
be
that
actually
could
be
a
collection
of
metrics,
and
once
that
collection
of
metrics
is
identified,
we
could
provide
guidance
on
them.
B
Okay,
but
either
way
it's.
This
is
about
providing
guidance.
So
this
is
not
a
it's,
not
a
normal
working
group
issue.
I
would.
I
would
consider
this
to
be
a
chaos
initiative,
similar
to
the
way
we
think
of
badging
as
an
initiative.
C
B
B
J
J
So
we
all
are
sure
that
we're
on
the
same
page,
I
mean,
I
think
this
is
a
multi-faceted
discussion
with
multiple
stakeholders,
to
put
it
all
in
business,
ops
terms,
but
it's
I
don't
know
like,
I
think
to
do
it
well,
we
have
to
be
very
explicit
about
what
and
how
and
who-
and
here
so
I
don't
know-
I
feel
like
that-
it
might
be
helpful
to
have
some
sort
of
view
of
what
we
are
explicitly
doing
and
what
we're
explicitly
not
doing
so
I
before
we
change
lucas's
language.
J
Maybe
we
comment
that
as
a
question,
did
you
mean
to
write
this
for
working
groups,
or
did
you
mean
to
write
this
for
metrics
implementers,
because
I
think
those
are
potentially
valid
points
but
would
have
a
different
focus
in
terms
of
recommendation
and
overview.
E
Yeah
like
whenever
this
discussion
comes
up,
all
these
two
things
always
mixed
up
so
like
we
have
a
policy
for
ourselves
as
a
community
policy
for
others
as
a
guidance.
So
maybe,
let's
have
a
clear
distinction,
because
whenever
this
discussion
arises,
it
always
gets
confused
in
these
two
aspects.
A
I
feel
like
it
would
be
very
helpful
if
lucas
was
here
so
maybe
we
should.
A
C
K
A
Okay,
thanks
matt
all
right,
so
we're
going
to
go
ahead
and
move
forward.
Anybody
has
any
final
comments
on
that:
go
ahead
and
drop
them
in
one
of
the
issues
somewhere
and
then
it'll
get
collected.
So
the
next
item
on
our
agenda
is
the
chaos
con
results
and
I
have
sophia
here.
Should
I
click
on
here?
Is
this
the
results
it
is?
I
can
also
just
present
yeah.
That's
great.
Let
me
do
that.
J
J
Are
you
seeing
chaos,
common
feedback,
summary
yeah,
looking
at
it?
Okay,
I
should
know
how
zoom
works
after
presenting
it
all
things
open
last
week,
so
this
one
we
quickly
run
through.
We
ran
a
quick
survey
after
kscon
to
get
some
feedback.
The
majority
of
people
that
filled
it
out
were
people
that
attended
in
person.
We
had
nine
respondents,
which
means
I
feel
like
some
of
you
are
probably
here.
So
thank
you.
J
I
didn't
actually
look
at
who
responded.
I
was
trying
to
respect
anonymity
here,
but
mostly
just
want
to
show
a
mix
of
folks
that
were
attending
generally
we
had
pretty
positive
ratings.
Our
weighted
average
score
was
4.3
satisfaction,
so
generally
people
were
felt
positive
about
the
event.
We
did
ask
what
were
your
favorite
sessions?
We
heard
pretty
much
comments
about
most
of
them.
People
like
the
incivility
session.
They
loved
the
lightning
talks
they
liked
the
rit
sessions.
J
J
There
was
definitely
some
feedback
points
that
we
got
around,
just
the
logistics
and
structure
of
it.
That
could
be
improved,
so
I
mostly
was
taking
this
as
a
hybrid
events
or
a
learning
pane
for
all
of
us,
especially
for
sort
of
these
smaller
satellite
events.
So
we
can't
lean
on
the
aggregate
tools
that
the
rest
of
the
platform-
sorry,
the
rest
of
the
conference,
is
using.
So
I
really
like
some
of
these
suggestions
that
I'm
looking
at
as
how
to
run
a
multi-channel
event.
J
So
generally,
we
could
have
had
better
and
more
frequent
communication
on
more
channels,
especially
because
we
kind
of
changed
the
the
schedule
a
little
bit
last
minute
too
so
kind
of
having
more
more
of
that
upfront
and
center
and
increasingly
promoting
that
increasing
promotional,
live
stream
during
the
event
for
folks
that
might
have
joined
later
on
making
it
easier
to
find
things
both
in
the
room
and
in
the
slack
channel.
J
More
specifically,
I
liked
that
there
were
some
feedback
points
that
we
should
have
had
more
breaks,
which
I
agree
is
the
person
who
made
the
schedule.
I
was
kind
of
under
the
objective
of
trying
to
squeeze
as
many
things
in
there
as
possible,
but
I
think
that
meant
that
we
lost
some
of
the
in-between
connection
and
discussion
and
sort
of
the
hallway
for
lack
of
a
better
term,
because
it
has
a
very
specific
meaning,
but
just
kind
of
the
in-between
space
there's
more
desire
to
have
more
of
that
space.
J
And
then
I
know
this
came
up
in
the
room
as
well.
We
were
talking
about
shortening
virtual
talks
and
I
liked
this
recommendation,
so
I
serviced
it
to
the
top,
maybe
keeping
those
shorter
versus
the
in-person
ones,
where
it's
easier
to
stay
engaged
and
to
stay
interactive
with
the
presenter
and
then
just
a
call
for
more
interactive
sessions.
J
We
had
discussed
this
up
front
in
chaos,
con
planning
and
opted
not
to
given
the
short
short
duration
of
the
schedule,
but
we
were
thinking
about
having
more
of
like
round
tables
and
discussions
and
more
of
a
workshop
setting,
and
we
did
get
some
feedback
that
that
would
have
been.
That
would
have
been
a
great
add-on.
So
I
guess
maybe
for
future
events.
If
we
have,
I
would
think
it
a
little
bit
more
time
just
because
I
feel
like
those.
J
G
J
J
J
Not
to
say
I
don't
know
if
anyone
has
run
an
event
where
every
talk
is
seven
minutes.
That
would
be
kind
of
a
wild
concept.
J
But
I
I
like
I
like
the
idea,
especially
with
these
sort
of
shorter
short
events,
so
playing
a
little
bit
more
with
the
session
like
the
format
and
then
just
some
specific
call-outs
for
types
of
roles
that
folks
thought
could
then
we
could
have
benefited
from
having
someone
who's
more
dedicated
to
our
social
media
channels
or
to
slack
to
ensure
that
people
are
staying,
engaged
and
active
and
connecting
the
dots
where
people
are
always
present
in
all
places.
J
I
I
like
that
the
ted
max
ted
does
max
out
at
20
minutes,
so
we
we
did
that
as
well.
Our
keynote
was
35,
but
everything
else
was
max
20..
Most
people
would
recommend
it
so
yay
just
the
same
score.
Distribution
as
the
overall
satisfaction
score,
and
then
last
thing
I
wanted
to
point
out
there
is
that
we
had
made
up
front
that
we
wanted
to
do
some
sort
of
re-airing
of
the
of
talks
that
were
popular
or
maybe
an
opportunity
to
have
an
in-depth
qa
with
panelists
or
speakers.
J
I
know
matt,
we
had
cut
your
session,
so
I
wanted
to
give
you
space
to
do
that,
and
I
wanted
to
kind
of
put
it
out
there
for
discussion.
I
I
have
a
strong
opinion
here
that
I
marked
so
that
everyone
could
see,
but
just
the
thought
that,
like
we
as
an
organization,
have
also
had
satellite
events
around
fosdem
which
isn't
happening
this
year,
it's
only
virtual,
so
I
thought
it
could
be
a
fun
time
to
have
our
virtual
only
one
around
it.
J
So
it's
sort
of
like
a
satellite
and
metaphossum
again,
and
that
would
also
give
us
a
couple
of
months
to
get
things
together.
Even
though
nothing
would
be
new,
it
would
just
be
an
opportunity
to
reconnect
and
to
discuss
further.
A
A
Or
I
could
like
screenshot
some
of
it
or
something
like
that,
like
mostly
I'm
just
I'm
curious
about
the
the
recommendations
of
like
this,
like
those
two
slides
that
have
those
specific
things
called
out
so
that
one
next
time
we
remember
that.
J
J
And
I'm
happy
to
put
myself
on
the
hook
to
to
help
support
it.
Given
that
I
was
involved
in
the
last
one
and
have
a
lot
of
the
pieces,
and
this
is,
I
feel,
like
the
part
two
of
the
last
one.
So.
A
A
A
Okay,
so
the
next
thing
on
our
agenda
is
this
concept
of
adding
another
person
to
action
items
as
we
assign
them,
which
we
absolutely
did
not
do
up
here.
But
that's,
okay,
I
don't
know
matt.
If
you
want
to
talk
about
this,
I
can't,
if
you
don't
I'm
go
ahead.
A
I
mean
really
that's
all
that
it
is.
We
were
talking
in
the
dei
working
group
about
adding
on
a
newcomer
to
help
with
onboarding
and
just
integrating
people
better
into
the
community
and
giving
them
something
to
do
instead
of
just
like
leaving
it
so
open
of
you
know,
whatever
you
want
to
do
here.
We
are
it's
very
like
ambiguous
and
kind
of
fluid,
which
is
okay,
but
not
maybe
the
best.
A
So
we
thought
that
in
the
working
groups,
if
there
are
action
items-
and
there
are
new
people
around-
include
them
to
partner
with
someone
who's
been
in
the
community
for
a
while,
would
be
a
good
way
to
onboard
them
and
to
integrate
them.
Any
other
comments.
C
The
other
comment
was
for
those
of
us
that
have
been
in
the
project
for
a
while,
like
asking
people
to
do.
Mentorship
can
be
a
big
ask,
sometimes
like
the
concept
of
mentorship
so
like.
If
I
I
don't
know,
if
I
look
at
ildico
or
sophia
right
to
say
like
would
you
be
willing
to
mentor
a
newcomer?
That's
a
big!
C
That's
a
big
ask
right
to
mentor
into
the
community
and
assigning
with
an
action
item
could
be
a
lower
overhead
way,
and
it's
like
time
boxed,
you
know,
has
a
it's
a
very
particular
thing
that
a
couple
people
would
be
working
together
for
just
a
short
period
of
time.
This
would
be
somebody
experienced
in
a
newcomer
in
the
community.
H
C
C
Working
group,
if
you
have
newcomers
or
new
participants
and
you're
doing
action
items
just
to
think
about
asking
them
to
participate
or
to
be
included
if
they'd,
like.
A
All
right,
we
only
have
a
couple
minutes
so,
but
I
know
we
want
to
talk
about.
The
contributor
list
is
the
next
thing
on
the
agenda.
I'm
gonna
maybe
suggest
that
we
all
think
about
this
between
now
and
next
week,
because
maintaining
contributor
lists
is
getting
really
tricky
to
do
as
people
come
and
go
and
we
want
to
make
it
opt-in,
but
how
do
we
handle
like
old
metrics
and
things
like
that,
and
I
know
this
actually
came
from
from
some
concerns
that
kevin
had
while
doing
this.
A
The
latest
release
so
coming
out.
If
you
have
anything
to
add
real
quick
to
that.
B
Just
that
the
the
current
list
we
have,
I
don't
think
it's
it's
fully
up
to
date.
I
think
we're
missing
out
on
people
and
it's
it's
really
just
a
it's
a
list
in
markdown.
Currently,
so
it's
it's
a
list,
the
and
I
have
kind
of
compiled
and
then
to
your
point,
you
know
we'd
like
it
to
be
opt-in.
B
We
there.
I
think
there
are
considerations
for
how
we
collect
and
store
the
data
or
the
discussion
we
had
earlier
and
then
how
we,
how
we,
how
we
share,
who
who's
on
the
contributor
list
as
well.
So
I
think
there
are
a
lot
of.
B
I
think
there
are
some
some
data
privacy
issues
and
then
there's
also
just
some
logistics
so
on
how
we
can
how
we
can
better,
save
and
save
the
data
and
recognize
our
contributors.
So.
A
Then,
to
be
clear,
kevin
are
you
talking
mostly
about
the
contributor
lists
within
the
metrics
or
the
overall
big
list
that
we
will
post
on
the
website.
B
Okay,
so
it
is
the
I
think,
it's
the
second
to
last
page,
or
it
might
be
the
last
page
in
on
the
pdf.
B
So
as
far
as
collecting
the
contributors
for
each
individual
metric,
I
think
we
have
that
down,
and
that
is
that
is
purely
opt-in,
and
that
is,
if
you
work
on
creating
the
metric.
You
just
add
your
name
to
the
bottom
of
the
metric
when
we're
when
we're
building
it
or
when
you
do
a
pull
request
on
the
on
the
item
or
on
the
on
the
metric.
B
So
I
am
talking
about
the
overall
contributors
list,
so
this
is
everyone
who
has
contributed
to
chaos
in
any
way
whatsoever,
and
we
have
been.
We
have
been
including
that
list
on
the
metrics
release.
As
I
said
on
the
I
think
it's
the
second
to
last
page,
and
it
is
really
just
a
it's
just
a
list
of
a
bunch
of
people.
J
I
have
a
question
which
isn't
the
best
way
to
answer
a
question,
but
the
the
who
contributes
where
metrics
group
that
came
up
with
the
various
views
of
different
types
of
contribution
I'd
be
curious
to
get
their
thoughts
on
how
to
organize
that,
because
I
know
having
just
a
list
of
contributors
might
not
necessarily
be
as
descriptive
as
you
wanted
to
be
just
who
was
involved,
who
wasn't
involved
versus
actually
providing
more
description
over
time
role,
function,
contribution,
type
and
impact.
J
If
we
do
want
to
get
more
specific
in
terms
of
how
people
contribute
in
the
amount
of
time,
they
contribute,
I'm
not
sure
emily
brown.
But
I
feel
like
that's
a
good
question
as
well,
because
I
may
get
aligned
with
that.
F
Yeah-
and
I
was
just
going
back
to
the
previous
discussion
as
well
during
ato,
there
was
a
lot
of
presentations
that
covered
people
who
are
coming
onto
the
project
who
know
about
open
source
in
general
and
aren't
familiar
with
the
ways
that
they
can
contribute
so
having
a
document
for
each
of
the
projects
or
each
like
you
know,
each
of
the
initiatives
could
really
help.
F
A
That's
really
that's
a
really
great
suggestion
and
love
that
context
around
the
other
benefits
that
it
provides
besides
recognition,
but
it's
also
a
signal
to
newcomers
for
what
they
can
do.
Sadly,
we
are
out
of
time
we're
actually
overtime.
So
let's
continue
this
next
week,
if
that's
okay
with
everybody,
also
just
so
just
to
bring
attention
to
it
all
the
chaos
metrics
have
been
translated
to
chinese.
So
thank
you.
Thank
you.
A
Thank
you
to
our
chinese
community
for
being
so
very
awesome
and
dedicated
and
devoted
to
chaos
and
keeping
it
up
to
date.
We
really
appreciate
you
all.
I
think
that's
it.
For
now,
everybody
have
a
great
rest
of
your
week
and
anything
we
didn't
get
to
talk
about.
Just
add
it
to
the
agenda
for
next
week,
we'll
make
sure
to
put
it
at
the
top.
So
thanks
everyone
take
care
of
yourselves,
see
y'all
later
see.