public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: mintty project
Date: Mon, 01 Jun 2015 08:36:00 -0000	[thread overview]
Message-ID: <20150601083638.GH4308@calimero.vinschen.de> (raw)
In-Reply-To: <556B79E7.8070700@towo.net>

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

On May 31 23:15, Thomas Wolff wrote:
> As a contributor to mintty, some sent me a notice discussing the move to
> github (http://www.reddit.com/r/cygwin/comments/37vgwi/what_happened_to_minttys_maintainer_andy_kopp/)
> and now there is already a github fork of mintty
> (https://github.com/nowox/mintty/tree/master/src).
> I'd like to discuss what you (cygwin maintainers and others) think of this
> move, whether it's good for mintty to be hosted on github. Personally I feel
> that a platform like sourceforge provides a more professional project
> environment which would provide more confidence in stable project
> development.
> What do you think?

It's not so much the hosting service providing the upstream repository
which concerns me, it's the lack of development, the lack of a responsive
maintainer, and the lack of a new, stable mintty package.  You're in for
one of the newly created pink plush hippos if you're going to take over
mintty maintainership ;)

Having said that, github is ok.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-06-01  8:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31 21:49 Thomas Wolff
2015-06-01  7:03 ` Tony Kelman
2015-06-01  8:36 ` Corinna Vinschen [this message]
2015-06-01 14:16   ` Frank Fesevur
2015-06-01 15:50     ` Corinna Vinschen
2015-06-05  5:36       ` Thomas Wolff
2015-06-08 12:13         ` Corinna Vinschen
2015-06-08 20:11           ` Csaba Raduly
2015-06-09  9:57             ` Corinna Vinschen
2015-06-09 19:55               ` Thomas Wolff
2015-06-10  8:18                 ` Corinna Vinschen
2015-06-23 18:54         ` Corinna Vinschen
2015-06-02  6:05   ` Thomas Wolff
2015-06-02  7:59     ` Corinna Vinschen
2015-06-01 16:14 ` Achim Gratz
2015-06-01 16:33   ` Corinna Vinschen
2015-06-02 18:04     ` Thomas Wolff
2015-06-02 18:39       ` Tony Kelman
2015-06-04  6:29         ` Thomas Wolff
2015-06-04  8:16           ` Frank Fesevur
2015-06-01 16:55   ` Eric Blake

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=20150601083638.GH4308@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@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).