►
From YouTube: CHAOSS Common Working Group March 16 2023
Description
Meeting minutes can be found here: https://docs.google.com/document/d/1xsii5tfmmDwWpuhrFcBJMeYeT3RipJdiCdHrbi0NalQ/edit
E
And
also
I
I
agree
with
the
complexity
of
the
project,
so
the
Hope
here
is
not
to
to
create
more
complexity.
It's
to
provide
an
opportunity
for
folks
who
want
to
engage
with
the
chaos
resources,
the
things
that
we
have
in
ways
that
are
meaningful
to
them.
A
A
Yeah
well,
and
to
be
clear:
the
complexity
as
I
see
it
isn't
a
isn't
a
bad
thing.
I
think
it's
actually
a
good
thing
like
the
project
is
evolving
and
we're
getting
more
groups
involved,
we're
getting
more
people
involved
and
I
think
this
is.
This
is
a
natural
evolution
of
the
growth
of
an
open
source
project
they
get,
they
get
more
complex,
but
it's
it's
a
good
thing.
I
think
we're
doing
it
in
a
way
that
makes
it
a
good
thing
and
not
a
just
complexity
for
complexity.
Right.
E
E
Any
other
comments,
then
we
can
move
on
okay,
so
we
have
a
new
metric
so
don.
This
is
what
you
put
on
right
here:
I'm
guessing
yes,
yes,
okay,.
E
And
it
was
I
guess
the
one
question
was:
is
this
going
to
remove
the
other
metric?
That
was
like
the
one
main
question
remember
there
were.
A
A
A
I
would
see,
I
would
see
us
removing
time
to
close
and
replacing
it
with
this
one.
Okay,
just
because
the
start
of
project
health
is
supposed
to
be.
A
E
E
A
The
auger
visual
Sean,
because
it's
not
in
the
pr.
B
A
D
D
No
I
was
I
was
here
well,
not
in
the
metrics
models,
but
I
was
I
was
here
in
the
meeting
where
we
edited
this
document
in
common
and
then
the
after
that
those
edits
were
made.
I
think
Don
made
the
pr
a
couple
hours
later.
Is
that
correct,
yeah.
A
B
C
E
C
The
change
I
made
is
this
visualization
actually
wasn't
there
the
there
was
a
link
to
the
PNG
file,
but
there
was
not
a
this,
but
this
wasn't
in
the
document,
so
I
clicked
on
that
PNG
and
put
it
in
the
document.
E
A
Was
there
so.
B
B
A
Okay,
Matt,
can
you
can
you
go
to
file
inversions
and
let's
just
look
I'm.
D
E
B
A
And
so
I
will
incorporate
the
ratio
metric
into
the
model.
E
D
C
E
Okay,
all
right
anything
else,
you
need
on
that
done.
E
Thank
you
all
right
so
yesterday
in
Dei.
A
B
E
In
their
repos,
these
are
the
kind
of
just
long-standing,
not
just
they've,
always
just
kind
of
been
there.
E
Four
metrics
that
we
were
asking
for
with
respect
to
the
dei.md
file
that
we
would
have
in
a
project
comment
on
how
they
address
newcomer
experience,
how
they
address,
project,
burnout
and
so
on
and
so
forth,
and
then,
as
they
move
up,
they
have
to
address
an
those
original,
four
plus
two
new
metrics
and
so
on.
E
So
the
discussion
that
came
up
yesterday
was
about
kind
of
really
thinking
through
what
these
four
metrics
should
be,
with
respect
to
kind
of
that
bronze
level
and
then
subsequently,
through
silver,
through
gold
and
through
Platinum.
What
those
four
original
metrics
should
be
and
the
the
the
two
that
came
up
as
maybe
something
later
down
the
road
that
we
would
ask
for
our
project
burnout.
For
example,
how
does
a
project
address
project
burnout
within
their
their
work?
And
then
how
does
that
project
recognize
contributors
in
their
work?
E
E
Project
accessibility,
which
is
a
metric
that
we
have
a
event,
location,
accessibility,
so
I
think
it
would
be
moderately
related
to
that,
and
then
communication
transparency
so
like
ensuring
that
the
community
is,
you
know,
has
open
in
public
documents
that
the
repositories
are
open
in
public,
that
all
meetings
are
open,
public,
transparent,
accessible
transcriptions
are
providing.
You
know
the
kind
of
things
like
this.
How
do
you?
How
does
your
community
work
to
to
be
open
and
and
transparent
in
your
work?
E
D
D
A
That
was
defined
because
I
think
it
depends
a
little
bit
on
how
that
bind,
whether
or
not
that
would
be
a
good
one
for
bronze
or
whether
that
would
be
more
appropriate
for
the
next
level,
because
if
it's,
you
know
like
hardcore
accessibility
topics
that
sometimes
takes
projects
a
little
while
to
find
someone
who
can
help
with
you
know,
is
it
accessible
via
screen?
A
Readers
is
that
you
know,
there's
there's
a
bunch
of
accessibility
stuff
that
a
brand
new
open
source
project
might
not
have
done
yet,
even
though
I
would
have
I
would
like
for
them
to,
but
it
requires
some
special
skills
to
do
some
of
that
kind
of
Hardcore
stuff.
We.
D
Did
talk
about
that
a
little
bit
yesterday?
This
is
more
kind
of
about
General
accessibility
and
it
doesn't
really
get
into
the
specific
accessibility
of
the
the
software
or
the
kind
of
the
that
Nielsen
Norman
accessibility
like
colorblindness
and
things
of
that
nature.
So
it's
more
about
kind
of
General
project,
accessibility,
okay,.
D
It's
on
an
on
an
open
platform:
I
suppose
you
have
access,
you
have
access
to
the
code.
I
mean
it's
kind
of
that
that
General
the
general
openness
of
the
project
right,
so
the
that,
at
a
base
level,
open
source
allows
you
to
do
these
things
and,
and
the
project
is
allowing
you
to
do
these
things
as
well.
Right,
okay,.
D
Little
bit
I
think
the
one
is
kind
of
about
the
maybe
the
platform
and
the
artifacts
being
accessible
and
the
other
one
is
kind
of
about
the
process
and
the
communication
being,
but
it's
generally
the
they
could
both
be
called
transparency
or
both
be
accessibility
or
both
be
openness
or
some
it's,
but
the
one
is
the
one
is
kind
of
about
the
platform
and
the
artifacts
and
the
other
one
is
about
the
work
process
and
the
communication,
but
transparency
around
both
of
them
and
access
to
both
of
them
is
what
I'm
getting
at
for
what
I'm
proposing,
because
at
a
base
level,
that's
the
like,
if
you're
looking
at
project,
if
you
don't
have
access
to
these,
then
your
you're
not
welcome.
A
I
would
maybe
sorry
can
we
go
back
to
the
project.
Accessibility,
I
would
maybe
call
that
something
else
and
not
not
use
the
word
accessibility,
because
I
think
that
that
you
know,
like
I,
immediately,
went
to
screen
readers,
and
you
know
colorblindness
and
sort
of
like
that
sort
of
thing.
E
D
And
I
do
want
to
reiterate
that
so
when
I,
when
I,
when
I
thought
of
these
two,
that
was
just
I
kind
of
thought
of
them
pretty
quickly
when
when
we
dropped
them
in
so
maybe
the
maybe
the
four
that
we're
choosing
aren't
don't
include
these
two,
but
my
my
inspiration
for
having
this
conversation
is
around
the
the
the
model
that
Dawn
had
proposed.
So
what
are
those?
What
are
those
four
starter
metrics
that
we
would
look
at
for
for
this?
D
So
maybe
it's!
Maybe
it's
not
these
two.
Maybe
it's
maybe
it's.
If
anyone
else
has
any
other
ideas
on
two
that
could
be
included
here
or
four
that
can
be
included.
I.
C
Yeah
and
I
think,
for
example,
access
to
project
work
times
or
communication
tools
that
involves
some
of
the
website
stuff,
where
you
actually
have
to
make
that
visible
to
people
I
think
like
access
to
project
documentation
like
honestly,
a
lot
of
Open
Source
projects
more
more
than
not
seem
to
be
poorly
documented.
C
B
C
So
I
mean
you
know:
I
guess:
hap
I
guess
having
it
as
opposed
to
not
having
it
is
good,
I!
Think
I,
wonder
if
there's
any
do
you
have
any
known
benchmarks
for
software
documentation
quality
done.
Is
anybody
trying
to
measure
that
that
needs
sounds.
B
F
F
Publish
and
I
mean
it's
I
agree
with
you,
it's
something
that
is
very
common
within
the
open
source
war,
and
one
good
aspect
that
we
can
look
at
documentation
is
to
copy
the
model
from
openstack.
They
treat
documentation
the
same
way
they
treat
code,
so
they
try
to
bring
in
contributions
in
that
space
and
give
credit
for
people
the
same
way.
F
Pull
requests
in
developing
complex
algorithm
is
done
so
in
that
way,
people
with
without
technical
background
have
grid
visibility
when
they're
rewarding
contributors
in
the
community
that
has
really
improved
their
documentation
tremendously
one
other
way.
We
could
also
improve
documentation.
I
mean
it's
still
new,
but
it's
working
for
the
trial
versions
is
using
a
kind
of
language
model.
To
explain
I
mean
those
are
things
we
can
discuss
later,
but
for
now
we
could
really
improve
copy
the
model
from
openstack.
It
works
very
well
and
I've
been
in
that
Community
I
see
yeah,
okay,.
D
I
was
just
gonna
say:
maybe
we
can
add.
Maybe
we
can
add
documentation
quality
as
a
as
a
metric
to
look
at
in
the
future
and
I
would
say
if,
if
we're
quality
metrics,
if
we're
adding
them
to
project
badging,
those
probably
are
down
down
the
line
in
gold
or
Platinum.
If
we're
starting
to
measure
quality,
I
think
early
on
in
early
on
in
bronze,
it's
more
about.
Do
these
things
exist
and
then
I.
Think
as
you
go,
you
go
down
through
the
that
the
badging
it
it
becomes.
F
B
C
C
It
was
documentation,
we
don't
know
who
abandons
even
trying,
because
the
documentation
is
support
or
it
doesn't
meet
meet
newcomers
where
they
are
so
that's
kind
of
the
case.
I
was
thinking
of.
F
F
A
lot
of
API
calls
have
changed.
The
documentation
is
not
reflecting
the
new
version.
There
was
a
space
where
you
need
to
do
a
CD
into
a
folder
that
folder
has
been
removed,
and
things
like
that,
so
people
keep
on
in
the
loop
of
the
oral
project.
It's
not
just
working,
so
they
cannot
even
understand
what
is
happening
foreign
at
times
like
the
openstack
model.
They
make
sure
that
documentation
and
code
goes
hand
in
hand.
Any
change
in
the
source
code
reflects
immediately
in
the
document
before
it
is
released.
A
The
other
thing
I'd
like
to
add
for
a
future
future
one
for
one
of
the
higher
levels
is
clear:
governance,
documentation
that
shows
a
path
to
leadership,
because
I
think
that's
super
important
I
mean
I'm
just
going
to
be
on
my
governance,
bandwagon
for.
C
B
E
E
D
F
D
D
F
C
D
Georg
had
access
to
that
all
along.
He
had
access
to
it,
but
I
think
he
had
stepped
away
from
the
project
for
kind
of
personal
reasons,
for
it's
a
short
period
of
time,
so
he
wasn't
around
during
that
that
conversation,
but
I
believe
him
and
Elizabeth
had
gotten
together
and
access
may
have
been
shared
okay,
so
it
sounds
good.
That's
awesome!
Okay,.
B
E
Couple
of
items
and
look
forward
to
seeing
you
all
again
thanks
for
coming
awesome.