►
From YouTube: 2022-09-13 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
Hello,
welcome
to
our
package.
Weekly
sync
today
is
september
13
and
we
are
going
to
go
over
our
announcements,
team
discussion
and
whatever
is
going
on
around
the
team.
So,
let's
start
with
some
announcements
and
strategy
updates.
So
I'm
going
to
be
out
the
rest
of
the
week,
I'm
working
on
a
coverage
issue
just
to
make
sure
that
some
things
are
completed.
A
Wait!
No,
I'm
talking
about
something
completely
different,
that
is
on
the
agenda,
but
also
so
I'm
out
the
rest
of
the
week,
and
the
only
thing
that
I'm
is
going
to
be
painting
is
the
planning
issue
that
I
would
like
to
make
sure
that
we
completed
by
the
end
of
the
week.
So
I'm
going
to
going
to
be
asking
for
your
support.
A
The
other
announcement
is
also
about
end
of
year
so
time
off,
but
this
time
about
end
of
year,
inviting
everyone
to
start
putting
your
time
on
pto
by
roots.
So
we
can
plan
very
very
carefully
because
I'm
expecting
there
were
going
to
be
some
weeks
that
everybody's
going
to
be
out,
which
is
perfectly
okay.
I'm
not
worried
about
that.
I'm
just
going
to
make
sure
that
we
do
kind
of
like
a
team
coverage
issue
instead
of
like
individual
cobras
issues.
So
everybody
is
very
aware
that
everybody's
out
there
are
not
reviews.
A
Next,
one
tim
is
back
next
week,
so
I
put
it
a
link
there
in
case
you
have
things
that
you
consider
important
for
him
to
to
take
a
look
on
the
higher
priority
we
mentioned
on
our
tips
and
tricks
for
pto
that
that
helps
a
lot.
So,
let's
help
tim.
Apparently
it
was
very
long
so
just
to
make
sure
that
he
have
key
things
to
take
a
look.
A
Next
one:
oh
yeah,
we
have
a
new
engineer
starting
suleimi.
Our
newest
go
engineer
is
starting
on
the
27th,
because,
obviously
familiar
friendly
the
day
before
so
question
is
here.
I
need
someone
interest
and
be
on
boarding
body,
ideally
that
will
fall
between
hai
mei,
joao
or
haley,
but
it's
open
to
anyone
on
the
team
because
onboard
the
body
is
not
about
the
area
that
they
have
to
work.
B
Yeah,
just
I
don't
know
if
I
had
a
chance
to
tell
this
to
the
team,
but
I
I
am
now
unofficially
supporting
configure
and
release
teams
as
a
software
engineering
test,
so
my
milestone
planning
is
like
spanning
across
these
three
teams.
I
just
wanted
to
make
it
transparent,
so
I
posted
the
issue
here
if
you're
curious,
but
either
way
I'll
be,
you
know,
anyways
addressing
individually
in
the
milestone
issues
of
each
team
as
well.
So
that's
pretty
much.
It.
A
B
I
I
just
added
a
comment
here
to
be
transparent
about
the
automation
of
the
mr
version
bump.
Basically,
this
is
now
up
for
review,
but
there
was
a
bit
of
a
delay
with
the
with
some
token
just
to
enable
the
smrt
merge
as
well
I'm
going
to
be
out
from
tomorrow.
So
I
probably
this
probably
won't
get
won't
get
to
be
merged
on
15.4.
B
I
don't
know
if
it's
an
idea
to
add
this
issue
in
the
15.5,
and
also
I
was
talking
with
steve
about
rpm
testing
might
be
that
the
end-to-end
test
doesn't
get
to
be
on
15.5
it.
It
is
highly
dependent
on
how
the
review
and
yeah
the
work
of
of
the
of
the
rpm
epic
goes.
So
I
probably
will
mark
the
rpm
test
as
a
stretch
depending
on
how
is
it
going
it?
It
was,
I
think,
label
as
delivery,
but
I
will
I'll
correct
that
michelle.
A
C
A
Okay,
maybe
I'm
going
to
skip
this
one
so.
A
D
Yeah
just
a
note
here
that
vito
became
a
manager
for
appsec,
so
we
no
longer
have
a
stable
counterpart
for
security,
and
so,
while
they
find
someone
for
us,
we
need
to
bring
upselk
in
general
for
all
security
needs.
A
I
would
like
to
hear
if
you
have
any
concerns
on
this
one
I
think,
like
I
knew
about
this
and
on
some
issues
that
you
were
thinking
bitter.
I
went
and
being
upset,
and
I
saw
like
good
great
like
good
time
on
responses
like
not
nothing
taking
like
very
long,
but
I
would
like
to
hear
like
you're
more
closely
to
that.
Do
you
think
this
is
going
to
become
a
concern
that
we
need
to
push
to
get
a
counterpart
like
quickly.
C
I
think,
with
responsiveness
to
reviews,
it
won't
be
a
huge
concern.
I
think,
in
terms
of
you
know,
like
expertise
in
the
security
of
package.
It's
good
to
have
someone
with
more
domain
expertise
there
or
more
more
time
spent
working
with
our
features.
A
A
Peter
mentioned
that
we
can
actually
pay
him
for
for
the
reviews
on
the
plan
and
et
cetera,
and
I'm
expecting
they
are
going
to
prepare
an
onboarding
for
whoever
gets
to
that
position.
At
some
point.