Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.
Community Standards and Participation Guidelines
The Developer community provides a growing number of opportunities for developers who wish to discuss content we publish, or debate issues more generally. Our aim is to ensure this platform is inclusive and safe, and that Developer community is the place on the net where developers will always find lively, informative and, above all, engaging discussions. This document covers all aspects of community interaction and moderation on Developer Community, including comments on blogs or articles.
There are a few simple guidelines which we expect all users to abide by. These apply across the site, while moderation decisions are also informed by the context in which comments are made. The objective is to maintain the Developer community as an inviting space is to focus on intelligent discussion of topics.
- We allow debate and dissent, but personal attacks, persistent trolling and mindless abuse will not be tolerated.
- We will not allow misrepresentation of Nokia to be published on our website.
- We reserve the right to limit content or move it to the appropriate location.
- We will not tolerate racism, sexism, homophobia or other forms of hate-speech, or contributions that could be interpreted as such.
- We will remove any content that may put Nokia in legal jeopardy.
- We will remove unauthorized publication of intellectual property
- We will remove any content that is obviously commercial or otherwise spam-like.
- We may remove posts or articles that are not relevant.
- These standards apply to all content, private or public, regardless of language.
Be aware that you may be misunderstood, so try to be clear about what you are saying, and expect that people may understand your contribution differently than you intended. Remember that text isn't always a great medium for conversation: tone of voice (sarcasm, humour and so on) doesn't always come across when using words on a screen. You can help to keep the Developer community areas open to all viewpoints by maintaining a reasonable tone, even in unreasonable circumstances.
- If you act with maturity and consideration for other users, you should have no problems.
- Don't be unpleasant. Demonstrate and share the intelligence, wisdom and humour we know you possess.
- Take some responsibility for the quality of the conversations in which you're participating. Help make this an intelligent place for discussion and it will be.
Most of the people who contribute to our discussion boards are volunteers. If someone is helpful, they are doing it as a favor to you. Therefore, out of respect for their time, you should follow these guidelines when posting a question.
- Before you post, spend some time trying to answer your question yourself. Search for the answer in Bing and StackOverflow, read the documentation, debug your application (particularly for exceptions), and search the discussion board itself for similar questions. If you can't find the answer, then it's okay to ask.
- Make sure you post in the proper forum, and give as much detail about what libraries and versions of those libraries as is relevant.
- Explain what you're trying to accomplish.
- Explain the problem you're having, in enough detail that people not working on the project will understand it. If you're getting an error, make sure to include the error text.
- If your program produces results that are different than what you expected, state what you expected, why you expected it, and the actual results you got.
- Explain what you've already tried to solve the problem.
- Questions that include code are best. Make sure the included code is written it as a short but complete program, and that the code is correctly formatted so that people can read it easily.
- Before you post, carefully read through your entire question to yourself one more time to make sure it makes sense. (Note that it is often at this step that people have "aha!" moments and realize how to solve their own problem.)
- Reply to the answers you get. Let everyone know whether their suggestions worked or what you did instead.
- Give back to the community by answering other peoples' questions when you can, too.
Ask any questions about the rules here
Developer Community Moderation Team