This forum is a pretty relaxed place, and everyone is welcome to contribute questions and answers, or just have a chat or make a comment.
If you do have a problem with your code though, you will get a better answer faster if you help by clearly explaining the problem.
This is not a set of rules of what you have to do, but if you can follow this guide then you are more likely to get the answer that solves your problem.
Before you write your question:
Search the forum and on Google. The answer may have been given already, and you won't have to wait for a reply. Searching 'MoSync + <error message>' is a good way to start. There is a great deal of documentation, screencasts, forum posts, tutorials and examples on the website.
1. Clearly and concisely explain your problem.
GOOD: "I've got a Screen* which is going out of scope when my downloader class starts a download"
BAD: "My screen doesn't work"
Just saying that the screen doesn't work doesn't let us understand your problem. The people who can help are a lot less likely to spend the time looking at your problem if you've net explained what is wrong.
Explain what you want to happen, and if necessary, explain how this is different to what is happening.
2. Explain what you've tried to do:
GOOD: "I've stripped out all the rest of my code to get this as simple as possible, and I've put debug through the process so I can track it in the console. I've tested the value before the process, and it is definitely set then"
BAD : Not writing anything
VERY BAD: Not actually trying anything before asking for help.
People will be more inclined to help people who've shown some initiative in solving the problem. The group of users least likely to be helped are those just begging for answers.
3. Tell us where you've already looked for answers
GOOD: "I've searched the forum, and found this link, but it doesn't really help my problem. I also did a Google search which brought up a lot of links about scope, but I don't know how to apply that to my code."
BAD: Taking up other people's time when you've not researched the possible solutions yourself.
By saying where you've already looked, you won't get those same links again. If you say that you've read the tutorial on the subject, and your question isn't covered, then you're not going to get an answer which is just a link to the tutorial.
4. If you have to paste code, use the Syntax Highlighter.
If you paste code straight into the text area, lots of your code will be stripped out. There is a way of posting code and making it readable to everyone else. Click 'Enable rich-text' beneath the space where you're writing your question. This will make a row of icons appear above your text. One of these (on the right hand side) looks like a yellow pen. Click it, and a popup window will appear. Paste your code into that window, and press 'Insert'. This will put your code in, and reader won't have to guess at what you've written.
5. If you have to attach code, zip it up
You can attach code to the forum if it is a zip file. If necessary, zip up your project folder, but don't include the Output or FinalOutput folders. Don't use rar.
6. Don't hijack other threads.
If you've got a new question, but it is clearly related to an existing thread, then please add your question to the bottom. Don't add your question to the bottom of a thread which is on a completely different topic. If nothing else, it may not be read by the people who can help.
7. Don't start new threads for the same question.
Asking a question in a new thread which has already been addressed in another thread is just going to confuse readers. Think about how you would like to find answers in the forum.
8. Don't make duplicate posts.
Don't post the same question in more than one thread, you're only going to get one answer.