Track our various Development Plans
Downloads | Bug Reporting | Software
API Docs | Languages | Books | Roadmap | Plans
Class Status | Build Status | Source Code
Mailing Lists | Forums | Chat | Blogs
General | Technical | Licensing | Asp.net | Security | WinForms
Mono shipped its first release in June 2004, and the project is moving forward in various directions:
- Performance, scalability, reliability improvements.
- Implementing missing functionality
- Implementing new features.
If you are interested in contributing, here are some pointers:
- Contribution HowTo
- Bugs: Known bugs in Mono, you can look at which issues people are reporting.
- MoMA Migration Reports: These are report of applications that people want to run with Mono, and the APIs that are missing or pending
- Resources: Go to this page to take a look at the status of our API classes.
The project is under active development and has a vibrant community. If you are looking at ways of helping the project, you have come to the right web page.
**Microsoft .NET source code:** If you have looked at Microsoft's proprietary implementation of .NET or their shared source code (which is also proprietary), you will not be able to contribute to Mono. If you would like to contribute in this area, be careful to not look into them in Visual Studio debugging experience.
Microsoft open-sourced parts of the .NET Framework, see .NET Source Code Integration for more details.
Contributing to the Mono runtime: If you are submitting changes to the runtime, you must make sure to release your change under the MIT license before it is integrated. You may do so by adding this line to your commit messages:
This change is released under the MIT license.
In general, be careful when you are implementing free software and you have access to proprietary code. We need to make sure that we are not using someone else’s copyrighted code accidentally.
Reverse Engineering: Do not use the ildasm, reflector or other equivalent tools program to disassemble proprietary code when you are planning to reimplement a class for Mono. If you have done this, we will not be able to use your code.
- Please stick to published documentation for implementing any classes; when in doubt, post to the mailing list and discuss the possible approaches with others.
Microsoft also publishes a lot of code under open source licenses (MS-PL or Apache2). Looking at that code poses no problem. Some examples of code that you can look at include Microsoft’s DLR, Microsoft’s MEF, Microsoft’s ASP.NET MVC, Microsoft’s OData client stack and Microsoft’s TinyCLR all licensed with open source compatible licenses.
Our immediate goals are described in the Mono Roadmap, in general fixing bugs, improving performance, improving documentation, quality and the overall polish are all good ways of contributing to Mono. You can track the various technologies on the Plans page.
You might want to look at the project To-Do list, there are various medium and large projects there.
Those are just broad things that need to be worked on, but something that would help tremendously would be to help with small duties in the project that need to be addressed.
You can see what needs to be done in the class libraries here
You can help write documentation, please see Mono Documentation Improvement Project.
After you have commited your patches to our git repository, please use the build status page to keep track of how your changes affect the build. If your patches turned the tree red, please back it out immediately.
Contributing to Mono
Contributing to the Class Libraries
For class library developers, we typically ask that you build NUnit tests to understand the API that you are going to implement, this will give you an insight beyond what the documentation states about the class. Then you should implement the code.
This is useful because once you submit the code it will help others not introduce problems in code that you depend on. Or if your project needs to be maintained and extended it will assist us in not breaking existing functionality that is implemented.
You should test the NUnit test cases on the real framework and make sure that all tests pass. Then these tests can be directly integrated into our build system.
When contributing to the class libraries, please have a look at our Coding_Guidelines. Note that our coding format is different from the default style from Visual Studio.
Testing on Various Platforms
Mono runs on many different platforms on many different architectures. However, no one can be expected to test their changes on all these platforms. To facilitate this, we run continuous builds for many platforms. The results are available on the Mono Build Status page.
This page allows you to ensure that:
- Your change did not break the build on a platform.
- Your unit tests pass on all platforms.
If you find that one of your commits broke something, don’t panic! Just please either fix it or revert your change. This keeps Mono working for everyone, no matter what platform they use.
Maintaining Multiple Trees
If you want to maintain multiple active Mono installations in your system (a stable release, and one or more development releases) read the Parallel Mono Environments page.
Debugging with Visual Studio
If you plan on developing on Windows and testing your work using Visual Studio, you will want to edit the assembly that you are working on, and remove from the AssemblyInfo.cs file the line that “signs” your assembly.
By removing the assembly signing, this will allow you to create a test project that includes your new assembly and that will load this new version of the assembly instead of the assembly that lives in the GAC.
For example, if you want to debug Mono’s Windows.Forms, you would load the solution from mcs/class/Managed.Windows.Forms, edit the AssemblyInfo to prevent the signing and rebuild the project. Then your test program can reference this assembly without loading the one from the GAC.
Ways to Contribute
There are three different philosophical approaches to helping the Mono project:
The selfish way is packed with adventure. You start by building your own software, and start using the compiler and tools that come with Mono. Eventually you will run into missing features, or a bug in the software. Since we ship all the source code for Mono, you can start tracking down the problem. Depending on how much time you have to devote to the problem you could: File a bug report; track down the problem and provide a better bug report; fix the bug and provide a patch (you can post it to the mono-devel mailing list; or discuss the solution on the mailing list). Ideally you will also write a regression test so the bug does not get re-introduced in the future. You can also get contact with the hackers through IRC channels.
The altruistic way is probably the easiest because you get to pick a piece of Mono that you might want to work on. You can pick an unfinished class (from our Class_Status); help with the documentation effort (mailing list for the documentation effort); fix existing bugs; help with the tools or writing tests that help make Mono more robust.
The educational way is an interesting one, because you pick a technology you are interested in, and work on that technology to learn the technology. If you are interested in it, please take a look at this list for possible projects.