Developers

From $1
    Table of contents

    If you want to contribute on the development of MonoDevelop, implement your own tools based on the platform, create new add-ins for the IDE, or just know more about the project, you'll find some useful information in this page. Here are some interesting links to start with:

    • Articles: A collection of articles written by the MonoDevelop community. You'll find technical documentation, tutorials and other useful information for learning about the MonoDevelop platform.
    • TODO: A list of features we would like MD to have. If you want to contribute, just pick one of them and notify through the mailing list that your are going to work on it.

    Contribute

    MonoDevelop is always looking for contributors to help with development. If you have some time and want to help, there are instructions below.

    Reporting Bugs

    Reporting bugs is a very easy way to help contribute to any project. MonoDevelop bugs are be filed at bugzilla.xamarin.com.

    To report a bug, follow the steps below:

    1. Create a Bugzilla account.
    2. Ensure the bug you are reporting hasn't already been fixed. Install the latest version of MonoDevelop using the "Current Development" instructions on the download page.
    3. Review the open MonoDevelop bugs and make sure that your bug hasn't been submitted already.
    4. If it hasn't been submitted, submit a new MonoDevelop bug.

    Error traces gathered by running MD from a terminal are often helpful in tracking down a bug. For more information read the article on logging.

    Submitting Patches

    Patches have to be submitted by using the Pull Request mechanism that github provides. Here is a summary of how it works:

    1. If you don't already have one, you have to create your own fork of the MonoDevelop repository. You can do it using the Fork command available in the main page of the project in github.
    2. Make and commit your changes in your forked repository.
    3. In the main page of your forked repository, click on the Pull Request command.
    4. In the Pull Request dialog, enter a descriptive comment of the change and add a recipient. You can use following users as recipients:
      • mhutch: ASP.NET, Mac port, MonoTouch, Moonlight, MonoMac, XML, T4
      • mkrueger: Text editor, C#, refactoring operations
      • slluis: everything else 

    Commit Rules

    There are a few rules to follow when committing code:

    1. Enter a meaningful explanation in the commit log message.
    2. The first line of the commit message should be prefixed by the component name in square brackets, if it affects a single component, e.g. [Ide]
    3. The first line of the commit message should be a short (ideally <50 columns) message, followed by a blank line. The rest of the commit message could contain a more detailed explanation of the change, wrapped to 80 columns.
    4. When entering a message describing a change, take into account that the goal is to explain why the change was done, rather than what was changed. For example, the message "Added property X" is in general useless since it is obvious looking at the patch.
    5. All changes included in a commit should be related and as atomic as possible. Here are some examples:
      • You do an API change that affects several projects across the source tree. All changes can go in a single commit.
      • You implement a new feature A, for example, in MonoDevelop.Projects. Then you implement another new feature B that uses A in MonoDevelop.Ide. Although those changes are related (B needs A), they should be committed separately, since they belong to two different features.
    6. Don't do reformatting commits, unless you're the original author of the code. This includes changing line endings.
    7. Never remove copyright notices from the code.
    8. Never remove licensing info from code.
    9. Never commit code you didn't write yourself or code that doesn't have a suitable license.

    Coding Guidelines

    New code written for MonoDevelop should follow the generic Mono Coding Guidelines, with the following exceptions:

    • use camelCase for field names
    • code must be indented using tabs, not spaces, and tabs have a width equal to 4 spaces
    • the opening brace { of a class or namespace should be put on a new line, like methods
    • lines should be wrapped to 120 chars, not 80

    The MonoDevelop solution is configured with formatting policies that conform to these guidelines.

    Public/protected API should be documented using XML doc comments, but keep them concise and useful. If they're generic/obvious and don't add any value, for example a constructor with a summary "create a new instance of Foo", they should be omitted.

    It's recommended to follow the .NET Framework Design Guidelines. If you do not have the excellent and detailed book, there is also a free digest and a section on MSDN. There are also some docs for .NET 1.1 that mostly remain applicable to newer versions of the framework.

    You should also follow our Human Interface Guidelines when designing windows and dialogs.

    A Note on Licensing

    All new code and modifications to existing code should be licensed under MIT X11. The MS-PL and Apache 2 licenses are acceptable for new libraries and new addins.

    Code and libraries licensed under version 2 of the LGPL license are acceptable under extraordinary circumstances.

    Code licensed under the GPL cannot be accepted.

    Although addins that do not follow these rules cannot be accepted into the MonoDevelop source repository, they can be hosted elsewhere. However, this generally means that they are much less likely to be maintained and distributed.

    Working on the Website

    We are always looking for help on developing the Monodevelop web site. If you're interested, please contact lluis at ximian dot com. Currently, we're are looking for the following:

    • Tutorials
    • Screenshots
    • Content writers

    Any contributions you may have though would be appreciated. The list above is in no way all inclusive.

    Tag page
    • No tags

    Files (0)

     
    You must login to post a comment.
    Page last modified 19:15, 29 Apr 2013 by jeff