public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Cc: Yaakov Selkowitz <yselkowi@redhat.com>
Subject: Re: Putting packages up for adoption
Date: Fri, 20 Mar 2020 11:19:07 +0100	[thread overview]
Message-ID: <20200320101907.GI778468@calimero.vinschen.de> (raw)
In-Reply-To: <cba88beea877fb065afc8c12d489243f2cb26011.camel@cygwin.com>

[-- Attachment #1: Type: text/plain, Size: 2670 bytes --]

On Mar 19 23:47, Yaakov Selkowitz wrote:
> Hello Cygwin package maintainers,
> 
> As you all probably noted, I haven't been around much.  My team at work
> has been really busy accomplishing some pretty amazing feats over the
> last number of months, most recently:
> 
> https://www.ibm.com/blogs/systems/red-hat-openshift-now-available-ibm-z-linuxone/
> 
> While it's been great for my career, it obviously hasn't been so good
> for you and the community as a whole, as I've really had absolutely no
> time to work on Cygwin packaging.  In fact, I've barely used my Windows
> machine and VMs at all for quite some time.  And to be completely
> honest, it really doesn't look like that's going to change anytime soon
> either.
> 
> To that end, in the best interest of the community, please consider my
> packages up for adoption.  I don't expect that any one person will take
> all of them; some are obsolete and due for removal anyway, some should
> be picked up as soon as possible, and others might just end up
> bitrotting if nobody is interested in them.  However, in whatever there
> is interest (or need), hopefully what is there now will serve as a
> strong foundation to on which to continue to build.
> 
> (And just to be perfectly clear, we're all in good health; this has
> nothing to do with the current crisis, except that maybe some of you
> have more time at home now to use to the benefit of Cygwin.)
> 
> I'll continue lurking on the lists, and with this burden off my
> shoulders, try to transition to being a little more active as a mentor.
> So, please feel free to ask questions (on list, please), particularly
> if you don't understand why I did something in my packaging.  There is
> (or at least was at the time!) a good reason for all of it, even though
> I often neglected to document why.  I'll try to do what I can to make
> this as smooth as possible.
> 
> All the best, stay safe, and keep on building!
> 
> --
> Yaakov

There's no number of goldstars or plush hippos which would do justice to
what you did for Cygwin, Yaakov.  If there's something like the ULTIMATE
PLUSH HIPPO REPLACING EVRY OTHER PLUSH HIPPO, you should get it.

Thanks for everything you did for Cygwin!

There's just one problem.  What happens to your packages which are not
upstream packages but Cygwin-specific?  Especially cygport comes to
mind.  Off the top of my head I don't know which other packages fall
into that category.

However, for these packages, we should ideally move them from your
cygwinports github repo to cygwin.com, right?


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-03-20 10:19 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20  3:47 Yaakov Selkowitz
2020-03-20  5:04 ` Marco Atzeri
2020-03-20  6:05   ` ASSI
2020-03-20 10:19     ` Corinna Vinschen
2020-03-20 10:23   ` Corinna Vinschen
2020-03-20  8:13 ` Hamish McIntyre-Bhatty
2020-03-20  8:28   ` Marco Atzeri
2020-03-20  9:29 ` Jan Nijtmans
2020-03-20 10:22   ` Corinna Vinschen
2020-03-22 22:34   ` Yaakov Selkowitz
2020-03-23 12:07     ` Jan Nijtmans
2020-03-23 15:45       ` Yaakov Selkowitz
2020-03-23 21:04         ` Jan Nijtmans
2020-03-23 23:37           ` Yaakov Selkowitz
2020-03-24 11:41             ` Jan Nijtmans
2020-03-24 13:51               ` Yaakov Selkowitz
2020-03-24 14:11                 ` Jan Nijtmans
2020-03-24 14:24                   ` Yaakov Selkowitz
2020-03-24 19:27                     ` Jan Nijtmans
2020-04-01  9:10                       ` Jan Nijtmans
2020-03-20 10:19 ` Corinna Vinschen [this message]
2020-03-20 12:11   ` Jon Turney
2020-03-24 20:19   ` Andrew Schulman
2020-04-01 20:58     ` Yaakov Selkowitz
2020-04-02  7:35       ` Corinna Vinschen
2020-07-21  0:33         ` Andrew Schulman
2020-03-20 12:09 ` Jon Turney
2020-03-21 12:47   ` Thomas Wolff
2020-03-21 14:10     ` Jon Turney
2020-03-20 12:31 ` Marco Atzeri
2020-03-20 17:32   ` Achim Gratz
2020-03-20 19:16     ` Hamish McIntyre-Bhatty
2020-03-20 19:22     ` Yaakov Selkowitz
2020-03-20 20:30     ` Marco Atzeri
2020-03-22 15:34       ` ASSI
2020-03-22 16:36         ` ASSI
2020-03-22 19:49           ` Yaakov Selkowitz
2020-03-22 20:39             ` Achim Gratz
2020-03-22 19:03   ` Achim Gratz
2020-03-23 17:14     ` ASSI
2020-03-23 23:06       ` Marco Atzeri
2020-03-20 16:17 ` Doug Henderson
2020-03-21 14:12   ` Jon Turney
2020-03-26  5:54 ` Marco Atzeri
2020-03-26  7:19   ` Yaakov Selkowitz
2020-03-27 17:52     ` Marco Atzeri
2020-03-27 20:52       ` Yaakov Selkowitz
2020-03-28  3:33         ` Marco Atzeri
2020-03-30  6:01           ` Yaakov Selkowitz
2020-03-27 17:53     ` Marco Atzeri
2020-03-27 18:32       ` Hamish McIntyre-Bhatty
2020-03-27 19:10         ` Yaakov Selkowitz
2020-03-27 20:02           ` Hamish McIntyre-Bhatty
2020-04-10 12:52     ` Python - plan & execution Marco Atzeri
2020-04-23 21:54       ` Yaakov Selkowitz
2020-04-27 14:34         ` Jon Turney
2020-05-25  4:52           ` Marco Atzeri
2020-05-25 13:43             ` Jon Turney
2020-05-25 23:45             ` Yaakov Selkowitz
2020-05-26  4:31               ` Marco Atzeri
2020-06-08 19:20                 ` Jon Turney
2020-06-08 20:02                   ` Marco Atzeri
2020-06-09 13:20                     ` Jon Turney
2020-06-09 19:16                       ` Marco Atzeri
2020-06-12 14:44                         ` Jon Turney
2020-05-25  5:02       ` Marco Atzeri
2020-07-07 18:40         ` Marco Atzeri
2020-07-09 23:52           ` airplanemath
2020-07-10  5:34             ` Marco Atzeri
2020-04-04  3:17 ` Putting packages up for adoption Marco Atzeri

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=20200320101907.GI778468@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    --cc=yselkowi@redhat.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).