Documentations

Contents

Porting Guide
User Guide
API Reference
Coding rules
Commit rules
Release Notes

Porting Guide

Please find it here.

User Guide

Installation

Getting Started
How to install Kconfig-frontend
Board-Specific tools like programming

Application

Application overall
How to add new application
How to add TASH commands
Shell commands list

SmartThings & OCF (Cloud Connection)

How to develop things using SmartThings Things SDK
How to use IoTivity

Audio

How to use Tinyalsa

FileSystem

How to use ROMFS

Debug methods

Shell commands list
How to use RAMDUMP
Logging System
Ttrace

TroubleShooting

API Reference

Please find it here.

Coding rules

Basically we follow Tizen Coding rule except R04.
We recommend using braces even if it has single statement.
Here is a link.
M means Mandatory, R means Recommendation.

Script to apply our C coding rule

There is the formatter.sh to apply our C coding rule at os/tools folder.
./formatter.sh --help helps how to use it.
Be aware that is not perfectly working on our coding rule.
For example, it makes a space between type casting and varibale which is a violation of coding rule.

Commit rules

1. Don't use past tense on commit title.
2. Please fill where and what you modify on commit title.
3. Please keep short title length.
   It makes git commit --oneline beautiful (easy to see).
4. Please add an empty line at second line of commit message to distinguish title and description. This is good to oneline command as well.
5. Please fill commit description what you do in detail.
6. Don't mix different kinds of changes like formater and code logic change.
7. To modify your commit which is in pull request, amend original one.
   Don't make a new commit to do it.
8. After making pull request, Don't update yours using git pull.
   Please use git rebase instead of pull.
   pull makes unnecessary commit like Merge branch 'master' into .
   That redundant commit is not helpful to developer and maintainer.

Release Notes

v1.1
v1.0