contributing 7.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190
  1. * Contributing to the Mono project
  2. There are many ways in which you can help in the Mono project:
  3. <ul>
  4. * <b>Programmers:</b> You can work on a free
  5. implementation of the <a
  6. href="class-library.html">class libraries</a>, the
  7. <a href="runtime.html">runtime engine</a>, <a
  8. href="tools.html">the tools</a>, the <a
  9. href="testing.html">testing framework</a>
  10. * <b>Writers:</b> You can help us bywriting <a
  11. href="documentation.html">documentation</a>.
  12. </ul>
  13. Those are just broad things that need to be worked on, but
  14. something that would help tremendously would be to help with
  15. small duties in the project that need to be addressed.
  16. You can see what needs to be done in the class libraries <a href="class-status.html">here</a>
  17. ** To start contributing
  18. As a programmer, you can contribute in three different scenarios to Mono:
  19. <ul>
  20. * If you only have Linux/Unix.
  21. * If you only have Windows.
  22. * If you have both Linux and Windows.
  23. </ul>
  24. You might also want to check our <a href="#setup">common
  25. setups</a> section that describes some common setups that people
  26. use while working on Mono.
  27. *** Contributing to the class library, regression tests or the compiler
  28. This only requires Windows currently.
  29. To start developing classes or to contribute to the compiler,
  30. you only need Windows and the .NET Framework 1.0 SDK. Please notice
  31. that you do not need Visual Studio (although you can use it if
  32. you want). The .NET Framework SDK requires some version of
  33. Windows XP or Windows NT. If you are running Windows 98, 95
  34. or Me, you could use instead the <a
  35. href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/001/829/msdncompositedoc.xml">.NET Redist package</a>, but it
  36. lacks the documentation browser and the ildasm program (C#, VB, JScript and IL
  37. assembler are included).
  38. You can get it <a href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true">here</a>
  39. If you are new to .NET, writing regression tests is a good way
  40. of starting to contribute: it will help you get used to C# as
  41. well as getting comfortable with the .NET APIs.
  42. This helps because at this point you might be the best
  43. qualified person to fix a problem found by the regression
  44. test, or you might have a new class to implement in the .NET
  45. world that only has a test suite.
  46. To get started writing tests see the <a href="testing.html">Test Suite</a>
  47. section. <a href="mono-contribution-howto">Here</a> there is a good All-In-One introduction to the art of writing tests.
  48. *** Contributing to the runtime engine
  49. This only requires Linux, currently some tasks are easier if you
  50. have access to Windows as well.
  51. Here are a few things you can do:
  52. <ul>
  53. * Port the runtime to other architectures.
  54. * Port the runtime to other operating systems.
  55. * Finish the IL code verifier in the runtime.
  56. * Hack the JIT, improve the code generator, add new
  57. pattern rules, improve the register allocator.
  58. * Implement the debugging interfaaces
  59. </ul>
  60. ** Bug reporting
  61. If you find bugs in Mono, please make sure you enter a bug
  62. report so we can keep track of problems in Mono.
  63. To enter bug reports go to <a href="http://bugzilla.ximian.com">
  64. http://bugzilla.ximian.com</a> and enter bug reports against
  65. your favorite component (Mono, Runtime, C# compiler).
  66. You can review the list of current bugs by going <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&product=Mono%2FMCS&product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=%27Importance%27&form_name=query">here</a>
  67. ** Small tasks
  68. A few smaller tasks are here, dropped in no particular order:
  69. <ul>
  70. * <b>Mono/doc and web site:</b> They need to be
  71. packaged up in the official `distribution'
  72. * Adding serialization support to all the classes.
  73. We have many classes, but we have not implemented in
  74. many cases the serialization and re-incarnation support in
  75. them (this is pretty straight forward code, and simple,
  76. but there is a lot to be done here).
  77. </ul>
  78. * Emacs support
  79. Brad Merryl's C# mode for Emacs is available: <a
  80. href="http://www.cybercom.net/~zbrad/DotNet/Emacs/">http://www.cybercom.net/~zbrad/DotNet/Emacs/</a>
  81. * Books on C# and DotNet.
  82. <ul>
  83. * Dotnet Books (<a href="http://www.dotnetbooks.com">http://www.dotnetbooks.com</a>)
  84. * Dotnet Resources (<a href="http://www.dotnetexperts.com/resources/">
  85. http://www.dotnetexperts.com/resources</a>)
  86. * O'Reilly C# Essentials (<a href="http://www.oreilly.com/catalog/csharpess/">
  87. http://www.oreally.com/catalog/csharpess</a>)
  88. * O'Really .NET Essentials (<a href="http://www.oreilly.com/catalog/dotnetfrmess/">
  89. http://www.oreally.com/catalog/dotnetfrmess</a>)
  90. </ul>
  91. <a name="setup">
  92. * Common Setups
  93. People running both Linux and Windows while contributing to
  94. Mono use a number of tricks to increase their productivity.
  95. Scenarios:
  96. <ul>
  97. * <b>Linux host and Windows host</b>
  98. The Windows file system is shared (right click on
  99. your hard drive icon, and select sharing, allow this
  100. to be shared).
  101. The Windows machine has the required build tools
  102. (cygwin, and the .NET framework). On the Windows
  103. machine, you want to setup the ssh server (run the
  104. ssh-host-config program to configure your ssh) and
  105. run it (from a cygwin terminal, type: /usr/sbin/sshd).
  106. From the Linux side, you want to mount the Windows
  107. file system, using something like this:
  108. <tt><pre>
  109. mount -t smbfs -o uid=miguel,username="Miguel de Icaza" "//quack/c$" /mnt
  110. </pre></tt>
  111. In the above example, my Linux user name is
  112. `miguel', and this will allow this user to have
  113. read/write access to the share.
  114. The host name is `quack', and the name of the share
  115. is `c$' (that is the C: partition).
  116. The file system is accessible on /mnt.
  117. You can perform your cvs update and cvs commits from
  118. the /mnt directory, and run Emacs or your favorite
  119. Linux text editor on the Unix side in this way.
  120. Then from another terminal, you can ssh into your
  121. Windows box using ssh, like this: ssh "Miguel de Icaza@quack"
  122. </ul>
  123. * Special Note
  124. If you have looked at Microsoft's implementation of .NET or
  125. their shared source code, you may not be able to contribute
  126. to Mono. Details will follow when we know more about this.
  127. In general be careful when you are implementing free software
  128. and you have access to proprietary code. We need to make sure
  129. that we are not using someone else's copyrighted code
  130. accidentally.
  131. Please do not use the <b>ildasm</b> program to disassemble
  132. proprietary code when you are planning to reimplement a class
  133. for Mono. If you have done this, we might not be able to use
  134. your code.
  135. Please stick to published documentation for implementing any
  136. classes.