Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of
 coachjeremyeastonmarks@gmail.com designates 209.85.221.178 as permitted
 sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=JxSE4WJ3F5/JS+FZAbcMk/6ZVww/GnDDs5NX+ncKmjBkG3dd9wIjkLK10VUhKtYTUs
         gX0XtIjsdz0EebNxdCK6RljL8sCTe21Muuu3vB95uzaylPyRzmqEkjuWeUZbp8szgh/h
         YHaOBPQqcku8TWq9NBfcGflAvFR/0Wg6FFb5o=
MIME-Version: 1.0
In-Reply-To: <4A44A1A1.4040201@zeus.net.au>
References: <F5DF5420-6DCA-4873-A8E4-8E9F501D5CB3@mac.com>
	 <EA921506-4ACE-43E4-8245-AECE0757C13E@innis.ca>
	 <e202160f0906251006i55c3f937t9b46395a29994246@mail.gmail.com>
	 <e736790906251142h9d260d7ob1667d7817ec8107@mail.gmail.com>
	 <1245985113.10349.197.camel@cameron> <4A44A1A1.4040201@zeus.net.au>
Date: Fri, 26 Jun 2009 06:24:43 -0500
Message-ID: <b23c74270906260424h66f3de43n782e72fa3b52c95a@mail.gmail.com>
Subject: Re: Jini.org
From: Jeremy Easton-Marks <coachjeremyeastonmarks@gmail.com>
To: river-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0015175cba5e495482046d3e96d0

--0015175cba5e495482046d3e96d0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I will gladly contribute to the JINI  paypal account.

Excuse my ignorance in any of these questions but.....
1) Where does the money go and who is in charge of it?
2) Is the Jini/River group setup to handle donations(i.e. incorporated as a
non-profit)?
3) Do we have to keep calling it River?

I agree with Peter completely. While most of the us in this group are
familiar with Jini and how to participate in it, it is hard to just jump in=
.
I would like to recommend a couple of things.
1) Easier tutorial on using JINI(Examples)
2) Better documentation
3) Mentorship program. All employees, and volunteers are temporary and
unless the information is passed on then it leaves when they do.

#1 and #2 are the biggest for me, since it is been one of the reasons I hav=
e
not been using Jini, and participating in the group.

Jeremy R. Easton-Marks

Senior Software Engineer
click2try.com

"=C3=AAtre fort pour =C3=AAtre utile"


On Fri, Jun 26, 2009 at 5:23 AM, Peter Firmstone <jini@zeus.net.au> wrote:

> I'll contribute too, let's get that Paypal account going, what a good ide=
a
> ;)
>
> I've recently spent some time going over some of the content on jini.orga=
nd feel strongly that key information there will assist us with River's
> future, both technical and philosophical.
>
> I've listened to the speeches in JCM more than once and still find the
> information relevant.
>
> There is too much opportunity and potential left for us with River to let
> it die, if anything I think that the shortcomings of Java have held us ba=
ck
> to some degree, namely classpath, jar, the complexity of security and the
> challenges of the internet.  It'll be interesting to watch how the OSGi a=
nd
> project Jigsaw evolve and see if there's potential to use relevant pieces=
.
>
> I've been thinking that rather than transferring whole jar files via
> classfile servers, versioned classes, individually compressed on demand
> (using caching with deflate compression and nio byte buffers) to speed up
> code transfer over slow networks (provided your not using whole package
> imports) and provide greater flexibility if required.  Furthermore,
> individual classes can evolve and exist alongside legacy copies, if they =
can
> be versioned.  There are other issues in doing so, however, such as, when=
 to
