►
Description
Starting this week, the Package Registry will be moving the retro to be done async in the team's Weekly Async Update issue each week.
Issue Example: https://gitlab.com/gitlab-org/ci-cd/package-stage/package-registry-group/package-registry/-/issues/14
A
All
right
welcome
to
this
week's
package
registry
weekly
retrospective.
That
will
not
be
actually
the
retrospective.
It
is
the
leak
ending,
January
27th
and
my
name
is
Carrie,
and
we
have
a
few
changes
that
we're
going
to
talk
about
today.
So
instead
of
doing
a
synchronous,
weekly
retrospective
I'd
like
to
move
it
to
be
on
everyone's
Friday
and
do
it
asynchronous
in
the
team's
weekly
update,
please
provide
your
feedback
and
thoughts
on
the
comment.
A
I
added
in
case
you'd
like
to
see
that
done
a
little
bit
differently
and
then
there's
also
I
had
two
ideas.
We
could
either
create
retro
threads
for
each
question
and
then
everybody
contributes
to
those
threads
I
tried
that
last
week
and
then
this
week,
I
wanted
to
see
what
it
felt
like
if
everyone
created
their
own
retro
thread
with
answering
the
questions
you
wanted
to
and
determining.
A
If
you
wanted
to
keep
your
comments
as
safe
and
private
or
if
you
wanted
to
share
it
publicly
depending
on
the
content
you
were
sharing,
it
was
up
to
you.
So
please
check
out
the
weekly
update
and
contribute
your
retro
thoughts
on
Friday,
so
going
forward.
We'll
have
retros
asynchronous
and
then
this
week
we're
going
to
just
kind
of
announce
these
changes
and
then
next
week
we'll
start
with
doing
a
weekly
team.
A
Sync
at
this
same
time,
actually
it'll
be
an
hour
earlier,
so
that
it
is
a
little
bit
more
inclusive
for
a
few
of
the
team.
Members
and
I
already
spoke
with
Tim
he's
good
with
just
doing
this
async,
because
that
would
be
at
6am
his
time
and
I
would
be
open
to.
We
could
do
it
even
an
hour
earlier
so
I'm
flexible
on
the
time.
B
I
think
at
some
point
we
we
might
achieve
like
the
the
the
one
team
at
gitlab
that
will
do
all
the
meetings.
Async
could
be
a
goal,
no
I
think
yeah.
We
need
to
try
this.
The
the
facing
team
ritual
one
thing
I
would
I
would
emphasis,
is
get
keeping
those
those
Retros
public,
because
usually
these
weekly
retrospective
was
recorded
publicly
unless
there
is
configuration
but
I
think
it's
a
good
idea
to
keep
that
transparency.
B
A
Awesome
so
lots
of
changes
as
we're
a
growing
team,
we'll
have
a
new
team
member
starting
next
week,
and
so
we
can
keep
iterating
as
we
figure
out
how
to
make
it
work
with
everyone's
time
zones.
But
I
think
what
you
called
out
is
super
important,
so
I,
like
everyone,
adding
their
own
retro
thoughts
and
keeping
it
public
unless
it
needs
to
be
safe,
for
whatever
reason
it's
up
to
the
contributor
to
decide
if
they
want
to
Mark
the
comment
as
public
or
leave
it
private
or
leave
it
as
public
awesome.