Coding Standards » History » Version 2
Eric Davis, 2010-08-19 03:12
A TOC is always nice to have
| 1 | 2 | Eric Davis | {{toc}} |
|---|---|---|---|
| 2 | |||
| 3 | 1 | Eric Davis | h1. Coding Standards |
| 4 | |||
| 5 | h2. Ruby and Rails Code |
||
| 6 | |||
| 7 | TODO: until then, follow the basic Ruby and Rails standards. |
||
| 8 | |||
| 9 | h2. Javascript |
||
| 10 | |||
| 11 | TODO |
||
| 12 | |||
| 13 | h2. CSS |
||
| 14 | |||
| 15 | TODO |
||
| 16 | |||
| 17 | h2. Commits |
||
| 18 | |||
| 19 | Commits should be formatted as below. If you are contributed via git, this will save the committer a bunch of time: |
||
| 20 | |||
| 21 | <pre> |
||
| 22 | Short summary of your commit, 72 characters. #nnnn |
||
| 23 | |||
| 24 | (This is optional) Longer description of the change, including a |
||
| 25 | list of what changed if it's a major change. Limit each line to 72 |
||
| 26 | characters and use basic textile (* for lists). |
||
| 27 | |||
| 28 | Contributed by Your Name |
||
| 29 | </pre> |