Resent-Date: Tue, 12 Dec 1995 15:37:35 -0500
Date: Tue, 12 Dec 1995 14:29:22 -0500
Message-Id: <199512121929.OAA06105@bedroom.cabi.net>
From: Karl Asha <karl@ncm.com>
To: Tim Bass <bass@dune.silkroad.com>
Cc: java-linux@java.blackdown.org
Subject: Reasoning for Creation of Second List
In-Reply-To: <199512102359.SAA03347@dune.silkroad.com>
References: <199512102359.SAA03347@dune.silkroad.com>
Resent-Message-Id: <"ZwEsS1.0.Vn.XTUpm"@liquor>
Resent-From: java-linux@java.blackdown.org
Precedence: list
Resent-Sender: java-linux-request@java.blackdown.org

Tim Bass writes:
 > 
 > Hello Everyone.
 > 
 > I would like to take this opportunity to explain why I created another
 > linux-java list in addition to java-linux.   Your kind attention is
 > appreciated.

In order for people to become confused between the similar names of
both lists? ;-)
 
 > First, but least important, I created linux-java when, for whatever
 > reason, I could not get a response from java-linux for a few days,
 > and on a few occasions when I tried to ping the server or do a trace
 > route, I found the destination unreachable.   Since then, I found
 > out that java-linux was not a majordomo site (I had assumed it was)
 > and subscribed (thanks Randy).   Why the occasional routing loop 
 > to the server, I can't tell you, but it happens to the best of us.

Yes, it's smartlist, most sources have reflected that now. Oh, and we
changed from oar.net to alternet, hence the downtime. Wee.
 
 > Second, and more important (at least to me) is the fact that Sun
 > Microsystems states directly that *anyone* who is a party to the
 > Java Licensing agreement with Sun can share the Java porting code
 > between themselves, directly.  In case this is not clear
 > to everyone, this simply means that
 > as long as we abide by the terms of the agreement and have signed
 > it, we can share the ported source for research and other non-
 > commercial uses.

Still waiting for the reason for another list ;-)
 
 > I have had little success (again, maybe I did not ask the question
 > properly) getting the current linux port source for research purposes
 > here in my lab (we have a source agreement in place with Sun). This
 > concerned me, at the time, because it appeared that one orgainization
 > was holding the linux port 'close to their chest' and if this is the
 > case, then we need to begin working on another, more open port.
 > (my posts and e-mails just, for what every reason, never were 
 >  anwered, and I'm not placing blame, I just am concerned, that's all)

Close to our chests? Port has been at ftp://java.blackdown.org since
the start, and openly available to all. 
 
 > If this is not the case, and my perception of the current situation
 > is incorrect, then the second list may not necessary.  But,
 > on the other hand, if the the current linux port of java is *not*
 > going to be shared with other linux developers that have signed
 > an agreement with Sun as well, then I think it wise, for the benefit
 > of the linux community as a whole, to encourage another, more open,
 > porting effort.
 > 
 > That's about it , everyone.  The Rational.

s/Rationale/Misunderstanding/;
 
 > If I'm mistaken about the linux-port and the direction of the port,
 > then I am happy to remove/change the second list.  I don't really take
 > pleasure in maintaining another service on my many servers and 
 > donating precious bandwidth without due cause.  But, on the other
 > hand, if the linux community would be better served by another
 > development track, then a second list is worth the trouble.

No problems with your list, lets just hope people don't get confused
between the two.
 
 > In my opinion, the overall interest of the linux community is more
 > important that the needs of a single individual or organization.
 > Maintaining lists are a lot of responsibility and whomever does
 > it takes on an extra burden.  But, we do need to share the source
 > code between individuals authorized to do so, it benefits the
 > entire community as a whole.
 > 
 > Best Regards,

This is a mighty speech from someone who was not entirely certain of
his perception of the situation ;-)
 
 > 
 > Tim
 > 
 > -- 

Cheers, 
Karl Asha
karl@ncm.com
NCM Networking Consultant/Programmer