Hackathon
Version 5 (Vadim Pisarevsky, 2013-01-24 07:27 pm)
| 1 | 1 | h1. Hackathon |
|
|---|---|---|---|
| 2 | 1 | ||
| 3 | 1 | _+hackathon=hack+marathon+_ |
|
| 4 | 1 | ||
| 5 | 1 | A hackathon is an event in which computer programmers and others in the field of software development collaborate intensively on software-related projects. |
|
| 6 | 1 | ||
| 7 | 1 | h3. The Purpose |
|
| 8 | 1 | ||
| 9 | 1 | For this hackathon, our goal is increasing code stability to make the library steady as possible. |
|
| 10 | 1 | ||
| 11 | 4 | Vadim Pisarevsky | * Improve library stability and quality of the documentation |
| 12 | 1 | * Provide feedback to our customers |
|
| 13 | 1 | ||
| 14 | 1 | h3. Organization |
|
| 15 | 1 | ||
| 16 | 4 | Vadim Pisarevsky | Hackathon duration is one week (from 8 October to 12 October). You should try to be in the office from 11 a.m. to 6 p.m. All communication activities will be at this time. |
| 17 | 1 | ||
| 18 | 1 | Each developer get own area of ââresponsibility: |
|
| 19 | 1 | ||
| 20 | 4 | Vadim Pisarevsky | |Evgeny | build issues, objdetect | |
| 21 | 4 | Vadim Pisarevsky | |Ilya Lavrenov | imgproc | |
| 22 | 4 | Vadim Pisarevsky | |Daniil, Oleg | android, misc | |
| 23 | 4 | Vadim Pisarevsky | |Vadim | patches, misc | |
| 24 | 4 | Vadim Pisarevsky | |Vsevolod| documentation| |
| 25 | 5 | Vadim Pisarevsky | | ... | ... | |
| 26 | 1 | ||
| 27 | 1 | Issues priorities in descending order: |
|
| 28 | 1 | * bug with provided solution (Patch with High priority) |
|
| 29 | 1 | * bug (from High to Low priorities) |
|
| 30 | 4 | Vadim Pisarevsky | * patch (implementing a new feature) |
| 31 | 1 | * feature |
|
| 32 | 1 | ||
| 33 | 1 | h3. Hacker Guide |
|
| 34 | 1 | ||
| 35 | 2 | Vadim Pisarevsky | You should write a test before the bug fix. This is very important to see your test failing, because later it will control regressions. Then, if you see it failing, you can fix the bug. This idea is very close to TDD's "Reg-Green-Refactor":http://blog.goyello.com/2011/09/13/red-green-refactor-cycle/ mantra. |
| 36 | 1 | ||
| 37 | 1 | Preferred sequence of actions: |
|
| 38 | 5 | Vadim Pisarevsky | * assign issue to yourself. You should choose some issue from the list of "hackathon issues":http://code.opencv.org/projects/opencv/issues?query_id=30 |
| 39 | 5 | Vadim Pisarevsky | * reproduce problem first, if it's a bug. If possible, add the test that reproduces the problem. |
| 40 | 5 | Vadim Pisarevsky | * fix problem. When you have compiling but failing test you can modify OpenCV to satisfy the test |
| 41 | 1 | * commit changes to the repository. In commit message you should use #$$$$ template to link it with the issue. |
|
| 42 | 1 | * change issue status to _Done_. You should use commit:<6-digit git commit hash> template in issue updating. Please don't change _Target version_. |
|
| 43 | 1 | ||
| 44 | 5 | Vadim Pisarevsky | If in doubt, please, assign the ticket to vadim pisarevsky before or after commit. |
| 45 | 1 | ||
| 46 | 1 | h3. Links |
|
| 47 | 1 | ||
| 48 | 1 | * "OpenCV hackathon slides":https://docs.google.com/a/itseez.com/presentation/d/1IvUOXAJ7FYO2NhplYTGJ0MvTjzKhJnSRano22yuaho4/edit#slide=id.gae260d7_1_17 |
|
| 49 | 1 | * "About hackathon":http://en.wikipedia.org/wiki/Hackathon |