public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Libor Ukropec <ace@seznam.cz>
To: cygwin-apps@cygwin.com
Subject: Re: How does a package become orphaned? (was Re: Attn maintainer: python-paramiko)
Date: Thu, 17 Nov 2022 11:24:38 +0100	[thread overview]
Message-ID: <be310c0a-f31a-a194-c98d-b89b38230111@seznam.cz> (raw)
In-Reply-To: <fdf66f37-7f55-f2cd-0317-a18f68465786@towo.net>

Dne 16.11.2022 v 12:52 Thomas Wolff napsal(a):
> 
>> 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...

See above in the thread - author did not react here on cygwin for months. What I did, I've 
found the author on GitHub and contacted him there as well.

 >>Jon Turney: 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!

>>
>> 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')

Any advice to this?
>>
>> 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.
and this?
>>
>> Thank you,
>> Libor
> 
> 


  reply	other threads:[~2022-11-17 10:24 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
2022-11-17 10:24             ` Libor Ukropec [this message]
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=be310c0a-f31a-a194-c98d-b89b38230111@seznam.cz \
    --to=ace@seznam.cz \
    --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).