[Top][All Lists]

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

What are tainted developers allowed to work on?

From: Robert Schuster
Subject: What are tainted developers allowed to work on?
Date: Wed, 05 Jan 2005 09:38:53 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.7.5) Gecko/20050105


James Damour telled us some months ago that he had studied certain sources
of the Sun JDK and is therefore considered a tainted developer which
cannot contribute code to GNU Classpath.

Nevertheless he is eager to help making Free Java a reality.

The problem is that we do not have a definite answer on what people like James
may contribute (or at least this answer is not written down). The GNU Classpath 
FAQ says:

3.2 Can I look as Sun's sources to get inspiration?
No. In fact, if you read Sun's sources we can't accept any code from you.
It was said however that there are other parts on which tainted developers may 
- Mauve test cases
- Example programs for Classpath
- Documentation fixes (on java[x]. or gnu. classes?)
- Helper programs (e.g. japitools) and scripts

Other things where we should find a resolution are:
- May tainted developers contribute ideas on design decisions (on 
- May tainted devs fix simple bugs (e.g forgotten imports that causes classpath 
compilation to fail or misspelled method names)

If we cannot find a solution on at least one of those points because of legal 
uncertainity whom do we have to ask then (FSF legal?)
and who is doing the communication?



Recent post by James Damour:

James asking to clarify situation on Javadoc commits in June 2004:

Mark's reply to James where he presents possible activities in the last 

reply via email to

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