From: Chad Dougherty <crd@acm.org>
To: Jon Turney <jon.turney@dronecode.org.uk>,
Libor Ukropec <ace@seznam.cz>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: How does a package become orphaned? (was Re: Attn maintainer: python-paramiko)
Date: Fri, 4 Nov 2022 09:05:49 -0400 [thread overview]
Message-ID: <a00310b1-a68f-0424-f3e1-e76f09490a40@acm.org> (raw)
In-Reply-To: <36a5d2b5-41f7-52a4-c95f-d9f2e4f12e96@dronecode.org.uk>
On 2022-11-04 08:34, Jon Turney wrote:
> The second is not so clear: A package is orphaned if it's maintainer
> is not responsive to queries as to if they still want to be the
> maintainer of the package.
>
> It's undefined how many times we should ping, or how long we should wait
> for a response, but I think that the ~10 months that's elapsed here is
> more than enough!
>
If the prospective adopter is also proposing an update that addresses
security vulnerabilities in the old package, I suggest that that, and
the severity and impact of those vulnerabilities be factored into the
timeout decision.
--
-Chad
next prev parent reply other threads:[~2022-11-04 13:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 22:17 Attn maintainer: python-paramiko Marco Atzeri
2022-01-27 4:18 ` Marco Atzeri
2022-11-02 20:04 ` Libor Ukropec
2022-11-04 12:34 ` How does a package become orphaned? (was Re: Attn maintainer: python-paramiko) Jon Turney
2022-11-04 13:05 ` Chad Dougherty [this message]
2022-11-15 18:47 ` Libor Ukropec
2022-11-16 11:52 ` Thomas Wolff
2022-11-17 10:24 ` Libor Ukropec
2022-11-17 18:32 ` Brian Inglis
2022-12-01 19:41 ` Jon Turney
2022-12-01 20:18 ` Libor Ukropec
2022-12-02 8:20 ` Marco Atzeri
2022-12-05 23:07 ` Libor Ukropec
2022-12-05 20:54 ` Jon Turney
2022-12-06 0:07 ` Libor Ukropec
2022-12-01 19:41 ` Jon Turney
2022-12-01 20:02 ` Achim Gratz
2023-05-09 20:16 ` Trusted maintainers (was: Re: How does a package become orphaned? (was Re: Attn maintainer: python-paramiko)) Jon Turney
2023-05-11 13:57 ` Andrew Schulman
2023-05-13 10:18 ` Marco Atzeri
2023-05-30 13:39 ` Andrew Schulman
2023-06-06 8:12 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a00310b1-a68f-0424-f3e1-e76f09490a40@acm.org \
--to=crd@acm.org \
--cc=ace@seznam.cz \
--cc=cygwin-apps@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).