►
From YouTube: 2022-05-24 Package weekly team meeting
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
Then
hello,
everyone
welcome
to
our
package
weekly
team
meeting
today
is
may
24th
and
just
to
share
some
announcements
and
study
updates.
We
have
the
issue
there,
so
you
can
have
some
time
to
go
and
review.
Anyone
have
something
else
that
wants
to
share
us
an
announcement
or
something
that
we
should
be
aware
of.
A
Okay,
so
then
we
can
move
to
our
team
discussion
in
our
new
format.
We
are
on
week
two
that
means
that
we
are
going
to
talk
about
performance
and
reliability.
Updates.
Katie
has
the
first
item
that
is
she's,
proposing
a
change
on
the
package
series
to
move
it
to
a
two-column
layout.
A
She
attached
the
design
proposals
to
the
issue
and
expecting
for
some
feedback
on
that.
A
side
note
in
here
this
was
not
added
to
our
milestone
plan
to
have
a
refinement
on
this
one,
but
considering
the
type
of
work.
Maybe
we
want
to
work
on
this
on
15
too,
so
it
would
be
interesting
to
have
your
feedback
in
there.
There
are
questions
about
like.
Is
this
going
to
need
some
backing
work
that
I
think
is
not,
but
it
would
be
good
to
have
some
engineers
taking
a
look
at
it.
A
Rahul
is,
I
think,
it's
already
looking
at
it
on
the
ux
on
the
front
perspective,
yeah
any
comments
on
that.
One.
A
Okay,
so
our
next
topic
is
I
I
was
just
adding
a
note
in
here,
so
thinking
on
all
these
word
that
we
have
in
our
limited
capacity
and
all
the
things
that
are
going
around,
I
think
we
can
levitate
some
of
the
community
contributors
and
their
work
and
their
amazing
work
they're
doing
with
us.
So
the
change
about
how
we
are
using
the
labels
about
accepting
merge,
requests
versus
seeking
community
contributions.
It's
a
very
interesting
change.
That
happened,
I
think,
like
two
three
months
ago.
A
A
Probably
when
we
refine
issues,
we
already
have
like
a
path
on
how
to
implement
the
solution,
so
we
can
just
add
it
in
the
description
and
then
the
bot
is
not
going
to
complain
that
we
don't
have
an
implementation
guide
and
we
can
use
those
labels
and
normally
those
labels
are
used
for
the
hackathon
also.
So
that
can
be
a
good
idea
just
sharing
with
all
of
you.
That
can
be
a
good
idea
on
how
we
can
get
some
of
the
reliability
issues
that
we
have.
A
And
next
one
is
now
to
review
all
our
reliability
and
performance
and
stuff,
like
that,
I
added
to
an
agenda
just
the
red
ones,
like
the
areas
that
we
need
to
focus
on.
I
would
like
to
share
with
you,
so
corrective
actions
is
list
on
our
prioritization
framework.
As
for
spiralization,
that
means
that
in
theory
we
should
prioritize
that,
on
top
of
anything
else
with
other
categories,
we
have
some
corrective
answers
from
some
time
ago.
Before
saying
that
we
want
to
fix
them.
I
would
like
your
help
to
confirm.
A
We
already
closed
some,
but
there
are
those
remaining
so
the
first
one.
Let
me
open
it
because
I
don't
remember
improving
monitoring
for
the
dependency
proxy.
I
think
it's
a
fairly
easy
change,
because
I
saw
that
it
was
about
the
dashboards
and
it
was
about
like
there
are
people
in
this
team
that
is
very
good
at
dashboards,
and
there
are
people
that
wants
to
learn.
So
it
can
be
a
very
good
opportunity
for
fading
and
solving
something
very
quickly
important
thing
here,
I'm
not
asking
to
schedule
this.
A
A
The
other
one,
it
was
a
word
that
a
community
contributor
has
started
and
then,
where
no
more
activity
there.
So
my
question
is:
can
we
pick
it
from
there
and
how
much
work
is
going
to
be
if
we
pick
it
from
there,
because
if
I
get
like
a
refinement
in
that,
probably
we
can
schedule
it
in
future
milestones
and
start
dropping
corrective
actions
to
see
that.
A
B
Sorry
thought
you
were
finished
michelle.
I
was
thinking
of
leaving
a
note
here
because
we
did
some
improvements
on
object,
storage,
testing
in
the
meantime,
so
we
can
just
leave
some
of
some
of
these
tests.
You
know
running
automatically
with
different
configurations
and
then
help
at
least
generate
enough
logs
for
investigating.
I
don't
know
if
that's
useful
enough,
but
I
I
can
leave
a
note
that
we
can
do
that
here
in
the
issue.
A
Regression
regression
issues,
we
have
two
issues,
but
one
is
the
corner
one
I
think
now.
I
need
to
remember
what
it
was
that
about.
A
Oh
yeah,
there
was
a
discussion
if
this
was
really
a
regression
or
not,
and
then
you
added
some
comments
steve
on
that
one,
and
I
know
that
remember
right
now
about
this
is
going
to
be
hard.
So
the
question
is
just
like
take
some
time,
so
we
can
do
some
refinement
and
and
plan
about
how
much
work
this
can
take.
So
later
we
can
prioritize
that.
C
Yeah
I'll
take
a
look.
I
remember
finding
like
what
was
actually
going
on
here,
but
I
don't
recall
like
if
it
was
ready
to
be
rated
or
anything.
A
Yeah
yeah
and
the
same
for
the
future
flags.
Thanks
to
david,
I
was
able
to
bring
the
huge
list
of
future
flags
to
only
two
more
than
we
want
to
remove
both
are
for
conan.
If
I
remember
well,
so
I
think
so,
it's
just
like
again
like
some
refinement
that
is
going
to
help
us
to
to
prioritize
things.
So
we
have
a
lot
of
things
that
we
want
to
fix.
We
don't
have
capacity,
so
we
need
to
prioritize
between
all
of
this
understanding
how
much
work
is
going
to
be,
can
help.
A
No,
the
conan
is
a
quarantine
test
and
for
the
current
interest,
my
idea
was
like
what
I
was
mentioning
about.
Adding
an
implementation
guide
rally
can
help
to
get
those
ones
like
feature.
Flags
are
removable,
sometimes
are
easy
and
quarantine,
that's
kind
of
not
so
easy,
but
if
we
have
some
refinement
in
there.
C
And
these
those
two
quarantine
tests
for
conan.
I
know
I
spent
a
lot
of
time
trying
to
figure
them
out.
So
it's
probably
we
just
need
to
schedule
like
a
fair
amount
of
time
to
look
at
those
when
it's
time,
because
I
think
we've
had
those
scheduled
in
the
past
and
I've
spent
many
hours
trying
to
reproduce
and
then
I
did
reproduce,
but
then
it
like
stopped
reproducing
after
a
couple
milestones.
So
it's
kind
of
it's
kind
of
been
a
mess
with
those
two.
B
A
Okay,
good
so
yeah,
these
are
the
the
most
important
things
that
we
were
having
on
our
reliability
and
performance.
I
want
to
just
let
you
know.
Thank
you
very
much,
we're
very
good
with
the
most
important
ones
that
are
infrared
and
security
issues,
so
that
is.
That
is
a
good
thing.
We
know
that
there
was
a
lot
of
okay
there's
multiple
teams
to
work
on
them.
We
are
good
there.
A
Okay,
so
if
we
don't
have
any
females,
then
I
think
that's
all
for
all
for
today.
Thank
you.