On Tue, 2013-03-12 at 06:13, Dan Creswell wrote:
> "But I do think we ought to keep the domain reg."
>
> Shouldn't we talk the grand "River rename"? I mean we've said before
> now that we'd treat net.jini as an old compatibility namespace and
> define some new ones over time....
>
Hmmm... My impression has always been that we were going to keep the
"net.jini" namespace and just move away from "com.sun" (which we should
probably get on with). I'm not sure why I have that impression.
Nostalgia, perhaps, but I still feel like if everything is in
"org.apache.river", then it seems like a "project" (e.g. Struts) as
opposed to a "technology" (e.g. JSF).
I suppose part of it is that the Jini name at least has some name
recognition and a place in history ("Jini was doing SOA before anybody
called it SOA"), whereas to promote River seems like starting from
scratch ("so how do you compare to Hadoop, Camel, JBI, JSON, CORBA, RMI,
and a hundred other technologies).
> Just raising a topic, not prosecuting an agenda.
>
Cheers,
Greg.
> On 12 March 2013 01:39, Greg Trasuk <[email protected]> wrote:
> >
> > I'm confused - wasn't that domain transferred to the Apache Software
> > Foundation? And if so, shouldn't the foundation be renewing the domain
> > registration?
> >
> > If not, I suspect that we should maintain it simply because our package
> > name starts with "net.jini". Who currently owns it? I'll chip in to
> > renew the domain registration, although I'm in agreement that any
> > content hosting can stop. If it helps, I can host a placeholder page on
> > my server. But I do think we ought to keep the domain reg.
> >
> > Cheers,
> >
> > Greg.
> >
> > On Mon, 2013-03-11 at 17:52, Peter wrote:
> >> The jini.net domain name registration has come up for renewal again.
> >>
> >> I'm wondering if anyone wants to take over as custodian?
> >>
> >> Does anyone have any time or ideas to do something useful with jini.net?
> >>
> >> Peter.
> >
