Community Development

The .NET Micro Framework team will accept any contribution proposal and rate their priority based on the community response and fit to the Micro Framework platform. The general rules for contributing bug fixes or new features can be found in the Micro Framework Contribution Guidelines document athe bottom of this page. In order to make a proposal any community member will want or will be required to file a feature request or issue with the issue tracker, or to vote for an existing one. Contributions will be prioritized at the beginning of every release cycle and features prioritized and published in a roadmap. It will be generally be still possible to modify the roadmap in the middle of a release cycle when and if high priority items come in late and enjoy a large community support.

The Core Tech Team of the .NET Micro Framework and the .NET Micro Framework team will be responsible for managing the prioritization process by the guidelines above and for publishing the roadmap. Any contribution or new feature accepted for a release cycle will show up in the roadmap and will be supervised by one or more Core Tech Team members. If you wish to contribute to the code base please signal your availability when you open your feature request or issue, and the .NET Micro Framework Team will put you in contact with one or more member of the Core Tech Team to start your design and implementation activities. Core Tech Team members will guide the community members through all development phases of design, implementation, testing and integration in the code base or tools. The .NET Micro Framework team will conduct the final review.

Core Tech Team members enjoy writing privileges to the code base while community members that want to work on a feature will be provided with writing privilege for the necessary time to complete their work.

 General rules

The .NET Micro Framework team will only accept for review components coded on the CodePlex distribution of the .NET Micro Framework. Reviews can be provided as packaged changes, e.g. through Visual Studio Team Explorer. All Code Tech members have access to that tool and community members can refer to them. Review can take several iterations, but with the help of the Core Tech Team members, we hope this will be quick and painless. After a project is reviewed and accepted by the .NET Micro Framework Team, it can be checked in by the community contributor. We will allow a time window during which the contributor will support the project directly. After the release is shipped, the .NET MF team will take over the support.

 Managed code contributions

Managed code contributions can be coded through the standard SDK but they need to be ported to the CodePlex distribution build system before being submitted for review. This is a very easy step to do, as the user just needs to change the .csproj file. As a general guideline, every additional component will be added as a separate assembly. Types that belong to the desktop framework must be added to the corresponding assembly and namespace.

Native code contributions

Native code contributions can be coded in the standard PK but need to be ported to the CodePlex distribution build system before submitting them for review. The project files for the native components are virtually identical.

SolutionWizard integration

The .NET MF team will take care of integrating the newly added components in SolutionWizard.

Managed and Native code contributions

Contributions that require both managed and native code must be provided for review with both parts on the CodePlex distribution code base.

 

Last edited Apr 26, 2012 at 4:23 PM by lorenzte, version 2