> evolve a class with a new version, much like the versioning issues with
> serialization.  That would of course require OpenJDK7.
>
> But first we must make it easier to participate, I think that the current
> focus on changes to the build and testing structures will help us grow, w=
e
> must continue to do so while preserving the past in order not to forget
> important lessons or repeat old mistakes in the future.
>
> N.B. Thank you very much Jim Waldo, for going to the trouble of retrievin=
g,
> getting approval for and uploading very relevant documentation.  And for
> inspiration...
>
> Cheers,
>
> Peter.
>
>
>
>
> Greg Trasuk wrote:
>
>> On Thu, 2009-06-25 at 14:42, Sam Chance wrote:
>>
>>
>>> Wow! This whole topic is scary. I know factually Jini is still
>>> relevant in certain places. I don't want it to die, personally.
>>>
>>> Is there an easy way for individuals (like me) to acquire the content
>>> on jini.org?
>>>
>>> Can we set up a fund or account using Paypal? This would allow us to
>>> individually contribute, as long as a trusted agent disperses funds to
>>> pay the bills.
>>>
>>> Also, can we change the wiki model to a controlled access site? Casual
>>> visitors get read-only rights. Others may apply for write-enabled
>>> accounts.
>>>
>>> I am willing to pay the bills as the trusted agent, if the group is
>>> willing to allow me.
>>>
>>> Just don't let it die.
>>>
>>> Sam
>>>
>>>
>>>
>>
>> I agree.  Don't let it die, and I've always thought that Jini should
>> have an identity apart from River.  I very much like the idea of a
>> Paypal donation page.  Does anyone know how to do that?  If there were
>> sufficient funds donated, it would be great to setup some sort of entity
>> to hold the Jini trademarks and own the domain.
>>
>> Cheers,
>>
>> Greg.
>>
>>
>>
>>> On 6/25/09, Jeff Ramsdale <jeff.ramsdale@gmail.com> wrote:
>>>
>>>
>>>> jini.org is currently hosted at Dreamhost and is run on Mediawiki.
>>>> I'm open to whatever the community decides. It's been frustrating
>>>> combating
>>>> the spammers while trying to keep jini.org as open as possible (per
>>>> wiki
>>>> culture). I'd be more defensive of keeping the site if the community h=
ad
>>>> taken greater ownership of it, but a lot of the content is stuff I
>>>> copied
>>>> from the previous site (like the Jini specs and all the content from
>>>> Jini
>>>> Community Meetings). I'd really hate to lose the JCM stuff, in
>>>> particular.
>>>>
>>>> -jeff
>>>>
>>>> On Thu, Jun 25, 2009 at 8:23 AM, Rick Innis <rick@innis.ca> wrote:
>>>>
>>>>
>>>>
>>>>> This is just a heads up that we have to decide if we want to
>>>>>
>>>>>
>>>>>> keep Jini.org around.  The site has been around since the
>>>>>> inception of the Jini Community in 1999, and has gone through
>>>>>> a number of transformations over the years.  It's current state
>>>>>> is that it is wiki-based and hosted by Dreamhost.
>>>>>>
>>>>>>
>>>>>>
>>>>> I use Dreamhost for my own hosting, and I'd be happy to add the
>>>>> jini.orgsite to that.
>>>>>
>>>>>  We have an outstanding bill for $239.40 that is due by July 8th to
>>>>> keep
>>>>>
>>>>>
>>>>>> the site going.
>>>>>>
>>>>>>
>>>>>>
>>>>> I' also happy to chip in towards this.
>>>>>
>>>>>  We can either:
>>>>>
>>>>>
>>>>>> - try to consolidate and move the content to Apache River,
>>>>>> - figure out how to fund the Jini.org site, or
>>>>>> - just let the site (and content) expire.
>>>>>>
>>>>>>
>>>>>>
>>>>> I agree with Patrick that the domain name should be kept up. I think
>>>>> migrating the useful content to the Apache River project is probably =
a
>>>>> good
>>>>> idea, and eventually redirecting jini.org there - it makes it clear
>>>>> that
>>>>> there's one source for the project.
>>>>>
>>>>> R.
>>>>>
>>>>>
>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
>>>>> To unsubscribe, send email to listserv@java.sun.com and include in th=
e
>>>>> body
>>>>> of the message "signoff JAVASPACES-USERS".  For general help, send
>>>>> email
>>>>> to
>>>>> listserv@java.sun.com and include in the body of the message "help".
>>>>>
>>>>> To view past JAVASPACES-USERS postings, please see:
>>>>> http://archives.java.sun.com/archives/javaspaces-users.html
>>>>>
>>>>>
>>>>>
>>>> --
>>> Sent from my mobile device
>>>
>>> Sam Chance
>>> 443-694-5293 (m)
>>> 410-694-0240 x108 (o)
>>>
>>>
>>
>

--0015175cba5e495482046d3e96d0--