►
From YouTube: 2023-01-12 Package Registry Group Weekly Retrospective
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
So
what
went
not
so
well
and
how
can
we
do
better
I'm
up?
First
I
fell
a
little
bit
behind
on
my
to-do's
and
other
priorities,
and
I
am
looking
forward
to
reading
David's
tips
and
tricks
on
how
to
be
productive
to
to
help
me
prioritize
my
time
and
work
on
that
better.
So
thanks
David
for
sharing
those
thoughts,
I
look
forward
to
reading
them,
David,
okay,.
B
So
so
you
have
a
hard
time
to
fell
asleep,
because
that
that
link
is
a
is
a
link
to
a
wall
of
text.
Well,
yeah
this
week,
pretty
much
the
same.
I
was
slow
catching
up
on
my
backlog
of
beings
and
reviews.
I'm,
not
sure
why
well
I
guess
there
are
several
photos,
but
it
was
a
week
like
this
on
to
what
went
well
with
Kerry.
A
Did
we're
progress
on
the
team
split?
Officially
I've
figured
out
how
to
set
up
geekbot,
so
some
team
members
that
work
on
both
the
package
registry
and
the
container
registry
can
post
one
stand
up
and
it
reports
to
both
channels.
B
Yeah
I
made
a
good
progress
on
Milestone
deliverables
because
this
week
is
well
potentially
the
last
week
for
the
Milestone,
but
I
made
good
progress
on
the
two
background,
migrations
I'm
working
on
and
they
are
quite
challenging,
but
one
is
already
approved
and
it's
waiting
for
the
second
one
which
is
in
maintain
a
review.
So
it's
looking
good
onto
rod.
C
D
This
week,
I
had
the
first
scene
with
a
mentor
to
pick
up
to
become
a
black
and
vacant
maintainer
and
I.
Think
now
it
feels
even
so.
I
started
reviewing
the
code
already
now.
It
feels
that
it's
like
officially,
and
there
is
some
progress
to
track.
D
A
Our
newest
team
member
nabita,
so
she
posted
onboarding,
is
going
smooth
done
with
the
first
Mr
and
so
that's
exciting
to
have
a
her
progress
on
that
and
next
topic.
What
was
something
interesting?
You
learned
this
week,
so
I
posted
I
learned
two
new
things.
The
first
one
is
how
another
team
uses
issue
weights.
I
thought
it
was
interesting
that
they
coordinate
each
of
the
weights
to
the
number
of
expected
Mrs
it
takes
and
like
the
rough
size
estimate.
A
So
it's
just
something
to
learn
how
other
teams
do
things,
so
we
can
take
in
mind
how
we
might
consider
changing
in
the
future
and
then
the
second
interesting
thing
was
in
a
coffee
chat
with
a
peer
em
I
learned
that
they
spent
their
holiday
break
automating
their
planner
issue,
using
chat
GPT
to
write
the
code,
so
I
thought
that
was
pretty
cool
and
I
want
to
borrow
their
code.
Even
that's
in
Python
I'm
not
familiar
with
that,
but
it
looks
like
a
fun
thing:
they
created
their
daily
comments
on
the
issue.
A
D
D
A
Awesome,
it
looks
like
it
was
organized
by
our
previous
team
member.
So
that's
really
cool
excited
to
hear
how
that
goes.
Thank
you
all,
and
this
concludes
our
weekly
async
Metro
I,
guess
not
async,
but
yep
thanks.