Return-Path: Delivered-To: apmail-incubator-aries-dev-archive@minotaur.apache.org Received: (qmail 74197 invoked from network); 2 Oct 2009 21:00:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Oct 2009 21:00:56 -0000 Received: (qmail 40772 invoked by uid 500); 2 Oct 2009 21:00:56 -0000 Delivered-To: apmail-incubator-aries-dev-archive@incubator.apache.org Received: (qmail 40724 invoked by uid 500); 2 Oct 2009 21:00:56 -0000 Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: aries-dev@incubator.apache.org Delivered-To: mailing list aries-dev@incubator.apache.org Received: (qmail 40714 invoked by uid 99); 2 Oct 2009 21:00:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Oct 2009 21:00:55 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ianrbsn@googlemail.com designates 209.85.218.226 as permitted sender) Received: from [209.85.218.226] (HELO mail-bw0-f226.google.com) (209.85.218.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Oct 2009 21:00:43 +0000 Received: by bwz26 with SMTP id 26so1278123bwz.12 for ; Fri, 02 Oct 2009 14:00:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Rxp+3vNit+G+TF7fmw7cgfVfzp37jTIdRMgVw2uDtlI=; b=Zokb1uwOOGb4GPoRDjJeQILuvPb9DgsD6Hb0XU8kO3Gn0YGrwx6zdgZkRGSJffyYhy FcBE7sjkWNbt2LwVhozxNi0xY/9RcYwmBjbA28r1BH1ETW/2Ztovk16rvs0U7aLMBJTp oprIv3JOXDQNyJcor++dpSDIY9Jxr4YMUx8wI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=m+KrkYmh4WDY/eASPZ5P4IIQeFlAk+sJ687+kqJNYv2ky73LkN0DGsDByRNxV1px/p Sdm4VTFhx3vqjIUqfRyZH7NcX9PkavK23pRx4GuvvIdBDl6OMqOSFcK09TkKXAlt1nJp aMyv9LOZz0Mi/5eDqmbURReQIsNgQHOZEtQ3M= Received: by 10.204.48.194 with SMTP id s2mr1501863bkf.210.1254517222884; Fri, 02 Oct 2009 14:00:22 -0700 (PDT) Received: from ?192.168.0.2? (93-97-38-188.zone5.bethere.co.uk [93.97.38.188]) by mx.google.com with ESMTPS id k29sm2886571fkk.25.2009.10.02.14.00.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 02 Oct 2009 14:00:21 -0700 (PDT) Message-ID: <4AC669EE.2090507@googlemail.com> Date: Fri, 02 Oct 2009 22:00:30 +0100 From: Ian Robinson User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: aries-dev@incubator.apache.org Subject: Re: Running TCKs on our code References: <79ECB372-4148-4641-95F9-44D12AC8F989@toolazydogs.com> <345578340910020131p701e7ce1yf9c09f4482ab8e87@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org My understanding from speaking to Dan Bandera (IBM's member of the OSGi BoD ) is that the OSGi Alliance BoD recognize that qualified not-for-profit organizations, such as ASF, have a need for OSGi Compliance Tests at no-charge, as evidenced by the Alliance's JSR 291 TCK license ( see: http://www.osgi.org/JSR291/TCK#nonprofitlicense ). I understand the Alliance has work in-progress now that will provide the OSGi Compliance Tests (which are undergoing OSGi member approval now) for the newly approved and published OSGi Service Platform Release 4 Version 4.2 Specifications under a similar license in the near future. If that license turns out to be acceptable to the ASF then we should be able to evolve to a position where we won't need a special mailing list for discussing finalized OSGi CTs. Ian Kevan Miller wrote: > > On Oct 2, 2009, at 10:27 AM, Jeremy Hughes wrote: > >> 2009/10/2 Alan D. Cabrera : >>> Luckily there's a couple of Alliance members in this project who can >>> perform >>> this task until things get sorted out. >>> >>> In any case we'll need a TCK mailing list; I'll get that done. I'm >>> not sure >>> how we'll vet membership. David, since you're a chair maybe you could >>> provide a list? >> >> Is there a precedent for a TCK mailing list on other Apache projects? >> What are the rules for entry? What gets discussed there that can't be >> discussed on the dev@ list? I just want to be clear on what we're >> talking about. > > Hi Jeremy, > Yes. There are TCK-specific mailing lists and TCK-specific SVN trees > within Apache. Access is limited to Apache committers who have signed > the following NDA -- http://www.apache.org/jcp/ApacheNDA.pdf > > TCK materials must be protected and kept private. Beyond PASS and > FAIL, there are limits on detailed discussions of the tests on public > mailing lists. Any specific discussions occur on the private TCK > mailing list. > >> >> I'm guessing the purpose of a TCK mailing list would be to discuss >> everything around running OSGi Compliance Tests, since I believe the >> OSGi Alliance only allows its members to download (maybe there are >> other levels of OSGi affiliation that would allow this too I don't >> know). >> >> What do other Apache projects do in this situation? Is there guidance >> or are we breaking new ground (in particular with the OSGi). Hasn't >> Felix come up against this before? What happens there? > > It sounds like the Felix "project" is not running TCK tests. Rather, > "individuals" (who are also members of the Alliance) are running TCK > tests on the Felix code. > > --kevan > > >