Here are some recommendations for content when creating a tutorial for the MeeGo SDK.
Details for the SDK documentation creation process are described [here]
# Create a bug # Create wiki content (w/source, screenshots, etc) # Request review, update bug. # Add link to the appropriate section of the [Developer_Guide_for_MeeGo_1.0 Developer's page]
The content of the tutorial is up to you but it should be concise and accurate. If you are not the expert, be clear to note that. For example: "Here is one way to <perform this feature>. There may be better ways." In addition, the following components are recommended if applicable:
Generally links to offsite content is not encouraged. Advertising, spam, or other inappropriate content will be removed and the author banned from further contributions.
Wiki standards should be used and look similar to [Developer_Guide_for_MeeGo_1.0 other tutorial pages]. Some basics:
Links to your new tutorial should be placed on the main developer page after a peer review and only when it is ready for developers to use.
Screenshots are encouraged if helpful.
Put into public git. If Qt, qmake, make, make install should be sufficient. If not Qt, autogen, make make install should be sufficient
* Code snippets
Small snippets can just be inline
* meego-sdk dev list * area specialists/maintainers * update bug