You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Peter Firmstone <ji...@zeus.net.au> on 2010/11/16 13:58:10 UTC
New name for Jini TCK? Was: Re: River-32 Clarification of Code Provenance
Nigel Daley wrote:
> On Oct 13, 2010, at 3:42 PM, Peter Firmstone wrote:
>
>
>> River is an Implementation of the Jini Spec.
>>
>> There is a Patent covenant, see River-339
>>
>> Sun is re-licensing its Jini technology Standard specifications under
>> ALv2 and providing a separate "Jini Community Standards Patent
>> Non-Assertion Covenant ("Covenant") that enables others to create
>> unrestricted independent implementations of the specifications.
>>
>>
>> There is a significant amount of remaining code, relevant to Apache River, which we may not be able to use as subprojects due to code provenance.
>>
>> I've closed River-338, which was for creating a subproject of the existing implementation of Jini Surrogate, since I haven't been able to satisfy code provenance rules. We can consider a clean room implementation for Jini Surrogate.
>>
>> Nigel Daley has confirmed that he is the primary author of the Jini TCK, River-32. Since Sun Microsystems licensed this code under AL2 and have provided a Patent Covenant and Nigel is an Emeritus Committer of Apache River, is this sufficient provenance to make a Subproject proposal for the Discovery Lookup and Join Test Kit?
>>
>> If this is the case, I was also wondering if Nigel would like to propose a name for the TCK Project?
>>
>
> Not much of a namer (just look at it's current name :p ). I happily defer to the active community :-)
>
> Cheers,
> Nige
>
>
>
Can anyone think of name for the Jini TCK?
Cheers,
Peter.
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code
Provenance
Posted by Greg Trasuk <tr...@stratuscom.com>.
On Tue, 2010-11-16 at 07:58, Peter Firmstone wrote:
>
> Can anyone think of name for the Jini TCK?
>
River TCK?
Cheers,
Greg.
>
> Cheers,
>
> Peter.
--
Greg Trasuk, President
StratusCom Manufacturing Systems Inc. - We use information technology to
solve business problems on your plant floor.
http://stratuscom.com
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code Provenance
Posted by Tom Hobbs <tv...@googlemail.com>.
Is the name just to satisfy some legal whatsit?
What about just dropping the 'T'? It then becomes the "Jini
Compatability Kit". Is that different enough?
On Tue, Nov 16, 2010 at 12:58 PM, Peter Firmstone <ji...@zeus.net.au> wrote:
> Nigel Daley wrote:
>>
>> On Oct 13, 2010, at 3:42 PM, Peter Firmstone wrote:
>>
>>
>>>
>>> River is an Implementation of the Jini Spec.
>>>
>>> There is a Patent covenant, see River-339
>>>
>>> Sun is re-licensing its Jini technology Standard specifications under
>>> ALv2 and providing a separate "Jini Community Standards Patent
>>> Non-Assertion Covenant ("Covenant") that enables others to create
>>> unrestricted independent implementations of the specifications.
>>>
>>>
>>> There is a significant amount of remaining code, relevant to Apache
>>> River, which we may not be able to use as subprojects due to code
>>> provenance.
>>>
>>> I've closed River-338, which was for creating a subproject of the
>>> existing implementation of Jini Surrogate, since I haven't been able to
>>> satisfy code provenance rules. We can consider a clean room implementation
>>> for Jini Surrogate.
>>>
>>> Nigel Daley has confirmed that he is the primary author of the Jini TCK,
>>> River-32. Since Sun Microsystems licensed this code under AL2 and have
>>> provided a Patent Covenant and Nigel is an Emeritus Committer of Apache
>>> River, is this sufficient provenance to make a Subproject proposal for the
>>> Discovery Lookup and Join Test Kit?
>>>
>>> If this is the case, I was also wondering if Nigel would like to propose
>>> a name for the TCK Project?
>>>
>>
>> Not much of a namer (just look at it's current name :p ). I happily defer
>> to the active community :-)
>>
>> Cheers,
>> Nige
>>
>>
>>
>
> Can anyone think of name for the Jini TCK?
>
>
> Cheers,
>
> Peter.
>
>
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code Provenance
Posted by Tom Hobbs <tv...@googlemail.com>.
Ditto. (-1)
"Chastise" is a bit obscure for me. An acronym where the words
describe the project works best in my opinion.
On Mon, Nov 22, 2010 at 3:47 PM, Christopher Dolan
<ch...@avid.com> wrote:
> -1 from me. I think too many open source projects have obscure names.
> Jini Compliance Kit (or River Compliance Kit) has obvious meaning and
> has better uniqueness in a search engine.
>
>
>
> Chris
>
>
>
> From: Jim Hurley [mailto:jim.hurley@me.com]
> Sent: Thursday, November 18, 2010 5:17 AM
> To: river-dev@incubator.apache.org
> Cc: river-dev@incubator.apache.org
> Subject: Re: New name for Jini TCK? Was: Re: River-32 Clarification of
> Code Provenance
>
>
>
> +1 Chastise
>
> That's great, Peter.
>
> -Jim
>
>
> On Nov 18, 2010, at 03:37 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
> :
>
> Gregg Wonderly wrote:
> >
> > I'd suggest the name of a river Dam somewhere in the world.
> Any
> > suggestions of fun and non-controversial names? For example,
> Hoover,
> > is probably not good because eventually people would just say
> "that
> > sucks" -:)
> >
> > Gregg Wonderly
>
> Well, we could name it Chastise, after the Dam Busters from WW2.
>
> Chastise also means to scold severely, which is what one would
> do to
> someone who didn't honour the Jini Discovery and Join Protocol.
>
> Cheers,
>
> Peter.
>
>
RE: New name for Jini TCK? Was: Re: River-32 Clarification of Code Provenance
Posted by Christopher Dolan <ch...@avid.com>.
-1 from me. I think too many open source projects have obscure names.
Jini Compliance Kit (or River Compliance Kit) has obvious meaning and
has better uniqueness in a search engine.
Chris
From: Jim Hurley [mailto:jim.hurley@me.com]
Sent: Thursday, November 18, 2010 5:17 AM
To: river-dev@incubator.apache.org
Cc: river-dev@incubator.apache.org
Subject: Re: New name for Jini TCK? Was: Re: River-32 Clarification of
Code Provenance
+1 Chastise
That's great, Peter.
-Jim
On Nov 18, 2010, at 03:37 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
:
Gregg Wonderly wrote:
>
> I'd suggest the name of a river Dam somewhere in the world.
Any
> suggestions of fun and non-controversial names? For example,
Hoover,
> is probably not good because eventually people would just say
"that
> sucks" -:)
>
> Gregg Wonderly
Well, we could name it Chastise, after the Dam Busters from WW2.
Chastise also means to scold severely, which is what one would
do to
someone who didn't honour the Jini Discovery and Join Protocol.
Cheers,
Peter.
Re: [vote] Re: New name for Jini TCK?
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Sun, Jan 30, 2011 at 10:32 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
> River Compatibility Kit or RiCK
Good.
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java
I live here; http://tinyurl.com/3xugrbk
I work here; http://tinyurl.com/24svnvk
I relax here; http://tinyurl.com/2cgsug
Re: [vote] Re: New name for Jini TCK?
Posted by Mike McGrady <mm...@topiatechnology.com>.
My preference would be that the committers develop a naming philosophy and that the philosophy would: (1) ban cute or geeky names, (2) give names semantically associated, in English, with function, (3) give a procedure for naming.
Just a thought. People unfairly or otherwise have their code value judged in their naming; "HI" for "hidden information", I think, will be okay, but "Diary" would color the code by casting doubt on the maturity of the coders. I didn't say it was fair or just.
Sent from my iPhone
Michael McGrady
Principal investigator AF081_028 SBIR
Chief Architect
Topia Technology, Inc
Work 1.253.572.9712
Cel 1.253.720.3365
On Jan 30, 2011, at 1:27 AM, Dan Creswell <da...@gmail.com> wrote:
> I think the name we choose is probably related to the other discussion about
> how we handle specifications....At least part of the kit's responsibility is
> to ensure compatibility with the specs IMHO.
>
> On that basis I'd be calling it Jini Compatibility Kit but, well, it's only
> a name and so long as it's clear what the kit itself is for/does it don't
> matter soooo much.
>
>
> On 30 January 2011 02:32, Peter Firmstone <ji...@zeus.net.au> wrote:
>
>> We had a number of suggestions for the Jini TCK subproject, thanks to all
>> who put forward suggestions and participated:
>>
>> * Jini Compatibility Kit
>> * Chastise
>> *
>>
>> River Compatibility Kit or RiCK
>>
>> * Torturer
>> * River Delta
>> * River TCK
>>
>> I propose that we assign the project name:
>>
>> "Rick" - River's Compatibility Kit.
>>
>> and describe it as:
>>
>> A test kit to ensure compatibility and compliance of services, proxy's and
>> clients with the Jini TM specifications:
>>
>> Jini TM lookup service specification v1.1
>> Jini TM discovery and join specification v3.0
>>
>> Regards,
>>
>> Peter.
>>
>>
>>
>>
Re: [vote] Re: New name for Jini TCK?
Posted by Dan Creswell <da...@gmail.com>.
Mmm, so back in the day we had the Jini Technical Oversight Committee -
couple of houses, one commercial, one non (I've got a feeling there was a
third house, general). I don't recall it formally anointing standards and
such but it could have done. It's a variation on the JCP ultimately which I
know is broken by virtue of abuse of an all powerful owning interest. No
need for it to be broken in our case if we allow the entire community to
decide who's on-board.
I could see a TOC like thing working reasonably well - expert developers and
expert users, working to develop specs which can then be turned into an
implementation (or indeed prototyped along the way). There is of course only
one implementation right now...
That ultimately may be what we get down to - do we entertain the idea there
may be another implementation in the future? I suspect probably not a whole
Kit but maybe individual services. If there are individual service
implementers (oh, like me, say) then specs and some kind of TOC to look
after them and protect the interests of "core" developers, independent
service implementers and users, might be a way to go.
There might well be some work to do on cleaning up specs and such to account
for com.sun.* or at least the current River implementation....
Two cents,
Dan.
On 30 January 2011 10:02, Peter Firmstone <ji...@zeus.net.au> wrote:
> Ok, why not, that's a reasonable suggestion, have you got any thoughts on
> how we might manage the Jini Standards Process?
>
> Cheers,
>
> Peter.
>
>
> Dan Creswell wrote:
>
>> I think the name we choose is probably related to the other discussion
>> about
>> how we handle specifications....At least part of the kit's responsibility
>> is
>> to ensure compatibility with the specs IMHO.
>>
>> On that basis I'd be calling it Jini Compatibility Kit but, well, it's
>> only
>> a name and so long as it's clear what the kit itself is for/does it don't
>> matter soooo much.
>>
>>
>> On 30 January 2011 02:32, Peter Firmstone <ji...@zeus.net.au> wrote:
>>
>>
>>
>>> We had a number of suggestions for the Jini TCK subproject, thanks to all
>>> who put forward suggestions and participated:
>>>
>>> * Jini Compatibility Kit
>>> * Chastise
>>> *
>>>
>>> River Compatibility Kit or RiCK
>>>
>>> * Torturer
>>> * River Delta
>>> * River TCK
>>>
>>> I propose that we assign the project name:
>>>
>>> "Rick" - River's Compatibility Kit.
>>>
>>> and describe it as:
>>>
>>> A test kit to ensure compatibility and compliance of services, proxy's
>>> and
>>> clients with the Jini TM specifications:
>>>
>>> Jini TM lookup service specification v1.1
>>> Jini TM discovery and join specification v3.0
>>>
>>> Regards,
>>>
>>> Peter.
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
Re: [vote] Re: New name for Jini TCK?
Posted by Peter Firmstone <ji...@zeus.net.au>.
Ok, why not, that's a reasonable suggestion, have you got any thoughts
on how we might manage the Jini Standards Process?
Cheers,
Peter.
Dan Creswell wrote:
> I think the name we choose is probably related to the other discussion about
> how we handle specifications....At least part of the kit's responsibility is
> to ensure compatibility with the specs IMHO.
>
> On that basis I'd be calling it Jini Compatibility Kit but, well, it's only
> a name and so long as it's clear what the kit itself is for/does it don't
> matter soooo much.
>
>
> On 30 January 2011 02:32, Peter Firmstone <ji...@zeus.net.au> wrote:
>
>
>> We had a number of suggestions for the Jini TCK subproject, thanks to all
>> who put forward suggestions and participated:
>>
>> * Jini Compatibility Kit
>> * Chastise
>> *
>>
>> River Compatibility Kit or RiCK
>>
>> * Torturer
>> * River Delta
>> * River TCK
>>
>> I propose that we assign the project name:
>>
>> "Rick" - River's Compatibility Kit.
>>
>> and describe it as:
>>
>> A test kit to ensure compatibility and compliance of services, proxy's and
>> clients with the Jini TM specifications:
>>
>> Jini TM lookup service specification v1.1
>> Jini TM discovery and join specification v3.0
>>
>> Regards,
>>
>> Peter.
>>
>>
>>
>>
>>
>
>
Re: [vote] Re: New name for Jini TCK?
Posted by Dan Creswell <da...@gmail.com>.
I think the name we choose is probably related to the other discussion about
how we handle specifications....At least part of the kit's responsibility is
to ensure compatibility with the specs IMHO.
On that basis I'd be calling it Jini Compatibility Kit but, well, it's only
a name and so long as it's clear what the kit itself is for/does it don't
matter soooo much.
On 30 January 2011 02:32, Peter Firmstone <ji...@zeus.net.au> wrote:
> We had a number of suggestions for the Jini TCK subproject, thanks to all
> who put forward suggestions and participated:
>
> * Jini Compatibility Kit
> * Chastise
> *
>
> River Compatibility Kit or RiCK
>
> * Torturer
> * River Delta
> * River TCK
>
> I propose that we assign the project name:
>
> "Rick" - River's Compatibility Kit.
>
> and describe it as:
>
> A test kit to ensure compatibility and compliance of services, proxy's and
> clients with the Jini TM specifications:
>
> Jini TM lookup service specification v1.1
> Jini TM discovery and join specification v3.0
>
> Regards,
>
> Peter.
>
>
>
>
Re: [vote] Re: New name for Jini TCK?
Posted by Benson Margulies <bi...@gmail.com>.
It seems to me that avoiding the term TCK is a good thing at this
point, so I like your suggestions.
On Sat, Jan 29, 2011 at 9:32 PM, Peter Firmstone <ji...@zeus.net.au> wrote:
> We had a number of suggestions for the Jini TCK subproject, thanks to all
> who put forward suggestions and participated:
>
> * Jini Compatibility Kit
> * Chastise
> *
>
> River Compatibility Kit or RiCK
>
> * Torturer
> * River Delta
> * River TCK
>
> I propose that we assign the project name:
>
> "Rick" - River's Compatibility Kit.
>
> and describe it as:
>
> A test kit to ensure compatibility and compliance of services, proxy's and
> clients with the Jini TM specifications:
>
> Jini TM lookup service specification v1.1
> Jini TM discovery and join specification v3.0
>
> Regards,
>
> Peter.
>
>
>
>
[vote] Re: New name for Jini TCK?
Posted by Peter Firmstone <ji...@zeus.net.au>.
We had a number of suggestions for the Jini TCK subproject, thanks to
all who put forward suggestions and participated:
* Jini Compatibility Kit
* Chastise
*
River Compatibility Kit or RiCK
* Torturer
* River Delta
* River TCK
I propose that we assign the project name:
"Rick" - River's Compatibility Kit.
and describe it as:
A test kit to ensure compatibility and compliance of services, proxy's
and clients with the Jini TM specifications:
Jini TM lookup service specification v1.1
Jini TM discovery and join specification v3.0
Regards,
Peter.
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code
Provenance
Posted by James Grahn <jg...@simulexinc.com>.
Alternatively, we might consider something along the theme of "River
Delta" where a river meets the ocean.
Before a River opens to the wider world, it goes through the Delta.
Also, the test results represent a kind of a "delta" between what an
implementation is and what it needs to be.
I would have also suggested "confluence", where one river meets another,
but that's already taken. I suppose there might be confusion over
"delta" as well, but I think it's more manageable because it's not an
actual product name.
Just another suggestion for where things could go, to make up for my
previous contribution. :-)
jamesG
On 11/22/2010 10:52 AM, Gregg Wonderly wrote:
> Just to clarify what I was trying to suggest... With the name River,
> compatibility gates would be like Dams, stopping incompatibility from
> getting through. If there is a Dam name, fun and clever to use, that
> would be cool. If there are other names which are great, than that's
> cool too.
>
> Just trying to keep things "fun"!
>
> Gregg Wonderly
>
> On 11/18/2010 10:40 AM, James Grahn wrote:
>> Totality Of River Testing for Undoubted Rigorous Establishment of
>> Riverness
>>
>> TORTURER
>>
>> "Does my River implementation pass muster?"
>> "We'll let you know as soon as we run it through the TORTURER."
>>
>> jamesG
>>
>> On 11/18/2010 10:46 AM, Benson Margulies wrote:
>>> Truly Open River Conformance Test Unlike Oracles Java TCK
>>>
>>> TORCTUOJ
>>>
>>>
>>>
>>>
>>> On Thu, Nov 18, 2010 at 10:36 AM, Dennis
>>> Reedy<de...@gmail.com> wrote:
>>>>>>>
>>>>>>> Can anyone think of name for the Jini TCK?
>>>>>>
>>>>>> I'd suggest the name of a river Dam somewhere in the world. Any
>>>>>> suggestions of fun and non-controversial names? For example,
>>>>>> Hoover, is probably not good because eventually people would just
>>>>>> say "that sucks" -:)
>>>>>>
>>>>>> Gregg Wonderly
>>>>>>
>>>>>
>>>>>
>>>>> Well, we could name it Chastise, after the Dam Busters from WW2.
>>>>> Chastise also means to scold severely, which is what one would do
>>>>> to someone who didn't honour the Jini Discovery and Join Protocol.
>>>>
>>>> River Compatibility Kit or RiCK?
>>>>
>>>>
>>>
>>
>
>
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code
Provenance
Posted by Gregg Wonderly <gr...@gmail.com>.
Just to clarify what I was trying to suggest... With the name River,
compatibility gates would be like Dams, stopping incompatibility from getting
through. If there is a Dam name, fun and clever to use, that would be cool. If
there are other names which are great, than that's cool too.
Just trying to keep things "fun"!
Gregg Wonderly
On 11/18/2010 10:40 AM, James Grahn wrote:
> Totality Of River Testing for Undoubted Rigorous Establishment of Riverness
>
> TORTURER
>
> "Does my River implementation pass muster?"
> "We'll let you know as soon as we run it through the TORTURER."
>
> jamesG
>
> On 11/18/2010 10:46 AM, Benson Margulies wrote:
>> Truly Open River Conformance Test Unlike Oracles Java TCK
>>
>> TORCTUOJ
>>
>>
>>
>>
>> On Thu, Nov 18, 2010 at 10:36 AM, Dennis Reedy<de...@gmail.com> wrote:
>>>>>>
>>>>>> Can anyone think of name for the Jini TCK?
>>>>>
>>>>> I'd suggest the name of a river Dam somewhere in the world. Any
>>>>> suggestions of fun and non-controversial names? For example, Hoover, is
>>>>> probably not good because eventually people would just say "that sucks" -:)
>>>>>
>>>>> Gregg Wonderly
>>>>>
>>>>
>>>>
>>>> Well, we could name it Chastise, after the Dam Busters from WW2. Chastise
>>>> also means to scold severely, which is what one would do to someone who
>>>> didn't honour the Jini Discovery and Join Protocol.
>>>
>>> River Compatibility Kit or RiCK?
>>>
>>>
>>
>
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code
Provenance
Posted by Zsolt Kúti <ku...@prolan.hu>.
Thu, 18 Nov 2010 11:40:04 -0500 -n
James Grahn <jg...@simulexinc.com> írta:
> Totality Of River Testing for Undoubted Rigorous Establishment of
> Riverness
>
> TORTURER
>
> "Does my River implementation pass muster?"
> "We'll let you know as soon as we run it through the TORTURER."
:-)
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code
Provenance
Posted by James Grahn <jg...@simulexinc.com>.
Totality Of River Testing for Undoubted Rigorous Establishment of Riverness
TORTURER
"Does my River implementation pass muster?"
"We'll let you know as soon as we run it through the TORTURER."
jamesG
On 11/18/2010 10:46 AM, Benson Margulies wrote:
> Truly Open River Conformance Test Unlike Oracles Java TCK
>
> TORCTUOJ
>
>
>
>
> On Thu, Nov 18, 2010 at 10:36 AM, Dennis Reedy<de...@gmail.com> wrote:
>>>>>
>>>>> Can anyone think of name for the Jini TCK?
>>>>
>>>> I'd suggest the name of a river Dam somewhere in the world. Any suggestions of fun and non-controversial names? For example, Hoover, is probably not good because eventually people would just say "that sucks" -:)
>>>>
>>>> Gregg Wonderly
>>>>
>>>
>>>
>>> Well, we could name it Chastise, after the Dam Busters from WW2. Chastise also means to scold severely, which is what one would do to someone who didn't honour the Jini Discovery and Join Protocol.
>>
>> River Compatibility Kit or RiCK?
>>
>>
>
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code Provenance
Posted by Benson Margulies <bi...@gmail.com>.
Truly Open River Conformance Test Unlike Oracles Java TCK
TORCTUOJ
On Thu, Nov 18, 2010 at 10:36 AM, Dennis Reedy <de...@gmail.com> wrote:
>>>>
>>>> Can anyone think of name for the Jini TCK?
>>>
>>> I'd suggest the name of a river Dam somewhere in the world. Any suggestions of fun and non-controversial names? For example, Hoover, is probably not good because eventually people would just say "that sucks" -:)
>>>
>>> Gregg Wonderly
>>>
>>
>>
>> Well, we could name it Chastise, after the Dam Busters from WW2. Chastise also means to scold severely, which is what one would do to someone who didn't honour the Jini Discovery and Join Protocol.
>
> River Compatibility Kit or RiCK?
>
>
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code
Provenance
Posted by Sim IJskes - QCG <si...@qcg.nl>.
On 18-11-10 16:36, Dennis Reedy wrote:
> River Compatibility Kit or RiCK?
+1
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code Provenance
Posted by Dennis Reedy <de...@gmail.com>.
>>>
>>> Can anyone think of name for the Jini TCK?
>>
>> I'd suggest the name of a river Dam somewhere in the world. Any suggestions of fun and non-controversial names? For example, Hoover, is probably not good because eventually people would just say "that sucks" -:)
>>
>> Gregg Wonderly
>>
>
>
> Well, we could name it Chastise, after the Dam Busters from WW2. Chastise also means to scold severely, which is what one would do to someone who didn't honour the Jini Discovery and Join Protocol.
River Compatibility Kit or RiCK?
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code
Provenance
Posted by Jim Hurley <ji...@me.com>.
+1 Chastise
That's great, Peter.
-Jim
On Nov 18, 2010, at 03:37 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
:
> Gregg Wonderly wrote:
> >
> > I'd suggest the name of a river Dam somewhere in the world. Any
> > suggestions of fun and non-controversial names? For example, Hoover,
> > is probably not good because eventually people would just say "that
> > sucks" -:)
> >
> > Gregg Wonderly
>
> Well, we could name it Chastise, after the Dam Busters from WW2.
> Chastise also means to scold severely, which is what one would do to
> someone who didn't honour the Jini Discovery and Join Protocol.
>
> Cheers,
>
> Peter.
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code
Provenance
Posted by Peter Firmstone <ji...@zeus.net.au>.
Gregg Wonderly wrote:
> On 11/16/2010 6:58 AM, Peter Firmstone wrote:
>> Nigel Daley wrote:
>>> On Oct 13, 2010, at 3:42 PM, Peter Firmstone wrote:
>>>
>>>> River is an Implementation of the Jini Spec.
>>>>
>>>> There is a Patent covenant, see River-339
>>>>
>>>> Sun is re-licensing its Jini technology Standard specifications under
>>>> ALv2 and providing a separate "Jini Community Standards Patent
>>>> Non-Assertion Covenant ("Covenant") that enables others to create
>>>> unrestricted independent implementations of the specifications.
>>>>
>>>>
>>>> There is a significant amount of remaining code, relevant to Apache
>>>> River,
>>>> which we may not be able to use as subprojects due to code provenance.
>>>>
>>>> I've closed River-338, which was for creating a subproject of the
>>>> existing
>>>> implementation of Jini Surrogate, since I haven't been able to
>>>> satisfy code
>>>> provenance rules. We can consider a clean room implementation for Jini
>>>> Surrogate.
>>>>
>>>> Nigel Daley has confirmed that he is the primary author of the Jini
>>>> TCK,
>>>> River-32. Since Sun Microsystems licensed this code under AL2 and have
>>>> provided a Patent Covenant and Nigel is an Emeritus Committer of
>>>> Apache
>>>> River, is this sufficient provenance to make a Subproject proposal
>>>> for the
>>>> Discovery Lookup and Join Test Kit?
>>>>
>>>> If this is the case, I was also wondering if Nigel would like to
>>>> propose a
>>>> name for the TCK Project?
>>>
>>> Not much of a namer (just look at it's current name :p ). I happily
>>> defer to
>>> the active community :-)
>>>
>>> Cheers,
>>> Nige
>>>
>>>
>>
>> Can anyone think of name for the Jini TCK?
>
> I'd suggest the name of a river Dam somewhere in the world. Any
> suggestions of fun and non-controversial names? For example, Hoover,
> is probably not good because eventually people would just say "that
> sucks" -:)
>
> Gregg Wonderly
>
Well, we could name it Chastise, after the Dam Busters from WW2.
Chastise also means to scold severely, which is what one would do to
someone who didn't honour the Jini Discovery and Join Protocol.
Cheers,
Peter.
Re: New name for Jini TCK? Was: Re: River-32 Clarification of Code
Provenance
Posted by Gregg Wonderly <gr...@wonderly.org>.
On 11/16/2010 6:58 AM, Peter Firmstone wrote:
> Nigel Daley wrote:
>> On Oct 13, 2010, at 3:42 PM, Peter Firmstone wrote:
>>
>>> River is an Implementation of the Jini Spec.
>>>
>>> There is a Patent covenant, see River-339
>>>
>>> Sun is re-licensing its Jini technology Standard specifications under
>>> ALv2 and providing a separate "Jini Community Standards Patent
>>> Non-Assertion Covenant ("Covenant") that enables others to create
>>> unrestricted independent implementations of the specifications.
>>>
>>>
>>> There is a significant amount of remaining code, relevant to Apache River,
>>> which we may not be able to use as subprojects due to code provenance.
>>>
>>> I've closed River-338, which was for creating a subproject of the existing
>>> implementation of Jini Surrogate, since I haven't been able to satisfy code
>>> provenance rules. We can consider a clean room implementation for Jini
>>> Surrogate.
>>>
>>> Nigel Daley has confirmed that he is the primary author of the Jini TCK,
>>> River-32. Since Sun Microsystems licensed this code under AL2 and have
>>> provided a Patent Covenant and Nigel is an Emeritus Committer of Apache
>>> River, is this sufficient provenance to make a Subproject proposal for the
>>> Discovery Lookup and Join Test Kit?
>>>
>>> If this is the case, I was also wondering if Nigel would like to propose a
>>> name for the TCK Project?
>>
>> Not much of a namer (just look at it's current name :p ). I happily defer to
>> the active community :-)
>>
>> Cheers,
>> Nige
>>
>>
>
> Can anyone think of name for the Jini TCK?
I'd suggest the name of a river Dam somewhere in the world. Any suggestions of
fun and non-controversial names? For example, Hoover, is probably not good
because eventually people would just say "that sucks" -:)
Gregg Wonderly