From owner-freebsd-testing@FreeBSD.ORG Thu May 21 15:58:13 2015 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CE912949 for ; Thu, 21 May 2015 15:58:13 +0000 (UTC) Received: from valentine.liquidneon.com (unknown [IPv6:2001:4978:f:5c6::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "valentine.liquidneon.com", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A5CE21015 for ; Thu, 21 May 2015 15:58:13 +0000 (UTC) Received: by valentine.liquidneon.com (Postfix, from userid 1018) id 105708FFE2; Thu, 21 May 2015 09:58:05 -0600 (MDT) Date: Thu, 21 May 2015 09:58:05 -0600 From: Brad Davis To: freebsd-testing@freebsd.org Subject: Re: svn commit: r283166 - vendor/atf/dist/atf-sh Message-ID: <20150521155805.GF91287@valentine.liquidneon.com> References: <201505210326.t4L3Qkb2095326@svn.freebsd.org> <20150521150920.GE91287@valentine.liquidneon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 15:58:13 -0000 On Thu, May 21, 2015 at 08:51:44AM -0700, Craig Rodrigues wrote: > On May 21, 2015 8:09 AM, "Brad Davis" wrote: > > > > Did anyone ever hear about getting ATF/Kyua out from under Google? Last > > time I submitted a pull request Julio asked me to sign some Google > > agreement. Which I am not interested in doing and I suspect is keeping > > other people interested in working on ATF/Kyua away as well. > > > > You raise a good point. I know of at least one person at EMC who submitted > a patch to kyua, but then could not get it accepted because of the need for > signing the Google Contributor License Agreement. Getting permission from > EMC to sign the Google CLA proved to be an uphill battle. > > I actually signed the Google CLA for kyua last year. However, this week, > Julio informed me that Google transferred all CLA from one database to > another, and in the process they lost my signed agreement!! So Julio asked > me to sign again. This is annoying. > > ATF/Kyua are Julio's things, so ideally, he would be the one to change the > licensing and signature requirements. However, since he is a Google > employee, he has some rules which he must follow. > > Other than that I don't see what can be done, other than some type of fork > of the kyua project or a rewrite of the code under a different license. Maybe we could fork it and put it under the FreeBSD github page, and then he could just contribute to that, but have it "owned" by FreeBSD instead.. Regards, Brad Davis