Check out the mcs module from CVS. The class/ directory containes all the code for the mainline (i.e. corlib, System.XML, etc.). The directory also contains the nunit2 tests. You can run the tests, add tests as neccesary, and fix tests that fail.
The documentation system is in the monodoc module in CVS. You can update the core docs in the class/ directory in that module or you can put one of the non-core modules (like gtk-sharp) to document. The documentation is in ECMA XML docs format and there are plenty of examples. For documentation there's a seperate mono-docs-list on ximian.com
-fawad
John Meredith wrote:
I would like to contribute on a regular basis to the Mono project. I've read the documentation, written some console based apps with Mono and had a look around the source code. I've also been programming in a professional environment using C# .NET (MS-Windows) for about a year and I am excited by Mono and would love to get involved.
I would like to do some unit testing to start with or maybe some documentation, but I was wondering which sections / classes need testing.
Could anyone please point me in the right direction? Thanks John Meredith
_______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
