►
From YouTube: CHAOSS Community Meeting July 26, 2022
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
A
A
couple
that
we
have
a-
I
don't
know
a
pretty
decent
agenda
today,
but
I
don't
think
a
lot
of
the
things
will
take
too
long.
So
this
is
just
a
reminder:
kind
of
for
everybody
for
just
doing
some
repository
cleanup
so
as
as
you're
kind
of
going
through
and
doing
metrics
reviews.
A
If
you
could
take
a
look
at
oh
just
things
like
whether
or
not
the
metrics
that
you
have
there
are
in
line
with
the
spreadsheet,
the
the
metrics.
The
the
links
that
you
have
provided
to
metrics
are
actually
active
in
your
github
repository,
so
you
know
how
we
have
those
some
of
those
initial
pages
here.
I'll
show
you
give
me
just
a
second
here.
A
A
A
A
A
Thanks
to,
let's
see
who
did
we
have
so
we
have
oma
who's
been
helping
out
and
precious
who's
been
helping
out,
and
so
you
can
see
kind
of.
In
this
column,
e
they've
just
been
taking
a
look,
and
myself
have
been
taking
a
look
at
the
released,
metrics
and
created
documents
that
are
any
suggested
changes
to
the
metrics.
So
each
of
the
working
groups
should
be
taking
a
look
at
their
metrics
kind
of
these
green
columns
or
I'm
sorry,
these
green
rows
that
you
have
and
provide
provide
some
some
commentary.
A
A
All
right,
it's
a
fairly
silent
group
today
and
I
think
I'm
the
only
one
with
video.
So
all
right.
So,
let's
see
how
about
to
do
group
associates.
I'm
not
sure
who
put
this
here.
C
That's
that's
for
me:
we've
been
working
with
anna
a
few
of
us
at
to
do
group
and
anna's
encouraged
chaos
to
become,
and
us
I
believe
it's
called
an
associate
member
where
we
would
and
I've
heard
you
know.
We
discussed
this
a
little
bit
at
the
board
meeting
and
I've
heard
different
perspectives
on
whether
or
not
to
to
make
that
affiliation.
D
The
way
that
to
do
group
has
operated
in
the
past
is
that
the
only
people
who
are
allowed
to
be
members
were
people
with
active,
open
source
program
offices,
and
this
was
deliberate
because
there
are
a
whole
set
of
people
who
really
just
want
to
sell
stuff
into
open
source
program
offices,
and
this
is
really
the
to-do
group
is
really
our
place
to
talk
amongst
ourselves
as
open
source
program
offices.
D
Without
having
that
constant,
you
know
people
trying
to
sell
us
things
so
so
to
be
a
full
member
of
the
to
do
group.
You
have
to
be
have
an
ospo
and
be
a
linux
foundation
member,
but
there
are
a
lot
of
these
other
things
that
are
kind
of
tangential.
D
Now
when
they
originally
came
to
us
with
this,
the
ospo
associates
program
was
not
well
defined.
We
didn't
the
to-do
group,
really
hadn't
decided
what
it
needed
to
be,
and
so
I
think
the
discussion
on
the
chaos
board
list
was,
you
know
we
don't
know
if
we
want
to
do
this
because
we
don't
know
what
it
means,
but
since
there's
been
a
bit
more
definition
behind
it
and
it
looks
like
what
what
we
want
to
do
is
actually
do
some
things
together.
D
So
there
are
some
new
programs
in
place
like
osbo
ology,
which
is
a
monthly
meetup
that
anyone
can
join.
You
don't
need
to
be
a
to-do
group
member,
but
we
could
partner
up
and
we
could
do
like
some
sort
of
like
joint
to
do.
Group
chaos
talk
maybe
at
one
of
these
hospitality
sessions
or
so
there's
more
stuff
that
we
feel
like
we
could
do
together
now,
just
because
the
the
to
do
group
under
you
know
anna's
lovely
program.
D
Management
has
expanded
drastically
from
what
we
what
we
used
to
do
so
I
mean
I
I
guess
I
you
know
I'm
kind
of
on
on
both
sides.
So
there's
a
bit
of
a
you
know
competing
interests
there,
but
it,
it
seems
to
me
like
it's
probably
in
the
best
interest
of
both
both
chaos
and
and
the
to-do
group.
C
D
D
Bit
in
this
list
that
you're,
showing
here
on
the
screen
that
was
missing,
I
think
the
original
one
was
this
to
do:
support
to
co-create
content.
It
looked
like
a
logo
exchange
the
first
time
we
looked
at
it,
which
isn't
that
interesting,
everybody
in
the
to-do
group
knows
about
the
chaos
project.
So
a
logo
exchange
didn't
really
didn't
really
buy
us
anything,
but
I
do
think
that
you
know
the
opportunity
to
do
to
do
more
jointly
with
the
two
organizations
is
where,
where
the
real
value
sits,.
A
I
think
it's
a
great
group
the
to
do
group
like
you
were
pointing
out
don
and
shawn.
The
overlap
is
pretty
clear
between
chaos
and
the
to
do
group
so.
C
B
A
In
the
ospology
is
that
that
is
that
the
the
like
the
monthly
talks
is
that
right
is
that
what
that
is?
We
were
because
stephen
jacobs
at
rit
was
mentioning
that
as
well.
D
Yeah
he
he
did.
I
think
he
did
one
of
the
talks
actually
for
for
oscillology
sessions,
but
yeah
they're,
they're
monthly
talks
on
topics
that
are
of
interest
to
to
do
groups,
but
anyone
anyone
can
join
and
then
I
think,
there's
also
an
osbology
repo,
where
there
might
be
some
discussions
and
other
things
around
it
as
well.
A
E
B
C
D
Yeah
it
didn't,
it
didn't,
really
look
like
it
had
any
benefit
for
us,
because
it
really
did
just
kind
of
look
like
a
logo
exchange,
and
so
I
think
that's
where
most
of
the
discussions
were
on
the
mailing
list.
It
might
be
good
to
go
back
before
we
fill
out
this
form
and
just
make
sure
that
we
didn't
forget
anything
that
we
talked
about.
A
For
sure,
do
you
think
I
should
send
this
out
back
to
the
board
list?
I
mean
we,
don't
it's
pretty
informal
as
to
how
we
would
if
it
like,
if
we
were
gonna,
do
this
like
do
we
need
approval?
C
I
have
no
idea
if
we
need
approval,
we
haven't
read
our,
but
it
seems
like
it
would
be.
You
know
it
seems
like
a
reasonable
step
to
circulate
it
to
the
executive
board,
for
you
know
see
if
there's
any
objection.
Okay,
I
can't
imagine
one
but
yeah.
B
A
Okay,
cool.
Thank
you
dawn
thanks,
sean.
A
C
Yeah,
I
think,
when
I
was
in
looking
at
the
previous
agenda
and
bringing
things
up
I
didn't
know
if
there
was
any,
I
we
discussed
project
badging
a
good
deal,
the
last
time
and
kind
of
went
away
to
think
about
it.
So
I
would,
I
thought,
I'd
throw
it
in
there,
but
we
don't
need
to
talk
about
it
today.
We
did
talk
about
it
quite
a
lot.
Last
week
last
week,.
A
C
A
Okay,
let's
see
question
from
the
community
handbook
team.
Is
there
anything
we
want
to
update
on
the
roadmap
I'm
guessing?
This
is
from
ruth
ruth
if
you're
on
yeah.
F
That's
from
me,
so
could
you
just
navigate
to
so
I
was
going
to
ask
if
this
was
up
to
date
and
if
you
wanted
to
update
anything
the
roadmap.
C
F
F
A
E
B
E
B
E
A
I'm
with
kevin
on
that
so
road
map,
and
then
you
read
that
it's
our
strategic
plan
and
then
I
look
at
the
four
things
and
they're
components
of
what
we
do,
which
seems
a
little
different.
So
maybe
the
suggestion
would
be
like
right.
It
could
be
a
couple
of
different
things
it
could
be.
These
are
the
this
is
who
we
are
kind
of
thing.
F
F
Not
really
it
just
talks
about
specific
terms,
there's
just
one
part
of
the
handbook
that
talks
about
like
specific
terms,
and
then
it
comes
from
working
groups
to
match
specific
terms
and
then
to
software
to
different
software,
so
that
talks
about
specific
dams.
B
E
So
we
do,
we
do
have
kind
of
some
of
this
information
on
the
website
in
different
ways,
and
I
do
have
some
ideas
on
how
we
can
kind
of
start
to
kind
of
split
this
out
and
kind
of
go
into
more
depth
on
here,
but
yeah.
E
I
think
it's
it's
two
different
things,
one
it's
kind
of
the
our
mission
or
strategy,
but
then
it's
also
the
like
the
how
we
do
our
work,
ruth
if
you
want
to,
if
you
want
to
chat
more
out
outside
of
this
meeting,
I'd,
be
happy
to
to
to
talk
to
you
more
about
it.
Maybe
in
the
next
web
content
meeting.
B
I
feel
this
is
like
the
three-part
process,
what
we
are
and
what
we
do,
what
you
short
math
is
what
we
do
and
what
we
want
to
achieve.
Maybe
a
goal
should
be
a
third
step.
What
we
are
is
a
history
or
what
we
have
been
doing
and
like
this,
the
slide
which
ruth
has
compiled
or
the
github
it
tells
us
what
we
are
doing
currently.
E
Yeah,
I
think
I
think,
that's
fair.
I
think
that's
kind
of
that's
a
little
bit
how
I
think
about
it
on
the
website
as
well.
B
So
this
link
goes
to
what
we
do,
the
one
which
the
roadmap
current
roadmap
tells
us
what
we
do
basically.
F
E
F
People,
the
main
commentary
poster
if
you
check
the
about
folder
you'd,
see
the
word
map.
F
Yeah
we
we
have,
we
do
have
admission
documents,
I
think
so.
Let
me
quickly
check.
F
Here
we
have
admission
history.
E
Yeah,
I
think
I
think
we
just
need
to
kind
of
separate
some
of
this
stuff
out,
so
maybe
push
some
of
it
into
our
mission,
push
some
of
it
into
the
about
and
maybe
push
some
of
it
into
a
a
third
document
that
maybe
describes
the
structure
of
how
we
do
work.
A
Oh
those
last
a
long
time.
Okay,
all
right
so
so
kind
of
the
action
item
it
sounded
like
was
kevin.
You
and
ruth
can
connect.
Maybe
in
the
web
content
meeting.
I
don't
know
if
it's
coming
up
later
this
week.
F
F
A
Website,
as
they
are
two
different
things,
obviously
like
how
much
do
you
see
a
lot
of
overlap
between
the
two
I.
E
Ideally,
I
would
like
to
pull
all
of
our
content
from
from
the
website
and
github
repositories,
so
the
the
documents
that
ruth
is
creating.
I
ideally
those
are
those
are
documents
that
I
could
also
use
on
the
the
website.
So
there
there
should
be.
There
should
be
overlap.
A
E
A
All
right,
great
cool,
any
other
comments,
ruth
about
the
road
map.
A
Any
other
questions
for
per
ruth
or
kevin
on
this.
Okay,
all
right
great
sean-
I
don't
know
if
you
know
this,
I
don't
think
you've
done
a
risk.
Working
group
update.
C
Are
we
actually,
I
think,
did
you
do
one
we
did?
It
was
sophia-
and
I
maybe
not
last
week,
but
maybe
the
week
before,
I'm.
A
Are
there
other
working
groups
that
would
like
to
to
kind
of
talk
about
the
work
that
they're
doing?
I
know
that
several
working
groups
have
spoken
so
far,
just
updates
sometimes
they're,
pretty
straightforward.
It's
just
things
like
new
metrics
that
are
being
deployed
or
revisions
that
are
currently
being
done,
or
efforts
that
are
being
undertaken
in
the
working
group.
C
I
can
I
can
report
back
that
last
week
we
said
the
evolution
working
group
would
have
built
the
metrics.
They
need
to
build
okay
and
then,
in
the
metrics
models
meeting
we
identified
three
new
evolution
metrics
that
are
desired.
So
that's
right.
I
shouldn't
have
spoken
up
last
week
at
this
meeting.
B
A
Thanks,
let's
see
a
couple
things
here,
just
as
as
we
hit
the
27
after
context
tagging,
so
this
is
something
that
we,
I
think
we
had
talked
about
last
week
in
the
community
call,
and
we
talked
about
it
more
in
the
common
working
group.
A
B
A
In
the
spreadsheet,
this
has
been
updated.
Thank
you
kevin
for
paying
me,
but
we
would
put
what
the
context
tags
are
for
a
particular
metric,
so
say,
for
example,
for
diversity
access
tickets.
We
would
have
some
context
tags
that
we
apply
it's
up
to
the
to
the
working
groups
to
create
or
to
apply
the
context
tags
to
new
metrics
kevin,
and
I
are
going
to
be
going
through
really
across
all
of
these.
All
of
the
green
rows.
Every
released
metric
to
suggest
context
tags
for
every
metric.
A
B
A
Which,
I
think
is
okay.
I
think
we
were
pretty
happy
in
the
common
working
group
with
this
set
of
tags
does.
Does
anybody
have
any
comments?
First,
on
whether
I
got
that
right.
B
B
E
I'm
going
to
say
yes,
yes,
it
would
be
helpful,
so
I
mean,
if
you're
looking
for
a
community
metrics,
then
you
get
a
list
of
30
community
metrics.
So
I
I
think
that
would
be
helpful
as
far
as
the
search
down
to
more
specific
things
that
you're
trying
to
measure
or
understand,
that's
where
the
the
keyword
tags
would
come
in,
but
at
but
at
a
high
level
that
that
first
initial
search
where
you
say
to
yourself,
you
know
I'm
looking
for
community
metrics.
E
I
think
a
list
that
that
comes
in
large
can
help
you
understand
what
what
those
community
metrics
are
looking
at.
E
You
can
kind
of
compare
some
of
the
metrics
and
models
that
you
see
from
that
and
a
new
user
could
could
then
take
that
and
probably
do
a
kind
of
a
more
complex
search
based
on
keywords
that
they
need.
So
so
I
would
say
yes,
it's
probably.
I
think
it
will
be
useful
and
I
think
it
will
kind
of
work
as
designed.
E
However,
to
be
honest
with
you
a
little
bit
of
it
is
going
to
be,
I
think
some
of
that
will
kind
of
we'll
figure
it
out,
as
we
start
dropping
these
metrics
into
the
into
the
context
areas.
You
know.
One
of
one
of
my
worries
was
that
you
know
we
have
70
metrics
and
35
of
them
would
be
in
one
context.
Area
and
35
would
be
in
another
context
area
and,
and
we
wouldn't
be
using
any
of
the
other
context
areas.
E
E
E
So
sorry,
I
think
I
I
was
a
little
long-winded,
but
hopefully
that
answers
your
question.
C
My
my
thought
was
the
other
thing.
That's
this
just
enables
a
lot
of
different
kinds
of
information:
navigation,
for
example,
we
could
have
everything
in
a
table
all
70,
some
metrics
sortable
by
the
context,
tags
or
alphabetically
filterable.
So
I
think
in
this
way
it's
easier
to
scan
through
what
we
have
right
now.
I
think
it
is
fairly
difficult
to
scan
through
because
everything
is
organized
by
working
group
and
that
may
not
represent
the
way
that
people
logically
consume
our
metrics.
So
again,
I
think
become
overwhelming.
E
A
B
Just
in
continuation,
we
can
put
this
as
a
future
implementation
either
we
do
it
ourselves
or
we
make
it
for
a
google
summer
of
a
good
person.
We
can
use
nlp
to
do
this
kind
of
work.
Make
it
very.
B
E
So
this
is,
this
is
work
that
we
are
doing
right
now
and
we
are
doing
it
as
part
of
google
summer
of
code.
E
However,
the
the
framework
that
we're
building
here
with
the
the
context
tags
and
the
keywords
would
allow
us
to
to
build
more
complicated
and
better
versions
of
kind
of
search
and
metrics
presentation
in
the
future.
So
so
I
would
agree
with
both
what
sean
said
a
moment
ago
and
what
armstrong
just
said.
A
All
right,
so
thank
you
for
the
comments
and
questions
kevin.
I
think
our
just
the
the
next
action
item,
if
we're
comfortable
with
this
set,
is
that
you-
and
I
are
gonna,
like
I
said-
gonna-
be
going
through
these.
Essentially
these
green
rows
and
providing
suggestions
to
the
working
groups
as
to
what
those
context
tags
could
be.
E
Agreed
yes,
yep
and
actually
I've
already
gone
through
for
common
and
evolution
and
value.
B
A
A
E
Was
actually
wondering
if
you
could
maybe
take
a
look
and
yeah
and
see
if
you
agree
or
disagree,
okay
with
the
ones
that
I
put
in,
and
I
I
actually
I
avoided
putting
in
two,
because
I
wanted
to
with
the
keywords
and
the
context
tags.
I
think
the
I
think
they're
gonna
work
best
if
we
really
try
to
limit
the
limit
them
to
like
the
really
obvious
ones
like
we
don't
wanna,
we
won't.
We
don't
wanna,
dig
and
force
these
to
happen.
A
E
Yeah
or
we
could
or
we
could
move
on
to
the
the
keywords
and
issue
the
context,
tag
and
keyword
pr's.
At
the
same
time,.
A
Okay,
that's
a
good
idea,
a
little
less
annoying,
I'm
just
trying
to
keep
the
noise
down
on
github
when
we
can
do
it
all
here.
A
little
bit.
Okay
sounds
good
great!
Thank
you
and
yes,
I
will
take
a
look
at
those
all
right.
Any
other
comments
on
context,
tagging
and
subsequently
keyword,
tagging
so
context.
A
E
Oh
and
a
and
a
reminder
that
these
these
tags,
so
we
did
we
just
mentioned
prs,
so
the
these
tags
will
be
added
to
the
the
metrics
documents
themselves
and
will
be
part
of
the
the
metrics
template
document.
Oh
yeah,
I
should
probably.
A
Sorry
last
couple
things
here:
google
summer
of
code
evals
are
due
this
week,
so
I'm
not
sure
how
many
mentors
we
have
on
the
call
but
they're
due
this
week
and
I
think
like
sean.
I
think
you
can
do
your
independently
kevin
doing
his.
For
example,
yeah
yeah.
A
But
they
can
occur
like
one
at
a
time.
Is
that
right,
absolutely
absolutely
okay,
it
doesn't
have
to
be
one
person
submitting
all
evals
at
one
time.
C
A
E
It
is,
it
is
just
one
mentor
submitting
an
evaluation
per
mentee,
though
right,
correct,
yes,
okay,.
A
So
if
there's
other,
I
would
guess
your
question
is
like:
if
there
are
other
mentors
you
might
want
to
coordinate
with
all
mentors
just
to
make
sure
everybody's
satisfied
with
yes,
yeah,
okay,
cool,
all
right
great,
so
these
are
gonna
occur.
I
don't
even
know
how
many
google
summer
code
students
we
have
right
now,
six
five.
A
So
these
are
all
going
to
kind
of
occur
independently,
with
the
mentors
and
I'll
just
keep
sending
reminders
to
slack,
and
we
should
probably
take
a
look
at
make
sure
that
we
connect
directly
with
the
mentors
if
they're
not
watching
that
channel
all
right.
So
that's
google
summer
of
code
evals
due
this
week
and
it's
we
have
to
do
them.
A
There's
there's
no
like
there's,
no
there's
no
late
period
that
we
can
do
them
later
so
and
then
last
thing
for
this
week
is
a
chaos
con.
So
we
have
three
sponsors.
So
thank
you
to
google,
to
red
hat
and
to
betergia.
A
So
that's
awesome.
So
we
were
really
happy
and
really
lucky.
So
we
will
get
like
coffee
and
stuff
like
that
for
chaos.
Con
no
problem
there
and
then
kevin,
I
just
I'll
there's
a
logo
or
red
hat
that
needs
to
be.
E
The
link
isn't
working.
Okay,
I'll
double
check
that,
while
I'm
there.
A
Okay,
all
right,
so
that's
great
news,
all
right,
everybody!
That's
it
does
anybody
else
have
anything
they
would
like
to
talk
about.
Today
we
have
a
few
minutes,
but
other
than
that,
we'll
open
it.