This document provides instructions on how to become a Tizen committer. It outlines the Tizen source code repositories, how to clone the code and modify bugs. It describes using the Git Build System and OBS Build tools. The roles of developers, maintainers, reviewers, and release engineers in the process are defined. The steps to submit a patch for review via Gerrit and the review process are covered. Resources for practicing the process like sample repositories are provided.

1. How to be a Tizen Committer
Jin Yoon

2. !

3. Open Source?
vs
Source Open?

4. Source Open
Source Open

5. Internal
Repository
Open
Repository
clone pullpush

6. Open Source
• Tizen 3.0
Reference : https://source.tizen.org/release/tizen-3.0-milestones

7. Open
Repository
push pull

8. Where to Find Sources?
• https://source.tizen.org/

10. Repository List
adaptation/alsa-scenario-scn-data-0-base

11. ?
34%
framework
16%
profile
15%
apps 9%
toolchains 5%
external 5%
scm 4%
sdk 3%
test 3%
adaptation
3%
samples 3%
Pkernel
adaptation
external
famework
apps

12. Hot Groups
platform
kernel adaptation upstream famework
apps samples
test
scm sdk
profile
mobile wearable tv ivi

14. Bugs in Forum?
https://developer.tizen.org/forums

15. Bugssss
https://bugs.tizen.org/jira/secure/Dashboard.jspa

18. Clone
* Reference
https://source.tizen.org/documentation/developer-guide/getting-started-guide/cloning-tizen-source

19. Branch
• master
• tizen_2.1
• tizen_2.2
• tizen_2.3
• tizen_2.4
• tizen

20. Modify Bugs
코드를 수정하세요.
참, 쉽죠?

21. SDK Build

22. OBS Build
References
"Git Build System"
https://source.tizen.org/documentation/reference/git-build-system
"[Tizen] 우분투에 타이젠 플랫폼 툴인 gbs & sdb 설치해보기"
http://storycompiler.tistory.com/35
"[Tizen] 타이젠 gbs의 모든 것"
http://storycompiler.tistory.com/38

24. Roles
Developers
Write and submit code to the development branch of a Git project.
Verify and review (vote "+1" or "-1") code changes for any project on any branch.
Maintainers
Create additional branches, such as upstream, development branch to profile projects.
Rebase master branch to upstream branch.
Review code, as well as approve (vote "+2") or reject (vote "-2") patches.
Guidelines for maintainers are:
Despite the granted power, maintainers must not accept their own changes without passing peer review ("+1") or ("+2").
The force push right is granted for maintainers to handle code rebase. Maintainers must not abuse the right to hide patch submissions that are
supposed to be reviewed.
Reviewers
Review code, as well as approve (vote "+2") or reject (vote "-2") patches.
Release Engineers
Approve submission to OBS.
Perform smoke-test of the resulting image and then transfer to the release area for QA engineers to perform further test.
QA Engineers
Perform thorough integration and verification of the image to eliminate regressions and bugs.

25. Submit a Patch to Gerrit
• Push
$ git push origin HEAD:refs/for/tizen
https://source.tizen.org/documentation/reference/gerri
t-usage
• Gerrit Site
https://review.tizen.org/gerrit

26. 1:n Review, Patches…

27. Reviewer’s Review
Reviewing a Patch on the Gerrit
To review a patch in the Gerrit web GUI, publish the comments and vote for the
patch, the patch will be merged or discarded depending on the voting results.

28. Reviewers
"타이젠을 말하다“
박영주 연구원 : yjoo93.park at samsung.com
"Tizen Application Inside Out"
이세문 연구원 : sm79.lee at samsung.com
"타이젠 UI앱의 필수, EFL 파헤치기"
정우현 연구원 : wh0705.jung at samsung.com
"더 빠르고 더 유연한 윈도우 시스템(Wayland on Tizen 3.0)
문관경 연구원 : kk.moon at samsung.com
"바닥부터 만들어보는 Tizen(Tizen from scratch)"
우상정 연구원 : sangjung.woo at samsung.com
"타이젠 오픈소스의 커미터가 되어보자!"
윤 진 연구원 : jinny.yoon at samsung.com
"Tizen SDK를 이용한 Tizen Platform 개발"
이승환 연구원 : sh.cat.lee at samsung.com

29. Practice
• Repository
git clone
ssh://<username>@review.tizen.org:29418/apps/native/sample/adventure

30. Hole #1

31. Hole #2

32. Hole #3

33. Hole #4

34. Telegram
• Repository
git clone ssh://<username>@review.tizen.org:29418/apps/native/telegram-tizen

35. Q&A