From owner-freebsd-testing@FreeBSD.ORG Thu May 21 15:51:46 2015 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7811B4B2; Thu, 21 May 2015 15:51:46 +0000 (UTC) Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EF8431F77; Thu, 21 May 2015 15:51:45 +0000 (UTC) Received: by lbbuc2 with SMTP id uc2so21322190lbb.2; Thu, 21 May 2015 08:51:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=s9gg0SE+450U0v9HA8frGDJLA+HnTezu4ZkKa3fqEoQ=; b=mffmfxi0QKRkmSQQUDco5Rtzm6DzTCLnB9sKnajDw+HlT970QsEu8ybjDw82Nqa4S1 uwnftcUxxntc2QOIr8q/uMqcIbV4rpzUR0AW79cfLH6Byv1KizkoKm369UYcwHNxAc2Y ufu3BouvrQV74CRYvkKTG4a0QvQ/69JQvp8Y4tEyOtsg/+xrkiAUxv7/SR7qiKV7Rq7k JDEYBT9OsKDvk6JhMsegxlR/v2ure9vuqXeqr+iQzFLHJByKWVFIRJQ9J5hb/Zw3T3hK UF3rBAkXmWMZx1N7D4bUVZDhAuv+jhkNvQ5FBMXxSMw5Y5GEpR7Tdidt0wSKlUe2fcCM rilg== MIME-Version: 1.0 X-Received: by 10.152.23.66 with SMTP id k2mr2834778laf.89.1432223504105; Thu, 21 May 2015 08:51:44 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.164.38 with HTTP; Thu, 21 May 2015 08:51:44 -0700 (PDT) Received: by 10.112.164.38 with HTTP; Thu, 21 May 2015 08:51:44 -0700 (PDT) In-Reply-To: <20150521150920.GE91287@valentine.liquidneon.com> References: <201505210326.t4L3Qkb2095326@svn.freebsd.org> <20150521150920.GE91287@valentine.liquidneon.com> Date: Thu, 21 May 2015 08:51:44 -0700 X-Google-Sender-Auth: T3cH2z8w_UdGwxjbe_Fq968XkjQ Message-ID: Subject: Re: svn commit: r283166 - vendor/atf/dist/atf-sh From: Craig Rodrigues To: Brad Davis Cc: freebsd-testing@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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:51:46 -0000 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. -- Craig