[Mono-list] Participation

[Jonathan Pryor]

The better question to ask is what would you like to do?

There are lots of things you can do:

  - Work on the class libraries.  See 
      http://www.go-mono.com/class-status.html
    The classes listed are the classes that need work, are incomplete,
    etc.  Find a namespace that interests you and start implementing.

  - Documentation.  Lots is needed.  It's in the monodoc CVS module.
    See also: http://www.go-mono.com/documentation.html
    However, you might want to wait on this until the documentation
    editor is complete.

  - HOWTOs.  These are in the monkeytalk CVS module, and can be seen at:
      http://www.go-mono.com/tutorial/html/en/index.html

  - Test Cases:  Either implement more, or fix the bugs that they are
    finding.  NUnit is used for test cases, but some are using NUnit,
    while others are using NUnit2, so I'm not sure what we should be 
    using for new test cases.

    However, I've heard that there are lots of mono bugs found by the
    current test cases, and these should be fixed.

  - Bug Fixes: See http://bugzilla.ximian.com, and look at the bugs for:
      gtk#
      Mono/Class Libraries
      Mono/Debugger
      Mono/Doctools
      Mono/mcs
      Mono/runtime

Hope this helps.
 - Jon

On Tue, 2003-01-28 at 09:00, Dushyant Bansal wrote:
> Hello,
> 
> I read about your project on SlashDot.  I can't commend you guys enough
> for making this effort.
> 
> I would like to contribute to the code.  I've never done any open source
> work before though.  Please tell me what I need to do to get involved.
> 
> Thanks,
> Dushyant
> 
> --------------------------------------------------------------------
> Dushyant Bansal
> MASc Candidate, Distributed and Mobile Systems,
> Computer Engineering,
> University of Waterloo,
> Canada
> 
> 
> _______________________________________________
> Mono-list maillist  -  Mono-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list