[Mono-list] Introduction

[Jonathan Pryor]

I have the standard boiler-plate answer ready for you (below), but it
summarizes to: fix bugs, write new code, writes tests, and help other
developers (documentation, HOWTOs).

These may be appropriate for a MS project.  I can't answer that, as I
don't know what requirements you need to fulfill.

On the more "interesting" side of things, you could also look into
Gnome/Bonobo+Mono interop, possibly using Remoting.Corba; see:

	http://remoting-corba.sourceforge.net/

I have no idea how easy that would be; all I do know is that someone was
looking into it on IRC last night, and they were unable to get it
working.  This (in my mind) would likely qualify for a MS project.

On with the standard answer...

  - 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.

    If you contribute to the class libraries, you should join
    mono-devel-list:

        http://lists.ximian.com/mailman/listinfo/mono-devel-list

    See also:

        http://www.go-mono.com/contributing.html

    Personally, I know that the EventLog and PerformanceCounter classes
    in the System.Diagnostics namespace (System.dll) could use some
    loving...and a good portable solution. :-)

    Or, you might be interested in re-implementing System.Xml in C#,
    for portability, fewer dependencies, and the elimination of
    temporary files.  Though, this *has* been estimated as being 9+
    months of work...  :-)

    You could also try asking on IRC for further examples.

  - 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

  - 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.

    If you contribute to Documentation, you should join mono-docs-list:

        http://lists.ximian.com/mailman/listinfo/mono-docs-list


  - 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.  NUnit2 is used for test cases.

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

Hope this helps.

 - Jon

On Fri, 2003-06-27 at 13:39, Sumit Shrotriya wrote:
> Hi All,
>   I am Sumit, a graduate CS student at RIT. I am really interested in
> the Mono project and was wondering if and how I could contribute to it.
> I have to complete my Masters Project as a part of my curriculum and I
> though it would be great if I could help create some part of Mono.
> 
>   Now I am really looking for Ideas...if you guys could suggest
> something that you would really like to see in mono, please do drop me a
> line.
> 
> Thanks a Ton,
> Sumit
> 
> 
> _______________________________________________
> Mono-list maillist  -  Mono-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list