From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) by sourceware.org (Postfix) with ESMTPS id 85B1B3959C9C for ; Wed, 16 Nov 2022 11:52:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 85B1B3959C9C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=towo.net Authentication-Results: sourceware.org; spf=none smtp.mailfrom=towo.net Received: from [192.168.178.51] ([91.65.247.133]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPSA (Nemesis) id 1M7v18-1orRDd0jI2-004xfd for ; Wed, 16 Nov 2022 12:52:35 +0100 Message-ID: Date: Wed, 16 Nov 2022 12:52:33 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: How does a package become orphaned? (was Re: Attn maintainer: python-paramiko) To: cygwin-apps@cygwin.com References: <3fdca14d-95fa-0398-46a9-6d5291ceae96@gmail.com> <0282d084-b2b2-132f-1e82-4159a4d1de05@gmail.com> <36a5d2b5-41f7-52a4-c95f-d9f2e4f12e96@dronecode.org.uk> From: Thomas Wolff In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:ypqEz5AIJxwmagxWEGZr96za1vAbv4CnLZS0vcZKnrla556Yv16 wS+XCUm+3QuHxReA9ffUK4jnHlDzq8pbvcwStSliD53Ru9d+zVP5CtH95n8e8ql/K356MrZ kZrhbydvlQDI50mpe9avkSdr8c/xQLDavFlCapOJW0PBvdmf6HADmmGlMpAyBbu4yWQ2/2G v/VScRtHH1gwVa3tpW3iw== X-UI-Out-Filterresults: notjunk:1;V03:K0:dX3Q4CnSh9M=:yICkfwLIQ4OgYLJwCSk25j AY/bc4VPy5EZfnuHOQztgIJ6fjZiY9sSUiEdI5rZwUOX0uSWp1zlqN9wtLLYrIGOaYVJ9d65n 6AhzJA3ZU/TB4wGxCCeGEKk4K2WJwTygr36g0ThsrPrze3NzFNG9vhN2nupdqr6ZbAtzQUr71 c6/6R+za8cb6ZN8olrlfMwIVm0sFMhWtfwRUlcUXUljvAFSXYyvLh8QcAd+6JZdsEk4ZKnmE6 gY1+/goe76Oax5AwmYosa1nOMwSvSYaUAt3etFGrpfC4/D1dTGOpglWTIdc6Gqep3hTxmEsRo DJaZLsoVZxPpgblPhs+UpweDN6Bail2JFeIOm84BFYm6uvJFGUaUQ6g0larQs0aLYKK+WH6yY oKXpd8pmLOoEPSg5z0EOz5RGUZR1A+tOeSHiFr3rPGi93lmCKngqJsq1qRT6N0a2XCbjVfz8r u6yox39e76FeQt1irf1/NhI8G46ABBPzx3po8UKNTa6T8HLx3vRGWWb+4XTHF3MMn/LdKtECu TP8gHj1Rw3IjtSJJdfw/f3AFjqjjRwypyvnMNbtda+6l/OpCjOhKOTbk8E+lRsuf7IzTmZzzJ YqoQ2JagDWcKCouTcZL44/rNiXBP/89eLYKSitMENPnxS/vXE87Hbz4qIWmlNp7SL7K6dsbdN l38OB5LrSv0uAelvbcH8IGgdkLq7+jIhMzM1xVjrKNOtSskIngie+71tU4bA4Weoy1Zf4xiz/ SHzMz70+R9LzawTD4vAwAtYLtSKbRocjSDawDuNsfW9bo9vx5yqJM5CduI+0WvmpSMQ8afE0/ T3E+xBdHGY6gPiPnFXx+k0DHdlOaVHpiVE7rOiyNTDpheIdzcILXZtnPD/gzrsACPN4mLCXzk 9//0hnN0hZzp+09tlS/oPfBpxUPb3hdUrOEE8dVKLmnhkXmFf772rc5ozUJQ/XwqNBrUjfeI1 A6sXGGtv26l69meUM3jizdyS8FvCuPPr0R+SXnKDaAwndbfdPrl9XGQ8juVf576j0dD8lXGDA OrL6GaxpcxP7XrJtRQeChkc2hkLY0gg39YFQpZDaUjFYDNc6jyTBiDx4MK37ZnRmlEwXj1RrL rdZgemuoWs56zg5Tjp64rxBIdXjNJmH2r8t7UTlonKtwDo2wB5nujEcorUXbuE1Dkr0gsmwGn Z8eG6vGcGEYIex/nWvY0Qx2defgGGlKigUySb7qDLCmlKvLDUFAs2o8AlrawzfKoIOlySEeWI gTt3emElXZOsO9Bw34YX7Fqh0ajZx/8HhCcCQeel/aqnJA6keILsGSmihdv54MFux9OSgReOH Z2vAMuVX X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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