From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: How does a package become orphaned? (was Re: Attn maintainer: python-paramiko)
Date: Wed, 16 Nov 2022 12:52:33 +0100 [thread overview]
Message-ID: <fdf66f37-7f55-f2cd-0317-a18f68465786@towo.net> (raw)
In-Reply-To: <d56aeb74-1acf-5ead-1bc7-aaf52d730f5d@seznam.cz>
Am 15/11/2022 um 19:47 schrieb Libor Ukropec:
> Dne 04.11.2022 v 14:05 Chad Dougherty napsal(a):
>> 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.
>>
> What I do not want to do is the violent take over, so I gave some time
> to the original owner of the python-paramiko to respond. I created a
> bug on github.com almost 2 weeks ago and so far no reaction:
> https://github.com/wildmichael/cygwin/issues/1
As a general comment, I'd like to point out that "almost 2 weeks" is
even less than someone's holiday time may be...
>
> So I'd like to ask for ITA for his several packages, BUT:
>
> the cygport is executing in "src_test" some python tests that in the
> end requires some python packages not available as cygwin packages
> (typing_extensions, mock, pytest-mock, may be others).
>
> So should I
> a) remove the test? (this is not my preference)
> or
> b) specify/execute in the cygport `pip3 install pkg1 pkg2 ...` - I'd
> expect that executing any stuff in the cygport is not allowed (and I
> do not want to trigger 'misuse alarm')
>
> and additional question - how do I execute scallywag "before" the ITA
> is approved and git repo created? Can/should I use 'playground' branch
> for another package that I already maintain?
>
> I do not see guide on cygwin.com is explaining this.
>
> Thank you,
> Libor
next prev parent reply other threads:[~2022-11-16 11:52 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
2022-11-15 18:47 ` Libor Ukropec
2022-11-16 11:52 ` Thomas Wolff [this message]
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=fdf66f37-7f55-f2cd-0317-a18f68465786@towo.net \
--to=towo@towo.net \
--cc=cygwin-apps@cygwin.com \
/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).