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:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=udu+/wY/y8xb5hlaGm0a4kxa5qcA2zTZvyVljgdoqlG
	OKAOaei3DJkndRAC04vT1F/BCyh1fVvtCLo4MxXlxqP3P4hcAW8ptX20rB7PoysY
	azam9pU4pLs0aozuvJZM6Z24Bqs/nvMgtBqPrIrwkT6eMJ9BOCA9mZ3ujcU3svK0
	=
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:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=arhHDc5MS5KvJ6lOWRtXhVO2nxc=; b=CvpdnPfWyYWnPp4x1
	TNcJ3O17qJNXi4TcAjTA2mPlM/zix4kyBdJI3hU3So+z+LDSQhbL4cyuAZjW6Hqa
	WFzACvkd60+TbXSvwpc2VuGCQJY0YQ5LrjNKIz9zki7ufm7y0XnVcN5zYvnYdgrV
	dnJTVl+YY6OQ2nLZ1zSFd45cVA=
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=4.6 required=5.0 tests=AWL,BAYES_50,FOREIGN_BODY,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2
X-HELO:	mout.kundenserver.de
Message-ID:	<556DF00C.2030000@towo.net>
Date:	Tue, 02 Jun 2015 20:03:56 +0200
From:	Thomas Wolff <towo AT towo DOT net>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: mintty project
References:	<556B79E7 DOT 8070700 AT towo DOT net> <87pp5fl827 DOT fsf AT Rainer DOT invalid> <20150601163329 DOT GQ4308 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20150601163329.GQ4308@calimero.vinschen.de>
X-TagToolbar-Keys:	D20150602200355586
X-UI-Out-Filterresults:	notjunk:1;V01:K0:8hWM7DYqDdU=:I0J+8hbcyM0dW83hTtffMM T4UcXj8o4VC6y64XZ0vZvVNerejRcV5QKUbcpcONZxVsXQl6LZHynpPJrfnZ8jhLmwku62srJ 8qt1KaonCp9Wre5QmW6fZ+Dmo61Gki4ERFtM+v00SsxZN4Mgb/ka75kVptWMAumw9/SYIXfNf vdzcjexlDfppi16MKTedYGrpC+YE0DwwE/gi5VyMV0gWprJP2CB68PmfgVnQciUX/jzOp0QkA QBAWxxaDd77hnCU9k8QZQtlxJQ29P05Nd9qZK/Qsoy3CgIKcwATQVCFRgAbyerDcBmyWdgO6f RZiDDBVtkXdIlBm5PGz/J73jS+BUmxYVEZqMX2iFvsxrF/sH0x6H2gK9cVEHWPM9fNQHFskyA 01ueQdevbfuasDCe8wXEIdSPD4BlDjO40ZLI6fRD5H0idrtSD4cg/TPKbRY+Bch40CMDb2aCo zlgUkD1PX/csuY2XBb9wn3I8qoNMqqpQe17DdYaWoBtXRN5VyVCkSA2e5PuQM8D1NHQGC0y+L Mw0XOWdDfl52xyUIeJrr3b54VRBLma5M9P4Tkd+JE0j9UgNvbkxPAemy2neI5QZNuB+FdQe8X 0Kd+guMbBCH2EJV15603VucjXrQjnwxsjrrBc2xAeGldveO5ClvOFlupaerMtyNnpODJDQ8Fx EYCyIWKil3bjoB++cjQqxjiq62+YTJp90pAAeqs+UEf488A==
X-IsSubscribed:	yes

Am 01.06.2015 um 18:33 schrieb Corinna Vinschen:
> On Jun  1 18:14, Achim Gratz wrote:
>> Thomas Wolff writes:
>>> 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.
>> ...
>> And that question of yours is moot since mintty already is on GitHub, in
>> 26 different forks.  Most of them are "Automatically exported from
>> Google Code." and some not even fully up-to-date.
After some browsing, I've learned that github encourages people to make 
private forks, as a playground or whatever.
That may be fine but doesn't really count as an argument for an 
"official" hosting platform.
>> Then closest to Cygwin is the one from cygwinports (Yaakov).
> That should probably be the version going ahead with...
That fork does not include the issue list (which could probably be 
added); also github/cygwinports is a github "user account" which, 
according to 
https://help.github.com/articles/what-are-the-different-access-permissions/ 
gives limited flexibility of assigning access rights. I guess as a 
package maintainer, admin rights of the official repository would be 
useful, which is an option with a github "organisation account".
So I see 3 options:
• 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.

Eric Blake wrote:
> I personally avoid github; it encourages the use of proprietary code ...
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?
------
Thomas

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
http://www.avast.com


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

- Raw text -