Contributing to Mauve is fairly easy -- we're pretty generous with cvs write access, and we don't require copyright assignments or anything like that. We do ask that you not have read Sun's source; we are a cleanroom test suite and we're concerned about contamination. And, we ask that you follow the general rules.

Luckily these rules are pretty easy to follow:

• Write a ChangeLog entry for each change.
• Follow the existing (GNU-ish) coding style.
• Make sure your tests compile and are as correct as possible before checking them in. We realize that sometimes the JDK has errors and can't always be used as a guide; in these situations make sure the test itself is documented to explain why it is the way it is.
• New tests and fixes can go in immediately; changes to the test harness or the build system should be discussed first.

Questions? Send them to mauve-discuss@sourceware.org!