Be Respectful & Patient
- Be patient with and kind to all forum participants.
- Disrespect, discourtesy, vulgarity, or threats of violence are not tolerated in our community. Abusive comments may be removed by moderators. Repeat offenders may have their accounts banned.
Successful Contributors Will:
- Search before posting: There is a good chance a thread about your topic or an answer to your question already exists. Help minimize duplicate posts to ensure useful information gets surfaced easily!
Use informative post titles: Keep titles short, specific, and on-topic so the forums are easier to navigate. If you’re asking a question, it should go in the title.
- Bad: I need help with iOS
- Good: How to enable paging when using UIScrollView?
Mark questions and discussions properly: When posting a thread, ensure that you are properly marking threads that ask a question as “question”. For a conversational topic, choose "new discussion".
- Provide steps to reproduce the issue: If an issue can be reproduced with a set of specific steps and/or a test case, include as much information as possible to help others reproduce it. This is especially helpful for not only the Xamarin team, but others to assist you, and report bugs if necessary. Attachments can be uploaded to a post. If the test case or diagnostic information is private, consider creating a new Bugzilla entry marked "Private (Xamarin Team Only)", and post a link.
- Respond to feedback: Make sure to check back on your post and reply with any further information requested. Make use of the
@mention syntax for notifying a user that you have responded.
- Tag posts as answered: Marking questions as “answered” helps other users encountering the same issue, and reduces the likelihood of duplicate posts being submitted.
- Remember to like posts: This makes it easier for users to find popular posts.
- Follow Xamarin's Branding Guidelines: For naming their social and forums accounts, events, meetup/user groups, and other organizations.
Successful Contributors Will Not:
- Spam: Post once in the forum that is the most relevant to your question, comment, or concern. Avoid comments that do not add value to the thead or help users. Comments like "Help", "Why?", etc. bury the original topic, are generally not actionable, and may discourage others from participating in a thread.
- Register multiple accounts on the Xamarin Forums
- Violate existing copyright, patent, trademark, or other proprietary rights
- Improperly credit sources: If you are going to post material that is not your own, give credit to the original authors. Failure to do so is considered plagiarism.
- Misrepresent their affiliation: Impersonations of Xamarin/Microsoft employees, forum users, or other people, regardless of their affiliation with Xamarin or Microsoft, are expressly disallowed.
- Engage in personal attacks: Do not attack fellow users or their comments. Use civil language at all times, even if you disagree with a comment. Do not stalk or otherwise harass others on the Xamarin forums.
- Disclose a user's unpublicized email address
- Comment on old posts: It's preferred to post a new question/discussion and include a link if there is relevant information you want to share when a topic is older than 6 months. There are some exceptions to this rule when an ongoing conversation is active on a long thread.
Posts that meet criteria discussed above may be closed by moderators.
English is the official language of our forums because it is the common language between our moderators and users. Because we cannot moderate conversations in a foreign language, you may not hold a conversation in the forums in languages other than English.
The Xamarin forums support Markdown. You can improve post readability by using the toolbox to format text or do it manually.
- Use subheadings to help split text-heavy posts into clear objectives: You can use this to help organize the text of a post. To organize longer posts with subheadings, use
# for 1st level headers,
## for 2nd level,
### for 3rd level, and so on.
- Format blockquotes by placing
> at the beginning of a line
- Place single back-ticks (`) around inline code: By writing `inline code`, you'll end up with
- Mark source code as code: To post source code that occupies multiple lines, use ``` followed by an empty line, your source code, and end with another empty line and ```. If your code snippet exceeds 25 lines, use GitHub Gist or another provider to host your snippet.
- Indent source code appropriately: Whitespace will be preserved in your post. As such, ensure that you're indenting code the way you want it to be seen.
Using the information above, you'll be able to format code like this: