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 <[email protected]> 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.
