classpath
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Sun tainting and Javadoc comments.


From: James Damour (Suvarov454)
Subject: Sun tainting and Javadoc comments.
Date: Sat, 26 Jun 2004 16:44:05 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5

As some of you may know, I suffer the painful stigma of having been tainted by reading the Sun Java source code. As such, I thought that my only way of contributing to FLOSS Java would be as an application developer (i.e. compile and run my Java apps under FLOSS VM's, and feed back bug reports). Twiun and Dalibor came up with another idea, however.

I may be able to fill in missing Javadoc comments in source files.

However, none of us are certain enough about the licensing involved with all of this, so we decided to check with the FSF, hence this missal to you august Classpath hackers. We'd like an official review of the issues to determine if a person who has been tainted can write Javadoc comments in source code. Does is matter how tainted the person is (i.e. I've read the contents of src.jar, but I've never agreed to the SCSL)? "No" is, of course, a perfectly acceptable answer; we just thought that we've come up with a clever way for us poor unclean pariahs to take a more active role in supporting FLOSS Java.

Thank you for your time.

James Damour
address@hidden





reply via email to

[Prev in Thread] Current Thread [Next in Thread]