On Fri, 22 Mar 2002 06:47, Ceki Gülcü wrote:
> All very good points. The question on my mind is whether these
> problems can be corrected in the future by opening up the (JCP) Java
> Community Process or whether the closed-like-a-clamp is a symptom
> of a more serious and profound disease - my suggested name would
> be "clampitis."
Actually I don't think that this is a huge problem in most JSRs. Theres is
basically thrre types of information shared on a JSR.
1. Information to share between EG members (most restrictive)
2. Information to share between EG members and EG members host organization
(ie sun employees can talk to Sun EG member)
3. Information that can be shared with public
Due to the structure of most JSRs (3) is not actually made available to the
public and I would like that to change but I am not sure it would be good for
java to remove (1) and (2).
Why are they needed? Well some companys wont take part in the discussions
unless there (2). For instance I would hate to see Sony not adopt java in its
next playstation due to this - and I think they would not have joined JSR134
if they had to openly reveal "proprietary" IP.
It is also useful for some people who publish papers for a living (ie
academics and researchers at big companys) as they usually can not freely
distribute papers until given the thumbs up by publishers. However as an EG
member I would prefer to see a relevent paper earlier than sooner.
However there are JSRs that have no good reason to carry much information in
(1) and (2) categories and thus should be opened up.
--
Cheers,
Pete
-----------------------------------------------------------
If your life passes before your eyes when you die,
does that include the part where your life passes before
your eyes?
-----------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
