Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

How to Contribute

Alexander Köplinger edited this pageAug 31, 2019 ·7 revisions

Contributing to Code

There are many ways to contribute to Xamarin.iOS and Xamarin.Mac: logging bugs, submitting pull requests, reporting issues, and creating suggestions.

Bindings

Thisdocument regroups different advice that are useful when writing bindings and explain our release process and tools.

When a new version of Xcode comes out, we run adiff tool to see the changes. The results then becomeswiki pages and these are the documents we use to add or update our bindings. As changes can be pretty massive, we need tosplit the work between Xamarin iOS/macOS team members and our lovely contributors.

Work Branches

Even if you have push rights on thexamarin/xamarin-macios repository, you should create a personal fork and create feature branches there when you need them. This keeps the main repository clean and your personal workflow cruft out of sight.

Pull Requests

To enable us to quickly review and accept your pull requests, always create one pull request per issue and link the issue in the pull request. Never merge multiple requests in one unless they have the same root cause. Be sure to follow ourCoding Guidelines and keep code changes as small as possible. Avoid pure formatting changes to code that has not been modified otherwise. Pull requests should contain tests whenever possible.

Where to ContributeCheck out thefull issues list for a list of all potential areas for contributions. Note that just because an issue exists in the repository does not mean we will accept a contribution to it. There are several reasons we may not accept a pull request like:

  • Someenhancement describe a real issue but the proposed way to solve it might not be the best one. Discussions on how to best solve the root issue should happen on the GitHub issue (and before a pull-request);
  • Negative impact on build time or build size. E.g. ideally the cost of fixing something should not have a huge impact on people that do not require that feature;
  • Incomplete support of all platforms. If a featurecan exists across all platforms then it should be implemented for all of them. This helps to create cross-platform applications;

To improve the chances to get a pull request merged you should select an issue that is labeled with thehelp wanted orbug labels. If the issue you want to work on is not labeled withhelp-wanted orbug, you can start a conversation with the issue owner asking whether an external contribution will be considered.

To discuss this project, and participate in the design or development, we use theGitter chat.

Gitter

Suggestions

We're also interested in your feedback for the future of Xamarin.iOS and Xamarin.Mac. You can submit a suggestion or feature request through the issue tracker. To make this process more effective, we may ask that these include more information to help define them more clearly.

Bugs

Take a look atour guide to filing issues.

Coding Guidelines

We useMono's Coding Guidelines.

Discussion Etiquette

In order to keep the conversation clear and transparent, please limit the discussion to English and keep things on topic with the issue. Be considerate of others and try to be courteous and professional at all times.

Clone this wiki locally

[8]ページ先頭

©2009-2025 Movatter.jp