►
From YouTube: CHAOSS Weekly Community Call 5/10/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
Opening
our
discussion
today
is
just
a
reminder
that
we're
looking
for
new
badgers,
which
I
believe
is
a
brand
new
name
for
people
who
participate
in
helping
to
badge
at
this
point
events
and
at
some
future
date,
projects
in
the
chaos
working
group
for
diversity,
equity
and
inclusion
matt.
I
don't
know
if
you
want
to
elaborate
on
that
any
further,
but
there's
an
info
session
on
may
18th
at
noon.
Central
time.
B
A
That's
awesome.
I
think
I
saw
a
picture
of
that
when
I
was
in
the
dei
meeting
yesterday,
so
that
that's
pretty
exciting,
there's
just
an
fy
in
here
that
increased
notifications
in
the
general
channel
for
reading
reminder
changes
and
additions
along
along
with
that
I'll.
Just
remind
folks
that
monday
may
30th
2022
at
11,
59,
pacific
daylight
time
is
the
deadline
for
submitting
things
to
the
open
source
summit.
Europe
and
if
you
do
submit
a
chaos
related
talk,
we'd
love
to
know
about
it.
So
make
a
make
a
point
of
sharing
that
with
us.
A
C
C
I
don't
know
how
forgotten
topic
I
submitted,
but
but
yes,
it's
it's.
It's
kind
of
like
shining
the
light
on
talking
about
di
metrics
that
we've
worked
on.
You
know
di
group,
so
I
kind
of
want
to
talk
about
how
to
or
take
folks
like
through,
like
a
session
on
the
different
focus
areas
we
have
in
di
group
and
how
you
know
folks
can
build
diverse
and
inclusive
open
source
communities.
C
A
Yeah
we'd
like
to,
I
think
we
decided
at
one
point
in
one
of
these
meetings
that
we
want
to
just
make
some
awareness
or
promotion
of
the
folks
within
the
community
who
are
giving
community
related
talks,
or,
if
you
have
another
talk
that
you'd
like
us
to
promote.
I
think
we'd
be
happy
to
do
that
as
well.
C
A
I'm
wondering
if
anyone
has
an
update
or
if
that
is
a
task
that
perhaps
needs
an
owner.
B
A
A
Okay,
and
are
we,
as
I
would
imagine,
the
transition
time,
then,
would
be
somewhere
over
the
summer,
where
we
would
maintain
the
mailing
list
for
broadcast,
but
not
communication
and
use
discourse
as
our
primary
means
of
reaching
out
to
the
community,
where
slack
had
primarily
been
our
channel
up.
To
that
point,
I
think
so.
Some
really
think
it's
a
good
bet,
okay,
excellent,
making
another
segue
and
swiftly
proceeding
through
the
agenda.
A
A
I
don't
have
a,
I
don't
have
it
in
my
head
who's.
I
know
I'm
looking
at
common,
but
I
don't
have
it
in
my
head
who's.
Looking
at
every
working
group,
I've
I've
seen
issues
created
around
metric
updates
in
most
of
the
working
groups.
I
noticed
in
the
risk
meeting
last
week
that
we
hadn't
gotten
any
yet,
and
I'm
wondering
I
guess
suppose
I
just
asked
the
question
with
regards
to
first
looking
for
prs
and
then
second,
the
process
for
updating
old,
metrics.
B
So
that
was
me
to
put
that
in
there.
So
just
for
the
working
groups,
you
may
start
seeing
some
prs
come
across,
which
are
just
some
proposed
updates
to
your
metrics.
You
know
like
maybe
some
formatting
changes
or
there's
something
in
a
list
form
that's
being
redundant
or
some
clarity
needs
to
be
made.
So
I
just
want
you
to
kind
of
keep
an
eye
out
for
those
pr's
coming
in.
As
you
see
them,
could
you
maybe
do
a
few
things?
B
One
just
link
it
to
the
issue
that
was
put
forward
not
or
just
ask
the
individual
who
has
put
the
pr
forward
to
link
it
to
the
associated
issue
and
then
also
in
the
pr
kind
of
articulate
what
it
is.
That's
changed.
A
lot
of
the
pr's
are
pretty
straightforward.
A
B
So
I
put
the
structure
that
sean
was
talking
about
in
the
chat.
I
think
you
know
one
of
the
big
things
that
we're
doing
in
the
metrics
model
working
group
is
really
trying
to
focus
on
not
only
the
descriptions
of
the
models
but
all
the
way
through
implementation.
B
So,
as
a
lot
of
you
know
with
metrics
themselves,
sometimes
it's
hard
for
people
to
approach
just
a
single
metric
and
really
know
what
to
do
with
it,
and
we
didn't
want
to
have
that
same
problem
as
we're
aggregating
these
metrics
into
metrics
models
that
you
just
kind
of
look
at
this
markdown
file
as
a
consumer
of
a
metrics
model
and
be
like
yeah.
That
makes
sense,
but,
like
now,
what
like?
How
do
I?
How
do
I
actually
put
this
into
practice?
B
And
so
that's
we're
pretty
happy
about
that
that
design
and
we're
getting
some
good
traction
in
the
group
so
that
that
was
all
I
wanted
to
bring
up
that
we're
following
just
kind
of
a
different
model
than
metrics.
It's
not
about
just
quick
release
of
metrics
models,
but
thinking
all
the
way
through
the
implementation
component
of
it
as
well.
A
Excellent
and
those
those
meetings
are
every
other
tuesday
at
6
pm
and
the
next
one
is
today
at
6
p.m.
Central
time
so,
and
we
have
several
mentorship
programs
that
we're
active
in
including
outreachy
google,
summer
of
code
and
google
season
of
docs,
and
we
are
in
the
process
of
finalizing
those
selections.
A
Of
fact
so
you
should
be,
we
should
be
looking
for
some
announcements
along
those
lines
very
shortly.
A
Yeah
in
the
google
season
of
docs,
the
the
hiring
quote-unquote
decision
comes
from
us
and
we
are
free
to
make
an
announcement.
So
that
program
is
a
little
bit
different
than
the
other
two
in
a
number
of
ways.
A
So
that's
just
a
little
a
little
nuance
to
the
google
season
of
docs
approach
and
I
know
I've
been
in
a
number
of
discussions
in
the
dei
meeting
and
I
think
in
this
meeting
as
well
about
changes
proposed
in
the
code
of
conduct
for
for
chaos
and
we're
not
changing
what
it
is.
But
I
think
making
it
more
specific
in
some
cases
and
maybe
I'll
just
bring
that
up
for
a
moment.
B
Here
and
let's
yeah,
I
can
give
some
background
here.
This
stems
from
a
conversation
we
had
with
joanna
lee
who's
at
the
linux
foundation
and
there's
a
lawyer
who
works
with
the
linux
foundation
and
does
a
lot
of
work
around
codes
of
conduct,
and
she
gave
us
two
recommendations
with
respect
to
our
code
of
conduct.
B
One
was
to
have
a
single
code
of
conduct
for
the
events
and
for
the
project
itself,
so
we've
just
been
working
on
making
sure
the
language
in
our
existing
code
of
conduct
is
clear
around
the
fact
that
this
code
of
conduct
applies
really
to
everything,
chaos
related
and
then
the
second
is:
if
you
could
scroll
down
a
little
bit
sean,
I
can
keep
going
so
yes
yeah.
So
right
there
stop.
So
it's
an
enforcement
guidelines.
B
Our
prior
code
of
conduct
was
pretty
vague
on
how
enforcement
would
occur.
It
would
just
kind
of
be
like
submissions
would
go
to
a
code
of
conduct
enforcement
team
and
discussion
will
be
had
and
decisions
will
be
made
so
we're.
We
were
really
just
following
some
published
guidance
on
what
enforcement
could
look
like
around
the
code
of
conduct
and
that's
what's
been
added
here.
A
Then
the
enforcement
team
toward
a
specific
consequence
without
being
overly
directive
and
detailed,
which,
if
we
were
that,
then
we
would
end
up
with
an
endlessly
long
list
of
specific
effects
and
impacts
and
resulting
consequences.
So
I
think
I
think
it's
a
manageable.
What
I
like
about
it
is,
I
think
the
impacts
are
easily
understandable
in
general
and
and
therefore
it's
a
manageable
implementation
process.
B
Agreed
and
each
of
these
comes
from
the
contributor
covenant,
so
it's
not
something
that
we
wrote
it's
something
that
we
are
taking
that
has
been
published
so
and
I
think
the
next,
as
we
kind
of
finalize
this,
the
next
step,
I
think
would
bri
would
be
to
bring
this
to
the
board
at
the
is.
We
have
a
board
meeting
around
ossna.
A
D
D
D
We
can
also
reach
out
to
individuals,
saying
hey.
We
think
you
would
be
good
on
the
enforcement
team.
Would
you
be
interested
in
serving
then
we
have
the
list
of
candidates
we
hold
an
election
and
the
the
unique
part
about
the
election
is
the
we.
We
tally
up
the
votes
which
people
can
vote
for,
multiple
people,
but
we
make
sure
to
have
a
diverse
team
on
the
enforcement
team.
So
if
we
see
that
the
top
votes
all
go
to
black
women,
then
we're
gonna
say:
okay,
let's
add
some
diversity.
E
A
D
F
I,
like
the
idea
of
the
existing
code
of
conduct
team
running
the
election.
I
also
think
that
when
somebody
puts
their
name
up
for
that
or
sorry,
I
think
there
should
be
some
criteria
for
people
that
can
put
their
name
in
for
this.
You
know
certain
time
of
I
don't
know
service
with
the
community,
because
what
we
don't
want
are
people
that
are
brand
new
to
the
community
being
in
the
position
of
enforcing
the
code
of
conduct.
A
Yeah,
I
agree
with
that
off
the
top
of
my
head.
I
think
active
engagement
with
the
community
for
some
period
of
time
and
it's
the
period
of
time
that
I
mean,
because
we
we've
certainly
had
a
lot
of
people
that
have
become
very
active
in
the
last
year.
So
perhaps
the
year
is
sufficient,
but
as
we
as
we
mature
as
an
organization,
it
becomes
more
difficult
to
really
internalize
some
of
the
things
that
make
make
chaos
work
well
as
a
diverse
and
welcoming
community,
and
so
perhaps
that
period
should
be
longer.
B
A
B
Of
the
current
team,
I
mean
it
would
be
great
if
it
could
happen
over
the
summer
that
if
we
had
a
new
code
of
conduct-
and
we
had
a
new
code
of
conduct
enforcement
team,
that
would
be
great
and
georg,
I'm
also
happy
to
if,
if
you're
gonna
hold
an
election
kind
of
talk
to
you
about
like
what
the
implications
are
for
being
on
a
team.
B
B
F
B
B
To
me,
it's
I
think,
like
what
I
had
come
on
to
understand
is
like
where
we
can
go
if
issues
arise
and
when,
like
what
kind
of
support
we
have
as
an
enforcement
team
by
being
part
of
the
linux
foundation
and
also
not
being
well,
I
don't
remember.
I
don't
remember
what
our
what
our
categorization
is
at
the
linux
foundation,
but
we
don't
like
have
paid
members,
there's
no
pay
component
to
our
community,
and
so
these
things
kind
of
differentiate
us
of
just
a
tiny
bit.
A
A
Okay,
I'll
make
a
note
of
that,
and
then
the
the
next
item
on
the
agenda
is
chaos
software.
I
just
wanted
to
make
the
community
aware
that
daniel
scardo
and
I
have
been
talking
about
having
a
chaos-
software
hackathon
tutorial,
some
combination
of
events
on
the
friday
or
saturday
preceding
open
source
summit
europe
using
space
that
daniel
has
acquired
or
that
I
I
would
acquire
from
a
local
university
and
in
concert
with
some
of
the
inner
source
commons
work
that
daniel
is
doing.
A
B
Have
you
two
have
you
thought
about
like
what
the
workshops
would
where
they
would
start
so?
Is
it
like
new
to
aggregate?
Let's
get
this
thing
installed:
newton
or
morelab.
Let's
get
this
installed
or
you've
already
got
these
things
installed,
let's
think
about
building
a
metric
model.
You
know
like
where,
in
that
journey.
A
Our
principal
interest
is
in
building
the
chaos
software
community
and
making
that
starting
point
easier
for
both
of
the
specific
packages,
but
also
leveraging,
possibly
and-
and
this
is
sort
of
where
we're
experimenting
with
both
grimoire
lab
and
auger
from
each
each
of
the
perspectives
of
who
knows
what,
now
and
and
trying
to
think
about
making
contributions
to
chaos.
Software
initially
become
a
less
of
a
heavy
lift.
I
think
both
grimoire,
lab
and
auger
are
a
pretty
heavy
lift
to
get
going
and
understand
well
enough
to
begin
thinking
about
where
to
make
contributions.
A
A
lot
of
what
we
intend
and
hope
to
do
is
to
make
the
starting
point
for
where
what
you
can.
What's
the
minimal
thing
that
you
can
set
up
and
understand
to
make
a
productive
contribution
to
each
of
the
packages.
So,
let's,
let's
try
to
move
away,
I
think
from
having
to
understand
them
in
all
of
their
comprehensiveness.
A
B
Do
you
know
of
any
communities
that
have
complicated
software
like
kubernetes
or
the
colonel
and
like
what
their
paths
to
get
people
to
contribute?
Are
I
don't?
Has
anybody
ever
seen
this
published,
like
you,
wouldn't
just
like
jump
into
the
kernel
and
just
start
like
contributing?
Well,
you
could
you
could
try
no.
F
I
could
tell
you
what
we
do
for
kubernetes,
so
historically,
what
we
used
to
do
is
at
the
contributor
summits.
We
would
bring
people
in
and
do
new
contributor
workshops,
so
we
would
try
to
get
them
spun
up
from
from
zero
to
you
know
having
the
environment
that
they
need
to
contribute.
F
We
also
found
that
that
did
not
work
very
well,
because
the
environment
was
so
complex
and
we
would
run
into
issues
where
you'd
have
an
employee
who
couldn't
get
everything
installed
on
their
computer
in
time
and
they'd
be
trying
to
download
images
during
the
event-
and
you
know
the
wi-fi
would
crap
out
and
then
we'd
run
into
issues
where
people
couldn't
sign
the
cla
for
for
the
cncf,
because
you
know,
there's
like
corporate
corporate
cla,
all
sorts
of
hoops
a
lot
of
people
have
to
jump
through,
so
so
full
disclosure-
I'm
not
super
involved
in
kubernetes
anymore,
but
they're
in
the
process
of
moving
to
new
contributor
workshops
that
are
sort
of
online.
F
That
people
can.
The
people
can
take
where
they
don't
have
to
actually
be
in
person
somewhere
specific,
but
it
is.
It
is
very
much
designed
to
to
get
people
started
from
from
the
ground
up,
and
I
know
that
they
have
some
some
tooling
around
that
as
well.
Maybe
some
specific
containers
or
there's
there's
some
stuff
that
you
have
to
download
to
kind
of
get
the
environment
up
and
running,
but
you
can
look
the
kubernetes
I'll
I'll,
just
find
it
and
drop
a
link
somewhere
super.
F
B
F
Yeah,
so
that's
sig,
contributor
strategy,
sorry
nope
contributor
experience.
It's.
B
A
contributor
experience,
because
I'm
wondering
if
yeah,
that
would
be
a
good
group
to
take
a
look
at
what
they've
published
or
to
talk
to
because
they
would
like,
when
you
were
talking
about
a
workshop
of
just
getting
it
started
like
you're
like
that.
Doesn't
work
so
well.
Here's
why?
Why
and
why?
And
here
and
here's
the
thing
we
did
whatever
it
might
be,
and
it
worked
really
really
well.
We
were
able
to
retain
three
people
at
this
one
workshop
to
become
contributors
and
I'd
be
curious
as
to
what
those
those
paths
are.
F
A
A
A
All
right,
well
thanks,
sean
all
right
motion
to
adjourn
or
whatever.
Thank
you
very
much.
Thank
you.
Thank
you
very
much
for
participating
in
this
week's
chaos
meeting.
I
will
see
you
all
next
week
and
until
then
I
hope
the
weather
remains
beautiful
and
we
have
the
same
good
weather
next
week,
as
we
have
had
this
week
for
everyone.