X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:from:to:references:in-reply-to
	:subject:date:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=nhJPF5HA5duo+Z+a
	egYGV9BdTc08mTjQVLPbSzWKRgGU6bTDgj6WftdVpjyjWnsgEfaojYeFx5WQbMtY
	IRvBxVCtLXPlxMxMwzDD+E/hg0CPpS1m8YiqsxScf3kGXFMe/xMl7P+/5eUE9eSn
	tl7w60/M8xJmnzVNCqdqOeT2Rps=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:from:to:references:in-reply-to
	:subject:date:mime-version:content-type
	:content-transfer-encoding; s=default; bh=M10jkR/zEF8AfC19oJyCPo
	GzAZk=; b=w+7i3VnbnpWxoPk5xMqKv3ffZ/ZGrEa2LWMybp2UrZG1KVMgLgghDL
	/kqK9L5L0na537DyMVBfUOkIRklgq2qyNPdECZrfQK6m2FH+l/pNMvt3JeGQESGa
	oYy45PewZj4Ch6P0X+YnGpm5ab2r9uFnUw3Iueyz4uN7JyPVZG8R4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=2.0 required=5.0 tests=AWL,BAYES_80,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2
X-HELO: BAY004-OMC1S5.hotmail.com
X-TMN: [qXCxqMBAI9jcYntb4MxECqdUpIzjMSVD]
Message-ID: <BAY169-DS9D800B9B9BCD35696B45DA7B50@phx.gbl>
From: "Tony Kelman" <tony AT kelman DOT net>
To: <cygwin AT cygwin DOT com>
References: <556B79E7 DOT 8070700 AT towo DOT net> <87pp5fl827 DOT fsf AT Rainer DOT invalid> <20150601163329 DOT GQ4308 AT calimero DOT vinschen DOT de> <556DF00C DOT 2030000 AT towo DOT net>
In-Reply-To: <556DF00C.2030000@towo.net>
Subject: Re: mintty project
Date: Tue, 2 Jun 2015 11:37:33 -0700
MIME-Version: 1.0
Content-Type: text/plain;	format=flowed;	charset="utf-8";	reply-type=response
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes

> • Yaakov could turn github/cygwinports into an "organisation account"
> and give me admin rights for the mintty repository.
> • I could create a dedicated account and repository.
> • I could host mintty somewhere else.

There is also an inactive "mintty" user on github, you could contact
github about name squatting there and try to turn that into an
organization account. Send nowox an email to let him know this
conversation is being had (he may not subscribe to the cygwin list?),
he might even be willing to transfer ownership of the migrated
repository that he's made, if that would save you any time.

> My concerns against github are different; I have a strong impression that 
> it encourages anarchic project handling,
> and I feel the concept of everybody being allowed to create forks and 
> submit "pull requests" may not be good for a core project.
>
> Opinions?

What's wrong with encouraging more people to contribute more easily?
Someone qualified still needs to review the patches before merging them,
and there are free services that offer excellent integration with github
to simplify automated testing.

The single biggest argument that I've ever seen in favor of using github
is this plot: https://jakevdp.github.io/figures/author_count.png
of the cumulative contributor count to numpy, scipy, and matplotlib over
time, comparing trends before and after those projects moved to github.

Large projects like Node.js, Rust, Julia, manage just fine with hundreds
of contributors on github (and would probably not flourish anywhere near
as well if they were not using github). For a project with a smaller
number of contributors like mintty, really the only thing you have to do
to avoid your perceived "anarchy" problem is emphasize that your repo is
the canonical upstream. If you're taking over maintenance of the cygwin
package, that's not hard to do.

-Tony


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple