►
From YouTube: 20210429 SIG Arch Code Org
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Cloud:
okay,
hi
everybody
today
is
thursday
april
29th.
This
is
the
meeting
for
the
code
organizations
of
project.
We
have
a
light
agenda.
We
will
start
with
arch
talking
about
debstat,
go
ahead,
ash.
B
Yep,
so
the
0.5.3
release
is
has
is
the
latest
release.
It
has
like
everything
the
previous
one
had
and
the
additional
feature
where
you
can
create
a
graph
which
is
revolving
around
a
particular
dependency.
So
basically,
it'll
show
all
the
chains
which
have
the
dependency
I
was
talking
to
pushkar
and
he
said
that
he
might
find
it
useful
because
he
scans
for
vulnerable
dependencies.
So
I
think
that
maybe
that's
useful
for
him,
but
other
than
that.
What
else
happened?
B
Oh
yeah,
we,
I
ran
the
deb
start
against
all
the
projects
inside
the
kubernetes
organization,
and
I
think
I
don't
remember
correctly,
but
it
ran
for
35ish
of
them
and
for
15
of
them
it
timed
out
timed
out
being
it
taking
more
than
three
minutes
and
in
case
you're
wondering
why
three
minutes
it's,
because
it
takes
it
about
1.40
seconds
for
kubernetes,
so
any
more
than
that,
it's
not
gonna
produce
a
result,
and
the
final
thing
is
about
adding
these
scripts
to
the
kkk
repository
which
I'm
like.
B
A
A
The
other
way
to
do
this
is
read
thoroughly
exactly
what
they're
saying
and
then
form
a
logical
proposal
which
is
different
from
what
is
there
in
the
pr
run
it
by
them.
You
can
use
the
sick
testing
mailing
list
to
continue
the
conversation
because
ben
responded
there
yeah,
so
you
can.
When
you
respond
to
ben
there,
you
can
add
christoph's
email,
so
they
are
on
the
same
thread.
A
So
try
to
do
whatever
you
can
asynchronously
before
the
next
sick
testing
meeting,
and
then
we
can
take
a
checkpoint
at
that
point.
Worst
case
scenario
christoph
did
leave,
notes
on
how
to
disable
the
verify
script
and
you
know-
and
basically
you
need
to
disable
the
verify
script
and
you
have
to
like.
A
Take
the
json
file
out
and
clean
up
the
vr.
That
way.
A
Will
be
we'll
do
things
by
hand
when
or
what
we
could
do
is
we
could
add
a
new
pr
job,
a
new
ci
free
permit
job,
which
is
executed
on
demand,
which
will
run
the
verify
script.
Do
you
see
what
I'm
saying
like
when
one
of
us
one
of
the
dependency
approvers
sees
this?
Then
we
will
trigger
a
job
to
see
what
the
difference
is
or
whatever,
like
whatever
is
the
new
information
that
comes
out
of
the
verify
job?
A
Okay-
and
that
might
be,
that
might
also
be
you
know
we
might
have
to
do
something
different,
which
is
trying
to
figure
out
like
what
is
well.
We
might
have
to
figure
out
how
to
get
the
previous
exactly
json
and
the
new
json
and
do
a
difference.
This.
B
A
There
is
a
way
to
do
it.
There
is
a
way
to.
There
is
a
way
in
github
when
a
github
action
is
triggered
to
figure
out.
The
previous
thing
we
might
have
to.
We
might
have
to
dig
a
little
bit
deeper
to
see
if
there
is
a
way
to
like
differentiate,
which
is
the
merge
pr
for
the
current
we
are
being
proposed,
and
where
is
the
master
before
that,
and
we
might
have
to
do
some
gymnastics
there.
A
Again,
we
leave
that
as
a
discussion
for
future
and
don't
pollute
that
with
like
what
needs
to
be
done
in
this
pr
so
see
if
you
can
come
to
an
agreement
with
kristoff
and
ben
on
this
pr
itself
on
that
testing
thread
and
we'll
see
where
we
land
up
with
that.
A
C
Nope,
I
was
also
looking
at
that
memory
thing
where
you
were
depending
I
planned
on
doing
some
deep
rock
stuff,
but
I
guess
it
is
not
very
on
fire
ratio
right
now,
since
it
is
working
for
kkk.
So
when
we
reach
on
like
running
it
on
other
reports,.
A
I
I
think
it
would
make
sense
to
dig
into
the
performance
thing
too,
like
try
to
figure
out
how
to
optimize
the
performance
stuff.
Like
one
example,
I
can
think
of
separating.
A
A
How
do
you
figure
out
where
you
know
where
things
take
time,
and
this
is
actually
a
really
good
opportunity
to
like
dig
into
why
it's
taking
too
much
time,
so
you
can
think
of
it
in
terms
of
algorithms,
you
can
think
of
in
terms
of
flame
graphs
and
then
see
if
you
can
come
up
with
something
innovative.
Maybe
you
can
use
instead
of
storing
everything
in
hash
maps.
A
Maybe
you
can
some
way
of
doing
what
do
you
call
that,
if
you
need
to
know
like
whether
you've
visited
the
same
thing
before,
instead
of
keeping
a
list
of
all
the
things,
then
just
figure
out
if
there
is
a
way
to
keep
it?
If
it's
memory
right
like
see
how
you
can
reduce
the
memory
consumption
by
storing
less
things
or
collapsing
things.
A
A
Md5
is
a
way
of
like
encoding
like
coming
up
with
a
shorter.
If
you
just
want
to
compare.
A
About
the
value
itself,
you
just
want
to
know
whether
the
same
thing
was
seen
before
right,
like
so
figure
out,
so
you
have
a
month
left
right.
So
if
there
is
no
other
things
coming
up,
then
I
would
dive
into
go.
How
go
works?
How
you
know
cpu
and
memory-
affects
the
algorithms
and
like
go
deep
into
it.
A
Got
it
right,
it's
going
to
be
useful
in
some
shape
or
form
when
you're
attacking
like
real
world
problems.
This
is
a
real
world
problem
anyway,
right
yeah.
A
Cool
okay,
did
you
have
anything
today?
No
as
the
shops.
A
Yes,
okay,
then
the
question
is
like:
is
there
anything
else
you
want
to
do
harsh.
B
Mean
I
have
been
like,
I'm
start
I'm
starting
to
go
to
release
engineering
meetings,
because
this
time
my
shadow
application
didn't
get
accepted,
but
that's
expected
since
I
like
never
showed
up
before
that,
but
so
yeah,
I'm
applying
for
the
next
cycle.
So
I'm
looking,
if
like
I
can,
help
out
there,
okay,
but
other
than
that.
If
you
have
something
I
could
work
on.
That
will
also
be
great.
A
Like
you
have
seen
things
right,
so
you
have
to
tell
me
what
you're
interested
in
then
I'll
guide
you,
I'm
not
gonna,
assign
you
something
if
you're
not
gonna,
be.