►
From YouTube: CHAOSS Evolution Working Group 1/25/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
So
I
think
how
do
people
feel
about
pausing
the
recording
and
taking
some
time
to
review
this,
or
should
we
just
keep
recording
and
let
people
watch
the
excitement.
A
I'm
gonna,
I
think
we've
discussed
a
lot
of
good
stuff,
so
I'm
restarting
the
recording.
So
in
short,
during
this
down
period,
we
narrowed
the
scope
of
change
request,
commit
to
focus
only
on
change,
request,
commits
and
not
the
complexity
or
lines
of
code.
Necessarily,
although
we
think
that
the
number
of
commits
is
a
signal
of
potentially
increasing
complexity.
A
What
we
need
is
that
that
is,
we
do
have
change
request
commits
implemented
in
auger.
I
don't
know
if
it's
available
through
the
api
right
now.
B
Code
change
code
review,
oh
review,
yeah
review
review,
commits
code
review,
commits.
A
Oh
yeah,
there's
just
a
heading
for
implementing.
Oh,
I
guess
implementation
is
a
super
heading
for
these
other
things
never
mind.
B
Yeah,
so
what
I've?
What
I've
noticed
is
that
underneath
implementation
oftentimes,
the
first
thing
that
shows
up
is
aggregators.
However,
it
seems,
like
we've
been
doing
it
without
the
heading
aggregators.
So
it'd
be
like
a
paragraph
that
would
kind
of
talk
about
aggregators
and
then
filters
as
its
own
thing
is
that
does
that
make
sense,
yeah.
A
Let
me
see
if
I
can
find
this
is
all
of
auger's
history
sean.
Can
we
have
a
source
of
this
image?
It's
actually
the
api
endpoint
that's
listed
below.
Okay,.
A
But
I
think
I
I
think
I
can
provide
a
parameter
that
will
narrow
the
scope.
B
A
A
Sorry,
our
our
schools
are
off
the
last
five
days
and
so
the
children
are
at
home,
I'll,
come
home
you're
off
it's
basically
a
covid
response.
B
B
A
Are
we
nine
o'clock
I
have
hiding
now
so
I'm
doing
worse
at
yeah
we're
at
the
end.
I
think
we
made
some
good
progress
here,
I'll
I'll
call
that
a
win
yep.
Thank
you
for
participating,
yep
and
I'll.
See
you
all
in
10
minutes.
All
right
sounds
good.
Bye.