-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathindex.html
161 lines (123 loc) · 2.65 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
<html><body>
<li>Tools
<ul>
<li>Mandatory
<ul>
<li>Source Content Management
<ul>
<li>Why</li>
</ul>
</li>
<li>Tickets
<ul>
<li>Why</li>
<li>What</li>
</ul>
</li>
<li>Unit test framework
<ul>
<li>Why</li>
</ul>
</li>
<li>Packager
<ul>
<li>Why</li>
<li>What</li>
</ul>
</li>
</ul>
</li>
<li>Nice to have
<ul>
<li>Continuous integration automate
<ul>
<li>Why</li>
<li>What</li>
</ul>
</li>
<li>Static analyser
<ul>
<li>Why</li>
<li>What</li>
</ul>
</li>
<li>Runtime analyser</li>
<li>I18n</li>
<li>Website</li>
<li>Documentation tools</li>
</ul></li>
</ul></li>
<h2 >Tools</h2>
<h3>Mandatory</h3>
<h4>Source Content Management</h4>
<h5>Why</h5>
A good scm allow you to:
<ul>
<li>Save your work and rollback easily</li>
<li>Keep trace of what you did, and how.</li>
<li>Implement features easily: branch,
so you don't break your project during development, and you can still commit.</li>
<li>Share, and work together.</li>
<li></li>
</ul>
<h6>What</h6>
<ul><li>git or GTFO</li></ul>
<h4>Tickets</h4>
<h5>Why</h5>
<ul>
<li>For bug reports.</li>
<li>For feature request.</li>
<li>As a todo list/backlog.</li>
</ul>
<h5>What</h5>
<ul>
<li>Redmine/chiliproject</li>
<li>Jira</li>
<li>Avoid trac if your project contains subprojects</li>
</ul>
<h4>Unit test framework</h4>
<h5>Why</h5>
Unit test are awesome for:
<ul>
<li>Debugging.</li>
<li>Avoid regressions.</li>
<li>They give nice examples of how to use your code.</li>
</ul>
<h4>Packager</h4>
<h5>Why</h5>
If you want your project to work you need to make it easy to test.
One way is to package it nicely.
<h5>What</h5>
If your whatever language, framework, does not provide it:
<ul>
<li>cpack (which can be used without cmake)</li>
<li>fpm</li>
<li>Be a man and right your own rules/specs/ebuild</li>
</ul>
<h3>Nice to have</h3>
<h4>Continuous integration automate</h4>
<h5>Why</h5>
<ul>
<li>It nice that it works on your computer, but it is better if it works on main targets (provides a packages for each target).</li>
<li>Runs all the tools bellow in background.</li>
</ul>
<h5>What</h5>
<ul>
<li>Jenkins</li>
<li>gitlab-ci</li>
<li>buildbot</li>
</ul>
<h4>Static analyser </h4>
<h5>Why</h5>
Efficient quality checking and nice advice at a low price. What's else?
<h5>What</h5>
<ul>
<li>clang/gcc</li>
<li>cppcheck/clint</li>
<li>sonar</li>
</ul>
<h4>Runtime analyser</h4>
<h4>I18n</h4>
<h4>Website</h4>
<h4>Documentation tools</h4>
</body></html>