►
From YouTube: CHAOSS Weekly Community Call June 13 2023
Description
Meeting summary for this meeting can be found here: https://chaoss.discourse.group/t/chaoss-weekly-community-summary-june-13-2023/174
A
Hey
everybody,
it's
June,
13th
and
you're
here
at
the
chaos
weekly
Community
call,
we've
just
been
discussing
cookies
and
pies,
and
now
I'm
like
really
excited
for
this
meeting.
To
be
done
so
I
can
go
Chow
Down
in
my
kitchen,
like
dig
some
cookies
out
somewhere
or
else
go
visit
Matt
because
apparently
he
has
cookies
all
the
time
in
his
house
with
fresh
baked
from
his
hands.
B
A
Gonna
share
my
screen.
If
you
have
not
told
us
what
your
favorite
dessert
is,
please
feel
free
to
do
that,
because
we
really
like
to
talk
about
this
stuff.
We've
just
spent
10
minutes
talking
about
it.
So
we'll
continue
if
we
have
time
at
the
end.
That's
fine!
A
First
off!
Let's
talk
about
this,
not
so
surprise
announcement.
If
you
have
seen
this
is
actually
a
really
exciting
date
for
chaos.
Today
we
have
good
things
on
the
agenda.
If.
C
A
Not
seen
our
blog
or
our
LinkedIn
post
or
the
post
and
slack
or
Twitter
or
Mastodon
guess
what
Don
Foster
Dr
Don
Foster
will
be.
Our
new
director
of
data
science,
which
is
huge
for
us
huge
for
us
Don,
is
an
amazing
piece
of
chaos.
Already
she
has
contributed
so
much
to
our
project,
both
in
terms
of
offering
her
insight
and
experience
she's
on
the
board.
She
leads.
A
The
Oscar
working
group
led
the
Common
working
group
forever,
she's,
just
a
fantastic
addition
to
our
community,
and
now
we
get
to
have
her
here
full
time
all
the
time,
so
I
am
selfishly
very
excited
to
be
able
to
work
with
Don
a
little
more
so
so,
yes,
it
is
starting
in
August
2023.
We
should
mention
Matt.
Do
you
want
to
talk
a
little
bit
about
like
what
that
means
for
chaos
in
terms
of
this
kind
of
new
Brave
New
World,
where
we're
going
into
data
science?
Sure.
D
So
I
think
for
a
long
time.
A
lot
of
you
know:
we've
been
developing
metrics
and
software,
but
we've
been
pretty
agnostic
as
to
how
we
speak
about
metrics
kind
of
publicly.
You
know
whether
it's
in
ospo's
or
university,
I,
suppose
or
scientific
software
communities,
we're
just
with
organizations
in
general
by
you
know
really
focusing
on
on
data
science.
I.
Think
we're
going
to
be
able
to
to
kind
of
ask
more
pointed
questions
from
the
chaos
project
and
be
able
to
answer
and
provide
Insight.
D
B
I
think
it
also
addresses
some
of
the
con.
Some
of
the
concerns
or
frustrations
that
ospo's
expressed
about
now
I
have
all
this
data.
What
do
I
do
with
it
so
having
a
data
science
role
kind
of
lets
us
formalize,
how
to
make
sense
of
it.
So
we
can
be
responsive
to
hospitals
that
want
things
and
then
we
can
help
them
have
them.
A
And
I
just
want
to
add,
too
that
this
is
not
just
for
corporate
I
suppose
but
Don's
going
to
help
us
those
in
any
context,
specifically
the
three
that
we
have
going
right
now,
which
is
scientific
software,
Community,
the
University
Hospitals
and,
of
course,
then
the
corporate
crossbows.
So
we
are
super
super
excited
to
have
Dawn
joining
us
full
time
in
August
to
talk
about.
A
You
know
all
of
these
things
and
to
really
work
with
these
groups
on
taking
our
metrics
to
the
next
level.
Really
it's
just
like
Matt
and
Sean
said
so.
E
I
guess
so
like
a
functional
question,
given
that
this
is
a
new
role
for
the
project,
I'm
just
curious.
How
much
I
guess
that's
really
a
question
for
Dawn,
but
I
mean
we're
thinking
about
enforces
here
like
how
much
her
sort
of
road
map
and
agenda
is
going
to
be
available
to
the
community.
In
terms
of
like,
if
there's
like
a
just
assuming
the
case,
where
there's
probably
going
to
be
a
lot
of
demand
for
something
like
this
and
I'm
just
kind
of
curious.
E
How
she's
going
to
sift
through
and
prioritize
things
and
I'm,
assuming
she'll
determine
how
best
to
do
that.
But
it
might
be
awesome
to
see
like
kind
of
her
project
plan
and
what
she
plans
to
do,
or
what
the
questions
she's
taking
on
in
support
of
which
types
of
cases,
types
of
organizations
and
I
I.
Don't
know
how
transparent
she's
planning
to
be
with
that
sort
of
thing
with
the
community.
D
So
to
the
in
terms
of
transparency,
I
think
at
least
my
Approach
would
be
to
kind
of
err
on
the
side
of
being
more
transparent
because
I
this
is
meant.
This
is
a
community
role.
So
this
is
a
chaos
Community
role.
D
This
is
intended
to
support
work
with
auger,
intended
to
support
work
with
grimoir
lab
intended
to
support
work
across
those
the
different
working.
You
know
the
context
working
groups
we
have
now,
but
how
so
so,
to
maybe
part
of
your
answer
but
to
how
to
prioritize
and
sift
through
that
I,
don't
I,
don't
have
a
good
answer
for
that
and
I
think
Don
could
speak
better
to
that.
E
E
D
A
look
at
this
would
you?
What
does
this
mean?
So
no
I
I
think
that's
important
this.
You
know,
as
we
were,
writing
this
up
this.
This
is
available
through
support
from
the
Sloan
Foundation
and,
as
we
were,
you
know
kind
of
writing
this
up.
This
is
not
intended
to
be
a
Consulting
role.
You
know
where
we,
the
chaos,
provide
cash
project,
provides
Consulting
Services,
but
really
meant
to
be
a
community
support
role,
so
I
would
suspect.
D
Most
of
the
questions
that
are
being
talked
about
are
the
ones
that
are
being
talked
about
in
the
working
groups
or
they're
being
talked
about
here
in
these
meetings
you
know
what
I
mean
or
on
the
slack
channels,
foreign.
A
F
F
A
D
Mean
it
would
make
a
lot
of
sense
right,
I
mean
because
I
think
there
are
a
lot
of
organizations,
whether
they're,
for-profit
or
not-for-profit,
or
you
know,
funding
foundations
or
whomever
it
might
be
that
relies
on
open
source
is
part
of
whatever
the
work
it
is
that
they
do
I.
Think
a
lot
of
people.
Try
it
to
your
point.
Sophia.
A
lot
of
people
have
questions
that
data
science
can
help
answer.
D
E
Yeah
and
just
for
I
think
many
of
you
are
on
that
call,
but
in
the
hospital
working
group
I
think
early
on
someone
asked
the
question
of
how
many
Osos
have
data
scientists
and
all
of
us
kind
of
had
partials
in
a
way
that
I
think
in
support
of
ospo.
It
can
be
it
like,
I,
I,
just
I.
Imagine
there's
going
to
be
a
lot
of
interest
to
work
with
on,
and
so
it's
more
just
a
appropriately
know
how
to
engage
without
just
again
throwing
it
at
her.
C
Wouldn't
the
in
the
metrics
models
working
group
be
the
kind
of
the
natural
place
for
her
to
land?
Isn't
that
the
work
that
they're
doing.
B
There's
compass
and
there's
eight,
not
and
so
I
think
possibly
one
thing
that
Don
may
do
is
because
she's
done
so
much
development
for
VMware
use
the
different
data
collection
tools
we
have
to
generate
candidate
like
Jupiter
notebooks
and
then
provide
use
that
as
kind
of
a
pathway
to
enabling
those
those
metric
models
or
or
insights.
That
I
suppose
want
to
be
incorporated
into
the
tools
using
the
code
that
she
generates
and
perhaps
to
build
a
community
of
people
who
do
something
like
that.
But
I
don't
want
to
speak
for
Don,
I.
B
D
I
do
I
will
say
Kevin
I
like
that
that
idea,
because
it's
just
something
to
talk
about
and
yes
to
your
point,
Sean
like
it
can
evolve,
but
as
the
different
context,
working
groups,
you
know,
we've
set
those
up,
so
folks
can
kind
of
speak
freely
about
what
they
would
like
to
see
and
what
they
would
like
to
do
with
respect
to
metrics
in
their
organization
without
worrying
about
you
know
some
of
the
underlying
details
that
are
involved
in
the
chaos
project
and
the
metrics
model
working
group
really
has
been
a
place
where
we
talk
about
bringing
those
you
know
those
ideas
forward
and
thinking
about
how
they're
connected
with
software
and
how
we
talk
through
the
models,
so
I
think
that's
where
you're
going
with
that
Kevin
and
I,
like
it.
D
C
A
And
I
also
think
too
that
maybe
her
role
will
be
more
about
not
necessarily
the
what
but
the
the.
Why
and
the
what
does
it
mean
two
which
metrics
models
doesn't
I
mean
they
touch
on,
but
as
far
as
like
interpreting
the
data
and
like
Trends
and
things
like
that,
it
doesn't
really
go
that
far.
It
kind
of
stops
after
defining
the
model.
So-
and
maybe
you
know
she
might
be
the
bridge
to
like
to
kind
of
pull
everything
together
in
one
place.
Yep.
D
A
Yeah
100
percent,
so
yeah
Don.
When
you
watch
this
recording,
if
you
watch
it,
we're
all
super
excited
for
you.
You're
gonna
solve
all
the
problems
and.
A
So
yay
is
that
do
we
Matt?
Do
you
know
if
it's.
B
It's
perfect
from
from
talking
to
Don
I,
think
I
think
we're
starting
the
paperwork
because
it's
the
cash
is
flowing
through
my
University
and
she's
gonna
start
sometime,
I
think
in
late
August.
You
know
she
may
not
like
have
a.
She
may
have
like
a
ramp
up,
but
she's
gonna
take
some
time
off.
I.
Think
she's,
with
VMware
through
sometime
in
July
and
she's
gonna.
Take
some
time
off
for
some
time
with
low.
B
A
We
decide
to
set
that
up
for
Community
participation.
Any
other
final
comments
about
data
science
and
chaos
and
Dawn.
G
I
I
see
more
I,
see
more
student
interns,
Google
server
of
code
coming
after
data
science.
Now.
A
A
If
we
didn't
have
enough
applicants
before
this
is
like
a
whole
other
whole
other
world,
okay,
yeah.
So
let's
go
ahead
and
move
on.
F
A
Want
to
remind
everybody
yet
again,
our
very
first
chaos
Con
in
Africa
is
happening
tomorrow.
So
hooray,
hooray.
The
organizing
committee
has
done
an
absolutely
outstanding
job
in
organizing
this
I
mean
it's
a
full
day
of
a
lot
of
stuff
going
on.
A
I
am
so
excited
for
it
there's
you
know
been
Design
Elements,
there's
been
all
kinds
of
scheduling
and
Outreach,
and
you
know
going
through
the
the
abstracts
and
choosing
which
I
mean
just
logistically
has
been
really
challenging
and
so
I'm,
just
so
proud
of
every
single
person
on
this
list
and
all
the
work
that
they've
done.
So
just
a
huge
shout
out
to
this
whole
team
here.
A
Does
anybody?
Is
there
anybody
on
the
call
that
knows
maybe.
F
A
Do
you
have
any
idea
of
like
what
we're
at
as
far
as
registrations
go
I'm,
just
curious?
If
you
don't
know,
that's
totally
fine.
F
F
A
F
F
Oh
okay,
I
think
we
have
about
over
100.
We
have
500
people
I.
A
A
A
So
you
know
just
again.
Logistically
it's
been
a
challenge
to
get
everybody
there.
So
super
super
excited
if.
A
If
you're
attending
virtually
you
can
just
go
to
our
chaos
tube
here
on
YouTube
and
then
there'll
be
a
live
stream
here.
So
I
don't
think.
I
have
a
specific
link
yet,
but
I'll
be
happy
to
post
that
in
slack,
if
they,
if
there
is
a
direct
link,
I
assume
that
won't
be
happening
until
the
live
stream
starts
and
then
we'll
have
the
link.
That's.
A
Any
questions
about
gascon,
Africa
Sean
is
also
giving
a
talk,
is
also
giving
a
talk.
He
is
so
is
Enoch
and
several
others
yeah.
B
Yeah,
a
slight
demo
but
I'm
gonna
focus
on
something
that's
more
engaging
than
watching
a
software
demo
cool.
It's
gonna,
be
a
full
video
production.
A
B
B
A
Okay,
the
next
one
is
just
a
quick
announcement,
I
guess,
because
I
don't
think
I've
announced
this
yet
there's
a
next
Badger
orientation.
If
you're
interested
in
becoming
a
Dei
event
badger
you
can
reach
out
to
me,
I
can
send
you
a
calendar,
invite
or
you
can
just
show
up
on
the
chaos
Channel
at
June
27th
at
two
o'clock
right
after
this
meeting.
It'll
happen
in
a
couple
weeks
right
after
this
meeting
that
year
ago,
so.
A
Good
and
then
I
like
pulled
out
my
actual
calculator
and
I'm
like
no.
That
is
not
correct
and
I
did
tag
port
Enoch
in
it,
but
I
know
Enoch
is
on
his
way
to
Africa
and
he's
giving
a
talk
there.
So.
A
Don't
think
you're,
tired,
I
think
it'll
do
it
if
it,
if
I,
do
it
automatically
it'll
just
give
that.
A
That
when
we
can,
but
anybody
have
questions
about
this-
we're
not
sure
what
that
is
a
little
more
context
around
that.
F
A
And
I
put
this
on
here.
What
else
would
we
like
to
talk
about
so
I'm
guessing?
This
was
either
a
matter
of
shot
that
put
that
on
there.
B
Yeah
I,
just
I,
have
a
few
quick
updates.
Enoch
and
the
team
and
I
went
through
a
couple
weeks
ago,
just
the
full
design
for
the
site,
and
it's
looking
really
good.
B
Pretty
really
good
progress
on
that
and
Enoch
and
I
have
been
working
pretty
closely
on
the
Automation
and
the
very
technical
low-level
detail.
We
had
originally
decided
to
have
chaos,
Africa
pull
just
basically
post
applications
and
agar
would
pull
them,
but
we
think
it
would
be
better
if
auger
had
an
API
that
they
could
just
call
every
time
someone
applied.
So
we
went
about
designing
that
in
its
entirety
last
night
and
one
of
the
auger
developers
is
building
that
today
and
tomorrow.
B
So
we'll
have
that
ready
to
test
for
the
next
or
to
demonstrate
for
the
next
meeting.
There's
also
some
report
design
work
that
I
owe
the
team
and
some
work.
This
is
basically
Enoch
and
I
worked
out
the
workflow
work.
That
was
our
task
after
the
last
main
meeting
for
that
group
and
and
I
have
to
work
out
the
the
I
have
the
report.
B
Design
I
have
to
put
into
a
document,
and
I
haven't,
haven't
done
that
yet
because
I
was
busy
working
out
the
details
of
the
flow
and
also
had
I,
don't
remember
what
happened
last
week,
but
I
think
I
was
still
really
heavily
in
Japan
time.
Oh
I
had
an
internet
outage
at
a
very
bad
time
again,
so
I
was
up
all
night
one
night,
so
yeah
not
that
everybody
really
cares
about
my
internet,
but
that's
that
yeah.
A
A
Feel
that
loud
for
those
who
aren't
sure
about
what
we're
talking
about
this
is
what
we're
talking
about,
and
it
was
on
the
GitHub
blog.
This
is
the
project
badging
kind
of
like
the
the
big
sibling
to
event
badging,
and
we
are
working
with
the
all-in
project
and
GitHub
on
this.
So,
if
you're
interested
in
like
kind
of
learning
about
what
it
is,
if
you
don't
know-
and
you
want
to
see
a
quick
summary
of
it-
this
is
it's
all
right
here
in
that
blog
post,
I.
B
Think
the
most
significant
difference,
if
you're
familiar
with
event
badging,
is
that
we
really
need
we
determined
that
it
for
this
to
be
tractable
and
sustainable.
We
would
have
to
automate
a
significant
part
of
it,
and
so
the
design
is
is
really
focused
on
how
to
get
a
valid
assessment
of
a
Project's
Dei
status
and
badge
level,
but
to
also
do
as
much
with
automation
as
we
can,
because
we
think
and
I
think
that's
is
right.
The
scale
of
project
badging
is
exponentially
larger
than
the
scale
of
event.
Badging.
A
Yeah
and
other
key
differences,
you
know
event
one
and
done
and
then
the
next
event
they
can
just
fill
out.
Another
application.
G
A
You
know
ongoing,
so
it's
you
know
we
have
to
have
some
kind
of
expiration
date
and
no
requests
to
reapply
and
then
also
it's
kind
of
it's
a
little
bit
harder
to
define
a
project
like.
Is
it
a
repo?
Is
it
an
org
like
what
is
it?
So
there
are
a
lot
of
differences
between
projects
and
events.
A
A
A
A
So
we're
super
excited
that
it's
actually
moving
forward
and
we
have
had
quite
a
few
responses
to
that
blog
post
once
GitHub
posted
that,
because
we
do,
we
are
asking
for
folks
who
want
to
and
include
their
projects
on
as
part
of
the
pilot,
so
there's
a
place
where
they
can
participate
or
we're
also
asking
folks
opening
it
up.
You
know
whoever
wants
to
help
us
develop
these
metrics
and
figure
out.
What's
going
to
be
in
each
level,
so
you
may
see
some
new
faces
in
our
Dei
working
group
as
well.
C
Have
we
have
we
looked
at
running
chaos
through
this
project
badging
process,
yet.
F
C
Yeah
and
maybe
to
maybe
to
make
sure
we're
we're
on
board
with
it
as
well.
So.
A
Whatever
this
dei.md
file
will
have
four
metrics
how
the
project
attends
to
four
different
metrics
and
the
template
that
we
gave
them
was
based
on
chaos
and
kind
of
how
we
do
things
so
we'll
have
to
figure
out
how
our
Dei
dot
MP5,
like
it,
might
get
flagged
as
like
a
as
a
bogus
one,
because
the
like
rdei.md
file
will
be
very
close
to
the
template,
because
we
use
dust
as
a
template.
If
that
makes
sense,
so
we'll
have
to
figure
that
out.
A
I
guess
if
we
run
it
through
the
Automation
and
it
does
not
go
through.
That
would
probably
be
why
I
would
imagine,
but
we
can
certainly
work
that
out.
A
A
D
D
I'm,
just
like
when
I,
when
I,
when
we
are
asking
whether
this
is
at
an
org
level
or
a
repo
level,
and
then
I
start
thinking
about
a
project
like
we
have
three
different
things
here
and
if
we
ask
for
the
Dei
dot
MD
file
to
be
put
in,
say
a
community
repo
to
me.
That
implies
it's
for
the
entire
org
or
if
we
ask
them
to
put
it
in
a
GitHub
folder
at
that
top
level,
that's
for
the
entire
org.
D
G
D
B
B
It
creates
three
different
places
where
the
chaos
Africa
team
may
have
to
scan
for
that
dei.md
file.
B
So
if
it's
in
a
community
repo,
that
would
be
one
place
if
it's
in
a
if
it's
at
the
org
level,
like
a
shared
file
across
the
repos,
that's
another
place,
and
then,
if
it's
in
each
repo,
that's
a
third
place,
so
I
I
think
we
decided
to
pile
it
at
the
repo
level,
but
but
moving
on
to
the
org
level
wouldn't
be
a
problem,
and
if
we
want
to
just
say
the
oral
or
level
and
specify
where
that
files
go
file
goes
I
think
we
can
still
make
that
design
change
at
this
time.